Troubleshooting guide

21
Software Upgrade Procedures
Enter the name of the remote node in place of 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.
Distribute Release 2.0.9 to the Remote Node
Step 2 Copy Release 2.0.9 files to remote-node. In a window running a login on distribution-node,
execute the following command:
bash# swremoteinstall -h remote-node 2.0.9
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.
Procedure 3, Change the Running Software Version
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.
Overview
Carry out these tasks for each node in your LightStream 2020 network in turn:
1 Connect to the Primary NP
2 Change the Running Software Version
Connect to the Primary NP
Step 1 Connect to the TCS hub on the node. Use a console terminal if you are on site. Use a dial-in
modem to connect to a remote node.
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.
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
hostname : Connection timed out
Permission denied.
Refer to the Special Procedures, Special Procedure D, Getting rsh to Work Successfully on a
Remote Node.
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.