IC 2.9.01 - LTE ALU eNodeB Hardware & Troubleshooting Overview - V1 PDF

LTE ALU eNodeB Hardware &
Troubleshooting Overview
IC – 2.9.01
LTE ALU eNodeB Hardware & Troubleshooting Overview IC – 2.9.01
_____________________________________________________________________________________________
Current Version
Document No, Date Author Reference Documents Description
IC – 2.9.01, 01/07/2016 Jim Hajjar LTE ALU eNodeB Hardware &

Troubleshooting Overview
Replaced Document
Document No, Date Reasons for Update
Document Checking and Approval
Controlled by Date 01/07/2016
Jim Hajjar
Checked by Date 01/07/2016
Tin To
Approved for
QuadGen Wireless by Date 01/07/2016
Paul Chory
This document contains information that is proprietary and confidential to QuadGen Wireless Solutions
Inc., which shall not be disclosed, transmitted or duplicated, used in whole or in part for any purpose
other than its intended purpose. Any use or disclosure in whole or in part of this information without
written permission of QuadGen Wireless Solutions is prohibited. Any other company and product names
mentioned are used for identification purposes only and may be trademarks of their respective
owners.© QuadGen Wireless Solutions Inc. All rights reserved
01/07/201 QuadGen Wireless Solutions- Proprietary 2

_____________________________________________________________________________________________
Table of Contents
1. Hardware Overview ............................................................................................ 5
1.1 BBU d2U shelf ........................................................................................... 5
1.2 Controller boards ...................................................................................... 5
1.3 BaseBand Cards ........................................................................................ 6
1.4 Small Form-Factor Pluggables (SFPs) in CPRI ports .................................. 7
1.5 Radio Frequency Modules (RFMs) – Remote Radio Heads (RRHs)........... 7
1.6 LteCells ...................................................................................................... 9
1.7 Remote Electrical Tilt (RETs) ................................................................... 11
1.7.1 Physical RETS............................................................................... 11
1.7.2 Logical RETS ................................................................................ 13
1.7.3 RET Cleanup (clear phantom RETs) ............................................. 15
1.7.4 RET Crossover Cable Info ............................................................ 15
1.8 eNodeB External Alarms ......................................................................... 18
1.8.1 Indoor eNodeB (BTS_Packaging = 0x1B)..................................... 18
1.8.2 Outdoor eNodeB (BTS_Packaging = 0x18) .................................. 19
1.8.3 External alarm operation ............................................................ 19
1.8.4 Configuring External Alarms ....................................................... 20
2. Troubleshooting Techniques ........................................................................... 23
2.1 Disabled LteCells ..................................................................................... 23
2.1.1 eNodeB must be unlocked .......................................................... 23
2.1.2 Lock/unlock the LteCell............................................................... 23
2.1.3 Check that the RRH supporting the LteCell is enabled ............... 23
2.1.4 Check that the bCEM supporting the LteCell is enabled ............ 24
2.1.5 Check the SFP rate type .............................................................. 24
2.1.6 Reset the eNodeB ....................................................................... 25
2.1.7 Identify eNodeB / LteCell Alarms................................................ 26
2.2 RF Verification Testing ............................................................................ 26
2.2.1 Standard 3 sector LTE eNodeB ................................................... 26
2.2.2 Antenna Cross Connected (ACC)................................................. 27

_____________________________________________________________________________________________
2.2.3 Four port RRHs with 2TX/4RX ..................................................... 28

2.2.4 Four port RRHs with 2TX/2RX (4PortMinus2) Configuration...... 29
2.2.5 Distributed Antenna System (DAS) Configuration ..................... 29
2.3 RRH LED Info ........................................................................................... 31
2.4 eCCM-u LED Info ..................................................................................... 32
2.5 bCEM2 LED Info ...................................................................................... 35
2.6 eCCM2 LED Info ...................................................................................... 36
2.7 RRH Technical Specs ............................................................................... 42
2.8 RRH Supported Bandwidths.................................................................... 43
2.9 Carrier Aggregation Supported Configurations ...................................... 44

_____________________________________________________________________________________________
1. Hardware Overview
1.1 BBU d2U shelf

The eNodeB is built on a BBU d2U shelf
1.2 Controller boards

The d2U contains one controller board (CB) – either an eCCM or eCCM2
The eCCM (Hardware Name ECCMU) has the following characteristics:
1. Inventory Unit Type MOD:eCCM-U_(enhanc.synch)_GE

2. Vendor Unit Type Number 3JR20073CB
3. Has six (6) CPRI ports to connect to up to six Radio Frequency Modules (RFMs)
4. GPS antenna connection
5. Backhaul connection on middle MDA port

_____________________________________________________________________________________________
The eCCM2 (Hardware Name ECCM2) has the following characteristics:
1. Inventory Unit Type MOD:eCCM2

2. Vendor Unit Type Number 3JR20120AB
3. Has nine (9) CPRI ports to connect to up to nine Radio Frequency Modules (RFMs)
5. Backhaul connection on BH1 port
1.3 BaseBand Cards
The d2U contains up to three baseband boards (BB) – either an eCEM or bCEM
1. eCEMs are much older – only support one carrier and one sector. Rarely used in ATT network
2. bCEM support up to 3 sectors (1 Carrier) or 3 carriers (1 sector) in carrier aggregation mode
3. Has nine (9) CPRI ports to connect to up to nine Radio Frequency Modules (RFMs)
5. Backhaul connection on BH1 port

_____________________________________________________________________________________________
1.4 Small Form-Factor Pluggables (SFPs) in CPRI ports

The CPRI ports and backhaul port requires an SFP to interface with the fiber cable going to the RRHs or
SIAD. The SFP rate types and model numbers can be checked on 5620SAM GUI under FRU or in NEM
1.5 Radio Frequency Modules (RFMs) – Remote Radio Heads (RRHs)

Here is a list of some common RRHs
700Mhz
RH2XALB12 RRH2x40-07L 109766345 (2 Port)
RRH2x40-07L-AT 3JR38001AA AR2XALB17 (2 Port)
RRH2x40-07L-DE 3JR38037AA RH2XASB29 (2 Port 700D band29)
850Mhz
2x60-850 3JR10601AA RH2XASB05 (2-port)
1900Mhz
2x60-1900 3JR10801AA (2-port)
AA B25A LP HH65A 3JR52701AAAA (4 -port)
2x60-1900A 3JR39501AA (4 port)
AA B25A LP HH65C SA2XCOB02 (4 port IA)
2100Mhz
RRH2x40-AWS AM1 | S1:21 | 109777250 (2-port)
RRH2x40-AWS AM1 | S1:8 | RDEM_READY 109776161 (4-port)
2300Mhz (WCS Band)

RRH4x25-B30 3JR41325AA RH4XALB30 (4-port)

_____________________________________________________________________________________________
Common fiber connections to RRHs
RRHs can be either MIMO 2TX/2RX (“two port”) or 4Port 2TX/4RX. There are some cases where
customer will only use one transmit port (SIMO 1TX/2RX) for DAS. The easiest way to determine if an
RRH is two port or 4Port is to look on 5620SAM GUI.

_____________________________________________________________________________________________
1.6 LteCells
The LteCell is a logical object used to create a unique LTE carrier in the eNodeB. The LteCell is specific
to a carrier and a sector. The ATT common standard LteCells are
Band Freq Name LteCells*

5 850 850 8A
4 2100 AWS 2A
2 1900 PCS 9A
17 700 700 7A
30 2300 WCS 3A
29 700 700D 7A
* note that the common LteCell names for sector are
A – Alpha
B – Beta
C - Gamma
The LteCell is not a physical device. It is a logical object that consists of the following physical objects:
1. Portion of the eCCM

2. Portion of the eCEM/bCEM
3. A specific CPRI port
4. A specific RRH
All of these physical must be enabled for the LteCell to be enabled.
Some important characteristics of LteCells are
 Bandwidth – parameter under FrequencyAndBandwidthFDD

_____________________________________________________________________________________________
Power – CellDLTotalPower (under LteCell cell info tab)
o 44.7 dBm = 30W

o 46.0 dBm = 40W
o 47.7 dBm = 60W
NOTE – here are common power levels for LteCells
TotalPower(W) cellDLTotalPower (dBm) referenceSignalPower (dBm)

10.0 40.0 18
Standard
20.0 43.0 18
Power
30.0 44.8 19
40.0 46.0 21
60.0 47.8 22
1.0 30 5
2.0 33 8
2.3 33.7 8
WCS Special Low Power
3.0 34.7 9
3.7 35.7 10
4.7 36.7 11
5.9 37.7 12
7.4 38.7 13
9.3 39.7 14
11.7 40.7 15
14.8 41.7 16
18.6 42.7 17
23.4 43.7 18
24.5 43.9 19
29.5 44.7 19
39.8 46.0 21
58.9 47.7 22
 numberOfULAntennas (under LteCell general tab)

o ulAntenna2 (2RX antenna ports)*
o ulAntenna4 (4RX antenna ports)
Note that it is possible to have only two RX ports configured with a 4Port RRH. This is where
customer has capped and disabled ports 3&4 on the RRH. Also called 4PortMinus2
configuration

_____________________________________________________________________________________________
1.7 Remote Electrical Tilt (RETs)

The Remote Electrical Tilt (RET) motor is a physical device in the antenna as well as a logical object on
the 5620SAM GUI.
1.7.1 Physical RETS

The physical RETs communicate over the AISG/ALD bus cable between the RET and the RRH.
The RRH automatically detects any/all RRHs on it’s AISG/ALD bus and reports it in NEM/GUI so long as
ALDBusScanEnable is TRUE.
An RRH can have no physical RETs reporting – meaning there is no RET detected or installed on the
RRH bus

_____________________________________________________________________________________________
The RRH can have single-actuator physical RETs (only one RETSubunit) – meaning – there is one
physical RET connected to RRH bus with a single adjustable tilt motor
The RRH can have multi-actuator physical RETs (more than one, usually two RETSubunits) – meaning –
there is one physical RET connected to RRH bus with two (or more) adjustable tilt motors
The RRH can also have multiple RETs each with one or more RETSubunits
One word of caution – Physical RETs are automatically created any time a RET is connected to the
RRH AISG/ALD bus. Once the physical RET object is created – it remains an object under the RRH

_____________________________________________________________________________________________
forever. In other words, if a RET motor is replaced, the new RET will show up as a new physical RET
object. At the same time, the original RET will remain under the RRH, but will show a “NO CONTACT TO
BOARD” alarm. These leftover RETs are referred to as “Phantom RETs” since they are really no longer
physically present, but do show up on eNodeB as a physical object. The only way to clear these phantom
RETs is by clearing them out of the mib. There is a detailed procedure available that documents how to
do this.
1.7.2 Logical RETS
For each physical RET present there needs to be an associated logical RET object on the 5620SAM.
The logical RETs are used to allow the 5620SAM to communicate with the RET motor and set the
appropriate tilt values. Logical RETs are not automatically built (as with physical RET objects). They
must be created with a work order.
Once created, the logical RETs show up under the Ret object on the component view of the 5620SAM
Each logical RET contains a RetSubunit – one for each corresponding physical RetSubunit
The parameter that links the physical RET with its associated logical RET is the serial number of the RET.
The parameter is called “Unique Name” on the physical RET and “retAldUniqueName” on the logical RET.
The logical RET with its retAldUniqueName links to the physical RET that has the exact associated
“UniqueName”. Here is sample logical RET with “retAldUniqueName = KACSF4774053”. Notice it has
already linked to the physical RET on RRH 161 (FRUID 1061231).

_____________________________________________________________________________________________
The physical RET with ID 1061231 is shown below.
Notice – Unique Name is KACSF4774053 – which matches the retAldUniqueName of the logical RET.
The physical RET general tab also shows the logical information if there is a linked logical RET. If there
is no logical RET, the Logical Information will be all empty fields.
The same goes for any RETSubunit under the linked RETs. The logical RetSubunit contains the
antennaElectricalTilt (deg) object that is used to control the tilt angle on the antenna. In this example, the
tilt is set to 3.0 degrees
st
It is also important to note that when the logical RET is 1 created with a workorder, the
antennaElectricalTilt is set to a value of “-90.0” degrees. When the new logical RET is created with the
tilt set to -90.0, when the link is made to the physical RET, the 5620SAM sends a query message to read
the programmed information from the physical RET and populates it into the logical RET.

_____________________________________________________________________________________________
This information includes
 Current electrical tilt value (and replaces the -90.0 with the current tilt value)
 maxElectricalTilt value
 minElectricalTilt value
 labelAssociateedENB value (if programmed)
 labelSectorId (if programmed)
The logical RetSubunit contains a parameter called antennaBandClass. For ATT sites, the QIC sets this
field to equal the RET BSID. The BSID is normally programmed by the TV into the labelAssociateedENB
or labelSectorId. If not programmed, the TV provides a RET worksheet with the BSID. A BSID is
provided for each physical RetSubunit
The logical RET contains a parameter called retFriendlyName. For ATT sites, the QIC sets this field to
equal the RET BSIDs of all the RetSubunits separated by “_”
There is a documented procedure on how to properly program the logical RETs and use automated tools
to generate the RET workorder.
1.7.3 RET Cleanup (clear phantom RETs)

1. Identify the phantom physical and logical RET (RET that has been removed from RRH)
a. Phantom physical RET has “No Contact To Board” major alarm
b. Phantom logical RET contains the serial number identified in 1.a
2. Take a snapshot eNodeB and import it into WPS

3. Create the WO to delete the phantom Logical RET
4. Secure shell to eNodeB, and go to the /data/db/active/mib directory
5. Delete physical RETs (rm RET* and then rm Ret*)
6. Reboot the eNodeB
7. Create the WO to add the Logical RET that has physical entity but no associated Logical RET.
8. Set the RET Subunit Tilt angle for LTE 1C, 2C and UMTS 850/1900 if applicable
1.7.4 RET Crossover Cable Info

_____________________________________________________________________________________________
There are some 700L/AWS RRHs that require an adapter cable (crossover) in line with the standard
AISG cable in order to detect the RETs. The adapter cable when used should be installed directly to the
RRH.
Based on RRH inventory data from 5620SAM it can be determined if crossover cable is needed.
In this example, comcode is 109759563 and series is P2 S0:3
Use lookup table to determine if crossover is needed

_____________________________________________________________________________________________
In this example 109759563 series P2 S0:3 requires the crossover

_____________________________________________________________________________________________
1.8 eNodeB External Alarms

The ALU eNodeB is capable of reporting the alarm status of devices connected external to the eNodeB.
These “external alarms” are either connected to the d2U shelf (32 alarms) or to the RRH (8 alarms per
RRH). The d2U external alarms are cabled from the devices to the 66 block back to the eNodeB through
the alarm module. The RRH external alarms are cabled from the devices to the RRH alarm port. The
RRH alarm status is then sent via messaging to the eCCM via the CPRI link. There are NO RRH alarm
connections to the 66 block or to the alarm module or to the d2U shelf. All alarm wiring is
between the device and the RRH.
The external alarm cabling and hardware varies depending on whether the eNodeB is and indoor rack
mount or an outdoor cabinet.
1.8.1 Indoor eNodeB (BTS_Packaging = 0x1B)

Note for indoor there is an eAMi alarm module that is cabled to the RUC. The customer punch down is
also known as the 66 block

_____________________________________________________________________________________________
1.8.2 Outdoor eNodeB (BTS_Packaging = 0x18)

Note for outdoor there is an eAMo alarm module that is cabled to the RUC and cabled to several devices
via ‘frame alarm’ cable (fan, door switch, airflow switch).
1.8.3 External alarm operation

The external devices report their alarms to the d2U or the RRH with two wires. The device creates either
an open circuit or a short circuit condition between the two wires. That is the fundamental concept of
external alarms – they are either a closed circuit between the two sense wires or an open circuit
between the two sense wires. The d2U or RRH external alarms are configured to be
 Connector_Usage - Active or InActive. InActive sets the eNB to ignore and Active sets
the eNB to report the specific alarm wire pair
 Alarm_Trigger – OpenOnAlarm or ClosedOnAlarm. This parameter determines when
the eNodeB reports the external alarm. OpenOnAlarm will trigger an alarm if there is an
open circuit on the two wire pair. ClosedOnAlarm will trigger an alarm if there is an short
circuit on the two wire pair.
NOTE – There is a bug with NEM LR14.3 on the 5620SAM. It improperly shows the
alarm trigger on all RRH alarms. This means that if you want a RRH external alarm
to be OpenOnAlarm, you must set it to ClosedOnAlarm (and vice versa) in NEM on
the 5620SAM. This issue does NOT apply to NEM run locally (direct connected to

_____________________________________________________________________________________________
eNB) by the FE.
Also note – many external devices have alarm trigger states of “NormallyClosed -
NC” or “NormallyOpen - NO”.
NormallyClosed is the same as OpenOnAlam
NormallyOpen is the same as ClosedOnAlarm
 Alarm_Label – This is a text field that contains the alarm name reported by eNodeB if the
alarm trigger condition is met on the alarm wire pair.
 Alarm_Severity – Critical, Major, Minor, Warning – This field sets the alarm severity
reported by the eNodeB.
1.8.4 Configuring External Alarms

The recommended way to configure external alarms is by utilizing one of the standard external alarm and
severity settings configuration files. These files are stored on the provisioning drive at /LTE/ExtAlarms.
Follow the attached procedure to load the configurations.
How to update ALU

LTE eNodeB external alarm configurations for ATT.docx
You can also use NEM to configure external alarms
1. In NEM Tree view, click on the “+” next to Alarms to display Alarms Configuration.
Click on Alarms Configurations, to load the alarm configurations (this can take a minute or
two).
2.
When alarm configs are loaded, the all the alarms tabs will be listed on right.
Click on the External Alarms tab to display the external alarm configuration table
3.

_____________________________________________________________________________________________
Click on the “Managed Object” header and then the “ID” header to list the External alarms
4.
in order, expand the column if necessary to see the entire text of the alarm description.
Click on the proper row based on the External Alarm Number in EACS file. Example,
Exernal Alarm Number 1 is alarm 1 on the NEM external alarm table.
Then right-click and select Edit External Alarms to open the alarm edit window for that
specific alarm number.
5.
6. Do not change the ID
Enter the User Label for this external alarm as defined in the EACS External Alarm
7.
Description.
8. Set Connector Usage to “Active”
Set the Alarm Trigger based on the Alarm Trigger definition

OpenOnAlarm = external alarm relay creates an open circuit (normally closed)
CloseOnAlarm = external alarm relay creates a closed circuit (normally open)
9.
10. Click on OK to submit
Verify the User Label, Connector Usage, and Polarity fields are updated on the
External Alarm configuration tab.
11.
12. Repeat steps 5 through 11 for each alarm defined on the eNodeB

_____________________________________________________________________________________________
Click on the Alarm Severity tab.
13.
Right click on the row of the first configured External Alarm based on the Description
column in table. Click on Edit Alarm Severity.
14.
Select the Customer supplied Severity for the alarm (Warning, Minor, Major, Critical).
15.
Click OK to save
Verify the Severity is correct on the Alarm Severity tab.
16.
17. Repeat steps 14 through 16 for each External Alarm to be configured.

_____________________________________________________________________________________________
2. Troubleshooting Techniques
2.1 Disabled LteCells
When the LteCell has the Administrative State changed to unlock, the operational state should go to
Enabled. If the operational state is enabled, then the LteCell is properly functioning and transmitting its
designed carrier on its designed sector.
If the operational state shows as Disabled, it means the LteCell is not functioning/transmitting.
Since the LteCell is not a “hardware” object and is a logical object consisting of eCCM/bCEM/RRH and
configuration data, you must analyze what is actually causing the LteCell to fail.
2.1.1 eNodeB must be unlocked

For any/all LteCells to enable, the eNodeB must be unlocked. Obviously, if any LteCells on an eNodeB
are enabled, then the eNodeB is unlocked. Especially for NSB sites or for sites where all LteCells are
disabled, verify that the Administrative State of the eNodeB is unlocked.
2.1.2 Lock/unlock the LteCell

Sometimes a simple lock/unlock will clear the issue and enable the LteCell.
2.1.3 Check that the RRH supporting the LteCell is enabled

For any/all LteCells to enable, the RRH for that carrier/sector must be unlocked and enabled. Verify that
the RRH has an operational state of enabled. You must have an enabled RRH for LteCell to enable.

_____________________________________________________________________________________________
Make certain that there are no configuration mismatch errors on the RRH ports that indicate the
eNodeB design does not match the physical RRH present (and redesign is needed)
2.1.4 Check that the bCEM supporting the LteCell is enabled

Identify which bCEM is associated with the LteCell on the Cell Info tab
In this example, the associated bCEM is 202000. Now look at the hardware tree under shelf 1. The
bCEM in slot 2 (bCEM1) is hardware number 20200. Slot3 (bCEM2) – 20300, Slot4 (bCEM3) - 20400
Make sure bCEM is enabled.
If the LteCell does not show an associated bCEM, make sure there are enough bCEMs equipped and
enabled to support the LteCell. A bCEM supports the following:
 one (1) carrier – three (3) sectors for non-Carrier Aggregation (CA) sites
 three (3) carriers – one (1) sector for CA sites
You must have an associated bCEM for the LteCell to enable.
2.1.5 Check the SFPs on the eCCM and RRHs to make sure rate type is OK
The wrong SFPs can cause RRHs to fail – but they can also cause LteCells to fail to enable. Run the
SFP check in the integration tool. You can also check the SFP types on GUI. Select RFU object on
component view tree. Filter by name = SFP.

_____________________________________________________________________________________________
The SFP rate type is listed under the manufacturerData field.
Use the table to determine the AT&T recommended SFP rate types. You must know the band, RRH
type, the LteCell bandwidth, and whether the LteCell/RRH is 2T2R (MIMO or 4PortMinus2) or 2T4R
(4Port)
In this example, the RRH is 1900, 2x60-1900A and the LteCell is 10Mhz with 4Port (ulAntenna4)
configuration. The table show that the RRH should have Rate 5. The eCCM SFP, for 10Mhz and 2T4R,
for that RRH is shows as Rate3 or Rate5. The SFP in the eCCM shown above is only 1300Mb. Rate3
is normally 3100Mb. Rate5 is normally 6200/6300Mb
2.1.6 Reset the eNodeB

If the eNodeB is enabled, the RRH is enabled, the bCEM is enabled, and the SFPs look correct, but the
LteCell still will not enable, try resetting the entire eNodeB. Often, a reset (lecreboot) will clear the error
preventing the LteCell from being enabled.

_____________________________________________________________________________________________
2.1.7 Identify eNodeB / LteCell Alarms

If there are configuration errors or L1L2 errors on the LteCell, these often indicate a configuration issue.
Escalate to design team to investigate.
2.2 RF Verification Testing

RF verification testing consists of measuring the transmit power, the RSSI, and VSWR on a specific
RRH’s RF path. The acceptable limits of these tests are contained in our integration tool. In almost all
cases, RF testing is done with the RRHs forced to maximum power out by setting OCNS to 100 (default is
OCNS at 0). Note that OCNS = 0 does not mean the TX power is zero. It means the RRH/LteCell will
transmit minimal power to maintain the carrier and support users. OCNS = 100 simulates fully loading
the RRH/LteCell with many users.
The RF tests are best run from the integration tool, but for troubleshooting, it can also be easily run from
the LTE Tools Menu option 3.
2.2.1 Standard 3 sector LTE eNodeB
 The LteCell Antenna Port is a logical port of the LteCell. It is NOT the physical port on the RRH.
Do not use this value when troubleshooting with a TV.
 The RRH antenna port is a true physical port on the RRH. For example, 1011000-1 is alpha 1C
RRH port 1. 1031000-2 is gamma 1C RRH port 2.
 In the above, you can tell the RRH is configured with 2TX ports and 2RX ports
o There are two ports (1 and 2) on each RRH
o There is a TX power value present for both ports (2TX)
o There is an RSSI value for both ports (2RX)
 Diversity Imbalance is the difference between the highest RSSI and lowest RSSI on any given
LteCell. So for alpha, the div imb is 1.3 (-98.5 – -97.2)
 You can also determine that this site is standard antenna configuration (not antenna cross
connect – ACC) because both LteCell logical antenna ports are linked to the same RRH

_____________________________________________________________________________________________
antenna ports. For example, OML02824_7B_1 port1 and port2 are both linked to RRH 1021000
(beta RRH) ports 1 and 2.
2.2.2 Antenna Cross Connected (ACC)
 You can determine that this site is antenna cross connect – ACC - because both LteCell logical
antenna ports are linked to different RRH antenna ports.
 Notice that for alpha LteCell – MOL03672_7A_1 – port 2 is linked to gamma RRH
port 2 1031000-2.
 Notice that for beta LteCell – MOL03672_7B_1 – port 1 is linked to alpha RRH
port 2 1011000-2.
 Notice that for gamma LteCell – MOL03672_7C_1 – port1 is linked to beta RRH
port 2 1021000-2.
LTeCell. So for beta, the div imb is 0.5 (-96.5 – -96.0)

_____________________________________________________________________________________________
2.2.3 Four port RRHs with 2TX/4RX
 Notice the 1900Mhz 2C LteCells (9A, 9B, 9C) all have four (4) antenna ports.
 Notice that for each LteCell, all four ports are linked to the same RRH antennaPorts.
 Notice that on each RRH, ports 1 and 2 have the following:
o All four ports have RSSI values since there are four receive ports or 4RX
o Only two ports – ports 1 and 2 – of RRH have transmit power and VSWR/RL. This is
because only two of the four ports are transmit ports or 2TX.
LteCell. So for alpha (9A), the div imb is 1.0 (-103.0 – -102.0)
 This configuration is referred to 4Port RRH or 2TX/4RX

_____________________________________________________________________________________________
2.2.4 Four port RRHs with 2TX/2RX (4PortMinus2) Configuration

 This is where there is an RRH with four (4) physical ports but the customer does not use ports 3
and 4 as RX ports. They usually cap the unused ports and they need to be disabled in the
configuration
 Since there are only 2RX ports configured on the LteCell (port 1 and 2) and ports 3 and 4 are
disabled, the RF results are exactly the same as a 2RX/2TX configuration (shown in 2.1.1)
 This configuration is referred to 4Port Minus2 - 2TX/2RX (note this designation is the same as a
two port RRH)
 The only way to know this configuration is by checking on the 5620SAM GUI
o The RRHs will have four physical antenna ports
o The LteCell will only have four logical antenna ports (2TX 2RX) instead of six (2TX 4RX)
o The LteCell will be configured with numberOfULAntennas = ulAntenna2
 RF verification is exactly the same as a two port RRH
2.2.5 Distributed Antenna System (DAS) Configuration
 This is where there is an RRH with two or four physical ports but the customer only uses port 1
as a TX/RX port. They usually cap the unused ports and they need to be disabled in the
configuration
 Notice that the TX power is 0.0 on the unused port 2.
 The VSWR and RL show a bogus value of -0.2 on the unused port 2
 The RSSI is ignored on port 2 even though the RRH returns a value – this is because ALU LTE
doesn’t fully support 1TX/1RX config (SISO Single-Input-Single-Output) – only 1TX/2RX (SIMO
Single-Input-Multiple-Output)

_____________________________________________________________________________________________
 The only way to know this configuration is by checking on the 5620SAM GUI
o On component view, under LteCell there will be an object called SimoResources
o This object is always present, but on non-DAS sites, the object has no children under it
o On DAS sites, there are two objects under SimoResources – PowerOffsetConfiguration
and UlinkMimo
o Examine the UplinkMimo object for a parameter ulTransmissionMode – for DAS it will be
set to TM1
 RF verification is only performed on port 1 – and there is no diversity imbalance requirement

unless the customer specifies they are using port 2 as a RX only port.

_____________________________________________________________________________________________
2.3 RRH LED Info

_____________________________________________________________________________________________
2.4 eCCM-u LED Info
CMA LED status
CMA (top row of matrix) The two left-most LEDs light after the eCCM-U has fully
booted. If they are not on, reboot the 9926 BBU by cycling power.

_____________________________________________________________________________________________
SYNC LED status

The SYNC LEDs show the status of the drop loads and GPS synchronization during integration.
eCCM-U MDA/PCM LEDs
The MDA and PCM LEDs are not used.

_____________________________________________________________________________________________
eCCM-U CPRI Port LEDs
eCCM-U GigE MDA port LED status
GigE MDA ports have LEDs that indicate signal activity.

_____________________________________________________________________________________________
2.5 bCEM2 LED Info

bCEM2 A4 LED status
bCEM2 A3 LED status – not used
bCEM2 A2 LED status
bCEM2 A1 LED status
ds

_____________________________________________________________________________________________
2.6 eCCM2 LED Info

The following provides an interpretation of the eCCM-U Model 2 LED matrix and eCCM-U Model 2 CPRI
LEDs.
eCCM2 CMA LED status

The following figure shows the operation of the CMA 3 and CMA 4 LEDs which display the status of the eCCM2 self
tests, software downloads, and boots.
Figure A-3: eCCM2 CMA 3 and 4

_____________________________________________________________________________________________

_____________________________________________________________________________________________
The following figure shows the operation of the CMA 2 LED which displays the software technology loaded on the
eCCM2 board.
Figure A-4: eCCM2 CMA 2
The following figure shows the operation of the CMA 1 LED which displays the activity status of the eCCM2 board.
Figure A-5: eCCM2 CMA 1

_____________________________________________________________________________________________
eCCM2 SYNC LED status

The following figures show the operation of the SYNC LEDs which display the status of the GPS receiver.
Figure A-6: eCCM2 SYNC 4

_____________________________________________________________________________________________
Note: This external source can be a slave eCCM2 that would acquire its synchronization from a master eCCM2.

_____________________________________________________________________________________________
eCCM2 LNK LED status

The following figure shows the operation of the LNK (link) LEDs which display which source is currently selected to
discipline the local oscillator.
Figure A-10: eCCM2 LNK 1, 2, 3, and 4
If blinking, the local oscillator is in holdover, meaning it has temporarily lost communication with the source
identified by the blinking LED.
If red, the holdover time has been exceeded.
eCCM2 CPRI LEDs

There are two LEDs per CPRI to show port status (SFP Tx enabled - green; SFP Rx detected signalling - green).
eCCM2 SFP LEDs

There are two LEDs per SFP backhaul to show port status (SFP Tx enabled - green; SFP Rx detected signalling -
green).
eCCM2 RJ-45 port LEDs

There are two LEDs per RJ-45 port to show link and activity status (link is connected - green; data in transmission
- blinking yellow).

_____________________________________________________________________________________________
2.7 RRH Technical Specs

_____________________________________________________________________________________________
2.8 RRH Supported Bandwidths

_____________________________________________________________________________________________
2.9 Carrier Aggregation Supported Configurations

IC 2.9.01 - LTE ALU eNodeB Hardware & Troubleshooting Overview - V1 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IC 2.9.01 - LTE ALU eNodeB Hardware & Troubleshooting Overview - V1 PDF

Uploaded by

Copyright:

Available Formats

LTE ALU eNodeB Hardware &

Document No, Date Author Reference Documents Description

IC – 2.9.01, 01/07/2016 Jim Hajjar LTE ALU eNodeB Hardware &

Document No, Date Reasons for Update

Document Checking and Approval

Controlled by Date 01/07/2016

Checked by Date 01/07/2016

QuadGen Wireless by Date 01/07/2016

01/07/201 QuadGen Wireless Solutions- Proprietary 2

01/07/201 QuadGen Wireless Solutions- Proprietary 3

2.2.3 Four port RRHs with 2TX/4RX ..................................................... 28

01/07/201 QuadGen Wireless Solutions- Proprietary 4

1.1 BBU d2U shelf

1.2 Controller boards

The eCCM (Hardware Name ECCMU) has the following characteristics:

1. Inventory Unit Type MOD:eCCM-U_(enhanc.synch)_GE

01/07/201 QuadGen Wireless Solutions- Proprietary 5

The eCCM2 (Hardware Name ECCM2) has the following characteristics:

1. Inventory Unit Type MOD:eCCM2

1.3 BaseBand Cards

01/07/201 QuadGen Wireless Solutions- Proprietary 6

1.4 Small Form-Factor Pluggables (SFPs) in CPRI ports

1.5 Radio Frequency Modules (RFMs) – Remote Radio Heads (RRHs)

2300Mhz (WCS Band)

01/07/201 QuadGen Wireless Solutions- Proprietary 7

Common fiber connections to RRHs

01/07/201 QuadGen Wireless Solutions- Proprietary 8

Band Freq Name LteCells*

1. Portion of the eCCM

All of these physical must be enabled for the LteCell to be enabled.

Some important characteristics of LteCells are

 Bandwidth – parameter under FrequencyAndBandwidthFDD

01/07/201 QuadGen Wireless Solutions- Proprietary 9

Power – CellDLTotalPower (under LteCell cell info tab)

o 44.7 dBm = 30W

NOTE – here are common power levels for LteCells

TotalPower(W) cellDLTotalPower (dBm) referenceSignalPower (dBm)

 numberOfULAntennas (under LteCell general tab)

01/07/201 QuadGen Wireless Solutions- Proprietary 10

1.7 Remote Electrical Tilt (RETs)

1.7.1 Physical RETS

01/07/201 QuadGen Wireless Solutions- Proprietary 11

01/07/201 QuadGen Wireless Solutions- Proprietary 12

1.7.2 Logical RETS

01/07/201 QuadGen Wireless Solutions- Proprietary 13

The physical RET with ID 1061231 is shown below.

01/07/201 QuadGen Wireless Solutions- Proprietary 14

This information includes

1.7.3 RET Cleanup (clear phantom RETs)

a. Phantom physical RET has “No Contact To Board” major alarm

b. Phantom logical RET contains the serial number identified in 1.a

2. Take a snapshot eNodeB and import it into WPS

1.7.4 RET Crossover Cable Info

01/07/201 QuadGen Wireless Solutions- Proprietary 15

In this example, comcode is 109759563 and series is P2 S0:3

Use lookup table to determine if crossover is needed

01/07/201 QuadGen Wireless Solutions- Proprietary 16

In this example 109759563 series P2 S0:3 requires the crossover

01/07/201 QuadGen Wireless Solutions- Proprietary 17

1.8 eNodeB External Alarms

1.8.1 Indoor eNodeB (BTS_Packaging = 0x1B)

01/07/201 QuadGen Wireless Solutions- Proprietary 18

1.8.2 Outdoor eNodeB (BTS_Packaging = 0x18)