|
|
This chapter describes the ViewRunner for Windows program, system files, navigational system, system dialog boxes, and management tools. The chapter contains the following sections:
ViewRunner for Windows is the graphical user interface application that lets you configure your Cisco 6100 Series system and manage Cisco 6100 Series nodes. ViewRunner for Windows supports the discovery of Cisco 6100 Series equipment. That is, once you have installed ViewRunner for Windows and connected it to your Cisco 6100 Series system, ViewRunner for Windows retrieves configuration data from the Cisco 6100 Series SNMP agent. It then displays a graphical representation of your Cisco 6100 Series system like the one shown in Figure 1-1.
The ViewRunner for Windows main menu supports three primary views:
ViewRunner for Windows Release 2.4.0 is bundled with the Cisco 6100 Series multiplexer chassis (MC), or it can be downloaded from Cisco Connection Online (CCO).
Table 1-1 summarizes the compatibility among Cisco 6100 Series system and ViewRunner for Windows releases.
| Cisco 6100 Series System Release | ||||||||
|---|---|---|---|---|---|---|---|---|
| 2.4.0 | 2.3.1 | 2.3.0 | 2.2.1/ 2.2.5 | 2.2.0 | 2.1.3 | 2.1.2 | ||
| Cisco 61301 | Cisco 61002 | |||||||
| ViewRunner for Windows Release |
|
|
|
|
|
|
|
|
2.4.0 | Yes | Yes | No | No | Yes | Yes | Yes | Yes |
2.3.5 | No | No | Yes | Yes | Yes | Yes | Yes | Yes |
2.3.0 | No | No | Yes3 | Yes3 | Yes4 | Yes | Yes | Yes |
2.2.1 | No | Yes | Yes5 | Yes5 | Yes5 | Yes | Yes | Yes |
2.2.0 | No | Yes | Yes5 | Yes5 | Yes5 | Yes | Yes5 | Yes |
2.1.0 | No | Yes | Yes6 | Yes6 | Yes6 | Yes6 | Yes6 | Yes |
The Chassis View provides the top-level user interface for the management of a single Cisco 6100 Series system.
There are three types of chassis in the Cisco 6100 Series system. The first two chassis can be managed through ViewRunner for Windows:
The Chassis View shown in Figure 1-1 provides menu bar operations and a bit-map front panel view of the Cisco 6100 Series system that displays the color-coded status of configured modules.
The Chassis View displays the MC and each Cisco LCC. 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 for Windows 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 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. Table 1-2 lists the colors according to the highest priority color (displays first) and the lowest priority color (displays last), in cases where more than one of the conditions described below is met. See "Cisco 6100 Series System and ViewRunner State Management," for more information on states and see the Cisco 6100 Series Alarm Summary Guide for detailed information on alarms.
| Ejector Tab Color (in order of priority) | State or Alarm Type | Description |
|---|---|---|
Red | A critical alarm is the most severe alarm present on the module or any of its ports. | |
Orange | A major alarm is the most severe alarm present on the module or any of its ports. | |
Yellow | A minor alarm is the most severe alarm present on the module or any of its ports. | |
Blue | 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 SC1 module has not communicated with it since power up. | |
Brown | Either the module is configured with the Administrative state of Locked, or all of the module's ports are configured with the Administrative state of Locked. | |
Green | The module and all of its ports are in a Normal state. |
| 1SC = system controller |
The ejector tab colors are updated when you
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 Series system. There are eight types of modules:
You should have some basic knowledge of the logical entities of the Cisco 6100 Series system. Those logical entities are as follows:
For descriptions of the modules listed above, refer to the Cisco 6100 Series User Guide.
The ViewRunner maintains several system files that reside in the same folder from which ViewRunner for Windows is launched. These key system files include
In addition to these files, there is a readme file explaining how to install the ViewRunner software.
The ViewRunner maintains a Release Definition file (RDF), that 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" section for more information about software
update downloads.
The RDF is named 9000-xxx-xx.RDF, where "9000-xxx-xx" is the latest release of the system. The file is stored in the ViewRunner system folder and contains information about the software and hardware release of the Cisco 6100 Series components. The information in each RDF looks like this:
9000-XXX-XXX,Release 2.3*******************************************************************************Hardware Revision Table*******************************************************************************Begin2651-003,1651-119-99,SMF"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*******************************************************************************Begin1651-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
Another key system file is the SC Feature Compatibility Matrix (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 you.
ViewRunner reads the FCM file to determine what features are supported in a given SC
software release and customizes the features presented 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 a new Cisco 6100 Series IP address is discovered if that node's SC software is not recognized. ViewRunner opens the Feature Compatibility Error dialog box (Figure 1-2) when you connect to a Cisco 6100 Series system containing an SC software version not found in the
FCM file.
In the event that a software upgrade fails, you can check the list of compatible hardware releases in the release definition file (RDF). The file is stored in the ViewRunner system folder and contains information about the software and hardware release of the Cisco 6100 Series components.
 | Caution Open the RDF using Windows Notepad only. Notepad provides a pure text display without hidden characters. Do not alter the RDF file. Altering the RDF will corrupt your ViewRunner for Windows application. |
In a case in which the SC 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 might eliminate this warning. However, this message typically means that a newer ViewRunner version should be available.
The FCM filename is SCFeatureCompatibilityMatrix.csv. It is maintained as an Excel spreadsheet and output as a comma-separated text file. Information in the matrix file is similar to the following.
SC Software Version,DirectConnect,SWDownload,LIMCSetAdminState,SCSetAdminState,SCMaintState,MIBIndexFix,MIBClearNVRAM,PreprovisionDirectATUC,Subtending,MarginAttenuation,Chassis Id Fix,LR Inband Mgmt Channel,Multiple Trap Recipients,Subscriber Idle Disconnect,136KB Subscriber Rates,ATU-C Parms,,,BEGIN,,,,,,,,,,,,,,,,,,,9651-001-07,,,,,,,,,,,,,,,,,,,9651-001-09,,,,,,,,,,,,,,,,,,,9651-001-12,DIRECT,,,,,,,,,,,,,,,,,,9651-001-13,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,9651-001-15,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,9651-001-20,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,,,,9651-001-21,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX9651-001-22,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS9651-001-23,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS9651-001-24,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS9651-001-25,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS9651-001-26,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMSdefault,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS,,,END,,,,,,,,,,,,,,,,,,,Note: All descriptions past this point are comments. These fieldsdo not get used by ViewRunner. Cisco-Austin updates the FeatureCapability Matrix file whenever a new SC software version is released.If a user connects ViewRunner to a node that "contains an SC softwareversion that is not recognized, a warning dialog will notify" theuser to obtain a newer version of the file. The SCFeatureCapabilityMatrix.csvfile should be downloaded and saved into the directory whereViewRunner is installed. If the updated file does not allow"ViewRunner to manage this node, then contact Customer Supportdirectly."BEGIN,,,,,,,,,,,,,,,,,,,System Part #,LoopRunner Rel,Contains SC SW,,,,9000-001-03,1.02 release,9651-001-07,,,,9000-001-04,1.02A release,9651-001-09,,,,9000-001-06,1.02C release,9651-001-12,,,,9000-001-07,2.0 release,9651-001-13,,,,9000-001-09,2.1.0 release,9651-001-15,,,,9000-001-10,2.1.1 release,9651-001-15,,,,9000-001-11,2.1.2 release,9651-001-15,,,,9000-001-12,2.2.0 release,9651-001-20,,,,9000-001-13, 2.1.3 release, 9651-001-21,,,,9000-001-12, 2.2.0 release, 9651-001-20,,,,9000-001-14, 2.2.1 release, 9651-001-22,,,,9000-001-15, 2.2.0.101 release, 9651-001-23,,,,9000-001-16, 2.2.5.100 release, 9651-001-24,,,,9000-001-18, 2.2.0.102 release, 9651-001-25,,,,9000-001-19, 2.2.0.103 release, 9651-001-25,,,,9000-001-20, 2.2.5.102 release, 9651-001-26,,,,9000-001-21, 2.2.5.103 release, 9651-001-26,,,,END,,,,,,,,,,,,,,,,,,,Feature Description,,,,,,DIRECT,LoopRunner supports Direct Connect Mode (Subscribersassociated directly to ATU-Cs. No LIMs) ,,,,,,,,,,SWDLD,"LoopRunner supports system software upgrading viaimage TFTP to node. This includes several MIB additions(HW table, Image table, etc)",,,,,,,,,,LCSACMIN,"LIM Controller Supports Configurable Admin State.If this feature is supported, VR should dim the LIMChassis Deletion menu options unless Admin State isLocked.",,,,,,,,,,SCSACMIN,SC Supports Configurable Administrative State.,,,,,,,,,,SCMAINT,SC Supports Configurable Maintenance State.,,,,,,,,,,MIFIX,"PR 285 - MIB indexes may now be specified during Rowcreation. Among other things, this eliminates requirementfor SC Reset prior to saving NVRAM configuration",,,,,,,,,,MICNVRAM,PR 1211 - MIB Supports Clearing NVRAM,,,,,,,,,,PPDATUC,PR 1340 - LoopRunner supports pre-provisioning ofATU-C modules in direct mode.,,,,,,,,,,SUBTEND,"LoopRunner supports Subtend Feature (Subtend hostmodule, Transit subscribers)",,,,,,,,,,MARGINATTEN,Support for setting ADSL margin and attenuationvalues on a per subscriber basis,,,,,,,,,,INBANDCH,Support for LoopRunner inband management channel andassociated Routing Table support,,,,,,,,,,TRAPRCVRS,Support for multiple trap recipients,,,,,,,,,,SUBSCRTIMEOUT,"Supports lrSubscrTimerType, lrSubscrTimerValuewhich defines if and when a subscriber is disconnectedafter a specified idle or session timout.",,,,,,,,,,LCCIDFIX,Supports pre-provisioning full range of ChassisIds (0-15),,,,,,,,,,BITRATES136KB,New physical layer rate combinations supportedby 136KB firmware (42 new bitrate combinations),,,,,,,,,,ATUCPARMS,ATUC Settable parameters for 136K baud enable/disableand Non-Timer CPE train enable/disable,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
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 Series system.
Events and information are logged in vrlog.txt when
The vrlog.txt file does not grow larger than 2 MB. At 2 MB, it returns to 0 and starts over. The information in vrlog.txt is presented in a format like this:
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, 199815: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, 199818: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 (Figure 1-3) contains the
current messages logged to vrlog.txt. These are only those error messages encountered during the current session.
ViewRunner for Windows supports three navigation methods:
These navigational methods are explained in the next three sections.
The primary means for retrieving information about a particular module or chassis are the left
and right mouse buttons. You can use either button to display properties about a particular module or chassis.
Double-clicking with the left mouse button opens the properties of the module directly beneath the cursor when the left button is selected. You can also use the right button of the mouse to display the menu listing module options. Menus are also context sensitive according to the chassis or slot that is beneath the cursor when the right button is selected.
Whether you choose to right- or left-click, placing the cursor over the chassis but outside of the slots and left-clicking selects the chassis. 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 menus show the options that appear when you right-click a particular entity.
Multiple options display when you right-click the Cisco 6100 Series MC in Chassis View. Figure 1-4 shows these options and their subsequent menus.
Table 1-3 lists the chassis menu options shown above and describes their functions.
| Menu Item | Description |
|---|---|
Gives you direct access to the Status or Configuration tabs for the Cisco 6100 Series system. | |
Displays the properties of physical and logical pools. | |
Opens the Active Connections view, displaying a list of the | |
Displays a comprehensive list of all subscribers currently | |
Displays a list of current PVCs and the subscribers associated with | |
Displays a list of all discovered modules and chassis. | |
Displays performance statistics for the Cisco 6100 Series system. | |
Displays the port configuration for Direct Connect configurations only. Therefore, it is dimmed here. | |
Allows management of the Cisco 6100 Series system through IP over ATM rather than through Ethernet. | |
Allows the setting of multiple IP addresses to receive traps of specific severity and above (or none at all). | |
Allows you to set specific routing for communication through the in-band management channel. | |
Opens the Events History View dialog box, which displays all events pertaining to the Cisco 6100 Series system. See the Cisco 6100 Series Alarm Summary Guide for more details. | |
Opens the Current Alarms View dialog box showing all alarms currently asserted in the system. | |
Initiates the sequence of SNMP messages required to rediscover Cisco 6100 Series equipment (chassis and modules) configured in | |
Retrieves current state and alarm information from the Cisco 6100 Series system and uses it to refresh the colors on each module's ejector tabs. | |
ViewRunner for Windows does not support this option in this release. Therefore, it is dimmed. |
The following options are displayed when you right-click the Cisco LCC. Figure 1-5 shows the two options available on the LCC menu.
Table 1-4 details the functions of the LCC menu options.
| Menu Item | Description |
|---|---|
Displays chassis properties such as backplane information. | |
Deletes the LCC |
The Module Properties and Port Properties menu items have two subitems that take you directly to the Status tab or Configuration tab for the module. The number of port items displayed in the module's menu is determined by the type of module selected. For example, the SC has no port items, the LIM and the STU-C have four port items, and the CAP ATU-C and the DMT-2 ATU-C module menus each have two port items.
Figure 1-6 shows the various menus that display when you right-click a CAP ATU-C module.
Figure 1-7 shows an example of the menus you see when you right-click a LIM.
Table 1-5 provides descriptions of each CAP ATU-C, DMT-2 ATU-C, STU-C and LIM module menu item.
| Menu Item | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration dialog box for a particular module. |
Port Properties | Gives you direct access to the Status or Configuration dialog box for a particular port. |
Deletes the specified module from the Cisco 6100 Series system. This option is dimmed unless the you lock an entity according to the rules specified in "Cisco 6100 Series System and ViewRunner State Management." 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 a chassis itself. |
Figure 1-8 displays the menu that appears when you right-click the SC.
Table 1-5 explains the functions of the SC menu options.
| Menu Items | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration dialog box for a particular module. |
Delete Module | Deletes the module. This option is dimmed unless the you lock an entity according to the rules specified in "Cisco 6100 Series System and ViewRunner State Management." This option is always dimmed for users with user-only privileges. |
6100 Properties | Displays the options available for the Cisco 6100 Series system, such as system date and time. |
Figure 1-9 shows the various menus displayed when you right-click the LIM controller. Table 1-7 describes these menu items.
| Menu Item | Description |
|---|---|
Module Properties | Gives you direct access to the Status or Configuration dialog box for a |
Delete Module | Deletes the LIM controller. This option is dimmed unless you lock an entity according to the rules specified in "Cisco 6100 Series System and ViewRunner State Management." 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. |
Allows you to reset the LIM controller. |
Figure 1-10 shows the menu that appears when you right-click an empty MC slot.
Table 1-8 describes each MC slot menu item and its function.
| Menu Item | Description |
|---|---|
Inserts a new module. Note This option is not supported in this release. | |
6100 Properties | Provides direct access to Cisco 6100 Series properties, such as system date and time. The Delete Chassis option is dimmed unless the you lock an entity according to the rules specified in "Cisco 6100 Series System and ViewRunner State Management." This option is always dimmed for users with user-only privileges. |
The menu in Figure 1-11 appears when you right-click an empty LCC slot.
Table 1-9 below provides descriptions of the empty LCC menu items.
| Menu Item | Description |
|---|---|
Insert Module | Inserts a new module. Note This option is not supported in this release. |
Chassis | Provides direct access to the Cisco LCC backplane revision information. The Delete Chassis option is dimmed unless you lock an entity according to the rules specified in "Cisco 6100 Series System and ViewRunner State Management." This option is always dimmed for users with user-only privileges. |
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 appears in Figure 1-12.
Table 1-10 describes the fields and icons used in the ViewRunner toolbar.
| Toolbar Field/Icon | Field or Icon Description |
|---|---|
|
| You can select this option from the toolbar Option menu. 6100 Addresses displays a drop-down list of IP addresses added to ViewRunner for Windows. Each IP address corresponds to a Cisco 6100 Series system. This option allows you to go back and forth easily between various Cisco 6100 Series systems. |
You can select this option from the toolbar View menu. Displays all events set for a Cisco 6100 Series system in the current Chassis View. | |
You can select this option from the toolbar View menu. Displays the Chassis View of the last discovered Cisco 6100 | |
You can select this option from the toolbar View menu. Displays all current alarms for the Cisco 6100 Series system at the time the dialog box is opened. The dialog box must be refreshed for old alarms to be cleared or new ones to be logged. |
The Chassis View Toolbar in Figure 1-13 appears directly under the ViewRunner toolbar.
The icons on the Chassis View toolbar in Figure 1-13 are described in Table 1-11.
| Chassis View Toolbar Icon | Icon Description |
|---|---|
This is two red arrows moving in a circle in the upper left-hand corner of a dialog box. This icon rediscovers a Cisco 6100 Series system and provides the most current view of ejector tab colors. | |
This is a small letter z. This icon shrinks the Cisco 6100 Series | |
This is a large letter Z. This icon enlarges the Cisco 6100 Series Chassis View until it is the size of the window. Then the icon becomes dimmed. |
As a third means of navigation, the menu hierarchy in ViewRunner for Windows consists of drop-down menus and their options.
Menu bar options allow you to view or modify the configuration, alarm, performance, and status details of Cisco 6100 Series components. The menu bar also lets you add and delete the LCC and modules.
Figure 1-14 shows all the main ViewRunner toolbar menu possibilities.
You can access each of these options by left-clicking the menu and selecting from among the options.
ViewRunner for Windows supports a logical service-oriented navigation, which allows rapid navigation to a module, port, or Subscriber Property dialog box from the summary dialog boxes.
Logical service-oriented navigation eliminates the need to bring up the craft-oriented Chassis View and click the physical position of the entity to be provisioned. Logical service-oriented navigation eliminates the need to use the physical navigation to the entity using the Chassis View. You can still double-click an entity in the Chassis View and access the property dialog boxes necessary to provision services.
The summary dialog boxes from which you can use the logical service hyperlinks include
For the dialog boxes that support the logical service-oriented navigation feature, the access identifier (AID) text displays as underlined, blue text, indicating that it is a hyperlink to the corresponding property dialog box. Single-clicking any underlined hyperlink takes you to the property dialog box associated with the selected entity. The cursor changes to a hand pointer when moved over one of the hyperlinks. For example, clicking the Subscriber ID link in the View All Subscribers dialog box opens the Subscriber Properties dialog box for the selected subscriber. The dialog box is the same as the one from the Port Configuration dialog box. The selected subscriber can be edited or deleted from this dialog box.
Clicking the Service Provisioning button will open the Service Provisioning dialog box, where you can add or delete permanent virtual circuits (PVCs). When the dialog box is dismissed, the View All Subscribers dialog box is updated with the new configuration.
Figure 1-15 shows an example of a View All Subscribers dialog box.
Figure 1-16 shows an Event History View dialog box with underlined hyperlinks.
When you access any Cisco 6100 Series component, there are similarities among the different dialog boxes that appear. These similarities are discussed in the following sections.
The properties dialog boxes for all chassis and modules in the Cisco 6100 Series Chassis View are similar to each other. To display the properties of a particular chassis or module, right-click a chassis or module and select the Properties option. This opens a Cisco 6100 Series chassis or module property dialog box respectively. The dialog box contains similar features, including a two-tiered tab design, overlaying a second, higher level set of tabs outside the basic property dialog box tabs. The outside (higher level) sets of tabs let you select between the module and any of the module's ports. The inside set of tabs provides the same functionality as the basic property dialog box tabs, allowing rapid selection between the selected module or Port Status and Configuration tabs. Use the tabs on the dialog boxes, typically the Status or Configuration tab, to access property dialog boxes for other types of logical entities, such as subscribers or pools.
ViewRunner for Windows displays attributes for an entity in tabbed dialog boxes. Each tab displays a category of information about the entity. Each tab represents a dialog box that may contain a tabbed control (for example, the module tab contains Status and Configuration tabs).
Common tab categories display, in this order: status, configuration, performance, or service provisioning. 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 views in Figure 1-17 and Figure 1-18 show the tabs common to Cisco 6100 Series components.
Table 1-12 describes the functions of CAP ATU-C, DMT-2 ATU-C, STU-C and LIM tab options.
| 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, and so forth. This tab displays options that allow you to manage the Administrative state. |
ViewRunner for Windows displays colors on module and port tabs, providing a quick indication of their Administrative and Operational state. The displayed color changes any time you:
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 in Table 1-13.
| Icon Color | State and Alarm Types | Description |
|---|---|---|
Blue | State---Unknown | For module tabs only. Indicates that the Equipage state of the module is Unfilled-Provisioned. This state is used to indicate that a module has been configured in the slot, but the SC has not communicated with it since power-up. |
Brown | State---Locked | For module or port tabs. Node reports Administrative state of Locked. |
Red | Alarm Type---Critical | For module or port tabs. A critical alarm is the most severe |
Orange | Alarm Type---Major | For module or port tabs. A major alarm is the most severe |
Yellow | Alarm Type---Minor | For module or port tabs. A minor alarm is the most severe |
Cyan | Alarm Type---Warning | For module or port tabs. A warning alarm is the most severe alarm present. Not supported in this release. |
Green | State---Normal/Up | For module or port tabs. Indicates a Normal state. |
Figure 1-19 shows the buttons common in ViewRunner for Windows.
Table 1-14 describes the ViewRunner for Windows common buttons.
| Button | Description |
|---|---|
OK | The OK button applies configuration data in the Property dialog box and then closes the When you press the OK button, ViewRunner for Windows sends SNMP sets in a specific sequence to ensure the configurations take effect immediately in the Cisco 6100 Series system. If you press the OK button while the Administrative state is Unlocked, ViewRunner for Windows allows the information that does not affect service to be modified. If you press the OK button while the Administrative state is Locked, ViewRunner for Windows locks the resource and sends all configuration information that has been modified. |
Cancel | If you press Cancel, the dialog box closes and ViewRunner does not apply configuration data. It discards any changes made without requesting user confirmation. |
Apply | If you press the Apply button, you send the entered configuration data to the Cisco 6100 Series system. This action leaves the dialog box open. The information just entered in the dialog box remains, so that it can be changed. When you press the Apply button, ViewRunner for Windows sends SNMP sets in a specific sequence, ensuring that the configurations take effect immediately in a Cisco 6100 Series system. If you press the Apply button while the Administrative state is Unlocked, ViewRunner for Windows allows the nonservice-affecting information to be modified. If you press the Apply button while the Administrative state configuration is Locked, ViewRunner for Windows will lock the resource and send all modified configuration information. |
Message dialog boxes of various types display particular instructions to you, as necessary. These message dialog boxes occur in addition to the event/alarm traps that are sent to one or more recipients. See "Event History and Current Alarms," for more information on events
and alarms.
Two types of message dialog boxes are supported: confirmation and error.
Confirmation dialog boxes alert you to the consequences of carrying out a requested action. They also request a response, and interrupt normal interaction with the ViewRunner for Windows application until the dialog box is closed. 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 dialog box text appears:
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 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 is always presented, indicating that the active connections terminate if the action is not ended.
The following actions result in confirmation dialog box displays:
Error Information dialog boxes convey various messages about user error and the cause of the error. Error Information dialog boxes pop up when application, communication, or Cisco 6100 Series system interaction errors occur. 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.
The ViewRunner Log dialog box pops up to the foreground whenever an SNMP message or error is posted. The ViewRunner Log dialog box contains informational messages that describe what has taken place since the program was loaded. More 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 the following:
10/08/97 15:09:55 Error on HostGetSysDescr - SNMP++: SNMP request timed out
Discovery of Cisco 610 at XXX.XXX.XXX.XXX failed
or
Discovery of Cisco 6100 at XXX.XXX.XXX.XXX failed
Solution: Make sure the Cisco 6100 Series system can be pinged. Correct the communication problem.
10/08/97 15:09:55 Error on HostBoardGetAdminStatus - SNMP++: SNMP request timed out
or
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 Series system can be pinged. Correct the communication problem. If the problem is transient, it was probably a network problem that has been corrected.
"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 Series system or ViewRunner for Windows software and should be reported to Cisco TAC.
Use the following five tools to manage the Cisco 6100 Series system and ViewRunner for Windows:
The configuration save and restore tool 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 the downloading of updated Cisco 6100 Series software.
See "Updating Cisco 6100 Series System Software," for more information.
Saving the configuration of older Cisco 6100 Series systems running software Version 1.02 or earlier will reset the system, causing a very temporary loss of service. All active connections will be reestablished within a few seconds. Saving the configuration of Cisco 6100 Series 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. |
System software download is the method by which a Cisco 6100 Series system can upgrade the software in each of the modules. The software download procedure requires an TFTP server. ViewRunner functions as a TFTP server and can handle requests for images from a Cisco 6100 Series system. However, ViewRunner also allows you 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, you 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 can choose not to restore the subtend information node.
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.
The following summary dialog boxes display information which can be saved to file. A Save button in the dialog box on the first six dialog boxes, and a Save button on the toolbar of the last two starts the save process.
You can use the Summary dialog box Save to File feature to save a customized (filtered or sorted) view of the summary dialog box contents into an ASCII text file. If you select the Save button, a Save List Options dialog box displays, allowing you to control how the output file is formatted. Initially, all column headings from the summary dialog box are displayed in a list.
You can delete headings whose corresponding columns are not to be included in the output file using the Save List Options dialog box. Reorder the columns by moving the headings up or down within the list. Use the buttons to the right of the headings list to reorder the columns. The columns print left to right in the order that their headings appear in the list (top to bottom). If you press the Reset button, you delete any layout changes.
Figure 1-20 shows an example of the Save List Options dialog box.
Select how to separate columns in a spreadsheet by choosing one of the options below.
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 fields with a comma. This selection works well for import of data into spreadsheet applications.
3. Tab--- Separates fields with a tab. This format works well for import of data into either spreadsheet or word processing applications.
ViewRunner saves the data to a predefined file, and, when you want to view the file, ViewRunner automatically launches NotePad with the file.
The Command Line Interface (CLI) feature enables you to retrieve fault management data from the Cisco 6100 Series system, using a Direct Connect serial interface or a Telnet session. Several users can access a single Cisco 6100 Series system simultaneously through independent Telnet sessions.
Currently, the only valid CLI commands show alarms on various managed objects.
The following are the input criteria for using the CLI:
Following are the common features for the data output formats:
Table 1-15 lists errors displayed for invalid commands
.
| Error Message | Invalid Command Description |
When too many arguments are entered | |
No response from Cisco 6100 Series system | 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) |
When the instance specified for first object is invalid | |
When the instance specified for second object is invalid |
The following is the command syntax for CLI commands.
>verb [noun_1] [adjective_1] [noun_2] [adjective_2] [options]
is the action/command to be executed. Valid verbs are | ||
| Lists all possible commands | |
noun_1 | Specifies the object on which command is to be executed. In the following example, alarms is the noun_1: Currently the only valid noun_1 is alarms. | |
Specifies the kind of noun or object. Adjective_1 is intelligent up to three unique characters/words. More than one adjective_1 can modify a noun_1. Each pair of connective terms must be separated by a period. In the following example, maj.crit is two adjective_1s: | ||
| crit | Critical 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 is generally a managed object of the Cisco 6100 Series system. The following command returns all critical alarms for all the chassis (MC and LCCs) for the Cisco 6100 Series system: | |
| sys | Cisco 6100 Series system |
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 = MC and l = LCC |
| In the following example, the command is to show all critical and major CAP ATU-C and STU-C alarms on the Cisco 6100 Series MC (which is always chassis instance number 0) at slot 12: | |
options | To activate certain types of operation, more than one option can be specified at one time, but every two consecutive options must be separated from each other by a period. Options are sensitive up to the first 3 characters; the rest are ignored. | |
Using the ViewRunner in-band management channel gives you direct control/management of the Cisco 6100 Series system through the ATM channel. Provisioning and operation of the system are identical whether through the Ethernet port or the in-band channel. The only difference is that if the in-band management channel is used, ViewRunner uses ATM as the physical layer for communication, rather than using conventional Ethernet physical media.
ViewRunner for Windows supports software downloads and restores for Cisco 6100 Series nodes. These nodes are managed through the in-band 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 are issued if the controller does not support software download/restore.
To run IP over ATM, the system uses RCF 1483, Multi-protocol over AAL5 in Logical Link Control (LLC) encapsulation mode. This encapsulation allows transporting by means of multiple protocols over a single VC.
To make sure that out-bound packets from the Cisco 6100 Series system are sent to the right interface (Ethernet or in-band), ViewRunner for Windows also supports a routing table for various IP addresses. This table is needed only if you use the in-band management channel. Ethernet takes care of its own routing. See "System Level Configuration," for more information on the in-band management channel.
Posted: Tue Oct 5 10:59:40 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.