Chassis: 8212zl J9091A - Management module failover failed

[mudvayne15]

Good day everyone,

Just want to ask what could probably the cause of not failing over to the standby module. 

Below is an old log and it just happens again today. I had no access on the switch remotely so I opt to hard boot the switch. 

Is there any way to identify if the management module is already faulty? I am very new to HP Procurve. 

!LOGS
I 07/29/19 04:57:05 00063 system: xM2: Mgmt Module 1 went down: 07/29/19
04:56:47
M 07/29/19 04:57:05 00064 system: xM2: Software exception at alloc_free.c:495 --
in 'Inet
I 07/29/19 04:57:05 00266 system: xM2: Resetting Mgmt Module 1
W 07/29/19 04:57:05 00268 system: xM2: Mgmt Module 2 - Failover occured
I 07/29/19 04:57:05 00061 system: xM2: -----------------------------------------
I 07/29/19 04:57:05 02759 chassis: AM2: Savepower LED timer is OFF.
I 07/29/19 04:57:06 00937 chassis: AM2: Fabric 1 inserted
I 07/29/19 04:57:06 00937 chassis: AM2: Fabric 2 inserted
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

phmnlccent-sw-1# show version
Management Module 1: Standby
Image stamp: /sw/code/build/btm(K_15_03)
Feb 3 2011 21:05:19
K.15.03.0007
68
Boot Image: Primary

Management Module 2: Active
Image stamp: /sw/code/build/btm(K_15_03)
Feb 3 2011 21:05:19
K.15.03.0007
68
Boot Image: Primary
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

phmnlccent-sw-1# show redundancy detail

Slot Role Module Up Since State Since State
---- -------- ------------------- ------------------- -----------------
MM1 Standby 07/29/19 13:56:19 07/29/19 04:57:04 Standby
MM2 Active 07/29/19 13:58:23 07/29/19 04:57:03 Active

Failover Log:

Slot Role Time Reason
---- -------- ------------------- ---------------
1 Active 07/29/19 04:56:47 Active Reset
1 Active 07/29/19 04:56:47 Crash

[parnassus]

You're dealing with a Switch running a HP ProVision NOS softwre release published almost 9 Years ago (K.15.03.0007 - February 2011) that experienced a MM crash: give it an update wouldn't be a good idea? maybe - just a guess - MM crash(es) could be related to software bugs solved along these years. Have a look here.

Hope to be right: your Switch's MMs redundancy worked...MM1 (Active MM) crashed and consequently your MM2 (Standby MM) took over. Isn't it? 

[mudvayne15]

Thank you, we already have scheduled the switch firmware upgrade. The problem is that it did not failover to the standby module.  The logs I had is 3 months old from a different engineer. 

[parnassus]

I'm sorry! my fault...I read your post on the phone and I was in a hurry...didn't notice logs provided were about an old issue. At this point I strongly suggedt you to plan an update. Read carefully Release Notes to discover if a BootROM update is required...it will be (automatically) performed so a two-reboots update need to be considered.