Unsolved
This post is more than 5 years old
4 Posts
0
1612
January 13th, 2018 06:00
Stack-problem 6224+6224f+6224F - Get Critical Error
Hello.
This type of models have beed workind around 2 years, but today was a major problem, i want to change speed on on LAG channel and lost connect to the units, All!!! Get connection by COM-port see this issue wich i never seed before._______________
saving crash record in crashdump.2
NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
nimTask 6130630 255 SUSPEND 0x1e71e24 6130090 3d0002 0
stack: base 0x6130630 end 0x6128630 size 32768 high 7584 margin 25184
options: 0x1009001
vector: 0x9999
Stack Trace:
0x1e71e24: taskSuspend (0x1e719e8) + 0x43c
0x6a3d6c: log_error_code (0x6a3c84) + 0xe8
0x054128: hapiBroadPhyModeSet (0x538dc) + 0x84c
0x04bd54: hapiBroadIntfAutoNegotiateConfig (0x4bac8) + 0x28c
0x0104f4: dapiCtl (0x10128) + 0x3cc
0x678ad8: dtlIntfNegotiationCapabilitiesSet (0x6788bc) + 0x21c
0x6bad34: nimSetIntfAutoNegoStatusCapabilities (0x6baabc) + 0x278
0x6ab7f4: nimIntfConfigApply (0x6ab6f8) + 0xfc
0x6af9a4: nimNotifyUserOfIntfChange (0x6af640) + 0x364
0x6b0ef4: nimTask (0x6b0d7c) + 0x178
0x1dbec60: vxTaskEntry (0x1dbec04) + 0x5c
r0 = 1274f80 sp = 6130090 r02 = 0 r03 = 0
r04 = 6130210 r05 = 4c r06 = 0 r07 = 0
r08 = 0 r09 = 75d6a64 r10 = 6130630 r11 = 1
r12 = 6130630 r13 = 0 r14 = 0 r15 = 0
r16 = 0 r17 = 0 r18 = 0 r19 = 0
r20 = 0 r21 = 0 r22 = 0 r23 = 0
r24 = 0 r25 = 0 r26 = 0 r27 = 0
r28 = 0 r29 = 2d6399c r30 = 6b0d7c r31 = 6130630
1274f80 ctr = lr =
1e71e24 pc =
cr =
20000882 xer = V 0
_____________________________________
I mention that in this case master switch reboot's and all unit do the same.. scarry thing :) I discontect all units from stacking ports,(stacking is done by manual. all it's ok cables to) master unit (6248) boot's perfectly and work done, even don't lost configuration, then i do this to second -6224f, BUT when i connect back 3 unit wich is 6224f all goe's down, i catch only this errror, and all stack go to reboot.
Please help with this problem.
Anythig was going ok about 2 years, not a single reboot.
0 events found
icecybe14
4 Posts
0
January 15th, 2018 11:00
Hi hi.
Thank you for reply
Swtiches :
1. 3.3.14.2
2. 3.3.14.2
3. Not Available
I use command for no negotiation for one port from lagg port. wich i previously removed from lagg.
The 3-rd unit can't work standalone because didn't configured as is, but when i boot alone with console port unit boot's normaly and wait for master unit to assign.
The rest of the stack operate now normally. But i never believe that simple : no negotiation, command cand collapse all stack from 96 port. Firmware of 3-rd stack are the same.
Now i am under some doubt's to connect back stack or not.
icecybe14
4 Posts
0
January 15th, 2018 15:00
I see, but for my bad or good i configured 3-rd from start to be NOT standalone unit if the stack connection goe's down. Now i'm accesing verry well the master unit and the 3-rd unit stand-alone by com-port
Also i noticed one strange thing, the 3-rd unit have port-channel with contain 3/g1-3/g3 ports, and all ports have 100mb/s wich is wrong, on other side of the switch are dell 6024 wich see lagg on 1g port, so i try to use NO negociation function, didn't work because port 3/g1 was in lagg i removed form lagg and use #no negotiation .........stack dead.
This can't be so critical error to shut down all stack, i want to say that i try to find out the root of the problem. Because i can rebuild stack back.. BUT if i didn't find problem s-it can happen any time...
no logic in this. Also i will try to switch images (use back-up image) maybe this can be the problem.
I can suggest only few: memory leak or firmware broken. As i see when stack is on-line, master stack start to load startup-conf and...when it arrive on : negotiation 3/g1 ... eror system cause critical error and master try to boot again...error i catch i printed in first message.
upd: on the master switch are too many interesting files, like
core-stack#show dir
File name Size (in bytes)
------------- ---------------
vpd.bin 256
log2.bin 262132
slog2.txt 2960
boot.dim 72
olog2.txt 0
backup-config 19829
hpc_broad.cfg 148
image1 9732180
slog1.txt 18944
startup-config 19910
fastpath.cfg 392
crashdump.ctl 356
sslt.rnd 1024
crashdump.3 33848
dh512.pem 156
dh1024.pem 245
AutoInstallTmpScript.scr 0
logNvmSave.bin 64
image2 9732180
olog1.txt 35520
crashdump.1 33848
crashdump.2 33848
slog0.txt 2368
asset.tag 17
TempConfigScript.scr 17213
crashdump.0 33848
running-config 19910
fastpathRun.cfg 392
core-stack#