Commands to Load a Configuration

Use the load commands to load your configuration from a saved configuration file.

The load merge and load replace commands include options for loading only system bootstrap or none-bootstrap configuration data from the specified configuration file. Bootstrap configuration data is part of the local configuration. It enables an SRC host to be a networked host, and includes parameters like system host-name, system domain-name, interfaces, and routing options.

You can automatically enable SRC components when the CLI starts. For example, this allows you to automatically enable the Juniper Networks database community on a system that has only the factory default configuration loaded. To configure the system to automatically enable components, add “Component.auto-enable = component-name” to the CLI backend bootstrap properties file “cli.properties.”

You can use the following commands in configuration mode to make configuration changes:

The relative option for the load merge, load replace, and load set commands lets you load the configuration at a specified hierarchy level.

The load merge, load override, and load replace commands let you update configuration statements in the SRC configuration from a text file or an XML file. The structure of this file must conform to the structure for an SRC configuration file. For this reason, we recommend that you copy the file based on the file format you plan to use:

For a merge or replace operation, you can save a copy of the configuration at any level in the configuration hierarchy, then load the updated configuration at the same level.

Use the editor of your choice to modify a saved configuration file. When you edit a file that is to be loaded into the SRC configuration, you can add specified attributes to specify actions to be taken.

SSH Host Keys

You can load SSH host keys into the configuration from the saved configuration file. When you execute commit, the loaded SSH host keys are used to update system key files (those in the /etc/ssh directory). The original files are backed up with the same filename with an additional “~”.

Component State

You can load SRC component states into the configuration from the saved configuration file. When you execute commit, the loaded component state values are used to automatically enable and disable the SRC components.

Related Documentation