Troubleshooting guide

23
Software Upgrade Procedures
Connect to the slot of the primary NP (the active NP) by typing the following command:
TCS HUB<<A>> connect
primary
Substitute 1 or 2 in place of primary, using the value that you arrived at in Step 4, above.
If necessary, log in to the NP as root.
Change the Running Software Version
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:
bash# swchgver
The swchgver program produces the following results:
Flash memory is reloaded (if appropriate).
The newly installed software is made the active version (on both NPs in a redundant
system).
The network processor (NP) is rebooted, so that the above changes take effect (both NPs
in a redundant system).
The line cards reload their software images.
Caution Do not interrupt the loading of flash memory, particularly on an NP. A card with partially
loaded flash cannot complete its boot sequence until flash is reloaded. If you 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:
WARNING: Unable to contact standby network processor:
Use [-force] option to bypass standby network processor.
[Consult your release note for advice on dealing with
a failure distributing to the other network process.]
If this occurs, refer to Special Procedure C, Verifying Connection to Backup NP
If everything fails then someone physically at the node site must later install the software on the
other NP as though it were a new NP/disk addition. See the LightStream 2020 Network
Operations Guide.