Eutran Frequent Alarms

8/15/2019 Eutran Frequent Alarms

1/51

HW&Frequent Alarm


2/51

• - HW alarm & procedure• - frequently alarm & procedure•

- follow alarm from BE & procedure


3/51

HW alarms & Procedure

• 1.Hardware overview• DU Board: DUL20

Port Connector Description

RI A-F SFP Interface DU-RU (electrical) or DU-RRU (optical)

TN A RJ-45 Gigabit Ethernet (electrical)

TN B SFP Gigabit Ethernet (optical)

IDL HSIO Inter-DU link (DU to DU)

LMT A RJ-45 Serial port for OSE shell over RS-232

LMT B RJ-45 Fast Ethernet for O&M

AUX RJ-45 Auxiliary (Common EC bus)

EC

RJ-45

EC bus (Dedicated EC bus)

GPS RJ-45 Used when the network synchronization source is a GPS receiver


4/51

Hardware Overview

• DUS41

Port Connector Description Interface/protocol A-F SFP Radio Interface, 10Gbps/s

Interface DU-RU (electrical) or DU-RRU (optical). Interface: Uu’, Protocol: CPRI (proprietary) C,D,E,F has also support for IDL2

TN A RJ-45 Transport Network,Gigabit Ethernet (electrical 1000BASE-T)

Interface: S1,X2 and Mul“Link1”

TN B SFP Transport Network,Gigabit Ethernet (optical SFP, 1000BASE-X)

Interface: S1,X2 and Mul“Link2”

TN C SFP Transport Network,Gigabit Ethernet (optical SFP, 1000BASE-X)

Interface: S1,X2 and MulNOT USED AT YET

IDL HSIO Inter-DU link (DU to DU) IDL1 COMP SFP Coordinated Multi Point communication (CoMP) NOT USED AT YET LMT RJ-45 Local Maintenance Terminal, ,

Fast Ethernet for local O&M Protocol: IPDefault enodeB IP: 169.254.1.10/24

EC RJ-45 EC bus (Dedicated EC bus) Communication with SCU(Fan Control) GPS RJ-45 Used when the network synchronization source is

a GPS receiver Protocol: NMEA 0183


5/51

Hardware Overview

• RU

Data 1&2: Gamma data and CPRI

RF A: Feeder connection TX/RX

RF B: Feeder connection RX

RX A I/O, RXB I/O: from cross-connecting RUsRXA out: for RX antenna sharing

(co-siting)


6/51

Hardware Overview

• Antenna System

AntennaSubUnit


7/51

Hardware Overview

• DU-RU Connection

DU

RI A

RI B

RI C

RI D

RI E

RI F

RU 1

RU 2

RU 3

RU 4

RU 5

RU 6

S1

S2

S3

DU

RI A

RI B

RI C

RI D

RI E

RI F

RRU 1

RRU 2

RRU 3

S1

S2

S3

RiPort

RfPort AuPort

Checking command1.hget riport remote: Check the interface connection between DU and RU/RRU.

2. hget rfbranch portref: Check the interface connection between RU/RRU andAntenna system.


8/51

Hardware OverviewOFFLINE_BKK0016-L21_DCG_K> hget riport remote

140226-20:15:35 OFFLINE_BKK0016-L21_dcg_k 10.0b ERBS_NODE_MODEL_D_1_188_COMPLETE stopfile=/tmp/1604..=================================================================================================================MO remoteRiPortRef=================================================================================================================AuxPlugInUnit=RRU-1,RiPort=DATA_1AuxPlugInUnit=RRU-1,RiPort=DATA_2 Subrack=1,Slot=1,PlugInUnit=1,RiPort=AAuxPlugInUnit=RRU-2,RiPort=DATA_1AuxPlugInUnit=RRU-2,RiPort=DATA_2 Subrack=1,Slot=1,PlugInUnit=1,RiPort=BAuxPlugInUnit=RRU-3,RiPort=DATA_1AuxPlugInUnit=RRU-3,RiPort=DATA_2 Subrack=1,Slot=1,PlugInUnit=1,RiPort=CSubrack=1,Slot=1,PlugInUnit=1,RiPort=A AuxPlugInUnit=RRU-1,RiPort=DATA_2Subrack=1,Slot=1,PlugInUnit=1,RiPort=B AuxPlugInUnit=RRU-2,RiPort=DATA_2Subrack=1,Slot=1,PlugInUnit=1,RiPort=C AuxPlugInUnit=RRU-3,RiPort=DATA_2

Subrack=1,Slot=1,PlugInUnit=1,RiPort=DSubrack=1,Slot=1,PlugInUnit=1,RiPort=ESubrack=1,Slot=1,PlugInUnit=1,RiPort=F=================================================================================================================Total: 12 MOs

OFFLINE_BKK0016-L21_DCG_K> hget rfbranch portref

140226-20:16:57 OFFLINE_BKK0016-L21_dcg_k 10.0b ERBS_NODE_MODEL_D_1_188_COMPLETE stopfile=/tmp/1604..=================================================================================================================MO auPortRef rfPortRef=================================================================================================================AntennaUnitGroup=1,RfBranch=1 [1] = AntennaUnitGroup=1,AntennaUnit=1,AntennaSubunit=1,AuPort=1 AuxPlugInUnit=RRU-1,DeviceGroup=ru,RfPort=AAntennaUnitGroup=1,RfBranch=2 [1] = AntennaUnitGroup=1,AntennaUnit=1,AntennaSubunit=1,AuPort=2 AuxPlugInUnit=RRU-1,DeviceGroup=ru,RfPort=BAntennaUnitGroup=2,RfBranch=1 [1] = AntennaUnitGroup=2,AntennaUnit=1,AntennaSubunit=1,AuPort=1 AuxPlugInUnit=RRU-2,DeviceGroup=ru,RfPort=AAntennaUnitGroup=2,RfBranch=2 [1] = AntennaUnitGroup=2,AntennaUnit=1,AntennaSubunit=1,AuPort=2 AuxPlugInUnit=RRU-2,DeviceGroup=ru,RfPort=BAntennaUnitGroup=3,RfBranch=1 [1] = AntennaUnitGroup=3,AntennaUnit=1,AntennaSubunit=1,AuPort=1 AuxPlugInUnit=RRU-3,DeviceGroup=ru,RfPort=AAntennaUnitGroup=3,RfBranch=2 [1] = AntennaUnitGroup=3,AntennaUnit=1,AntennaSubunit=1,AuPort=2 AuxPlugInUnit=RRU-3,DeviceGroup=ru,RfPort=B=================================================================================================================Total: 6 MOs

Added 6 MOs to group: hget_group


9/51

HW Alarm• Basic command:• 1.Get:Check the MO details: get xxx(MO name) xxxx(Attribute name)Show the attribute value of all related MO: get . xxxx(Attribute name)

• 2.Set:Change the attribute value of one MO: set xxx(MO name) xxxx(Attribute name)Change all attribute of related MO: set . xxxx(Attribute name)• 3. acl/acc:List the action of one MO: acl xxx(MO name)Start the action: acc xxx(MO name) xxxxx(action describtion from command acl)• 4.pr & st:List all related MO: pr XXX(MO name) For example: pr cellrelation (Check all cell relations)Check the status of MO: st xxx(MO name)• 5.bl/debBlock or Deblock the MO.• Most command we used when check eNB have the same structure , just

need to change the MO or attribute name.• Attachment is some eNB basic command.


10/51

Auto-configuration of Board Not Possible

specificProblem eventType probableCause perceivedSeverity

ManagedObject

serviceImpact

(CellDown,CellAvailability= 0%)(Y = Yes, N =No)

serviceDegrade(Y = Yes, N = No)

Auto-Configuration ofBoard Not Possible

EQUIPMENT_ALARM UNAVAILABLE WARNING Slot N Y

Procedure of solving alarm:1.Verify the board has been inserted into the correct slot in thesubrack and the correct fan has been inserted in the subrack.2.If the alarm cause cause is Auto-configuration disabled, theconfiguration doesn't match the inserted board , set the value to true.

3.If the alarm cause is Auto-install for PiuType failed,Install the loadmodules for the PIU Type.4.If the board or fan is not part of the current configuration, the nodemust be upgraded with an Upgrade Package that supports therespective board or fan. The additionalInfo in the alarm gives moreinformation on the problem with the current configuration.Alternatively, use another board or fan with a supported revision


11/51

BatteryMissing


ManagedObject

serviceImpact(CellDown,CellAvailability = 0%)(Y = Yes, N = No)


BatteryMissing PROCESSING_ERROR_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR

MAJOR BatteryBackup

N N

• Procedure of solving alarm:1.Check if non-exist BFU MO have been created.2.Restart the BFU.3.Check the battery cables.4.Replace the BFU.5.Replace the battery.


12/51

CurrentTooHigh


ManagedObject



CurrentTooHighEQUIPMENT_ALARM

EQUIPMENT_MALFUNCTION MINOR RfPort

N N

• Reason of the alarm:

1. Start-Up of antenna system devices. RETs or RET part of AIR, and TMAs need highcurrent levels when they are turned on.2. Short circuit.3. Other dramatic reduction on the branch equivalent DC resistance because ofmalfunction on the antenna system equipment.4. Too many units connected.• Procedure of solving the alarm:1.Check if the Rfport connected to RET or TMA is configured correctly.2. Check for a short circuit in the power supply and antenna system.3.Check cable connection.Change cables if necessary.4.If alarm remains,disconnect a RET or TMA.If alarms still remains,replace the RET,TMA or AIR.


13/51

Disconnected

specificProblem eventType probableCause perceivedSeverity Managed Object

serviceImpact

(CellDown,CellAvailability = 0%)(Y = Yes, N = No)

serviceDegrade

(Y = Yes, N= No)

Disconnected EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MAJOR Cabinet N N

Disconnected EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MAJOR EquipmentSupportFunction

N N

Disconnected EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR ExternalNode N N

Disconnected EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MAJOR FanGroup N N

Disconnected EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MAJOR HwUnit N N


14/51

Disconnected• Actions for Cabinet1.Connect the smoke detector to the SCU.2.Restart the SCU to which the smoke detector is connected.

• Actions for EquipmentSupportFunction1. Check that the secondary node Digital Unit (DU) and primary node DU areconnected to the EC bus on correct hubPosition.2.If the alarm remains, check that secondary node and primary node are configuredproperly through the attributes SupportSystemControl and hubPosition3.If the alarm remains,restart the secondary node DU.4.If the alarm remains, restart the primary node DU.5.Change the cable that connects the secondary or primary node in this node to theEC bus.6.Change the EC bus hub or the SHU


15/51

Disconnected• Actions for ExternalNode1.Check that the number of the ExternalNode MO in the primary node is consistentwith the number of secondary nodes installed in the RBS.2.If the alarm remains, check that the other nodes in the RBS are configured assecondary nodes. The secondary nodes must have attribute SupportSystemControl setto FALSE.3.If the alarm remains, check that the attribute hubPosition on the EcPort MO (of theExternalNode MO) in this node has the same value as attribute hubPosition on theHwUnit MO (of the PlugInUnit MO) in the corresponding secondary node.4.Check the cable to EC bus and restart DU or replace cable when needed.

•

Actions for FanGroup1.Restart the System Control Unit/Support Part (SCU/SUP).2.check that attribute climateSystem is correctly configured for this RBS and that thecorresponding correct number of fan groups is installed in the RBS.


16/51

Disconnected• Actions for FanGroup1.Check that the node is configured properly and that the hardware unit is present inthis RBS node. The correct number of HwUnit MOs with correct HwUnitType must beconfigured on the node.2.Restart the hardware unit and check the cable,hardware is properly connected and

change the faulty unit when necessary.


17/51


ManagedObject

serviceImpact(CellDown,CellAvailability =0%)(Y = Yes, N = No)


EnclosureDoorOpenENVIRONMENTAL _ALARM

ENCLOSURE_DOOR_OPEN_M3100 MAJOR Cabinet N N

• Procedure for solving alarm:1. Check whether there is any authorized personnel at the site. Follow the securityroutines.Close the door.


ManagedObject



FanFailureEQUIPMENT_ALARM

EQUIPMENT_MALFUNCTION MAJOR FanGroup N Y

• Procedure for solving alarm:1.Restart the Support Control Unit to see if it has ceased.2.Lock the SCU,change the fan and unlock the SCU.


18/51


ManagedObject



Gigabit Ethernet LinkRedundancy Fault

EQUIPMENT_ALARM

REPLACEABLE_UNIT_PROBLEM WARNING

GigaBitEthernet N N


ManagedObject



GeneralHwErrorEQUIPMENT_ALARM

EQUIPMENT_MALFUNCTION MAJOR HwUnit N Y

• Procedure for solving alarm:1.Restart the faulty board or unit.2.Change the board or unit.

• Procedure for solving alarm:1.If the network equipment is incorrectly configured, correct the configuration,possibly in cooperation with the other maintenance center.2.Examine the cables between the node and the network equipment to ensure thatthey are correctly connected and that they are not faulty.3.Connect to a different port on the network equipment for the faulty link, possibly in

cooperation with the maintenance center for the network equipment.


19/51

HW Fault


serviceImpact


serviceDegrade

(Y = Yes, N= No)

HwFault EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR AntennaNearUnit N N

HwFault EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR DeviceGroup Y Y

HwFault EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR RiPort Y Y

• Alarms occurs when there is a hardware failure in the RET or theTMA(AntennanearUnit), DU/RU/RRU(DeviceGroup) , or the SFP module is faulty,disconnected or does not support the required bitrate.

• Actions for AntennaNearUnit1.Identify the faulty RET or TMA and inspect it visually (check the power supply,cables, and so on). Replace the cables if necessary.2.If the alarm remains, restart the faulty RET or TMA.3.If the alarm remains, replace the RET or TMA.


20/51

HW Fault• Actions for DeviceGroup1.Identify the faulty unit and inspect it visually (check the power supply, cables, and soon).2.If the alarm remains, restart the faulty unit. If the faulty unit is a Digital Unit, restartit with restart rank RESTART_COLDWTEST.

3.Replace the faulty unit.

• Actions for RiPort1.Identify the faulty SFP module connected to the RU or RRU.2.Replace the faulty SFP module.


21/51

LinkFailure


ManagedObject

serviceImpact(CellDown,CellAvailability= 0%)(Y = Yes, N =No)


LinkFailureEQUIPMENT_ALARM LINK_FAILURE MINOR RiPort N Y

• Communication link problem, radio interface connection.Possible source for thealarm is a faulty DU, cable, or RU/RRU.

•

The alarm also occurs if the SFP (Small Form-factor Pluggable) module is faulty,disconnected or does not support the required bit rate. The additional texts Faultyor Incompatible SFP Module or Missing SFP Module will then be displayed.

Action for SFP module :1. For Faulty or Incompatible SFP Module : Change the faulty SFP module to the unit

generating the alarm.

2. For Missing SFP Module : Reconnect the missing or disconnected SFP module tothe unit generating the alarm

Action for DU,cable or RU/RRU:1.Restart the DU and RU/RRU to see if alarm has ceased.2.If not, check the cable connection between DU and RU/RRU, replace the cable ifnecessary.


22/51

Loss of Tracking

• Reason of the alarm1. The system or radio clock cannot track a synchronization reference because the

reference has a very large frequency deviation. This fault location isSynchronization reference.

2. The system or radio clock cannot track any synchronization reference as a resultof a faulty Timing Unit or the aging of its oscillator. This fault location is TimingUnit.


ManagedObject

serviceImpact(CellDown,CellAvailability= 0%)(Y = Yes, N =No)


Loss of TrackingEQUIPMENT_ALARM

REPLACEABLE_UNIT_PROBLEM MAJOR

Synchronization Y Y


23/51

Loss of Tracking• Procedure for solving alarm1. Examine the value of the attribute, syncRefStatus in the MO, Synchronization,for all defined references.

2. Remove all synchronization references whose state is LOSS_OF_TRACKING,

configure one (or more, if needed) new synchronization references .3. Examine the value of the attribute, tuSystemClock in MO, TimingUnit, for alltiming units in the node. Lock the board that is in state, LOSS_OF_TRACKING,using hard lock.4. Restart board.

5. Unlock the board, using the instruction, Unlock Board. Reset theLOSS_OF_TRACKING state, using the action, resetLossOfTracking in the MO,Synchronization, for all synchronization references.

6. If alarm exsit, replace the board containing the TU.


24/51

LossofMains



serviceDegrade(Y = Yes, N= No)

LossOfMainsENVIRONMENTAL_ALARM

COMMERCIAL_POWER_FAILURE MAJOR HwUnit N N

LossOfMainsENVIRONMENTAL_ALARM

COMMERCIAL_POWER_FAILURE MAJOR PowerSupply N N

• Reason of the alarm: PSU detects a fault in the incoming power supply.

• Procedure for solving alarm1. Check the incoming power supply. If the incoming power supply is absent, contact

the incoming power supplier or the next level of maintenance support.2. Check the power source fuses.Change any defective fuse.


25/51

No Contact




NoContact EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR AntennaNearUnit N N

NoContactPROCESSING_ERROR_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR AntennaNearUnit N N

NoContact EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR AuxPlugInUnit Y Y

• Reason of the alarm:1. AuxPlugInUnit: Connection to resource is lost, or connection is not established.

The AdditionalText: "(Mixed Mode)" indicates that the RU may be shared andpossible conflict with another RAN needs to be considered.

2. AntennaNearUnit(EQUIPMENT_MALFUNCTION): The alarm originates from anantenna near unit due to either loss of connection or inability to establish it.

3. AntennaNearUnit(CONFIGURATION_OR_CUSTOMIZING_ERROR): The alarm isissued when there is no license for the feature to activate installed equipment.


26/51

No Contact• Actions for AuxPlugInUnit

1. Check that the configuration of the MO RiPort matches the physicalconfiguration .2. Identify and lock the faulty unit, replace the faulty unit (RU, cable, SFP..)

and unlock it.3. escalation.

• Actions for AntennaNearUnit

1. Check the cable connection.2. Restart the RU serving the AnteenaNearUnit.

3. Check ifthe proper licence is installed.


27/51

PowerFailure


serviceImpact


serviceDegrade

(Y = Yes, N= No)

PowerFailureEQUIPMENT_ALARM POWER_SUPPLY_FAILURE MINOR AuxPlugInUnit Y Y

• Reason of the alarm: Incoming power supply failure to RU.• Procedure of solving the alarm:

1. Loss of mains is the most likely cause for the PowerFailure alarm to be raised.Therefore, start by checking for external AC problems and make sure that thepower supply switch is turned on.

2. If the alarm ports of a Remote Radio Unit (RRU) are configured for poweroutage supervision, the ExternalAlarm is ceased on affected alarm ports atRRU power outage. Check the ExternalAlarm configuration as theExternalAlarm that preceded PowerFailure might point to the cause for

PowerFailure to be raised.3. If alarm still remains, check that the power supply cable to the PDU is

properly inserted and working. Change the cable if necessary.4. Identify the RU generating the alarm by inspecting the LED lights on the front

of the unit. The RU with all LED lights off is generating the alarm. Check thatthe power supply cable connecting the PDU to the RU is properly insertedand working. Change the cable if necessary.

5. Change the PDU. If alarm remains, change the RU/RRU.


28/51

RetFailure




RetFailure EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR RetSubUnit N N

• Reason of the alarm :1.Configuration file problem.The file needed for the actuator to know how to move that specific antenna unit is missing.

2.Unable to move antenna due to jam.Physical problem with the motor or the actuator detected on the RET subunit tilting theaddressed antenna unit.3.Actuator interference The actuator has been moved by an unknown reason.• Procedure of solving the alarm :

1. check the alarm additional information

2. If it is Configuration file problem, Install a correct antenna configuration file3. If it is Unable to move antenna due to jam,

- Inspect the antenna and remove any physical obstructions for tilt- If the alarm remains, identify and change faulty equipment

4. If it is Actuator interference, Set a new value for electricalAntennaTilt to tilt the antenna to thewanted position


29/51

VswrOverThreshold




VswrOverThreshold EQUIPMENT_ALARM EQUIPMENT_MALFUNCTION MINOR RfPort N Y

• Reason of the alarm :The alarm is caused by a decrease of return loss below the sensitivity threshold because ofproblems in the antenna unit or antenna feeder.• Procedure of solving alarm :1. Check that the RfPort and RfBranch MOs (for example, parametersAntennaSupervisionSensitivity, dlAttenuation, and ulAttenuation) are correctly configured.

-If the configuration is changed, restart the digital unit, as described in Restart Board.2. If the alarm remains, restart the radio unit, as described in Restart Board.Check if the alarm has ceased. It can take up to 30 minutes for the alarm to reappear.3. If the alarm remains, check that the feeder is connected properly to the antenna, andthat there is no short circuit in the feeder and antenna system. See Feeder SystemGuideline.4. If the alarm remains, check that there is no water in the feeder, no snow covering theantenna, or there is no excessive RF signal coming from an external source.5. If the alarm remains, replace the faulty antenna equipment. If applicable, replace the

Tower Mounted Amplifier (TMA).


30/51

Frequent alarm & Procedure


31/51

Disk Volume C/D Full




Disk Volume C Full EQUIPMENT_ALARM DISK_PROBLEM MAJOR ManagedElement N N

Disk Volume D Full EQUIPMENT_ALARM DISK_PROBLEM MAJOR PlugInUnit N N

•

Reason of the alarm :Too much redundant data stored on the C/D volume.• Procedure of solving alarm :1. Determine whether there are old UpgradePackage MOs that should be deleted. If

so, delete them.

2. Investigate whether there are further upgrade package MOs, or CVs that can bedeleted.If so, delete them.


32/51

Duplicate IP Address Fault

• Reason of the alarm:Configuration fault or communication protocol error.• Procedure of solving the alarm:1.For IpAccessHostEt:a.Set the correct address in the attribute ipAddress in the IpAccessHostEtMO.b.Wait for 5 minutes to see if it's ceased

2.For Ipv6Interface:a.Find the GigaBitEthernet MO by following the reference from the attributeethernetRef in the Ipv6Interface MO.b.Read the attribute macAddressLink1 from the GigaBitEthernet MO.c.Consult the next level of maintenance support or replace a board.




Duplicate IP Address FaultCOMMUNICATIONS_ALARM

COMMUNICATION_PROTOCOL_ERROR MAJOR IpAccessHostEt Y Y

Duplicate IP Address FaultCOMMUNICATIONS_ALARM

COMMUNICATION_PROTOCOL_ERROR MAJOR Ipv6Interface N N


33/51

Emergency Unlock of SoftwareLicensing




Emergency Unlock of SoftwareLicensing

QUALITY_OF_SERVICE _ALARM ALARM_INDICATION_SIGNAL MINOR Licensing N N

• Reason of the alarm :

The alarm is issued when someone activates the Emergency state, using the actionsetEmergencyState . The purpose of this Emergency state is to free the software of alllicense restrictions in an emergency situation, so that the capacity of the node ismaximized.• Procedure of solving alarm:1.Investigate whether a new LKF containing a Emergency Unlock Reset key for the node hasbeen ordered and received from the Ericsson Customer License Center. If so, continue withthe next step. If not, contact the Ericsson Customer License Center and order a new LKF.Wait for the new key to be received before proceeding.2.Install the new LKF into the node from the FTP or SFTP server, using the operation andmaintenance tool that is used for node maintenance. The MO action isupdateLicenseKeyFile.3.Verify that the alarm ceases.


34/51

ExternalAlarm

• Reason of the alarm:This alarm is issued for external equipment connected to the RBS, or equipmentwithin the RBS that is defined as external equipment. Possible alarm triggers are asfollows:1.An external equipment supervision limit is exceeded2.An external equipment fault condition existsAlarm severity and actions to take depend on which external equipment is issuing thealarm. Information in the alarm is based on the customer’s configuration of the

corresponding MO(1)

AlarmPort.• Procedure of solving the alarm:1.check that the corresponding MO AlarmPort is configured properly and consistentlywith the connected external equipment.




ExternalAlarmUNKNOWN_EVENT_TYPE

EXTERNAL_EQUIPMENT_FAILURE MINOR AlarmPort N N


35/51

ExternalLinkFailure

• Reason of the alarm:The alarm is issued when the X2 link to at least one neighboring eNodeB is

down after four re-setup attempts. The time between each re-setup attemptis controlled by the x2RetryTimer.• Procedure of solving the alarm:1.Check that the corresponding TermPointToEnb MO of the remote eNB is notin the LOCKED administrative state

2.Check the underlaying transport network between the eNB and the remoteeNB for faults and if such exist, correct them.




ExternalLinkFailure EQUIPMENT_ALARM LINK_FAILURE MINOR ENodeBFunction N N


36/51

FeatureResourceMissing

• Reason of the alarm:1. For Rfport:The VSWR feature license is missing or the VSWR feature is

not supported in the RU for the antenna port.2. For SectorEquipmentFunction:The optional feature license stated in

Additional Text is missing and the sector is configured for this feature3. For EUtranCellFDD:This alarm is issued during cell unlock if a feature

license is missing or inoperable. If the missing feature license is 6 CellSupport the alarm is generated when unlocking the fourth cell.


serviceImpact


serviceDegrade

(Y = Yes, N= No)

FeatureResourceMissingPROCESSING_ERROR_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR RfPort N N


CONFIGURATION_OR_CUSTOMIZING_ERROR MAJOR

SectorEquipmentFunction Y Y


CONFIGURATION_OR_CUSTOMIZING_ERROR MAJOR EUtranCellFDD Y Y


37/51

FeatureResourceMissing• Action for VSWR feature license missing and Rfport: Install and activate

VSWR Antenna Supervision license or turn off VSWR Supervision.

• Action for VSWR feature not supported and Rfport: Replace the RU or turnoff VSWR supervision

• Action for SectorEquipmentFunction or EUtranCellFDD: Install the featurelicense stated as missing in the Additional Text. If the Additional Textstates the license as inoperable, the operationalState of the feature is

disabled. Enable the feature.


38/51

Gigabit Ethernet Link Fault




Gigabit Ethernet Link FaultCOMMUNICATIONS_ALARM LOSS_OF_SIGNAL MAJOR GigaBitEthernet N Y

• Reason of the alarm:

1. Link Fault.The traffic on the link is disturbed. Link fault, board fault,Ethernet network fault or configuration fault.2. Autonegotiation Failed to Meet Minimum Configured Requirements. The

traffic continues at a lower speed than configured.


39/51

Gigabit Ethernet Link Fault• Procedure of solving the alarm:1. Ensure that the attribute autoNegotiation in the MO GigaBitEthernet, isaligned on the local and the remote side. If the alarm ceases, exit thisprocedure.2. If the fault is in the remote node and if the alarm ceases when the fault hasbeen repaired, exit this procedure. If there is no fault in the remote node, goto Step 3 .3. Identify the board with the faulty Gigabit Ethernet Link.4. Lock the faulty board, using the instruction Lock Board. The Lock type isHard lock.5. Restart the faulty board, using the instruction, Restart Board. TheRestartRank is Cold with Test and the RestartReason is Restart ordered toresolve O&M issues. In the field RestartInfo, write the name of this alarm.6. Unlock the board, using the instruction Unlock Board. If the alarm is notissued again, exit this procedure.7. If traffic continues at a lower speed than configured, check the used SFPinformation.


40/51

InconsistentConfiguration


ManagedObject

serviceImpact

(CellDown,CellAvailability =0%)(Y = Yes, N = No)

serviceDe

grade(Y = Yes,N = No)

InconsistentConfigurationPROCESSING_ERROR_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR AntennaUnit N N


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR DeviceGroup Y Y


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR RetSubUnit N N


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR RfPort Y Y


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR RiPort Y Y


CONFIGURATION_OR_CUSTOMIZING_ERROR MAJOR


InconsistentConfiguration

PROCESSING_ERR

OR_ALARM

CONFIGURATION_OR_C

USTOMIZING_ERROR MAJOR MbsfnArea N Y


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR AlarmPort N N


CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR EcPort N N


41/51

InconsistentConfiguration• Action for AntennaUnit:This alarm is raised when the total tilt range of the antenna unit is modified, there is noRemote Electrical Tilt (RET), and mechanicalAntennaTilt is out of the total tilt range.1.Change maximum or minimum total tilt or mechanicalAntennaTilt to get total tilt withinthe maximum and minimum total tilt range• Action for DeviceGroup:The Managed Object configuration of the unit is inconsistent. Either a program is missing orthe configuration is wrong.1. Consult the next level of maintenance support to retrieve an Upgrade Package with a

correct Managed Object configuration• Action for RetSubUnit:This alarm is raised when the total tilt range of the AntennaSubunit is modified, causing the

electricalAntennaTilt to be out of the total tilt range.1. Change maximum or minimum total tilt or electricalAntennaTilt to get total tilt within themaximum and minimum total tilt range. The electricalAntennaTilt shall be set to get totaltilt (electricalAntennaTilt on the RetSubUnit MO + mechanicalAntennaTilt on theAntennaUnit MO) within the maximum and minimum total tilt range.TheelectricalAntennaTilt also needs to be set within the ranges of the physical RET.


42/51

InconsistentConfiguration• Action for RfPort:The alarm is raised when more ports are configured than what the radio unitsupports.1.Check the software configuration, and configure the correct number of RETports.2.Restart DU.• Action for RiPort:This alarm is generated in Mixed Mode when the CPRI cable is not connectedaccording to what is configured in the MIB.

Additional Text: Either the CPRI cable is wrongly connected or there is aconfiguration fault (Mixed Mode)The AdditionalText: "(Mixed Mode)" indicates that the RU may be shared andpossible conflict with another RAN needs to be considered.1.Reconnect the CPRI cable.


43/51

InconsistentConfiguration•

Action for MbsfnArea:Inconsistent configuration of Mbsfn subframes. A cell is connected to several Mbsfnareas. The subframes in these Mbsfn areas are overlapped.1. Lock the MbsfnArea MO.2.Check the configuration of subframes used by the MbsfnArea in the attributecommonSFAlloc so that these do not overlap with subframes used by anotheractivated MbsfnArea.3.Check the configuration of notificationIndicator so that it is not the same as foranother MbsfnArea that is activated in the same cell.4.Unlock the MbsfnArea MO.

• Action for SectorEquipmentFunction:This alarm is raised because of, for example, an incorrect configuration of how thehardware, such as antenna near products, or radio equipment, are connected.The alarm might be related to output power licenses. For example, insufficient outputpower licenses are installed or there are hardware-related output power limitations.1.Check if the hardware, such as antenna near products or radio equipment, iscorrectly configured in the MOM. Modify the configuration if necessary.2.Check if sufficient output power licenses are installed or if there are any hardware-

related output power limitations.


44/51

InconsistentConfiguration• Action for AlarmPort:In mixed mode configurations, at external alarm port configuration, the RBSSystem attempts to setup a physical alarm port on a Remote Radio Unit (RRU)with a normallyOpen attribute that is different from the shared client's value.1.In the LTE node, lock the AlarmPort MO.2.In the WCDMA node, lock the AlmDevice MO.3.In the LTE node, set the normallyOpen attribute in the AlarmPort MO.4.In the LTE node, unlock the AlarmPort MO.5.In the WCDMA node, set the normallyOpen attribute in the AlmDevice MO.6.In the WCDMA node, unlock the AlmDevice MO.• Action for EcPort:

This alarm is raised if the hubposition is empty or not valid. Conflicting values ofhubposition also cause this alarm.1.Check if the hubposition is given a proper value, that is, the value is set to theport to which the hardware unit is connected to in the hub. The hubposition valueis not configured for any other EcPort MO.


45/51

License Key File Fault


ManagedObject

serviceImpact(CellDown,

CellAvailability =0%)(Y = Yes, N = No)

serviceDegrade

(Y = Yes,N = No)

License Key File FaultQUALITY_OF_SERVICE_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR CRITICAL Licensing Y Y

• Reason of the alarm:The node has no valid LKF installed.• Procedure of solving the alarm:1. Confirm that a new LKF has been ordered and received from the EricssonCustomer License Center.2. Install the new LKF in the node from the FTP or SFTP server. Use the action

updateLicenseKeyFile on the MO Licensing.


46/51

NTP Server Reachability Fault


ManagedObject



serviceDegrade

(Y = Yes,N = No)

NTP Server Reachability FaultCOMMUNICATIONS_ALARM UNAVAILABLE MAJOR IpSyncRef N N

• Reason of the alarm:Communication problems toward NTP server, configuration fault or HW fault.• Procedure of solving the alarm:1. Examine the value of the attribute, ntpServerIpAddress, in the MO,IpSyncRef(or “Get . Ntpserveraddress “ to check the value) 2. Contact the NTP server, using the action, ping on the MO, IpAccessHostEt

3. If there is no contact with the NTP server, contact the maintenance centerfor that NTP server, or contact the maintenance center for the network.Request them to act on the fault. There can be a configuration fault in thenetwork.

Password File Fault &Remote IP


47/51

Password File Fault &Remote IPAddress Unreachable




serviceDegrade

(Y = Yes,N = No)

Password File FaultQUALITY_OF_SERVICE_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR MINOR Security N N

• Procedure of solving the alarm:1.Access the node via SSH or Telnet.2.Set a new password, using the shell command passwd . The alarmautomatically ceases when a new password is set


serviceImpact(CellDown,CellAvailability =

0%)(Y = Yes, N = No)

serviceDegrade(Y = Yes,

N = No)

Remote IP AddressUnreachable

COMMUNICATIONS_ALARM UNAVAILABLE MINOR Sctp N N

• Procedure of solving the alarm:Check the IP address connectivity from core side.


48/51

ResourceConfigurationFailure




serviceDegrade

(Y = Yes,N = No)

ResourceConfigurationFailureEQUIPMENT_ALARM

EQUIPMENT_MALFUNCTION MINOR RetSubUnit N N

ResourceConfigurationFailurePROCESSING_ERROR_ALARM

SYSTEM_CALL_UNSUCCESSFUL MAJOR


ResourceConfigurationFailurePROCESSING_ERROR_ALARM TIMEOUT_EXPIRED MAJOR


ResourceConfigurationFailurePROCESSING_ERROR_ALARM

CONFIGURATION_OR_CUSTOMIZING_ERROR MAJOR EUtranCellFDD Y Y

ResourceConfigurationFailurePROCESSING_ERROR_ALARM TIMEOUT_EXPIRED MAJOR EUtranCellFDD Y Y

• Action for RetSubUnit:The alarm is raised when the resource configuration fails, because the RET tiltis in an unknown position.Calibrate the RET using the forcedCalibration action of the RetSubUnit.


49/51

ResourceConfigurationFailure• Action for SectorEquipmentFunction Systemcall Unsuccessful:

The alarm is raised when the sector is activated and the resource allocation forthe sector fails. This can be caused by a rejected signal from requested HW.1. Lock the sector using the SectorEquipmentFunction MO, check this MO andreferenced Rfbranch parameter values.2. Lock cell/sector and unlock sector/cell again.

• Action for SectorEquipmentFunction TIMEOUT_EXPIRED:This alarm is raised when the sector is activated and the resource allocation forthe sector fails. This can be caused by a signal timeout from requested HW.1. Lock the cell using the EUtranCellFDD MO.2. Unlock the cell.3. Check that the alarm has ceased.4. If the alarm remains, restart the RU. See Restart Board.5. Check that the alarm has ceased.6. If the alarm remains, restart the node. See Restart Node.7. Check that the alarm has ceased.8. If the alarm remains, consult the next level of maintenance support


50/51

ResourceConfigurationFailure• Action for EUtranCellFDD CONFIGURATION_OR_CUSTOMIZING_ERROR :1. Check the EUtranCellFDD MO parameter values. Make sure configuraion is correct.2. Lock EUtranCellFDD and SectorEquipmentFunction, and unlock them.

• Action for EUtranCellFDD TIMEOUT_EXPIRED:The alarm is raised when activation of resources hangs or when the cell is activated and the

resource allocation for the cell fails. This can be caused by a missing signal from therequested resource or by disabled (failed) resources during startup of the node.1. Lock and Unlock the cell using the EUtranCellFDD MO.Check ifthe alarm has ceased.2. If the alarm remains, check that the Digital Unit (DU) and RU is enabled and unlocked.4. If the DU is locked, unlock the DU.5. If the RU is locked, unlock the RU.6. Lock the cell using the EUtranCellFDD MO.7. Unlock the cell.8. If the alarm remains, restart the RU. See Restart Board.8. Check that the alarm has ceased.9. If the alarm remains, restart the node. See Restart Node.10. Check that the alarm has ceased.11. If the alarm remains, consult the next level of maintenance support.


51/51

LTE Alarm list

Documents

Eutran Frequent Alarms