Persistence of Securestack Configurations after a Config Change
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-07-2013 02:16 PM
Article ID: 5482
Products
SecureStack
C5-Series, C3-Series, C2-Series
B5-Series, B3-Series, B2-Series
A4-Series, A2-Series
Commands
'save config'
'set snmp persistmode'
Goals
Save the configuration
Save to startup
Save active
Changes
Changed configuration
Rebooted the switch
Symptoms
Lost configuration
Configuration not being saved
Cause
Any entered switch or router configurations are implemented immediately, becoming part of the active configuration.
However, upon completion of configuration changes, an extra step is required in order to save the changes sooner than after up to two minutes on a standalone or master unit or after up to 30 minutes across a stack. If this is not done, then the configuration changes may be lost upon the next SecureStack reboot.
The following information comes from the SecureStack Configuration Guides.
Configuration Persistence Mode
The default state of configuration persistence mode is "auto", which means that when CLI configuration commands are entered, or when a configuration file stored on the switch is executed, the configuration is saved to NVRAM automatically at the following intervals:
You can change the persistence mode from "auto" to "manual" with the 'set snmp persistmode' command. If the persistence mode is set to "manual", configuration commands will not be automatically written to NVRAM. Although the configuration commands will actively modify the running configuration, they will not persist across a reset unless the 'save config' command has been executed.
The 'show snmp persistmode' command may be used to view the current persistence mode setting.
Solution
FAD (Functions as Designed).
To avoid possible configuration loss:
Products
SecureStack
C5-Series, C3-Series, C2-Series
B5-Series, B3-Series, B2-Series
A4-Series, A2-Series
Commands
'save config'
'set snmp persistmode'
Goals
Save the configuration
Save to startup
Save active
Changes
Changed configuration
Rebooted the switch
Symptoms
Lost configuration
Configuration not being saved
Cause
Any entered switch or router configurations are implemented immediately, becoming part of the active configuration.
However, upon completion of configuration changes, an extra step is required in order to save the changes sooner than after up to two minutes on a standalone or master unit or after up to 30 minutes across a stack. If this is not done, then the configuration changes may be lost upon the next SecureStack reboot.
The following information comes from the SecureStack Configuration Guides.
Configuration Persistence Mode
The default state of configuration persistence mode is "auto", which means that when CLI configuration commands are entered, or when a configuration file stored on the switch is executed, the configuration is saved to NVRAM automatically at the following intervals:
- On a stand-alone unit, the configuration is checked every two minutes and saved if there has been a change.
- On a stack, the configuration is saved across the stack every 30 minutes if there has been a change.
You can change the persistence mode from "auto" to "manual" with the 'set snmp persistmode' command. If the persistence mode is set to "manual", configuration commands will not be automatically written to NVRAM. Although the configuration commands will actively modify the running configuration, they will not persist across a reset unless the 'save config' command has been executed.
The 'show snmp persistmode' command may be used to view the current persistence mode setting.
Solution
FAD (Functions as Designed).
To avoid possible configuration loss:
- With persistmode at either setting, issue the 'save config' command (with the C2, requires firmware 2.01.22 or higher), to immediately save the changes to NVRAM;
- With persistmode at the default "auto" setting, wait at least two full minutes following a configuration change before powering down or resetting the unit/stack;
- With persistmode at the default "auto" setting, issue the 'reset' command, to immediately save the changes to NVRAM and reset the unit/stack: SecureStack(rw)->reset Are you sure you want to reload the stack? (y/n) y Saving Configuration to stacking members Reloading all switches.If your intent is to power down the unit/stack rather than resetting it, you may safely power down the unit(s) at any time after the reboot has begun.
0 REPLIES 0
