Configuration File Types

There are two types of configuration files on the GigaVUE H Series node – standard configuration files and text configuration files (known as command files):

■

Standard configuration files can be used to store and apply a set of settings with the configuration switch-to command. Use this command to ensure that all configurations, including the order of map rule IDs are restored properly.

■

Text configuration files are not really configuration files at all – instead, they are lists of CLI commands used to build a particular configuration. Text configuration files are useful for both troubleshooting and backup purposes – you can quickly see what commands built a particular configuration, or you can store regular backups of text files containing the commands on an external host. Text configuration files can also be applied in the CLI using the configuration text file <filename> apply command.

You work with text configuration files using the configuration text command and its arguments.

Information Excluded from Text Configuration Files

For security reasons, text configuration files do not include plaintext passwords, such as SMTP passwords, AAA keys (RADIUS or TACACS+), private keys in RSA/DSA identities. Because of this, they cannot completely restore a given configuration using configuration text file <filename> apply.

Reserved Empty Database File

The empty database file, empty_db_file_dnu, is a reserved file. Do not use this filename (dnu) in any database operation such as configuration write to or configuration switch-to commands as the filename is removed when the node is reloaded.