|
|
This chapter describes the ViewRunner for HP OpenView program, system files, navigational system, system dialogs, and management tools. The chapter contains the following sections:
ViewRunner for HP OpenView is a carrier class Element Management System (EMS) that enables users to manage a network of Cisco 6100s. Key ViewRunner features include:
ViewRunner for HP OpenView is the graphical user interface application that lets you configure and manage Cisco 6100 Advanced Digital Subscriber Line Access Multiplexers (ADSLAMS). ViewRunner for HP OpenView supports the Cisco 6100 auto-discovery of equipment, which means that once you have installed ViewRunner and connected it to your Cisco 6100, ViewRunner for HP OpenView retrieves configuration data from the Cisco 6100's SNMP agent. It then displays a graphical representation of your Cisco 6100 like the one shown in Figure 1-1.
ViewRunner for HP OpenView has three client applications View Map, View Admin, and View LoopRunner. View Map contains hierarchical views of networks of Cisco 6100s as well as subtended configurations. It has a New Equipment window that contains newly discovered Cisco 6100s, and a New Subtend Group window showing newly discovered subtended Cisco 6100s. View Admin is used to define and administer users (operators) of the ViewRunner for HP OpenView client applications. View LoopRunner provides the primary graphical user interface with which to manage Cisco 6100s. It provides a superset of the functionality of ViewRunner for Windows.
The following matrix describes the compatibility among Cisco 6100 and ViewRunner for HP OpenView releases.
| Cisco 6100 Releases | |||||
|---|---|---|---|---|---|
| Release 2.3.0 | Releases 2.2.1/2.2.5 | Release 2.2.0 | Release 2.1.3 | Release 2.1.2 | |
| ViewRunner for HP OpenView |
|
|
|
|
|
Release 2.3.5 | X | X | X | X | X |
Release 2.3.0 | 6100 2.2.1 | X | X | X | X |
Release 2.2.0 | 6100 2.2.0 | 6100 2.2.0 | X | X | X |
Legend: | 6100 X.Y.Z - ViewRunner presents a feature set customized to this Cisco 6100 release's capabilities. View Runner presents a feature set corresponding to the specified Cisco 6100 X.Y.Z release's capabilities. ViewRunner prompts the user when the Chassis View is opened that the feature set is not recognized and a default feature set is being used. | ||||
The Chassis View provides the top-level user interface to manage a single Cisco 6100.
There are three types of chassis in the Cisco 6100. The first two of them can be managed through ViewRunner for HP OpenView:
The Chassis View shown below provides both menu bar operations and a bitmap front panel view of the Cisco 6100 that displays color-coded status of configured modules.
The Chassis View displays the multiplexer chassis (MC) and each 6110 line concentration chassis (LCC). It also provides a top level display of modules, which you can view, add (preprovision), modify, and delete. From the Chassis View, you can view all status information, manage all configurations, and check the performance of the Cisco 6100.
The Chassis View displays colored module ejector tabs to indicate the status and state of each module and its ports. The color displayed is based on a set of rules defined below. The list below describes the highest priority color to display first and the lowest priority color last, in cases where more than one of the conditions described below is met. See "Cisco 6100 and ViewRunner State Management" for more information on states and see the Cisco 6100 Series Maintenance and Troubleshooting Guide for detailed information on alarms.
| Tab Color | State | State Type | Description |
|---|---|---|---|
Off-white | Unmanaged | Administrative | This state indicates the resource should not be monitored and that the operational status is being ignored. Traps are still received and displayed in the Event Categories window. ViewRunner uses this state for displaying modules in Cisco 6100s that are in loss of communication, but for which there is configuration information in the database. |
Blue | Unknown | Operational | This state indicates that the Cisco 6100 Slot State is Empty-Provisioned. This state occurs when the system controller (SC) has not communicated with the module, but a module configuration exists for the slot. This could occur when:
|
Brown | Locked | Administrative | Either the module or all of the module's ports have an Administrative State of Locked. |
Red | Critical Alarm | Operational | A critical alarm is the most severe alarm present on the module or any of its ports. |
Orange | Major Alarm | Operational | A major alarm is the most severe alarm present on the module or any of its ports. |
Yellow | Minor Alarm | Operational | A minor alarm is the most severe alarm present on the module or any of its ports. |
Green | Normal | Operational | The module and all of its ports are in a Normal state. The module is physically present and the module and at least one of its ports has an Administrative State of Unlocked. |
Client windows are updated dynamically in real time while they are open. Changes detected by ViewRunner server applications are propagated to all ViewRunner clients when:
Traps are propagated to all clients, updating alarm colors (ejector tabs) and the Event Categories window. Configuration, alarm, View Map, and OpenView Map synchronization algorithms keep ViewRunner current with the node/network state.
To run ViewRunner for HP OpenView, you should also have some basic knowledge of the physical modules of the Cisco 6100. There are six types of configurable modules:
You should also have some basic knowledge of the logical entities of the Cisco 6100. Those logical entities are as follows:
For descriptions of these modules, consult the Cisco 6100 Set Up and Installation Guide.
The ViewRunner maintains several key system files that reside in the subdirectories of the server home directory. These key system files include:
In addition to these files, there is a README file explaining how to install the ViewRunner software.
A release definition files (RDF) identifies the software image that is compatible with each hardware module/revision for a given system release. During software updates, ViewRunner applies the selected RDF file to the SC. Multiple RDF files and associated images may be maintained in the ViewRunner directories. See "Software Update Download" section for more information about software update downloads.
The RDF is named 9000-xxx-xx.RDF where "9000-xxx-xx" is the latest release of the system. The file is stored in $VRS_HOME/RDF and contains information about the software and hardware release of the Cisco 6100 components. The information in each RDF will look similar to the following:
9000-001-23R,Production Release 2.3.0.201*******************************************************************************Hardware Revision Table*******************************************************************************Begin 2651-003,9651-001-28,"SC" 2601-014,9601-001-25,"OC-3 NI SMF" 2601-015,9601-001-25,"OC-3 NI MMF" 2601-016,9601-001-25,"DS3 NI" 2601-012,9601-001-25,"Subtending DS3 NI" 2601-021,9601-001-25,"Subtending DS3 NI FPGA mod" 2601-020,9601-001-25,"Subtending OC-3 NI MMF FPGA mod" 2601-019,9601-001-25,"Subtending OC-3 NI SMF FPGA mod" 2601-022,9601-001-25,"OC3 SM NIM Temperature Hardened" 2601-023,9601-001-25,"OC3 MM NIM Temperature Hardened" 2601-024,9601-001-25,"DS3 NIM Temperature Hardened" 2101-003,0101-001-18,"Dual ATU-C CAP Direct Connect" 2101-004,0101-001-18,"Dual ATU-C CAP DOH" 2101-005,0101-001-18,"Dual ATU-C CAP DOH" 2102-002,0010-152-00,"Dual ATU-C DMT Issue 1 Direct Connect" 2102-003,0010-152-00,"Dual ATU-C DMT Issue 1 Direct Connect" 2651-004,9651-002-11,"LCM" 2601-017,9601-005-11,"SHM" End ******************************************************************************* Image Table ******************************************************************************* Begin 9651-001-28,psc203102.ima,865552,2712234465,"SC" 9601-001-25,pni203102.ima,581380,4072816583,"NI" 0101-001-18,cap2.3.0.3.ima,237520,3164022261,"ATUC" 0010-152-00,dmt2.3.0.5.ima,237520,3179656967,"ATUC" 9651-002-11,lcmR2.2.5.ima,237520,163741187,"LCM" 9601-005-11,pst202102.ima,394296,1333253802,"SHM" End
Another key system file is the SC feature compatibility matrix FCM) file which contains feature descriptions of all required system releases. ViewRunner servers read the FCM file when they start up and use the matrix to customize the features to present to the user based on the SC release loaded on the Cisco 6100.
For example, an older release of a Cisco 6100 LIM controller module will not support the newer feature that allows the Administrative State to lock all entities before deleting a chassis. Therefore, ViewRunner consults the compatibility matrix to determine that it should disable the Delete Chassis option if the module is not locked by the user.
Newer Cisco 6100 releases may be managed by ViewRunner without updating this file; however, the user is warned each time a client opens the 6100 Chassis View if that node's SC software is not recognized. The following error dialog is generated when you connect to a Cisco 6100 containing an SC software version not found in the feature compatibility matrix file.
In these cases, ViewRunner will present a default SC feature set to the user which corresponds to the features in the last recognized SC system release. Any newer features on the SC will not be accessible. An updated FCM file may be obtained at the Cisco CCO Web site or by contacting Cisco TAC. Obtaining a newer FCM file may eliminate this warning. However, this message typically means that a newer ViewRunner version should be available.
The file SCFeatureCompatibilityMatrix.csv is stored in $VRS_HOME/CMF.
Information in the FCM should be similar to the following.
SC Software Version DirectConnect SWDownload LIMCSetAdminState SCSetAdminState SCMaintState MIBIndexFix MIBClearNVRAM PreprovisionDirectATUC Subtending MarginAttenuation Chassis Id Fix LR Inband Mgmt Channel Multiple Trap Recipients Subscriber Idle Disconnect 136KB Subscriber Rates ATU-C ParmsBEGIN9651-001-079651-001-099651-001-12 DIRECT9651-001-13 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC MARGINATTEN9651-001-15 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX9651-001-21 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX9651-001-20 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB9651-001-22 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMS9651-001-23 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMS9651-001-24 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMS9651-001-25 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMS9651-001-26 DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMSdefault DIRECT SWDLD LCSADMIN SCSADMIN SCMAINT MIFIX MICNVRAM PPDATUC SUBTEND MARGINATTEN LCCIDFIX INBANDCH TRAPRCVRS SUBSCTIMEOUT BITRATES136KB ATUCPARMSENDNote: All descriptions past this point are comments. These fields do not get used by ViewRunner. Cisco-Austin updates the Feature Capability Matrix file whenever a new SC software version is released. If a user connects ViewRunner to a node that contains anSC software version that is not recognized, a warning dialog will notify the user to obtain a newer version of the file. The most up-to-date Feature. Compatibility File may be obtained at http://www.netspeed.com/tech.html. The SCFeatureCapabilityMatrix.csvfile should be downloaded and saved into the directory where ViewRunner is installed. If the updated file does not allow ViewRunner to manage this node, then contact Customer Support directly.System Part # LoopRunner Rel Contains SC SWBEGIN9000-001-03 1.02 release 9651-001-079000-001-04 1.02A release 9651-001-099000-001-06 1.02C release 9651-001-129000-001-07 2.0 release 9651-001-139000-001-09 2.1.0 release 9651-001-159000-001-10 2.1.1 release 9651-001-159000-001-11 2.1.2 release 9651-001-159000-001-13 2.1.3 release 9651-001-219000-001-12 2.2.0 release 9651-001-209000-001-14 2.2.1 release 9651-001-229000-001-15 2.2.0.101 release 9651-001-239000-001-16 2.2.5.100 release 9651-001-249000-001-18 2.2.0.102 release 9651-001-259000-001-19 2.2.0.103 release 9651-001-259000-001-20 2.2.5.102 release 9651-001-269000-001-21 2.2.5.103 release 9651-001-26ENDFeature DescriptionDIRECT LoopRunner supports Direct Connect Mode (Subscribers associated directly to ATU-Cs. No LIMs)SWDLD "LoopRunner supports system software upgrading via image TFTP to node. This includes several MIB additions (HW table, Image table, etc)"LCSACMIN "LIM Controller Supports Configurable Admin State. If this feature is supported, VR should dim the LIM Chassis Deletion menu options unless Admin State is Locked."SCSACMIN SC Supports Configurable Administrative State.SCMAINT SC Supports Configurable Maintenance State.MIFIX "PR 285 - MIB indexes may now be specified during Row creation. Among other things, this eliminates requirement for SC Reset prior to saving NVRAM configuration"MICNVRAM PR 1211 - MIB Supports Clearing NVRAMPPDATUC PR 1340 - LoopRunner supports pre-provisioning of ATU-C modules in direct mode.SUBTEND "LoopRunner supports Subtend Feature (Subtend host module, Transit subscribers)"MARGINATTEN Support for setting ADSL margin and attenuation values on a per subscriber basisINBANDCH Support for LoopRunner inband management channel and associated Routing Table supportTRAPRCVRS Support for multiple trap recipientsSUBSCRTIMEOUT "Supports lrSubscrTimerType, lrSubscrTimerValue which defines if and when a subscriber is disconnected after a specified idle or session timout."LCCIDFIX Supports pre-provisioning full range of Chassis Ids (0-15)BITRATES136KB New physical layer rate combinations supported by 136KB firmware (42 new bitrate combinations)ATUCPARMS ATUC Settable parameters for 136K baud enable/disable and Non-Timer CPE train enable/disable
ViewRunner maintains configuration files that customize ViewRunner operation. These files are read when ViewRunner servers are started up.
During software upgrade, when moving to a release which supports new subscriber data which is not supported in the release being upgraded from, defaults are taken from the vrconstants.conf file instead of relying on node defaults. This allows the user to upgrade software and get default subscriber values set to their site defaults. Otherwise, if the node default does not match what the customer wanted, they would have to modify each subscriber manually after the upgrade.
ViewRunner for HP OpenView maintains log files for all its server processes. These files log key events into text files which can be viewed with any UNIX text editor. The log files are stored in $VRS_HOME/log in files named <process_name>.log.<pid>. A log file is created for each process every time it starts up. The files are intended to be used in troubleshooting problems with ViewRunner and the Cisco 6100.
The following figure is an listing of the log files:
The following figure is an example of the vrProcessMon.log.25875 from the above list illustrating the types of events that are logged.
ViewRunner for HP OpenView is the Element Management System (EMS) for the Cisco 6100 ADSLAM system. It is the graphical user interface (GUI) application that provides the user with full graphical functionality to manage Cisco 6100 nodes using the HP OpenView operating environment.
ViewRunner for HP OpenView supports the discovery, configuration, and synchronization of Cisco 6100 equipment. Once you have installed ViewRunner for HP OpenView and established connection to your Cisco 6100, ViewRunner for HP OpenView retrieves configuration data from the Cisco 6100's SNMP Management Information Base (MIB) and synchronizes it with the Oracle database system for easy management and operation.
ViewRunner is implemented in a client/server architecture. The server provides interfaces to Cisco 6100s and performs services to the clients upon requests from those clients. The client then provides the human interface for ViewRunner.
ViewRunner provides authentication through user logins and passwords, and it supports multi-user access regulation. When changes are made, broadcast services are used to propagate configuration/status changes to all clients through the use of colors and text.
When ViewRunner displays client information as windows are first opened, the status (state) and Administrative State information is retrieved from the Cisco 6100. All other configuration data is retrieved from the Oracle database.
Client windows are updated dynamically in real time while they are open. Changes detected by ViewRunner server applications are propagated to all ViewRunner clients when:
Traps are propagated to all clients, updating alarm colors and the Event Categories window. Configuration, alarm, View Map, and OpenView Map synchronization algorithms keep ViewRunner current with the node/network state.
For more information about the client/server architecture, please see the ViewRunner for HP OpenView Installation and Administration Guide.
ViewRunner for HP OpenView is fully integrated with HP OpenView to take advantage of certain OpenView capabilities.
The HP OpenView Network Node Manager 5.1x typically manages nodes within an IP segment, communicating using the Simple Network Management Protocol (SNMP). The most important of the HP OpenView features where ViewRunner is concerned are as follows:
ViewRunner applications are integrated with HP OpenView in the following ways:
Some of the inherent OpenView capabilities used by ViewRunner include:
Oracle is the relational database management system (DBMS) that is the repository for all Cisco 6100 and ViewRunner configuration information.
As a relational data base management system (RDBMS), Oracle allows flexible use of its table content. Oracle also provides SQL access to that table information. More specifically, Oracle table content:
Some of the specific benefits to using Oracle include:
ViewRunner for HP OpenView takes advantage of OpenView windowing and mapping capabilities for its views and navigation. Because of this integration, OpenView online Help can be used to find out in-depth operational details about using the windows efficiently.
HP OpenView has an extensive online Help system available. You can access it from any of the ViewRunner screens either through the Help button in the window menu or through a radio button on the bottom of the window.
For example, access help for HP OpenView Windows by selecting Help > Overview on the menu bar in the Wire Center submap view;
ViewRunner's View Map application is responsible for displaying the logical containment hierarchy for Cisco 6100 equipment in a customer's network. Because View Map is integrated with HP OpenView map, online Help can give you a detailed look at how the map function works.
Figure 1-6 and Figure 1-7 describe the anatomy of a submap screen in HP OpenView and thus for ViewRunner.
ViewRunner's View Map application is responsible for displaying logical views of the Cisco 6100 equipment in your network. View Map-enabled maps co-exist with other vendors applications, such as HP's IP Map application. View Map is integrated into the IP Map polling process, so if auto-discovery of Cisco 6100 equipment is desired, IP Map must be enabled for the map and IP Polling must be set. See "ViewRunner Maps and Views" for details on creating and using View Map maps.
Here's how HP OpenView Help describes maps, and thus View Map's maps.
View Map makes use of HP OpenView submaps to create the various levels of the hierarchy. View Map does not support independent submaps. Here's HP OpenView Help information on Submaps.
An object represents a particular entity or resource in a networked system. View Map uses standard HP OpenView objects and some of its own. The objects used by View Map include:
Here's the HP OpenView Help information regarding objects.
View Map uses standard OpenView symbols for the World and Location domains. It uses Cisco icon symbols to represent:
Prior releases used some symbol and field names in HP Openview that are different that those used in this release. Table 1-3 lists theold and new names used in each HP OpenView window.
Prior releases used some symbol and field names in HP OpenView maps that are different than those used in this release. Table 1-3 lists the old and new names used in each HP OpenView window
| Window | Old Name | New Name |
|---|---|---|
HP OpenView Root Window | Subtend Networks | Subtend Locations |
| New Subtend LoopRunners | New Subtend Cisco6100s |
HP OpenView Classes | NetSpeed | CiscoDSL |
| NetSpeedConnection | CiscoDSLConnection |
| LoopRunnerPort | (removed) |
| NIConnection | (removed) |
HPO OpenView Sub-classes | NetSpeed:WireCenter | CiscoDSL:WireCenter |
| NetSpeed:SubtendLocation | CiscoDSL:Subtend Location |
| NetSpeed:SubtendGroup | CiscoDSL:SubtendGroup |
| NetSpeedConnection:Subtend | CiscoDSLConnection:Subtend |
| LoopRunner:LoopRunner | CiscoDSLAM:Cisco6100 |
| LoopRunner:LoopRunnerLOC | CiscoDSLAM:Cisco6100LOC |
| NetSpeed:LRZend | (removed) |
| NetSpeed:WireCenterInLOC | (removed) |
| NetSpeed:SubtendNetwork | (removed) |
| LooopRunnerPort:LIMPort | (removed) |
| LoopRunnerPort:ATUCPort | (removed) |
| LoopRunnerPort:SHMPort6 | (removed) |
Fields | LoopRunnerIPAddress | CiscoDSLAMIPAdcdress |
| LRInband Address | CiscoDSLAMInbandAddress |
| IsNetSpeedObject | IsCiscoDSLObject |
| IsSubtendNetwork | IsSubtendLocation |
| IsSubtendLoopRunner | IsSubtendCisco6100 |
| IsLoopRunner | IsCisco6100 |
| IsLoopRunnerInterface | (removed) |
| IsLoopRunnerZEnd | (removed) |
| NotImplemented | (removed) |
| PortModuleType | (removed) |
Here's what HP OpenView Help has to say about symbols.
By default, the ovw (graphical network map) program is executable by anyone. Although everyone may have permissions to make changes to maps, only the first person who opens an ovw map has read-write access to the map, and subsequent users who open the same session have read-only access. When the person who has read-write access closes his/her map, another user may use Map > Refresh to gain read-write access.
See the ViewRunner for HP OpenView Installation and Administration Guide for more information on setting up user permission levels.
ViewRunner adds capability to the basic HP OpenView map functions. OpenView imposes restrictions that View Map does not because ViewRunner uses an Oracle database as its respository for map information.
There are two types of maps possible in OpenView:
ViewRunner's View Map application does support multiple simultaneous read-write maps. A user may have uniquely named read-write map, and ViewRunner automatically correlates all read-write maps to keep them in sync with each other. Changes made to a read-write map will be propogated to other read-write maps immediately.
Each ViewRunner ovw session maintains a log of the map modifications provisioned since the client session was begun. The ViewMap log may be accessed to determine the reasons a refresh of the map may be needed. Note that the Map > Refresh Map option is non-dimmed on the menu only when a user's map is not up-to-date.
The user is allowed to specify either automatic or manual layout of nodes within a map. Using manual layout, the map synchronization process retains the manual layout of the nodes within a map. In automatic layout, map synchronization deletes the nodes and re-adds them to synchronize with the database.
The View Map client application provides the user with a hierarchal view of a network of Cisco 6100 equipment. View LoopRunner provides the user with a front panel view of a selected Cisco 6100, allowing him/her to view that Cisco 6100's status, manage its configuration, and check its performance.
The overall hierarchy is as follows:
New Equipment Window | |||
World | |||
| Location(s) | ||
|
| Wire Center | |
|
|
| 6100 Interfaces View |
|
|
| 6100 Chassis View |
New Subtend Cisco 6100s | |||
Subtend Networks | |||
| Subtend Location(s) | ||
|
| Subtend Group | |
The two Cisco 6100 views (Interfaces and Chassis) are provided by the View LoopRunner application which is discussed later in this chapter. The other views are provided by the View Map application. An example of the view hierarchy is found in Figure 1-12. ViewRunner for HP OpenView allows the user to double click on a Cisco 6100 series icon in View Map to open Chassis View for that node.
Navigating among these views is accomplished through double-clicking a symbol in one of the ViewRunner windows or through menu options available in the various views. Right click menus on Cisco 6100 symbols allow rapid navigation. Double-clicking a Cisco 6100 symbol opens Chassis View for that node.
Another view of the hierarchy can be found in Figure 1-12 which shows a geographically based hierarchy of windows beginning with the root window and going all the way down to a Wire Center provisioned with Cisco 6100s.
The following diagram gives a more detailed view of the interactions between windows and views.
ViewRunner for HP OpenView supports several navigation methods:
The primary mechanism for retrieving information about a particular module or chassis is the right mouse button. The right button acts as a shortcut method for displaying properties about a particular module or chassis.
Use the right button of the mouse to bring up the pop-up menu containing a list of options available for a particular module. Pop-up menus are also context sensitive based on the chassis, module, or slot that is beneath the cursor when the right button is selected.
Placing the cursor over the chassis but outside of the slots selects the chassis. Pop-up menu options are dimmed for users that do not have necessary privileges, or when a menu option is not supported based on the current configuration.
The following series of pop-up menus show the options that appear when you right click on a particular component.
The following options are displayed when you right click on the MC:
| Pop-Up Menu Item | Description |
|---|---|
Synchronize 6100 Configuration | Initiates the sequence of SNMP messages required to reconcile the ViewRunner database with the Cisco 6100 configurations. This menu option rediscovers Cisco 6100 equipment and configuration. |
Synchronize 6100 Alarms | Initiates the sequence of SNMP message to reconcile the alarm table in the ViewRunner database with the current state of the Cisco 6100. |
6100 Properties | Allows you to check and set properties common to the entire Cisco 6100 such as the current date and time for the Cisco 6100. |
Pool Properties | Opens the Pool Properties configuration window (DOH configurations only). |
Active Connections | Opens the Active Connections view, displaying a list of the currently active ATU-C port to line port connections in the Cisco 6100. This window supports logical service oriented navigation. |
View All Subscribers | Allows you to view all the subscribers for a node, subtend group, or Wire Center. This window supports logical service oriented navigation. |
View All PVC | Allows you to view all of the subscribers defined for the Cisco 6100, subtend group, or Wire Center along with their configured PVCs. This window supports logical service oriented navigation. |
View Equipment Inventory | Allows you to view an inventory of all the equipment in the Cisco 6100, subtend group, or Wire Center. This window supports logical screen oriented navigation. |
6100 Performance | Allows you to view Cisco 6100 performance statistics. |
Port Service Configuration | Shows all the ports that are available and those that are in service or are capable of service (Direct Connect configurations only). |
6100 Current Alarms | Opens an alarm window displaying all the currently asserted alarms in the Cisco 6100. This window supports logical screen oriented navigation. |
Routing Table | Allows you to set the routing table in support of the inband management channel and multiple trap recipients |
6100 Trap Recipients | Allows you to set multiple trap recipients |
6100 Inband Management Channel | Allows you to manage the Cisco 6100 through an inband channel rather than through the ethernet channel |
Add Chassis | Allows an operator with sufficient privileges to pre-provision a new LIM chassis for the Cisco 6100. |
The following options are displayed when you right click on the LCC:
| Pop-Up Menu Item | Description |
|---|---|
Chassis Properties | Displays the backplane revision number for this LIM chassis. |
Delete Chassis | Allows the user to delete the LIM chassis. Unless all the modules and ports are set to Adminstrative State Locked, the option to delete the chassis will be greyed out. |
Selecting the Module Properties option brings up the Module Properties screen, which displays properties about a particular module. Each of these screens has a number of tabs associated with it. The number of tabs shown on the screen depends on the type of module.
The number of port items displayed in the plug-in module pop-up menu is context sensitive based on the type of module selected. For example, the SC pop-up has no port items, LIM module pop-up has four port items, and ATU-C module pop-up has two port items.
The following options are displayed when you right click on a ATU-C module:
The following options are displayed when you right click on a LIM module:
| Pop-up Menu Item | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration tabs for a particular module. |
Port Properties | Gives you direct access to the Status or Configuration tabs for a particular port. |
Delete Module | Deletes the specified module from the Cisco 6100. This option is greyed out unless the you lock the module or all of its ports. This option is always greyed out for users with read-only privileges. |
Chassis | Gives you direct access to the chassis drop down menu. |
The following options are displayed when you right click on the SC:
| Pop-up Menu Item | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration tabs for a particular module. |
Delete Module | Deletes the module. This option is greyed out unless the you lock the module (not supported in this release). This option is always greyed out for users with read-only privileges. |
Chassis | Gives you direct access to the Chassis drop down menu. |
The following options are displayed when you right click on the LIM controller:
| Pop-up Menu Item | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration tabs for a particular module. |
Delete Module | Deletes the module. This option is greyed out unless the you lock the module. This option is always greyed out for users with read-only privileges. |
Chassis | Gives you direct access to the Chassis drop down menu. |
The following options appear when you right click on an empty slot in the MC:
| Pop-Up Menu Item | Description |
|---|---|
Insert | Opens a dialog containing a visual representation of the modules that may be pre-provisioned in the selected slot. |
6100 Properties | Gives you direct access to the chassis status or configuration. |
Access any Cisco 6100 component and notice the similarities between the screens that appear. Most components have windows, tabs, and buttons very similar to each other as described later in this chapter.
The following options appear when you right click on an empty slot in the LCC:
| Pop-Up Menu Item | Description |
|---|---|
Insert | Opens a dialog containing a visual representation of the modules that may be pre-provisioned in the selected slot. |
Chassis | Gives you direct access to the chassis properties or allows you to delete the chassis. The Delete Chassis option is grayed out unless all modules are locked or deleted first. |
As a second means of navigation, HP OpenView has a toolbar that allows you to bypass the menu hierarchy to perform certain tasks.
The HP OpenView toolbar is found in Figure 1-22
See the HP OpenView Help system for more information on each of the icons.
There is another toolbar on the 6100 Chassis View.
The icons on this bar are described in Table 1-12.
| Chassis View Toolbar Icons | Icon Description |
|---|---|
Synchronize 6100 Configuration | Initiates the sequence of SNMP messages required to reconcile the ViewRunner database with the Cisco 6100 configurations. This menu option rediscovers Cisco 6100 equipment and configuration. |
Synchronize 6100 Alarms | Initiates the sequence of SNMP messages to reconcile alarm tables in the ViewRunner database with the current state of the Cisco 6100 |
6100 Current Alarms | Opens an alarm window displaying all the currently asserted alarms in the Cisco 6100. This window supports logical service oriented navigation. |
Zoom Out | Shrinks the Cisco 6100 Chassis View. |
Zoom In | Enlarges the Cisco 6100 Chassis View. |
Current Alarms Count | Displays the number of currently asserted alarms which are critical (red), major (orange), and minor (yellow). |
As another means of navigation, the menu hierarchy in ViewRunner for HP OpenView consists of a menu bar with dropdown menus and options therein. The next few figures show each of the dropdown menus on the Root Map of ViewRunner.
ViewRunner for HP OpenView supports logical service oriented navigation, which allows rapid navigation to a module, port, or subscriber property dialog from the summary dialogs.
Logical service oriented navigation eliminates the need to bring up the craft oriented Chassis View and click on the physical position of the entity to be provisioned. Although logical service oriented navigation eliminates the need to use the physical navigation to the entity via the Chassis View, you can still double click on an entity in the Chassis View and access the property dialogs necessary to provision services.
The summary dialogs from which you can use the logical service hyperlinks include:
For the dialogs that support the logical service oriented navigation feature, the access identifier (AID) text displays as blue text indicating that it is a hyperlink to the corresponding property dialog. Single clicking on any blue hyperlink will take you to the property dialog associated with the selected entity. For example, clicking on the subscriber ID in the View All Subscribers dialog opens the Subscriber Properties dialog for the selected subscriber. The dialog is the same as the one from the Port Configuration screen. The selected subscriber can be edited or deleted from this dialog.
Single clicking on the Cisco 6100 name will take you to the 6100 Chassis View. For summary dialogs displaying scoped views, selecting a property dialog on another Cisco 6100 will result in that 6100 Chassis View opening first.
Clicking on the Service Provisioning button will open the Service Provisioning dialog, where permanent virtual circuits (PVCs) may be added or deleted. When the dialog is dismissed, the View All Subscribers dialog is updated with the new configuration.
If you click on any text in the Line Port field as shown in Figure 1-36, you go immediately to the Module Properties status window displaying the LCC, slot, and port shown in that text to easily check what is happening on that port.
The following shows a Current Alarms window with blue hyperlinks:
Clicking on the text in the first line of the AID field will take you to the Module Properties window for the ATU-C in slot 10.
When you access any Cisco 6100 component, you will notice the similarities between the screens that appear. Most components have windows, tabs, and buttons very similar to each other as described below.
The properties windows for all chassis and modules in the Cisco 6100 Chassis View are similar to each other. To display the properties of a particular chassis or module, right click the mouse on a chassis or a module and select Properties option. This opens a Cisco 6100, chassis, or module property windows respectively. The windows contain similar features including a two-tiered tab design, overlaying a second, higher level set of tabs outside the basic property dialog tabs. The outside (higher level) sets of tabs lets you select between the module and any of the module's ports. The inside sets of tabs provide the same functionality as the basic property dialog tabs, allowing rapid selection between the selected module or port's Status and Configuration tabs.Use the tabs on the windows - typically the Status or Configuration tabs - to access property windows for other types of logical entities, such as subscribers or pools.
ViewRunner for HP OpenView uses common tabbed dialogs for all property dialogs (Status, Configuration, as so on). Attributes for an entity are displayed in a tabbed dialog. Each tab displays a category of information about the entity. Each tab is a dialog itself that may contain a tabbed control (for example, the module tab contains Status and Configuration Tabs). See "Cisco 6100 and ViewRunner State Management" for a discussion on entities.
Common tab categories used by entities display status, configuration, performance, and/or service provisioning, in this order. Only a subset of these tabs typically applies to any given entity. Module level tab categories, however, contain two levels of tabs. The top level module and port tabs display the common tab categories.
The following shows the tabs common to Cisco 6100 components:
ViewRunner for HP OpenView displays the Administrative and Operational states of the node as an icon on the module and port tabs of the Module Properties dialogs. The color of the LED (Light Emitting Diode) to the immediate left of the tab name indicates state of the module or port. See the appendix, "Use of Color in ViewRunner."
| Tab | Description |
|---|---|
Status | Displays the status of various states associated with a module or chassis. |
Configuration | Displays specifics about the configuration, such as inventory details, port information, etc. Also allows you to manage the Administrative states. |
ViewRunner for HP OpenView uses colors to show various states of entities. See "Use of Color in ViewRunner" for more information on ViewRunner's use of colors.
The following diagrams show the button common in ViewRunner for HP OpenView:
| Button | Description |
|---|---|
OK | The OK button applies configuration data in the property dialog and then closes the dialog. When the OK buttons is selected, ViewRunner for HP OpenView sends SNMP sets in a specific sequence to assure the configurations take affect immediately in the Cisco 6100. If the OK button is selected while the Administrative State is Unlocked, ViewRunner for HP OpenView allows the non-service affecting information to be modified. If the OK button is selected while the Administrative State is Locked, |
Cancel | The Cancel button closes the window without applying configuration data. It discards any changes made without requesting user confirmation.
|
Apply | The Apply button applies the configuration data entered by the user. |
Message dialogs of various types display as necessary to communicate particular instructions to you. These message dialogs are in addition to the event/alarm traps that are sent to one or more recipients. See "Multiple Trap Recipients" section for more information about traps and "Events and Alarms Management" for more information on events and alarms.
Two types of message dialogs are supported: confirmation and error.
Confirmation dialogs alert you to the consequences of carrying out a requested action, request a response, and interrupt normal interaction with the ViewRunner for HP OpenView application until the dialog is closed. Confirmation dialogs contain a confirmation icon, a message, a confirmation request, and Yes/No buttons.
In some instances, a confirmation message warns of the general consequences of proceeding. If the entity or any of its subordinates is involved in an active ADSL connection, a confirmation dialog is always presented indicating that the active connection(s) will be terminated if the action is not aborted.
The following actions result in confirmation dialogs appearing:
Error dialogs convey a message about a user error and detail the cause of the error. Error dialogs pop up when application, communication, or Cisco 6100 interaction errors occur. You must acknowledge that the error occurred to close the error dialog.
Error information dialogs appear if you leave a field required for configuration blank.
ViewRunner for HP OpenView communicates with Cisco 6100s using SNMP through either an overlay (out-of-band) IP network such as Ethernet or through an inband management channel over ATM. ViewRunner can lose communication with a Cisco 6100 for a variety of reasons, but a loss of communication error is generated when any ViewRunner initiated SNMP request does not succeed or when HP OpenView IP Discovery generates enough failures for a node.
When a loss of communication with a Cisco 6100 is detected, a pop up dialog appears indicating a "Loss of Communication with Cisco 6100 <name>". You must click OK before continuing. Because loss of communication can happen because of congestion in the network and for other reasons that may cause it to be intermittent, ViewRunner will continue to poll the Cisco 6100 at specific intervals (set by the COMMUNICATION_LOSS_TIMEOUT parameter) to see if it can establish communications.
There are four tools that can be used to manage the Cisco 6100 and ViewRunner for HP OpenView:
The configuration save and restore feature allows you to upload NVRAM to out-of-node storage to provide a backup of node configuration data. Downloading NVRAM back into an SC enables recovery from a corrupted or replaced SC. It also allows you to quickly recover your configuration after downloading updated Cisco 6100 software. (See "Updating Cisco 6100 Software" for more information.)
System software download is the method by which a Cisco 6100 can upgrade the software in each of the modules that support downloading to the module. The software download procedure requires an TFTP server. ViewRunner functions as an TFTP server and will be capable of handling requests for images from a Cisco 6100.
The process is triggered by user menu selection or SC reset. As a fail-safe measure, prior to initiating a system reset, the user should use the configuration save and restore wizard (see "Configuration Save and Restore") to store the current NVRAM configuration for later retrieval should something go wrong with software download.
ViewRunner for HP OpenView supports software downloads and restores for Cisco 6100 nodes being managed via the inband management channel or the ethernet management channel. The menu option allowing this feature is active only if the SC supports the feature and the node is being managed through one of the management channels. Warnings will be issued if software download/restore is not supported by the current SC.
The CLI feature provides the ability to retrieve fault management data from the Cisco 6100, using a Direct Connect serial interface or a telnet session. Multiple users can access a single Cisco 6100 simultaneously through independent telnet sessions.
The following are the input criteria for using the CLI:
Following are the common features for the data output formats:
The following errors will be displayed for invalid commands:
The following is the command syntax for CLI commands:
>verb [noun_1] [adjective_1] [noun_2] [adjective_2] [options]
where
verb | is the action/command need to be executed. Valid verbs are: | |
| help | lists all possible commands |
noun_1 | specifies the object on which command need to be executed. In the following example, alarms is the noun_1: Currently the only valid noun_1 is alarms. | |
adjective_1 | specifies the kind of noun or object. Adjective_1 is intelligent up to 3 unique characters/words. More than one adjective_1 can modify a noun_1, each separated by a period. In the following example, maj.crit are two adjective_1s: The valid adjective_1 entries are: | |
| crit | critical alarms |
| If you do not specify an alarm severity to be displayed, the system will display all alarms. | |
noun_2 | specifies the object on which the command is to be executed. This is generally a managed object of the Cisco 6100. The following command would return all critical alarms for all the chassis (MC and LCCs) for that Cisco 6100. Valid noun_2 objects are: | |
| sys | Cisco 6100 |
adjective_2 | specifies the kind of noun or object. Generally, adjective_2 is the instance of a Cisco 6100 managed object. Object instances vary with the type of objects. The entry takes the form of > show alarms [crit | maj | min] [noun_2] [c].[i].[s].[p] where c, i, s, and p indicate the following values: | |
| c | indicates the chassis, where m.0 = MC and l = LCC |
| In the following example, the command is to show all critical and major ATU-C alarms on Cisco 6100 multiplexer chassis (which is always chassis instance number 0) at slot 12: | |
options | to activate certain type of operation, i.e. filter. More than one option can be specified at one time, each separated by a period. Options are sensitive up to the first 3 characters; the rest will be ignored. | |
Using the inband management channel feature of the ViewRunner for HP OpenView allows direct control/management of the Cisco 6100 through the ATM channel. The inband management channel is transparent to ViewRunner in that provisioning and operation of the system are identical whether through the ethernet port or the inband channel. The only difference is that instead of using conventional ethernet physical media to communicate to the Cisco 6100, ViewRunner will use ATM as the physical layer for communication.
To run IP over ATM, the system uses RCF 1483 "Multi-protocol over AAL5" in Logical Link Control (LLC) encapsulation mode. This encapsulation will allow transporting via multiple protocols over a single VC.
To make sure the out-bound packets from the Cisco 6100 are sent to the right interface (ethernet or inband), a routing table for various IP addresses is also supported. This table is only needed when you use the inband management channel. Ethernet takes care of its own routing. See "System Level Configuration" for more information on the inband management channel.
Posted: Fri Oct 8 12:49:36 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.