Troubleshooting guide

17
Software Upgrade Procedures
Outline of Upgrade Procedures
The following procedures are used to upgrade a network to Release 2.0.9 software:
Procedure 1, Copy New Software to the Distribution Node
Use the swinstall command to copy the new software from the installation diskettes to the node
being used as the software distribution node. (If swinstall reports insufficient disk space, you will
be directed to perform Special Procedure A, Freeing Up Disk Space.)
Procedure 2, Copy New Software to Remote Nodes
Use the swremoteinstall command to copy the new software from the distribution node to other
nodes in the LightStream 2020 network. (If swremoteinstall reports insufficient disk space, you
will be directed to perform Special Procedure A, Freeing Up Disk Space.)
Procedure 3, Change the Running Software Version
Use the swchgver command to change the version of software running on each node after
copying the new software to the node.
Procedure 4, Verify Switch Card Flash
Verify that the current version of switch card flash memory is present on the switch cards, and
upgrade it if necessary.
Outline of Special Procedures
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.
Special Procedure A, Freeing Up Disk Space
If the swinstall command or the swremoteinstall command reports that you do not have enough
disk space, delete files for obsolete releases of software.
Special Procedure B, Falling Back to the Prior Version
You have the option of falling back to the prior version of software if you wish to do so for any
reason.
Special Procedure C, Verifying Connection to Backup NP
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.
Special Procedure D, Getting rsh to Work Successfully on a Remote Node
If the swremoteinstall command (which uses the rsh command) reports that it does not have
permission to copy the files to the remote node, look in this section for some common causes and
how to correct them.
Special Procedure E, Backing Up the Distribution Diskettes
Some users may wish to back up the distribution diskettes.