Page 1 of 1

Issue with saving config with a stack

Posted: 15 May 2025 09:24
by Cristek
Hello all.
I'm having issues saving a config of this particular stack config.
I can see the stack is working (and there's no issues at this site reported by the customer) but I've done a few vlan changes and I am now unable to save my work. I've tried:
- write memory flash-synchro
- copy running certified flash-synchro
- copy running certified
And I always get the same outcome as below:

Code: Select all

something-> 
something-> 
something-> show virtual-chassis topology 
Legend: Status suffix "+" means an added unit after last saved topology

Local Chassis: 1
 Oper                                   Config   Oper                          
 Chas  Role         Status              Chas ID  Pri   Group  MAC-Address      
-----+------------+-------------------+--------+-----+------+------------------
 1     Master       Running             1        100   199    94:24:e1:f3:3c:c7
 2     Slave        Running             2        100   199    94:24:e1:f3:53:4d

something-> 
something-> 
something-> wr m f

File /flash/working/vcsetup.cfg replaced.

File /flash/working/vcboot.cfg replaced.

Thu May 15 14:12:58 : flashManager Main INFO message:
+++ Verifying image directory working on CMM flash
Please wait...

Thu May 15 14:13:27 : ChassisSupervisor bootMgr INFO message:
+++ Copy running to certified: Synchronizing chassis 2
Thu May 15 14:13:27  flashManager Main ERR Missing or empty image file Taos.img
Thu May 15 14:13:27  flashManager Main ERR Image verify failed

Thu May 15 14:13:27 : ChassisSupervisor bootMgr ERR message:
+++ Copy running to certified failed on chassis 2
ERROR: Copy running to certified succeeded; Secondary synchronization failed

something-> 
something-> 
something-> 
something-> sh microcode 
   /flash/working
   Package           Release                 Size     Description
-----------------+-------------------------+---------+-----------------------------------
Taos.img          5.2.7.R07                 76007652  Alcatel-Lucent OS

OHaras-Sw1-Maincomms-> sh microcode loaded 
   /flash/working
   Package           Release                 Size     Description
-----------------+-------------------------+---------+-----------------------------------
Taos.img          5.2.7.R07                 76007652  Alcatel-Lucent OS

OHaras-Sw1-Maincomms-> sh microcode working 
   /flash/working
   Package           Release                 Size     Description
-----------------+-------------------------+---------+-----------------------------------
Taos.img          5.2.7.R07                 76007652  Alcatel-Lucent OS

OHaras-Sw1-Maincomms-> sh microcode certified 
   /flash/certified
   Package           Release                 Size     Description
-----------------+-------------------------+---------+-----------------------------------
Taos.img          5.2.7.R07                 76007652  Alcatel-Lucent OS

something-> 
something-> 
something-> 
Any ideas you can pass on to point me in the right direction?
And if I have to do schedule a reboot to fix this, is there a chance it wont come back due to a bigger problem?

Re: Issue with saving config with a stack

Posted: 15 May 2025 13:30
by silvio
check at the second chassis for the missing files. Maybe you have to copy them manually.
If the issue persists save your config to your pc and reload the whole vc.
BR Silvio

Re: Issue with saving config with a stack

Posted: 16 May 2025 04:40
by Cristek
Hi,
My mind was going that direction as well, but I was afraid to mess with it remotely. It's a 2h drive each way for the closest engineer :)
Also it's a Friday and they work weekends so I was afraid of doing too many changes.

So, I've logged into this stack and then SSH'd into the 2nd switch on the stack (ssh 127.10.2.65) and then I did a copy of the TAOS.IMG from working to certified. The command went through just fine, and then I SSH back to the main switch and I got the same error when saving.

This is as much as I tried as today is a Friday.
Also this following image shows the contents of both directories (left is the main switch, and right is the 2nd switch on the stack):
https://ibb.co/gMw1bQFh

If I have to go onsite, then I have to go onsite and there's nothing I can do, but any additional ideas are very much welcome :)

Re: Issue with saving config with a stack

Posted: 19 May 2025 09:35
by silvio
Hi,
the image is the same at both chassis in both directories (same size too).
Because "write memory" is working, also a remote reload should work.
You can check with "image integrity check working key-file imgsha256sum" and the same for certified.
If this is okay, you can at night do a "reload from working rollback-timeout 15". If you have access to the switch after the reload please do "reload cancel".
Otherwise the switch will reboot again - but from certified.
BR Silvio