|
|
This chapter describes the tasks you must perform to begin working with the Cisco Element Management Framework (Cisco EMF) and the Cisco Digital Subscriber Line Manager (CDM). These tasks include:
Figure 2-1 details the tasks you should perform to begin working within Cisco EMF and CDM.
Refer to the Cisco Digital Subscriber Line Manager Installation Guide and to the Cisco Element Management Framework Installation Instructions for instructions on installing CDM and Cisco EMF.
To start a CDM session, first you must start a Cisco EMF user session. When you start Cisco EMF, the CDM starts also. Each active Cisco EMF session uses a single Cisco EMF user license.
This section describes how to start a Cisco EMF session.
 |
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 where Cisco EMF Release 3.0 is installed (for example, /opt/cemf3).
The Login window appears (Figure 2-2).
Step 2 Enter your user name and password.
Step 3 Click Ok to proceed.
If you enter an unknown user name or password, an error is displayed. Click Ok, 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 will not start and the Login window closes. |
When you enter a valid user name and the password, the session starts and the
Cisco EMF Launchpad window appears (see Figure 2-3).
The icons displayed in the Cisco EMF Manager frame on the Launchpad represent applications that are provided by this Cisco EMF installation. Extra icons may appear if additional packages are installed. The icons displayed in Figure 2-3 represent the standard Cisco EMF tools.
The Cisco EMF MapViewer application provides flexibility in viewing, building, and monitoring your network using graphical representations of network elements.
Map Viewer is the primary entry point into the CDM. When you launch the Map Viewer, a window appears that corresponds to the highlighted map icon in the hierarchy pane. You can monitor the status of all network elements, or abstractions of elements, contained within the network and you can launch any of the additional applications on the Cisco EMF Launchpad.
To launch the Cisco EMF Map Viewer application, click the Viewer icon (Figure 2-4) or select MapViewer from the menu when using other Cisco EMF applications. Access the menu by right-clicking on a selected object.
Refer to the Cisco Element Management Framework User Guide for further details on the Cisco EMF Map Viewer application.
The Cisco EMF Object Group Manager (Groups) application enables you to organize network elements into object groups.
To launch the Cisco EMF Object Group Manager application, click the Groups icon (Figure 2-5) or select Groups from the menu when using other Cisco EMF applications. Access the menu by right-clicking on a selected object.
Refer to the Cisco Element Management Framework User Guide for further details on the Cisco EMF Object Group Manager application.
Cisco EMF User Access Control enables system administrators to control user access to various features of the system. This is important for security and for efficient and effective network management.
To launch the Cisco EMF User Access Control application, click the Access icon (Figure 2-6) or select Access from the menu when using other Cisco EMF applications. Access the menu by right-clicking on a selected object.
Refer to the Cisco Element Management Framework User Guide for further details on the Cisco EMF User Access Control application.
In Cisco EMF, when a condition (fault) occurs on a managed object in the network, the system is notified immediately. This notification is shown as an event and can be viewed with the Cisco EMF Event Browser.
To launch the Event Browser application, use one of the following three methods:
Refer to the Cisco Element Management Framework User Guide for further details on the Event Browser application.
The Cisco EMF Auto Discovery application allows you to examine the network for IP and SNMP devices and create a managed object for each new device discovered. You can open Auto Discovery from the Cisco EMF Launchpad window or from the menu available on a selected object.
To launch the Cisco EMF Auto Discovery application, click the Discovery icon (Figure 2-8) or select Discovery from the menu when using other Cisco EMF applications. Access the menu by right-clicking on a selected object.
Refer to the Cisco Element Management Framework User Guide for further details on the Cisco EMF Auto Discovery application.
To quit a Cisco EMF user session:
Step 2 A dialog box prompts you to quit the Cisco EMF. Click the Yes button to quit the session.
All active applications are closed and the session terminates.
This section describes three main CDM functions:
In CDM you can deploy objects manually or automatically by using a wizard-style deployment tool. This tool enables you to automatically deploy a network that is created according to the model prescribed by the Cisco EMF. You can deploy objects before the object is physically installed in a Cisco DSLAM in the field. The CDM detects the presence of previously deployed network equipment as soon as that equipment becomes operational. The CDM can auto discover equipment as an alternative to manual deployment.
You have two options when deploying objects in CEMF:
Preprovisioning is a type of deployment. The difference between deployment and preprovisioning is that preprovisioning is performed before the hardware is actually present; deployment is performed when the hardware is present. Preprovisioning allows you to deploy cards within the chassis before they are actually present in the hardware. Also, you can configure the preprovisioned card. For example, if you know a DMT card is forthcoming, you can deploy and preprovision it in a selected chassis and perform all relevant DMT card configuration. When the DMT card becomes physically available, CDM accepts the configuration you have already performed. Preprovisioned objects are not monitored, which means that alarm, status, and performance information are not available on a preprovisioned card.
When the DMT line card is physically installed in the Cisco DSLAM chassis, you can move the card from the preprovisioned state to the commissioned state by clicking Commission. When a preprovisioned card is commissioned, its status changes to Normal. Then you can monitor alarm, status, and performance information on the card.
|
Note You can only deploy preprovisioned DMT line cards when the related Cisco DSLAM chassis and NI-2 card are in a Normal state. |
Producing a manageable Cisco DSLAM in Cisco EMF is a two stage process, as shown in Figure 2-9.
The first stage is chassis deployment. The Cisco DSLAM chassis can be manually deployed or it can be auto discovered (refer to the "Using Auto Discovery" section).
The second stage of the deployment process is to deploy the Cisco DSLAM objects at subchassis level. This involves auto-discovering the subchassis objects and/or deploying additional sub chassis objects manually.
You can manually deploy a Cisco DSLAM chassis from the Map Viewer application in the CDM Manager view.
To manually deploy a Cisco DSLAM chassis under a site:
Step 2 Select the option for the chassis type you want to deploy (for example, Cisco 6260 or Cisco 6130), then click Forward.
The Deployment Wizard---Object Parameters window appears (Figure 2-11).
Step 3 Enter the number of DSLAM units (number of chassis you want to deploy) and a prefix for the unit name. You can accept the default prefix or create your own. Click Forward.
The Deployment Wizard---Object Parameters window appears (Figure 2-12).
Step 4 Enter the IP address of the chassis under the Object Parameters area.
Step 5 Enter the SNMP Read/Write Communities and SNMP Version.
Step 6 Enter a Chassis Name. The chassis must have a unique name. Click Forward.
The Deployment Wizard---Summary window appears (Figure 2-13).
Step 7 The Summary window summarizes the deployment you have just created and enables you to commit or reject the deployment. When you deploy a chassis, a shelf object is also created, thus deploying two objects (see Figure 2-13). To commit the deployment, click Finish. A feedback window indicates whether or not deployment is successful. To reject the deployment, click Cancel.
You can commission a chassis to begin actively managing that chassis and the cards contained within the chassis (if applicable). After you commission the chassis, alarm, performance, and status data can be collected or received 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 hardware is not detected in the chassis).
To commission a DSLAM chassis within the Map Viewer, right-click the chassis object you want to commission and select Cisco DSL Manager > Physical > Chassis > Configuration. Click the Commission button to activate commissioning. When you commission a chassis, the sub-rack discovery begins, which discovers all cards within the chassis and commissions them if possible. Use this option when you have a newly deployed system because sub-rack discovery can deploy and commission several cards at one time. If you want to deploy and commission one card or a few, you may want to manually deploy those cards instead. To do so, manually commission each chassis and card.
To decommission the chassis, click the Decommission button. When you decommission the chassis, all objects within the chassis are also decommissioned.
After you deploy the chassis object, you can begin deploying the cards within the chassis. You can deploy an NI-2 card either by sub-rack discovery (refer to the "Commissioning or Decommissioning a Cisco DSLAM Chassis" section for details) or by manual deployment. This section describes how to manually deploy an NI-2 management card.
The Deployment Wizard---Templates window appears (Figure 2-14).
Step 2 Select the type of NI-2 card (DS3 or OC-3) and select the type of Cisco DSLAM chassis under which you want to create an NI-2 card. Click Forward.
The Deployment Wizard---Object Parameters window opens (Figure 2-15).
Step 3 Enter the number of NI-2 management cards you want to deploy. You can also change the card name prefix, if desired. Click Forward.
The Deployment Wizard---Object Parameters window appears (Figure 2-16).
Step 4 Type the slot number (you must enter 10 or 11) where you want to place the NI-2 management card. Type a card name (this name must be unique). Click Forward.
The Deployment Wizard---Summary window appears (Figure 2-17).
The Deployment Summary window summarizes the deployment that you have performed and prompts you to commit or reject the deployment. When you deploy an NI-2 management card, interfaces representing the ports on the NI-2 card are automatically created as well. If you are deploying an OC-3 NI-2, then two OC-3 interfaces are deployed, representing the two OC-3 ports on the NI-2 card. If you are deploying a DS3 NI-2, then three DS3 interfaces are deployed, representing the three DS3 ports on the NI-2 card. Therefore, three or four objects are deployed.
Step 5 To commit the deployment, click Finish. A feedback window informs you if the deployment is successful or not. To reject the deployment, click Cancel.
You can manually commission an NI-2 management card in the Configuration window. If you have commissioned the chassis object, and the sub-rack discovery has located the NI-2 card, it also commissions the NI-2 card. In this case, you do not need to commission it manually.
To commission or decommission an NI-2 card:
The Configuration window appears (Figure 2-18).
|
Note You can use this process to commission or decommission a DMT line card also. Right-click a DMT line card instead of an NI-2 card, as described in Step 1. |
Step 2 Click the Commission or Decommission button.
To manually deploy a DMT line card under a Cisco DSLAM chassis:
The Deployment Wizard---Templates window appears (Figure 2-19).
Step 2 Select either the Create DMT Card under 6260 Chassis or the Create DMT Card under 6130 Chassis option. Click Forward.
The Deployment Wizard---Object Parameters window appears (Figure 2-20).
Step 3 Enter the number of DMT cards you want to deploy. You can change the card name prefix, if desired. Click Forward.
The Development Wizard---Object Parameters window appears (Figure 2-21).
Step 4 Type the slot number where you want to place the DMT card. Name the DMT card (the name must be unique.) Click Forward.
The Deployment Wizard---Summary window appears (Figure 2-22).
The Deployment Summary window summarizes the deployment that you have performed and gives you the option to commit or reject the deployment. When you deploy a DMT line card, four DMT interfaces are automatically deployed as well, representing the four ADSL ports on a DMT card. Therefore, a total of five objects are deployed.
Step 5 To commit the deployment, click Finish. A feedback window informs you if the deployment is successful or not.To reject the deployment, click Cancel.
When you commission or decommission a DMT line card, all interfaces on that line card are also commissioned or decommissioned. Refer to the "Commissioning or Decommissioning an NI-2 Management Card" section for details. If you want to commission or decommission a DMT interface individually, refer to the following section.
To individually commission or decommission a DMT interface:
The Interface Configuration window appears (Figure 2-23).
Step 2 Click the Commission or Decommission button.
Auto Discovery discovers any Cisco DSLAMs using either IP or SNMP identifiers. When Auto Discovery finds a DSLAM chassis, it creates a chassis object. After a chassis is detected, an object representing a chassis is created and placed under the path 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 multi-hop discovery. You can schedule multi-hop discovery to run at preset times (the Cisco EMF user guide describes how to set the schedules). You can also specify the physical location under which you want the discovered objects created.
To access Auto Discovery, right-click an object and select Deployment > Auto Discovery.
The Auto Discovery application has three different mechanisms for discovering devices:
1. IP---ICMP pings are sent to IP addresses within a given IP address range. If a response is received on an ICMP ping, an object is created; if no response is received, no object is created.
2. SNMP---SNMP get requests are sent to IP addresses in a given IP address range. Several SNMP community strings can be used so that equipment with different community strings are discovered in the same discovery session. Based upon the SNMP information returned for devices, Cisco EMF decides whether or not the device is a DSLAM. If the device is a DSLAM, an object is created. If the device is not a DSLAM, no object is created.
3. IP and SNMP --- ICMP pings are sent out to find devices. If a device is found, SNMP get requests are sent out and based on the information they receive, Cisco EMF decides whether or not the device is a DSLAM. If the device is a DSLAM, an object is created; if the device is not a DSLAM, no objects are created. This is the default mechanism.
|
Note ICMP abbreviates Internet Connection Management Protocol; SNMP abbreviates Simple Network Management Protocol. |
Refer to the Cisco Element Management Framework User Guide for further information on using Auto Discovery.
The overall status of a selected object appears at the bottom left corner of each window as one of the following:
The state of each object directly affects the operations you can perform on that object. By default, the window refreshes every 10 seconds, displaying any updated states.
In the Normal state, the CDM polls the device to detect whether or not objects are present. When an object enters the Normal state, the CDM polls the object every 60 seconds to determine if it is present. When you click the Commission button on an object, that object is placed into the Normal state.
When you have started performance logging on a card or interface, the state of that object changes from Normal to Perf Monitoring. This shows you that the selected card or interface has performance logging enabled, so that performance data can be collected on the object and viewed either in the Performance windows or the Performance Manager.
If the status is Errored, none of the displayed values can be queried. For example, if a chassis becomes unreachable for some reason, the chassis state changes to Errored.
When you want to replace an existing card or perform any kind of maintenance work on an object, you should first decommission that object.
When you decommission an object:
Decommission buttons are located within certain windows, depending on the type of object selected. When you decommission an object, the children of that object also change their status to decommissioned. However, interfaces cannot be decommissioned.
Preprovisioning is a type of deployment. The difference between deployment and preprovisioning is that preprovisioning is performed before the hardware is actually present; deployment is performed when the hardware is present. Preprovisioning allows you to deploy cards within the chassis before they are actually present in the hardware. Also, you can configure the preprovisioned card. For example, if you know a DMT line card is forthcoming, you can deploy and preprovision it in a selected chassis and perform all relevant DMT card configuration. When the DMT card becomes physically available, CDM accepts the configuration you have already performed. Preprovisioned objects are not monitored, which means that alarm, status, and performance information are not available on a preprovisioned card.
When the DMT line card is physically installed in the Cisco DSLAM chassis, Cisco EMF automatically detects it and commissions the DMT card, changing it to the Normal state. However, you can also manually move the DMT line card from the preprovisioned state to the commissioned state by clicking the Commission button. When a preprovisioned card is commissioned, its status changes to Normal. Now you can monitor alarm, status, and performance information (if performance logging is selected) on the card.
|
Note You can deploy preprovisioned DMT line cards only when the related Cisco DSLAM chassis and NI-2 card are in a Normal state. |
Posted: Mon Jul 31 05:53:34 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.