Stack auto-unit-replacement showing NO

[bbooth]

I have a stack of 3 switches (SW:6.0.4.020 / FW 6.0.0.6) and discovered that when I performed the command - "show stack auto-unit-replacement", I see that "ready for replacement" is showing NO on all of them. This stack is the only one showing NO.

Have anyone seen this before and know what needs to be done to fix it?
I also perform the command from config terminal “stack auto-unit-replacement enable” and rechecked, nothing changed.

02D-5520A#show stack auto-unit-replacement
Auto Unit Replacement Auto-Restore: Enabled
Auto Unit Replacement Auto-Save: Enabled

UNIT # LAST CONFIG-SAVE TIME-STAMP READY FOR REPLACEMENT
Unit 1 159 days 10:21:58 NO
Unit 2 172 days 07:10:02 NO
Unit 3 000 days 00:00:00 NO



Thanks!

[ldutirou]

Hello,

One of my customers has got exactly the same behavior on its stacks. We discovered that it appears when “autosave” is disabled on the stack, which is not the default state. After enabling autosave globally, we can see that “ready for replacement” turns to YES for all units but it can take up to an hour.
We are running version 6-3-0 on pure stacks of ERS 5650.
Hope this help.
Regards,
Laurent.

Sorry, I didn’t notice your question on the network infrastructure forum… There is a solution document published on Avaya’s (Doc ID: SOLN201998) saying that upgrade to 6-2-4 solved the issue. Do not go further in versions, the problem is back in 6-3-0.
Regards,
Laurent.

[bbooth]

Thanks! However show autosave is Enabled. I will upgrade the s/w and f/w as they are quite old now.

[bbooth]

Fixed

After a FW/SW upgrade to 6.0.0.21 / 6.3.5.024 the problem is fixed.

02D-5520A#show stack auto-unit-replacement
Auto Unit Replacement Auto-Restore: Enabled
Auto Unit Replacement Auto-Save: Enabled

UNIT # LAST CONFIG-SAVE TIME-STAMP READY FOR REPLACEMENT
Unit 1 010 days 15:05:09 YES
Unit 2 010 days 15:04:57 YES
Unit 3 010 days 15:05:07 YES
Unit 4 010 days 15:05:08 YES