ViewRunner for HP OpenView Overview

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

1.1 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:

HP OpenView integration coexists with other vendors' management applications.
UNIX client/server design supports multiuser operation.
Dynamic graphical user interface (GUI) displays near real-time network status.
Oracle Relational Database Management System (RDBMS) stores a cache of all Cisco 6100 Series configurations.
Autodiscovers all Cisco 6100 Series nodes.
EMS management, including fault, configuration, accounting, performance, and security (FCAPS) of Cisco 6100 Series networks.

1.2 Understanding Cisco 6100 Series Chassis and Modules

ViewRunner for HP OpenView is the GUI application that lets you configure and manage Cisco 6100 Series Advanced Digital Subscriber Line Access Multiplexers (ADSLAM). 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 the Cisco 6100 Series and ViewRunner for HP OpenView releases.

Table 1-1: ViewRunner and Cisco 6100 Series System Release Compatibility Matrix
Cisco 6100 Series System Release

2.4.0 2.3.1 2.3.0 2.2.1/
2.2.5 2.2.0 2.1.3 2.1.2

Cisco 6130 ¹ Cisco 6100 ²

ViewRunner for HP OpenView Releases

2.4.0

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

2.3.5

No

No

Yes

Yes

Yes

Yes

Yes

Yes

2.3.0

No

No

Yes³

Yes³

Yes⁴

Yes

Yes

Yes

2.2.0

No

No

Yes⁵

Yes⁵

Yes⁵

Yes

Yes

Yes

¹The Cisco 6130 multiplexer chassis (MC) feature support present in Release 2.4.0 or higher.
²Systems with a Cisco 6100 MC installed must connect to the network through a Cisco PSC to provide the secondary lightning protection required by NEBS. Therefore, a Cisco 6100 MC cannot support a Direct Connect without PSC configuration.
³ViewRunner manages this Cisco 6100 Series system as a 2.2.1 release. ViewRunner presents a feature set corresponding to the capabilities of the Cisco 6100 Series system release noted. When you open Chassis View, ViewRunner tells you that the feature set is not recognized and that a default feature set is
being used.
⁴FCM update for 2.2.5 required.
⁵ViewRunner manages this Cisco 6100 Series system as a 2.2.0 release. ViewRunner presents a feature set corresponding to the capabilities of the Cisco 6100 Series system release noted. When you open Chassis View, ViewRunner tells you that the feature set is not recognized and that a default feature set is
being used.

**Table 1-1: ViewRunner and Cisco 6100 Series System Release Compatibility Matrix**
	Cisco 6100 Series System Release
	2.4.0	2.3.1	2.3.0	2.2.1/ 2.2.5	2.2.0	2.1.3	2.1.2
	Cisco 6130 ¹	Cisco 6100 ²
ViewRunner for HP OpenView Releases
2.4.0	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
2.3.5	No	No	Yes	Yes	Yes	Yes	Yes	Yes
2.3.0	No	No	Yes³	Yes³	Yes⁴	Yes	Yes	Yes
2.2.0	No	No	Yes⁵	Yes⁵	Yes⁵	Yes	Yes	Yes

1.2.1 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.

Multiplexer chassis (MC)
Line concentration chassis (LCC)
POTS splitter chassis (PSC)

Note The PSC 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 would show a line concentration chassis (LCC). 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, the 6100 Chassis View dialog box displays the MC and each LCC. 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.

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 "Cisco 6100 Series System and ViewRunner State Management" for more information on states and see the Cisco 6100 Series 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.

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

Changes are detected when the dialog box is first opened.
Changes are made in client provisioning.
Changes are discovered during configuration, alarm, or map synchronization.
Traps are received.
Traps are propagated to all clients, updating alarm colors (ejector tabs), and the Event Categories window. Configuration, alarm, ViewMap, and OpenView map synchronization algorithms keep ViewRunner current with the node or network state.

Lock and key icons that display on the modules in the Chassis View dialog box indicate the administrative state of the module and its ports as shown in Table 1-3.

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

Icon Module State Port State

Lock (shown locked)

Locked or all ports locked

All ports locked

Lock (shown unlocked)

Unlocked

All ports unlocked

Lock (shown locked) with key

Unlocked

At least one port locked

Icon	Module State	Port State
Lock (shown locked)	Locked or all ports locked	All ports locked
Lock (shown unlocked)	Unlocked	All ports unlocked
Lock (shown locked) with key	Unlocked	At least one port locked

1.2.2 Managed Entities

To run ViewRunner for HP OpenView, you should also have some basic knowledge of the physical modules for the Cisco 6100 Series system. There are seven types of configurable modules.

Note POTS splitter modules are not configured or monitored through ViewRunner.

System controller (SC) module
Network interface (NI) module
DS3 subtend host module (STM)
ATU-C modules (both CAP and DMT)
SDSL Transmission Unit---Central office (STU-C) modules
Line interface module (LIM)
LIM controller module

Note Direct Connect configurations do not use LIMs or LIM controller modules. Therefore, these entities are not managed in Direct Connect configurations. The DMT ATU-C modules and STU-C modules are not used in DOH configurations, and therefore, not managed in DOH configurations.

For descriptions of these modules, consult the Cisco 6100 Series User Guide.

Note PSC and POTS modules are not autodiscovered or managed by ViewRunner.

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

ATU-C ports (both CAP and DMT)
STU-C ports
LIM ports
Subtend ports
Logical pools
Subscribers
Transit subscribers (for subtended systems)
Permanent virtual connections (PVCs)

1.3 System Files

ViewRunner maintains several key system files that reside in the subdirectories of the server home directory. These key system files include

Release definition files (RDF) and software images
Feature compatibility matrix (FCM) file
ViewRunner configuration files
ViewRunner log files

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).

1.3.1 Release Definition File

An 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 "Software Download" section for more information about
updating software.

9000-001-23R,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

1.3.2 Feature Compatibility Matrix File

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-2 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-2: 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
,,,,,,,,,,
,,,,,,,,,,
,,,,,,,,,,
,,,,,,,,,,

1.3.3 ViewRunner Configuration Files

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

$VRS_HOME/conf/vrconstants.conf---Defines application settings. See the ViewRunner for HP OpenView Installation and Administration Guide for details.
$VRS_HOME/conf/eventcodes.conf ---Defines the text strings that display for each alarm type. These text strings display in the Error Events Browser, Current Alarms dialog box and detailed property status dialog boxes.

1.3.4 Software Upgrade Defaults

During software upgrade, when moving to a release that supports new subscriber data that 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 you to upgrade software and get default subscriber values set to the site defaults. Otherwise, if the node default did not match what the customer wants, they would have to modify each subscriber manually after the upgrade.

1.3.5 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-3 provides an example listing of the log files.

Figure 1-3: ViewRunner Log Files

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

Figure 1-4: Partial ViewRunner Log

1.4 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 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

Changes are detected when the dialog box is first opened
Changes in client provisioning are made
Changes are discovered during configuration, alarm, or map synchronization
Traps are received

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.

1.5 Integration with HP OpenView and Oracle

ViewRunner for HP OpenView is the EMS for the Cisco 6100 Series ADSLAM 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 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.

1.5.1 Integration with HP OpenView

ViewRunner for HP OpenView is fully integrated with HP OpenView to take advantage of certain OpenView capabilities.

1.5.1.1 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:

Integration of heterogeneous vender applications (menus and maps)
Map display of the current network topology
- Nodes can be either discovered automatically or provisioned manually
- Ability to rapidly find and navigate to instances of nodes on maps
- Selection of automatic or manual layout of nodes within a map
Automatic discovery of network nodes in an IP overlay segment
Event reception and forwarding
Full-featured event browser application with an Event Categories window displaying all event report choices
Collection of SNMP data, event threshold definition, and performance graphing
Ability to load and browse vendor SNMP MIBs
Support for SNMP application programming interfaces (APIs) for third-party
management development

1.5.1.2 Application Integration

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

Cisco 6100 Series systems display in OpenView's hierarchical maps (ovw API).
IP Map can automatically discover Cisco 6100 Series nodes.
ViewRunner uses OpenView's SNMP stack to communicate with Cisco 6100 Series systems.
Cisco 6100 Series events are logged in OpenView's Event Categories window.
Shutting down OpenView also stops ViewRunner.

1.5.1.3 Inherent OpenView Capabilities

Some of the inherent OpenView capabilities used by ViewRunner include

Event forwarding using Transmission Control Protocol (TCP)

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

Data collection
Event threshold definition
Performance graphing

1.5.2 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. Following is an list of the ViewRunner and Cisco 6100 Series system information stored in the Oracle database:

Serves as cache for all Cisco 6100 Series configurations
Stores the user administration and Cisco 6100 Series privileges
Stores map information
Stores alarms and alarm history

Some of the specific benefits of using Oracle include

Improves client response time
Improves application (server) start up time and network bandwidth utilization
Serves as the master map database, enabling support for multiple synchronized read-write maps, bypassing the HP OpenView limitation
Arbitrates and prevents multiple updates of a single record

1.6 HP OpenView Windows 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-5.

Figure 1-5: 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 Navigation in ViewMap.
Table 1-4: Hierarchy from the Root Window

New Equipment Window

World

Location(s)

Wire Center

6100 Chassis View

New Subtend Cisco 6100 Series Systems

Subtend Networks

Subtend Location(s)

Subtend Group

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

Figure 1-6: HP OpenView Windows Help

Figure 1-7: HP OpenView Windows Help (Continued)

1.7 ViewMap Integration 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 "ViewRunner Maps and Views," for details on creating and using ViewMap maps.

1.7.1 Map Operation

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

Figure 1-8: HP OpenView Map Help

1.7.2 Submaps

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

Figure 1-9: HP OpenView Submaps Help

1.7.3 Objects

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

Location submaps, including World and Subtend Networks
Wire Center submaps, including New Equipment and New Subtend 6100s
Cisco 6100 Series equipment

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

Figure 1-10: HP OpenView Objects Help

1.7.4 Symbols

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

Wire Centers, including New Equipment and New Subtend Group
Subtend Networks
Cisco 6100 Series equipment in Wire Centers

Prior releases 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

CiscoDSLConnection

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)

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	CiscoDSLConnection
	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-11 provides an example of the HP OpenView Help definition for symbols.

Figure 1-11: HP OpenView Symbols Help

1.7.5 Map Permissions

By default, the ovw (graphical network map) program is executable by anyone. 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 session 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.

1.7.6 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 respository for map information. The following subsections describe first the OpenView restrictions and second the ViewMap added capabilities.

1.7.6.1 HP OpenView Map Operation

There are two types of maps possible in OpenView.

Read-write map---A map opened with read-write access is completely editable. You can add objects and connections, create submaps, and change object attribute values. Only one user can open a given map with read-write access at any one time. Multiple read-write maps cannot be opened simultaneously.
Read-only map---A map opened with read-only access does not automatically receive updates on topological events such as the addition or deletion of symbols, objects, or submaps, or the relocation of symbols by applications or other users. Multiple read-only maps can be opened simultaneously. Users must use Map > Refresh Map to view the updates provisioned by the read-write map user.

1.7.6.2 ViewRunner ViewMap Synchronization

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.

Read-write maps are updated when
- A user successfully logs in.
- A location is added to or deleted from a read-write map.
- A Cisco 6100 Series system is moved from one location to another.
- An alarm synchronization is performed.
Impacts on users with read-write maps
- Large networks with many open read-write maps might experience sluggishness.
- Maps are current with the actions of other users' read-write maps.

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:

Read-only maps do have their colors updated automatically when traps are received or alarm synchronizations are performed.
Read-only maps do not have the changes in symbols updated automatically when
- Changes are made to location or subtend location hierarchies (that is, additions or subtractions of locations or movement of Cisco 6100 Series systems or subtend groups).
- Cisco 6100 Series systems are synchronized or deleted.
- Cisco 6100 Series symbols are changed.
Read-only maps are updated when the menu option Map > Refresh Map is selected.
If the user who had the map opened with read-write access has subsequently closed that map, the refresh converts the read-only map of the next user to read-write.
Impacts on users with read-only maps
- Users might not always have a correct view of the hierarchy.
- Users might not have a correct view of the Cisco 6100 Series Loss of Communication
  (LOC) state.

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.

1.8 Navigation 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

New Equipment Window

World

Location(s)

Wire Center

6100 Chassis View

New Subtend Cisco 6100 Series Systems

Subtend Networks

Subtend Location(s)

Subtend Group

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-12. 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-12: 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-13, 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-13 gives a more detailed view of the interactions between windows and views.

Figure 1-13: Navigation Diagram

1.9 Navigation in ViewRunner Chassis View

ViewRunner for HP OpenView supports several navigation methods.

Right-click menus
Toolbar access
Menu hierarchy

1.9.1 Right-Click Menus

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 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-14 through Figure 1-22 are examples of menus that provide options when you right click a particular component.

1.9.1.1 Right Clicking on the Multiplexer Chassis

The options in Figure 1-14 display when you right click the Multiplexer Chassis (MC).

Figure 1-14: MC Chassis View Menu

Table 1-7: MC 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 LCC for the Cisco 6100 Series.

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 LCC for the Cisco 6100 Series.

1.9.1.2 Right Clicking on the Line Concentration Chassis

The options in Figure 1-15 display when you right click the LCC.

Figure 1-15: LCC View Menu

Table 1-8: LCC Menu Options

Menu Options Description

Chassis Properties

Displays the backplane revision number for this LIM chassis.

Delete Chassis

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

Menu Options	Description
Chassis Properties	Displays the backplane revision number for this LIM chassis.
Delete Chassis	Allows you to delete the LCC. Unless the LIM controller is set to Administrative State Locked, the option to delete the chassis is dimmed. (HP OpenView automatically locks all modules, ports, and subscribers before deleting all the module configurations.)

1.9.2 Right Clicking on Modules

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 controller 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 "Common Dialog Box Elements" section.

1.9.2.1 Right Clicking on ATU-C Modules

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

Figure 1-16: ATU-C Module Properties Menu

1.9.2.2 Right Clicking on STU-C Modules

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

Figure 1-17: 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

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

Chassis

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

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	Deletes the specified module from the Cisco 6100 Series system. This option is dimmed unless the you lock the module or all of its ports. This option is always dimmed for users with read-only privileges.
Chassis	Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Chassis.

1.9.2.3 Right Clicking on LIMs

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

Figure 1-18: 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

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

Chassis

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

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	Deletes the specified module from the Cisco 6100 Series system. This option is dimmed unless the you lock the module or all of its ports. This option is always dimmed for users with read-only privileges.
Chassis	Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to the Delete Chassis.

1.9.2.4 Right Clicking on the SC Module

The options in Figure 1-19 display when you right click the SC module.

Figure 1-19: System Controller Module Properties Menu

Table 1-11: SC Module Menu Options

Menu Option 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 dimmed unless you lock the module. This option is always dimmed for users with read-only privileges.

Chassis

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

Menu Option	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 dimmed unless you lock the module. This option is always dimmed for users with read-only privileges.
Chassis	Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Chassis.

1.9.2.5 Right Clicking on the LIM Controller Module

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

Figure 1-20: 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

Deletes the module. This option is dimmed unless you lock the module. This option is always dimmed for users with read-only privileges.

Chassis

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

Menu Option	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 dimmed unless you lock the module. This option is always dimmed for users with read-only privileges.
Chassis	Gives you direct access to the Chassis menu which allows you to view the Chassis Properties or to Delete Chassis.

1.9.2.6 Right Clicking on an MC Empty Slot

Figure 1-21 shows the options that appear when you right click an empty slot in the MC.

Figure 1-21: MC Empty Slot Menu

Table 1-13: MC 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 chassis Status or Configuration.

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 chassis Status or Configuration.

1.9.2.7 Right Clicking on an LCC Empty Slot

The options in Figure 1-22 appear when you right click an empty slot in the LCC.

Figure 1-22: LCC Empty Slot Menu

Table 1-14: LCC 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 unavailable unless all modules are locked or deleted first.

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 unavailable unless all modules are locked or deleted first.

1.9.3 Toolbar Access

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-23 shows the HP OpenView toolbar.

Figure 1-23: 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-24 shows an example of another toolbar that is found in the 6100 Chassis View window.

Figure 1-24: 6100 Chassis View Toolbar

The icons for the toolbar in Figure 1-24 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).

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).

1.9.4 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-25 through Figure 1-36 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-25: Root Window

Figure 1-26: Map Menu

Figure 1-27: Edit Menu

Figure 1-28: Locate Menu

Figure 1-29: View Menu

Figure 1-30: Performance Menu

Figure 1-31: Configuration Menu

Figure 1-32: Fault Menu

Figure 1-33: Security Menu

Figure 1-34: Miscellaneous Menu

Figure 1-35: Options Menu

Figure 1-36: Help Menu

1.10 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

Current Alarm
View All Subscribers
Subscriber PVCs
View Equipment Inventory
Active Connections
Port Service Configuration (Direct Connect configuration only)

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 on the subscriber ID in the View All Subscribers 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-37 for an example of the View All Subscribers hyperlinks.

Figure 1-37: View All Subscribers Hyperlinks

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

Figure 1-38: Line Port Hyperlinks

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

Figure 1-39: 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.

1.11 Common Dialog Box Elements

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.

1.11.1 Common Dialog Boxes

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.

1.11.2 Common Tabs

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 "Cisco 6100 Series System and ViewRunner State Management," 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-40 and Figure 1-42 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 only if the administrative state is Locked.

Figure 1-40: ATU-C Module Tabs

Figure 1-41: STU-C Module Tabs

Figure 1-42: 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.

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.

1.11.3 Common Colors

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.

1.11.4 Common Buttons

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

Figure 1-43: 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.

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.

1.12 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 "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 dialog boxes, confirmation and error, are supported by ViewRunner for HP OpenView. They are discussed in the following sections.

1.12.1 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:

Locking an entity that is involved in an active ADSL connection displays a confirmation that the active connection(s) terminate if the action is not aborted.
Deleting a resource informs you of the extent of configuration data deleted, associations removed, and entities deleted.
Modifying the system service type to DOH or DC.

1.12.2 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.

1.12.3 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.

1.13 Cisco 6100 Series and ViewRunner Management Tools

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

Configuration save and restore
Software update download
Command line interface (CLI)
Inband management channel

1.13.1 Configuration Save and Restore

The configuration save and restore feature allows you to upload nonvolatile random-access memory (NVRAM) to out-of-node storage to provide a backup of node configuration data. Downloading NVRAM back into a system controller enables recovery from a corrupted or replaced system controller. It also allows you to quickly recover your configuration after downloading updated Cisco 6100 Series software. (See "Updating the Cisco 6100 Series System Software," for more information about software download.)

Note ViewRunner does not support saving the configuration of older Cisco 6100 Series systems that are running software version 1.02.

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 a loss of service for subscribers.

The configuration save and restore feature is discussed in detail in "Configuration Save and Restore."

1.13.2 Software Download

System software download is the method by which a Cisco 6100 Series system can upgrade the software in each of the modules that support downloading. The software download procedure requires a TFTP server. ViewRunner functions as a TFTP server and is capable of handling requests for images from a Cisco 6100 Series system.

The process is triggered by user menu selection or system controller reset. As a fail-safe measure, prior to initiating a system reset, you should use the configuration save and restore wizard (see "Configuration Save and Restore") to store the current NVRAM configuration for possible retrieval in case something goes wrong during the software download (see "Updating the Cisco 6100 Series System Software.")

1.13.3 Inband Channel Software Download Capability

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 "System-Level Configuration."

1.13.4 Command Line Interface

The CLI feature provides the ability to retrieve fault management data from the Cisco 6100 Series system, using a directly connected serial interface or a telnet session. Multiple users can access a single Cisco 6100 Series system simultaneously through independent telnet sessions.

Note The only valid CLI commands are to show the alarms on various managed objects.

1.13.4.1 Command Line Input Interface

Following are the input criteria for using the CLI:

The serial interface requires a DB-9 male connector attached to the system controller's face plate serial port.
The terminal should be VT100 compatible, and the serial interface software should be configured at 38400 baud, no parity, 8 data bits, 1 stop bit, and no flow control (38400, N, 8, 1, N).
Typing CTRL-L refreshes and redraws the CLI screen.
The default telnet port number to connect to the CLI is 7000. To connect to the system controller, type the IP address followed by the port number 7000 (for example, telnet 192.168.7.71 7000).
The default prompt is " > ".
The first word typed on the CLI prompt is the command (which is a verb) and is followed by either one or more arguments or no arguments.
Each argument is separated by one space.
Commands and arguments are not case sensitive.
The up arrow displays the last command entered on prompt (history).
The history command can be edited for rapid command syntax modification.
An invalid command entry lists all the valid commands supported.

1.13.4.2 Command Line Output Interface

Following are the common features for the data output formats:

Print formats for various command outputs are specified for VT100 terminals.
The screen is formatted to 24 lines by 80 characters.
Print messages scroll up to 20 lines and then wait for user's acknowledgment
(for example, Press any key to proceed).

1.13.4.3 Error Output

Following are the errors that display for invalid commands and what they mean:

Too many arguments passed---Displays when too many arguments are entered.
No response from 6100---Displays if CLI could not get a response from either the management interface manager (MIM or the fault manager (FM).
Invalid argument n---Displays when argument n is invalid (where n is a number between 1 and 5).
Invalid first object instance---Displays when the instance specified for first object is invalid.
Invalid second object instance---Displays when the instance specified for second object
is invalid.

1.13.4.4 Command Syntax

Following is the syntax for CLI commands:

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

where

verb

This is the action or command that needs to be executed. Valid verbs are

help
?
show

lists all possible commands
lists all possible commands
retrieves and displays data on screen

noun_1

This specifies the object on which the command needs 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

This specifies the kind of noun or object. Adjective_1 is sensitive up to 3 unique characters or words. More than one adjective_1 can modify a noun_1, each separated by a period. In the following example of maj.crit, maj and crit are each an adjective_1:

> show alarms maj.crit sys

The valid adjective_1 entries are

crit
maj
min

critical alarms
major alarms
minor alarms

If you do not specify the alarm severity that you want displayed, the system displays all alarms.

noun_2

This specifies the object on which the command needs to be executed. This is generally a managed object of the Cisco 6100 Series system. The following command would return all critical alarms for all the chassis (MC and LCCs) for that Cisco 6100 Series system.

> show alarms crit chas

The 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 (referred to as STM in all other documentation)
line port
modem port

adjective_2

This specifies the kind of noun or object. Generally, adjective_2 is the instance of a Cisco 6100 Series managed object. Object instances vary with the type of objects. An example of an adjective_2 entry follows:

> show alarms [crit | maj | min] [noun_2] [c].[i].[s].[p]

where c, i, s, and p indicate the following values:

c
i

s

p

indicates the chassis, where m.0 = MC and l = LCC.
indicates the chassis instance. For the MC, the value is always 0. For the LCC, the value is the DIP switch setting for that LCC.
indicates the slot number of the object. The value corresponds to the slot number on the chassis where the object is physically located.
indicates the port number of the object. The value is 1 to 4 corresponding to the port on the object. Ports are identified from the top down starting with 1. Currently, only the ATU-C, LIM, and STM ports are supported.

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

> show alarms crit.maj atuc m.0.12.2

options

This is to activate certain types of operation, that is, to 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 are ignored.

1.13.5 Inband Management Channel

Using the inband management channel feature of the ViewRunner for HP OpenView allows direct control and management of the Cisco 6100 Series system 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 with the Cisco 6100 Series system, ViewRunner uses ATM as the physical layer for communication.

To run IP over ATM, the system uses RFC 1483 "Multiprotocol Encapsulation over ATM Adaptation Layer 5" in Logical Link Control (LLC) encapsulation mode. This encapsulation allows transporting through multiple protocols over a single VC.

To ensure that the outbound packets from the Cisco 6100 Series system 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.

New Equipment Window
World
	Location(s)
		Wire Center
			6100 Chassis View
New Subtend Cisco 6100 Series Systems
Subtend Networks
	Subtend Location(s)
		Subtend Group

verb	This is the action or command that needs to be executed. Valid verbs are
	help ? show	lists all possible commands lists all possible commands retrieves and displays data on screen
noun_1	This specifies the object on which the command needs 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	This specifies the kind of noun or object. Adjective_1 is sensitive up to 3 unique characters or words. More than one adjective_1 can modify a noun_1, each separated by a period. In the following example of maj.crit, maj and crit are each an adjective_1: `>` show alarms maj.crit sys The valid adjective_1 entries are
	crit maj min	critical alarms major alarms minor alarms
	If you do not specify the alarm severity that you want displayed, the system displays all alarms.
noun_2	This specifies the object on which the command needs to be executed. This is generally a managed object of the Cisco 6100 Series system. The following command would return all critical alarms for all the chassis (MC and LCCs) for that Cisco 6100 Series system. `>` show alarms crit chas The 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 (referred to as STM in all other documentation) line port modem port
adjective_2	This specifies the kind of noun or object. Generally, adjective_2 is the instance of a Cisco 6100 Series managed object. Object instances vary with the type of objects. An example of an adjective_2 entry follows: > show alarms [crit \| maj \| min] [noun_2] [c].[i].[s].[p] where c, i, s, and p indicate the following values:
	c i s p	indicates the chassis, where m.0 = MC and l = LCC. indicates the chassis instance. For the MC, the value is always 0. For the LCC, the value is the DIP switch setting for that LCC. indicates the slot number of the object. The value corresponds to the slot number on the chassis where the object is physically located. indicates the port number of the object. The value is 1 to 4 corresponding to the port on the object. Ports are identified from the top down starting with 1. Currently, only the ATU-C, LIM, and STM ports are supported.
	In the following example, the command is to show all critical and major ATU-C alarms on the Cisco 6100 Series MC (which is always chassis instance number 0) at slot 12: `>` show alarms crit.maj atuc m.0.12.2
options	This is to activate certain types of operation, that is, to 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 are ignored.

Table of Contents

ViewRunner for HP OpenView Overview