Configuring a Multiple Cisco 6400 UAC Architecture

Configuring ATM Service for Multiple Cisco 6400 UACs

Prerequisites

Configuring the System

Connection Templates

Creating Mappings for ATM Interfaces

Designating Inter-Machine Tie Interfaces

Managing Connections

Creating Connections

CNOM Internal Work Flow for connectSubscriberToATMServiceConnection

Querying Connections

Deleting Connections

Configuring the CNOM for a Multiple Cisco 6400 UAC Architecture

End-to-End Connection in a Cisco 6400 UAC Architecture

ATM Connection in a Cisco 6400 UAC Topology

CNOM Internal Work Flow for setupCLECConfig

Connect and Disconnect Scripts

Making Multiple Cisco 6400 UAC ATM Connections

Configuring a Multiple Cisco 6400 UAC Architecture

This chapter describes the connection attributes and processes of a Cisco Network Order Manager architecture consisting of a series of Cisco 6400 Universal Access Concentrators (UACs).

Configuring ATM Service for Multiple Cisco 6400 UACs

This section details the use of CNOM for managing PVCs in a network containing clusters of Cisco 6400 UAC devices. Each cluster acts as a virtual switch, and the task of CNOM is to make PVC connections across the virtual switches. CNOM uses the facilities of the Cisco 6400 Service Connection Manager (SCM) to interact with the 6400 UAC devices. See Figure 4-1.

Figure 4-1: Cisco 6400 UAC to Cisco 6400 UAC Configuration

Use the network order policy createSubscriberToATMService to create connections over any arrangement of Cisco 6400 UAC devices provided each end-to-end connection passes through, at most, two devices.

The PVCs in each Cisco 6400 UAC are managed using the ATM subscriber and service management features of SCM. The Service Connection Manager Network Order Adapter (SCM NOA) specifies the ingress and egress PVCs used, and also the name of the connection template applied to the PVCs. The CNOM network order policy (NOP), for connection creation, locates the ingress and egress interfaces in CEMF, finds the tie port, and creates an end-to-end connection from the ingress interface to the egress interface through the tie port, using PVC information supplied in the network order. SCM auto-allocates the PVC used at the tie ports.

If SCM finds the ingress and egress interfaces on the same Cisco 6400 UAC, it makes a single cross-connection within that device.

Prerequisites

Before you can use CNOM to configure Cisco 6400 UAC devices, you must install the following software:

CEMF Release 3.0.4 and appropriate CEMF patches (see the CNOM Release Notes)
Cisco 6400 Service Connection Manager (SCM)
CNOM packages DDMG, DDMGen, C6400DMMm

Refer to the installation guides for each product for installation procedures. The CNOM installation and upgrade procedures are described in "Installing Cisco Network Order Manager."

Configuring the System

This section describes how to set up CNOM to manage connections in a network with multiple Cisco 6400 UACs. Connection management is possible only after you configure the following:

Connection templates in SCM for the cross-connects
Mapping objects for ingress and egress ports (only if CEMF names will not be supplied in the network orders)
Inter-machine tie port information

The procedures for performing these configuration tasks are detailed in the following sections.

Connection Templates

An SCM connection template is a type of CEMF profile that contains ATM QoS settings to apply to a connection. By applying the profile (that is, by specifying the profile name in the connection template), you can apply those ATM QoS parameter settings to the connection rather than having to specify each parameter value separately. CNOM requires that at least one connection template is configured in SCM to facilitate connections in a network of multiple Cisco 6400 UACs.

Manage the connection templates using the SCM GUI (refer the Cisco 6400 Service Connection Manager User Guide), or using the CNOM network order interface.

To manage:

SCM connection templates through the CNOM network order interface, use the policies createConnectionTemplate, modifyConnectionTemplate, and deleteConnectionTemplate.
Utility scripts create_qos, modify_qos, and delete_qos to enable connection templates, use the command line on the CEMF server.

Creating Mappings for ATM Interfaces

Network orders for creating connections in a multiple Cisco 6400 UAC network architecture supply names for the ingress and egress ATM interfaces. Use mapping objects to define the aliases available for use in network orders. If the names in the network order are not CEMF names, you must resolve each supplied name to be a CEMF name. To resolve supplied names to CEMF names, use mapping objects.

The mapping objects for a multiple Cisco 6400 UAC network architecture are called line IDs. Manage line IDs using the following commands:

set_line_ids <ContainmentPath> <LineId,LineId,LineId> <SubdomainId>—Creates a list of line ID mapping objects, and sets the line ID attribute to be the comma-separated list of mappings. Previous mapping objects for the interface are removed.
add_line_id <ContainmentPath> <LineId> <SubdomainId>—Adds a line ID alias to an interface.
remove_line_id <ContainmentPath> <LineId>—Removes a single line ID alias from an interface. This step must be completed before you can remove a chassis.
cleanup_line_id <LineId>—Removes line IDs that were not deleted before you removed a chassis or uninstalled CNOM.

Note Use the cleanup_line_Id command only to remove line IDs that were not deleted before a chassis was removed or CNOM was uninstalled. For instance, if you attempt to use or remove a line ID from a removed chassis and receive an error message that you can not use that particular line ID, run the cleanup_line_Id [<LineId>] [<ContainmentPath>] command.

reset_line_ids <ContainmentPath>—Removes line ID mapping objects for an interface, and clears the line ID attribute.
get_line_id <ContainmentPath>—Returns the value of the line ID attribute which may consist of a comma-separated list of line ID aliases.
get_object_for_line <LineId>—Returns the name of the interface with the specified line ID alias.

The values of the line ID aliases may contain any alphanumeric characters plus (-), (.), and (_).

Designating Inter-Machine Tie Interfaces

The interfaces that connect two Cisco 6400 UAC devices in a network of multiple Cisco 6400 UACs are called inter-machine tie (IMT) interfaces. Before you can make connections through IMT interfaces, you must configure the applicable interfaces in CNOM.

To manage IMT interfaces, use the following command:

set_IMT <interface name> <interface name>

: Where:

Managing Connections

This section describes how to create, delete, and query PVC connections across a pair of Cisco 6400 UAC devices.

Creating Connections

Use the network order policy connectSubscriberToATMService to create a pair of PVCs that form an end-to-end connection across two connected Cisco 6400 UAC devices. CNOM expects the network order to contain the attributes listed in Table 4-1.

Table 4-1: Network Order Attributes for Network Order Policy connectSubscriberToATMService

Attribute	Description
`workOrder:DDMWorkOrder.connectionIdentifier`	A unique identifier for the connection.
`workOrder:DDMWorkOrder.ingressIdentifier`	A line ID value that resolves to an interface in the ingress Cisco 6400 UAC device.
`workOrder:DDMWorkOrder.egressIdentifier`	A line ID value that resolves to an interface on the egress Cisco 6400 UAC device.
`workOrder:DDMWorkOrder.serviceCharacteristics`	The name of an SCM connection template.
`workOrder:DDMWorkOrder.ingressVPI`	The VPI/VCI values to be used on the ingress interface.
`workOrder:DDMWorkOrder.ingressVCI`	—
`workOrder:DDMWorkOrder.egressVPI`	The VPI and VCI values to be used on the egress interface.
`workOrder:DDMWorkOrder.egressVCI`	—
`workOrder:DDM.finalWorkOrder`	Optional attribute which when set, causes the contents of the internal work order to be returned to the user. To view error messages, this attribute must be set.

CNOM Internal Work Flow for connectSubscriberToATMServiceConnection

CNOM performs the following steps to execute the connectSubscriberToATMServiceConnection policy:

Initial State: ddmGateway:DDMGenc:C6400DMM.findCLECInterface_CSAS

1. Find Interface Object: FindMappedObject

2. Find Chassis Object: GetAncestorPrimitive

3. Get RT Object: FindMappedObject

4. Find RT Chassis: GetAncestorPrimitive

5. Get CLEC Interface name: GetContainmentPath

6. Get RT Interface name: GetContainmentPath

7. Create Connection Object: ObjectDeployPrimitive

8. Create Service Object: ObjectDeployPrimitive

9. Copy values to egress point: Annotate

a. Find RT Egress Interface: queryInterface

b. Find CLEC Ingress Interface: Annotate

c. Copy values to RT Ingress: Annotate

10. Set attributes of ATM Service: SetupATMService

11. Connect Subscriber: ConnectSubscriber

12. Copy RT values to Egress: Annotate

13. Copy RT values to Ingress: Annotate

14. Set attributes of ATM Service: SetupATMService

15. Connect Subscriber: ConnectSubscriber

Note When you use CNOM with SCM Version 2.0.1 or SCM Version 2.1.1, the connection template specified by the serviceCharacteristics attribute is not applied to the PVC. The PVCs are assigned default parameters according to the configuration of each Cisco 6400 UAC device.

Querying Connections

Use the network order policy getATMConnectionData to gather information about existing connections. The network order policy getATMConnectionData requires the following attributes (Table 4-2).

Table 4-2: Attributes for Network Order Policy getATMConnectionData

Attribute	Description
`workOrder:DDMWorkOrder.connectionIdentifier`	A unique identifier for the connection.
`workOrder:DDM.finalWorkOrder`	Must be set in order for the internal work order to be returned to user. The internal work order contains the results of the query.

The getATMConnectionData policy returns the values of the attributes set on a connection object during execution of the network order policy connectSubscriberToATMService.

Deleting Connections

Use the network order policy disconnectSubscriberAndService to delete the PVCs associated with an end-to-end connection (Table 4-3).

Table 4-3: Attributes for Network Order Policy disconnectSubscriberAndService

Attribute	Description
`workOrder:DDMWorkOrder.connectionIdentifier`	A unique identifier for the connection.
`workOrder:DDM.finalWorkOrder`	Optional attribute, which, when set, causes the contents of internal work order to be returned to user.

Configuring the CNOM for a Multiple Cisco 6400 UAC Architecture

The policy connectSubscriberSCM sets up a connection between an ingress port and a service in a Cisco 6400 UAC. To run the policy successfully, meet the following conditions:

Cisco 6400 UAC is deployed and commissioned.
Service instances are deployed and commissioned.
Service name is configured in LocalDB:C6400DMM.serviceName for the service.
Connection Template objects are deployed and configured.
Line IDs are configured for Cisco 6400 UAC ingress ports.

See the "Configuring Line IDs for CNOM Modules" section for more details.

The connectSubscriberSCM policy performs the following actions:

1. Identifies the ingress port using the line ID or CEMF object name supplied in the incoming work order.

2. Deploys the subscriber object and configures the subscriber values.

3. Allocates a valid VPI/VCI value if one was not provided by the work order.

4. Invokes a connect action on the subscriber object to perform the connection.

See the "NI-1 Profile Policies" section for more information on standards and procedures.

The following optional attributes are supported in work orders for the connection. The attributes are dependent on the type of services to which the connection is made:

workOrder:DDMWorkOrder.rfc1483SubIfIPAddress
workOrder:DDMWorkOrder.rfc1483SubIfSubnetMask
workOrder:DDMWorkOrder.vcIPAddress
workOrder:DDMWorkOrder.rfc1483EncapsType
workOrder:DDMWorkOrder.cpeSupportInArp
workOrder:DDMWorkOrder.ptamdConnectionType
workOrder:DDMWorkOrder.ptamdEncapsType
workOrder:DDMWorkOrder.rbeSubIfIPAddress
workOrder:DDMWorkOrder.rbeSubIfSubnetMask

End-to-End Connection in a Cisco 6400 UAC Architecture

Use the following policies for managing connections in a network of multiple Cisco 6400 UACs.

ATM Connection in a Cisco 6400 UAC Topology

This section and the sections that follow contain information for setting up an ATM Policy in a Cisco 6400 UAC.

The Cisco 6400 UAC architecture features clusters of Cisco 6400 UAC devices arranged in two layers—Remote Terminal (RT) and Competitive Local Exchange Carrier (CLEC)—with full interconnection between the layers. The task for CNOM is to create a pair of PVCs, one on each device, which makes a connection between a port on one Cisco 6400 UAC in a cluster to a port on another Cisco 6400 UAC in a cluster. In this application, the Cisco 6400 UAC devices in:

One layer of a cluster is referred to as RT Cisco 6400 UACs
The other layer is referred to as CLEC Cisco 6400 UACs

The policy connectSubscriberToATMService sets up an ATM cross-connect between an RT Cisco 6400 UAC and a CLEC Cisco 6400 UAC chassis. The policy creates and manages both the services and the subscriber connections for this service. To run the policy successfully, meet the following conditions:

The Cisco 6400 UACs are deployed and commissioned.

The ingress and egress ports are identified and configured with line IDs. See the "Configuring Line IDs for CNOM Modules" section for more details.
The inter-machine tie ports are configured using the policy set_IMT.

Note If the RT and the CLEC Cisco 6400 UAC are the same, you do not need this subscriber-to-ATM configuration.

The connection templates are deployed and configured.

The policy is assigned the following parameters:

workOrder:DDMWorkOrder.connectionIdentifier
workOrder:DDMWorkOrder.ingressIdentifier
workOrder:DDMWorkOrder.egressIdentifier
workOrder:DDMWorkOrder.serviceCharacteristics
workOrder:DDMWorkOrder.ingressVPI
workOrder:DDMWorkOrder.ingressVCI
workOrder:DDMWorkOrder.egressVPI
workOrder:DDMWorkOrder.egressVCI

Use the policy connectSubscriberToATMService to set up an ATM cross-connect between an RT Cisco 6400 UAC and a CLEC Cisco 6400 UAC chassis (Table 4-4).

Attribute	Description
`workOrder:DDMWorkOrder.setupCLECConfig`	Creates and manages both the services and the subscriber connections for this service.

Table 4-4: Attributes for Network Order Policy connectSubscriberTo ATMService

Attribute Description

workOrder:DDMWorkOrder.setupCLECConfig

Creates and manages both the services and the subscriber connections for this service.

CNOM Internal Work Flow for setupCLECConfig

CNOM performs the following steps to execute the setupCLECConfig policy:

Initial State: C6400DMMCtrller:C6400DMM.findCLECPort_SCC

1. Find CLEC Port by Name: ResolveName

2. Find CLEC Chassis: GetAncestorPrimitive

3. Find RT Port: ResolveName

4. Set RT Connected TP attributes: SetAttributesPrimitive

5. Set CLEC Connected TP attributes: SetAttributesPrimitive

Connection Status

If a connection is:

Successful—The socketDaSet command returns the message "Successfully set the following." The connectionObjects view contains a set of objects representing the connection. At the root level of the connectionObjects view is an object with the same name as the workOrder:DDMWorkOrder.connectionIdentifier value. Expand this object to show the objects C6400DMMServices and C6400DMMConnection.

: You can view the ATM services created by the policy under C6400DMMServices. Use the SCM to access the windows to view and configure the services.
: The subscriber and the connections that were set up for this connection are shown under C6400DMMConnection. The subscriber and connection objects are SCM objects and have subscriber and connection windows accessible from this view.

Unsuccessful—The socketDaSet command returns the message "Failed to set the following." Refer to log files ddmGateway.audit, ddmGateway.log, and C6400DMMCtrller.log for more information.

To disconnect a connection made through the connectSubscriberToATMService policy, use the policy disconnectSubscriberAndService. The policy is assigned the connection identifier supplied for the connection in the attribute workOrder:DDMWorkOrder.connectionIdentifier and removes it.

Connect and Disconnect Scripts

The following connect* and disconnect* perl scripts provide a wrapper around socketDaSet to provide a command line option to invoke the policies. You run these scripts from a CEMF shell.

connect_atm—connectSubscriberToATMService—Multiple Cisco 6400 UAC policy connect
disconnect_atm-disconnectSubscriberAndService—Multiple Cisco 6400 UAC policy disconnect
connect_cdm-connectSubscriber_cdm—CDM DSLAM end-to-end connection
disconnect_cdm-disconnectSubscriber_cdm—CDM DSLAM disconnect
connect_scm-connectSubscriberSCM—Cisco 6400 UAC connection
disconnect_scm-disconnectSubscriberSCM—Cisco 6400 UAC connection disconnect

Invoking these scripts without arguments displays the usage statement for the scripts.

These scripts generate a connection identifier using a config file /opt/cemf/db/conncount by default. The connection identifier is generated as string CONN-<conncount> where <conncount> is incrementally generated.

Note When you run the connect_atm script with the -syslog option, the system only records part of the work order in the syslog file. This is because the buffer on the CNOM system is too small to store the entire work order in the syslog record.

Making Multiple Cisco 6400 UAC ATM Connections

Use the script connect_atm to invoke the SCM NOA policy connectSubscriberToATMService based on the following inputs as arguments:

Ingress Identifier—The Remote Chassis ingress port
Egress Identifier—The CLEC Chassis egress port
Service Characteristics—ATM QoS Template name
Ingress VPI
Ingress VCI
Egress VPI
Egress VCI

CNOM performs the appropriate gets and sets to make the ATM connection. To disconnect the connection, use the script disconnect_atm with the connection identifier.

Table of Contents

Connection Status