Configuring the Cisco 6260 DSLAM Equipment Module

The Cisco 6260 DSLAM Equipment Module supports provisioning of cross connections on Cisco 6260 DLSAM DSL access concentrators. The Cisco 6260 DLSAM multiplexes traffic from up to 120 ADSL subscriber ports to a single WAN port. Using a subtending feature, you can link up to 13 Cisco 6260 DLSAM chassis to a single WAN trunk. Each card cage can accommodate two second generation network interface cards (NI-2) and 30 line cards (only one NI-2 card is allowed in this release of CPC). This release provides support for the following network interface cards:

Two variants of the NI-2 card are available:
- 2-port OC3c/STM-1 card
- 3-port DS3 card
The NI-2 card provides the following:
- 1 WAN trunk port
- 1 or 2 subtending ports
- Cisco IOS software
- SNMP agent
- ATM switch fabric
One line card is available: the 4-port DMT line card. This line card provides four discrete multi-tone T1.413 Issue 2 compliant ATUC modems that support ADSL connections over POTS or direct connections. The card support maximum data rates of 8032 Mbps downstream and 864 upstream on all four ports simultaneously.

This release also provides support for the following types of connections:

ATM cross connect between WAN port and DSL port (PVC)
Dangling ATM cross connect on WAN or subtending port (in-band management: upload only)

Other supported features include:

Network and node upload
Auto-generation of VPI/VCI numbers and preassigned VPI/VCI

The Equipment Module uses Cisco's IOS command line interface to download changes to the network. Cisco IOS is also used to configure the Cisco 6260 DSLAM. The software requirements are highlighted below:

Table 9-1: Software Requirements

Vendor Product Version Notes

Cisco

Cisco Internet Operating System (IOS)

12.0(5)DA

Network elements must be configured using this version of Cisco IOS.

Vendor	Product	Version	Notes
Cisco	Cisco Internet Operating System (IOS)	12.0(5)DA	Network elements must be configured using this version of Cisco IOS.

To configure the Cisco 6260 DLSAM Equipment Module you must have installed it during the CPC Server and Client installation procedures. For more information about installing CPC, refer to the chapter titled "Initial Installation".

Step 1 Configure Network Timeout.

Step 2 Initial System Upload.

Step 3 Re-upload (if configuration information has changed)

Step 4 Working with Physical Ports

Step 5 Adding Inter-Network Links (Topology) Information

Step 6 Working with Service Element Profiles

Network Timeout

The Cisco 6260 DLSAM Equipment Module implements an overall timeout for service provisioning Transactions. Network Timeout is defined by the environment variables CCP_ACTIVATION_TIMEOUT (default = 45 seconds) and CCP_RESET_TIMEOUT (default = 45 seconds). They define the maximum interval (measured in seconds) allowed for each service element activation and for the rollback of each service element respectively. The maximum interval time amounts to the maximum time that elapses before the network interface (NIF) times out.

For example, if CCP_ACTIVATION_TIMEOUT=180, the NIF is allowed three minutes to activate an item in a Transaction.

The default settings are used if the NIF detects that these variables are not set in the environment.

Network Timeout requires shutting down the server if it is not already down, setting the variables, and then restarting it to pick up the environment changes.

To set the CCP_ACTIVATION_TIMEOUT environment variable:

Step 1 Shut down the CPC server by issuing the following command:

SYnpt -h

Step 2 Set the environment variable to an integer (measured in seconds) that amounts to the maximum time to elapse before the NIF times out:

export CCP_ACTIVATION_TIMEOUT=90

To set the CCP_RESET_TIMEOUT environment variable:

Step 3 Set the environment variable to an integer (measured in seconds) that amounts to the maximum time to elapse before the NIF times out:

export CCP_RESET_TIMEOUT=90

Step 4 Bring CPC up by sourcing the server environment. To source the environment, run the following commands in succession:

cd /opt/SY/CPC/Server/mng/utility
. syccpovdef
SYnpt -sS

Initial System Upload

To provision services, the CPC database must have detailed knowledge of the managed subnetworks. Using a procedure called upload, objects are created within the CPC database that represent objects of the managed network.

Note The term upload does not refer to the creation of inter-network links because they are outside the scope of any single Equipment Module. See the section titled "Adding Inter-Network Links (Topology) Information".

CPC supports the following types of upload:

fabric (nodes, DSL templates, physical ports, logical ports, traffic tables)
service (cross connections)
fabric and service (all)

For the Cisco 6260 DLSAM Equipment Module you can upload many nodes at once (network upload) or an individual node at a time. CPC supports the following upload scenarios:

Given a Network object, upload just the fabric elements for the nodes in that network
Given a Network object, upload just the Service elements for the nodes in that network
Given a Network object, upload all fabric and Service elements for the nodes in that network
Given a Node object, upload just the fabric elements for that node
Given a Node object, upload just the Service elements for that node
Given a Node object, upload all fabric and Service elements for that node

Note The upload function takes precedence over any Transactions that are running at the time of upload. If the upload function makes a change back to the fabric that affects a running Transaction (such as deleting a logical port that the threader has decided to use) then this Transaction fails and must be restarted.

Network and Node objects must be created to perform an Upload.

Before You Upload: Creating a Network Object

One network object must be created for each network. The following steps explain how to create a network object.

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Click the Cisco 6260 DSLAM Network folder to highlight it. You can select objects in the Tree Viewer Cisco 6260 DSLAM Network list or you can filter your requests for specific criteria.

Step 3 Click the Subset Viewer button on the toolbar.

Step 4 Enter the attribute values in the available row of cells.

Step 5 Save the network object by clicking the save button on the toolbar.

Step 6 To specify other attributes, click a cell in the row to highlight the row and click the Object Viewer button on the toolbar.

: When creating a network object, the Subset Viewer will request the following attributes:

Mandatory fields:
- Name: network name
Fields that have default values:
- Transit Cost: the cost of crossing the subnetwork. This is typically assigned the value of 500.

: When creating a network object in the Object Viewer, these attributes can be seen:

Fields that have default values and can not be modified:
- Class: the CPC class name for the Network Object
- Opaque: the threading strategy (opaque or transparent). The default is disabled.
- Use Backup EMSL disabled to use the primary EMS, enabled to use the backup EMS. The default is disabled.
- Resource Map:0

Step 7 Save the network object by clicking the save button on the toolbar.

Step 8 Apply the transaction by clicking the apply button on the toolbar.

Note Attribute fields can be added to the Subset Viewer if required. Refer to the section titled "Cisco 6260 DSLAM DSL Physical Port Attributes".

Creating a Node Object

You should create Node objects for all Cisco 6260 DLSAM nodes in the network. The following steps explain how to create a Node object.

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Cisco 6260 DLSAM list or you can filter your request for specific criteria.

Step 3 Double-click the Cisco 6260 DLSAM Network object that contains the Node object that you are creating.

Step 4 Click on Cisco 6260 DLSAM Node to highlight it.

Step 5 Click the Subset Viewer button on the toolbar.

: Enter the attribute values in the available row of cells. When creating a Node object, the Subset Viewer will request the following attributes;

Mandatory fields:
- Name: node name
- Network: the name of the network that this node belongs to
- Management Address: fill in the IP address or symbolic name for the node
- Transit Cost: the cost of crossing this node. This is typically assigned a value of 1000.
- User Name: the user name for the node
- Access Password: the access password for the node.
- Enable Password: the enable password for the node.
Fields that have default values that can not be modified:
- Node Type: this specifies the equipment type. The default is CN12 DSLAM.

Step 6 Save the Node object by clicking the save button on the toolbar.

Step 7 To specify the other attributes, click a cell in the row to highlight the row and click the Object Viewer button on the toolbar. You can specify the following attributes:

Containing Region
Geographical Location
Organization Location

: Fields that have default values that can not be modified

Class

Step 8 Save the Node object by clicking the save button on the toolbar.

Step 9 Apply the transaction by clicking the apply button on the toolbar.

Network Upload

This section describes how to upload the fabric and service elements.

Uploading the Fabric and Service Elements for a Network Object

After creating a network object, you can now upload the fabric and service elements. To upload the fabric and service elements for a Network object, complete the following steps:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Tree Viewer Cisco 6260 DSLAM Network list or you can filter your requests for specific criteria.

Step 3 Click a network object from the list to highlight it.

Step 4 Select load fabric from the Element menu. The upload begins.

Step 5 When the upload is complete, an xterm window will display. If there were errors during the upload they will appear in this window.

Uploading the Fabric Elements for a Network Object

Given that the network object is in place, you can now upload fabric. Uploading Network fabric creates the node objects that correspond to the specified network. Any fabric element contained by the nodes is also updated.

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Tree Viewer Cisco 6260 DSLAM Network list or you can filter your requests for specific criteria.

Step 3 Click a network object from the list to highlight it.

Step 4 Select load fabric from the Element menu. The upload begins.

Step 5 When the upload is complete, an xterm window will display. If there were errors during the upload they will appear in this window.

Uploading the Service Elements for a Network Object

After you have uploaded the fabric elements, you can upload the services.

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Tree Viewer Cisco 6260 DSLAM Network list or you can filter your requests for specific criteria.

Step 3 Click a network object from the list to highlight it.

Step 4 Select load services from the Element menu. The upload begins.

Step 5 When the upload is complete, an xterm window will display. If there were errors during the upload they will appear in this window

Uploading for Individual Nodes

This section describes how to upload for individual nodes.

After you create a Node object, you may want to upload all the fabric and service elements for that node. The fabric elements for a Node object are the node itself, physical ports, and logical ports. The service elements are the objects used to create services (cross connections). Complete the following steps to upload the fabric and service elements:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Cisco 6260 DSLAM Network list or you can filter your request for specific criteria.

Step 3 Double-click a Cisco 6260 DSLAM Network object folder to open it.

Step 4 Click the Cisco 6260 DSLAM Network object folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all the nodes, double-click the Cisco 6260 DSLAM Node folder.

Step 5 Click the node you wish to upload and highlight it.

Step 6 Select load both (fabric and services) from the Element menu. The upload will begin.

Step 7 When the upload is complete, an xterm window displays. If there were errors during the upload they appear in this window.

Uploading the Fabric Elements for a Node Object

After you create a Node object, you may want to upload just the fabric elements for that node. Complete the following steps to upload the fabric elements:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Cisco 6260 DSLAM Network list or you can filter your request for specific criteria.

Step 3 Double-click a Cisco 6260 DSLAM Network object folder to open it.

Step 5 Click the node you wish to upload and highlight it.

Step 6 Select load fabric from the Element menu. The upload will begin.

Step 7 When the upload is complete, an xterm window displays. If there were errors during the upload they appear in this window.

Uploading the Service Elements for a Node Object

After you create a Node object, you may want to upload just the service elements for that node. Complete the following steps to upload the service elements:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DLSAM Network folder to open it. You can select objects in the Cisco 6260 DSLAM Network list or you can filter your request for specific criteria.

Step 3 Double-click a Cisco 6260 DSLAM Network object folder to open it.

Step 5 Click the node you wish to upload and highlight it.

Step 6 Select load services from the Element menu. The upload will begin.

Step 7 When the upload is complete, an xterm window displays. If there were errors during the upload they appear in this window.

Viewing the Upload Progress

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Upload Request folder to open it.

Step 3 Double-click the specific upload request folder to open it.

Step 4 Double-click the Upload Request Log to open it.

Step 5 Click the AuditLog to highlight it and click the Log Viewer button on the toolbar.

Re-Upload

The CPC database needs to be continually updated if changes are being made to nodes in the network in order to stay synchronized. You should re-upload after any of the following scenarios:

an existing node has been upgraded
new hardware has been added to a switch
you need to recover from a failure situation (to synchronize the database with the network)
when Service elements are not updated by CPC (both for initial population of the database and also for co-existence with other provisioning products)

To re-upload you need to upload the fabric and service elements of that node.

DSL Templates

DSL templates are profiles used by physical ports that define attributes for physical ports. The Cisco 6260 DSLAM employs templates to configure DSL physical ports rather than configure them directly. These templates are uploaded during fabric element upload and can be associated with more than one physical port.

Working with Physical Ports

This release allows you to modify the DSL physical ports. WAN physical port modifications are not supported in this release.

Modifying Physical Ports

The only attributes that can be modified for a DSL physical port are either bandwidth (incoming and outgoing) or the DSL template name (which itself contains a bandwidth attribute). To modify these attributes, complete the following steps:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DSLAM Network folder to open it. You can select objects in the Cisco 6260 DLSAM Network list or you can filter your request for specific criteria.

Step 3 Double-click a Cisco 6260 DSLAM Network object folder to open it.

Step 4 Click the Cisco 6260 DSLAM Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the node that contains the physical port that you want to modify and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6260 DSLAM Node folder.

Step 5 Double-click the specific node folder to open it.

Step 6 Click the type physical port you would like to modify from the list (for example, Cisco 6260 DSLAM Physical Port).

Step 7 Enter the search criteria in the appropriate filter fields to find the physical port you want to modify and click the getlist button on the toolbar. To list all of the physical ports, double-click the physical port folder.

Step 8 Click the specific physical port to highlight it.

Step 9 Click the Object Viewer button on the toolbar.

Step 10 Click the cell containing the attribute you want to modify and enter a new value (only incoming/outgoing bandwidth or template name can be modified).

Note When modifying the bandwidth for a DSL physical port, the value must not exceed the upstream/downstream bandwidth value specified in the DSL template. Values greater than those specified in the template will give an error message. The bandwidth (upstream and downstream) values contained in the DSL template equal the sum of the maximum fast path bit rate and the maximum interleaved path bit rate.

Step 11 Save the template by clicking the save button on the toolbar.

Step 12 Apply the transaction by clicking the apply button on the toolbar.

Cisco 6260 DSLAM DSL Physical Port Attributes

The Cisco N12 DSLAM DSL physical port Object Viewer provides you with access to the additional attributes that you can configure for a physical port.

Figure 9-1 shows the Cisco N12 DSLAM DSL Physical Port Object Viewer.

Figure 9-1: Cisco N12 DLSAM DSL Physical Port Object Viewer

Table 9-2 below lists the attributes for a DSL physical port. Attributes with an asterisk "*" next to their Default value indicates that these fields cannot be changed.

Table 9-2: Cisco N12 DSLAM DSL Physical Port Attributes

Attribute Name Description Acceptable Values Default Value

Common Attributes

Name

The DSL physical port name

Text string (up to 24 characters)

*

Customer

The is the customer.

Text string (up to 16 characters)

*

Domain

This is the domain name.

Text string (up to 16 characters)

*

Profile

This attribute is not supported by this equipment module.

Default

Default*

Port Number

This is the physical port number.

0-2147483647

*

Shelf Slot Number

This is the physical port shelf slot number.

Text string (up to 16 characters)

*

Port Type

The DSL physical port type.

ADSL

ADSL*

Bandwidth (kbits/s)

The bandwidth for the physical port.

0-maximum port bandwidth

0*

Max PDU size (bytes)

The maximum protocol data unit size.

0*

Subscriber Id

The subscriber identification number.

Text string (up to 32 characters)

*

Class

The CPC class name for this physical port object.

C2dp

C2dp*

Service Object Id

The Service Object identification number that owns this port.

Text string (up to 44 characters)

*

Protocol

The protocol supported by this physical port.

DSL

DSL*

Maximum Timeslots

Specify the maximum number of channels for this physical port.

0*

Contained By

Network

This identifies the network that contains the physical port. This attribute is auto-generated based on the physical port's location.

Text string (up to 32 characters)

*

Node

This identifies the node that contains the physical port. This attribute is auto-generated based on the physical port's location.

Text string (up to 32 characters)

*

srmlink.srname

Text string (up to 32 characters)

LAN Attributes

Maximum Incoming Bandwidth (kbits/s)

The maximum incoming bandwidth supported by this physical port. This value is auto-generated based on the physical port type.

0-2147483647

0*

Maximum Outgoing Bandwidth (kbits/s)

The maximum outgoing bandwidth supported by this physical port. This value is auto-generated based on the physical port type.

0-2147483647

0*

Incoming Bandwidth (kbits/s)

The incoming bandwidth for this physical port.

0-2147483647

0

Outgoing Bandwidth (kbits/s)

The outgoing bandwidth for this physical port.

0-2147483647

0

AZ signal-to-ratio margin

The AZ signal-to-noise ratio margin. The higher this margin is set, the more protection there is against data corruption. Higher margins support lower data rates for a given loop.

0-2147483647

3*

ZA signal-to-ratio margin

The ZA signal-to-ratio margin. The higher this margin is set, the more protection there is against data corruption. Higher margins support lower data rates for a given loop.

0-2147483647

3*

Rate Adaptation Mode

The rate adaptation mode for the physical port.

Fixed, Dynamic, Startup

Fixed

Cisco N12 DSLAM

Cisco N12 DSLAM DSL Template

Specify the Cisco N12 DSLAM DSL Template that is being used.

Text string (up to 32 characters)

default

Port Enable

Specify whether or not to enable or disable the physical port.

TRUE, FALSE

TRUE*

Attribute Name	Description	Acceptable Values	Default Value
Common Attributes
Name	The DSL physical port name	Text string (up to 24 characters)	*
Customer	The is the customer.	Text string (up to 16 characters)	*
Domain	This is the domain name.	Text string (up to 16 characters)	*
Profile	This attribute is not supported by this equipment module.	Default	Default*
Port Number	This is the physical port number.	0-2147483647	*
Shelf Slot Number	This is the physical port shelf slot number.	Text string (up to 16 characters)	*
Port Type	The DSL physical port type.	ADSL	ADSL*
Bandwidth (kbits/s)	The bandwidth for the physical port.	0-maximum port bandwidth	0*
Max PDU size (bytes)	The maximum protocol data unit size.		0*
Subscriber Id	The subscriber identification number.	Text string (up to 32 characters)	*
Class	The CPC class name for this physical port object.	C2dp	C2dp*
Service Object Id	The Service Object identification number that owns this port.	Text string (up to 44 characters)	*
Protocol	The protocol supported by this physical port.	DSL	DSL*
Maximum Timeslots	Specify the maximum number of channels for this physical port.		0*
Contained By
Network	This identifies the network that contains the physical port. This attribute is auto-generated based on the physical port's location.	Text string (up to 32 characters)	*
Node	This identifies the node that contains the physical port. This attribute is auto-generated based on the physical port's location.	Text string (up to 32 characters)	*
srmlink.srname		Text string (up to 32 characters)
LAN Attributes
Maximum Incoming Bandwidth (kbits/s)	The maximum incoming bandwidth supported by this physical port. This value is auto-generated based on the physical port type.	0-2147483647	0*
Maximum Outgoing Bandwidth (kbits/s)	The maximum outgoing bandwidth supported by this physical port. This value is auto-generated based on the physical port type.	0-2147483647	0*
Incoming Bandwidth (kbits/s)	The incoming bandwidth for this physical port.	0-2147483647	0
Outgoing Bandwidth (kbits/s)	The outgoing bandwidth for this physical port.	0-2147483647	0
AZ signal-to-ratio margin	The AZ signal-to-noise ratio margin. The higher this margin is set, the more protection there is against data corruption. Higher margins support lower data rates for a given loop.	0-2147483647	3*
ZA signal-to-ratio margin	The ZA signal-to-ratio margin. The higher this margin is set, the more protection there is against data corruption. Higher margins support lower data rates for a given loop.	0-2147483647	3*
Rate Adaptation Mode	The rate adaptation mode for the physical port.	Fixed, Dynamic, Startup	Fixed
Cisco N12 DSLAM
Cisco N12 DSLAM DSL Template	Specify the Cisco N12 DSLAM DSL Template that is being used.	Text string (up to 32 characters)	default
Port Enable	Specify whether or not to enable or disable the physical port.	TRUE, FALSE	TRUE*

Logical Ports

In this release, all ATM logical ports are created during fabric upload. Logical port creation, modification and deletion are not supported in this release.

Adding Inter-Network Links (Topology) Information

After uploading new fabric elements and Service elements, you need to add extra topology information which the upload function is unable to determine (because the information is not known to the node). Topology information or internetwork links are outside the scope of a single node or subnet manager and must be added manually through the CPC GUI or the FTI.

Adding Links Using the GUI

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Cisco 6260 DSLAM Network folder to open it. You can select objects in the Cisco 6260 DLSAM Network list or you can filter your request for specific criteria. Refer to the section "Filtering" in the chapter titled "GUI Navigation" for more information on filtering in the Tree Viewer.

Step 3 Double-click a network object folder to open it.

Step 4 Click the Cisco 6260 DSLAM Node folder to highlight it. Enter search criteria in the appropriate filter fields to find the Node object and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco 6260 DSLAM Node folder.

Step 5 Double-click the specific node folder to open it.

Step 6 Click a Cisco N12 DSLAM logical port folder (for example, Cisco N12 DSLAM ATM Logical Port) to highlight it. Enter search criteria in the appropriate filter fields to find a specific logical port and then click the get list button on the toolbar.

Step 7 Paste the chosen logical port in the Link Subset Viewer by clicking the paste button on the toolbar. The Link Subset Viewer has cells for Local Logical Port and another for Remote Logical Port, representing the two endpoints of the internetwork link. You must choose a logical port for both endpoints.

Step 8 You can create a locked or unlocked link. If you want to create a link, but disallow any provisioning of services across it, select Locked by clicking the empty cell below either of the Lport Status menus. When the cell is clicked, a pull down menu will appear. If you want CPC to use the link, leave the default value as Unlocked.

Step 9 If you are not satisfied with a value, click the appropriate field and modify it.

Step 10 Save the link object by clicking the save button on the toolbar.

Step 11 Apply the Transaction by clicking the apply button on the toolbar.

Step 12 Repeat the above procedure for the creation of each internetworking link.

Traffic Tables

Nodes in the Cisco N12 DSLAM network contain traffic tables. Rows in the traffic table define traffic parameters for one direction or a PVC flow. Each PVC may refer to two traffic table rows, one for each direction. Traffic table rows can also be referenced by more than one PVC, applying the same traffic parameters to each. A traffic table index must be present before creating ATM-ATM cross connections in a Cisco N12 DSLAM node.

Working with Service Element Profiles

Service element profiles provide you with access to the Cisco-specific attributes for a particular Service element. There is a corresponding Service element profile for each Service element type that the node supports. Default profiles provide the initial (default) attribute values for the corresponding object class whenever such a new object is created.

For a given Service element, more than one profile may be defined. However, for a given object, only one profile may be associated at any one time.

Since profiles themselves are objects which you can create and modify, they provide a means to store and name commonly used sets of attributes and provide a reliable shorthand method of configuring any number of new objects. A profile has most of the same attributes as the corresponding object class. Some attributes of the object class are not included in the profile because they are expected to be unique for each object. For example, the DLCI on a Frame Relay Cross Connection would not be a profile attribute. Similarly, an object's name is not a profile attribute.

The attributes of a profile are referred to as initial value attributes because they are used to assign the initial values to the corresponding object. Once a new object has been created based on a profile, changes to profile attribute values do not cause any changes to the corresponding object. The only time the profile attributes affect the object is when you create a new object or when you reassign an existing object to the same or different profile.

For the Cisco N12 DSLAM Equipment Module, you can create Service Element profiles for the following supported Service element:

ATM-ATM Cross Connections

This section details the generic procedure for creating, modifying, and deleting Service element profiles, and then provides the specific configurable attributes for each Service element profile for this Equipment Module.

If you provide values for these attributes and also provide values in other places when you are creating a service (either during service creation or in a Service object profile) the threader will override the values based on the following scale of priorities:

1. Service object Object Viewer--All information provided in the Service object SubsetViewer is used by CPC.

2. Service object profile--CPC will only use the information provided in the Service object profile for values that are either not available or not specified in the Service object SubsetViewer.

3. Service element profile--CPC uses values from the Service element profile for all attributes that are not present or not specified in the Service object profile or on the Service object SubsetViewer.

Creating a Service Element Profile

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Equipment Module folder to open it.

Step 3 Double-click the Cisco N12 DSLAM Equipment Module folder to open it.

Step 4 Click the folder that represents the Service element profile you want to create (for example, Cisco N12 DSLAM ATM-ATM Cross-Connect Profile) to highlight it.

Step 5 Click the Object Viewer button on the toolbar.

Step 6 Enter a Name for the profile and enter the appropriate attribute values in the available row of cells.

Step 7 Save the profile by clicking the save button on the toolbar.

Step 8 Apply the Transaction by clicking the apply button on the toolbar.

Modifying a Service Element Profile

To modify a Service element profile, complete the following steps:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Equipment Module folder to open it.

Step 3 Double-click the Cisco N12 DSLAM Equipment Module folder to open it.

Step 4 Click the folder that represents the Service element profile you want to modify (for example, Cisco N12 DSLAM ATM-ATM Cross-Connect Profile) to highlight it.

Step 5 Click the Subset Viewer button on the toolbar.

Step 6 Click the get list button on the toolbar to get a list of profiles.

Step 7 Click the profile and modify the values in the available row of cells.

Step 8 Save the profile by clicking the save button on the toolbar.

Step 9 To specify other attributes, highlight the row and click the ObejctViewer button on the toolbar. For more information about the configurable attributes and their values, refer to the attribute tables in this section.

Step 10 Save the profile by clicking the save button on the toolbar. Apply the Transaction by clicking the apply button on the toolbar.

Note Attribute fields in the Subset Viewer can be added, modified and deleted if required. Refer to the section "Customization" in the chapter titled "GUI Navigation" for more information on customizing the Subset Viewer.

Deleting a Service Element Profile

To delete a Service element profile, complete the following steps:

Step 1 Click the Tree Viewer button on the toolbar.

Step 2 Double-click the Equipment Module folder to open it.

Step 3 Double-click the Cisco N12 DSLAM Equipment Module folder to open it.

Step 4 Double-click the type of profile that you want to delete (for example, Cisco N12 DSLAM ATM-ATM Cross-Connect Profile).

Step 5 Click the specific profile to highlight it.

Step 6 Click the delete button on the toolbar.

Step 7 Apply the Transaction by clicking the apply button on the toolbar.

ATM Cross Connection Service Element Profile Attributes

The ATM-ATM Cross Connection Service element profile provides you with access to the additional attributes that you can configure for an ATM service through the Cisco N12 DSLAM. The ATM cross connect object represents a cross connect between two ATM logical ports in the same node. The information you provide in the Service element profile is communicated to the Cisco N12 DSLAM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile.

Figure 9-2 shows the Cisco N12 DSLAM ATM-ATM Cross Connection Profile Object Viewer.

Figure 9-2: Cisco N12 DSLAM ATM-ATM Cross Connection Profile Object Viewer

Table 9-3 below lists the configurable attributes for the Cisco N12 DSLAM ATM-ATM cross connection. Attributes marked with an asterisk "*" next to their Default value indicates that these fields should not be changed.

Table 9-3: Cisco N12 DSLAM ATM-ATM Cross Connection Profile Attributes

Attribute Name Description Acceptable Values Default Value

Common Attributes

Name

The cross connection name.

Text string (up to 24 characters)

Customer

The customer name.

Text string (up to 16 characters)

Domain

The domain name.

Text string (up to 16 characters)

Recovery Priority

The recovery priority for NNI resiliency.

0...n where 0 indicates that the service should not be moved, 1 is the highest priority and n is the lowest priority

0

UNI Recovery Priority

The recovery priority for UNI resiliency.

0...n where 0 indicates that the service should not be moved, 1 is the highest priority and n is the lowest priority

0

Provider Service

The provider service for the cross connection.

Text string (up to 32 characters)

Service Object Id

The service object Id for the cross connection.

Text string (up to 44 characters)

A Endpoint VCI

The VCI for the A endpoint.

-1-1023

-1

A Endpoint VPI

The VPI for the A endpoint.

-1-1023

-1

Z Endpoint VCI

The VCI for the Z endpoint.

-1-1023

-1

Z Endpoint VPI

The VPI for the Z endpoint.

-1-1023

-1

ATM Attributes

Circuit Type

The circuit type.

VC, VP

VC

Class of Service

You can specify the class of service for traffic. The class of service determines which traffic descriptor you can select.

nrt_VBR, rt_VBR, UBR, CBR, None

0

Fixed Found Trip Time

The Fixed Round Trip Time is the sum of the fixed and propagation delays from the source destination and back.

0-16700000

0

A to Z, Z to A Directions

Bandwidth

(kbits/s)

The bandwidth for the cross connection.

0-2147483647

0

Primary Logical Port

The original logical port that is being hacked up by UNI resiliency (nodename/portname).

text string (up to 44 characters)

Sustainable Cell Rate (cells/s)

SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met.

0-910533065

0

Peak Cell Rate

(cells/s)

PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met.

0-910533065

0

Minimum Cell Rate (cells/s)

MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection.

0-910533065

0

Maximum Burst Size (cells)

MBS is the maximum number of cells that can be received at the PCR. This allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are tagged or dropped. The parameters applies only to VBR traffic.

0-2147483647

0

CDVT(micro-seconds)

Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allows for jitter (CDV).

0-2147483647

0

Traffic Desc

This is the traffic descriptor type which describes the specified traffic parameters for the service (for more information see the chapter titled "Provisioning ATM Services".

VBR.3, VBR.2, VBR.1, UBR.2, UBR.1, CBR.1, None

None

Initial Cell Rate (cells/sec)

The Equipment Module does not support this attribute.

0

Rate Increase Factor

The Equipment Module does not support this attribute.

1/16

NRM (cells)

The Equipment Module does not support this attribute.

0

Rate Decrease Factor

The Equipment Module does not support this attribute.

1/16

ACR Decrease Time Factor (millisec)

The Equipment Module does not support this attribute.

0

TRM (millisec)

The Equipment Module does not support this attribute.

100

Transient Buffer Exposure (cell)

The Equipment Module does not support this attribute.

0

Cutoff Decrease Factor

The Equipment Module does not support this attribute.

1/16

Cisco N12 DSLAM

A-Side Logical Port Reference

The logical port reference for the A-side. This is in the format slot/port.

Text string (up to 12 characters)

Z-Side Logical Port Reference

The logical port reference for the Z-side. This is in the format slot/port.

Text string (up to 12 characters)

Packet Discard Enable

Specify whether or not to enable or disable packet discard.

TRUE, FALSE

FALSE

A to Z, Z to A directions

Usage Parameter Control

The usage parameter control for the a-z and z-a directions. When set to "derived," the Equipment Module delivers a value of pass, tag or drop based on the traffic descriptor type.

pass, tag, drop, or derived

derived

CDVT Default Value

The a-z and z-a CDVT not specified in the connection traffic table. The logical port specific default value is used.

TRUE, FALSE

FALSE

MBS Default Value

The a-z and z-a MBS not specified in the connection traffic table. The logical port specific default value is used.

TRUE, FALSE

FALSE

Attribute Name	Description	Acceptable Values	Default Value
Common Attributes
Name	The cross connection name.	Text string (up to 24 characters)
Customer	The customer name.	Text string (up to 16 characters)
Domain	The domain name.	Text string (up to 16 characters)
Recovery Priority	The recovery priority for NNI resiliency.	0...n where 0 indicates that the service should not be moved, 1 is the highest priority and n is the lowest priority	0
UNI Recovery Priority	The recovery priority for UNI resiliency.	0...n where 0 indicates that the service should not be moved, 1 is the highest priority and n is the lowest priority	0
Provider Service	The provider service for the cross connection.	Text string (up to 32 characters)
Service Object Id	The service object Id for the cross connection.	Text string (up to 44 characters)
A Endpoint VCI	The VCI for the A endpoint.	-1-1023	-1
A Endpoint VPI	The VPI for the A endpoint.	-1-1023	-1
Z Endpoint VCI	The VCI for the Z endpoint.	-1-1023	-1
Z Endpoint VPI	The VPI for the Z endpoint.	-1-1023	-1
ATM Attributes
Circuit Type	The circuit type.	VC, VP	VC
Class of Service	You can specify the class of service for traffic. The class of service determines which traffic descriptor you can select.	nrt_VBR, rt_VBR, UBR, CBR, None	0
Fixed Found Trip Time	The Fixed Round Trip Time is the sum of the fixed and propagation delays from the source destination and back.	0-16700000	0
A to Z, Z to A Directions
Bandwidth (kbits/s)	The bandwidth for the cross connection.	0-2147483647	0
Primary Logical Port	The original logical port that is being hacked up by UNI resiliency (nodename/portname).	text string (up to 44 characters)
Sustainable Cell Rate (cells/s)	SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met.	0-910533065	0
Peak Cell Rate (cells/s)	PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met.	0-910533065	0
Minimum Cell Rate (cells/s)	MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection.	0-910533065	0
Maximum Burst Size (cells)	MBS is the maximum number of cells that can be received at the PCR. This allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are tagged or dropped. The parameters applies only to VBR traffic.	0-2147483647	0
CDVT(micro-seconds)	Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allows for jitter (CDV).	0-2147483647	0
Traffic Desc	This is the traffic descriptor type which describes the specified traffic parameters for the service (for more information see the chapter titled "Provisioning ATM Services".	VBR.3, VBR.2, VBR.1, UBR.2, UBR.1, CBR.1, None	None
Initial Cell Rate (cells/sec)	The Equipment Module does not support this attribute.		0
Rate Increase Factor	The Equipment Module does not support this attribute.		1/16
NRM (cells)	The Equipment Module does not support this attribute.		0
Rate Decrease Factor	The Equipment Module does not support this attribute.		1/16
ACR Decrease Time Factor (millisec)	The Equipment Module does not support this attribute.		0
TRM (millisec)	The Equipment Module does not support this attribute.		100
Transient Buffer Exposure (cell)	The Equipment Module does not support this attribute.		0
Cutoff Decrease Factor	The Equipment Module does not support this attribute.		1/16
Cisco N12 DSLAM
A-Side Logical Port Reference	The logical port reference for the A-side. This is in the format slot/port.	Text string (up to 12 characters)
Z-Side Logical Port Reference	The logical port reference for the Z-side. This is in the format slot/port.	Text string (up to 12 characters)
Packet Discard Enable	Specify whether or not to enable or disable packet discard.	TRUE, FALSE	FALSE
A to Z, Z to A directions
Usage Parameter Control	The usage parameter control for the a-z and z-a directions. When set to "derived," the Equipment Module delivers a value of pass, tag or drop based on the traffic descriptor type.	pass, tag, drop, or derived	derived
CDVT Default Value	The a-z and z-a CDVT not specified in the connection traffic table. The logical port specific default value is used.	TRUE, FALSE	FALSE
MBS Default Value	The a-z and z-a MBS not specified in the connection traffic table. The logical port specific default value is used.	TRUE, FALSE	FALSE

Table of Contents

Configuring the Cisco 6260 DSLAM Equipment Module