Using ViewRunner---An Overview

This chapter provides an overview of how to use the ViewRunner software, including its system files, navigational system, system dialog boxes, and management tools.

This chapter contains the following sections:

Using the GUI to Set Up the Cisco 6100 Series Chassis and Modules

You can use the ViewRunner graphical user interface (GUI) to configure your Cisco 6100 Series system and manage Cisco 6100 Series nodes. ViewRunner supports the discovery of Cisco 6100 Series equipment. That is, once you have installed ViewRunner and connected it to your Cisco 6100 Series system, ViewRunner retrieves configuration data from the Cisco 6100 Series simple network management protocol (SNMP) agent.

After ViewRunner retrieves this configuration data, the GUI displays a graphical representation of your Cisco 6100 Series system, called the Chassis View. An example is shown in Figure 1-1.

Figure 1-1: Cisco 6100 Series Chassis View---Direct Connect Configuration

The ViewRunner GUI includes the following primary views:

The Chassis View---A graphical representation of the Cisco 6100 Series system that you can configure according to your system needs.

The Events History dialog box---Keeps a log of events that occur as you run your session.

The Current Alarm dialog box---Provides details of current alarms. (See "Viewing Events and Alarms," for more information on events and alarms.)

Note Events (informational and alarm) are described in detail in the Cisco 6100 Series with NI-1 Alarm Summary Guide.

ViewRunner for Windows Release 3.0.0 is shipped with the Cisco 6100/6130 chassis, or you can download ViewRunner for Windows Release 3.0.0 from the Cisco web site, Cisco Connection Online (CCO).

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

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

Cisco 6100 Series System Release¹^,²

3.0.0 2.4.1 2.4.0 2.3.x 2.2.1/
2.2.5 2.2.0

ViewRunner Release

3.0.0

Yes

Yes

Yes

Yes

Yes

Yes

2.4.1

No

Yes

Yes

No

No

No

2.4.0

No

No

Yes

No

No

No

2.3.5

No

No

No

Yes³

Yes

Yes

2.3.0

No

No

No

No

Yes³

Yes

2.2.1

No

No

No

No

Yes

Yes

2.2.0

No

No

No

No

No

Yes

¹The Cisco 6130 chassis feature support is present in Release 2.4.0 or later.
²Systems with a Cisco 6100 installed must connect to the network through a POTS splitter to provide the secondary lightning protection required by NEBS. Therefore, a Cisco 6100 cannot support a Direct Connect without a POTS splitter configuration.
³The most recent Feature Compatibility Matrix (FCM) file may be required. ViewRunner will detect and display a warning if a newer FCM is required.

	Cisco 6100 Series System Release¹^,²
3.0.0	2.4.1	2.4.0	2.3.x	2.2.1/ 2.2.5	2.2.0
ViewRunner Release
3.0.0	Yes	Yes	Yes	Yes	Yes	Yes
2.4.1	No	Yes	Yes	No	No	No
2.4.0	No	No	Yes	No	No	No
2.3.5	No	No	No	Yes³	Yes	Yes
2.3.0	No	No	No	No	Yes³	Yes
2.2.1	No	No	No	No	Yes	Yes
2.2.0	No	No	No	No	No	Yes

Viewing the Cisco 6100 from the ViewRunner Chassis View

The Chassis View is the top-level user interface from which you manage a single Cisco 6100 Series system.

The Cisco 6100 Series system includes the following chassis types:

Cisco 6100/6130 chassis
Cisco 6110 (Digital Off-Hook configurations only)
Cisco 6120 POTS splitter chassis (or the Siecor POTS splitter chassis)

You can use ViewRunner to manage the Cisco 6100/6130 chassis and the Cisco 6110 chassis.

Note ViewRunner does not configure or monitor the POTS splitter chassis. However, ViewRunner captures and displays alarm conditions for the Cisco 6120 POTS splitter chassis.

The Chassis View, shown in Figure 1-2, provides menu bar operations and a bit-map front-panel view of the Cisco 6100 Series system. This front-panel view displays the color-coded status of configured modules. (See the "Detecting Entity Status Through Colors" section for more information about color-coded status.)

Note The Chassis View corresponds to the type of configuration that you select. The Chassis View shown in Figure 1-2 displays the Digital Off-Hook (DOH) configuration. Refer to the ViewRunner for Windows Installation and Administration Guide for information on how to choose a configuration style.

Figure 1-2: Cisco 6100 Series Chassis View---Digital Off-Hook Configuration

Note After the Chassis View is open, you cannot close it. Notice that the "x" in the upper right corner has been disabled. You can, however, minimize the window.

The Chassis View displays the Cisco 6100/6130 Chassis and each Cisco 6110. It also provides a top-level display of modules, which you can view, add to, modify, or delete. From the Chassis View, you can view all status information, manage all configurations, and check the performance of the Cisco 6100 Series system. The Chassis View title bar displays the date and time the system was last discovered. See "Discovery," for information about discovery.

Caution If two ViewRunner applications are managing the same Cisco 6100 Series system and open the same configuration dialog box simultaneously, the last operator to click OK or Apply overwrites the other operator's data. The software does not attempt to prevent this occurrence or to inform you that it has happened.

The Chassis View displays colored module tabs to indicate the status and state of each module and its ports. These colors are listed and described in Table 1-2. The highest priority color displays first, and the lowest priority color displays last when more than one of the conditions described in Table 1-2 occurs.

See "Using ViewRunner to Manage the Status of the Cisco 6100 Series System," for more information on states, and refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide for detailed information about alarms.

Table 1-2: Cisco 6100 Series Chassis View Tab Color Prioritization

Tab Color (by priority) State or Alarm Type Description

Red

Alarm type---Critical

A critical alarm is the most severe alarm that is present on the module or any of its ports.

Orange

Alarm type---Major

A major alarm is the second most severe alarm that is present on the module or any of its ports.

Yellow

Alarm type---Minor

A minor alarm is the one lowest in severity that is present on the module or any of its ports.

Blue

State---Unknown

Indicates that the module is empty but provisioned. This state is displayed when you have configured a module in the slot, but the system controller module has not communicated with it since power up.

Green

State---Normal

The module and all of its ports are in a normal, operational state.

Tab Color (by priority)	State or Alarm Type	Description
Red	Alarm type---Critical	A critical alarm is the most severe alarm that is present on the module or any of its ports.
Orange	Alarm type---Major	A major alarm is the second most severe alarm that is present on the module or any of its ports.
Yellow	Alarm type---Minor	A minor alarm is the one lowest in severity that is present on the module or any of its ports.
Blue	State---Unknown	Indicates that the module is empty but provisioned. This state is displayed when you have configured a module in the slot, but the system controller module has not communicated with it since power up.
Green	State---Normal	The module and all of its ports are in a normal, operational state.

Note Previous versions of ViewRunner used the color brown to indicate that a module is Locked. Release 3.0.0 indicates Locked and Unlocked states by the lock icons. See the "Administrative State" section for a description of the Locked and Unlocked states and the lock icons.

ViewRunner updates the tab colors when you take any of the following actions:

Open the Cisco 6100 Series Chassis View.
Right-click the Cisco 6100/6130 Chassis and choose Discover 6100.
Right-click the Cisco 6100/6130 Chassis and choose Refresh status.

Note ViewRunner does not update the color ejector tabs dynamically. Updates occur according to background polling. As a result, the colors that you see do not necessarily indicate the most current status of the module and its ports. To get the most current ejector tab colors, right-click the Cisco 6100/6130 Chassis and choose Refresh status.

Using ViewRunner to Manage Entities

To run ViewRunner, you should have some basic knowledge of Microsoft Windows 95, Windows 98, or Windows NT, and how to use Windows applications. You should also have some basic knowledge of the physical modules of the Cisco 6100 Series system.

ViewRunner manages the following modules:

System controller module
Network interface module
DS3 subtending host module (STM)
CAP ATU-C module
STU-C module---supported only by the Cisco 6130 node software versions 2.1 and 3.0.0 system
DMT-2 ATU-C module
Flexi module (CAP or DMT-2)
Line interface module (LIM)
LIM controller module

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

You should have some basic knowledge of the logical entities of the Cisco 6100 Series system. The Cisco 6100 Series system includes the following logical entities:

CAP ATU-C ports
DMT-2 ATU-C ports
STU-C ports
LIM ports
Logical pools
Subscribers (line rates, VPI/VCI)

Note ViewRunner does not discover or manage POTS splitter chassis and modules.

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

Getting Information from System Files

ViewRunner maintains several system files that reside in the same folder from which you launch ViewRunner. These files provide information to help you set up and run ViewRunner. You may need to open and read the following system files while you are using ViewRunner:

Release definition file (RDF)
Feature compatibility matrix (FCM) file
Key events log file
Subscriber defaults text file (subscriberdefaults.ini)

These files are described in the following sections.

In addition to these files, a readme file is included that explains how to install the ViewRunner software.

Note You can obtain updates on the World Wide Web from Cisco Connection Online (CCO) or by contacting Cisco Technical Assistance Center (TAC).

Identifying Release Compatibility with Hardware

ViewRunner for Windows maintains an RDF. This file identifies the software that is compatible with each hardware module or revision for a given system release. The system controller and ViewRunner use this file to check release compatibilities for software update downloads. See the "Downloading Software Updates" section for more information about how to download software updates.

The name of the RDF is C6100-xxx-xx.rdf, where "C6100-xxx-xx" is the latest release. 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 as follows:

The first line identifies the software release number.
The Hardware Revision Table identifies hardware versions for each type of module.
The Image Table identifies the module software versions and their associated images.

The following script is an example of an RDF:

6000-300-30A,Alpha Release 3.0.0.118 
*******************************************************************************
Hardware Revision Table
*******************************************************************************
Begin
2651-003,9651-001-36,"SC","none"
2101-004,9101-001-26,"Dual ATU-C CAP DOH","none"
2101-011,9101-005-04,"4x Flex ATU-C DMT","dmt"
2101-011,9101-004-08,"4x Flex ATU-C CAP","cap"
2601-014,9601-001-32,"OC-3 NI SMF","none"
2601-015,9601-001-32,"OC-3 NI MMF","none"
2601-016,9601-001-32,"DS3 NI","none"
2601-012,9601-001-32,"Subtending DS3 NI","none"
2601-021,9601-001-32,"Subtending DS3 NI FPGA mod","none"
2601-020,9601-001-32,"Subtending OC-3 NI MMF FPGA mod","none"
2601-019,9601-001-32,"Subtending OC-3 NI SMF FPGA mod","none"
2601-022,9601-001-32,"OC3 SM NIM Temperature Hardened","none"
2601-023,9601-001-32,"OC3 MM NIM Temperature Hardened","none"
2601-024,9601-001-32,"DS3 NIM Temperature Hardened","none"
2101-003,9101-001-26,"Dual ATU-C CAP Direct Connect","none"
2101-005,9101-001-26,"Dual ATU-C CAP DOH","none"
2651-004,9651-002-12,"LCM","none"
2601-017,9601-005-13,"SHM","none"
2107-007,9101-008-04,"Quad STU-C SDSL Direct Connect","none"
3102-002,9101-008-04,"SDSL Direct Connect (Prototype)","none"
3101-004,9101-008-04,"Quad STU-C SDSL Direct Connect","none"
2101-007,9101-008-04,"Quad STU-C SDSL Direct Connect","none"
2101-008,9101-003-05,"Dual ATU-C DMT-II Direct Connect","none",(5385-579-97)
2101-009,9101-001-26,"Dual ATU-C CAP Direct Connect","none"
2101-010,9101-001-26,"Dual ATU-C CAP DOH","none"
2101-008,5385-579-97,"DSP Image for Dual ATU-C DMT-II Direct Connect","supplementary",(9101-003-05)
End
*******************************************************************************
Image Table
*******************************************************************************
Begin
9651-001-36,psc304000.ima,375284,1708768357,"SC"
9101-001-26,cp3.0.118.imz,87683,4070172187,"ATUC"
9101-005-04,flexdmt13.imz,130670,1721065818,"ATUC"
9101-004-08,fc3.0.118.imz,142682,3065507739,"ATUC"
9601-001-32,pni304000.ima,269620,2026075729,"NI"
9651-002-12,lcmR2.2.5.imz,18602,1043470102,"LCM"
9601-005-13,pst302000.ima,203892,2066491651,"SHM"
9101-008-04,sl3.0.1.3.imz,99937,188791415,"STU-C"
9101-003-05,2dm3.0.0.4.imz,90374,2710206634,"ATU-C"
5385-579-97,cobld.imz,278106,4222849510,"ATU-C"
End

Determining Feature Compatibility

You can determine feature compatibility through the system controller FCM file. This file contains feature descriptions of node software releases that ViewRunner supports. ViewRunner uses this matrix to customize its features.

ViewRunner reads the FCM file to determine what features are supported in a given system controller module software release and customizes the features that it presents to you when you connect to that Cisco 6100 Series system.

ViewRunner can manage newer Cisco 6100 Series releases without updating this file; however, you are warned each time ViewRunner discovers a new Cisco 6100 Series internet protocol (IP) address if ViewRunner does not recognize the system-controller node software. When you connect to a Cisco 6100 Series system that contains a system-controller module software version that ViewRunner cannot find in the FCM file, ViewRunner opens the Feature Compatibility Error dialog box, shown in Figure 1-3.

Figure 1-3: Feature Compatibility Error Dialog Box

In the event that a software upgrade fails, you can check the list of compatible hardware releases in the RDF. Look for this file in the ViewRunner system folder. The RDF contains information about the software and hardware release of the Cisco 6100 Series components, as described in the previous section.

Caution Open the RDF by using Windows Notepad only. Notepad provides a pure text display without hidden characters. Do not alter the RDF file. Altering the RDF corrupts your ViewRunner for Windows application.

In a case in which the system controller software is not contained in the FCM file, ViewRunner presents the latest default feature set to you. You can obtain an updated FCM file through CCO or from the Cisco TAC. Obtaining a newer FCM file could eliminate the warning shown in Figure 1-3. However, this message typically means that a newer ViewRunner version should be available.

The FCM file name is SCFeatureCompatibilityMatrix.csv. This file is in a spreadsheet format and output as a comma-separated text file. See "Sample Feature Compatibility Matrix File" for an example of an FCM file.

Tracking Key ViewRunner Events

The key events log file tracks significant ViewRunner events into a text file named vrlog.txt. You can find this file in the folder from which you launched ViewRunner. The purpose of this file is to troubleshoot problems with ViewRunner and the Cisco 6100 Series system.

ViewRunner logs events and information in the vrlog.txt file as a result of the following situations:

ViewRunner starts up. The information that is logged includes the software version number.

ViewRunner exits.

ViewRunner discovers a Cisco 6100 Series system. The information that is logged includes the IP address and timeout value that ViewRunner sets for the SNMP.

A software upgrade and configuration restore process generates information.

SNMP errors exist.

The vrlog.txt file can increase to a size of 2 MB and no larger. Once the .txt file reaches 2 MB, it returns to 0 and starts over. The following script is an example of a vrlog.txt file:

ViewRunner started (EXE-300:0, DLL- 300:0) (Jan 28, 2000   14:08:02)
Discovering 'GoalPost,172.21.177.18' & setting SNMP_TIMEOUT_DELAY to 5000 (Jan 28, 2000   14:08:10)
01/28/2000 14:09:50    Error on HostBoardGetSWRevision - SNMP++: SNMP request timed out (Jan 28, 2000   14:09:50)
Discovery of 6100 at 172.21.177.18 failed (Jan 28, 2000   14:09:50)
ViewRunner exited (Jan 28, 2000   14:10:21)
ViewRunner started (EXE-300:0, DLL- 300:0) (Jan 28, 2000   14:10:41)
Discovering 'NMS-DC-3,172.21.178.194' & setting SNMP_TIMEOUT_DELAY to 5000 (Jan 28, 2000   14:11:24)
01/28/2000 14:13:04    Error on HostBoardGetSWRevision - SNMP++: SNMP request timed out (Jan 28, 2000   14:13:04)
Discovery of 6100 at 172.21.178.194 failed (Jan 28, 2000   14:13:04)
ViewRunner exited (Jan 28, 2000   14:13:14)
ViewRunner started (EXE-300:0, DLL- 300:0) (Jan 28, 2000   14:45:14)
Discovering 'NMS-DC-3,172.21.178.194' & setting SNMP_TIMEOUT_DELAY to 5000 (Jan 28, 2000   14:45:23)
01/28/2000 14:47:03    Error on HostBoardGetSWRevision - SNMP++: SNMP request timed out (Jan 28, 2000   14:47:03)
Discovery of 6100 at 172.21.178.194 failed (Jan 28, 2000   14:47:03)
Discovering 'topshelf,172.21.177.22' & setting SNMP_TIMEOUT_DELAY to 5000 (Jan 28, 2000   14:47:11)
01/28/2000 14:48:51    Error on HostBoardGetSWRevision - SNMP++: SNMP request timed out (Jan 28, 2000   14:48:51)
Discovery of 6100 at 172.21.177.22 failed (Jan 28, 2000   14:48:51)
ViewRunner exited (Jan 28, 2000   14:49:10)
ViewRunner started (EXE-300:0, DLL- 300:0) (Jan 28, 2000   15:22:38)
Discovering 'topshelf,172.21.177.22' & setting SNMP_TIMEOUT_DELAY to 5000 (Jan 28, 2000   15:22:42)
01/28/2000 15:24:22    Error on HostBoardGetSWRevision - SNMP++: SNMP request timed out (Jan 28, 2000   15:24:22)
Discovery of 6100 at 172.21.177.22 failed (Jan 28, 2000   15:24:22)
ViewRunner exited (Jan 28, 2000   15:24:29)

In any given session in ViewRunner, the ViewRunner Log Window (shown in Figure 1-4) contains the error messages that are logged to vrlog.txt during that session.

Figure 1-4: ViewRunner Log Window

Getting Information about Subscriber Defaults

You can use the subscriberdefaults.ini file to determine the subscriber default settings. This file is part of your ViewRunner installation. An example of the file is included at the end of this section. For more information about installing this file, see the ViewRunner for Windows Installation and Administration Guide.

To get information about the default subscriber values, complete the following steps:

Step 1 From your Windows Start menu, choose Program, then Accessories, and then Notepad.

Step 2 In Notepad, choose Open from the File menu.

Step 3 Find your ViewRunner folder, and then the file subscriberdefaults.ini.

Step 4 Double-click the subscriberdefaults.ini file to open and view it.

Step 5 Close Notepad.

If you want to modify the parameter settings for a provisioned subscriber, see the chapter on provisioning subscribers in the ViewRunner for Windows Direct Connect Provisioning Guide or the ViewRunner for Windows Digital Off-Hook Provisioning Guide.

An example of a subscriberdefaults.ini file follows. Sections are separated by square brackets [ ].

[Subscriber_Stuc2b1q_Defaults]
RateDown=784
RateUp=784
 
[Subscriber_AtucDmt2_Defaults]
RateDown=8032
RateUp=864
RateDownDMT2GliteEnabled=1536
RateUpDMT2GliteDisabled=512
MarginDown=6
MarginUp=6
FecRedundancyBytes=7	// 0(0), 2(1), 4(2), 6(3), 8(4), 12(5), 14(6), 16(7)
InterleavedDelay=7	// 0(0), 250(1), 500(2), 1000(3), 2000(4), 4000(5), 8000(6), 16000(7), 32000(8), 64000(9)
OverheadFrame=3		// full-async(0), full-sync(1), reduced-separate(2), reduced-marge(3) 
TrainingMode=0		// standard(0), fastTrain(1)
BitSwapping=0		// disabled(0), enabled(1)
TrellisCode=0		// disabled(0), enabled(1)
PsdXmitPwrDownDmt2=3	// -49(0), -46(1), -43(2), -40(3), -37(4), -34(5)
AllowGlite=0		// disabled(0), enabled(1)
 
[Subscriber_AtucCap_Defaults]
RateDown=7168
RateUp=1088
MarginDown=3
MarginUp=6
CPESignature=0
TimerType=1
Timeout=100
AllowIdle=0
IdleTimeout=30
PvcIdleMark=1000
AllowSession=0
SessionTimeout=120
LockoutTime=20
ReedSolomon=1		// longInterleave(0), shortInterleave(1), disable136Ds(2)
PsdXmitPwrDown=1	// -37(0), -40(1), -43(2), -46(3), -49(4)
PsdXmitPwrUp=0		// -38(0), -41(1), -44(2), -47(3), -50(4), -53(5)
Rate136Boolean=0	// disabled(0), enabled(1)
Rate17Boolean=0		// disabled(0), enabled(1)
Rate68Boolean=0		// disabled(0), enabled(1)

Navigating in ViewRunner

You can navigate in ViewRunner by using the methods that are described in the following sections:

Using the Mouse to Display Module and Chassis Menus

To retrieve information about a particular module or chassis, you can double-click the left mouse button or right-click the right mouse button once. Using the mouse buttons displays menus for a particular module or chassis or opens dialog boxes in which you can monitor status and set configuration information.

Double-click the left mouse button to open the Module Properties dialog box for the module that is directly beneath the cursor. You can use the right mouse button (right-click on a module) to display the menu that contains Status and Configuration items for the modules, ports, and the 6100 chassis. Selecting these items opens the Module Properties dialog box Status and Configuration tabs.

Menus are context sensitive, depending on the chassis or slot that is beneath the cursor when you right-click the mouse .

To select the chassis itself, place the cursor over the chassis, but outside of the slots on the side or rim. Double-click the left mouse button to open the 6100 Properties dialog box. Right-click to access the chassis menu. Menu options are dimmed if any of the following conditions are true:

You do not have the necessary security privileges to execute those options.
You have not met the specific requirements that allow those options.
Your version of the system controller software does not support those options.

You right-click the mouse button to access the entity menus, which are described in the following sections:

Using the Cisco 6100/6130 Chassis Menu

To view the management options for the Cisco 6100 Series system chassis, right-click the edge or rim of the Cisco 6100/6130 chassis on the ViewRunner GUI. The Chassis menu displays, shown in Figure 1-5, from which you can choose several items. These items are described in Table 1-3. (The options that are dimmed in Figure 1-5 are Port Service Configuration, directly below 6100 Performance, and Add LIM Chassis, directly below Refresh status.)

Figure 1-5: 6100 Chassis Menu

Note The Pool Properties option is unavailable in Direct Connect configurations. However, the Port Service Configuration option is enabled for Direct Connect configurations. Figure 1-5 shows an example of the options in a DOH configuration.

The items from the Chassis menu are listed and described in Table 1-3. The Description column describes what happens when you choose the menu item. The dialog boxes that open when you choose items from the Chassis menu are described in more detail in subsequent chapters of this manual.

Table 1-3: Chassis Menu Items

Menu Item Description

6100 Series Properties

Opens either the Status or Configuration tabs on the 6100 Properties dialog box.

Pool Properties

Opens the Pool Properties dialog box, which displays the properties of physical and logical pools on the Physical Pool tabs and the Logical Pool tabs. (This field relates to Digital Off-Hook configurations only.)

Active Connections

Opens the Active Connections dialog box, which lists the active connections and in-service modems.

View All Subscribers

Opens the View All Subscribers dialog box, which displays a comprehensive list of all subscribers who are currently receiving service.

View Subscriber PVCs

Opens the Subscriber PVCs dialog box, which lists current PVCs and the subscribers who are associated with the PVCs.

View Equipment Inventory

Opens the Equipment Inventory dialog box, which lists all discovered modules and inventory details about them. For DOH configurations, this dialog box also identifies associated pools.

6100 Performance

Opens the Performance Management dialog box, which displays performance statistics for the Cisco 6100 Series system.

Port Service Configuration

Opens the Port Service Configuration dialog box, which displays the port configuration for Direct Connect configurations only. (This item is dimmed in Figure 1-5, which shows a menu for a DOH configuration.)

In-band Management Channel

Opens the Configure Inband Management Channel dialog box on which you manage the Cisco 6100 Series system through IP over ATM rather than through Ethernet.

Traps Recipients

Opens the Traps Recipients dialog box, on which you set multiple IP addresses to receive traps of specific severity and above (or none at all).

Routing Table

Opens the Routing Table dialog box on which you set specific routing for communication through the in-band management channel.

Event History Window

Opens the Events History, which displays events that pertain to the Cisco 6100 Series system. Refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide for more details.

Current Alarms

Opens the Current Alarms, a list of all alarms that are currently asserted in the system.

Discover 6100

Initiates the sequence of SNMP messages that are required to rediscover the Cisco 6100 Series equipment (chassis and modules), which is configured in the system.

Refresh status

Retrieves current state and alarm information from the Cisco 6100 Series system and uses it to refresh the colors or lock-and-key icons on each module tab.

Add LIM Chassis

ViewRunner does not support this option in this release. Therefore, it is dimmed.

Menu Item	Description
6100 Series Properties	Opens either the Status or Configuration tabs on the 6100 Properties dialog box.
Pool Properties	Opens the Pool Properties dialog box, which displays the properties of physical and logical pools on the Physical Pool tabs and the Logical Pool tabs. (This field relates to Digital Off-Hook configurations only.)
Active Connections	Opens the Active Connections dialog box, which lists the active connections and in-service modems.
View All Subscribers	Opens the View All Subscribers dialog box, which displays a comprehensive list of all subscribers who are currently receiving service.
View Subscriber PVCs	Opens the Subscriber PVCs dialog box, which lists current PVCs and the subscribers who are associated with the PVCs.
View Equipment Inventory	Opens the Equipment Inventory dialog box, which lists all discovered modules and inventory details about them. For DOH configurations, this dialog box also identifies associated pools.
6100 Performance	Opens the Performance Management dialog box, which displays performance statistics for the Cisco 6100 Series system.
Port Service Configuration	Opens the Port Service Configuration dialog box, which displays the port configuration for Direct Connect configurations only. (This item is dimmed in Figure 1-5, which shows a menu for a DOH configuration.)
In-band Management Channel	Opens the Configure Inband Management Channel dialog box on which you manage the Cisco 6100 Series system through IP over ATM rather than through Ethernet.
Traps Recipients	Opens the Traps Recipients dialog box, on which you set multiple IP addresses to receive traps of specific severity and above (or none at all).
Routing Table	Opens the Routing Table dialog box on which you set specific routing for communication through the in-band management channel.
Event History Window	Opens the Events History, which displays events that pertain to the Cisco 6100 Series system. Refer to the Cisco 6100 Series with NI-1 Alarm Summary Guide for more details.
Current Alarms	Opens the Current Alarms, a list of all alarms that are currently asserted in the system.
Discover 6100	Initiates the sequence of SNMP messages that are required to rediscover the Cisco 6100 Series equipment (chassis and modules), which is configured in the system.
Refresh status	Retrieves current state and alarm information from the Cisco 6100 Series system and uses it to refresh the colors or lock-and-key icons on each module tab.
Add LIM Chassis	ViewRunner does not support this option in this release. Therefore, it is dimmed.

Using the Cisco 6110 Chassis Menu

To use the options for managing the Cisco 6110 chassis, right-click the Cisco 6110 chassis. Figure 1-6 shows the two options that are available on the Cisco 6110 chassis menu.

Note The Cisco 6110 chassis options apply only to DOH configurations.

Figure 1-6: Cisco 6110 Chassis Menu

Table 1-4 describes the functions of the Cisco 6110 menu options.

Table 1-4: Cisco 6110 Menu Options

Menu Item Description

Chassis Properties

Displays chassis properties such as backplane information.

Delete Chassis

Deletes the Cisco 6110.

Menu Item	Description
Chassis Properties	Displays chassis properties such as backplane information.
Delete Chassis	Deletes the Cisco 6110.

Using the Modules and Ports Menus

To access the Status and Configuration tabs for modules, their ports, and the chassis, right-click with your cursor over the targeted module. Right-clicking a module displays the menu for that module, its port, and the 6100 Properties. The Module Properties menu includes items that you can choose to navigate directly to the Status tab or Configuration tab for that module and for the 6100 chassis.

Figure 1-7 shows the menus that you can access by right-clicking a module.

Figure 1-7: Module, Port, and 6100 Properties Menus

The type of module that you choose determines the number of port items that a module menu displays. For example, the system controller has no port items; the LIM, the Flexi, and the STU-C module menus each have four port items; the CAP ATU-C and DMT-2 ATU-C module menus each have two port items. These menus are shown in the illustrations that follow. (The Delete Chassis and Delete Module options are dimmed in most of these illustrations because this option is dimmed unless an entity is locked.)

Figure 1-8 shows an example of the LIM Module Properties menu.

Note LIMs exist only in DOH configurations.

Figure 1-8: LIM Menu Showing the Module Properties Menu

Figure 1-9 shows an example of the LIM Port Properties menu.

Figure 1-9: LIM Menu Showing the Port Properties Menu

Figure 1-10 shows an example of the LIM Chassis menu.

Figure 1-10: LIM Menu Showing the Chassis Menu

Table 1-5 describes each of the Module, Port, and LIM menu items.

Table 1-5: Module, Port, and LIM Menu Items

Menu Item Description

Module Properties

Gives you direct access to the Status and Configuration tabs on the corresponding Module Properties dialog box for a particular module.

Port Properties

Gives you direct access to the Status and Configuration tabs on the corresponding Module Properties dialog box for a particular port.

Delete Module

Deletes the specified module from the Cisco 6100 Series system. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Chassis

Gives you direct access to the chassis properties. Selecting this option is the same as right-clicking on a chassis itself.

Menu Item	Description
Module Properties	Gives you direct access to the Status and Configuration tabs on the corresponding Module Properties dialog box for a particular module.
Port Properties	Gives you direct access to the Status and Configuration tabs on the corresponding Module Properties dialog box for a particular port.
Delete Module	Deletes the specified module from the Cisco 6100 Series system. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.
Chassis	Gives you direct access to the chassis properties. Selecting this option is the same as right-clicking on a chassis itself.

Using the System Controller Menu

To access the management options for the system controller, right-click with your cursor over the system controller module. The menu that displays is shown in Figure 1-11.

Figure 1-11: System Controller Menu and SubMenu

Table 1-5 describes the System Controller menu options and describes each of their functions.

Table 1-6: System Controller Menu Items

Menu Items Description

Module Properties

Opens the SC Module Properties dialog box Status and Configuration tabs.

Delete Module

Deletes the module. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

6100 Properties

Opens the 6100 Properties dialog box Status and Configuration tabs.

Menu Items	Description
Module Properties	Opens the SC Module Properties dialog box Status and Configuration tabs.
Delete Module	Deletes the module. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.
6100 Properties	Opens the 6100 Properties dialog box Status and Configuration tabs.

Using the LIM Controller Menus

To access the options for managing the LIM controller, right-click with your cursor over the LIM.

Note The LIM controller options apply only to DOH configurations.

The menus that are displayed when you click on the LIM are shown in Figure 1-12.

Figure 1-12: LIM Controller---Module and Chassis Properties Menus

The menu options for the LIM controller are described in Table 1-7.

Table 1-7: LIM Controller Menu Items

Menu Item Description

Module Properties

Gives you direct access to the Status or Configuration tabs for the LIM controller module.

Delete Module

Deletes the LIM controller. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Chassis

Displays a menu for selecting chassis options, including Chassis Properties and Delete Chassis.

Reset

Allows you to reset the LIM controller.

Menu Item	Description
Module Properties	Gives you direct access to the Status or Configuration tabs for the LIM controller module.
Delete Module	Deletes the LIM controller. This option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.
Chassis	Displays a menu for selecting chassis options, including Chassis Properties and Delete Chassis.
Reset	Allows you to reset the LIM controller.

Using the Empty Chassis Slot Menu

To manage the properties and configurations of an empty slot, right-click that slot. The menu that appears is shown in Figure 1-13.

Figure 1-13: Empty Slot Menu

Table 1-8 describes each chassis slot menu item and its function.

Table 1-8: Empty Chassis Slot Menu Items

Menu Item Description

Insert Module

Not available with this software version.

6100 Properties

Provides direct access to Cisco 6100 Series properties, such as system date and time. The Delete Chassis option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Menu Item	Description
Insert Module	Not available with this software version.
6100 Properties	Provides direct access to Cisco 6100 Series properties, such as system date and time. The Delete Chassis option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Using the Empty Cisco 6110 Slot

To manage the properties and configuration of an empty Cisco 6110 chassis, right-click the empty Cisco 6110 chassis. The menu in Figure 1-14 appears.

Figure 1-14: Empty Cisco 6110 Slot Menu

Table 1-9 describes the items on the empty Cisco 6110 menu.

Table 1-9: Empty Cisco 6110 Slot Menu Items

Menu Item Description

Insert Module

Not available with this software version.

Chassis

Provides direct access to the Cisco 6110 backplane revision information. The Delete Chassis option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Menu Item	Description
Insert Module	Not available with this software version.
Chassis	Provides direct access to the Cisco 6110 backplane revision information. The Delete Chassis option is dimmed unless you lock an entity according to the rules specified in "Using ViewRunner to Manage the Status of the Cisco 6100 Series System." This option is always dimmed for users with user-only privileges.

Using the Menu Bar

You can also navigate in ViewRunner by using the menu bar on the GUI. The menu bar is located at the top of the GUI and is shown in Figure 1-16. The "Using the Toolbar" section describes the tool icons on the toolbar.

Figure 1-15: ViewRunner Menu Bar

The menu bar contains the following menus:

File---Save Configuration, Restore Configuration, Exit (see Figure 1-16).
Edit---Discover 6100, Discover New Events, and Remove Selected Events (see Figure 1-17). The last two menu choices are dimmed until you open the Events History dialog box and events are occurring.
Options---Login, Administration, 6100 Addresses, ViewRunner Preferences (see Figure 1-18).
Tools---Upgrade 6100 Software, View 6100 Software Image Data, Convert to DC Mode (see Figure 1-19). The menu option Convert to DC Mode is dimmed unless you change this setting in the ViewRunner Preferences dialog box.
View---Status Bar, Chassis View, Event History View, Current Alarms View, Zoom-In, Zoom-Out (see Figure 1-20).
Window---Cascade, Tile Horizontally, Tile Vertically, Configuration last discovered, Current Events last discovered, and Current Alarms last discovered (see Figure 1-21).
Help---About ViewRunner.

Note Online Help is currently unavailable in ViewRunner.

You can access each of these options by clicking the menu and choosing from among the items.

Figure 1-16: File Menu

Figure 1-17: Edit Menu

Figure 1-18: Options Menu

Figure 1-19: Tools Menu

Figure 1-20: View Menu

Figure 1-21: Window Menu

The toolbar is located directly below the menu bar and is described in the following section.

Using the Toolbar

You can use the GUI toolbar to navigate in ViewRunner and bypass the menu bar (located above the toolbar) to perform certain tasks. The ViewRunner toolbar is shown in Figure 1-22.

Figure 1-22: ViewRunner Toolbar

The fields and icons in the toolbar are listed and described in Table 1-10.

Table 1-10: ViewRunner Toolbar Description

Toolbar Item Description

6100 IP address list box

Displays a list of IP addresses that you have added in the 6100 Addresses dialog box. (See "Setting 6100 Addresses" section for how to add IP addresses to this list.) Each IP address corresponds to a Cisco 6100 Series system. Use this option to navigate between various Cisco 6100 Series systems.

Event History

Displays all of the events that are set for a Cisco 6100 Series system in the current Chassis View. This tool is a bell icon.You can also choose this option from the toolbar View menu.

Chassis View

Displays the Chassis View of the last discovered Cisco 6100 Series system. This tool is a small chassis icon.
You can also choose this option from the menu bar View menu.

Current Alarms

Displays all current alarms for the Cisco 6100 Series system at the time you open the dialog box. You must refresh the dialog box for ViewRunner to clear old alarms or log new ones. This tool is a bell icon that has a red exclamation mark on it.
You can also choose this option from the menu bar View menu.

Toolbar Item	Description
6100 IP address list box	Displays a list of IP addresses that you have added in the 6100 Addresses dialog box. (See "Setting 6100 Addresses" section for how to add IP addresses to this list.) Each IP address corresponds to a Cisco 6100 Series system. Use this option to navigate between various Cisco 6100 Series systems.
Event History	Displays all of the events that are set for a Cisco 6100 Series system in the current Chassis View. This tool is a bell icon.You can also choose this option from the toolbar View menu.
Chassis View	Displays the Chassis View of the last discovered Cisco 6100 Series system. This tool is a small chassis icon. You can also choose this option from the menu bar View menu.
Current Alarms	Displays all current alarms for the Cisco 6100 Series system at the time you open the dialog box. You must refresh the dialog box for ViewRunner to clear old alarms or log new ones. This tool is a bell icon that has a red exclamation mark on it. You can also choose this option from the menu bar View menu.

Setting 6100 Addresses

To set IP or node addresses that you want to appear on the 6100 address list box, follow these steps:

Step 1 Chose 6100 Addresses from the Option menu.

Doing this opens the 6100 Address dialog box, shown in Figure 1-23.

Figure 1-23: 6100 Address Dialog Box

Any current addresses that you have already added display in the Current 6100s group box.

Step 2 Type in the IP address in the IP Address field.

Step 3 Type a name in the Name field if you want to identify this IP address by a specific name.

Step 4 Click Add to include this IP address to the Current 6100s group box list.

Step 5 Repeat Step 2 through Step 4 for any IP addresses that you want to include in the list.

Step 6 Click OK when you are finished to return to the Chassis view.

Step 7 To delete an address in the Current 6100s group box list, highlight that address, click Delete, and then click OK to return to the Chassis view.

Chassis View Toolbar

The Chassis View toolbar in Figure 1-24 appears directly below the ViewRunner toolbar on the GUI.

Figure 1-24: Chassis View Toolbar

The icons on the Chassis View toolbar in Figure 1-24 are described in Table 1-11.

Table 1-11: Chassis View Toolbar Icon Description

Chassis View Toolbar Icon Description

Discover 6100

Rediscovers a Cisco 6100 Series system and provides the most current tab colors.

Zoom out

Decreases the appearance of the Cisco 6100 Series Chassis View.

Zoom in

Enlarges the appearance of the Cisco 6100 Series Chassis View until it is the size of the window, at which time the icon becomes dimmed.

Chassis View Toolbar Icon	Description
Discover 6100	Rediscovers a Cisco 6100 Series system and provides the most current tab colors.
Zoom out	Decreases the appearance of the Cisco 6100 Series Chassis View.
Zoom in	Enlarges the appearance of the Cisco 6100 Series Chassis View until it is the size of the window, at which time the icon becomes dimmed.

Using a Logical Service Orientation

Another way to navigate in ViewRunner is to use logical service-oriented navigation. This method allows quick navigation to a module, port, or Subscriber Properties dialog box from the following summary dialog boxes:

View All Subscribers
Event History
Current Alarms
Subscriber PVCs
View Equipment Inventory
Active Connections
Performance Management
Port Service Configuration (Direct Connect configuration only)

When provisioning subscribers to ports for service, using logical service-oriented navigation eliminates the need to display the GUI Chassis View and click the physical position of the entity that you are provisioning. You can still double-click an entity in the Chassis View and access the property dialog boxes that are necessary to provision services.

For the dialog boxes that support the logical service-oriented navigation feature, the access identifier (AID) text displays as blue, underlined text. This convention indicates that the text is a hyperlink to the corresponding property dialog box. Clicking any blue, underlined hyperlink takes you to the property dialog box that is associated with the selected entity. The cursor changes to a hand pointer when you move it over one of the hyperlinks.

For example, if you click the Subscriber ID link in the View All Subscribers dialog box, the Subscriber Properties dialog box for the selected subscriber opens. The dialog box is the same as the one that you open from the Port Configuration tab on the Module Properties dialog box. You can then edit or delete the selected subscriber from this dialog box.

If you click the Service Provisioning button on the Subscriber Properties dialog box, you open the Service Provisioning dialog box, where you can add or delete permanent virtual circuits (PVCs). When you close the dialog box, ViewRunner updates the View All Subscribers dialog box with the new configuration.

An example of a View All Subscribers dialog box is shown in Figure 1-25.

Figure 1-25: View All Subscribers Dialog Box

An example of the Event History View dialog box with underlined hyperlinks is shown in Figure 1-26.

Figure 1-26: Event History View Dialog Box

Identifying the Common Elements of the ViewRunner GUI

You can use ViewRunner more easily by being aware of the similar features of the GUI dialog boxes. These similarities, common tabs, and common buttons, are discussed in the following sections.

Identifying Common Dialog Box Features

The properties dialog boxes, for all of the chassis and modules in the Cisco 6100 Series Chassis View, share a similar appearance and common elements such as tabs and buttons. To display the properties of a particular chassis or module, right-click the chassis or module, and then choose Properties from the menu. You can choose either Status or Configuration from the menu for that entity (port, module, chassis) to open the associated properties dialog box to that particular tab.

Double-clicking opens a Cisco 6100 Series chassis or module properties dialog box, respectively, to its Status tab. An example of a Module Properties dialog box open to the Status tab is shown in Figure 1-27. An example of a 6100 Properties dialog box is shown in Figure 1-28.

Figure 1-27: Module Properties Dialog Box

Figure 1-28: 6100 Properties Dialog Box

Identifying Common Tab Elements

ViewRunner dialog boxes make use of tabs to group options that you use for similar kinds of settings. The properties dialog boxes for all of the modules including the system controller module, the network interface module, the LIM, the LIM controller, and the xDSL modules all contain tabs.

The Module Properties dialog box contains these two sets of tabs:

One set of tabs show the module and its ports. You click on either the module tab or one of the port tabs to select the properties you want to check or modify.
The second set of tabs contain a Status tab and a Configuration tab. On the Status tab, you can check the status of the port, module, or chassis that you selected on the first set of tabs. On the Configuration tab, you can configure the settings for the module or port that you selected in the first set of tabs, or for the chassis.

The tabs that are common to the Cisco 6100 Series components are shown in Figure 1-29, Figure 1-31. and Figure 1-31.

Note The LIM tabs apply only to DOH configurations. STU-C and DMT-2 ATU-C tabs apply only to Direct Connect configurations.

Figure 1-29: CAP ATU-C, DMT-2 ATU-C, and STU-C Module Tabs

Figure 1-30: Flexi Module Tabs

Figure 1-31: LIM Tabs

Table 1-12 describes the functions of the common tab options.

Table 1-12: CAP ATU-C, DMT-2 ATU-C, STU-C, and LIM Tab Descriptions

Tab Description

Module

Specifies which entity you clicked on.

Port

Specifies the port whose status you want to view or whose configuration you want to set.

Status

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

Configuration

Displays specific information about the configuration of a module, such as inventory details, port information, and so forth. This tab displays options that allow you to manage the Administrative state.

Tab	Description
Module	Specifies which entity you clicked on.
Port	Specifies the port whose status you want to view or whose configuration you want to set.
Status	Displays the status of the various states that are associated with a module or chassis.
Configuration	Displays specific information about the configuration of a module, such as inventory details, port information, and so forth. This tab displays options that allow you to manage the Administrative state.

Identifying the Common Dialog Box Buttons

ViewRunner dialog boxes share the common buttons OK, Cancel, Apply, and Refresh. The first three buttons are shown in Figure 1-32.

Figure 1-32: Common Buttons

Table 1-13 describes the common buttons.

Table 1-13: Common Button Descriptions

Button Description

OK

Applies data that you input on a dialog box, and then closes it.

When you click OK, ViewRunner sends SNMP messages in a specific sequence to ensure that the configurations immediately take effect in the Cisco 6100 Series system.

If you click OK while the Administrative state is Unlocked, ViewRunner allows the information that does not affect service to be modified.

If you click OK while the Administrative state is Locked, ViewRunner locks the resource and commits all configuration information that you have modified.

Cancel

Closes the dialog box and ViewRunner does not apply the data that you have set or modified. ViewRunner discards any changes that you have made without requesting user confirmation.

Apply

Sends the data that you entered to the Cisco 6100 Series system. The dialog box remains open. At this point, you can still change the information that you have entered in the dialog box.

When you click Apply, ViewRunner sends SNMP messages in a specific sequence, which ensures that the configurations immediately take effect in a Cisco 6100 Series system.

If you click Apply while the Administrative state is Unlocked, ViewRunner allows you to modify the nonservice-affecting information.

If you click Apply while the Administrative state is Locked, ViewRunner locks the resource and commits all information that you set or modified.

Refresh

Obtains the most recent data from the system and reflects this data on the dialog box fields and displays.

Button	Description
OK	Applies data that you input on a dialog box, and then closes it. When you click OK, ViewRunner sends SNMP messages in a specific sequence to ensure that the configurations immediately take effect in the Cisco 6100 Series system. If you click OK while the Administrative state is Unlocked, ViewRunner allows the information that does not affect service to be modified. If you click OK while the Administrative state is Locked, ViewRunner locks the resource and commits all configuration information that you have modified.
Cancel	Closes the dialog box and ViewRunner does not apply the data that you have set or modified. ViewRunner discards any changes that you have made without requesting user confirmation.
Apply	Sends the data that you entered to the Cisco 6100 Series system. The dialog box remains open. At this point, you can still change the information that you have entered in the dialog box. When you click Apply, ViewRunner sends SNMP messages in a specific sequence, which ensures that the configurations immediately take effect in a Cisco 6100 Series system. If you click Apply while the Administrative state is Unlocked, ViewRunner allows you to modify the nonservice-affecting information. If you click Apply while the Administrative state is Locked, ViewRunner locks the resource and commits all information that you set or modified.
Refresh	Obtains the most recent data from the system and reflects this data on the dialog box fields and displays.

Detecting Entity Status Through Colors

ViewRunner displays colors on the module and port tab images. You can check the colors for a quick indication of the Administrative and Operational state of a port or module. ViewRunner refreshes the displayed color when you take any of the following actions:

Open a properties dialog box
Click the Status tab
Change the Administrative state, and then click OK or Apply.

A priority scheme defines which color is displayed on the module or port tab; that is, ViewRunner displays tabs of different colors to show the levels of state functionality. The tab colors and priorities are defined in Table 1-14.

Table 1-14: State Colors for Modules and Ports

Color State and Alarm Types Description

Blue

State---Unknown

For module tabs only. Indicates that the module is Unfilled-Provisioned. This state indicates that you have configured a module in the slot, but the system controller has not communicated with it since powering up.

Red

Alarm Type---Critical

For module or port tabs. A critical alarm is the most severe alarm that is present.

Orange

Alarm Type---Major

For module or port tabs. A major alarm is the most severe alarm that is present.

Yellow

Alarm Type---Minor

For module or port tabs. A minor alarm is the most severe alarm that is present.

Cyan

Alarm Type---Warning

For module or port tabs. A warning alarm is the most severe alarm that is present.

Green

State---Normal/Up

For module or port tabs. Indicates a normal state.

Color	State and Alarm Types	Description
Blue	State---Unknown	For module tabs only. Indicates that the module is Unfilled-Provisioned. This state indicates that you have configured a module in the slot, but the system controller has not communicated with it since powering up.
Red	Alarm Type---Critical	For module or port tabs. A critical alarm is the most severe alarm that is present.
Orange	Alarm Type---Major	For module or port tabs. A major alarm is the most severe alarm that is present.
Yellow	Alarm Type---Minor	For module or port tabs. A minor alarm is the most severe alarm that is present.
Cyan	Alarm Type---Warning	For module or port tabs. A warning alarm is the most severe alarm that is present.
Green	State---Normal/Up	For module or port tabs. Indicates a normal state.

Communicating With ViewRunner

ViewRunner communicates through various message dialog boxes. These message dialog boxes display particular instructions to you, as necessary, and occur in addition to the events or alarm traps that are sent to one or more recipients. (See "Viewing Events and Alarms," for more information on events and alarms.)

The following types of dialog boxes communicate information to you:

Confirmation dialog boxes
Error Information dialog boxes
SNMP message or error dialog boxes

Confirming Actions

Confirmation dialog boxes alert you to the consequences of carrying out a requested action. They also request a response, and their presence interrupts normal interaction with the ViewRunner application until you close the dialog box. An example of a Configuration dialog box is shown in Figure 1-33.

Figure 1-33: Example of Confirmation Dialog Box

The following actions cause the Confirmation dialog box to open:

Locking an entity that is involved in an active ADSL or SDSL connection. The message tells you that the active connections terminate if you do not end the action.
Deleting a resource. The message informs you of the extent of the configuration data that you are about to delete, which associations will be removed as a result of deleting the resource, and entities that will be deleted.
Modifying the system service type to DOH or Direct Connect.

Confirmation dialog boxes contain a confirmation icon, a message, a confirmation request, and Yes/No buttons. For example, if you attempt to delete a module, the following confirmation text appears in a Confirmation dialog box:

Deletion removes LCC module, port, subscriber, and PVC 
configurations. All LCC modules will be reset. Are You Sure?

The message informs you about the delete action. In some instances, a confirmation message warns you of the general consequences of proceeding. If the entity, or any of its subordinates, is involved in an active ADSL or SDSL connection, a Confirmation dialog box always appears, indicating that the active connections terminate if you do not end the action.

Getting Information About Errors

You can get information from ViewRunner about errors through the Error Information dialog boxes, which convey various messages about user error and the cause of the error. Error Information dialog boxes display when any of the following types of errors occur:

Application
Communication
Cisco 6100 Series system interaction

You must acknowledge that the error occurred to close the error dialog box.

An Error Information dialog box also appears if you leave a required field blank.

Getting Posted SNMP Messages or Errors

The ViewRunner Log Window is minimized once you open it, but automatically opens whenever an SNMP message or error is posted. The ViewRunner Log Window contains informational messages that describe what has taken place since you began running ViewRunner. The ViewRunner Log Window is a window rather than a dialog box; you cannot close it. You can, however, minimize it by selecting Minimize from its menu bar, and you can clear the messages in it by selecting Clear from its menu bar.

The ViewRunner Log Window displays SNMP error messages as they occur. You can expect some SNMP error messages during normal operation. These messages include SNMP timeout messages, which typically do not indicate a serious error unless they are persistent.

The following situations result in SNMP error messages:

Problem---ViewRunner is unable to discover a Cisco 6100 Series system because you entered the incorrect IP address or, for some other reason, communication is not successful. The resulting error message informs you that discovery has failed.

: Solution---Make sure you can ping the Cisco 6100 Series system. Correct the communication problem.

Problem---A time-out message returned from SNMP++ can indicate that a problem occurred when the system controller communicated with the agent. A time-out message can also indicate a serious problem such as a system controller not responding, or it may indicate a less serious problem such as high network traffic or a communications error. The resulting error message informs you that the SNMP request has timed out.

: Solution---Make sure you can ping the Cisco 6100 Series system. Correct the communication problem. If the problem is transient, it was probably a network problem that has been resolved.

Other messages could indicate an internal error with the Cisco 6100 Series system or with the ViewRunner software. Report any errors that you cannot resolve to Cisco TAC.

Note Before you report any problems that you discovered by using the Log dialog box, rename and save the vrlog.txt file. Then retrace your steps to the point just before the error message occurred. Also, note the exact error message that appeared in the Log dialog box. Report both the point-of-occurrence and the message itself when you contact Cisco TAC.

Managing ViewRunner and the Cisco 6100 Series System

The following functions are available to help you better manage the Cisco 6100 Series system and ViewRunner:

Saving and Restoring Configuration Data

You can back up node configuration data by using the save configuration tool. You can then use the restore configuration tool to quickly recover your configuration, which enable recovery from a corrupted or replaced system controller.

See "Using the Save Configuration and Restore Configuration Features," 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

You can take advantage of software updates by downloading new system software from a TFTP server. ViewRunner functions as a TFTP server and can handle requests for images from a Cisco 6100 Series system when the updates are located on the ViewRunner system. You can also use ViewRunner to specify any IP address and file path for TFTP so that other TFTP servers can handle file transfer.

The process is triggered by user menu selection or by resetting the system controller. As a fail-safe measure, before you reset the system, you should use the configuration save and restore wizard, described in "Using the Save Configuration and Restore Configuration Features." Follow this procedure 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.

Saving to a File

You can output the contents of certain lists of data to an ASCII text file. Notepad automatically launches to display this file. You can then modify the file, save it, or print it.

You can save information to a file from the following dialog boxes:

Active Connections
View All Subscribers
Subscriber PVCs
Equipment Inventory
Port Service Configuration
6100 Software Images
Event History Window
Current Alarm Window

In the first six dialog boxes listed, use the Save button to save to a file. In the last two dialog boxes listed, use the Save to File icon (that looks like a floppy disk) on the toolbar to save to a file. Use the Save to File feature to save a customized (filtered or sorted) view of the summary dialog box contents into an ASCII text file by completing the following steps:

Step 1 Click Save, or click the Save to File icon from the toolbar in the Current Alarm or Event History windows, to open a Save List Options dialog box.

An example of the Save List Options dialog box is shown in Figure 1-34.

Figure 1-34: Save List Options Dialog Box

Step 2 In the File Name field, leave the default of Output.txt, or type in a new name.

Notepad will launch the file with this file name after you have complete these steps.

Step 3 Optionally, in the Title field, type in a title that will appear at the top of the Notepad file.

In this dialog box, you can control how the output file is formatted. Initially, a list displays all column headings from the summary dialog box.

Step 4 Reorder the columns by moving the heading names using the up or down Move arrows to the right of the list.

Step 5 Delete the headings of corresponding columns that you do not want to include in the output file by clicking the Delete button to the right of the list.

The columns print left to right in the order that their headings appear in the list (see Figure 1-34).

Step 6 Click Reset to undo any changes you have made.

Step 7 Decide how to separate columns in a spreadsheet by selecting one of the following options:

Blank fill---Check this option to pad the contents of a column with blanks until a predefined width is reached. This option works well to display or print using fixed-width fonts.
Comma---Check this option to separate fields with a comma. This selection works well to import data into spreadsheet applications.
Tab---Check this option to separates fields with a tab. This format works well to import data into either spreadsheet or word-processing applications.

Step 8 Click OK to save the file and have it immediately open in Notepad.

Using the Command Line Interface

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:

Ensure that you have met the following requirements:

The serial interface includes a DB-9 male connector that is attached to the system controller faceplate serial port.
The terminal is VT100 compatible
The serial interface software is configured at 38,400 baud, no parity, 8 data bits, 1 stop bit, and no flow control (38400, N, 8, 1, N).
The default Telnet port number for the CLI connection is 7000. To connect to the system controller, specify the IP address followed by the port number 7000 (for example, telnet 192.168.7.71 7000).

Press Ctrl-L to refresh and redraw the CLI dialog box.

Use the following command syntax:
- The first word you should type next to the CLI prompt is a command (a verb) followed by one or more arguments or no argument.
- Separate each argument with one space.
- Commands and arguments are not case sensitive.
(See the "Using the Command Syntax" section for a more detailed description.)
Press the up arrow to display the last command that you entered on prompt (history).
You can edit the history command for rapid command syntax modification.
If you attempt to enter an invalid command, a list of supported commands displays.

Guidelines for Getting Output from the CLI

Data output formats can include the following common features:

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

Determining Invalid Commands from the CLI

Table 1-15 describes the errors that display for invalid commands.

.
Table 1-15: 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.

Directly Controlling and Managing the Cisco 6100 Series System through the ATM Channel

You can use the ViewRunner in-band management channel to directly control and manage the Cisco 6100 Series system through the asynchronous transfer mode (ATM) channel. You provision and operate the system in the same way whether you are using an Ethernet port or an in-band channel. The only difference between the two methods is that if you use the in-band management channel, ViewRunner uses the ATM as the physical layer for communication, rather than using conventional Ethernet physical media.

ViewRunner supports software downloads and restorations for Cisco 6100 Series nodes. You manage these nodes through the in-band 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. If the controller does not support software download or restore, ViewRunner issues warnings.

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 by means of multiple protocols over a single virtual channel.

To ensure that the Cisco 6100 Series system is sending the outbound packets to the correct interface (Ethernet or in-band), ViewRunner supports a routing table for various IP addresses. You only need to use this table if you use the in-band management channel. Ethernet takes care of its own routing. See "Configuring the System," for more information on the in-band management channel.

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.

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.

Table of Contents

Using ViewRunner---An Overview