Configuration load operation

The NISH client provides the ability to provision a template-based configuration on multiple SR OS nodes with a specific device-label grouping. This operation is completed using the MD-CLI load command.

When using the load command within NISH for multinode configuration, the merge and full-replace options are supported. The referenced configuration file supplied to the load command must be accessible from each individual SR OS node within the addressed set of nodes, unless it is prefixed with the URL prefix nish://. When nish:// is used, the relative or absolute path or filename that follows nish:// is treated as local to the NISH client.

Note: The MD-CLI load command is the only supported method for multinode configuration from the NISH client.

The load command within a multi-device context (MDC) is atomic, that is, it succeeds on all addressed SR OS nodes or no SR OS nodes.

See the 7450 ESS, 7750 SR, 7950 XRS, and VSR MD-CLI Command Reference Guide for more information about the load command.

The following table describes examples of the supported file URL options that can be used to reference the configuration template file when using the load merge and load full-replace commands for multinode configuration from the NISH client. In the examples, a configuration file called myconfig.cfg is referenced.

Table 1. File URL reference options for NISH client load merge and replace
File URL reference	Description
load merge cf3:/myconfig.cfg	The myconfig.cfg file containing the configuration changes must be accessible in the root directory of cf3:, on each node in the set of addressed nodes.
load merge ftp://`user:password`@100.0.0.1/myconfig.cfg	Each node in the set of addressed nodes must be able to successfully connect to the FTP server at 100.0.0.1 and authenticate using the user and password credentials.
load merge nish://myconfig.cfg	Each node in the set of addressed nodes is configured by merging the file myconfig.cfg located in the current working directory of the host operating system on which the NISH client is running.
load merge nish:///`home`/`username`/myconfig.cfg	Each node in the set of addressed nodes is configured by merging the myconfig.cfg file located in the home directory of the user on the host operating system on which the NISH client is running.