Cisco Network Order Manager System Configuration

CNOM Configuration

Profile Management

Setting Up a Subtended Hierarchy

Configuring Line IDs for CNOM Modules

Setting the Line ID of a DSLAM Port

Setting the Line ID for a Cisco UAC Port

Setting Quality of Service

Cisco Network Order Manager System Configuration

This appendix describes how to configure CNOM. It contains several sections:

CNOM Configuration

To configure a CNOM system, you must complete the following:

Installation—Install CEMF, any required patches, relevant element managers, and necessary CNOM components on applicable servers.
Configuration—Create and configure profiles which you can later apply to connection segments (PVCs, DMT ports). Configure topology attributes to allow CNOM to navigate the network.
Operation—Submit network orders to the ddmGateway process to bring the system live.

After installation, configure CNOM using script utilities supplied with the product to create mapping objects and set the various attributes in CEMF that CNOM uses during connection management. Examples of configuration tasks that are carried out are:

Creating mapping objects to allow resolution from interface names received in network orders to CEMF object IDs. The line ID values used in the Cisco 6400 UAC architecture are examples of this.
Configuring inter-machine tie ports in the multiple Cisco 6400 UAC architecture using the set_IMT command.

Configuration is normally required after any new device is installed in the network if the new device is to support connections managed by CNOM.

Profile Management

Network orders that create connections contain the attribute serviceCharacteristics, whose value corresponds to the names of profiles that will be applied by the various participating element managers. The settings in each profile should support the intended characteristics of the connection. So, an ADSL profile called Gold in CDM sets line speeds on a DSL port which match the speed settings in the Gold SCM connection template that is applied to a PVC cross-connect.

Each element manager must be configured to contain profiles corresponding to each possible value of serviceCharacteristics. For example, suppose you have the following transport speeds and DSL types:

ADSL-1.5x384—ADSL transport with upstream/downstream speeds of 1.5 Mbps and 384 kbps
ADSL-512x128—ADSL transport with upstream/downstream speeds of 512 kbps and 128 kbps
SDSL-512—SDSL transport with speed 512 kbps
SDSL-256—SDSL transport with speed 256 kbps

In this case you might set up DMT, ADSL, CAP and ATM QoS profiles named ADSL-1.5x384 and ADSL-512x128, and SDSL and ATM QoS profiles named SDSL-512 and SDSL-256. In the network order, you would also specify the name of the appropriate profile for the serviceCharacteristics attribute.

The primitive ConfigureDSLPort, used in the policy connectSubscriber applies the profiles of the appropriate type for the port being configured.

Setting Up a Subtended Hierarchy

The subtend hierarchy in CDM Release 3.0 is modeled in CEMF as a containment view called Subtend. All DSLAMs which are to be used by CNOM must appear in this view, even if they operate as standalone units. The view contains the chassis object for each DSLAM, and each chassis object contains its trunk and subtend ports. Chassis objects appear at either:

The root of the tree—Indicating that they are not connected to the subtend port of any other DSLAM
Under a subtend port of another DSLAM—Indicating that the trunk port is connected to the specified subtend port

The policy setupSubtend automatically sets up the DSLAM in a Subtend view and also sets the attributes to designate the network port and subtend ports.

To set up subtending, invoke the subtend command as follows:

./subtend node_chassis_path [subtend_port_path]

The subtend command includes two parameters:

The containment path of the node that must be set up in the Subtend view
An optional subtend port under which the node needs to be subtended

Note When you upgrade from CNOM Release 1.03 or 1.05 or CDM Release 3.1 or later, you must remove the Subtend package before you begin the upgrade.

To position a node under a subtend path:

1. The subtend port must already exist in the Subtend view. If the second parameter is not provided, the node is placed in the top level of the subtend view. For example, to set up a subtend view of three nodes (Node1/Node2/Node3), each with a single SONET trunk port and single SONET subtend port, run the following commands:

./subtend Physical:/Site-1/Node1-Shelf/Node1-Chassis

./subtend Physical:/Site-1/Node2-Shelf/Node2-Chassis subtend:/Node1-Chassis/SONET-10-2

./subtend Physical:/Site-1/Node3-Shelf/Node3-Chassis subtend:/Node2-Chassis/SONET-10-2

: For NI-1 nodes, enter the containment path of the chassis as:

Physical:/.../C6100v30TrapMgmt/C6100v30ManagedElement/C6100v30MultiplexerChassis-1

Note Run the subtend command from the CEMF shell.

2. After you set the information to the connected DSLAMs, tag each service instance with a service name to tell the service to which it is being connected. This name is used in the work order to identify the candidate set of service instances from which you choose the destination. Set the value using the socketDaSet command as follows:

./socketDaSet <serviceInstance> LocalDB:C6400NOA.serviceName (<val>)

3. Replace <serviceInstance> with the full name of the service instance being used, and replace <val> with the desired name. For example:

socketDaSet Cisco6400ServiceView:/sw1/sw1-chassis/PPP-IP_Service-1 \ 
LocalDB:C6400NOA.serviceName "(AOL)"

Configuring Line IDs for CNOM Modules

Line IDs are used in CNOM to identify the ingress point (start) or egress point (end) of a connection. For example, line IDs are used to identify the ingress port for a DSLAM or a Cisco 6400 UAC connection. In the SCM ATM Connection policy, the line IDs are used to identify both an ingress and egress value. The line IDs are:

Any string value associated with a port such as circuit ID, phone number, and so on.
The identifier that is received in incoming work orders if a CEMF name is not supplied.

For example:

The line ID for a DSLAM line port is a unique identifier assigned to the subscriber served by this line port (for example, the phone number 4085551212).
For a Cisco 6400 UAC ingress port, the line ID is the set of DSLAMs being serviced by the UAC (for example, DSLAM-1, DSLAM-2, DSLAM-3). Each comma-separated value must be unique for the port and cannot be assigned to another port.

For performance, line IDs are managed in an invisible view, ObjectMapView, under the technology object DDMTopology.lineID. For each line ID assigned to a port, the system creates a map object whose name matches the line ID. The line ID object includes the following attributes:

LocalDB:DDMMappingObject.targetObject—The line port which is assigned this line ID.
LocalDB:DDMMappingObject.subdomainId—The subdomain (the set of CNOM devices) that the line port belongs to: DSLAM or C6400DMM.

In addition, the line port sets the value in its local attribute (LocalDB:DDMTopology.lineID).

When you assign the value DSLAM-1,DSLAM-2,DSLAM-3 to a line port, the resulting configuration in CEMF is as follows:

Three line ID objects are created under ObjectMapView:/DDMTopology with the names DSLAM-1, DSLAM-2, and DSLAM-3
The targetObject is set as the ingress port
The ingress port's attribute LocalDB:DDMTopology.lineID is assigned the line ID value DSLAM-1,DSLAM-2,DSLAM-3

Line IDs are configured using policies which provide a more abstract form of mapping objects to arbitrary attribute values. The policies include:

./setMappingValues—Sets a new set of mapping values for the object
./resetMappingValues—Resets existing mapping values for an object
./addMappingValue—Adds a new mapping value to the object
./removeMappingValue—Removes a mapping value from the object
./findMappingTarget—Identifies an object with a mapping value and returns the target object

The following command line scripts provide perl wrapper scripts to execute this policy:

./set_map_values
./reset_map_values
./add_map_value
./remove_map_value
./get_object_for_value

Command line scripts are provided to configure line IDs for CNOM.

Note If the same line IDs are assigned to more than one port, policies fail.

Setting the Line ID of a DSLAM Port

Use the ./set_line_ids script to assign a line ID to a DSLAM port to identify a subscriber line attached to the port. The script assigns a new ID to the port if none exists, or it overwrites an existing line ID with a new value. The command syntax is as follows:

./set_line_ids <port> <line_ID> DSLAM

Where:

<port> is the containment path of the ingress or egress port whose line ID you are setting.
<line_ID> is a unique identifier for the subscriber, such as a circuit ID or telephone number. DSLAM indicates that the line ID is assigned to a port in the DSLAM subdomain.

The following command assigns the line ID 408-555-1212 to the DSLAM port Chelmsford/.../DMT-5-1 (where \ indicates that the command continues on a new line):

./set_line_ids ComponentManaged:/Chelmsford/ni2-90-shelf/ni2-90-chassis/D5/DMT-5-1 \ 4085551212 DSLAM

Setting the Line ID for a Cisco UAC Port

To identify the set of DSLAMs served by the UAC, set the line ID for a Cisco 6400 UAC port. The command syntax is as follows:

./set_line_ids <port> <line_ID> C6400DMM

For <port>, specify the containment path of the ingress or egress port whose line ID you are setting.
For <line_ID>, specify the set of DSLAMs served by the port (include commas between each DSLAM name). C6400DMM indicates that the line ID is assigned to a port in the Cisco 6400 UAC subdomain.

The following command sets the line ID for the UAC port sw1-shelf/.../ATM-3-1-0
(where \ indicates that the command continues on a new line). The line ID indicates that the port serves DSLAM-1, DSLAM-2, and DSLAM-3.

./set_line_ids Cisco6400ServiceView:/sw1-shelf/sw1-chassis/sw1-nsp/OC3-3-1/ATM-3-1-0 \ DSLAM-1,DSLAM-2,DSLAM-3 C6400DMM

Note Run all of the following commands from the CEMF shell.

The ./get_line_id <port> script prints the line ID of the ingress port for the specified port. For example, for the port sw1-shelf/.../ATM-3-1-0, the script returns the value DSLAM-1,DSLAM-2,DSLAM-3.
The ./get_object_for_line script takes a line ID value and prints the containment path of the object that is assigned this value. For example, ./get_object_for_line DSLAM-1 returns the value:

workOrder:DDMWorkOrder.objectName 
Cisco6400ServiceView:/sw1-shelf/sw1-chassis/sw1-nsp/OC3-3-1/ATM-3-1-0

The reset_line_ids script resets the line ID for a specified port. For example, to reset the line ID for the port sw1-shelf/.../ATM-3-1-0, issue the command as follows:

./reset_line_ids Cisco6400ServiceView:/sw1-shelf/sw1-chassis/sw1-nsp/OC3-3-1/ATM-3-1-0

: If you then run ./get_line_id, the script returns an empty value (because the line ID has been reset).

The ./add_line_id script assigns an additional line ID to the specified port's current line ID. For example, if the line ID is DSLAM-1,DSLAM-2,DSLAM-3 and you issue the following command, the line ID becomes DSLAM-1,DSLAM-2,DSLAM-3,DSLAM-4.

./add_line_id Cisco6400ServiceView:/sw1-shelf/sw1-chassis/sw1-nsp/OC3-3-1/ATM-3-1-0 \ 

DSLAM-4 C6400DMM

The ./remove_line_id script removes a line ID from the port's current value. For example, the following command removes DSLAM-2, making the port's line ID value DSLAM-1,DSLAM-3,DSLAM-4:

./remove_line_id Cisco6400ServiceView:/sw1-shelf/sw1-chassis/sw1-nsp/OC3-3-1/ATM-3-1-0 
\ DSLAM-2 C6400DMM

: If you run ./get_object_for_line DSLAM-2, the script returns an error, as this value is no longer mapped to an object.

Setting Quality of Service

For CNOM to successfully make connections, you must name at least one fully configured quality of service (QoS) through the network. To set a quality of service, perform the following steps:

Step 1 Create a CDM Manager DMT profile using an appropriate name.

Step 2 Create a CDM Manager DSL profile using an appropriate name.

Step 3 Create a CDM Manager ATM connection profile using an appropriate name.

Step 4 Create an SCM connection template using an appropriate name.

Note An appropriate name in the above procedure is any convention that functions within the network administrator for keeping a variety of QoS packages uniquely identified. For example, Gold, Silver, and Bronze are identifiers that can designate (in a hierarchical order) various QoS packages.

Tag each connection template with a profile name to tell CNOM which named QoS it represents. This name is used in the work order to identify the appropriate connection template for a connection.

Table of Contents