encryption-keykey[hash | hash2]
noencryption-key
bof
This command creates a key for configuration file encryption and hashing using the AES256 cipher algorithm. This key is used for all configuration files (primary, secondary, and tertiary).
After creating the encryption key, use the admin save command to save the encrypted file.
If the admin rollback save command is used, the rollback files are also encrypted.
The no form of this command deletes the configured encryption key.
no encryption-key
specifies the encryption key
If the hash or hash2 parameter is not configured, the key is entered in plaintext and the key length must be between 8 and 32 characters. A plaintext key cannot contain embedded nulls or end with ‟hash” or ‟hash2”.
If the hash or hash2 parameter is configured, the key is hashed and the key length must be between 1 and 64 characters.
specifies that the key is entered in an encrypted form
specifies that the key is entered in a more complex encrypted form. The hash2 encryption scheme is node-specific and the key cannot be transferred between nodes.
persist {on | off}
bof
This command specifies whether the system preserves system indexes when a save command is executed. During a subsequent boot, the index file is read along with the configuration file. As a result, a number of system indexes are preserved between reboots, including the interface index, LSP IDs, and path IDs. This reduces resynchronizations of the Network Management System (NMS) with the affected network element.
If persist is on and the reboot with the appropriate index file fails, SNMP is operationally shut down to prevent the management system from accessing and possibly synchronizing with a partially booted or incomplete network element. To enable SNMP access, enter the config>system>snmp>no shutdowncommand.
If persist is enabled and the admin save <url> command is executed with an FTP path used as the <url> parameter, two FTP sessions simultaneously open to the FTP server. The FTP server must be configured to allow multiple sessions from the same login; otherwise, the configuration and index files are not saved correctly.
Persistency files (.pst) should not be saved on the same disk as the configuration files and the image files.
When an operator sets the location for the persistency file, the system checks to ensure that the disk has enough free space. If there is not enough free space, the persistency does not become active and a trap is generated. The operator must free up adequate disk space before persistency becomes active. The system performs a space availability check every 30 seconds. As soon as the space is available the persistency becomes active on the next 30-second check.
off
preserves the system index when saving the configuration
disables the system index saves between reboots
primary-config file-url
no primary-config
bof
This command specifies the name and location of the primary configuration file.
The system attempts to use the configuration specified in primary-config. If the specified file cannot be located, the system automatically attempts to obtain the configuration from the location specified in secondary-config and then in tertiary-config.
If an error in the configuration file is encountered, the boot process aborts.
The no form of the command removes the primary-config configuration.
n/a
the primary configuration file location (see Table: URL Types and Syntax for parameter descriptions)
primary-image file-url
no primary image
bof
This command specifies the primary directory location for runtime image file loading.
The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.
The no form of the command removes the primary-image configuration.
n/a
the location-url can either be local (this CSM) or a remote FTP server (see Table: URL Types and Syntax for parameter descriptions)
secondary-config file-url
no secondary-config
bof
This command specifies the name and location of the secondary configuration file.
The system attempts to use the configuration as specified in secondary-config if the primary config cannot be located. If the secondary-config file cannot be located, the system attempts to obtain the configuration from the location specified in the tertiary-config.
If an error in the configuration file is encountered, the boot process aborts.
The no form of the command removes the secondary-config configuration.
n/a
the secondary configuration file location (see Table: URL Types and Syntax for parameter descriptions)
secondary-image file-url
no secondary-image
bof
This command specifies the secondary directory location for runtime image file loading.
The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.
The no form of the command removes the secondary-image configuration.
n/a
the file-url can either be local (this CSM) or a remote FTP server (see Table: URL Types and Syntax for parameter descriptions)
tertiary-config file-url
no tertiary-config
bof
This command specifies the name and location of the tertiary configuration file.
The system attempts to use the configuration specified in tertiary-config if both the primary and secondary config files cannot be located. If this file cannot be located, the system boots with the factory default configuration.
If an error in the configuration file is encountered, the boot process aborts.
The no form of the command removes the tertiary-config configuration.
n/a
the tertiary configuration file location (see Table: URL Types and Syntax for parameter descriptions)
tertiary-image file-url
no tertiary-image
bof
This command specifies the tertiary directory location for runtime image file loading.
The system attempts to load all runtime image files configured in the primary-image first. If this fails, the system attempts to load the runtime images from the location configured in the secondary-image. If the secondary image load fails, the tertiary image specified in tertiary-image is used.
All runtime image files (both.tim) must be located in the same directory.
The no form of the command removes the tertiary-image configuration.
n/a
the file-url can either be local (this CSM) or a remote FTP server (see Table: URL Types and Syntax for parameter descriptions)