Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Troubleshooting Guide
Evo Controller 8200/RNC
Contents
1 Overview
1 Overview
This document provides troubleshooting information for isolating and correcting common
malfunctions encountered during the operation and maintenance of the Radio Network
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 2 of 21
Controller (RNC) and the RNC cluster activated by feature RNC in Pool (FAJ 121 2096). For
more information on the RNC in Pool feature refer to RNC in Pool.
Some parts of the procedure are performed remotely by an Operation and Maintenance
Center (OMC) operator, other parts by site personnel.
Note: Be aware that some of the procedures described here affect the traffic and service
level of the RNC.
1. Make sure that the circuit breakers located in the distribution units are turned on.
2. For the PFM, check the status of the two optical indicators located in the middle of the
front panel.
3. If the left power indicator is lit with a steady green light and the right MIA indicator is
dark, power is fed to the PFM and subrack.
4. If the left power indicator is lit with a flashing green light, check that the power
branches are on for the PFM. Check that the additional optical indicators at each end
of the front panel have the following status:
◾ For the PFM-LOD, the two left indicators are lit with a steady green light.
◾ For the PFM-HOD, any three of the four indicators are lit with a steady green
light.
5. To check that the power is on for the Cabinet Aggregation Switch (CAX), check the
status of the Operation optical indicator next to the power connector, marked -48 V on
the CAX Control and Interface Boards (CCIBs).
6. If the indicator is lit with a steady green light, power is fed to the CAX.
7. To check that the power is on for the APP, check the status of the power optical
indicator to the right of the power connector, marked -48 V.
8. If the indicator is lit with a steady green light, power is fed to the APP.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 3 of 21
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 4 of 21
1. Ensure that the connections between CMXBs in the MS, ES1, ES2 and the CAX are as
in Table 1. The connections are shown in Figure 3.
Front Front
From Subrack Port To Subrack Port Cable
Connector Connector
CMXB3_04/05- TSR 491
MS E1 1 CMXB3_00/50-7 US E1 1
10 678/1000
CMXB3_04/05- TSR 491
MS E2 2 CMXB3_00/47-7 US E2 2
13 678/1000
CMXB3_04/83- TSR 491
MS E1 1 CMXB3_00/50-16 US E1 1
10 678/1500
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 5 of 21
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 6 of 21
2. Ensure that the connections between SCXBs in the MS, ES1, ES2 and the CAX are as
in Figure 4
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 7 of 21
3. Check the Power Fan Module (PFM) optical power status indicators.
◾ The Green optical indicator at the center of the front panel is a power status
indicator. Steady ON indicates the PFM is able to supply sufficient power to the
subrack backplane. Flashing indicates the power supply is not sufficient.
◾ Blue optical indicator is a Manual Intervention Allowed (MIA). At power up or
reset, it is in the OFF state.
◾ There are two Green optical indicators at the sides of the front panel. They
represent input voltage levels at each of the four power inputs A-D.
For more information on the PFM indicators refer to Optical Indicators. For a detailed
description of the PFM refer to PFM Description.
1. Ensure that the Ethernet inter-Switch Link (ESL) cables between CMXBs are connected
correctly, according to Figure 5.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 8 of 21
2. Ensure that the Control Inter-Switch Link (CISL) cables between SCXBs are connected
correctly, according to Figure 6.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 9 of 21
3. Ensure that the EPBs in slots 3 and 26 are connected to the port in position 68 on the
lower and upper APP unit, as presented in Figure 7.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 10 of 21
4. Ensure that the connections between CMXBs in MS and APPs are as in Figure 8.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 11 of 21
5. Ensure that the connections between SCXBs in MS and APPs are as in Figure 9.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 12 of 21
6. Check the Power Fan Module (PFM) optical power status indicators.
◾ Green optical indicator is a power status indicator. When voltage exceeds 25V at
any of the PFM power inlets, including the rear connector, it starts flashing.
◾ Blue optical indicator is a Manual Intervention Allowed (MIA). At power up or
reset, it is in the OFF state.
◾ Green optical indicators, two at each end of the front panel, represents input
voltage levels at each of the four power inputs A-D.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 13 of 21
If the reason is that there is a hardware fault, the faulty board must be replaced. A board is
normally replaced, only if the yellow indicator also shows a constant light. See Table 2.
Behavior Interpretation
Constant light Fault
Off No fault
The red indicator can be flashing when the board is being started, but that does not indicate
any fault.
The green optical indicator shows the state of operation. See Table 3.
The blue optical indicator can be set by the operator to prevent the board from being used
by the system. See Table 4.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 14 of 21
The yellow optical indicator shows information about the board. A board is normally
replaced, only if the yellow indicator shows a constant light or if no indicators are lit at all.
See Table 5.
Note: Recommendations for board placement are subject to change due to product
development.
1. Connect the computer to the RNC serial port and log on to the shell.
2. Run the following command without any arguments: ifconfig
3. The command returns the current IP address, subnet mask, and broadcast.
Note: The RNC ID must be unique. If the RNC has the RNC in Pool feature (FAJ 121 2096)
activated, the RNC ID must be the same as for all the RNCs in the cluster it belongs
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 15 of 21
to. Changing the RNC IDs for the RNCs in a cluster requires a restart of all those
RNCs.
Note: The change of RNC ID takes effect upon the next node restart.
1. In the EM menu bar, click Alarm and Alarm List. The Alarm List window opens,
showing alarms, their severity and their probable causes.
If the RNC has the RNC in Pool feature (FAJ 121 2096) activated, the SW version must be
the same as for all the members of the cluster it belongs to.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 16 of 21
3. Select the required HW name to view the properties in the right pane.
4. In the MO Properties tab check the value of administrativeProductData and
operationalProductData for Subrack and productData for Slot.
1. Select the Radio Network view and expand the Iub Links folder.
2. Select the appropriate IubLink to view the MO properties.
Note: No traffic or service is available until the restart is complete. To restart the entire
cluster of RNCs when the RNC in Pool feature (FAJ 121 2096) is activated, the
operator has to restart each cluster member individually. It is possible to only
restart one of the RNCs in the cluster without restarting the whole cluster.
Note: Restarting a board causes any other system resource dependent on this board to
become disabled and might temporarily cause a partial or complete loss of service
from this RNC or connected RBSs. It might also cause a number of alarms to be
generated.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 17 of 21
◾ Lock Board.
◾ Unlock Board.
1. In the EM, select the RadioNetwork view and expand the Utran Cells element.
2. Select the required UtranCell.
3. In the MO Properties tab change the attribute administrativeState to LOCKED and
then press Apply.
4. Press Refresh.
In the Table tab, the value of the administrativeState is LOCKED and the value of
the operationalState is changed to DISABLED.
To save a backup of the CVs, use the procedures described in Saving a Configuration
Version Backup.
To restore a remotely stored CV in a node, from an external FTP server, use the procedures
described in Restoring a Configuration Version Backup.
To restore a CV in a node, from a PC that has serial and Ethernet connections to the node,
use the procedures described in Emergency Restoring a Configuration Version Backup.
Note: If the RNC has the RNC in Pool feature (FAJ 121 2096) activated, the SW version
must be the same as for all the members of the cluster it belongs to.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 18 of 21
Detailed instructions can be found in Install Upgrade Package, and in Upgrade Node with
Upgrade Package.
Note: Install only installs the Load Modules (LMs) required for this upgrade.
Only those LMs that have not already been installed through another UP are
transferred to the node file system. The nonBlockingForcedInstall is more
time consuming since all load modules must be transferred to the node and be
installed.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 19 of 21
The upgrade and upgradeWithStop actions cause a soft upgrade that normally
does not require a node restart.
Note: If an error message is displayed, stating that the upgrade cannot be executed,
act on the errors and start again from step 1 in this section.
5. If the Java Virtual Machine (JVM) on the node restarts, the EM on the Client restarts
automatically. If the upgrade has also upgraded the EM version, the user is prompted
to restart the EM client.
6. Select Table tab on the right side of EM window and use Refresh values to continue
supervising the upgrade progress.
1. In the EM Software view, select the UP tab in the right pane to see
UpgradePackages.
2. Right-click on the specific UpgradePackage and choose UP Properties. Then press the
Confirm Upgrade button.
Note: The Confirm Upgrade button, used for making the UP permanent, is
enabled only when the upgrade process is completed (and the name of the
properties window has changed from Upgrade to Confirm). It is necessary
to confirm a completed upgrade within 60 minutes (default value) or the node
discards the upgrade and restarts from the rollback configuration version
(CV). The user can change the value of the time-out, by setting the
parameter confirmWatchdogTimeOut in the Upgrade Control File (UCF).
For RNCs that are members of a cluster, the upgrade must be synchronized using the
Controlled Upgrade Restart function. Controlled Upgrade Restart allows a synchronized
restart by splitting the upgrade into two phases, a preparation phase that stops just before
the node restart, and an activation phase that resumes the upgrade by doing the upgrade
node restart. The preparation phase can be started before the maintenance window for the
RNC's in the cluster. Once the preparation phase is complete on the cluster members, all the
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 20 of 21
RNC are restarted simultaneously to complete the activation phase. For more details on the
Controlled Upgrade Restart, refer to Software Management.
1. In the EM Upgrade and Backup view, right-click the All Upgrade Packages in the
left pane and select Create new Upgrade Package. The Add MO UpgradePackage
window appears.
2. Right-click on the UP to be reinstalled and select either install or
nonBlockingForcedInstall. The UpgradePackage Properties window appears.
Note: Install only installs the LMs required for this upgrade.
Only those LMs that have not already been installed through another UP are
transferred to the node file system. The nonBlockingForcedInstall is more
time consuming since all load modules must be transferred to the node and be
installed.
1. Once the installation is complete, click the reinstalled UpgradePackage and select the
MO Properties tab. The Attributes window is displayed.
2. Click the Actions tab. The Actions window is displayed.
3. From the drop down menu select rebootNodeUpgrade or Upgrade. If the upgrade is
done for an cluster member RNC, select rebootNodeUpgradeWithStop or
upgradeWithStop. Click the Execute button at the bottom of the window.
The upgrade and upgradeWithStop actions cause a soft upgrade that normally
does not require a node restart.
Note: If an error message is displayed, stating that the upgrade cannot be executed, act
on the errors and start again from step 1 in this section.
If the RNC has the RNC in Pool feature (FAJ 121 2096) activated, the SW version must be
the same as for all the members of the cluster it belongs to.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018
Troubleshooting Guide Page 21 of 21
Note: The Alarm Audit function only applies for alarms related to RNC radio network
functionality.
To perform an RNC Alarm Audit, use AMOS or establish a shell connection to the node. Use
the following command:
alarmaudit
© Ericsson AB 2011-2014. All rights reserved. No part of this document may be reproduced in any
Copyright
form without the written permission of the copyright owner.
The contents of this document are subject to revision without notice due to continued progress in
Disclaimer methodology, design and manufacturing. Ericsson shall have no liability for any error or damage
of any kind resulting from the use of this document.
All trademarks mentioned herein are the property of their respective owners. These are shown in
Trademark List
the document Trademark Information.
http://localhost:9032/alexserv?AC=LINK&ID=9502&FN=24_1553-AXD10503_1-V3Ue... 23/01/2018