BB Alarm Troubleshooting
BB Alarm Troubleshooting
BB Alarm Troubleshooting
1. Alarm:
Solution:
==============================================================================
1241 NodeSupport=1,SectorEquipmentFunction=S5
==============================================================================
administrativeState 1 (UNLOCKED)
availabilityStatus i[0] =
availableSectorPower 0
configuredOutputPower 40000
eUtranFqBands s[6] = Band3: full on all Band4: partial on all Band9: full on all Band10: partial on all
Band35: partial on all Band66: partial on all
mixedModeRadio true
operationalState 1 (ENABLED)
reservedBy [1] =
rfBranchRef [4] =
sectorEquipmentFunctionId S5
userLabel
utranFddFqBands s[4] = Band III: full on all Band IV: partial on all Band IX: full on all Band X: partial
on all
=====================================================================
Total: 1 MOs
Check the configuration of rfbranch one by one. In this case, the parameter of dlTrafficDelay for rfbrach 2 is wrong,
=====================================================================================
977 Equipment=1,AntennaUnitGroup=5,RfBranch=1
=====================================================================================
auPortRef [1] =
dlAttenuation i[15] = 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
dlTrafficDelay i[15] = 114 114 114 114 114 114 114 114 114 114 114 114 114 114 114
reservedBy [1] =
rfBranchId 1
rfPortRef FieldReplaceableUnit=RRU-5,RfPort=A
tmaRef
ulAttenuation i[15] = 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
ulTrafficDelay i[15] = 114 114 114 114 114 114 114 114 114 114 114 114 114 114 114
userLabel
=====================================================================================
Total: 1 MOs
=====================================================================================
872 Equipment=1,AntennaUnitGroup=5,RfBranch=2
=====================================================================================
auPortRef [1] =
dlAttenuation i[15] = 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
dlTrafficDelay i[15] = 114 114 114 114 114 114 114 114 114 114 114 114 114 114 114
reservedBy [1] =
rfPortRef FieldReplaceableUnit=RRU-5,RfPort=B
tmaRef
ulAttenuation i[40] = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
-1 -1 -1 -1 -1 -1 -1 -1 -1
ulTrafficDelay i[40] = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1
-1 -1 -1 -1 -1 -1 -1 -1 -1 -1
userLabel
Total: 1 MOs
Step1:
===================================================================================
872 Equipment=1,AntennaUnitGroup=5,RfBranch=2
===================================================================================
=====================================================================================
Id MO ulAttenuation Result
=====================================================================================
=====================================================================================
Total: 1 MOs attempted, 1 MOs set (Takes effect: cells using RfBranch disabled/enabled)
===================================================================================
872 Equipment=1,AntennaUnitGroup=5,RfBranch=2
===================================================================================
=====================================================================================
Id MO ulTrafficDelay Result
=====================================================================================
872 AntennaUnitGroup=5,RfBranch=2
114,114,114,114,114,114,114,114,114,114,114,114,114,114,114 >>> Set.
=====================================================================================
Total: 1 MOs attempted, 1 MOs set (Takes effect: cells using RfBranch disabled/enabled)
Step 2:
Note:
ulTrafficDelay and dlTrafficDelay: The value range for each entry is 0..500000 (0..500000 ns). Unused
entries are set to -1.
2. NGS
Background:
In the synchronization group LTE is the role for SYNC_PROVIDER, which means LTE get the sync signal
directly from NTP server and GSM/UMTS is the role for SYNC_RECEIVER.
Alarm:
Root Cause:
LTE baseband don’t play the role for provide due to UMTS is up before LTE ready.
After LTE back to service, both LTE/UMTS stay the status for SYNC_PROVIDER.
Solution:
Just stop receive sync signal using the action below for both UMTS and LTE
Step1:
UMTS:
bl TransportNetwork=1,Synchronization=1,NodeGroupSyncMember=1
LTE:
Transport=1,Synchronization=1,RadioEquipmentClock=1,NodeGroupSyncMember=1
Step2:
deblock LTE first, check NGS local status, make sure it’s SYNC_PROVIDER
Step3:
Issue:
Solution:
Step1:
=====================================================================
MO Attribute Value
=====================================================================
======================================================================
Total: 1 MOs
Step2:
[Node Side] Re-run the online certificate enrollment, make sure it succeed.
Step3:
[Node Side] Finish the post work after online certificate enrollment.
Step4:
[OSS Side] Execute the WA provided by Hannu (remove the node name from
/var/tmp/nma_added.
4. Alarm:
After the node back, check alarm, if not cleared, go to next step
step2. Match cell with sector and RRU to address the issue location
=====================================================================
=====================================================================
=====================================================================
Then you can easily match the cells to its sector carrier, then the RRU can be match.
Ex: cell EUtranCellFDD=CMI6945R_1NB01_S03, its sector carrier is 7, then its RRU is RRU-7
LTE 900 share RRU with GSM 900, and RRU port DATA_1 used for LTE while DATA_2 used
for GSM
LTE 1800 is LTE only, then RRU DATA_1 should be used for LTE
LTE 2100 share RRU with UMTS 2100, and RRU port DATA_2 used for LTE while DATA_1
used for GSM
=====================================================================
=====================================================================
From the information get from step 2, you can easily find this RRU is used for L1800, so
DATA_1 should be used.
There will be alarm like cable wrongly connected or no HW detected if the port reference is
incorrect.
Just modify the riportRef2 with right one, cell/rru need to be locked during modify
Please go to next step if all configuration is correct or the alarm still there
Please note that we can only call ASP check HW connection after we check the configuration
ourselves,
Otherwise they will complain if HW connection is ok while the root cause is wrong
configuration in baseband!
IBC –
For SIMO
6. Alarm:
Solution:
Step1:
If issue port is ‘A’ in the alarm slogan, just let ASP check the feeder cable connection between
RRU RF port A and antenna.
Check type of related issue cells, check with ASP about it is IBC or MACRO.
If issue cell is MACRO, just let ASP check the feeder cable connection between RRU rf port B and
antenna.
get . noofused
bl fdd
bl sector
bl Equipment=1,AuxPlugInUnit=RRU-1,DeviceGroup=ru,RfPort=B
deb fdd
deb sector
7. Alarm:
Step1:
>get . vswr
FieldReplaceableUnit=RRU-4,RfPort=A vswrSupervisionSensitivity 50
Step2:
8. Alarm:
2016-05-13 09:51:27 M Resource Allocation Failure
EUtranCellFDD=LPG8201T_2NB01_R01 (Requested TX-power is not available
totalPowermW: 7007.134651, availPowermW: 5128.613840)
Step1:
>get . power
Step2:
Step3:
>restart RRU
9. Alarm:
RaxDeviceGroup_GeneralSwError
Subrack=1,Slot=1,PlugInUnit=1,PiuDevice=5,RaxDeviceGroup=1 (equipment_malfunction)
Background:
Solution:
Restart Piudevice=5
10. Alarm:
11. Alarm:
12. Alarm:
2016-05-23 09:05:38 w Sync Frequency Server Reachability Fault
Synchronization=1,RadioEquipmentClock=1,RadioEquipmentClockReference=1 (No IP
connectivity towards NTP server)
Symptom:
Solution:
Step1:
=====================================================================
MO Attribute Value
=====================================================================
Ntp=1,NtpFrequencySync=1 syncServerNtpIpAddress 10.79.36.16
=====================================================================
Total: 2 MOs
Step2:
Check IP design from Alice Wang mail. Check the NTP server IP. Please modify it if here is the
wrong IP.
Step3:
=====================================================================
6151 Transport=1,Ntp=1,NtpFrequencySync=1
=====================================================================
Set syncServerNtpIpAddress on 1 MOs. Are you Sure [y/n] ? y
=====================================================================
Id MO syncServerNtpIpAddress Result
=====================================================================
=====================================================================
Total: 1 MOs attempted, 1 MOs set
=====================================================================
6152 Transport=1,Ntp=1,NtpFrequencySync=2
=====================================================================
=====================================================================
Id MO syncServerNtpIpAddress Result
=====================================================================
6152 Ntp=1,NtpFrequencySync=2 10.79.36.34 >>> Set.
=====================================================================
Total: 1 MOs attempted, 1 MOs set
Step4:
13. Alarm:
Description:
Solution:
Ask asp check rilink, re-plugin SFP module.