|
|
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 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:
Table 3-1 shows the tasks that are required to get started with CDM and the documents in which to find the instructions.
| Step | 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. | Cisco CDM Installation Notes |
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 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 6160 Element Manager User Guide |
Step 7 | Set passwords. After you deploy a network element, and before you can commission a network element, you must enter the Cisco IOS command line security password information and enable the password. | Cisco 6160 Element Manager User Guide |
Step 8 | Commission a DSLAM chassis so that the software can actively manage the chassis and the cards within the chassis. | Cisco 6160 Element Manager User Guide |
Step 9 | Set up subscribers; upload profiles, configure, and apply. | Cisco 6160 Element Manager User Guide |
Step 10 | Manage Cisco DSLAM objects—View alarms, status, current and historical data, and manage inventory of network objects. | Cisco 6160 Element Manager User Guide |
Refer to the Cisco Digital Subscriber Line Manager Installation Notes for instructions on installing Cisco EMF and CDM.
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. |
(Replace CEMFROOT with the root directory location in which Cisco EMF Version 3.0 is installed. For example, /opt/cemf3.)
The Login window appears (Figure 3-1).
Step 2 Enter your user name and password.
When you initially log into Cisco EMF/CDM, type admin (lowercase) in the user name and password fields.
Step 3 Click Ok to proceed.
If you enter an unknown user name or password, the system 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 appears (Figure 3-2).
The Cisco EMF Launchpad (Figure 3-2) is the first window that appears after you successfully log in to Cisco EMF.
The icons displayed in the Cisco EMF Launchpad window represent access to applications that are available with the standard Cisco EMF installation. Additional icons may appear if you install additional applications. Two methods are available from which you can launch the application:
|
Note The first time you access the Launchpad window, you may be unable to launch an application by clicking an icon if your console is not set up to display sufficient colors. If so, a dialog box might be located behind the Launchpad window. Move the Launchpad window until you see a dialog box with the following warning message, "There are insufficient colors available for CEMF client. Some applications may not display information correctly." In the warning dialog box, click OK. You can now launch an application. |
Figure 3-2 shows the standard Cisco EMF application icons.
The following sections briefly describe each icon available in the standard Cisco EMF installation. Refer to the Cisco Element Management Framework User Guide for detailed information regarding Cisco EMF applications.
When you click the Viewer icon, you launch the Map Viewer window. Map Viewer lets you view, build, and monitor the equipment on your network.
Map Viewer is the primary entry point into CDM. When you launch Map Viewer, the equipment on your network appears in a hierarchical structure on the left side of the window. When you select an item from the list, the graphical representation appears in the right side of the window.
When you click the Groups icon, you launch the Object Group Manager window. Use this window to organize network objects into object groups.
When you click the Access icon, you launch the Access Manager window. System administrator privileges are required to access this window. As a system administrator, you can control user access to several features of the system. This is important for security and for efficient and effective network management.
When you click the Events icon, you launch the Event Browser window. The Event Browser is a network service management tool that lets you identify events (notification of a condition or fault) that occur in the network. By identifying these events, you can act to resolve them quickly and efficiently.
For example, a power supply fault in a chassis would require an engineer to locate the physical object to rectify the problem. Such a fault would be critical to the operation of the network and would need prompt attention. When a fault occurs on a managed object in the network, the system is notified immediately.
When you click the Discovery icon, you launch the Discover Network Devices window. Use Auto Discovery to examine the network for IP and SNMP devices and create a managed object for each new device that is automatically discovered (recognized) by the software.
To start a CDM session, you must first start Cisco EMF. When you start Cisco EMF, the system automatically starts CDM.
The main configuration areas in CDM are:
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.
If you have only a few objects to deploy, use manual deployment. When you select the Deploy option, the system launches the Deployment Wizard. The Deployment Wizard guides you through the deployment process.
The Auto Discovery feature automatically discovers existing networks, saving time and effort that you might otherwise spend manually discovering networks. Auto Discovery interrogates the network for IP and Simple Network Management Protocol (SNMP) devices and creates an object for each new device discovered. Auto Discovery provides an efficient way to discover Cisco DSLAMs that have already been installed.
Preprovisioning is a type of deployment. The difference between preprovisioning and deployment 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 the preprovisioned card. For example, if you know that 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. |
To configure a Cisco DSLAM that can be managed by the software, 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 means of 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 this outline (see Figure 3-3 for a visual outline):
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 Auto Discovery feature (refer to the "Auto Discovering Objects" section).
3. Deploy DSLAM chassis objects by one of the following methods:
You can manually deploy a Cisco DSLAM chassis from the Map Viewer window. To access Map Viewer, click the Viewer icon on the Launchpad. When you deploy a Cisco DSLAM chassis, you are configuring the chassis and SNMP parameters for the chassis.
To manually deploy a Cisco DSLAM chassis under a site, follow these steps.
|
Note Make sure the generic site is already deployed. |
Step 2 Select Deployment > Deploy Cisco DSLAM.
The Deployment Wizard Templates window appears (Figure 3-4).
Step 3 Select the option for the chassis type you want to deploy (Create 6160 Chassis under user named shelf), then click Forward.
The first of two Deployment Wizard—Object Parameters window appears.
Step 4 Configure the parameters in the first Deployment Wizard—Object Parameters window, and then click Forward to proceed to the next window.
|
Note The following section defines the fields that are located in the Deployment Wizard—Object Parameters (for Cisco DSLAM chassis) windows. |
After you configure the parameters in the Deployment Wizard—Object Parameters windows, the Deployment Wizard Summary window appears (Figure 3-5).
The Deployment 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 Summary window (see Figure 3-5).
Step 5 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.
Table 3-2 defines the fields that are located in the Deployment Wizard—Object Parameters (for Cisco DSLAM chassis) windows.
| Field | Definition | ||
|---|---|---|---|
Number of DSLAM Units | Type the number of DSLAM chassis you want to deploy. We recommend that you deploy one chassis at a time. | ||
Prefix for Unit Name | Accept the default prefix generated by the software, or type a unique prefix for the unit name. The value you enter in the Prefix for Unit Name field is carried 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 so that it is not included as part of the Chassis Name field. | ||
Chassis IP Address | Type 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 have the IP address. | ||
SNMP V2c Read Community | Type the name to be used for the read-only relationship. The name you enter here must match the SNMP community read string on the Cisco DSLAM.
| ||
SNMP V2c Write Community | Type the name to be used for the read-write relationship. The name you enter here must match the SNMP write community string on the Cisco DSLAM.
| ||
SNMP Version | Type the version of SNMP that is running on the equipment in the Chassis IP Address field.
| ||
Chassis Name | Use the default chassis name (generated as a result of your entry in the Prefix for Unit Name field) or type a unique name for the chassis you are deploying. |
After you deploy the chassis, you can begin deploying the cards within the chassis. You can deploy the NI-2 card manually.
A Cisco DSLAM chassis supports one or two NI-2 cards. When you deploy an NI-2 card, you are configuring the parameters for the card. This section describes how you manually deploy an NI-2 card.
To manually deploy an NI-2 card, follow these steps:
Step 2 Select Deployment > Deploy Cisco DSLAM.
The Deployment Wizard—Templates window appears (Figure 3-6).
Step 3 Select the type of NI-2 card (DS3, OC-3, or OC-3/DS3) and the type of Cisco DSLAM chassis for which you want to deploy an NI-2 card, then click Forward.
The first of two Deployment Wizard—Object Parameters windows appears.
Step 4 Configure the parameters in the first Deployment Wizard—Object Parameters window, and then click Forward to proceed to the next window.
The following section defines the fields that are located in the Deployment Wizard—Object Parameters (NI-2 card) windows.
|
Note If you are deploying more than one NI-2 card, the software automatically increments the values in the fields of 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 NI-2 card is SysController1, the value in the Card Name field for the second card displays as SysController2. |
After you configure the parameters in the Deployment Wizard—Object Parameters windows, the Deployment Wizard Summary window appears (Figure 3-7).
The Deployment Wizard Summary window prompts you to commit or reject the deployment. When you deploy an NI-2 card, the system automatically creates interfaces that represent the ports on the NI-2 card. Therefore, more than one object may be deployed when you deploy an NI-2 card.
Step 5 To commit the deployment, click Finish. To reject the deployment, click Cancel.
A feedback window informs you if the deployment is successful.
Table 3-3 defines the fields that are located in the Deployment Wizard—Object Parameters (for NI-2 card) windows.
| Field | Definition |
|---|---|
Number of NI-2 Cards | Type the number of NI-2 cards you want to deploy for the chassis you selected from the Deployment Wizard—Templates window. Valid values are 1 and 2. |
Card Name Prefix | Accept the default prefix that is generated by the software, or type a unique prefix for the card name. The value you enter in the Card Name Prefix field is carried 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 so that it is not included as part of the Card Name field. |
NI-2 Card Slot Number (10 or 11) | Type the slot number in which the NI-2 card is installed in the Cisco DSLAM chassis. Valid values are 10 and 11. If you chose to deploy more than one card in the Number of NI-2 Cards 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 appears 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 type a unique name for the NI-2 card. An example of a unique card name is 6160NI2slot10 (where 6160 is the chassis in which the card is installed, NI2 is the card name, and slot10 is the physical location of the card in the chassis). If you are deploying two NI-2 cards for this chassis, the system retains the card name you entered for the first NI-2 card and adds a digit to the end of the card name to indicate which card you are currently configuring. |
A Cisco DSLAM chassis supports several line cards. When you deploy a line card, you are configuring the parameters for the card. This section describes how you deploy a line card, followed by the parameters (field definitions) for each type of line card supported by the Cisco 6160 chassis.
To manually deploy a line card in a Cisco 6160 chassis, follow these steps:
Step 2 Select Deployment > Deploy Cisco DSLAM.
The Deployment Wizard—Templates window appears (Figure 3-8).
Step 3 Select the Create [type of card] Card under 6160 Chassis option, then click Forward.
The first of two or more Deployment Wizard—Object Parameters windows appears.
Step 4 Configure the parameters in the first Deployment Wizard—Object Parameters window, and then click Forward to proceed to the next window.
The following sections define the fields that are located in the Deployment Wizard—Object Parameters windows for each type of line card.
|
Note If you are deploying more than one line card (must be of the same card type), the software automatically increments the values in the fields of 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 appears (Figure 3-9).
The Deployment Summary window prompts you to commit or reject the deployment.
Step 5 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 (representing the ports on a line card) are automatically deployed as well. Therefore, multiple objects may be deployed for a line card. |
Table 3-4 defines the fields that are located in the Deployment Wizard—Object Parameters (4DMT card) window.
| Field | Definition |
|---|---|
Number of DMT Cards | Type the number of DMT cards you want to deploy for the chassis you selected from the Deployment Wizard—Templates window. The maximum limit is 32. |
Card Name Prefix | Accept the default prefix that is generated by the software, or type a unique prefix for the card name. The value you enter in the Card Name Prefix field is carried 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 so that it is not included as part of the Card Name field. |
DMT Card Slot Number | Type the slot number in which the DMT card will be installed in the Cisco DSLAM chassis. Valid values are 1 to 9 and 12 to 34 (slots 10 and 11 are reserved for NI-2 cards). If you chose to deploy more than one card in the Number of DMT Cards field, this field (and the Card Name field) remains visible until you enter data for each of the DMT cards you are deploying. The Deployment Summary window appears 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 type 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 slot 2 is the physical location of the card in the chassis). If you are deploying multiple DMT cards for this chassis, the system retains the card name 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. |
Table 3-5 defines the fields that are located in the Deployment Wizard—Object Parameters (4xSDSL card) windows.
| Field | Definition |
|---|---|
Number of SDSL Cards | Type the number of 4xSDSL cards you want to deploy for the chassis you selected from the Deployment Wizard—Templates window. The maximum limit is 32. |
Card Name Prefix | Accept the default prefix generated by the software, or type a unique prefix for the card name. The value you enter in the Card Name Prefix field is carried 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 so that it is not included as part of the Card Name field. |
SDSL Card Slot Number | Type the slot number in which the 4xSDSL card will be installed in the Cisco DSLAM chassis. Valid values are 1 to 9 and 12 to 34 (slots 10 and 11 are reserved for 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) remains visible until you enter data for each of the 4xSDSL cards you are deploying. The Deployment Summary window appears 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 type 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, the system 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. |
Table 3-6 defines 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. |
| Field | Definition |
|---|---|
Number of Cisco Flexi Cap Card Objects or Number of Cisco Flexi DMT Card Objects | Type the number of 4xflexi cards you want to deploy for the chassis you selected from the Deployment Wizard—Templates window. The maximum limit is 32. |
Card Name Prefix | Accept the default prefix that is generated by the software, or type a unique prefix for the card name. The value you enter in the Card Name Prefix field is carried 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 so that it is not included as part of the Card Name field. |
Flexi CAP Card Slot Number or Flexi DMT Card Slot Number | Type the slot number in which the 4xflexi card will be installed in the Cisco DSLAM chassis. Valid values are 1 to 9 and 12 to 34 (slots 10 and 11 are reserved for 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 appears 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 type 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. |
Table 3-7 defines the fields that are located in the Deployment Wizard—Object Parameters (8-port IDSL card) windows.
| Field | Definition |
|---|---|
IDSL Card Slot Number | Type the slot number in which the IDSL card will be installed in the Cisco DSLAM chassis. Valid values are 1 to 9 and 12 to 34 (slots 10 and 11 are reserved for NI-2 cards). If you chose to deploy more than one IDSL card in the Number of Cisco IDSL 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 appears 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 type a unique name for the IDSL 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 IDSL cards for this chassis, the system retains the card name you entered for the first IDSL card and adds a digit to the end of the card name (for each subsequent card) to indicate which card you are currently configuring. |
Some element manager features use the Cisco IOS command line interface. Therefore, after you deploy a chassis, and before you can commission a chassis, you must enter the chassis Cisco IOS command line security password information.
You cannot configure a chassis or its objects unless the network manager has provided you with the appropriate command line interface password values. These are set in the Management Information window, IOS/Command Line Security tab.
|
Note The network manager is responsible for changing the Cisco IOS command line security passwords. General users should not change these passwords. |
To enter chassis Cisco IOS command line security information, follow these steps:
Step 2 Select Cisco DSL Manager > Physical > Chassis > Management Information.
The Management Information window appears (Figure 3-10).
Step 3 Verify the information in the Configuration tab, and then click the IOS/Command Line Security tab.
|
Note Refer to the following section for field definitions. |
The Cisco IOS command line security information becomes the active window (Figure 3-11).
Step 4 Enter the Cisco IOS command line security information.
|
Note Refer to the following section for field definitions. |
Step 5 Click Save Locally to save your passwords locally in Cisco EMF/CDM. Click Save to Device to save the passwords on the selected DSLAM.
|
Note When you click the Save to Device button, the information is saved locally and on the device. |
Table 3-8 defines the fields that are located in the Management Information—Configuration tab window (see Figure 3-10).
| Field | Definition | ||
|---|---|---|---|
IP Address | Display only. Shows the IP address of the selected chassis.
| ||
System Name | Display only. Shows the system name. | ||
System Contact | Type the name of the person or persons responsible for the network equipment. | ||
System Location | Type the physical location of the network equipment. | ||
Extra Location Information | Type additional physical location information for the network equipment. |
Table 3-9 defines the fields that are located in the Management Information—IOS/Command Line Security tab window (see Figure 3-11).
| Field | Definition |
|---|---|
User Name | Enter your network user name. This is the name you use to access the software. The user name you enter in this field should match the user name on the Cisco DSLAM. |
Login Password | Enter your login password. This is the password you use to access the software. The login password you enter in this field should match the login password on the Cisco DSLAM. |
Exec Password | Enter your Cisco IOS CLI password. This is the enable password that allows you to configure the elements on the network. The password you enter in this field should match the password on the Cisco DSLAM. |
Before you can begin actively managing the objects on your network, you must commission the objects that you have deployed. After you commission the chassis, the system can collect alarm, performance, and status data for the chassis and the cards within 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). Refer to the "Configuring or Querying Network Components" section for detailed information regarding network object states.
When you commission a chassis, you are making the chassis and all associated objects (cards and interfaces) available to be managed on the network. You can, however, manually commission associated objects after you have already commissioned a chassis, or you can let the system automatically commission the associated objects. For example, if you add a card after you have commissioned a chassis, the chassis will automatically commission itself during the next polling cycle (approximately 20 to 30 seconds).
To commission a DSLAM chassis, follow these steps:
Step 2 Select Cisco DSL Manager > Physical > Chassis > Configuration.
The Chassis Configuration window appears (Figure 3-12).
By default, the Configuration tab is the active window.
Step 3 Click the Commission button.
You can view the commission status (succeeded or failed) at the bottom of the window, in the Commission Status area.
When you click the Commission button, the system performs the following functions:
|
Note Cisco recommends that, after you click the Commission button, you go back to the Physical view to monitor the software as it populates the chassis objects. As the system populates the objects, icons appear in 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 (is not physically present in the chassis and cannot be managed). |
When you commission a chassis, you are making the chassis and all associated objects (cards and interfaces) available to be managed on the network. However, if a card or interface is added to the chassis after you have already commissioned a chassis, you can manually commission that card or interface.
|
Note You can save time by letting the chassis automatically commission its objects during the polling cycles rather than manually commissioning a card or interface. |
You can commission a card from the Configuration window. From this window, you can also enter common language location identifier (CLLI) codes or text descriptions for each card in the chassis.
To open the Configuration window, follow these steps:
The Configuration window appears (Figure 3-13).
Step 2 Select the chassis and card from the list boxes on the left side of the window.
Step 3 Commission or decommission the selected card by clicking the appropriate button.
Step 4 Click Save, or select File > Save, to save all changes.
|
Note You can type CLLI codes, or other text descriptions in the Description 1 and Description 2 fields. The information you enter in these fields is saved in CDM; it is not saved on the hardware. After you enter a description, the system displays the descriptive text each time a user selects the object with which a description is associated. |
You can commission an interface from the Interface Configuration window. You can also view generic configuration information for the selected interface from this window.
To commission an interface, follow these steps:
The Interface Configuration window appears (Figure 3-14).
Step 2 Select the chassis, card, and interface from the list boxes on the left side of the window.
|
Note Refer to the following section for field definitions. |
Step 3 Commission or decommission the selected interface by clicking the appropriate button.
Step 4 Click Save, or select File > Save, to save all changes.
Table 3-10 defines the fields that are located in the Interface Configuration window.
| Field | Definition |
|---|---|
Alias | The secondary name for the interface as specified by the network manager. |
Administration Status | Specifies the state of the interface. Valid values are: Up—The interface is connected to a CPE and is ready to pass packets. Down—The interface is not available to pass packets. Testing—The interface is in testing mode, and is not available to pass packets. |
Link Up/Down Trap Enable | Specifies if link up/down traps should be generated for this interface. |
Supplementary Information | You can type additional information for this interface. |
|
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, the system cannot commission the chassis you are configuring. |
To open the SNMP Management window, follow these steps:
The SNMP Management window appears (Figure 3-15).
Step 2 Select the chassis for which you want to configure SNMP information from the list box on the left side of the window.
Step 3 Configure the SNMP management parameters.
The following section defines the fields in the SNMP Management window.
The SNMP Management window contains four areas of information:
Table 3-11 defines the fields that are located in the SNMP Management window (see Figure 3-15).
| Field | Definition |
|---|---|
V1 Read | If you are using SNMP Version 1, type the name to be used for the read-only relationship. The name you enter here must match the privileges on the Cisco DSLAM. |
V1 Write | If you are using SNMP Version 1, type the name to be used for the read-write relationship. The name you enter here must match the privileges on the Cisco DSLAM. |
V2 Read | If you are using SNMP Version 2, type the name to be used for the read-only relationship. The name you enter here must match the privileges on the Cisco DSLAM. |
V2 Write | If you are using SNMP Version 2, type the name to be used for the read-write relationship. The name you enter here must match the privileges on the Cisco DSLAM. |
SNMP Version | Select the version of SNMP that is running on the selected chassis. Valid selections are V1 and V2C. CDM does not currently support SNMP Version 3. |
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. |
You can delete a Cisco DSLAM chassis or chassis objects from most active windows, or by selecting an object from the left side of the Map Viewer window. When you delete a chassis, you also 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 the system is no longer actively managing the chassis.
To delete a chassis, follow these steps:
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 appears (Figure 3-16).
Step 2 Click Finish to delete the selected chassis, or click Cancel to abort the process.
After you click the Finish button, the system informs you that the deletion was successful.
You can also delete a chassis object in CDM. To delete an object from a chassis, follow the procedures in the preceding section, but select an NI-2 card or line card from the list box rather than a chassis.
|
Note You must first decommission an NI-2 card before you can delete it. You can, however, delete a line card without decommissioning the card. |
Posted: Tue Aug 29 09:00:06 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
