Commands to Save a Configuration to a File

You can save both the local and shared configuration of the C Series Controller. The local (slot) configuration is configuration data that is stored in a C Series Controller’s local file system. Shared configuration is configuration data that is stored in the Juniper Networks database. The Juniper Networks database can be in standalone mode or community mode. SSH host keys and the SRC component states (enable/disable) are automatically saved together with other configuration data.

Saving and loading the configuration allows you to fully restore a C Series Controller to the configuration and operational state based on which configuration you save and load. For example, you can restore a system to the factory-default, reinstall a system, or deploy a new system configuration from the saved configuration.

Saving and loading the local configuration allows you to restore a C Series Controller host that uses the Juniper Networks database community for the source of the shared configuration. Saving and loading a shared configuration can be used to restore C Series Controller hosts that have the Juniper Networks database set to standalone mode. In certain cases, it can also be used to restore systems running in a Juniper Networks database community.

You can use the following commands in configuration mode to save the configuration to a text or XML file:

You can save the configuration data in either a text or XML file.

SSH Host Keys

When you execute the save local or save command at the top or system edit level, SSH host keys are saved and visible in the configuration file under “system ssh-host-keys.” You cannot set or view the configuration of SSH host keys using the SRC CLI. SSH host keys are obtained from system files located in the /etc/ssh directory. The SSH host key data saved into configuration files is refreshed with the most recent data in the files when you execute the save command.

Component State

When you execute the save local or save command, the state of the SRC components is polled and saved in the configuration file under “component-state.” However, like the SSH host keys, you cannot view or set the values for the component state using the CLI.

When you load and commit the configuration from a saved file, the SRC software sets the state of the components in the C Series Controller to the state saved in the configuration file. Components that were in either the “running” or “stopped” state when polled are automatically enabled, and components that were “disabled” when polled are automatically disabled.

Related Documentation