Persisting SLX Configurations

SLX 20.1.1 Behavior

In SLX 20.1.1, configuration management process maintains two databases.

• Running-DB maintains the running configuration.
• Startup-DB maintains the persisted configuration which is created or updated when the copy running-config startup-config command is executed.

SLX OS maintains a startup file which is an ASCII file saved in flash when running-config is copied to startup-config. The startup file can also be updated by any ASCII config from outside the switch. By default, when system reboots, the SLX OS replays the configuration from the Startup database. The user can modify the Startup file to replay the configuration if required. It is also done in some exception cases like firmware upgrade or DB corruption.

Maintenance mode can be enabled by configuring enable under system-maintenance configuration mode. If the configuration is persisted, the switch needs to be in maintenance mode before reloading for it to come back in maintenance mode.

SLX 20.1.2 Enhancement

In SLX 20.1.2, all the configurations are stored in one database which also persists.

• The show running-config command always fetches the configuration from the database.
• The copy running-config startup-config command keeps a copy of the startup-file in flash.
• Checkpoint creations for rollback operations depend on the database.
• After a upgrade or downgrade, replaying the startup-file resumes the database cleanup operations.

Maintenance mode can be enabled by configuring enable-on-reboot under system-maintenance configuration mode. After the reboot, the switch comes back up in maintenance mode and remains operational.

SLX(config-system-maintenance)# enable-on-reboot
SLX(config-system-maintenance)# [no] enable-on-reboot

The system maintenance turn-off command brings the system out of maintenance mode.