cc/td/doc/product/dsl_prod/vrmgtsw/vr4w
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for
ViewRunner for Windows Release 2.4.0

Release Notes for
ViewRunner for Windows Release 2.4.0

September 27, 1999

These release notes discuss features, resolved bugs, and unresolved bugs for the ViewRunner for Windows Release 2.4.0.

For more detailed information about the features in these release notes, refer to the "Related Documentation" section. Information about electronic documentation can be found in the in the "Cisco Connection Online" section.

1. Contents

These release notes describe the following topics:

2. ViewRunner for Windows

ViewRunner for Windows Release 2.4.0 is the craft interface for the Cisco 6100 Series system for its Release 2.4.0 (SF-6100-2.4.0). It is operates with the Cisco 6100 Series system multiplexer chassis (MC) and can be downloaded from Cisco Connection Online (CCO).


Note Digital Off-Hook (DOH) features are not fully tested or supported in ViewRunner for Windows Release 2.4.0 hardware (Cisco 6100 or 6130) or software. DOH will be supported in the ViewRunner for Windows Release 3.0.0.

3. Software Matrix

This section details the compatibility of the following Cisco 6100 Series system elements:

Table 1 summarizes the compatibility between the Cisco 6100 Series system and the ViewRunner for Windows software.

Caution ViewRunner for Windows Release 2.4.0 does not manage a 2.3.x node.


Table 1: ViewRunner and Cisco 6100 Series System Release Compatibility Matrix
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

1The Cisco 6130 multiplexer chassis (MC) feature support present in Release 2.4.0 or higher.
2Systems with a Cisco 6100 MC installed must connect to the network through a Cisco PSC to provide the secondary lightning protection required by NEBS. Therefore, a Cisco 6100 MC cannot support a Direct Connect without PSC configuration.
3ViewRunner manages this Cisco 6100 Series system as a 2.2.1 release. ViewRunner presents a feature set corresponding to the capabilities of the Cisco 6100 Series system release noted. When you open Chassis View, ViewRunner tells you that the feature set is not recognized and that a default feature set is being used.
4FCM update for 2.2.5 required.
5ViewRunner manages this Cisco 6100 Series system as a 2.2.0 release. ViewRunner presents a feature set corresponding to the capabilities of the Cisco 6100 Series system release noted. When you open Chassis View, ViewRunner tells you that the feature set is not recognized and that a default feature set is being used.
6ViewRunner manages this Cisco 6100 Series system as a 2.1.x release. ViewRunner presents a feature set corresponding to the capabilities of the Cisco 6100 Series system release noted. When you open Chassis View, ViewRunner tells you that the feature set is not recognized and that a default feature set is being used.


Note You can find hardware compatibility matrixes for ViewRunner for Windows software and Cisco 6100 Series systems in the Cisco 6100 Series Release Notes.

4. New Features

The following are the new features for ViewRunner for Windows Release 2.4.0.

4.1 CAP ATU-C and DMT-2 ATU-C New Feature Support

Table 3 describes ViewRunner for Windows new feature support for CAP ATU-C and DMT-2 ATU-C modules.


Table 2: CAP ATU-C and DMT-2 ATU-C Modules New Feature Support
Module Type New Feature Supported Description

CAP ATU-C, DMT-2 ATU-C

Circuit ID Field Activation

Provides more line and location detail for a particular subscriber. You can configure and display circuit ID for each subscriber. The circuit field accepts up to 20 characters. Valid characters include
A to Z, a to z, 0 to 9, {.,-=;:'#!$%&*()<>_+/\}.

DMT-2 ATU-C

ViewRunner for Windows Support

Transmission rates:

  • Downstream range from 32k to 8032k.

  • Upstream range from 32k to 864k.

  • Bit rates are determined by the number of carriers and the number of bits per carrier.

CAP ATU-C

DMT-2 ATU-C

Per-Subscriber Power Setting Transmittal

You can refine signal attenuation by setting power transmittal in DBm/Hz per subscriber.

Configure transmit power attribute using the Subscriber Properties dialog box in the PSD Transmit Power field. Default values are

  • Upstream: -38

  • Downstream: -40

Note Cisco recommends that the value be set at -40 DBm/Hz for the most productive results.

DMT-2 ATU-C

Interleaved Path Support1

Default value is set to 16000 and the unit is microsecond.

Although you can configure interleaved values on the DMT-2 Subscriber Properties dialog box, the Interleaved latency option is the default per subscriber on the Service Provisioning dialog box. The Interleaved setting cannot be changed. Delay options include: 0, 500, 1000, 2000, 4000, 8000, 16000, 32000, 64000. Delay settings 16000 to 64000 result in a maximum setting.

DMT-2 ATU-C

Training Mode

The read-only default is set to Standard Train.

CAP ATU-C

DMT-2 ATU-C

Priority Queue Support

You can configure the priority queue for each subscriber PVC through the Service Provisioning dialog box. The default Priority Queue setting is 3. You can also configure the priority queue for each transit subscriber PVC through the Transit Subscriber dialog box. A new header field labeled Priority displays priority in a list box.

Values 1 through 3 represent queues. Queue usage follows these rules:

  • Queue 1—Voice transfer

  • Queue 2—Signalling

  • Queue 3—Data Transfer

DMT-2 ATU-C

Performance Monitoring: Parameter and value

You can access the Parameter field in the DMT-2 Port Status dialog box to view performance counters such as HecVioll and FarCvflfe. Performance counters measure the DMT-2 port performance according to the following factors:

  • Attenuation equations

  • Signal-to-noise ratios

  • Number of anomalies per interval

  • Types of defects such as SEF or LPR

  • Number of cells used

The Value field contains the value of the performance counter.

DMT-2 ATU-C

Forward Error Correction (FEC)

You can configure the number of redundancy bytes in both upstream and downstream. The default value is 16. The unit is bytes. Redundancy byte amount options range in multiples of two from 2 to 16.

DMT-2 ATU-C

Overhead Framing Structure

The default overhead framing structure value is 3. You can configure overhead framing according to the structure definitions and values below.

  • Full asynchronous—Full overhead framing with asynchronous bit-to-modem timing (enabled synchronization control mechanism). Value = 0.

  • Full synchronous—Full overhead framing with synchronous bit-to-modem timing (disabled synchronization control mechanism) Value = 1

  • Reduced separate fast—Reduced overhead framing with separate fast and sync bytes in fast and interleaved latency buffer respectively (64 kbits/s framing overhead) Value = 2

  • Reduced merged fast—Reduced overhead framing with merged fast and dsync byte, using either the fast or interleaved latency buffer (32kbit/s framing overhead). Value = 3

CAP ATU-C

DMT-2 ATU-C

Network Interface Module Information

You can determine the physical layer and the number of ports from the NI Module Port Configuration dialog box.

DMT-2 ATU-C

ATM virtual circuit support

Support for the ATM PVC is similar to the existing CAP ATU-C module. Subscriber provisioning is similar to the CAP ATU-C module, except for training rates.

1Follow this path to open the DMT-2 Subscriber Properties dialog box:
Subscriber Properties > More Parameters > DMT-2 Subscriber Properties dialog box

4.2 ViewRunner Enhancements

Table 3 describes enhancements in ViewRunner for Windows Release 2.4.0.


Table 3: ViewRunner Enhancements
Enhanced Feature Description

System Name/ System Location fields

The 6100 Properties dialog box provides two new fields where you can enter the name and location of the system you are using.

Rules:

    1. When the system is set up for the first time, the System Name and System Location fields are empty strings.

    2. Field length for both fields is 255 characters.

    3. To save the system name and system location variables, click Apply.

    4. The system name and system location variables are restored each time you select the 6100 Properties dialog box.

6130 Chassis Fan Tray Present toggle

The 6100 Properties dialog box now allows you to indicate whether or not a chassis fan tray is present on a Cisco 6100 or 6130 chassis by clicking a toggle.

Rules:

    1. If you check the chassis Fan Tray Present toggle, the operational status of the fan tray will display on the 6130 Event History View as an event such as, "Fan tray detected."

    2. Keywords in the FCM governing fan tray support and chassis revision are: CHASSISREV and FANTRAY.

Fan Tray Alarms

Two critical severity fan tray alarms now display.

MC Fan Failure—When you have checked the Fan Tray Present toggle on the 6100 Properties dialog box but a fan tray is not present, a critial alarm will display on the Current Alarms View dialog box.

MC Fan Required—When you have configured a module requiring a fan tray, such as the DMT-2 ATU-C module, and no fan tray can be detected, a critical alarm will display on the Current Alarms View dialog box.

Note In ViewRunner for Windows Release 2.4.0, DMT-2 ATU-C modules require a fan tray to configure accurately. If a fan tray is not present, DMT-2 ATU-C modules will detrain with a corresponding critical alarm.

Detraining under the same conditions will be prevented in ViewRunner for Windows Release 2.4.1.

View All Subscriber PVCs summary dialog box

Latency and priority values now display

Administrative state icons on the Cisco 6100 Series Chassis view

The module color now indicates operation and preprovision status as follows:

  • White—ViewRunner has lost communication with the Cisco 6100 Series node, but this module is present in the ViewRunner database.

  • Blue—The module has been preprovisioned in the chassis.

  • Green—The module and all of its ports are in normal operational state.

  • Yellow—Outstanding alarm (minor) on the module or any of its ports.

  • Orange—Outstanding alarm (major) on the module or any of its ports.

  • Red—Outstanding alarm (critical) on the module or any of its ports.

5. Release Caveats

Before installing ViewRunner for Windows, note the following caveats and follow those procedures appropriate to your operating system.

    1. Windows 95 installation of ViewRunner for Windows 2.4.0 requires the following patches:

    2. Windows NT requires Service Pack 4 or later.

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

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

  When you click OK the program fails to load.
  If you see the preceding error message, the system DLL files that OCX: MSCOMCT2.OCX depends on are not current.
  Update the core OS COM files by installing the Distributed COM (DCOM) libraries.

    4. Windows NT dual-homed systems are not supported. If you have a multihomed system, disable one network adapter before attempting to run ViewRunner for Windows Release 2.4.0.

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

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

    7. 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.

6. Resolved Bugs for ViewRunner for Windows Release 2.4.0

No resolved bugs exist for ViewRunner for Windows Release 2.4.0.

7. Open Bugs in ViewRunner for Windows Release 2.4.0

The bugs listed in Table 4 are open in ViewRunner for Windows Release 2.4.0.


Table 4: Open Bugs in Release 2.4.0
Bug Number Description

CSCdk50956

ViewRunner for Windows allows you to delete yourself as a user.

Impact: This forces the administrator to create another account for the user, which would lead to a time delay.

Workaround: Do not delete yourself as a user.

CSCne02378

View Subscriber PVC dialog box doesn't display the In-band Management Channel (IMC) PVC.

Impact: The user might not understand why a network side VCC cannot be configured. The reason is that it is already being used by the IMC.

Workaround: Remember that the IMC VPI/VCI combination cannot be used on network side VCCs.

CSCne02377

Summary Dialog Save to File (WinNT only): Refresh button corrupts list-box column names and does not reset Delete button if all columns were deleted.

Impact: None. The dialog box refreshes the next time it is opened.

Workaround: None.

CSCne02120

An SC timeout (similar to the TFTP timeout) is needed to handle situations where ViewRunner Software Download or Restore is waiting for the SC to return from reset.

Impact: If the SC never comes back after the SC reset or after Clear NVRAM, the Software Download or Restore wizard waits forever.

Workaround: Kill ViewRunner and restart.

CSCne01959

When adding a new subscriber, the Service Provisioning button should be dimmed (it is always enabled).

Impact: You can navigate to a dialog box that is not available for data entry. All service provisioning fields are disabled until the subscriber is properly configured.

Workaround: Configure subscriber before provisioning VCCs.

8. Related Documentation

The following sections list the central office (CO) and customer premises equipment (CPE) publications that relate to the Cisco DSL product family.

8.1 CO Publications

A complete list of all released Cisco 6100 Series system with NI-1 related documentation is available on the World Wide Web at http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/c6100/index.htm.

The following ViewRunner management software is used to provision and manage the Cisco 6100 Series system with NI-1. A complete list of all released ViewRunner documentation is available on the Word Wide Web.

8.2 CPE Publications

The Cisco CPE, also known as the Cisco 600 Series, is part of the Cisco end-to-end DSL product family. CPE comprises modems and routers at the customer site primarily used by home office and corporate LAN personnel. Most CPE uses the Cisco Broadband Operating System (CBOS) as its operating system. CBOS provides a comprehensive command set and web interface that allow you to configure your Cisco CPE modem or router.

A complete list of all released Cisco 600 Series documentation is available on the World Wide Web at http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/c600s/index.htm.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Sun Sep 29 00:43:00 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.