MDS 9124 reset Reason: Reset triggered due to HA policy of Reset

Luis Policarpo · ‎09-03-2014

Hi,

4 MDS 9124 switches rebooting with the same strange behavior. The problem occurs if we have instability (e.g. spanning-tree calculation problems) on the LAN where the management interfaces are connected.

ciscomds11# show version

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

BIOS: version 1.0.16

loader: version N/A

kickstart: version 4.2(3)

system: version 4.2(3)

BIOS compile time: 10/23/08

kickstart image file is: bootflash:/m9100-s2ek9-kickstart-mz.4.2.3.bin

kickstart compile time: 10/26/2009 0:00:00 [12/05/2009 05:47:54]

system image file is: bootflash:/m9100-s2ek9-mz.4.2.3.bin

system compile time: 10/26/2009 0:00:00 [12/05/2009 07:07:26]

Hardware

cisco MDS 9124 (1 Slot) Chassis ("1/2/4 Gbps FC/Supervisor-2")

Motorola, e500 with 516136 kB of memory.

Processor Board ID JAF1223ASFS

Device name: ciscomds11

bootflash: 254464 kB

Kernel uptime is 0 day(s), 22 hour(s), 39 minute(s), 49 second(s)

Last reset at 569578 usecs after Mon Sep 1 12:25:37 2014

Reason: Reset triggered due to HA policy of Reset

System version: 4.2(3)

Service: sysmgr stateful recovery

ciscomds11#

Can anyone please help? Thanks

Luis Policarpo

Keny Perez · ‎09-04-2014

When was the last time the MDS was rebooted? I remember an old bug that reboots devices after 700+ days up (fixed already) and that might be causing the issue here...

-Kenny

Luis Policarpo · ‎09-05-2014

Hi Kenny,

thats not the issue. The customer made a change on a switch that provoked a major problem on the spanning-tree calculation in the network. After that ALL 4 MDSs rebooted simultaneously with the same reason.

I think the problem is related with this bug: https://tools.cisco.com/bugsearch/bug/CSCTJ68614.

Thanks.

Luis

Luis Policarpo · ‎09-09-2014

Hi,

upgraded to software version 4.2(9) and problem solved.

Thanks,

Luis