cc/td/doc/product/rtrmgmt/cdm/cdm34
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Getting Started Using CDM
 Tasks for Getting Started
 Information about Installing Cisco EMF and CDM
 Starting a Cisco EMF User Session
 Ending a Cisco EMF User Session
 Using CDM
 Specifying Chassis Information and Setting the Cisco IOS Passwords
 Commissioning the DSLAM and other Network Elements
 Configuring Interfaces
 Enabling SNMP Trap Generation
 Deleting Network Elements

Getting Started Using CDM

This chapter describes the tasks you must perform to begin working with CDM. To manage Cisco DSLAMs on the network, you should be familiar with the Cisco EMF and CDM GUIs. This chapter briefly describes the Cisco EMF portion of the software, but mainly describes the CDM user interface.

This chapter includes the following sections:

Tasks for Getting Started

The following tasks are required to get started with CDM and the documents in which to find the instructions.

Task Cisco Document Reference
Step 1 

Install Cisco EMF before you install CDM.

Cisco Element Management Framework User Guide

Step 2 

Start Cisco EMF before you install CDM. Do not begin a user session at this time.

Cisco Element Management Framework User Guide

Step 3 

Install CDM.

Installation Notes for the Cisco DSL Manager NI-1 and NI-2, Release 3.4

Step 4 

Start a Cisco EMF user session. When you start a Cisco EMF user session, CDM starts up automatically.

Cisco Element Management Framework User Guide

Step 5 

Deploy a site from which Cisco DSLAMs, and its objects, are to be managed.

Cisco Element Management Framework User Guide

Step 6 

Deploy chassis and chassis objects through a combination of Cisco EMF and CDM functions.

Cisco Element Management Framework User Guide

Cisco DSL Manager NI-2 User Guide

Step 7 

If you have used autodiscovery for a chassis, set passwords. After you manually deploy a chassis, and before you can commission it, you must enter the Cisco IOS command line security password information and enable the password.

See the "Manually Deploying a Cisco DSLAM Chassis" section. Also see the "Specifying Chassis Information and Setting the Cisco IOS Passwords" section.

Step 8 

Commission a DSLAM chassis so that the software can actively manage the chassis and the cards within the chassis.

See the "Commissioning a Cisco DSLAM Chassis" section.

Step 9 

Set up subscribers; use default xDSL profiles or create new profiles. Set up subscriber connections and upload QoS profiles.

See "Creating and Applying xDSL Profiles," and "Creating Connections and ATM QoS Profiles."

Step 10 

Manage Cisco DSLAM objects—View alarms, status, and current and historical data, and manage inventory of network objects.

See "Viewing System and Object Status,""Viewing Performance Data," "Viewing Inventory and Summary Information," and "Viewing Alarms and Events."

Information about Installing Cisco EMF and CDM

Refer to the Installation Notes for the Cisco DSL Manager NI-1 and NI-2, Release 3.4 for instructions on installing CDM. Refer to the Cisco Element Management Framework Installation and Administration Guide, Release 3.2 document for instructions on installing Cisco EMF.

Starting a Cisco EMF User Session

Each active Cisco EMF session requires a single Cisco EMF license. To start a Cisco EMF session, follow these steps.

Note   Cisco EMF should already be running. If, upon starting, you receive a message that Cisco EMF is not running, contact your system administrator.
Step 1   At the UNIX prompt, enter the following command:

CEMFROOT/bin/cemf session

Replace CEMFROOT with the root directory location in which Cisco EMF Version 3.x is installed. For example, /opt/cemf3.

The Login window opens. (See Figure 2-1.)


Figure 2-1   Login Window


Step 2   Enter your user name and password.

When you initially log in to Cisco EMF/CDM, enter admin (all lowercase) in the user name and password fields.

Note    After you use the initial password to log in, your system or network administrator can use the Cisco EMF access manager to create user groups and new passwords. see the chapter about user access control in the Cisco Element Management Framework User Guide for more information.

Step 3   Click OK to proceed.

If you enter an unknown user name or password, CDM displays an error message. To continue, click OK, and then enter a valid user name and password.

Note    You are allowed three attempts to enter a valid user name and password. If you do not enter a valid user name and password after three attempts, the session does not start and the Login window closes.

When you enter a valid user name and password, the session starts and the Cisco EMF Launchpad window opens. (See Figure 2-2.)



Figure 2-2   Cisco Element Manager Framework Launchpad Window



Note   For more information about using the Cisco EMF Launchpad window, see
the "Using the Cisco EMF Launchpad" section.

Ending a Cisco EMF User Session

To end or exit from a Cisco EMF user session, follow these steps:

Step 1   Choose one of the following methods to quit the session:


Figure 2-3   Close Icon


A dialog box opens that asks whether you wish to quit the Cisco EMF Manager System.

Step 2   Click Yes to quit the session.

All active applications close and the session terminates.


Using CDM

This section includes the following topics:

To start a CDM session, you must first start Cisco EMF by using the cemf start command. You use the cemf session command to launch the Map Viewer window, from which you can perform all CDM tasks. When you start Cisco EMF, CDM automatically starts too. The first step to managing a network with CDM is to deploy the DSLAM chassis and then commission it, which initiates autodiscovery of the DSLAM NI-2 card, line cards, and any preprovisioned settings and xDSL profiles.

Deploying Objects

This section includes the following topics:

Using CDM, you can deploy objects manually or let the software automatically deploy Cisco equipment on the network. You can also deploy objects before they are physically installed in a Cisco DSLAM in the field. CDM detects the presence of previously deployed network equipment as soon as that equipment becomes operational.

Manually Deploying Objects

If you have only a few objects to deploy, use manual deployment. When you choose the Deploy option, you open the Deployment Wizard window, which guides you through the deployment process.

Autodiscovery Process

Autodiscovery automatically discovers existing networks, saving time and effort that you might otherwise spend manually discovering networks. Autodiscovery interrogates the network for IP and SNMP devices, then creates an object for each new device it discovers. Autodiscovery is an efficient way to discover Cisco DSLAMs that are already installed. See the "The Autodiscovery Process" section for a more detailed description of autodiscovery.

Preprovisioning Feature

Preprovisioning is a type of deployment. The difference between deployment and preprovisioning is that you preprovision an object before the hardware is actually present; you deploy an object when the hardware is present. Preprovisioning allows you to deploy cards within a chassis before they are physically installed in the hardware.

You can also configure a preprovisioned card. For example, if you know a 4DMT card is to be installed in a chassis, you can deploy and preprovision the 4DMT card in a selected chassis and perform all relevant 4DMT card configurations. When the 4DMT card becomes physically available, CDM accepts the configuration you have already performed. The system does not monitor preprovisioned objects, which means that alarm, status, and performance information are not available for preprovisioned hardware.

When the 4DMT card is physically inserted in a card slot in the chassis, subscribers and line card configuration are immediately loaded into that line card. The software automatically detects the existence of the cards and moves the cards into the Normal state. You can then monitor alarm, status, and performance information on the card.

Note   You can deploy preprovisioned line cards only if the related Cisco DSLAM chassis and NI-2 card are in a Normal or Decommissioned state.

Deployment Process

To configure a Cisco DSLAM that the software can manage, you must first deploy the generic site in which you want the Cisco DSLAM located. (A generic object is a nontechnology-specific object.) You can deploy the site by opening the Deployment Wizard template. After you successfully deploy the generic site, you can begin deploying the chassis and chassis objects.

To deploy a manageable Cisco DSLAM, follow these guidelines (see Figure 2-4 for a visual guide):

1. Deploy generic site—Deploy the generic site using the Deployment Wizard template. Refer to the Cisco Element Management Framework User Guide for information on deploying a site.

2. Deploy DSLAM chassis—Deploy the Cisco DSLAM chassis manually or use the Autodiscovery feature. (See the "The Autodiscovery Process" section.)

3. Deploy DSLAM chassis objects using one of the following methods:


Figure 2-4   Deployment Process


Deploying a Generic Site

Before you deploy a Cisco DSLAM chassis, you must deploy one or more generic sites under which you can then deploy DSLAMs. Complete the following steps to deploy a generic site:

Step 1   From the left side of the Map Viewer window, right-click the Physical map hierarchy view icon.

Step 2   Choose Deployment > Deploy Generic Objects from the object menu.

The Deployment Wizard—Templates window opens. (See Figure 2-5.)


Figure 2-5   Deployment Wizard—Templates Window


Step 3   Click Site, then click Forward.

The Deployment Wizard—Object Parameters Window opens. (See Figure 2-6.)


Figure 2-6   Deployment Wizard —Object Parameters Window


Step 4   Enter the number of sites that you want to deploy in the Number of Sites field, and then click Forward.

The next Deployment Wizard—Object Parameters window opens. (See Figure 2-7.)


Figure 2-7   Deployment Wizard—Object Parameters Window


Step 5   Enter the name of the site in the Site Name Field, then click Forward.

The Deployment Wizard—Views window opens. (See Figure 2-8.)


Figure 2-8   Deployment Wizard—Views Window


Step 6   Repeat Step 5 for each site that you want to deploy.

For example, if you entered 24 in the Number of Sites field (in Step 4), CDM prompts you to enter the name for each of the 24 sites.

Step 7   Click Select next to the Physical field.

The Object Selector window opens. (See Figure 2-9.)


Figure 2-9   Object Selector Dialog Box


Step 8   Click Physical, and then Apply to apply this site to the Physical view.

The Deployment Wizard—Summary window opens. (See Figure 2-10.)


Figure 2-10   Deployment Wizard—Summary Window


Step 9   Click Finish to deploy the generic site or sites.

Step 10   Repeat Step 5 through Step 9 for each site. For example, if you entered 24 in the Number of Sites field (in Step 4), CDM prompts you to enter the name for each of the 24 sites.

Step 11   Verify that the sites you have deployed display on the left side of the Map Viewer window.


Manually Deploying a Cisco DSLAM Chassis

You can manually deploy a Cisco DSLAM chassis from the Map Viewer window. To access the Map Viewer, click the Viewer icon in the Launchpad. When you deploy a Cisco DSLAM chassis, you are configuring the chassis and SNMP parameters for the chassis. You manually deploy a DSLAM chassis through the Deployment Wizard window.

Note   Before you deploy a DSLAM chassis, you must deploy a site (see the "Deploying a Generic Site" section on page 2-8 for these instructions).

To manually deploy a Cisco DSLAM chassis under a site, complete the following steps:

Step 1   From the left side of the Map Viewer window, within the CDM Manager view, right-click the site to access the object menu.

Step 2   Choose Deployment > Deploy Cisco DSLAM.

The Deployment Wizard—Templates window open. (See Figure 2-11.)


Figure 2-11   Deployment Wizard—Templates Window


Step 3   Click Create <DSLAM type> Chassis under auto named shelf or Create <DSLAM type> Chassis under user named shelf, and then click Forward.

Tip You can have CDM name the DSLAM chassis, or you can create a name for the chassis.

The Deployment Wizard—Object Parameters window opens. (See Figure 2-12.)


Figure 2-12   Deployment Wizard—Object Parameters Window


Step 4   Enter the appropriate number of DSLAMs in the DSLAM units field.

Step 5   Enter the name for the DSLAM units in the Prefix for unit name field.

Step 6   Click Forward to proceed.

Note    Cisco recommends that you deploy one chassis at a time.
Note    If you choose to deploy a chassis under a user-named shelf, the Number of DSLAM units and Prefix for unit name fields display in two separate Deployment Wizard—Object Parameters windows.

Step 7   In the Prefix for unit name field, accept the default prefix that CDM generates, or enter a unique prefix for the unit name.

The value that you enter in the Prefix for unit name field carries over to the Chassis Name field to minimize duplicate data entry. You can use the default value, change the value, or delete the default value to exclude it from part of the Chassis Name field.

Step 8   Click Forward to continue.

Step 9   Click Select next to the Physical field to select the Physical site under which you want to deploy this DSLAM.

The Object Selector dialog box opens. (See Figure 2-13.)


Figure 2-13   Object Selector Dialog Box


Step 10   Click the + next to Physical to display the sites that are deployed.

Step 11   Click the site under which you want to deploy the DSLAM chassis.

The Deployment Wizard—Views window reopens and displays the Site that you selected in the Object Selector dialog box next to the Physical and Component Managed fields.

Step 12   Click Forward to continue.

The next Deployment Wizard—Object Parameters window opens. (See Figure 2-14.)


Figure 2-14   Deployment Wizard—Object Parameters Window


Step 13   Enter the appropriate information in the fields in this window, as follows:

    a. In the Chassis IP Address field, enter the valid IP address for the chassis you are deploying; the maximum alphanumeric limit is 15 characters.

Contact your system administrator if you do not know the IP address.

    b. In the SNMP V2c Read Community field, enter the name for the read-only relationship; the name that you enter must match the SNMP community read string on the Cisco DSLAM.

The default entry might not match the Cisco DSLAM privileges; be sure to enter a name that matches the SNMP community read string.

    c. In the SNMP V2c Write Community field, enter the name for the read-write relationship; the name you enter here must match the SNMP write community string on the Cisco DSLAM.

You must replace the default entry; it might not match the Cisco DSLAM privileges.

    d. In the SNMP Version field, enter the version of SNMP that is running on the equipment in the Chassis IP Address field from the following choices:

    e. In the Chassis Name field, use the default chassis name (that CMD generates as a result of your entry in the Prefix for Unit Name field) or enter a unique name for the chassis you are deploying.

    f. In the Login Password field, enter the login password for this DSLAM.

    g. In the Exec Password field, enter the executive password for this DSLAM; this password should match the IOS privileged password for the IOS that is running on the DSLAM.

Step 14   Click Forward to complete the deployment process.

The Deployment Wizard Summary window opens and informs you that CDM is ready to deploy the DSLAM chassis. (See Figure 2-15.)


Figure 2-15   Deployment Wizard Summary Window


The Deployment Wizard Summary window prompts you to commit or reject the deployment. When you deploy a chassis, a shelf object is also created (thus deploying two objects), as shown in the Deployment Wizard Summary window (see Figure 2-15).

Step 15   To commit the deployment, click Finish; to reject the deployment, click Cancel.

If the deployment is successful, the object appears in the chassis view. If the deployment is unsuccessful, the Deployment Wizard—Summary window informs you that the deployment failed.


If the DSLAM that you deployed is populated and ready to be managed on the network, you need to commission it next. See the "Commissioning the DSLAM and other Network Elements" section for instructions on how to commission the DSLAM and begin managing its network elements.

If after you have commissioned a DSLAM, you need to change or replace an NI card or a line card, you can first preprovision the card, and then manually deploy the card. The following sections provide instructions on manually deploying cards on a DSLAM.

Manually Deploying a Line Card

This section includes the following topics:

Table 2-1 lists the types of line cards that you can deploy on each DSLAM through the CDM interface.

Table 2-1   Line Card Deployment

Line Card DSLAMs Supported
Cisco 6015 Cisco 6100 Cisco 6130 Cisco 6160 Cisco 6260

8xDMT

yes

no

no

yes

yes

8xDMTC

yes

no

no

yes

yes

8xG.SHDSL

yes

no

no

yes

yes

FlexiCAP

yes

yes

yes

yes

no

FlexiDMT

yes

yes

yes

yes

yes

DMT

no

yes

yes

yes

no

DMT over ISDN

yes

no

no

no

yes

SDSL

no

no

yes

yes

yes

When you deploy a line card, you are configuring the parameters for the card. This section describes how you deploy a line card, and it provides the parameters (field definitions) for each of the basic types of line cards supported by the various DSLAM chassis. These instructions pertain to a DMT line card, but they can apply to any type of line card that is supported on the Cisco DSLAMs.

Note   Be aware of the intermixing rules and compatibility issues for Cisco DSLAMs. Refer to the following Cisco publications: Cisco DSLAM Compatibility Notes, Cisco 6100 with NI-2 Hardware Installation Guide, Cisco 6130 with NI-2 Hardware Installation Guide, Cisco 6015 Hardware Installation Guide, Cisco 6160 Hardware Installation Guide, and Cisco 6260 Hardware Installation Guide. These documents provide the most up-to-date information. You can navigate to each of these publications from the following URL: http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/index.htm.

To manually deploy a line card in a chassis, complete the following steps:

Step 1   In the Map Viewer window, right-click the chassis in which you want to deploy a line card.

Step 2   Choose Deployment > Deploy Cisco DSLAM from the object menu.

The Deployment Wizard—Templates window opens. (See Figure 2-16.)


Figure 2-16   Deployment Wizard—Templates Window


Step 3   Click Create [type of card] Card under <DSLAM type> Chassis, then click Forward.

The first of two or more Deployment Wizard—Object Parameters windows opens.

The instructions for entering information in the Deployment Wizard—Object Parameters windows that follow are generic. Definitions for the fields that are specific to the type of line card are described in the following tables:

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


Figure 2-17   Deployment Wizard—Object Parameters Window


Step 4   Enter the appropriate information in the Deployment Wizard—Object Parameters window, as follows:

    a. In the Number of [type of card] Cards field, enter the number of line cards that you want to deploy for this chassis; for the 6100, 6130, and 6160, the maximum number is 32.For the 6260, the maximum number is 30, and for the 6015, the maximum number is 6 slots.

    b. In the Card name prefix field, accept the default prefix, or enter a unique prefix for the card name.

The value that you enter in the Card name prefix field carries over to the Card Name field to minimize duplicate data entry. You can use the default value, change the value, or delete the default value to exclude it from part of the Card Name field.

The next Deployment Wizard—Object Parameters window opens. (See Figure 2-18.)


Figure 2-18   Deployment Wizard—Object Parameters Window


Step 5   Enter the appropriate information in the Deployment Wizard—Object Parameters window, as follows:

    a. In the [type of card] Card Slot Number field, enter the slot number in which the line card will be installed in the Cisco DSLAM chassis.

Valid values for each type of DSLAM are as follows:

If you chose to deploy more than one card in the Number of [type of card] Cards field, this field (and the Card Name field) remain visible until you enter data for each of the [type of card] cards you are deploying. The Deployment Wizard Summary window appears only after you assign a slot number and card name for each card you are deploying.

    b. In the Card Name field, accept the default card name (that is generated as a result of your entry in the Card Name Prefix field) or enter a unique name for the line card.

An example of a unique card name is DMT6XXXslot2 (where DMT is the card name, 6XXX is the chassis in which the card is installed, and slot2 is the physical location of the card in the chassis). If you are deploying multiple DMT cards for this chassis, CDM retains the card name that you entered for the first DMT card and adds a digit to the end of the card name, for each subsequent card, to indicate which card you are currently configuring.

Step 6   Click Forward to continue.

Note    If you are deploying more than one line card, the software automatically increments the values in the fields in the second Deployment Wizard—Object Parameters window to indicate the card you are currently configuring. You can accept or overwrite the default values.

For example, if the Card Name value for the first line card is DMT1, the value in the Card Name field for the second line card displays as DMT2.

After you configure the parameters in the Deployment Wizard—Object Parameters windows, the Deployment Wizard Summary window opens. (See Figure 2-19.)


Figure 2-19   Deployment Wizard Summary Window—Line Card


The Deployment Summary window displays the number of objects CDM is ready to deploy. In this example, CDM is deploying an 8xDMT line card, which includes 8 ports and a line card—a total of 9 objects to be deployed.

Step 7   To commit the deployment, click Finish. To reject the deployment, click Cancel.

If the deployment is successful, the object appears in the chassis view. If the deployment is not successful, a feedback window informs you that the deployment failed.

Note    When you deploy a line card, the interfaces (that represent the ports on a line card) are automatically deployed as well. Therefore, the number of ports plus the interface are deployed for a line card.


Deployment Wizard—Object Parameter Field Definitions for the 8xDMT Card

Table 2-2 describes the fields that are located in the Deployment Wizard—Object Parameters (8xDMT card) window.

Table 2-2   Deployment Wizard—Object Parameters Field Definitions for the 8xDMT Card

Field Description

Number of DMT Cards

Enter the number of DMT cards you want to deploy for the chassis that you selected from the Deployment Wizard—Templates window using the following guidelines:

  • The maximum number for the 6160 is 32.
  • The maximum number for the 6260 is 30
  • The maximum number for the 6015 is 6.

Card Name Prefix

Accept the default prefix that CDM generates, or enter a unique prefix for the card name.

The value that you enter in the Card Name Prefix field carries over to the Card Name field to minimize duplicate data entry. You can use the default value, change the value, or delete the default value to exclude it from part of the Card Name field.

DMT Card Slot Number

Enter the slot number in which you will install the DMT card in the Cisco DSLAM using the following guidelines.

  • Valid values for the 6160 are 1 to 9 and 12 to 34. (Slots 10 and 11 are reserved for NI-2 cards.)
  • Valid values for the 6260 are 1 to 9 and 12 to 32. (Slots 10 and 11 are reserved for the NI-2 cards.)Valid values for the 6015 are 1 to 6.

If you chose to deploy more than one card in the Number of DMT Cards field, this field and the Card Name field remain visible until you enter data for each of the DMT cards you are deploying. The Deployment Summary window opens only after you assign a slot number and card name for each card you are deploying.

Card Name

Use the default card name that CDM generates as a result of your entry in the Card Name Prefix field, or enter a unique name for the DMT card. An example of a unique card name is DMT6160slot2, where DMT is the card name, 6160 is the chassis in which the card is installed, and slot2 is the physical location of the card in the chassis.

If you are deploying multiple DMT cards for this chassis, CDM retains the card name that you entered for the first DMT card and adds a digit to the end of the card name for each subsequent card. This process indicates which card you are currently configuring.

Deployment Wizard—Object Parameter Field Definitions for the 4xSDSL Card

Table 2-3 describes the fields that are located in the Deployment Wizard—Object Parameters (4xSDSL card) windows.

Table 2-3   Deployment Wizard—Object Parameters Field Definitions for the
4xSDSL Card

Field Description

Number of SDSL Cards

Enter the number of 4xSDSL cards that you want to deploy for the chassis you selected from the Deployment Wizard—Templates window. The maximum number for the 6130 and 6160 is 32. The maximum number for the 6260 is 30.

Card Name Prefix

Accept the default prefix that CDM generates, or enter a unique prefix for the card name.

The value that you enter in the Card Name Prefix field carries over to the Card Name field to minimize duplicate data entry. You can use the default value, change the value, or delete the default value to exclude it from part of the Card Name field.

SDSL Card Slot Number

Enter the slot number in which you plan to install the 4xSDSL in the Cisco DSLAM using the following guidelines.

  • Valid values for the 6130 are 1 to 8, 13 to 28, and 31 to 38 (slots 10 and 11 are reserved for NI-2 cards, and slots 9, 12, 29, and 30 are reserved for future development).
  • Valid values for the 6160 are 1 to 9 and 12 to 34; slots 10 and 11 are reserved for NI-2 cards.
  • Valid values for the 6260 are 1 to 9 and 12 to 32 (slots 10 and 11 are reserved for the NI-2 cards).

If you chose to deploy more than one card in the Number of SDSL Cards field, this field and the Card Name field remain visible until you enter data for each of the 4xSDSL cards you are deploying. The Deployment Summary window opens only after you assign a slot number and card name for each card you are deploying.

Card Name

Use the default card name that CDM generates as a result of your entry in the Card Name Prefix field, or enter a unique name for the 4xSDSL card. An example of a unique card name is SDSL6160slot2, where SDSL is the card name, 6160 is the chassis in which the card is installed, and slot2 is the physical location of the card in the chassis.

If you are deploying multiple 4xSDSL cards for this chassis, CDM retains the card name you entered for the first 4xSDSL card and adds a digit to the end of the card name (for each subsequent card) to indicate which card you are currently configuring.

Deployment Wizard—Object Parameter Field Definitions for the 4xflexi Card

Table 2-4 describes the fields that are located in the Deployment Wizard—Object Parameters (4xflexi card) windows.

Note   CDM provides two options for deploying a 4xflexi card—Create Cisco Flexi CAP Line Card and Create Cisco Flexi DMT Line Card. The fields in the Deployment Wizard—Object Parameters windows are the same for the 4xflexi CAP and 4xflexi (DMT), therefore, use the field definitions in this section for both.

Table 2-4   Deployment Wizard—Object Parameters Field Definitions for the 4xflexi Card

Field Description

Number of Cisco Flexi Cap Card Objects or Number of Cisco Flexi DMT Card Objects

Enter the number of 4xflexi cards you want to deploy for the chassis you selected from the Deployment Wizard—Templates window using the following guidelines:

  • The maximum number for the 6015 is 6.
  • The maximum number for the 6100, 6130, and 6160 is 32.
  • The maximum number for the 6260 is 30.

Card Name Prefix

Accept the default prefix that CDM generates, or enter a unique prefix for the card name.

The value you enter in the Card Name Prefix field carries over to the Card Name field to minimize duplicate data entry. You can use the default value, change the value, or delete the default value to exclude it from part of the Card Name field.

Flexi CAP Card Slot Number or Flexi DMT Card Slot Number

Enter the slot number in which the 4xflexi card will be installed in the Cisco DSLAM chassis using the following guidelines:

  • Valid values for the 6015 are 1 to 6.
  • Valid values for the 6100 and 6130 are 1 to 8, 13 to 28, and 31 to 38 (slots 10 and 11 are reserved for NI-2 cards, and slots 9, 12, 29, and 30 are reserved for future development).
  • Valid values for the 6160 are 1 to 9 and 12 to 34; slots 10 and 11 are reserved for NI-2 cards.
  • Valid values for the 6260 are 1 to 9 and 12 to 32 (slots 10 and 11 are reserved for the NI-2 cards).

If you chose to deploy more than one Flexi card in the Number of Cisco Flexi XXX Card Objects field, this field (and the Card Name field) remains visible until you enter data for each of the cards you are deploying. The Deployment Summary window opens only after you assign a slot number and card name for each card you are deploying.

Card Name

Use the default card name (generated as a result of your entry in the Card Name Prefix field) or enter a unique name for the 4xflexi card. An example of a unique card name is FCAP6160slot3 (where FCAP is the card name, 6160 is the chassis in which the card is installed, and slot3 is the physical location of the card in the chassis).

If you are deploying multiple flexi cards for this chassis, the system retains the card name you entered for the first flexi card and adds a digit to the end of the card name (for each subsequent card) to indicate which card you are currently configuring.

Specifying Chassis Information and Setting the Cisco IOS Passwords

This section provides instructions to enter the appropriate chassis information in the Management Information window so that you can set the Cisco IOS command line interface (CLI) passwords. This section includes the following topics:

Some element manager applications use the Cisco IOS CLI. Therefore, after you deploy a chassis, and before you can commission a chassis, you must enter the Cisco IOS command line security password information for the Cisco DSLAM chassis. Setting the IOS CLI security passwords allows CDM to use IOS commands to communicate with the DSLAM through a telnet window that you open from the CDM GUI.

When you manually deploy a DSLAM, you can enter the IOS passwords in the Deployment Wizard window. See the "Manually Deploying a Cisco DSLAM Chassis" section.

You can configure a chassis or its objects only if the system administrator provides you with the appropriate CLI password values. These values are set in the Management Information window, IOS/Command Line Security tab.

Note   The system administrator or network manager should be responsible for changing the Cisco IOS CLI security passwords; general users should not change these passwords.

Setting Chassis Information in the Management Information Window

To enter chassis Cisco IOS command line security information, follow these steps:

Step 1   From the Map Viewer window, within the Physical view, right-click the chassis for which you want to set security information to access the object menu.

Step 2   Choose Cisco DSL Manager > Chassis > Administration > IOS Settings from the object menu.

The Management Information window opens. (See Figure 2-20.)


Figure 2-20   Management Information Window—Configuration Tab


Step 3   Enter the appropriate information in the fields on this tab, as follows:

    a. In the IP Address field, verify the IP address of the chassis for which you are setting the security password.

Do not change the chassis IP address from this window; this field is display only.

    b. In the System Name field, verify the name of the system; this field is display only.

    c. In the System Contact field, enter the name of the person or persons who are responsible for the network equipment.

    d. In the System Location field, enter the physical location of the network equipment.

    e. In the Extra Location Information field, enter additional physical location information for the network equipment.

Step 4   Verify the information in the Configuration tab.


Setting the Cisco IOS Command Line Security Password

Complete these steps to set the Cisco IOS CLI security password:

Step 1   Click the IOS/Command Line Security tab.

The IOS Command Line Security tab becomes active. (See Figure 2-21.)


Figure 2-21   Management Information Window—IOS/Command Line Security Tab


Step 2   Enter the Cisco IOS command line security information as follows:

    a. Do not enter a user name in the User Name field.

Generally a user name is not set on the node, so you should leave this field blank. Setting a user name allows that user and only that user to log in through the Telnet window and use IOS CLI commands from CDM to the DSLAM.

    b. In the Login Password field, enter the login password.

This is the password that users will enter to use the IOS CLI from CDM through a telnet window. The login password entered in this field should match the login password on the Cisco DSLAM.

    c. In the Exec Password field, enter your Cisco IOS CLI password.

This is the enable password that allows you to configure the elements on the network. The password that you enter in this field should match the privileged IOS password on the Cisco DSLAM.

Step 3   Click Save Locally to save your passwords locally in Cisco EMF and CDM.

Step 4   Click Save to Device to save the passwords on the selected DSLAM.

Note    When you click the Save to Device button, CDM saves the information locally and on the device.

An Action Report window opens and displays "Security details saved successfully."

Step 5   Click Save to save changes or Close to cancel.


Commissioning the DSLAM and other Network Elements

This section includes the following topics:

Before you can begin actively managing the elements on your network, you must commission the objects that you have deployed. After you commission the chassis, CDM can collect alarm, performance, and status data for the chassis and the cards that are installed in the chassis.

The initial status of a commissioned chassis is Normal. The initial status for a commissioned card is either Normal or Preprovisioned if the physical card is not detected in the chassis. See the "Configuring or Querying Network Components and Using Hierarchical Levels" section for more information about network object states.

Commissioning a Cisco DSLAM Chassis

When you commission a chassis, the chassis and all of its associated objects (that is, cards and interfaces) become available for management on the network. You can manually commission associated objects after you have already commissioned a chassis, or you can allow CDM to automatically commission the associated objects. For example, if you add a card after you have commissioned a chassis, the chassis automatically commissions itself during the next polling cycle (approximately 20 to 30 seconds).

To commission a DSLAM chassis, follow these steps:

Step 1   From the left side of the Map Viewer window, within the Physical view, right-click the chassis you want to commission to open the object menu.

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

The Chassis Configuration window opens to the Configuration tab. (See Figure 2-22.)


Figure 2-22   Chassis Configuration Window—Configuration Tab


Step 3   Click Commission.


The Chassis Configuration window Configuration tab includes the following areas, which are described in Table 2-5:

Table 2-5   Chassis Configuration Window Field Descriptions

Field Description
Validation Parameters

Number of Slots

Displays the number of slots in the DSLAM.

Unavailable Slots

Displays the number of slots that are unavailable for management on the network.

Max Number of Sub-Modules per Slot

Identifies the number of submodules per slot.

Action

Failure

Use the down arrow to identify the type of action that you want a failure to initiate, as follows:

  • Nothing
  • SendTrap
  • Shutdown
  • Send Trap and Shutdown

Change

Select this diamond if you want to change the reason for failure.

Clock

Source Priority

Not used.

Clocking Mode

Not used.

Power Supply

PS1 Admin Status

Not used.

PS2 Admin Status

Not used.

Actions

Management

Click Commission to commission an object, or click Decommission to decommission an object.

Note You must first decommission an object before you can delete it.

Global Performance Logging

Click Start to begin global performance logging, or click Stop to suspend global performance logging.

Commission Status

Status of last commission

Displays Success or Failed after you click the Commission button.

When you click Commission, CDM performs the following functions:

During subrack discovery, CDM examines the chassis and automatically discovers and commissions the various interfaces on the cards in the chassis.

Note    Cisco recommends that after you click Commission, you look at the Map Viewer window and monitor the Physical view as the software populates the chassis objects. As the software populates the objects, icons display on the right side of the window. If a card icon contains a lock symbol on the upper left side of the icon, the card is preprovisioned, that is, not physically present in the chassis and therefore not able to be managed. An example of this view is shown in Figure 2-23.

Figure 2-23   Example of a Commissioned Chassis


The icon that displays in the upper left corner of the chassis indicates the state of the chassis:

Commissioning Cards

When you commission a chassis, the chassis and all of its associated objects (that is, cards and interfaces), become available for management on the network. However, if you add a card or interface to the chassis after you have already commissioned the chassis, you can manually commission that card.

Note   You can save time by allowing the chassis to automatically commission its objects during the polling cycles, rather than manually commissioning a card or interface.

To commission a card, you use the Configuration window. From this window, you can also enter common location language identifier (CLLI) codes or text descriptions for each card in the chassis.

To open the Configuration window and commission a card, follow these steps:

Step 1   From the left side of the Map Viewer window, within the Physical view, right-click the NI-2 card or the line card that you want to commission.

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

The Configuration window opens. (See Figure 2-24.)


Figure 2-24   Configuration Window


Step 3   Select the chassis and card from the list box on the left side of the window.

Step 4   Enter CLLI codes or other text descriptions in the Description 1 and Description 2 fields.

CDM saves the information that you enter in these fields, but not to the hardware. After you enter a description, CDM displays the descriptive text each time a user selects the object with which a description is associated.

Step 5   Click Commission to commission the card, or click Decommission to decommission the card.

The status of the commission process displays at the bottom of the window in the Status field.

Step 6   Click Save in the toolbar, or choose File > Save.


Configuring Interfaces

This section includes the following topics:

Configuring ATM Interfaces

Complete the following steps to configure ATM interfaces:

Step 1   From the left side of the Map Viewer window, right-click the interface for which you want to configure ATM properties.

Step 2   Chose Cisco DSL Manager > Interface > Configuration > ATM from the object menu.

The ATM Interface Configuration window opens to the Configuration (1) tab (see Figure 2-25).


Figure 2-25   ATM Interface Configuration Window—Configuration (1) Tab


Step 3   Refer to the descriptions of the fields in this window to set the ATM configuration fields. (See Table 2-6 and Table 2-7.)


The ATM Interface Configuration window has two tabs—Configuration (1) and Configuration (2). The fields on the Configuration (1) tab are described in Table 2-6. This tab has two areas—ATM Configuration and Interim Link Management Interface (ILMI) Configuration.

Table 2-6   ATM Configuration Window Configuration (1) Tab Field Descriptions

Field Description
ATM Configuration

Neighbor IP Address

Enter the IP address of the neighbor system that is connected to the far end of this interface and to which the network management system can send SNMP messages. This is only available when the chassis are managed though inband management.

Interface Type

Use the down arrow to specify the type of ATM interface: UNI1 (User to Network), PNNI2, IISP3, or NNI PVC only. To modify the interface type, the interface administrative status has to be down and interface Ilmi autoconfiguration must be disabled.

ATM Interface Side

Use the down arrow to specify whether ATM interface is subscriber (user) side or network side. Select notApplicable to specify that the interface type is other than uni or iisp.

SVC UPC4 Intent

Use the down arrow to specify the type of UPC to use on the destination half-leg of soft PVCs: passing, tagging, or dropping. Values other than passing are allowed only if policing is supported on the interface.

Address Type

Use the down arrow to specify the type of ATM addresses on this interface: nsap, es1, e164, or null. Only null or NSAP are supported in this version. If you select NSAP you must also specify the NSAP address.

Loopback

Use the down arrow to specify to the loopback mode:

  • line enabled: Packets are transmitted back to the source to test interface functionality and ensure that packets transmitted through the interface reach the destination without data loss.
  • no loopback (disabled): Restricts connection status (success or failure) messages from being received.
  • diagnostic: The transmit data stream is looped to the transmit direction.

Maximum VPCs5

Enter the maximum number of PVCs and SPVCs that are supported for this interface.

Maximum VCCs6

Enter the maximum number of PVCs and SPVCs that are supported for this interface.

Number of VCs per VP

Use the down arrow to set the number of virtual channels per virtual path.

NSAP7 Address

Enter the NSAP address.

Neighbor Interface Name

Enter the name of the connected interface on the neighbor system at the far end of this interface, to which the network management system can send SNMP messages. This is only available when the chassis are managed though inband management.

UNI Type

Use the down arrow to specify the type of UNI type, either private or public. Only specify this field if the ATM interface type is UNI.

UNI Signalling Version

Use the down arrow to specify the version of UNI signalling that is currently being used on the UNI or IISP interface: atmfUni3Dot0, atmfUni3Dot1, or atmfUni4Dot0. Choose Not applicable when the interface is a PNNI interface or when signalling is disabled. To change the setting in this field, the interface admin status must be down and the interface Ilmi autoconfiguration disabled.

Signalling Admin Status

Use the down arrow to enable or disable signalling/sscop8 on this interface. Choose disable to clear all the active SVCs on this interface.

Well-known VC Mode

Use the down arrow to specify whether well-known VCs should be created automatically or manually on the interface.

Transmit Queue Limit

Enter the transmit length.

Maximum Active VPI Bits

Enter the maximum number of active VPI bits configured for use on this interface.

Maximum Active VCI Bits

Enter the maximum number of active VCI bits configured for use on this interface.

Clock Source

Use the down arrow to specify the type of clock source, either none or internal.

ILMI Configuration

Keepalive Time

Enter the amount of time that should elapse between successive ILMI keepalive messages sent on this interface. A value of 0 disables ILMI keepalive messages on this interface.

Auto-Configuration

Use the down arrow to enable or disable the ILMI link and interface type determination. The configuration takes effect only on the next interface restart.

Address Registration

Use the down arrow to enable or disable ILMI address Registration on this interface. The configuration takes effect only on the next interface restart.

Trap

Use the down arrow to enable or disable traps for this interface.

VPI Value

Enter the VPI value of the VCC that supports the ILMI for this interface. If the VPI Value is set to 0, the ILMI will be disabled.

VCI Value

Enter the VCI value of the VCC that supports the ILMI for this interface. If the VCI Value is set to 0, the ILMI will be disabled.

Configuration

Use the down arrow to enable or disable ILMI configuration on this interface. The configuration takes effect only on the next interface restart. Disabling this object will also disable address registration, auto-configuration, and keepalive time.

1UNI = user to network

2PNNI = private network to network

3IISP = interim interface signalling protocol

4UPC = usage parameter control

5VPCs = virtual path connections

6VCCs = virtual circuit connections

7NSAP = Network Service Access Point

8SSCOP = Service Specific Connection Oriented Protocol

The Configuration (2) tab has three areas—Information Element Transfer, Physical Layer, and DS1/E1/DS3/E3. This tab is shown in Figure 2-26.


Figure 2-26   ATM Configuration Window Configuration (2) Tab


The fields on the Configuration (2) tab are described in Table 2-7.

Table 2-7   ATM Configuration Window Configuration (2) Tab Field Descriptions

Field Description
Information Element Transfer

Broadband High Layer

Use the down arrow to enable or disable to accept, transfer, and deliver the Broadband High Layer information element from the calling party to the called party.

Broadband Low Layer

Use the down arrow to enable or disable to accept, transfer, and deliver the Broadband Low Layer information element from the calling party to the called party.

Broadband Repeat Indicator

Use the down arrow to enable or disable to accept, transfer, and deliver the Broadband Repeat Indicator information element from the calling party to the called party. This object shall only be transferred if the Broadband Low Layer is enabled.

Calling Party Subnet Address

Use the down arrow to enable or disable to accept and transfer the calling party subaddress information.

Calling Party Number

Use the down arrow to enable or disable the calling party number information element is transferred to the called party.

Called Party Subnet Address

Use the down arrow to enable or disable to accept, transfer, and deliver called party subaddress information.

ATM Adaptation Layer Parameters

Use the down arrow to enable or disable to accept, transfer, and deliver the ATM adaption layer parameters.

Unknown Information Element

Use the down arrow to enable or disable to accept, transfer, and deliver the unknown Information Element from the calling party to the called party.

Physical Layer

Transmit Clock Source

Use the down arrow to specify the source of the transmit clock:

  • loopTiming—The recovered receive clock is used as the transmit clock.
  • freeRunning—A local clock source is used.
  • networkDerived—The recovered receive clock from another interface is used as the transmit clock source.

Clock Source Priority

Use the down arrow to set the priority of this interface if configured as a network clock source: notConfigured, priority1, priority2, priority3, priority4. notConfigured indicates this is not configured as a network clock source.

Line Coding

Use the down arrow to specify the line coding that is present on the physical interface (applies to DS1/E1 interfaces only):

  • ami1 on the DS1/E1 interface.
  • b8zs indicates B8ZS2 line code on DS1 interfaces.
  • hdb3 indicates HDB33 line code on E1 interfaces.

Loopback Configuration

Use the down arrow to specify the loopback configuration on the physical interface:

  • noLoop indicates no loopback is present.
  • diagnosticLoop indicates transmit data stream is looped to the receive direction.
  • lineLoop indicates receive data stream is looped to the transmit direction.

Cell Payload Scrambling

Use the down arrow to set cell payload scrambling to on or off.

STS-Stream Scrambling

Use the down arrow set STS4-stream scrambling to on or off.

DS1/E1/DS3/E3

Line Buildout (physical interfaces)

Use the down arrow to set the line buildout configuration on the transmit signal:

  • e3AllCables: all E3 interface cables.
  • ds3CablesUnder225: DS3 interface cables under 225 feet
  • ds3CablesOver225: DS3 interface cables over 225 feet
  • ds1Cables0To110: DS1 interface cables 0 to 110 feet
  • ds1Cables110To220: DS1 interface cables 110 to 220 feet
  • ds1Cables220To330: DS1 interface cables 220 to 330 fee
  • ds1Cables330To440: DS1 interface cables 330 to 440 feet
  • ds1Cables440To550: DS1 interface cables 440 to 550 feet
  • ds1Cables550To660: DS1 interface cables 550 to 660 feet
  • ds1CablesOver600: DS1 interface cables over 600 feet
  • e1AllCables: all E1 interface cables

Framing Mode (physical interfaces)

Use the down arrow to set the framing format:

  • sonet: sts-3c (OC-3) or sts-12c format (OC-12)
  • sdh indicates stm1 (OC-3) or stm4 (OC-12)
  • ds3m23adm indicates M23 ADM5 mode; applies to DS3 interfaces
  • ds3m23plcp indicates M23 PLCP6 mode; applies to DS3 interfaces
  • ds3cbitadm indicates C-BIT ADM mode; applies to DS3 interfaces
  • ds3cbitplcp indicates C-BIT PLCP mode; applies to DS3 interfaces
  • e3g832adm indicates G.832 ADM mode; applies to E3 interfaces
  • e3g751adm indicates G.751 ADM mode; applies to E3 interfaces
  • e3g751plcp indicates G.751 PLCP mode; applies to E3 interfaces
  • ds1sfadm indicates DS1 SF ADM mode; applies to DS1 interfaces
  • ds1esfadm indicates DS1 ESF ADM mode; applies to DS1 interfaces
  • ds1sfplcp indicates DS1 SF PLCP mode; applies to DS1 interfaces
  • ds1esfplcp indicates DS1 ESF PLCP mode; applies to DS1 interfaces
  • e1adm indicates E1 ADM mode; applies to E1 interfaces
  • e1plcp indicates E1 PLCP mode; applies to E1 interfaces
  • e1crcadm indicates E1 CRC-4 ADM mode; applies to E1 interfaces
  • e1crcplcp indicates E1 CRC-4 PLCP mode; applies to E1 interfaces
1AMI = alternate mark inversion

2B8ZS = bipolar with 8 zero substitution

3HDB3 = high density bipolar 3

4STS = synchronous transport signal

5ADM = add/drop multiplexer

6PLCP = physical layer convergence protocol

Configuring the T1/E1 Interface

Complete the following steps to configure a DS1 (T1/E1) interface:

Step 1   From the left side of the Map Viewer window, right-click the DSLAM whose DS1 interface you want to configure and choose Cisco DSL Manager > Interface > T1/E1.

The T1/E1 Interface Configuration window opens (see Figure 2-27).


Figure 2-27   T1/E1 Interface Configuration Window


Step 2   Select the NI card from the list box on the left to set the parameters for this interface.


The T1/E1 Interface Configuration window has one tab, Configuration. The fields on this tab are described in Table 2-8.

Table 2-8   T1/E1 Interface Configuration Window

Field Description

Line Type

Use the down arrow to choose the type of line for this circuit:

  • dsx1ESF1
  • dsx1D42
  • dsx1E1
  • dsx1E1-CRC3
  • dsx1E1-MF4
  • dsx1E1-CRC-MF

Time Elapsed

Displays the number of seconds that have elapsed since the beginning of the current measurement period.

Transmit Clock Source

Use the down arrow to choose the transmit clock source:

  • loopTiming
  • localTiming
  • throughTiming

Facility Data Link

Use the down arrow to choose the type of zero code suppression to be used on this circuit:

  • other
  • dsx1Ansi-T1-403
  • dsx1Att-54016
  • dsx1Fdl-none

Circuit Identifier

Displays the transmission vendor's circuit ID.

Line Coding

Use the down arrow to choose the line coding:

  • JBZS
  • B8ZS5
  • HDB36
  • ZBTSI7
  • AMI8
  • other

Loopback Config

Use the down arrow to choose the loopback configuration type:

  • dsx1NoLoop
  • dsx1PayloadLoop
  • dsx1LineLoop
  • dsx1otherLoop

Signal Mode

Use the down arrow to choose the type of signal mode:

  • none
  • robbedBit
  • bitOriented
  • messageOriented

Send Code

Use the down arrow to choose the type of code to be sent across the DS1 interface:

  • dsx1SendNoCode
  • dsx1SendLineCode
  • dsx1SendPayloadCode
  • dsx1SendResetCode
  • dsx1SendQRS
  • dsx1Send511Patttern
  • dsx1Send3in24Pattern
  • dsx1SendOtherTestPattern
1ESF = extended super frame or extended superframe format

2D4 = 4th generation channel back

3CRC = cyclic redundancy check

4MF = multiframe

5B8ZS = bipolar with 8 zero substitution

6HBD3 = high density bipolar 3

7ZBTSI = zero byte time slot interchange

8AMI = alternate mark inversion

Configuring an E3 Interface

Complete the following steps to configure an E3 interface.

Step 1   From the left side of the Map Viewer window, right-click the DSLAM whose E3 interface you want to configure and choose Cisco DSL Manager > Interface > E3.

The Manage DS3/E3 Interface Configuration window opens (see Figure 2-28).


Figure 2-28   Manage DS3/E3 Interface Configuration Window


Step 2   Select the NI card from the list box on the left to set the parameters for this interface.

Step 3   Set the fields as described in Table 2-9.


The DS3/E3 Interface Configuration window has one tab, Configuration and one area, E3 Configuration Parameters. The fields on this tab are described in Table 2-9.

Table 2-9   DS3/E3 Interface Configuration Window

Field Description

Circuit Identifier

Displays the circuit ID for the interface.

Transmit Clock Source

Use the down arrow to choose the type of transmit clock source:

  • LoopTiming
  • LocalTiming

Loopback Config

Use the down arrow to choose the type of loopback configuration:

  • No Loop
  • Payload Loop
  • Line Loop
  • Other Loop

Line Type

Use the down arrow to set the line type:

  • dsx3Cbit Parity
  • e3other
  • e3Framed
  • e3Plcp1
1PLCP = Physical Layer Convergence Protocol

Enabling SNMP Trap Generation

In the SNMP Management window, you can enable or disable trap generation on a selected device. You can also verify and modify the SNMP version and read or write names for a selected device from this window.

Note   Use this window to modify SNMP information. You must set SNMP information when you deploy the chassis (see the "Manually Deploying a Cisco DSLAM Chassis" section). Otherwise, CDM is unable to commission the chassis that you are configuring.

To open the SNMP Management window and enable SNMP trap generation, follow these steps:

Step 1   From the left side of the Map Viewer window, within the Physical view, right-click the chassis for which you want to set SNMP traps.

Step 2   Choose Cisco DSL Manager > Chassis > Administration > SNMP Settings from the object menu.

The SNMP Management window opens. (See Figure 2-29.)


Figure 2-29   SNMP Management Window


The chassis that you selected in the previous step is highlighted in the list box on the left side of the window. The SNMP Management window contains four areas of information:

When you open the SNMP Management window, CDM populates the fields to display the SNMP parameters that are set when you deploy that DSLAM. CDM does not currently support SNMP Version 3.

Step 3   In the Trap Generation field, click Enable or Disable.


You can enable or disable trap generation by clicking the appropriate button. When trap generation is enabled on a selected chassis, any traps generate alarms and send them to the IP address of the specified chassis. This means that alarms are visible to the user in the appropriate view of CDM. You can also disable this feature, so that no traps are generated and no alarms are sent. This means that no alarms are visible to the user on the selected chassis.


Deleting Network Elements

You can delete Cisco DSLAM chassis or line cards from most active windows, or by selecting an object from the left side of the Map Viewer window. When you delete a chassis, you delete all cards, interfaces, connections, and profiles within that chassis. You can only delete a chassis if it is decommissioned (has never been commissioned or has been decommissioned), which means that CDM is no longer actively managing the chassis.

Before you can delete a chassis, a module, or a line card from CDM, you must first decommission it, as follows.

Caution   If a module or line card has never been commissioned, do not decommission it before you delete it. An example is a preprovisioned line card that does not physically exist on the hardware but that is present in CDM. Because it does not physically exist in the DSLAM, you should not decommission it before you delete it. Rather, use the steps for deletion described in the following section to delete it from CDM. If you try to decommission it first, problems will occur.
Step 1   From the left side of the Map Viewer window, right-click the chassis or other object that you want to delete.

Step 2   Choose the appropriate menu options to open the appropriate Configuration window:

    a. Choose Cisco DSL Manager > Chassis > Configuration from the object menu to open the Chassis Configuration window (see Figure 2-22) and decommission a chassis.

    b. Choose Cisco DSL Manager > Module > Configuration from the object menu to open the Configuration window (see Figure 2-24) and decommission a module.

Step 3   Click Decommission in the related Configuration window.

Step 4   Verify that the chassis, module, or line card is decommissioned in the Status field.


After CDM has successfully decommissioned the chassis, module, or interface, you can delete it as follows:

Step 1   From the left side of the Map Viewer window, right-click the chassis, module, or interface to open the object menu.

Step 2   Choose Deployment > Delete Objects from the object menu.

Note    You can also select a chassis to be deleted from the list box in an active window, such as the Chassis Configuration window, and then select Deployment > Delete Objects.

The Deployment Wizard—Summary window opens. (See Figure 2-30.)


Figure 2-30   Deployment Wizard Summary Window—Delete Object


Step 3   Click Finish to delete the selected chassis, module, or interface (or click Cancel to abort the process).

After you click Finish, CDM informs you whether the deletion was successful.



hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Jan 24 06:01:34 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.