Alarm-triggered eNodeB Operations
(1) Carrier or Cell Unavailable
Alarm ID Alarm
Name NE Feature ID Feature Name
ALM-26200 Board Hardware Fault eNodeB l LAOFD-001001 l LAOFD-001002 l LAOFD-070201 l LAOFD-070202 l LAOFD-080201 l LAOFD-080202 l LTE-A Introduction l Carrier Aggregation for Downlink 2CC in 40MHz l Flexible CA from Multiple Carriers
Alarm ID Alarm
Name NE Feature ID Feature Name
ALM-29240 Cell Unavaila ble eNodeB l LAOFD-080207 l LAOFD-080208 l LAOFD-081237 l MRFD-101222 l Inter-eNodeB CA based on Coordinated BBU l Inter-eNodeB CA based on Relaxed backhaul l Carrier Aggregation for Uplink 2CC [Trial] l Carrier Aggregation for Downlink 3CC in 40MHz l Carrier Aggregation for Downlink 3CC in 60MHz l Carrier Aggregation with DL 4x4 MIMO [Trial] l FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
If an alarm listed in the preceding table is reported as indicating a hardware fault or cell unavailability, the eNodeB performs the following fallback operations:
l If the faulty cell has been configured as an SCell of a CA UE, the eNodeB sends an RRC Connection Reconfiguration message to remove the SCell for the UE. If the faulty cell has not been configured as an SCell of any CA UE, the eNodeB does not send an RRC Connection Reconfiguration message to configure the cell as an SCell for any CA UE. l If the faulty cell is the PCell of a CA UE, the CA UE may encounter service drops or
service unavailability.
(2) Clock Synchronization Capability Degraded
Alarm ID Alarm
Name NE Feature ID Feature Name
ALM-26262 External Clock Reference Problem eNodeB l LAOFD-001001 l LAOFD-001002 l LAOFD-070201 l LAOFD-070202 l LAOFD-080201 l LAOFD-080202 l LAOFD-080207 l LAOFD-080208 l LAOFD-081237 l MRFD-101222 l LTE-A Introduction l Carrier Aggregation for Downlink 2CC in 40MHz l Flexible CA from Multiple Carriers l Inter-eNodeB CA based on Coordinated BBU l Inter-eNodeB CA based on Relaxed backhaul l Carrier Aggregation for Uplink 2CC [Trial] l Carrier Aggregation for Downlink 3CC in 40MHz l Carrier Aggregation for Downlink 3CC in 60MHz l Carrier Aggregation with DL 4x4 MIMO [Trial] l FDD+TDD Carrier Aggregation(LTE FDD) [Trial]
If the clock synchronization capability deteriorates because of a clock or hardware fault, the eNodeB reports the alarm listed in the preceding table, and the following impact is generated: l SCells cannot be configured for CA UEs that access the faulty eNodeB in scenarios of
initial access, handovers, or RRC connection re-establishments. l Other eNodeBs cannot configure cells in the faulty eNodeB as SCells.
l SCells are removed for the CA UEs that treat cells served by the faulty eNodeB as their PCells or SCells.
Handle the alarm according to the alarm reference. If the fault is rectified, CA services are restored as follows:
l SCells can be configured for CA UEs that access the eNodeB in scenarios of initial access, handovers, or RRC connection re-establishments.
l Functioning eNodeBs can configure cells in the originally faulty eNodeB as SCells.
Fault Description
After CA is enabled, the CA-related counters provided in 6.5 Performance Monitoring retain the value of 0.
Fault Handling
If CA works in CA-group-based configuration mode, perform the following steps on the U2000 client:
Step 1 Run the LST ENODEBALGOSWITCH command to check whether FreqCfgSwitch under CA Algorithm Switch is off.
l If the switch is off, go to Step 3. l If the switch is on, go to Step 2.
Step 2 Run the MOD ENODEBALGOSWITCH command with the
FreqCfgSwitch(FreqCfgSwitch) option of the CA Algorithm Switch parameter deselected. Then, check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values.
l If the counters produce non-zero values, no further action is required. l If the counters retain the value of 0, go to Step 3.
Step 3 Check whether ALM-26200 Board Hardware Fault or ALM-29240 Cell Unavailable is reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the DSP CAGROUPCELL command to check the running status of all CA groups configured on the eNodeB. The running status includes information such as whether the link between cells in one CA group is normal, whether related licenses work normally, and whether the CA configuration state is normal.
l If the running status is normal, go to Step 5.
l If any status is abnormal, rectify the fault. Then, check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 5.
Step 5 Run the LST CAGROUPSCELLCFG command to check whether candidate SCells are correctly configured in the eNodeB.
l If the configurations are correct, go to Step 6.
l If they are incorrectly configured, correct the configurations by following the
instructions described in 6.4 Deployment. Then, check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 6.
Step 6 If CA-related hardware and data configurations are correct, check whether the fault is due to no UE access to the network.
1. Start a Uu interface tracing task as follows: Choose Monitor > Signaling Trace > Signaling Trace Management. In the navigation tree on the left of the Signaling Trace Management tab page, choose LTE > Application Layer > Uu Interface Trace. Select an NE, set tracing task parameters, and then click Finish to start signaling tracing.
2. Run the MOD ENODEBALGOSWITCH command with
SccBlindCfgSwitch(SccBlindCfgSwitch) under the CA Algorithm Switch parameter selected, and run the ADD CAGROUPSCELLCFG command with SCell Blind Configuration Flag set to TRUE(TRUE) for all candidate SCells associated with the PCell. Enable a CA UE to access the network. Check the Uu interface tracing results for an RRC_CONN_RECFG message.
– If CA-related counters provided in 6.5 Performance Monitoring produce non-zero values, these counters had the value of 0 because there was no CA UE on the network. No further action is required.
– If the RRC_CONN_RECFG message indicates that the eNodeB configures a candidate cell as an SCell for the UE, but the CA-related counters in 6.5 Performance Monitoring still retain the value of 0, contact Huawei engineers. – If the eNodeB does not deliver an RRC_CONN_RECFG message to configure an
SCell for the UE, contact Huawei engineers. ----End
If CA works in frequency-based or adaptive configuration mode, perform the following steps on the U2000 client:
Step 1 Run the LST ENODEBALGOSWITCH command to check whether the required switch (FreqCfgSwitch or AdpCaSwitch) under CA Algorithm Switch is on.
l If the switch is on, go to Step 3. l If the switch is off, go to Step 2.
Step 2 Run the MOD ENODEBALGOSWITCH command with the
FreqCfgSwitch(FreqCfgSwitch) option of the CA Algorithm Switch parameter selected. Then, check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values.
l If the counters produce non-zero values, no further action is required. l If the counters retain the value of 0, go to Step 3.
Step 3 Check whether ALM-26200 Board Hardware Fault or ALM-29240 Cell Unavailable is reported.
l If an alarm is reported, handle the alarm and then check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 4.
l If neither alarm is reported, go to Step 4.
Step 4 Run the LST PCCFREQCFG and LST SCCFREQCFG commands to check whether PCC and SCC configurations are correct.
l If the configurations are correct, go to Step 5.
l If the configurations are incorrect, correct them by following the instructions described in 6.4 Deployment. Then, check whether the CA-related counters provided in 6.5 Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 5.
Step 5 Run the LST EUTRANINTERNFREQ command and view Downlink EARFCN in the command output to check whether candidate SCCs are correctly configured as neighboring frequencies of each cell.
l If the configurations are correct, go to Step 6.
l If the configurations are incorrect, run the MOD EUTRANINTERNFREQ command to correct them. Then, check whether the CA-related counters provided in 6.5
Performance Monitoring produce non-zero values. If the counters produce non-zero values, no further action is required. If the counters retain the value of 0, go to Step 6. Step 6 Run the DSP PCCSCELLLIST command and view PCC Downlink EARFCN and SCC
Downlink EARFCN in the command output to check whether the number of SCells dynamically configured for each cell has reached eight.
l If the number has reached eight, wait 15 minutes and check again. If the check finds that CA takes effect, no further action is required. If CA still does not work, contact Huawei engineers.
l If the number is less than eight, go to Step 7.
Step 7 Run the MOD CAMGTCFG command with Carrier Aggregation A4 RSRP threshold set to -140. Run the DSP PCCSCELLLIST command to check the SCells dynamically
configured for the PCell.
l If SCells are displayed in the command output, enable a CA UE to access the network in the overlapping area of the PCell identified by PCC Local Cell ID and one of the SCells identified by SCC Local Cell ID.
l If no SCell is displayed in the command output, enable a CA UE to access the network in the overlapping area of the PCell and a potential SCell.
Step 8 Start Uu interface tracing. When the CA UE accesses the network, observe as follows: l If CA-related counters provided in 6.5 Performance Monitoring produce non-zero
values, these counters had the value of 0 because there was no CA UE on the network. No further action is required.
l If the RRC_CONN_RECFG message indicates that the eNodeB configures an SCell for the UE, but the CA-related counters in 6.5 Performance Monitoring still retain the value of 0, contact Huawei engineers.
l If the eNodeB does not deliver an RRC_CONN_RECFG message to configure an SCell for the UE, contact Huawei engineers.
----End