Scribd
Upload
1K views23 pages

Node B - Alarms Troubleshooting

Uploaded by

hassan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
1K views23 pages

Node B - Alarms Troubleshooting

Uploaded by

hassan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 23

Node B – Alarms &

Troubleshooting
Contents

 How to check alarms???.


 Test Board Functionality
 HW Status – ATMA, ARETU, RUS,DUW.
 DUW Manual Restart Procedure.
 How to check sector status???
 Ping Test – NTP Server & OAM Default GW
 Troubleshooting

© Ericsson AB 2009 2 2010-11-10


1. How to check for alarms???

Open RBS Element Manager.


Select the tab Alarm ( as in picture )
Click on Alarm List for present Alarms
Click on Alarm Log for Alarms History

© Ericsson AB 2009 3 2010-11-10


Alarm List View

Focus on MO Instance , Probable Cause & Specific Problem.


MO Instance – Tells where this alarm affected ( Eg: Which Sector )

Probable Cause – Tells the nature of alarm ( Eg: HW / SW / Configuration Issue )

Specific Problem – Tells what is the alarm

© Ericsson AB 2009 4 2010-11-10


Alarm Log View

© Ericsson AB 2009 5 2010-11-10


Test Board Functionality

•Test Board can be used to confirm if the HW is faulty or


not.

•DUW, RUS, ATMA, ARETU for all sectors can be tested.

•This option is available in Tools tab in Element Manager.

© Ericsson AB 2009 6 2010-11-10


Test Board Procedure

1. Select the board to test


2. Press Lock ( bottom right Button )
3. Select the board again
4. Press Start ( bottom right Button )
5. The RESULT will show PASSED / FAILED
6. Press Unlock to finish the test.

© Ericsson AB 2009 7 2010-11-10


HW Status – ATMA & ARETU

Select & Expand EquipmentSector AntennasSectorAntenna=1-1/2-1/3-1.

Check the OperationalState for ENABLED/DISABLED

ENABLED = Working Fine / DISABLED = We have a problem.

© Ericsson AB 2009 8 2010-11-10


HW Status – RUS

•Select & Expand EquipmentRbsSubrack=RUW1RbsSlot=3/5/7/9/11/13.


•RbsSlot=3/7/11 for U900 RUSs & 5/9/13 for U2100 RUSs
•Check the OperationalState for ENABLED/DISABLED
•ENABLED = Working Normal / DISABLED = Troubleshooting required.

© Ericsson AB 2009 9 2010-11-10


HW Status – DUW

•Select & Expand EquipmentSubrack=1Slot=1PluginUnit=1


•Check the OperationalState for ENABLED/DISABLED
•ENABLED = Working Normal / DISABLED = Troubleshooting required.

© Ericsson AB 2009 10 2010-11-10


DUW – Manual Restart Procedure

•Select & Expand EquipmentSubrack=1Slot=1PluginUnit=1


•Right Click PluginUnit=1, Select Lock / Unlock to Lock DUW.
•Right Click PluginUnit=1, Select Manual Restart.
•A new window will open up ( see next page ).

© Ericsson AB 2009 11 2010-11-10


DUW – Manual Restart Procedure

1. For restartRank , select RESTART_WARM(0)


2. For restartReason, select PLANNED_RECONFIGURATON(0)
3. For restartInfo, enter some text
4. Then click Execute to initiate restart.

© Ericsson AB 2009 12 2010-11-10


How to check Sector status???

•Select Radio Network


•Check operationalState & availabilitySatus for
RbsLocalCell=S1C1/S2C1/S3C1.
•operationalState = ENABLED & availabilitySatus = NO_STATUS
means cell / sector is up.
•operationalState = ENABLED & availabilitySatus = OFFLINE means
cell / sector is down.

© Ericsson AB 2009 13 2010-11-10


Ping Test : NTP Server & OAM Default Gateway

•Select & Expand : IP RelationsIP Access Host ET IPaccesshostET=1.


•Click on MO PropertiesActions
•Enter NTP Server IP in host ( From OAM Script )
•Press Execute
•If Result = Alive, site is reachable / Result = No Answer, Site is not reachable

•TO Ping OAM Default Gateway IP, Use Hyper Terminal / Tera Term / Putty
•Use Command “ Ping <oamDefaultRouter 0 IP address>. ( From OAM Script )
•The Result will be Alive / No Answer.

© Ericsson AB 2009 14 2010-11-10


Troubleshooting
 Node B / Site Down:-
Case 1:- Site Down, DUW not reachable from RNC.

 Reasons may be Power / Transmission / Climate (High Temp) / HW Faulty (DUW)


 Contact 2G BSS support to check GSM is affected, and check a history of alarms
like Mains failure, RBS Running On Battery, System Under Voltage etc to verify
power issue. Also external alarms for High Temp ( if applicable ).
 Contact Transmission Support to check the MW Link status, along with alarm log.
 Check the transmission cable between DUW & Traffic Node.
 Use TEST BOARD to check the DUW.

Case 2:- Site Down, DUW reachable from RNC.

 Reasons may be temporary or permanent SW issue.


 Contact RNC Support team to Lock all HWs and give a restart node with latest CV.
 For a permanent SW problem, perform a Format & Reconfiguration.

© Ericsson AB 2009 15 2010-11-10


Troubleshooting
 NTP Server Reachability Fault / NTP Server Time Sync
Problem:-

 Most probably a Transmission Issue.


 Use ping test for NTP Server & OAM Default Gateway to confirm.
 Take Transmission Support to check the link status, Vlan, Ethernet & WAN
configurations in Traffic Node
 If not a transmission Issue, contact RNC support for clearance.

 Gigabit Ethernet Link Fault:-

 Check the transmission cable between DUW & Traffic Node.


 Take Transmission Support to check the link status, Vlan, Ethernet & WAN
configurations in Traffic Node.
 Check the NPU in Traffic Node is healthy and working well.
 Check the status of TN A port in DUW.

PS:- This alarm will also result in raising NTP Server related alarms.

© Ericsson AB 2009 16 2010-11-10


Troubleshooting
 Emergency Unlock of Software Licensing:-

 This alarm is related to Emergency State activation in DUW.


 To be cleared by RNC Support team.

 Password File Fault:-

 This alarm will be raised after Format & Reconfiguration


 To be cleared by RNC Support team.

 License Key File Fault:-

 This alarm will be raised after Format & Reconfiguration.


 Also at the time of using a new DUW.
 To be cleared by RNC Support team.

© Ericsson AB 2009 17 2010-11-10


Troubleshooting
 DownlinkBaseBandPool_DlHwLessThanDlCapacity /
UplinkBaseBandPool_UlHwLessThanUlCapacity:-

 Confirm all RUS’s are operational with out any alarms.


 This alarm could also be related to License issues, contact RNC support to verify this
possibility.
 Reload the DUW with latest CV
 This alarm also can be associated with another alarms.

 RaxDeviceGroup_GeneralSwError /
TxDeviceGroup_GeneralSwError :-

 This alarm is related to SW error in DUW


 Lock all the HW’s and restart DUW
 If not cleared, Perform format & reconfiguration.
 If not cleared, Replace DUW

PS:- This alarms will be a reason for above alarm.


© Ericsson AB 2009 18 2010-11-10
Troubleshooting
 AuxPlugInUnit_CommunicationLostWithTma:-

 Cause of this alarm is RUS can’t detect the TMA.


 Reasons might be feeder swap between RF A & RF B ports in RUS, Feeder
connector not done very well, loose jumper, Faulty TMA or Faulty RUS (Very rarely).
 To find out swap feeder, take support from RNC to check the TMA current.
 Confirm all the connectors and connection points are in good shape.
 Replace TMA if confirmed faulty.

 AuxPlugInUnit_CommunicationLostWithRet:-

 Alarms related to TMA can cause this alarm


 If TMA is ok, then it could be related to RETU Cable or RETU itself.
 Check the continuity of cable using multi-meter, if faulty replace the cable.
 If cable is fine, then replace RETU

© Ericsson AB 2009 19 2010-11-10


Troubleshooting
 RetDevice_RetFailure ( Not Configured ) /
RetDevice_ElectricalAntennaTiltOutOfRange:-

 The above two alarms are configuration error related alarms.


 Can be cleared remotely.

 DeviceGroup_SfpModuleConfigurationMismatch:-

 This alarm depends on how many sectors are created in Node B & how many RUS’s
are connected.
 Make sure all the RUS’s are operational
 Check the CPRI cables are in good condition

© Ericsson AB 2009 20 2010-11-10


Troubleshooting
 DigitalCable_Disconnected:-

 DUW doesn’t have communication with RUS


 Check CPRI cable ( Try to disconnect & Reconnect the cable )
 Check RUS ( DC Power, Reset ), if not cleared replace RUS.

 AntennaBranch_FeederCurrentTooLowInBranchA /
AntennaBranch_FeederCurrentTooHighInBranchB:-

 If the alarm is related to Branch A, check the feeder connectors& jumpers are
properly made and tightened.
 Next, check and confirm the TMA is not faulty. If faulty, replace TMA

 If the alarm is related to branch B, turn of the supervision by below steps:

– Select & Expand: EquipmentSector AntennasSectorAntenna=1-1/2-1/3-1


– Right click: AntennaBranch=BMO PropertiesLow Current Suprvision = OFF
– Create CV & make it startable.

© Ericsson AB 2009 21 2010-11-10


Troubleshooting
 DeviceGroup_TemperatureExceptionallyHigh:-.

 Reason is VSWR or High Temperature.


 Normally this alarm is raised in RUS 02 type due to VSWR

 Carrier_RejectSignalFromHardware:-

 If this alarm appeared in RUS 02 based sites, Lock & Reset HW. If not cleared
replace RUS
 If this alarm appeared in RUS 01 based sites, swap the RUS to RUS 02.

 Disconnected  (Lost contact with the node that controls


external alarms, power and climate HW, cabinetIdentifier):-

 The reason behind this alarm is wrong Node Parameter configuration.


 In DUW, define Support System Control = False / Hub Position = <A5/A6/A7>
 In DUG, Define Add Node = <A5/A6/A7>
 Also, check the cable between DUW & SHU.
© Ericsson AB 2009 22 2010-11-10
© Ericsson AB 2009 23 2010-11-10

You might also like