|
|
This chapter describes the tasks you need to start 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 Cisco EMF, but focuses mostly on the CDM GUI.
This chapter includes the following sections:
Table 3-1 lists the steps that you need to accomplish to start running CDM and related documentation.
| Step | Task | Cisco Document Reference |
|---|---|---|
Step 1 | Install Cisco EMF (you must do this before you install CDM. | Cisco Element Management Framework User Guide |
Step 2 | Start Cisco EMF (you must do this before you install the CDM). Do not begin a user session at this time. | Cisco Element Management Framework User Guide |
Step 3 | Install CDM. | Cisco CDM NI-2 Installation Notes |
Step 4 | Start a Cisco EMF user session. When you start a Cisco EMF user session, CDM automatically starts. | Cisco Element Management Framework User Guide |
Step 5 | Deploy a site from which Cisco DSLAMs, and the chassis objects, are to be managed. | Cisco Element Management Framework User Guide |
Step 6 | Deploy Cisco DSLAM chassis and chassis objects through a combination of Cisco EMF and CDM functions. | Cisco Element Management Framework User Guide Cisco 6015 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 6015 Element Manager User Guide |
Step 8 | Commission a chassis so the software can actively manage the chassis and the objects within the chassis. | Cisco 6015 Element Manager User Guide |
Step 9 | Set up subscribers; upload profiles, configure, and apply profiles. | Cisco 6015 Element Manager User Guide |
Step 10 | Begin to manage Cisco DSLAM objects—view alarms, status, current and historical data, and manage inventory of network objects. | Cisco 6015 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. |
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, which is shown in Figure 3-1, opens.
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.
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, which is shown in Figure 3-2.
For more information about using the Launchpad, see the "Using the Cisco EMF Launchpad" section.
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 include
These two main steps are described in the sections that follow.
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 choose the Deploy option, you open the Deployment Wizard window, which guides you through the deployment 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 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 the 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. |
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 3-3 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 (refer to "The Autodiscovery Process" section).
3. Deploy DSLAM chassis objects either by
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. You manually deploy a DSLAM chassis through the Deployment Wizard window.
To manually deploy a Cisco DSLAM chassis under a site, complete the following steps.
|
Note Make sure the generic site is already deployed. |
Step 2 Choose Deployment > Deploy Cisco DSLAM.
The Deployment Wizard—Templates window opens, which is shown in Figure 3-4.
Step 3 Click Create 6015 Chassis under user named shelf, and then click Forward.
The Deployment Wizard—Object Parameters window opens, which is shown in Figure 3-5.
Step 4 Enter the appropriate number in the two fields on this window, and then click Forward to proceed.
The next Deployment Wizard—Object Parameters window opens, which is shown in Figure 3-6.
Step 5 Enter the appropriate information in the fields on this window, as follows:
a. Enter the number of DSLAM chassis you want to deploy in the Number of DSLAM Units field.
|
Note Cisco recommends that you deploy one chassis at a time. |
b. In the Prefix for Unit Name field, accept the default prefix generated by the software, or enter a unique prefix for the unit name.
c. In the Chassis IP Address field, enter the valid IP address for the chassis you are deploying; the maximum alphanumeric limit is 15 characters.
d. 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.
|
Note The default entry might not match the Cisco DSLAM privileges; be sure to enter a name that matches the SNMP community read string. |
e. 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.
|
Note Do not use the default entry. It might not match the Cisco DSLAM privileges. |
f. In the SNMP Version field, enter the version of SNMP that is running on the equipment in the Chassis IP Address field.
g. In the Chassis Name field, use the default chassis name (that is generated as a result of your entry in the Prefix for Unit Name field) or enter a unique name for the chassis you are deploying.
After you configure the parameters on the Deployment Wizard—Object Parameters window, the Deployment Wizard Summary window opens, which is shown in Figure 3-7.
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 3-7).
Step 6 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, a the Deployment Wizard—Summary window informs you that the deployment failed.
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.
To manually deploy an NI-2 card, follow these steps:
Step 2 Choose Deployment > Deploy Cisco DSLAM from the object menu.
The Deployment Wizard—Templates window opens, which is shown in Figure 3-8.
Step 3 Click Create OC3 NI2 Card under 6015 chassis or Create DS3 NI2 Card under 6015 Chassis, then click Forward to continue.
The Deployment Wizard—Object Parameters window opens.
Step 4 Enter the information in the fields on the Deployment Wizard—Object Parameters window as follows:
a. In the Number of NI-2 Cards field, enter the number of NI-2 cards that you want to deploy for this chassis; valid values are 1 and 2.
b. In the Card Name Prefix field, accept the default prefix, or enter a unique prefix for the card name.
|
Note 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. |
c. In the NI-2 Card Slot Number (10 or 11) field, enter the slot number in which the NI-2 card is installed in the Cisco DSLAM chassis; valid values are 10 and 11.
d. 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 NI-2 card.
|
Note If you are deploying more than one NI-2 card, the software automatically increments the values in the fields in the second Deployment Wizard—Object Parameters window to indicate the card that 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. |
Step 5 Click Forward to continue.
The Deployment Wizard Summary window opens, which is shown in Figure 3-9.
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 6 To commit the deployment, click Finish; to reject the deployment, click Cancel.
A feedback window informs you if the deployment is successful.
When you deploy a 4DMT line card, you are configuring the parameters for that line card. This section describes how to deploy a 4DMT line card.
To manually deploy a line card in a Cisco 6015 chassis, follow these steps:
Step 2 Choose Deployment > Deploy Cisco DSLAM from the object menu.
The Deployment Wizard—Templates window opens, which is shown in Figure 3-10.
Step 3 Click Create DMT Card under 6015 Chassis, and then click Forward.
The Deployment Wizard—Object Parameters window opens.
Step 4 Enter the appropriate information in the Deployment Wizard—Object Parameters window, as follows:
a. In the Number of DMT Cards field, enter the number of DMT cards that you want to deploy for this chassis; the maximum number is 32.
b. In the Card Name Prefix field, accept the default prefix, or enter a unique prefix for the card name.
c. In the DMT Card Slot Number field, enter the slot number in which the DMT card will be installed in the Cisco DSLAM chassis.
d. 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 DMT card.
Step 5 Click Forward to continue.
|
Note If you are deploying more than one 4DMT 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, which is shown in Figure 3-11.
The Deployment Wizard Summary window prompts you to commit or reject the deployment.
Step 6 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, 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 automatically deploy. Therefore, multiple objects may deploy for a line card. |
Some element manager applications use the Cisco IOS command line interface (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.
You can only configure a chassis or its objects if the network manager provides you with the appropriate CLI password values. These values are set in the Management Information window, IOS/Command Line Security tab.
|
Note Only 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 Choose Cisco DSL Manager > Physical > Chassis > Management Information from the object menu.
The Management Information window opens, which is shown in Figure 3-12.
Step 3 Verify the information in the Configuration tab, and then click the IOS/Command Line Security tab.
Step 4 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.
|
Note Do not change the chassis IP address from this window. |
b. In the System Name, verify the name of the system; this field is read only.
c. In the System Contact field, enter the name of the person or persons who are responsible for the network equipment; this field is read only.
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.
The IOS Command Line Security tab, which is shown in Figure 3-13, becomes active.
Step 5 Enter the Cisco IOS command line security information as follows:
a. In the User Name field, enter your network user name.
b. In the Login Password field, enter your login password.
c. In the Exec Password field, enter your Cisco IOS CLI password.
Step 6 Click Save Locally to save your passwords locally in Cisco EMF and CDM.
Step 7 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. |
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 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" section for more information about network object states.
The following sections includes instructions for commissioning chassis, cards, and interfaces (ports).
When you commission a chassis, the chassis and all 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 the system 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 2 Choose Cisco DSL Manager > Physical > Chassis > Configuration from the object menu.
The Chassis Configuration window opens, which is shown in Figure 3-14. The Chassis Configuration window opens to the Configuration tab.
Step 3 Click Commission.
You can view the commission status (succeeded or failed) at the bottom of the window, in the Commission Status area.
When you click Commission, the system performs the following functions:
|
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 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, that is, not physically present in the chassis and therefore not able to be managed. An example of this view is shown in Figure 3-15. |
When you commission a chassis, the chassis and all 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 or interface.
|
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 2 Choose Cisco DSL Manager > Physical > Module > Configuration from the object menu.
The Configuration window opens, which is shown in Figure 3-16.
Step 3 Select the chassis and card from the list box on the left side of the window.
Step 4 Click Commission to commission the card, or click Decommission to decommission the card.
Step 5 Click Save on the toolbar, or select File > Save.
|
Note You can enter 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 but not 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 (line card port) from the Interface Configuration window. You can also view generic configuration information for the selected interface on this window.
To commission an interface, follow these steps:
Step 2 Choose Cisco DSL Manager > Physical > Interface > Generic > Configuration from the object menu.
The Interface Configuration window opens, which is shown in Figure 3-17.
Step 3 Select the chassis, card, and interface from the list boxes on the left side of the window.
Step 4 Enter the appropriate information in the Configurable Parameters fields, as follows:
a. In the Alias field, enter the secondary name for the interface as specified by the network manager.
b. In the Administration Status field, use the down arrow to select from the following choices that specify the state of the interface.
c. In the Supplementary Information, you can enter additional information for this interface.
Step 5 Click Commission to commission this interface.
Step 6 Click Decommission to decommission this interface.
Step 7 Click Save in the toolbar, or select File > Save, to save all changes.
On 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). You must set SNMP information when you deploy a chassis or the system 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 2 Choose Cisco DSL Manager > Physical > Chassis > SNMP Management from the object menu.
The SNMP Management window opens, which is shown in Figure 3-18.
Step 3 Select the chassis for which you want to configure SNMP information from the list box on the left side of the window.
The SNMP Management window contains four areas of information:
Step 4 Configure the SNMP management parameters as follows:
a. If you are using SNMP Version 1, in the V1 Read field, enter the name to be used for the read-only relationship; the name you enter here must match the privileges on the Cisco DSLAM.
b. If you are using SNMP Version 1, in the V1 Write field, enter the name to be used for the read-write relationship; the name you enter here must match the privileges on the Cisco DSLAM.
c. If you are using SNMP Version 2, in the V2 Read field, enter the name to be used for the read-only relationship; the name you enter here must match the privileges on the Cisco DSLAM.
d. If you are using SNMP Version 2, in the V2 Write field, enter the name to be used for the read-write relationship; the name you enter here must match the privileges on the Cisco DSLAM.
e. In the SNMP Version field, select the version of SNMP that is running on the selected chassis.
f. In the Trap Generation field, click Enable or Disable.
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:
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, which is shown in Figure 3-19.
Step 3 Click Finish to delete the selected chassis, or click Cancel to abort the process.
After you click Finish, the system informs you whether 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 "Deleting a Chassis" 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 Sep 5 09:20:08 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
