Ch 4: Creating Connections and ATM QoS Profiles

This chapter describes how to use the connection synchronization policy feature, how to create PVCs and SPVCs, how to manage virtual channels links (VCLs), how to manually upload ATM connections and create ATM quality of service (QoS) profiles, and how to use inverse multiplexing over ATM (IMA) on Cisco 6015 and 6160 DSLAMs.

This chapter includes the following sections:

Polling the Chassis and Setting the Connection Synchronization Policy

This section describes two features that preserve the synchronization of CDM and DSLAM configurations after you deploy and commission the DSLAM through CDM. This section includes the following topics:

These two features, which you can set in the Chassis Polling/Connection Policy window, include:

Chassis Polling—Automatically saves configuration data from the DSLAM running configuration to the DSLAM startup configuration.
Connection Synchronization Policy—Configures the synchronization of PVC or SPVC data between CDM and the DSLAM. If you do not choose to set policy, a default policy is set.

CDM automatically synchronizes connection information, that is, PVCs and SPVCs, between the DSLAM and CDM. In certain cases when you make a change to the IOS running configuration, such as creating or deleting a PVC, CDM might not save the change to the startup configuration before the DSLAM reboots. In this case, you can set three policies to specify how the data is synchronized. These are described in the "Overview of the Connection Synchronization Policy" section.

The Chassis Polling/Connection Policy window is shown in Figure 4-1.

Figure 4-1 Chassis Polling/Connection Policy Window

Overview of Chassis Polling

The chassis polling feature instructs CDM to periodically poll the DSLAM for changes to the running configuration. If the polling process determines that the running configuration has changed, CDM sets an internal flag, called a dirty flag, against the DSLAM. The value that you set in the Dirty Flag Check Interval field in the Chassis Polling/Connection Policy window determines the polling interval (in seconds), as shown in Figure 4-1.

CDM periodically polls the value of the dirty flag. If CDM sets the dirty flag to TRUE, CDM saves the running configuration in the chassis. CDM writes the running configuration into the startup configuration only if the internal dirty flag is TRUE. This operation is referred as the write mem operation. You can define how often CDM performs the write mem operation in the Write Memory Interval field in the Chassis Polling/Connection Policy window. The default value for the Write Memory Interval is 1800 seconds; the value range is from 1800 to 86400 seconds.

Setting Polling Intervals

When changes occur on the DSLAM, the polling function checks the running configuration against the saved configuration. If a change has occurred, and the device has not saved the configuration, CDM issues a dirty flag.

You can set the polling interval and the dirty flag check interval in the Chassis Polling/Connection Policy window as follows.

Step 1 On the Map Viewer window, within the Physical view, click the chassis object whose connection policy you want to set.

Step 2 Choose Cisco DSL Manager > Chassis > Administration > Chassis Polling/Connection Policy from the object menu.

The Chassis Polling/Connection Policy window opens. (See Figure 4-5.)

Figure 4-2 Chassis Polling/Connection Policy Window

The area for setting intervals is the Polling Intervals area.

Step 3 In the Write Memory Interval (seconds) field, enter the number of seconds to specify how often you want CDM to perform a write memory (and save the configuration).

The default setting is 1800 seconds.

Step 4 In the Dirty Flag Check Interval (seconds), enter the number of seconds to specify how often you want CDM to check for a dirty flag.

The default setting is 900 seconds.

CDM checks the running configuration against the saved configuration to see whether a change has occurred on the DSLAM since the last configuration save. If a change has occurred, CDM sets the dirty flag (marked "dirty"). The next time the writemem task executes, it checks the state of the dirty flag. If CDM sets the dirty flag, the writemem task writes the IOS running configuration to the startup configuration.

Step 5 Click the Save icon in the toolbar to save the settings.

Synchronizing Alarms and Saving the Running Configuration

You can save the DSLAM running configuration in the Chassis Configuration window, which opens to the Device Management tab. (See Figure 4-3.)

Figure 4-3 Chassis Configuration Window—Device Management Tab

Click the writeMem button to force a write memory operation on a selected chassis and save the DSLAM IOS running configuration to the startup configuration.

Overview of the Connection Synchronization Policy

You can set policy (rules) to instruct CDM to automatically synchronize PVCs and SPVCs, between CDM and the DSLAM. You set this parameter in the in the Connection Policy area of the Chassis Polling/Connection Policy window. (See Figure 4-4.)

Figure 4-4 Chassis Polling/Connection Policy Window

The value that you select in the Connection Synchronization Policy field also determines which PVC and SPVC ATM connections CDM will upload when you use the ATM Connection Upload window to upload ATM connections.

The three types of synchronization policies include:

Normal—No action. The DSLAM is master, but do not add a connection to or delete a connection from CDM.
DeviceisMaster—The default. This setting specifies that the DSLAM (device) is the reference point for PVC creations and deletions. CDM will sync up to the device. If a connection is present on the DSLAM but not in CDM, CDM will create the connection. If a connection is absent on the DSLAM but present in CDM, CDM will delete the connection.
EMIsMasterAfterFirstSync—This setting specifies that the element manager, that is, CDM, is the reference point for PVC creations and deletions. The device syncs up to CDM for information about PVC settings. If the connection is present in CDM but not the DSLAM, CDM creates the connection in the DSLAM. If the connection is absent in CDM but present in the DSLAM, CDM deletes the connection from the DSLAM.

The default policy is DeviceisMaster. When you deploy and commission a DSLAM, CDM first copies the device IOS information into CDM. After commissioning is complete, CDM becomes the reference point for PVC creations and deletions.

Table 4-1, Table 4-2, and Table 4-3 describe the behaviors associated with the settings of the synchronization policies.

Table 4-1 Connection Policy—Normal

Connection in CEMF	Connection State in CEMF	Connection State in DSLAM	Synchronization Policy Behavior
Present	Normal	Not present	Change state to decommission.
Present	Decommission	Not present	Do not do anything.
Present	Normal	Present	No action needed.
Present	Decommission	Present	Change state to normal.
Not present	—	Present	Create in CEMF.

Table 4-2 Connection Policy—Device is Master

Connection in CEMF	Connection State in CEMF	Connection State in DSLAM	Synchronization Policy Behavior
Present	Normal	Not present	Remove from CEMF.
Present	Decommission	Not present	Remove from CEMF.
Present	Normal	Present	No action needed.
Present	Decommission	Present	Change cemf state to normal.
Not present	—	Present	Create in CEMF.

Table 4-3 Connection Policy—CEMF is Master After First Sync

Connection in CEMF	Connection State in CEMF	Connection State in DSLAM	Synchronization Policy Behavior
Present	Normal	Not present	Create in device.
Present	Decommission	Not present	No action needed.
Present	Normal	Present	No action needed.
Present	Decommission	Present	Remove from device.
Not present	—	Present	Remove from device.

Setting the Connection Synchronization Policy

Complete the following steps to set the connection synchronization policy:

Step 1 On the Map Viewer window, within the Physical view, click the chassis object whose connection policy you want to set to access the object menu.

Step 2 Choose Cisco DSL Manager > Chassis > Administration > Chassis Polling/Connection Policy.

The Chassis Polling/Connection Policy window opens. (See Figure 4-5.)

Figure 4-5 Chassis Polling/Connection Policy Window

Step 3 In the Connection Policy area, use the down arrow in the Connection Synchronization Policy field to set the policy from one of the following choices:

Normal—No action. The DSLAM is master, but do not add a connection to or delete a connection from CDM.
DeviceisMaster—This setting specifies that the DSLAM (device) is the reference point for PVC creations and deletions. CDM will sync up to the device. If a connection is present on the DSLAM but not in CDM, CDM will create the connection. If a connection is absent on the DSLAM but present in CDM, CDM will delete the connection.
EMIsMasterAfterFirstSync—The default. This setting specifies that the element manager, that is, CDM, is the reference point for PVC creations and deletions. The device syncs up to CDM for information about PVC settings. If the connection is present in CDM but not the DSLAM, CDM creates the connection in the DSLAM. If the connection is absent in CDM but present in the DSLAM, CDM deletes the connection from the DSLAM.

Step 4 Click the Save icon in the toolbar to save this setting.

Creating ATM QoS Profiles

This section includes the following topics:

The Cisco DSLAM contains default ATM QoS profiles. ATM QoS profiles are also known as ATM traffic descriptors. You can create and save ATM QoS profiles in the QoS Profiles window. CDM stores ATM QoS profiles and creates the parameters on the device when CDM creates the PVC or SPVC.

Note After you create an ATM QoS profile, you can only edit that profile if it is not applied to a port. If a profile has been applied to a specific port, CDM prevents you from altering the profile. You can view the ports that are using a certain profile by running a Cisco EMF query against the profile name. (Refer to the Cisco Element Management Framework User Guide for details.)

Opening the ATM QoS Profiles Configuration Window

To create an ATM QoS profile, first open the ATM QoS Profiles Configuration window:

Step 1 From the left side of the Map Viewer window, within any view, right-click the chassis object for which you want to create an ATM QoS profile.

Step 2 Choose Cisco DSL Manager > Chassis > Profile Management > ATM QoS Profiles from the object menu.

The ATM QoS Profiles Configuration window opens. (See Figure 4-6.)

Figure 4-6 ATM QoS Profiles Configuration Window—Profile Tab

The ATM QoS Profiles Configuration window contains two tabs—Profile and RxTx Parameters. The ATM QoS Profiles Configuration window opens to the Profile tab. The RxTx Parameters tab, which is shown in Figure 4-7, contains the receive and transmit parameters for the selected ATM QoS profile.

Figure 4-7 ATM QoS Profiles Configuration Window—RxTx Parameters Tab

Creating an ATM QoS Profile

Complete the following steps to create a new ATM QoS profile in the ATM QoS Profiles window:

Step 1 Select the profile that you want to use as a template from the list box in the left side of the window.

Step 2 Click Create Profile.

Step 3 Enter the new profile name in the Prompt dialog box, and then click OK.

Step 4 Enter the appropriate information in the required fields in the Profile tab as follows:

a. In the Profile Type field, enter the type of profile that you are creating, for example, ATM QoS profile.

b. In the Profile Descriptions field, enter a description for this profile.

Use the horizontal and vertical scroll bars to navigate.

Step 5 Click the RxTx Parameters tab, and enter the parameters that you want to set in this tab in either the Receive Parameters area or the Transmit Parameters area:

a. Use the down arrow to select from the choices in the QoS Category field, which indicates the current QoS category of the selected profile—either SCR0 or SCR10.

The type of CLP (cell loss priority) that you choose causes certain fields in the Receive Parameters and Transmit Parameters areas to become dimmed. Only those parameters that are valid for the type of CLP you choose are editable.

b. Enter a value in the CLP field, which indicates the value in the ATM cell header that determines the probability of the network dropping a cell if the network becomes congested.

Valid parameter choices include:

Parameter	Choices
ABR¹	pcr², mcr³, cdvt⁴
CBR⁵	pcr, cdvt
UBR⁶	pcr, mcr, cdvt
VBR-RT⁷	scr⁸, pcr, mbs⁹, cdvt
VBR-NRT¹⁰	scr, pcr, mbs, cdvt

1ABR = available bit rate

2PCR = peak cell rate

3MCR = maximum cell rate

4CDVT = cell delay variation tolerance

5CBR = constant bit rate

6UBR = unspecified bit rate

7VBR-RT = variable bit rate real time

8SCR = sustained cell rate

9MBS = maximum burst size

10VBR-NRT = variable bit rate not real time

Cells that have 0 (zero) in the CLP field have ensured priority and are unlikely to be dropped. Cells with 1 in the CLP field have best-effort priority and might be dropped during periods of congestion so that resources are free to handle ensured traffic.

c. Enter a value in the SCR field to specify the maximum sustained-cell-rate (scr) traffic parameter in cells per second that is allowed for connections.

d. Enter a value in the PCR field to specify the maximum transmission rate of cells in cells per second.

e. Enter a value in the MCR field to specify the lowest acceptable transmission rate for connections in cells per second.

f. Enter a value in the MBCS field to specify the maximum burst cell size permitted for cells received for connections on this interface in cell times.

g. Enter a value in the CDVT field to specify the estimated cell delay variation experienced by cells for connections received on this interface in cell times.

Step 6 Click Save to save your changes.

Deleting an ATM QoS Profile

To delete an existing ATM QoS profile, complete the following steps in the ATM QoS Profiles Configuration window:

Step 1 Right-click the profile name you want to delete in the list box.

Step 2 Choose Deployment > Delete Objects.

The Deployment Wizard Summary window opens.

Step 3 Click Finish to delete the selected object.

A message displays to confirm successful deletion.

Note You cannot delete a profile that is currently in use. To view the ports that use a specific profile, you can run a Cisco EMF query against the profile name (refer to the Cisco Element Management Framework User Guide for details.)

Creating PVCs and SPVCs

This section includes the following topics:

A PVC is a permanent virtual connection that must be configured from source to destination. PVCs save bandwidth that is associated with establishing a channel when a virtual channel must exist all the time. You can deploy a PVC or SPVC (which creates the PVC/SPVC within Cisco EMF), apply a QoS profile (ATM traffic descriptor) to the PVC or SPVC, and then create the connection on the device. Deploying and creating a PVC creates a cross connection within one device; deploying and creating an SPVC creates a connection between the incoming port on one device and the outgoing port on another device.

Note After you create a PVC or an SPVC, you can only view the channel within the Component Managed view. The channel does not appear in the other Map Viewer Element Manager views.

Guidelines for Configuring ATM Virtual Channels

Service provisioning for ATM must adhere to a variety of configuration standards, which prevent errors when establishing ATM connections. CDM includes service provisioning logic to ensure valid combinations of configuration data.

Consider the following guidelines before you configure ATM virtual channels:

You can provision more than one permanent virtual connection (PVC) for each subscriber.
Each PVC contains both a network-side and a subscriber-side virtual channel link (VCL).
Each VCC has both a VPI and a VCI.
VPC switching is not supported in this release.
If you enter VCI numbers, you must also enter VPI numbers.

Creating PVCs and SPVCs Overview

You can create PVCs or SPVCs to specify an ATM connection. You can choose from the following types of ATM connections in the Deployment Wizard—Templates window:

PVC and virtual channel link (VCL) under ATM switch
PVC and VCL under ATM switch using trunk port
SPVC with Cisco EMF endpoint
SPVC with non-Cisco EMF endpoint

Creating ATM PVCs

Complete the following steps to deploy an ATM PVC and VCL under an ATM switch or under an ATM switch using a trunk port:

Step 1 From the Component Managed view, right-click over the interface for which you want to deploy an ATM PVC and VCL connection to access the object menu.

Step 2 Choose Deployment > Deploy ATM Connection > PVC.

The Deployment Wizard—Templates window opens. (See Figure 4-8.)

Figure 4-8 Deployment Wizard—Templates Window

Step 3 Click either Template for CiscoPVC and CiscoVCLs under ATM Switch or Template for CiscoPVC and CiscoVCLs under ATM Switch using Trunk Port to highlight your choice, and then click Forward.

The Deployment Wizard—Object Parameters window opens. (See Figure 4-9.)

Figure 4-9 Deployment Wizard—Object Parameters Window

Tip You can use the Tab key to move from one field to the next.

Step 4 Enter the appropriate information in the Object Parameters fields as follows:

a. Enter the number of SPVC objects that you want to deploy from 1 to 100 in the Number of ciscoSPVC objects field.

The number that you enter into this field deploys that number of PVCs on the designated interface.

b. Enter the name you want to give the PVC in the PVC name field; make sure this name in unique.

c. Enter the QoS profile name for the PVC you are deploying in the Profile Name field.

To view a list of the ATM QoS profiles, open the ATM QoS Profiles Configuration window by choosing Cisco DSL Manager > Chassis > Profile Management > ATM QoS Profiles from the object menu.

d. Enter the subscriber ID in the Subscriber ID field, or you can leave this value undefined.

e. Enter the number of the subscriber-side VPI in the Source VPI field.

f. Enter the number of the subscriber-side VCI in the Source VCI field.

g. Enter the number of the network-side VPI in the Destination VPI field.

h. Enter the number of the network-side VCI in the Destination VCI field.

If you set the values in the VPI and VCI fields, you must disable auto allocation. If you want to enable auto allocation, leave the VPI and VCI fields blank.

i. Leave the default, 0, to disable auto allocation or enter 1 to enable autoallocation in the Auto Allocate Source field.

Your choice depends on whether you want CDM to automatically allocate the VPIs and VCIs.

j. Click Forward to continue.

The next Deployment Wizard—Object Parameters window opens. (See Figure 4-10).

Figure 4-10 Deployment Wizard—Object Parameters Window

Step 5 Enter 0 for disable or 1 for enable in the Auto Allocate Destination field to specify whether you want CDM to autoallocate the destination address.

Step 6 Enter 1 for yes in the Create connection field to specify that you want CDM to create the connection.

Step 7 Click Forward to continue.

The Deployment Wizard—Views window opens. If you are deploying an ATM Connection PVC under ATM Switch, this window has two Component Managed fields. Each has a Select button next to it. If you are deploying an ATM Connection PVC under ATM switch using Trunk Port, this window has one Component Managed field with a Select button next to it.

Step 8 Click Select to open the Object Selector window opens. (See Figure 4-11.)

Figure 4-11 Object Selector Window

Step 9 Click + next to the objects that are listed to drill down to the source interface that you want to select for this PVC, then click Apply.

The Deployment Wizard—Views window opens again and displays the interface that you selected from the Object Selector window. You selection populates both fields.

Note If you are deploying PVCs and VCLs under ATM and not using a trunk port, you must use a different selection for your outgoing port.

Step 10 Repeat Step 8 and Step 9 if the window displays a second Component Managed field to specify an outgoing port.

Note Skip Step 10 if you select the Template for Cisco PVC and Cisco VCLS under ATM Switch using Trunk Port. If you use this template, CDM automatically selects the trunk port for the network end of the PVC.

The Deployment Wizard—Views window displays the interfaces that you have selected. An example is shown in Figure 4-12.

Figure 4-12 Example Deployment Wizard—Views Window

Step 11 Click Forward to continue.

The Deployment Wizard—Summary window, which is shown in Figure 4-14, opens to inform you that the deployment process is ready and summarizes the deployment that you have selected.

Figure 4-13 Deployment Wizard—Summary Window

The Deployment Wizard—Results window, which is shown in Figure 4-14, opens and displays the results of the deployment.

Figure 4-14 Deployment Wizard—Results Window

Step 12 Click Finish to complete the deployment.

The Deployment Wizard—Summary window, which is shown in Figure 4-14, summarizes your deployment. In this example, the software failed to apply the profile. When you create a PVC or SPVC, the software creates two virtual channel links (VCLs) that represent the two incoming and outgoing endpoints.

You need to verify that CDM completed the following three tasks:

Created the PVC
Applied to the ATM QoS profile
Completed the connection

If CDM failed to complete any of these tasks, you must manually create the connection. See the "Creating PVCs and SPVCs" section, "Applying an ATM QoS Profile to a PVC or SPVC" section, and the "Manually Uploading ATM QoS Profiles" section for the related instructions.

Deploying ATM SPVCs with a Cisco EMF Endpoint

To deploy SPVCs with a Cisco EMF endpoint, complete the steps that follow. When you deploy an SPVC for which the endpoint is a network service that is not under the management of Cisco EMF (non-CEMF endpoint), you deploy the SPVC in a different way.

Note To create an SPVC that has a non-Cisco EMF endpoint, see the "Deploying an ATM SPVC with a non-Cisco EMF Endpoint" section.

Step 1 From the left side of the Map Viewer window, right-click the chassis object for which you want to create a PVC or SPVC.

Step 2 Choose Deployment > Deploy ATM Connection > SPVC from the object menu.

The Deployment Wizard—Templates window opens. An example of this window is shown in Figure 4-15.

Figure 4-15 Deployment Wizard—Templates Window for Deploying an ATM SPVC

Step 3 Click Template for Cisco SPVC with CEMF end point.

The Deployment Wizard—Object Parameters window opens. (See Figure 4-16.)

Figure 4-16 Deployment Wizard—Object Parameters Window ATM SPVC with a CEMF Endpoint

Tip You can use the Tab key to move from one field to the next.

Step 4 Enter the appropriate choices as follows:

a. Enter 1 in the number of SPVC objects that you want to deploy in the Number of ciscoSPVC objects field.

b. Enter the SPVC name in the SPVC name field; make sure that the name you choose is unique.

c. Enter the name of the profile that you want to use in the Profile field, or use the default by leaving Default in this field.

d. Enter the subscriber ID in the Subscriber ID field, or leave this value undefined.

e. Enter the subscriber-side VPI in the Source VPI field.

f. Enter the subscriber-side VC in the Source VCI field.

g. Enter the network-side VPI in the Destination VPI field.

h. Enter the network-side VCI in the Destination VCI field.

If you set the values in the VPI and VCI fields, you must disable auto allocation. If you want to enable auto allocation, leave the VPI and VCI fields blank.

i. Enter a 0 to disable autoallocation or 1 to enable autoallocation in the Auto Allocate Source field depending on whether you want CDM to automatically allocate the VPIs and VCIs.

j. Click Forward to continue.

The next Deployment Wizard—Object Parameters window opens. (See Figure 4-17.)

Figure 4-17 Deployment Wizard—Object Parameters Window

Step 5 Enter 0 for disable or 1 for enable in the Auto Allocate Destination field to specify whether you want CDM to autoallocate the destination address.

Step 6 Enter 1 for yes in the Create connection field to specify that you want CDM to create the connection.

Step 7 Click Forward to continue.

The Deployment Wizard—Views window opens. This window has two Component Managed fields. Each has a Select button next to it.

Step 8 Click Select to open the Object Selector window opens. (See Figure 4-18.)

Figure 4-18 Object Selector Window

Step 9 Click + next to the objects that are listed to drill down to the interface that you want to select for this PVC, then click Apply.

The Deployment Wizard—Views window opens again and displays the interface that you selected from the Object Selector window.

Step 10 Repeat Step 8 and Step 9 if the window displays a second Component Managed field and consider the following guidelines:

a. If the port is a CEMF endpoint, you must select an NI-2 port from another DSLAM.

b. If the port is a non-CEMF endpoint, you must select another network address.

Note If you do not select the correct ports in the Object Selector window, your SPVC deployment fails.

The Deployment Wizard—Views window displays the interfaces that you have selected. An example of this window is shown in Figure 4-19.

Figure 4-19 Example of a Deployment Wizard—Views Window

Step 11 Click Forward to continue.

The Deployment Wizard—Summary window, which is shown in Figure 4-20, opens and displays the deployment action that is to take place.

Figure 4-20 Deployment Wizard—Summary Window

Step 12 Click Finish to complete the deployment.

The Deployment Wizard—Results window opens. (See Figure 4-21.)

Figure 4-21 Deployment Wizard—Results Window

The Deployment Wizard—Summary window, which is shown in Figure 4-20, summarizes your deployment. In this example, the software failed to apply the profile. When you create a PVC or SPVC, the software also creates two virtual channel links (VCLs) that represent the two incoming and outgoing endpoints.

You can configure and view status and performance for these VCLs. The procedure for doing this is described in the "Managing VCLs" section.

Deploying an ATM SPVC with a non-Cisco EMF Endpoint

To deploy an SPVC for which the endpoint is a network service that is not under the management of Cisco EMF, complete the following steps:

Step 1 From the left side of the Map Viewer window, within the Component Managed view, right-click the chassis object for which you want to create a non-CEMF SPVC.

Step 2 Choose Deployment > Deploy ATM Connection > SPVC from the object menu.

The Deployment Wizard—Templates window opens. (See Figure 4-22.)

Figure 4-22 Deployment Wizard—Templates Window for Deploying an ATM SPVC

Step 3 Click Template for Cisco SPVC with nonCEMF end point.

The Deployment Wizard—Object Parameters window opens. (See Figure 4-23.)

Figure 4-23 Deployment Wizard—Object Parameters Window ATM SPVC with non-CEMF Endpoint

Tip You can use the Tab key to move from one field to the next.

Step 4 Enter the appropriate choices:

a. Enter the number of SPVC objects that you want to deploy from 1 to 100 in the Number of ciscoSPVC objects field.

If you enter 8, for example, in the Number of ciscoSPVC objects field, CDM deploys 8 SPVCs on that interface.

b. Enter the SPVC name in the SPVC name field; make sure that the name you choose is unique (not used by another SPVC).

c. Enter the subscriber ID in the Subscriber ID field or leave this value undefined.

d. Enter the destination network service access point (NSAP) address in the Destination NSAP address field.

If the non-CEMF endpoint runs Cisco IOS, you can obtain the destination NSAP address by using the show atm address command. This command displays a list of all of the ATM interfaces on a chassis and their NSAP addresses. Select the NSAP address from the network interface that you want to specify. For example, ATM 0/2.

e. Enter the name of the profile that you want to use in the Profile field, or use the default by leaving Default in this field.

f. Enter the subscriber-side VPI in the Source VPI field.

g. Enter the subscriber-side VC in the Source VCI field.

h. Enter the network-side VPI in the Destination VPI field.

i. Enter the network-side VCI in the Destination VCI field.

If you set the values in the VPI and VCI fields, you must disable auto allocation. If you want to enable auto allocation, leave the VPI and VCI fields blank.

j. Enter a 0 to disable autoallocation or 1 to enable autoallocation in the Auto Allocate Source field depending on whether you want CDM to automatically allocate the VPIs and VCIs.

k. Enter 1 for yes in the Create connection field to specify that you want CDM to create the connection.

l. Click Forward to continue.

The next Deployment Wizard—Object Parameters window opens. (See Figure 4-24.)

Figure 4-24 Deployment Wizard—Object Parameters Window

Step 5 Leave the setting as 0 for disable in the Auto Allocate Destination field.

Step 6 Enter 1 for yes in the Create connection field to specify that you want CDM to create the connection.

Step 7 Click Forward to continue.

The Deployment Wizard—Views window opens. This window has two Component Managed fields. Each has a Select button next to it.

Step 8 Click Select to open the Object Selector window opens. (See Figure 4-25.)

Figure 4-25 Object Selector Window

Step 9 Click + next to the objects that are listed to drill down to the interface that you want to select for this PVC, then click Apply.

The Deployment Wizard—Views window opens again and displays the interface that you selected from the Object Selector window.

Step 10 Repeat Step 8 and Step 9 if the window displays a second Component Managed field and consider the following guidelines:

a. If the port is a CEMF endpoint, you must select an NI-2 port from another DSLAM.

b. If the port is a non-CEMF endpoint, you must select another network address.

Note If you do not select the correct ports in the Object Selector window, your SPVC deployment fails.

The Deployment Wizard—Views window displays the interfaces that you have selected. An example of this window is shown in Figure 4-26.

Figure 4-26 Example of the Deployment Wizard—Views Window

Step 11 Click Forward to continue.

The Deployment Wizard—Summary window opens and displays the deployment action that is to take place. (See Figure 4-20.)

Figure 4-27 Deployment Wizard—Summary Window

Step 12 Click Finish to complete the deployment.

The Deployment Wizard—Results window opens and indicates whether the deployment was successful. (See Figure 4-28.)

Figure 4-28 Deployment Wizard—Results Window

The Deployment Wizard—Summary window (see Figure 4-20) summarizes your deployment. In this example, the software failed to apply the profile. When you create a PVC or SPVC, the software also creates two virtual channel links (VCLs) that represent the two incoming and outgoing endpoints.

Note The number of objects that you enter in the Number of ciscoSPVC objects fields, is reflected on the left side of the Map Viewer window. For example, if you enter 8 in this field, 8 VCLs display below that interface. This example is shown in Figure 4-29.

Figure 4-29 Example of Deploying Multiple SPVC Objects

You can configure and view status and performance for these VCLs, which is described in the "Managing VCLs" section.

Note Deploying an ATM PVC or SPVC does not create the connection on the device. To create the actual connections, you must use the ATM QoS Profiles Management window and the ATM Connections Management window.

Applying an ATM QoS Profile to a PVC or SPVC

When you create a PVC or SPVC, you can specify the ATM QoS profile for that connection at deployment. When the DSLAM is synchronized, these connections and profiles are automatically uploaded.

However, if for some reason the deployment is not completely successful, you can manually apply the ATM QoS profile to the PVC or SPVC. To apply an ATM QoS profile, complete the following steps:

Step 1 From the left side of the Map Viewer window, within the Component Managed view, right-click the chassis object to which you want to apply an ATM QoS profile.

Step 2 Choose Cisco DSL Manager > Connection > Configuration > ATM from the object menu.

The ATM Connection QoS Configuration window opens to the Profile tab opens. (See Figure 4-30.)

Figure 4-30 ATM Connection QoS Configuration Window—Profile Tab

Step 3 From the list box on the left side of the window, select the related chassis, card, interface, and connection (PVC or SPVC).

This connection should be the PVC or SPVC to which you want to apply the ATM QoS profile. Any current ATM QoS profile that is applied to the selected PVC or SPVC displays on the right side of the window.

Step 4 From the menu bar, choose Edit > Apply Profile.

A list of ATM QoS profiles displays to the right of the menu.

Step 5 Select the ATM QoS profile that you want to apply from the list.

After you apply the profile, a status line displays briefly in the lower left corner of the window that indicates whether CDM successfully applied the profile. The information for the selected new profile displays on the right side of the window.

Activating the PVC or SPVC Connection

The instructions in this section are necessary only if a failure occurred when you deployed the PVC or SPVC. If a failure occurred after you created a PVC or SPVC in CDM and applied an ATM QoS profile to the PVC or SPVC, you can connect the PVC or SPVC on the device to activate the connection. Complete these steps to activate the connection:

Step 1 From the left side of the Map Viewer window, within the Component Managed view, right-click the chassis object for which you want to activate the PVC or SPVC connection.

Step 2 Choose Cisco DSL Manager > Connection > Connection Management > ATM from the object menu.

The ATM Connections Management window opens to the Configuration tab. (See Figure 4-31.)

Figure 4-31 ATM Connections Management Window

Step 3 From the left side of the window, select the related chassis, card, interface, and connection that you want to create.

Step 4 On the Configuration tab, enter the desired information in the Subscriber Info, Source, and Destination areas.

See Table 4-4 for descriptions of the fields in this tab.

Note If you are creating an SPVC, the NSAP Address for the outgoing port also displays.

Step 5 Click Connect in the Action area.

You are prompted to confirm this action. Clicking the Connect button instructs CDM to create the subscriber connection on the device. The connection object changes to the Normal state.

Step 6 If you want to disconnect the subscriber connection, click Disconnect.

In the second Actions area, you can click the Decommission button, which suspends management of the connection. When you decommission a connection, alarms are no longer reported against this connection and performance polling is no longer performed on the connection.

Table 4-4 contains information about the parameters in the Subscriber Info, Source, and Destination areas of the Configuration Tab.

Table 4-4 ATM Connections Management—Configuration Tab Parameter Definitions

Parameter	Definition
Subscriber Info
Subscriber ID	Enter the subscriber ID.
Source
Source VPI	Enter the VPI value of the source VCL. For Cisco CPEs this value can be 1. For CPEs that are non-Cisco and for SPVCs, this value can be 32 to 4000. For PVCs, this value can be 0 to 355.
Source VCI	Enter the VCI value of the source VCL. For Cisco CPEs, this value can be 0 to 3. For CPEs that are non-Cisco and for SPVCs, it can be 1 to 1000. For PVCs, this value can be 32 to 16383.
Auto Allocation	Use the down arrow to select enable or disable. The source VPI and source VCI values are provided automatically if you click the Source Port and Source VCL buttons. The Source Port button displays the ATM Configuration window for the selected PVC or SPVC. The Source VCL button displays the VCL Configuration window for the selected PVC or SPVC. These buttons allow you to view or perform more detailed configuration on both VCLs.
Destination
Destination VPI/Destination VCI	VPI and VCI values of the destination VCL. If you set the VPI value to 0 or 2 to 27, VCI can be 0 to 399. If you set the VPI value to 1, VCI can be 1 to 1599.
Auto Allocation	The source VPI and source VCI values are provided automatically if you select the Auto Allocation button on each side (Source and Destination.)
NSAP Address	The ATM address that you must provide if you are configuring an SPVC with a non CEMF endpoint. When your configuration includes a subtended chassis, you must provide the NSAP address for the destination ATM end point of the connection. Note This field is only applicable to SPVCs, not PVCs. Clicking the Destination Port button displays the ATM Configuration window for the selected PVC or SPVC. Clicking the Destination VCL button displays the VCL Configuration window for the selected PVC or SPVC. Clicking these buttons allows you to view and perform more detailed configuration on both VCLs. See the "Managing VCLs" section for more information about configuring VCLs.

Managing VCLs

This section includes the following topics:

When you create an ATM connection (PVC or SPVC), CDM automatically creates two Virtual Channel Links (VCLs). One VCL represents the source or incoming port, and the other VCL represents the destination or outgoing port. You can view or modify the configuration, performance, and status of VCLs through the VCL Management window.

Configuring a VCL

This section includes instructions for configuring an ATM VCL through the ATM VCL Configuration window and setting up Layer 3 configuration parameters in the ATM VCL Configuration window Layer 3 Configuration tab.

Using the ATM VCL Configuration Window—Configuration Tab

To configure an ATM VCL, open the VCL Management window as follows:

Step 1 In the Map Viewer window, within the Component Managed view, right-click the interface that has a PVC already created and for which you want to configure a VCL.

Step 2 Choose Cisco DSL Manager> Connection > VCL Management > Config from the object menu.

The ATM VCL Configuration window opens. (See Figure 4-32.)

Figure 4-32 ATM VCL Configuration Window—Configuration Tab

Step 3 Select a VCL from the list box on the left side of the window.

The Configuration tab contains four areas:

VPI/VCI
Traffic Information
Encapsulation Parameters
OAM Information

Configure the values for the VCL that you have selected in Step 5.

Step 4 The VPI/VCI area contains the following information (read only):

a. In the VPI field, VPI values display for either the source VCL or the destination VCL, depending upon the type of VCL that you select.

b. In the VCI field, the VCI values display for either the source VCL or the destination VCL, depending upon the type of VCL that you select.

Step 5 In the Traffic Information area, enter the following information:

a. In the UPC Mode field, use the down arrow to select pass, tag, drop, or local shaping for the Usage Parameter Control Mode on the established connection.

b. In the EPD Mode field, use the down arrow to select enable or disable, to enable or disable early packet discard at this specific connection.

Step 6 In the Encapsulation Parameters area, determine whether to set the following fields:

a. If the Encapsulation Flag is set to aal5Mux, use the down arrow in the Encapsulation Protocol field to specify the Protocol for the terminating VC; if the Encapsulation Flag is not set to aal5Mux, you do not need to set this parameter.

Valid choices include the following parameters:

other
ip
xns
appletalk
clns
decnet
novell
apollo
vines

b. In the Encapsulation Flag field, use the down arrow to specify the encapsulation type for the terminating VC.

Valid choices include the following parameters. ATM Adaptation Layer 5 (AAL5) segments and reassembles data units up to 65,535 octets into ATM cell payloads. AAL5 is suited for variable bit rate traffic such as TCP/IP and signalling.

aal5Snap—AAL5 subnetwork access protocol
aal5Nlpid—AAL5 network layer protocol ID
aal5FrNlpid—AAL5 frame relay network layer protocol ID (not used)
aal5Mux—AAL5 multiprotocol over ATM
aal34Smds—AAL3/4 switched multimegabit data service
aalQsAal—Signalling AAL
aal5Ilmi—AAL5 integrated local management interface
aal5Lane—AAL5 LAN emulation
aal5Pnni—AAL5 private network to network interface

c. If the Encapsulation flag field is set to aal5Lane, use the down arrow to set the AAL User Type parameter; if the Encapsulation Flag is not set to aal5Lane, you do not need to set this parameter.

Valid options include the following parameters:

other
boxConfigure—Shared Server/Client end of a Configure VCC
busForward—BUS end of the Data Forward VCC
busSend—BUS end of the Data Send VCC
clientConfigure—LE Client end of the Configure Direct VCC
clientData—One end of the Data Direct VCC
clientDirect—LE Client end of the Control Direct VCC
clientDistribute—LE Client end of the Control Distribute VCC
clientForward—LE Client end of the Multicast Forward VCC
clientSend—LE Client end of the Multicast Send VCC
configure—Config Server end of any Configure VCC
serverConfigure—LE Server end of the Configure VCC
serverDirect—LE Server end of the Control Direct VCC
serverDistribute—LE Server end of the Control Distribute VCC

Step 7 In the operation, administration, and maintenance (OAM) cell Information area, enter the following information:

a. In the AIS Mode field, use the down arrow to select enable or disable.

This field enables or disables the Enable Alarm Indication Signal OAM cell generation if the interface fails when cross-connecting virtual channel.

b. In the RDI Mode field, use the down arrow to select enable or disable.

This fields enables or disables the Enable Remote Defect Indication (RDI) OAM cell generation. In ATM, if the physical layer detects loss of signal or cell synchronization, RDI cells report a VPC/VCC failure. RDI cells are sent upstream by a VPC/VCC end point to notify the source VPC/VCC end point of the downstream failure.

Step 8 Click Save in the toolbar to save your configuration settings.

The configuration information for the selected VCL displays on the right side of the window. You can view or modify this information.

Description of the ATM VCL Configuration Window—Configuration Tab

Table 4-5 describes the fields in the ATM VCL Configuration Window Configuration tab.

Table 4-5 ATM VCL Configuration Window—Configuration Tab Field Definitions

Field	Definition
VPI/VCI
VPI	Displays the VPI for the selected interface.
VCI	Displays the VCI for the selected interface.
Traffic Information
UPC¹ Mode	Use the down arrow to select from the following choices. This field specifies cell traffic handling based on the guaranteed quality of service for a subscriber: passing—Allows the cell to pass through tagging—Tags the cell and allows it to go through; because the cell is tagged, it could get dropped later if the network is congested. dropping—Drops the cell. local shaping
EPD² Mode	Use the down arrow to enable or disable this mode.
Encapsulation Parameters
Encapsulation Protocol	Use the down arrow to specify the protocol if the encapsulation flag parameter is set to aal5Mux from the following choices: other ip xns appletalk clns decnet novell apollo vines
Encapsulation Flag	Use the down arrow to set the encapsulation flag from the following choices: aal5Snap—AAL5 subnetwork access protocol aal5Nlpid—AAL5 network layer protocol ID aal5FrNlpid—(not used) aal5Mux—AAL5 multiprotocol over ATM aal34Smds—AAL3/4 switched multimegabit data service aalQsAal—Signalling AAL aal5Ilmi—AAL5 integrated local management interface aal5Lane—AAL5 LAN emulation aal5Pnni—AAL5 private network to network interface
AAL³ User Type	Use the down arrow to set the AAL user type parameter if the encapsulation flag is set to aal5Lane from the following choices: other boxConfigure—Shared Server/Client end of a Configure VCC busForward—BUS⁴ end of the Data Forward VCC busSend—BUS end of the Data Send VCC clientConfigure—LE⁵ Client end of the Configure Direct VCC clientData—One end of the Data Direct VCC clientDirect—LE Client end of the Control Direct VCC clientDistribute—LE Client end of the Control Distribute VCC clientForward—LE Client end of the Multicast Forward VCC clientSend—LE Client end of the Multicast Send VCC configure—Config Server end of any Configure VCC serverConfigure—LE Server end of the Configure VCC serverDirect—LE Server end of the Control Direct VCC serverDistribute—LE Server end of the Control Distribute VCC
OAM Information
AIS⁶ Mode	Use the down arrow to select enable or disable.
RDI⁷ Mode	Use the down arrow to select enable or disable.

1UPC = usage parameter control

2EPD = early packet discard

3AAL = ATM adaptation layer

4BUS = broadcast and unknown server

5LE = LAN emulation

6AIS = alarm indication signal

7RDI = remote defect indication

Description of the ATM VCL Configuration Management Window—Layer 3 Configuration Tab

The Layer 3 Configuration tab is not used in CDM.

Viewing ATM VCL Performance

You can start performance logging for a selected connection to gather performance data for that connection in the VCL Performance window. You can view this performance data by using the Performance menu or in the Performance Manager window.

Complete the following steps to view ATM VCL performance:

Step 1 From the left side of the Map Viewer window, within the Component Managed view, right-click the chassis object whose VCL performance you want to monitor.

Step 2 Choose Cisco DSL Manager > Connection > VCL Management > Performance from the object menu.

The ATM VCL Performance window opens to the Performance tab. (See Figure 4-33.)

Figure 4-33 ATM VCL Performance Window

The chassis and module name that you selected are highlighted on the left.

Step 3 Click Start to begin performance polling on the selected VCL.

Step 4 Click Yes in the Yes/No dialog box to start performance polling.

The Action Report window opens and displays the status of this action. When polling is complete, the ATM VCL performance data for this chassis and module displays on the right side of the window.

The Performance tab contains three areas:

Bandwidth Utilization
VC Statistics
Performance Monitoring

The fields in this tab are described in Table 4-6.

Table 4-6 ATM VCL Performance Window—Performance Tab Field Descriptions

Field	Description
Bandwidth Utilization
Receive	Not used.
Transmit	Not used.
VC Statistics
In Cells	Displays the total number of cells received on this VCL.
Out Cells	Displays the total number of cells transmitted on this VCL.
UPC¹ Violations	Displays the total number of UPC Violations on this VCL.
Packets In	Displays the total number of packets received on this VCL.
Cell Drops	Displays the total number of cells dropped on this VCL.
Packet Drops	Displays the total number of packets dropped on this VCL.
Performance Monitoring
Start and Stop	Click the Start button to initiate performance monitoring on the selected VCL; click the Stop button to end performance monitoring. Performance monitoring collects and displays data on the object, either in the Performance windows or the Performance Manager. See "Viewing Performance Data," for more information about monitoring performance.

1UPC = usage parameter control

Viewing VCL Status

To view VCL status, follow these steps:

Step 1 From the left side of the Map Viewer window, within the Component Managed view, right-click the line card interface whose VCL status you want to view.

Step 2 Choose Cisco DSL Manager > Connection > VCL Management > Status from the object menu.

The ATM VCL Status window opens to the Status tab. (See Figure 4-34.)

Figure 4-34 ATM VCL Status Window

Step 3 The line card you selected is highlighted on the left, or from the list box on the left side of the window, select a VCL.

The status information for the selected VCL displays on the right.

The Status tab contains four areas:

VCL Status
Characteristics
Soft PVC Details
OAM Details

Table 4-7 provides descriptions of the fields in this window.

Table 4-7 ATM VCL Status Window—Status Tab Field Descriptions

Field	Description
VCL Status
Operational State	Displays the status of the VCL connection.
Last Change	Displays the time elapsed since the last status change.
Install Time	Displays the time elapsed since the last installation.
Characteristics
Span Type	Displays the VCL span type.
Connection Type	Displays the virtual connection configuration type.
Cast Type	Displays the virtual connection cast type.
Soft PVC Details
Location	Indicates the calling or called side of a SPVC.
Number of Attempts	Indicates the number of attempts made to install this SPVC.
Last Release Cause	Indicates the cause of the last connection release.
OAM Details
Segment Loopback	Indicates whether the segment loopback is enabled or disabled on the virtual channel selected.
Loopback Interval	Indicates the frequency with which the OAM loopback cells are generated.

Manually Uploading ATM QoS Profiles

CDM automatically synchronizes connection information (that is, PVC and SPVCs) between the DSLAM and CDM. This synchronization process occurs at regular intervals; the default is every 30 minutes. However an operator can manually force an upload of connection information.

When you upload existing ATM connections and ATM QoS profiles, CDM discovers any existing ATM connections and places them into the Normal state. You can then begin automatically managing the subscribers associated with these connections. CDM uploads ATM QoS profiles and PVCs or SPVCs and their associated connection parameters (VPIs and VCIs) to the correct interfaces; you can then view and adjust them in the CDM GUI.

Note CDM uploads PVC and SPVC information based on the connection synchronization policy that you have selected. See the "Polling the Chassis and Setting the Connection Synchronization Policy" section for more information.

If your deployment of PVCs or SPVCs and associated ATM QoS profiles fails, you can upload them manually by completing the following steps:

Step 1 In the Map Viewer window, within the Physical view, right-click a chassis object to access the object menu.

Step 2 Choose Cisco DSL Manager > Connection > Upload Synchronization > ATM. (See Figure 4-35.)

Figure 4-35 Choosing Upload Synchronization from the Object Menu

The ATM Connection Upload window opens. (See Figure 4-36.)

Figure 4-36 ATM Connection Upload Window

The name of the chassis that you selected is highlighted in the list box on the left side of the window.

The names of uploaded ATM connections and ATM QoS profiles are based on the following formats:

ATM connections—PVC_(index of incoming port.VPI value.VCI value.index of outgoing port.
VPI value.VCI value)
ATM QoS profiles—QoSProfile_(assigned number)

Step 3 Click Upload.

All ATM connections and ATM QoS profiles that are currently configured on the selected device are uploaded into CDM. The way you configure the connection synchronization policy determines which PVC and SPVC connections CDM uploads. See the "Polling the Chassis and Setting the Connection Synchronization Policy" section for more information about how to configure the connection synchronization policy.

Using Inverse Multiplexing over ATM on Cisco 6015, 6160, and 6260 DSLAMs

This section is applicable to Cisco 6015, 6160, and 6260 DSLAMs.

You can use inverse multiplexing over ATM (IMA) to join together several slower speed links to create a virtual high-speed link. The following sections include an overview of IMA and how to move IMA links in CDM:

Overview of IMA

IMA provides access to ATM networks by combining the bandwidth of multiple DS1/E1 links into groups that collectively provide higher intermediate rates. In CDM, an IMA group can have up to 4 T1 links, and each link provides 1.544 Mbps.

IMA breaks up the ATM cell stream and distributes the cells over the multiple physical links of an IMA group, and then recombines the cells into a single stream at the other end of the connection. The ATM cells are distributed in a round robin fashion over the physical links of the IMA group, demultiplexed at the receiving IMA group, and passed in their original form to the ATM layer (see Figure 4-37). Using the multiple links of an IMA group increases the logical link bandwidth to approximately the sum of the individual link rates.

IMA requires a minimum of two commissioned chassis. CDM automatically provides four IMA groups to each chassis upon the completion of the commissioning process. You can use these IMA groups to group individual IMA links.

Note If you choose to assign IMA links to IMA groups, each group must be assigned the minimum number of links as configured in IOS. The default value is one link per group.

Figure 4-37 Inverse Multiplexing and Demultiplexing of ATM Cells Through IMA Groups

The T1 and E1 IMA port adapters have eight ports. You can use the eight ports on the T1 and E1 IMA port adapters as independent ATM links or in the IMA mode. Some examples of combinations include:

Four IMA groups
Three IMA groups and one independent ATM link
Two IMA groups and two independent ATM links
One IMA group and three independent ATM links
No IMA group and four independent ATM links

The T1 (1.544 Mbps) and E1 (2.048 Mbps) IMA port adapters provide trunk connectivity and are used for intercampus or wide-area links. The T1 and E1 IMA port adapters support unshielded twisted-pair connectors.

Configuring IMA Groups

To configure IMA groups, complete the following steps:

Step 1 From the left side of the Map Viewer window, from within the Physical or IMA hierarchy view, right-click the NI card icon for the IMA group whose configuration you want to edit.

Step 2 Choose Cisco DSL Manager > Interface > Configuration > IMA Configuration from the object menu.

The IMA Group Configuration window opens. (See Figure 4-38.)

Figure 4-38 IMA Group Configuration Window

The left side list box displays the IMA group whose configuration you want to change.

Step 3 Edit the values in this window as needed.

Note The fields in this window are described in Table 4-8.

This window contains the following four areas:

IMA Group Details
IMA Group Configuration
IMA Links
Test Pattern Control

Table 4-8 IMA Group Configuration Window

Field

Description

IMA Group Details

Symmetry

Displays the results of symmetric mode adjustment during IMA group start up.

Transit IMA ID

Displays the IMA link ID.

ICP¹

Displays the current values for the following fields:

Alpha Value
Beta Value
Gamma Value

IMA Group Configuration

Frame Length

Use the down arrow to select the transmit frame length from one of the following choices:

m32
m64
m128
m256

Clock Mode

Use the down arrow to select the transmit clock mode.

cfc—common transmit clock
itc—independent transmit clock

Minimum no. of Links

Enter the minimum number of transmit and receive links that are required to be active for the IMA group to be in the operational state. Valid choices range from 1 to 32.

IMA Links

Maximum Differential Delay allowed

Enter the maximum number of milliseconds of differential delay among the links that will be tolerated on this interface. The default value is 25.

Test Pattern Control

Test Link ifindex²

Enter the value to designate an interface as the test link for use in the Test Pattern Procedure. The distinguished value of zero specifies that the implementation may choose the Test Link, in which case the implementation may also choose the value of 'imaGroupTestPattern'. The value zero may also be used if no link has yet been added to the group.

Note This value is not the same as the Tx LID³ value, but instead either identifies the ifIndex value of the test link to be used by the Test Pattern Procedure (that is, the link whose LID value is inserted in the Tx LID field of the transmitted ICP cells), or identifies that the implementation may choose the test link (if the value is zero).

The default value for this field is 0.

Test Procedure Status

Use the down arrow to select disabled, operating, or linkFail.

Test Pattern

Enter the test pattern to invoke a test pattern object. Test pattern objects are implemented if the IMA implements the test pattern procedure. In this case, all test pattern procedure-related objects must be implemented. Specifically, these objects include:

imaGroupTestLinkIfIndex
imaGroupTestPattern
imaGroupTestProcStatus
imaLinkRxTestPattern
imaLinkTestProcStatus

1ICP = intelligent cell processing

2ifindex = interface index

3LID = link ID

Table of Contents

Creating Connections and ATM QoS Profiles

Polling the Chassis and Setting the Connection Synchronization Policy

Overview of Chassis Polling

Setting Polling Intervals

Synchronizing Alarms and Saving the Running Configuration

Overview of the Connection Synchronization Policy

Setting the Connection Synchronization Policy

Creating ATM QoS Profiles

Opening the ATM QoS Profiles Configuration Window

Creating an ATM QoS Profile

Deleting an ATM QoS Profile

Creating PVCs and SPVCs

Guidelines for Configuring ATM Virtual Channels

Creating PVCs and SPVCs Overview

Creating ATM PVCs

Deploying ATM SPVCs with a Cisco EMF Endpoint

Deploying an ATM SPVC with a non-Cisco EMF Endpoint

Applying an ATM QoS Profile to a PVC or SPVC

Activating the PVC or SPVC Connection

Managing VCLs

Configuring a VCL

Using the ATM VCL Configuration Window—Configuration Tab

Description of the ATM VCL Configuration Window—Configuration Tab

Description of the ATM VCL Configuration Management Window—Layer 3 Configuration Tab

Viewing ATM VCL Performance

Viewing VCL Status

Manually Uploading ATM QoS Profiles

Using Inverse Multiplexing over ATM on Cisco 6015, 6160, and 6260 DSLAMs

Overview of IMA

Configuring IMA Groups