Troubleshooting guide

32
Special Procedures
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”).
Special Procedure B, Falling Back to the Prior Version
Use this procedure if you wish to revert to the prior version of software:
Step 1 Log in to the Primary NP as root if you have not already done so.
Step 2 Use Procedure 3, Change the Running Software Version, to revert to the prior version,
giving the earlier version number as the argument of the swchgver command. For example,
if the prior version is 2.0.8, enter the command as follows:
bash# swchgver 2.0.8
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.
Note The fallback procedure does not reload old flash versions in cards.
Special Procedure C, Verifying Connection to Backup NP
Use this procedure to verify that the primary NP can communicate with the other NP.
To perform this procedure, 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 1 If you are not already connected to the slot of the primary NP, connect to the primary NP.
Do this by typing ‘. (backquote plus dot, that is, left single quote plus period) to connect
to the TCS hub, and entering the following command (substituting the slot number of the
primary NP for primary ):
TCS HUB<<A>> connect primary
Step 2 If you are not already logged in to the primary NP as root, log in to the primary NP as root.