|
|
This chapter describes the key features of the Element Management (EM) component of the Cisco 6260 DSL Manager (CDM).
The Element Management component of the CDM provides the following key features.
Figure 3-1 shows the CDM tasks you must perform to get started and the order in which you should perform them.
To launch the Element Management Graphical User Interface (GUI) screens, select the relevant option from the drop down menus available on a map node, an object in the Object Manager or from an object pick list on an open Element Management GUI screen. Table 3-1 details the Element Management GUI screens that can be launched from which object or map types:
| Task | Launch Point | |||||||
| Manager | Site | Shelf | Chassis | NI2 Card | NI2-OC3 Port | Line Card | ADSL Line Card Port | |
Open Map For Object | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Open Configuration Screen | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Open Event Browser | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Open Chassis Inventory | No | Yes | No | Yes | No | No | No | No |
Open ATM Traffic Descriptor Configuration | No | Yes | No | Yes | Yes | No | No | No |
Open DMT Profiles | No | Yes | No | Yes | Yes | No | No | No |
Open DMT Port Configuration | No | Yes | No | Yes | No | No | Yes | Yes |
Open OC3 Port Status | No | Yes | No | Yes | Yes | Yes | No | No |
Open OC3 Port Performance | No | Yes | No | Yes | Yes | Yes | No | No |
Open NI2 Status | No | Yes | No | Yes | Yes | No | No | No |
Open NI2 Inventory | No | Yes | No | Yes | Yes | No | No | No |
Open Line Card Inventory | No | Yes | No | Yes | No | No | Yes | No |
Open ADSL Line Status | No | Yes | No | Yes | Yes | No | Yes | Yes |
Open ADSL Line Performance | No | Yes | No | Yes | No | No | Yes | Yes |
Open PVC Configuration | No | Yes | No | No | No | No | No | Yes |
Auto Discovery is used to discover an existing network and can save time and effort. With Auto Discovery the network is interrogated for IP and SNMP devices and an object created for each new device discovered.
The Auto Discovery feature is also used to identify new CDM devices and their detailed hardware configuration after physical installation.
The Auto Discovery application has three different mechanisms for discovering devices:
1. IP
ICMP pings are used to find devices in a given IP address range. This finds which IP device exists, but does discover what kind of device it is.
2. SNMP
SNMP get requests are used to find devices in a given IP address range. Several SNMP community strings can be used so that equipment with different community strings can be discovered in the same discovery session. The SNMP information returned by devices is used to work out what kind of device has been found.
3. IP and SNMP
ICMP pings are used to find devices and then SNMP requests are used to interrogate the devices to find out what kind of device they are. This is the default mechanism.
Auto Discovery can discover devices on more than one subnetwork by using multi-hop discovery. It can be scheduled to run at preset times, the CEMF User Guide details how to set the schedules.
An option is available to specify the physical location that discovered objects will be created under.
Once the 6260 has been detected, an object representing a Chassis and the NI2 module is created and placed under the Site from which auto discovery was launched. A map of the chassis and NI2 is also created.
Auto Discovery can be opened from the MapViewer or Object Manager:
Step 1 From the Map Viewer place the cursor over a node representing an existing network object then press and hold the right mouse button
or
From the Object Manager navigate to a relevant network object, place the cursor over it then press and hold the right mouse button.
Step 2 Press and hold down the right mouse button, a pop-up menu appears.
Step 3 Select the AV Tools, Open Auto Discovery option.
Step 4 Release the mouse button. The Discover Network Devices screen appears:
The Discover Network Devices screen has the following sections:
You can enter the configuration details to be used for the Auto Discovery.
Displays the name of the selected device. The name of the selected site is specified. This is a read only attribute.
Displays the IP address of the machine from which this CDM is run. The address of the selected device is automatically specified and displayed. This is a read only attribute.
Select this to select the type of the discovery method. There are three discovery methods:
You should enter the total number of hops (routing metric used to measure the distance between a source and a destination) required.
You can enter the IP configuration details to be used for the Auto Discovery.
For IP devices, in the Ping Retries data entry box, type the number of times the system will try to identify if there is an active machine connected at a specified IP address. The maximum number is 10.
You can enter the SNMP configuration details to be used for the Auto Discovery.
In the data entry box next to SNMP Retries, enter the number of times the system should try to communicate with a device without receiving an expected reply, before it is discarded as not being an SNMP device. The maximum number is 10.
The SNMP community string is used to discover the devices during Auto Discovery. Enter a community name in the New Community data entry box and select the Add button. The new community name will be displayed with all the other community names entered.
You can remove any of the displayed community names by selecting the community name and then selecting the Remove button.
The objects that are discovered will be displayed under the path selected in Physical Location.
This section is used to check that the correct path is shown for Auto Discovery. You can change the path if required.
You can view the Discovery Interface details from the Device Interfaces section of the screen.
To view the discovery interface details proceed as follows:
Step 1 Double click on an entry in the Device Interface list in the Discover Network Devices screen. The Discovery Interface screen appears:
Step 2 You can modify the Start Address and End Address details of the Discovery Interface screen.
Step 3 Select OK to proceed or Cancel to terminate the changes.
To discover IP devices:
Step 1 Select the object that Auto Discovery will be carried out from.
Step 2 Open the Discover Network Devices screen (shown in Figure 3-2).
Step 3 The object name and address appears in the Discovery Configuration section of the window.
Step 4 Select the drop down list next to Discovery Method and select IP from the displayed list. IP appears next to Discovery Method.
Step 5 Type the number of times the system will try to identify if there is an active machine connected at a specified address into the Ping Retries data entry box.
Step 6 Select the Use Physical Path radio button. Ensure the correct path is shown. Select Get Path and select the correct Physical Containment, if required. Objects available for selection have an associated green color box. A red color box next to a node indicates that the object is not available.
Step 7 Select the Do Discovery button to start the discovery process. When Auto Discovery begins the system checks for existing devices in a selected address range. The discovery process will ignore any existing devices. The Discovery Progress screen appears. The Action Log section of the Discovery Progress screen displays the Auto Discovery progress in a tabular format.
Step 8 When the relevant IP devices on the network are discovered an object class is created and stored under the mgmtContainment and networkContainment trees for each device.
Step 9 Select the Close button to close the Discovery Progress screen.
To discover SNMP devices or SNMP and IP devices:
Step 1 Select the object that Auto Discovery will be carried out from.
Step 2 Open the Discover Network Devices screen (shown in Figure 3-2). The object name and address appear in the Discovery Configuration section of the window.
Step 3 Select the drop down list next to Discovery Method and select SNMP or IP and SNMP from the displayed list. SNMP or IP and SNMP will be displayed next to Discovery Method.
Step 4 Set the Hop Count to the number of subsequent devices you want to discover away from the start network. The maximum number is 16.
Step 5 Enter a number in the Ping Retries data entry box. Ping Retries is the number of times the system should try to identify if there is an active machine connected at a specified IP address or IP devices.
Step 6 Enter a community name in the New Community data entry box.
Step 7 Select the Add button. The new community name appears with all the other community names entered.
Step 8 Enter a number into the SNMP Retries data entry box. SNMP Retries is the number of times the system should try to communicate with a device (without receiving an expected reply, before it is discarded as a non SNMP device).
Step 9 Select the Use Physical Path check button in the Physical Location option box. Make sure the correct path is shown. Select Get Path and select the correct Physical Containment if required. Objects available for selection will have a associated green color box. A red color box next to a node indicates that the object is not available.
Step 10 Select the Do Discovery button to start the Auto Discovery process. The Discovery Progress screen appears.
Step 11 The Action Log displays the Auto Discovery progress and displays the results in tabular form.
Step 12 When all the relevant SNMP devices on the network have been discovered, an object class is created and stored under the SNMP containment tree.
Step 13 Devices, which respond to SNMP requests, will be put in the SNMP containment tree.
Step 14 When all the relevant IP devices on the network have been discovered, an object class will be created and stored under the mgmtContainment and networkContainment trees for each device. When the IP discovery and creation process is complete any SNMP devices on the network will be discovered and have an object class created and stored under the SNMP containment tree.
Select the Do Discovery button to initiate the discovery and display the progress details of the Auto Discovery process. It displays the total number of objects created.
To view the Discovery Progress screen:
Step 1 Select the Do Discovery button from the Discover Network Devices screen. The Discovery Progress screen appears:
Step 2 You can view the discovery progress for the selected device.
Step 3 Select the Stop button to terminate the discovery progress.
In order to discover a 6260 chassis that is present on a remote network, the user should perform the following actions:
1. Add a route on the server machine to allow devices in the remote network to be contacted.
2. Deploy a site in Object Manager that is to contain all the discovered 6260 chassis objects.
3. Deploy a network object in Object Manager giving it the IP address of the network to be discovered.
4. From the newly deployed network object, launch the auto discovery application.
5. Enter appropriate details for retries, community strings, address range etc. Select the Physical Containment button and from the Object Selector, select the Site object created in 2. And press the Apply button.
6. Select the Do Discovery button.
The relevant 6260 chassis objects will then be created under the selected Site object.
Deployment is the process of preparing the CEMF Server for the creation and subsequent management of new network elements. It is occasionally referred to as Provisioning. It is also occasionally referred to as Pre-Provisioning - meaning that part of the network setup before the service is actually provisioned. Once objects are deployed, the initial state of all objects will be normal.
Pre-Provisioning is the process of reserving and configuring a space in the system for network equipment, which have not yet been physically slotted into the system rack. It refers to a particular state of the device or object. If an object/device is in pre-provisioned state, it means that though the device/object is not present, the system has been pre-provisioned to hold an object of similar type. Thus the line cards in the CDM will be able to exist in a state known as pre-provisioned but the CDM will not monitor their status. When the cards are placed in the physical equipment, it will be possible to move the line card from the pre-provisioned state to the commissioned state by clicking on the Commission button, refer to Commission.
You can also create Site, Chassis, NI2 and Line Card objects manually from the MapViewer or Object Manager applications.
Each object has two names, its object name and its graphic icon name
During deployment and object creation these names are the same, however if you rename one occurrence, you must ensure that the other occurrence of the name is also changed. For full information about the naming of objects refer to the CEMF User Guide.
You can create new Chassis, NI2 and Line Card objects using Deployment from the following object types or map nodes:
| Task | Launch Point | |||||||
| Manager | Site | Shelf | Chassis | NI2 Card | NI2-OC3 Port | Line Card | ADSL Line Card Port | |
Deploy Network | Yes | Yes | No | No | No | No | No | No |
Deploy Site | Yes | Yes | No | No | No | No | No | No |
Deploy Cisco 6260 DSLAM | No | Yes | No | No | No | No | No | No |
Deploy Cisco 6260 DMT Line Card | No | No | No | No | Yes | No | No | No |
From the Manager object drop down menu select Deploy and then one of the following options. The Deployment Wizard then launches automatically:
To deploy a Network you must supply the following information: the network type (that is, Deploy WAN Network, Deploy Network, Deploy LAN Network, Deploy FrameRelay Network, Deploy FDDI Network, Deploy Ethernet Network or Deploy ATM Network), the Number of selected network(s), the name of the selected network and it's IP address.
To deploy a site, you must supply the following information: the type of deployment (that is, Deploy Auto Named Site or Deploy User Named Site), the Number of sites and the Site name prefix.
From the Site object drop down menu select Deploy and then one of the following options. The Deployment Wizard then launches automatically:
To successfully deploy a DSLAM you must supply the following information: the type of deployment (that is Create OC3-NI2 under an Auto-named or user-named Shelf, or Create DS3-NI2 under an Auto-named or user-named Shelf, or Create an OC3-NI2 or a DS3-NI2 under a Port), the number of objects to be deployed and their name prefix, Attributes including IP Address, SNMP V1 and V2c (Read/Write) Communities, SNMP Version, the Chassis name and the Class name. This deployment option is fully described in Deploying a CDM DSLAM Under A Site.
To successfully deploy a Network you must supply the following information: the network type (that is, Deploy WAN Network, Deploy Network, Deploy LAN Network, Deploy FrameRelay Network, Deploy FDDI Network, Deploy Ethernet Network or Deploy ATM Network), the Number of selected network(s), the name of the selected network and it's IP address.
To successfully deploy a site, supply the following information: the type of deployment (that is, Deploy Auto Named Site or Deploy User Named Site), the Number of sites and the Site name prefix.
From the NI2 object drop down menu select the following option. The Deployment Wizard launches automatically:
To successfully deploy an NI2 Line Card and associated ports, supply the following information: the number of c6260DMTCard objects and the c6260DMTCard number (the slot number of each card), and the position of the line card in the physical containment. This deployment option is fully described in Deploying a DMT Line Card .
The Deployment Wizard is used to deploy new network objects which can then be managed. It is launched from pop up menus available on selected objects in the Map Viewer or Object Manager applications. The sequence of screens seen during deployment in the Wizard are as follows:
The type of deployment required is selected from a list available on this screen.
Templates support the notion of global parameters, which describe general characteristics of the profile such as the number of top-level objects. Once you select a template then the global parameters are processed and displayed on the Deployment Details screen.
The deployment scenario is now at a stage where the Wizard has finished processing the first localComponent and again needs to determine which object to process next using the cardinality parameter defined for the localComponent class definition.
The deployment scenario may now continue with the Containment Details screen. The Wizard automatically derives a physContainment path for the ACMEShelf object using the launch object. You have the option to change the containment path.
The Deployment Summary screen appears at the end of the deployment sequence and shows each class and how many instances.
To deploy a CDM DSLAM under a site:
Step 1 In the Map Viewer or Object Manager, select the site or manager or container object. Press and hold down the right mouse button, a pop-up menu appears.
Step 2 Select the Deploy, Cisco 6260 DSLAM.
Step 3 The Deployment Selector Screen appears:
Step 4 Select one of the first four options available in the Deployment Selector Screen.
Step 5 Click the Forward>> button.
Step 6 The Deployment Details Screen appears:
Step 7 Click the Forward>> button to display the Object Details Screen:
Step 8 Enter the IP Address of the N12 device in the Attributes section.
Step 9 Select the SNMP version of the N12 device and click the Forward>> button. The Object Details Screen (Chassis Object) appears:
Step 10 Enter a c6260Chassis name in the Attributes box.
Step 11 Click the Forward >> button. The Object Details Screen (NI2 object) appears:
Step 12 Enter a c6260NI2 name in the Attributes box.
Step 13 Click the Forward >> button. The Deployment Summary Screen appears:
The Deployment Summary Screen summarizes the deployment you have created and gives you the option to commit or reject the deployment.
Step 14 To commit the deployment click the Finish button to confirm the operation. The Cancel button changes to the Dismiss button. Click the Dismiss button to close the screen
or
To reject the deployment, click the Cancel button.
Step 15 A feedback screen then informs you if deployment has been successful or not.
To deploy a DMT line card:
Step 1 Click the MapViewer icon or the Objects icon from the Launchpad.
Step 2 Place the cursor over the relevant NI2 object. Press and hold down the right mouse button, a pop-up menu appears.
Step 3 Move the cursor on the Deploy Cisco 6260 DMT Card to highlight it. Release the mouse button.
Step 4 The Deployment Selector Screen appears:
Step 5 Select the deployment you require and click the Forward button. The Containment Details Screen appears.
Step 6 Click the Select button to view the PhysContainment screen.
Step 7 Select the chassis object and click the Apply button in the PhysContainment screen.
Step 8 You will see the Deployment Summary screen:
The Deployment Summary Screen summarizes the deployment that you have created and gives you to commit or reject the deployment.
Step 9 To commit the deployment click the Finish button to confirm the operation. The Cancel button changes to the Dismiss button. Click the Dismiss button to close the screen
or
To reject the deployment, click the Cancel button.
Step 10 A feedback screen then informs you if deployment has been successful or not.
Use the Site Information option to enter site information and contact details for the selected site (for example, the site address and contact information).
To view and edit the Site Information screen, proceed as follows:
Step 1 In the Map Viewer or Object Manager application, right select the Site object. A pop-up menu appears.
Step 2 Select the Site Information option, the Site Information screen appears:
The Site Information screen has three tabbed sections, as follows:
The Site Information tab appears as default.
Enter information into each of the data entry boxes (as required) to identify the location of the site.
To enter information for first contact:
Step 1 Select the Contact One tab, you will see a screen similar to Figure 3-16:
Step 2 Enter information into each of the data entry boxes as required, to provide personal contact details for an individual at the site.
Enter the details of a second contact person at the selected site.
Use Notes option to enter notes for a selected site.
To view or edit the Notes screen, proceed as follows:
Step 1 In the Map Viewer
Step 2 Place the cursor over the relevant Site object. Press and hold down the right mouse button, a pop-up menu appears.
Step 3 Select the Notes option and release the mouse button, the Notes screen appears:
Step 4 Enter information into the Notes section.
Step 5 Click the Save icon to save any changes.
Step 6 Click the Close icon.
In the commissioned state, the CDM polls the device to detect whether it is present or not.
When an object enters the commissioned state, the CDM polls the object every twenty seconds to determine if it is present or not. If the object has been physically installed it will attempt to commission all of its descendents. That is, it will determine whether the object's children and descendents are present or not. Once all of the object's descendents have been installed or otherwise detected, the object's state will be set to normal.
Commission is available on the NI2 status screen which can be opened from an NI2 object in the Map Viewer or Object manager applications. Click the COMMISSION button to launch the Subrack Discovery process.
When you want to replace an existing card or perform any kind of maintenance work, an object should be decommissioned. Click the Decommissioned button to change the status from Normal to Decommissioned. The children of the objects will also change their status to decommissioned.
The state of a selected object is shown in the status bar, and directly affects the operations you can perform on that object. Table 3-3 shows the possible states for each object.
| Shelf | Chassis | NI2 | OC3 Port | DMT Card | ADSL Line | |
Normal | Valid | Valid | Valid | Valid | Valid | Valid |
Errored | Valid | Valid | Valid | Valid | Valid | Valid |
Decommissioned | Valid | Valid | Valid | Valid | Valid | Valid |
Commissioning | Valid | Valid | Valid | Valid | Valid | Valid |
Preprovisioned |
|
|
|
| Valid | Valid |
PreprovisionError |
|
|
|
| Valid | Valid |
LinkDown |
|
|
|
|
| Valid |
InvalidState |
|
|
|
| Valid | Valid |
Posted: Wed Sep 15 08:28:50 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.
