Auto-Persistence of Configuration Data

All configurations performed on the device are automatically persisted. You do not need to perform copy running-config startup-config explicitly to persist the configuration.

Configurations are saved to a persistent configuration datastore. During device bring-up, configurations are replayed from this datastore. If the datastore becomes unusable for any reason, configurations are replayed from a startup-file.

By default, the startup-file has the factory-default configuration. This startup-file is updated with datastore entries whenever user executes copy running-config startup-config.

Configuration Replay during Device Boot

By default, configurations are replayed from the datastore when the device boots up. However, after the execution of either of the below operations (and reboot), configurations will be replayed from the startup-file instead of the database.

copy default-config startup-config
Copy <tftp:/scp:/ftp:/usb:/flash:>/<file> startup-config

Upgrade and Downgrade Considerations

Before a firmware upgrade or downgrade, it is mandatory to execute copy running-config startup-config. This will ensure that the startup-file is in sync with the configuration datastore.

Command Information

The following examples illustrate how to display the default, startup, and running configurations.

Displaying the Default Configuration:
To display the default configuration, enter show file with the default configuration filename, in privileged EXEC mode.
```
(device)# show file defaultconfig.standalone
```
Displaying the Startup Configuration
To display the contents of the startup configuration, enter show startup-config, in privileged EXEC mode.
```
(device)# show startup-config
```
Displaying the Running Configuration
To display the contents of the running configuration, enter show running-config in privileged EXEC mode.
```
(device)# show running-config
```

The show startup-database command has been deprecated.