cc/td/doc/product/dsl_prod/vrmgtsw/vr4ov/rel30
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

ViewRunner for HP OpenView Overview

ViewRunner for HP OpenView Overview

This chapter describes the ViewRunner for HP OpenView program, system files, navigational system, system dialog boxes, and management tools. This chapter contains the following sections:

ViewRunner Features

ViewRunner for HP OpenView is a carrier class Element Management System (EMS) that enables users to manage a network of Cisco 6100 Series systems. Following are some key features for ViewRunner:

Client/Server Architecture

ViewRunner is implemented in a client/server architecture. The server provides interfaces to Cisco 6100 Series systems 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 multiuser access regulation. When changes are made, broadcast services are used to propagate configuration or status changes to all clients through the use of icons, colors, and text.

When ViewRunner displays client information as dialog boxes are first opened, the status (state) and Administrative State information is retrieved from the Cisco 6100 Series system. All other configuration data is retrieved from the Oracle database.

Client dialog boxes 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 windows. Configuration, alarm, ViewMap, and OpenView map synchronization algorithms keep ViewRunner current with the node or network state.

For more information about the client/server architecture, please see the ViewRunner for HP OpenView Installation and Administration Guide.

Integration with HP OpenView and Oracle

ViewRunner for HP OpenView is the EMS for the Cisco 6100 Series digital subscriber line access multiplexer (DSLAM) system. It is the GUI application that provides you with full graphical functionality to manage Cisco 6100 Series nodes using the HP OpenView operating environment. ViewRunner for HP OpenView is fully integrated with HP OpenView to take advantage of certain OpenView capabilities.

ViewRunner for HP OpenView supports the discovery, configuration, and synchronization of Cisco 6100 Series equipment. Once you have installed ViewRunner for HP OpenView and established the connection to your Cisco 6100 Series system, ViewRunner for HP OpenView retrieves configuration data from the Cisco 6100 Series system SNMP Management Information Base (MIB) and synchronizes it with the Oracle database system for easy management and operation.

HP OpenView Features

The HP OpenView Network Node Manager 5.1x typically manages nodes within an IP segment, communicating by using the SNMP. The most important of the HP OpenView features where ViewRunner is concerned are as follows:

Application Integration

ViewRunner applications are integrated with HP OpenView in the following ways:

Inherent OpenView Capabilities

Some of the inherent OpenView capabilities used by ViewRunner include

Note This is nonstandard. SNMP normally uses User Datagram Protocol (UDP) for traps.

Integration with the Oracle RDBMS

Oracle is the RDBMS that is the repository for all Cisco 6100 Series system and ViewRunner configuration information.

As an RDBMS, Oracle allows flexible use of its table content. Oracle also provides Structured Query Language (SQL) access to that table content. The following is a list of the ViewRunner and Cisco 6100 Series system information stored in the Oracle database:

Some of the specific benefits of using Oracle include

Using the GUI to Manage Cisco 6100 Series Chassis and Modules

ViewRunner for HP OpenView is the GUI application that lets you configure and manage Cisco 6100 Series DSLAM. ViewRunner for HP OpenView supports the Cisco 6100 Series system autodiscovery of equipment, which means that once you have installed ViewRunner and connected it to your Cisco 6100 Series system, ViewRunner for HP OpenView retrieves configuration data from the Cisco 6100 Series system's Simple Network Management Protocol (SNMP) agent. It then displays a graphical representation of your Cisco 6100 Series system like the one shown in Figure 1-1.

ViewRunner for HP OpenView has three client applications---ViewMap, View Admin, and View LoopRunner. ViewMap contains hierarchical views of Cisco 6100 Series system networks as well as subtended configurations. It has a New Equipment window that contains newly discovered Cisco 6100 Series systems, and a New Subtend Cisco 6100s Group window showing newly discovered subtended Cisco 6100 Series systems. View Admin is used to define and administer users (operators) of the ViewRunner for HP OpenView client applications. View LoopRunner provides the primary GUI with which to manage Cisco 6100 Series systems.

Table 1-1 summarizes the compatibility among Cisco 6100 Series system and ViewRunner for HP OpenView software releases.


Table 1-1: ViewRunner for HP OpenView and Cisco 6100 Series System Release Compatibility
Cisco 6100 Series System Release1,2
3.0.0 2.4.1 2.4.0 2.3.x 2.2.1/
2.2.5 		2.2.0
ViewRunner for HP OpenView Release

3.0.0

Yes

Yes

Yes

Yes

Yes

Yes

2.4.1

No

Yes

Yes

Yes

Yes

Yes

2.4.0

No

No

Yes

Yes

Yes

Yes

2.3.5

No

No

No

Yes3

Yes

Yes

2.3.0

No

No

No

No

Yes3

Yes

2.2.0

No

No

No

No

No

Yes

1The Cisco 6130 chassis feature support is present in Release 2.4.0 or later.
2Systems with a Cisco 6100 installed must connect to the network through a POTS splitter. Therefore, a Cisco 6100 cannot support a Direct Connect without a POTS splitter configuration.
3The most recent FCM file may be required. ViewRunner will detect and display a warning if a newer FCM is required.

Viewing the Cisco 6100 from the ViewRunner Chassis View

The ViewRunner chassis view provides the top-level user interface to manage a single Cisco 6100 Series system.

There are three types of chassis in a Cisco 6100 Series system. The first two can be managed through ViewRunner for HP OpenView.

Note The Cisco 6120 chassis is not configured or monitored through ViewRunner because it is a passive device.

The chassis view shown in Figure 1-1 provides both menu bar operations and a bitmap front panel view of the Cisco 6100 Series system that displays color-coded status and administrative state icons of configured modules and module ports.

Note The chassis view differs depending on the configuration style you select. The view shown in Figure 1-1 displays the Direct Connect (DC) configuration style. The chassis view of a Digital Off-Hook (DOH) configuration, Figure 1-2, shows a Cisco 6110. See the ViewRunner for HP OpenView Installation and Administration Guide for information on choosing a configuration style.

Figure 1-1: 6100 Chassis View Dialog Box


In a DOH configuration, Figure 1-2, the 6100 Chassis View dialog box displays the Cisco 6100/6130 and each Cisco 6110. It also provides a top level display of modules, which you can view, add (preprovision), modify, and delete. From the 6100 Chassis View, you can view all status and administrative state information, manage all configurations, and check the performance of the Cisco 6100 Series.


Figure 1-2: DOH Configuration


The 6100 Chassis View displays colored module ejector tabs and icons that feature a lock and key to indicate the status and state of each module and its ports. The color of each ejector tabs that displays is based on a set of rules defined in Table 1-2, which describes the highest priority color that displays first and the lowest priority color that displays last, in cases where more than one of the conditions described is met. See "Using ViewRunner to Manage the Status of the Cisco 6100 Series System" for more information on states and see the Cisco 6100 Series with NI-1 Alarm Summary Guide for detailed information on alarms.


Table 1-2: Cisco 6100 Series Chassis View Operational State Colors
Tab Color Description

White

This state indicates that 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 6100 Series systems that are in loss of communication, but for which there is configuration information in the database.

Blue

This state indicates that the Cisco 6100 Series Slot State is Empty---Provisioned. This state occurs when the system controller has not communicated with the module, but a module configuration exists for the slot. This could occur when

  • ViewRunner (or any manager) preprovisions a module into an empty slot.

  • A module was configured in a slot but was not present during or since a system controller reset or insertion.

Red

This state indicates that a critical alarm is the most severe alarm present on the module or any of its ports.

Orange

This state indicates a major outstanding alarm on the module or any of its ports.

Yellow

This state indicates that a minor alarm is the least severe alarm present on the module or any of its ports.

Green

This state indicates that the module and all of its ports are in a Normal state.

Client dialog boxes are updated dynamically in real time while they are open. Changes detected by ViewRunner server applications are propagated to all ViewRunner clients when

Figure 1-3 shows the lock and key icons, as seen in slot 5, that display on the modules in the Chassis View dialog box indicating the administrative state of the module and its ports as described in Table 1-3.


Figure 1-3: Lock and Key Icon in Slot 5



Table 1-3: Cisco 6100 Series Chassis View Module and Port Administrative State Icons
Icon Module State Port State

Lock

Locked

Locked

Lock

Unlocked

Locked

UnLock

Unlocked

Unlocked

Lock and key

Unlocked

At least one port is locked

Managing Entities

To run ViewRunner for HP OpenView, you should also have some basic knowledge of the physical modules for the Cisco 6100 Series system. You can configure the following modules:

Note POTS splitter modules are not configured or monitored through ViewRunner.
Note Only Digital Off-Hook configurations use LIMs or LIM controller modules. Therefore, these entities are not managed in Direct Connect configurations.

For descriptions of these modules, consult the Cisco 6100 Series with NI-1 User Guide.

You should also have some basic knowledge of the logical entities for the Cisco 6100 Series system. Those logical entities are as follows:

Getting Information from System Files

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.

Note Updates to the RDF and FCM can be obtained from the Cisco CCO Web site or by contacting the Cisco Technical Assistance Center (TAC).

Identifying Release Compatibility with Hardware

A Release Definition File (RDF) identifies the software image that is compatible with each hardware module or revision for a given system release. During software updates, ViewRunner applies the selected RDF to the system controller. Multiple RDFs and associated images can be maintained in the ViewRunner directories. See the "Downloading Software Updates" section for more information about updating software.

The name of the RDF is 9000-xxx-xx.R, where "9000-xxx-xx" is the latest release of the system. You can file the RDF in the ViewRunner system folder. The RDF contains information about the software and hardware release for the Cisco 6100 Series components.

The following text is an example of an RDF:

9000-xxx-xxR,Production Release 2.4.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

Determining Feature Compatibility

Another key system file is the system controller 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 you. This customization is based on the system controller release loaded on the Cisco 6100 Series system.

For example, an older release of a Cisco 6100 Series LIM controller module does not support the newer feature that allows the Administrative State to lock all entities automatically before deleting a chassis. Therefore, ViewRunner consults the compatibility matrix to determine that it should disable the Delete Chassis option if you have not locked the module.

Newer Cisco 6100 Series releases can be managed by ViewRunner without updating this file; however, you are warned each time a client opens the 6100 Chassis View dialog box if the system controller software for that node is not recognized. The ViewRunner Error dialog box shown in Figure 1-4 is generated when you connect to a Cisco 6100 Series system containing a system controller software version that is not found in the FCM file.


Figure 1-4: ViewRunner Error Dialog Box


In these cases, ViewRunner presents a default system controller feature set to the user that corresponds to the features in the last recognized system controller system release. Any newer features on the system controller are not accessible. An updated FCM file can be obtained at the Cisco CCO Web site or by contacting Cisco TAC. Obtaining a newer FCM file can 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 Parms,,,
BEGIN,,,,,,,,,,,,,,,,,,,
9651-001-07,,,,,,,,,,,,,,,,,,,
9651-001-09,,,,,,,,,,,,,,,,,,,
9651-001-12,DIRECT,,,,,,,,,,,,,,,,,,
9651-001-13,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,
9651-001-15,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,
9651-001-20,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,,,,
9651-001-21,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX
9651-001-22,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-23,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS, 
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-24,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-25,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-26,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS, 
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
default,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS,,,
END,,,,,,,,,,,,,,,,,,,
 
Note: 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 an SC software 
version that is not recognized, a warning dialog will notify" the 
user to obtain a newer version of the file. The SCFeatureCapabilityMatrix.csv 
file 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."
BEGIN,,,,,,,,,,,,,,,,,,,
System Part #,LoopRunner Rel,Contains SC SW,,,,
9000-001-03,1.02 release,9651-001-07,,,,
9000-001-04,1.02A release,9651-001-09,,,,
9000-001-06,1.02C release,9651-001-12,,,,
9000-001-07,2.0 release,9651-001-13,,,,
9000-001-09,2.1.0 release,9651-001-15,,,,
9000-001-10,2.1.1 release,9651-001-15,,,,
9000-001-11,2.1.2 release,9651-001-15,,,,
9000-001-12,2.2.0 release,9651-001-20,,,,
9000-001-13, 2.1.3 release, 9651-001-21,,,,
9000-001-12, 2.2.0 release, 9651-001-20,,,,
9000-001-14, 2.2.1 release, 9651-001-22,,,,
9000-001-15, 2.2.0.101 release, 9651-001-23,,,,
9000-001-16, 2.2.5.100 release, 9651-001-24,,,,
9000-001-18, 2.2.0.102 release, 9651-001-25,,,,
9000-001-19, 2.2.0.103 release, 9651-001-25,,,,
9000-001-20, 2.2.5.102 release, 9651-001-26,,,,
9000-001-21, 2.2.5.103 release, 9651-001-26,,,,
END,,,,,,,,,,,,,,,,,,,
 
Feature Description,,,,,,
DIRECT,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 NVRAM,,,,,,,,,,
PPDATUC,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 basis,,,,,,,,,,
INBANDCH,Support for LoopRunner inband management channel and 
	associated Routing Table support,,,,,,,,,,
TRAPRCVRS,Support for multiple trap recipients,,,,,,,,,,
SUBSCRTIMEOUT,"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 Configuration Files

ViewRunner maintains configuration files that customize ViewRunner operation. The following files are read when ViewRunner servers are started up:

Software Upgrade Defaults

During software upgrade, when moving to a release that supports new subscriber data that is not supported in your previous release, defaults are taken from the vrconstants.conf file instead of relying on node defaults. This allows you to upgrade software and get default subscriber values set to the site defaults.

ViewRunner Log Files

ViewRunner for HP OpenView maintains log files for all its server processes. These files log key events into text files that 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 for use when troubleshooting problems with ViewRunner and the Cisco 6100 Series system. Figure 1-5 provides an example listing of the log files.


Figure 1-5: ViewRunner Log Files


Figure 1-6 is an example of the vrProcessMon.log.1225 log file from Figure 1-5 illustrating the types of events that are logged.


Figure 1-6: Partial ViewRunner Log


Obtaining Online Help

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 windows through the Help option on the menu bar.

For example, access help for HP OpenView Windows by selecting Help > On Window on the menu bar in the Root view, as shown in Figure 1-7.


Figure 1-7: HP OpenView Help


ViewRunner's ViewMap application is responsible for displaying the logical containment hierarchy for Cisco 6100 Series equipment in a customer's network.

Because ViewMap is integrated with HP OpenView map, online Help can give you a detailed look at how the map function works.

Table 1-4 provides the overall Root window hierarchy. For more information, see Navigating in ViewMap.


Table 1-4: Hierarchy from the Root Window

Internet

Note Does not display in the root window if IP Map is disabled when creating the map.

New Equipment Window

World

Location(s)

Wire Center

Cisco 6100

Subtend locations

New Subtend Cisco 6100s

Figure 1-8 and Figure 1-9 describe the anatomy of a submap in HP OpenView and, therefore, for ViewRunner.


Figure 1-8: HP OpenView Windows Help



Figure 1-9: HP OpenView Windows Help (continued)


Integrating ViewMap with HP OpenView

The ViewRunner ViewMap application is responsible for displaying logical views of the Cisco 6100 Series equipment in your network. ViewMap-enabled maps coexist with other vendors' applications, such as HP's IP Map application. ViewMap is integrated into the IP Map polling process, so if autodiscovery of Cisco 6100 Series equipment is desired, IP Map must be enabled for the map and IP Polling must be set. See "Managing ViewRunner Maps and Views," for details on creating and using ViewMap maps.

Using the Map Interface

ViewRunner ViewMap is modeled after the HP OpenView map functions. Figure 1-10 shows how HP OpenView Help describes maps and, therefore, the ViewMap maps.


Figure 1-10: HP OpenView Map Help


Using Submaps

ViewMap makes use of HP OpenView submaps to create the various levels of the hierarchy. ViewMap does not support independent submaps. Figure 1-11 shows the HP OpenView Help information on submaps. See Navigating in ViewMap for more information.


Figure 1-11: HP OpenView Submaps Help


Using Objects

An object represents a particular entity or resource in a networked system. ViewMap uses standard HP OpenView objects and some of its own. ViewMap uses the following objects:

Figure 1-12 shows the HP OpenView Help information about objects.


Figure 1-12: HP OpenView Objects Help


Using Symbols

ViewMap uses standard OpenView symbols for the World and Location domains. It uses Cisco icon symbols to represent

Prior releases (for example, before version 2.3.5) used some symbol and field names in HP OpenView maps that are different from those used in this release. Table 1-5 lists the old and new names used in each HP OpenView window.


Table 1-5: Old and New Names used in HP OpenView Windows
Window Old Name New Name

HP OpenView Root Window

Subtend Networks

Subtend Locations

New Subtend LoopRunners

New Subtend Cisco 6100 Series systems

HP OpenView Classes

NetSpeed

CiscoDSL

NetSpeedConnection

(removed)

LoopRunnerPort

(removed)

NIConnection

(removed)

HP OpenView Subclasses

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)

Figure 1-13 provides an example of the HP OpenView Help definition for symbols.


Figure 1-13: HP OpenView Symbols Help


Map Permissions

By default, the ovw (graphical network map) program is executable by anyone who has UNIX write permission on the map files. Although everyone can 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 map have read-only access. When the person who has read-write access closes the map, another user can 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.

Map Synchronization

ViewRunner adds capability to the basic HP OpenView map functions. OpenView imposes restrictions that ViewMap does not because ViewRunner uses an Oracle database as its repository for map information. The following subsections describe first the OpenView restrictions and second the ViewMap added capabilities.

Operating the HP OpenView Map

There are two types of maps possible in OpenView.

Synchronizing ViewRunner ViewMaps

The ViewRunner ViewMap application supports multiple simultaneous read-write maps. A user can have more than one 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 are propagated to other read-write maps immediately.

Each ViewRunner ovw session maintains a log of the map modifications made since the client session was begun. You can access the ViewMap log to determine the reasons a refresh of the map might be needed. Note that the Map > Refresh Map option is available on the menu only when a user's map is not up-to-date. Following is a list of map sychronization rules:

You can 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.

Navigating in ViewMap

The ViewMap client application provides you with a hierarchal view of a Cisco 6100 Series equipment network. View LoopRunner provides you with a front panel view of a selected Cisco 6100 Series system, allowing you to view the status of that Cisco 6100 Series system, manage its configuration, and check its performance. Table 1-6 provides the overall Root window hierarchy.


Table 1-6: Hierarchy from the Root Window

Internet

Note Does not display in the root window if IP Map is disabled when creating the map.

New Equipment Window

World

Location(s)

Wire Center

Cisco 6100

Subtend locations

New Subtend Cisco 6100s

The Cisco 6100 Series system 6100 Chassis View window is provided by the View LoopRunner application, which is discussed in the "View LoopRunner" section. The other views are provided by the ViewMap application. An example of the view hierarchy is found in Figure 1-14. ViewRunner for HP OpenView allows you to double-click a Cisco 6100 Series icon in ViewMap to open the chassis view for that node.


Figure 1-14: ViewMap Hierarchy Views


Navigating among these views is accomplished by 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 Series symbols allow rapid navigation. Double-clicking a Cisco 6100 Series symbol opens the chassis view for that node.

Another view of the hierarchy can be found in Figure 1-15, which shows a geographically based hierarchy of windows beginning with the Root window and going all the way down to a Wire Center that is provisioned with Cisco 6100 Series systems. The diagram in Figure 1-15 gives a more detailed view of the interactions between windows and views.


Figure 1-15: Navigation Diagram


Navigating in the ViewRunner Chassis View

ViewRunner for HP OpenView supports several navigation methods.

Viewing Menus with a Right-Click

A mechanism for retrieving information about a particular module or chassis is the right mouse button. The right-click provides a shortcut method for displaying properties about a particular module or chassis.

Use the right button of the mouse to bring up the menu containing a list of options available for a particular module. Menus are also context sensitive depending on which chassis, module, or slot is beneath the cursor when the right button is selected.

Placing the cursor over the chassis but outside of the slots selects the chassis. Menu options are dimmed for users who do not have necessary privileges, or when a menu option is not supported based on the current configuration.

Figure 1-16 through Figure 1-24 are examples of menus that provide options when you right-click a particular component.

Right-Clicking on the Cisco 6100/6130 Chassis

The options in Figure 1-16 display when you right-click the Cisco 6100/6130.


Figure 1-16: Cisco 6100/6130 Chassis View Menu



Table 1-7: Cisco 6100/6130 Chassis Menu Options
Menu Option Description

Synchronize 6100 Configuration

Initiates the sequence of SNMP messages that are required to reconcile the ViewRunner database with the Cisco 6100 Series configurations. This menu option rediscovers Cisco 6100 Series equipment and configurations.

Synchronize 6100 Alarms

Initiates the sequence of SNMP messages to reconcile the alarm table in the ViewRunner database with the current state of the Cisco 6100 Series system.

6100 Properties

Allows you to check and set properties common to the entire Cisco 6100 Series system such as the current date and time for the Cisco 6100 Series system.

Pool Properties

Opens the Pool Properties configuration dialog box (DOH configurations only).

Active Connections

Opens the Active Connections view, displaying a list of the currently active ATU-C or STU-C port-to-line-port connections in the Cisco 6100 Series system. This dialog box supports logical service-oriented navigation.

View All Subscribers

Allows you to view all the subscribers for a node, subtend group, or Wire Center. This dialog box supports logical service-oriented navigation.

View All PVCs

Allows you to view all of the subscribers defined for the Cisco 6100 Series system, subtend group, or Wire Center along with their configured PVCs. This dialog box supports logical service-oriented navigation.

View Equipment Inventory

Allows you to view an inventory of all the equipment in the Cisco 6100 Series system, subtend group, or Wire Center. This dialog box supports logical service-oriented navigation.

6100 Performance

Allows you to view Cisco 6100 Series 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 dialog box displaying all the currently asserted alarms in the Cisco 6100 Series system. This dialog box supports logical service-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 Series system through an inband channel rather than through the Ethernet channel.

Add Chassis

Allows an operator with sufficient privileges to preprovision a new Cisco 6110 for the Cisco 6100 Series.

Right-Clicking on the Cisco 6110 chassis

The options in Figure 1-17 display when you right-click the Cisco 6110.


Figure 1-17: Cisco 6110 View Menu



Table 1-8: Cisco 6110 Menu Options
Menu Options Description

Chassis Properties

Displays the backplane revision number for this LIM chassis.

Delete Chassis

Allows you to delete the Cisco 6110. Unless the LIM controller is set to Administrative State Locked, the option to delete the chassis is dimmed. (ViewRunner for HP OpenView automatically locks all modules, ports, and subscribers before deleting all the module configurations.)

Right-Clicking a Module

Selecting the Module Properties option brings up the Module Properties dialog box, which displays properties about a particular module. Each dialog box has a number of tabs associated with it. The number of tabs shown in the dialog box depends on the type of module.

The number of port options displayed in the module menu is context sensitive depending on the type of module selected. For example, the system controller menu has no port options, the LIM module menu has four port options, and the ATU-C module menu has two port options.

If you access any Cisco 6100 Series component, notice the similarities between the dialog boxes that appear. Most components have dialog boxes, tabs, and buttons very similar to each other as described in the "Identifying the Common Elements of the ViewRunner GUI" section.

Right-Clicking on ATU-C Modules

The options in Figure 1-18 display when you right-click an ATU-C module.


Figure 1-18: ATU-C Module Properties Menu


Right-Clicking on STU-C Modules

The options in Figure 1-19 display when you right-click an STU-C module.


Figure 1-19: STU-C Module Properties Menu



Table 1-9: STU-C Module Menu Options
Menu Option 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

This option is dimmed unless the you lock the module or all of its ports. Deletes the specified module from the Cisco 6100 Series system. This option is always dimmed for users with read-only privileges and on the system controller module.

Chassis

Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Chassis.

Right-Clicking on LIMs

The options in Figure 1-20 display when you right-click a LIM.


Figure 1-20: LIM Properties Menu



Table 1-10: ATU-C and LIM Menu Options
Menu Option 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

This option is dimmed unless the you lock the module or all of its ports. Deletes the specified module from the Cisco 6100 Series system. This option is always dimmed for users with read-only privileges and on the system controller module.

Chassis

Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to the Delete Chassis.

Right-Clicking the System Controller Module

The options in Figure 1-21 display when you right-click the system controller module.


Figure 1-21: System Controller Module Properties Menu



Table 1-11: System Controller Module Menu Options
Menu Option Description

Module Properties

Gives you direct access to the Status or Configuration tabs for a particular module.

Delete Module

This option is always dimmed for the system controller module.

Chassis

Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Chassis.

Right-Clicking the LIM Controller Module

The options in Figure 1-22 display when you right-click the LIM controller module.


Figure 1-22: LIM Controller Module Properties Menu



Table 1-12: LIM Controller Module Menu Options
Menu Option Description

Module Properties

Gives you direct access to the Status or Configuration tabs for a particular module.

Delete Module

The Delete Module option is unavailable on the 6100 node software version. For versions that allow locking of the LCM, only the LCM should be locked. For all other versions, all the LIM modules should be locked.

Chassis

Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Module.

Right-Clicking a Cisco 6100/6130 Empty Slot

Figure 1-23 shows the options that appear when you right-click an empty slot in the Cisco 6100/6130.


Figure 1-23: Cisco 6100/6130 Empty Slot Menu



Table 1-13: Cisco 6100/6130 Empty Slot Menu Options
Menu Option Description

Insert

Opens a dialog box containing a visual representation of the modules that can be preprovisioned in the selected slot.

6100 Properties

Gives you direct access to the Cisco 6100 Status or Configuration tabs.

Right-Clicking a Cisco 6110 Empty Slot

The options in Figure 1-24 appear when you right-click an empty slot in the Cisco 6110.


Figure 1-24: Cisco 6110 Empty Slot Menu



Table 1-14: Cisco 6110 Empty Slot Menu Options
Menu Option Description

Insert

Opens a dialog box containing a visual representation of the modules that can be preprovisioned 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 not available unless all modules are locked or deleted first.

Double-Clicking Entities

Another mechanism for viewing information on a chassis or module is to place your cursor on the entity and double-click the left button on your mouse. The double-click method automatically displays the window views.

Double-Clicking the Cisco 6100/6130 Chassis

Placing your cursor on the chassis displays the Cisco 6100/6130 Properties Window. Double-clicking the Cisco 6100/6130 opens to the Status tab on the 6100 Properties dialog box.

Figure 1-25 shows the Cisco 6100 chassis Status tab.


Figure 1-25: 6100 Properties Window


Double-Clicking a Module

Placing your cursor on any module and double-clicking displays the Module Properties dialog box, Port, Status, and Configuration tabs. Figure 1-26 shows the Module Properties dialog box, Status tab.

Note You can access the Status and Configuration tabs on the Module Properties dialog boxes in several ways, including using the right mouse button menu options, menu bar options, navigation buttons on dialog boxes, double-clicking hyperlinks within dialog boxes, and simply double-clicking the chassis or modules. The instructions in this document present one access method---right-clicking the Chassis View to access the chassis and module or port menus. You can, of course, access these menus by using your own preferred method.

Figure 1-26: Module Properties Dialog Box


Navigating by Using the Toolbar

As a second means of navigation, HP OpenView has a toolbar that allows you to bypass the menu hierarchy to perform certain tasks. Figure 1-27 shows the HP OpenView toolbar.


Figure 1-27: HP OpenView Toolbar


Clicking on an icon on the toolbar performs the task indicated by the icon. See the HP OpenView Help system for more information on each of the icons. Figure 1-28 shows an example of another toolbar that is found in the 6100 Chassis View window.


Figure 1-28: 6100 Chassis View Toolbar


The icons for the toolbar in Figure 1-28 are described from left to right in Table 1-15.


Table 1-15: Chassis View Toolbar Icon Description
Chassis View Toolbar Icon Icon Description

Synchronize 6100 Configuration

Initiates the sequence of SNMP messages required to reconcile the ViewRunner database with the Cisco 6100 Series configurations. This menu option rediscovers Cisco 6100 Series equipment and configurations.

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 Series system.

6100 Current Alarms

Opens an alarm dialog box displaying all the currently asserted alarms in the Cisco 6100 Series system. This dialog box supports logical service-oriented navigation.

Zoom Out

Shrinks the 6100 Chassis View window.

Zoom In

Enlarges the 6100 Chassis View window.

Current Alarms Count

Displays the number of currently asserted alarms that are critical (red), major (orange), and minor (yellow).

Navigating Through the Menu Hierarchy

As another means of navigation, the menu hierarchy in ViewRunner for HP OpenView consists of a menu bar with menus and options. Figure 1-29 through Figure 1-40 show each of the menus in the Root window of ViewRunner. Selecting options from these menus allows you to provision, operate, and monitor Cisco 6100 Series systems within your network. These menu options are discussed in subsequent chapters in this manual.


Figure 1-29: Root Window



Figure 1-30: Map Menu



Figure 1-31: Edit Menu



Figure 1-32: Locate Menu



Figure 1-33: View Menu



Figure 1-34: Performance Menu



Figure 1-35: Configuration Menu



Figure 1-36: Fault Menu



Figure 1-37: Security Menu



Figure 1-38: Miscellaneous Menu



Figure 1-39: Options Menu



Figure 1-40: Help Menu


Using Logical Service-Oriented Navigation

ViewRunner for HP OpenView supports logical service-oriented navigation, which allows rapid navigation to a module, port, or subscriber properties dialog box from the summary dialog boxes through a process similar to hyperlinks.

Logical service-oriented navigation eliminates the need to bring up the craft-oriented chassis view and click 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 6100 Chassis View window, you can still double-click an entity in the 6100 Chassis View and access the properties dialog boxes necessary to provision services.

The summary dialog boxes from which you can use the logical service hyperlinks include

For the dialog boxes 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 box. Clicking any blue hyperlink takes you to the property dialog box associated with the selected entity. For example, clicking the subscriber ID in the View All Subscribers dialog box or from the Performance dialog box opens the Subscriber Properties dialog box for the selected subscriber. The dialog box is the same as the one from the Port Configuration dialog box. The selected subscriber can be edited or deleted from this dialog box.

Clicking the Cisco 6100 Series system name takes you to the 6100 Chassis View window. For summary dialog boxes displaying scoped views, selecting a properties dialog box on another Cisco 6100 Series system results in that 6100 Chassis View window opening first.

Clicking Service Provisioning opens the Service Provisioning dialog box, where PVCs can be added or deleted. When the dialog box is dismissed, the View All Subscribers dialog box is updated with the new configuration. See Figure 1-41 for an example of the View All Subscribers hyperlinks.


Figure 1-41: View All Subscribers Hyperlinks


If you click on any text in the Line Port column, as shown in Figure 1-41, you go immediately to the Module Properties Status dialog box that displays the Cisco 6110, slot, and port shown in that text to easily check what is happening on that port as shown in Figure 1-42.


Figure 1-42: Line Port Hyperlinks


Figure 1-43 shows a Current Alarms dialog box with blue hyperlinks.


Figure 1-43: Current Alarms Dialog Box with Hyperlinks


Clicking on the text in the first line of the AID field takes you to the Module Properties dialog box for that ATU-C module.

Identifying the Common Elements of the ViewRunner GUI

When you access any Cisco 6100 Series component, notice the similarities between the dialog boxes that appear. Most components have dialog boxes, tabs, and buttons very similar to each other as described in the following sections.

Identifying Common Dialog Boxes Features

The properties dialog boxes for all chassis and modules in the Cisco 6100 Series 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 the Properties option. This opens a Cisco 6100 Series system, chassis, or module properties dialog box respectively.

The dialog boxes contain similar features including a two-tiered tab design, overlaying a second, higher level set of tabs outside the basic properties dialog box tabs. The outside (higher level) set of tabs lets you select between the module and any of the module's ports. The inside set of tabs provide the same functionality as the basic properties dialog box tabs, allowing rapid selection between the selected module or port's Status and Configuration tabs. Use the tabs on the dialog boxes---typically the Status or Configuration tabs---to access properties dialog boxes for other types of logical entities, such as subscribers or pools.

Identifying Common Tab Elements

ViewRunner for HP OpenView uses common tabbed dialog boxes for all properties dialog boxes (Status, Configuration, and so on). Attributes for an entity display in a tabbed dialog box. Each tab displays a category of information about the entity. Each tab is a dialog box itself that might contain a tabbed control (for example, the module tab contains Status and Configuration tabs). See "Using ViewRunner to Manage the Status of the Cisco 6100 Series System," for a discussion on entities.

Common tab categories used by entities display status, configuration, performance, 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.

Figure 1-44 and Figure 1-46 show the tabs that are common to Cisco 6100 Series components.

Note The LIM tabs do not apply in Direct Connect configurations.

ViewRunner for HP OpenView displays the Administrative and Operational states of the node as icons on the module and port tabs of the Module Properties dialog box. The bell icon to the immediate left of the tab name indicates the state of the module or port. Use of color indicates operational state similar to the ejector tabs. See "Use of Color in ViewRunner." The lock icon displays when the module and all ports are locked or when the module is unlocked, but all ports are locked. See the "Viewing the Cisco 6100 from the ViewRunner Chassis View" section for more information on the lock and key icons.


Figure 1-44: ATU-C Module Tabs



Figure 1-45: STU-C Module Tabs



Figure 1-46: LIM Tabs



Table 1-16: ATU-C, STU-C, and LIM Tab Descriptions
Tab Description

Status

Displays the status of various states associated with a module or chassis.

Configuration

Displays specific configuration information, such as inventory details, port information, and so on. Also allows you to manage the administrative states.

Common Colors

ViewRunner for HP OpenView uses colors to show various states of entities. See "Use of Color in ViewRunner," for more information on the use of color in ViewRunner.

Identifying Common Buttons

Figure 1-47 shows the buttons common in ViewRunner for HP OpenView. Table 1-17 provides descriptions of these buttons.


Figure 1-47: Common Buttons



Table 1-17: Common Button Descriptions
Button Description

OK

The OK button applies configuration data in the property dialog box and then closes the dialog box.

When OK is selected, ViewRunner for HP OpenView sends SNMP sets in a specific sequence to ensure that the configurations take effect immediately in the Cisco 6100 Series system.

If OK is selected while the Administrative State is Unlocked, ViewRunner for HP OpenView allows the nonservice-affecting information to be modified.

If OK is selected while the Administrative State is Locked, ViewRunner for HP OpenView locks the resource and sends all configuration information that has been modified.

Cancel

The Cancel button closes the dialog box without applying configuration data. It discards any changes made without requesting user confirmation.

Apply

The Apply button applies the configuration data you enter.

Identifying Message Dialog Boxes

Message dialog boxes of various types display as necessary to communicate particular instructions to you. These message dialog boxes are in addition to the event and alarm traps that are sent to one or more recipients. See the "Setting Multiple Trap Recipients" section for more information about traps and "Viewing Events and Alarms," for more information on events and alarms.

Two types of message dialog boxes, confirmation and error, are supported by ViewRunner for HP OpenView. They are discussed in the following sections.

Viewing Confirmation Dialog Boxes

Confirmation dialog boxes alert you to the consequences of carrying out a requested action, request a response from you, and interrupt normal interaction with the ViewRunner for HP OpenView application until the dialog box is closed. Confirmation dialog boxes 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 box is always presented indicating that the active connection(s) terminate if the action is not aborted.

The following actions result in confirmation dialog boxes appearing:

Viewing Error Information Dialog Boxes

An error information dialog box conveys a message about a user error and details the cause of the error. Error information dialog boxes display when application, communication, or Cisco 6100 Series interaction errors occur. You must acknowledge that the error occurred to close the error information dialog box.

Error information dialog boxes appear if you leave a field blank that is required for configuration.

Viewing SNMP Loss of Communication Dialog Boxes

ViewRunner for HP OpenView communicates with Cisco 6100 Series systems 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 Series system for a variety of reasons, but a loss of communication error information dialog box 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 Series system is detected, a dialog box appears indicating a "Loss of Communication with Cisco 6100 Series system <name>". You must click OK before continuing. Because loss of communication can happen due of congestion in the network and for other reasons that can cause it to be intermittent, ViewRunner continues to poll the Cisco 6100 Series system at specific intervals (set by the COMMUNICATION_LOSS_TIMEOUT parameter) to see if it can establish communications.

Managing ViewRunner for HP OpenView and the Cisco 6100 Series System

There are four tools that can be used to manage the Cisco 6100 Series systems and ViewRunner for HP OpenView.

Saving and Restoring Configuration Data

You can back up node configuration data by using the configuration save and restore tool. Using this tool, you can upload nonvolatile random access memory (NVRAM) to out-of-node storage. Then you can download the NVRAM back into a system controller, which enables recovery from a corrupted or replaced system controller. You can also use the save and restore tool to quickly recover your configuration after downloading updated Cisco 6100 Series software.

See "Using the Configuration Save and Restore Feature," for more information on saving and restoring configuration data.

Caution Do not edit the saved file. Restoration of the configuration is unpredictable if the file is edited and could result in a corruption of the system and loss of service for subscribers.

Downloading Software Updates

To take advantage of software updates, you need to download new system software from a TFTP server when it becomes available.

As a fail-safe measure, prior to initiating a system reset, you should use the configuration save and restore wizard (see "Using the Configuration Save and Restore Feature") to store the current NVRAM configuration for later retrieval, in case you experience problems with the software download.

Software download restores the subtend details of the node that is being updated to preserve the connections. However, you can choose not to restore the subtend information node.

Using the In-band Channel Software Download Feature

ViewRunner for HP OpenView supports software downloads and restores for Cisco 6100 Series nodes being managed through the inband management channel or the ethernet management channel. The menu option that allows this feature is active only if the system controller supports the feature and the node is being managed through one of the management channels. Warnings are issued if software download or restore is not supported by the current system controller.

The inband management channel is discussed in detail in "Configuring the System."

Using the Command Line Interface Feature

You can use the command line interface (CLI) to retrieve fault management data from the Cisco 6100 Series system. The system must have a Direct Connect serial interface or be running a Telnet session. Several users can access a single Cisco 6100 Series system simultaneously through independent Telnet sessions.

Currently, the only valid CLI commands display alarms on various managed objects.

Guidelines for Inputting Commands into the CLI

Be aware of the following input criteria when you use the CLI:

Guidelines for Inputting Commands into the CLI

Be aware of the following input criteria when you use the CLI:

Guidelines for Getting Output from the CLI

Data output formats can include the following common features:

Determining Invalid Commands from the CLI

Table 1-18 lists the errors that display for invalid commands.


Table 1-18: Error Messages---Invalid Commands
Error Message Description

Too many arguments passed

You have entered too many arguments.

No response from Cisco 6100 Series system

The CLI was unable to get a response from either the management interface manager (MIM) or the fault manager (FM).

Invalid argument n

An argument n is invalid (where n is a number between 1 and 5).

Invalid first object instance

An instance specified for first object is invalid.

Invalid second object instance

An instance specified for second object is invalid.

Using the Command Syntax

Use the following command syntax for CLI commands:

>verb [noun_1] [adjective_1] [noun_2] [adjective_2] [options]

verb

Designates the action/command to be executed. Valid verbs include:

help
?
show

Lists all possible commands
Lists all possible commands
Retrieves and displays data on dialog box

noun_1

Specifies the object on which the command is to be executed. In the following example, alarms is the noun_1:

> show alarms sys

Currently the only valid noun_1 is alarms.

adjective_1

Specifies the kind of noun or object. Adjective_1 is intelligent up to three unique words. More than one adjective_1 can modify a noun_1. You must use a period to separate each pair of connective terms. In the following example, maj.crit is two adjective_1s:

> show alarms maj.crit sys

The following words are valid adjective_1 entries:

crit

maj

min

Critical alarms

Major alarms

Minor alarms

If you do not specify an alarm severity to be displayed, the system displays all alarms.

noun_2

Specifies the object on which the command is to be executed. This command is generally a managed object of the Cisco 6100 Series system. The following command returns all critical alarms for all of the Cisco 6100 Series system chassis:

> show alarms crit chas

Valid noun_2 objects are

sys

chas

slot

sc

ni

atuc

lim

lcm

shm

lp

mp

Cisco 6100 Series system

Cisco 6100 Series chassis

Slot in any chassis

System controller module

Network interface module

ATU-C module

Line interface module

LIM controller module

Subtend host module

Line port

Modem port

adjective_2

Specifies the kind of noun or object. Generally, adjective_2 is the instance of a Cisco 6100 Series managed object. Object instances vary with object type.

The entry takes this form

> 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 = Cisco 6100/6130

and l = Cisco 6110

i

Indicates the chassis instance. For the Cisco 6100/6130, the value is always 0. For the Cisco 6110, the value is the DIP switch setting for that Cisco 6110.

s

Indicates the slot number of the object. The value corresponds to the slot number on the chassis where the object is physically located.

p

Indicates the port number of the object. The value is 1 to 4 with the actual number being determined by the port on the object. Ports are identified from the top down starting with 1. Currently, only the CAP ATU-C, STU-C, LIM, and STM ports are supported.

In the following example, the command is to show all critical and major CAP ATU-C and STU-C alarms on the Cisco 6100/6130 chassis (which is always chassis instance number 0) at slot 12:

> show alarms crit.maj atuc m.0.12.2

options

To activate certain types of operations, you can specify more than one option at one time. You must use a period to separate every two consecutive options from each other. Options are sensitive up to the first three characters; the remaining characters are ignored.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Mar 2 10:16:22 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.