1.

If the cause of the node stoppage is being investigated, replace the Core MP(s
) with new boards, if possible. Then go to Step 4. If the boards cannot be repl
aced, collect traces from the node by using the following commands: ?bs -g -c "t
e log read" > /d/node_data.txt
?bs -g -c "llog -l" >> /d/node_data.txt
?bs -g -c "vii" >> /d/node_data.txt
?bs -g -c "dumpelg" >> /d/node_data.txt
2.Save information regarding the CV usage by using the command:
cv cu >> /d/node_data.txt.
3.Back up the following files and directories to the PC: ?/d/node_data.txt
?/c/logfiles
?/c/systemfiles
?/c/pmd
Note: Use binary mode when transferring files to and from the node.
4.Unzip the backup CV on the PC, if not already done.
5.Unzip the UPs on the PC, if not already done.
6.If the node has two Core MPs, stop the Core MP that will not be used for loadi
ng the node. Connect the PC to the serial port on the board for the MP, and exec
ute the command reload --.
7.Stop the Core MP that will be used for loading the node, by connecting the PC
to the serial port on the board, and execute the command reload --.
8.Set the IP configuration in the node, with the command ifconfig le0 <ipaddress
> netmask <netmask> broadcast <broadcastaddress>.
9.Set the default gateway address in the node with the command route add default
<gateway>.
10.Make the new IP configuration active in the node, by restarting the board aga
in with command reload --.
11.Verify that the /c2 volume is mounted by using the command vols /c2. If the /
c2 volume is not mounted, mount the volume using the command mount_c2.
12.Make sure that any CV control files in the node can be overwritten, using the
command chmod 777 /d/cv.ptr /d/rollback.cnt /d/rollback.ini.
13.Open a command prompt window on the PC, and go to the \misc directory of the
CV to be restored, with the command cd <pathToCV>\misc.
14.If the hardware configuration has been changed since the backup CV was create
d, edit the file that controls the autoconfiguration in the node (autoconfig.xml
). This is explained with comments within the file.
15.Transfer the CV to the node with the command ftp -v -s:cvftpput.sh <ipaddress
>. <ipaddress> is the IP address of the node.
When executing the command, stay in the \misc directory of the CV to be restored
.
16.Go to each UP directory that has to be transferred to the node, and transfer
the UP files with the command ftp -v -s:<pathToCV>\misc\upftpput_<no_rev>.sh <ip
address>.
When executing the command, stay on the same level in the structure as where the
Upgrade Control File (UCF)<ucf>.xml is located.
Note: The upftpput_<no_rev>.sh script expects that the name of the UCF on the P
C is the same as the name of the UCF on the FTP server when the UpgradePackage M
O is created.
17.Start the node with the command reload.
18.Verify that the correct time is set in the node by using the command readcloc
k. If the time is incorrect, set the time by using the command setclock <YYYY-MM
-DD HH:MM:SS>.
19.When the node has started successfully, look for a possible alarm on the MO S
ecurity. Act on the alarm by using the corresponding instruction.
20.Verify that the correct security level is set by reading the attribute secmod
e in the Security MO. If necessary, set the desired security level using the ins
truction Setting Security Level.
21.Look for a possible alarm on the MO Licensing. The License Key File might be
missing after the stoppage and must then be reinstalled by using the action upda
teLicenseKeyFile on the MO Licensing.
22.Make other reconfigurations that are necessary. As the CV can be old, or has
even come from another node, and the disks might have been formatted, both traff
ic and O&M-related reconfigurations might be needed.
23.If there is a redundant Core MP that was stopped in Step 6, connect the PC t
o the serial port on the board, and execute the command reload to start it again
.
24.If necessary, create a new CV, that contains the reconfigurations made in St
ep 22, and set it to startable. See Upgrade and Backup.
25.The node creates a new CV in step Step 17, containing the possibly new IP pa
rameters. Consider deleting the downloaded CV at a later stage. The CV cannot be
deleted at this time, as it is loaded.