Ericsson DU Radios x BaseBand Radios

Equipment
1

Ericsson has 2 types of radios: it can be DU Radio or BaseBand Radio

Depending on radio type, corresponding information is extracted from different sources.

  • For CM (Configuration Management): when you Export via BulkCM you will find MOs only for DU Radio, MOs only for BaseBand Radios and MOs for Both. (“Corresponding” MOs have almost the same columns, so it’s easy to join it).

  • For Inventory: you can use 2 programs:
    SMO: to export Inventory for DU Radios
    SHM: to export Inventory for BaseBand Radios

In the Inventory case, if you want to get the Inventory Information of the entire network (DU Radios + BB Radios) you need to query 2 MOs: AuxPlugInUnit (for DU Radios) and FieldReplaceableUnit (for BB Radios).

Unfortunately, for DU Radios the information that should be present in AuxPlugInUnit is empty. So, we need to get this info via SMO.

So, things get a little confusing.

The AMOS approach could be used, but this is hard to schedule, fopr example in crontab (you would be needed to update sitelist regularly), making automation a problem.

!!! WORKAROUND to get a complete report inventory (RRU + BBU) for Ericsson !!!

For DU Radios:
Parse XML file (generated with SMO CPP command*)
*Because CM_BulkCM MO AuxPlugInUnit, that should contain the info, is empty!

For BaseBand Radios:
Parse XML file (generated with BulkCM Export - MO FieldReplaceableUnit)

BTS 2G:
Parse Text file (generated with bsm command)

Boda can parse it all, all you need to do is work with processed data. :wink:

Ericsson DU Radios x BaseBand Radios
Ericsson DU Radios x BaseBand Radios1024×1024 120 KB

5 Likes
2

This is the kind of information you don’t learn in school.

And nobody tell you easily explained like this.

Note: I wish i had found this article before (currently i already know this issue); anyway, was good to refresh.

1 Like
4

It may have been a while since this post was made, but I also encountered a similar task, associating the cells to their corresponding RRU, and indicating their power and MIMO configuration.

This last part was not difficult, but I think it was a bit difficult to link the EutrancellFDD with the RRU Serial Number.

Here are the steps, a bit long, but they worked for me to make this kind of inventory.

Export the EUtranCellFDD MO. Here we will get the EUtranCellFDDId and sectorCarrierRef.
cmedit get * EUtranCellFDD.sectorCarrierRef -t

Export the SectorCarrierRef MO. Here we will get the SectorCarrierId and sectorFunctionRef.
cmedit get * SectorCarrier.(configuredMaxTxPower, maximumTransmissionPower, noOfRxAntennas, noOfTxAntennas, sectorFunctionRef) -t

With the two previous points, if we combine NodeID + SectorCarrierRef, we can associate the EUtranCellFDDId and its configuration (MIMO, configuredMaxTxPower, maximumTransmissionPower, etc, values ​​that are in the MO: sectorCarrierRef)

Export the RfBranch MO. Here we will get all the branches defined in the BaseBand, to get the associated one for the LTE cell, we filter those that have typeSectorCarrier=SectorEquipmentFunction, and with this we get the SectorCarrierID
cmedit get * RfBranch.(reservedBy, rfPortRef) -t

Finally, we export the MO: FieldReplaceableUnit. Which contains the RRUs connected to the baseband. Here we are interested in the FieldReplaceableUnitId, which we can associate with the RfBranch.SectorCarrierID
cmedit get * fieldReplaceableUnit.(administrativeState, productData) -t

Finally, to create the relationships and know which RRU an LTE cell is associated with, we have to create the following keys to do a search:

NodeID + sectorCarrierRef (MO: EUtranCellFDD ) → NodeID + SectorCarrierId(MO: SectorCarrierRef) = MIMO + Power Config + SectorEquipmentFunction

NodeID + SectorEquipmentFunction (MO: SectorCarrierRef) → NodeID + SectorEquipmentFunction (MO: RfBranch) = RRU_NAME

NodeID + RRU_NAME (MO: RfBranch) → NodeID + FieldReplaceableUnitId (MO: FieldReplaceableUnit) = productName + serialNumber

2 Likes