Cisco Model 6109 6 MHz Off-Air Reference (NTSC) Guide De Montage
Network Resource Management
4039132 Rev B
21
In general, the USRM is not case sensitive in commands. When a command or name
is case sensitive, this will be indicated in the document. The first two arguments on
the command line are mandatory. The first argument specifies the device type to
create. This argument is case sensitive since it specifies a name used to form a linux
library name. The second argument is the instance name. The instance name is the
unique (within a single USRM) name used to identify the object. The name cannot
be changed after creation. Changing the name requires deletion of the device and
then re-creating the device. The device can already exist. This means a file can be
edited and reapplied at will.
is case sensitive, this will be indicated in the document. The first two arguments on
the command line are mandatory. The first argument specifies the device type to
create. This argument is case sensitive since it specifies a name used to form a linux
library name. The second argument is the instance name. The instance name is the
unique (within a single USRM) name used to identify the object. The name cannot
be changed after creation. Changing the name requires deletion of the device and
then re-creating the device. The device can already exist. This means a file can be
edited and reapplied at will.
The following is an example command line.
gqam GQAM011 CtrlIpAddress=172.16.4.61\
PortTable.ServiceGroupId.1 1000\
PortTable.ServiceGroupId.2 1001\
PortTable.ServiceGroupId.3 1002\
PortTable.ServiceGroupId.4 1003
This command line creates a "gqam" device named "GQAM011". The IP address of
the device is preset and the service group Id for each RF port is also preset.
the device is preset and the service group Id for each RF port is also preset.
Standard Configuration File Format
The standard configuration file format is a more flexible format with some
advantages. The primary advantage is that the object specification is not required.
The file will be applied to the object where it is requested. This allows a common file
to be applied to many objects. Every USRM component provides a Software page
allowing application of a configuration file. The object is implicit in this case. Second,
each command is on a separate line in the file. Long command lines are not required.
advantages. The primary advantage is that the object specification is not required.
The file will be applied to the object where it is requested. This allows a common file
to be applied to many objects. Every USRM component provides a Software page
allowing application of a configuration file. The object is implicit in this case. Second,
each command is on a separate line in the file. Long command lines are not required.
The standard configuration file support three basic commands. The first argument
on the command line indicates the command type. The create command is used to
create an object. The object command is used to specify an object. When the first
argument is not create or object, then the command is interpreted as a command to
apply a state. In the standard format, the example from the legacy section would be
written as follows.
on the command line indicates the command type. The create command is used to
create an object. The object command is used to specify an object. When the first
argument is not create or object, then the command is interpreted as a command to
apply a state. In the standard format, the example from the legacy section would be
written as follows.
create gqam GQAM011
CtrlIpAddress=172.16.4.61
PortTable.ServiceGroupId.1 1000
PortTable.ServiceGroupId.2 1001
PortTable.ServiceGroupId.3 1002
PortTable.ServiceGroupId.4 1003
Note: In the legacy example, the white spaces on lines 2 and greater were required as
terminators. In the standard format, they are not required, but are recommended for
readability.
terminators. In the standard format, they are not required, but are recommended for
readability.