Uploaded by gibsonjohn626

Insufficient RF power issues and solutions.docx

advertisement
Insufficient RF power issues and solutions
1, Insufficient RF power in radio equipment Alarm
SW version:
LTE RAN L16B
Symptoms:
Alarm present- Resource Allocation Failure Service Degraded
SectorCarrier=1 (Insufficient RF power in radio equipment)
Diagnostics:
Answer/Analysis Result
This alarm means configuredMaxTxPower more than
availableHwOutputPower in current configuration
Remedy Procedure:
Do following steps: 1) Block sector 2) Block cell 3) Change
configuredMaxTxPower value should be equal to availableHwOutputPower
4) Deblock sector 5) Deblock cell Example->
NODE> alt 2016-08-02 10:51:22 m Resource Allocation Failure Service
Degraded SectorCarrier=1 (Insufficient RF power in radio equipment) >>>
Total: 1 Alarms (0 Critical, 0 Major)
NODE> get . OutputPower 160802-11:08:37 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699
=======================================================
======================================= Proxy MO Attribute
Value
=======================================================
======================================= 1516
SectorEquipmentFunction=1 availableHwOutputPower 10000 NODE> get .
configuredMaxTxPower 160802-11:09:11 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699
=======================================================
======================================= Proxy MO Attribute
Value
=======================================================
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
======================================= 1275 SectorCarrier=1
configuredMaxTxPower 20000
configuredMaxTxPower is more than availableHwOutputPower so need to be
change Step-1) NODE> bl sector
Step-2) NODE> bl cell Step-3) NODE> set 1275 configuredMaxTxPower
10000 160802-11:09:40 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699 Set
configuredMaxTxPower on following 1 MOs ?
=======================================================
============================ 1275
ENodeBFunction=1,SectorCarrier=1
=======================================================
============================ Set configuredMaxTxPower on 1
MOs. Are you Sure [y/n] ? y
=======================================================
======================================= Id MO
configuredMaxTxPower Result
=======================================================
======================================= 1275 SectorCarrier=1
10000 >>> Set.
=======================================================
======================================= Total: 1 MOs
attempted, 1 MOs set (Takes effect: Object unlocked) Step-4) NODE> deb
sector 160802-11:09:57 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699 Deblock
following 4 MOs ?
=======================================================
============================ 1332
ENodeBFunction=1,EUtranCellFDD=1 Step-5) NODE> deb cell
NODE> st cell 160802-11:10:11 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699
=======================================================
============================ Proxy Adm State Op. State MO
=======================================================
============================ 352 1 (ENABLED)
Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,SubDeviceGroup=bb1,CellDeviceSet=1 1332 1 (UNLOCKED) 1 (ENABLED)
ENodeBFunction=1,EUtranCellFDD=1 Total: 5 MOs
NODE> get . configuredMaxTxPower 160802-11:12:59 10.75.0.109 16.0q
ERBS_NODE_MODEL_H_1_83_COMPLETE stopfile=/tmp/23699
=======================================================
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
======================================= Proxy MO Attribute
Value
=======================================================
======================================= 1275 SectorCarrier=1
configuredMaxTxPower 10000
2, Insufficient RF power Hardware Activation Codes
Case 1:
SW version:
LTE RAN L17A
Symptoms:
Alarm present- alarm Resource Allocation Failure Service Degraded
SectorCarrier=6 (Insufficient RF power Hardware Activation Codes)
Diagnostics:
Answer/Analysis Result
This is Licensing issue, System run out of license.
Remedy Procedure:
Alarm :
=======================================================
============================ Sever Specific Problem MO
(Cause/AdditionalInfo)
=======================================================
============================ Min Resource Allocation Failure
Service Degraded SectorCarrier=5 (Insufficient RF power Hardware
Activation Codes)
=======================================================
============================ 2334
ENodeBFunction=1,SectorCarrier=5
=======================================================
============================ SectorCarrierId 5 availabilityStatus 64
(DEGRADED) configuredMaxTxPower 80000 maximumTransmissionPower
430 partOfSectorPower 100 License:
=======================================================
============================ CapacityId FAJ StartDate StopDate
CapLimit CapValue HardLimit HardValue ChangeReason Description
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
=======================================================
============================
CXC4010625 FAJ1210546 2016-12-25 No Limit True 6 True 6 Licensed
Output power 20W to 40W CXC4010626 FAJ1210547 2016-12-25 No Limit
True 6 True 6 Licensed Output power 40W to 60W CXC4011161
FAK1010020 2016-12-25 No Limit True 6 True 6 Licensed Output Power
60W to 80W
This is a licensing rather than a radio software issue. On the systems, there are
6 licenses for the power classes (6 20-40, 6 40-60, 6 60-80W) According to
configuration one of the configured sectors uses radios in cascade. Since
power license apply to radios rather than to sectors. As such, the sector with
the cascaded radios uses up two 20W-40W licenses instead of just one, and
thus for one of the sectors there are no 2-40W licenses left, and it remains at
20W. The alarm is raised because the system runs out of 20W to 40W licenses
- it has 6 but it needs 7, since one of the sectors uses 2 radios in cascade. The
CPI documentation states that in this cascaded configuration, 2 licenses are
required. It is documented in the CPI for the license 303/1553-HSC 105 50/1V1 Uen A Output Power 20 W to 40 W
http://cpistore.internal.ericsson.com/alexserv?LI=EN/LZN7850001/1
R10C&FN=303_1553-hsc10550_1-v1uen.a.html&ac=linkext Section 2.1
Table 1 shows that when you have 2 radios in the sector configured at 80W, it
uses 2 40W licenses.
Case 2:
SW version:
LTE RAN L17A
Symptoms:
Alarm present:
Service Degraded EUtranCellFDD=Cell1 (performance_degraded)
Resource Allocation Failure Service Degraded SectorCarrier=Cell1
(Insufficient RF power Hardware Activation Codes)
Before upgrade:
> get sec power
=======================================================
=======================================
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
MO Attribute Value
=======================================================
=======================================
SectorCarrier=Cell1 csiRsPowerRatio 0
SectorCarrier=Cell1 maximumTransmissionPower 460
SectorCarrier=Cell1 partOfSectorPower 100
SectorEquipmentFunction=S1 availableSectorPower 40000
SectorEquipmentFunction=S1 configuredOutputPower 80000
SectorEquipmentFunction=S2 availableSectorPower 0
SectorEquipmentFunction=S2 configuredOutputPower 80000
SectorEquipmentFunction=S3 availableSectorPower 0
SectorEquipmentFunction=S3 configuredOutputPower 80000
=======================================================
=======================================
After upgrade:
> get sec power
=======================================================
=======================================
MO Attribute Value
=======================================================
=======================================SectorCarrier=Cell1
configuredMaxTxPower 80000
SectorCarrier=Cell1 csiRsPowerRatio 0
SectorCarrier=Cell1 maximumTransmissionPower 460
SectorCarrier=Cell1 txPowerPersistentLock false
SectorEquipmentFunction=S1 availableHwOutputPower 0
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
SectorEquipmentFunction=S2 availableHwOutputPower 0
SectorEquipmentFunction=S3 availableHwOutputPower 0
=======================================================
=======================================
Diagnostics:
Answer/Analysis Result
This is Licensing issue, System run out of license.
Remedy Procedure: Do following steps: 1) Block sector 2) Block cell 3)
Apply for a new license and install it, or activate the EM license for
maintaining the service. 4) Deblock sector 5) Deblock cell
3, Related Knowledge
If upgrading from release L16B Please see PLM Info on SectorCarrier power
altered after L17A upgrade for more recent info about this issue.
Problem could occur while on L16B IP1 (or earlier SW):
used one of the deprecated parameters:
configuredOutputPower/partOfSectorPower;
and/or used the new MOM parameter: ConfiguredMaxTxPower.
This could cause the inconsistency between the new MOM and deprecated
MOM parameters in the database, and present a risk that
configuredMaxTxPower will change during the next upgrade from L16B IP1
(or earlier SW).
The following check can be performed prior to upgrade to make sure that
attributes are synchronized:
Make sure ‘partOfSectorPower’ is not shown as ‘0’, and
(partOfSectorPower*configuredOutputPower/100) = configuredMaxTxPower
Note: values of left and right parts of the equation might be slightly different,
up to about 1%.
If this formula is not fulfilled, please explicitly set both the
configuredOutputPower and partOfSectorPower to reflect the value for
configuredMaxTxPower.
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
Even if the formula is fulfilled, explicitly set configuredOutputPower to the
value it already has.
The deprecated parameters can be accessed via AMOS/moshell. The
following flag must be set when starting AMOS/moshell so that all the
deprecated attributes can be visible:
AMOS/moshell -v exclude_deprecated=0 <ip-address>
LRAT Cells that belong to the same Sector should be locked before any power
related changes. That is - add/remove SectorCarriers for the Sector, change of
power for related SectorCarriers. Otherwise, the synchronization between old
and new parameters will fail.
HWAC for LTE eNodeB
The eNodeB requires HWAC for channel bandwith, the number of connected
users, Baseband capacity for UL and DL, output power and the number of
physical resource blocks in UL and DL.
For LTE, the RBS6000 does not use a fingerprint, but a unique nodeId which
is defined at site integration.
The following HWAC keys are applicable for RBS6000:
This study source was downloaded by 100000845204320 from CourseHero.com on 12-14-2022 06:21:19 GMT -06:00
https://www.coursehero.com/documents/52015241/Insufficient-RF-power-issues-and-solutionsdocx/
Powered by TCPDF (www.tcpdf.org)
Download