|
|
This chapter provides the instructions for installing the ViewRunner for Windows software and for understanding the system files provided by ViewRunner.
To connect your PC to the Cisco 6100 use the following steps:
Step 1 Turn OFF your PC.
Step 2 Connect the PC to the Ethernet RJ-45 adapter on the multiplexer backplane.
Step 3 Power ON the PC.
Step 4 Power ON the Cisco 6100.
Once the PC is connected to the Cisco 6100, follow the steps described in the following sections to install the ViewRunner for Windows software.
To install ViewRunner for Windows from a diskette, use the following steps.
Step 1 Insert the ViewRunner for Windows program disk 1 into your disk drive.
Step 2 Access your disk drive icon and double-click on setup.exe.
Step 3 Follow the installation wizard prompts to begin copying the ViewRunner for Windows files. Once the copying completes, the ViewRunner for Windows icon appears in a new program group and on the desktop.
Step 4 Start ViewRunner for Windows by double-clicking on the ViewRunner for Windows icon.
By default, the wizard installs the system files in c:\Program Files\Cisco\ViewRunner 2.3.5 (or the latest release number).
If you choose not to use the install wizard to install ViewRunner for Windows, you can simply copy all the files from the disks or from another folder into a folder on your hard drive.
Cisco recommends that you use the default location c:\Program Files\Cisco\ViewRunner 2.3.5 (or the latest release number) as the folder in which you copy ViewRunner for Windows.
To run ViewRunner or Windows, double-click on ViewRunner.exe.
You can also download the latest ViewRunner for Windows software and Cisco 6100 images from CCO using the procedures below.
Step 1 Go to the Cisco site at www.cisco.com
Step 2 Go to the "Service and Support" section.
Step 3 Click the "Software Center" link.
Step 4 Click the "Login" link at the top of the page.
Step 5 Enter your Cisco user name and password.
Step 6 Click the"Network Management Products" link.
Step 7 Click the "Cisco ViewRunner Software" link
Step 8 Click the "vr4w235.exe" link.
Step 9 The Software Download page opens and displays:
Step 10 Click on your chosen server protocol link.
Step 11 A system window opens, allowing you to browse to the folder where you wish to install the ViewRunner 2.3.5 application.
Step 12 After you select and open a folder, ViewRunner installs to that location.
The ViewRunner maintains several system files that reside in the same folder launching ViewRunner for Windows. These system files include:
The ViewRunner maintains a release definition file (RDF) which identifies the software that is compatible with each hardware module/revision for a given system release. The system controller (SC) and the ViewRunner use this file to check release compatibilities for 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:
6000-230-09A,Development Release 2.3.0.9 ******************************************************************************* Hardware Revision Table ******************************************************************************* Begin 2651-003,5651-227-19,"SC" 2601-014,5601-215-19,"OC-3 NI SMF" 2601-015,5601-215-19,"OC-3 NI MMF" 2601-016,5601-215-19,"DS3 NI" 2601-012,5601-215-19,"Subtending DS3 NI" 2601-021,5601-215-19,"Subtending DS3 NI FPGA mod" 2601-020,5601-215-19,"Subtending OC-3 NI MMF FPGA mod" 2601-019,5601-215-19,"Subtending OC-3 NI SMF FPGA mod" 2601-022,5601-215-19,"OC3 SM NIM Temperature Hardened" 2601-023,5601-215-19,"OC3 MM NIM Temperature Hardened" 2601-024,5601-215-19,"DS3 NIM Temperature Hardened" 2101-003,5101-203-01,"Dual ATU-C CAP Direct Connect" 2101-004,5101-203-01,"Dual ATU-C CAP DOH" 2101-005,5101-203-01,"Dual ATU-C CAP DOH" 2102-002,5102-203-05,"Dual ATU-C DMT Issue 1 Direct Connect" 2102-003,5102-203-05,"Dual ATU-C DMT Issue 1 Direct Connect" 2651-004,5651-002-11,"LCM" 2601-017,5612-071-01,"SHM" End ******************************************************************************* Image Table ******************************************************************************* Begin 5651-227-19,sc2.27.1.9.ima,864880,3513080176,"SC" 5601-215-19,ni2.15.1.9.ima,580192,648112810,"NI" 5101-203-01,cap2.3.0.2.ima,237520,1697389940,"ATUC" 5102-203-05,dmt2.3.0.5.ima,237520,3179656967,"ATUC" 5651-002-11,lcmR2.2.5.ima,237520,163741187,"LCM" 5612-071-01,shm2.7.1.1.ima,391392,3001303266,"SHM" End
Another 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 (LCM) will not support the newer feature that allows the Administrative state to lock all entities before deleting a chassis. Therefore, the ViewRunner consults the FCM file to determine that it should disable the Delete Chassis option if the user does not lock the module.
ViewRunner reads the FCM file to determine what features are supported in a given SC software release and customizes the features presented to the user when connected to that 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 6100 containing an SC software version not found in the FCM file.
In these cases, ViewRunner will present the latest default feature set to the user. An updated FCM is available at Cisco Connection Online (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. It 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 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 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 softwareversion 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.netspeed.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 Stunned 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 Settable parameters for 136K baud enable/disable and Non-Timer CPE train enable/disable
ViewRunner for Windows supports a 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 intended use of the file is to troubleshoot problems with ViewRunner and the Cisco 6100.
The following events and information are logged in VRLOG.TXT
The VRLOG.TXT file will not grow larger than two MBs. At two MBs, it truncates to zero and starts over. The information in VRLOG.TXT is presented in a format similar to the following:
03/01/99 15:04:33 Error on HostGetSysUpTime - SNMP++: SNMP request timed out
(Mar 01, 1999 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 (Mar 02, 1999
15:56:10)
HostGetSystemConnectMode failed. SC code does not support Direct Connect (Mar 02,
1999 15:56:15)
ViewRunner exited (Mar 02, 1999 15:57:29)
ViewRunner started (EXE-200:0, DLL- 200:0) (Mar 02, 1999 18:56:33)
Discovering 'vrdemo,172.16.1.236' & setting SNMP_TIMEOUT_DELAY to 1000 (Mar 02, 1999
18:56:47)
HostGetSystemConnectMode failed. SC code does not support Direct Connect (Mar 02,
1999 18:56:51)
ViewRunner exited (Mar 02, 1999 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.
Posted: Mon Oct 11 22:30:46 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.