|
|
This chapter describes how to add subscribers and apply profiles to a subscriber. This chapter also includes information and instructions for setting up subtending configurations.
This chapter includes the following sections:
CDM enables you to perform several types of configurations:
 |
Note ATM QoS profiles are also known as ATM traffic descriptors. |
Adding a subscriber involves creating and applying a profile to a subscriber line; creating and applying a PVC or an SPVC; then configuring two VCLs, which are the end points of your connection (one outgoing port and one incoming port). A "subscriber" in CDM, then, is made up of a subscriber line that has a PVC (or SPVC) with two VCLs at each end.
Step 2 Create a profile.
Step 3 Apply the profile to the subscriber line.
Step 4 Create a PVC or SPVC object.
Step 5 Apply a QoS profile to the PVC or SPVC.
Step 6 Associate the PVC or SPVC with the device.
Step 7 (Optional) Start performance polling on the connection.
Before you can upload any subscribers or profiles, make sure your Telnet passwords are configured in CDM.
To check Telnet passwords:
The Management Information window appears (Figure 4-1).
Step 2 Click the IOS/Command Line Security tab (Figure 4-1).
Step 3 Enter your User Name, Exec Password, and Login Password.
Step 4 Click the Save Locally button to save your passwords locally on the device or chassis.
The ATM Connection Upload window appears (Figure 4-2).
Step 2 The chassis you selected appears at the left. Click Upload. All ATM connections and ATM QoS profiles currently configured on the selected device are uploaded into CDM.
Uploaded ATM connections and ATM QoS profiles are named according to the following formats:
When you upload existing ADSL and DMT profiles, any existing ADSL and DMT profiles are created in CDM. After these profiles are uploaded, you can view and modify them in CDM.
The ADSL or DMT Upload Profile window appears (Figure 4-3).
Step 2 The chassis you selected appears at the left. Click Upload, and all ADSL (or DMT, depending upon which window you are in) profiles currently configured on the selected device are uploaded into CDM.
Uploaded ADSL and DMT profiles are named according to the following formats:
You can create DMT profiles to apply to DMT interfaces. One DMT profile can be applied to multiple DMT interfaces on a card.
|
Note After you create a DMT profile, you can edit that profile only if it is not being used. If any subscribers are using that profile, you are not allowed to alter the profile. You can view and identify the subscribers 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). |
|
Note DMT profiles are saved and stored in CDM. |
To begin creating DMT profiles, open the DMT Interface Profiles window.
The DMT Interface Profile window appears (Figure 4-4).
The DMT Interface Profile window contains only one tab, Profile. The Profile tab contains four areas:
Step 2 Create a profile.
You can create a new profile by typing information in the required fields, or copying the parameters from an existing profile.
Table 4-1 defines the fields that are located in the DMT Interface Profile window.
| Field | Definition |
|---|---|
Profile Type | Enter the type of profile you are creating (in this instance, a DMT interface profile.) |
Profile Description | Enter a description for this profile. Use the horizontal and vertical scroll tools to view text not displayed in the window. |
Bit Swap | Indicates whether or not the ATU-C performs bit swapping. Bit swapping can maximize error performance by attempting to maintain an acceptable margin for each bin by equalizing the margin across all bins through bit reallocation. |
Bit Swap Margin From | The ATU-C marks a bin as a "from" bin if the bin margin falls below a specified target value and the difference between the margin and target exceeds a specified threshold value. Valid values are in the range from 1 through 9. If this value is too low, the ATU-C may toggle the bit allocation on bins frequently. If impulse noise is present, the frequent toggling of bit allocation can cause errors. If this value is too high, the ATU-C may not identify an adequate number of bins from which it can swap bits, which decreases the ability of the ATU-C to equalize the margin across all bins. |
Bit Swap Margin To | The ATU-C marks a bin as a "to" bin if the bin margin exceeds a specified target value and the difference between the margin and target exceeds a specified threshold value. Valid values are in the range 1 through 9. If this value is too low, the ATU-C may toggle bit allocation on bins frequently. If impulse noise is present, the frequent toggling of bit allocation can cause errors. If this value is too high, the ATU-C may not identify an adequate number of bins to which it can swap bits, which decreases the ability of the ATU-C to equalize the margin across all bins. |
Training Mode | Displays the mode employed by the downstream device and upstream device when the devices are training against each other. The devices can employ one of two training modes. The default-training mode for ADSL modems is standard. |
Operating Mode | Displays the line-operating mode that the ADSL line employs. An ADSL line uses of one of two operating modes. |
Trellis Coding | Indicates whether or not trellis coding is used on the DMT line. |
Overhead Framing | Displays the negotiated overhead framing structure being used by the downstream device and upstream device. Possible framing structures are:
|
Check Bytes | |
Codeword Size | Displays the number of symbols per codeword being used by the downstream for downstream messages on an interleaved channel during the training sequence. The downstream can fall back from this value, based on the aggregate data rate achieved during training. |
|
Note You cannot delete a profile that is currently in use. If you want to view the subscribers that are using 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). |
QoS Profile windows allow you to create and save ATM QoS profiles (also known as ATM traffic descriptors). CDM stores ATM QoS profiles, and the parameters are created on the device when the PVC or SPVC on the device.
|
Note After you create an ATM QoS profile, you can only edit that profile if the profile is not being used. If any subscribers are using that profile, you are not allowed to alter the profile. You can view which specific subscribers 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.) |
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:
To open the ATM QoS Profile Configuration window, proceed as follows:
The ATM QoS Profiles Configuration window appears (Figure 4-5).
The ATM QoS Profiles window contains two tabs—Profile and RxTx Parameters. The Profile tab appears by default when you open the ATM QoS Profiles window.
Step 2 Create a profile.
You can create a new profile by typing information in the required fields, or copying the parameters from an existing profile.
Table 4-2 defines the fields that are located in the ATM QoS Profiles Configuration window—Profile tab.
| Field | Description |
|---|---|
Profile Type | Enter the type of profile you are creating (in this instance, an ATM QoS profile.) |
Profile Description | Enter a description for this profile. Use the horizontal and vertical scroll tools to view text not displayed in the window. |
The RxTx Parameters tab contains the receive and transmit parameters for the selected ATM QoS profile as shown in Figure 4-6.
Table 4-3 defines the fields that are located in the RxTx Parameters tab
.
| Field | Definition |
|---|---|
QoS Category | Indicates the current QoS category of the selected profile. |
CLP (cell loss priority) | Indicates the value in the ATM cell header that determines the probability of a cell being dropped if the network becomes congested. Cells that have 0 (zero) in the CLP field have insured 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 insured traffic. |
SCR (sustainable cell rate) | Indicates the maximum sustained-cell-rate (scr) traffic parameter that is allowed for subscribers. |
PCR (peak cell rate) | Indicates the maximum transmission rate of cells. |
MCR (minimum cell rate) | Indicates the lowest acceptable transmission rate (specified in cells per second) for subscribers. |
MBCS (maximum burst cell size) | Indicates the maximum burst cell size permitted for cells received for subscribers on this interface. |
CDVT (cell delay variation tolerance) | Indicates the cell delay variation estimated to be experienced by cells for subscribers received on this interface. |
|
Note You cannot delete a profile that is currently in use. To view the subscribers 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.) |
You can create ADSL profiles to apply to DMT interfaces. One ADSL profile can be applied to multiple DMT interfaces on a card.
|
Note After you create an ADSL profile, you can edit that profile only if it is not being used. If any subscribers are using that profile, you are not allowed to alter the profile. You can view the subscribers 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). |
|
Note ADSL Profiles are saved and stored in CDM. |
To view the ADSL Profiles window, use the following steps:
The ADSL Interface Profile window appears (Figure 4-7).
The ADSL Interface Profile window contains one tab, Profile.
Step 2 Create a profile.
You can create a new profile by typing information in the required fields, or copying the parameters from an existing profile.
Table 4-4 defines the fields that are located in the ADSL Parameters area.
| Field | Definition | ||
|---|---|---|---|
Target Signal/Noise Margin (tenth dB) | This is the noise margin the modem must achieve with a BER of 10-7 or better to successfully complete initialization.
| ||
Interleave Channel Delay (ms) | Interleave delay for this channel. Interleave delay applies only to the interleave channel and defines the mapping (relative spacing) between subsequent input bytes at the interleaver input and their placement in the bit stream at the interleave output. | ||
Interleave Minimum Transmit Rate (bps) | Configured minimum transmit rate for Interleave channels, in bits per second. | ||
Interleave Maximum Transmit Rate (bps) | Configured maximum transmit rate for Interleave channels, in bits per second. |
|
Note You cannot delete a profile that is currently in use. If you want to view the subscribers that are using 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.) |
After you create a DMT profile, you can apply that profile to a DMT interface. One DMT profile can be applied to multiple DMT interfaces on a card.
|
Note DMT profiles are saved and stored in CDM. |
To view the DMT Interface Configuration window, use the following steps:
The DMT Interface Configuration window appears (Figure 4-8).
Step 2 From the list boxes at the left, select the chassis, card, and DMT interface to which you want to apply the DMT Profile. Any current profiles applied to the selected DMT interface appear in the tab at the right.
Step 3 From the toolbar, select Edit >Apply Profile. A list of DMT profiles appear.
Step 4 Click the named DMT profile you want to apply. After you apply the profile, a status line appears briefly in the lower left corner of the window, which indicates whether or not the profile is applied successfully. The information for the selected profile appears in the tab at the right.
After you create an ADSL profile, you can apply that profile to an ADSL (DMT) interface. One ADSL profile can be applied to multiple ADSL (DMT) interfaces on a card.
Four DMT interfaces are created automatically when you deploy a DMT line card. These "DMT" interfaces are actually ATM over ADSL over DMT interfaces. This means that three technologies are supported by one interface.
|
Note ADSL profiles are saved and stored in CDM. |
To view the ADSL Interface Configuration window, use the following steps:
The ADSL Interface Configuration window appears (Figure 4-9).
Step 2 From the list box at the left, select the chassis, card, and ADSL (DMT) interface to which you want to apply the ADSL profile. Any current ADSL profiles applied to the selected DMT interface appear in the tab at the right.
Step 3 From the toolbar, select Edit > Apply Profile. A list of ADSL profiles appear.
Step 4 Click the named ADSL profile you want to apply. After you apply the profile, a status line appears briefly in the lower left corner of the window, which indicates whether or not the profile is applied successfully. The information for the selected new profile appears in the tab at the right.
|
Note The ADSL Interface Configuration tab contains three areas: Profile Details, ADSL Parameters, and Actions. For detailed information about these fields, refer to the "Creating an ADSL Profile" section . |
A PVC is a permanent logical connection that must be configured from source to destination. PVCs save bandwidth associated with establishing a circuit when a virtual circuit must exist all the time. You can deploy a PVC or SPVC (which creates the PVC/SPVC within Cisco EMF), apply an ATM traffic descriptor to the PVC or SPVC, 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, the circuit can be viewed only within the Component Managed view. The circuit does not appear in the CDM Manager view. |
To view the Deployment Wizard window:
The Deployment Wizard—Object Parameters window appears (Figure 4-10).
Step 2 Enter the number of PVCs or SPVCs you wish to create. Click Forward.
The Deployment Wizard—Object Parameters window appears (Figure 4-11).
Step 3 Enter the PVC name. Ensure this name is unique. Enter your subscriber ID if desired, or you can leave the value undefined. Click Forward.
The Deployment Wizard—Views window appears (Figure 4-12).
Step 4 Click the first Select button to choose an incoming port for the PVC or SPVC.
For a PVC or SPVC, select a DMT interface for the incoming port.
Your selection populates both fields. However, you must use a different selection for your outgoing port.
|
Note If you are creating an SPVC with a nonCDM end point, you must make only one selection on this window for the incoming port. An extra window appears after this window that prompts you to enter a network service access point (NSAP) address for the outgoing port. |
Step 5 Click the second Select button to choose an outgoing port.
If you are creating a PVC, select an OC-3 or DS3 interface on the NI-2 management card for the outgoing port. If you are creating an SPVC, select the destination ATM end point of the connection.
The Deployment Wizard—Summary window appears (Figure 4-13).
|
Note If you do not select the correct ports in this window, your PVC or SPVC deployment fails. |
Step 6 Click Finish to complete the deployment.
This window (Figure 4-13) summarizes your deployment. When you create a PVC or SPVC, two virtual channel links (VCLs) are also created, representing the two incoming and outgoing end points.
|
Note If you are creating an SPVC with a nonCDM end point, only one Virtual Channel Link (VCL) is created. |
You can configure and view status and performance for these VCLs (refer to the "Managing VCLs" section for details.)
|
Note If you deploy a PVC or SPVC, this does not create the PVC or SPVC on the device. |
After you create a PVC or SPVC, you can apply the ATM QoS profile that you created earlier to the PVC or SPVC.
To view the ATM Connection QoS Configuration window, use the following steps:
The ATM Connection QoS Configuration window appears (Figure 4-14).
Step 2 From the list box at the left, 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 profiles applied to the selected PVC or SPVC appear in the tabs at the right.
Step 3 From the toolbar, select the option Edit > Apply Profile. A list of ATM QoS profiles appears.
Step 4 Click the named ATM QoS profile you want to apply. After you apply the profile, a status line appears briefly in the lower left corner of the window, which indicates whether or not the profile is applied successfully. The information for the selected new profile appears in the tabs at the right.
After you create a PVC or SPVC and apply an ATM QoS profile to the PVC or SPVC, you must create the PVC or SPVC on the device. This activates the connection.
The ATM Connections Management window appears (Figure 4-15).
Step 2 Select the related chassis, card, interface, and connection you want to create. Within the Configuration tab, type the desired information in the Subscriber Info, Source, and Destination areas.
|
Note If you are creating an SPVC, the NSAP address for the outgoing port is also displayed. |
Step 3 Click the Connect button in the Action area. You are prompted to confirm this action. The Connect button creates the subscriber connection on the device. The connection object changes to the Normal state. If you want to disconnect the subscriber connection, click the Disconnect button.
In the second Actions area, you can click the Decommission button, which stops management of the connection. When you decommission a connection, alarms are no longer reported against it, and performance polling is no longer performed on the connection.
Table 4-5 defines the fields that are located in the ATM Connection Management window.
| Field | Definition |
|---|---|
Subscriber ID | Type your subscriber ID. |
Source VPI | VPI value of the source VCL. |
Source VCI | VCI value of the source VCL. |
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.) 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 and perform more detailed configuration on both VCLs. |
Destination VPI | VPI value of the destination VCL. |
Destination VCI | VCI value of the destination VCL. |
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 you must provide if you are configuring an SPVC. When you have subtended chassis, you must provide the NSAP address for the destination ATM end point of the connection. (This field is only applicable to SPVCs, not PVCs.) The Destination Port button displays the ATM Configuration window for the selected PVC or SPVC. The Destination VCL button displays the VCL Configuration window for the selected PVC or SPVC. These buttons allow you to view and perform more detailed configuration on both VCLs. |
When you create an ATM connection (PVC or SPVC), two Virtual Channel Links (VCLs) are created automatically. 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.
To open the VCL Management window, use the following steps:
The ATM VCL Configuration window appears (Figure 4-16).
Step 2 Select a VCL from the list box at the left. The configuration information for the selected VCL appears in the tab at the right. You can view or modify this information.
The Configuration tab contains four areas:
Table 4-6 defines the fields that are located in the Configuration tab.
| Field | Definition |
|---|---|
VPI | Displays the current VPI values for either the source VCL or the destination VCL, depending upon the type of VCL selected. |
VCI | Displays the current VCI values for either the source VCL or the destination VCL, depending upon the type of VCL selected. |
UPC Mode | Displays the details of the Usage Parameter Control Mode on the established connection, the operations for which are
|
EPD Mode | Indicates whether the Early Packet Discard operation is enabled or disabled at this specific connection. |
Encapsulation Protocol | Allows you to specify the Protocol for terminating VC if Encapsulation Flag is aal5Mux. The options available are other, ip, xns, appletalk, clns, decnet, novell, apollo, and vines. |
Encapsulation Flag | Allows you to specify the encapsulation type for terminating VC. The options available are other, aal5Snap, aal5Nlpid, aal5FrNlpid, aal5Mux, aal34Smds, aalQsAal, aal5Ilmi, aal5Lane, and aal5Pnni. |
AAL User Type | Allows you to specify the user types if the Encapsulation flag is aal5Lane. The options available are
|
AIS Mode | Indicates whether Enable Alarm Indication Signal OAM cell generation is enabled or disabled if the interface fails on a cross connect virtual channel. |
RDI Mode | Displays details on the Enable Remote Defect Indication OAM cell generation. In ATM, if the physical layer detects a 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. |
|
Note The Layer 3 Configuration tab in the ATM VCL Configuration window does not apply to CDM 3.2 and is inoperable. |
To begin logging performance data on a VCL, use the following steps:
The ATM VCL Performance window appears (Figure 4-17).
Step 2 From the list box, select a VCL.
Step 3 Click the Start button to begin performance polling on the selected VCL.
The Performance tab contains three areas:
Table 4-7 defines the fields that are located in the Performance tab.
| Field | Definition |
|---|---|
Receive | Percentage of available bandwidth used when receiving information on the connection. |
Transmit | Percentage of available bandwidth used when transmitting information on the connection. |
In Cells | Total number of cells received on this VCL. |
Out Cells | Total number of cells transmitted on this VCL. |
UPC Violations | Total number UPC violations on this VCL. |
Packets In | Total number of packets received on this VCL. |
Cell Drops | Total number of cells dropped on this VCL. |
Packet Drops | Total number of packets dropped on this VCL. |
Start button | Click the Start button to begin Performance Polling on the selected VCL. Performance polling collects and displays data on the object, either in the Performance windows or the Performance Manager window (See and "Viewing Historical Performance Data" section for more information about performance data.) |
To view VCL status, use the following steps:
The ATM VCL Status window appears (Figure 4-18).
Step 2 From the list box at the left, select a VCL.
The status information for the selected VCL appears in the tab at the right.
The Status tab contains four areas:
Table 4-8 defines the fields that are located in the Status tab.
| Field | Definition |
|---|---|
Operational State | Status of the VCL connection. |
Last Change | Time elapsed since the last status change. |
Install Time | Time elapsed since the last installation. |
Span Type | VCL span type. |
Connection Type | VC configuration type. |
Cast Type | VC cast type. |
Location | Indicates the calling or called side of a soft PVC. |
Number of Attempts | Indicates the number of retries made to install this soft PVC. |
Last Release Cause | Indicates the cause of the last connection release. |
Segment Loopback | Indicates whether the segment loopback is enabled or disable on the virtual channel selected. |
Loopback Interval | Indicates the frequency with which the OAM loopback cells are generated. |
Posted: Thu Aug 31 11:00:37 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.