Page 1 of 1

CS Debug: STR NON FATAL

Posted: 21 Dec 2011 21:11
by jacky
Hey guys,

I got this OS6850-P48X 6.4.3.779.R01 switches that give me below error log once. I'm don't know why suddenly the NI 1 & 2 switch down and after a few minutes
(20minutes i think), it up again. Have you all ever experience this issue?

Any ideas?

STACK-MANAGER info == SM == Stacking link A status changed: DOWN
STACK-MANAGER info == SM == Stacking link B status changed: DOWN
CSM-CHASSIS alert ******* CS Debug: STR NON FATAL ********
CSM-CHASSIS alert Source file name : cs_csm_fsm_util.c
CSM-CHASSIS alert Line number in the file: 3229
CSM-CHASSIS alert Error number : 00000000
CSM-CHASSIS alert Comments : zcSendto Failed, return code: -6
CSM-CHASSIS alert ******* CS Debug: STR NON FATAL ********
CSM-CHASSIS alert Source file name : cs_csm_fsm_util.c
CSM-CHASSIS alert Line number in the file: 3229
CSM-CHASSIS alert Error number : 00000000
CSM-CHASSIS alert Comments : zcSendto Failed, return code: -6
STACK-MANAGER info == SM == Primary change reset connection (old 0, new 4, prev 1)
CSM-CHASSIS info == CSM == IDLE received PRIMARY role - TAKEOVER in Progress ...
CSM-CHASSIS alert == CSM == loading config_manager.lnk from /flash/working/Kbase.img
HSM-CHASSIS info == HSM == HsmTakeover() From IDLE to PRIMARY otherCMM=0
HSM-CHASSIS warning == HSM == IDLE TO PRIMARY.Setting forceNiTakeover to TRUE.
HSM-CHASSIS info T1:Ni Insertion detected on slot 4

Thanks guys

Re: CS Debug: STR NON FATAL

Posted: 24 Dec 2011 15:33
by one6f
Hi jacky,
I understand you have an 2xOS6850-P48X stack which permanent rebooted or takeover.
If it is the case try to isolate this issue, detach stack cable and start each module alone.
On the console you get detailed output.
If a stand alone module gone down after 20-30 min. you have may be corrupted RAM.

Re: CS Debug: STR NON FATAL

Posted: 06 Feb 2012 11:05
by jiggsy72
When you stack just two chassis, do you need to use 2 stacking cables or will one do? And does using 2 add any benefit?

Re: CS Debug: STR NON FATAL

Posted: 07 Feb 2012 04:26
by one6f
Hi,
normally you need a ring in the stack, hence you need to use both stacking cables in 2xstack, in production anyway.
Raw Capacity: 24Gbps FD (12Gbps FD “Stack-A” and 12Gbps FD “Stack-B”)
Throughput: The Stacking (Stack “A” & Stack “B” run at 10G) supports 2x10 GigabitEthports at wire-speed: 2 * 14,880,952.3 pps = 29,761,904.6pps (approx: 29.8Mpps)
To avoiding split stacks use the redundant stacking cable. In order to avoid isolated modules within the virtual chassis, simply make sure that a redundant stacking cable connection exists between the top- most and bottom-most switches at all times.