|
|
This Chapter provides an overview of the Cisco 6260 Digital Subscriber Line Manager (CDM) application using Cisco Element Management Framework (CEMF). For further information about the basic concepts of CEMF refer to the CEMF User Guide. The CEMF commands, icons and menus used to access services on the 6260 CDM are described.

Figure 2-1 shows a typical deployment and interconnection example for the 6260 CDM where it is connected to a Cisco 6400 Universal Access Concentrator system.
Figure 2-1 also demonstrates the subtending feature of the 6260 CDM, refer to Subtending.
CEMF is an open carrier class management system, designed to integrate with third party products and proprietary operational support systems. The CEMF User Guide gives full information about the application.
Many management protocols, both standards-based and proprietary, are supported by CEMF in a manner transparent to the applications that access the network. This leads to new network devices being managed instantly and new management applications being developed quickly to meet new requirements.
The Login screen is used to control user access to the 6260 CDM based on a pre-set name/password combination. An administrator can define this combination.
To start a client application (that is, the user GUI screens):
Step 1 Type <AVROOT>/bin/avsession.
Step 2 The Login screen appears. You are prompted to enter your user name and a password. The default user name is admin and the default password is admin.
Step 3 You will see the Launchpad screen, refer to CEMF Launchpad.
A log in record of users who access the GUI screens is maintained. This information is provided as ASCII text files c6260Manager.audit and C6260SSManager.audit which can be found in <AVROOT>/logs
The Launchpad icons, shown in Figure 2-2 represent the standard CEMF tools. Click the appropriate icon to launch an CEMF tool.

The 6260 CDM supports multi-user access. Each user session has access to the tools displayed on the CEMF Launchpad. Any changes made in a user session are reflected immediately in all other user sessions.
Additionally, it is possible to run multiple Event Browsers and Map Viewers on separate client workstations. This provides the option for a number of users to simultaneously monitor the same or distinct portions of the managed network.
All of a user's applications can be run on client workstations remote from the server. This means that the load on the server is dependent only on how much data the user requests from the server.
When more than one user access the same network element via any of the 6260 CDM screens, screens on other users' workstations are automatically updated to reflect the most recent status changes made to an element by any user. Dynamic Update provides a facility to enable or disable these automatic updates.
A map is a graphical representation of related managed objects. Maps can be defined in a hierarchy, with each node on a map having a sub-map. Different levels of complexity in a managed network can be seen by looking at high level maps or by navigating to sub-maps which represent lower levels of detail in the managed network.
Nodes and links on a map are graphical symbols which represent managed objects in the network or abstracted objects. A node has an iconic representation while a link has a vector representation. Links can only exist as a connection between two nodes.
Nodes and links can have sub-maps, thus defining a hierarchy of maps which the user can browse. Top level maps can be used to display administrative or physical network domains with sub-maps displaying more detail until actual managed elements are represented.
A network node displays the current event or alarm status of the object it represents. The alarm status of an object is the severity of the most severe alarm that is currently active on the object.
A sub-map propagates the most severe event or alarm status of all its nodes to the node on the parent map through which this sub-map can be accessed. The node on the parent map then displays the combined severity of its sub-map and the node it represents.
Thus a user can view a top level map and see the overall status of the network. When a node on the map shows a condition, the user can view successive sub-maps until they see the source of the condition.
Tasks can be carried out on any managed objects. These tasks or functions are referred to as services on objects, and are easily accessed from the different applications including the Map Viewer, Event Browser and Object Group Manager.
You can select one or more object and right click. This will display the list of services or actions available on an object in a pop up menu.
Throughout CEMF you can select either individual or multiple objects from lists displayed in the various windows. When more than one object is selected the pop up menu will display the services common to those objects.
This section describes basic instructions on how to access and use the key features contained within the 6260 CDM. The CDM runs on the CEMF, which provides generic network management functionalities and capabilities. It is assumed that you are fully conversant with the CDM equipment and have read all the relevant Cisco documentation. CEMF commands, icons and menus used to access services on the CDM are described.
The CDM system has up to two NI2 cards and up to thirty line cards. Each line card has multiple ports, each port can be connected to a subscriber through an xDSL modem. The CDM system can be configured and monitored.
The following classes of objects are identified in the CDM:
Map Viewer displays a graphical representation of a selected 6260 chassis and is the primary entry point into the CDM system after the initial deployment of a site has been done using the Object Manager, refer to Object Manager.
To access the Map Viewer, proceed as follows:
Step 1 Click the MapViewer icon from the Launchpad:
Step 2 The Map Viewer screen appears. The screen is divided into two sections, the hierarchy pane and the map pane. Dragging the boundary to the required position will re-size a section.
Step 3 A screen similar to Figure 2-3 appears. The map pane displays a map of the selected object. In Figure 2-3 the empty slots are grayed and the slots with either the line cards or the NI2 cards are represented with images.

The user can change the mode from Map Hierarchy to View or Build. In view mode the hierarchy pane is removed and the map pane fills the whole screen. In build mode the map pane fills the whole screen, this mode is used to edit existing maps and add new maps.
The hierarchy pane is used to navigate through the sub-maps. Double click on any of the nodes in the tree to view the relevant sub-map on the map pane.
The hierarchy pane is used to navigate around the maps in the system. When the Map Viewer is launched the hierarchy pane displays the Root icon and an icon for each top-level map. There are two icon types that can appear in the hierarchy pane:
1. Map with sub-maps
2. Map without sub-maps
The map currently displayed in the map pane will have its corresponding map icon highlighted in the hierarchy pane.
The map pane is used to monitor the status of all network elements and to launch any available applications. The map pane displays a map corresponding to the selected map icon in the hierarchy pane.
The map can contain nodes and links. There are three types of nodes and ten types of links. Each node on a map that has an object assigned to it has a colored status bar (for icons) or colored background (for nodes). The color corresponds to the highest event severity reported by the object, or any object in a sub-map assigned to the object.
The severity of events and their corresponding colors are shown in Table 2-1.
| Color | Severity of Event |
Red | Critical |
Orange | Major |
Yellow | Minor |
Cyan | Warning |
Green | No Events (Normal) |
Blue | Card decommissioned or not installed |
White | Informational |
Dark green | Preprovision |
Events on the 6260 CDM are raised from SNMP traps. All sources of events are available via simple GUIs, providing an integrated fault management solution.
The Event Browser is used to view any events that have been flagged by the system.
All network objects are displayed using a color code that identifies the operational status. Events can be propagated up the element hierarchy according to severity, refer to Table 2-1.
All events are stored within the Event Browser which shows current and historical data. You can navigate directly from a single event within the browser to the affected object to perform detailed configuration activities.
Additionally, the 6260 CDM can be complemented by the Event Manager application. Among other features, this enables thresholds to be set to monitor any supported 6260 Element Manager MIB variable (that is, those which appear on the 6260 CDM Element Manager GUIs).
The Object Manager is an application that displays objects in different hierarchies. Use Object Manager to navigate to other objects so that services can be invoked on that object. Object Manager is used for the initial deployment to create a site which is then used to discover objects on the system.
A system administrator uses the Access Manager application to add new users to the system, remove users and change passwords when required. The system administrator, whose user name is admin, can add/delete any user name and change any password without knowing the user's old password.
This section contains the basic instructions on how to access and use the key features contained within the CDM screens.
The layout of a typical CDM Graphical User Interface (GUI) screen is shown in Figure 2-4 :

Use this menu options to Save any changes, Print the displayed window and Close the window.
The options available on the Edit menu depend on the application screen that is open and can include copy, paste, delete or edit.
Use these menu options to Acknowledge changes, toggle Dynamic Update On or Off,
Each window has an option to select Navigation. This will display a drop down list of possible tasks, select the task you require.
Each screen has a Window menu option. When a screen has been left opened it will appear in this list. To view a window that is open, select the Window option and select the screen you require from the drop down list.
The Action menu displays the commands available for the selected screens.
The Help menu allows you to view help information for a selected option.
The toolbar at the top of each screen contains icon buttons which invoke various tools and menu options.
The ToolTips option displays a brief description of the tool or icon that the cursor is left over. ToolTips is enabled as default. When you place the cursor on any attribute in any screen, a ToolTip will display the functionality of the selected attribute.
When a screen covers several areas of information, the screen may be divided into tabs. Select the required tab to view related attributes and to perform certain operations.
You can enter a string into the data entry box within a specific range.
Click on the combo box to display the options that are assigned to the selected parameter.
Click the Forward >> button to advance to the next screen.
Click the << Back button to return to the previous screen.
Click the Cancel button to terminate the operation.
Click the Finish button to confirm the operation.
Click the Dismiss button to close the screen.
System status information such as commissioned, decommission, normal etc., is displayed in the information display area at the bottom of the screen.
This displays the present status of the selected object. You can double click on the status display area to display the Status Dialog screen. This list recent status messages.
The Update button at the bottom of each screen displays the status. This can be:
In CEMF the relationship between objects is modelled by parent / child containment trees. Every object has parents and children in one or more containment trees. Each tree represents a different view of the managed network, e.g. physical containment, network or logical containment, and management containment.
You can access CDM objects by navigating through one of the containment trees to find the object.
The following containments provide the most logical views of the networks and it is recommended that you use them in the 6260 CDM Element Manager:
mgmtContainment, refer to mgmtContainment
physContainment, refer to physContainment
networkContainment, refer to networkContainment
mapObjectContainment, refer to mapObjectContainment
subtendContainment, refer to subtend Containment
This holds all the managed objects in the network. This tree shows the management relationships between objects. Generally speaking, objects further down the tree are managed by objects above them in the tree. The CDM Server object is always at the top of this tree.

This holds location information for all equipment in the network. The relationships defined in this tree are physical containment relationships. For example, a bay will appear below a central office because the bay is physically contained inside the central office.

This displays all IP devices under their parent network. This tree provides a logical view of the network structure. It does not provide topology information.

This is the only containment tree that defines the exact event propagation path. It is used to reflect the relationship between maps and displays a chassis front panel representation of the contents of the chassis.

This containmment is used to view the subtended relationship between 6260 NI2s, it is populated during the deployment process using the Deployment Wizard and not auto discovered.

![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Wed Sep 15 08:28:44 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.