10-08-2013 10:39 PM - edited 03-07-2019 03:55 PM
Hi All,
We are facing issue that 2960-stack switches are rebboted automatically after configuring Dynamic ARP Inspection (DAI).
We have removed the arp access-list configured for static IP in DAI confighuration then it stop rebooting.
Switch IOS : c2960s-universalk9-mz.150-1.SE3
We are suspecting bug from Crash file:
CSCuj39096 - 2960S switches crashing due to hwidb corruption
Externally found severe (Sev2) bug: A-Assigned
05863: 000063: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: System previously crashed with the following message: (Switch-2)
005864: 000064: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: Cisco IOS Software, C2960S Software (C2960S-UNIVERSALK9-M), Version 15.0(1)SE3, RELEASE SOFTWARE (fc1) (Switch-2)
005865: 000065: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: Technical Support:
http://www.cisco.com/techsupport
(Switch-2)
005866: 000066: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: Copyright (c) 1986-2012 by Cisco Systems, Inc. (Switch-2)
005867: 000067: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: Compiled Wed 30-May-12 14:35 by prod_rel_team (Switch-2)
005868: 000069: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: Debug Exception (Could be NULL pointer dereference) Exception (0x2000)! (Switch-2)
005869: 000070: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: (Switch-2)
005870: 000071: Oct 8 10:16:55.096 UTC: %PLATFORM-1-CRASHED: SRR0 = 0x018D6E78 SRR1 = 0x00029230 SRR2 = 0x01DD20FC SRR3 = 0x00029230 (Switch-2)
10-09-2013 12:20 PM
Hi Pawan,
I analyzed this issue and this behaving is matching the below DDTS,
CSCts90288 - 2960S stack crashed after "no ip arp inspection" on an interface
The crash occurred after upgrading the code on the 2960 stack from 12.2(55)SE to 12.2(58)SE2. After upgrading the code customer tried entering the command "ip arp inspection trust" or "no ip arp inspection trust" under any interface.
When customer enter either command on a member switch port or a master switch port, all the member switches crash. customer downgraded back to 12.2(55)SE.
The problem is seen only on 15.0(1)SE train, there are no planned rebuild on this branch.
PS: The problem is not seen on 15.0(2)SE train.
Regards,
Aru
*** Please rate if the post is useful ***
10-09-2013 04:03 PM
I'd stay away from 15.0(1)SE-train. It's riddled with bugs.
Try 15.0(2)SE4 instead.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide