Cisco Model 6109 6 MHz Off-Air Reference (NTSC) Guide De Montage
Network Resource Management
4039132 Rev B
19
Configuration Files and Formats
The USRM provides functions to input or output configuration files. A
configuration file is a sequence of commands in text form used to save or set the
state of USRM configuration objects. A configuration file can be generated from the
USRM by extracting current state information and writing to a file. Conversely, a
configuration file can also be input to the USRM applying the commands from the
file to the USRM configuration.
configuration file is a sequence of commands in text form used to save or set the
state of USRM configuration objects. A configuration file can be generated from the
USRM by extracting current state information and writing to a file. Conversely, a
configuration file can also be input to the USRM applying the commands from the
file to the USRM configuration.
The USRM supports two configuration file formats, as follows:
Legacy format - The legacy format was inherited from the base software used to
form the USRM. This format is supported, but not recommended for new
applications.
form the USRM. This format is supported, but not recommended for new
applications.
Standard format - The standard format is recommended for all new
applications. The standard format provides the functions of the legacy format
plus additional features.
applications. The standard format provides the functions of the legacy format
plus additional features.
Common Features
The command processors that input and apply configuration files use a common
preprocessor. The result is that both file types support a preprocessor that can be
used to adjust the content of the file using text directives. In most cases, the
preprocessor commands begin with the # character. Unlike other commands,
preprocessor commands must begin in the first column of the line.
preprocessor. The result is that both file types support a preprocessor that can be
used to adjust the content of the file using text directives. In most cases, the
preprocessor commands begin with the # character. Unlike other commands,
preprocessor commands must begin in the first column of the line.
A named argument can be defined. The "#define argName argValue" specifies an
argument and the value of the argument. The example below creates a variable x
with value 1. This argument can be used in two ways. First, the #ifdef operator can
be used to test if the argument exists. Second, the value of the argument will be
substituted in text strings when the argument name is surrounded by the $
character. For example, 1234$x$5678 is translated to 123415678.
argument and the value of the argument. The example below creates a variable x
with value 1. This argument can be used in two ways. First, the #ifdef operator can
be used to test if the argument exists. Second, the value of the argument will be
substituted in text strings when the argument name is surrounded by the $
character. For example, 1234$x$5678 is translated to 123415678.
#define x 1
A section can be skipped using #ifdef or #ifndef. The directive is terminated with a
#else or #endif. The preprocessor is very limited and only supports one level of
conditional processing. In the following example, Command1, Command2, and
Command3 are not processed.
#else or #endif. The preprocessor is very limited and only supports one level of
conditional processing. In the following example, Command1, Command2, and
Command3 are not processed.
#ifdef xyz
Command1
Command2
Command3
#endif