Cisco Model 6109 6 MHz Off-Air Reference (NTSC) Guide De Montage
Chapter 1 Overview
12
4039132 Rev B
Configuration Provisioning
The USRM maintains its configuration by creating a file in the persistdata directory
for each component. This file indicates that the component exists and maintains the
nonvolatile state of the component. When the software is activated and there are no
configuration files in the persistdata directory, the software executes a procedure to
create the default configuration. The default USRM configuration is made up of
base USRM platform components and plug-in components for specific applications.
for each component. This file indicates that the component exists and maintains the
nonvolatile state of the component. When the software is activated and there are no
configuration files in the persistdata directory, the software executes a procedure to
create the default configuration. The default USRM configuration is made up of
base USRM platform components and plug-in components for specific applications.
The default USRM configuration hierarchy is established by a configuration file in
the ConfigFiles directory. These configuration files are input on the initial activation
of the software. Initial activation is indicated by lack of any files in the persistdata
directory. When the software is activated the first time, or whenever the persistdata
files have been deleted, the software inputs two configuration files to create the
software component hierarchy, in order, as follows:
1 The default USRM configuration file is input first.
the ConfigFiles directory. These configuration files are input on the initial activation
of the software. Initial activation is indicated by lack of any files in the persistdata
directory. When the software is activated the first time, or whenever the persistdata
files have been deleted, the software inputs two configuration files to create the
software component hierarchy, in order, as follows:
1 The default USRM configuration file is input first.
Note: This file defines the standard base software platform components without
any plug-in application-specific components.
any plug-in application-specific components.
2 The license.conf file is input second.
Note: This file defines the plug-in components for the specific application.
Default Configuration File
One of two files is used to define the default configuration depending on the normal
role for the server. The normal role for a server is to be either a primary server or a
standby server. The following configuration files define the initial configuration for
a server depending on its role.
role for the server. The normal role for a server is to be either a primary server or a
standby server. The following configuration files define the initial configuration for
a server depending on its role.
For a primary server, the configuration file location and file name is:
ConfigFiles/DefaultConfigPrimary.txt
For a standby server, the configuration file location and file name is:
ConfigFiles/DefaultConfigStandby.txt
Important: These files should not be modified.
Application-Specific License.conf File
After inputting the default configuration file, the software next inputs the
ConfigFiles/license.conf file. This file is installed by the factory based on the part
number of the product. This file contains a list of the application-specific
components for the configuration.
ConfigFiles/license.conf file. This file is installed by the factory based on the part
number of the product. This file contains a list of the application-specific
components for the configuration.
Important: The license.conf file does not contain the names of the network resources
such as QAMs, encryptors, etc. The network resources must be added either
through the USRM web interface or via a device configuration file. Refer to Network
Resource Management (on page 16) for more information on creating network
resources.
such as QAMs, encryptors, etc. The network resources must be added either
through the USRM web interface or via a device configuration file. Refer to Network
Resource Management (on page 16) for more information on creating network
resources.