|
|
This chapter describes how to begin using Cisco Digital Subscriber Line Manager (CDM) to manage your Cisco 6100/6130 DSLAM chassis system. To run CDM, you must first launch Cisco EMF. Next you must deploy and then commission the DSLAM chassis and modules. Alternatively, you can have CDM autodiscover the Cisco 6100/6130 DSLAM chassis. CDM discovers the equipment configuration during the commissioning process. If anyone using the system makes changes to the system configuration through an application or command line interface other than CDM, CDM is unable to reflect these changes until you synchronize the system.
This chapter includes the following sections:
 |
Note Refer to the Cisco Element Management Framework User Guide for more detailed information and instructions about using the Cisco EMF application. |
|
Note Refer to the Cisco DSL Manager Installation Notes and the Cisco Element Management Framework Installation and Administration Guide for instructions on installing CDM and Cisco EMF. |
"Using CDM," describes how to launch Cisco EMF and CDM, open the Map Viewer window and the CDM Manager and Physical hierarchy views. Before managed elements can display in the Map Viewer, however, you must deploy and synchronize a Cisco 6100 Series DSLAM chassis.
This section describes how to get started using CDM and includes the following topics:
You can deploy CDM objects manually or automatically. Manual deployment is a good option if you do not have many objects to discover. This section first describes how to automatically deploy and commission your system, and second, describes how to manually deploy a chassis and modules.
A deployment wizard automatically deploys a network that is modeled in Cisco EMF. When you choose either Deployment or Deploy Cisco 6100 ADSL from the option menu, the deployment wizard automatically opens and guides you through the deployment process. The deployment wizard deploys objects in Cisco EMF in advance of actual deployment on a Cisco DSLAM chassis in the field. CDM detects the presence of previously deployed network equipment as soon as that equipment is operational. CDM autodiscovers equipment as an alternative to manual deployment.
Autodiscovery perceives existing networks, which saves the time and effort involved in manually discovering networks. Autodiscovery queries the network for IP and SNMP devices, and creates an object for each new device that it discovers. Autodiscovery is the most effortless way to discover Cisco DSLAMs that are already installed. See the "Autodiscovery" section for more information about the autodiscovery process.
Preprovisioning is a way to configure a module before you deploy a DSLAM chassis. For example, if you know that you are going to use CAP modules in a chassis, you can set all of the relevant configurations on that CAP-ADSL module. When the CAP-ADSL module becomes physically available, it assumes all of the configuration information that you have already created.
The network monitors a preprovisioned object only after it is commissioned; that is, alarm, status, and performance information are unavailable on a preprovisioned module. CDM commissions or decommissions a parent chassis when you click the Commission or Decommission button on the System/Commission/Decommission/Config Sync Window window. When you physically insert a module into a slot in the parent chassis, the node notifies CDM via a trap. When CDM receives the trap, it moves the module from preprovisioned state to commissioned state.
When the node detects a preprovisioned module, the status of that module changes to Enabled and Equipped. You can then monitor the module; it is a real, existing module.
|
Note You can only deploy preprovisioned modules when the related Cisco DSLAM chassis and NI-1 module are in a Normal state. |
Setting up management for a Cisco DSLAM in Cisco EMF is a two-stage process. The first stage is chassis deployment. You can manually deploy the Cisco DSLAM chassis or you can autodiscover it, as described in the "Autodiscovery" section.
The second stage of the deployment process is to deploy the Cisco DSLAM objects at the subchassis level. This second stage involves autodiscovering the subchassis objects and then manually deploying additional subchassis objects. See the "Manually Deploying Modules" section for instructions on deploying all supported modules.
A diagram of the deployment process is shown in Figure 2-1.
You can manually deploy a Cisco DSLAM chassis from the Map Viewer window. To manually deploy a Cisco DSLAM chassis under a site, complete the following steps:
Step 2 Choose Deployment > Deploy Cisco 6100 ADSL from the object menu.
The Deployment Wizard—Templates window, which is shown in Figure 2-2, opens.
Step 3 Select NI-1 Chassis Deployment and click Forward.
The Deployment Wizard—Object Parameters window, which is shown in Figure 2-3, opens.
Step 4 Enter the appropriate number in the Number of NI-1 DSLAMs to be deployed field, and then click Forward.
For example, enter 1 in these fields if you are creating and deploying only one DSLAM chassis.
The next Deployment Wizard—Object Parameters window, which is shown in Figure 2-4, opens.
Step 5 Enter the appropriate information in the fields on this window, as follows:
a. Enter the IP address for the chassis that you are deploying in the Ethernet IP Address field.
b. Leave the default, public, for the SNMP V1 Read Community field.
c. Leave the default, private, for the SNMP V1 Write Community field.
d. Leave the default, public, for the SNMP V2 Read Community field.
e. Leave the default, private, for the SNMP V2 Write Community field.
f. Leave the default, snmpv1, for the SNMP Version field, or select snmpV2c, or snmpV3.
g. In the C6100v30TrapMgmt name field, enter a name for the chassis that you are deploying, for example, C6100v30TrapMgmt-DirectConnect-NI-1.
|
Note The C6100v30TrapMgmt object is deployed only in the hidden SNMPTrapMapper view; therefore it will be invisible to you. |
Step 6 Click Forward to continue.
The Deployment Wizard—Object Parameters window, which is shown in Figure 2-5, opens.
Step 7 Enter the IP address again in the IP Address field.
Step 8 Enter the name of the managed element in the C6100v30ManagedElement name field.
Step 9 Click Forward to continue.
The Deployment Wizard—Views window, which is shown in Figure 2-6, opens.
Step 10 Click Select next to Physical to select the physical relationship.
This option sets the site for the DSLAM.
The Object Selector window, which is shown in Figure 2-7, opens.
Step 11 Choose the physical site, then click Apply.
You use this window to set up the physical sites that contain one or more managed DSLAMS.
The Object Selector window closes, returning you to the Deployment Wizard—Views window. The site that you selected in the Object Selector window displays in the Physical field on the next Deployment Wizard—Views window, which is shown in Figure 2-8.
The Deployment Wizard—Summary window, which is shown in Figure 2-9, opens and displays a summary of the deployment instructions that you have entered.
Step 12 Click Finish to deploy the chassis.
When the deployment process is complete, the Deployment Wizard—Results window informs you of the results of the deployment process. On the left side of the Map Viewer window, in the Physical hierarchy view, which is shown in Figure 2-10, you can see the results of the deployment process.
Step 13 Click Finish to close the Deployment Wizard.
On the left side of the Map Viewer window, the chassis that you deployed displays in both the C6100v30Mgr hierarchy view and the Physical hierarchy view. If you already have modules in place in a chassis, after you commission and synchronize the chassis, the modules also appear under these views. Procedures to deploy modules are described in the "Manually Deploying Modules" section.
If you click C6100v30ManagedElement—[Name of chassis] from the C61xxChassisView hierarchy view on the left side of the Map Viewer window, a shaded graphical representation of the chassis displays, as shown in Figure 2-11.
The chassis graphic stays dimmed until you commission it, which is described in "Commissioning and Decommissioning a Cisco DSLAM Chassis" section.
This section includes the following topics:
You can commission a chassis to begin actively managing that chassis and the modules that are contained within the chassis (if applicable). Once you commission the chassis, CDM begins to collect and receive alarm, performance, and status data for the chassis and its modules. The initial status of a commissioned chassis is normal. The initial status of a commissioned chassis is normal. The initial status for a commissioned module is either disabled and provisioned if CDM does not detect the physical module hardware in the chassis, or enabled and equipped if CDM does detect the module.
To commission a DSLAM chassis within the Map Viewer window, follow these steps:
Step 2 Choose Open System/Commission/Decommission/Config sync Dialog from the object menu.
The System/Commission/Decommission/Config sync Dialog window, which is shown in Figure 2-12, opens.
Step 3 Click Commission to activate commissioning.
Step 4 Click Yes in the confirmation dialog box to proceed.
When you commission a chassis, CDM begins subrack discovery, and discovers all of the modules within the chassis and commissions them. This process is efficient for a newly deployed system because subrack discovery can deploy and commission several modules at a time.
After you have completed commissioning the DSLAM, the graphical chassis view on the right side of the Map Viewer window is no longer dimmed. To synchronize the chassis with any modules that are present in the hardware, complete the following steps. The System/Commission/Decommission/Config sync Dialog window, which is shown in Figure 2-12, should still be open.
Step 2 Click Synchronize in the System/Commission/Decommission/Config sync Dialog window.
Step 3 Click Yes in the confirmation dialog box.
Wait a few minutes for Cisco EMF and CDM to synchronize the node with the GUI. The status displays at the bottom of the System/Commission/Decommission/Config sync Dialog window. After synchronization is complete, an Action Report window, which is shown in Figure 2-13, opens to inform you whether the process succeeded or failed.
Step 4 Click Close to close the Action Report window, or click Save to save this information to a log file.
When you need to take a DSLAM for maintenance or have another break in service, you may need to decommission the chassis.
To decommission a DSLAM chassis from the Map Viewer window, follow these steps:
Step 2 Choose Open System/Commission/Decommission/Config Sync from the object menu.
The System/Commission/Decommission/Config Sync window, which is shown in Figure 2-14, opens.
Step 3 Click Decommission to activate decommissioning.
|
Note When you decommission the chassis, CDM decommissions all of the objects within that chassis. |
After you complete chassis deployment and then commission the system, any modules that are present in a chassis are also commissioned. The most efficient way to predeploy a module is from the Create Module dialog (on Mux Chassis) window. You access this window by right-clicking C6100v30MultiplexerChassis from the left side of the Map Viewer window and choosing Open Create Module on Mux Chassis Dialog from the C6100v30MultiplexerChassis object menu. (See the "Steps to Preprovision a Module" section for the instructions on creating modules from this window.)
However, you can also use the Deployment Wizard—Templates window to manually deploy and commission the following types of modules:
|
Note The illustrations in this section show example windows that open when you manually deploy a module. The example windows show various types of modules previously listed that you can deploy through the Deployment Wizard. However, the procedure for deploying these different types of modules follow the same basic steps. |
Complete the following steps to deploy a module using the Deployment Wizard.
Step 2 Choose Deployment > Deploy Cisco6100ADSL.
The Deployment Wizard—Templates window, shown in Figure 2-15, opens.
Step 3 Select the type of module that you want to create from the list to access the template for that type of module, and then click Forward.
In this example, the Deploy ATUC CAPADSL under Mux Chassis choice is highlighted; the user here is deploying an ATU-C module.
The Deployment Wizard—Object Parameters window, which is shown in Figure 2-16, opens.
Step 4 Enter the Number of [c6100v30ATUCModule]Objects in this field.
Step 5 Enter the Chassis Index in this field.
Step 6 Click Forward.
The next Deployment Wizard—Object Parameters window, which is shown in Figure 2-17, opens.
|
Note The fields on this window vary slightly from the one shown in Figure 2-17, depending on which type of module you are deploying. |
Step 7 Enter the applicable information in the fields on this window, as follows:
b. Enter the IP address in the IP Address field.
c. Leave the default, public, for the SNMP V1 Read Community field.
d. Leave the default, private, for the SNMP V1 Write Community field.
e. Leave the default, public, for the SNMP V2 Read Community field.
f. Leave the default, private, for the SNMP V2 Write Community field.
g. Leave the default, snmpv1, for the SNMP Version field, or select snmpV2c, or snmpV3.
Step 8 Click Forward to continue.
For some modules, the Deployment Wizard—Views window opens, in which you can specify the physical map and the C6100v30Multiplexer Chassis from which you want CDM to manage this module object.
Step 9 If the Deployment Wizard—Views window opens, click Select to open the Object Selector window and choose the object manager entity for this module.
When you have completed entering information in all of the relevant windows, the Deployment Wizard—Summary window, shown in Figure 2-19, opens.
The Deployment Wizard—Summary window summarizes the deployment options that you have specified. You can commit to or reject the deployment.
Step 10 To commit the deployment, click Finish.
A message dialog box informs you whether the deployment is successful.
Step 11 To reject the deployment, click Cancel.
This section describes how the software automatically discovers network elements and includes the following topics:
Autodiscovery discovers and commissions any Cisco DSLAMs with either IP or SNMP identifiers. When CDM locates a DSLAM chassis, it creates a chassis object. Once CDM detects a chassis, it creates an object that represents this chassis and places it within the path that you selected in the Auto Discovery window (under Use Physical Path). A map of the chassis is also created.
Auto Discovery can discover devices on more than one subnetwork by using multihop discovery. You can schedule multihop discovery to run at preset times (the Cisco Element Manager Framework User Guide details how to set the schedules). You can also specify the physical location under which discovered objects will be created.
The Auto Discovery application has three different mechanisms for discovering devices:
To begin autodiscovery, follow these steps:
Step 2 Choose Deployment > Auto Discovery.
The Discover Network Devices window, which is shown in Figure 2-20, opens.
Step 3 In the Discovery Configuration group box, leave or enter the appropriate information in the following fields:
c. Discovery Method—Choose IP and SNMP
e. IP Configuration—Specify the number of times to retry pings
f. If you choose IP and SNMP discovery (the recommended choice), enter or verify the information in the SNMP Configuration fields.
Step 4 In the Physical Location field, select Use Physical Path.
Step 5 If you need to change the path that displays in this field, click Get Path to browse to the correct path.
Step 6 If you want to choose a specific part or section of a network, click Refine Range.
The Discovery Interface window, which is shown in Figure 2-21, opens.
Step 7 Enter the IP address for a specific network section in the Start Address and End Address fields, and then click OK.
The Discovery Interface window closes.
Step 8 Click Start at the bottom of the Discover Network Devices window to begin the autodiscovery process.
The Discovery Process window, shown in Figure 2-22, opens.
This window displays the progress of the autodiscovery process.
Step 9 Click Stop and then Close when you want to stop the process or when the process completes.
You preprovision a module before the hardware is actually present in the Cisco 6100 Series system. Whereas, you deploy a module when the hardware is present. In other words, you can use the preprovisioning feature to deploy modules within the chassis before you place them into the chassis.
You can also configure the preprovisioned module. For example, if you plan to populate a chassis with a DMT line card, you can deploy and preprovision this type of module in a selected chassis and perform all relevant DMT module configurations. When the DMT card becomes physically available, CDM accepts the configuration that you have already created. CDM does not monitor preprovisioned objects; alarm, status, and performance information are not available on a preprovisioned module
After you physically install a module in the Cisco DSLAM chassis, Cisco EMF automatically detects the module and commissions it, moving it into the equipped and operational state. When CDM commissions a preprovisioned module, the status of the module changes to preprovisioned. At that time, you can monitor alarm, status, and performance information (if performance logging is enabled) on the module.
|
Note You can deploy preprovisioned modules only when the related Cisco DSLAM chassis and NI-1 card are in a Normal state. |
Complete these steps to preprovision a module.
Step 2 Choose Open Create Module on MUX Chassis Dialog to open the Create Module dialog (on Mux Chassis) window, shown in Figure 2-23.
Step 3 Enter the slot number in the Slot Index field.
Step 4 In the Board Type field, select one of the following types of modules:
Step 5 In the FlexATU-C Specific Data group box, FlexATU-C Line Code field, choose CAP or DMT2.
Step 6 In the ATU-C Specific Data group box, ATU-C Line Code field, choose CAP or DMT2.
Step 7 In the NI Module specific Data group box, Interface Type field, choose OC3C or DS3.
Step 8 Click Create New Module.
A confirmation dialog box opens asking if you want to create a new module with the specified data.
Step 9 Click Yes to create the module.
An Action Report window opens to inform you whether the create process succeeded.
Step 10 Click Close to close this window.
The overall state of a selected object displays at the bottom left corner of each window. The state of each object directly affects the operations that you can perform on that object. By default, the window refreshes every 10 seconds, displaying any updated states. The states are described in Table 2-1.
Posted: Wed Jan 8 09:56:50 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
