Save configuration error

[Fauriant_Trista]

During a maintenance, after doing some changes on a stack configuration (stack composed of 2 x460 and one x440), we wanted to save the configuration on the primary so we've done the following command:

The configuration file primary.cfg already exists.
Do you want to save configuration to primary.cfg and overwrite it? (y/N) Yes

After that we received this message:

Error: This command cannot be executed during configuration save.

But after looking, we don't find how to verify the saving process. The only thing that we have found is the last save which was tried was done by the Ridgeline server three days ago:

09/20/2015 19:06:23.72 Slot-1: x.x.x.x (telnet) userXXX: SAVE CONFIGURATION

But the last configuration done apparently have been made last June 1st (below output of show switch command)

primary.cfg Created by ExtremeXOS version 15.5.3.4
1053995 bytes saved on Mon Jun 1 01:37:34 2015

Please, how can I verify and release the saving process (other than reboot) ?

Thanks a lot.

Tristan

[Fauriant_Trista]

Last Sunday, we've made the modification for the synchronization of the slot 2, but unfortunately after the reload of this slot, it was always not synchronized, a reboot of the entire stack has been made and the synchronization is now ok.

Thanks for your support.

[Fauriant_Trista]

Prashanth, responses to your questions :

System UpTime: 214 days 21 hours 50 minutes 19 seconds (for the stack)

Yes the stack was synced during the last maintenance window. But I've seen that the slot 2 have reboot during the last months many time for unexpected reasons. Here the log of the last reboot :

08/24/2015 01:06:05.88 Slot-1: Module in Slot-2 is operational
08/24/2015 01:06:01.33 Slot-1: Done synching ACLs to Slot-2
08/24/2015 01:06:00.87 Slot-1: Synching ACLs to Slot-2
08/24/2015 01:05:40.07 Slot-1: Slot-2 being Powered ON
08/24/2015 01:05:37.05 Slot-1: Module in Slot-2 is inserted
08/24/2015 01:02:55.57 Slot-3: Slot-2 FAILED (1) Not In Sync
08/24/2015 01:02:55.56 Slot-3: BACKUP NODE (Slot-2) DOWN
08/24/2015 01:02:54.07 Slot-1: Slot-2 down, resetting all TCP connections to it
08/24/2015 01:02:54.07 Slot-1: Module in Slot-2 is removed
08/24/2015 01:02:53.48 Slot-1: BACKUP NODE (Slot-2) DOWN
08/24/2015 01:02:53.29 Slot-1: Slot-2 down, resetting all TCP connections to it
08/24/2015 01:02:53.29 Slot-1: Module in Slot-2 is removed

I'm not aware of changes in the last months, I've checked the show debug system-dump and nothing is present. We'll try to resynchronize the slot next Sunday, I will make a feedback when it's done.

[Prashanth_KG]

Just to investigate why it went to this state, share the following details:

whats the uptime of the stack?
Was it in Sync since the boot of the slot 2?
Were you aware of any recent changes made to this stack like adding / modifying the details in Ridgeline etc.,

Lets see if we can get a clue for the trigger.

And just to set the expectation right..
Finding the root cause might be difficult as the stack is already in the failed state and the recovery option would require a reboot.

[Prashanth_KG]

Hi Tristan,

Thank you for sharing the details. Only way to synchronise the slots would require the reboot of the target slot.

synchronize slot

This will reboot the mentioned slot number and during the bootup, it will be synchronized.

Hope this helps!