0% found this document useful (0 votes)
71 views

Title:: Utrancell - Nbapreconfigurationfailure On Cells in Ericsson Hrernc02 and Hrernc03 After W12 To W13 Software Upgrade

After upgrading NodeBs from W12 to W13 software, 55 cells across two RNCs began showing NBAP reconfiguration failure alarms and experiencing downlink power degradation. The cause was a mismatch between the maximum downlink power configured in the RNC versus the actual maximum supported by the NodeBs. Updating the RNC configuration to match the NodeB capability resolved the issues.

Uploaded by

Godwin Magaba
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views

Title:: Utrancell - Nbapreconfigurationfailure On Cells in Ericsson Hrernc02 and Hrernc03 After W12 To W13 Software Upgrade

After upgrading NodeBs from W12 to W13 software, 55 cells across two RNCs began showing NBAP reconfiguration failure alarms and experiencing downlink power degradation. The cause was a mismatch between the maximum downlink power configured in the RNC versus the actual maximum supported by the NodeBs. Updating the RNC configuration to match the NodeB capability resolved the issues.

Uploaded by

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

NBAP RECONFIGURATION FAILURE ALARM ON CELLS ON W13 SOFTWARE

TITLE: UTRANCELL_NBAPRECONFIGURATIONFAILURE ON CELLS


IN ERICSSON HRERNC02 AND HRERNC03 AFTER W12 TO W13
SOFTWARE UPGRADE

INCIDENT DATE: 25/09/2014

TT REFERENCE: EWZNAT2014100800000482 (2140)

PROBLEM DESCRIPTION:

The Node Bs were upgraded from W12 to W13 through the normal RNC upgrades via OSS. The
upgrades completed successfully for the NodeBs. However a total of 25 cells in HRERNC03 and a
total of 30cells in HRERNC02 started showing alarm UtranCell_NbapReconfigurationFailure. This
problem cause interference because cells are trying to push more power from the RNC compared to
what Node B is capable of.

PROBLEM SYMPTOMS

i.   UtranCell_NbapReconfigurationFailure performance_degraded 
ii. DlPower degradation alarms observed

Date & Time (Local) S Specific Problem                    MO (Cause/AdditionalInfo)

2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUF


ECONET CANS

(nbapCause: DlPowerDegradation)

2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUE


(nbapCause: DlPowerDegradation)

2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUD


(nbapCause: DlPowerDegradation)

2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUA


(nbapCause: DlPowerDegradation)
2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUB
(nbapCause: DlPowerDegradation)

2014-09-2603:38:26 AL w UtranCell_NbapReconfigurationFailure UtranCell=0290MUC


(nbapCause: DlPowerDegradation)

REMEDY CONDITIONS:

1. MaxDlPowerCapability, primaryCpichPower & maximumTransmissionPower are within acceptable


range

2. Utrancells are operational

3. Alarm present on all 3 sectors

4. JVM restart does not solve the problem

SOLUTION(S)

1. Check the power from RbsLocalCell: maxDlPowerCapability and note down this value which is
the maximum downlink power capability of the NodeB. This is a read only value and its
hardcoded in the RBS. For a cell using more than one carrier, this value is the maximum DL
power capability among the carriers
2. Correct the value of maximumTransmissionPower for the cells in RNC which was set to 480.
Change this value to be equal to maxDlPowerCapability

When the above remedy was carried out all alarms were cleared

CAUSE

- Configuration mismatch between maximumTransmissionPower of cells in RNC and the


maximum downlink power (maxDlPowerCapability) allowed by Node B caused this problem.
- RNC will internally set a reference value representing the previously configured
maximumTransmissionPower in the cell. An alarm is issued if the RBS reports a degradation of
its maxPowerCapDl below 2dB.
RECOMMENDATION

An audit of maximumTransmissionPower in RNC and maxDlPowerCapability in Node B should be done to


ensure that the two values are the same.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy