Alarm
Category
NbapCommon_Layer3SetupFailure
Critical
BfDevice_BatteryMissing M BfDevice_DcDistributionFailure BfDevice_BatteryVoltageSupervisionTooLowPrioLoadDisconnected BfDevice_BatteryVoltageSupervisionTooLowMainLoadDisconnected
Major Major Major Major
Auto-Configuration of Board Not Possible unavailable PsDevice_LossOfMains
Warning Major
AuxPlugInUnit_CommunicationLostWithRet
Major
AuxPlugInUnit_CommunicationLostWithAsc AuxPlugInUnit_CommunicationLost
Major Major
AntennaBranch_FeederCurrentTooHighInBranchB SectorAntenna_FeederCurrentTooHigh equipment_malfunction SectorAntenna=3
Major Major
NodeBFunction_UlHwUsageExceedsUlLicenseLevel
Major
Emergency Unlock of Software Licensing
Major
FcuDeviceGroup_NumberOfHwEntitiesMismatch
Major
DownlinkBaseBandPool_DlHwLessThanDlCapacity
Minor
NodeBFunction_DlHwUsageExceedsDlLicenseLevel
Major
Carrier_SignalNotReceivedWithinTime timeout_expired
Major
Ethernet Switch Port Fault
Major
Loss of Tracking
Major
AlmDevice_ExternalAlarm
Critical
BfDevice_BatteryChargingFailure PDH Loss of Frame IMA Link Reception Unusable at Far End Remote Defect Indication on IMA Link IMA Link Reception Misconnected Loss of IMA Frame
Major Major Warning Warning Major Major
PowerSupplySystem_BatteryOverTemperature
Major
UpLinkBaseBandPool_ULHWLessThanULCapacity FcuDeviceGroup_EnclosureDoorOpen
Minor Major Major
TxDevicegroup_GeneralSWError Plug-In Unit General Problem UtranCell_NbapReconfigurationFailure w CluDeviceGroup_EnclosureDoorOpen UbchDeviceSet_GeneralSWError PowerSupplySystem_BatteryOverTemperature RuDeviceGroup_GammaUplinkFailure RuDeviceGroup_GeneralHwError PsuDeviceGroup_GeneralHwError RetDevice_RetFailure RbsLocalCell_MaxNumHsPdschCodesExceedsLicense Key File Fault dLimit RbsLocalCell_CellReleaseFailure TpaDevice_AmplificationError TrDevice_GeneralHwError Power Failure Left Slot System Clock in Holdover Mode AuxPlugInUnit_PiuConnectionLost E1 Down Sector Failure
N.B: Sometimes a restart is the only thing needed to clear an alarm.
Major Warning Major Major Major Major Major Major Major Major Major Major Major Major Major Major Major Critical
Resolution Transmission related alarm. Node B is having connectivity issues with the RNC.Most times a node restart would clear the alarm. If not, Transmission Team should check their end (Hubs involved) The alarm could be as a result of A disconnected or faulty cable between the battery and the Battery Fuse Unit (BFU), A faulty BFU, A faulty battery or the battery is stolen. What can be done a) check the cable from the BFU to the battery b) replace the BFU c) replace/install the battery. BFU can be restarted using element manager.If BFU is not in use, lock it. Likely causes, A blown fuse or a tripped circuit breaker. Replace Fuse or CCT Breaker. RBS is running on batteries only and the battery voltage is below a cert ain operator-defined or hardware default level .BFU locked if not in use Has to do with one of the Boards.Board suspected faulty or not in use.Boards should be locked and unplugged as the case may be. PSU Breaker controlling AC m ains should be reset. PSU could be r eplaced. Communication with RETU is lost.You could attempt restarting the RUIF, RU, and FU. RETU is suspected to be faulty and should be replaced Communication with ASC is lost.You could attempt restarting the RUIF, RU, and FU. ASC is suspected to be faulty and should be replaced
Likely cause is Incorrectly connected feeder or jum per cable between ASC, RETU and Antenna.Lock/Unlock RU and wait 10mins to see if alarm clears. Faulty Antenna. Antenna should probably be changed. licensed limit has been reached in the RBS.Uplink Hardware is RAX card. Usually a new upgraded license is installed. The alarm is issued when someone activates the Emergency state, using the action, setEmergencyState. The purpose of this Emergency state is to free the software of all license restrictions in an emergency situation, so that the capacity of the node is m aximized. The Emergency state remains active for seven days. After this seven-day period, the Emer gency state ceases automatically, but the alarm remains, to act as a reminder that the Emergency state has been activated once already. The Emergency state can be activated again for a second seven-day period, if necessary. After this second seven-day period, the Emergency state can only be activated again, if a new License Key File (LKF) containing an Emergency unlock reset key is received from Ericsson and installed into the node. E// generates license key based on finger print of the node. i.e. X911506883. License is updated using moshell or SMO to clear the alarm. License is transferred to node via FTP most likely causes of the alarm are: A faulty or disconnected fan unit cable , Too few fans installed. Reset FCU breaker on Power distribution unit on site Downlink Hardware TX Board(S) ar e not utilizing up to the capacity configured on the license.Alarm is minor and it dosent affect traffic. To clear the alarm more TX Boards might need to be added to meet up to configured capacity or the license is downgraded. Restarting the TX Boards could also be attempted. licensed limit has been reached in the RBS.Downlink Hardware isTX card. Usually a new upgraded license is installed. Restart the board concerned, Restart the RBS, Export and Delete in EM and run the Site and Cabinet Configuration. Ethernet Switch Ports are located on the ETM-FX Boards which are used for IP. If technology in place is ATM not IP then the particular port should be blocked to clear the alarm since the board is not in use. Site is losing sync reference. A restart could clear the alarm. Also doing get sync, lacl sync, acc proxy lossoftracking and adding a sync ref could also do. Changing sync priority is also another option. BBU(Battery Backup Unit) Breaker should be reset to clear the alarm most times.BFU can also be replaced to clear alarm.
The likely causes of the alarm are: A disconnected cable A faulty battery temperature sensor or faulty sensor cable A faulty Battery Fuse Unit (BFU). A hard reset done at site could clear the alarm. Reseting the node from the mains.
Check the status of the E1. st phys or st e1. Inform Field Engineer to visit site and investigate.Reset TX Link The likely cause is one of the following: A fault in the climate system A battery temperature sensor fault Battery failure High environmental temperature
Uplink Hardware RAX Board(S) ar e not utilizing up to the capacity configured on the license.Alarm is minor and it dosent affect traffic. To clear the alarm, more RAX Boards might need to be added to meet up to configured capacity or the license is downgraded. Restarting the RAX Boards could also be attempted. RBS door is opened or there is a risk for temperature problems caused by disturbed airflow. The alarm usually comes with an MO reference like Subrack=1,Slot=11,PlugInUnit=1,TxDeviceGroup=1, which shows that the software errors is coming from slot 11 which is the TX Card. A cold restart of the card acc 001100 manualrestart should clear the alarm. 1.Lock, restart and unlock the board or Plugin Unit might need to be replaced. Door to the site is open. Field Engineer should be called to close the entr ance door to the site. Restart RAX Card Problem suspected to be Faulty RU, RAX, RUIF or Gamma cable between RUIF and RU.Restart RAX Card, Rus, RUIF.If alarm persists, change the respective hardwares. Most likely RU might need to be changed. Restart RU,Lock/Unlock PSU should be changed
Means it takes time for a call to be released. A warm restart should be enough to clear the alarm. Fault affects Transmit Power Amplifier in RU. Restart or replace RU 2G is usually down most times when alarm comes up Usually follows with a loss of tracking alarm. A warm restart should do. If not clear the lossoftracking alarm. Check the status of the E1. st phys or st e1. Inform Field Engineer to visit site and investigate. Swap Rus and restart
