Recovering a Node on Site

Copyright
Ericsson AB 2009|2010. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to continued
progress in methodology, design and manufacturing. Ericsson shall have no liability for
any error or damage of any kind resulting from the use of this document.
Contents
1
Introduction
1.1
Prerequisites
2
2.1
2.2

Procedure
Actions to Perform Prior to the Site Visit
Actions to Perform On-Site

1 Introduction
These instructions describe how to reconnect an RBS to which the operator has lost
Operation and Maintenance (O&M) contact.
When the O&M contact is lost it means that communication cannot be established using
File Transfer Protocol (FTP), Secure FTP (SFTP), or the RBS Element Manager. The
RBS might still be active carrying payload traffic.
The likely causes of losing the O&M contact with the node are as follows:
1. The Operation and Maintenance Center (OMC) equipment has failed.
2. The O&M transport network has failed.
3. The RBS has failed due to:
Power supply failure on site
Site climate control equipment failure caused the RBS to turn itself off to
prevent overheating and permanent damage
Faulty RBS hardware, software, configuration, lack of memory or other
resources (traffic overload), violation of system limits, or incorrect manual
intervention
This document deals only with the case where the RBS has failed.
The Operations Support Systems | Radio and Core (OSS-RC) checks the connections
with RBSs regularly. A Heartbeat Failure alarm is raised for an RBS when there are no
responses from it.

1.1 Prerequisites
Before starting the procedure, the prerequisites listed below must be fulfilled:
The OSS-RC alarm Heartbeat Failure has not ceased

The communication with the RBS is lost and it is not possible to start the RBS
Element Manager from a remote location
There are transmission alarms from other transport network nodes pointing at the
RBS
No other relevant transport network problem has been identified
User names and passwords to the RBS and to the FTP server are available

1.1.1 Documents
Before leaving for the site, ensure the following are available
Site Installation Documentation (SID)
Before leaving for the site, ensure the contents of the following documents are known:
Personal Health and Safety Information
System Safety Information

1.1.2 Tools
Before leaving for the site, ensure the following tools are at hand:
A PC to function as:
A hyper terminal connected to the serial port on the Digital Unit (DU)
(software is installed on the PC for terminal emulation, for example
Windows HyperTerminal)
An FTP server for transfer of a Configuration Version (CV) and other files
to the DU over the Ethernet port
The processing environment for the RBS Element Manager, see document
Installing an Element Management Application for requirements
An Ethernet cable to connect the PC to the Fast Ethernet port (LMT B); typically
a category 5 patch cable with 8P8C modular connectors (RJ-45) and TIA/EIA-568
A wiring (included in cable package NTM 50346/100)
A cable for the serial connection, for example, an adapter RJ-45 to DSUB 9
(included in cable package NTM 50346/100) and a crossed Ethernet cable;
typically a category 5 patch cable with 8P8C modular connectors (RJ-45) and
TIA/EIA-568 A to B wiring
An Electrostatic Discharge (ESD) wrist strap (LTT 601 136/1)

1.1.3 Conditions
Before leaving for the site, ensure the following conditions are met:
The keys for access to site and cabinet are available
User names and passwords to the RBS and to the FTP server are available
Copies of the correct RBS backup CV and the applicable Upgrade Package (UP)
set are stored on the PC
All parameters required to perform the task are available, for example the O&M
IP address of the RBS when it is restarted on the backup CV
Applicable License Key File (LKF) is stored on a known directory on an FTP
server, for example on the Software Management Repository Services (SMRS)
server

A replacement DU preferably preloaded with the site unique configuration; if not

preloaded the DU can be restored on-site

2 Procedure
The instructions in this section are divided into:
Activities to perform at an OMC
Activities to perform on-site
For workflow prior to a site visit, see Figure 1. For workflow on-site, see Figure 2 and
Figure 3.

edw:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000262b.eps.pdf

ed
w:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000262b.eps.pdf
Figure 1 Workflow at OMC

edw:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000263b.eps.pdf

ed
w:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000263b.eps.pdf
Figure 2 Workflow On-Site

edw:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000264a.eps.pdf

ed
w:/alex?ac=image&fn=58_1543-LZA7016004Uen.B-l0000264a.eps.pdf
Figure 3 Workflow On-Site (Continued)

2.1 Actions to Perform Prior to the Site Visit

This section describes actions to perform from an OMC prior to the site visit.

2.1.1 Contacting and Restarting the RBS

To contact the RBS and restart the RBS, proceed as follows:
1. Open a command prompt and ping the RBS. Is the RBS responding?
1.
Yes: Proceed with the next step.
2.
No: Go to Section 2.2.
2. Open a command prompt and start a Telnet session. Is communication
established?
3.
Yes: Proceed with the next step.
4.
No: Go to Section 2.1.2.
3. Restart the RBS by entering the following command:
5.
restartObj me cold 3
6.
Note: The DU carries no traffic during restart.
1.
Go to Section 2.1.3.

2.1.2 Checking the OSS-RC Alarm List

Check the OSS-RC alarm list for RBS alarms indicating failures related to the following:
The RBS external power supply
(if applicable)
The RBS internal power supply
The climate control system
If any of these alarms are present, the failure is most likely in the component that issued
the alarm. The problem must be attended to on site. Follow the relevant alarm
instructions to eliminate the fault that caused the alarms.
When alarms are acted on, go to Section 2.1.3.
If no relevant alarms were found, prepare for a site visit and follow instructions in
Section 2.2.

2.1.3 Starting the RBS Element Manager

Start the RBS Element Manager. Is the RBS Element Manager starting successfully?
Yes: Go to Section 2.1.4.
No: Go to Section 2.2.

2.1.4 Check RBS Alarm Lists

To check the RBS alarm list, proceed as follows:
1. Open the RBS Element Manager alarm list and check for active alarms. Are there
any relevant active alarms in the alarm list?
1.
Yes: Act on alarms according to corresponding alarm instructions. When
all relevant active alarms are cleared, go to Section 2.1.6.
2.
No: proceed with the next step.
2. Check if the OSS-RC alarm Heartbeat Failure has ceased within the next five
minutes. Heartbeat Failure ceased?
3.
No: Go to Section 2.1.5.
4.
Yes: Go to Section 2.1.6.

2.1.5 Restoring DU Configurations

To restore a DU configuration using a backup CV stored on an FTP server, proceed as
follows:
1. Transfer the backup CV and UPs to the RBS and restore the configuration, see
Restoring a Configuration Version Backup.
1.
Note: The DU carries no traffic during restart.
1.
Check if the OSS-RC alarm Heartbeat Failure has ceased within the next five
minutes. Heartbeat Failure ceased?
2. Yes: Proceed with the next step.
3. No: Go to Section 2.2.
2.
Restore licenses for the RBS by downloading a prepared LKF from the FTP
server. Use the RBS Element Manager and the action updateLicenseKeyFile, see
Licensing.
3.
Configure the desired O&M security level in the RBS by downloading and
activating prepared security related files, see the OSS-RC document Security System
Administration, OSS-RC.
4.
Open the RBS Element Manager alarm list and check for active alarms.
4. If any alarms are found, follow the corresponding alarm instructions.

2.1.6 Final Check

No further action is necessary if the following conditions are met:
The OSS-RC alarm Heartbeat Failure has ceased
There are no transmission alarms from other transport network nodes pointing at
the RBS
If these conditions cannot be met, consult the next level of maintenance support.

2.2 Actions to Perform On-Site

This section describes actions to perform on-site when the problem could not be solved
from OMC.

2.2.1 Connecting the PC to the DU

To connect the PC to the Ethernet port of the DU, proceed as follows:
1. Connect the PC to the Fast Ethernet port (LMT B) of the DU, see Connecting a
Client Computer.
2. Start the RBS Element Manager, using the local O&M IP address 169.254.1.10. Is
the RBS Element Manager starting successfully?
1.
Yes: Go to Section 2.2.3.
2.
No: Go to Section 2.2.2.

2.2.2 Checking O&M IP Configuration

To check and change the O&M IP address using the serial port, proceed as follows:
1. Connect the PC to the serial port (LMT A) of the DU, see Connecting a Client
Computer
2. Check the O&M IP configuration in the node by command ifconfig. Is the O&M
IP address correct and according to SID?
1.
Yes: Go to Section 2.2.4.

2.
No: proceed with the next step.
3. Start the RBS Element Manager, using the IP address obtained in the previous
step.
4. Use the action assignIpAddress on MO IpHostLink to change the O&M IP
configuration. See also IP O&M.
5. Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
3.
Yes: Go to Section 2.2.4.
4.
No: Request an OMC operator to continue with Section 2.1.3.

2.2.3 Checking RBS Alarm Lists

To check the alarm list, proceed as follows:
1. Open the RBS Element Manager alarm list and check for transmission alarms and
alarms on the DU. Are there any relevant active alarms?
1.
Yes: Act on alarms according to corresponding alarm instructions. When
all relevant active alarms are cleared, proceed with the next step.
2.
No: Go to Section 2.2.4.
2. Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Heartbeat Failure active?
3.
Yes: Go to Section 2.2.4.
4.
No: Request an OMC operator to continue with Section 2.1.3.

2.2.4 Checking Cables and Connections

To check internal cables, external cables, and transmission equipment, proceed as
follows:
1. Check RBS internal cables from the DU to the interface towards site cabling for
faults. See Non-RF Connections and Digital Unit Description for information
about internal cables and connectors. Is the internal cabling OK?
1.
No: Reconnect or replace cables, then proceed with the next step.
2.
Yes: Go to Step 3.
2. Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
3.
No: Request an OMC operator to continue with Section 2.1.3.
4.
Yes: Proceed with the next step.
3. Check RBS external transmission cables and transmission equipment according to
SID. Are external cables and equipment OK?
5.
No: Reconnect or replace cables or transmission equipment, then proceed
with the next step.
6.
Yes: Go to Section 2.2.5.
4. Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
7.
No: Request an OMC operator to continue with Section 2.1.3.
8.
Yes: Go to Section 2.2.5.

2.2.5 Restarting DUs

To restart the DU, proceed as follows:
1. Restart the DU according to one of the following methods:

If it is possible to start the RBS Element Manager, restart the DU with

RestartRank set to RESTART_COLDWTEST, see Restart Board.
If the RBS Element Manager is not available, restart the DU by
disconnecting the power to the DU using the circuit breaker on the Power
Distribution Unit (PDU). For information about which circuit breaker
controls the DU, see Non-RF Connections. Wait one minute and switch on
the circuit breaker again. Wait for the software to load, this may take
several minutes.
1.
Note: The DU carries no traffic during restart.
1.
Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
2. Yes: Go to Section 2.2.6.
3. No: Request an OMC operator to continue with Section 2.1.3.

2.2.6 Restoring DUs

To restore the configuration on the DU with a backup CV, UPs and licenses, proceed as
follows:
1. Set up a serial connection PC-to-DU, transfer a backup CV and UPs from the PC
and restart the DU, see Restoring Digital Units.
1.
Note: The DU carries no traffic during restart.
1.
Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
2. Yes: Go to Section 2.2.7.
3. No: Request an OMC operator to continue with Section 2.1.3.

2.2.7 Replacing and Restoring DUs

To replace and restore the DU, proceed as follows:
1. Lock the DU, see Lock Board.
1.
Note: Removing, restarting, or blocking this unit stops all traffic on the
unit. In cases of single unit configurations, it causes a total stop in traffic on the
node.
1.
Replace the DU, see Replacing Digital Units.
2.
If the new DU is not already preconfigured with the site-unique configuration,
then transfer a backup CV and UPs from the PC to the new DU and restart the DU,
see Restoring Digital Units.
3.
Request an OMC operator to check if the OSS-RC alarm Heartbeat Failure is still
active after five minutes. Is Heartbeat Failure active?
2. Yes: Proceed with the next step.
3. No: Request an OMC operator to continue with Section 2.1.3.
4.
Lock the DU and put back the original DU, see Replacing Digital Units.
5.
Reconnect any cables disconnected during the procedure.
6.
Consult the next level of maintenance support.