ViewRunner for Windows Overview

The "ViewRunner for Windows Overview" chapter describes the ViewRunner for Windows program, system files, navigational system, system dialogs, and management tools. The chapter contains the following sections:

Understanding Cisco 6100 Chassis and Modules
System Files
ViewRunner for Windows Navigation
Common Screen Elements
Message Dialogs
Cisco 6100 and ViewRunner Management Tools

1.1 Understanding Cisco 6100 Chassis and Modules

ViewRunner for Windows is the graphical user interface application that lets you configure your Cisco 6100 system and manage Cisco 6100 nodes. ViewRunner for Windows supports the auto-discovery of Cisco 6100 equipment. That is once you have installed ViewRunner for Windows and connected it to your Cisco 6100, ViewRunner for Windows retrieves configuration data from the Cisco 6100's SNMP agent. It then displays a graphical representation of your Cisco 6100 like the one shown in Figure 1-1.

ViewRunner for Windows main menu supports three primary views: the chassis view, whereby you can see a graphical representation of the Cisco 6100 and configure it according to your system needs, the events history view, and the current alarm view. See "Event History and Current Alarms" for more information on events and alarms.

Note Events (informational and alarms) are covered in detail in of the Cisco 6100 Maintenance and Troubleshooting Manual.

ViewRunner for Windows 2.3.5 is the craft interface for the Cisco 6100 for its 2.3.0 (SF-6100-2.3.0) release. It is bundled with the Cisco 6100 multiplexer chassis or may be downloaded from Cisco Connection Online (CCO).

The ViewRunner for Windows 2.3.5 release supports the following Cisco 6100 releases:

Cisco 6100 2.3.0 (SF-6100-2.3.0)
Cisco 6100 2.2.5 (SF-6100-2.2.5)
Cisco 6100 2.2.1 (SF-6100-2.2.1)
Cisco 6100 2.2.0 (SF-6100-2.2.0)
Cisco 6100 2.1.3 (SF-6100-2.1.3)
Cisco 6100 2.1.2

The following matrix more fully describes the compatibility among Cisco 6100 and ViewRunner for Windows releases.

Table 1-1: ViewRunner for Windows and Cisco 6100 Release Compatibility Matrix
Cisco 6100 Releases

Release 2.3.0 Releases 2.2.1/2.2.5 Release 2.2.0 Release 2.1.3 Release 2.1.2

ViewRunner for Windows

Release 2.3.5

X

X

X

X

X

Release 2.3.0

Cisco 6100 2.2.1

X
FCM update for 2.2.5

X

X

X

Release 2.2.1

Cisco 6100 2.2.0

Cisco 6100 2.2.0

X

X

X

Release 2.2.0

Cisco 6100 2.2.0

Cisco 6100 2.2.0

X

Cisco 6100 2.2.0

X

Release 2.1.0

Cisco 6100 2.1.x

Cisco 6100 2.1.x

Cisco 6100 2.1.x

Cisco 6100 2.1.x

X

Legend:
X indicates that ViewRunner presents a feature set customized to this Cisco 6100 release's capabilities.

Cisco 6100 X.Y.Z -View Runner presents a feature set corresponding to the specified Cisco 6100 X.Y.Z release's capabilities. ViewRunner prompts the user when the Chassis View is opened that the feature set is not recognized and a default feature set is being used.

**Table 1-1: ViewRunner for Windows and Cisco 6100 Release Compatibility Matrix**
	Cisco 6100 Releases
	Release 2.3.0	Releases 2.2.1/2.2.5	Release 2.2.0	Release 2.1.3	Release 2.1.2
ViewRunner for Windows
Release 2.3.5	X	X	X	X	X
Release 2.3.0	Cisco 6100 2.2.1	X FCM update for 2.2.5	X	X	X
Release 2.2.1	Cisco 6100 2.2.0	Cisco 6100 2.2.0	X	X	X
Release 2.2.0	Cisco 6100 2.2.0	Cisco 6100 2.2.0	X	Cisco 6100 2.2.0	X
Release 2.1.0	Cisco 6100 2.1.x	Cisco 6100 2.1.x	Cisco 6100 2.1.x	Cisco 6100 2.1.x	X
Legend:	X indicates that ViewRunner presents a feature set customized to this Cisco 6100 release's capabilities. Cisco 6100 X.Y.Z -View Runner presents a feature set corresponding to the specified Cisco 6100 X.Y.Z release's capabilities. ViewRunner prompts the user when the Chassis View is opened that the feature set is not recognized and a default feature set is being used.

1.1.1 Chassis View

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

There are three types of chassis in the Cisco 6100 system. The first two of them can be managed through ViewRunner for Windows:

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

Note The POTS splitter chassis is not configured or monitored through ViewRunner. However, alarm conditions for this chassis are trapped and displayed by ViewRunner.

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

Note The chassis view differs depending upon the configuration style you select. The chassis view shown below displays the Digital Off-Hook (DOH) standard configuration style. See the ViewRunner for Windows Installation and Administration Manual for information on choosing a configuration style.

Figure 1-1: Cisco 6100 Chassis View

Note Once the Chassis View has been opened, it cannot be closed. Notice the "x" in the upper right hand corner has been disabled. You can minimize the window, however, to get it off the screen.

The chassis view displays the MC and each 6110 LCC. It also provides a top level display of modules, which you can view, add, modify, and delete. From the chassis view, you can view all status information, manage all configurations, and check the performance of the Cisco 6100. The chassis view title bar includes a timestamp of the date and time the system was last discovered. (See "Discovery," for information about auto-discovery.)

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

The chassis view displays colored module ejector tabs to indicate the status and state of each module and its ports. The color displayed is based on a set of rules defined below. The list below describes the highest priority color to display first and the lowest priority color last, in cases where more than one of the conditions described below is met. See "Cisco 6100 and ViewRunner State Management" for more information on states and see the Cisco 6100 Maintenance and Troubleshooting Manual for detailed information on alarms.

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

Ejector Tab Color State Description

Blue

Unknown

Indicates the Equipage state of the module is Unfilled-Provisioned. This state is used when a module has been configured in the slot; however, the SC¹ has not communicated with it since power up.

Brown

Locked

Either the module or all of the module's ports are configured with Administrative state of Locked.

Red

Critical Alarm

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

Orange

Major Alarm

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

Yellow

Minor Alarm

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

Green

Normal

The module and all of its ports are in a Normal state.

¹system controller

Ejector Tab Color	State	Description
Blue	Unknown	Indicates the Equipage state of the module is Unfilled-Provisioned. This state is used when a module has been configured in the slot; however, the SC¹ has not communicated with it since power up.
Brown	Locked	Either the module or all of the module's ports are configured with Administrative state of Locked.
Red	Critical Alarm	A critical alarm is the most severe alarm present on the module or any of its ports.
Orange	Major Alarm	A major alarm is the most severe alarm present on the module or any of its ports.
Yellow	Minor Alarm	A minor alarm is the most severe alarm present on the module or any of its ports.
Green	Normal	The module and all of its ports are in a Normal state.

The ejector tab colors are updated when you:

Open the Cisco 6100 Chassis View
Right click on the MC and select the Discover 6100 option
Right click on the MC and select the Refresh status option

Note The color ejector tabs do not get updated dynamically. Updates are based on background polling. As a result, the colors 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 on the MC and select the Refresh status option.

1.1.2 Managed Entities

To run ViewRunner for Windows, you should have some basic knowledge of Microsoft Windows 95, Microsoft 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. There are six types of modules:

SC
Network interface (NI) module
DS3 subtending module (STM)
ATU-C (CAP and DMT) modules
Line interface module (LIM) controller
LIM modules

Note Direct Connect configurations do not use LIMs or LIM controllers. Therefore, these entities are not managed in Direct Connect configurations.

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

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

Note POTS splitter chassis and modules are not auto-discovered nor managed by ViewRunner.

For descriptions of these modules, consult the Cisco 6100 Set Up and Installation Manual.

1.2 System Files

The ViewRunner maintains several system files that reside in the same folder from which ViewRunner for Windows is launched. These key system files include:

Release definition file (RDF)
Feature compatibility matrix (FCM) file
Key events log file

In addition to these files, there is a README file explaining how to install the ViewRunner software.

Note Updates to these files may be obtained from the Cisco Connection Online (CCO) or by contacting Cisco TAC.

1.2.1 Release Definition File

The ViewRunner maintains an RDF which identifies the software that is compatible with each hardware module/revision for a given system release. The SC and the ViewRunner use this file to check release compatibilities for software update downloads. See "Software Update Download" for more information about software update downloads.

The RDF is named 9000-xxx-xx.RDF where "9000-xxx-xx" is the latest release of the system. The file is stored in the ViewRunner system folder and contains information about the software and hardware release of the Cisco 6100 components. The information in each RDF will look similar to the following:

9000-XXX-XXX,Release 2.3
*******************************************************************************
Hardware Revision Table
*******************************************************************************
Begin
2651-003,1651-119-99,"SC"
2601-014,1601-117-99,"OC-3 NI SMF"
2601-015,1601-117-99,"OC-3 NI MMF"
2601-016,1601-117-99,"DS3 NI"
2601-012,1601-117-99,"Subtending DS3 NI"
2601-011,1601-117-99,"Subtending OC-3 NI MMF"
2601-010,1601-117-99,"Subtending OC-3 NI SMF"
2601-021,1601-117-99,"Subtending DS3 NI FPGA mod"
2601-020,1601-117-99,"Subtending OC-3 NI FPGA mod"
2601-019,1601-117-99,"Subtending OC-3 NI FPGA mod"
2101-003,9101-001-99,"Dual ATU-C CAP Direct Connect"
2101-004,9101-001-99,"Dual ATU-C CAP DOH"
2651-004,9651-002-99,"LCM"
2601-017,9601-005-99,"SHM"
End
*******************************************************************************
Image Table
*******************************************************************************
Begin
1651-119-99,scAL2.1.ima,836448,2108954440,"SC"
1601-117-99,niAL2.1.ima,537300,1861675004,"NI"
9101-001-99,atucDev1.60.ima,237520,654259661,"ATU-C"
9651-002-99,lcm2_d2.ima,237520,4124819411,"LCM"
9601-005-99,shmAL2.1.ima,390528,2430210418,"SHM"
End

1.2.2 Feature Compatibility Matrix File

Another key system file is the SC FCM file which contains feature descriptions of all releases up to and including the latest. ViewRunner uses the matrix to customize the features it presents to the user based on the SC release loaded on the Cisco 6100.

For example, an older release of a Cisco 6100 LIM controller module will not support the newer feature that allows the Administrative state to lock all entities before deleting a chassis. Therefore, the ViewRunner consults the compatibility matrix to determine that it should disable the Delete Chassis option if the module is not locked by the user.

ViewRunner reads the FCM to determine what features are supported in a given SC software release and customizes the features presented to the user when connected to that Cisco 6100.

Newer Cisco 6100 releases may be managed by ViewRunner without updating this file; however, the user is warned each time a new Cisco 6100 IP address is discovered if that node's SC software is not recognized. The following error dialog is generated when you connect to a Cisco 6100 containing an SC software version not found in the feature compatibility matrix file.

Figure 1-2: Feature Compatibility Error Dialog

In these cases, ViewRunner will present the latest default feature set to the user. An updated FCM may be obtained through CCO or by contacting Cisco TAC Center. Obtaining a newer FCM file may eliminate this warning. However, this message typically means that a newer ViewRunner version should be available.

The matrix file is named SCFeatureCompatibilityMatrix.csv, and is maintained as an Excel spreadsheet and output as a comma separated text file. Information in the matrix file should be similar to the following.

SC Software Version Direct Connect 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		MARGINATTEN						
9651-001-15	DIRECT	SWDLD	LCSADMIN	SCSADMIN	SCMAINT	MIFIX	MICNVRAM	PPDATUC	SUBTEND	MARGINATTEN	LCCIDFIX					
9651-001-21	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-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 most up-to-date 
Feature Compatibility File may be obtained at 
http://www.cisco.com/tech.html.  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."
,,,,,,,,,,
System Part #,LoopRunner Rel, Contains SC SW,,,,
BEGIN		
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-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)."
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 timeout."
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 parameters for 136K baud enable/disable and Non-Timer CPE train enable/disable

1.2.3 Key Events Log File

ViewRunner for Windows supports a log file that logs key events into a text file named VRLOG.TXT. This file is created in the folder from which the ViewRunner program was invoked. The file is intended to be used in troubleshooting problems with ViewRunner and the Cisco 6100.

The following events and information are logged in VRLOG.TXT

when ViewRunner starts up, including the software version number
when ViewRunner exits
any time a Cisco 6100 is auto-discovered, including IP address and timeout value being set for SNMP
any SNMP error that appears in the log window
SNMP errors not currently being handled by ViewRunner that might be useful (as in, GetSystemConnectMode() failure)
when SysUpTime drops below our "known" time (as in, detects SC reset)

The VRLOG.TXT file will not grow larger than 2 MBs. At 2 MBs, it truncates to 0 and starts over. The information in VRLOG.TXT is presented in a format similar to the following:

06/01/98 15:04:33    Error on HostGetSysUpTime - SNMP++: SNMP request timed out 
     (Jun 01, 1998   15:04:33)
ViewRunner exited (Jun 01, 1998   15:07:33)
ViewRunner started (EXE-200:0, DLL- 200:0) (Jun 02, 1998   15:55:57)
Discovering 'vrdemo,172.16.1.236' & setting SNMP_TIMEOUT_DELAY to 1000 (Jun 02, 1998   
     15:56:10)
HostGetSystemConnectMode failed. SC code does not support Direct Connect (Jun 02, 
     1998   15:56:15)
ViewRunner exited (Jun 02, 1998   15:57:29)
ViewRunner started (EXE-200:0, DLL- 200:0) (Jun 02, 1998   18:56:33)
Discovering 'vrdemo,172.16.1.236' & setting SNMP_TIMEOUT_DELAY to 1000 (Jun 02, 1998   
     18:56:47)
HostGetSystemConnectMode failed. SC code does not support Direct Connect (Jun 02, 
     1998   18:56:51)
ViewRunner exited (Jun 02, 1998   19:03:31)

In any given session in ViewRunner, the ViewRunner Log Window contains the current messages logged to the VRLOG.TXT file. These are only those error messages encountered during this session. The following figure illustrates the ViewRunner Log Window.

Figure 1-3: ViewRunner Log Window

1.3 ViewRunner for Windows Navigation

ViewRunner for Windows supports three navigation methods:

Double Left Click/Right Click Access
Toolbar Access
Menu Hierarchy

These navigational methods are explained in the next three sections.

1.3.1 Double Left Click/Right Click Access

The primary mechanisms for retrieving information about a particular module or chassis are the left and right mouse buttons. Both buttons act as a shortcut method for displaying properties about a particular module or chassis.

Double clicking with the left mouse button brings up the properties of the module that is directly beneath the cursor when the left button is selected. You can also use the right button of the mouse to bring up the pop-up menu containing a list of options available for a particular module. Pop-up menus are also context sensitive based on the chassis or slot that is beneath the cursor when the right button is selected.

Whether you choose to right or left, placing the cursor over the chassis but outside of the slots and left clicking, selects the chassis. Pop-up menu options are dimmed if you do not have necessary security privileges to execute those options. Menu options also are dimmed if requirements have not been met to allow those options or if the SC software version does not support those options.

The following series of pop-up menus show the options that appear when you right click on a particular entity.

Right Clicking on the Multiplexer Chassis

The following options are displayed when you right click on the Cisco 6100 MC in chassis view.

Note The Pool Properties... option is grayed out in Direct Connect configurations. However, the Port Service Configuration... option is enabled for Direct Connect configurations.

Figure 1-4: MC Pop-Up Menu

Pop-Up Menu Item	Description
Cisco 6100 Properties	Gives you direct access to the Status or Configuration tabs for the Cisco 6100.
Pool Properties	Displays the properties of physical and logical pools.
Active Connections	Opens the Active Connections view, displaying a list of the currently active ATU-C port to line port connections in the Cisco 6100.
View All Subscribers	Displays a comprehensive list of all subscribers currently receiving service.
View Subscriber PVCs	Displays a list of current PVCs and the subscribers associated with the PVCs.
View Equipment Inventory	Displays a list of all auto-discovered modules and chassis.
Cisco 6100 Performance	Displays performance statistics for the Cisco 6100.
Port Service Configuration	Displays the port configuration for Direct Connect configurations only. Therefore, it is grayed out here.
Inband Management Channel	Allows management of the Cisco 6100 through IP over ATM rather than through Ethernet.
Traps Recipients	Allows the setting of multiple IP addresses to receive traps of specific severity and above (or none at all).
Routing Table	Allows you to set specific routing for communication through the inband management channel.
Event History Window	Opens the Events window, which displays all events pertaining to the Cisco 6100. See the Cisco 6100 Maintenance and Troubleshooting Manual for more details.
Current Alarms	Opens a window showing all alarms currently asserted in the system.
Discover 6100	Initiates the sequence of SNMP messages required to rediscover Cisco 6100 equipment (chassis and modules) configured in the system.
Refresh status	Retrieves current state and alarm information from the Cisco 6100 and uses it to refresh the colors on the each module's ejector tabs.
Add LIM Chassis	ViewRunner for Windows does not support this option in this release. Therefore, it is grayed out.

Table 1-3: MC Pop-Up Menu Items

Pop-Up Menu Item Description

Cisco 6100 Properties

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

Pool Properties

Displays the properties of physical and logical pools.

Active Connections

Opens the Active Connections view, displaying a list of the currently active ATU-C port to line port connections in the Cisco 6100.

View All Subscribers

Displays a comprehensive list of all subscribers currently receiving service.

View Subscriber PVCs

Displays a list of current PVCs and the subscribers associated with the PVCs.

View Equipment Inventory

Displays a list of all auto-discovered modules and chassis.

Cisco 6100 Performance

Displays performance statistics for the Cisco 6100.

Port Service Configuration

Displays the port configuration for Direct Connect configurations only. Therefore, it is grayed out here.

Inband Management Channel

Allows management of the Cisco 6100 through IP over ATM rather than through Ethernet.

Traps Recipients

Allows the setting of multiple IP addresses to receive traps of specific severity and above (or none at all).

Routing Table

Allows you to set specific routing for communication through the inband management channel.

Event History Window

Opens the Events window, which displays all events pertaining to the Cisco 6100. See the Cisco 6100 Maintenance and Troubleshooting Manual for more details.

Current Alarms

Opens a window showing all alarms currently asserted in the system.

Discover 6100

Initiates the sequence of SNMP messages required to rediscover Cisco 6100 equipment (chassis and modules) configured in the system.

Refresh status

Retrieves current state and alarm information from the Cisco 6100 and uses it to refresh the colors on the each module's ejector tabs.

Add LIM Chassis

ViewRunner for Windows does not support this option in this release. Therefore, it is grayed out.

Right Clicking on the LIM Chassis

The following options are displayed when you right click on the Cisco 6110 LIM chassis.

Note The LIM chassis options do not apply in Direct Connect configurations.

Figure 1-5: LCC Pop-Up Menu

Pop-Up Menu Item	Description
Chassis Properties	Displays chassis properties such as backplane information.
Delete Chassis	Deletes the LCC (Cisco 6110)

Figure 1-6: LCC Pop-Up Menu Items

Pop-Up Menu Item Description

Chassis Properties

Displays chassis properties such as backplane information.

Delete Chassis

Deletes the LCC (Cisco 6110)

Right Clicking on Modules or Ports

The Module Properties and Port Properties pop-up menu items have two sub-items that take you directly to the Status tab or Configuration tab for the module. The number of port items displayed in the module's pop-up menu is context sensitive based on the type of module selected. For example, the SC pop-up has no port items, the LIM module pop-up has four port items, and the ATU-C module pop-up has two port items.

Right Clicking on ATU-C Modules

The following options are displayed when you right click on an ATU-C module:

Figure 1-7: ATU-C Pop-Up Menu

The following options are displayed when you right click on a LIM module.

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

Figure 1-8: LIM Pop-Up Menu

Pop-Up Menu Item	Description
Module Properties	Gives you direct access to the Status or Configuration tabs for a particular module.
Port Properties	Gives you direct access to the Status or Configuration tabs for a particular port.
Delete Module	Deletes the specified module from the Cisco 6100. This option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management." chapter. This option is always grayed out for users with User only privileges.
Chassis	Gives you direct access to the chassis properties. Selecting this option is the same as right-clicking a chassis itself.

Table 1-4: ATU-C and LIM Pop-Up Menu Items

Pop-Up Menu Item Description

Module Properties

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

Port Properties

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

Delete Module

Deletes the specified module from the Cisco 6100. This option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management." chapter. This option is always grayed out for users with User only privileges.

Chassis

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

1.3.2 Right Clicking on the System Controller

The following options are displayed when you right click on the SC:

Figure 1-9: SC Pop-Up Menu

Pop-Up Menu Items	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 grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.
6100 Properties	Displays the options available for the Cisco 6100 such as system date and time.

Table 1-5: SC Pop-Up Menu Items

Pop-Up Menu Items 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 grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

6100 Properties

Displays the options available for the Cisco 6100 such as system date and time.

1.3.3 Right Clicking on the LIM Controller

The following options are displayed when you right click on the LIM controller.

Note The LIM controller options do not apply in Direct Connect configurations.

Figure 1-10: LIM Controller Pop-Up Menu

Table 1-6: LIM Controller Pop-Up Menu Items

Pop-Up Menu Item Description

Module Properties

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

Delete Module

Deletes the LIM controller. This option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

Chassis

Displays a pop-up menu for selecting chassis options including Chassis Properties and Delete Chassis.

Reset

Allows you to reset the LIM controller.

Pop-Up Menu Item	Description
Module Properties	Gives you direct access to the Status or Configuration tabs for a particular module.
Delete Module	Deletes the LIM controller. This option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.
Chassis	Displays a pop-up menu for selecting chassis options including Chassis Properties and Delete Chassis.
Reset	Allows you to reset the LIM controller.

1.3.4 Right Clicking on an Empty MC Slot

The following options appear when you right click on an empty MC (Cisco 6100) slot:

Figure 1-11: Empty Slot Pop-Up Menu

Table 1-7: Empty MC Slot Pop-Up Menu Items

Pop-Up Menu Item Description

Insert Module

Inserts a new module.

Note This option is not supported in this release.

6100 Properties

Provides direct access to Cisco 6100 properties such as system date and time. The Delete Chassis option is grayed out unless the you lock an entity according to the rules specified in "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

Pop-Up Menu Item	Description
Insert Module	Inserts a new module. Note This option is not supported in this release.
6100 Properties	Provides direct access to Cisco 6100 properties such as system date and time. The Delete Chassis option is grayed out unless the you lock an entity according to the rules specified in "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

1.3.5 Right Clicking on an Empty LCC Slot

The following options appear when you right click on an empty LCC (6110) slot.

Figure 1-12: Empty LCC Slot Pop-Up Menu

Pop-Up Menu Item	Description
Insert Module	Inserts a new module. Note This option is not supported in this release.
Chassis	Provides direct access to 6110 chassis backplane revision information. The Delete Chassis option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

Table 1-8: Empty LCC Slot Pop-Up Menu Items

Pop-Up Menu Item Description

Insert Module

Inserts a new module.

Note This option is not supported in this release.

Chassis

Provides direct access to 6110 chassis backplane revision information. The Delete Chassis option is grayed out unless the you lock an entity according to the rules specified in the "Cisco 6100 and ViewRunner State Management," chapter. This option is always grayed out for users with User only privileges.

1.3.6 Toolbar Access

As a second means of navigation, ViewRunner for Windows has a toolbar that allows you to bypass the menu hierarchy to perform certain tasks.

The ViewRunner toolbar is found in Figure 1-13.

Figure 1-13: ViewRunner Toolbar

Table 1-9: ViewRunner Toolbar Field/Icon Description

Toolbar Field/Icon Field or Icon Description

IP Address

Displays a drop-down list of IP addresses added to
ViewRunner for Windows. Each IP address corresponds to a Cisco 6100. This option allows you to flip back and forth easily between various Cisco 6100s.

Event History Window

Displays all events set for a Cisco 6100 in the current chassis view.

Chassis View

Displays the chassis view of the last discovered Cisco 6100.

Current Alarms Window

Displays all current alarms the Cisco 6100 at the time the window is opened. The window must be refreshed to clear old or log new alarms.

Current Alarms Count

Displays the number of current alarms polled which are critical (red), major (orange), and minor (yellow).

Toolbar Field/Icon	Field or Icon Description
IP Address	Displays a drop-down list of IP addresses added to ViewRunner for Windows. Each IP address corresponds to a Cisco 6100. This option allows you to flip back and forth easily between various Cisco 6100s.
Event History Window	Displays all events set for a Cisco 6100 in the current chassis view.
Chassis View	Displays the chassis view of the last discovered Cisco 6100.
Current Alarms Window	Displays all current alarms the Cisco 6100 at the time the window is opened. The window must be refreshed to clear old or log new alarms.
Current Alarms Count	Displays the number of current alarms polled which are critical (red), major (orange), and minor (yellow).

Figure 1-14: Chassis View Toolbar

The icons on this bar are described in Table 1-10.

Table 1-10: Chassis View Toolbar Icon Description

Chassis View Toolbar Icons Icon Description

Discover 6100

Rediscovers a Cisco 6100 and provides most current view of ejector tab colors.

Zoom Out

Shrinks the Cisco 6100 Chassis View.

Zoom In

Enlarges the Cisco 6100 Chassis View until it is the size of the window. Then it becomes grayed out.

Chassis View Toolbar Icons	Icon Description
Discover 6100	Rediscovers a Cisco 6100 and provides most current view of ejector tab colors.
Zoom Out	Shrinks the Cisco 6100 Chassis View.
Zoom In	Enlarges the Cisco 6100 Chassis View until it is the size of the window. Then it becomes grayed out.

1.3.7 Menu Access

As a third means of navigation, the menu hierarchy in ViewRunner for Windows consists of dropdown menus and options therein.

Menu bar options are available to view or modify the configuration, alarm, performance and status details of Cisco 6100 components. The menu bar also lets you add and delete 6110 chassis and modules.

The Figure 1-15 shows all the main ViewRunner menu possibilities.

Figure 1-15: Menu Hierarchy - Top Level

You can access each of these options by left-clicking on the menu and selecting from the options.

1.3.8 Logical Service Oriented Navigation

ViewRunner for Windows supports a logical service oriented navigation which allows rapid navigation to a module, port, or subscriber Property dialog from the summary dialogs.

Logical service oriented navigation eliminates the need to bring up the craft oriented chassis view and click on the physical position of the entity to be provisioned. Although logical service oriented navigation eliminates the need to use the physical navigation to the entity via the chassis view, you can still double click on an entity in the chassis view and access the property dialogs necessary to provision services.

The summary dialogs from which you can use the logical service hyperlinks include:

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

For the dialogs that support the logical service oriented navigation feature, the access identifier (AID) text displays as underlined, blue text indicating that it is a hyperlink to the corresponding property dialog. Single clicking on any underlined hyperlink will take you to the property dialog associated with the selected entity. The cursor changes to a hand pointer when moved over one of the hyperlinks. For example, clicking on the subscriber ID in the View All Subscribers dialog opens the Subscriber Properties dialog for the selected subscriber. The dialog is the same as the one from the Port Configuration screen. The selected subscriber can be edited or deleted from this dialog.

Clicking on the Service Provisioning button will open the Service Provisioning dialog, where permanent virtual circuits (PVCs) may be added or deleted. When the dialog is dismissed, the View All Subscribers dialog is updated with the new configuration.

Figure 1-16: View All Subscribers - Hyperlinks.

The following shows an Event History Window with underlined hyperlinks:

Figure 1-17: Event History Window - Hyperlinks

1.4 Common Screen Elements

When you access any Cisco 6100 component, you will notice the similarities between the screens that appear. Most components have windows, tabs, and buttons very similar to each other as described below.

1.4.1 Common Windows

The properties windows for all chassis and modules in the Cisco 6100 chassis view are similar to each other. To display the properties of a particular chassis or module, right click the mouse on a chassis or a module and select Properties option. This opens a Cisco 6100, chassis, or module property window respectively. The windows contain similar features including a two-tiered tab design, overlaying a second, higher level set of tabs outside the basic property dialog tabs. The outside (higher level) sets of tabs lets you select between the module and any of the module's ports. The inside sets of tabs provide the same functionality as the basic property dialog tabs, allowing rapid selection between the selected module or port's Status and Configuration tabs.Use the tabs on the windows, typically the Status or Configuration tabs, to access property windows for other types of logical entities, such as subscribers or pools.

1.4.2 Common Tabs

ViewRunner for Windows uses common tabbed dialogs for all property dialogs (Status, Configuration). Attributes for an entity are displayed in a tabbed dialog. Each tab displays a category of information about the entity. Each tab is a dialog itself that may contain a tabbed control (for example, the module tab contains Status and Configuration Tabs). See "Cisco 6100 and ViewRunner State Management" for a discussion on entities.

Common tab categories used by entities display status, configuration, performance, and/or service provisioning, in this order. Only a subset of these tabs typically applies to any given entity. Module level tab categories, however, contain two levels of tabs. The top level module and port tabs display the common tab categories.

The following diagrams show the tabs common to Cisco 6100 components:

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

Figure 1-18: ATU-C Module Tabs

Figure 1-19: LIM Module Tabs

Table 1-11: ATU-C and LIM Tab Descriptions

Tab Description

Status

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

Configuration

Displays specifics about the configuration, such as inventory details, port information, etc. Also allows you to manage the Administrative state.

Tab	Description
Status	Displays the status of various states associated with a module or chassis.
Configuration	Displays specifics about the configuration, such as inventory details, port information, etc. Also allows you to manage the Administrative state.

1.4.3 Common Colors

ViewRunner for Windows displays colors on module and port tabs to provide a quick status view of their Administrative and Operational state. The displayed color changes anytime you:

open a property window,
select the status tab,
change the Administrative state, and select OK or Apply

A priority scheme defines which color is displayed on the module or port tab.

ViewRunner for Windows uses tabs with different colors to show various levels of state functionality. The varying tab colors are defined below:

Table 1-12: State Colors for Modules and Ports

Icon Color State Description

Blue

Unknown

For module tabs only. Indicates the Equipage state of the module is Unfilled-Provisioned. This state is used to depict when a module has been configured in the slot, however the SC has not communicated with it since power up.

Brown

Locked

For module or port tabs - Node reports Administrative state of Locked.

Red

Critical Alarm

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

Orange

Major Alarm

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

Yellow

Minor Alarm

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

Cyan

Warning Alarm

For module or port tabs - A warning alarm is the most severe alarm present. Not supported in this release.

Green

Normal/Up

For module or port tabs. Indicates a Normal state.

Icon Color	State	Description
Blue	Unknown	For module tabs only. Indicates the Equipage state of the module is Unfilled-Provisioned. This state is used to depict when a module has been configured in the slot, however the SC has not communicated with it since power up.
Brown	Locked	For module or port tabs - Node reports Administrative state of Locked.
Red	Critical Alarm	For module or port tabs - A critical alarm is the most severe alarm present
Orange	Major Alarm	For module or port tabs - A major alarm is the most severe alarm present
Yellow	Minor Alarm	For module or port tabs - A minor alarm is the most severe alarm present.
Cyan	Warning Alarm	For module or port tabs - A warning alarm is the most severe alarm present. Not supported in this release.
Green	Normal/Up	For module or port tabs. Indicates a Normal state.

1.4.4 Common Buttons

The following diagrams show the button common in ViewRunner for Windows:

Figure 1-20: Common Buttons

Table 1-13: Common Button Descriptions

Button Description

OK

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

When the OK buttons is selected, ViewRunner for Windows sends SNMP sets in a specific sequence to assure the configurations take affect immediately in the Cisco 6100.

If the OK button is selected while the Administrative state is Unlocked, ViewRunner for Windows allows the non-service affecting information to be modified.

If the OK button is selected while the Administrative state is Locked, ViewRunner for Windows will lock the resource and send all configuration information that has been modified.

Cancel

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

Apply

The Apply button sends the entered configuration data to the Cisco 6100 and leaves the dialog open. It also leaves the information just entered in the dialog so it can be changed.

When the APPLY buttons is selected, ViewRunner for Windows sends SNMP sets in a specific sequence to assure the configurations take affect immediately in the Cisco 6100.

If the APPLY button is selected while the Administrative state is Unlocked, ViewRunner for Windows allows the non-service affecting information to be modified.

If the APPLY button is selected while the on screen Administrative state configuration is Locked, ViewRunner for Windows will lock the resource and send all configuration information that has been modified.

Button	Description
OK	The OK button applies configuration data in the property dialog and then closes the dialog. When the OK buttons is selected, ViewRunner for Windows sends SNMP sets in a specific sequence to assure the configurations take affect immediately in the Cisco 6100. If the OK button is selected while the Administrative state is Unlocked, ViewRunner for Windows allows the non-service affecting information to be modified. If the OK button is selected while the Administrative state is Locked, ViewRunner for Windows will lock the resource and send all configuration information that has been modified.
Cancel	The Cancel button closes the window without applying configuration data. It discards any changes made without requesting user confirmation.
Apply	The Apply button sends the entered configuration data to the Cisco 6100 and leaves the dialog open. It also leaves the information just entered in the dialog so it can be changed. When the APPLY buttons is selected, ViewRunner for Windows sends SNMP sets in a specific sequence to assure the configurations take affect immediately in the Cisco 6100. If the APPLY button is selected while the Administrative state is Unlocked, ViewRunner for Windows allows the non-service affecting information to be modified. If the APPLY button is selected while the on screen Administrative state configuration is Locked, ViewRunner for Windows will lock the resource and send all configuration information that has been modified.

1.5 Message Dialogs

Message dialogs of various types display as necessary to communicate particular instructions to you. These message dialogs are in addition to the event/alarm traps that are sent to one or more recipients. See Section 6.3. for more information about traps and the "Event History and Current Alarms," for more information on events and alarms.

Two types of message dialogs are supported: confirmation and error.

1.5.1 Confirmation Dialogs

Confirmation dialogs alert you of the consequences of carrying out a requested action, request a response, and interrupt normal interaction with the ViewRunner for Windows application until the dialog is closed. Confirmation dialogs 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 dialog text appears:

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

The message appears to inform you about the delete action. In some instances, a confirmation message warns of the general consequences of proceeding. If the entity or any of its subordinates is involved in an active ADSL connection, a confirmation dialog is always presented indicating that the active connection(s) will be terminated if the action is not aborted.

The following actions result in confirmation dialogs appearing:

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

1.5.2 Error Information Dialogs

Error dialogs convey a message about a user error and detail the cause of the error. Error dialogs pop up when application, communication, or Cisco 6100 interaction errors occur. You must acknowledge that the error occurred to close the error dialog.

Error information dialogs appear if you leave a field required for configuration blank.

1.5.3 SNMP Message or Error Dialogs

The ViewRunner Log Window pops up to the foreground whenever a SNMP message or error is posted. The ViewRunner Log Window contains informational messages that describe a history of what has taken place since the program was loaded. Most important, it displays SNMP error messages as they occur. Some SNMP error messages are expected during normal operation. These include SNMP Timeout messages, which typically do not indicate a serious error unless they are persistent. The messages include:

ViewRunner may not be able to discover a Cisco 6100 if the wrong IP address is entered or if communication is not possible. In these situations, the following error message displays:

10/08/97 15:09:55 Error on HostGetSysDescr - SNMP++: SNMP request timed out 
Discovery of Cisco 6100 at XXX.XXX.XXX.XXX failed

Discovery of Cisco 6100 at XXX.XXX.XXX.XXX failed

Solution: Make sure the Cisco 6100 can be pinged. Correct the communication problem.

A time out message returned from SNMP++ means there was a problem communicating with the agent. It may also indicate a serious problem such as an SC not responding, or it may indicate a less serious problem such as high network traffic or a communications error. This message looks like this:

10/08/97 15:09:55 Error on HostBoardGetAdminStatus - SNMP++: SNMP request timed out

10/08/97 15:09:55 Error on HostEventGetFirstDescription- SNMP++: SNMP request timed out		Oid=1.3.6.1.4.1.1871.2.1.1.1.1.1.3.1.1.1.2.0

Solution: Make sure the Cisco 6100 can be pinged. Correct the communication problem. If the problem is transient, it was likely a network problem that has been corrected.

Another error may be seen in this release, but not in future releases. This error indicates that the user attempted to configure a network VPI/VCI combination that is invalid or already in use. This message looks like this:

"10/08/97 15:09:55 ***SNMP error on HostSubscriberAddPvc - SNMP++: Agent indicates error in SNMP request. PDU Error status - SNMP: Cannot perform operation, General Error
Oid=1.3.6.1.4.1.1871.2.1.1.1.1.1.2.1.5.1.2.12.3"

Solution: Specify a Network side VPI/VCI that is not in use.

Any messages other than those listed above might indicate an internal error with the Cisco 6100 or ViewRunner for Windows software and should be reported to Cisco TAC.

Note Before reporting any problems discovered via the Log Window, please rename and save VRLOG.TXT. Then retrace your steps to just before the error message occurred. Also, please note the exact error message that appeared in the Log Window. Report both of these when you contact Cisco TAC.

1.6 Cisco 6100 and ViewRunner Management Tools

There are four tools that can be used to manage the Cisco 6100 and ViewRunner for Windows:

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

1.6.1 Configuration Save and Restore

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

Saving the configuration of older Cisco 6100 systems running software version 1.02 or earlier will reset the system, causing a very temporary loss of service. All active connections will be re-established within a few seconds. Saving the configuration of Cisco 6100 systems running SC version 2.1 or later does not result in a loss of service.

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.

1.6.2 Software Update Download

System software download is the method by which a Cisco 6100 can upgrade the software in each of the modules that support downloading to the module. The software download procedure requires an TFTP server. ViewRunner functions as an TFTP server and will be capable of handling requests for images from a Cisco 6100. However, ViewRunner also will allow the user 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 SC reset. As a fail-safe measure, prior to initiating a system reset, the user should use the configuration save and restore wizard (see the "Configuration Save and Restore,") to store the current NVRAM configuration for later retrieval should something go wrong with software download.

Software download restores the subtend details of the node being updated to preserve the connections. However, you have the option not to restore subtend information node should you wish not to restore subtend information.

1.6.3 Summary Dialog Save to File

The contents of certain lists of data may be output to an ASCII text file by the user. NotePad is automatically launched to display this file. The user can modify the file, save it, or print it.

The following are the summary dialogs which can be saved to file. A Save button in the dialog box on the first six dialogs, and a Save button on the toolbar of the last two starts the save process.

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

This feature is designed to save a customized (filtered and/or sorted) view of the summary dialog contents into an ASCII text file. When the Save button is selected, a configuration dialog displays allowing the user to control how the output file is formatted. Initially, all column headings from the summary dialog are displayed in a list.

The user can delete headings whose corresponding columns are not to be included in the output file. The columns can be reordered by moving the headings up or down within the list using the buttons to the right of the headings list. The columns will print left to right in the order that their headings appear in the list (top to bottom). A reset button throws away any layout changes.

Figure 1-21: Save List Options

The user can select how to separate columns by selecting one of three choices:

1. Blank fill - This option pads the contents of a column with blanks until a predefined width is reached. This option works well for display or printing using fixed-width fonts.

2. Comma - Separates each field with a comma. This selection works well for import into spreadsheet applications.

3. Tab - Separates each field with a tab. This format works well for import into either spreadsheet or word processing applications.

ViewRunner saves the data to a predefined file and automatically launches NotePad with this file when you want to view it.

1.6.4 Command Line Interface (CLI)

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

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

Command Line Input Interface

The following are the input criteria for using the CLI:

The serial interface requires a DB9 male connector attached to the SC'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 will refresh and redraw the CLI screen.
The default telnet port number to connect to the CLI is 7000. So to connect to the SC, specify 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 (verb) and is followed by one or more arguments or no arguments.
Each argument is separated by one space.
Commands and arguments are not case sensitive.
Up arrow displays the last command entered on prompt (history).
The history command is can be edited for rapid command syntax modification.
An invalid command entry lists all the valid commands supported.

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 will scroll up to 20 lines and then wait for user's acknowledgment.
(for example, Press any key to proceed).

Error output

The following errors will be displayed for invalid commands:

too many arguments passed

When too many arguments are entered.

no response from Cisco 6100

If CLI could not get response from either the management interface manager (MIM) or the fault manager (FM).

invalid argument n

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

invalid first object instance

When the instance specified for first object is invalid.

invalid second object instance

When the instance specified for second object is invalid.

too many arguments passed	When too many arguments are entered.
no response from Cisco 6100	If CLI could not get response from either the management interface manager (MIM) or the fault manager (FM).
invalid argument n	When argument n is invalid (where n is a number between 1 and 5).
invalid first object instance	When the instance specified for first object is invalid.
invalid second object instance	When the instance specified for second object is invalid.

Command Syntax

The following is the command syntax for CLI commands:

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

where

verb

is the action/command need to be executed. Valid verbs are:

help
?
show

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

noun_1

specifies the object on which command need 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 3 unique characters/words. More than one adjective_1 can modify a noun_1, each separated by a period. In the following example, maj.crit are two adjective_1s:

> 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 an alarm severity to be displayed, the system will display all alarms.

noun_2

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

> show alarms crit chas

Valid noun_2 objects are:

sys
chas
slot
sc
ni
atuc
lim
lcm
shm
lp
mp

Cisco 6100 system
Cisco 6100 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 managed object. Object instances vary with the type of objects.

The entry takes the form of

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

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

c
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-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 Cisco 6100 multiplexer chassis (which is always chassis instance number 0) at slot 12:

> show alarms crit.maj atuc m.0.12.2

options

to activate certain type of operation, i.e. filter. More than one option can be specified at one time, each separated by a period. Options are sensitive up to the first 3 characters; the rest will be ignored.

1.6.5 Inband Management Channel

Using the inband management channel feature of the ViewRunner for Windows allows direct control/management of the Cisco 6100 through the ATM channel. The inband management channel is transparent to ViewRunner in that provisioning and operation of the system are identical whether through the Ethernet port or the inband channel. The only difference is that instead of using conventional Ethernet physical media to communicate to the Cisco 6100, ViewRunner will use ATM as the physical layer for communication.

ViewRunner for Windows supports software downloads and restores for Cisco 6100 nodes being managed via the inband management channel or the ethernet management channel. The menu option allowing this feature is active only if the SC supports the feature and the node is being managed through one of the management channels. Warnings will be issued if software download / restore is not supported by the SC.

To run IP over ATM, the system uses RCF 1483 "Multi-protocol over AAL5" in Logical Link Control (LLC) encapsulation mode. This encapsulation will allow transporting via multiple protocols over a single VC.

To make sure the out-bound packets from the Cisco 6100 are sent to the right interface (Ethernet or inband), a routing table for various IP addresses is also supported. This table is only needed when you use the inband management channel. Ethernet takes care of its own routing. See the "System Level Configuration," for more information on the inband management channel.

verb	is the action/command need to be executed. Valid verbs are:
	help ? show	lists all possible commands lists all possible commands retrieves and displays data on screen
noun_1	specifies the object on which command need 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 3 unique characters/words. More than one adjective_1 can modify a noun_1, each separated by a period. In the following example, maj.crit are two adjective_1s: `>` 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 an alarm severity to be displayed, the system will display all alarms.
noun_2	specifies the object on which the command is to be executed. This is generally a managed object of the Cisco 6100 system. The following command would return all critical alarms for all the chassis (MC and LCCs) for that Cisco 6100 system. `>` show alarms crit chas Valid noun_2 objects are:
	sys chas slot sc ni atuc lim lcm shm lp mp	Cisco 6100 system Cisco 6100 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 managed object. Object instances vary with the type of objects. The entry takes the form of > show alarms [crit \| maj \| min] [noun_2] [c].[i].[s].[p] where c, i, s, and p indicate the following values:
	c 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-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 Cisco 6100 multiplexer chassis (which is always chassis instance number 0) at slot 12: `>` show alarms crit.maj atuc m.0.12.2
options	to activate certain type of operation, i.e. filter. More than one option can be specified at one time, each separated by a period. Options are sensitive up to the first 3 characters; the rest will be ignored.

Table of Contents

ViewRunner for Windows Overview