Guest

Cisco Lightstream ATM Switches

LightStream 2020 Release Notes 2.3(1)

 Feedback

Table Of Contents

LightStream 2020 Release Notes for Software Release 2.3(1)

Contents

LightStream 2020 Overview

Enhancements

Software Release 2.3(1)

Software Upgrade Procedures

Procedure 1, Copy New Software to the Distribution Node

Procedure 2, Copy New Software to Remote Nodes

Procedure 3, Change the Running Software Version

Special Procedures

Special Procedure A, Freeing Up Disk Space

Special Procedure B, Falling Back to the Prior Version

Special Procedure C, Verifying Connection to Backup NP

Special Procedure D, Troubleshooting rsh to on a Remote Node

Special Procedure E, Backing Up the Distribution Diskettes

Special Procedure F, Freeing Up Memory on an NP

Workstation Upgrade Procedures

Procedure 1, Upgrading StreamView Software Under HP OpenView

Procedure 2, Upgrading StreamView Software Without HP OpenView

Special Considerations

Congestion Avoidance

Documentation

Firmware

Hardware and Diagnostics

Installation, Upgrade, and Initial Configuration

Internetworking

Network Management: CiscoView

Network Management: The StreamView CFG Tool

Network Management: The StreamView PVC and VLI Tools

Network Management: The Command Line Interface (CLI)

Network Management: The LightStream Topology Map

Network Management: Other

Other

Platform

Resource Allocation

Traps

Resolved Problems

Documentation

Internetworking

Network Management

Platform

Appendix A: Hardware Compatibility Table

Appendix B: Flash Memory Image Checksum Values

Document Conventions

Where to Find Safety and Warning Information

Obtaining Documentation

Cisco.com

Product Documentation DVD

Cisco Optical Networking Product Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


LightStream 2020 Release Notes for Software Release 2.3(1)


Date: January 10, 1997

Text Part Number: 78-4028-01

These release notes describe the enhancements, software upgrade procedures, and special considerations for controlled Software Release 2.3(1) of the LightStream 2020 multiservice ATM switch (LS2020 switch).

Software Release 2.3(1) is a base release of LS2020 node software. It supersedes all prior releases and upgrades of Release 2.0, Release 2.1, and Release 2.1.1 software.

Software Release 2.3(1) completely replaces Software Release 2.1.1 with a full set of installation diskettes. These release notes include the entire contents of Release Notes 2.3.1 and include information about special considerations and resolved problems fixed in Software Release 2.1(1.1), 2.1(1.2), 2.1(1.3), 2.1(1.91), 2.1(1.92), and 2.1(1.93).

Contents

This document includes the following information:

LightStream 2020 Overview

Enhancements

Software Upgrade Procedures

Special Procedures

Workstation Upgrade Procedures

Special Considerations

Resolved Problems

Appendix A: Hardware Compatibility Table

Appendix B: Flash Memory Image Checksum Values

Document Conventions

Where to Find Safety and Warning Information

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

LightStream 2020 Overview

The LightStream 2020 multiservice asynchronous transfer mode (ATM) switch is designed for campus backbone, wide area network (WAN), and public edge switch deployment. It is well suited for business-critical applications requiring data, voice, and video, by supporting Ethernet, Fiber Distributed Data Interface (FDDI), ATM, Frame Relay, and circuit emulation interfaces. It provides the connectivity, flexibility, and performance required by the most demanding networks, and its redundant power supplies, switching fabrics, and network processors help to ensure high reliability.

For customers who see ATM technology as the foundation of networks of the future, but are concerned about preserving investments in existing network infrastructures, the LS2020 provides Ethernet and FDDI switching that can be easily migrated to ATM at any time.

The advanced traffic and buffer management of the LS2020 node provides complete control over bandwidth allocation, Quality-of-Service (QoS), and congestion avoidance for networks in service today, while providing a growth path as networks increase in size and complexity.

Enhancements

This section discusses the enhancements and changes in functionality for Software Release 2.3(1).

Software Release 2.3(1)

The enhancements for Software Release 2.3(1) include:

Spanning Tree Enhancements

UNIX Environmental Validation Check

Trace Route Feature

OC-3c SC Connector

CiscoView

Documentation Master Index

Spanning-Tree Enhancements

The spanning-tree operation is supported on both the Ethernet and FDDI interfaces and is controllable on a per LAN port basis. The spanning-tree operation can be enabled or disabled and BPDUs can be transferred on each interface. Once the enable or disable state is set, explicit network management action is required to change the state. IEEE spanning-tree protocols are supported.

Network management for spanning-tree supports line and graphically oriented user interfaces for the configuration of each interface and supports status information on the state of each interface.

UNIX Environmental Validation Check

The StreamView application includes an environmental validation tool that facilitates the installation/upgrade and troubleshooting of the StreamView programs cfg, pvc, vli, cfg_a, and monitor. Upon startup of each program, the environmental validation tool checks environmental components required to run the programs. Results of the environmental validation check are written to a temporary log file in the /tmp directory. If no errors are found upon completion of the environmental validation check, the temporary log file is deleted. If errors are found, the temporary log file includes the name of the environmental components and the path name.

Trace Route Feature

Provides a mechanism to trace a circuit from source edge to destination edge of the LS2020 network and return status and statistics from the edge and intermediate line cards. It also provides the ability to get information about SVCs carrying bridged traffic at the entry and exit edges. Trace route is integrated into the command line interface (CLI).

OC-3 SC Connector

The OC-3c single-mode access card now has an SC-type connector. The new OC-3c card is functionally identical to the existing OC-3c card that uses an ST-type connector.

CiscoView

CiscoView is a GUI device management software application that provides dynamic status, statistics, and comprehensive configuration information for Cisco System's switched and internetworking products. CiscoView allows you to display configuration and performance information, and perform minor troubleshooting tasks. CiscoView is provided in addition to the LS2020 CLI and StreamView management tools, which remain in place.

Documentation Master Index

A new volume has been added to the LS2020 documentation set: the LightStream 2020 Master Index, which combines the indexes found in each of the nine printed manuals. Use the master index when you're not sure which manual contains the information you need.

Software Upgrade Procedures

This section provides information for upgrading the LightStream 2020 switch to Software Release 2.3(1). Use this software upgrade procedure to upgrade software on an LS2020 node that has already been installed and is running. For this release to be installed:

The network processor must have 32 MB of memory

You must be running at least Software Release 2.0.5

You must have a modem in each node to allow remote software upgrades. (For more information on modems, see the LightStream 2020 Site Planning and Cabling Guide.)


Note To prevent isolating a node during this upgrade, you must have a modem connected to the switch card(s) of that node. For more information regarding compatible modems, see the LS2020 Site Planning and CableingGuide.


You may want to review Appendix A: Hardware Compatibility Table. This table specifies the minimum hardware revision levels required by this version of the LightStream 2020 software.


Note Do NOT use these software upgrade procedures if:


You are installing a network processor with an uninitialized disk. In that case, use the installation procedures given in the LightStream 2020 Installation Guide, Appendix B, "Software Reinstallation."

You are upgrading the network management software running on a Sun workstation. In that case, use the procedures described in the section " Workstation Upgrade Procedures" later in this document.

You are installing the network management software on a Sun workstation for the first time. In that case, refer to the section entitled "Installing StreamView Software" in the LightStream 2020 Installation Guide.


Caution The LS2020 NP is a special-purpose communications processor. It should not be used as a general-purpose UNIX host. If any files have been copied or placed on the disk (especially in the root partition), they should be removed before upgrading the software to Release 2.3(1). If the names of any files provided by Cisco have been changed, the original file names should be restored.

Below is a list of the LS2020 Software Release 2.3(1) distribution diskettes.

LS2020 Software Release 2.3(1) Distribution Diskettes
Number of diskettes
Version Listed on Diskette Label

Boot Disk

1

2.3(1)

System Diskettes

3

2.3(1)

Application Diskettes

8

2.3(1)

Diagnostic Diskettes

4

2.3(1)

Firmware Diskettes

2

2.3(1)


Use the following procedures to upgrade a network to Software Release 2.3(1):

Procedure 1, Copy New Software to the Distribution Node. Use the swinstall command to copy the new software from the installation diskettes to the node being used as the software distribution node. (If swinstall reports insufficient disk space, you will be directed to perform Special Procedure A, Freeing Up Disk Space. If swinstall reports insufficient memory, you will be directed to perform Special Procedure F, Freeing Up Memory on an NP)

Procedure 2, Copy New Software to Remote Nodes. Use the swremoteinstall command to copy the new software from the distribution node to other nodes in the LS2020 network. (If swremoteinstall reports that there is not enough disk space on a remote node, you will be directed to perform Special Procedure A, Freeing Up Disk Space. If swremoteinstall reports insufficient memory, you will be directed to perform Special Procedure F, Freeing Up Memory on an NP)

Procedure 3, Change the Running Software Version. Use the swchgver command to change the version of software running on each node after you copy the new software to the node.( If swchgver reports insufficient memory, you will be directed to perform Special Procedure F, Freeing Up Memory on an NP.)

In addition, you may need to perform one or more of these procedures:

Special Procedure A, Freeing Up Disk Space. If the swinstall command or the swremoteinstall command reports that you do not have enough disk space, delete files associated with obsolete releases of software.

Special Procedure B, Falling Back to the Prior Version. You can fall back to the prior version of software if you wish to for any reason.

Special Procedure C, Verifying Connection to Backup NP. Use this procedure if the swchgver command fails to contact the backup NP on a redundant system.

Special Procedure D, Troubleshooting rsh to on a Remote Node. If the swremoteinstall command (which uses the rsh command) reports that it does not have permission to copy the files to the remote node, this section describes some of the common causes and how to correct them.

Special Procedure E, Backing Up the Distribution Diskettes. You may wish to make copies of the distribution diskettes.

Special Procedure F, Freeing Up Memory on an NP. Use this procedure when there is insufficient memory to run a software installation procedure on an NP.

Procedure 1, Copy New Software to the Distribution Node

With this procedure, you copy the new software to a local LS2020 node from the distribution disk set. This local node is referred to as the distribution node. To perform this procedure, use a terminal connected to the console port of the distribution node. Only the person doing the installation should be logged on to the system.


Note If you are upgrading from Software Release 2.0.10 or 2.1.1 to 2.3(1), this procedure causes Flash memory to be reloaded. The Flash reload time depends on your system configuration.


Perform the following taksks, which are detailed in the sections that follow, to upgrade the distribution node (or any local node) to Software Release 2.3(1) node software:


Step 1 Connect to the primary NP.

Step 2 Copy Software Release 2.3(1) from floppies to hard disk.

In Procedure 2, Copy New Software to Remote Nodes, you use the distribution node as the source for copying the software to other nodes in the network.


Note If for any reason you discontinue installation of this release after you have started loading software, delete this release using Special Procedure A, Freeing Up Disk Space. This minimizes the impact of the interrupted installation on future installations. When you resume installation of this release, you must restart at the beginning of this procedure.


Connect to the Primary NP


Step 1 Enter `. (backquote plus dot, that is, left single quote plus period).

Step 2 At the TCS HUB prompt, use the connect command to connect to the NP in slot 1:

TCS HUB <<A>> connect 1

You may need to press Return a second time after typing the connect command in order to get a prompt from the NP.

A prompt should appear asking for a user login name:

user name: 

Note If someone using the machine before you has not logged out, your prompt may be different. If this occurs, log out and log back in as root.


Step 3 Log in as root. The bash prompt appears (with # indicating a root login):

user name: root 
password: 
bash#

If your system has only one NP, go to Step 6 now.


Step 4 On a system with redundant NPs, verify that you are connected to the primary NP (the active NP), as follows:

At the bash prompt, enter the cli command to start the CLI:

bash# cli

At the CLI prompt, enter the show chassis command.

In the resulting display, determine whether you are connected to the primary NP or the backup NP by examining the entries for "Slot of Primary NP" and "Slot of This NP."

Are you connected to the primary or backup NP?

If the two entries identify the same NP number, you are connected to the primary NP (the active NP). Since you connected to slot 1 in Step 1 above, the following is true:

primary= 1
backup= 2

Make a note of this. Use the value 1 where you see the parameter name "primary" in later procedures.

If the two entries do not identify the same NP number, you are connected to the backup NP. Since you connected to slot 1 in Step 1 above, the following is true:

primary = 2
backup = 1

Make a note of this. Use the value 2 where you see the parameter name "primary" in Step 5, below, and in other procedures.


Use the exit or quit command to exit from the CLI.

If you are connected to the primary NP, go to Step 6 now.

Step 5 If you are connected to the backup NP, disconnect from it and connect to the primary NP (the active NP):

Enter `. (backquote plus dot, that is, left single quote plus period) to return to the TCS HUB.

Connect to the slot of the primary NP by typing the following command:

TCS HUB<<A>> connect <primary>
where <primary> is either 1 or 2.

Log in to the NP as root.

Copy Release 2.3(1) Software from Floppies to Hard Disk

Step 6 Determine which floppy disk drive is appropriate to use for the upgrade. NP slot 1 is connected to the bottom disk drive, and NP slot 2 is connected to the top disk drive.

Step 7 The boot disk is not used in this upgrade procedure. You will run the swinstall utility once for each diskette set. Install the diskette sets in this order: system, application, diagnostics, firmware.

Step 8 Enter the swinstall command at the bash prompt:

  bash# swinstall

Note If the swinstall program reports that there is insufficient disk space for the installation, go to Special Procedure A, Freeing Up Disk Space, before continuing. If the swinstall program reports insufficient memory, go to Special Procedure F, Freeing Up Memory on an NP.


When the program prompts you for a diskette, insert the first diskette (of the diskette set that you are currently installing) into the appropriate drive and press Return. Repeat as the program prompts you for more diskettes in the current set.

Step 9 Repeat Step 8 for each diskette set, following the order given under Step 6.

Procedure 2, Copy New Software to Remote Nodes

With this procedure you distribute new software from the distribution node to other LS2020 nodes. Carry out this procedure for all remote nodes before going to Procedure 3, Change the Running Software Version.

If you do not wish to upgrade software remotely, you can upgrade software directly from the distribution diskettes on each node in your LS2020 network. To do this, carry out Procedure 1, Copy New Software to the Distribution Node, and Procedure 3, Change the Running Software Version, on each node in the network.

Before proceeding, make sure that the following is true:

Distribution Node
Remote Node

You are logged in to the distribution node.

No other user is logged in.

The distribution node is running LS2020 application software.

You are able to establish an rsh connection and a modem connection at each remote site. (You do not need to be physically located at the remote node site.)

The remote node is running LS2020 application software.


Perform the following tasks for each node in your LS2020 network:

Verify the remote command execution

Distribute Software Release 2.3(1) to remote nodes

Verify Remote Command Execution

Verify that it is possible to execute commands on the remote node from the distribution node:


Step 1 On the distribution node, execute the following command:

bash# rsh remote-node hostname

Enter the name of the remote node in place of remote-node.

If the command succeeds, it prints the name of remote-node. Continue to Step 2.

If this is the first time you have upgraded, this step is likely to fail. If the command fails, it prints one of the following messages:

hostname: unknown host 
hostname: Connection timed out 
Permission denied.

Note If the command fails, refer to "Special Procedure D, Troubleshooting rsh to on a Remote Node" section.


Distribute Software Release 2.3(1) to Remote Nodes

Step 2 Copy Software Release 2.3(1) files to remote-node. In a window running a login on distribution-node, execute the following command:

bash# swremoteinstall -h remote-node 2.3.1 

Enter the name of the remote node in place of remote-node.

The swremoteinstall process checks memory and disk availability and copies Software Release 2.3(1) to the remote-node. It should take 5 to 10 minutes, depending upon bandwidth between the nodes.


Note If the swremoteinstall program reports there is not enough disk space for the installation, connect to the remote node through a modem port or Telnet connection and follow "Special Procedure A, Freeing Up Disk Space" on the remote node. If the swremoteinstall program reports insufficient memory, go to "Special Procedure F, Freeing Up Memory on an NP" section. Then repeat Step 2.


Procedure 3, Change the Running Software Version

With this procedure you activate the software that has been copied to the node, and the node begins running the new LS2020 application software.

Perform the following tasks for each node in your LS2020 network:

Connect to the Primary NP

Change the Running Software Version

Connect to the Primary NP


Step 1 Connect to the TCS hub on the node. Use a console terminal if you are on site. Use a dial-in modem to connect to a remote node.


Caution Do not use a network connection such as Telnet to connect to the node for purposes of changing the running software version. During the procedure, a card may be reset, breaking your Telnet connection and interrupting the change process.

Step 2 Enter `. (backquote plus dot, that is, left single quote plus period). You should see the TCS prompt.

Step 3 At the TCS HUB prompt, use the connect command to connect to the NP in slot 1:

TCS HUB <<A>> connect 1

The user name prompt should appear. Log in as root. The bash prompt appears (with # indicating a root login).

user name: root
password:
bash#

After you type the connect command, you may need to press Return a second time in order to get a prompt from the NP.

If someone using the machine before you has not logged out of a session, your prompt may be different. Attempt to get back to a bash prompt and log out.

If your system has only one NP, go to Step 6 now.

Step 4 On a system with redundant NPs, determine whether you are connected to the primary NP (the active NP), as follows:

At the bash prompt, enter the cli command to start the CLI:

bash# cli

At the CLI prompt, enter the show chassis command.

Determine whether you are connected to the primary NP or the backup NP by examining the entries for "Slot of Primary NP" and "Slot of This NP."

Are you connected to the primary or backup NP?

If the two entries identify the same NP number, you are connected to the primary NP (the active NP). Since you connected to slot 1 in Step 1, above, the following is true:

primary= 1
backup= 2

Make a note of this. Use the value 1 where you see the parameter name primary in later procedures.

If the two entries do not identify the same NP number, you are connected to the backup NP. Since you connected to slot 1 in Step 3 above, the following is true:

primary = 2
backup = 1

Make a note of this. Use the value 2 where you see the parameter name primary in Step 5, below, and in other procedures.


Use the exit or quit command to exit from the CLI.

Step 5 If you are connected to the primary NP, skip Step 5. If you are connected to the backup NP, disconnect from it and connect to the primary NP:

Enter `. (backquote plus dot, that is, left single quote plus period) to return to the TCS HUB.

Connect to the slot of the primary NP (the active NP) by typing the following command:

TCS HUB<<A>> connect primary

Substitute 1 or 2 in place of primary, as explained above.

If necessary, log in to the NP as root.

Change the Running Software Version


Note The swchgver program usually takes about 20 minutes to run. A card's fault (FLT) light comes on and stays on for the duration of loading of Flash on that card.


Step 6 Use the swchgver program to run the software that you have just installed:

bash# swchgver 

The swchgver program produces the following results:

Flash memory is reloaded on each card (if a newer version has been installed).

The software is copied to the backup NP (in a redundant system).

The newly installed software is made the active version (on both NPs in a redundant system).

The network processor (NP) is rebooted, so that the changes take effect (both NPs in a redundant system).

The line cards reload their software images.


Caution Do not interrupt the loading of Flash memory, particularly on an NP. A card with partially loaded Flash cannot complete its boot sequence until Flash is reloaded. If you dial in, you must remain dialed in until the process has completed and the NP(s) have rebooted. If flash loading is interrupted, call Cisco Customer Support at 1-800-553-2447.


Note If the swremoteinstall program reports insufficient memory, you will be directed to perform "Special Procedure F, Freeing Up Memory on an NP" section. Then repeat Step 6.


Step 7 On a redundant NP system, the swchgver program automatically copies the new software from the primary NP (the currently active NP) to the backup NP. This copy may fail, for example, if the other NP is not running application software. If the copy fails, use one of the options listed below.

If one the following error messages is displayed, refer to "Special Procedure C, Verifying Connection to Backup NP" section.

1. WARNING: This is a dual NP system where the current NP is
unable to contact the backup NP".
Thus, swchgver run on this NP will not interact with the
backup NP in the expected way to ensure that each NP is
running a consistent software release.
To run swchgver anyway, you must explicitly specify all desired
swchgver options.  Typical choices might be
  -  swchgver <#ver> -force -nordist 
  -  swchgver <#ver> -force -nordist -nolinecardreset -noflashupdate

2. Failed to execute "rsh other-np /bin/true".
This is possibly due to an invalid /.rhosts file on the backup
NP.  Please check the /.rhosts file on the backup NP and make
sure it contains the line "other-np root". 

The following error message is due to interference between swchgver and the mechanism that keeps critical files on the two NPs in synch. You are unlikely to receive this message. However, if this message appears, wait a moment and then invoke the swchgver program a second time.

  bash# swchgver
  swchgver: checking backup NP /dev/sd0b disk space for 2.3.1
         (/usr/app)
  /bin/rsh: Executable file in use
  swchgver: Error: attempt to contact other-np failed.
  bash#

If the backup NP is not running the LightStream application, see "Special Procedure C, Verifying Connection to Backup NP" section. If the backup NP has never had the application set installed, have someone who is physically at the node site install the software on the other NP as though it were a new NP/disk addition. For more information, refer to Appendix B in the LightStream 2020 Installation Guide.

Example Output from a Successful Upgrade

The following is an example of the output that results when this upgrade procedure is carried out with the console trap level set to info:


sqatb11:1# swinfo
    VERSIONS INSTALLED ON DISK:
                        2.1.0
                        2.3.1
                        new
    CURRENTLY RUNNING VERSIONS:
                        2.1.0
sqatb11:1# swchgver
  free memory required: 1500K
  free memory available:        6672K
WARNING: Do not terminate connection.  Wait for swchgver completion.
Checking and downloading FLASH memory for all function cards
fcload: slot 1: flash image is up to date (xsum==0xf682)
fcload: slot 3: flash image is up to date (xsum==0xc218)
fcload: slot 4: flash image is up to date (xsum==0x8fd1)
fcload: slot 5: flash image is up to date (xsum==0x8ac)
fcload: slot 6: flash image is up to date (xsum==0x8fd1)
fcload: slot 7: flash image is up to date (xsum==0x8fd1)
fcload: slot 8: flash image is up to date (xsum==0xc218)
fcload: slot 9: flash image is up to date (xsum==0xc218)
fcload: slot 10: flash image is up to date (xsum==0x8fd1)
fcload: slot 15: flash image is up to date (xsum==0xe82a)
Forcing reset of line cards

==> (OPER) NDD_5 at 11/04/96 15:58:59 EST (11/04/96 20:58:59 GMT)
      Line Card sqatb11:3 (OC3-TR) down (ERMP failure 0x401).                  

==> (OPER) NDD_5 at 11/04/96 15:59:06 EST (11/04/96 20:59:06 GMT)
      Line Card sqatb11:4 (PLC1-LS-EDGE) down (ERMP failure 0x401).            

==> (GENERIC) at 11/04/96 15:59:07 EST (11/04/96 20:59:07 GMT)
Link Down Trap at 11/04/96 15:59:07 EST (11/04/96 20:59:07 GMT)                
      Port 4000                                                                

==> (GENERIC) at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)
Link Down Trap at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)                
      Port 4001                                                                

==> (GENERIC) at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)
Link Down Trap at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)                
      Port 4002                                                                

==> (GENERIC) at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)
Link Down Trap at 11/04/96 15:59:08 EST (11/04/96 20:59:08 GMT)                
      Port 4003                                                                

==> (GENERIC) at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)
Link Down Trap at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)                
      Port 4004                                                                

==> (GENERIC) at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)
Link Down Trap at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)                
      Port 4005                                                                

==> (GENERIC) at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)
Link Down Trap at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)                
      Port 4006                                                                

==> (GENERIC) at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)
Link Down Trap at 11/04/96 15:59:09 EST (11/04/96 20:59:09 GMT)                
      Port 4007                                                                

==> (OPER) NDD_5 at 11/04/96 15:59:11 EST (11/04/96 20:59:11 GMT)
      Line Card sqatb11:5 (LS-EDGE) down (ERMP failure 0x401).                 

==> (GENERIC) at 11/04/96 15:59:13 EST (11/04/96 20:59:13 GMT)
Link Down Trap at 11/04/96 15:59:13 EST (11/04/96 20:59:13 GMT)                
      Port 5000                                                                

==> (GENERIC) at 11/04/96 15:59:15 EST (11/04/96 20:59:15 GMT)
Link Down Trap at 11/04/96 15:59:15 EST (11/04/96 20:59:15 GMT)                
      Port 5001                                                                

==> (GENERIC) at 11/04/96 15:59:16 EST (11/04/96 20:59:16 GMT)
Link Down Trap at 11/04/96 15:59:16 EST (11/04/96 20:59:16 GMT)                
      Port 5002                                                                

==> (GENERIC) at 11/04/96 15:59:16 EST (11/04/96 20:59:16 GMT)
Link Down Trap at 11/04/96 15:59:16 EST (11/04/96 20:59:16 GMT)                
      Port 5003                                                                

==> (GENERIC) at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)
Link Down Trap at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)                
      Port 5004                                                                

==> (GENERIC) at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)
Link Down Trap at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)                
      Port 5005                                                                

==> (GENERIC) at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)
Link Down Trap at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)                
      Port 5006                                                                

==> (GENERIC) at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)
Link Down Trap at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)                
      Port 5007                                                                

==> (OPER) NDD_5 at 11/04/96 15:59:17 EST (11/04/96 20:59:17 GMT)
      Line Card sqatb11:6 (FDDI) down (ERMP failure 0x401).                    

==> (OPER) NDD_5 at 11/04/96 15:59:20 EST (11/04/96 20:59:20 GMT)
      Line Card sqatb11:7 (CEM) down (ERMP failure 0x401).                     

==> (OPER) NDD_5 at 11/04/96 15:59:26 EST (11/04/96 20:59:26 GMT)
      Line Card sqatb11:8 (OC3-EDGE) down (ERMP failure 0x401).                

==> (GENERIC) at 11/04/96 15:59:26 EST (11/04/96 20:59:26 GMT)
Link Down Trap at 11/04/96 15:59:26 EST (11/04/96 20:59:26 GMT)                
      Port 8000                                                                

==> (GENERIC) at 11/04/96 15:59:26 EST (11/04/96 20:59:26 GMT)
Link Down Trap at 11/04/96 15:59:26 EST (11/04/96 20:59:26 GMT)                
      Port 8001                                                                

==> (OPER) NDD_5 at 11/04/96 15:59:29 EST (11/04/96 20:59:29 GMT)
      Line Card sqatb11:9 (OC3-TR) down (ERMP failure 0x401).                  

==> (OPER) NDD_5 at 11/04/96 15:59:33 EST (11/04/96 20:59:33 GMT)
      Line Card sqatb11:10 (ETHERNET) down (ERMP failure 0x401).               
Rebooting the network processor
PROGRAM: comment: (ls2_3_1_rel) compiled Oct 25 1996 @ 17:46:09 [pid:67]
[comment.67]: 11/4/96 15:59:36 EDT (11/4/96 20:59:36 GMT): USER root: swchgver:  Rebooting 
the network processor

[comment.67]: 11/4/96 15:59:36 EDT (11/4/96 20:59:36 GMT): USER root: swchgver:  Rebooting 
the network processor

==> (OPER) COMMENT_1001 at 11/04/96 15:59:36 EST (11/04/96 20:59:36 GMT)
      USER root: swchgver:  Rebooting the network processor                    

**** LynxOS [rebooted by /bin/reboot] is down ****

Memory Autosizing...(32Meg)...Done
Clearing 32Meg Memory...Done

NP1 POST Version 0.261  Jun 17 1996

 
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz
{|}~

                NP1 POST SUMMARY:
                ----------------
                        0 Tests Failed 

booting: drive:0, partition:0, kernel:"lynx.os", flags:0x4308
Resetting SCSI bus
Kernel linked for 0xea010000
LOAD AT 0x10000
        491520+49152+463432[+63348+52522]
TOTAL SIZE: 1119976 at 0x1001c
START AT 0x10020
NP memory size: 32 MB
ILACC: EEPROM enet addr:08:00:08:00:81:bc, Silicon Rev:0x5, IB:0xea1ca8e0
virtual console: IB: 0xea1bdfe0
NCR 53C710: Chip Revision: 0x2, IB: 0xec1c1000

LynxOS/68040-MVME167 Version 2.1.0
Copyright 1992 Lynx Real-Time Systems Inc.
All rights reserved.

LynxOS release 2.1.0, level 1: NP-LynxOS #136: compiled Oct 24 1996 18:55:38

LynxOS Startup: ma


fsck /dev/sd0a
(all sizes and block numbers in decimal)
(file system creation time is Tue Oct 29 15:36:28 1996)
checking used files
recovering orphaned files
making free block list
making free inode list
45807 free blocks 3356 free inodes

fsck /dev/sd0b
(all sizes and block numbers in decimal)
(file system creation time is Tue Oct 29 15:36:48 1996)
checking used files
recovering orphaned files
making free block list
making free inode list
36401 free blocks 3525 free inodes

fsck /dev/sd0c
(all sizes and block numbers in decimal)
(file system creation time is Tue Oct 29 15:37:09 1996)
checking used files
recovering orphaned files
making free block list
making free inode list
8302 free blocks 3549 free inodes

fsck /dev/sd0d
(all sizes and block numbers in decimal)
(file system creation time is Tue Oct 29 15:37:29 1996)
checking used files
recovering orphaned files
making free block list
making free inode list
337925 free blocks 21810 free inodes

Mounting all filesystems
Starting VM system ... Virtual Memory Engaged!
inetd started
Starting crond ...
Initializing the switch hardware interface ...
Using switch A, cards are NOT synchronized, fast cutover is supported
PCP version: 0x410, CMP version: 0x12, FSU version 0x109
Starting the switch software at Mon Nov  4 16:04:47 EST 1996
LightStream 2020 Version 2.3.1
Copyright 1993 LightStream Corp.  All rights reserved.
Portions copyright 1992 by Lynx Real-Time Systems Inc., 1983 by the Regents
of the University of California, 1988 and 1990 by Paul Vixie, and 1991 by
SNMP Research Inc.


This software contains unpublished proprietary and trade secret information
of LightStream Corp.

LightStream 2020 Software provided to the U.S. Government is subject to the
notices on the software and on the LightStream user documentation copyright
page.
PROGRAM: cbuf: (ls2_3_1_rel) compiled Oct 25 1996 @ 17:38:47 [pid:58]
user name:

Special Procedures

Special Procedure A, Freeing Up Disk Space

Use this procedure if the swinstall or swremoteinstall programs report that there is insufficient disk space.

Identify Files to Delete


Step 1 Log in to the target node as root.

Step 2 Identify the software to remove. To do this, enter the command swdelete with no argument, as in the following example:

bash# swdelete 
Usage: swdelete version -f 
           version:      version of software to delete (e.g. 2.0.0) 
             -f:           remove even if currently running version 
                           WARNING: deleting currently running version also 
                                    deletes current configuration data 
Description: 
  Deletes the indicated release, first checking to make sure 
  that the release is not currently in use. 
  (For an update release, both the update and the underlying  
   major release are in use.) 
    VERSIONS ON DISK
								                        2.0.7
								                        2.0.8
								                        2.1.0
CURRENTLY RUNNING VERSIONS: 
                        2.1.0 
bash#  
If you attempt to delete the running version of software, the following message appears:
swdelete: Will not remove current running system (2.1.0) and  
          configuration data. 

Delete Obsolete Version Files

Step 3 Use the swdelete command to delete obsolete version files:

bash# swdelete 2.0.7 
Deleting version 2.0.7 
bash# 

Step 4 Return to the section that referred you to this procedure.

Special Procedure B, Falling Back to the Prior Version

Use this procedure if you wish to revert to the prior version of software.


Step 1 Log into the LS2020 node as root if you have not already done so.

Step 2 Use Procedure 3, Change the Running Software Version, to revert to the prior version, giving the earlier version number as the argument of the swchgver command. For example, if the prior version is 2.1.0, enter the command as follows:

LSnode:1# swchgver 2.1.0 

Note The LS2020 configuration information is stored with the current release when downloaded from the network management system. When you upgrade to a new release, that information is copied forward to initialize the new release's configuration when you perform swinstall or swremoteinstall. When falling back to a previous release, the configuration will match the last time that software release was operational, which may not reflect the current configuration.



Note The fallback procedure does not reload old Flash versions in cards. The new Flash remains.


Return to the section that referred you here.

Special Procedure C, Verifying Connection to Backup NP

Use this procedure to verify that the primary NP can communicate with the other NP. To perform this procedure, use a terminal connected to the console port of a chassis that has redundant NPs.


Note Do not use this procedure if the other NP is rebooting. During reboot, the other NP will not be accessible for a period of several minutes.



Step 1 If you are not already connected to the slot of the primary NP, connect to the primary NP. Do this by typing `. (backquote plus dot, that is, left single quote plus period) to connect to the TCS hub, and entering the following command (substituting the slot number of the primary NP for primary):

TCS HUB<<A>> connect primary

Step 2 If you are not already logged in to the primary NP as root, log in to the primary NP as root.

Step 3 If there is a redundant NP in this chassis, verify that the other NP is functioning as backup. Enter the following command:

bash# rsh other-np /bin/true

Three different results are possible:

No error message

bash# rsh other-np /bin/true 
bash# 

This result indicates success. The other NP is up and accessible. Return to the section that referred you to this special procedure.

Connection timed out (the timeout takes about 75 seconds)

bash# rsh other-np /bin/true 
other-np: connection timed out 
bash#

This result indicates that the backup NP is not up. Go to Step 4.

Permission denied

bash# rsh other-np /bin/true 
Permission denied. 
bash#

This result indicates that the backup NP is up, but not accessible due to a permissions mismatch. Go to Step 4.

Step 4 If you receive the error message bash#, reset the other NP using these steps:

Return to the TCS by typing `. (backquote plus dot, that is, left single quote plus period).

Reset the backup NP by typing the following (substituting the slot number of the backup NP for backup):

TCS HUB<<A>>reset backup

Connect to the backup NP by typing the following (substituting the slot number of the backup NP for backup):

TCS HUB<<A>>connect backup

Monitor the reboot, looking for the following two trap messages:

==> (OPER) NDD_2 at mm/dd/yy/ hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT) 
      Network Processor <node_name:slot> becoming backup np 
 
==> (GENERIC) at mm/dd/yy/ hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT) 
      Cold Start Trap at mm/dd/yy hh:mm:ss <time-zone> (mm/dd/yy hh:mm:ss GMT)

You may have to wait about 5 minutes for these traps to appear.

Reconnect to the primary NP. Repeat Step 3. If the same failure occurs, call Cisco Customer Support at 1-800-553-2447.

Step 5 You may receive the following error message:

Permission denied.

The message indicates the rsh permissions on the backup NP are incorrect.

Log in to the backup NP as root using rsh.

bash# rsh other-np 
login root vt100 
password: 
. 
. 
. 
bash# 

Verify that the file "/.rhosts" contains the line "other-np root" bash# grep
"other-np /.rhosts".
If this line is missing, add it with the following command:

bash# cp /.rhosts /.rhosts.bak 
bash# echo "other-np root" >>/.rhosts

Note Enter the redirect operator twice, with no space (>>). If you enter it once (>) you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /.rhosts.bak /.rhosts to recover the original file.


Log out of the backup NP. That leaves you connected to the primary NP again. Repeat Step 3. If the same failure occurs, verify that /etc/hosts is a symbolic link to /usr/etc/hosts, as in the example below:

sqatb45:ls -ls /etc | grep hosts
1 lr-------- 1 root 15 Dec  6 14:39 hosts -> /usr/etc/hosts

If /etc/hosts is not a symbolic link, it should be. If you are uncomfortable with making changes to system files, call Cisco Customer Support at 1-800-553-2447. Otherwise, you should verify that all information in /etc/hosts is also in /usr/etc/hosts. Verify that there is an entry for other-np in /usr/etc/hosts. Then create a symbolic link:

bash# mv /etc/hosts /etc/hosts.orig
bash# ln -s /usr/etc/hosts /etc/hosts
bash# grep /etc/hosts other-np

If the last command above returns a line like the example below, return to Step 3. If it fails to return anything, call Cisco Customer Support at 1-800-553-2447.

bash#:grep other-np /etc/hosts 
172.27.208.145   sqatb45-backup other-np

Special Procedure D, Troubleshooting rsh to on a Remote Node

Use this procedure if the rsh command reports an error message:


Step 1 On the distribution node, examine the file /etc/hosts and /usr/etc/hosts to verify that there is an entry for remote-node . You can use the grep command for this:

bash# grep remote-node /usr/etc/hosts

If there is an entry for remote-note, go to Step 3.

Step 2 If there is no entry for remote-node, create a backup copy of the /usr/etc/hosts file and then create an entry for remote-node in /usr/etc/hosts:

bash# cp /usr/etc/hosts /usr/etc/hosts.bak 
bash# echo "Primary_IP_address remote-node" >> /usr/etc/hosts

Enter the name of the remote node in place of remote-node, and enter the IP address of the remote node in place of Primary_IP_address. You can use the vi editor in place of the echo command. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.


Note Enter the redirect operator twice, with no space (>>). If you enter it once (>) you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /usr/etc/hosts.bak /usr/etc/hosts to recover the original file.


Repeat Step 1, and if successful, again attempt to rsh to <remote-node> bash# rsh <remote-node> host name. If successful, return to the section that referred you to this procedure.


Note If you see the error message "Connection Timed Out," the remote node or a link to it is down. Refer to the chapter entitled "Troubleshooting Procedures" in the LightStream 2020 Network Operations Guide. When the problem is corrected, repeat Step 1. If you see the error message "Permission Denied" or any other message, proceed with this procedure.


Step 3 Make a Telnet connection to remote-node and log in.

Step 4 Verify that the .rhosts file is a read-only file for group and world:

bash# ls -l /.rhosts 
-rw-r--r--   1 root         71 Aug  1 14:54 /.rhosts 

If any value other than -rw-r--r-- appears at the beginning of the ls output, enter:

bash# chmod 644 /.rhosts 

Step 5 Examine the file /.rhosts to see if it includes an entry for distribution-node. Use the following command (enter the name of the distribution node in place of distribution-node):

bash# grep distribution-node /.rhosts 

Step 6 If the entry for distribution-node is not displayed, edit the file /.rhosts, adding to it a line consisting of the name of the distribution node followed by the word root (enter the name of the distribution node in place of distribution-node):

bash# cp /.rhosts /.rhosts.bak 
bash# echo "distribution-node root" >> /.rhosts 

You can also use the vi editor in place of the echo command, if you wish. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.


Note Enter the redirect operator twice, with no space (>>). If you enter it once (>) you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /.rhosts.bak /.rhosts to recover the original file.


Step 7 On the remote node, examine the file /usr/etc/hosts to verify that there is an entry for distribution-node in it. Use the grep command for this (enter the name of the distribution node in place of distribution-node):

bash# grep distribution-node /usr/etc/hosts 

Step 8 If there is no entry for distribution-node, create one as follows:

bash# cp /usr/etc/hosts /usr/etc/hosts.bak 
bash# echo "Primary_IP_address distribution-node" >> /usr/etc/hosts 

Enter the IP address of the distribution node in place of Primary_IP_address, and the name of the distribution node in place of distribution-node. You may use the vi editor in place of the echo command. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.


Note Enter the redirect operator twice, with no space (>>). If you enter it once (>) you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /usr/etc/hosts.bak /usr/etc/hosts to recover the original file.


Step 9 Log out of the remote node and repeat Step 1.

If the test in fails again, contact Cisco Customer Support at 1-800-553-2447.

Special Procedure E, Backing Up the Distribution Diskettes

If you are concerned about how carefully your diskettes may be handled and stored, you may wish to back up the software distribution diskettes before proceeding with the upgrade.

Requirements for the Procedure

In this procedure, you must have access to a PC running DOS 5.0 and supporting at least one 1.44-MB floppy disk drive. You must also have at least 17 blank, DOS-formatted 1.44-MB diskettes.

You should also be aware of the following:

With the /v option, the diskcopy command verifies that the copy is correct. If you wish to use the diskcomp command redundantly to verify that the copy is correct, refer to your DOS documentation for that command.

Do not use the dir command to verify the contents of the diskette. There is no FAT (the DOS file allocation table) on LS2020 distribution diskettes, so there can be none on your backup diskettes. Consequently, if you enter dir a: or dir b:, you see a read error message issued by DOS.

If Your PC Has Two 1.44-MB Floppy Disk Drives

For each LS2020 software distribution diskette, perform the following:


Step 1 Insert the distribution diskette in the floppy disk drive. In the examples shown here, we assume this is disk drive A.

Step 2 Insert the blank, formatted diskette in the second 1.44 Mb disk drive. In the examples shown here, we assume this is disk drive B.

Step 3 Enter the following command at the DOS prompt:

C:\> diskcopy a: b: /v 

The program copies the data from the distribution diskette in drive A to the backup diskette in drive B.

If Your PC Has Just One 1.44-MB Floppy Disk Drive

For each LS2020 software distribution diskette, perform the following:


Step 1 Insert the distribution diskette in the floppy disk drive. In the example shown here, we assume this is disk drive A.

Step 2 Enter the following command at the DOS prompt:

C:\> diskcopy a: a: /v 

The program reads a portion of the disk contents into memory. When it prompts you to do so, remove the distribution diskette and insert a blank, formatted diskette into the floppy disk drive.

Step 3 The program copies the data from memory onto the diskette. When it prompts you to do so, remove the backup diskette and insert the distribution diskette into the floppy disk drive.

Step 4 Alternate disks in Step 3 in response to program prompts until the disk copy is complete.

Step 5 Select the next disk in the set and go to step 2.

Special Procedure F, Freeing Up Memory on an NP

Use this procedure when there is insufficient memory to run a software installation procedure on an NP.


Step 1 Log into the target NP. For swinstall, this is the local system. For swremoteinstall, this is the host to which you are installing to. Telnet to that host.

Step 2 Type ps -ax to determine which processes are running and how much memory needs to be freed. The amount of free memory is displayed in the last line of output. Each software procedure requires a different amount of memory to run to completion (see the related Note below). Here is a list of memory requirements for this release:

swinstall - 1650KB
swremoteinstall -  1000KB
swchgver -  1500KB

If 1650 K of memory is now free you can continue with the original software update procedure. If not, take the actions described in sections 3, 4, and 5 below, checking the amount of memory after each change until enough memory has been freed.


Note The check for available memory is performed within the installation script and therefore underestimates the amount of free memory available. In this release, this can be solved by freeing up 500KB more than requested by swinstall, swremoteinstall, or swchgver. The adjusted amount of memory for each procedure is swinstall 2150KB, swremoteinstall 1500KB, swchgver 2000KB.


Step 3 If there is too little memory free and if ps -ax reported that any cli process was active, then the CLI process must be stopped. Ideally, you can determine who is runing CLI and have them quit the tool. If this is not possible then CLI can be forcibly removed with the command "kill -9 <pid>", where <pid> is the process id for the CLI as reported by the ps command. Continue with Step 2.

Step 4 If there are no active CLI processes, it is possible that a number of different users have logged onto the NP using Telnet. Determine this with the who command. Ideally there are only one or two users logged into the node, depending on whether you are connected through the hub/console port or are logged in through Telnet. This is an example of running the who command on an NP:

# who
root      ttyp0     Unknown-HostName  Sun Jul 14 15:04:55
fldsup    ttyp1     191.254.254.254   Mon Jul 15 09:07:34
hewey     ttyp3     191.254.254.253   Mon Jul 15 09:07:34
dewey     ttyp4     191.254.254.155   Mon Jul 15 09:00:34
lewey     ttyp5     191.254.254.254   Mon Jul 15 09:05:34

In this case, asking hewey, dewey, and lewey to log out will free up some space. In general all users not involved with the software installation should log out.

Step 5 As a last resort, memory can be freed by deactivating a line card, thus freeing up its resources. To do this use the CLI set cardx inactive command on the target NP, where X is the card number to deactivate. IMPORTANT: If you deactivate a line card before software installation you will need to activate that line card once the software installation procedure is finished. Otherwise, the card will remain inactive, even following a reboot of the chassis. If a line card must be deactivated, once reactivated, Flash must be installed on that line card using the LynxOS command Fcload -s <slot #> -flash.

Workstation Upgrade Procedures

The procedures in this section explain how to install Software Release 2.3(1) network management software onto your UNIX workstation from the tape provided with this release.


Note If you are installing the StreamView software on a workstation for the first time, do not use these instructions. Refer instead to Chapter 3 of the LightStream 2020 Installation Guide.


When you complete one of the following upgrade procedures, you will be able to run the Software Release 2.3(1) StreamView network management software on your UNIX workstation:

Procedure 1, Upgrading StreamView Software Under HP OpenView

Procedure 2, Upgrading StreamView Software Without HP OpenView

For Information on º
See º

Running the configuration program

LightStream 2020 Configuration Guide

Running the CLI and the monitor

LightStream 2020 Network Operations Guide

CLI commands and the MIB

LightStream 2020 CLI Reference Manual

LynxOS commands

LightStream 2020 NP O/S Reference Manual



Note Refer to the LightStream 2020 Site Planning and Cabling Guide for a list of NMS hardware and software requirements.


Procedure 1, Upgrading StreamView Software Under HP OpenView

If you are installing the StreamView software without HP OpenView, go to "Procedure 2, Upgrading StreamView Software Without HP OpenView" section.

If you installed an earlier version of StreamView under HP OpenView, use this procedure to upgrade your installation to Software Release 2.3(1). You need to be running at least Version 3.3 of HP OpenView to run LS2020 management software under HP OpenView.

This LS2020 StreamView installation requires the HP OpenView OVIC utility version 1.4 or later. To verify the version number, execute the following command at the shell prompt on your UNIX workstation:

# cat /usr/OV/install/system/OVIC/ovindex

Release 1.4 is indicated by the line in this file.

Loading StreamView for HP OpenView

The StreamView network management software portion of the LS2020 software includes three modules: the configurator (cfg, pvc, vli), the monitor, and the topology map. The CLI and the LS2020 enterprise-specific MIB are packaged with all three StreamView modules.

When installing the network management software, use the ovinstall command to:

Check the HP OpenView installation utilities version

Create the /usr/OV/bin/ls_bin directory

Update several HP OpenView directories with LS2020 registration and bitmap files

Load the enterprise-specific MIB into the /usr/OV/snmp_mibs directory and install it under HP OpenView

Create the /usr/OV/databases/ls directory for the MIB database

To load the network management software, perform the following steps:


Step 1 Log in to the UNIX workstation as root. If logging in as root is disabled, issue the following command to give yourself root privileges:

$ su 
password:<root password>

Step 2 Create a user account called npadmin, if it does not already exist.

The CLI uses the password for the npadmin account as the password for the CLI protected mode. If no npadmin account has been defined for the workstation, the CLI uses the root password as the CLI protected-mode password.

Step 3 Ensure that the /usr/OV/bin directory is in your path (the installation procedure uses this directory). To display your path, issue the following command at the SunOS prompt:

# echo $PATH 

To set your path in a Bourne shell or a bash shell, issue the following command:

# PATH=$PATH:/usr/OV/bin 
# export PATH

To set your path in a C shell (csh), issue the following command:

# setenv PATH ${PATH}:/usr/OV/bin

The LS2020 StreamView installation requires the HP OpenView OVIC utility Version 1.4 or later. To verify the version number, execute the following command at the shell prompt on your UNIX workstation:

# cat /usr/OV/install/system/OVIC/ovindex

Release 1.4 is indicated by the line TCS HUB<<A>> in this file.

Step 4 Insert the tape containing the LS2020 software into the UNIX workstation tape drive.

Step 5 Extract the StreamView network management modules from the tape using the ovinstall command. This process takes from 5 to 15 minutes to install the modules and their associated files.


Note For an example of StreamView output generated using the HP OpenView commands, refer to the appendix "StreamView Output Samples."


To extract the StreamView configurator module, enter the following command:

# ovinstall -r -p LS-CONFIGURE - - -d <tape-drive>

<tape drive> is /dev/rst0, unless your tape drive has been configured to use a different device (for example, /dev/rst1 or /dev/rst2). The -r switch allows the program to overwrite an existing installation. If you specify an incorrect device in the ovinstall command, the installation process terminates immediately and returns the following message or its equivalent:

"ovinstall: cannot install product definition for LS-CONFIGURE"

Note The ovinstall command creates a log file named /tmp/update.log. If a problem occurs during the installation process, you can examine this file to determine the problem. To view this file, issue the following command: more /tmp/update.log.


To extract the StreamView monitor, enter the following command:

# ovinstall -r -p LS-MONITOR - - -d <tape-drive>

To extract the StreamView topology map software, enter the following:

# ovinstall -r -p LS-TOPOMAP -- -d <tape-drive> 

Step 6 Update the HP OpenView Fields database with StreamView fields using the following command:

# ovw -fields

Step 7 Verify that the network management software modules have been properly installed using the following command:

# ovw -verify

The verify program takes less than a minute to run and prints the names of the objects that it verifies. If the verification process fails, an error message displays on the screen. In this case, call your Cisco service representative for assistance.

Step 8 Check the status of HP OpenView daemons using the following command:

# ovstatus

If the ovstatus command returns the messagebash# enter the following command from user ID root to start OV daemons:

# ovstart

Step 9 Execute the xnmsnmpconf command at the shell prompt to update variables associated with the SNMP community.

This command displays the SNMP configuration screen. Double-click on the default parameters field (which contains default values in text fields). Modify the following field values to read as shown:

Port (remote)	161
Timeout	6.0
Retry	2 

The default polling interval is 5 minutes, which determines how long it will be before the display indicates changes in the network. Setting the polling interval to a value less than 5 minutes causes additional SNMP traffic to be generated and is, therefore, not advised.

By default, LS2020 nodes require the use of the write community for SNMP set operations, as indicated below:

set community: write

However, you may choose to use another name for the community that has read/write privileges, or you may choose to allow SNMP set operations from any community.

To allow such operations, however, you must configure the HP OpenView environment appropriately using the xnmsnmpconf command.

If you do not use the default communities, you must change the files at the LS2020 nodes to conform to the behavior of HP OpenView.

See the section "Changing Default SNMP Community Names" in the chapter "Set-up Procedures" in the LightStream 2020 Installation Guide.

Step 10 Verify that the /etc/services file contains the following lines:

snmp 	161/udp 
snmp-trap	162/udp

If these lines are not present in the /etc/services file, create them. To do so, as user ID root, open the /etc/services file.

Insert the and connection timed outlines in the appropriate location in the /etc/services file and close the file.

The installation of the network management software is now complete. The next section describes how to create a user environment to run network management software applications under HP OpenView.


Note If the user environment variables are not properly set, the software will not properly find or use the StreamView applications. It may be necessary to close all HP OpenView windows and restart HP OpenView with the correct environment.


Setting Up a User Environment Under HP OpenView

This section describes how to set up the StreamView applications to run under HP OpenView. Every user intending to run StreamView under HP OpenView must perform the procedures in this section.

These procedures assume that you have already installed the network management software applications on a UNIX workstation, as described in the preceding section, "Loading StreamView for HP OpenView" section.

This section provides instructions for setting up the user environment for the Bourne shell and its derivatives (sh and bash) and the C shell (csh). For clarity, the set-up procedures for the Bourne shells and the C shell are discussed under separate headings below.

Other shells may differ in details; in the case of another shell, consult the applicable documentation for that shell.

In preparation for setting up the user environment under HP OpenView, determine the type of shell each user is using.

In an NFS environment that uses the Network Information Services (NIS) facility, enter the following command:

# ypmatch <username> passwd

In an environment that does not use the NIS facility, enter the following command:

# egrep <username> /etc/passwd

The shell can be identified from the last field of the password entry, as shown in the following example:

jjones:o@elQMkzZv7o		F:10563:312:Jon Jones:/home/jjones:/bin/bash

Setting Environment Variables for Bourne Shell and Derivatives

To set up the StreamView software to operate under HP OpenView and the Bourne shells, sh and bash, perform the following procedures:


Step 1 From your home directory, edit the .profile file or the .bash_profile file that is read by the shell at login.

Add the following lines to the end of the file:

PATH=$PATH:/usr/OV/bin/ls_bin 
LSC_DATABASE=/usr/OV/databases/ls/configure.netdb 
LSC_CFGLOGPATH=/usr/OV/log 
LSC_CFGTCPPORT=6789 
XKEYSYMDB=<pathname>/XKeysymDB 
NMSROOT=<CiscoView location, if present>
XVTPATH=/usr/OV/bin/ls_bin
export PATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT XKEYSYMDB NMSROOT XVTPATH

Note To determine the <pathname> for TCS HUB<<A>> in the fourth line from the bottom, consult your system administrator. The file XKeysymDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeysymDB file. However, the search process may be lengthy and may disclose multiple copies of the file. Also, note the upper- and lower-case characters in the XKeysymDB filename; this case sensitivity is critical. If bash# rsh other-np login root vt100 password: . . . is incorrectly defined, that is, no file named XKeySymDB is found where bash# points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix under the heading "Error Output When XKEYSYMDB Is Undefined."


Step 2 Determine whether a UIDPATH variable is already set in your login environment by issuing the following command:

% echo $UIDPATH 

Step 3 If the system displays a search path in Step 2, add the following lines to the end of the .profile file or the .bash_profile file:

UIDPATH=$UIDPATH:/usr/OV/bin/ls_bin/%U 
export UIDPATH 

Otherwise, if the system displays the message or displays no message, add the following lines to the .profile file or the .bash_profile file:

UIDPATH=/usr/OV/bin/ls_bin/%U 
export UIDPATH 

Step 4 Determine whether an bash# variable is already set in your login environment by issuing the following command:

% echo $XFILESEARCHPATH 

Step 5 If the system displays a search path in Step 4, add the following line to the end of the .profile file or the .bash_profile file:

XFILESEARCHPATH=$XFILESEARCHPATH:/usr/OV/%T/%N%S 
export XFILESEARCHPATH 

Otherwise, if the system displays the message or displays no message, use the following command to check for the existence of the referenced directory.

% ls /usr/openwin/lib/app-defaults/ 

If this directory exists, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/openwin/lib/%T/%N%S:/usr/OV/%T/%N%S 
export XFILESEARCHPATH 

Use the following command to check that the referenced directory exists:

% ls /usr/lib/X11/app-defaults/ 

If the previous directory does not exist, but this directory does exist, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S 
export XFILESEARCHPATH 

If both of the above directories exist, add the following lines to the end of the .profile or .bash_profile file:

XFILESEARCHPATH=/usr/openwin/lib/%T/%N%S:/usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S 
export XFILESEARCHPATH 

If neither of the above directories exists, call your network administrator or Cisco Systems Customer Support for assistance.

Step 6 If this is a new HP OpenView user, check the user's home directory for the existence of the .Xdefaults file (or its equivalent .Xresources). If this file contains data, proceed with Step 7.

If this file exists but contains no data, append the contents of the /usr/OV/newconfig/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/OV/newconfig/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/OV/newconfig/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the LightStream 2020 Installation Guide , "StreamView Output Samples" appendix.

Step 7 Issue the following command from the UNIX workstation to start HP OpenView:

% ovw

If, after issuing the ovw command, the message cid: ov1.4 is returned, issue the following command:

% ovstatus 

This command reports the nature of the problem, as shown below:

ovstatus: ovspnd is not running; use ovstart to start ovspnd

Log in as root and issue the ovstart command as shown below:

# ovstart

As an alternative, if you want to start HP OpenView and run it in background mode while keeping the current window active, issue the following command:

% ovw&

In background mode, the ovw process is fully usable.


Note If LS2020 applications are invoked from within HP OpenView, such applications inherit the environment and privileges of the user account from which the ovw command is issued. When the StreamView configurator is invoked under HP OpenView, the access permissions for the configuration database file created by this module correspond to the privileges of the user issuing the ovw command.


Step 8 If the following error message appears in the parent window from which you started HP OpenView in Step 8, the cid: ov1.4 is not set correctly:

ovw: Xt Warning: Cannot convert string "helvr14" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr12" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr10" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr08" to type FontStruct

Shut down HP OpenView, revert to Step 5 above, and add ovstatus: ovspnd is not running; use ovstart to start ovspnd,to the Port (remote) 161 . Continue from that point with Step 9 and Step 7 to restart HP OpenView.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by Timeout 6.0 , taking on the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not in the same group, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read/write access privileges to the file configure.netdb:

# cd /usr/OV/databases/ls
# chgrp <ops-group> configure.netdb

where ops-group is the value of the group to be used on the system.

Step 9 Any HP OpenView user logged in during the installation process should now log out and log in again to use the new environment variables.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. For more information about the StreamViw environment check utility, see the LightStream 2020 Installation Guide.

Setting Environment Variables for C Shell and Derivatives

To set up network management software to operate under HP OpenView and the C shell, perform the following steps:


Step 1 From your home directory, edit the .cshrc file that is read by the C shell on login. Add the following lines to the end of the file:

setenv PATH ${PATH}:/usr/OV/bin/ls_bin 
setenv LSC_DATABASE /usr/OV/databases/ls/configure.netdb 
setenv LSC_CFGLOGPATH /usr/OV/log 
setenv LSC_CFGTCPPORT 6789 
setenv XKEYSYMDB <pathname>/XKeysymDB 
setenv NMSROOT <CiscoView location, if present> 
setenv XVTPATH /usr/OV/bin/ls_bin

Note To determine the <pathname> for Retry 2 in the third to last line above, consult your system administrator. The file snmp 161/udp should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the snmp-trap 162/udp file. However, be aware that the search process may be lengthy and find multiple copies of the file. Also, note the upper- and lower-case conventions in the XKEYSYMDB file name; this case sensitivity is critical. If XKEYSYMDB is incorrectly defined, that is, no file named XKEYSYMDB is found where UIDPATH: unbound variable points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide "StreamView Output Samples" appendix under the heading "Error Output When XKEYSYMDB Is Undefined."


Step 2 Determine whether a XFILESEARCHPATH variable is already set in your login environment by issuing the following command:

% echo $UIDPATH

Step 3 If the system displays a search path in Step 2, add the following line to the end of the .cshrc file:

setenv UIDPATH ${UIDPATH}:/usr/OV/bin/ls_bin/%U

Otherwise, if the system displays the message XFILESEARCHPATH: unbound variable or displays no message, add the following line to the end of the .cshrc file:

setenv UIDPATH /usr/OV/bin/ls_bin/%U

Step 4 Determine whether an ovw: cannot connect to database variable is already set in your login environment by issuing the following command:

% echo $XFILESEARCHPATH

Step 5 If the system displays a search path in Step 4, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH ${XFILESEARCHPATH}:/usr/OV/%T/%N%S

Otherwise, if the system displays the message XFILESEARCHPATHor displays no message, use the following command to check that the following directory:

% ls /usr/openwin/lib/app-defaults/

If this directory exists, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/openwin/lib/%T/%N%S:/usr/OV/%T/%N%S

Use the following commands to check for the existence of the referenced directory:

% ls /usr/lib/X11/app-defaults/

If the first directory does not exist, but this second directory does exist, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/lib/X11/%T/%N%S:/usr/OV/%T/%N%S

If both of the directories exist, add the following line to the end of the .cshrc file:

setenv XFILESEARCHPATH /usr/openwin/lib/%T/%N%S:/usr/lib/X11/%T/%N%S:\ /usr/OV/%T/%N%S

If neither of the directories exist, call your network administrator or Cisco Systems Customer Support for assistance.

Step 6 If this is a new HP OpenView user, check the user's home directory for the existence of the .Xdefaults file (or its equivalent .Xresources). If this file contains data, proceed with Step 7.

If this file exists but contains no data, append the contents of the /usr/OV/newconfig/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/OV/newconfig/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/OV/newconfig/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the appendix "StreamView Output Samples."

Step 7 Issue the following command from the UNIX workstation to start HP OpenView:

% ovw

If, after issuing the ovw command, the message /usr/OV/%T/%N%S is returned, issue the following command:

% ovstatus 

This command reports the nature of the problem, as shown below:

ovstatus: ovspnd is not running; use ovstart to start ovspnd

Login as root and issue the ovstart command, as shown below:

# ovstart

As an alternative, if you want to start HP OpenView and run it in background mode while keeping the current window active, issue the following command:

% ovw&

In background mode, the ovw process is fully usable.


Note If you invoke LS2020 applications from within HP OpenView, the applications inherit the environment and privileges of the user account from which the ovw command is issued. When the StreamView configurator is invoked under HP OpenView, the access permissions for the configuration database file created by this module correspond to the privileges of the user issuing the ovw command.


Step 8 If the following error message appears in the parent window from which you started HP OpenView in Step 7, the XFILESEARCHPATH is not set correctly:

ovw: Xt Warning: Cannot convert string "helvr14" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr12" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr10" to type FontStruct
ovw: Xt Warning: Cannot convert string "helvr08" to type FontStruct

In this case, shut down HP OpenView, revert to Step 5, and add LSC_DATABASE to the XKEYSYMDB. Continue from that point with Step 9 and Step 7 to restart HP OpenView.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by XKeysymDB. It has the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If not, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read-write access privileges to the file configure.netdb:

# cd /usr/OV/databases/ls
# chgrp <ops-group> configure.netdb

where ops-group is the value of the group to be used on the system.

Step 9 Any HP OpenView user logged in during the installation process should now log out and log in again to use the new environment variables.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. For more information about the StreamView environment check utility, see the LightStream 2020 Installation Guide.

Procedure 2, Upgrading StreamView Software Without HP OpenView

If you installed an earlier version of StreamView without HP OpenView, use this procedure to upgrade your installation to Software Release 2.3(1).

Loading StreamView Without HP OpenView

Without HP OpenView, the StreamView software portion of the LS2020 software includes two modules: the configurator, and the monitor. The CLI and the LS2020 enterprise-specific MIB are packaged with all three network management software modules.

To install the StreamView network management software applications to operate stand-alone without HP OpenView, perform the following steps:


Step 1 Log in to the UNIX workstation as root.


Step 1 Create a user account called npadmin, if one does not already exist.

The CLI uses the password for the npadmin account as the password for the CLI protected mode. If no npadmin account is defined for the UNIX workstation, the CLI uses the root password as the CLI protected mode password.

Step 2 Back up your ovsnmp.conf file if you have customized your existing configuration files and you wish to preserve them for a subsequent installation or upgrade of the network management software.

For example, if you have already installed Release 2.3.1 of the network management software in a non-HP OpenView environment and you need to re-install the software for some reason, you should first back up any configuration files you have customized since the previous installation.

Specifically, if you customize the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, you should save a backup copy of this file and restore it after the installation has been completed (see Step 7).

To back up the ovsnmp.conf file, change to the proper directory and copy the configuration file.

# cd /usr/LightStream-2.3.1/templates 
# cp ovsnmp.conf ovsnmp.conf.custom

Issue the list (ls) command to display the existing configuration files, as shown below:

# ls ovsnmp.conf*

This command lists the following configuration files:

ovsnmp.conf
ovsnmp.conf.custom

Step 3 Change to the root directory by issuing the following command:

# cd /

Step 4 Insert the LS2020 StreamView network management software tape into the UNIX workstation tape drive.

Step 5 Issue the following commands in the order shown to rewind, fast forward to the proper location and extract the files from tape:

# mt -f <tape-drive> rew 
# mt -f <tape-drive> fsf 4 
# tar xvpf <tape-drive>

<tape-drive> is /dev/nrst0, unless your tape drive has been configured to use a different port, for example, /dev/nrst1, or /dev/nrst2.


Note It is important to include the letter n "no rewind" as the leading character in the tape drive parameter (for example, nrst0 for <tape drive> rst0). If you omit this character, you will not be able to read the tape.


The extraction process, which takes from 10 to 20 minutes to complete, creates the following directory structures:

/usr/LightStream-2.3.1 
/usr/LightStream-2.3.1/bin 
/usr/LightStream-2.3.1/db 
/usr/LightStream-2.3.1/etc 
/usr/LightStream-2.3.1/hyperhelp 
/usr/LightStream-2.3.1/lib 
/usr/LightStream-2.3.1/log 
/usr/LightStream-2.3.1/mib 
/usr/LightStream-2.3.1/templates

Step 6 Restore your ovsnmp.conf file, if necessary.

If you saved a backup copy of your ovsnmp.conf file in Step 3, determine whether differences exist between your backup copy of the ovsnmp.conf.custom file and the new ovsnmp.conf file.

If no differences between these files are reported, the files are identical. On the other hand, if differences are reported, save the distribution copy of the ovsnmp.conf file by issuing the following command:

# mv ovsnmp.conf ovsnmp.conf.orig

Copy your custom configuration file to ovsnmp.conf by issuing the following command:

# cp ovsnmp.conf.custom ovsnmp.conf

Verify your file listing:

# ls ovsnmp.conf* 
 
	ovsnmp.conf 
	ovsnmp.conf.custom 
	ovsnmp.conf.orig 

Step 7 Edit the /etc/services file.Verify that the /etc/services file contains the following entries:

snmp	161/udp 
snmp-trap	162/udp

If this entry is not present in the /etc/services file, create the entries and close the file.

The installation of the network management software is now complete. The next section describes how to set up the UNIX workstation environment for using network management software in a non-HP OpenView environment.

Setting Up a User Environment Without HP OpenView

This section describes how to set up the StreamView application to run on the UNIX workstation without HP OpenView. Each LS2020 user intending to run StreamView on the UNIX workstation without HP OpenView must complete the procedures in this section.

It is assumed that you have already installed the StreamView application on a UNIX workstation to operate without HP OpenView, as described in the preceding section, " Procedure 2, Upgrading StreamView Software Without HP OpenView."


Note Release 2.3.1 is in a new directory structure. Existing users must update their environmental settings.


This section provides instructions for setting up the StreamView user environment for the Bourne shell and its derivatives (sh and bash) and the C shell (csh). For convenience and clarity, the set-up procedures for these shells are described under separate headings below.

Note that other shells may differ in details; in the case of another shell, consult the appropriate shell documentation for additional information.

Determine which type of shell to use:

In an NFS environment using the Network Information Services (NIS) facility, enter the following command:

ypmatch <username> passwd 

In an environment that does not use the NIS facility, enter the following command:

egrep <username> /etc/passwd 

The last field of the output that results from either of the above commands identifies the shell in use, as shown in the following example:

jjones:o@elQMkzZv7oF:10563:312:Jon Jones:/home/jjones:/bin/bash

Setting Environment Variables for Bourne Shell and Derivatives

To set up the StreamView software to operate without HP OpenView under the Bourne shells, sh and bash, perform the following procedures:


Step 1 Each StreamView user must define several environment variables. To do so, go to your home directory and edit the .profile file or the .bash_profile file that the Bourne shell reads on login.

Step 2 Determine whether a XKeysymDB variable is already set in your login environment by entering the following command:

% echo $UIDPATH

Step 3 If the system displays a search path in Step 4, add the following lines to the end of the .profile file or the .bash_profile file:

PATH=$PATH:/usr/LightStream-2.3.1/bin  
UIDPATH=$UIDPATH:/usr/LightStream-2.3.1/bin/%U 
LSC_DATABASE=/usr/LightStream-2.3.1/db/configure.netdb 
LSC_CFGLOGPATH=/usr/LightStream-2.3.1/log 
LSC_CFGTCPPORT=6789 
OVSNMP_CONF_FILE=/usr/LightStream-2.3.1/templates/ovsnmp.conf 
XKEYSYMDB=<pathname>/XKeysymDB 
XVTPATH=/usr/LightStream-2.3.1/bin 
export PATH UIDPATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT OVSNMP_CONF_FILE\ XKEYSYMDB 
XVTPATH

Note To determine the <pathname> for XKeysymDB shown in the Bourne shell procedures below, consult your system administrator. The file XKEYSYMDB should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XKeySymDB file. However, be aware that the search process may be lengthy and may disclose multiple copies of the file. Also, note the upper- and lower-case characters in the XKEYSYMDBfilename; this case sensitivity is critical. If UIDPATH is incorrectly defined, that is, no file named UIDPATH: Undefined variable is found where XFILESEARCHPATH points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide "StreamView Output Samples" appendix under the heading "Error Output When XKEYSYMDB Is Undefined."


After adding the data called for in this step to the appropriate file, skip to Step 7.

Step 4 If the system displaysXFILESEARCHPATH: undefined variable or no message in response to the ovw: cannot connect to database command, add the following lines to the end of the .profile file or the .bash_profile file:


Note Path is order sensitive. If multiple StreamViews are in path, the first one will be executed.


PATH=$PATH:/usr/LightStream-2.3.1/bin 
UIDPATH=/usr/LightStream-2.3.1/bin/%U 
LSC_DATABASE=/usr/LightStream-2.3.1/db/configure.netdb 
LSC_CFGLOGPATH=/usr/LightStream-2.3.1/log 
LSC_CFGTCPPORT=6789 
OVSNMP_CONF_FILE=/usr/LightStream-2.3.1/templates/ovsnmp.conf 
XKEYSYMDB=<pathname>/XKeysymDB 
XVTPATH=/usr/LightStream-2.3.1/bin 
export PATH UIDPATH LSC_DATABASE LSC_CFGLOGPATH LSC_CFGTCPPORT OVSNMP_CONF_FILE\ XKEYSYMDB 
XVTPATH

Continue with Step 7.

Step 5 Check the user's home directory for the existence of the .Xdefaults file. If this file is present and contains data, skip to Step 6.

If this file exists but contains no data, append the contents of the /usr/LightStream-2.3.1/templates/xdefaults file to the user's .Xdefaults file by issuing the following commands:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/LightStream-2.3.1/templates/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/LightStream-2.3.1/templates/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the appendix "StreamView Output Samples."

Step 6 By default, LS2020 nodes require the use of the write community for SNMP set operations. You may choose to use another name for your community with read/write access privileges, or you may choose to allow SNMP set operations from any community.

For StreamView to successfully read and write to an LS2020, the StreamView community strings must match the strings defined on the LS2020 itself.

If you change the community name, you must kill the cfg_a process for the changes to take effect. The process will be restarted the next time you download a configuration.

To kill the cfg_a process, peform the following:

a. Log in as root.

b. At the prompt, type:

% ps -ax | grep cfg_a

c. Find the PID number for the cfg_a in the resulting display, then type:

% kill -9 <pid# of cfg_a>

Note If you change a community name in the ovsnmp.conf file you must also change the community name on the LS2020 node. For more information about changing community names, see the LightStream 2020 Installation Guide.


To configure this snmp communities option in a UNIX workstation environment, edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, or change the files at each LS2020 node to conform to your workstation's behavior.

See the section "Changing Default SNMP Community Names" in the chapter "Set-up Procedures" for information about setting up SNMP communities in an LS2020 network. Use a text editor such as emacs or vi to modify the file /usr/LightStream-2.3.1/templates/ovsnmp.conf. The file itself contains instructions for formatting each entry.

Step 7 Any user logged in during the installation and configuration process should now log out and log in again to activate the new environment variables.

Note that the first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by LSC_DATABASE, with the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not in the same group, users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has the required read/write access privileges to the file configure.netdb:

# cd /usr/LightStream-2.3.1/db
# chgrp <ops-group> configure.netdb

where ops-group represents the value of the group to be used on the system.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file.

Setting Environment Variables for C Shell and Derivatives

To set up the StreamView software to operate without HP OpenView under the C shell, perform the following steps:


Step 1 From your home directory, edit the .cshrc file that is read by the C shell on login. Add the following lines to the end of the file:

setenv PATH ${PATH}:/usr/LightStream-2.3.1/bin 
setenv LSC_DATABASE /usr/LightStream-2.3.1/db/configure.netdb 
setenv LSC_CFGLOGPATH /usr/LightStream-2.3.1/log 
setenv LSC_CFGTCPPORT 6789 
setenv OVSNMP_CONF_FILE /usr/LightStream-2.3.1/templates/ovsnmp.conf 
setenv XKEYSYMDB <pathname>/XKeysymDB 
setenv XVTPATH /usr/LightStream-2.3.1/bin


Note To determine the# for XFILESEARCHPATH in the second to last line above, consult your system administrator. The file /usr/OV/%T/%N%S should be in the subdirectory lib, lib/X11, or /usr/openwin/lib under the directory containing your X Windows executables. You can use the command find / -name XKeysymDB -print to search for the XFILESEARCHPATH file. However, be aware that the search process may be lengthy and find multiple copies of the file. Also, note the upper- and lower-case conventions in the LSC_DATABASE file name; this case sensitivity is critical. If UIDPATH is incorrectly defined, that is, no file named XKEYSYMDB is found where XKeysymDB points, error output is directed to the standard error output device (STDERR). A sample of such output is shown in the LightStream 2020 Installation Guide "StreamView Output Samples" appendix under the heading "Error Output When XKEYSYMDB Is Undefined."


Step 2 Determine whether a XKeysymDB variable is already set in your login environment by issuing the following command:

% echo $UIDPATH

If the system displays the message XKeysymDB or displays no message, add the following line to the end of the .cshrc file:

setenv UIDPATH /usr/LightStream-2.3.1/bin/%U

Step 3 If the system displays a search path in Step 2, add the following line to the end of the .cshrc file:

setenv UIDPATH ${UIDPATH}:/usr/LightStream-2.3.1/bin/%U 

Step 4 Check the user's home directory for the existence of the .Xdefaults file (or its equivalent .Xresources). If this file contains data, proceed with Step 5.

If this file exists but contains no data, append the contents of the /usr/LightStream-2.3.1/templates/xdefaults file to the user's .Xdefaults file by issuing the following command sequence:

% mv .Xdefaults Xdef.sav
% cat Xdef.sav /usr/LightStream-2.3.1/templates/xdefaults > .Xdefaults

This step gives you access to the screen fonts and application colors needed for display purposes.

If you need to revert to the old .Xdefaults file, you can find its contents in the backup file Xdef.sav.

If the .Xdefaults file does not exist in the user's home directory, issue the following command to create it:

% cp /usr/LightStream-2.3.1/templates/xdefaults .Xdefaults

A sample .Xdefaults file is shown in the appendix "StreamView Output Samples."

Step 5 By default, LS2020 nodes require the use of the write community for SNMP set operations. You may choose to use another name for your community with read/write access privileges, or you may choose to allow SNMP set operations from any community.

If you change the community name, you must kill the cfg_a process for the changes to take effect. The process will be restarted the next time you download a configuration.

To kill the cfg_a process, perform the following:

a. Log in as root.

b. At the prompt, type:

% ps -ax|grep cfg_a

c. Find the PID numberfor the cfg_a in the resulting display, then type:

% kill -9 <pid# of cfg_a>

Note If you change a community name in the ovsnmp.conf file you must also change the community name on the LS2020 node. For more information about changing community names, refer to the chapter "Set-up Procedures."


To configure this option in your UNIX environment, edit the file /usr/LightStream-2.3.1/templates/ovsnmp.conf, or change the files at each LS2020 node to conform to your workstation's behavior.

Refer to the section "Changing Default SNMP Community Names" in the chapter "Set-up Procedures" for information about setting up SNMP communities in an LS2020 network. Use a text editor such as emacs or vi to modify the file /usr/LightStream-2.3.1/templates/ovsnmp.conf. The file itself contains instructions for formatting each entry.

Step 6 Any user logged in during the installation and configuration process should now log out and log in again to use the new environment variables.

The first time the StreamView configurator tool (cfg) is executed, the database is created automatically with the name specified by XKEYSYMDBtaking on the extensions .dir and .pag and the file permissions of the first user.

All users who will create or modify LS2020 node configurations must be in the same UNIX group. If they are not, such users will be limited to read-only access to the database and, therefore, will not be able to update LS2020 nodes with configuration information from the global database.

For example, if the operations group has read-only access to the global database, user ID root should issue the following commands to ensure that the operations group has required read/write access privileges to the file configure.netdb:

# cd /usr/LightStream-2.3.1/db
# chgrp <ops-group> configure.netdb

where ops-group represents the value of the group to be used on the system.

A new feature in Software Release 2.3.1 is the StreamView environment check utility. It checks for correct settings of environment variables in the user's environment. The utility reports status, any warnings, and any fatal errors in a log file. For more information about the StreamView environment check utility, see the LightStream 2020 Installation Guide.

Fallback to the Previous Software Version

This procedure provides instructions to fall back to a previous software version.
If you are running StreamView from /usr/OV, and you wish to fall back to the previous release, enter the following information:

cd /usr/LightStream-2.3.1/bin 
ls -ls | grep bin	# Find all files containing "bin" in the name. 
	# This should return your backup executable 
	# directory, for example, bin-2.3.1. Move 
	# the directory back over the new directory.  
mv bin-2.3.1 bin	# This restores your prior release executables.

Special Considerations

This section describes the special considerations that apply to software release 2.3(1) of the LS2020 multiservice ATM switch. These special considerations are drawn from reports of hands-on experience with the product by LS2020 customers and Cisco Systems engineers.

Most of the special considerations here are provided with an LS2020 defect number. If you contact Cisco Systems about a special consideration, please refer to it by its defect number.

Special Considerations are listed by their defect number in the following subsections:

Congestion Avoidance

Documentation

Firmware

Hardware and Diagnostics

Installation, Upgrade, and Initial Configuration

Internetworking

Network Management

Other

Platform

Resource Allocation

Traps

Congestion Avoidance

Congestion Avoidance (CA) Not Enforced for Point-to-Multipoint Circuits

Traffic entering the network on point-to-multipoint circuits is not throttled at entry ports when congestion starts to build within the network. A consequence of this is that CA more severely throttles unicast traffic at entry ports. The effect is to give multicast traffic priority over the unicast traffic.

Switch Bandwidth is Not Taken Into Account for Call Admission

Switch bandwidth is not taken into account in call admission decisions. Each line card has a 200 Mbs path (called its switch path) into the node switch. The cards are designed so that all port cards can run at line rate without overrunning the card switch path when all circuits through the ports are unicast circuits. Prior to the introduction of the Release 2.1 multicast feature it was unnecessary to take switch bandwidth into account in making call admission decisions because it was not possible to overcommit the card switch path.

When a multicast circuit branches at a node, incoming data is replicated for each branch at the card's switch path. Because Release 2.1 call admission does not take card switch path bandwidth into account, the following abnormal behavior is possible:

A multicast circuit can be established that cannot possibly carry the requested bandwidth. Consider, for example, a 40 Mbps guaranteed circuit over an FDDI LAN interface branching to five other FDDI LAN interfaces (requiring 240 Mbps from the switch). This circuit would drop cells at the card switch path when attempting to carry sustained traffic at the allocated rate.

The 200 Mbs switch path can become a congestion point if its bandwidth is overallocated; that is, if each individual circuit fits but they all do not fit together. Unlike trunks and exit ports, the card switch path is not protected by the CA mechanism. Therefore, the onset of congestion on the switch path does not force drops at the entry edges to eliminate the congestion. As a result, individual cells from packets would be dropped at the congested card switch path.

When there is congestion on a card switch path, there is no mechanism to drop best effort traffic ahead of insured traffic. The cell CLP bit, the XCLP bit, and cell transfer priority are all ignored in the identification of cells to drop. This affects Unicast insured traffic as well as multicast insured traffic. No impact is likely on guaranteed traffic and higher priority traffic (such as CBR) in an operational setting.

These limitations will be addressed in a future release.

LSCle02064 LAN Packet Flooding Performance

A LS2020 node can flood between 70 and 100 packets per second (depending on the node and network configuration) by means of its general purpose flooding mechanism.

Recommended Action

If higher packet flooding performance is required, configure a multicast group for the flooding. With adequate network capacity the LS2020 multicast feature can support flooding at up to LAN port rates.

Documentation

LSCle05036 Response timeout increases with each retry in ovsnmp.conf

In the ovnsmp.conf file specified by the OVSNMP_CONF_FILE environmental variable, the response timeout for each retry increases. For example, the line format in an ovsnmp.conf file is:

a:b:*:c:d:300:e:f:

in which#

a = IP address to match

b = Community string to use for SNMP Get Requests

c = SNMP response timeout in tenths of a second.

d = SNMP retry count

e = remote port number (standard value is 161)

f = Community string to use for SNMP Set Requests

An example is: *.*.*.*:public:*:70:5:300:161:write:

Will match any IP address, use "public" as the Community string for performing SNMP Get Requests, SNMP response timeout = 7 seconds, SNMP retry count = 5, "write" will be used as the Community string for performing SNMP Set Requests.

Now try using this line: *.*.*.*:bad:*:100:1:300:161:write:

This will use "bad" as the get string, 10 seconds for a response timeout, with 1 retry. "bad" is not a valid get string in the chassis's communities list, so doing a Verify should eventually time out. In this case, it should timeout after 10 seconds, and it does. However, changing the retry count and redoing a Verify causes timeouts to occur much later than expected. See chart below:

Response Timeout Value
Retry Count
Timed Out at

100 (10 sec)

1

10 sec

100 (10 sec)

2

30 sec

100 (10 sec)

3

70 sec

100 (10 sec)

4

130 sec

100 (10 sec)

5

210 sec

100 (10 sec)

6

310 sec


LSCle05188 Running "cfg_a -display_check" causes Sparc20 to reboot

When a user manually runs cfg_a with the -display_check option, the workstation may crash and reboot. The crash/reboot was caused by a corrupt database.

Recommended Action

The following Sun OS patches will prevent this problem: 102264-02, 102544-02, and 100444-76.

LSCle05457 CRC errors on an a trunk not reported to CLI statistics

CRC errors on a trunk not reported to CLI statistics. CRC errors were being reported on an MS trunk ports which was sufficient to prevent swremoteinstalls over those trunk ports, yet there was no indication of errors on the cli statistics. The trunk appeared to be up and functional. For further information, see LSCle05429.

Workaround

Use swaccstats to debug problems with swremoteinstall.

Firmware

There are no firmware special considerations for Software Release 2.3(1).

Hardware and Diagnostics

LSCle02440 8-Port T3 Card Does Not Report Loss of Signal (LOS)

The hardware is unable to report LOS because of the line interface unit (LIU) chip used in the T3 card's front end circuitry. The LIU chip has a very sensitive receiver capable of detecting signals down to 35mV. This allows the card to detect signals over long distances or very poor grade coaxial cables.

Because of this receiver sensitivity, the LIU picks up noise when there is no signal on the line, and continuously resets the LOS detection circuit, with the result that LOS status is never reliably set.

A newer version of the LIU device will be available in the future. Until then when the hardware detects a loss of frame (LOF) condition, a LOS condition will also be reported.

LSCle02741 Diagnostics May Fail Test 70 on a Medium-Speed Line Card

The diagnostics software does not set the card up properly for this test, and it fails intermittently.

Recommended Action

Either deselect test 70 when running the diagnostics on a medium-speed line card, or ignore failures of test 70.

LSCle03113 8t3 Loss of signal is unreliable for nettime line failure detection

The transwitch ART on the 8t3 card cannot accurately detect loss of signal. Therefore, do not use a 8t3 port as a nettime source until the new revision of the transwitch ART arrives.

LSCle03233 Flash Installation May Fail on Linecards that Fail POST

When upgrading flash (for instance, when inserting a spare card into a running system), the fcload -flash command may fail if the card is failing its power-on self test. The following fragment displays such a sequence:

fcload: (ls2_1_1) compiled Dec 13 1995 @ 22:14:26 [version 1.82.2.3]
...
fcload: slot 3: NOTE: post failed.
fcload: slot 3: begin load of flash image (/usr/fware/flash_clc1.rec) through switch
[WARNING: DO NOT INTERRUPT]
fcload: slot 3: putting card into TESTING mode for flash upgrade.
fcload: slot 3: waiting for remote SWACC loader to initialize:.Failed
fcload: SWACC loader on slot 3 failed to run
fcload: slot 3: failed to load "/usr/fware/flash_clc1.rec" via the switch flash
fcload: slot 3: disabling switch interface...

Recommended Action

Load the card using the -t switch (to force the load to occur over the TCS channel):

fcload -s <slot_number> -flash -force -t 

Using the TCS will take approximately 15 minutes per card.

LSCle05519 8SAC test 55.13 fails when using X.21 fantail

PLC/8SAC Diagnostic Test 55.13 (Serial_Octart_Ext_Loopback_Test) will fail if the PLC/8SAC is connected to an X.21 fantail. This test was not designed to operate with an X.21 fantail (RS449 and V.35 only).

Workaround

a. Ignore failures associated with 55.13 under the conditions described above.

b. Do not select test 55.13 for execution under the coditions described above.

LSCle05527 NP POST incorrectly adjusts TEMP2 WARNING value

NP POST for release 2.1(1.93), 2.1(1.94), 2.3(1) incorrectly adjusts the TEMP2 WARNING value for the bottom temperature sensor to 0x86. This translates to 131 degrees F (55 C). The correct TEMP2 WARNING value should be 0x93, which translates to 143 degrees F (61 C).

Workaround

If the system is operating in an environment where the ambient room temperature exceeds 86 degrees F (30 C), the bottom temperature sensor may detect a temperature that exceeds the TEMP2 WARNING threshold. The trap message associated with the TEMP2 WARNING condition could be disabled, but this is not a Cisco recommended work around.

Installation, Upgrade, and Initial Configuration

LSCle00710 Procedure for Checking Software on the Backup NP

When verifying a software installation using the ckswinstall utility on a redundant-NP system, the software installation on each of the two NPs must be checked explicitly.

Recommended Action


Step 1 Run ckswinstall on the current primary NP.

Step 2 Run ckswinstall on the current backup NP.

LSnode:2#  rsh other-np ckswinstall ...

LSCle01015 Fallback from swchgver Does Not Copy Configuration Files Back

LS2020 configuration information is stored on disk as part of a specific release. When a new release is installed, configuration information from an old release is copied forward to the new release as part of the installation process. Configuration information, however, is not automatically copied between releases when swchgver is used to change the current release.

For instance, if a node is upgraded to run new software, configuration changes are made, and then the node is downgraded to a previous release, the node is running with the configuration information that was cached at the time of the upgrade, which does not include the subsequent changes.

Recommended Action

Before fallhack, use the older version of StreamView to verify all node and circuit parameters. After falling back to an old version, download the current configuration to the node from the StreamView tools.

Alternatively, before falling back to an old version, copy the files in /usr/app/base-newrel/config to /usr/app/base-oldrel/config before the fallback (replace newrel and oldrel with the appropriate release numbers, such as 2.1.1 and 2.0.8).

LSCle02863 The setsnmpconfig Script May Fail if Configuration Database is Locked

When a switch is booted, if it detects that the minimum required configuration information is missing, it runs the setsnmpconfig script and prompts you for configuration information. If you supply the minimum node configuration information, and later discover that this information is not in the configuration database, it may be because the configuration database lock was set when setsnmpconfig was started.

Recommended Action

While logged in as root, use the following commands to delete the configuration database lock and run setsnmpconfig manually:

LSNode:1# rm /usr/app/base/config/configure.netdb.lock 
LSNode:1# setsnmpconfig

LSCle02869 Cannot Execute swinstall After it Fails Once Due to Disk Read Error

The swinstall utility fails if the /mnt mount is in use. This may come about because of a disk read error in a previous invocation of swinstall. For example, due to a media error.

Recommended Action

Unmount the floppy drive with the command umount /mnt, and then run swinstall again.

Internetworking

Hot Standby Routing Protocol (HSRP) Enhancement for LS2020 FDDI cards

In previous releases, the HSRP protocol did not work properly in a configuration where the LS2020 is operating as a bridge between 2 AGS+ or 7000 series FDDI routers.

Cisco AGS+ and 7000 series routers execute HSRP for the purposes of quickly recognizing and recovering from a router problem in a network. The HSRP protocol will define routers as either "active" or "standby", assign a priority, and establish a preempt strategy. Throughout this process, routers may change their MAC addresses relative to their HSRP assignments. Currently, Cisco AGS+ and 7000 series routers bring a FDDI port up and down in order to change a MAC address.

The LS2020, operating as a bridge, performs Spanning Tree (802.1) for all active LAN ports. Each time a port is brought down, the LS2020 initiates the Spanning Tree learn process and blocks traffic for a period of time. This blocking period disallows these routers from establishing an HSRP relationship. As the HSRP initialization process continues, the FDDI ports on both the HSRP routers and LS2020 continue to go up and down.The HSRP Enhancement corrects this interoperability issue.

Implementation of lsLanPortHsrpDelay MIB variable

An HSRP MIB variable has been added to the LS2020 private MIB. When the variable is set, the LS2020 FDDI line card will delay initiation of the Spanning Tree learn operation for a period of milliseconds after a FDDI link down state has been detected. The delay time will be programmable via the HSRP MIB variable. This delay will allow the FDDI ring to come back up, allowing neighboring HSRP routers to initialize properly. The LS2020 will not re-initialize Spanning Tree for that port if the ring comes back up within the delay period. In all cases, the FDDI up/down state transition will be reported to the LS2020 trap log. If FDDI port stays down longer than programmed delay time, the LS2020 will go through normal Spanning Tree re-initialization for that port.

Using lsLanPortHsrpDelay MIB variable

The HSRP private MIB variable allows the user to set a delay period for an LS2020 FDDI port. The characteristics of the MIB variable are listed below:


                MIB Variable Name:  lsLanPortHsrpDelay
                Data Type:          Integer
                Default Value:      0 (no delay, for non-HSRP configurations)
                Range:              0 thru 2000.  Value indicates the number 
                                        of milliseconds to delay invoking the
                                        Spanning Tree Learn operation after a 
                                        link down is detected.  
                Configuration:      Per port
                Error Checking:     Value must be in valid range.  Variable 
                                    only applicable to FDDI ports.

The MIB variable can be set via cli in the following manner.

                *cli> getsnmp lsLanPortHsrpDelay.8200
                        Name: lsLanPortHsrpDelay.8200    Value: 0 
                *cli> set config lock
                *cli> setsnmp lsLanPortHsrpDelay.8200 2000
                        Name: lsLanPortHsrpDelay.8200    Value: 2000
                *cli> set config unlock
                *cli> getsnmp lsLanPortHsrpDelay.8200
                        Name: lsLanPortHsrpDelay.8200    Value: 2000 

This command sequence will program a 2000 millisecond (2 second) delay for FDDI port 8.0. If a FDDI port 8.0 goes down, the port has 2 seconds to come back up before the Spanning Tree Learn operation is invoked. If port 8.0 returns to an up state within the 2 second period, Spanning Tree for that port will not be re-initialized.

Configurable Maximum Flows per (LAN) Card

In all previous releases, the maximum number of flows used in atmm/lcm initialization is 1200. This new enhancement allows configuration of "max-flows" for a line card. The default number continues to be 1200; the total number of flows available for each chassis is 10,000. The chassis maximum of 10,000 flows can be divided among all the LAN (FDDI and Ethernet) line cards in the chassis. For example, if there are 3 line cards in a chassis, the 10,000 flows could be divided by assigning each of the two cards a maximum of 4,000 flows and the remaining card 2,000 flows (4000+4000+2000=10000).


Note Although there is no restriction on the number of flows in a network, there is a restriction on the number of MAC addresses supported a network.


Implementation of Configurable Maximum Flows per Card

A new MIB object, cardMaxLanFlows, controls the maximum number of flows allocated to an "ecc_lan" process for a line card. This MIB object is accessed by the Card-Index and controls the amount of flow resources allocated to the line card process on the NP. Changing this MIB object for individual cards is useful in a network configuration where LAN segments are loaded unevenly. When cardMaxLanFlows is set to a number different than that currently in use, ECC records this value in shared-memory, gracefully shuts down, and exits.When a new ECC is automatically created, it uses the previously recorded number. If the cardMaxLanFlows is recorded in the MMA database, ECC is notified by an SNMP set command for the new value.

Using cardMaxLanFlows

This release of software provides SNMP get/set support for the new MIB object cardMaxLanFlows. To display or set the maximum number of flows assigned to a line card, use the CLI commands getsnmp and setsnmp. Use the CLI command set config to save new values in the MMA database. For example, to display the current value and assign a new value, 4000, for line card 6:

*cli> getsnmp cardMaxLanFlows.6 
Name: cardMaxLanFlows.6        Value: 1200
*cli> set config lock
*cli> setsnmp cardMaxLanFlows.6 4000
Name: cardMaxLanFlows.6        Value: 4000
*cli> set config unlock
4000 is now recorded in the database for card 6.

Note The line card will restart and may be unavailable for several minutes.


*cli> getsnmp cardMaxLanFlows.6
Name: cardMaxLanFlows.6        Value: 4000

If the value is changed without first locking the database, expect a sequence similar to the following. In this sequence, the line card reboot is triggered by the new value but the database value is used when the line card is re-initialized. Note the failed getsnmp command while the line card is rebooting.

*cli> setsnmp cardMaxLanFlows.6 5500
Name: cardMaxLanFlows.6        Value: 5500
*cli> getsnmp cardMaxLanFlows.6 
Error in response to request - No such variable name.
(The object may really not exist, or, if you did a "set/setsnmp/define",
 you may want to check your SNMP <community> string.)
*cli> getsnmp cardMaxLanFlows.6 
Name: cardMaxLanFlows.6        Value: 4000

Limitations of Configurable Maximum Flows

When ecc terminates itself, it will interrupt all current active flows and connections.

The interruption in service is about 3 minutes.

The system is limited by the total amount of free memory. If the max-flows requested is too high and the available memory is too low, the new ecc may not be able to work or even start.

If a value for cardMaxLanFlows.<card> is recorded in the mma-database (by a previous "set config lock" command), this value is always used. This means that you must change it by:

*cli> set config lock
*cli> setsnmp cardMaxLanFlows.<card> <desired-max-flows>
*cli> set config unlock
.... wait until a new ecc for <card> comes up and then verify:
*cli> getsnmp cardMaxLanFlows.<card>

When the terminating ecc is highly loaded, the new ecc will create a high load on the system when establishing all previous flows and connections.

Custom Filter Action DROP

In previous releases of software, custom filter actions were defined as either Block or Forward. Release 2.1(1.1) introduces a new action that can be applied to bridge, ip, or ipx custom filters: Drop, an alternative resource allocation for action Block. When a block filter is defined, a flow is used to program the line card hardware for each unique (mac source, mac dest, level 3) occurrence of a packet matching that filter. The next time that unique occurrence of a packet is seen at the line card, it is removed (blocked) from the LS2020 network. If the same packet matches a filter action of Drop (rather than Block), the packet is removed from the LS2020 network at the time of the filter match logic on the NP, and no flow resources are used. The trade-off of using Drop rather than Block is a higher CPU utilization on the NP rather than a consumption of flow resources to program the line card. In some networks, it may be desirable to use a combination of Block and Drop filters to obtain the most efficient use of flows and CPU.

Implementation of Filter Action Drop

The action Drop can be assigned for any custom filter when that custom filter is assigned to a port. Furthermore, the Drop action can be assigned for any port default filter action. For more information regarding Custom Filters, see the LS2020 Network Operations Guide. For more information regarding CLI commands to define filters and their assignment for LAN ports, see the LS2020 CLI Reference Manual.

Using Filter Action Drop

This release of software provides CLI support for the new filter action Drop. If you want to drop all AppleTalk packets on a port, define a bridge filter that matches all AppleTalk packets and assign the action Drop for that port's use of the filter. For example:

*cli> define bflt 40 (macDst == 00:dd:00:00:00:00)
*cli> show bflt 40
bflt 40:  (macDst == 00:dd:00:00:00:00)
*cli> show port 4.1 bflt-def
Default Bridge Filter action is FORWARD
*cli> set port 4.1 bflt 40 ?   
One of `forward', `block', `drop' or `delete'
*cli> set port 4.1 bflt 40 drop 10
*cli> show port 4.1 bflt
BRIDGE Filter number 40:
------------------
            priority 10
            action   drop
 Multicast Group ID  0
 Traffic Profile ID  0
            matches  0
Default Bridge Filter action is FORWARD

Limitations of Custom Filter Action Drop

Because a packet matching a filter with an action of Drop is processed by the NP, the CPU utilization of the NP may become stressed if too much processing is required. In that case, use the action Block to program the line card hardware to recognize and remove the packet from the network.

Configurable ARP Spoofing per Port

Software Release 2.1(1.1) allows the LS2020 ARP spoofing to be disabled on a per-port basis. There are two scenarios when the ARP spoofing function does not produce the desired result. First, when a router connected to the bridged LAN is providing a proxy-ARP service between virtual subnets implemented on the bridged LAN. Second, if the LS2020 network is used to create multiple non-overlapping, bridged domains, it is possible to configure multiple hosts with the same IP address.


Note It is highly recommended that you turn off ARP spoofing when the LS2020 is attached to routers.


Implementation of Configurable ARP Spoofing per Port

A new MIB object, lsLanPortArpProxy, can be configured by SNMP get/set processing for each LAN port (FDDI, Ethernet) on the chassis running this release of software. By default, each port is enabled for ARP Spoofing, identifiable by the port's lsLanPortArpProxy having a value of 1. A value of 2 written to the port's lsLanPortArpProxy will disable ARP Spoofing on that port.

When a port participates in ARP Spoofing, MAC/IP addresses learned on that port are recorded as an entry in the arp cache table. Two functions result from that entry. First, if an arp request matching the IP address of the cache entry is received from outside the LS2020 network, the LS2020 will respond with a Proxy ARP reply. Second, the LS2020 arp refresh function will be active on that port. Arp refresh in Release 2.1(1.1) ages the entries in the arp cache table every 6 minutes. At the expiration of the 6 minute age, the LS2020 transmits a unicast arp request out of the interface where the entry was learned.

When a port disables arp spoofing, MAC/IP addresses are not learned on that port. Consequently, no arp cache table entries are recorded for MAC/IP addresses on that port. Without entries in the arp cache table, the LS2020 will not Proxy reply to arp requests for addresses on that port. Nor will the LS2020 transmit refresh arp requests out of that port.

Using Configurable ARP Spoofing per Port

Use SNMP get/set commands to display and set the arp spoofing value for a LAN port in the LS2020 network. To write a new value to the SNMP database, use the CLI command set config to first lock the database for writing. For example, the following sequence of CLI commands queries a port's participating in arp spoofing, and changes that port's behavior to disable arp spoofing.

*cli> getsnmp lsLanPortArpProxy.4102
Name: lsLanPortArpProxy.4102 Value: 1
*cli> set config lock
*cli> setsnmp lsLanPortArpProxy.4102 2
Name: lsLanPortArpProxy.4102 Value: 2
*cli> set config unlock
*cli> getsnmp lsLanPortArpProxy.4102
Name: lsLanPortArpProxy.4102 Value: 2

Note the change of behavior for the port that disabled arp spoofing. For any arp cache table entries that were learned from that port while arp spoofing was enabled, the next refresh age will age-out those entries. While those entries remain in the cache, it is possible that a Proxy Reply for that entry will be generated and transmitted out of a port that is enabled for arp spoofing.

Configurable Flow Timeout per Card

The default life of a flow established in the LS2020 network is 5 minutes. A LAN flow is terminated after five consecutive minutes of inactivity. Because some network implementations may depend on a several-packet exchange for each flow, flow resources would be more efficiently used if the flow timeout were less than 5 minutes. In this release, the flow timeout is configurable per LAN card in the LS2020.

Implementation of Configurable Flow Timeout

The MIB object, debugLsCardInactivityTimer, can be accessed by SNMP get/set commands to change the timeout age of flows on a LAN card in the LS2020 network. Units of measurement are in seconds. When the timeout age of flows is changed, the new value participates in algorithmic processing on the line card. The actual age timeout depends on the number of flows being serviced on that line card. As such, there is a variance in the actual timeout age of each flow. Use the following guidelines:

The lowest value is 100 seconds (1 minute, 40 seconds).

The highest usable value is 300 seconds (5 minutes).

The variance for actual timeout age is not expected to exceed 2 times the value of the object.

Using Configurable Flow Timeout Per Port

The following sequence of CLI getsnmp/setsnmp commands show retrieving and setting the flow timeout age for an FDDI card. Remember to use the CLI command set config to lock the SNMP database previous to modifying the value; otherwise, the last value written to the database is used the next time the card is initialized.

*cli> gets debugLsCardInactivityTimer.4
Name: debugLsCardInactivityTimer.4 Value: 300
*cli> set config lock
*cli> sets debugLsCardInactivityTimer.4 100
Name: debugLsCardInactivityTimer.4 Value: 100
*cli> set config unlock                    
*cli> gets debugLsCardInactivityTimer.4    
Name: debugLsCardInactivityTimer.4 Value: 100

Limitations of debugLsCardInactivityTimer

The variance of actual flow timeout aging shown in the following sample of measurements for a line card with 2 flows established and a configured timeout age of 100 seconds. For this measurement, the same test was repeated 7 times.

Test........Age at Timeout
1..................1:45
2..................3:00
3..................1:15
4..................1:50
5..................1:50
6..................2:25
7..................3:00

LSCle00461 Unable to get information about an FDDI port

The "show port <fddi port> " displays only partial information about an FDDI port.

Recommended Action

Check your SNMP <community> string

LSCle04754 Defining the snapProto filter to a port does not provide the expected results

When setting the snapProto filter to a port, packets could not be transmitted because the snapProto is different than the packet sent.

LSCle05472 ECC assertion failed - mcDisconnectIndication 784 exp

The CP_HUNG string and crash happened because the debugging printout took too long. The stack backtrace printed out at that point gives some clues about what the linecard was doing at the time of the crash:

Network Management: CiscoView

LSCle03921 CiscoView gets compressed to menubar (CSCdi65897)

Periodically, when CiscoView rediscovers the status of LS2020 cards, such as when the state of a card is changed from AdminStatus of UP to DOWN, the view will shrink to being only a menu bar.

Workaround

Reopen the device using File->OpenDevice.

LSCle03405 CiscoView does not properly shrink the nettime clock in 50% (CSCdi65897)

When viewing an LS2020 in 50% mode, the Nettime Clock image remains at full size. The image continues to display nettime clock status. The image is the wrong size.

Workaround

No workaround necessary.

LSCle03431 CiscoView hangs when modifying chassisActiveIpAddr

CiscoView allows the user to change the IP addressing for the LS2020. The user must be aware that changing the active IP address for a device will cause loss of SNMP contact with the device.

Workaround

After changing the active IP address, CiscoView must open the device using the new IP address and not the old.

LSCle04972 Print feature prints screen area w/overlapping windows (CSCdi67287)

Generic problem for all of CiscoView. Where overlapping windows will obscure the CiscoView window that is to be printed.

Workaround

Move all windows off of the CiscoView window to be printed.

LSCle04970 Ljet Print option does not work (CSCdi60413)

Generic problem for all of CiscoView. When using the printing setup features, if Ljet is selected as the desired print format, a tcl/tk error popup will result. Not printing will occur.

Network Management: The StreamView CFG Tool

LSCle02679 Use Leading Zeros when Specifying MAC Addresses

Under some circumstances, the StreamView CFG tool requires Media Access Control (MAC) addresses to be specified with leading zeros, so that, for example, a MAC address such as the following is not accepted:

1:2:3:4:5:6

Recommended Action

When using the CFG tool, specify a leading zero in any MAC address field whose value is in the range 0x00 - 0x0F, as in the following example:

01:02:03:04:05:06

LSCle02686 Value in Chassis Name Field May be Inaccurate

Under certain circumstances, the value displayed in the Chassis Name field of the StreamView CFG tool may be inaccurate. For example, this may happen if a switch icon has been renamed using OpenView facilities, and is then selected in the StreamView topology map, and the configuration tool is started from the Topology map tool (in order to configure the selected switch).

Recommended Action

Use StreamView rather than HP OpenView to rename icons.

Start the configuration tool and select the chassis you wish to configure from the list of switches shown rather than from the topology map.

LSCle05475 Can corrupt database if run in both r-o and r-w modes without exiting CFG

Under some unusual circumstances the database may be corrupted if the user opens it first with read-only privileges, modifies configuration and then reopens the same database with read-write privileges.

Workaround

If the privileges need to be changed from read-only to read-write, then first exit the CFG and then restart it in read-write mode.

Network Management: The StreamView PVC and VLI Tools

LSCle00956 StreamView PVC Tool Has No Save As File Menu Item

The PVC and VLI configuration tools do not support a Save As function.

Recommended Action

To create copies of the database, use the Save As option of CFG. Do not copy the .dir and .pag files with UNIX shell commands.

LSCle00962 Deleted DLCIs May Not Be Reused Prior to Configuration Download

In the Release 2.1 PVC tool, under certain circumstances it is not possible to reuse the data link connection identifier (DLCI) previously assigned to a deleted frame relay circuit, even though the modified configuration has been successfully downloaded to the switch.

Recommended Action

Flush the current in-memory database image maintained by the PVC tool by selecting the Read DB button, then add the new circuit using the deleted DLCI.

LSCle02872 Use Update: Send All to Update VLI Information

In the StreamView VLI tool, the Update: Send Changes Only operation does not work. The button has been deactivated.

Recommended Action

To update the VLI configuration of a switch, use the Update: Send All operation. This is the only active option.

LSCle02919 Verify May Report Changes in Default Secondary Scale Value

Following a Verify operation, the StreamView PVC tool may report a difference in the value of the secondary scale factor associated with a PVC, when in fact it is unchanged from the default value. The chassis reports the actual (default) percentage of the maximum rate, but the database reports the internal value as "default."

Recommended Action

If the secondary scale has not been modified, ignore the reported difference. The chassis value is written to the database when you apply the change.

LSCle02924 Number of Virtual Circuits (VCs) Not Compared to Configured Card Maximum

The StreamView PVC tool does not verify that the number of circuits configured on a port falls within the configured number of circuits (MaxVCs) that may be configured on the port. Configuring a greater number of circuits than the allowed value results in a failure to establish some of the configured circuits when the configuration is downloaded to the switch. The same is true for frame relay circuits and the per-port Max Supported VCs value.

Recommended Action

To help ensure that all circuits configured through a port are set up, the number of circuits configured must not exceed the number of VCs allowed through the card or port.

For a port operating in frame relay service, the maximum number of circuits which may be configured on a port is set by the value of the XKeySymDB management information base (MIB) object, which corresponds to the CFG port field Max Supported VCs.

For a port operating in UNI service, the maximum number of circuits which may be configured on a port is set by the value of the cardMaxVCs MIB object, or the expert mode field Max VCs.

The aggregate number of circuits on all ports on a card may not exceed the value of the cardMaxVCs MIB object in all service cases.

LSCle02947 Cancelling a Verify Operation and Executing a Save Operation May Cause PVC to Exit

Under certain circumstances, if you perform the following sequence of actions with the StreamView PVC tool, it may report an internal error and then exit:

a. Start a Verify operation against two switches.

b. Cancel the running Verify operation with the Cancel button.

c. Schedule a download to a switch.

d. Initiate the download by executing the Save operation.

Recommended Action

Avoid cancelling a running Verify operation. If you have cancelled a Verify operation and want to download a configuration next, execute the Read DB operation before starting the download.

LSCle02855 The Clear Button Does Not Terminate an Update

In the PVC configurator, you select the option to update a node with new information from the database as follows:

a. Enter the appropriate parameters in the 'SendUpdate...Update Time' menubar pulldown menu.

b. Select 'Save' from the 'File' pulldown menu.

Once you do this, the update process (to the node) becomes essentially irrevocable, unless the currently running cfg_a child process is terminated.

The "cfg_a" child process, which is the independent process that actually performs the node update, can be terminated by using the Unix ps command to determine its Process ID number (PID), followed by a Unix kill command on that PID number.

Do not misconstrue the Clear button on the Update Time Screen as an alternative method by which you can abort a pending node update. The Clear button has no bearing on the process of updating a node configuration from the global database. It is simply used to clear an entry from the scrollable list box of user-defined chassis-pair entries on the 'SendUpdate...Update Time' screen.

LSCle02857 Default Parameter Values Represented as "Unconfigured"

When a node is updated with a new PVC (particularly a virtual channel identifier (VCI) PVC), with most of the PVC values left blank, accepting default values, subsequent Verify operations may show something like the following:

Attribute Differences - Database   /  Switch 
------------------------------------------------ 
Circuit chicago7.4.0,1-chicago7.4.1,1 
Source IR/TD            unconfigured  109 
Source Insured Burst    unconfigured  128 
Source MR/MD            unconfigured  96000 
Source Max. Burst       unconfigured  128 
Dest. IR/TD             unconfigured  109 
Dest. Insured Burst     unconfigured  128 
Dest MR/MD              unconfigured  96000 
Dest Max. Burst         unconfigured  128 

The "unconfigured" value under the "Database" column is a reminder that these values were left blank, when the PVC was sent to the node during a SendUpdate operation. If you wish to accept the default values from the switch, apply the changes and subsequent verify should show no differences.

LSCle02927 StreamView CFG: Deleted Filter Assignments may not be Reassigned

Under highly unusual circumstances, if a filter assignment or a PVC has been deleted from a port, but a download operation has not been performed, it may not be possible to reassign a filter to that port using the same filter ID, or a PVC using the same PVC identifier (DLCI or VCI number).

Recommended Action

In general, there is no need to delete a filter assignment and then reassign the filter. If you wish to modify a filter assignment, you may do so using the filter assignment Edit operation. However, if you do encounter this problem, perform a download after deleting the filter assignment. This allows the filter to be reassigned.

If you must reuse the identifier of a deleted filter assignment or PVC, download the switch configuration before you assign the identifier to a new object of the same type.

LSCle03080 Verifying PVCs on a node that has no PVCs configured can hang the node's NP

When using the PVC StreamView GUI Tool to verify the state of PVC's on a target node that doesn't have any PVC's defined, it is possible that an SNMP timeout may (incorrectly) occur. This is a result of the excessive amount of time it takes the LS2020 to "walk" through empty PVC MIB tables.

Recommended Action

The problem can usually be ameliorated by defining at least one PVC on the target node (using either PVC StreamView or the CLI) before verifying the state of PVCs.

LSCle05376 Can't add PVC if previously clicked on existing PVC

The listbox is not letting the New/Add process free to add new PVCs.I clicked on the PVCs in the listbox, I then tried to use it as a basis to build a new pvc by clicking on New and then Add. Nothing happened.

Workaround

Click outside the listbox and try again.

Network Management: The Command Line Interface (CLI)

LSCle01068 Rate Statistics for Ports are Inaccurate

The Rate information produced by the CLI when displaying port statistics is not accurate.

Recommended Action

Increasing the interval between displays of the statistics increases the rate accuracy. Very short intervals have a small baseline, so that the brief delay between request and retrieval of statistics can significantly skew results. By waiting 10-20 seconds between display requests, the baseline increases, the delays become less significant (a smaller percentage of the baseline), and the rates become much more accurate.

LSCle02390 Turning Off tty Output Paging

By default, the LS2020 CLI uses a functional equivalent of the UNIX more command to meter multiline terminal output.

Recommended Action

You may disable more-style output metering by specifying the -nomore switch on the command line when you start the CLI, as follows:

LSNode:2# cli -nomore  
...

LSCle02634 The CLI May Falsely Report No Filters Defined or No Multicast Groups Defined

Under certain circumstances, such as when a high SNMP processing load is placed on the LS2020 SNMP agent, the LS2020 CLI show bflt, show ipflt, and show ipxflt commands may report that no filters exist, or the show mcast command may report that no multicast groups exist. This is due to the CLI failing to receive a response to an SNMP request associated with the command.

Recommended Action

Usually, failure to receive a response to an SNMP request is indicated by a message saying "No response - try again", or "Request timed out". When such a message appears in conjunction with a message that no filters or multicast groups exist, disregard the messages and repeat the show command.

LSCle02658 Multicast Groups: Non-LAN Ports are Accepted as Destination Endpoints by CLI

The Release 2.1 CLI tool permits you to define a multicast group containing one or more destination endpoints which are not local area network (LAN) service (for example, Ethernet or FDDI) ports.

Recommended Action

While it is possible to define a multicast group containing non-LAN ports, the LS2020 signalling and ATM management facilities will not establish a multicast connection branch terminating at a destination port other than a LAN service port. Therefore there is no danger that multicast LAN traffic will be accidentally delivered to a device attached to a frame relay, frame forwarding, ATM UNI, or circuit emulation edge interface.

LSCle02661 CLI May Fail to Identify MIB Version If Started Too Soon

If, during the course of a node reboot, the CLI is started prematurely, such that certain MIB objects are not yet available because the processes that have registered for them have not completely booted up yet, then it is likely that CLI will display the following error message at start-up time:

Unable to determine MIB version... 

Recommended Action

The CLI session will now terminate itself, and must be restarted when such a condition exists.

LSCle02922 Setting Port Peak Cell Rate

The syntax of the command set card cardno peak-cell-rate cell-rate may suggest that one is setting the aggregate rate for all ports on the specified card. In fact, this command sets the per-port peak cell rate for each port on the specified card. The syntax of this command will be made unambiguous in a future release.

LSCle02952 Delete Filter Operation May Report "Invalid Filter"

Under unusual circumstances, the CLI may report that a filter being deleted is invalid, even though the filter is deleted successfully.

Recommended Action

Use the show bflt, show ipflt, or show ipxflt command to verify that a filter exists and is valid before you delete it. After you delete the filter, use the same command to verify that it has been deleted.

LSCle04505 cli crash on startup if in write protected directory

During TCS initialization the system can't bind socket in a write protected directory. If CLI isn't installed properly, the effective user ID of the CLI isn't set to root and CLI can't write into the write protected directory.

Recommended Action

Run CLI to check if it is properly installed in a write protected directory, then check any displayed messages.

Network Management: The LightStream Topology Map

LSCle02044 Adding Switches to an Existing Topology Map Domain

The StreamView topology map tool does not allow you to add a LS2020 switch to an existing LS2020 domain.

Recommended Action

To include a switch in a domain, you must recreate the domain. Delete the original domain, then select all icons desired for the domain (including the switch that is to be added), and recreate the domain.

LSCle04558 Large Output Queue Length Indicator Trips in the Topology Map Tool

The LS2020 topology map application performs a vaildation of ifoutQlen and reports errors if its value is beyond legal limits. For the LSC trunk. OC3, and 4port/8 port T3/E3 cards it may report errors erroneously.

Recommended Action

Any error reports with ifOutQLen values less than 100 should be ignored.

Network Management: Other

LSCle01083 Use HP OpenView Release 3.3

Use HP OpenView Release 3.3 to manage your LS2020 network.

If you are using HP OpenView to manage your LS2020 network, it is strongly recommended that you use Version 3.3 in order to avoid certain problems with the tool which may have an adverse effect on LS2020 simple network management protocol (SNMP) agent and system performance. Before Release 3.3, HP OpenView formats SNMP requests into a single buffer which can exceed the SNMP maximum of 484 bytes if a data collection has more than 20 variables.

Recommended Action

If you have HPOV Release 3.2 or earlier, when you set up data collection using HP OpenView, limit the size of collections to less than 20 variables.

LSCle01141/LSCle01540 Stopping an Unwanted Download

No function is currently provided to stop a long download.

Recommended Action

It is possible to abort downloads with the SunOS kill command. Log in as root to the network management system (NMS) station and use the command ps ax to find the process ID (PID) of each cfg_a process. Do not kill the cfg_a process with the lowest PID, it is the parent cfg_a process. Any cfg_a process with a higher PID is a child process, which you may kill. If more than one download is in process, they can be distinguished only by remembering the order in which the downloads were invoked (one with a lower PID was invoked earlier, and one with a higher PID was invoked later). However, even when the correct process is killed the results can be unpredictable, because some part of the configuration might have been downloaded and some not. It may be better to wait for a download to terminate normally.

LSCle01355 Specify Valid UNIX File Names With File Operations

Under certain circumstances while using the StreamView Save As operation, it may be possible to specify strings containing white space and nonprintable characters as file names.

While such file name strings may be accepted by the tools, they do not form valid UNIX file names. Creation of files so named may fail, or files so named may be difficult to manipulate later using standard UNIX mechanisms.

Recommended Action

When working with the StreamView tool set, do not use white space characters, non-printing characters, or control characters in file names.

LSCle02715 Network Management Station May be Attached to a PLC Port

Network operations on the LS2020 NP are available from three connection sources:

The test and control system (TCS) modem and console ports

The NP Ethernet port

A port on a packet line card (PLC)

Connections through TCS and the NP Ethernet port are well described in the documentation for this release. Connection through a PLC port is not.

Recommended Action

An NMS connected to a port on a PLC is able to connect to an NP in the network if two configuration tasks are performed:


Step 1 Configure the IP address of the NM workstation.

Step 2 Enable the NP Traffic Filter on that port to forward connection requests to the NP.


The IP address of the NMS must be configured with a unique host number on the same network as the LS2020 Chassis IP network. For instance, if the Chassis IP address in an LS2020 network is configured as network address 123.45.6.0, the NMS must also have 123.45.6.0 as the network portion of its IP address. Secondly, if host addresses 1-10 are configured for Primary and Secondary NP Chassis IP addresses in the LS2020 network, the NMS must be configured with a host address other than in the range 1-10, for example, 123.45.6.11.

The default configuration of each PLC port in this release is to block all traffic intended for an NP. The LS2020 private MIB variable that defines the action (forward or block) for PLC port traffic with an NP as its destination is lsLanPortNpTrafficFilter. The values to which this variable can be set are 1 (forward) and 2 (block). This release provides two ways of setting lsLanPortNpTrafficFilter:

By using the CLI set port c.p npdeliver command

By configuring and downloading the port attribute "forward" from StreamView

Use the following CLI command to set port 1 of Ethernet card 6 to forward received traffic destined for an NP in the network:

cli> set config lock 
cli> set port 6.1 np-deliver forward  
cli> set config unlock 

Use the following CLI command to set that port to block the same traffic:

cli> set config lock 
cli> set port 6.1 np-deliver block 
cli> set config unlock 

The StreamView cfg program can also be used to control whether a PLC port forwards or blocks traffic destined for an NP. In the Port Configuration window, configure the NP Traffic parameter by selecting either the Forward or Block button, and then sendupdate and save the configuration.

LSCle02769 No ifPhysAddress Object from ifTable Entry for NP Interfaces

The instance of the ifTable for the Network Processor (NP) does not provide an instance of the ifPhysAddress object.

LSCle05329 Can set least-cost-routing field to 0, an invalid value

Under some unusual circumstances the Least Cost Routing field in the Port configuration window may remain uninitialized and have a value 0. During download, corresponding MIB object will fail.

Workaround

Manually set Least Cost Routing to the desired value and repeat download.

LSCle05330 Can set call setup retry field to 0, an invalid value

Under some unusual circumstances the Call Setup Retry field in the Port configuration window may remain unitialized and have a value 0. During download corresponding MIB object will fail.

Workaround

Manually set Call Setup Retry to the desired value and repeat download.

LSCle05345 circuit trace with statistics options gives incorrect circuit status

When the circuit-trace command is executed with "statistics" option, the displayed output has incorrect field values. The inorrect fields are max rate, max burst and reserved bandwidth.

Workaround

Use commands show port c.p <listvci | listdlci | frameforward> or show chassis <listvic | listdlci | listff> to display max rate and max burst. Use command list-port-vc c.p to display reserved bandwidth.

LSCle05349 If CLI comand is complete, weird tab completions can be added

Under some unusual circumstances if a partial option is given for a completed command, TAB may expand it making it correct.

Workaround

Avoid doing this.

LSCle05423 database is locked before read/write set , and not cleared at exit

Sometimes the database locking file is not cleared. If you are the only user of the database, ignore the lock message and select Read or overwrite lock.

LSCle05424 database changes lost with multiple CFGs, single user

When a database is open by one CFG in read-write mode and another CFG starts and the user overwrites the lock, then the following saves from the two CFGs will overwrite each other. This will result in some changes being lost.

The user is instructed by CFG upon save that the lock belongs to another process and the database changes may be lost, but is not prevented from doing that.

Workaround

Do as instructed by CFG and also avoid opening two StreamView applications at the same time in read-write mode by overwriting lock. Instead, close th first application before opening the second one. It is ok to have one application in read-only mode and another in read-write mode.

LSCle05425 database converter issues a warning message, if lock file is already present

During a database conversion a warning message may appear indicating that the lock is currently owned by another person.

Workaround

If this warning message appears, overwrite the database, or you may remove the lock file corresponding to the database being converted before converting the database.

LSCle05426 PVC changes lost if single user, PVC and CFG locking

When a database is open by CFG in the read-write mode and PVC starts and the user then overwirtes the lock, the next time you save, the two applications are overwritten. Some changes will be lost.

The user is instructed by each application (upon save) that the lock belongs to another process and that the database changes may be lost, but the user is not prevented from doing that.

Workaround

Do as instructed by CFG/PVC and also avoid opening two StreamView applications at the same time in read-write mode by overwriting the lock. Instead, close the first application before opening the second. It is ok to have one application in read-only mode and another in read-write mode.

LSCle05428 CFG_A in download from VLI terminated abnormally

Under some circumstances a download from cfg_a may be terminated abnormally if update of several nodes is scheduled simultaneously from the Send Update session. A fatal XVT error will be printed on xterm.

No database corruption or misconfiguration occurs.

Workaround

Avoid if possible simultaneous updates of multiple nodes from the same Send Update session. If this error occured, check if the cfg_a process is still running (ps -ax | grep cfg_a), if not, restart cfg_a manually. Also, check in the log if all scheduled downloads completed successfully. Reschedule those not performed or those failed.

LSCle05433 XVT help dialog file, print does not work, nothing happens

The help dialog window of any StreamView application provides a File->Print menu item to output the current help topic in PostScript format to a file. In the 2.3.1 release, this function does not work even though the environment variable XKEYSYMDB has been set correctly as instructed in this release note. Nothing happens when the File->Print menu item is selected from the help dialog window.

Recommended Action

At runtime users need to set the environment variable XVTPATH to /usr/OV/bin/ls_bin (if using HPOV) or to /usr/LightStream-2.3.1/bin (without HPOV) to prevent File->Print from crashing the help application.

LSCle05442 CLI memory leak on set static route PVC

Some CLI commands may cause memory leaks. This can be verified using the ps -ax | grep cli UNIX/LynxOS command.

Workaround

If memory shortage becomes a problem, restart cli (quit and start over).

LSCle05443 show chassis listvci shows different max-burst values for same pvc

The CLI show chassis listvci command shows different max burst values for the source and destination on the same circuit.

Workaround

To get a correct max burst value you can use the commands get snmp sUniCktOperDestMaxBurst.CC0PP.VCI and getsnmp sUniCktOperSrcMaxBurst.CC0PP.VCI.

LSCle05446 aggregate bandwidth exceeded error popup dialog not correct

When configuring an LS card in the node configurator (cfg), sometimes an error popup appears declaring that "aggregate bandwidth" has been exceeded. Back off one or more ports' DCE/DTE bit rates so the aggregate is within the specified limit.

This popup states combined the DCE/DTE bit rate in bits/second. This popup is correct.

LSCle05455 Verifying E3 framing type not behaving as expected

Verifying the functionality of CFG does not report differences in the Framing type values for 4 port E3 trunk ports. Also, for the same port type, the verify function may report differences in DS3 Line Type values which is not applicable for 4 port E3 trunk ports.

Workaround

Ignore the verify report related to 4 port E3 trunk ports values form Framing Type and DS3 Line Type. Use cli to get the correct values for Framing type.

LSCle05456 Read database find of circuits is chassis A/chassis B is order dependent

In 2.3.1 PVC configurator, a new feature has been added. This feature allows user to specify "All" for Chassis A and/or Chassis B, in addition to just specify a chassis name, when performing a Read Database operation. This feature, however, is not working correctly for all combinations of ChassisA/CardA/PortA ChassisB/CardB/PortB pair. It is recommended that this new feature not be used in 2.3.1 PVC configurator. In any case, the database and runtime in-memory data are not corrupted or compromised. Any pvc created is stored correctly to the database.

To not use the above new feature, observe the following three restrictions:

Do not use "All" for Chassis A and/or Chassis B when performing a Read Database operation. Always use a chassis name for both Chassis A and Chassis B.

Using "All" in Chassis A and/or Chassis B when performing a Read Database operation might not give all the pvc's.

When performing a Read Database operation for two chassis, always put the chassis with a higher ID in Chassis A, and that with a lower ID in Chassis B. If Chassis A and Chassis B are the same, it does no matter.

Performing a Read Database operation with Chassis A having a lower ID than that of Chassis B will not list any pvc's between them.

If "All" is chosen for Card A, use "All" for Card B as well. If a card number is chosen for Card A, use a card number for Card B as well. Do not use "All" in Card A and a card number in Card B, or vice versa.

Performing a Read Database operation with "All" in Card A and a card number in Card B, or vice versa, will give a wrong list of pvc's.

LSCle05464 2.3.1 monitor cannot monitor 2.0.10 nodes

The 2.3.1 monitor cannot open a 2.0 node for display. There is no nettime functionality registered in R2.0, and the monitor is not able to set the nettime status icon. The monitor will only display blank panels, and never updates the actual card types in any slot.

Recommended Action

Use 2.0.7 monitor for any node running pre-2.1.1 software.

LSCle05465 Additional `define multicast' commands add chassis, but cannot delete chassis

When creating a mcast filter, and adding a number of chassis.card.port's to the filter, you cannot eliminate one of the chassis.cd.pt from the list without deleting the whole filter and re-entering it. You can add more to the list.

Other

Loss of Carriage Return or Echo

A terminal may lose carriage return or echo functionality.

Recommended Action

Execute the bash tset command to restore the lost property. Do this by entering the tset command at the bash prompt and pressing Return. Note that when you enter the command, the text does not appear on the screen.

Out of Range Bit Rates Permitted on Low-Speed Cards (LS1)

With the set port c.p dte-bitrate command, values as high as 6,000,000 bps are available, but values over 3,840,000 bps are not supported on LS1 cards.

Recommended Action

Do not set rates higher than 3.84-Mbps per port on LS1 cards. With the set port c.p dce-bitrate command, the values 4000 and 5376 (Kbits) are available but not supported. Rates higher than 3.84-Mbps per port may work for large packets.

LSCle05529 No Error Checking with setsnmp

The CLI setsnmp command allows you to directly modify variables in the MIB. However, this command does not validate its arguments and does not prevent you from setting a MIB variable to an inappropriate value.

Recommended Action

The preferred approach is to use high-level CLI set commands to change MIB variables and avoid setsnmp unless specifically instructed otherwise. These commands give the CLI enough context to validate the new value for the variable before changing the MIB.

LSCle00404 FDDI PATH Configuration Table is Not Supported

The RFC 1512 fddimibPATHConfigTable MIB object is not implemented.

LSCle00711 Periodic rdist to the Secondary NP Does not Check for Available Disk Space

On a redundant NP system, an automatic mechanism updates software and configuration information from the current primary NP to the current secondary NP. If the current secondary NP runs out of disk space, the secondary NP is not kept consistent with the primary NP.

Recommended Action

Establish a regular maintenance procedure of checking disk space availability on both NPs.

LSCle00720 FDDI Path Test Feature is Not Supported

The command set port c.p fddi smt station path test has no effect.

LSCle00961 Cannot Connect to Backup NP in Diagnostic Mode

You cannot load NP diagnostics and then connect to the backup NP.

Recommended Action

Use the CLI test command to run network processor (NP) diagnostics. The test command may be used on any card except the active NP. (The command test -m is not supported on the backup NP.)

LSCle01044 STP - External Bridge Loops and LS2020 VLI Functionality

The presence of external bridge loops may result in loss of LS2020 VLI functionality.

Recommended Action

When configuring LS2020 switches with external topology loops, configure the bridge priority for the switches such that one of them will become the spanning tree root.

LSCle01318 OC-3 Card Continuously Bounced When Connected to SONET MUX

When an OC-3c port was connected to a SONET multiplexor with internal clocking, the connection continuously bounced.

Recommended Action

When connecting an OC-3c port configured for internal clocking to a SONET multiplexor, a clocking type of external for the LS2020 port should normally be used (rather than the default of internal). Use of internal clocking may prevent the port from operating correctly.

LSCle02174 - Loopback - ATM-UNI Status Wrongly Reported Up

When set to remote loopback, the correct operational status for an ATM UNI port should be DOWN, but the reported status is UP. This is because the operational status of the ATM UNI interface does not take into account the physical layer indications.

LSCle02211 DSX1 Statistics Tables Not Implemented

The current, interval, and total tables of the DSX1 MIB (RFC 1406) are not supported for CEMAC cards in Release 2.1.

LSCle02228 - Old cardMaxVCs Value is Retained After Card Swap

The UIDPATH: unbound variable parameter applies to the card slot. As a result, when a card of one type replaces a card of another type, the value of echo $UIDPATH set for the first card may be inappropriate for its replacement.

Recommended Action

When you replace a card with a card of another type, verify that the value set in cardMaxVCs is appropriate for the new card type, and change it if necessary. From the CFG tool, delete the original card type and add the new type. Use the Sendupdate Changes only operation to send the new configuration to the chassis.

LSCle02656 IP Filtering Not Supported for 802.3 (SNAP) Encapsulated IP Frames

Custom filters do not work for 802.3 encapsulated IP frames.

Recommended Action

Do not attempt to filter 802.3 (SNAP) encapsulated IP frames.

LSCle02709 dot1dStpPortEnable Not Set When LAN Port is Down

When a LAN port is operationally down (unplugged), attempts to set the dot1dStpPortEnable object for the port appear to succeed but in fact have no affect.

Recommended Action

Do not attempt to set the dot1dStpPortEnable object when a LAN port is operationally down.

Platform

LSCle01719 No indication that flow not started on FR PVC

The PVC appears to be up when setting up a frame relay PVC across two ports.

Recommended Action

If you suspect that data is blocked on a PVC, but the PVC displays as being active, check the local and remote LMI status. The LMI status must be active for data flow to be enabled. This feature can be disabled using the "frProvMiCompliance" MIB variable.

LSCle01924 Phantom packets created on Internetworking cards

The line card appeared to be sending packets to the NPs on unrecognized VCs for multiple ports although these ports were either disconnected or connected to a repeater with no other devices.

LSCle02904 Cards which are down are reported as up

When available memory is low, cards fail to reload, however card status is reported as up.

Recommended Action

This can be caused by the following three known factors:

The number of VCs allocated through card MaxVCs can use too much memory.

Too many CLI processes may be running. It is recommended that CLI be run remotely when memory is low.

There may be too many users logged in.

LSCle03048 System reboots - leaves no trace of why

If the system reboots, it displays the reason for the reboot on the console port. If these messages are not saved, there is no other way to determine what happened.

Recommended Action

Set up a device to capture the messages displayed to the console port.

LSCle03098 Non-operational, non-LAN edge ports reported as operational

Non-operational, non-LAN edge ports reported as operational.

Recommended Action

If an edge port is not a LAN port, note the following three things about it:

For the card on which the port resides, all output in the " <pathname>" column output by the cli command "show card" might be wrong and should be ignored.

The "XKEYSYMDB" output by the cli command "show port" might be wrong and should be ignored.

The MIB object XKeysymDB for that port might contain an incorrect value and should be ignored.

LSCle03101 Getsnmp displays some values as strange characters instead of a hex number

Walking the XKeysymDB mib variable will produce some garbage values. These garbage values are for addresses not in use by the system.

LSCle04370 CEMAC target/max depth default values

The default target depth setting for CEMAC is supposed to be equal to 2 msec worth of data. The max setting should default to twice the target depth.

for T1, 2 msec = 386 bytes = default target setting

for E1, 2 msec = 512 bytes = default target setting

LSCle04433 TCS race condition - reset followed by status

When issuing "set card 7 active" the TCS slave is reset and does not respond to TCS messages, requests until fully initialized.

Recommended Action

Retry.

LSCle04692 Large pastes to telneted (with no carriage return) hangs system

Large pastes to a telnet session put the LS2020 into a state where simple commands issued anywhere will hang.

Recommended Action

Logging out of the telnet session may eliminate this situation.

LSCle04755 SWUD failure on FDDI card - 8000 flows, single card

There is a design limitation on the LS2020 when running certain applications.

Recommended Action

To avoid this situation, you should consult the LAN Design Guide on the web.


Note We understand this behavior and are currently working to resolve this special consideration in a future release.


LSCle04789 OC3 trunk card crashed with ndd fatal error

The LS2020 may inadvertently create a core file during swchgver.

Recommended Action

Ignore this core file.

LSCle04811 Inefficient use of available resources

If a trunk reaches the limit imposed on it by card MaxVC, it continues to advertise its available bandwidth. This can cause VCs to be attempted across the trunk, but consistently fail.

Recommended Action

Reduce the amount of data bandwidth available to that trunk so that no bandwidth will be advertised.

LSCle05129 A part of the static path configuration is cleared by transitioning

A part of static path configuration is cleared by bringing an edge card down and then back up.

LSCle05195 Can establish static path PVC with incorrect configuration parameter

A stataic path PVC with an incorrect configuration parameter, such as a non-existing card/port or non-activated card port, can be established.

Workaround

Use the correct up-to-date parameters.

LSCle05342 Different VPIs cause ermp and nd to not sync up

When configuring VPI numbers on a LS2020 trunk, both ends of the trunk must be configured with the same VPI number.

Workaround

Have carrier change the VPI numbers to equal.

LSCle05351 On a dual NP system, inconsistent designated STP root

Sometimes the STP process on a dual NP system may not converge on the same spanning tree designated root.

Workaround

There is no operational affect on the network since it happens on the backup NP.

LSCle05360 Config BPDU with lower path cost is not being propagated

When a config BPDU with lower path cost is received on a port, it is not being propagated over to other ports of the bridge.

LSCle05421 2.0.10.2 to 2.3.1 migration lost mma.db

The mma.db is moved as part of swinstall. At the the time of swinstall, the database is copied to /usr/app/base-2.3.1/config. That directory becomes /usr/app/base/config after swchgver, however because the swchgver was done several days later, the information was now VERY stale. This MAY explain why cards were left in TESTING mode after flash update. It still doesn't explain conclusively why standard testnode cards or new trunk cards were so left. It does explain why configured PVCs were not found after swchgver. Swchgver should be done as soon as practicable following swinstall.

Workaround

If swchgver is done after installation, and changes have been made to the mma.db since installation, the operator must copy /usr/app/base/config/mma.db.* to /usr/app/base-2.3.1/config/ before executing swchgver; OR/ after swchgver, cp /usr/app/base-(old)/config/mma.db.* to /usr/app/base/config/.

LSCle05437 It is not possible to delete a static route pvc

It is not possible to delete static-route-pvc from mma's database correctly using the cli command or NMS.

Workaround

If a PVC is configured with static route, for example, pvcStaticPathIndex or pvcCbrStaticPathIndex was set to non-zero value at least once, delete the PVC as follows:

1. ATM VCI PVC

cli> setsnmp pvcStatus.<c00p>.<VCI#> 3 
cli> set port <c.p> vci <VCI#> del 

2. Constant Bit-Rate PVC

cli> setsnmp pvcCbrStatus.<c00p>.1 3 
cli> set port <c.p> cbrpvc 1 del 

3. Frame Relay DLCI PVC

cli> setsnmp pvcStatus.<c00p>.<DLCI#> 3 
cli> set port <c.p> dlci <DLCI#> del 

4. Frame Forwarding PVC

cli> setsnmp pvcStatus.<c00p>.1 3

LSCle05450 Trunk is up, but not recognized by GID

Under severe stress testing characterized by many trunk transitions in a large network of LS2020's, a pair of nodes may loose communications over their trunk ports. This communication loss is the result of a GIDD synchronization error, which causes the nodes to lose FULL ADJACENCY with each other. The problem may be confirmed by performing a "show gid neighbors" command from the cli prompt on both of the effected nodes. One of the nodes will show a FULL adaceny state and the other node will show a non-FULL state (eg. EXISTENT, UNKNOWN). The trunk cards will appear to be operationally UP, but will not send traffic or respond properly to query commands. The nodes will remain in this state as long as there is one active trunk between the 2 effected nodes.

Workaround

All trunks between the 2 effected nodes must be brought down such that there is no traffic being exchanged between the nodes. This can be verified by the mma.traplog indicating a NBRDOWN event for the node who was in the FULL adjacency state. The trunks can then be brought up and GIDD will resynchronize properly. Communication between the 2 nodes will then resume.

LSCle05451 The PLC and SAC trunk discards cells with no drop-priority-control

The PLC and SAC trunk discards cells with no drop-priority-control when there is congestion on the trunk line.

LSCle05453 and LSCle05452 The show port command can't indicate cell drop info

The show port command doesn't indicate the cell drop information at LS-trunk correctly; Discard Packets can be incorrect.

LSCle05458 frProvMiMaxSupportedVCs defaulting to 1024; actually allows 25

Observed that frProvMiMaxSupportedVCs was being defaulted to 1024 by the chassis. When PVCs were configured with this value, a maximum of 25 PVCs would be established.

Workaround

Set the value to a legal value equal to or greater than the maximum number of circuits that you plan to activate on this edge port.

LSCle05463 swdelete in primary NP corrupted file systems in backup

Workaround

After deleting any files from the primary NP, before rebooting the primary or backup NP, the operator should wait until at least one trap of the following type has been received:

USER root: updatefiles: Successfully updated standby network processor.

LSCle05466 Newly added segments of static path are lost after resetting the card

Workaround

Delete the static path, and then recreate it with all the desired elements.

LSCle05471 All line cards can go down when try to write to a bad floppy drive using tar

Workaround

Loading diskettes into the LS2020 diskette drive which cause a read error has been known to cause line cards to reload. This is due to the heavy cpu load in processing the diskette read error.

Recommended Action

The diskette drive should only be used to load new software in order to minimalize the occurrace of this problem.

LSCle05474 ATM UNI VCI takes an IR=100,000,000 as a legal value

Workaround

Do not set to an illegal value, the legal range is 1 - 32399.

Resource Allocation

LSCle01369 and LSCle01791, Restrict MIB Variable Polling to 20 per Second or Less

The rate at which the LS2020 SNMP agent processes SNMP requests is currently limited to approximately 20 requests per second. For optimum system and SNMP monitoring performance, you should seek to limit the rate at which SNMP requests are delivered to the agent to 20 requests per second or less.

Note that SNMP requests may be originated by an external NM System (such as HP OpenView), the StreamView tool set, the LS2020 CLI, and the LS2020 collector utility.

The NP software does not throttle excess traffic from external SNMP devices. This can consume CPU resources and can cause spanning tree timeouts and other timeouts, degrading system performance. When this happens, you must reduce the SNMP traffic from the external device.

Recommended Action

To reduce the SNMP request rate, you might reduce the number of variables being tracked, increase the polling interval, reduce the number of concurrent network management processes that are requesting data, or delete unused collections defined and running on the switch.

LSCle01701 PVC Setup can Deadlock when Resources Do Not Allow Creation of All Configured PVCs

In Release 2.1, PVCs are implemented as two unidirectional circuits, rather than as a single bi-directional circuit. The LS2020 at each end of the circuit establishes the transmit circuit for the PVC from its end.

In a situation where there is insufficient bandwidth between two nodes, it is possible for several PVCs to get stuck in a half-open state. For example, suppose there is sufficient bandwidth between LS2020 A and LS2020 B to support one PVC (PVC 1 or PVC 2, but not both). It could happen that PVC 1 between A and B has its A-to-B circuit established, but not its B-to-A circuit, and that PVC 2 has its B-to-A circuit established, but not its A-to-B circuit. PVC 1 and 2 will stay in this state indefinitely because there is insufficient bandwidth between A and B to support the additional unidirectional circuits required to fully establish PVC 1 and PVC 2.

This does not occur in a network with sufficient capacity to support the PVCs configured for it. However, it could become a problem if trunks fail, so that existing PVCs need to be re-routed, and there is insufficient trunk bandwidth in the trunk-reduced network to support all of the PVCs.

Recommended Action

To recover from this state to the point that the trunk-reduced network supports the PVCs capacity permits (as opposed to far fewer, due bandwidth wasted by half-open circuits), do the following: make a priority list of PVCs, and temporarily disable low-priority PVCs. After the high-priority PVCs have been reestablished, re-enable the low priority ones. When the failed trunks are restored and lost network capacity is recovered, the LS2020s will reestablish the remaining low-priority PVCs.

Traps

LSCle02530 - No Trap for Invalid Receive Clock

The T3 access card does not send traps to report that it has an invalid receive clock.

LSCle02638 Trap nptmm_2010 Reported When Line Card is Removed or Reset

Whenever a board is removed or reset the following benign INFO trap may be reported:

(INFO) NPTMM_2010 at <local date time> (<GMT date time>)  
      ERROR: Slot <n> TCS Action Register 23 
      Read Error (UNIX error 15: Address fault detected)

Recommended Action

Ignore this trap.

LSCle03174 and LSCle04553

While running swchgver, if Flash memory on a line card requires an upgrade, the swchgver program brings the line card down to load Flash. While the line card is down, a trap similar to the following one may appear:

==> (OPER) NPTMM_9 at 12/04/95 14:13:50 CST (12/04/95 20:13:50 GMT) 
Card 6 Download Failed More Than 2 Times; New Download Is Not Initiated   

This trap appears because the ND process detects that the card is down and attempts to reload it. The ND process issues the trap if it tries and fails to load the card twice before the Flash upgrade is complete and the card comes back up. After the Flash upgrade is complete and the card comes back up, the card is reloaded.

Recommended Action

Ignore this trap.

Resolved Problems

This section summarizes problems fixed in Release 2.3(1).

Documentation

LSCle05180

Reference to 2.1(1.91) in release notes

LSCle05053

default MAX VCs set to 500 for all non-Cemac and non-NP cards

LSCle05244

cli must be restarted after an mma process was updated


Internetworking

LSCle04387

FDDI ring transitions constantly when inter-frame delay <16microseconds

LSCle04549

2 802.10 BPDUs not flooded

LSCle04665

FDDI ring transitions constantly when inter-frame delay <100 microseconds

LSCle04866

FDDI port oper status incorrect after transition

LSCle04986

pairs of macs lose connectivity


Network Management

LSCle00892

cfg_a error opening log not reported to parent window

LSCle01625

Use the CLI to set IP addresses to 0.0.0.0

LSCle01792

save causes spurious waiting for download message

LSCle01802

UNIX DBM used for configuration database

LSCle02016

Need a way to find all circuits terminating on a given chassis/card/port

LSCle02020

Database locking scheme is inadequate

LSCle02025

Prompt to save changes displayed prior to exit

LSCle02225

Default max values vcs for 8t3 trunk card is too low

LSCle02684

Modifying line card MIB objects while card is down

LSCle02880

cfg_a if card rebooted, card parameters are not set

LSCle02921

The show card command does not differentiate between T3 and E3 access cards

LScle03099

streamview tools ignore ovsnmp.conf file

LSCle03103

CLC card configure does not download clc1InfoAdm clock

LSCle03109

cli should not start if too many other clis are running

LSCle03142

StreamView tools usually crash on startup

LSCle03232

MMA should handle larger PDUs than the minimum accepted size

LSCle03308

Improper conversion of lsNtClockingSwitchAdmin

LSCle03469

DS3 line type field configuration in E3 (MSAC)

LSCle03553

set port circuitid won't allow entry of chassis ID

LSCle03648

cfg doesn't use hourglass cursor when it should

LSCle03734

mma.comm file; no public line

LSCle03784

cli to/from switch statistics displays incorrect values

LSCle03828

cli core dump with "walksnmp 1.3.6.1.4.1.711.1"

LSCle03840

DB conversion tool outputs an abnormally large file

LSCle03851

after del group member in multicast group, del button not greyed out - crash

LSCle03883

show snmp prints incorrect chassis name

LSCle03914

could not download config from streamview

LSCle04027

need public 0.0.0.0 read in mma.communities

LSCle04064

After reboot cli fails to show card-specific data

LSCle04111

FDDI port configuration allows multiple instance of it to be configured

LSCle04127

number of segments differs for the same static-path by two different commands

LSCle04140

set port <c.p.> static-path <#> del couldn't delete the existing one

LSCle04144

accepting null values to be chosen in list box of some fields

LSCle04189

adding one segment to a static path detletes all remaining segments

LSCle04268

E3 trunk (MSAC) card db conversion from 2.1.1 to 2.3.1 not proper

LSCle04269

bridge filter configuration conversion improper for 2.1.1 to 2.3.1

LSCle04277

setting LSC card inactive/active causes NP to reset

LSCle04281

pvc declares a verify error when one does not exist

LSCle04288

cfg send update couldn't set the editted cost value for OC3 and E3 trunk

LSCle04331

System is up for about 115 hours but "System up time" displays 3,619 hours

LSCle04358

Sun cli warning message

LSCle04367

show chassis listpvc: lists DLCls in addition to cbr pvcs

LSCle04380

vli does not recognize F-ether card in chassis

LSCle04384

verify gives differences for OC3 trunk cards after db conversion and send update

LSCle04393

cbr circuits showing up on 8SAC ports

LSCle04398

cli_startup.xterm on LightStream tape has improper comment line

LSCle04400

showing incorrect peak-port cell rate for E3 trunk card in cfg GUI tool

LSCle04407

CiscoView requires PDUs larger than 484 octets

LSCle04432

cli tells "lost network communications"

LSCle04463

Incorrect syntax for set port cbr pvc crashed CLI

LSCle04465

If db is set for r/o privileges for a user, CFG hangs

LSCle04475

set port <c.p> static path <#> del gives more help for complete command

LSCle04486

cli gives segmentation fault (core dump) when viewing port info of FDDI

LSCle04927

CiscoView LS2020 image exceeds some monitor resolutions

LSCle04505

cli crash on startup if in a write protected directory

LSCle04527

cfg paints background and hangs if LSC_DATABASE points to DB with no write permission

LSCle04534

Invalid LSC_DATABASE environment variable

LSCle04540

Cannot build cbrPVC, if destination line card

LSCle04543

discard after verify - buttons on top should be greyed out

LSCle04552

error in LightStream MIB file

LSCle04554

2.1 corruption sometimes displayed in differences scroll list

LSCle04555

come out of verify - nodename is highlighted but not selected

LSCle04569

XVT error when ReadDB button pushed second time

LSCle04582

cfg rename allows creation of duplicate chassis

LSCle04585

NetTime dialog, attempt add port clock yields XVT error

LSCle04605

general/snmp cli menu item does nothing

LSCle04609

two parallel clis on a local chassis can set config lock

LSCle04640

list-port-vc command syntax errors

LSCle04641

circuit-trace command syntax errors

LSCle04649

wrong slot radio button is selected when doing card SWAP, COPY, and MOVE

LSCle04660

circuit-trace command terminates with an error message after successful trace

LSCle04651

forced to kill cfg after setting max VCs to invalid value before adding card

LSCle04680

in multi-screen display of circuit-trace, if we press "q" it changes host

LSCle04682

CLI continues to "Request timed out - retrying" message

LSCle04696

set snmp hostname from one node to another doesn't work sometimes

LSCle04709

Saving of database causes core dump in cfg

LSCle04738

OC3 (1 port), E3 edge (4 ports) and T3 edge (4 ports) are not present

LSCle04740

cfg allows port change from FF to FR (vice versa) when pvc exists for port

LSCle04808

CFG segmentation fault when changing databases

LSCle04832

set snmp host? ends with segmentation fault

LSCle04833

Cannot set hostname to other system using LynxOS cli

LSCle04834

cannot lock multiple chassis at the same time

LSCle04858

workgroup disappeared, mode changed from INCLUDE to EXCLUDE

LSCle04881

Authentication failure with non-standard mma community

LSCle04883

defaulted database dir gets concatenated one more time

LSCle04896

4/8T3, 4E3 circuit defaults not provided with "new"

LSCle04980

Trying to save non-default database will crash cfg

LSCle04981

Trying to convert databases to 2.3.1 in cfg causes core dump

LSCle04984

cli doesn't accept 0 value for insured-burst parameter

LSCle04997

nothing in PVC selectable if close diff window

LSCle05003

seg fault/bus eror when saving vli changes after file to exit

LSCle05004

pvc core dumps w/particular 2.1.1.93 originated database

LSCle05005

vli core dumps w/particular 2.1.1.93 database

LSCle05038

Environmental checker prevents cfg startup if use ./cfg

LSCle05040

show chassis list-static-path giving unknown parameter

LSCle05045

show port <c.p> cbrpvc <pvc #> does not work

LSCle05046

add help option for cmd line cfg, pvc, vli

LSCle05047

add cmd line option to do env check w/o starting application

LSCle05052

pvc conversion is not taking place properly from 2.0.8 to 2.3.1

LSCle05057

generation of consistent readable messages for env_checker outcome

LSCle05062

converted database update to the node aborts abruptly

LSCle05063

NP traffic field of Ethernet port configuration is not converting correctly

LSCle05064

spanning tree configuration conversion from 2.1.0 to 2.1

LSCle05065

Filter assignment configuration conversion from 2.1.0 to 2.3.1 fails

LSCle05072

corrupted database

LSCle05073

circuit-trace error message may confuse the user

LSCle05074

Peak PortCellRate value list is different for 2.1 and 2.3.1

LSCle05075

pvc send update is failing due to invalid pvc # in snmp variable correspondence

LSCle05084

an arbitrary value has been assigned for "call reoptimize" field of E1

LSCle05115

circuit-trace does not work for ctrl circuits

LSCle05121

cost-reduced OC3 is not identified in cli

LSCle05129

static path configuration is cleared by edge

LSCle05141

config_check fatal error when OVSNMP_CONF_FIle not defined

LSCle05145

get XVT errors when trying to read 2.3.1 log files

LSCle05146

char ctrl-C puts cli config lock into an unknown mode

LSCle05157

Memory leak in cli show chassis command

LSCle05158

node crashed with ndd exiting because it couldn't run mma

LSCle05160

taking a long time to convert a huge database to 2.3.1

LSCle05161

default dir in file - open dialog box isn't LSC_DATABASE directory

LSCle05162

ReadDB is taking a long time to get the pvcs information

LSCle05164

deleting a bridge filter saying "invalid bridge filter specified"

LSCle05172

mma memory leak when configuring static routes

LSCle05193

a part of the static path configuration is cleared by transitioning

LSCle05197

Core dump using new button aftert using ReadDB and listbox selection

LSCle05200

decompress/convert/open error loop; cfg segmentation fault

LSCle05211

set port 3.1 frame-forward static 1 ? gives wrong help in cli

LSCle05212

list-port-vc on an NP card says "The card has 8 ports"

LSCle05224

remote circuit-trace with GCI value not tracing some circuits

LSCle05227

File, Save of a non-default database doesn't save the database

LSCle05230

Make database changes, File, new, hit cancel, chassis name list is empty

LSCle05232

Get error message if a database is locked

LSCle05234

Segmentation fault converting database if working directory is read-only

LSCle05235

"Store R2.3.1 database operation failed" message while converting

LSCle05239

mma crashed after "send_update" to the node

LSCle05247

database conversion tool is not validating some fields during conversion

LSCle05257

show chassis listpvc: not displaying TD/MD values correctly

LSCle05313

File, Print can't print

LSCle05332

show card c.p ports not showing port info

LSCle05344

showing negative values in statistics information

LSCle05346

circuit-trace command with statistics option shows CEMAC port as trunk

LSCle05355

After editing assigned static route, it cannot be deleted

LSCle05367

show card 1 says lost network connection

LSCle05387

two typos in error message

LSCle05388

when config database is locked, circuit trace command fails

LSCle05395

hard coded message is out of sync, 2.3.1 managing 2.07

LSCle05413

show card #card is not listing all available cards

LSCle05445

Platform responds to snmp getRequests with 2K packets

LSCle05459

Can't unlock mma database after show chassis lispvc


Other

LSCle04872

ethernet card crashes when supporting spanning tree blocking ports


Platform

LSCle02712

2.1 swud failure, NP's own slot

LSCle03349

Getting request rejected by mma for unknown reason

LSCle03812

Incorrect load status reported

LSCle04326

incorrect display for "show port" command

LSCle04474

leafgen or trunk lcc consumes all mbufs, resultsin system halt

LSCle04478

console locks up, swud fails, 6000 flows test, lynx.os.dev

LSCle04529

system-wide memory shortage (system runs out of memory buffers)

LSCle04620

ERMP failure during trunk rerouting

LSCle04629

changing atmm strings to "const char" would save memory

LSCle04644

Congestion Avoidance delayed after "best effort" buffer is filled

LSCle04704

gidd consumes all mbufs, resulting in a system halt

LSCle04720

with bad switch card, both NPs claim to be primary

LSCle04769

Error [ndd.72]: ERMP channel when timing

LSCle04787

ERMP failures eventually under heavy ON-chassis

LSCle04807

LAN port multicast/bflt assignments deleted from the database after reboot

LSCle04822

embug_alloc:task 0x80 w 5 size 16464- no buckets left

LSCle04876

swinstall gets tar: executable file in use

LSCle04892

8SAC self clocking option is broken

LSCle04894

Frame relay data corruption causing FRMR

LSCle04895

Frame relay issues DLCI=0 when invalid

LSCle04944

Primary NP rebooted causing secondary NP to become primary

LSCle04950

Port clocking type setting error on 8SAC

LSCle04968

frame and data corruption from ls1 zilog transmitting

LSCle04975

Congestion Avoidance messages from linecard to NP should be unreliable

LSCle04977

MIB variable is missing for CEMAC card in "portInfoType" object

LSCle04982

no traffic is passing when max-burst is set to <13 cps

LSCle05018

2 ch network outage sep 6

LSCle05044

default value of edgeCallReoptimize is differentfrom MIB spec

LSCle05060

lcc for CLC/OC3 edge is leading memory

LSCle05085

CEMAC cbrpvc not doing periodic reoptimization to select the least cost

LSCle05119

Cards with only 200 ckts will not bring up ports

LSCle05128

static route info on FR port is cleared on port inact/act

LSCle05148

system hangs after power cycle

LSCle05152

both NPs become primary after receiving TCS NMI

LSCle05156

cannot ping from one chassis to others

LSCle05171

ermp_error() called with the wrong number of arguments

LSCle05175

NPCC process on exited

LSCle05178

bflt/mcast port assignments deleted from the database

LSCle05179

Invoking CLI after an install from a freshdisk

LSCle05181

atmm mib using invalid if index, causing list-port-vc to fail

LSCle05191

static route info of pvc on Frame Relay protocol is cleared

LSCle05192

Contents of the clock reference table are cleared when the NP card

LSCle05196

cannot turn on reoptimization on FR port (with LSC0 after reconfig)

LSCle05205

E1 cp_crash every time NETTIME_OC3_TRUNK_FAIL is run

LSCle05229

swchgver did not proceed with flash upgrade

LSCle05260

swcvhgver gave "LWMA_INIT ERROR" message

LSCle05261

system crashed into kernel debugger

LSCle05263

system crashed - can't run required program vifm

LSCle05264

need more information with the update files error message

LSCle05316

LSC trunk repeatedly goes up/down at short intervals after trunk cable

LSCle05322

LCC exited for two of the line cards

LSCle05339

OC3 card went down after the system came up

LSCle05353

The PVC for NP IP connection cannot be re-established

LSCle05366

Traffic profile data in bridge filter command

LSCle05404

static path segments are not being deleted

LSCle05431

The data field of LCC process increases

LSCle05432

Last segment of static route information becomes inact

LSCle05460

distribution node must be running 2.3.1 to swremoteinstall

LSCle05484

setting certain mib to same value causing port


Appendix A: Hardware Compatibility Table

The following table specifies the minimum hardware revision levels required by this version of the LightStream 2020 software. The part number and revision level can be found on each piece of hardware. You can also learn them by using the bash command sysver -a. Information in this table is subject to change; for further information, contact Cisco customer support.

.

Part Number
Previous Part Number
Description
Minimum Revision

73-1430-01

2121973G01

Midplane

P01

73-1430-04

N/A

Midplane 2

A0

73-1449-01

2123864G01

Release 2 switch card

F

73-1428-01

2121701G01

Network processor

K

73-1428-02

2121701G01

Network processor

A0

73-1431-01

2121992G01

Network processor access card

PB

73-1432-01

2122002G01

Low-speed line card

G (must have rev I if TCS slave is less than rev C0)

73-1433-01

2122007G01

Low-speed access card

C

800-00408-01

2222718G01

V.35 fantail (for low-speed or serial cards)

P01

800-00408-02

N/A

V.35 fantail (for low-speed or serial cards)

A0

800-00410-01

2222807G01

RS-449 fantail (for low-speed or serial cards)

P01

800-00410-02

N/A

RS-449 fantail (for low-speed or serial cards)

A0

800-00414-01

2223856G01

X.21 fantail (for low-speed or serial cards)

A

73-1434-01

2122009G01

Medium-speed line card

I

73-1560-01

N/A

Medium-speed line card 2

A

N/A

2122012G01

T3 medium-speed access card

A

N/A

2122012G02

E3 medium-speed access card

B

73-1438-01

2123258G01

T3 medium-speed access card

A

73-1439-01

2123258G02

E3 PLCP medium-speed access card

03

73-1440-01

2123258G03

E3 G.804 medium-speed access card

B

73-1437-01

2123086G01

Packet line card

E (F if CEMAC installed)

73-1437-02

N/A

Packet line card

H0

73-1450-01

2123988G01

Ethernet access card

B

73-1452-01

2124055G01

FDDI access card

C

73-1452-02

N/A

FDDI access card

A0

73-1441-01

2123263G01

Cell line card, 2 TSUs (for 2-port OC3AC)

G

73-1442-01

2123263G02

Cell line card, 1 TSU (for 1-port OC3AC)

C

73-1443-02

2123864G01

8-port T3 access card

A0

73-1444-01

2123265G01

Single-mode, 2-port OC-3c access card

D

73-1445-01

2123265G02

Multimode, 2-port OC3 access card

C

73-1446-01

2123265G03

Single-mode, 1-port OC3 access card

A

73-1447-01

2123265G04

Multimode, 1-port OC3 access card

A

73-1451-01

2124026G01

8-port serial access card

A0

73-1451-02

N/A

8-port serial access card

A0

73-1459-01

2170057G01

T1 circuit emulation access card

B

73-1460-02

N/A

E1 circuit emulation access card

A0

73-1465-01

N/A

8-port fiber ethernet access card

A0

73-1528-01

N/A

8-port E3 access card

A0

73-1529-02

N/A

4-port E3 access card

A0

73-1555-02

N/A

4-port T3 access card

A0

73-1680-01

N/A

Packet line card

A0

800-00463-01

N/A

E1 BNC fantail

A0

800-00551-01

N/A

E1 SMZ fantail

A0


Appendix B: Flash Memory Image Checksum Values

Every time you install a card in a slot of the system, you must verify that it has the correct Flash memory checksum, and upgrade Flash if necessary. The procedure for doing this is given in the LightStream 2020 Hardware Reference and Troubleshooting Guide. Use the bash command sysver -a|more to display Flash checksums. The checksums for this new release are as follows:

If the Flash checksum is 0xE82A for a Release 2 switch card, or 0x50CA for a Release 1 switch card, then the specified switch card already has the latest Flash image.

Network Processor:       Flash Image Checksum:  0xF682 
Switch Card 1:           Flash Image Checksum:  0x50CA 
Switch Card 2:           Flash Image Checksum:  0xE82A 
Low Speed Card:          Flash Image Checksum:  0x08AC 
Medium Speed Card:       Flash Image Checksum:  0x6120 
Packet Line Card:        Flash Image Checksum:  0x8FD1 
Cell Line Card:           Flash Image Checksum:  0xC218

Appendix C: Software Diagnostic Versions

The following diagnostic versions are used in this release.

diag_np1.aout Version 1.575
diag_ls1.aout Version 0.721
diag_ms1.aout Version 1.495
diag_clc1.aout Version 2.110
diag_plc1.aout Version 2.005
sys_np1.aout Version 1.460

Document Conventions

This publication uses the following conventions:

Convention
Application

boldface

Commands and keywords in body text.

italic

Command input that is supplied by the user.

[     ]

Keywords or arguments that appear within square brackets are optional.

{ x | x | x }

A choice of keywords (represented by x) appears in braces separated by vertical bars. The user must select one.

Ctrl

The control key. For example, where Ctrl + D is written, hold down the Control key while pressing the D key.

XKeysymDB

Examples of information displayed on the screen.

boldface screen font

Examples of information that the user must enter.

<     >

Command parameters that must be replaced by module-specific codes.



Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.



Caution Means reader be careful. In this situation, the user might do something that could result in equipment damage or loss of data.

Warning


IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071

SAVE THESE INSTRUCTIONS


Where to Find Safety and Warning Information

For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15xxx systems. It also includes translations of the safety warnings that appear in the ONS 15xxx system documentation.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Cisco Optical Networking Product Documentation CD-ROM

Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only —  security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies —  psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html