The instructions include commands of the following types: Command Line Interface (COLI) commands operating on the node.

e. These types of commands are always entered in the terminal emulation software of the PC. Windows commands operating on the PC. These types of commands are always entered in the command prompt window of the PC and are addressed in these instructions with the slogan "Windows command".

1. Preparing CV and UPs on PC

To prepare the external backup CV and UPs on the PC, proceed as follows: 1. Extract the contents of the zipped files containing the external backup CV onto the PC, if not already done. 2. Extract the contents of the zipped files containing the UPs onto the PC, if not already done. 3. On the PC, go to the \misc directory of the CV to be restored. 4. Edit the autoconfig.xml file that controls the autoconfiguration in the node. This is explained by comments within the file. 5. If necessary, edit the ipaddress2.xml file that sets the IP parameters of the Gigabit Ethernet interface. Edits to perform are explained by comments within the file. Editing the file is normally necessary only when the backup CV is from another node than the one to restore.

2. Verifying Node IP Configuration

To verify the IP configuration of the Fast Ethernet port of the DU before using it to transfer backup files from the PC, proceed as follows: 1. Connect the PC to the serial port (labeled LMT A) and the Fast Ethernet port (labeled LMT B) of the DU, as described in Connecting a Client Computer. The

communication on the Fast Ethernet port must not necessary be working at this point. 2. Stop the DU by restarting it in forced backup mode using the reload -command on the serial port. 3. Verify that the /c2 volume was automatically mounted using the vols command. If the /c2 volume is not mounted, mount the volume using the mount_c2 command. 4. Verify connectivity on the Fast Ethernet port of the DU using command ping <ipaddress> from the Windows command prompt. The default and normally never changed IP address is 169.254.1.10. 5. Was the ping successful resulting in a response from the node? Yes: go to Section 3 No: continue to the next step. 6. Check the IP configuration of the Fast Ethernet port in the node using the ifconfig command. The IP configuration of the PC must match the IP configuration of the node as described in Connecting a Client Computer. The Fast Ethernet port is the le0 interface that corresponds to the EthernetLink MO if the MO structure is configured. 7. If necessary, set the IP configuration in the node by <ipaddress> netmask <netmask> broadcast command ifconfig le0 <broadcastaddress>. 8. Check the default gateway address in the node using the route command. The default gateway in the node must match the IP address of the PC. 9. If necessary, set the default gateway address in the node using the route add default <gateway> command. 10. If the IP configuration is changed, make the new IP configuration active by restarting the DU using the reload -- command.

11. Verify that the /c2 volume is mounted using the vols /c2 command. If the /c2 volume is not mounted, mount the volume using the mount_c2 command. 12. From the Windows command prompt, verify IP connectivity to the Fast Ethernet port of the DU using the Windows command ping<ipaddress>, where <ipaddress> is the le0 IP address of the node.

3. Transferring and Activating Backup CV and UPs

To transfer the external backup CV and UPs from the PC to the node and to start the node using the backup, proceed as follows: 1. 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. 2. Open a command prompt window on the PC and go to the \misc directory of the CV to be restored using the Windows command cd <pathToCV>\misc. 3. From the Windows command prompt, transfer the CV to the node using the Windows command ftp -v -s:cvftpput.sh <ipaddress>, where <ipaddress> is the le0 IP address of the node. When executing the command, stay in the \misc directory of the CV to be restored. 4. On the PC, go to each UP directory to be transferred to the node, and transfer the UP files using the Windows command ftp v -s:<pathToCV>\misc\upftpput_<no_rev>.sh <ipaddress>. When executing the command, be on the same level in the structure as where the <up>.xml (Upgrade Control) file is located. 5. Start the node by using the reload command. Wait until the node has started successfully on the transferred backup CV.This takes several minutes. The DU is restored with the backup CV and UPs when it has started successfully.

4. Restoring Licenses and Security Configuration

To restore licenses and the O&M security configuration, proceed as follows: 1. Verify that the correct time is set in the node using the readclock command. If the time is incorrect, set the time by using the setclock command.

2. Check for alarms on the Security MO. Act on alarms using the corresponding instruction. 3. Verify that the correct security level is set by checking the Security.requestedSecurityLevel attribute or by using the secmode -s command. If necessary, set the desired security level as described in Setting Security Level. Note: Changing the node password must always be synchronized with OSS-RC. To set or change the node password, follow the instructions in Security for O&M Node Access and the OSS-RC document Security System Administration, OSSRC. 4. Check for alarms on the Licensing MO. The LKF might be missing after the stoppage and must then be reinstalled using the Licensing.updateLicenseKeyFile action. If the backup CV was from another node, make sure setting the correct node name on the ManagedElement.logicalName parameter before installing the LKF. 5. Perform other necessary reconfigurations. Since the backup CV may be old, come from another node, or the disks might have been formatted, both traffic and O&Mrelated reconfigurations might be necessary. When this step and all the steps above are successfully completed, the DU is fully restored including software, configuration, security, and licensing. 5. Concluding Activities To backup the configuration, check hardware status, and reconnect cables, proceed as follows: 1. If necessary, create a new CV, that contains the reconfigurations made in Step 5 in section 4 , and set it to startable as described in Software Management. Note: The node creates a new CV in Step 5 Page 6 containing possibly new IP parameters. Consider deleting the downloaded CV at a later stage. The CV cannot be deleted at this time, since it is loaded. 2. Make a visual inspection of the status of hardware and verify the following: Red optical indicators are off Green optical indicators are on 3. Check the alarm list using the RBS Element Manager and verify that there are no alarms indicating DU problems. 4. Reconnect cables to LMT A and LMT B if cables were disconnected.

5. Request the Operation and Maintenance Center (OMC) to verify O&M access to the node.

This section provides background information to the procedure and lists typical error cases. These instructions describe how to restore a CV in a node from a PC. The backup of the CV must have been saved correctly, for example, as described in Saving a Configuration Version Backup. However, the CV might have been saved correctly using another procedure also using the save function in the node. The external CV is stored in the form of a zip archive on an FTP server and is retrieved and extracted onto the PC. The CV itself contains FTP scripts that will transfer the CV and the UP files to the node. The CV and UPs will be transferred to the DU in the node. The DU controls the loading of the node and the /c disk is on the DU. If the procedure is applied on a failing DU, format the disk first to eliminate any existing data. Note: If the disk is formatted, all data on it are lost. Configuration files that are not included in a CV must then be reinstalled on the node. These files are normally present on an external file server. Examples of configuration files not included in a CV are the LKF and the files for security files. The commands to the node are sent on the serial port, and the files are transferred from the PC on the Fast Ethernet port. The procedure also makes it possible to load a CV from another node of the same node type with a similar configuration. Use a CV from another node only if there is no external CV from the same node. If a CV from another node is used, the IP settings might have to be changed. Enabling autoconfiguration settings in the autoconfig.xml file makes it possible to use a backup CV from another hardware configuration than the one to restore. Autoconfiguration must normally be enabled, but if it is certain that the node configuration matches the external CV, autoconfiguration can be disabled. Before starting on the backup CV, all the necessary load module files must be stored on the disk in the DU. All necessary files, including load module files for UPs and the files that control the CV function, are transferred by FTP scripts from the PC to the DU. It does not matter if the disk is empty or already contains the files. This means that both the CV itself, and the UPs must be available on the PC, and the necessary UPs must be listed in the uplist.xml file in the CV. The scripts for transferring all files are executed when the DU is in backup mode. This eliminates all possible interference from the node itself. The FM Advanced task profile

might be required to set the DU into backup mode with the reload -- command. The command is always allowed when the DU is already in backup mode.

Error Cases
If the restoration fails, typical error cases are the following: The scripts fail to transfer files for the following reasons: Files are missing on the PC. The DU is not in backup mode. The IP configuration is not correct. The CV control files are write protected or the CV already exists.

Loss of communication after the node is started for the following reasons: - Vital software is not loaded due to a mismatch between the CV and the node. The IP configuration is incorrect.

If the node cannot be restarted using these instructions, contact the next level of maintenance support.