Resource Allocation Failure

Operating Instructions

89/1543-LZA 701 6014/1 Uen AS

Copyright

© Ericsson AB 2016-2018. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Contents

Contents

1 Select Remedy Actions for Resource Allocation Failure 1

2 Remedy Actions for <Cell MO>: Baseband interconnect

resource shortage 12

3 Remedy Actions for <Cell MO>: CPRI resource shortage <X> 13

3.1 Replace SFP 13
3.2 Remove Cell 13

4 Remedy Actions for <Cell MO>: Insufficient 5+5 MHz Sector

Carrier licenses 14

5 Remedy Actions for <Cell MO>: Failed to allocate path 15

5.1 Remedy Actions for Configured CPRI Capacity Exceeds Max
Value in CPRI Limitations 15
5.2 Remedy Actions for Link Failure for Multi-Link Configurations 16
5.3 Remedy Actions for LTE System and WCDMA System Out of
Sync 16

6 Remedy Actions for <Cell MO>: Maximum Cellrange feature is

not activated and cellRange is not set to default value 17

7 Remedy Actions for <Cell MO>: No common sampling rate

between baseband and radio 18

8 Remedy Actions for <Cell MO>: Not enough HW resources are

available to create the cell with reason <fault code> 19

9 Remedy Actions for <Cell MO>: Performance mode mismatch:

Supported=<s>, Requested=<s> 20

10 Remedy Actions for <Sector Carrier MO> or <Cell MO> or <Trx

MO>: Unable to allocate baseband HW resources due to
insufficient baseband HWAC for this RAT 21

11 Remedy Actions for <Sector Carrier> or <Cell MO> or <Trx

MO>: Unable to allocate Baseband HW resources for this MO 22

12 Remedy Actions for <Cell MO> or <Trx MO>: Unable to allocate

baseband HW resources for this RAT 23

13 Remedy Actions for <Cell MO>: Unsupported combination of

radio units within the sector 24

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

Resource Allocation Failure

14 Remedy Actions for <Sector Carrier MO> or <Cell Carrier MO>

or <Trx MO>: No RF power Hardware Activation Code
available 25

15 Remedy Actions for EUtranCellFDD or EUtranCellTDD: No

available carrier path, adjacent filter branches not available 26

16 Remedy Actions for EUtranCellFDD or EUtranCellTDD: <n> Dl

carriers invalid Request 27

17 Remedy Actions for EUtranCellFDD or EUtranCellTDD: <n> Ul

carriers invalid request 28

18 Remedy Actions for EUtranCellFDD or EUtranCellTDD: Lbt

allocation failed 29

19 Remedy Actions for EUtranCellFDD or EUtranCellTDD:

sectorCarrier has intersection between <cellId1> and <cellId2> 30

20 Remedy Actions for EUtranCellFDD or EUtranCellTDD: The

number of requested Rx carriers is not the same for all sectors. 31

21 Remedy Actions for EUtranCellFDD or EUtranCellTDD: The

number of requested Tx carriers is not the same for all sectors. 32

22 Remedy Actions for EUtranCellFDD, EUtranCellTDD or

NbIotCell: Invalid earfcn 33

23 Remedy Actions for EUtranCellFDD: Parameter

carrierFrequency is out of range 34

24 Remedy Actions for EUtranCellFDD: Incorrect master/clone

setup 35

25 Remedy Actions for EUtranCellFDD: Invalid isDlOnly and

noOfRxAntennas 36

26 Remedy Actions for EUtranCellFDD: Capacity license for

number of unlocked IOT cells exceeded 37

27 Remedy Actions for EUtranCellFDD: Requested

PHASE_COMP_OFF but the radio does not support it. Turning
off the phase compensation on radio is not possible. Does not
supported by Radio, or protocol mismatch between DU and
Radio. 38

28 Remedy Actions for EUtranCellFDD or EUtranCellTDD: Turning

off the phase compensation on radio is not possible. Does not
supported by Radio, or protocol mismatch between DU and
Radio. 39

29 Remedy Actions for EUtranCellTDD: Parameter

carrierFrequency is out of range 40

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Contents

30 Remedy Actions for EUtranCellTDD: Requested number of Rx

or Tx antennas are not allowed with Octal Antenna feature 41

31 Remedy Actions for EUtranCellTDD: The Requested

axcSlotSize Must Be the Same Value for all CPRI Links in DL
and UL 42

32 Remedy Action for NRSectorCarrier: Baseband SW

incompatible with radio unit in the sector 43

33 Remedy Actions for MbmsService: GBR admission failed 44

34 Remedy Actions for MbmsService: Transport tunnel allocation

fault 45

35 Remedy Actions for MbmsService: Subframe allocation failed 46

36 Remedy Actions for NbIotCell: Capacity license for number of

unlocked IOT cells exceeded 47

37 Remedy Actions for NbIotCell: NB-IOT cell resources not

allocated by hosting EUtran cell 48

38 Remedy Actions for NodeBLocalCell: Unable to allocate radio

HW resources due to both insufficient HWAC and capacity
license for number of Cell Carriers 49

39 Remedy Actions for NodeBLocalCell: Unable to allocate radio

HW resources due to insufficient capacity license WCDMA Cell
Carriers for this MO 50

40 Remedy Actions for NodeBLocalCell: Unable to allocate radio

HW resources due to insufficient WCDMA Number of Cell
Carriers HWAC for this MO 51

41 Remedy Action for PimCancellationFunction MO 52

42 Remedy Actions for <Sector Carrier MO> or <Trx MO>: No RF

power available in radio equipment 53

43 Remedy Actions for <Trx MO>: AvailabilityStatus = FAILED 54

44 Remedy Actions for <Trx MO>: Unable to allocate radio HW

resources due to insufficient HWAC GSM Cell Carrier (TRX)
ERS for this MO 55

45 Remedy Actions for Trx: Not enough baseband resources are

available to setup the TRX 56

46 Remedy Actions for Trx with ExtTrx: Not enough baseband

resources are available to setup the TRX 57

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

Resource Allocation Failure

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

1 Select Remedy Actions for Resource

Allocation Failure

The additional text Mixed Mode Radio with external ME indicates that the
RD is shared with an external ME and possible conflict with another RAN needs
to be considered.

Table 1 Select Remedy Actions

Managed Object Additional Text Link to Remedy Actions
EUtranCellFDD <n> Dl carriers Remedy Actions for
invalid request EUtranCellFDD or
EUtranCellTDD: <n> Dl
carriers invalid Request
on page 27
EUtranCellFDD Baseband Remedy actions
interconnect
resource shortage
EUtranCellFDD Capacity license for Remedy actions
number of unlocked
IOT cells exceeded
EUtranCellFDD CPRI resource Remedy actions
shortage <X>
EUtranCellFDD Combine cell Invalid Remedy Actions for
isDlOnly and EUtranCellFDD: Invalid
noOfRequestedRx isDlOnly and
noOfRxAntennas on
page 36
EUtranCellFDD Failed to allocate Remedy actions
path
EUtranCellFDD Incorrect master/ Remedy actions
clone setup
EUtranCellFDD <Insufficient 5+5 Remedy actions
MHz Sector Carrier
licenses
EUtranCellFDD Invalid earfcn Remedy Actions for
EUtranCellFDD,
EUtranCellTDD or
NbIotCell: Invalid earfcn
on page 33

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 1

 Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

EUtranCellFDD Invalid isDlOnly and Remedy Actions for
noOfRxAntennas EUtranCellFDD: Invalid
isDlOnly and
noOfRxAntennas on
page 36
EUtranCellFDD Lbt allocation Remedy Actions for
failure EUtranCellFDD or
EUtranCellTDD: Lbt
allocation failed on page
29
EUtranCellFDD Maximum Cellrange Remedy actions
feature is not
activated and
cellRange is not set
to default value
EUtranCellFDD <n> Ul carriers Remedy Actions for
invalid request EUtranCellFDD or
EUtranCellTDD: <n> Ul
carriers invalid request
on page 28
EUtranCellFDD No available carrier Remedy actions
path, adjacent
filter branches not
available
EUtranCellFDD No common sampling Remedy actions
rate between
baseband and radio
EUtranCellFDD Not enough HW Remedy actions
resources are
available to create
the cell with reason
<fault code>
EUtranCellFDD Parameter Remedy actions
carrierFrequency is
out of range
EUtranCellFDD Performance mode Remedy actions
mismatch:
Supported=<s>,
Requested=<s>

2 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

EUtranCellFDD PSIcell Invalid Remedy Actions for
isDlOnly and EUtranCellFDD: Invalid
noOfRequestedRx isDlOnly and
noOfRxAntennas on
page 36
EUtranCellFDD Turning off the Remedy Actions for
phase compensation EUtranCellFDD or
on radio is not EUtranCellTDD: Turning
possible. Does not off the phase
supported by Radio, compensation on radio is
or protocol mismatch not possible. Does not
between DU and supported by Radio, or
Radio. protocol mismatch
between DU and Radio.
on page 39
EUtranCellFDD Unable to allocate Remedy actions
baseband HW
resources due to
insufficient
baseband HWAC for
this RAT
EUtranCellFDD Unable to allocate Remedy actions
baseband HW
resources for this
MO
EUtranCellFDD Unable to allocate Remedy actions
baseband HW
resources for this
RAT
EUtranCellFDD Unsupported Remedy actions
combination of radio
units within the
sector
EUtranCellFDD sectorCarrier has Remedy Actions for
intersection between EUtranCellFDD or
<cellId1> and EUtranCellTDD:
<cellId2> sectorCarrier has
intersection between
<cellId1> and <cellId2>
on page 30
EUtranCellFDD The number of Remedy Actions for
requested Rx EUtranCellFDD or
EUtranCellTDD: The

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 3

 Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

carriers is not the number of requested Rx
same for all sectors carriers is not the same
for all sectors. on page
31
EUtranCellFDD The number of Remedy Actions for
requested Tx EUtranCellFDD or
carriers is not the EUtranCellTDD: The
same for all sectors number of requested Tx
carriers is not the same
for all sectors. on page
32
EUtranCellTDD Baseband Remedy actions
interconnect
resource shortage
EUtranCellTDD CPRI resource Remedy actions
shortage <X>
EUtranCellTDD Failed to allocate Remedy actions
path
EUtranCellTDD Insufficient 5+5 MHz Remedy actions
Sector Carrier
licenses
EUtranCellTDD Invalid earfcn Remedy Actions for
EUtranCellFDD,
EUtranCellTDD or
NbIotCell: Invalid earfcn
on page 33
EUtranCellTDD Lbt allocation Remedy Actions for
failure EUtranCellFDD or
EUtranCellTDD: Lbt
allocation failed on page
29
EUtranCellTDD Maximum Cellrange Remedy actions
feature is not
activated and
cellRange is not set
to default value
EUtranCellTDD <n> Ul carriers Remedy Actions for
invalid request EUtranCellFDD or
EUtranCellTDD: <n> Ul
carriers invalid request
on page 28

4 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

EUtranCellTDD <n> Dl carriers Remedy Actions for
invalid request EUtranCellFDD or
EUtranCellTDD: <n> Dl
carriers invalid Request
on page 27
EUtranCellTDD No available carrier Remedy actions
path, adjacent
filter branches not
available
EUtranCellTDD No common sampling Remedy actions
rate between
baseband and radio
EUtranCellTDD Not enough HW Remedy actions
resources are
available to create
the cell with reason
<fault code>
EUtranCellTDD Parameter Remedy actions
carrierFrequency is
out of range
EUtranCellTDD Performance mode Remedy actions
mismatch:
Supported=<s>,
Requested=<s>
EUtranCellTDD Turning off the Remedy Actions for
phase compensation EUtranCellFDD or
on radio is not EUtranCellTDD: Turning
possible. Does not off the phase
supported by Radio, compensation on radio is
or protocol mismatch not possible. Does not
between DU and supported by Radio, or
Radio. protocol mismatch
between DU and Radio.
on page 39
EUtranCellTDD Requested number of Remedy actions
Rx or Tx antennas
are not allowed with
Octal Antenna
feature
EUtranCellTDD The requested Remedy actions
axcSlotSize must be
the same value for

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 5

 Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

all CPRI links in DL
and UL
EUtranCellTDD Unable to allocate Remedy actions
baseband HW
resources due to
insufficient
baseband HWAC for
this RAT
EUtranCellTDD Unable to allocate Remedy actions
baseband HW
resources for this
MO
EUtranCellTDD Unable to allocate Remedy actions
baseband HW
resources for this
RAT
EUtranCellTDD Unsupported Remedy actions
combination of radio
units within the
sector
EUtranCellTDD sectorCarrier has Remedy Actions for
intersection between EUtranCellFDD or
<cellId1> and EUtranCellTDD:
<cellId2> sectorCarrier has
intersection between
<cellId1> and <cellId2>
on page 30
EUtranCellTDD The number of Remedy Actions for
requested Rx EUtranCellFDD or
carriers is not the EUtranCellTDD: The
same for all sectors number of requested Rx
carriers is not the same
for all sectors. on page
31
EUtranCellTDD The number of Remedy Actions for
requested Tx EUtranCellFDD or
carriers is not the EUtranCellTDD: The
same for all sectors number of requested Tx
carriers is not the same
for all sectors. on page
32

6 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

ExtTrx Not enough baseband Remedy actions
resources are
available to setup
the TRX
ExtTrx No RF power available in Remedy actions
radio equipment
ExtTrx No RF power Hardware Remedy actions
Activation Code
available
ExtTrx Unable to allocate Remedy actions
baseband HW resources
due to insufficient
baseband HWAC for this
RAT
ExtTrx Unable to allocate Remedy actions
baseband HW resources
for this MO
ExtTrx Unable to allocate Remedy actions
baseband HW resources
for this RAT
ExtTrx Unable to allocate radio Remedy actions
HW resources due to
insufficient HWAC GSM
Cell Carrier (TRX) ERS
for this MO
NRSectorCarrier Baseband SW Remedy actions
incompatible with
radio unit in the
sector
NRSectorCarrier No RF power Remedy actions
available in radio
equipment
NRSectorCarrier No RF power Hardware Remedy actions
Activation Code
available
NRSectorCarrier Unable to allocate Remedy actions
baseband HW
resources for this
MO
NRSectorCarrier Unable to allocate Remedy actions
baseband HW
resources due to
insufficient

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 7

 Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

baseband HWAC for
this RAT
MbmsService GBR admission failed Remedy actions
MbmsService Subframe allocation Remedy Actions for
failure MbmsService: Subframe
allocation failed on page
46
MbmsService Transport tunnel Remedy actions
allocation fault
NbIotCell Baseband Remedy actions
interconnect
resource shortage
NbIotCell Capacity license for Remedy actions
number of unlocked
IOT cells exceeded
NbIotCell Invalid earfcn Remedy Actions for
EUtranCellFDD,
EUtranCellTDD or
NbIotCell: Invalid earfcn
on page 33
NbIotCell NB-IOT cell Remedy actions
resources not
allocated by hosting
EUtran cell
NbIotCell No common sampling Remedy actions
rate between
baseband and radio
NbIotCell Not enough HW Remedy actions
resources are
available to create
the cell with reason
<fault code>
NbIotCell Performance mode Remedy actions
mismatch:
Supported=<s>,
Requested=<s>
NbIotCell Unable to allocate Remedy actions
baseband HW
resources for this
MO

8 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

NbIotCell Unable to allocate Remedy actions
baseband HW
resources for this
RAT
NbIotCell Unsupported Remedy actions
combination of radio
units within the
sector
NodeBLocalCell Baseband Remedy actions
interconnect
resource shortage
NodeBLocalCell CPRI resource Remedy actions
shortage <X>
NodeBLocalCell Not enough HW Remedy actions
resources are
available to create
the cell with reason
<fault code>
NodeBLocalCell Unable to allocate Remedy actions
baseband HW
resources due to
insufficient
baseband HWAC for
this RAT
NodeBLocalCell Unable to allocate Remedy actions
baseband HW
resources for this
MO
NodeBLocalCell Unable to allocate Remedy actions
baseband HW
resources for this
RAT
NodeBLocalCell Unable to allocate Remedy actions
radio HW resources
due to both
insufficient HWAC
and capacity license
for number of cell
carriers
NodeBLocalCell Unable to allocate Remedy actions
radio HW resources

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 9

 Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

due to insufficient
capacity license
WCDMA Cell Carriers
for this MO
NodeBLocalCell Unable to allocate Remedy actions
radio HW resources
due to insufficient
WCDMA Number of Cell
Carriers HWAC for
this MO
NodeBSectorCarrier No RF power Remedy actions
available in radio
equipment
NodeBSectorCarrier No RF power Hardware Remedy actions
Activation Code
available
PimCancellationFunct Addition of Remedy actions
ion cancellation group
failed due to
resource shortage
PimCancellationFunct Addition of DL Remedy actions
ion carriers failed due
to resource shortage
PimCancellationFunct Addition of UL Remedy actions
ion carriers failed due
to resource shortage
SectorCarrier No RF power Remedy actions
available in radio
equipment
SectorCarrier No RF power Hardware Remedy actions
Activation Code
available
Trx Not enough baseband Remedy actions
resources are
available to setup
the TRX
Trx No RF power Remedy actions
available in radio
equipment

10 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Select Remedy Actions for Resource Allocation Failure

Managed Object Additional Text Link to Remedy Actions

Trx No RF power Hardware Remedy actions
Activation Code
available
Trx Unable to allocate Remedy actions
baseband HW
resources due to
insufficient
baseband HWAC for
this RAT
Trx Unable to allocate Remedy actions
baseband HW
resources for this
MO
Trx Unable to allocate Remedy actions
baseband HW
resources for this
RAT
Trx Unable to allocate radio Remedy actions
HW resources due to
insufficient HWAC GSM
Cell Carrier (TRX) ERS
for this MO

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 11

 Resource Allocation Failure

2 Remedy Actions for <Cell MO>: Baseband

interconnect resource shortage

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIoTCell

— NodeBLocalCell

Steps

1. Check the status of all DUs and Baseband units. If there is at least one DU or
Baseband unit with operationalState set to DISABLED in the
corresponding PlugInUnit MO instance or the FieldReplaceableUnit MO
instance, resolve that first.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Reconfigure the SectorCarrier MO to use less TX branches and RX

branches.

5. Lock the cell.

6. Unlock the cell.

If the alarm remains, do the following:

7. Reduce the number of TX branches and RX branches in other

SectorCarrier MOs that are located on the same DU or Baseband unit as
the failing cell. The attribute hostingDigitalUnit shows on which DU or
Baseband unit each cell is located.
If the alarm remains, do the following:

8. Consult the next level of maintenance support.

12 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Cell MO>: CPRI resource shortage <X>

3 Remedy Actions for <Cell MO>: CPRI

resource shortage <X>

1. If the radio, DU or Baseband unit has higher bandwidth capacity than the
value indicated in the additional text, use the following remedy actions.

2. If the radio, DU or Baseband unit has the same or lower bandwidth capacity
than the value indicated in the additional text, use the following remedy
actions.

3.1 Replace SFP

Steps

1. Lock the cell.

2. Replace the SFP or SFPs on the optical cable.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

3.2 Remove Cell

Steps

1. Lock the cell.

2. Remove the cell.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 13

 Resource Allocation Failure

4 Remedy Actions for <Cell MO>: Insufficient

5+5 MHz Sector Carrier licenses

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

Steps

1. Choose one of the following actions:

— Enable a sufficient level of the capacity license for 5+5 MHz Sector
Carrier to meet the current configuration requirement.

— Reconfigure the existing cells with decreased channel bandwidth or

fewer sector carriers, so that the currently enabled level of the capacity
license is sufficient.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

14 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Cell MO>: Failed to allocate path

5 Remedy Actions for <Cell MO>: Failed to

allocate path

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

Steps

Configured CPRI capacity exceeds max value in CPRI limitations

1. If the configured CPRI capacity exceeds max value in CPRI limitations, use
the following remedy actions.
For more information, see CPRI Capacity.
Link failure for multi-link configurations

2. Check the operationalState attribute and the presence of Link Failure

alarms on the RiLink MO used by the cell.
LTE system and CDMA system out of sync

3. If the LTE system (DU) and CDMA system (XMU) are out of sync for XMU02
LTE and CDMA mixed mode configuration, use the following remedy actions.

5.1 Remedy Actions for Configured CPRI Capacity Exceeds

Max Value in CPRI Limitations
1. Lock the cell.

2. Adjust the number of cells, number of antennas, or carrier bandwidth.

3. Check if feature CPRI Compression resolves the problem.

For more information, see CPRI Compression.

4. Check if feature CPRI Compression with Baseband R resolves the problem.

For more information, see CPRI Compression with Baseband R.

5. Unlock the cell.

If the alarm remains, do the following:

6. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 15

 Resource Allocation Failure

5.2 Remedy Actions for Link Failure for Multi-Link

Configurations
1. Lock the cell.

2. Replace the faulty link.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

5.3 Remedy Actions for LTE System and WCDMA System

Out of Sync
1. Lock the cell.

2. Unlock the cell.

If the alarm remains, do the following:

3. Restart the XMU 02.

If the alarm remains, do the following:

4. Restart the node.

If the alarm remains, do the following:

5. Consult the next level of maintenance support.

16 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Cell MO>: Maximum Cellrange feature is not activated and cellRange is not set to default value

6 Remedy Actions for <Cell MO>: Maximum

Cellrange feature is not activated and
cellRange is not set to default value

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

Steps

1. Lock the cell.

2. Check that the necessary Maximum Cell Range license is available for the
requested configuration. If not, activate the license for Maximum Cell Range,
or change the value of the attribute cellRange in the applicable
EUtranCellFDD or EUtranCellTDD instance.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 17

 Resource Allocation Failure

7 Remedy Actions for <Cell MO>: No common

sampling rate between baseband and radio

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIotCell

Steps

1. Lock the cell.

2. Unlock the cell.

If the alarm remains, do the following:

3. Restart each radio unit that is used for the cell.

If the alarm remains, do the following:

4. Restart the DU or Baseband unit that is used for the cell.

If the alarm remains, do the following for further troubleshooting:

5. Enable the cell with less capacity.

a. Lock one of the radio units used for the cell.

b. Lock the cell.
c. Unlock the cell.
d. Repeat Step 5.a to Step 5.c until the cell becomes enabled or until
each radio unit has been tried.

Result: If the cell has become enabled, availabilityStatus is set to

DEGRADED in the corresponding cell MO instance. This indicates that the
cell uses less TX branches, RX branches, or both, compared to the
configuration in the applicable SectorCarrier MO.
If the alarm remains, do the following:

6. Unlock all radio units.

7. Consult the next level of maintenance support.

18 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Cell MO>: Not enough HW resources are available to create the cell with reason <fault code>

8 Remedy Actions for <Cell MO>: Not enough

HW resources are available to create the cell
with reason <fault code>

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIoTCell

— NodeBLocalCell

Steps

1. Lock the cell.

2. Check that a sufficient level of hardware related capacity is available for the
requested configuration. If not, enable a higher level of capacity.

3. Unlock the cell.

If the alarm remains, do the following:

4. Configure the cell parameters to use less hardware resources or install more
hardware.
If the alarm remains, do the following:

5. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 19

 Resource Allocation Failure

9 Remedy Actions for <Cell MO>: Performance

mode mismatch: Supported=<s>,
Requested=<s>

The Resource Allocation Failure alarm is raised with the additional text
Performance mode mismatch: Supported=<s>, Requested=<s> when the
required performance mode is not supported by the used radio.

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIotCell

Steps

1. Check the radioTransmitPerformanceMode attribute under the

SectorCarrier MO in all sector carriers that are connected to the cell to find
the one with mismatched configuration.

2. Lock the cell.

3. Perform one of the following steps:

— To stay on a mode that is supported by the existing radio, set the
performance mode as DEFAULT on attribute
radioTransmitPerformanceMode under the SectorCarrier MO.

— To switch to the requested mode, replace the radio with one that
supports the requested performance mode according to the instructions
for the appropriate radio.

For more information about performance modes and which radio types do
not support 256-QAM, see 256-QAM Downlink.

4. Unlock the cell.

If the alarm remains, do the following:

5. Consult the next level of maintenance support.

20 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Sector Carrier MO> or <Cell MO> or <Trx MO>: Unable to allocate baseband HW resources due to
insufficient baseband HWAC for this RAT

10 Remedy Actions for <Sector Carrier MO> or

<Cell MO> or <Trx MO>: Unable to allocate
baseband HW resources due to insufficient
baseband HWAC for this RAT

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NRSectorCarrier

— NbIotCell

— NodeBLocalCell

— Trx

— Trx with ExtTrx

Note: The ExtTrx is only used for the GSM feature Combined Cell. The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO should be locked/unlocked. For more Combined Cell
information, see Manage Radio Network GSM and GSM RAN User
Description, Combined Cell.

Steps

1. Lock the cells or TRXs of the affected RAT.

2. Verify that the hardware supports the number of RATs.

3. Enable a sufficient level of the HWAC for the hardware related capacity.

4. Unlock the previously locked cells or TRXs.

If the alarm remains, do the following:

5. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

6. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 21

 Resource Allocation Failure

11 Remedy Actions for <Sector Carrier> or <Cell

MO> or <Trx MO>: Unable to allocate
Baseband HW resources for this MO

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NRSectorCarrier

— NodeBLocalCell

— Trx

— Trx with ExtTrx

Note: The ExtTrx is only used for the GSM feature Combined Cell. The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO should be locked/unlocked. For more Combined Cell
information, see Manage Radio Network GSM and GSM RAN User
Description, Combined Cell.

Steps

1. Delete excessive cells or TRXs or extension TRXs.

If the alarm remains, do the following:

2. Delete the cell, TRX or extension TRX and set it up again with the same
attributes.
If the alarm remains, do the following:

3. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

22 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Cell MO> or <Trx MO>: Unable to allocate baseband HW resources for this RAT

12 Remedy Actions for <Cell MO> or <Trx MO>:

Unable to allocate baseband HW resources
for this RAT

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIotCell

— NodeBLocalCell

— Trx

— Trx with ExtTrx

Note: The ExtTrx is only used for the GSM feature Combined Cell. The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO should be locked/unlocked. For more Combined Cell
information, see Manage Radio Network GSM and GSM RAN User
Description, Combined Cell.

Steps

1. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

2. Remove one of the RATs from the configuration by deleting all of its cells or
TRXs.
For more information, see Manage Mixed Mode Managed Element.
If the alarm remains, do the following:

3. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 23

 Resource Allocation Failure

13 Remedy Actions for <Cell MO>: Unsupported

combination of radio units within the sector

This procedure is valid for the following MOs:

— EUtranCellFDD

— EUtranCellTDD

— NbIotCell

Steps

1. Check if the radio units used in the sector are compatible.

For further information, see RBS Configurations.

2. If the radio units are not compatible, replace one of the radio units with a
unit of a compatible type.
Until the radio unit is replaced, do the following:

3. Enable the cell with less capacity.

a. Lock the radio unit to be replaced.

b. Lock the cell.
c. Unlock the cell.

Result: The cell becomes enabled with availabilityStatus set to

DEGRADED in the corresponding cell MO instance. This indicates that the
cell uses less TX branches, RX branches, or both, compared to the
configuration in the applicable SectorCarrier MO.
If the alarm remains, do the following:

4. Consult the next level of maintenance support.

24 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Sector Carrier MO> or <Cell Carrier MO> or <Trx MO>: No RF power Hardware Activation Code
available

14 Remedy Actions for <Sector Carrier MO> or

<Cell Carrier MO> or <Trx MO>: No RF power
Hardware Activation Code available

This procedure is valid for the following MOs:

— ExtTrx

— NRSectorCarrier

— NodeBSectorCarrier

— SectorCarrier

— Trx

Note: The ExtTrx is only used for the GSM feature Combined Cell. The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO should be locked/unlocked. For more Combined Cell
information, see Manage Radio Network GSM and GSM RAN User
Description, Combined Cell.

Steps

1. Lock all cells or TRXs used by the radio.

2. Enable a sufficient level of the HWAC for the hardware related capacity RF
Power or reconfigure the affected cells, TRXs or extension TRXs to a power
level for which the currently enabled level of the HWAC is sufficient. Also
consider the power configuration of other cells or TRXs using the same radio
in a mixed-mode configuration.

3. Unlock the previously locked cells or TRXs.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 25

 Resource Allocation Failure

15 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: No available carrier path,
adjacent filter branches not available

1. Lock every cell used by the radio.

2. Unlock every cell that has been previously locked.

If the alarm remains, do the following:

3. Restart the radio unit.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

26 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD or EUtranCellTDD: <n> Dl carriers invalid Request

16 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: <n> Dl carriers invalid
Request

The alarm is raised due to a faulty configuration that depends on installed

licenses, activated features and configured hardware.

Steps

1. Lock the cell.

2. Change the value of the SectorCarrier.noOfRxAntennas attribute.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 27

 Resource Allocation Failure

17 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: <n> Ul carriers invalid
request

The alarm is raised due to a faulty configuration that depends on installed

licenses, activated features and configured hardware.

Steps

1. Lock the cell.

2. Change the value of the SectorCarrier.noOfTxAntennas attribute.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

28 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD or EUtranCellTDD: Lbt allocation failed

18 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: Lbt allocation failed

The alarm is raised when there is inconsistency between the configuration of LAA
cell and the capability of hardware resources allocated to it.

Steps

1. Lock the cell.

2. Check if the attributes of the LAA cell and interaction with other features are
consistent.

3. Correct inconsistencies if any.

4. Unlock the cell.

If the alarm remains, do the following:

5. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 29

 Resource Allocation Failure

19 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: sectorCarrier has
intersection between <cellId1> and <cellId2>

The alarm is raised when the sectorCarrierRef is referenced to other cells as a

combined cell.

Steps

1. Lock the cell.

2. Check if there are any conflicting sectorCarrierRef attributes.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

30 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD or EUtranCellTDD: The number of requested Rx carriers is not the same for all sectors.

20 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: The number of requested Rx
carriers is not the same for all sectors.

The alarm is raised when the SectorCarrier.noOfRxAntennas attributes

referenced by one combined cell are different.

Steps

1. Lock the cell.

2. Set the SectorCarrier.noOfRxAntennas attributes referenced by one

combined cell to the same value.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 31

 Resource Allocation Failure

21 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: The number of requested Tx
carriers is not the same for all sectors.

The alarm is raised when the SectorCarrier.noOfTxAntennas attributes

referenced by one combined cell are different.

Steps

1. Lock the cell.

2. Set the SectorCarrier.noOfTxAntennas attributes referenced by one

combined cell to the same value.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

32 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD, EUtranCellTDD or NbIotCell: Invalid earfcn

22 Remedy Actions for EUtranCellFDD,

EUtranCellTDD or NbIotCell: Invalid earfcn

The alarm is raised when the cell is configured with an earfcn that is not
supported by the radio.

Steps

1. Lock the cell.

2. Change the earfcn attribute to the right value.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 33

 Resource Allocation Failure

23 Remedy Actions for EUtranCellFDD:

Parameter carrierFrequency is out of range

1. Change the frequency to a valid earfcndl value using the action

changeFrequency(<earfcn>).

2. Update the uplink frequency by changing the attribute earfcnul.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

34 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD: Incorrect master/clone setup

24 Remedy Actions for EUtranCellFDD:

Incorrect master/clone setup

1. Lock the cell.

2. Correct the RfBranchId attributes that define the relationship between the
master and the clone branches.
For more information, see Transmit Data Cloning.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 35

 Resource Allocation Failure

25 Remedy Actions for EUtranCellFDD: Invalid

isDlOnly and noOfRxAntennas

The alarm is raised if the EUtranCellFDD.isDlOnly attribute is true, and the

EUtranCellFDD.noOfRxAntennas attribute is greater than 0.

Steps

1. Lock the cell.

Option Description
If the requested Reset the carrier attribute
configuration is DL only EUtranCellFDD.noOfRxAntennas to 0.
If the requested Reset the cell attribute
configuration is not DL EUtranCellFDD.isDlOnly to false.
only

2. Unlock the cell.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

36 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD: Capacity license for number of unlocked IOT cells exceeded

26 Remedy Actions for EUtranCellFDD: Capacity

license for number of unlocked IOT cells
exceeded

Note: The alarm can be raised on both legacy LTE cells with Cat-M1 support
enabled and all NB-IoT cells.

Steps

1. Install a sufficient number of IoT Carrier licenses to meet the current Cat-M
configuration requirements. One for each EUtranCellFDD MO with Cat-M1
support enabled.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 37

 Resource Allocation Failure

27 Remedy Actions for EUtranCellFDD:

Requested PHASE_COMP_OFF but the radio
does not support it. Turning off the phase
compensation on radio is not possible. Does
not supported by Radio, or protocol
mismatch between DU and Radio.

1. Check if the URI and the password added to the UpgradePackage and SwM
MOs are correct.

2. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

38 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellFDD or EUtranCellTDD: Turning off the phase compensation on radio is not possible. Does
not supported by Radio, or protocol mismatch between DU and Radio.

28 Remedy Actions for EUtranCellFDD or

EUtranCellTDD: Turning off the phase
compensation on radio is not possible. Does
not supported by Radio, or protocol
mismatch between DU and Radio.

1. Check if the URI and the password added to the UpgradePackage and SwM
MOs are correct.

2. Restart the faulty unit with restartRank RESTART_WARM.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 39

 Resource Allocation Failure

29 Remedy Actions for EUtranCellTDD:

Parameter carrierFrequency is out of range

1. Change the frequency to a valid earfcn value using the action

changeFrequency(<earfcn>).
If the alarm remains, do the following:

2. Consult the next level of maintenance support.

40 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for EUtranCellTDD: Requested number of Rx or Tx antennas are not allowed with Octal Antenna feature

30 Remedy Actions for EUtranCellTDD:

Requested number of Rx or Tx antennas are
not allowed with Octal Antenna feature

1. Lock the cell.

2. Set the value of the attribute noOfRxAntennas to 8.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 41

 Resource Allocation Failure

31 Remedy Actions for EUtranCellTDD: The

Requested axcSlotSize Must Be the Same
Value for all CPRI Links in DL and UL

Steps

1. Restart the radio unit.

If the alarm remains, do the following:

2. Consult the next level of maintenance support.

42 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Action for NRSectorCarrier: Baseband SW incompatible with radio unit in the sector

32 Remedy Action for NRSectorCarrier:

Baseband SW incompatible with radio unit in
the sector

This alarm is raised when the radio unit is not supported by the NR node
software.

Steps

1. Check that the NRSectorCarrier.sectorEquipmentFunction attribute

refers to the correct instance of SectorEquipmentFunction MO.

2. If not, set the NRSectorCarrier.administrativeState attribute to

LOCKED.

3. Change the configuration that the

NRSectorCarrier.sectorEquipmentFunction refers to the correct instance
of SectorEquipmentFunction MO.

4. Set the NRSectorCarrier.administrativeState attribute to UNLOCKED.

If the alarm remains, do the following:

5. Restart the NR Node.

If the alarm remains, do the following:

6. Check that the radio unit is supported by the NR Node software for the
intended configuration.
If the alarm remains, do the following:

7. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 43

 Resource Allocation Failure

33 Remedy Actions for MbmsService: GBR

admission failed

This procedure is valid for DU radio nodes only.

Steps

1. Check that the sum of the MBMS E-RAB Guaranteed Bit Rate Downlink for
activated MBMS Services does not exceed the value of
AdmissionControl.dlMbmsGbrRatio.

MBMS E-RAB Guaranteed Bit Rate Downlink is configured in the Broadcast

Management Center in the core network for each MBMS Service and is
received by the eNodeB in the M3 Mbms Session Start Request messages.

44 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for MbmsService: Transport tunnel allocation fault

34 Remedy Actions for MbmsService: Transport

tunnel allocation fault

For DU radio nodes, do the following:

— Check that there is a correctly configured MulticastListener MO.

— Check that no more than 15 different multicast groups have been activated.

For Baseband radio nodes, do the following:

— Check that no more than 30 different multicast groups have been activated.

— Check that Mbms.m1IpInterfaceRef is correctly configured, and that the

referenced interface is not a loopback interface or an interface that has an
encapsulation reference to an IpSecTunnel instance.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 45

 Resource Allocation Failure

35 Remedy Actions for MbmsService: Subframe

allocation failed

The alarm is raised when there are not enough MBMS resources, and the lowest
priority resources are not broadcast.

The number of sub-frames needed for the transmission is calculated based on the
GBR parameter. The priority of the service is determined first by its ARP Priority
Level, then by its Service ID.

Steps

1. Check if the parameters are properly defined. If not, do the following:

— Stop the service.

— Change the incorrect parameter.

— Restart the service.

2. Check if the sub-frame configuration for the related MbsfnArena is correct. If

not, do the following:
— Lock the related MbsfnArea.

— Correct the MbsfnArea.commonSFAllocList.

— Unlock the related MbsfnArea.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

46 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for NbIotCell: Capacity license for number of unlocked IOT cells exceeded

36 Remedy Actions for NbIotCell: Capacity

license for number of unlocked IOT cells
exceeded

Note: The alarm can be raised on both legacy LTE cells with Cat-M1 support
enabled and all NB-IoT cells.

Steps

1. Install a sufficient number of IoT Carrier licenses to meet the current Nb-IoT
configuration. One for each NbIotCell MO whether it is in Standalone,
Inband or Guardband mode.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 47

 Resource Allocation Failure

37 Remedy Actions for NbIotCell: NB-IOT cell

resources not allocated by hosting EUtran
cell

1. Lock the NbIotCell.

2. Lock the hosting EUtranCell, found in eutranCellRef attribute.

3. Unlock the hosting EUtranCell.

4. Unlock the NbIotCell.

If the alarm remains, do the following:

5. Consult the next level of maintenance support.

48 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for NodeBLocalCell: Unable to allocate radio HW resources due to both insufficient HWAC and capacity
license for number of Cell Carriers

38 Remedy Actions for NodeBLocalCell: Unable

to allocate radio HW resources due to both
insufficient HWAC and capacity license for
number of Cell Carriers

1. Perform one of the following:

— Enable a sufficient level of both the HWAC for WCDMA Number of Cell
Carriers and the software capacity license for WCDMA Cell Carriers that
meet the current configuration requirements.

— Reconfigure the existing cells with fewer cell carriers, so that the current
levels of the HWAC and the software capacity license are sufficient.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 49

 Resource Allocation Failure

39 Remedy Actions for NodeBLocalCell: Unable

to allocate radio HW resources due to
insufficient capacity license WCDMA Cell
Carriers for this MO

1. Perform one of the following:

— Enable a sufficient level of software capacity license for WCDMA Cell
Carriers that meets the current configuration requirement.

— Reconfigure the existing cells with fewer cell carriers so that the current
level of the software license is sufficient.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

50 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for NodeBLocalCell: Unable to allocate radio HW resources due to insufficient WCDMA Number of Cell
Carriers HWAC for this MO

40 Remedy Actions for NodeBLocalCell: Unable

to allocate radio HW resources due to
insufficient WCDMA Number of Cell Carriers
HWAC for this MO

1. Perform one of the following:

— Enable a sufficient level of the HWAC for WCDMA Number of Cell
Carriers that meets the current configuration requirement.

— Reconfigure the existing cells with fewer cell carriers so that the current
level of the HWAC is sufficient.

2. Lock the cell.

3. Unlock the cell.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 51

 Resource Allocation Failure

41 Remedy Action for PimCancellationFunction

MO

1. Delete the PimCancellationConfig MO reference to

PimCancellationFunction MO for the carrier that failed..

2. Re-configure cancellation groups for Baseband P with these affected uplink

and downlink carriers. Addition of a Baseband P can be required for more
capacity consideration.
If the alarm remains, do the following:

3. Consult the next level of maintenance support.

52 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Sector Carrier MO> or <Trx MO>: No RF power available in radio equipment

42 Remedy Actions for <Sector Carrier MO> or

<Trx MO>: No RF power available in radio
equipment

This procedure is valid for the following MOs:

— ExtTrx

— NRSectorCarrier

— NodeBSectorCarrier

— NodeBSectorCarrier

— Trx

Note: The ExtTrx is only used for the GSM feature Combined Cell. The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO should be locked/unlocked. For more Combined Cell
information, see Manage Radio Network GSM and GSM RAN User
Description, Combined Cell.

Steps

1. Lock all cells, sector carriers, or TRXs used by the radio.

2. Do one of the following:

— Install a radio unit to match the requested power.

— Reconfigure the affected cells, sector carriers, TRXs or extension TRXs to

a power level within the available RF power level. Also consider the
power configuration of other cells or TRXs using the same radio in a
mixed-mode configuration.

3. Unlock all the cells or TRXs.

If the alarm remains, do the following:

4. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 53

 Resource Allocation Failure

43 Remedy Actions for <Trx MO>:

AvailabilityStatus = FAILED

This procedure is valid for the following MOs:

— ExtTrx

— Trx

Note: The ExtTrx is only used for the GSM feature Combined Cell. For more
Combined Cell information, see Manage Radio Network GSM and GSM
RAN User Description, Combined Cell.

Steps

1. Ensure that the sum of the values of each configuredMaxTxPower attribute

for all Trx MO instances or ExtTrx MO instances referring to the same
RfBranchTx used by the same SectorEquipmentFunction MO is lower or
equal to the capacity of the hardware and the level of the enabled HWAC for
RF Power. If not, enable a sufficient level of the HWAC. Also consider the
power configuration of SectorCarrierEnsure that the sum of the values of
each MOs and NodeBSectorCarrier MOs referring to the same
SectorEquipmentFunction MO in a mixed-mode configuration.
If the alarm remains, do the following:

2. Install more hardware.

If the alarm remains, do the following:

3. Consult the next level of maintenance support.

54 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for <Trx MO>: Unable to allocate radio HW resources due to insufficient HWAC GSM Cell Carrier (TRX)
ERS for this MO

44 Remedy Actions for <Trx MO>: Unable to

allocate radio HW resources due to
insufficient HWAC GSM Cell Carrier (TRX)
ERS for this MO

This alarm can be raised on Trx MO. For the GSM feature Combined Cell, this
alarm can be raised on both Trx MO and ExtTrx MO at the same time.

This procedure is valid for the following MOs:

— Trx

— Trx with ExtTrx

Steps

1. Choose one of the following actions:

— Enable a sufficient level of the HWAC for the hardware related capacity
GSM Cell Carrier (TRX) ERS.

— Reconfigure the existing GSM sectors with fewer cell carriers (TRXs) by
locking one or several TRXs, so that the currently enabled level of the
HWAC is sufficient.
If the alarm remains, do the following:

2. Consult the next level of maintenance support.

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 55

 Resource Allocation Failure

45 Remedy Actions for Trx: Not enough

baseband resources are available to setup
the TRX

The maximum number of TRXs supported by a Baseband unit is divided into

groups of 12 TRXs. One, two or four groups are supported. For more information,
see Chapter 1.5 in Manage Radio Network, GSM.

Steps

1. Lock all Trx MO instances under every GsmSector instance of BtsFunction.

2. Unlock all previously locked Trx instances.

Result: The reallocation of the resources for the transceivers starts.

If the alarm remains, do the following:

3. Check that the Baseband unit is capable of supporting the total number of
Trx instances configured in the node. If necessary, change the Baseband unit
to a higher capacity unit.

4. Check that the number of Trx MO instances in the node is divided into
groups of 12. If necessary split one or more GSM Sectors. For more
information, see Chapter 1.5 in Manage Radio Network, GSM.

Example
In a configuration with three GsmSector MOs with eight Trx MOs each, one
GsmSector must be split into two GsmSector instances with four Trx MOs
each. This way, a GsmSector MO with eight Trx instances and a GsmSector
MO with four Trx instances can a group of 12 TRXs.

Note: The Abis MO TG in the BSC also needs to be split to match the
GsmSector configuration.
If the alarm remains, do the following:

5. Consult the next level of maintenance support.

56 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27

 Remedy Actions for Trx with ExtTrx: Not enough baseband resources are available to setup the TRX

46 Remedy Actions for Trx with ExtTrx: Not

enough baseband resources are available to
setup the TRX

The maximum number of TRXs supported by a Baseband unit is divided into

groups of 12 TRXs. One, two or four groups are supported. For more information,
see Chapter 1.5 in Manage Radio Network, GSM.

For the GSM feature Combined Cell, there is a limitation that the maximum grand
total number of MO Trx and MO ExtTrx instances must less than or equal to 84,
and this limitation is applied for GSM single mode and the Mixed Mode. For more
information, see Chapter 1.6 in Manage Radio Network, GSM.

Note: The ExtTrx is used only for the GSM feature Combined Cell.The ExtTrx
MO does not have the attribute administrativeState, instead the
parent Trx MO has to be locked and unlocked. For more information, see
Manage Radio Network GSM and GSM RAN User Description, Combined
Cell.

Steps

1. Lock all Trx MO instances under every GsmSector instance of BtsFunction.

2. Unlock all previously locked Trx instances.

Result: The reallocation of the resources for the transceivers starts.

If the alarm remains, do the following:

3. Check that the Baseband unit is capable of supporting the total number of
Trx instances and ExtTrx instances configured in the node. If necessary,
change the Baseband unit to a higher capacity unit.

4. Check that the number of Trx MO instances and ExtTrx MO instances in the
node is divided into groups of 12. If necessary split one or more GSM
Sectors.For more information, see Chapter 1.5 in Manage Radio Network,
GSM.

Example
In a configuration with three GsmSector MOs with eight Trx MOs each, one
GsmSector must be split into two GsmSector instances with four Trx MOs
each. This way, a GsmSector MO with eight Trx instances and a GsmSector
MO with four Trx instances can a group of 12 TRXs.

Note: The Abis MO TG in the BSC also needs to be split to match the
GsmSector configuration.
If the alarm remains, do the following:

89/1543-LZA 701 6014/1 Uen AS | 2019-06-27 57

 Resource Allocation Failure

5. Consult the next level of maintenance support.

58 89/1543-LZA 701 6014/1 Uen AS | 2019-06-27