Troubleshooting Guide Evo8200

Troubleshooting Guide Page 1 of 21
USER GUIDE 24/1553-AXD 105 03/1-V3 Uen V
Troubleshooting Guide
Evo Controller 8200/RNC
Contents
1 Overview
2 Common Corrective Procedures

2.1 Checking Input Power
2.2 Checking Power Distribution
2.3 Checking Signal Cabling in RNC with CAX
2.4 Checking Signal Cabling in RNC with APP
2.5 Checking Cable Connectors on Boards
2.6 Checking Optical Indicators
2.6.1 Fault Indicator (Red)
2.6.2 Operation Indicator (Green)
2.6.3 Maintenance Indicator (Blue)
2.6.4 Information Indicator (Yellow)
2.7 Checking Board Positions
2.8 Resolving RNC EM Logon Problems
2.9 Checking the RNC IP Address and Default Routing Address
2.10 Checking and Changing RNC ID
2.11 Viewing Alarms
2.11.1 Viewing Alarm Lists
2.11.2 Viewing Alarm Details
2.12 Viewing Software Versions
2.13 Viewing HW Versions
2.14 Viewing MO Properties
2.15 Restarting RNC
2.16 Restarting Boards
2.17 Locking and Unlocking Boards
2.18 Locking and Unlocking Managed Objects
2.19 Handling Configuration Versions
2.19.1 Creating CV Backup
2.19.2 Restoring CVs
2.20 Performing Software Upgrade
2.21 Reinstalling Software Upgrade Package
2.22 Collecting Trace Logs
2.23 Performing RNC Alarm Audit
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
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.
2 Common Corrective Procedures

This section describes procedures for correcting common malfunctions.
Note: Be aware that some of the procedures described here affect the traffic and service
level of the RNC.
2.1 Checking Input Power

To verify the power connection, do the following:
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.
2.2 Checking Power Distribution

Ensure that the power cables are connected as shown in Figure 1 or in Figure 2 if the APP is
present.
Figure 1 Power Cable Distribution in Evo Controller 8200/RNC with CAX
Figure 2 Power Cable Distribution in Evo Controller 8200/RNC
2.3 Checking Signal Cabling in RNC with CAX
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.
Table 1 Connections between MS, ES-1, ES -2 and US
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
CMXB3_04/83- MS E2 2 CMXB3_00/47-16 US E2 2 TSR 491

13 678/1500
CMXB3_04/05- TSR 491
MS E3 3 CMXB3_04/83-15 MS E3 3
15 678/700
CMXB3_04/05- TSR 491
MS E4 4 CMXB3_04/83-18 MS E4 4
18 678/700
CMXB3_24/05- TSR 491
ES-1 E1 1 CMXB3_00/45-7 US E3 3
10 678/1500
CMXB3_24/05- TSR 491
ES-1 E2 2 CMXB3_00/42-7 US E4 4
13 678/1500
CMXB3_24/83- TSR 491
ES-1 E1 1 CMXB3_00/45-16 US E3 3
10 678/2000
CMXB3_24/83- TSR 491
ES-1 E2 2 CMXB3_00/42-16 US E4 4
13 678/2000
CMXB3_24/05- TSR 491
ES-1 E3 3 CMXB3_24/83-15 ES-1 E3 3
15 678/700
CMXB3_24/05- TSR 491
ES-1 E4 4 CMXB3_24/83-18 ES-1 E4 4
18 678/700
CMXB3_44/05- TSR 491
ES-2 E1 1 CCIB_00/17-2 US E1 7
10 678/2000
CMXB3_44/05- TSR 491
ES-2 E2 2 CCIB_00/15-2 US E2 8
13 678/2000
CMXB3_44/83- TSR 491
ES-2 E1 1 CCIB_00/17-11 US E1 7
10 678/2000
CMXB3_44/83- TSR 491
ES-2 E2 2 CCIB_00/15-11 US E2 8
13 678/2000
CMXB3_44/05- TSR 491
ES-2 E3 3 CMXB3_44/83-15 ES-2 E3 3
15 678/700
CMXB3_44/05- TSR 491
ES-2 E4 4 CMXB3_44/83-18 ES-2 E4 4
18 678/700
Figure 3 Connections between CMXBs in MS, ES1, ES2 and CAX
2. Ensure that the connections between SCXBs in the MS, ES1, ES2 and the CAX are as
in Figure 4
Figure 4 Connections between SCXBs in MS, ES1, ES2 and CAX
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.
2.4 Checking Signal Cabling in RNC with APP
1. Ensure that the Ethernet inter-Switch Link (ESL) cables between CMXBs are connected
correctly, according to Figure 5.
2. Ensure that the Control Inter-Switch Link (CISL) cables between SCXBs are connected
correctly, according to Figure 6.
Figure 5 Connections Between CMXB3 in MS and ES-1 and ES-2.
Figure 6 Connections Between SCXB3 in MS and ES-1 and ES-2
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.
Figure 7 Connectors for EPB-To-APP Signal Cables
4. Ensure that the connections between CMXBs in MS and APPs are as in Figure 8.
Figure 8 Connections between CMXBs in MS and APPs
5. Ensure that the connections between SCXBs in MS and APPs are as in Figure 9.
Figure 9 Connections between SCXBs in MS and APPs
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.
2.5 Checking Cable Connectors on Boards

Check that each cable connector is properly attached.
2.6 Checking Optical Indicators

The circuit boards in the RNC are equipped with optical indicators.
The optical indicators are placed vertically in the following order:
◾ Fault indicator (red), see Section 2.6.1.

◾ Operation indicator (green), see Section 2.6.2.
◾ Maintenance indicator (blue), see Section 2.6.3.

◾ Information indicator (yellow), see Section 2.6.4.
2.6.1 Fault Indicator (Red)
The red optical indicator can be lit for two reasons:
◾ A hardware fault has been detected.

◾ There is not enough power available.
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.
Table 2 Red Optical Indicator States
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.
2.6.2 Operation Indicator (Green)
The green optical indicator shows the state of operation. See Table 3.
Table 3 Green Optical Indicator States
Behavior Interpretation Comment

Constant light Power available Ready for operation
Blinking slowly Dependent A resource that is required to start or maintain
(0.5 Hz) resource missing operation of the board, is missing
Blinking at a Loading or
medium rate (2 testing in
Hz) progress
Blinking at a fast Initial boot test
rate (16 Hz)
Off Power not
available
2.6.3 Maintenance Indicator (Blue)
The blue optical indicator can be set by the operator to prevent the board from being used
by the system. See Table 4.
Table 4 Blue Optical Indicator States

Constant light Full maintenance mode enabled. Manual intervention allowed.
Blinking slowly (0.5 Removing traffic Board is going into maintenance
Hz) mode.
Off Maintenance mode disabled. Manual intervention not allowed.
2.6.4 Information Indicator (Yellow)
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.
Table 5 Yellow Optical Indicator States

Constant light Board locked or
marked as faulty
Blinking slowly Shutdown of
(0.5 Hz) board in progress
Blinking at a fast Board busy Not used on all boards
rate (16 Hz)
Off Board unlocked
2.7 Checking Board Positions

When troubleshooting unwanted hardware behavior, always check that the boards are
located according to latest recommendations in Hardware Configuration Data.
Note: Recommendations for board placement are subject to change due to product
development.
2.8 Resolving RNC EM Logon Problems

Use the following documents for solving Element Manager (EM) logon problems:
◾ Installing an Element Management Application

◾ Product Handling
2.9 Checking the RNC IP Address and Default Routing Address

Use a terminal emulation program, such as PuTTY, for checking the RNC Internet Protocol
(IP) address. Detailed instructions on using this tool can be found in Product Handling.
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.
2.10 Checking and Changing RNC ID

Use the EM for checking and changing RNC Identity (ID). Detailed instructions on using this
tool can be found in Element Manager.
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
to. Changing the RNC IDs for the RNCs in a cluster requires a restart of all those
RNCs.
1. In the EM Containment view, select the ManagedElement and then RncFunction

object in the MO Tree.
2. In the MO properties tab in the right pane, change the value of the rncId attribute.
3. Click Apply.
Note: The change of RNC ID takes effect upon the next node restart.
2.11 Viewing Alarms

Use the Element Manager for viewing alarms and alarm details. Detailed instructions on
using this tool can be found in Element Manager.
2.11.1 Viewing Alarm Lists
1. In the EM menu bar, click Alarm and Alarm List. The Alarm List window opens,
showing alarms, their severity and their probable causes.
2.11.2 Viewing Alarm Details
1. Open the Alarm List as described above.

2. Right-click on the appropriate alarm, then click Details in the shortcut menu.
2.12 Viewing Software Versions

Use the EM for viewing software (SW) versions. Detailed instructions on using this tool can
be found in Element Manager.
1. Expand the EM Containment view.

2. In the MO Tree expand the SwManagement element.
3. Scroll down to find the UpgradePackage object.
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.
2.13 Viewing HW Versions

Use the EM for viewing hardware (HW) versions. Detailed instructions on using this tool can
be found in Element Manager.
1. Expand the EM Equipment view.

2. In the MO Tree expand the Equipment element.
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.
2.14 Viewing MO Properties

Use the EM for viewing MO properties. Detailed instructions on using this tool can be found
in Element Manager.
1. Select the Radio Network view and expand the Iub Links folder.
2. Select the appropriate IubLink to view the MO properties.
2.15 Restarting RNC

Use the EM restarting RNC. Detailed instructions can be found in Restart Node.
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.
1. In the EM Containment view, select the ManagedElement object.

2. Select the MO Properties tab in the right pane.
3. In the Actions tab, select the required restartRank from among Warm, Refresh,
Cold, or Cold w test, and select the required restartReason.
4. Click Execute.
2.16 Restarting Boards

Use the EM for restarting a board. Detailed instructions can be found in Restart Board.
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.
1. In the EM window, select the Containment view.

2. In the MO Tree expand the Equipment element.
3. Expand the required Subrack and then Slot.
4. Right-click on the required PlugInUnit and from the shortcut menu, select
manualRestart.
5. In the new window, select the required restartRank and restartReason .
6. Click Execute.
2.17 Locking and Unlocking Boards

For locking and unlocking boards, refer to:
◾ Lock Board.
◾ Unlock Board.
2.18 Locking and Unlocking Managed Objects

Use the EM for locking and unlocking a Managed Object (MO). Detailed instructions on using
this tool can be found in Element Manager.
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.
5. Click the required cell again.

6. In the MO Properties tab change the attribute administrativeState to UNLOCKED
and then press Apply.
7. Press Refresh.
The administrativeState is then changed to UNLOCKED and the operationalState

is changed to ENABLED.
2.19 Handling Configuration Versions

This section describes how to handle Configuration Version (CV).
2.19.1 Creating CV Backup
To save a backup of the CVs, use the procedures described in Saving a Configuration
Version Backup.
2.19.2 Restoring CVs
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.
2.20 Performing Software Upgrade

SW upgrade is performed in two steps:
◾ Downloading a SW Upgrade Package (UP) to the node.

◾ Putting the SW UP into operation, and confirming the upgrade.
Detailed instructions can be found in Install Upgrade Package, and in Upgrade Node with
Upgrade Package.
Downloading the SW UP to the node is done in the following way:
1. In the EM Upgrade and Backup view, select ManagedElement=1, SwManagement=1

from the MO Tree on the left.
2. Right-click the All Upgrade Packages and select Create new Upgrade Package. The
Add MO UpgradePackage window appears.
3. In the ID field, enter the id of the UP.
4. In the ftpServerIpAddress field, enter the IP address of the FTP server where the UP
is located.
5. In the upFilePathOnFtpServer field, enter the complete file path with the file name of
the control xml file that identifies the UP.
6. In the user and password fields, enter a valid user name and password to the FTP
server.
7. Click Add. The Upgrade Control File (UCF) path is checked, and the FTP server is
contacted. When the UCF xml file is found in the FTP server, it is downloaded to the
node. No other files are downloaded at this point. The MO added successfully
information is displayed at the bottom of the window.
8. Close the window and click the Refresh Tree button at the bottom of the MO Tree
pane. The new UP appears on the MO list.
9. Right-click on the new UP and select either Install or nonBlockingForcedInstall.
The UpgradePackage Properties window appears.
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.
10. Click the Execute button at the bottom of the window.
Putting the SW UP into operation is done in the following way:
1. In the EM Upgrade and Backup view, select ManagedElement=1, SwManagement=1,

All Upgrade Packages from the MO Tree to see the UpgradePackages.
2. Click the relevant UpgradePackage and select the MO Properties tab. The Attributes
window is displayed.
3. Click the Actions tab. The Actions window is displayed.

4. 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.
Note: The rebootNodeUpgrade and rebootNodeUpgradeWithStop actions cause a hard

upgrade that normally results in the restart of the node.
The upgrade and upgradeWithStop actions cause a soft upgrade that normally
does not require a node restart.
If the rebootNodeUpgradeWithStop or upgradeWithStop action is selected, the upgrade

process is stopped before the node restart and the UpgradePackage MO enters state
WAITING_FOR_RESUME. To resume the upgrade, execute the resumeSwUpgrade action on
the UpgradePackage MO. For more information, refer to Upgrade and Backup.
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.
Confirm the SW UP in the following way:
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).
3. A confirmation window appears. Click Yes to confirm the upgrade.
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
RNC are restarted simultaneously to complete the activation phase. For more details on the
Controlled Upgrade Restart, refer to Software Management.
2.21 Reinstalling Software Upgrade Package

Use the EM for this task. Detailed instructions can be found in Element Manager.
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.
3. Click the Execute button at the bottom of the window.
Putting the reinstalled SW UP into operation is done the following way:
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.
Note: The rebootNodeUpgrade and rebootNodeUpgradeWithStop actions cause a hard

upgrade that normally results in the restart of the node.
The upgrade and upgradeWithStop actions cause a soft upgrade that normally
does not require a node restart.
If the rebootNodeUpgradeWithStop or upgradeWithStop action is selected, the upgrade

process is stopped before the node restart and the UpgradePackage MO enters state
WAITING_FOR_RESUME. To resume the upgrade, execute the resumeSwUpgrade action on the
UpgradePackage MO. For more information, refer to Upgrade and Backup.
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.
2.22 Collecting Trace Logs

For information regarding collecting trace logs, refer to Data Collection Guideline.
2.23 Performing RNC Alarm Audit

If the RNC node displays an active alarm but the resource specified in the alarm is enabled
and in operation, use the RNC Alarm Audit. The Alarm Audit validates existing alarms and
clears all invalid alarms if any such alarms are detected.
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.
Troubleshooting Guide Evo Controller 8200/RNC

Troubleshooting Guide Evo8200

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Troubleshooting Guide Evo8200

Încărcat de

Drepturi de autor:

Formate disponibile

Troubleshooting Guide Page 1 of 21

USER GUIDE 24/1553-AXD 105 03/1-V3 Uen V

2 Common Corrective Procedures

2 Common Corrective Procedures

2.1 Checking Input Power

2.2 Checking Power Distribution

Figure 1 Power Cable Distribution in Evo Controller 8200/RNC with CAX

Figure 2 Power Cable Distribution in Evo Controller 8200/RNC

2.3 Checking Signal Cabling in RNC with CAX

Table 1 Connections between MS, ES-1, ES -2 and US

CMXB3_04/83- MS E2 2 CMXB3_00/47-16 US E2 2 TSR 491

Figure 3 Connections between CMXBs in MS, ES1, ES2 and CAX

Figure 4 Connections between SCXBs in MS, ES1, ES2 and CAX

2.4 Checking Signal Cabling in RNC with APP

Figure 5 Connections Between CMXB3 in MS and ES-1 and ES-2.

Figure 6 Connections Between SCXB3 in MS and ES-1 and ES-2

Figure 7 Connectors for EPB-To-APP Signal Cables

Figure 8 Connections between CMXBs in MS and APPs

Figure 9 Connections between SCXBs in MS and APPs

2.5 Checking Cable Connectors on Boards

2.6 Checking Optical Indicators

The optical indicators are placed vertically in the following order:

◾ Fault indicator (red), see Section 2.6.1.

◾ Maintenance indicator (blue), see Section 2.6.3.

2.6.1 Fault Indicator (Red)

The red optical indicator can be lit for two reasons:

◾ A hardware fault has been detected.

Table 2 Red Optical Indicator States

2.6.2 Operation Indicator (Green)

Table 3 Green Optical Indicator States

Behavior Interpretation Comment

2.6.3 Maintenance Indicator (Blue)

Table 4 Blue Optical Indicator States

Behavior Interpretation Comment

2.6.4 Information Indicator (Yellow)

Table 5 Yellow Optical Indicator States

Behavior Interpretation Comment

2.7 Checking Board Positions

2.8 Resolving RNC EM Logon Problems

◾ Installing an Element Management Application

2.9 Checking the RNC IP Address and Default Routing Address

2.10 Checking and Changing RNC ID

1. In the EM Containment view, select the ManagedElement and then RncFunction

2.11 Viewing Alarms

2.11.1 Viewing Alarm Lists

2.11.2 Viewing Alarm Details

1. Open the Alarm List as described above.

2.12 Viewing Software Versions

1. Expand the EM Containment view.

2.13 Viewing HW Versions

1. Expand the EM Equipment view.

2.14 Viewing MO Properties

2.15 Restarting RNC

1. In the EM Containment view, select the ManagedElement object.

2.16 Restarting Boards

1. In the EM window, select the Containment view.

2.17 Locking and Unlocking Boards

2.18 Locking and Unlocking Managed Objects

5. Click the required cell again.

The administrativeState is then changed to UNLOCKED and the operationalState

2.19 Handling Configuration Versions

2.19.1 Creating CV Backup

2.19.2 Restoring CVs

2.20 Performing Software Upgrade