Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

STMI4 Reboot

Status
Not open for further replies.

kevin906

MIS
Aug 4, 2006
167
US
STMI4 Card rebooted and reloaded itself.
I have not seen the associated error message before.
Anyone else seen this and have any ideas?
Not sure if the customer network was a contributor or if this card is suspect.
The NCUI card on the same shelf showed no issues during this event and it's in the same subnet.
I have not pulled the logs from the STMI4 card as they are fairly cryptic.

F5749 N3535 RESET BPA BOARD LW REQUEST 19-12-10 14:43:41
PEN:1-18-007-000 Board:STMI4/1 PartNo:Q2324-X500
REASON:03H SIGNALING AND IMMEDIATE RESET OF BOARD
MSG_CAT_HSA_REBOOT

F5749 N3536 RESET BPA BOARD LW REQUEST 19-12-10 14:43:41
PEN:1-18-007-000 Board:STMI4 PartNo:Q2324-X500
REASON:03H SIGNALING AND IMMEDIATE RESET OF BOARD
MSG_CAT_HSA_REBOOT

F5749 N3537 RESET BPA BOARD LW REQUEST 19-12-10 14:43:41
PEN:1-18-007-000 Board:STMI4 PartNo:Q2324-X500
REASON:03H SIGNALING AND IMMEDIATE RESET OF BOARD
MSG_CAT_HSA_REBOOT

F5749 N3538 RESET BPA BOARD LW REQUEST 19-12-10 14:43:42
PEN:1-18-007-000 Board:STMI4 PartNo:Q2324-X500
REASON:03H SIGNALING AND IMMEDIATE RESET OF BOARD
MSG_CAT_HSA_REBOOT

F5345 N3539 TEMPLOCK BPA BOARD INIT ERROR 19-12-10 14:43:42
PEN:1-18-007-000 Board:STMI4 PartNo:Q2324-X500

F5354 N3540 OUT SERV BPA BOARD SECONDARY OUT ATTEND L 19-12-10 14:44:32
PEN:1-18-007-000 Board:-- PartNo:--


F5350 N3542 IN SERV BPA BOARD SECONDARY IN ATTEND L 19-12-10 14:44:39
PEN:1-18-007-000 Board:-- PartNo:--

----------------------------------------

System Release Info


PROGRAM SYSTEM : Y0-E30YC
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4801BH6012|V6 R1.12.60
PROGRAM SYSTEM WITH CODE SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS

PROGRAM SYSTEM : Y7-P3TYT
VERSION NUMBER : 60
CORRECTION VERSION NUMBER : 001
PART NUMBER : P30252N4801U00013|V6 R1.13.10
PROGRAM SYSTEM WITH TEXT SUBSYSTEMS
INTERFACE VERSION:
PROGRAM SYSTEM DOES NOT CONTAIN ANY INTERFACE VERSIONS


 
When I had a 4000, I used to see that behavior once every couple of months. Nobody could ever figure out why. Replacing the card didn't seem to have any effect. There are some things you can do to minimize the impact.

Use both network connections on the STMI cards. If configured right, the card will use either network connection. (In WBM, set "Use the Second LAN as: Redundancy for LAN1) I'd run them to different switches if you have the option. That keeps the paths separate and allows you to reboot one switch without dropping the STMI card. Only one port will be active at a time.

If you have extra STMI cards, set your cards up in board pools. (AMO: BPOOL) If there is a card failure, the system will switch the card "bad" and move everything to a spare card. It does take a couple of minutes to swap, but it's better than being hard down for an extended time. Usually rebooting the "bad" card will make it "good" again. I rarely every had actually "bad" STMI cards.

I think the STMI cards rebooting may be related to an overload condition or some sort of firmware bug. We were never able to figure out what caused the cards to fail like they did. We've been quite happy since migrating to an OSV system.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4 & V6, OpenScape Xpressions V7, OpenScape Contact Center V8, OpenScape Voice V9
 
There's a known problem in V6 with reloading of STMI cards.
I can't find the link now but it more or less said to upgrade.
If I find it I will post it here.
I have one customer with the problem, you could try reloading it via CRON maybe once a week at a low traffic time.
 
Make sure also that you have the lates LW for the STMI board:
PZKSTI40 LW A2.004-013
 
The other possibility is the primary network connection "winked" as I have had that happen here on occasion, and suspect it's when someone is adding or removing network connections from the network switch and they wiggle it or something. In my case we have redundant network connections on all those cards and it just flips over to the other one and then flips back.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top