|
|
The LightStream 2020 Release Notes
for Software Release 2.0.9
These release notes describe features, enhancements, special considerations, and software upgrade procedures for software Release 2.0.9 of the LightStream 2020 enterprise ATM switch.
This software base release is an upgrade to base Release 2.0.7. It subsumes upgrade 2.0.8, and it supersedes base release 2.0.7 node software and all prior releases. StreamView Network Management software is not updated in this release.
These release notes are organized as follows:
Describes new features of Release 2.0.9 and enhancements to existing features.
Describes compatibility issues that must be resolved by bringing hardware up to current revision levels before upgrading LS2020 software.
Lists checksum values for flash memory on cards for this release.
Describes special considerations and caveats for Release 2.0.9 of the LS2020 product.
Describes how to determine the software release presently installed on the system hard disk. Describes how to upgrade your software to Release 2.0.9. Discusses disk utilization.
Describes procedures related to the upgrade process, such as how to free up disk space, fall back to prior versions of the software, and verify connections to the backup NP.
Lists problems of Release 2.0.8 that have been resolved in Release 2.0.9.
Release 2.0.9 contains improvements to existing functionality found in Release 2.0. The improvements are in the following areas:
The only change in functionality is that the modem and terminal ports on the switch card no longer support the BREAK detection mechanism. The user must configure the proper baud rates for local and remote (modem) access.
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 or by using the bash command sysver -a.
| Part Number | Previous Part Number | Description | Minimum Revision |
|---|---|---|---|
Software releases 2.0.0 and above require a 32 MB network processor (NP).
Software Release 2.0.5 is the minimum software revision necessary for the support of redundant switches.
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 procedures are given in the LightStream 2020 Hardware Reference and Troubleshooting Guide. Use the bash command sysver -a to display flash checksums. The checksums for this new release are as follows:
If the flash checksum is 0x64A2 for a Release 2 switch card or 0x5D00 for a Release 1 switch card, then the specified switch card already has the latest flash image.
Note The label Switch Card 1 denotes Release 1 of the switch card, and the label Switch Card 2 denotes Release 2 of the switch card.
This section describes special considerations that apply to Release 2.0.9 of the LightStream 2020 enterprise ATM switch. These special considerations are drawn from reports of hands-on experience with the product by LightStream 2020 customers, Cisco developers, and Cisco software quality assurance personnel.
Most of the special considerations here are given Cisco case numbers. If you contact Cisco Systems about any of these special considerations, please refer to the case number.
The TCS HUB for Release 2 switch cards no longer uses the BREAK detection mechanism (also known as the auto-baud or pseudo-auto-baud mechanism) to select the baud rate on either the console or modem port.
The set and show commands of the Release 2 switch card TCS HUB are now used to select and display the baud rate. These commands manipulate and interpret the contents of certain fields in the midplane EEPROM that are used by the Release 2 switch card TCS HUB to initialize the console and modem port baud rates.
The midplane EEPROM locations used to maintain the console and modem baud rates were previously reserved. When the new Release 2 switch card TCS HUB code is installed in a Release 2 switch card in a system that has never had those reserved midplane EEPROM locations initialized, the new code detects that these locations are uninitialized and initializes them with default values (9600 baud for the console port and 2400 baud for the modem port).
The syntax of the set command of the Release 2 switch card TCS HUB is as follows:
The arguments of the command are as follows:
The syntax of the show command of the Release 2 switch card TCS HUB is as follows:
The arguments of the command are as follows:
You can change the baud rate at any time. It takes effect on power-up or board reset, or (for the modem port) when the modem port is reinitialized with the TCS HUB init command. The syntax of the init command is as follows:
There are currently three ways to match console terminal and console port baud rates if the console port is initialized with a baud rate other than the one to which the console terminal is set:
Change the console terminal baud rate (if possible) until the Release 2 switch card TCS HUB prompt is displayed when you press the [Return] key. There are seven possible console baud rates. Starting with the default rate, set up the console terminal to run with each one until a match has been found.
Dial into the LightStream 2020 switch. Use the command set {sa | sb} console baudrate rate to change the console port baud rate to the console terminal baud rate, specifying the switch whose baud rate you wish to set.
Reset the Release 2 switch card by entering the following TCS HUB reset command:
This breaks the modem connection and reinitializes the console port to the selected baud rate.
Use the console attached to the fully operational switch, or dial in to the switch through the modem port. From this switch, use the command set {sa | sb} console baudrate rate to change the console port baud rate to the console terminal baud rate, specifying the other switch.
If none of the above works, contact Cisco Systems, Inc.
If the modem port is initialized with a baud rate other than the one with which the modem can operate, you can change the modem port baud rate in either of two ways:
Dial in to the LightStream 2020 chassis and determine the address of this switch card (the one to which the modem is attached).
Type the following commands at the TCS HUB prompt:
Use the address of the other switch. That is, if you are connected to Switch Card A, specify sb in these commands, and if you are connected to Switch Card B, specify sa in these commands. Specify the baud rate to which the modem is set.
A terminal may lose carriage return or echo functionality.
Workaround: Execute the bash tset command to restore the lost property.
The primary TCS hub and the primary (active) switch fabric may be on different switch cards in a redundant system.
The CLI show chassis primaryswitch command indicates which switch fabric is active. The primary TCS hub is indicated in any of the following three ways:
2. The use of uppercase letters in the TCS HUB prompt. That is, the prompt TCS HUB <<B>> indicates that the TCS hub on the card in Slot B is active, and the prompt tcs hub <<b>> indicates that it is secondary. (In both cases, the name of the hub card to which you are connected is indicated by the letter in brackets.)
3. The LED labelled TCS SEL on the switch card is lit.
On systems with at least one Release 1 switch card, using a CLI command to change which switch is primary causes the chassis to reboot. The CLI command is set chassis primaryswitch.
The configuration tool and CLI allow rates to be set to 6 Mbps aggregate for low-speed cards. The maximum throughput per port for the low-speed card is about 4.1 Mbps and 4600 frames/sec, when you are using committed traffic and an 88-byte frame. If the rate is set above this limit, the excess may be dropped.
Workaround: Do not set rates higher than 3.84 Mbps per port on low-speed cards.
Although limited functionality for a frame relay NNI interface is present in the Release 2.0.9 software, this is not a supported functionality.
Looping of a Frame Relay UNI interface provides no useful diagnostic information because the UNI protocol is asymmetric. The LightStream 2020 switch supports internal looping of such a port by first converting it to an NNI interface. A successful loop sets the administrative state of the port to testing and the operational state to up.
In Release 2.0.9, FDDI and Ethernet ports cannot be looped.
The CLI utility allows you to directly modify variables in the MIB using the setsnmp command. This command performs no validation of its input data and does not prevent you from setting a MIB variable to an inappropriate value.
Workaround: Use the following command within the CLI to change MIB variables:
This approach gives the CLI enough context to validate the new value for the variable before performing the change to the MIB.
The POST timeout value on all packet line cards and cell line cards (PLC and CLC) must be modified to support new PLC and CLC POST.
Verify the POST timeout value of cards in your system by typing the following at the TCS command prompt:
The value read should be 0x0e4e.
If the value read is different from this one, enter the following at the TCS command prompt:
The oc3InfoMediumType object can be set to 1 for Synchronous Optical Network (SONET) operation or to 2 for Synchronous Digital Hierarchy (SDH) operation of the OC-3 card.
The default for OC-3 ports is to use SONET. The following paragraphs tell you how to set a series of OC-3 ports to use SDH instead of SONET.
Identify all OC-3 ports in your network that you want to run SDH.
Step 2 Use the long port number format cc0pp, where cc is the card number (leading 0 not required) and pp is the port number. For example, Port 1 on Card 5 of an OC-3 card is 5001. (For a detailed description of this port number format, see the LightStream 2020 CLI Reference Manual.)
To configure OC-3 ports to use SDH, follow this procedure for each switch:
Step 2 Start the CLI
Step 3 Enter protected mode with the protected command and password:
Step 4 Set the SNMP community name to a community that has write authorization. In the following sample command, this community is named write:
Step 5 Set the configuration lock so that your changes are written to the configuration database:
Step 6 Configure identified OC-3 ports to use SDH:
The MIB object name must be typed with uppercase letters exactly as shown, e.g. oc3InfoMediumType.10003 for Port 3 on OC-3, Card 10.
Step 7 When you have reconfigured all of the identified OC-3 ports, unlock the configuration database:
Note If you want to configure a port for SONET, carry out this same procedure, substituting the
following command in Step 6:
*cli> setsnmp oc3InfoMediumType.cc0pp 1
*cli>
Every time you install a card in a slot of the system, use this procedure:
Step 2 To see the current flash checksums of all cards in the chassis, enter the following command:
The correct checksums are as follows:
Note The label Switch Card 1 denotes Release 1 of the switch card, and the label Switch Card 2 denotes Release 2 of the switch card.
Step 3 If a line card or NP flash checksum is not correct, load the flash into the card by using the following command:
Here, slot# represents the slot number of the card with the incorrect flash checksum.
If a new switch card has an incorrect flash checksum, load the flash by following the procedure described in "Procedure 4, Verify Switch Card Flash."
Step 4 Verify flash again (Step 1 and Step 2 above).
Step 5 If the card still has an incorrect flash checksum the flash is loaded, contact Cisco Customer Support.
The special considerations in this section are provided with a Cisco case number. If you contact Cisco about any of these special considerations, please refer to the case number.
CLI does not allow you to set bandwidth parameters for virtual circuits to defaults.
Use the values specified in the LightStream 2020 Configuration Guide.
Deleting one PVC hangs up MMA when hundreds of PVCs are used.
If hundreds of PVCs are created on a single port, the deleting of one PVC can take a long time. The result will be an SNMP timeout to the Net Management tool that you are using to delete the PVC. The delay could be several minutes when over 100 PVCs are created on a given port.
A bug in HP OpenView limits collections to less than 20 variables.
Data collection fails with collections set up for more than 20 variables. In compliance with the SNMP standard, the LightStream 2020 software drops such requests.
Workaround: When setting up a data collection by using HP OpenView, limit the collection to fewer than 20 variables.
The tar utility is usable with floppy disk, but it generates errors.
If you attempt to use tar on a floppy drive (for example tar xvf /dev/sd1) when no diskette is present in the drive, various uninformative error messages appear on the console. Similar error messages appear when you use a disk that has not been formatted for an IBM PS/2 (Models 50, 60, 70, 80 and compatibles). Furthermore, if you use a floppy disk with media errors, the software process using the device may hang, preventing access to the floppy or terminal where the tar command is being run.
Workaround: Reboot the network processor.
Bandwidth allocation does not check egress port capacity.
Release 1 medium-speed card counts receive errors when a cable is not attached.
When the receive port on a Release 1 medium-speed card has no cable attached or is attached to an unterminated cable, the receive error counts are incremented (if that port is configured, high error-rate traps appear on the console).
The ckswinstall command (for verifying a software installation) has two confusing aspects.
1. The ckswinstall utility reports spurious permission mismatches on directories under /usr/app.
2. When you use the ckswinstall command to verify an update distribution (for instance Release 2.0.8), ckswinstall only verifies the software in the update. On a system running an update, most of the software in use is from the original release, so ckswinstall should also be run on that original release (for example, Release 2.0.7). When you run ckswinstall on the underlying release, spurious errors are reported against software that was upgraded as part of the update.
No procedure is described for checking software on the standby NP.
When you verify 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. Here are the procedures for doing so:
Step 2 Run ckswinstall on the current backup NP.
Periodic rdist to the secondary NP doesn't check for disk space available.
On a redundant NP system, an automatic mechanism updates software and configuration information, taking data from the current primary NP and applying it 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. Furthermore, no error is reported.
Workaround: Establish a regular maintenance procedure for checking disk space availability on both NPs.
Insertion of the disk tray assembly can cause damage to connectors.
Rapid insertion of the disk tray assembly can defeat the guiding mechanism and may damage the pins of the connectors. Use care when inserting or removing the disk tray.
The Switch Fault LED lights when a redundant power supply is inserted.
The switch fault LED lights if a power tray is present, but is not generating 48 volts. When a power supply is inserted, it can take up to 750 ms to produce 48 volts after AC power is supplied. If the system checks the power supply during these 750 ms, it finds that the system is not generating 48 volts and sets the DC OK signal to False. In this circumstance, ignore the fault LED. Normal operation is never interrupted.
You do not need to enable the NP after a power-off/power-on sequence (Release 1 switch cards only).
The proper sequence to bring up a card from the TCS HUB after a power slot off command is to issue the reset slot command. This turns on the card power and initiates the card boot sequence.
Issuing a power slot on command only turns the card VCC on; it does not initiate the card boot sequence.
You may be unable to free up sufficient disk space for a new release.
When attempting to install a new release, you may be told that insufficient disk space is available on the sd0c partition. See "Special Procedure A, Freeing Up Disk Space" for instructions on deleting old releases to free up sufficient space for the new release. If, after you do this, the installation procedure still reports that insufficient disk space is available on sd0c, contact your support organization for assistance.
HUB reported POST PASSED and POST error at the same time.
There are several situations in which this can happen. With a Release 1 switch card, it happens most often when the TCS power off command is used followed by a TCS power on command.
If you are using TCS commands with a Release 1 switch card, the proper method for bringing a card back to life is to use the power off command and then to use the reset command.
The following TCS hub command reports POST passed:
The following TCS hub command reports POST_ERR:
The command show chassis listtrunks shows the same trunk twice.
The CLI command show chassis listtrunks shows a separate record for each trunk from each end. This might be improved in the future with information being consolidated into one record per trunk.
Discarded cells are not accounted for in CLI statistics.
On the OC3 card, the per-port Discarded Rcvd Packets statistic in the CLI show port display does not include permit drops. Permit blocks are displayed correctly in the per-VCI statistics.
PVC has no "Save As" file menu item
The PVC and VLI configurators do not support a "Save As" function. To create copies of the database, use the "Save As" option of the node configurator (cfg). Do not copy the .dat/.pag files with bash shell commands.
You cannot connect to backup NP in diagnostic mode.
Network processor (NP) diagnostics must be run from the hub. The mechanism by which diagnostics are run on some cards using the CLI on the primary NP (the CLI test command) is not supported for running diagnostics on a second NP.
The deleted PVC cannot be added in again: "Waiting to be deleted from switch."
The current implementation restriction requires that, after initiating a download, the user wait until the download completes before trying to modify the records involved in the download. Further, the user needs to reread the database after the download completes before modifying the records.
Fallback from swchgver does not copy config files back.
LightStream 2020 configuration information is stored on disk as part of a specific release. Configuration information from an old release is copied forward to a new release as part of installation of the new release. Configuration information, however, is not automatically copied between releases when swchgver is used to change the current release.
Take, for example, the situation where a node is upgraded to run new software and, after the upgrade, configuration changes are made. If the node is then downgraded to a previous release, the node runs with the configuration information that was cached at the time of the upgrade, not the changes that were made after the upgrade.
After falling back to an old version, the current configuration cache can be downloaded to the node to set the newest configuration.
Alternatively, before falling back to an old version, the files in /usr/app/base-newrel/config can be copied to /usr/app/base-oldrel/config (replace newrel and oldrel with the appropriate release numbers, such as 2.0.8 and 2.0.7).
External bridge loops cause loss of VLI functionality.
When configuring LightStream 2020 nodes with external topology loops, configure the bridge priority for the nodes to make one node the spanning-tree root.
The rate information produced by the CLI when displaying port statistics is not accurate.
An ATM UNI or FF port reports operationally up when disconnected.
Currently, the frame forwarding and ATM-UNI interfaces cannot report their actual operational status. This is because these interfaces do not provide a link-level reliability indication (such as the LMI for FR or Trunk-Up-Down (TUD) for LightStream 2020 trunks). The operational status on these ports is always the same as the administrative status of the port. The operational status does not indicate physical layer or data-link layer status.
Request a way to abort an unwanted download.
Currently, there is no function for aborting long downloads. However, it is possible to abort downloads with the UNIX kill command. 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, because 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, the downloads can be distinguished only by remembering the order in which they were invoked (one with a lower PID was invoked earlier, and one with a higher PID was invoked later). Even when the correct process is killed, the results can be unpredictable, because part of the configuration might have been downloaded.
FR should be upgraded to support T1.617a-1993.
The Frame Relay LMI conforms to T1.617-1991 but has not been upgraded to meet T1.617a-1993. This should not affect normal operation of the port, but may affect conformance tests designed to verify the updated standard. The FR port interoperates with LMIs that conform to either version of this standard.
The file Open/Save dialog box filter does not work.
If you are making a backup of the global database using the Save As command, the backup file should end in the .pag extension.
CDN #1745 (NP1 diagnostic fails tests 22,23,24 intermittently).
This is a problem with the revision of the PIT timer used on some NP cards. A modified software algorithm has been put in the NP to make this test more reliable. Some problems remain.
The procedure to make backup copies of install diskettes should be documented in the Network Operations Guide. See "Special Procedure E, Backing Up the Distribution Diskettes."
File->Open defaults to the home directory of the ovw initializer.
When a database is opened from the File->Open menu item, the path defaults to the home directory of the initiator of ovw instead of following LSC_DATABASE.
Workaround: Double-click in Directories to navigate to the /usr/OV/databases/ls directory, and then select the appropriate directory.
The Release 1 switch card and the Release 2 switch card interoperate with the following modems:
Zoom 9624V
Zoom FXV (FX9624V)
Hayes SmartModem 2400 V.24
Using any other modem may cause unpredictable results.
OC-3 card continuously bounced when connected to SONET MUX.
When connecting an OC3 port to a SONET multiplexor, you should normally use a clocking type of external (rather than the default of internal). Use of internal clocking may prevent the port from operating correctly.
External SNMP devices impact system performance.
The NP software does not throttle excess traffic from external SNMP devices. This can consume CPU resources and cause timeouts, such as spanning-tree timeouts that degrade system performance. Typical sources of SNMP packets include the LightStream 2020 monitor, HP OpenView statistical graphing facilities that display a large number of MIB variables, and third-party network management applications. When SNMP traffic is degrading system performance, you must reduce the SNMP traffic from the external device. You might reduce the number of variables being tracked, increase the polling interval, or reduce the number of concurrent network management processes which are requesting data.
The command set card card# testing no longer works and is rejected by the CLI. The test command puts the card in the testing state. Use the command test card# -m to put card card# in the testing state, load diagnostics, and establish an I/O tap connection from the CLI to card card#.
The Release 2.0 Installation and Troubleshooting Manual, on page 3-38, says to search the /etc/services file for the string snmp-traps. It should say to search for the string snmp-trap.
Page 3-42 of the same document suggests that you change the polling interval to 1 minute. The polling interval should be left at the default of 5 minutes.
When connected to an FDDI with an AGS+, the LightStream 2020 switch loses a small number of ping requests and responses. Probes on the FDDI Access Card have detected the LightStream 2020 inserting an IDLE/VIOLATION symbol pair and idles after the source address is transmitted. The cause and conditions for this behavior are not currently known. The problem is under investigation.
This section provides information about upgrading the LightStream 2020 enterprise ATM switch to release 2.0.9 of LightStream 2020 software.
Note The following procedures are for upgrades, not for new installations. If you are installing a network processor (NP) with an uninitialized disk, use the installation procedures given in the LightStream 2020 Installation Guide. Use the upgrade procedures described here only if you are upgrading software on a LightStream 2020 node that has already been installed and is running.
Note The following procedure for software installation of Release 2.0.9 causes flash memory to be reloaded. The flash reload time depends on your system configuration. Also, you must explicitly reload switch card flash memory according to the installation procedure.
For Release 2.0.9 to be installed, the network processor must have 32 Mb of memory.
For Release 2.0.9 to be installed successfully, you must currently be running at least Release 2.0.3 software.
You must have a modem in each remote node to which the software upgrade is to be sent. Refer to the section entitled "Modem Recommendations" in the LightStream 2020 Site Planning and Cabling Guide.
| Caution The LightStream 2020 NP is a special-purpose communications processor. It should not be used as a general-purpose UNIX host. If any files have been copied to or placed on the disk (especially in the root partition), they should be removed before the upgrade to release 2.0.9. If the names of any Cisco-provided files have been changed, the original file names should be restored. |
Below is a list of the LightStream 2020 Release 2.0.9 node software distribution diskettes.
| LightStream 2020 Release 2.0.9 Distribution Diskettes | Version Listed on Diskette Label |
|---|---|
The following procedures are used to upgrade a network to Release 2.0.9 software:
Use the swinstall command to copy the new software from the installation diskettes to the node being used as the software distribution node. (If swinstall reports insufficient disk space, you will be directed to perform Special Procedure A, Freeing Up Disk Space.)
Use the swremoteinstall command to copy the new software from the distribution node to other nodes in the LightStream 2020 network. (If swremoteinstall reports insufficient disk space, you will be directed to perform Special Procedure A, Freeing Up Disk Space.)
Use the swchgver command to change the version of software running on each node after copying the new software to the node.
Verify that the current version of switch card flash memory is present on the switch cards, and upgrade it if necessary.
These procedures are not normally needed. However, it is possible that an upgrade step will require you to perform one or more of these procedures.
If the swinstall command or the swremoteinstall command reports that you do not have enough disk space, delete files for obsolete releases of software.
You have the option of falling back to the prior version of software if you wish to do so for any reason.
If the swchgver command fails to contact the backup NP on a redundant system, look in this section for some of the common causes and how to correct them.
If the swremoteinstall command (which uses the rsh command) reports that it does not have permission to copy the files to the remote node, look in this section for some common causes and how to correct them.
Some users may wish to back up the distribution diskettes.
With this procedure you copy the new software from the distribution disk set to a local LightStream 2020 node. This local node is referred to as the distribution node. In Procedure 2, Copy New Software to Remote Nodes , you use the distribution node as the source from which to copy the software to other nodes in the network.
Note If for any reason you discontinue installation of this release after you have started loading software, you should delete this release using Special Procedure A, Freeing Up Disk Space. This minimizes the impact of the interrupted installation on future installations. When you resume installation of this release, you must restart at the beginning of this procedure.
The following tasks are necessary for an upgrade of the distribution node (or any local node) to Release 2.0.9 node software:
1. Connect to the Primary NP .
2. Copy Release 2.0.9 Software from Floppies to Hard Disk .
To perform these tasks, use a terminal connected to the console port of the distribution node. The system should be running with no one else logged on the system.
Step 2 At the TCS HUB prompt, use the connect command to connect to the NP in slot 1:
You may need to press [Return] a second time after typing the connect command in order to get a prompt from the NP.
A prompt should appear asking for a user login name:
Note If someone using the machine before you has not logged out, your prompt may be different from the one shown here. If this occurs, log out and log back in as root.
Step 3 Log in as root. The bash prompt appears (with # indicating a root login).
If your system has only one NP, go to Step 6 now. |
Step 4 On a system with redundant NPs, verify that you are connected to the primary NP (the active NP):
If the two entries identify the same NP number, then you are connected to the primary NP (the active NP). Since you connected to slot 1 in Step 2 above, the following is true: Make a note of this. You will use the value 1 where you see the parameter name "primary" in later procedures. If the two entries do not identify the same NP number, then you are connected to the backup NP. Since you connected to slot 1 in Step 2 above, the following is true: Make a note of this. You will use the value 2 where you see the parameter name "primary" in Step 5, below, and in other procedures. |
Step 5 If you are connected to the backup NP, disconnect from it and connect to the primary NP (the active NP) as follows:
Step 6 Determine which floppy disk drive is appropriate to use for the upgrade. NP slot 1 is connected to the bottom disk drive, and NP slot 2 is connected to the top disk drive.
The boot disk is not used in this upgrade procedure. You will run the swinstall utility once for each diskette set. If you are currently running any version from Version 2.0.3 through 2.0.8a3, install the diskette sets in this order: system, application, diagnostics, firmware.
Step 7 Enter the swinstall command at the bash prompt:
If the swinstall program reports that there is insufficient disk space for the installation, carry out Special Procedure A, Freeing Up Disk Space, before continuing. |
When the program prompts you for a diskette, insert the first diskette (of the diskette set that you are currently installing) into the appropriate drive and press [Return]. Repeat as the program prompts you for more diskettes in the current set.
Step 8 Repeat Step 7 for each diskette set, following the order given under Step 6.
With this procedure you distribute new software from the distribution node to other LightStream 2020 nodes. Carry out this procedure for each remote node in turn. Then carry out Procedure 3, Change the Running Software Version, for each remote node in turn. After all other nodes have and are running the new software, carry out Procedure 3, Change the Running Software Version, on the distribution node.
Note It is also possible to upgrade software directly from the distribution diskettes on each node in your LightStream 2020 network. To do this, carry out Procedure 1, Copy New Software to the Distribution Node , and Procedure 3, Change the Running Software Version, on each node in the network.
The following connectivity requirements apply:
| Distribution Node | Remote Node |
|---|---|
Carry out these tasks for each node in your LightStream 2020 network in turn:
1. Verify Remote Command Execution
2. Distribute Release 2.0.9 to the Remote Node
Verify that it is possible to execute commands on the remote node from the distribution node.
Enter the name of the remote node in place of remote-node.
If the command succeeds, it prints the name of remote-node. Continue to Step 2 . If the command fails, it prints one of the following messages:
hostname: unknown host Refer to the Special Procedures, Special Procedure D, Getting rsh to Work Successfully on a Remote Node. |
Note If this is the first time you have upgraded, then this step is likely to fail. For more information, see "Special Procedure D, Getting rsh to Work Successfully on a Remote Node" later in this document.
Step 2 Copy Release 2.0.9 files to remote-node. In a window running a login on distribution-node, execute the following command:
Enter the name of the remote node in place of remote-node.
The swremoteinstall process checks disk space and copies Release 2.0.9 to remote-node. It should take 5 to 10 minutes, depending upon bandwidth between the nodes.
If the swremoteinstall program reports that there is not enough disk space for the installation, connect to the remote node through a modem port or telnet connection and follow Special Procedure A, Freeing Up Disk Space on the remote node. Then repeat Step 2 . |
With this procedure you activate the software that has been copied to the node, and the node begins running the new LightStream 2020 application software.
Carry out these tasks for each node in your LightStream 2020 network in turn:
2. Change the Running Software Version
| Caution Do not use a network connection such as Telnet to connect to the node for purposes of changing the running software version. During the procedure, a card may be reset, breaking your Telnet connection and interrupting the change process. |
Step 2 Enter `. (backquote plus dot, that is, left single quote plus period).
Step 3 At the TCS HUB prompt, use the connect command to connect to the NP in Slot 1, as follows:
The user name: prompt should appear. Log in as root. The bash prompt appears (with # indicating a root login).
You may need to enter a second [Return] after typing the connect command in order to get a prompt from the NP.
If someone using the machine before you has not logged out of their session, your prompt may be different than the one shown above. Attempt to get back to a bash prompt and log out.
Step 4 On a system with redundant NPs, verify that you are connected to the primary NP:
If the two entries identify the same NP number, then you are connected to the primary NP (the active NP). Since you connected to slot 1 in Step 3 above, the following is true: Make a note of this. You will use the value 1 where you see the parameter name "primary" in later procedures. If the two entries do not identify the same NP number, then you are connected to the backup NP. Since you connected to slot 1 in Step 3 above, the following is true: Make a note of this. You will use the value 2 where you see the parameter name "primary" in Step 5, below, and in other procedures. |
Step 5 If the two entries identify the same NP number, you are connected to the primary NP. If you are connected to the backup NP, disconnect from it and connect to the primary NP as follows:
Substitute 1 or 2 in place of primary, using the value that you arrived at in Step 4, above.
Note The swchgver program ordinarily takes about a minute to run. However, it can take as much as 2.5 hours if it loads program images into flash memory on all the cards (about 15 minutes per card for ten cards). A card's fault light comes on and stays on for the duration of loading of flash on that card.
Step 6 Use the swchgver program to run the software that you have just installed:
The swchgver program produces the following results:
| Caution Do not interrupt the loading of flash memory, particularly on an NP. A card with partially loaded flash cannot complete its boot sequence until flash is reloaded. If you create this situation, call Cisco Customer Support at 1-800-553-NETS (6387) or 1-800-553-2447. |
Step 7 On a redundant NP system, the swchgver program automatically copies the new software from the primary NP (the currently active NP) to the backup NP. This copy may fail—for example, if the other NP is not currently running application software. If the copy fails, the swchgver program may print out a diagnostic message and return to the bash prompt.
Example of a diagnostic message:
If this occurs, refer to Special Procedure C, Verifying Connection to Backup NP
The following is an example of output seen when this upgrade procedure is carried out with the console trap level set to info:
With this procedure you verify the version of flash memory in each node's switch cards, and upgrade if necessary.
If the verification step that follows indicates that switch card flash needs to be upgraded, a console connection to the NP is required for performance of the upgrade. To do this, you must use either a console terminal located at the node site or a dial-in modem connected to the TCS HUB modem port.
| Caution
This operation takes your node out of operation. |
Carry out this procedure for each node in your LightStream 2020 network in turn:
2. Verify Need to Upgrade Switch Card Flash
4. Repeat for Redundant Switch (if applicable)
5. Reboot NP
6. Verify Flash Version on All Upgraded Switch Cards
Step 2 Determine the checksum for the switch card flash image.
If the flash checksum is 0x64A2 for a Release 2 switch card or 0x5D00 for a Release 1 switch card, the specified switch card already has the latest flash image.
As above, if the flash checksum is 0x64A2 for a Release 2 switch card or 0x5D00 for a Release 1 switch card, the specified switch card already has the latest flash image.
Note A card whose flash checksum is not as specified above does not have the latest flash image.
Perform Step 3 through
Step 12 of this procedure for each such
card. If both cards (or one in a non-redundant system) have the latest flash image, skip the remaining
steps of the procedure
(Step 3 through
Step 12).
Step 3 If a new image is to be loaded into flash on a switch card, shutdown the node:
The following display appears:
Step 4 At the Option> prompt, select Option 6:
The following display appears:
Step 5 At the Boot: prompt, enter the following command (the 0 in sd0b is a zero):
The node reboots using the system monitor software. The following display appears:
Step 6 Load the switch card flash memory for Slot A.
If you see the following error message, repeat Step 6: If you do not see this message, and you do not see the System Monitor-> prompt, go to Step 7. If you see the following error message when loading a Release 1 switch card, reboot the primary NP: Then perform Step 2 to verify that the checksum is 0x5D00. This problem only occurs with redundant Release 1 switch cards. The message is misleading, because the flash update does complete successfully.
If you do see the System Monitor-> prompt, the flash load has completed successfully. Go to |
Step 7 If you do not see the System Monitor-> prompt, the flash load has failed. Do the following:
The following display appears:
Memory Autosizing ... (32 Meg) ... Done
Clearing 32 Meg Memory ... Done
NP1 POST Version 0.225 Feb 21, 1995
NP1 POST Summary
----------------
0 Tests Failed
System will boot in 5 seconds: hit <RETURN> to interrupt.
This prompt is repeated once a second, giving you more than one opportunity to press the [Return] key and prevent a reboot. When you press [Return], the boot menu appears:
System will boot in 5 seconds: hit <RETURN> to interrupt.
System will boot in 4 seconds: hit <RETURN> to interrupt.
Network Processor bootstrap (version 1.3: Sep 13 1993)
1 - Boot ATM switch application
2 - Begin full installation with boot from floppy disk
3 - List contents of hard disk root directory
4 - List contents of floppy disk root directory
5 - Boot system single-user
6 - Escape to full set of bootstrap options
7 - Extended help
Option>
Step 8 If there is a redundant switch card in Slot B, load the switch card's flash memory.
If you see the following error message, repeat Step 8: If you do not see this message and do not see the System Monitor-> prompt, go back to Step 7 followed by Step 4 and Step 5 (as specified in Step 7). After performing Step 5, resume the present procedure at Step 9 . If you see the following error message when loading a Release 1 switch card, reboot the primary NP: Then perform Step 2 to verify that the checksum is 0x5D00. This problem only happens with redundant Release 1 switch cards. The message is misleading, because the flash update does complete successfully. If you see the System Monitor-> prompt, the flash load has completed successfully. Go to Step 9 . |
Step 9 To load operational software into the NP, reboot it as follows:
Step 10 Log in on the NP as root.
Step 11 To see the current flash checksums of Switch Card A, enter the following command:
To see the current flash checksums of Switch Card B, enter the following command:
If the flash checksum is 0x64A2 for a Release 2 switch card or 0x5D00 for a Release 1 switch card, the specified switch card now has the latest flash image.
Step 12 If the switch card has an incorrect flash checksum, load the flash again by executing the present procedure, Procedure 4, Verify Switch Card Flash.
Verify flash again (Step 10 and Step 11 above).
If the card still has an incorrect flash checksum after you load flash a second time, contact Cisco Customer Support at 1-800-553-NETS (6387) or 1-800-553-2447.
Use this procedure if swinstall or swremoteinstall reports that there is insufficient disk space.
Step 2 Identify the software to remove. To do this, enter the command swdelete with no argument, as in the following example:
If you attempt to delete the running version of software, the following message appears:
Step 3 Use the swdelete command to delete obsolete version files:
| Caution Do not delete the currently running software versions (2.0.7 and 2.0.8 in the example shown in Step 2, above). |
Return to the section that referred you to this procedure ("Procedure 1, Copy New Software to the Distribution Node " or "Procedure 2, Copy New Software to Remote Nodes ").
Use this procedure if you wish to revert to the prior version of software:
Step 2 Use Procedure 3, Change the Running Software Version, to revert to the prior version, giving the earlier version number as the argument of the swchgver command. For example, if the prior version is 2.0.8, enter the command as follows:
Note LightStream 2020 configuration information, when downloaded from the NMS, is stored with the current release. When you upgrade to a new release, that configuration information is copied forward to initialize the new release's configuration. When falling back to a previous release, the configuration will match the last time that software release was operational, which may not reflect the current configuration.
Use this procedure to verify that the primary NP can communicate with the other NP.
To perform this procedure, you should be using a terminal connected to the console port of a chassis with redundant NPs.
Note In this procedure the other NP is assumed not to be rebooting. During reboot, the other NP is not accessible for several minutes.
Step 2 If you are not already logged in to the primary NP as root, log in to the primary NP as root.
Step 3 If there is a redundant NP in this chassis, verify that the other NP is functioning as backup. Enter the following command:
The following results are possible:
bash# rsh other-np /bin/true
bash#
This result indicates success. The other NP is up and accessible. Return to the section that referred you to this Special Procedure ("Procedure 3, Change the Running Software Version").
bash# rsh other-np /bin/true
other-np: connection timed out
bash#
This result indicates that the backup NP is not up. Go to Step 4 .
bash# rsh other-np /bin/true
Permission denied.
bash#
This result indicates that the backup NP is up, but not accessible because of a permissions mismatch. Go to Step 4 .
Step 4 The following error message may be generated (after about 75 seconds):
If this message is displayed, reset the other NP:
Step 5 The following error message may be generated:
If this message is displayed, the rsh permissions on the backup NP are incorrect.
bash# rsh other-np
login root vt100
password:
.
.
.
bash#
bash# cp /.rhosts /.rhosts.bak
bash# echo "other-np root" >>/.rhosts
Note Be sure you enter the redirect operator twice, with no space (>>). If you enter it only once (>), you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /.rhosts.bak /.rhosts to recover the original file.
Return to the section that referred you to this procedure ("Procedure 3, Change the Running Software Version").
Use this procedure if the rsh command reports an error message:
bash# grep remote-node /usr/etc/hosts
bash# cp /usr/etc/hosts /usr/etc/hosts.bak
bash# echo "Primary_IP_address remote-node" >> /usr/etc/hosts
Enter the name of the remote node in place of remote-node and the IP address of the remote node in place of Primary_IP_address. (You can use the vi editor in place of the echo command. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.)
Note Be sure you enter the redirect operator twice, with no space (>>). If you enter it only once (>), you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /usr/etc/hosts.bak /usr/etc/hosts to recover the original file.
If you see the error message "Permission Denied" or any other message, ignore it and continue to Step 2.
Step 2 Make a telnet connection to remotenode and log in.
Step 3 Verify that the .rhosts file is a read-only file for group and world:
If any value other than -rw-r--r-- appears at the beginning of the ls output, enter the following command:
Step 4 Examine the file /.rhosts to see if it includes an entry for distribution-node. Use the following command (enter the name of the distribution node in place of distribution-node):
Step 5 If the entry for distribution-node is not displayed, edit the file /.rhosts, adding to it a line consisting of the name of the distribution node followed by the word root (enter the name of the distribution node in place of distribution-node):
(You can use the vi editor in place of the echo command. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.)
Note Be sure you enter the redirect operator twice, with no space (>>). If you enter it only once (>), you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /.rhosts.bak /.rhosts to recover the original file.
Step 6 On the remote node, examine the file /usr/etc/hosts to verify that there is an entry for distribution-node in it. You can use the grep command for this (enter the name of the distribution node in place of distribution-node):
Step 7 If there is no entry for distribution-node, create one:
Enter the IP address of the distribution node in place of Primary_IP_address, and the name of the distribution node in place of distribution-node. (You can use the vi editor in place of the echo command. See the LightStream 2020 NP O/S Reference Manual for information about the vi editor.)
Note Be sure you enter the redirect operator twice, with no space (>>). If you enter it only once (>), you will overwrite the existing file rather than appending to it. If you make a mistake, enter the command cp /usr/etc/hosts.bak /usr/etc/hosts to recover the original file.
Step 8 Log out of the remote node and repeat Step 1.
If the test fails again, contact Cisco Customer Support at 1-800-553-NETS (6387) or 1-800-553-2447.
Return to the section that referred you to this procedure ("Procedure 2, Copy New Software to Remote Nodes ").
To protect the software distribution diskettes, you can back them up before proceeding with the upgrade.
In this procedure, you are assumed to have access to a PC running DOS 5.0 or later and supporting at least one 1.44 MB floppy disk drive. You are also assumed to have a supply of at least 15 blank, DOS-formatted 1.44 MB diskettes.
Note With the /v option, the diskcopy command verifies that the copy is correct. If you wish to use the diskcomp command redundantly to verify that the copy is correct, refer to your DOS documentation for that command.
Note Do not use the dir command to verify the contents of the diskette. There is no FAT (the DOS file allocation table) on LightStream 2020 distribution diskettes, so there can be none on your backup diskettes. Consequently, if you enter dir a: or dir b:, DOS issues a read error message.
For each LightStream 2020 software distribution diskette, do the following:
Step 2 Insert the blank, formatted diskette in the second 1.44 MB disk drive. (In the examples shown here, this is Disk Drive B.
Step 3 Enter the following command at the DOS prompt:
Step 4 The program copies the data from the distribution diskette in Drive A to the backup diskette in Drive B.
For each LightStream 2020 software distribution diskette, do the following:
Step 2 Enter the following command at the DOS prompt:
Step 3 The program reads a portion of the disk contents into memory. When it prompts you to do so, remove the distribution diskette and insert a blank, formatted diskette into the floppy disk drive.
Step 4 The program copies the data from memory onto the diskette. When it prompts you to do so, remove the backup diskette and insert the distribution diskette into the floppy disk drive.
Step 5 Alternate Step 3 and Step 4 in response to program prompts until the disk copy is complete.
The platform bugs listed below have been fixed in Release 2.0.9.
The platform bugs listed below have been fixed in Release 2.0.8a2 and are incorporated in Release 2.0.9.
Posted: Thu Jan 23 06:50:31 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.