Installing ViewRunner for Windows

2.1 Connecting the ViewRunner for Windows PC to the Cisco 6100 Series System

2.2 Installing ViewRunner Software

2.2.1 Installing Supplemental Software

2.2.1.1 Windows 95 Patches

2.2.1.2 Windows NT Installation Patch

2.2.1.3 Additional Caveats

2.2.2 Installing from Disk

2.2.3 Installing from Files

2.2.4 Downloading from the Web

2.3 Managing ViewRunner System Files

2.3.1 Release Definition File

2.3.2 Feature Compatibility Matrix File

2.3.3 Key Events Log File

Installing ViewRunner for Windows

This chapter provides the instructions for installing the ViewRunner for Windows software and for understanding the system files provided by ViewRunner.

2.1 Connecting the ViewRunner for Windows PC to the Cisco 6100 Series System

To connect your PC to the Cisco 6100 Series system,

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.

Note If your Cisco 6100 Series system is equipped with Cisco 6110 line concentration chassis (LCCs), connect an additional management cable from the Cisco 6100 Series multiplexer chassis (MC) 26-pin SCSI connector (J47) to a corresponding 26-pin SCSI connector (J29) on the LCC. Connect additional cables to each LCC.

Step 4 Power on the Cisco 6100 Series system.

2.2 Installing ViewRunner Software

After you connect the PC to the Cisco 6100 Series system, use the following sections to install the ViewRunner for Windows software.

2.2.1 Installing Supplemental Software

Before you install the ViewRunner for Windows Release 2.4.0 software, see the "Windows 95 Patches" section through the "Additional Caveats" section and install the appropriate supplemental software as required.

2.2.1.1 Windows 95 Patches

Windows 95 installation of ViewRunner for Windows Release 2.4.0 requires that you install the following patches:

1. Version 2.1---Installation of Service Pack 1or later. The download is available at: http://www.microsoft.com/windows95/downloads/

2. Version 2.2---Install the latest Winsock 2 package: W95ws2setup.exe. The download is available at: http://www.microsoft.com/windows95/downloads/contents/WURecommended/S_WUServicePacks/W95SvcPack1/Default.asp

2.2.1.2 Windows NT Installation Patch

Windows NT installation requires the following patch:

Service Pack 4 or later.

2.2.1.3 Additional Caveats

You may need to download some system DLL files before installing ViewRunner for Windows Release 2.4.0 onto a Windows 95 operating system. Additional information concerning Windows NT dual-homed systems and remote TFTP servers is also listed in this section.

1. In some versions of Windows 95, double-clicking the ViewRunner icon causes an error message to appear:

"Unable to Load OCX:MSCOMCT2.OCX. See DDTS CSCdm19617."

When you click OK the program fails to load.

If the error message above appears, the system DLL files that OCX: MSCOMCT2.OCX depends upon are not current.

Update the core OS COM files by installing the Distributed COM (DCOM) libraries.

(a) DCOM for Windows 95 or Windows 98 is available at:
http://www.microsoft.com/com/redirs/resource_fnf.asp

(b) Download Release 1.2 or later from this link:
http://www.microsoft.com/com/resources/downloads.asp

2. Windows NT dual-homed systems are not supported. If you have a dual-homed system, disable one of the network interface cards before you attempt to run ViewRunner for Windows
Release 2.4.0.

3. For remote TFTP with a UNIX server, the path for the remote TFTP server must correspond to the path configuration on the TFTP daemon.

If the TFTP daemon is configured with the "-s" which specifies the default root path, then on the VR4W remote TFTP path, enter "/"
If the TFTP daemon is not configured with the "-s" then on the VR4W remote TFTP path, enter the absolute path which points to the location of the image files, such as "/TFTPboot"

4. The Cisco 6100 and 6130 Series fan tray alarm detrains a DMT-2 module in this Release.

5. CPE timer settings must be configured correctly for a Release 2.4.0 Direct Connect session
and for idle timers. If you convert from DOH to DC in this Release, you must confirm all CPE timer settings.

2.2.2 Installing from Disk

To install ViewRunner for Windows from a disk

Step 1 Insert the ViewRunner for Windows program disk 1 into your disk drive.

Step 2 Access your disk drive icon and double-click setup.exe.

Step 3 Follow the installation wizard prompts to begin copying the ViewRunner for Windows files. After 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 the ViewRunner for Windows icon.

By default, the wizard installs the system files in
c:\Program Files\Cisco\ViewRunner 2.4.0 (or the latest release number).

Note To use ViewRunner for Windows, initialize the Cisco 6100 Series system so that it can be discovered. See "Cisco 6100 Series System Initialization," for instructions on initializing the Cisco 6100 Series system.

2.2.3 Installing from Files

If you choose not to use the install wizard to install ViewRunner for Windows, you can 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.4.0 (or the latest release number) as the folder in which you copy ViewRunner for Windows.

To run ViewRunner or Windows, double-click ViewRunner.exe

2.2.4 Downloading from the Web

You can also download the latest ViewRunner for Windows software and Cisco 6100 Series system images from CCO using the following procedures.

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. The Software Center page opens.

Step 4 Click the Login link at the top of the page. The Login dialog box opens.

Step 5 Enter your Cisco user name and password.

Step 6 Click the Network Management Products link. The Network Management Products page opens.

Step 7 Click the Cisco ViewRunner Software link. The ViewRunner Software page opens.

Step 8 Click the vr4w240.exe link.

The Software Download page opens and displays:

The file name for ViewRunner 2.4.0 software

A variety of server protocols according to location

Step 9 Click your chosen server protocol link.

Step 10 A system window opens, allowing you to browse to the folder in which you want to install the ViewRunner 2.4.0 application.

Step 11 After you select and open a folder, ViewRunner 2.4.0 installs to that location.

2.3 Managing ViewRunner System Files

The ViewRunner software maintains several system files that reside in the same folder launching ViewRunner for Windows. These system files include:

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

2.3.1 Release Definition 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.

The ViewRunner software maintains a RDF to identify the software that is compatible with each hardware module or revision for system releases. The RDF is named 9000-xxx-xx.RDF where "9000-xxx-xx" is the latest release of the system. The information in an RDF appears similar to
the following:

6000-230-09A,Development Release 2.4.0
*******************************************************************************
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

2.3.2 Feature Compatibility Matrix File

If you need to discover the node software that ViewRunner for Windows supports, open the system controller feature compatibility matrix file that accompanies the Cisco 6100 Series system. You may also access this file from the Cisco Online web site (see Downloading from the Web). The ViewRunner software reads the FCM file to determine supported features in a given SC software release and customizes the features presented to the user when the user connects to that Cisco 6100 Series system.

Caution Do not modify the SC FCM file. Doing so will degrade or corrupt node
software functionality.

The SC FCM file:

Contains feature descriptions of all releases up to and including the latest ViewRunner software.
Uses the matrix to customize the features it presents to the user based on the SC release loaded on the Cisco 6100 Series system.

For example, an earlier release of a Cisco 6100 Series LIM controller module (LCM) does not support the later feature that allows the Administrative state to lock all entities before deleting a chassis. Therefore, the ViewRunner software consults the FCM file to determine that it should disable the Delete Chassis option if the user does not lock the module.

You can manage later Cisco 6100 Series releases using the ViewRunner software without updating this file. Each time a new Cisco 6100 Series IP address is discovered an error warning appears if the SC software for that node is not recognized (Figure 2-1).

Figure 2-1: Feature Compatibility Error Dialog Box

If the SC software for the node is not recognized, ViewRunner software presents the latest default feature set to the user.

To eliminate this error warning, take one of the following actions:

Obtain an updated FCM at Cisco Connection Online (CCO).
Contact Cisco Technical Assistance Center (TAC) Center.

Obtaining a newer FCM file may eliminate this warning since this message typically means that a later ViewRunner version is 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 appears similar to the following:

SC Software Version,DirectConnect,SWDownload,LIMCSetAdminState,
     SCSetAdminState,SCMaintState,MIBIndexFix,MIBClearNVRAM,
     PreprovisionDirectATUC,Subtending,MarginAttenuation,
     Chassis Id Fix,LR Inband Mgmt Channel,Multiple Trap Recipients,
     Subscriber Idle Disconnect,136KB Subscriber Rates,ATU-C Parms,,,
BEGIN,,,,,,,,,,,,,,,,,,,
9651-001-07,,,,,,,,,,,,,,,,,,,
9651-001-09,,,,,,,,,,,,,,,,,,,
9651-001-12,DIRECT,,,,,,,,,,,,,,,,,,
9651-001-13,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
     PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,
9651-001-15,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
     PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,,,,,,,,
9651-001-20,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
     PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
     SUBSCTIMEOUT,BITRATES136KB,,,,
9651-001-21,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX
9651-001-22,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-23,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS, 
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-24,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-25,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
9651-001-26,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
	PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS, 
	SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS
			 				 				 			 						 default,DIRECT,SWDLD,LCSADMIN,SCSADMIN,SCMAINT,MIFIX,MICNVRAM,
     PPDATUC,SUBTEND,MARGINATTEN,LCCIDFIX,INBANDCH,TRAPRCVRS,
     SUBSCTIMEOUT,BITRATES136KB,ATUCPARMS,,,
END,,,,,,,,,,,,,,,,,,,
 
Note: All descriptions past this point are comments.  These fields 
do not get used by ViewRunner.  Cisco-Austin updates the Feature 
Capability Matrix file whenever a new SC software version is released.  
If a user connects ViewRunner to a node that "contains an SC software 
version that is not recognized, a warning dialog will notify" the 
user to obtain a newer version of the file. The SCFeatureCapabilityMatrix.csv 
file should be downloaded and saved into the directory where 
ViewRunner is installed.  If the updated file does not allow 
"ViewRunner to manage this node, then contact Customer Support 
directly."
BEGIN,,,,,,,,,,,,,,,,,,,
System Part #,LoopRunner Rel,Contains SC SW,,,,
9000-001-03,1.02 release,9651-001-07,,,,
9000-001-04,1.02A release,9651-001-09,,,,
9000-001-06,1.02C release,9651-001-12,,,,
9000-001-07,2.0 release,9651-001-13,,,,
9000-001-09,2.1.0 release,9651-001-15,,,,
9000-001-10,2.1.1 release,9651-001-15,,,,
9000-001-11,2.1.2 release,9651-001-15,,,,
9000-001-12,2.2.0 release,9651-001-20,,,,
9000-001-13, 2.1.3 release, 9651-001-21,,,,
9000-001-12, 2.2.0 release, 9651-001-20,,,,
9000-001-14, 2.2.1 release, 9651-001-22,,,,
9000-001-15, 2.2.0.101 release, 9651-001-23,,,,
9000-001-16, 2.2.5.100 release, 9651-001-24,,,,
9000-001-18, 2.2.0.102 release, 9651-001-25,,,,
9000-001-19, 2.2.0.103 release, 9651-001-25,,,,
9000-001-20, 2.2.5.102 release, 9651-001-26,,,,
9000-001-21, 2.2.5.103 release, 9651-001-26,,,,
END,,,,,,,,,,,,,,,,,,,
 
Feature Description,,,,,,
DIRECT,LoopRunner supports Direct Connect Mode (Subscribers 
     associated directly to ATU-Cs.  No LIMs) ,,,,,,,,,,
SWDLD,"LoopRunner supports system software upgrading via 
     image TFTP to node. This includes several MIB additions 
     (HW table, Image table, etc)",,,,,,,,,,
LCSACMIN,"LIM Controller Supports Configurable Admin State.  
     If this feature is supported, VR should dim the LIM 
     Chassis Deletion menu options unless Admin State is 
     Locked.",,,,,,,,,,
SCSACMIN,SC Supports Configurable Administrative State.,,,,,,,,,,
SCMAINT,SC Supports Configurable Maintenance State.,,,,,,,,,,
MIFIX,"PR 285 -  MIB indexes may now be specified during Row 
     creation.  Among other things, this eliminates requirement 
     for SC Reset prior to saving NVRAM configuration",,,,,,,,,,
MICNVRAM,PR 1211 -  MIB Supports Clearing NVRAM,,,,,,,,,,
PPDATUC,PR 1340 -  LoopRunner supports pre-provisioning of 
     ATU-C modules in direct mode.,,,,,,,,,,
SUBTEND,"LoopRunner supports Subtend Feature (Subtend host 
     module, Transit subscribers)",,,,,,,,,,
MARGINATTEN,Support for setting ADSL margin and attenuation 
     values on a per subscriber basis,,,,,,,,,,
INBANDCH,Support for LoopRunner inband management channel and 
     associated Routing Table support,,,,,,,,,,
TRAPRCVRS,Support for multiple trap recipients,,,,,,,,,,
SUBSCRTIMEOUT,"Supports lrSubscrTimerType, lrSubscrTimerValue 
     which defines if and when a subscriber is disconnected 
     after a specified idle or session timout.",,,,,,,,,,
LCCIDFIX,Supports pre-provisioning full range of Chassis 
     Ids (0-15),,,,,,,,,,
BITRATES136KB,New physical layer rate combinations supported 
     by 136KB firmware   (42 new bitrate combinations),,,,,,,,,,
ATUCPARMS,ATUC Settable parameters for 136K baud enable/disable 
	and Non-Timer CPE train enable/disable
,,,,,,,,,,
,,,,,,,,,,
,,,,,,,,,,
,,,,,,,,,,

2.3.3 Key Events Log File

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. You can use this file to troubleshoot problems with ViewRunner and the Cisco 6100 Series system.

ViewRunner software logs the following key events and information in VRLOG.TXT:

The specific time ViewRunner starts up, including the software version number

The specific time ViewRunner exits

Each specific time a Cisco 6100 Series system is discovered, including IP address and timeout value set for SNMP
Each SNMP error that appears in the Log dialog box
Each SNMP error 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 does not grow larger than two MBs. At two MBs, it truncates to zero and starts over. The information in VRLOG.TXT appears 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 session in ViewRunner, the ViewRunner Log dialog box contains the current messages logged to the VRLOG.TXT file (Figure 2-2). These are only the error messages encountered during this session.

Figure 2-2: ViewRunner Log Dialog Box

Table of Contents

Installing ViewRunner for Windows