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.

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, "Installing StreamView to Run Under HP OpenView," starting on page 24.

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

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 UIDPATH: unbound variable 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 XFILESEARCHPATH 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:

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, appendix "StreamView Output Samples" appendix.

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

Shut down HP OpenView, revert to Step 5 above, and add /usr/OV/%T/%N%S to the XFILESEARCHPATH. 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 LSC_DATABASE, 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.

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

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 line to the end of the .cshrc file:

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

Otherwise, if the system displays the message UIDPATH: Undefined 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 XFILESEARCHPATH 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:

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:

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 /usr/OV/%T/%N%S to the XFILESEARCHPATH. 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 LSC_DATABASE. 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.

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

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 4 Change to the root directory by issuing the following command:

# cd /

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

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

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

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

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

Step 4 If the system displays UIDPATH: unbound variable or no message in response to the echo $UIDPATH command, 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=/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.

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

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

% echo $UIDPATH

If the system displays the message UIDPATH: Undefined variable 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.

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:

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

1) Ignore failures associated with 55.13 under the conditions described above.

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

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.

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

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 frProvMiMaxSupportedVCs 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:

1. Start a Verify operation against two switches.
   
   
2. Cancel the running Verify operation with the Cancel button.
   
   
3. Schedule a download to a switch.
   
   
4. 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:

1. Enter the appropriate parameters in the 'SendUpdate...Update Time' menubar pulldown menu.
   
   
2. 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 XVTPATH 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:

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

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

   
   
   
3. 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 cardMaxVCs parameter applies to the card slot. As a result, when a card of one type replaces a card of another type, the value of cardMaxVCs 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:

1. The number of VCs allocated through card MaxVCs can use too much memory.
   
   
2. Too many CLI processes may be running. It is recommended that CLI be run remotely when memory is low.
   
   
3. 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:

1. For the card on which the port resides, all output in the "Oper Status" column output by the cli command "show card" might be wrong and should be ignored.
   
   
2. The "Oper Status:" output by the cli command "show port" might be wrong and should be ignored.
   
   
3. The MIB object ifOperStatus 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 dot1dTpFdbAddress 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.

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

Internetworking

Network Management

Other

Platform

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.

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

Cisco Connection Online

Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously·a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

WWW: http://www.cisco.com.

WWW: http://www-europe.cisco.com.

WWW: http://www-china.cisco.com.

Telnet: cco.cisco.com.

Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact ccohelp@cisco.com. For additional information, contact ccoteam@cisco.com.

If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or csrep@cisco.com.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

AtmDirector, AutoConnect, AutoRoute, AXIS, BPX, Catalyst, CD-PAC, CiscoAdvantage, CiscoFusion, Cisco IOS, the Cisco IOS logo, CiscoLink, CiscoPro, the CiscoPro logo, CiscoRemote, the CiscoRemote logo, CiscoSecure, Cisco Systems, CiscoView, CiscoVision, CiscoWorks, ClickStart, ControlStream, EdgeConnect, EtherChannel, FairShare, FastCell, FastForward, FastManager, FastMate, FastPADlmp, FastPADmicro, FastPADmp, FragmentFree, FrameClass, Fulcrum INS, IGX, Impact, Internet Junction, JumpStart, LAN2LAN Enterprise, LAN2LAN Remote Office, LightSwitch, MICA, NetBeyond, NetFlow, Newport Systems Solutions, Packet, PIX, Point and Click Internetworking, RouteStream, Secure/IP, SMARTnet, StrataSphere, StrataSphere BILLder, StrataSphere Connection Manager, StrataSphere Modeler, StrataSphere Optimizer, Stratm, StrataView Plus, StreamView, SwitchProbe, SwitchVision, SwitchWare, SynchroniCD, The Cell, The FastPacket Company, TokenSwitch, TrafficDirector, Virtual EtherSwitch, VirtualStream, VlanDirector, Web Clusters, WNIC, Workgroup Director, Workgroup Stack, and XCI are trademarks; Access by Cisco, Bringing the Power of Internetworking to Everyone, Enter the Net with MultiNet, and The Network Works. No Excuses. are service marks; and Cisco, the Cisco Systems logo, CollisionFree, Combinet, EtherSwitch, FastHub, FastLink, FastNIC, FastPacket, FastPAD, FastSwitch, ForeSight, Grand, Grand Junction, Grand Junction Networks, the Grand Junction Networks logo, HSSI, IGRP, IPX, Kalpana, the Kalpana logo, LightStream, MultiNet, MultiWare, OptiClass, Personal Ethernet, Phase/IP, RPS, StrataCom, TGV, the TGV logo, and UniverCD are registered trademarks of Cisco Systems, Inc. All other trademarks, service marks, registered trademarks, or registered service marks mentioned in this document are the property of their respective owners.

Copyright © 1997, Cisco Systems, Inc.
All rights reserved. Printed in USA.
9611R