Nokia Help2 PDF

12/21/2019 Alarms
Alarm Reference > 33. Airscale FDD > Alarms

Alarms
Alarms
Note: Some alarms that the 5620 SAM can raise against this device may not be listed in this chapter. Associating alarms with specific NE types is an ongoing effort. If the 5620 SAM raises an alarm against this device type,
and the alarm is not described in this chapter, see Chapter 50, Unspecified NE.
Table 12243: ActiveAbnormalCondition
Alarm Attributes Applicable major release
Name: ActiveAbnormalCondition (3938) Severity: major Release:

Type: activeAbnormalConditionAlarm Specific problem: Not Applicable FL16A
Package: netw.ActiveAbnormalCondition Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: ActiveAbnormalConditionState
Description: The alarm is an indication for abnormal condition on NE.
Raising condition: ('abnormalCondition' EQUAL 'true')
Clearing condition: ('abnormalCondition' EQUAL 'false')
Remedial action: This alarm is raised when there is a abnormal state indication on NE.
Table 12244: AGWDiameterPeerDown
Name: AGWDiameterPeerDown (844) Severity: indeterminate Release:

Type: EpcAlarm Specific problem: Not Applicable FL16A
Package: lte.AGWDiameterPeerDown Implicitly cleared: true
Raised on class: lte.AGWDiameterPeer Default probable cause: EPSPeerDown
Description: The alarm is raised when the path management state of a Diameter peer changes to a state other than Up.
Raising condition: ('Path Management State' NOT EQUAL 'Active')
Clearing condition: ('Path Management State' EQUAL 'Active')
Remedial action: A Ga reference point (peer) is operationally down for one of the following reasons: the underlying IP or physical interface is down, the far end peer is down or the underlying transport between this NE and
the peer NE is down. To resolve the issue ensure that the IP/physical interface is up, check that the far end peer is operational and check that the underlying transport network is up.
Table 12245: AUTO_NEGO_MIS_MATCH

Name: AUTO_NEGO_MIS_MATCH (11513) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: AUTO NEGO MIS MATCH FL16A
Package: racfl.AUTO_NEGO_MIS_MATCH Implicitly cleared: true
Raised on class: racfl.MRBTS Default probable cause: INDETERMINATE
Description: AUTO NEGO MIS MATCH This alarm indicates that there is a mismatch between the BTS configuration and the auto-negotiation result. If the alarm is active, a synchronization loop is possible.
Remedial action: Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: Try with local management or site support equipment. Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone: Confirm that the
Ethernet Synchronization master/slave settings are correct on the Flexi Zone Micro BTS or Flexi Zone Access Point and backhaul equipment. Note: The Flexi Zone Micro BTS and Flexi Zone Access Point only support
slave mode.
Table 12246: BareMetalReachabilityDown
Name: BareMetalReachabilityDown (10273) Severity: major Release:

Type: virtualPortAlarm Specific problem: Not Applicable FL16A
Package: dctr.BareMetalReachabilityDown Implicitly cleared: true
Raised on class: dctr.BMDevice Default probable cause: BareMetalReachabilityDownOrDeleted
Description: The alarm is raised when Bare Metal server is reachability down.
Raising condition: (('bgpReachabilityState' NOT EQUAL '0'))
Clearing condition: (('bgpReachabilityState' EQUAL '0'))
Remedial action: This alarm can be cleared when bare metal device BGP prefix is up. Check for virtual switch controller down or virtual switch down or interface/port down in underlay network (hence the BGP prefix not
advertised).
Table 12247: BASE_STATION_CONNECTIVITY_DEGRADED
Name: BASE_STATION_CONNECTIVITY_DEGRADED (11514) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BASE STATION CONNECTIVITY DEGRADED FL16A
Package: racfl.BASE_STATION_CONNECTIVITY_DEGRADED Implicitly cleared: true
Description: BASE STATION CONNECTIVITY DEGRADED A major fault (or faults) has occured in the base station interface. Check the reason for the fault from the supplementary text field of the alarm. The effect of the
fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels
the alarm when the fault has been corrected.
GTP-U Path Failure

FAULT ID
6150: EFaultId_GtpuPathFailure
https://infocenter.nokia.com/public/5620SAM140R7A/index.jsp?topic=%2FSAM_AR%2Fhtml%2FNokiaFDDAirscale9891.html 1/148
12/21/2019 Alarms
MEANING
In GTP-U supervision, a network element did not respond to the GTP-U: Echo Request message within the allotted time.
INSTRUCTIONS
1. Check the GTP-U path supervision configuration of the eNB.
2. Check if the supervised network element is operating correctly.
3. Check the communication equipment between the eNB and the supervised network element.
In case actDualUPlaneIpAddress =" true, the S-GW might still be reachable although an alarm caused by fault 6150 is reported.
Check whether other alarms caused by fault 6150 are active, and check whether all GTP-U paths to the S-GW are concerned or not. If you find that all GTP-U paths t
FAULT NAME
M3 interface recovery failure
FAULT ID
6850: EFaultId_M3ResetRetryOut
MEANING
M3 interface reset has failed after several attempts. This indicates that a severe failure has occurred. There might be some configuration problem, there is no M3
INSTRUCTIONS
Note: Perform the steps below in the listed order until the alarm disappears.
1. Check the availability of MME.
2. Check the connection with MME.
3. Disconnect and reconnect MME.
FAULT NAME
M3 interface setup failure
FAULT ID
6851: EFaultId_M3SetupFailure
MEANING
There is no M3 connectivity to an MME, the MME has failed, and so on. If the fault is canceled, autonomous recovery actions (reset) have solved the fault situatio
INSTRUCTIONS
Note: Perform the steps below in the listed order until the alarm disappears:
1. Check availability of MME.
2. Check other faults on MME and BTS.
3. Check the parameters related to M3 interface in the BTS and MME.
4. Reset the BTS.
FAULT NAME
RIM interface error
FAULT ID
6323: EFaultId_RimInterfaceError
MEANING
1. An RIM association could not be established because an RIM Error PDU has been received for an RIM-enabled GERAN neighbor cell.
2. An RIM Application Error has been detected.
3. S1 links to all configured MMEs are active, but the routing of RIM PDU to the RIM-enabled WCDMA neighbor cell is not available.
INSTRUCTIONS
Check the value of the parameter "rimStatus" in LNADJG or LNADJW (according to the alarm source) objects to find all impacted RIM associations.
If only a few LNADJG or LNADJW objects have "rimStatus" Unavailable, check if LNADJG or LNADJW identifiers (cell global ID) of related GERAN or UTRAN cells are co
If many LNADJG or LNADJW objects have "rimStatus" Unavailable, check the connectivity to GSM or WCDMA network (MME<->SGSN<->BSC).
Note that only one alarm for one PLMN is raised due to the RIM faults for GERAN and only one for UTRAN, no matter how many LNADJGs or LNADJWs are affected at a gi
FAULT NAME
RIM interface timeout
FAULT ID
6322: EFaultId_RimInterfaceTimeout
MEANING
A RIM request to the serving BSS has failed after several attempts. This means that the System Information for the related GERAN or UTRAN neighbor cells is not re
INSTRUCTIONS
Check the value of the parameter "rimStatus" in LNADJG or LNADJW (according to the alarm source) objects to find all impacted RIM associations.
If only a few LNADJG or LNADJW objects have "rimStatus" Unavailable, check if the LNADJG or LNADJW identifiers (cell global ID) of the related GERAN or UTRAN cell
If many LNADJG or LNADJW objects have "rimStatus" Unavailable, check the connectivity to the GSM or WCDMA network (MME<->SGSN<->BSC).
Note that only one alarm for one PLMN is raised due to the RIM faults for GERAN, and only one for UTRAN no matter how many LNADJGs or LNADJWs are affected at a gi
FAULT NAME
S1 interface recovery failure
FAULT ID
6317: EFaultId_S1ResetRetryOut
MEANING
The S1 interface reset has failed after several attempts. This indicates that a severe failure has occurred: there is some configuration problem; there is no S1 c
INSTRUCTIONS
1. Check the availability of the MME.
2. Check the connection with the MME.
3. Disconnect and reconnect the MME.
FAULT NAME
S1 interface setup failure
FAULT ID
6308: EFaultId_S1SetupRetryOut
MEANING
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:
There is no S1 connectivity to an MME.
The fault is generated if the S1 setup procedure has subsequently been attempted but failed the number of times equal to "maxS1SetRetry".
Flexi Zone Micro FDD, Flexi Zone Micro TDD:
There is no S1 connectivity to an MME, the MME has failed, and so on. If the fault is cancelled, autonomous recovery actions (reset) will solve the fault situatio
INSTRUCTIONS
12/21/2019 Alarms

2. Check other faults on the MME and BTS.
3. Check the parameters related to the S1 interface in the BTS and MME.
4. Reset the BTS.
FAULT NAME
S1 SCTP path failure
FAULT ID
6204: EFaultId_S1SctpPathAl
MEANING
One of the transport paths (SCTP) in SCTP connection to the MME has failed. This is only applicable when SCTP multi-homing is supported. An alternate transport pa
INSTRUCTIONS
1. Check whether the transport path is alive.
2. Check the configuration of transport addresses at MME.
FAULT NAME
Toggling: <Fault name>
FAULT ID
4026: EFaultId_TogglingAl
MEANING
This alarm is used to inform the operator that another BTS fault (the original fault) is toggling.
The alarm that is related to the original fault is suppressed and the new alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is raised.
Toggling alarms that are related to the original faults are suppressed until the toggling condition is cleared.
The severity of this BTS fault is the same as the severity of the original
toggling BTS fault.
INSTRUCTIONS
1. Check the fault name of the toggling BTS fault.
2. Follow the instructions of the toggling BTS fault to clear the problem.
Note: Detailed information about the toggling frequency can be found in the alarm history file, which can be downloaded using BTS Site Manager. The log file is a
FAULT NAME
Transport layer connection failure in M3 interface
FAULT ID
6205: EFaultId_M3SctpEndpointAl
MEANING
The transport path (SCTP) for connection to MME has been broken. The reason for this can be an unplugged cable to MME. No transport path is available to pursue op
INSTRUCTIONS
1. Check the connection with MME, particularly whether the M3 link is broken.
2. Check if the MME is operational.
3. Check if the speed and duplex setting of eNB M3 port is consistent with switch port, which is connected directly to the eNB for example both "Autodetect" or bo
If this fault happens right after a commissioning or a configuration change, verify the following configuration data: IP address of the MME.
FAULT NAME
Transport layer connection failure in S1 interface
FAULT ID
6202: EFaultId_S1SctpEndpointAl
MEANING
The transport path (SCTP) for connection to the MME is broken. This might be because of an unplugged cable to the MME. There is no transport path available to con
INSTRUCTIONS
1. Check the connection with the MME, accordingly, based on whether the S1 link is broken.
3. Check if the speed and duplex setting of the eNB S1 port is consistent with the switch port that is connected directly to the eNB (for example, they are both "
If this fault happens right after a commissioning or a configuration change, verify the IP address of the MME.
FAULT NAME
Transport layer connection failure in X2 interface
FAULT ID
6203: EFaultId_X2SctpEndpointAl
MEANING
The transport path (SCTP) for connection to an adjacent BTS is broken. This might be because of an unplugged cable to the adjacent BTS. There is no transport path
INSTRUCTIONS
Note: Perform the steps below in the listed order until the BTS fault disappears:
1. Check the connection with the adjacent BTS based on whether the X2 link is broken.
2. Check if the adjacent BTS is operational.
If this fault happens right after a commissioning or a configuration change, verify the IP address of the adjacent BTS.
FAULT NAME
X2 interface recovery failure
FAULT ID
6303: EFaultId_X2ResetRetryOut
MEANING
The X2 interface reset has failed after several attempts. This indicates that a severe failure has occurred. For example, there is some configuration problem, the
INSTRUCTIONS
1. Check the availability of the adjacent BTS.
2. Check the connection with the adjacent BTS.
3. Disconnect and reconnect the adjacent BTS.
FAULT NAME
X2 interface setup failure
FAULT ID
12/21/2019 Alarms
6304: EFaultId_X2SetupRetryOut
MEANING
There is no X2 connectivity to an adjacent BTS, the adjacent BTS has failed, and so on.
INSTRUCTIONS
1. Check the connectivity to the related adjacent BTS.
2. Check other faults.
3. Check the parameters related to the X2 interface of the adjacent BTS.
4. Reset the BTS."
Table 12248: BASE_STATION_CONNECTIVITY_LOST
Name: BASE_STATION_CONNECTIVITY_LOST (11515) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BASE STATION CONNECTIVITY LOST FL16A
Package: racfl.BASE_STATION_CONNECTIVITY_LOST Implicitly cleared: true
Description: BASE STATION CONNECTIVITY LOST A critical fault (or faults) has occured in the base station interface. Check the reason for the fault from the supplementary text field of the alarm. The effect of the fault on
the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels the
alarm when the fault has been corrected.
FAULT NAME
S1 interface recovery failure
FAULT ID
6317: EFaultId_S1ResetRetryOut
MEANING
The S1 interface reset has failed after several attempts. This indicates that a severe failure has occurred: there is some configuration problem; there is no S1 c
INSTRUCTIONS
FAULT NAME
S1 interface setup failure
FAULT ID
6308: EFaultId_S1SetupRetryOut
MEANING
There is no S1 connectivity to an MME.
The fault is generated if the S1 setup procedure has subsequently been attempted but failed the number of times equal to "maxS1SetRetry".
There is no S1 connectivity to an MME, the MME has failed, and so on. If the fault is cancelled, autonomous recovery actions (reset) will solve the fault situatio
INSTRUCTIONS
2. Check other faults on the MME and BTS.
3. Check the parameters related to the S1 interface in the BTS and MME.
4. Reset the BTS.
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
Transport layer connection failure in S1 interface
FAULT ID
6202: EFaultId_S1SctpEndpointAl
MEANING
The transport path (SCTP) for connection to the MME is broken. This might be because of an unplugged cable to the MME. There is no transport path available to con
INSTRUCTIONS
1. Check the connection with the MME, accordingly, based on whether the S1 link is broken.
3. Check if the speed and duplex setting of the eNB S1 port is consistent with the switch port that is connected directly to the eNB (for example, they are both "
If this fault happens right after a commissioning or a configuration change, verify the IP address of the MME.
Table 12249: BASE_STATION_FAULTY
Name: BASE_STATION_FAULTY (11516) Severity: indeterminate Release:

Type: equipmentAlarm Specific problem: BASE STATION FAULTY FL16A
Package: racfl.BASE_STATION_FAULTY Implicitly cleared: true
12/21/2019 Alarms
Description: BASE STATION FAULTY A critical fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm. The effect of the fault on the functioning of the
network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels the alarm when the fault has
been corrected.
Verify the configuration of a BTS by checking the commissioning, cabling and correct installation of the units/modules at the BTS. Make sure the environment does
Before a unit/module is replaced at the BTS, the site should be reset to recover from any temporary faults which might have caused the malfunctioning of the unit/
In case of the FSM failure (FSM or FSM sub-unit is reported as source) it is possible that other units are also reported as faulty since it is impossible for them
Below is the list of BTS fault(s) which may have caused this alarm in BTS FL16A/TL16A release. In the case of an earlier SW release and if you need more detailed
FAULT NAME
Antenna link is down
FAULT ID
476: EFaultId_Rp3BusError
MEANING
The antenna (RP3) link is down. The transmitter or receiver drops from synchronization.
INSTRUCTIONS
1. Restart the BTS.
2. If that does not help, replace the alarming module.
Flexi BTS FDD/TDD: In case the FSP is causing the alarm, replace the FSM because the alarm is related to the fixed FSP inside the FSM.
Flexi BTS FDD/TDD, AirScale BTS FDD/TDD: If FBBx or ABIx is causing the alarm, replace the FBBx or ABIx.
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna: Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Anten
FAULT NAME
AP blocked
FAULT ID
4260: EFaultId_ApBlockedAl
MEANING
The Flexi Zone Access Point is blocked by the BTS Site Manager. This is done to avoid fault indications that might be raised during a Flexi Zone Access Point main
INSTRUCTIONS
To cancel the fault, unblock the Flexi Zone Access Point.
FAULT NAME
Baseband bus configuration of <x> was rejected
FAULT ID
1811: EFaultId_BbBus_ConfFailedAl
MEANING
The baseband-bus-related configuration of <x> has been rejected by the HW SW, DSP, or RF SW.
INSTRUCTIONS
Replace the alarming module.
1. Download the correct configuration.
2. Reset the BTS.
3. Replace the BTS.
Flexi Zone:
2. Reset the Flexi Zone Access Point from the BTSSM.
3. Replace the Flexi Zone Access Point.
Flexi Zone SFN Antenna:
2. Reset the Flexi Zone SFN Antenna from the BTSSM.
3. Replace the Flexi Zone SFN Antenna.
FAULT NAME
Baseband bus failure
FAULT ID
3020: EFaultId_BaseBandBusFailure
MEANING
The Flexi BTS has detected an abnormal operation or a failure in the BTS
internal or external (optical link) baseband bus. The failure cannot be
attributed to a specific module and there are several possible fault sources.
INSTRUCTIONS
Note: Perform the steps below in the listed order until the BTS fault disappears.
1. Check the other active BTS faults and act accordingly.
2. Check the cables between the System Module and RF Module.
3. Reset the RF Module and/or System Module, depending on the alarm source:
a. Reset the RF Module by blocking and unblocking it.
b. Reset the System Module by blocking and unblocking it.
4. Replace the alarming RF Module.
5. If the System Module is the source, or replacing the RF Module does not clear the fault situation, replace the alarming System Module.
FAULT NAME
Baseband resources mapping to cells failure
FAULT ID
12: EFaultId_TcomConfigAl
MEANING
A failure is detected when the eNodeB O>M; system presents available FSPs to C-plane software in order to map FSPs to a cell. The FSPs related to the faulty opera
INSTRUCTIONS
1. Block and unblock the BTS.
2. Perform a power-off reset.
3. If steps 1 and 2 do not help, replace the module that is causing the
alarm.
12/21/2019 Alarms
FAULT NAME
BB bus reception error (summing device)
FAULT ID
2016: EFaultId_Muksu_SMTimeOffAl
MEANING
The master frame in the received baseband bus frame is not in the correct place related to the internally-generated master frame pulse. Either the frame has been
INSTRUCTIONS
1. Check the cables between the system module and the RF module, the cable between the FBBx/ABIx module and the RF module, and the cable between the system module
2. Replace the unit that causes the alarm (system module or FBBx/ABIx).
FAULT NAME
BB bus transmission error
FAULT ID
2017: EFaultId_Muksu_SRx10b8bAl
MEANING
A decoding error has been detected in the baseband internal link. The data packet is lost, or the content is corrupted.
This situation also occurs when the links are not synchronized with each other.
INSTRUCTIONS
1. Check the cables between the system module and the RF module, and the cable between the FBBx/ABIA module and the RF module.
2. Reset the system module.
3. Replace the alarming module (system module).
FAULT NAME
Boot configuration inconsistency detected
FAULT ID
4102: EFaultId_BootConfigurationInconsistencyAl
MEANING
During SW update, the configurations of the active and passive SW in the HW unit have been detected to be the same. Active and passive SW configurations are compa
- before SW download
- during SW activation, before active and passive SW switch
- during start-up
INSTRUCTIONS
1. Block/unblock the Flexi Zone Micro BTS to reset.
2. If blocking or unblocking the Flexi Zone Micro BTS does not solve the problem, replace the faulty Flexi Zone Micro BTS.
Flexi Zone Access Point, Flexi Zone SFN Antenna:
None
FAULT NAME
BTS blocked
FAULT ID
50: EFaultId_BTSBlockedAl
MEANING
The BTS is blocked with the BTS Site Manager. The purpose is to avoid fault indications that might be raised during a BTS maintenance task.
INSTRUCTIONS
Unblock the BTS to cancel the fault. Unblocking the BTS causes a BTS reset.
FAULT NAME
BTS file error
FAULT ID
1802: EFaultId_FileRequestFlashAl
MEANING
A software download to FSP, DSP, ABIx or FR has failed.
INSTRUCTIONS
Note: Perform the following steps in the listed order until the fault disappears:
1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template.
2. Download two different software packages so that the faulty file is removed from the BTS.
3. Download the software again.
4. Replace the System Module.
FAULT NAME
BTS internal SW management problem
FAULT ID
3090: EFaultId_BtsInternalSwManagementProblem
MEANING
A software update to a module or sub-assembly has failed, or a corrupted SW file has been detected in the FLASH.
INSTRUCTIONS
1. Check the other active BTS faults. If the ROM disk is corrupted, change the alarming module.
2. Reset the RF Module and/or System Module (depending on the fault source) by blocking/unblocking it.
3. Update and activate the SW to the BTS.
4. Check the SW files.
5. Replace the alarming module.
1. Check the other active Flexi Zone Micro BTS or Flexi Zone Access Point faults. If the ROM disk is corrupted, change the Flexi Zone Micro BTS or Flexi Zone Acce
2. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point by blocking/unblocking it.
Flexi Zone:
1. Check the other active Flexi Zone Access Point faults. If the ROM disk is corrupted, change the Flexi Zone Access Point.
2. Reset the Flexi Zone Access Point to trigger new SW load.
1. Check the other active Flexi Zone SFN Antenna faults. If the ROM disk is corrupted, change the Flexi Zone SFN Antenna.
2. Reset the Flexi Zone SFN Antenna to trigger new SW load.
12/21/2019 Alarms
FAULT NAME
BTS Location Lock violation detected
FAULT ID
4284: EFaultId_LocationLockViolation
MEANING
A Location Lock violation has been detected after a BTS reboot.
1. The distance between the newly-acquired BTS position and the GNSS position that is stored in the Location Lock evidence file exceeds the configured limit.
2. The newly-configured parameters (IP address of the first routing hop, physical subnet address of the BTS, or MAC address of the first routing hop) do not match
The integrity check of the Location Lock evidence data has failed after a BTS reboot.
1. The Location Lock evidence file is missing.
2. The Location Lock evidence file has failed P7 signature validation.
INSTRUCTIONS
1. If the BTS detects a Location Lock violation:
- If the BTS has been relocated without authorization, the alarm is expected.
- If the BTS relocation is authorized, disable the Location Lock feature and then re-enable it to reacquire the correct Location Lock evidence.
2. If the BTS detects a missing or corrupted Location Lock evidence:
- Disable the Location Lock feature and then re-enable it in order to recover.
- If, during the above operation, the BTS has reported fault 4283:EFaultId_LocationLockFailed, replace the faulty device.
FAULT NAME
BTS master clock tuning failure
FAULT ID
1818: EFaultId_Ov_OscAl
MEANING
The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is less than or equal to the Min.OcxoControlValue.Alarm.Set value specified i
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:
The master clock frequency is tuned to within 5% of its minimum or maximum offset. The Flexi Zone Micro BTS or Flexi Zone SFN Antenna does not use DAC tuning.
INSTRUCTIONS
Note: Perform the steps below in the listed order until the fault disappears:
1. Check the other alarms of the BTS and FTM and act accordingly.
2. If there are no other synchronization-related alarms active. Start the fast tuning with the BTS Site Manager.
3. Reset the site. Run fast tuning again.
4. Check the reference signal accuracy by measuring it with a frequency counter (requires a good timebase for the counter). The reference signal can be found from
5. If that does not help, replace the system module.
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:
This fault is most likely the result of a BTS hardware problem, or a reference source that is being followed by the BTS that is in a faulted condition, thereby pr
1. Identify the currently selected synchronization reference source of the BTS with the active 1818 fault. If it is a transport-based reference source that involv
2. If the BTS uses its GPS reference source while the 1818 fault, or if the 1818 fault, persists for more than two hours after correcting, and problems associated
FAULT NAME
BTS or unit temperature too high
FAULT ID
4182: EFaultId_BtsTempTooHighAl
MEANING
The temperature of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has exceeded the predefined threshold.
INSTRUCTIONS
1. Validate if the ambient temperature is within the specifications and if no foreign debris has accumulated on the unit.
FAULT NAME
BTS or Unit temperature too low
FAULT ID
4183: EFaultId_BtsTempTooLowAl
MEANING
The temperature of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has exceeded the thresholds for operation.
INSTRUCTIONS
None
FAULT NAME
BTS reference clock missing
FAULT ID
3080: EFaultId_BtsReferenceClockMissing
MEANING
This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the configured synchronization reference signal, if
Background information:
There is configurable synchronization priority list in the FlexiBTS, AirScaleBTS.
Normally, all the Flexi BTS sources are not in use at the same time (it depends on the network planning and BTS configuration). During BTS start-up, the available
The source for the TRS can be TDM interface signal (for example, E1, T1, and so on), physical layer Synchronous Ethernet (SyncE) signal or application layer Timin
The GPS source (if provisioned) is the highest priority reference source. The GPS source is considered to be unusable as a reference source if it is not tracking
The BTS supports a ToP or SyncE reference source that has configurable priorities relative to each other through the "synchroSourceList" parameter.
INSTRUCTIONS
Depending on the installed and commissioned synchronization source(s) listed in the "Meaning" section, see the commissioned synchronization option below and perfo
GPS receiver (PPS source):
1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal wh
2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.
3. There might be a malfunction in the BTS. Perform a BTS site reset.
4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors.
5. There might be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.
External 2.048 MHz signal:
1. If there is an external 2.048 MHz signal source commissioned at the BTS site, check the BTS faults of that device and act accordingly. If this does not help, c
12/21/2019 Alarms
FTM reference (TDM, SyncE or ToP as source):
1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: The FTM unit operates so that if it is not locked to a sync
2. Check the alarms of the FTM unit and act accordingly.
3. Check the synchronization settings of the FTM unit.
5. There might be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally, the reason is not an equipment failur
If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if performing a BTS site reset does not help,
Depending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned synchronization option below and perform t
GPS source:
1. If a loss of communication or the 1 PPS clock is associated with the Flexi Zone Micro BTS or Flexi Zone SFN Antenna integrated GPS receiver, perform a (remote)
SyncE or ToP as source:
1. Check the alarms of the Flexi Zone Micro BTS or Flexi Zone SFN Antenna unit and act accordingly.
2. Verify that the Primary Reference Clock (PRC) or Master Clock of the associated Synchronous Ethernet or Timing over Packet (ToP) source is active and providing
3. If the associated reference source fault persists after successfully performing steps 1 and 2 above, a Flexi Zone Micro BTS or Flexi Zone SFN Antenna replaceme
FAULT NAME
BTS reset required
FAULT ID
4001: EFaultId_BtsResetNeededAl
MEANING
This fault notifies the operator that the BTS must be reset to solve a problem that has been discovered by the BTS O>M; system, and that the BTS O>M; will not tri
1. The BTS has detected a commissioned (configured in SCF) extension baseband
module (for example, FBBC) that was not detected during BTS startup. Thus, the BTS must be reset to take the module into use.
2. The BTS has again detected a working FSP that has already been used but has then failed, or is disconnected, and cannot be taken into use without a BTS reset.
Note: LCR supported by the FSP is reported as the fault source in this case.
3. An FSP overheat has occurred. The FSP must be restored to normal temperature, and the BTS must be reset, to put the card back into use.
4. An internal problem has been detected, and the BTS cannot continue start-up
without a BTS reset.
5. The BTS O>M; system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed
Note: The affected LCR is reported as the fault source in this case.
6. In BTS runtime, the BTS O>M; system has detected resources necessary to cell setup that were not detected during BTS start-up, for example, commissioned radio
7. BTS O>M; has detected an extension baseband module, for example, FBBC, on the same QSFP port, which is different than the previously-removed baseband card, for
8. An FSP unit was not ready during BTS start-up, for example, because of a unit boot SW update. The BTS must be reset to take the module into use.
9. The BTS has cleared an alarm and triggers an autonomous BTS reset to enable
normal BTS operability, but the BTS reset counter has been exceeded. The operator must perform a BTS reset to enable BTS operability.
10. There is an internal problem resulting in the failure of the activation or deactivation of snapshot collection triggered by SysLog substring. A BTS reset from
11. FDD only - Phase synchronization source was not available in BTS start-up,
and alarm with fault 4153 was raised. Phase synchronization source is available now. BTS reset is needed to activate features requiring network-level synchronizat
12. BTS cannot execute FSP or BTS autonomous recovery reset because of either of the following reasons:
- It will disable any working cell
- An internal BTS limitation
13. FSP card is lost or disconnected. A BTS reset is necessary to protect the BTS from a crash after the card hot insert.
14. FSP autonomous recovery reset has failed. A BTS reset is necessary to try to recover the FSP.
15. FSMr3 only - CRAN configuration for a cell has failed. A BTS reset is necessary to reconfigure CRAN.
16. There is an internal problem with the radio module configuration. A BTS reset is necessary to take the radio module into use. FR is the fault source in this c
17. FSP power on failed after fault 4077 (FSP overheated) is canceled. A BTS reset is needed to try to take the FSP into use.
18. Unauthorized RF module was detected. Corresponding RFM plug-in (partial property file) has been downloaded. BTS reset is needed in order to activate new plug-
Only case #10 is applicable for FZM.
INSTRUCTIONS
1. Check the alarm diagnostic information for the reason of the fault report before the reset.
2. Reset (block and unblock) the BTS.
FAULT NAME
BTS RF BB energy too high
FAULT ID
1975: EFaultId_BtsRfBbEnergyTooHighAl
MEANING
TX baseband power is too high.
INSTRUCTIONS
1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
2. If that does not help, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
BTS startup temperature out of specification.
FAULT ID
4184: EFaultId_BtsStartupTempOutOfSpecAl
MEANING
The temperature of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna is not in the specified range for operation during startup.
INSTRUCTIONS
1. Validate that the ambient temperature is within the specifications and that no foreign debris has accumulated on the unit.
2. Verify if the solar shield is installed.
FAULT NAME
BTS synchronization is missing during startup
FAULT ID
4160: EFaultId_BtsClockSourceOutOfSynchronizationDuringStartupAl
12/21/2019 Alarms
MEANING
The synchronization source of the BTS is not available when it works as synchronization slave during start-up.
INSTRUCTIONS
1. Check the cable connection between the synchronization master and its GPS.
2. Check the alarms in the synchronization master system module and act accordingly. Since the synchronization master is a separate system from the synchronizatio
3. Reset the synchronization master system module.
FAULT NAME
BTS vendor-specific file fault
FAULT ID
6262: EFaultId_InvalidVendorSpecificFile
MEANING
There has been an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup.
The fault is also detected when a vendor-specific file is missing.
INSTRUCTIONS
1. Check the other active BTS faults.
2. Reset the System Module by blocking and unblocking it.
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:
1. Check the other active BTS faults.
2. Reset the BTS by blocking and unblocking it.
5. Replace the Flexi Zone Micro BTS or Flexi Zone Controller.
FAULT NAME
Commissioning error: <x>
FAULT ID
3060: EFaultId_CommissioningError
MEANING
Some of the commissioning parameters are either missing or faulty, or there is a mismatch between them.
INSTRUCTIONS
1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard.
2. Load the correct commissioning file to the BTS.
FAULT NAME
Communication failure
FAULT ID
1806: EFaultId_CommunicationFailureAl
MEANING
Communication with an application has failed. It has not replied to the message that has been sent/resent to it.
INSTRUCTIONS
1. Make sure that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. Check the unit/module that is causin
2. Check the fault history.
FAULT NAME
Communication Loss on all S1 links and OAM link
FAULT ID
4295: EFaultId_CommLossOnAllS1LinksAndOamLinkAl
MEANING
Communication on all S1 links and OAM link has been lost.
INSTRUCTIONS
If this alarm is observed from the BTSSM, check the backhaul connection of the BTS.
FAULT NAME
Configuration and hardware mismatch
FAULT ID
4282: EFaultId_ConfigurationAndHardwareMismatchAl
MEANING
The detected hardware does not support the SCF configuration.
INSTRUCTIONS
1. Read the diagnostic information of the alarm.
2. If the diagnostic information is "IQ compression or forced link speed incorrect
in site configuration file", check what configurations are supported by
Nokia, correct IQ compression, or force link speed value in the Site Configuration File (SCF), and then re-commission the BTS.
3. If the diagnostic info is "Number of detected RET units in multiRET
is not consistent with site configuration file" or its equivalent information for RAE, correct the RET or RAE configuration to remove the extra entries, and then
FAULT NAME
Configuration error: <x>
FAULT ID
3070: EFaultId_ConfigurationError
MEANING
There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch in the BTS configuration.
INSTRUCTIONS
1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration.
2. Check that the BTS cell parameters from the Network management system match
the BTS HW configuration (for example, frequency, power).
3. Check the Network management system alarms for the alarming local cell (LCR).
4. Recommission the BTS to ensure that all parameters are correctly configured.
12/21/2019 Alarms
FAULT NAME
Configuration Failed
FAULT ID
4265: EFaultId_ApConfFailedAl
MEANING
The Flexi Zone AP is out of order because of a configuration problem, which prevents the FZAP from coming into service. This fault is only reported for non-fatal
INSTRUCTIONS
1. Check all alarms posted by the Flexi Zone Access Point prior to this fault.
2. Check the configuration of the FZAP against similarly-configured FZAPs of the same type.
3. Reset the Flexi Zone Access Point.
4. Reset the Flexi Zone Controller.
FAULT NAME
Connection to ToP master missing
FAULT ID
4058: EFaultId_TopRefClkMissingAl
MEANING
The reference clock monitoring has detected a loss of the ToP reference clock signal received from the master clock.
INSTRUCTIONS
Note: Perform the steps below in the listed order until the fault disappears.
1. Check the Ethernet interface functionality used by Timing Over Packet. Check if other faults related to the Ethernet interface exist.
2. Check Timing Over Packet configuration. Ensure that the Master clock IP address is configured properly and that the Master clock supports the given parameters.
3. Check the Master clock functionality.
4. Check that the IP connection between the Master clock and Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna is working.
FAULT NAME
DSP application fatal error
FAULT ID
6707: EFaultId_DspApplicationFatalErrAl
MEANING
A fatal error of the DSP Application SW has occurred.
Flexi BTS FDD, Flexi BTS TDD:
If an FSP in the BTS generates this fault, there is a malfunction in
the corresponding FSP sub-module.
If all FSPs generate this fault, there is a malfunction in the FSM.
If an FSP in the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna generates this fault, there is a malfunction in the whole Flexi Zone Mic
INSTRUCTIONS
1. Reset the System Module.
2. Replace the System Module, or FBBx or ABIx module (according to the fault source).
Perform the steps below in the listed order until the fault disappears.
2. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
DSP concurrent crash error
FAULT ID
6709: EFaultId_DspConcurrentCrashErrAl
MEANING
A digital signal processing (DSP) concurrent crash has occurred (a fatal error was indicated in one of the DSP cores that belong to the same chip).
INSTRUCTIONS
1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.
2. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone
SFN Antenna.
FAULT NAME
DSP platform fatal error
FAULT ID
6706: EFaultId_DspPlatformFatalErrAl
MEANING
A fatal error of the DSP HWAPI SW has occurred.
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
eNB configuration failed
FAULT ID
6293: EFaultId_EnbConfigurationFailedAl
MEANING
The BTS configuration has failed in the C-Plane.
INSTRUCTIONS
Block and unblock the BTS.
FAULT NAME
External GPS receiver in holdover
FAULT ID
4210: EFaultId_ExtGpsInHoldoverAl
MEANING
The external GPS or GNSS receiver module has lost satellite visibility and is currently operating in holdover mode.
INSTRUCTIONS
1. One of the most common reasons for this fault indication (especially occasional indications) is that the GPS or GNSS antenna installation has not been done pro
2. Check the other possible alarms or fault indications of the GPS or GNSS receiver and the BTS, and act accordingly.
3. There might be a malfunction in the GPS or GNSS receiver. Perform a (remote) power reset for the GPS or GNSS receiver module.
4. If there is only the alarming GPS or GNSS receiver connected to the GPS or GNSS antenna, check the antenna power feeding setting in the GPS or GNSS receiver se
5. Check the connection between the GPS or GNSS receiver module, and GPS or GNSS antenna. Note that one antenna might be shared at the BTS site between many GPS o
6. Perform a local or physical power reset for the alarming GPS or GNSS receiver module.
7. There might be an HW fault in the GPS or GNSS antenna and/or possible antenna line splitter, possible line amplifier, or lightning or surge protector devices.
8. There might be an HW fault in the GPS or GNSS receiver module. Check the operation and change the GPS or GNSS receiver module if needed.
FAULT NAME
Externally triggered DSP fatal error
FAULT ID
6708: EFaultId_ExternallyTriggeredDspFatalErrAl
MEANING
The BTS has purposely triggered a GPIO reset for the DSP.
If an FSP in the BTS generates this fault, there is a malfunction in the whole BTS.
INSTRUCTIONS
2. Replace the System Module, or FBBx or ABIx module (according to the fault source)
FAULT NAME
Failure in optical interface
FAULT ID
3030: EFaultId_FailureInOptical_Rp3Interface
MEANING
The AirScale/Flexi BTS (System Module) has detected an abnormal operation or a failure
in an optical RP3 interface between two modules .
The failure cannot be attributed to a specific module but there are several
possible fault sources, for example, fiber optical cable, SFP, or individual module.
INSTRUCTIONS
1. PROBLEM IDENTIFICATION
Ensure you have the latest documentation available:
Use the Operating Documentation from of the Released/Supported Configurations to
check the SW and HW details.
Check the SW version, List of Generic Faults (LGF), and Technical Notes for any
known faults related to SW in use.
Note: Use the fault-specific troubleshoot instructions from NOLS;" Failure
in optical RP3 interface trouble shooting" document as a detailed guidance
for remote and site-specific investigations; On Site Investigations and Measurements.
2. REMOTE INVESTIGATIONS
Check if anything has changed in the system. What triggered the alarm:
SW updates, configuration, commissioning or Carrier power changes, RF sharing
activations or HW unit swaps. If the alarm appeared after any changes, revert to
previous status if possible and see if the problem disappeared.
Check if the alarm depends on traffic; compare to similar cases in network. How
wide is the problem (single case, one of few). If any other device or RFM
related alarms, the root cause can also be an external one (for example, connection box). Study the BTS alarm history of active and cancelled alarms, for example,
3. REMOTE ACTIONS
Reset the BTS. For ON-SITE INVESTIGATIONS and ON-SITE SPECIFIC MEASUREMENTS, see details to site investigation from the troubleshooting document.
FAULT NAME
Failure in replaceable baseband unit
FAULT ID
3003: EFaultId_FbiaFailureAl
MEANING
The BTS has detected an abnormal operation or a failure in the BTS replaceable
baseband unit.
INSTRUCTIONS
Note: Perform the steps below in the listed order until the BTS fault indication disappears:
2. Ensure that the plug-in type baseband unit is installed correctly.
3. Reset the alarming baseband unit.
4. Replace the alarming baseband unit.
FAULT NAME
Fatal OSE Error
FAULT ID
418: EFaultId_OseFatalErr
MEANING
The operating system (OSE) goes into the error handler with a fatal status. This might be caused by an out-of-memory situation.
12/21/2019 Alarms
AirScale BTS FDD/TDD, Flexi BTS FDD/TDD:
If only one FSP/ABIx in the BTS generates this fault, there is a malfunction in one of the FSP/ABIx submodules.
Flexi BTS FDD/TDD:
The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, an out of memory situation.
INSTRUCTIONS
2. According to the fault source replace either:
- the System Module (Flexi BTS FDD/TDD)
- FBBx/ABIx module (AirScale BTS FDD/TDD, Flexi BTS FDD/TDD).
Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
Faulty configuration of system modules
FAULT ID
1858: EFaultId_FaultyFcmConfigurationAl
MEANING
The synchronization set-up between a BTS configured as slave, and a BTS working as master has failed during BTS startup. A possible reason is that the master and
INSTRUCTIONS
Check that the WCDMA master system module is connected to the system module when the SCF parameter "syncMaster" =" "FALSE".
FAULT NAME
File System access failed
FAULT ID
4088: EFaultId_FileSystemAccessFailedAl
MEANING
File system access operations like file system mounting or file opening have failed.
INSTRUCTIONS
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:
Update the BTS SW, unless it is automatically updated by NetAct.
None
FAULT NAME
Firmware SW mismatch
FAULT ID
2056: EFaultId_SwMismatchAl
MEANING
The software update to the BTS has failed or the BTS software is corrupted.
INSTRUCTIONS
1. Switch to the most recently-active BTS configuration.
2. Retry the software update.
Flexi Zone (Flexi Zone Access Point):
1. Reset the Flexi Zone Access Point to trigger SW upgrade again.
Flexi Zone (Flexi Zone Controller):
1. Retry the embedded SW update manually.
2. If this does not help, switch to the latest active BTS configuration.
3. Retry the SW update.
1. Reset the Flexi Zone SFN Antenna to trigger SW upgrade again.
FAULT NAME
Flexi Zone Micro BTS system clock missing
FAULT ID
4188: EFaultId_FZMSysClkMissingAl
MEANING
Some of the generated system clock signals are missing, or the generated system clocks are not locked.
INSTRUCTIONS
FAULT NAME
FSP overheating
FAULT ID
4077: EFaultId_FspOverheatingAl
MEANING
The temperature of the FSP/ABIx board has exceeded the critical threshold value.
INSTRUCTIONS
1. Check the fans and ensure that the ambient temperature on the site is acceptable.
FAULT NAME
FSP subunit lost
FAULT ID
4341: EFaultId_FspSubunitLostAl
MEANING
An FSP (ABIx) subunit is unavailable (lost).
INSTRUCTIONS
AirScale BTS FDD, AirScale BTS TDD:
Note: Perform the steps below in the listed order until the fault is resolved:
1. Reset the BTS using block or unblock.
2. Replace the extension baseband module (ABIx) according to the fault source.
12/21/2019 Alarms
FAULT NAME
GPS Receiver alarm: control interface not available
FAULT ID
4011: EFaultId_GPSSystemElementAl
MEANING
The BTS has detected a communication problem with the GPS receiver.
The fault is ignored until the GPS receiver has reached the commissioned state.
INSTRUCTIONS
Perform the steps below in the listed order until the fault disappears, and if the fault does not get cancelled after autonomous GPS power reset (wait for five mi
Control Interface not available:
1. The BTS has detected a malfunction in the control interface of the GPS receiver. A possible reason is that the BTS and the GPS receiver do not support a common
2. Perform a (remote) BTS site reset for the whole BTS.
3. Perform a power reset for the whole BTS.
4. The cable between the GPS receiver and the BTS might be working incorrectly. Check if the pins of the connectors (on both ends of the cable) are free from oxid
5. The cable between the GPS receiver and the BTS might be faulty. Check the situation and change the cable if needed.
6. There might be a hardware fault in the GPS receiver. Check the operation and change the GPS module if needed.
7. There might be a hardware fault in the BTS System Module. Check the operation and change the System Module if needed.
1. The Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has detected a malfunction in the control interface of the GPS receiver. The possi
2. Perform a (remote) site reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
3. Perform a power reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
4. There might be a hardware fault in the GPS Receiver or the BTS or access point. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN An
FAULT NAME
GPS receiver alarm: not tracking satellites
FAULT ID
4122: EFaultId_GpsReceiverNotTrackingSatellitesAl
MEANING
The fault indicates poor GPS antenna installation.
INSTRUCTIONS
Not tracking satellites:
1. The most common reason for this fault indication is that the GPS antenna installation has not been done properly, that is, the sky visibility is not good enoug
3. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module, if needed.
FAULT NAME
Incompatible SW version detected
FAULT ID
23: EFaultId_IncompatibleSwVersionAl
MEANING
Incompatible software has been detected.
INSTRUCTIONS
Update the BTS with the compatible SW (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated b
In case of RF modules with factory SW loaded, SW update is a mandatory step.
FAULT NAME
Incorrect radio network parameters
FAULT ID
6252: EFaultId_FailureInNetworkPlanFile
MEANING
There was an opening, reading, or file content problem with a radio network
configuration file at the BTS startup, or at the activation of the delta configuration file. The detected problem can be a file handling problem (for example, ope
INSTRUCTIONS
1. Check the commissioning parameters with the BTS Site Manager Commissioning
Wizard.
Flexi Zone, Flexi Zone SFN Antenna:
1. Check the Additional Info field of the fault and use it as guide to troubleshoot the faulty FZAP or Flexi Zone SFN Antenna.
2. Check the configuration of the FZAP or Flexi Zone SFN Antenna.
3. Reset the Flexi Zone Access Point or Flexi Zone SFN Antenna.
4. Reset the Flexi Zone Controller, Flexi Zone Micro BTS, or Flexi Zone Access Point.
FAULT NAME
Internal MTU configuration failure
FAULT ID
4025: EFaultId_MtuConfigurationFailureAl
MEANING
The internal maximum transfer unit (MTU) configuration has failed on the FSP or FBB/ABIx.
INSTRUCTIONS
1. Reset the System Module that is causing the alarm.
2. Replace the System Module that is causing the alarm.
1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
2. Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
FAULT NAME
12/21/2019 Alarms
Invalid configuration file
FAULT ID
4036: EFaultId_InvalidConfigurationFileAl
MEANING
The commissioning file is corrupted, or an incorrect SCF file has been detected during BTS startup as follows:
1. Commissioning data: The commissioning file is corrupted, or a parameter has a missing or incorrect value.
2. RNW data: "RNW has wrong format," "RNW could not be parsed," "RNW has wrong schema," "Validation failed due to incompatible data," "no RNW cell managedObject i
The commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows:
1. Commissioning data: The commissioning file is missing, or a parameter has a missing or incorrect value.
2. RNW data: "RNW not found," "RNW has wrong format," "RNW could not be parsed," "RNW has wrong schema," "Validation failed due to incompatible data," "no RNW cel
INSTRUCTIONS
Check and correct the contents of the commissioning file.
1. Check and correct the contents of the commissioning file.
2. Recommission the BTS or Flexi Zone SFN Antenna with the valid commissioning file.
FAULT NAME
Master unit has lost connection to the slave unit
FAULT ID
4019: EFaultId_KeepAliveStatusErrorAl
MEANING
The connection to the FSP/ABIx or DSP has been lost, or the sub-module reports an error situation.
The connection to the DSP module has been lost.
INSTRUCTIONS
1. Reset the BTS.
2. Replace the faulty module.
FAULT NAME
Message routing problem in receiver (RX)
FAULT ID
2058: EFaultId_MuksuMsgRoutingFailedAl
MEANING
An interrupt is generated if a message does not get routed.
This is considered normal when DSPs are starting up and RP3 sync is done.
INSTRUCTIONS
If OptIf is the source:
1. Check the antenna mapping to the local cells in the commissioning file.
2. Depending which optical interface is notified as faulty check the cables between
- the System Module and RF Module, or the cable between the FBB module and the RF Module (Flexi BTS FDD/TDD),
- the cable between the ABIx module and the RF Module (AirScale BTS FDD/TDD).
3. Block and unblock the RF Module.
4. Perform a BTS reset.
5. Replace the RF module behind the optical link.
Flexi BTS FDD/TDD:
If FSP is the source:
1. Perform a System Module reset.
2. If that does not help, replace the System Module.
Flexi BTS FDD/TDD, AirScale BTS FDD/TDD:
If FBB/ABIx is the source:
2. If that does not help, replace the FBB/ABIx card.
FAULT NAME
No connection to Flexi transport submodule
FAULT ID
3511: EFaultId_NoConnectionToFtAl
MEANING
The connection to the Flexi Transport sub-module (FTM) or transport application is lost.
INSTRUCTIONS
Flexi BTS:
1. Reset the site.
2. Replace the Transport sub-module, which is located inside the System Module.
FAULT NAME
No connection to unit
FAULT ID
10: EFaultId_NoConnectionToUnitAl
MEANING
The connection to a module that belongs to the BTS configuration has been lost.
In case of SNMP radios, there is a problem with the optical interface or an internal fault, which results in a radio reset.
INSTRUCTIONS
1. Ensure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the module that is causing the alarm.
FAULT NAME
No downlink baseband data
FAULT ID
1976: EFaultId_RfNoDownlinkBasebandDataAl
MEANING
12/21/2019 Alarms
The RF does not detect downlink baseband data when at least one carrier is enabled. There might be a problem in software components which source downlink data, or
INSTRUCTIONS
None
FAULT NAME
Non-recoverable Synchronization Alignment Fault
FAULT ID
4273: EFaultId_SyncAlignNonRecAl
MEANING
The Flexi Zone Micro BTS/Flexi Zone Access Point/Flexi Zone SFN Antenna has encountered a significant synchronization alignment fault requiring that the BTS under
INSTRUCTIONS
Check for and resolve any faults related to any and all configured synchronization reference sources. If BTS is unable to resume operation or reliably stay in ope
A manual eNodeB reset and cell enable is necessary to acquire synchronization in the RIBS configuration.
FAULT NAME
Not able to synchronize baseband bus with <x>
FAULT ID
1815: EFaultId_BbBus_SyncFailedAl
MEANING
The baseband bus synchronization towards <x> has failed.
INSTRUCTIONS
Perform the recovery in the following sequence:
1. Check if the cable connecting the system module and radio module, or the cable connecting the extension baseband module and radio module is fixed firmly to the
2. Replace the cable.
3. Change the faulty module (FBBx/ABIx or FR).
4. If it does not help, replace the FCM/FCT (system module).
Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
FAULT NAME
Oven oscillator clock missing
FAULT ID
1819: EFaultId_OcxoClkMissAl
MEANING
The output signal of the OXCO is missing, and the FCM/FCT cannot deliver the 30.72 MHz System Clock required by the other units.
INSTRUCTIONS
1. Block/unblock the System Module.
FAULT NAME
Oven oscillator heating failure
FAULT ID
1817: EFaultId_Ov_Osc_HeatAl
MEANING
The OCXO warm-up takes too long, and the OCXO does not become active within a period of eight minutes from power-on. The ambient temperature might also be too low
INSTRUCTIONS
Replace the alarming System Module.
FAULT NAME
POST test failed
FAULT ID
69: EFaultId_Post_test_failedAl
MEANING
The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected.
INSTRUCTIONS
1. Reset the alarming unit or module.
2. Remove or reinsert the alarming unit or module.
3. Replace the alarming unit or module.
FAULT NAME
PPS reference missing
FAULT ID
1898: EFaultId_PpsRefMissAl
MEANING
1. The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver or the SyncHub master.
2. (TDD only) The PPS signal from the SyncHub master is unusable because its reported phase error is too large.
INSTRUCTIONS
1. Check the GPS receiver installation.
2. Check the GPS receiver status.
3. Check the connection between the GPS receiver and the FSM.
4. Check the cable or connection towards a SyncHub master when operating as SyncHub slave.
5. Check the status of the SyncHub master.
FAULT NAME
Reference clock missing in startup
FAULT ID
4153: EFaultId_PpsRefClcMissInStrtAl
MEANING
Phase synchronization has been commissioned at the btsSyncMode, but phase reference
clock is unavailable during a waiting period within the start-up procedure.
12/21/2019 Alarms
INSTRUCTIONS
Depending on the installed and commissioned synchronization sources, see the
commissioned synchronization options below and perform the steps in the listed
order until the BTS fault indication disappears:
3. Check the connection between the GPS receiver and FSM.
eNB is Sync hub slave and RF sharing is enabled:
1. Check if sync master provides sync signal.
2. Check the connection between sync master and sync slave.
3. Check sync settings at sync slave.
eNB is a part of CRAN cluster:
Perform all the steps from above.
TRS reference (ToP as source):
1. Check that the signal is being received from the ToP Master.
2. Check the TRS status.
3. Check the synchronization settings of the TRS unit.
BTS is Sync hub slave and RF sharing is enabled:
1. Remove the root cause that leads to the sync hub slave being not synchronized .
2) If there is a need to change settings, either perform remote re-commissioning through NetAct, or un-commission the BTS prior to re-commissioning using the Site
FAULT NAME
RF Unit temperature too high
FAULT ID
4185: EFaultId_RfTempTooHighAl
MEANING
The validated sensor temperature on the PA is higher than the predefined HW temperature.
INSTRUCTIONS
3. If those do not help, replace the BTS.
FAULT NAME
SFN Antenna blocked
FAULT ID
4348: EFaultId_AntBlockedAl
MEANING
The Flexi Zone SFN Antenna is blocked by the BTS Site Manager or WebUI. This is done to avoid fault indications that might be raised during an SFN Antenna mainten
INSTRUCTIONS
Unblock the Flexi Zone SFN Antenna to cancel the fault.
FAULT NAME
SFN Antenna cell deletion failure
FAULT ID
4356: EFaultId_SfnAntCellDeletionFailureAl
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point failed to delete the cell on the Flexi Zone SFN Antenna.
INSTRUCTIONS
1. Perform a reset of the Flexi Zone SFN Antenna.
2. If step above does not help, perform a reset of the BTS/FZAP.
3. If steps above do not help, replace the alarming module.
FAULT NAME
SFN Antenna cell reconfiguration failure
FAULT ID
4358: EFaultId_SfnAntCellReconfigurationFailureAl
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point failed to reconfigure the cell on the Flexi Zone SFN Antenna.
INSTRUCTIONS
FAULT NAME
SFN Antenna cell setup failure
FAULT ID
4355: EFaultId_SfnAntCellSetupFailureAl
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point failed to setup the cell on the Flexi Zone SFN Antenna.
INSTRUCTIONS
FAULT NAME
SFN Antenna cell shutdown failure
FAULT ID
4357: EFaultId_SfnAntCellShutdownFailureAl
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point failed to shut down the cell on the Flexi Zone SFN Antenna.
INSTRUCTIONS
FAULT NAME
SFN Antenna Configuration Failed
12/21/2019 Alarms
FAULT ID
4362: EFaultId_AntConfFailedAl
MEANING
The Flexi Zone SFN Antenna is out of order because of a configuration problem, which prevents the Flexi Zone SFN Antenna from coming into service. This fault is o
INSTRUCTIONS
1. Check all alarms posted by the Flexi Zone SFN Antenna prior to this fault.
2. Check the configuration of the Flexi Zone SFN Antenna against similarly-configured Flexi Zone SFN Antennas of the same type.
3. Reset the Flexi Zone SFN Antenna.
4. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point.
FAULT NAME
SFN Antenna registration failure
FAULT ID
4354: EFaultId_SfnAntRegistrationFailureAl
MEANING
THe Flexi Zone Micro BTS or Flexi Zone Access Point failed to register the Flexi Zone SFN Antenna.
INSTRUCTIONS
FAULT NAME
SFN Master initialization failure
FAULT ID
4359: EFaultId_PhyProxyIpConfigAl
MEANING
SFN Master PhyProxy module initialization has failed.
INSTRUCTIONS
1. Perform a reset of the BTS or FZAP.
2. If step above does not help, replace the alarming module.
FAULT NAME
Summing service default initialization failed
FAULT ID
4092: EFaultId_MurkkuDefaultInitFailedAl
MEANING
The summing service default configuration has failed.
INSTRUCTIONS
If FSM is the fault source:
1. Reset the system module. (Note that all cells, including those that are operational, will be reset.)
2. If a reset does not resolve the fault situation, replace the system module.
If FBB/ABIx is the fault source:
2. If a reset does not resolve the fault situation, replace the FBBx/ABIx module.
FAULT NAME
SW corrupted
FAULT ID
1850: EFaultId_SwCorruptedAl
MEANING
A corrupted SW file in the FLASH has been detected.
The unit cannot complete start-up.
INSTRUCTIONS
Update the SW to the BTS.
FAULT NAME
SWDistributionFailure
FAULT ID
4259: EFaultId_SwDistributionAl
MEANING
The Flexi Zone Controller has failed to upgrade the software on the Flexi Zone Access Point because of an HTTPD server configuration error, an error during startu
INSTRUCTIONS
1. When the Flexi Zone Access Point (FZAP) has failed to join the zone, restart HTTPD RG (through SCLI) and then reset the failed FZAPs.
2. When the SW upgrade has failed, retry the software load.
3. Restart the Zone Controller.
4. Replace the faulty device.
FAULT NAME
SW fallback
FAULT ID
4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl
4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl
4085: EfaultId_FallbackDueToTransportRequestAl
MEANING
4082:
The source unit has reached the maximum number of reset retries, that is, the source unit cannot successfully finish start-up after the SW update.
If BTS O&M has detected that the BTS can start with the previously-active SW version - BTS O&M processed consistent fallback and
1. the previously-active SW version is running in all HW units in the BTS and
2. the BTS is up and running.
Otherwise:
1. the previously-active SW version is not running in all HW units in the BTS and
2. the BTS is not up and running (recovery SW update is still supported).
Fault 4082 for FSP fallback can be canceled due to SW upgrade on FSP only.
In this case, an FSP reset to activate the new version of SW may cancel the fault.
The state of the fault is start/cancel for FSP SW fallback only.
4083:
The source unit has requested SW fallback because of a critical problem that had occurred during start-up after the SW update due to configuration data migration
12/21/2019 Alarms
Otherwise:
4085:
Transport SW on the source unit has indicated the need for a software fallback.
Otherwise:
INSTRUCTIONS
The BTS start-up was not successful.
If the fault is reported with alarms 7650, 7651, 7653 raised and SW is not consistent in the BTS, then NetAct autonomously triggers an SW update with immediate ac
1. The BTS will be onAir with the previously-running SW.
2. The SW will be consistent in BTS.
3. The BTS will report active SW fallback fault but with alarm 7651.
If the fault is reported with alarm 7651 and SW is consistent in BTS, then the operator should trigger SW update for the BTS to the requested SW version. After su
1. The BTS will be onAir with requested SW running.
3. SW fallback fault and the related alarm will be canceled.
Flexi Zone:
None
FAULT NAME
Synchronization holdover time expired
FAULT ID
4187: EFaultId_SyncHoldoverTimeExpiredAl
MEANING
The Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has been operating in the synchronization holdover mode (because of a continued loss
INSTRUCTIONS
Address faults associated with any and all configured synchronization reference sources. This fault will clear, and RF transmissions can resume when the Flexi Zon
FAULT NAME
Synchronization master missing
FAULT ID
4114: EFaultId_SynchronizationMasterMissingAl
MEANING
Synchronization is lost when the system module is working as a synchronization slave system module. This usually indicates that a synchronization master system mo
INSTRUCTIONS
Perform the steps in the listed order until the fault is resolved.
1. Wait for the startup to be completed if a synchronization master system module has been reset.
2. If fault 1858: EFaultId_FaultyFcmConfigurationAl is active, check the RP3-01 optical cable between the synchronization master and synchronization slave system
3. Check the alarms in the synchronization master system module and act accordingly.
4. Reset the synchronization master system module.
5. Reset the slave system module by using block/unblock. Note that the side effect of the slave system module reset might be a shared radio module(s) reset. Cells
FAULT NAME
System Module failure
FAULT ID
3000: EFaultId_SystemModuleFailure
MEANING
The BTS has detected an abnormal operation or a failure in the internal functionality of the System Module.
INSTRUCTIONS
FAULT NAME
TD-SCDMA major alarm
FAULT ID
4178: EFaultId_TdscdmaMajorAl
MEANING
The Ir router has reported a major problem with TD-SCDMA. The TD-LTE performance is affected, and cells are disabled.
INSTRUCTIONS
Check the TD-SCDMA for active alarms.
FAULT NAME
Temperature alarm
FAULT ID
3040: EFaultId_TemperatureAlarm
MEANING
The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the modules are beyond the specified limits.
INSTRUCTIONS
1. Check the other BTS faults and act accordingly.
2. Check the ambient temperature of the BTS or the other modules. If the ambient temperature is too high, make sure the airflow to the BTS modules is unobstructed
3. Block and unblock the alarming module to reset it.
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
Transmission clock missing
FAULT ID
1816: EFaultId_Trans_Clk_MsgAl
MEANING
The reference clock monitoring has detected a loss of signal in the reference received from the FT.
INSTRUCTIONS
1. Check that the signal is being received from the reference clock source.
Check the backhaul connection.
FAULT NAME
Unit initialization failure
FAULT ID
4040: EFaultId_InitFaultManAl
MEANING
A module initialization has failed.
INSTRUCTIONS
1. Block/unblock the alarming module.
2. If FSP or FBB or ABIx is the fault source, perform FSP or FBB or ABIx reset recovery. If FCM/FCT is the fault source, perform system module reset recovery. If
3. If steps 1 and 2 do not help, replace the alarming module.
1. Reset the BTS.
FAULT NAME
FAULT ID
4208: EFaultId_RromIpConfigAl
MEANING
The RROM TRS IP configuring or reconfiguring has failed.
INSTRUCTIONS
Check the transport-related configuration (C-Plane address, U-Plane address, and Transport network ID). If the fault was raised at startup, correct the configurat
FAULT NAME
Unit not supported by current BTS SW version
FAULT ID
95: EFaultId_NotSupportedUnit
MEANING
An unsupported unit has been detected in the System Module. This typically happens when a new unit version is installed while an older system module SW, which doe
INSTRUCTIONS
1. Upgrade the system module SW.
2. Replace the unit.
FAULT NAME
Unit SW download failed
FAULT ID
6: EFaultId_SwDownloadAl
MEANING
A software update in the module or submodule has failed.
INSTRUCTIONS
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone (Flexi Zone Controller):
1. Download the BTS SW again.
3. If step 2 does not help, replace the alarming module.
1. Check other alarms associated with software upgrade.
2. Reset the AP to trigger software upgrade.
3. If step 2 does not help, replace the Flexi Zone Access Point.
2. Reset the SFN ANT to trigger software upgrade.
12/21/2019 Alarms
3. If step 2 does not help, replace the Flexi Zone SFN Antenna.
FAULT NAME
Unit synchronization failed
FAULT ID
16: EFaultId_SynchronizationAl
MEANING
The FCM or FSP, FCT (HW rel.4) or ABIx synchronization has failed.
INSTRUCTIONS
1. Block or unblock the module that is causing the alarm.
2. Replace the module that is causing the alarm.
FAULT NAME
Unknown HW resource
FAULT ID
94: EFaultId_UnknownUnitType
MEANING
A unit cannot be identified by its product code or by its physical device address (object ID).
INSTRUCTIONS
Replace the alarming unit or module.
Replace the BTS or Flexi Zone SFN Antenna.
FAULT NAME
U-Plane Computing Environment Container Failure
FAULT ID
4339: EFaultId_UplaneComputingEnvironmentContainerFailureAl
MEANING
An error has been detected during the start-up or normal run-time operation of the 2CE virtual container.
INSTRUCTIONS
Perform the following steps in the listed order until the fault disappears:
1. Reset the Flexi Zone Micro BTS/Flexi Zone Access Point.
2. Replace the Flexi Zone Micro BTS/Flexi Zone Access Point.
FAULT NAME
Validation of signed file failed
FAULT ID
4145: EFaultId_SignatureValidationFailedAl
MEANING
SW file validation against its signature has failed.
INSTRUCTIONS
Update the BTS to the required SW version.
If 7650 is active, immediate activation is mandatory.
FAULT NAME
Z1 Link Failure
FAULT ID
4258: EFaultId_Z1LinkFailureAl
MEANING
The Z1 link between the Flexi Zone Controller and the Flexi Zone Access Point is out of service.
INSTRUCTIONS
Check all the alarms posted by the Flexi Zone Access Point prior to the Z1 link failure.
FAULT NAME
Z3 Link Failure
FAULT ID
4344: EFaultId_Z3LinkFailureAl
MEANING
The Z3 link between the Flexi Zone Micro BTS, or Flexi Zone Access Point, and the Flexi Zone SFN Antenna is out of service.
INSTRUCTIONS
Check all the alarms posted by the Flexi Zone SFN Antenna prior to the Z3 link failure."
Table 12250: BASE_STATION_LICENSE_LIMITATION
Name: BASE_STATION_LICENSE_LIMITATION (11517) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: BASE STATION LICENSE LIMITATION FL16A
Package: racfl.BASE_STATION_LICENSE_LIMITATION Implicitly cleared: true
Description: BASE STATION LICENSE LIMITATION A critical fault (or faults) has occurred in the base station connectivity/interface. Check the reason for the fault from the supplementary text field of the alarm. The effect
of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically
cancels the alarm when the fault has been corrected.
Remedial action: FAULT NAME Active users license limitation FAULT ID 4337: EFaultId_ActiveUsersLimitAl MEANING The eNB enters capacity limited mode due to missing licenses. Calls from excess users will be
rejected except for handover and emergency calls. INSTRUCTIONS Add licenses to the Centralized License Server to avoid call limitation. See "Centralized License Server Help" document in NOLS for details. FAULT
NAME Cell Shutdown Due To Baseband Capacity License Limit FAULT ID 4349: EFaultId_CellShutdownDueToBasebandCapacityLicenseLimitAl MEANING The cell is shut down because it occupies baseband capacity that
is over the licensed limit. INSTRUCTIONS Add licenses to the Centralized License Server to avoid the traffic limitation. See "Centralized License Server Help" document in NOLS for details. FAULT NAME IP Traffic Capacity
Limit FAULT ID 4293: EFaultId_IPTrafficCapacityLimitAl MEANING The user's eNB IP traffic is throttled because of a missing license. INSTRUCTIONS Read the alarm diagnostic information to know when the missing
license was detected and at what level the IP traffic is currently throttled in relation to the peak rate. Add licenses to CLS to avoid the traffic limitation. If licenses are not added, the level will be decreased to the lowest level,
which is 50% of peak rate.
Table 12251: BASE_STATION_NOTIFICATION
12/21/2019 Alarms
Name: BASE_STATION_NOTIFICATION (11518) Severity: indeterminate Release:

Type: equipmentAlarm Specific problem: BASE STATION NOTIFICATION FL16A
Package: racfl.BASE_STATION_NOTIFICATION Implicitly cleared: true
Description: BASE STATION NOTIFICATION A minor fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm. The effect of the fault on the functioning
of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels the alarm when the
fault has been corrected.
Below is the list of BTS faults which might have caused this alarm in BTS FL16A/TL16A release. In case of earlier SW release and in case you need more detailed fa
-----------------------------------------------
FAULT NAME
# autonomous reset as recovery action
FAULT ID
52: EFaultId_UnitAutonomousResetAl
MEANING
The fault informs the operator that the BTS is trying to correct a fault situation by performing a recovery reset to a unit, the site, or the BTS.
In case of an RF module reset in RF chaining configuration, the BTS also resets all RF modules that are further in the chain.
The BTS tries to recover from a fault situation by performing a site reset.
INSTRUCTIONS
Check the fault history and other active faults of the unit.
Note: This fault does not require any (special) actions.
FAULT NAME
10b8b coding error in optical interface device
FAULT ID
2004: EFaultId_OIC_LVDSRecAl
MEANING
The fiber cable is experiencing interference; data transmission is faulty.
A physical connection failure between the optical interface and the summing function has occurred.
The reason of the fault might be a low-quality or polluted SFP, or a low-quality optical cable used to connect radio module to system module/extension baseband mo
INSTRUCTIONS
Note: Perform the steps in the listed order until the fault is resolved.
1. Reset the radio module behind the cable reported as the fault source by blocking/unblocking it.
3. Replace the SFP on the radio module port where the cable reported as fault source is terminated.
4. Replace the SFP on the system module or extension baseband module port where the cable reported as fault source is terminated.
5. Replace the optical cable reported as fault source.
6. Replace the radio module behind the cable reported as fault source.
7. If the system module reset helped but the fault is reported again after some time or if the actions mentioned above have not cleared the fault situation, repla
FAULT NAME
2M external reference missing
FAULT ID
1899: EFaultId_2MExtRefMissAl
MEANING
The reference clock monitoring has detected a signal loss of 2.048 MHz received from an external reference source, connected to Sync In interface of the System Mo
INSTRUCTIONS
1. Check the cabling (connected to Sync In interface).
2. Check if the 2.048 MHz reference source is working normally, and the 2.048 MHz signal is available.
FAULT NAME
3GPP/AISG communication administratively disabled
FAULT ID
4142: EFaultId_Communication3gppAdministrativelyDisabledAl
MEANING
The HDLC link has been disabled for the reporting Antenna Line or IUANT port.
INSTRUCTIONS
Enable the parameter "Communication3gppEnabled" for the reporting Antenna Line to revert changes.
FAULT NAME
Abnormal CPRI interface to next hop <OptIf ID>
FAULT ID
1974: EFaultId_AbnormalCpriInterfaceToNextHopAl
MEANING
The optical interface is not working properly.
The CPRI transmission is not working properly.
This fault is valid only for radio modules in a chain configuration.
Note: The Optif is from the perspective of the previous radio.
INSTRUCTIONS
1. Check the cables between the RF module that is reported as the fault source and the RF module that is closer to the system module or ABIA.
2. Reset the RF module.
3. If that does not help, block or unblock the site.
4. If that does not help, replace the RF module that is causing the alarm (connected to the faulty optical link, to the end farther from the system module).
12/21/2019 Alarms
FAULT NAME
Abnormal CPRI interface to upper hop <OptIf ID>
FAULT ID
1965: EFaultId_AbnormalCpriInterfaceToUpperHopAl
MEANING
The optical interface does not work properly. CPRI transmission to the upper hop does not work properly.
INSTRUCTIONS
Execute the following steps in the ordered sequence. If any of the step does not help, execute the next one:
1. Reset the radio module behind the cable reported as the fault source.
3. Replace the SFP on the radio module port where the cable reported as the fault source is terminated.
4. Replace the SFP on the system module or the extension baseband module port where the cable reported as the fault source is terminated.
5. Replace the optical cable reported as the fault source.
6. Replace the radio module behind the cable reported as the fault source.
7. If the actions mentioned above did not clear the faulty situation, replace the extension baseband module (if the fault is reported on the cable connected to th
FAULT NAME
Abnormal reception on SFP to next hop <OptIf ID>
FAULT ID
1973: EFaultId_AbnormalReceptionOnSfpToNextHopAl
MEANING
INSTRUCTIONS
4. If that does not help, replace the RF module that is generating the alarm.
FAULT NAME
Abnormal reception on SFP to upper hop <OptIf ID>
FAULT ID
1971: EFaultId_AbnormalReceptionOnSfpToUpperHopAl
MEANING
The optical interface is not working properly. There is abnormal signal reception from the upper hop FR. This fault is valid only for radio modules in chain confi
INSTRUCTIONS
1. Check the cables between the system module and the RF module.
3. If those do not help, block and unblock the site.
4. If those do not help, replace the RF module that is generating the alarm.
FAULT NAME
Access panel port(s) enabled
FAULT ID
234: EFaultId_AccessPanelPortEnaAl
MEANING
The FlexiZone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has detected that one or more access panel ports is enabled.
This state of elevated security risk is not expected in field conditions.
INSTRUCTIONS
1. Determine if this event is expected. Investigate audit logs as necessary.
2. If this action is unexpected, use SSH to disable access panel port(s) and/or physically inspect site installation.
FAULT NAME
ALD port configuration failure
FAULT ID
4255: EFaultId_AldPortFailureAl
MEANING
The Radio Module has detected switch configuration mismatch on the ALD port.
INSTRUCTIONS
1. Check the configuration of the ALD port.
2. The alarm is cancelled only when the RF Module is reset, or the BTS is reset.
FAULT NAME
ALD Port power failure
FAULT ID
4069: EFaultId_Rs485PowerFailureAl
MEANING
OBSAI interface:
The Radio Module has detected an over-current condition in the RS485 IUANT port.
Some antenna line device is causing overload. Antenna line devices powered by the RS485 IUANT are out of order because of the lack of DC power.
CPRI/Ir interface:
Overcurrent case:
The Radio Module has detected over-current on the ALD port. Some antenna line device is causing overload. Depending on hardware implementation, antenna line devic
Undercurrent case:
The Radio Module has detected undercurrent on the ALD port. There is a problem with ALD port connection. Depending on hardware implementation, antenna line device
INSTRUCTIONS
1. Check the ALD interface and antenna line devices. Fix or replace the faulty parts or devices.
2. The alarm is cancelled only when the RF Module is reset, or if the BTS is reset.
FAULT NAME
Antenna line device configuration failure
FAULT ID
1888: EFaultId_AlConfigurationFailureAl
MEANING
Antenna Line Device is not properly configured.
Antenna Line Device set-up fails, for example due to protocol error or interoperability problem.
12/21/2019 Alarms
INSTRUCTIONS
1. Check/correct the antenna line configuration.
2. If that does not help, replace the antenna line device.
FAULT NAME
Antenna Line Device failure
FAULT ID
3100: EFaultId_AntennaLineFailure
MEANING
The System Module, or the device itself, has detected an abnormal operation or a failure in the antenna line device.
INSTRUCTIONS
1. Check the antenna line and antenna line devices. Ensure that the antenna line connectors are in the right torque.
2. Block and unblock the alarming RF module to reset it.
3. Replace the faulty parts and/or devices along the antenna line.
4. Replace the RF Module.
FAULT NAME
Antenna line device HW failure
FAULT ID
1847: EFaultId_HardwareErrorAl
MEANING
A hardware failure has been reported by ALD (RET, MHA).
INSTRUCTIONS
1. Reset the radio module to give a power-off reset to the antenna line devices.
2. If step 1 does not help, replace the antenna line device.
FAULT NAME
Antenna line device missing software
FAULT ID
1848: EFaultId_WorkingSoftwareMissingAl
MEANING
The unit is in download mode state. This fault is returned when an unsupported procedure occurs in download mode.
INSTRUCTIONS
1. Upload the correct SW to the device (if possible) or perform an ALD power reset (for example, by RF module reset).
FAULT NAME
Antenna line device operation failure
FAULT ID
4239: EFaultId_AldOperationFailureAl
MEANING
The radio module indicated an error upon execution of remote electrical tilt (RET)-related logical operation.
INSTRUCTIONS
1. Check the antenna line and RET devices. Fix or replace the faulty parts or devices.
2. To cancel the alarm, perform an RF module startup or BTS reset.
FAULT NAME
Antenna Line Device Operation Failure
FAULT ID
1871: EFaultId_BusyAl
1872: EFaultId_FormatErrorAl
1873: EFaultId_UnsupportedProcedureAl
1874: EFaultId_OutOfRangeAl
MEANING
The device is not working properly, the configuration is not valid, or a given parameter is incorrect.
INSTRUCTIONS
1. Check the functionality of the antenna line device.
2. Check the compatibility between the antenna line device and the BTS.
3. Check that the given parameters are in the valid range.
FAULT NAME
Antenna line device SW download failure
FAULT ID
4047: EFaultId_FileCrcErrorAl
4048: EFaultId_FileContentErrorAl
MEANING
An SW download to an antenna line device has failed because of an incorrect checksum or file format.
INSTRUCTIONS
1. Check the SW package.
2. Download the SW to the antenna line device again.
FAULT NAME
Antenna line failure
FAULT ID
1836: EFaultId_ALOvercurrentAl
MEANING
The radio module or filter has detected overcurrent on the antenna line. The antenna line might be damaged (short-circuited), or some antenna line device is causi
INSTRUCTIONS
1. Check the antenna line and antenna line devices. Fix or replace the faulty parts or devices.
2. For CPRI-A radios, the fault might cancel automatically if the fault condition is cleared within 1 minute of detection. For some CPRI-A radios, the fault might
3. For all other radios, the fault is canceled only when the RF module or the BTS is reset.
12/21/2019 Alarms
FAULT NAME
Antenna line operation degraded
FAULT ID
4046: EFaultId_AntennaLineDegradedAl
MEANING
An alarm message has been received from the antenna line device. The antenna line operation is degraded.
INSTRUCTIONS
Perform the following steps on the MasterRAT side:
1. Check the antenna line and antenna line device that is causing the alarm.
2. Fix or replace the faulty parts and devices.
FAULT NAME
Antenna line setup failure
FAULT ID
4238: EFaultId_AntennaLineSetupFailureAl
MEANING
An antenna line or antenna line device is not properly configured.
The antenna line setup and device scan fails because of exceeded time limit or too many ALDs detected from the ALD port.
The radio module reports the fault when the antenna line starts.
INSTRUCTIONS
1. Check or correct the RET device configuration (that is, the RET connected to the radio module generating the alarm).
FAULT NAME
Antenna line switched off due to high VSWR
FAULT ID
1957: EFaultId_AntennaLineSwitchedOffAl
MEANING
Tx in the RF module has been switched off to protect the radio module hardware, which might be damaged because of high-reflection (VSWR) conditions.
INSTRUCTIONS
1. The VSWR measured at the RF (transmitter) exceeds values that are acceptable by the RF module.
2. Check the impedance matching of the Antenna Line System (replace elements that cause mismatch).
3. To check if the above-mentioned steps have solved the problem, reset the RF module.
*Forcing the RF HW to work under such conditions might result in permanent damage to the RF HW.
FAULT NAME
AP Discovery Failure Due to Misconfiguration
FAULT ID
4281: EFaultId_ApDiscFailMisconf
MEANING
This fault denotes the inability to identify the FZAP based on the information provisioned in APMOD.
INSTRUCTIONS
1. Verify if the APMOD provisioning data have been correctly entered.
2. Verify if the siteID provisioned on the FZAP was entered correctly.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
2. Reset the BTS.
3. Replace the BTS.
Flexi Zone:
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Boot configuration inconsistency detected
FAULT ID
4102: EFaultId_BootConfigurationInconsistencyAl
MEANING
During SW update, the configurations of the active and passive SW in the HW unit have been detected to be the same. Active and passive SW configurations are compa
- before SW download
- during SW activation, before active and passive SW switch
- during start-up
INSTRUCTIONS
1. Block/unblock the Flexi Zone Micro BTS to reset.
2. If blocking or unblocking the Flexi Zone Micro BTS does not solve the problem, replace the faulty Flexi Zone Micro BTS.
None
FAULT NAME
BTS file error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
FAULT NAME
BTS is uncommissioned
FAULT ID
4030: EFaultId_NoCommDataAl
MEANING
Flexi BTS FDD, Flexi BTS TDD:, AirScale BTS FDD, AirScale BTS TDD
12/21/2019 Alarms
The commissioning file download has not been started from the BTS Site Manager or from NetAct during auto-configuration. Either the auto-configuration might not b
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Controller:
The commissioning file download has not been started from the BTS Site Manager or from NetAct during auto-configuration. The auto-configuration might not be enabl
Flexi Zone Access Point:
The commissioning file download has not been started from the Flexi Zone Controller. The discovery of the Flexi Zone Access Point by the Flexi Zone Controller mig
The commissioning file download has not been started from the Flexi Zone Micro BTS or Flexi Zone Access Point. The discovery of the Flexi Zone SFN Antenna by the
INSTRUCTIONS
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Controller:
1. In NetAct, check if auto-configuration is enabled and if the required license and commissioning files are available.
2. Check the auto-connection or auto-configuration information using the BTS Site Manager.
1. Check the connectivity of the access point to the Flexi Zone Controller.
2. Reset the Flexi Zone Access Point from the BTSSM connected to the FZAP.
4. Contact Nokia.
1. Check the connectivity of the Flexi Zone SFN Antenna to the Flexi Zone Micro BTS or Flexi Zone Access Point.
3. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point.
4. Contact Nokia.
FAULT NAME
BTS Location Lock failed
FAULT ID
4283: EFaultId_LocationLockFailed
MEANING
The Location Lock has failed.
1. The BTS was not able to acquire Location Lock evidence data after feature activation. Depending on the configured detection methods:
- The BTS might time out while waiting for GNSS coordinates.
- The following network parameters are not available: IP address of the first routing hop, physical subnet address of the BTS, or MAC address of the first routing
2. The BTS has failed to update the Location Lock evidence file because of a flash file system error.
INSTRUCTIONS
1. If the BTS cannot acquire GNSS coordinates:
- Disable the Location Lock feature.
- Fix the problem with the GNSS receiver. Alternatively, configure the detection method to a method other than GNSS.
- Re-enable the Location Lock feature.
2. If the BTS cannot acquire network configuration parameters:
- Disable the Location Lock feature.
- Fix the problem with network configuration.
- Re-enable the Location Lock feature.
3. If the BTS failed to update the Location Lock evidence:
- Disable and then re-enable the Location Lock feature.
- If the problem persists, replace the faulty device.
FAULT NAME
BTS Location Lock violation detected
FAULT ID
4284: EFaultId_LocationLockViolation
MEANING
A Location Lock violation has been detected after a BTS reboot.
1. The distance between the newly-acquired BTS position and the GNSS position that is stored in the Location Lock evidence file exceeds the configured limit.
2. The newly-configured parameters (IP address of the first routing hop, physical subnet address of the BTS, or MAC address of the first routing hop) do not match
The integrity check of the Location Lock evidence data has failed after a BTS reboot.
1. The Location Lock evidence file is missing.
2. The Location Lock evidence file has failed P7 signature validation.
INSTRUCTIONS
1. If the BTS detects a Location Lock violation:
- If the BTS has been relocated without authorization, the alarm is expected.
- If the BTS relocation is authorized, disable the Location Lock feature and then re-enable it to reacquire the correct Location Lock evidence.
2. If the BTS detects a missing or corrupted Location Lock evidence:
- Disable the Location Lock feature and then re-enable it in order to recover.
- If, during the above operation, the BTS has reported fault 4283:EFaultId_LocationLockFailed, replace the faulty device.
FAULT NAME
BTS power cycle detected
FAULT ID
237: EFaultId_PowerCycleDetectedAl
MEANING
A power cycle is detected. This fault is raised at BTS startup after the power cycle.
INSTRUCTIONS
If the problem persists, verify the power source of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
BTS power voltage rail failure
FAULT ID
4190: EFaultId_PowerVoltageRailFailureAl
MEANING
The potential power down condition of the Flexi Zone Micro BTS or Flexi Zone Access Point.
INSTRUCTIONS
1. Check the power supply.
2. Because of the short amount of time, it is possible (despite efforts to prevent it) that the fault does not reach the operator console before the alarming devi
3. Because of false detection, it is possible (despite efforts to prevent it) that the fault is raised and the alarming device is not powered down.
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
GPS source:
FAULT NAME
BTS reset required
FAULT ID
MEANING
This fault notifies the operator that the BTS must be reset to solve a problem that has been discovered by the BTS O>M; system, and that the BTS O>M; will not tri
5. The BTS O>M; system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed
6. In BTS runtime, the BTS O>M; system has detected resources necessary to cell setup that were not detected during BTS start-up, for example, commissioned radio
7. BTS O>M; has detected an extension baseband module, for example, FBBC, on the same QSFP port, which is different than the previously-removed baseband card, for
INSTRUCTIONS
FAULT NAME
BTS reset time increased
FAULT ID
4091: EFaultId_BtsResetTimeIncreasedAl
12/21/2019 Alarms
MEANING
During reset, the BTS has detected that an RF module connected to the system module is affected by a power cycle failure and other additional actions performed by
INSTRUCTIONS
None
FAULT NAME
BTS SW download or activation failed
FAULT ID
29: EFaultId_FileCorruptionAl
30: EFaultId_SwUpdateAl
MEANING
The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem in the module, or a corrupted flash file s
INSTRUCTIONS
2. If other flash memory-related faults are active for the alarming module at the same time, replace the alarming module.
2. If other flash memory-related faults are active for the BTS at the same time, replace the BTS.
1. Retry the SW update by resetting the Flexi Zone Access Point using the BTS SM.
2. If other flash memory-related faults are active for the Flexi Zone Access Point at the same time, replace the Access Point.
1. Retry the SW update by resetting the Flexi Zone SFN Antenna using the BTS SM.
2. If other flash memory-related faults are active for the Flexi Zone SFN Antenna at the same time, replace the Flexi Zone SFN Antenna.
FAULT NAME
BTS time not corrected
FAULT ID
26: EFaultId_NtpTimeNotSetAl
MEANING
The SNTP time or GPS time cannot be fetched within the time limit.
The UTC time source is not available in the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
INSTRUCTIONS
1. Check the NTP setting.
2. Check the stratum parameter on the NTP server.
3. Check that a GNSS is configured and connected.
FAULT NAME
Buffer over/underflow in clock crossing logic
FAULT ID
2054: EFaultId_MuksuRxClkErrorAl
MEANING
The clock-crossing buffer underflow or overflow in the RX block, and the received data, might be invalid. The fault is an indication of either there is too large
INSTRUCTIONS
1. Check the status of the module behind the faulty link (power on, and so on).
2. Check the alarming fiber connection.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Compensation buffer is not enough for RF module delay difference
FAULT ID
4276: EFaultId_RelativeDistanceCompensationBufferNotEnoughAl
MEANING
The transmission delay difference between the radio module that needs to be compensated, and the radio module with the maximum transmission delay, is bigger than
The transmission delay includes the delay in the optical modules of both the system module and radio modules, the delay in the optical fibers and forward delay of
INSTRUCTIONS
Reduce the length of the cables used to connect the radio module to the system module. If the radio module works in the chain, you can also remove the previous ra
12/21/2019 Alarms
FAULT NAME
Configuration and hardware mismatch
FAULT ID
4282: EFaultId_ConfigurationAndHardwareMismatchAl
MEANING
The detected hardware does not support the SCF configuration.
INSTRUCTIONS
1. Read the diagnostic information of the alarm.
2. If the diagnostic information is "IQ compression or forced link speed incorrect
in site configuration file", check what configurations are supported by
Nokia, correct IQ compression, or force link speed value in the Site Configuration File (SCF), and then re-commission the BTS.
3. If the diagnostic info is "Number of detected RET units in multiRET
is not consistent with site configuration file" or its equivalent information for RAE, correct the RET or RAE configuration to remove the extra entries, and then
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Configuration file corrupted
FAULT ID
1924: EFaultId_FrConfigurationFileCorrupted
MEANING
The RF Module SW has detected conflicting or corrupted configuration data.
INSTRUCTIONS
1. Reset the RF HW unit.
2. If problem is still observed after performing step 1, replace the RF HW unit.
FAULT NAME
Configuration reset
FAULT ID
4181: EFaultId_ConfigResetAl
MEANING
The Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna detects that configuration reset has been invoked.
INSTRUCTIONS
2. If this action is unexpected, use SSH to disable maintenance port(s) and/or physically inspect site installation.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Connection Unstable At 3Gbps
FAULT ID
4310: EFaultId_ConnectionUnstableAt3Gbps
MEANING
The RP30-1 connection between the system module and radio module, or between the extension baseband module (FBBx) and the radio module, is not stable at 3 Gbps.
INSTRUCTIONS
1. Check if the optical transmission network connecting the system module with the radio module, or the extension baseband module (FBBx) and the radio module, sup
2. Check if the cable connecting the system module and the radio module, or the cable connecting the extension baseband module and the radio module is fixed firml
4. Change the radio module where the unstable link is terminated.
5. If this does not help, replace the FBBx if the unstable link is terminated
on FBBx.
6. If this does not help, replace the FCT (system module).
If an alarm with fault 4038 (Radio master conflict) is reported at the same time,
follow the instructions of fault 4038 because in some cases fault 4038 might be the root cause of fault 4310.
FAULT NAME
12/21/2019 Alarms
FAULT ID
MEANING
The RP30-1 connection between the system module and the radio module, or between an extension baseband module (FBBx/ABIx) and the radio module, is not stable at 6
INSTRUCTIONS
1. Check if the optical transmission network connecting the system module and
the radio module, or the extension baseband module (FBBx/ABIx) and the radio module,
supports 6 Gbps transmission.
2. Check if the cable connecting the system module and the radio module, or the
cable connecting the extension baseband module and the radio module, is connected
firmly to the modules.
5. If this does not help, replace the FBBx/ABIx if the unstable link is terminated
on the FBBx/ABIx.
If an alarm with fault 4038 (Radio master conflict) is reported at the same
time, follow the instructions of fault 4038 because in some cases fault 4038 might
be the root cause of fault 4309.
FAULT NAME
Constellation mode not supported
FAULT ID
4296: EFaultId_ConstellationModeNotSupportedAl
MEANING
The BTS has detected an incompatible operator-selected constellation mode for
the GNSS receiver.
INSTRUCTIONS
Configure a valid GNSS constellation mode supported by the GNSS receiver to
cancel the fault (wait for 60 seconds).
FAULT NAME
Cooling fan broken
FAULT ID
4078: EFaultId_FanBrokenAl
MEANING
One or more fans are not running although the temperature (indicated by Tcontrol) is higher than the value of the T.start parameter in the BTS Property File (BPF)
INSTRUCTIONS
1. Check that the fan or airflow is not blocked by any object.
2. Check that the fan connector is properly mounted.
3. If that does not help, replace the fan.
FAULT NAME
Cooling fan broken: <X>
FAULT ID
1933: EFaultId_FrFanBroken
MEANING
Fan(s) in the RF module is/are not running.
INSTRUCTIONS
1. Check if the fan or air flow is blocked by any object. Remove any objects that might be blocking the fan or air flow.
2. Check if the fan connector is properly mounted. Mount the fan connector properly.
3. If the alarm continues, reset the radio module.
4. If the alarm continues, replace the fan module.
FAULT NAME
Cooling fan has reduced from the set speed
FAULT ID
1934: EFaultId_FrFanReducedSetSpeed
MEANING
Fan(s) in RF module is/are rotating slower than requested.
INSTRUCTIONS
1. Check if the fan or air flow is blocked by any object. Remove any objects
that might be blocking the fan or air flow.
2. Check if the fan connector is properly mounted. Mount the fan connector
properly.
FAULT NAME
Cooling fan is over speeding
FAULT ID
4080: EFaultId_FanOverSpeedAl
MEANING
One or more fans are running faster than requested.
INSTRUCTIONS
Replace the fans.
FAULT NAME
Cooling fan is over speeding
FAULT ID
1935: EFaultId_FrFanOverSpeed
MEANING
Fan(s) in the RF module rotate faster than required.
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Cooling fan speed decreased
FAULT ID
4079: EFaultId_CoolingFanSpeedDecreasedAl
MEANING
The speed of one or more fans is excessively deviating from the requested control.
INSTRUCTIONS
1. Check if the fan or airflow is not blocked by any object.
2. Check if the fan connector is properly mounted.
3. If that does not help, replace the fan.
FAULT NAME
Correctable bit toggling error
FAULT ID
6700: EFaultId_CorrectableBitTogglingError
MEANING
A correctable bit toggling error is detected in DSP memory.
INSTRUCTIONS
The fault doesn't require any special action because it was already autonomously corrected.
FAULT NAME
CPRI-A RF sharing mode conflict
FAULT ID
4375: EFaultId_CpriArfSharingModeConflictAl
MEANING
The LTE eNB has detected an RF sharing configuration conflict in the radio that is also connected to a CDMA BTS.
1. If the alarm diagnostic information contains "Incorrect mode configuration for CPRI-A RF Sharing", then one of the following invalid configurations is detected
1.1. The LTE eNB is in stand-alone mode and the CDMA BTS is in any mode.
1.2. The LTE eNB is in any mode and the CDMA BTS is in stand-alone mode.
1.3. The LTE eNB and CDMA BTS are both in secondary mode.
2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", then the LTE eNB is operating in a secondary
INSTRUCTIONS
1. If the alarm diagnostic information contains "Incorrect mode configuration for CPRI-A RF Sharing", then configure the correct CPRI-A RF sharing mode on the LTE
1.1. LTE eNB is in secondary mode and CDMA BTS is in primary mode.
1.2. LTE eNB is in stand-alone mode and CDMA BTS is disconnected from the radio.
2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", reconfigure the CDMA BTS to give both SW and
3. If the previous steps do not help, reset the alarming radio unit.
4. If the previous steps do not help, reset the LTE eNB and/or CDMA BTS.
FAULT NAME
CRAN configuration alarm
FAULT ID
4274: EFaultId_CranIncorrectConfigurationAl
MEANING
The Centralized Radio Access Network (CRAN) configuration and the exchanged information between the connected BTSs show conflicts. CRAN functionality between the
INSTRUCTIONS
1. Read the diagnostic information in the alarm to find out detailed information about the fault reason.
2. Correct the site configuration file of own BTS or neighbor BTS according to the diagnostic information.
3. Re-commission the BTS and neighbor BTS using the valid commissioning files.
FAULT NAME
Critical BER detected on the optical connection to Radio Module
FAULT ID
1956: EFaultId_CritBerOnRp3
MEANING
An abnormally high bit error rate has been detected on the optical link to the radio module, which results in permanent baseband processing failure. I/Q data stre
INSTRUCTIONS
Instructions are divided into three sections. Execute steps from the chosen section based on best knowledge and common sense to minimize the cost and
time effort.
Section A: Check on system module side:
1. Check if the connector seal is properly mounted and is firmly in place.
2. Check if the small form-factor pluggable (SFP) is properly connected/mounted in the system module. If the SFP's connection/mounting is not correct, readjust th
3. Check if the LED indicates that the SFP is faulty (connected to system module). Replace the SFP if it is faulty.
4. Check if the optical cable is properly connected/mounted in the SFP.
5. Clean the optical connectors that are connected to the SFP. Reset the RF HW
unit and check if this solves the problem.
Section B: Check on the radio module side:
2. Check if the small form-factor pluggable (SFP) is properly connected/mounted in the RF module. If the SFP's connection/mounting is not correct, readjust the co
4. Clean the optical connectors at the RF module end. Reset the RF HW unit and check if this solves the problem.
Section C: Check the optical connection:
1. Check if the optical cables are not overly bent. If they are, replace the optical cables, since overly bending the optical fiber cables damages the cables and
2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the system module end. Check the measuring equipment documentation for inst
3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF module end. Check the measuring equipment documentation for instructi
If the alarm continues after executing steps from sections A,B, and C, replace
the RF module.
FAULT NAME
Critical bit toggling error
FAULT ID
6701: EFaultId_CriticalBitTogglingError
MEANING
A non-correctable, bit-toggling error has been detected in the critical DSP memory.
INSTRUCTIONS
1. Reset the System/Baseband Module.
2. Replace the System/Baseband Module.
2. If the fault persists, Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
12/21/2019 Alarms
FAULT NAME
DC voltage administratively disabled
FAULT ID
4141: EFaultId_DcVoltageAdministrativelyDisabledAl
MEANING
The feeding voltage is disabled for the selected antenna line.
INSTRUCTIONS
To revert the changes, the DC voltage should be enabled for the reporting antenna line.
FAULT NAME
Diagnostic Files collected
FAULT ID
6450: EFaultId_TechnicalLogUploadRecommended
MEANING
After a DSP crash, the eNB collects core dumps and DSP memory dumps from the crashed DSP.
After an FCT or an FSP crash, the eNB collects core dumps from the crashed unit.
Fault 6450 notifies the operator that the logs are stored in the eNB and can be collected in the snapshot.
INSTRUCTIONS
Collect technical logs from the BTS to clear the alarm raised by this fault.
Internal logs collected by this process can only be analyzed by Nokia R&D.
Additionally:
- Check the alarm history to confirm the frequency of fault 6450 in a specific eNB.
- Check the alarm history for other alarms in the same eNB that might be related, especially alarms with:
a. FSP or FBBB alarm source
b. with the following fault IDs: 418, 6706-6709, 12, 476, 1806, 1811, 4019
- Check the eNB for any performance issues.
If an alarm with fault 6450 frequently occurs in the same eNB, there are alarms with the same faults mentioned above in the same eNB, or the eNB performance is de
Take note if logs from different DSPs of the same FSP are stored in the eNB, only one alarm with fault 6450 is reported as related to one DSP. The next alarm with
FAULT NAME
Difference between BTS master clock and reference frequency
FAULT ID
9: EFaultId_DacWordChangeAl
MEANING
Flexi BTS FDD, AirScale BTS FDD:
The reference frequency that the BTS master clock receives has changed by about 0.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) durin
The cause of the alarm can be:
1. The reference frequency has changed because of a fault in the transmission network synchronization, which in turn is caused by an equipment fault or a setting
2. The reference frequency fluctuates continuously because of a significant amount of jitter or wander in the transmission network. The alarm is continuously acti
3. If the BTS-integrated transport part receives the synchronization information through the 2.048 MHz synchronization input (external clock source), the alarm si
4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason is in the Iub or reference signal beh
The reference frequency that the BTS master clock receives has experienced a significant change during the measurement period as compared to the BTS master clock
The cause of the alarm can be:
1. The reference frequency has changed because of a fault in the transmission network synchronization, which in turn is caused by an equipment fault or a setting
2. The reference frequency fluctuates continuously because of a significant amount of jitter or wander in the transmission network. The alarm is continuously acti
3. If the BTS-integrated transport part receives the synchronization information through the 2.048 MHz synchronization input (external clock source), the alarm si
4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason is in the Iub or reference signal beh
INSTRUCTIONS
Because there are several possibilities for the alarm activation, a BTS Clock Frequency History feature has been developed. You can access the stored history data
1. In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term accuracy of the Iub signal must be
2. If the basic accuracy of the Iub signal is correct, but there is too much instability, that is, the jitter or wander is outside the acceptable limits, you must
3. In case of a BTS equipment fault, the location might be:
Transport part:
- First, check the alarms of the TRS with the BTS Site Manager and act accordingly.
- If there are no alarms, check the TRS synchronization settings.
FCM unit:
- If the TDM reference signal accuracy and the TRS are in order, but the FCM unit is still alarming, run the fast tuning with the BTS Site Manager.
- If the alarm is still active after the fast tuning is finished, reset the site. If the problem does not disappear in a few minutes, reset the site.
- If that does not help, replace the FCM unit.
Note that if the reason is in the transmission network synchronization, replacing the faulty unit does not solve the problem. Furthermore, the alarm activity (fre
network, not to a fault in the unit.
4. After the fault situation has been cleared, you might need to tune the BTS master clock because the BTS master clock adjustment is quite slow. You can perform
- manually by changing the DAC word (during a site visit)
- with fast tuning, in which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning)
Note, however, that you should only use the fast tuning in case the Iub reference signal is known to be a good one. Otherwise, the BTS frequency might be tuned in
Background information: The principle is that in the mobile network, the synchronization goes from S1 interface. But in reality, that chain might be broken somewh
FAULT NAME
DSP loading failure
FAULT ID
1962: EFaultId_RruDspLoadingFailure
MEANING
DSP loading has failed.
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Error in file server during file download
FAULT ID
27: EFaultId_FileServerAl
MEANING
The BTS cannot obtain a file from the file server (there is an error in either FTP open or FTP get). The file server is down, the file is missing, or the path is
INSTRUCTIONS
1. Retry the file update for a few times.
2. Check the FTP account user settings.
3. Check the file and path names.
4. Check the administration log on the file server.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Failure in connection between BTS and iOMS or 3rd party tool
FAULT ID
6261: EFaultId_TraceConnectionFaultyAl
MEANING
A failure has occurred in the trace connection between the BTS and the iOMS, or a third-party tool.
INSTRUCTIONS
Check the connection with the iOMS or the third-party tool.
FAULT NAME
Failure in connection to Real-time PM Collection Entity
FAULT ID
4203: EFaultId_RtpmConnectionFaultAl
MEANING
A failure has occurred in the connection to the configured Real-time Performance Management (RTPM) entity, for example, the Traffica Network Element Server (TNES)
INSTRUCTIONS
1. Verify if the IP address is properly configured at the BTS.
2. Verify if the Real-time Performance Management (RTPM) entity is operational and available.
3. If the above have been verified, the operator can reset the BTS at a suitable time.
FAULT NAME
Failure in log file gathering
FAULT ID
4176: EFaultId_LogGatheringFailureAl
MEANING
Gathering logs from the unit has failed, and one or more log files from a particular RF module is not available in the BTS snapshot.
INSTRUCTIONS
Restart the faulty unit and retry the BTS snapshot request using the BTS Site Manager.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
3. REMOTE ACTIONS
FAULT NAME
FAULT ID
12/21/2019 Alarms
MEANING
baseband unit.
INSTRUCTIONS
FAULT NAME
Failure in trace session
FAULT ID
6263: EFaultId_TraceSessionAl
MEANING
A failure has occurred during activation or de-activation of a trace session (subscriber trace, cell trace, or interface trace session).
In case of subscriber trace, the possible reasons are:
- The Subscriber Trace feature is not enabled in the BTS.
- The ID used for the subscriber trace session is already in use for another active subscriber trace session.
- The number of subscriber trace sessions in the BTS has reached the maximum number of subscriber trace sessions supported by the BTS, which is 60.
- The handover in the BTS is ongoing for the UE to be traced.
In case of cell and interface trace, the possible reasons are:
- The Cell Trace feature is not enabled in the BTS.
- The ID used for the cell and interface trace session is already in use for another active cell and interface trace session.
- The number of cell and interface trace sessions in the BTS has reached the maximum number of cell and interface trace sessions supported by the BTS, which is 12
INSTRUCTIONS
For failure in the subscriber trace session activation or de-activation, based on the error cause provided as part of the additional info for the alarm raised, th
- "Subscriber & Equipment Trace feature not enabled": Enable the subscriber trace feature in the BTS. Any events corresponding to the failed subscriber trace, and
- "trace reference in use, trace cannot be started": This problem is out of the scope of what can be fixed in the BTS, and is within the scope of the Network Mana
- "max number of UE trace session reached, trace cannot be started": This problem is out of the scope of what can be fixed in the BTS, and is within the scope of
- "Trace session cannot be started due to ongoing handover for the UE" or "Trace session cannot be stopped due to ongoing handover for the UE": This problem is ou
For failure in cell or interface trace session activation or de-activation, based on the error cause provided as part of the additional info for the alarm raised,
- "Cell trace feature is not enabled": Enable the cell trace feature in the BTS. Afterwards, try again to activate the required cell or interface trace sessions.
- "trace reference in use, trace cannot be started": This problem is out of the scope of what can be fixed in the BTS, and is within the scope of the Network Mana
- "max number of cell/interface trace sessions reached, trace cannot be started": This problem is out of the scope of what can be fixed in the BTS, and is within
FAULT NAME
Failure to download software due to missing software signature
FAULT ID
4269: EFaultId_SwBuildSignatureMissingAl
MEANING
There has been a failure to validate the software signature for the software release that has been requested to be downloaded to the BTS system module because the
INSTRUCTIONS
Retry the SW update.
FAULT NAME
Failure to verify a signed software release
FAULT ID
4267: EFaultId_SwBuildElementSignatureVerificationAl
MEANING
There has been a failure to validate the hash of the questioned SW files for FCT except of the Hash Container file or the Hash Container Signature file in the sof
INSTRUCTIONS
FAULT NAME
Failure to verify the signature of a signed software release
FAULT ID
4266: EFaultId_SwBuildSignatureVerificationAl
MEANING
There has been a failure to validate the software release signature for the software release that has just been requested to be downloaded to the BTS system modul
INSTRUCTIONS
FAULT NAME
Fan failure
FAULT ID
3050: EFaultId_FanFailure
MEANING
A fan, all the fans, or more than one fan in the same fan group are rotating slower or faster than requested, are not rotating at all, or the RPM information is n
INSTRUCTIONS
1. Check if fan or air flow is blocked by any object(s). Remove any blocking
object(s).
3. If the alarm is still observed, reset the radio module by using block/unblock.
4. If the alarm is still observed, replace the fan module.
FAULT NAME
Fan vendor not detected
FAULT ID
4073: EFaultId_FanVendorNotDetectedAl
MEANING
A fan delivered by an unknown vendor is detected (system module hardware rel.2),
or the fan speed is too low for successful detection. Another detection attempt
occurs after the fan test timer expires (system module hardware rel.3).
This fault is reported for both operational and non-operational fans in hardware
12/21/2019 Alarms
detection phase only.
INSTRUCTIONS
1. Check the fan and the connector.
2. Replace the fan.
FAULT NAME
File corrupted in SW download
FAULT ID
28: EFaultId_SwPackageAl
MEANING
The download is corrupted, or the software is incompatible.
INSTRUCTIONS
2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.
FAULT NAME
File System access failed
FAULT ID
4088: EFaultId_FileSystemAccessFailedAl
MEANING
File system access operations like file system mounting or file opening have failed.
INSTRUCTIONS
Update the BTS SW, unless it is automatically updated by NetAct.
None
FAULT NAME
Filter tuning failure
FAULT ID
1840: EFaultId_TuningFailureAl
MEANING
The Radio Module is unable to tune to a required sub-band properly (tuning
failure), or another major failure has been detected by the Radio Module
(unit faulty).
INSTRUCTIONS
Replace the alarming Radio Module/MultiRadio Combiner.
FAULT NAME
Filter unit faulty
FAULT ID
1841: EFaultId_UnitFaultyAl
MEANING
The radio module has detected an internal filter failure.
INSTRUCTIONS
1. Reset the radio module.
2. If resetting the radio module does not help, replace the alarming radio module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FPGA R/W error
FAULT ID
1963: EFaultId_FpgaRwErrorAl
MEANING
An error has occurred during a read/write attempt on the FPGA.
INSTRUCTIONS
1. Reset the RF Module.
2. If that does not help, replace the alarming RF Module.
FAULT NAME
FPGA SW update failed
FAULT ID
1928: EFaultId_FrFpgaSwUpdateFailed
MEANING
The FPGA software update in the RF module has failed.
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Frame clock missing
FAULT ID
1903: EFaultId_FrFrameClockMissing
MEANING
The System Module clock reference differs from the RF Module clock.
INSTRUCTIONS
Instructions are divided into three sections. Execute the steps from the section chosen based on the best knowledge and common sense to minimize the cost and time
Section A: Check on the system module side:
1. Check if the connector seal is properly mounted and firmly in place.
2. Check if the Small Form Factor Pluggable (SFP) is properly connected/mounted in the System Module. If SFP connection/mounting is incorrect, readjust the connec
3. Check if the LED indicates the faulty SFP (connected to System Module). Replace the SFP if it is faulty.
5. Clean the optical connectors that are connected to the SFP. Reset the RF HW and check if this solves the problem.
1. Check if connector seal is properly mounted and firmly in place.
2. Check if the Small Form Factor Pluggable (SFP) is properly connected/mounted in the RF module. If SFP connection/mounting is incorrect, readjust the connection
1. Check if the optical cables are not overly bent. If they are, replace the optical cables since overly bending the optical fiber cables damages the cables and c
2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System Module end. Check the measuring equipment documentation for instr
3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF Module end. Check the measuring equipment documentation for instructi
If the alarm still persists after executing the steps from sections A, B, and C, replace the RF module.
FAULT NAME
FR module reset requested
FAULT ID
1981: EFaultId_FrResetRequestedAl
MEANING
The FR module has detected a transient problem that requires a reset recovery.
INSTRUCTIONS
No actions are needed since the BTS recovers independently. If the alarm occurs multiple times, check other active alarms to determine the root cause.
FAULT NAME
FR not critical functionality not supported or are not configured correctly.
FAULT ID
4271: EFaultId_FrNotCriticalFunctionalityNotSupportedAl
MEANING
FR functions that are not critical for cell setup are not supported or are not configured correctly. The reason for this might be incompatible RFSW version.
INSTRUCTIONS
Check other active alarms.
FAULT NAME
FZAP Not Connected Successfully
FAULT ID
4322: EFaultId_FzapNotConnectedSuccessfullyAl
MEANING
The target Flexi Zone Access Point (FZAP) has not yet been successfully connected to the Flexi Zone Controller (FZC). This might mean that the physical FZAP does
INSTRUCTIONS
If the target FZAP does not physically exist, ignore this fault or clean it up by deleting the target FZAP. Otherwise, perform the following steps:
1. Check all other alarms posted against the target FZAP on FZC.
2. Check the alarms raised on the FZAP through WebUI or FZAP BTSSM.
FAULT NAME
FZC LTE time out of sync
FAULT ID
4331: EFaultId_FzcLteTimeOutOfSyncAl
MEANING
The LTE time on the Flexi Zone Controller is out of sync and might not be accurate. As a result, the MBMS service is disabled on the Flexi Zone Controller.
INSTRUCTIONS
This fault is raised if the Flexi Zone Controller has acquired LTE time sync with one of its FZAPs before but has failed to maintain the time sync because of one
1. None of the FZAPs are connected anymore.
2. All of its connected FZAPs has lost sync with their time source.
Perform actions to ensure that the FZAPs are connected to the FZC and/or recover the time sync with their time source.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
GPS receiver alarm: EEPROM invalid
FAULT ID
4126: EFaultId_GpsReceiverEepromInvalidAl
MEANING
The GPS receiver has detected that one or more EEPROM segments were corrupted at reset, and had to be set to their factory default settings.
INSTRUCTIONS
Perform the steps below in the listed order until the fault disappears:
EEPROM invalid:
1. The GPS receiver has detected a malfunction in its EEPROM memory. Perform a (remote) power reset for the GPS receiver.
2. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module if needed.
FAULT NAME
GPS receiver alarm: no stored position
FAULT ID
4124: EFaultId_GpsReceiverNoStoredPositionAl
MEANING
There is no accurate position stored in the EEPROM.
INSTRUCTIONS
No stored position:
One of the settings of the GPS receiver settings is incorrect. Using the manager SW of the GPS receiver, set the receiver to store the position into non-volatile
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
GPS receiver alarm: position questionable
FAULT ID
4125: EFaultId_GpsReceiverPositionQuestionableAl
MEANING
The receiver is used in stored position, but has been moved to a new position after that.
INSTRUCTIONS
Position questionable:
1. The GPS receiver has a valid position data, but it is not properly in line with the information estimated from the actual satellite visibility. The reason for
3. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module if needed.
FAULT NAME
GPS receiver alarm: recommended firmware is not in use
FAULT ID
4272: EFaultId_IncompatibleGpsSwVersionAl
MEANING
A software update of the GPS or GNSS receiver could not be done by the BTS. The GPS or GNSS receiver works correctly, but it has an incompatible software version
INSTRUCTIONS
1. Reset the GPS or GNSS module.
2. Block and unblock the BTS to activate a BTS reset.
3. Trigger a software update procedure for the GPS or GNSS module from NetAct or BTS Site Manager.
4. Replace the alarming GPS or GNSS module.
FAULT NAME
GPS receiver alarm: survey in progress
FAULT ID
4123: EFaultId_GpsReceiverSurveyInProgressAl
MEANING
The GPS receiver is running a site or self survey.
INSTRUCTIONS
Survey in progress:
1. No actions required as the the alarm is only informative. Normally, the GPS receiver runs the survey for two reasons:
a. Somebody has started the survey manually.
b. The GPS receiver has noticed that the position has changed, and the receiver has started an automatic survey.
Note also that automatic survey takes place every time during the first start-up.
12/21/2019 Alarms
2. If the automatic survey takes place every now and then, it might be an indication that the sky visibility is poor, and according to the poorly-tracked satellit
3. If the GPS installation is good but the automatic survey still takes place every now and then, there might be a malfunction in the GPS receiver. Perform a (rem
4. If the actions detailed in the previous steps do not correct the situation, there might be an HW fault in the GPS receiver. Check the operation and change the
FAULT NAME
GPS reference source indicates antenna short or overcurrent
FAULT ID
6803: EFaultId_GpsAntennaCurrentHighAl
MEANING
The GPS antenna includes an active amplifier, which is powered over the antenna cable by the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Ante
INSTRUCTIONS
1. If using an external GPS antenna and this alarm sets and clears intermittently during normal operation, it is likely that some external factor in the connectio
2. Consider other alarms that might be occurring or configuration changes that were made just prior to this alarm as possible sources for this alarm.
3. If there are no external factors or if the alarm is persistent, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna GPS Antenn
4. If not using an external GPS antenna, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
High memory consumption
FAULT ID
6502: EFaultId_HighMemoryConsumptionAl
MEANING
The physical memory supervision has detected that memory usage has exceeded 90% (FCT (HW rel.3), ASIA) or 98% (FSP/ABIA).
INSTRUCTIONS
Source:
- FCT (HW rel.3)/AIA: Perform eNB reset.
- FSP/FBB/ABIA: Change the cell configuration to decrease call processing load.
None
FAULT NAME
Incoherence in cell configuration
FAULT ID
4000: EFaultId_IncoherencyInConfiguration
MEANING
Too many cells are commissioned to the BTS.
More LNCELs than the supported maximum number is configured, or too many LCRs are commissioned to one RF module.
INSTRUCTIONS
If other alarms are reported, re-commission the BTS with the correct number of cells per BTS.
Re-commission the BTS with the correct number of LCRs per RF module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Increased BER detected on the optical connection to Radio Module
FAULT ID
1955: EFaultId_IncrBerOnRp3
MEANING
Increased bit error rate has been detected on the optical link to the radio module, which results in sporadic LCV errors in downlink baseband processing.
INSTRUCTIONS
Instructions are divided into three sections. Choose the appropriate section and perform the corresponding steps:
5. Clean the optical connectors that are connected to the SFP. Reset the RF hardware unit and check if this solves the problem.
4. Clean the optical connectors at the RF module end. Reset the RF hardware unit and check if this solves the problem.
2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the system module end. Check measuring equipment documentation for instructi
3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF module end. Check measuring equipment documentation for instructions.
the RF module.
FAULT NAME
Inter-core communication failure
FAULT ID
6814: EFaultId_InterCoreCommFailure
12/21/2019 Alarms
MEANING
A failure has been detected in the internal communication between cores.
INSTRUCTIONS
None
FAULT NAME
Invalid configuration file
FAULT ID
4036: EFaultId_InvalidConfigurationFileAl
MEANING
The commissioning file is corrupted, or an incorrect SCF file has been detected during BTS startup as follows:
1. Commissioning data: The commissioning file is corrupted, or a parameter has a missing or incorrect value.
2. RNW data: "RNW has wrong format," "RNW could not be parsed," "RNW has wrong schema," "Validation failed due to incompatible data," "no RNW cell managedObject i
The commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows:
1. Commissioning data: The commissioning file is missing, or a parameter has a missing or incorrect value.
2. RNW data: "RNW not found," "RNW has wrong format," "RNW could not be parsed," "RNW has wrong schema," "Validation failed due to incompatible data," "no RNW cel
INSTRUCTIONS
Check and correct the contents of the commissioning file.
1. Check and correct the contents of the commissioning file.
2. Recommission the BTS or Flexi Zone SFN Antenna with the valid commissioning file.
FAULT NAME
LNA in bypass mode
FAULT ID
4270: EFaultId_MhaBypassModeAl
MEANING
The MHA was unexpectedly set to bypass mode. The fault might be the result of a conflict in MHA management for a device that can be managed from more than one BTS
INSTRUCTIONS
If LNA is shared between two BTSs and it supports separate AISG ports
for each BTS, check if the LNA is not switched to bypass mode by other BTSs.
FAULT NAME
Low noise amplifier failure
FAULT ID
1839: EFaultId_LNAFailureAl
MEANING
The Radio Module has detected a malfunction of an internal LNA unit.
INSTRUCTIONS
Replace the alarming Radio Module.
FAULT NAME
LTE-LTE RF sharing configuration alarm
FAULT ID
4336: EFaultId_LteLteRfSharingIncorrectConfigurationAl
MEANING
The LTE-LTE RF Sharing configuration and the exchanged information between the two LTE BTSs show conflicts.
INSTRUCTIONS
1. Read the diagnostic information in the alarm to find out detailed information
about the fault reason.
2. For the following reason, update BTS SW to correct version: IncompatibleConfigNeighborEnbSwVersionMismatch.
FAULT NAME
M3 SCTP path failure
FAULT ID
6206: EFaultId_M3SctpPathAl
MEANING
One of the transport paths (SCTP) in SCTP connection to MME (which provides MBMS service) has failed. This is only applicable when SCTP multi-homing is supported.
INSTRUCTIONS
1. Check whether the transport path is alive.
2. Check the configuration of transport addresses at MME.
FAULT NAME
Manual location entry not supported
FAULT ID
4328: EFaultId_ManualLocationEntryNotSupportedAl
MEANING
The BTS has detected that the GNSS receiver does not support the operator-selected manual location entry.
INSTRUCTIONS
Change the GNSS location mode to automatic to cancel the fault. The fault is canceled after 60 seconds.
FAULT NAME
Mast Head Amplifier fault
FAULT ID
3120: EFaultId_MastHeadAmplifierFault
MEANING
The FlexiBTS/AirScaleBTS has detected an abnormal operation, or a failure, in the Masthead Amplifier (MHA).
Note that the Tower Mounted Amplifier (TMA) is synonymous to the MHA, and is used by the Antenna Interface Standards Group (AISG).
12/21/2019 Alarms
INSTRUCTIONS
1. Check the cables related to the Masthead Amplifier (MHA).
2. Block and unblock the RF Module to which the MHA is connected to reset the alarming MHA module.
3. Replace the faulty devices.
FAULT NAME
Maximum number handover/emergency call UEs are connected to the eNB Zone
FAULT ID
6325: EFaultId_MaxNumUePerClusterReachedForEmergencyOrHandoverCall
MEANING
The operator-configured maximum number of UEs connecting through an emergency call or through an incoming handover (MaxNumClusterUe + 10% reserve) has been reache
INSTRUCTIONS
This fault does not require any actions. This alarm clears automatically when the number of connected UEs remains below maxNumClusterUe + 10% reserve for at least
FAULT NAME
Maximum number normal call UEs are connected to the eNB Zone
FAULT ID
6324: EFaultId_MaxNumUePerClusterReachedForNormalCall
MEANING
The operator-configured maximum number of UEs connecting through a normal call (maxNumClusterUe) has been reached. Until one or more of the currently connected UE
INSTRUCTIONS
This fault does not require any actions. This alarm clears automatically when the number of connected UEs remains below maxNumClusterUe for at least 20 seconds.
FAULT NAME
Maximum number of 1xRTT neighbor cells exceeded
FAULT ID
6299: EFaultId_MaximumNumberOfRttNbCellsAl
MEANING
A neighbor cell, which is detected by a UE through measurements due to activated ANR features, could not be stored because the maximum number of 1xRTT neighbor ce
INSTRUCTIONS
The operator should do either of the following after receiving fault to recover the BTS to full operational:
1. Manually remove the neighbor object below limit.
2. Reconfigure or manually change the threshold limit.
FAULT NAME
Maximum number of neighbor eNBs/cells exceeded
FAULT ID
6265: EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded
MEANING
This alarm indicates that the maximum number of LNADJ, LNADJL, or both LNADJ and LNADJL objects has been exceeded in the eNB and that the new object has not been
INSTRUCTIONS
1.Check if the maximum number of LNADJ objects has been reached. If yes, check if there are LNADJ objects that can be manually deleted. This makes space for new L
2.Check if the maximum number of LNADJL objects has been reached. If yes, check if there are LNADJL objects related with the LNADJ object that can be manually del
FAULT NAME
Maximum number of WCDMA neighbor cells is exceeded
FAULT ID
6268: EfaultId_MaximumNumberOfWcdmaNbCellsAl
MEANING
This alarm indicates that a WCDMA neighbor cell, which is reported by a UE through ANR-specific measurements, could not be stored because the maximum number of LN
"A neighbour WCDMA cell which is reported by an UE due to activated ANR feature(s) could not be stored because the maximum number of WCDMA neighbour cells is reac
INSTRUCTIONS
Check if the maximum number of LNADJW was reached. If so, check if there are LNADJW objects that can be manually deleted. This makes space for new LNADJW object.
FAULT NAME
Maximum number of WCDMA neighbor relations is exceeded
FAULT ID
6269: EfaultId_MaximumNumberOfWcdmaNbRelsAI
MEANING
This alarm indicates that a WCDMA neighbor relation, which is reported by a UE through ANR-specific measurements, could not be stored because the maximum number o
"LTE cell ECGI{ecgiAdjEnbId = %d, ecgiLcrId = %d, ecgiPlmnId = { %d, %d, %d}} , WCDMA cell CGI {rncId= %d, CellId= %d, cgiPlmnId = { %d, %d, %d}}".
INSTRUCTIONS
Check if the maximum number of LNRELW objects has been reached. If so, check if there are LNRELW objects that can be manually deleted. This makes space for new LN
FAULT NAME
Maximum number of WCDMA neighbor relations per cell and carrier is exceeded
FAULT ID
6270: EfaultId_MaximumNumberOfWcdmaNbRelsPerCellAndCarrierAl
MEANING
This alarm indicates that a WCDMA neighbor relation, which is reported by a
UE because of activated UTRAN ANR feature, has been stored but at least one
of the mobility parameters of LNRELW (csfbPsHoAllowed, psHoAllowed, srvccAllowed)
has been set to "forbidden" because the number of neighbor relations
(LNRELW instances) exceeds the maximum number of WCDMA neighbor cells, which
might be used by the eNB in measurement configurations (for psHoAllowed or srvccAllowed, limit in 3GPP 36.331 is (32); for csfbPsHoAllowed is LNHOW::maxNumCsfbTar
The additional alarm info holds the ARFCN of the affected carrier frequency as well as the LNCEL and LNRELW instance number in the form of:
"Affected WCDMA ARFCN carrier = %d, LTE cell ECGI{ecgiAdjEnbId = %d, ecgiLcrId = %d, ecgiPlmnId = { %d, %d, %d}} , WCDMA cell CGI {rncId= %d, CellId= %d, cgiPlmnI
INSTRUCTIONS
Check that the maximum number of mobility parameters (either of: csfbPsHoAllowed, psHoAllowed, srvccAllowed) of LNRELW per cell and WCDMA carrier frequency is bel
FAULT NAME
12/21/2019 Alarms
MBMS session cannot be resumed
FAULT ID
6853: EFaultId_MbmsSessionSuspendedAl
MEANING
At least one suspended MBMS session cannot be resumed because of insufficient MBMS resources.
INSTRUCTIONS
This fault is a warning and cannot be cleared. The sessions that cannot be resumed are automatically cleared using M3 Partial Reset procedures.
FAULT NAME
MCE configuration update failure
FAULT ID
6854: EFaultId_MceConfigFailureAl
MEANING
MCE configuration update has finally failed.
The MME could not be informed about the modification of at least one of the following MCE configuration data:
- global MCE ID
- MCE name
- supported MBMS service area identities
INSTRUCTIONS
FAULT NAME
MFBI cell configuration conflict
FAULT ID
6278: EFaultId_MfbiCellConfigurationConflict
MEANING
The EARFCN of an LTE neighbor cell is a mapped EARFCN according to the MFBI-profile configuration (that is, the requirement for a homogeneous MFBI configuration i
As a consequence, HO to this neighbor cell is not possible, and call drop rate might increase if there is no other suitable handover target. If the UE-based ANR i
INSTRUCTIONS
FAULT NAME
MHA operation degraded
FAULT ID
1869: EFaultId_MinorTMAFaultAl
MEANING
A fault in the Masthead Amplifier (MHA) is detected. MHA functionality is degraded. The real impact cannot be determined.
INSTRUCTIONS
Reset the MHA (using Radio Module reset). If this does not help, replace the alarming module.
FAULT NAME
MHA operation failure
FAULT ID
1870: EFaultId_MajorTMAFaultAl
MEANING
A fault in the Masthead Amplifier (MHA) has been detected. The MHA is not working.
INSTRUCTIONS
1. Reset the MHA by using radio module reset.
2. If this does not solve the problem, replace the alarming module.
FAULT NAME
Mismatched RRU optical module <optif ID>
FAULT ID
1969: EFaultId_MismatchedSfpAl
MEANING
The small form-factor pluggable (SFP) module is mismatched.
INSTRUCTIONS
Replace the faulty SFP.
FAULT NAME
Module Clock faulty
FAULT ID
1926: EFaultId_FrModuleClockFaulty
MEANING
The RF module has lost lock to the incoming clock.
INSTRUCTIONS
Instructions are divided into three sections. Execute the steps from the section chosen based on best knowledge and common sense to minimize the cost and time eff
2. Check if the Small Form Factor Pluggable (SFP) is properly connected or mounted in the System Module. If the SFP's connection or mounting is incorrect, readjus
4. Check if the optical cable is properly connected or mounted in the SFP.
5. Clean the optical connectors that are connected to the SFP. Reset the RF HW unit and check if this solves the problem.
2. Check if the Small Form Factor Pluggable (SFP) is properly connected or mounted in the RF module. If SFP connection or mounting is incorrect, readjust the conn
4. Clean the optical connectors at the FR module end. Reset the FR HW unit and check if this solves the problem.
1. Check if the optical cables are not overly bent. If they are, replace the optical cable, since overly bending the optical fiber cables damages the cables and c
2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System Module's end. Check the documentation of the measuring equipment
3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the FR Module's end. Check the documentation of the measuring equipment for
If the alarm continues after executing the steps from sections A, B, and C, replace the FR module.
12/21/2019 Alarms
FAULT NAME
No connection to RP1 interface
FAULT ID
4189: EFaultId_NoRp1ConnectAl
MEANING
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone (Flexi Zone Access Point), Flexi Zone SFN Antenna:
The connection to the RP1 Transport (TRSW) or Radio Frequency (RFSW) interface has been lost.
The connection to RP1 Transport (TRSW) interface has been lost.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
No feedback signal
FAULT ID
1920: EFaultId_FrNoFeedBackSignal
MEANING
The feedback signal to predistortion is too weak or missing. The TX performance is degraded.
INSTRUCTIONS
FAULT NAME
No module fan detected
FAULT ID
1932: EFaultId_FrNoFansDetected
MEANING
The RF module cannot identify the fan vendor or the fan is not installed.
INSTRUCTIONS
4. If alarm continues, replace the fan module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Not critical bit toggling error
FAULT ID
6702: EFaultId_NotCriticalBitTogglingError
MEANING
A non-correctable bit toggling error is detected in the non-critical DSP memory area.
INSTRUCTIONS
1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN
Antenna.
2. If the fault persists, replace the Flexi Zone Micro BTS or Flexi
Zone Access Point.
FAULT NAME
NTP Frequency Synchronization OCXO Calibration Expired
FAULT ID
6822: EFaultId_NtpSyncOcxoCalibrationExpiredAl
MEANING
This fault indicates that the BTS reference oscillator calibration has expired. The reference oscillator calibration is used to minimize the BTS initialization ti
When operating with the Network Time Protocol (NTP) frequency synchronization reference source, long initialization times can be required when the reference oscil
INSTRUCTIONS
Perform the following steps in order until the fault disappears.
12/21/2019 Alarms
1. Check the Ethernet interface functionality used by Network Time Protocol. Check if other faults related to the Ethernet interface exist.
2. Check the Network Time Protocol configuration. Ensure that the NTP Server IP address is configured properly.
3. Check the Network Time Protocol server functionality.
4. Check that the IP connection between the Network Time Protocol server and Flexi Zone Micro BTS or Flexi Zone Access Point is working.
FAULT NAME
Obsolete SW version detected
FAULT ID
24: EFaultId_ObsoleteSwVersionAl
MEANING
There is an attempt to download an unsupported SW version.
INSTRUCTIONS
Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated by the
FAULT NAME
OIC MCU Buffer Full
FAULT ID
2011: EFaultId_OIC_MCUBFullAl
MEANING
The control message traffic between the modules is malfunctioning.
INSTRUCTIONS
Check the alarms for the connected module.
FAULT NAME
Operation on shared optical port failed
FAULT ID
4180: EFaultId_OperationOnSharedOpticalPortFailedAl
MEANING
The shared OptIF mode cannot be read from or changed in the FBBC card.
INSTRUCTIONS
Fault 4180 is raised if switch setting is not successful. After the fourth attempt, group fault 3003 is raised. If there are other working cells on FBBC, the user
FAULT NAME
Optical interface data/control/ethernet buffer full
FAULT ID
2006: EFaultId_OIC_DBRxFullAl
2010: EFaultId_OIC_EBFullAl
MEANING
The RP3 or Ethernet buffering is not working, and the buffer becomes full. The
optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect initialization.
Fault 2006 may be detected in Flexi BTS TDD only.
Fault 2010 may be detected both in Flexi BTS FDD and TDD.
INSTRUCTIONS
1. Exchange the alarming and working links, and check where the alarm is reported
now.
2. If the alarming link remains the same, replace the System Module.
3. If the alarming link changes, replace the module behind that link.
FAULT NAME
Optical Interface faulty
FAULT ID
2000: EFaultId_OIC_TxAl
2001: EFaultId_OIC_PresAl
MEANING
A small form-factor pluggable (SFP) malfunction has occurred (fault 2000), or the SFP module is not physically present, that is, there is no electrical connection
INSTRUCTIONS
1. Check that the small form-factor pluggable (SFP) is properly connected to the System Module.
2. Replace the SFP module.
FAULT NAME
Optical link speed change failure
FAULT ID
4342: EFaultId_OptLinkSpeedChangeFailedAl
MEANING
The optical interface is not operating at the maximum speed. Not all cell configurations are supported.
INSTRUCTIONS
1. Check the optical cable and the SFPs on both ends of the optical interface and replace hardware if needed.
2. Restart the radio unit connected to the affected optical interface.
FAULT NAME
Overload monitoring: High number of neighbor related objects
FAULT ID
6286: EFaultId_HighNumberAnrMoiReachedAl
MEANING
This fault is reported when the BTS detects that the number of neighbor-related objects (which represents the neighboring BTS, and its cells with the relationship
INSTRUCTIONS
Removing neighbor-related objects below the internal threshold turns off the notification alarm. The BTS stays in full operational state.
FAULT NAME
Parallel optical link length mismatch
FAULT ID
4072: EFaultId_ParallelLinkDifferenceTooLargeAl
MEANING
12/21/2019 Alarms
- The mutual length difference of the parallel RP3-01/CPRI links toward one radio module is too large (more than 60 meters in OBSAI RRU, and 146 meters in CPRI RR
- RF sharing has been disabled with master WCDMA because the mutual length difference between the cables of the WCDMA system module-shared RF and the LTE system m
The additional info in the alarm about difference in length should be delivered in the alarm only when LTE is radio master.
The information consists of:
- The number of physical port on the system module where primary link starts.
- The number of physical port on the system module where secondary too long/too short link starts.
- The difference in lengths with information if secondary link is too short or too long.
- The difference in delays in nanoseconds.
INSTRUCTIONS
If the fault is detected in non-sharing configuration:
1. Block and unblock the radio module where the faulty fiber cable is connected. Please note it will reset all cells for which the radio module provides services.
2. If it does not help, replace parallel RP3-01/CPRI fiber links toward one radio module so that the maximum mutual length difference between fibers is less than
If the fault is triggered because of an incorrect RF sharing configuration, check that the RF sharing feature is enabled on synchronization master system module.
If the alarm with fault 4038 (Radio master conflict) is reported at the same time,
follow the instruction for fault 4038 because in some cases, 4038 may be the root cause of fault 4072.
FAULT NAME
Peer system module connection lost
FAULT ID
4110: EFaultId_PeerSystemModuleConnectionLostAl
MEANING
The master system module has lost optical or sync connection to the peer system module.
INSTRUCTIONS
Check the reported alarms of the peer system module.
Check the optical connection between the master LTE and peer system modules.
In a BTS configuration where one system module provides PPS synchronization signal to another system module over a separate sync cable (sync hub configuration), c
FAULT NAME
Phase error exceeds 5 us limit
FAULT ID
6280: EFaultId_PhaseSynchronizationErrorAl
MEANING
This fault indicates that the absolute phase error of a BTS exceeds the limit of 5 us, and the features depending on that accuracy have been deactivated. This ca
- the absolute value of the estimated phase error of an eNB has exceeded the limit of 5 us.
- the eNB is more than 6 hours in holdover mode which means that the estimated
phase error value might not be reliable. It is assumed in this case that
the real absolute value of phase error is greater than 5 us.
- the eNB is more than 24 hours in assisted holdover mode which means that the estimated phase error value might not be reliable. It is assumed in this case that
the real absolute value of phase error is greater than 5 us.
- the eNB is synchronized by a Sync Master, which reports the phase error of the provided sync signal. The absolute value of the estimated total phase error in th
INSTRUCTIONS
If GPS is configured as the reference clock, do the following:
If the TOP signal is configured as the reference clock, check the connection to the TOP server.
FAULT NAME
Pipe dangerously overheating
FAULT ID
1938: EFaultId_FrPipeOverheat
MEANING
The validated temperature of any PA or Pipe sensor in the RF module is greater than or equal to the pre-defined value in the unit property file.
INSTRUCTIONS
1. Check if the ambient temperature or environmental conditions are within the design limits of the radio module. When the ambient temperature or environmental co
2. Check if the air flow is not blocked by some objects. Ensure the minimum thermal clearances are followed. Remove any objects that might be blocking the air flo
3. Check if excessive sunlight is causing an overheat. Install sunshield following the mounting instructions and recommendations.
FAULT NAME
Post test failed
FAULT ID
1925: EFaultId_FrPostTestFailed
MEANING
An RF module's power-on self-test has failed at start-up.
INSTRUCTIONS
2. If the problem continues after performing step 1, replace the RF HW unit.
FAULT NAME
Power on #smodLogicalId #pwrLineId line switched off at the front panel
FAULT ID
4365: EFaultId_RfPowerSwitchedOffFromFrontPanelAl
MEANING
Power feeding for the given Radio Module has been switched off by the user from
the front panel of the PDU.
INSTRUCTIONS
Enable power feeding towards the Radio Module by switching RF power on in the BTS Site Manager or at the front panel of the PDU.
FAULT NAME
Power on #smodLogicalId #pwrLineId line switched off remotely by user
FAULT ID
4107: EFaultId_RfPowerSwitchedOffFromBtsSmAl
MEANING
Power feeding for the given radio module has been remotely switched off using BTS Site Manager.
12/21/2019 Alarms
INSTRUCTIONS
Enable power feeding toward the radio module by switching RF power on in BTS Site Manager.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Previously downloaded plan [planId] was overwritten by a new plan [planId]
FAULT ID
4340: EFaultId_PreviouslyDownloadedPlanOverwrittenAl
MEANING
Previously downloaded plan[Id] was overwritten by a new plan[Id].
INSTRUCTIONS
No action is required.
FAULT NAME
Radio memory consumption exceeds abnormal threshold
FAULT ID
4329: EFaultId_RadioMemAboveAbnormalThresholdAl
MEANING
Free memory on the radio module is limited.
INSTRUCTIONS
Recovery restart of the faulty radio module is highly recommended and should be scheduled in the nearest suitable time (for example, during low traffic period).
FAULT NAME
Radio memory consumption exceeds critical threshold
FAULT ID
4330: EFaultId_RadioMemAboveCriticalThresholdAl
MEANING
The radio module has no free memory.
INSTRUCTIONS
Recovery restart of the faulty radio module is highly recommended and should be done as soon as possible.
FAULT NAME
Radio module access panel open
FAULT ID
1991: EFaultId_FrAccessPanelOpenAl
MEANING
The Radio Module is reporting that the access door protecting the maintenance data port is open. The maintenance port allows local control of the Radio Module.
INSTRUCTIONS
Check access door and close if open.
FAULT NAME
Radio module internal communication failure
FAULT ID
1990: EFaultId_FrInternalCommunicationFailureAl
MEANING
The fault is reported in radio modules that consists of two separate hardware units connected by optical cable. The near end Radio Module subunit cannot communic
INSTRUCTIONS
1. Reset the alarming radio unit.
2. If reset has not canceled the fault condition, replace the alarming radio unit hardware.
FAULT NAME
Radio module internal hardware assignment indeterminate
FAULT ID
1993: EFaultId_FrInternalHwAssignmentIndeterminateAl
MEANING
The fault is reported by complex radio modules with multiple physical units where functionality is distributed. An incompatibility has been found with the identif
INSTRUCTIONS
2. If a reset does not cancel the fault condition, ensure that the Primary subunit does not have an Alarm Cap on the ASIG ALM connector (the ALM connector can hav
FAULT NAME
Radio module internal hardware configuration mismatch
FAULT ID
1992: EFaultId_FrInternalHwConfigurationMismatchAl
12/21/2019 Alarms
MEANING
The fault is reported by complex radio modules with multiple physical units where functionality is distributed. An incompatibility has been found between board r
INSTRUCTIONS
2. If a reset does not cancel the fault condition, replace one or both subunits so that they are both of the same type.
FAULT NAME
Radio module low optical signal level to next hop
FAULT ID
1995: EFaultId_FrLowOpticalSignalLevelToNextHopAl
MEANING
The received optical signal on the link port is unexpectedly low from the next hop (further from system module), though communication is still possible.
There is a poor CPRI link connection, bad CPRI cable, or failing CPRI transceiver at the next radio module connected to the cable reported as fault source.
INSTRUCTIONS
1. Reset the radio module reporting the fault (one with blinking red LED display) by blocking/unblocking it. The radio reporting the fault is the one on the cable
2. Reset the system module or radio on the other end of the cable reported as fault source.
3. Replace the SFP on the radio module port of the radio reporting the fault.
4. Replace the SFP on the system module or extension baseband module or radio port on the other end of the cable reported as fault source.
6. Replace the radio module reporting the fault, one with blinking red LED display.
7. If resetting the device where the cable that is reported as the fault source is terminated helps, but the fault is reported again after some time or if the act
FAULT NAME
Radio module low optical signal level to upper hop
FAULT ID
1994: EFaultId_FrLowOpticalSignalLevelToUpperHopAl
MEANING
The received optical signal on the link port is unexpectedly low from upper hop (toward the system module), though communication is still possible.
There is a poor CPRI link connection, bad CPRI cable, or failing CPRI transceiver at the previous radio module or system module connected to the cable reported as
INSTRUCTIONS
1. Reset the radio module reporting the fault (the one with the blinking red LED display) by blocking/unblocking it. The radio reporting the fault is the one on t
2. Reset the system module or radio on the other end of the cable reported as the fault source.
6. Replace the radio module reporting the fault (the one with blinking red LED display).
FAULT NAME
Receive diversity expansion module communication failure
FAULT ID
1989: EFaultId_FrReceiveDiversityExpansionModuleCommunicationFailureAl
MEANING
The communication radio module with external Receive Diversity Expansion Module (RDEM) is lost. The cable to the external RDEM module may be broken or disconnecte
INSTRUCTIONS
1. Reset the alarming radio module.
2. If it does not help, replace the cable between the radio module and the Receive Diversity Expansion Module (RDEM).
3. If previous steps have not cancelled alarm reported due to the fault, replace the alarming radio module.
FAULT NAME
Receiving failure in Optical Interface
FAULT ID
2002: EFaultId_OIC_RxAl
MEANING
The incoming optical signal to the Small Form-Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached.
The connection between the System Module and the RF Module is broken, or the connection between the Baseband Module (for example, FBBC) and the RF Module is broke
INSTRUCTIONS
2. Check the Small Form-Factor Pluggable (SFP) from both ends (the System Module and the module behind the faulty link). The optical interface LED indicates the f
3. Clean the connectors, test the fiber cable, and replace it if it is faulty.
4. If the previous steps do not help, replace the module behind the faulty link.
FAULT NAME
RET Antenna control failure
FAULT ID
1842: EFaultId_MotorJamAl
1843: EFaultId_ActuatorJamAl
1844: EFaultId_NotCalibratedAl
1845: EFaultId_NotConfiguredAl
1846: EFaultId_ActuatorInterferenceAl
MEANING
1845: TILT is not configured.
Others: Antenna tilting is not possible or might function incorrectly.
INSTRUCTIONS
Perform RET calibration. If that does not help, replace the RET unit.
In case of 1845: send a valid configuration file to the alarming device.
FAULT NAME
RF BB bus configuration error
FAULT ID
1905: EFaultId_FrRfBbBusConfigError
MEANING
The RF Module baseband bus was configured incorrectly.
INSTRUCTIONS
1. Confirm if the existing applied configuration is within the configured RF
HW capabilities.
2. Check BTS connections and commissioning settings.
3. Block or unblock the BTS.
4. If HW configuration is confirmed, then this problem is caused by eNB
SW. Check other active alarms.
12/21/2019 Alarms
FAULT NAME
RF BB bus synchronization error
FAULT ID
1904: EFaultId_FrRfBbBusSynchError
MEANING
The baseband bus between the System Module and RF Module is out of synchronization.
INSTRUCTIONS
Instructions are divided into three sections. Execute steps from the chosen section based on best knowledge and common sense to minimize the cost and time effort.
2. Check if the SFP (Small Form Factor Pluggable) is properly connected/mounted in the System Module. If the SFP connection/mounting is not correct, re-adjust the
2. Check if the SFP (Small Form Factor Pluggable) is properly connected/mounted in the RF module. If the SFP connection/mounting is not correct, readjust the conn
1. Check if the optical cables are not overly bent. If they are, replace them since overly bending the optical fiber cables damages them and can detach or damage
3. OPTIONAL: Test the fiber cable (for example measure the optical attenuation) from the RF Module end. Check the measuring equipment documentation for instructio
If the alarm is still observed after executing steps from sections A, B, and C, replace the RF module.
FAULT NAME
RF Module blocked
FAULT ID
1931: EFaultId_FrBlocked
MEANING
This fault is detected in a radio-sharing configuration where a WCDMA FSM is the master system module, and a LTE FSM/ASIA plays the role of the slave module. This
INSTRUCTIONS
No action is needed.
FAULT NAME
RF Module configuring failed
FAULT ID
1900: EFaultId_FrConfiguringFailed
MEANING
The RF module configuration has failed because of an HW or SW fault.
INSTRUCTIONS
For URGA, URCB, URCC, and URKA radio variants, if the fault is preceded by a
dual branch failure with any combination of faults with IDs 1839, 1907, 1911, or 1957 in the radio, reset the radio first to attempt to clear the fault before pro
For all radio variants:
1. Confirm if the currently applied configuration is within the configured RF HW capabilities.
In LTE-LTE sharing, check if the configuration of both eNBs is consistent with the shared radio capability. Correct the configuration, recommission the eNBs, and
3. Block/unblock the BTS.
4. If the HW configuration is confirmed as correct, this problem is caused by the eNB SW. Check other active alarms.
FAULT NAME
RF Module critical file not found
FAULT ID
1901: EFaultId_FrCriticalFileNotFound
MEANING
A critical configuration file is missing from the RF Module.
INSTRUCTIONS
1. Verify if the HWP1 file is present in the FR module. Download the file if it is missing. Reset the FR module.
2. If the file is present, block/unblock the RF HW unit.
3. If the problem continues after performing step 2, replace the FR HW unit.
2. Replace the Flexi Zone Micro BTS.
Flexi Zone:
1. Reset Flexi Zone Access Point.
1. Reset Flexi Zone SFN Antenna.
FAULT NAME
RF Module failure
FAULT ID
3010: EFaultId_RfModuleFailure
MEANING
The BTS has detected an abnormal operation or a failure in the internal functionality of the RF Module.
INSTRUCTIONS
2. If the problem still persists after step 1 has been performed, replace the RF HW unit.
1. Check the other active Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna faults and act accordingly.
3. If that does not help, replace the faulty Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
12/21/2019 Alarms
FAULT NAME
RF Module faulty primary optical link
FAULT ID
1984: EFaultId_FrPrimaryLinkLossAl
MEANING
The radio unit has detected a failure on its optical connection to the system module or an upstream radio unit (chaining case).
INSTRUCTIONS
1. Check the small form-factor pluggable (SFP) from both ends (the system module and the radio unit) and replace if one or both is faulty or unsupported.
2. Clean the connectors, test the fiber cable, and replace them if they are faulty.
3. If the previous steps do not help, replace the alarming radio unit hardware.
FAULT NAME
RF Module file not found
FAULT ID
1902: EFaultId_FrFileNotFound
MEANING
The RF Module SW has detected that a non-critical configuration file is missing.
INSTRUCTIONS
1. Check that the TEMP and CALI files are present. Upload any missing files. Reset the RF Module.
2. If the files are present, reset the FR HW unit.
3. If the problem is still observed after performing step 1, replace the FR HW unit.
1. Block and/or unblock BTS.
Flexi Zone:
FAULT NAME
RF Module gain adjusting failure
FAULT ID
1908: EFaultId_FrGainAdjust
MEANING
The TX output power adjustment has failed.
CLGC convergence has failed. Gain target cannot be achieved.
INSTRUCTIONS
2. If the problem is still observed after performing step 1, replace the RF HW unit.
1. Check the configuration.
FAULT NAME
RF Module out of order
FAULT ID
1912: EFaultId_FrOutOfOrder
MEANING
The RF module is out of order because of a software or hardware fault.
INSTRUCTIONS
2. If the problem continues after step 1 has been performed, replace the RF HW unit.
FAULT NAME
RF Module power input faulty
FAULT ID
1959: EFaultId_FrPowerInputFaultAl
MEANING
Input voltage to the radio unit is outside of the expected range, but the radio unit power supply can still provide output voltages adequate for operation.
INSTRUCTIONS
1. Check the power supply to the affected radio module.
2. If the alarm persists, replace the radio module that is generating the alarm.
FAULT NAME
RF Module power supply output faulty
FAULT ID
1918: EFaultId_FrPowerOutputFault
MEANING
The power supply supervision has detected an overvoltage, undervoltage, or overcurrent in the RF module.
INSTRUCTIONS
Flexi Zone Micro FDD, Flexi Zone, Flexi Zone SFN Antenna:
FAULT NAME
RF module unauthorized
12/21/2019 Alarms
FAULT ID
4278: EFaultId_RfModuleUnauthorizedAl
MEANING
RFM product authorization has failed because of missing RFM properties. RFM
is not supported by the current BTS software release and the BTS did not find
relevant hardware properties for the RF module on FSM. The BTS failed to retrieve the corresponding RFM plug-in module from the Network Management System as well.
INSTRUCTIONS
1. Make sure that the corresponding RFM plug-in module has been installed on the network server in NMS (NetAct SW Archive).
2. Update the corresponding RFM plug-in software module in the BTS/eNB from NetAct.
3. Supply the RFM plug-in software module to BTS/eNB locally via BTS Site Manager if NetAct connection is not available.
Note: You need to commission the radio module before it can be taken into use.
FAULT NAME
RF Power decreased
FAULT ID
1927: EFaultId_FrPowerDecreased
MEANING
The highest temperature exceeds the power decrease limit in the RF module.
INSTRUCTIONS
1. Check if the ambient temperature or environmental conditions are within the design limits for the radio module. When the ambient temperature or environmental c
2. Check if the air flow is not blocked by some objects. Make sure minimum thermal clearances are followed. Remove any objects that might be blocking the airflow,
3. Check if excessive sunlight is causing an overheat. Install sunshield following mounting instructions and recommendations.
FAULT NAME
RP3 routing collisions are detected on FR module
FAULT ID
1958: EFaultId_Rp3CollisionOnFr
MEANING
The FR module has detected permanent RP3 routing collisions in either downlink (TX), or uplink (RX) transmission directions.
INSTRUCTIONS
1. Check the BTS connections and commissioning settings.
2. Block and unblock the BTS (using the local BTS Site Manager connection if a remote connection is not possible).
FAULT NAME
RRU CPU and DSP link failure
FAULT ID
1961: DspLinkFailureAl
MEANING
The CPU cannot connect to the DSP.
INSTRUCTIONS
FAULT NAME
RRU DPD self test failure
FAULT ID
1960: EFaultId_DpdTestFailureAl
MEANING
The RRU digital pre-distortion (DPD) has failed during self test.
INSTRUCTIONS
2. If that does not help, replace the RF Module that is generating the alarm.
FAULT NAME
RRU power loss
FAULT ID
1972: EFaultId_RruAcPowerLossAl
MEANING
The RRU has lost its power supply.
INSTRUCTIONS
1. Check the power connection to the RF module.
FAULT NAME
RX out of order
FAULT ID
1911: EFaultId_FrRxOutOfOrder
MEANING
The RX RF synthesizer of the RF module is not locked.
For SNMP interface:
The received power is low for the RRH.
For CPRI-A interface:
The RX path in the FR module is faulty.
INSTRUCTIONS
2. If the problem continues after resetting the RF HW unit, replace the RF HW unit.
3. In case of SNMP radio, the only way to clear the fault is to reset the radio or replace the unit.
1. Reset the HW unit.
2. If the problem continues after resetting the HW unit, replace the HW unit.
12/21/2019 Alarms
FAULT NAME
S1 eNB configuration update failure
FAULT ID
6321: EFaultId_S1EnbConfigurationUpdate
MEANING
The S1 eNB configuration update procedure has failed.
The MME could not be informed about the modification of at least one of the following eNB configuration data:
- eNB Name
- Supported TAs (TAC, PLMN Identities)
- Default paging DRX
INSTRUCTIONS
FAULT NAME
Serial console activated
FAULT ID
4334: EFaultId_SerialConsoleActivatedAl
MEANING
Serial console is activated on BTS.
INSTRUCTIONS
Disable the serial console (set U-boot variable console_uart to -1).
FAULT NAME
Severe SFP performance aggravation <optIf ID>
FAULT ID
1966: EFaultId_SevereSfpPerformanceAggravationAl
MEANING
The optical interface is not working properly; performance aggravation is high.
INSTRUCTIONS
1. Check the cables between the System Module or ABIA and RF Module.
4. If those do not help, replace the RF module that is causing the alarm.
FAULT NAME
Severe SFP reception power aggravation <optIf ID>
FAULT ID
1967: EFaultId_SevereSfpReceptionPowerAggravationAl
MEANING
The optical interface is not working properly. The received power aggravation is high.
INSTRUCTIONS
FAULT NAME
SFN Antenna Discovery Failure Due to Misconfiguration
FAULT ID
4346: EFaultId_AntDiscFailMisconfAl
MEANING
This denotes the inability to identify the SFN Antenna based on the information provisioned in ANTMOD or APANTMOD.
INSTRUCTIONS
1. Verify that the ANTMOD or APANTMOD provisioning data have been correctly entered.
2. Verify if the siteID provisioned on the SFN Antenna was entered correctly.
FAULT NAME
SFN Antenna Not Connected Successfully
FAULT ID
4347: EFaultId_AntNotConnectedSuccessfullyAl
MEANING
The target SFN Antenna has not yet been successfully connected to the Flexi Zone Micro BTS or Flexi Zone Access Point. This might mean that the physical SFN Anten
INSTRUCTIONS
If the target SFN Antenna does not physically exist, ignore this fault or clean it up by deleting the target SFN Antenna. Otherwise, perform the following steps:
1. Check all other alarms posted against the target SFN Antenna.
2. Check the alarms raised on the SFN Antenna through WebUI.
FAULT NAME
SFP Failure <optIf ID>
FAULT ID
1948: EFaultId_AbnormalOpticalSfpOfIrInterfaceAl
MEANING
The small form-factor pluggable (SFP) module might be missing or faulty.
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
SFP missing <OptIf ID>
FAULT ID
1964: EFaultId_SfpMissingAl
MEANING
The optical interface is not working properly. The Small Form-factor Pluggable (SFP) module might be missing, or it might be faulty.
INSTRUCTIONS
FAULT NAME
SFP on RF Module faulty or unsupported
FAULT ID
1986: EFaultId_SfpOnRadioModuleFaultyOrUnsupportedAl
MEANING
The SFP on the radio unit is either faulty or not supported.
INSTRUCTIONS
2. Reset the affected radio unit.
FAULT NAME
Shared radio not synchronized to Radio Master
FAULT ID
4253: EFaultId_SharedRadioNotSyncToMasterAl
MEANING
The radio slave system module cannot use the shared radio because the radio master system module has not provided a reference clock to the shared radio.
INSTRUCTIONS
Perform following actions until the problem is solved:
1. Check the optical connection between the radio master system module and the shared radio.
2. Check the alarms in the radio master system module and act accordingly.
3. Reset the radio master system module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
TD-SCDMA minor alarm
FAULT ID
4179: EFaultId_TdscdmaMinorAl
MEANING
The Ir router has reported a minor alarm that is caused by TD-SCDMA. TD-LTE performance might be affected.
INSTRUCTIONS
FAULT NAME
Temperature alarm
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Temperature too low (Heating ongoing)
FAULT ID
1922: EFaultId_FrTemperatureTooLow
MEANING
Out of order unit status: The radio unit is too cold for proper operation. Heating of the module is ongoing.
Working unit status: The radio unit is below its normal operating temperature but is still capable of transmitting. Problems might occur.
INSTRUCTIONS
Wait until the alarm is canceled. This might take up to 30 minutes.
If the alarm is not canceled, check if the ambient temperature is within the design limits for the radio module.
If the ambient temperature is out of limits, then the alarm is expected and no further actions are needed.
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Transmission quality deteriorated
FAULT ID
1921: EFaultId_FrTransmissionQualityDetoriated
MEANING
The TX signal adjustment has failed.
INSTRUCTIONS
2. If the problem still persists after performing step 1, replace the RF HW unit.
FAULT NAME
Tuning frequency out of range
FAULT ID
4043: EFaultId_TuningFrequencyOutOfRangeAl
MEANING
The Radio Module has detected that the requested frequency does not fit the capabilities offered by Radio Module.
INSTRUCTIONS
Re-configure the frequency settings in a proper way with respect to the capabilities of the Radio Module.
FAULT NAME
TX input overdrive
FAULT ID
1985: EFaultId_FrTxInputOverdriveAl
MEANING
Hardware protection logic in the radio unit has activated overdrive protection on the TX path to avoid damage to hardware. Overdrive protection keeps the TX path
INSTRUCTIONS
1. Confirm if the existing applied configuration is within the configured FR HW capabilities.
3. Restart the radio unit.
4. If the fault condition persists after the radio restart, restart the BTS.
5. If the HW configuration is confirmed, then this problem is caused by the eNB SW. Check other active alarms.
FAULT NAME
TX out of order
FAULT ID
1907: EFaultId_FrTxOutOfOrder
MEANING
The RF module's TX path cannot be used.
INSTRUCTIONS
1. Check the connection and integrity of the antenna connector, cable, and antenna.
2. If this is for more than two RF units within the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna, reset the alarming RF HW unit.
3. Reset the BTS device. If the alarm persists, replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
FAULT NAME
TX output overdrive
FAULT ID
1983: EFaultId_FrTxOutputOverdriveAl
MEANING
Hardware protection logic in the radio unit has disabled the TX path to protect the radio unit because of an overdrive condition detected in the power amplifier c
INSTRUCTIONS
1. Check whether any other alarms concerning the faulty unit have been reported (such as Input Overdrive or high VSWR). If other alarms have been reported, follow
3. If previous steps have not canceled the fault condition, replace the alarming radio unit hardware.
12/21/2019 Alarms
FAULT NAME
Unit (module) dangerously overheating
FAULT ID
1937: EFaultId_FrDangerouslyOverheat
MEANING
The validated RF sensor temperature is greater than or equal to the pre-defined value in the unit property file.
INSTRUCTIONS
1. Check if the ambient temperature/environmental conditions are within the design limits of the radio module. When the ambient temperature/environmental conditio
2. Check if the air flow is not blocked by some objects. Make sure the minimum thermal clearances are followed. Remove any objects that might be blocking the air
3. Check if excessive sunlight is causing an overheat. Install sunshield, following the mounting instructions and recommendations.
FAULT NAME
Unit (module) temperature is high
FAULT ID
1936: EFaultId_FrTempHigh
MEANING
The validated RF module temperature is higher than or equal to the pre-defined maximum allowed value.
INSTRUCTIONS
FAULT NAME
Unit blocked
FAULT ID
48: EFaultId_UnitBlockedAl
MEANING
A module is blocked with the BTS Site Manager.
The purpose is to avoid fault indications that might be raised during the module maintenance task.
The fault is raised only when an LTE system module (FSM) is the master agent of the blocked radio module (FR), or when an LTE system module shares a CPRI/Ir radio
INSTRUCTIONS
Unblock the module with the BTS Site Manager.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unit temperature is high
FAULT ID
2: EFaultId_UnitOverheatAl
MEANING
The temperature of a unit exceeds the threshold value.
INSTRUCTIONS
Check the active fan alarms and the air flow of the BTS.
FAULT NAME
Unit unidentified
FAULT ID
1923: EFaultId_FrUnitUnidentified
MEANING
The permanent memory in the RF module is corrupted, and the module product code or serial number is missing, or the module product code is unknown.
INSTRUCTIONS
1. Check the configuration. Download the updated configuration if required.
12/21/2019 Alarms
2. Reset the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
3. Replace the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
FAULT NAME
Unsigned software release has been successfully downloaded
FAULT ID
4268: EFaultId_UnsignedSwReleaseAl
MEANING
An unsigned software release has been downloaded to a BTS system module that is currently running a software release that implements software signature checking.
INSTRUCTIONS
No manual action is needed from the operator.
FAULT NAME
Validation of signed file failed
FAULT ID
4145: EFaultId_SignatureValidationFailedAl
MEANING
SW file validation against its signature has failed.
INSTRUCTIONS
Update the BTS to the required SW version.
If 7650 is active, immediate activation is mandatory.
FAULT NAME
VSWR major alarm
FAULT ID
1837: EFaultId_VSWRMajorAl
MEANING
The VSWR value exceeds the level that is defined as a criterion for VSWR major event. The impedance of the antenna line does not match the impedance that the radi
The detected VSWR exceeds the predefined threshold. The antenna, antenna feed line, or both are disconnected, mismatched, or damaged.
INSTRUCTIONS
1. Check the antenna cables, connectors, antenna, and antenna line devices that can interfere with the RF signal.
2. Check the antenna line (TX-cable-antenna) impedance matching.
Note: For CPRI-A radios, the alarm with fault 1837 is reported if the VSWR value exceeds the level that is defined as a criterion for VSWR major only once. It mea
For other radio types, the alarm is reported if the VSWR value exceeds the threshold in more than one consecutive measurements. Short or accidental peak of the VS
1. Check the connection and integrity of antenna connectors, cable, and antenna.
2. Reset the BTS device. If the alarm persists, replace the BTS.
Flexi Zone:
2. Reset the Flexi Zone Access Point. If the alarm persists, replace the Flexi Zone Access Point.
2. Reset the Flexi Zone SFN Antenna. If the alarm persists, replace the Flexi Zone SFN Antenna.
FAULT NAME
VSWR minor alarm
FAULT ID
1838: EFaultId_VSWRMinorAl
MEANING
The VSWR value exceeds the level defined as criterion for VSWR Minor event. The impedance of the antenna line does not match the impedance required by the Radio M
INSTRUCTIONS
1. Check the antenna cables, connectors, antenna, and antenna line devices that might cause interference with the RF signal.
Note: For CPRI-A radios, the alarm with fault 1838 is reported if VSWR value exceeds the level that is defined as criterion for VSWR minor only once. It means the
For other radio types, the alarm is reported if VSWR value exceeds the threshold in more than one consecutive measurements. Short/accidental peak of VSWR value wi
Table 12252: BASE_STATION_OPERATION_DEGRADED
Name: BASE_STATION_OPERATION_DEGRADED (11519) Severity: indeterminate Release:

Type: equipmentAlarm Specific problem: BASE STATION OPERATION DEGRADED FL16A
Package: racfl.BASE_STATION_OPERATION_DEGRADED Implicitly cleared: true
Description: BASE STATION OPERATION DEGRADED A major fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm. The effect of the fault on the
functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels the alarm
when the fault has been corrected.
Below is the list of BTS fault(s) which might have caused this alarm in BTS FL16A/TL16A release. In case of earlier SW release and in case you need more detailed
FAULT NAME
2M external reference missing
FAULT ID
1899: EFaultId_2MExtRefMissAl
MEANING
The reference clock monitoring has detected a signal loss of 2.048 MHz received from an external reference source, connected to Sync In interface of the System Mo
INSTRUCTIONS
1. Check the cabling (connected to Sync In interface).
2. Check if the 2.048 MHz reference source is working normally, and the 2.048 MHz signal is available.
12/21/2019 Alarms
FAULT NAME
Address mismatch in summing
FAULT ID
2019: EFaultId_Muksu_SsubMmAl
MEANING
There is a baseband bus address mismatch in the summing. There are two possible causes:
1. A configuration error (two different baseband units functioning) - after an acknowledgement, the fault returns.
2. Data corruption on the bus - appears once when an unsynchronized data is sent by the baseband.
INSTRUCTIONS
Check the antenna mapping to the local cells in the commissioning file.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
1. Restart the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
2. Reset the BTS.
3. Replace the BTS.
Flexi Zone:
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
BTS file error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
FAULT NAME
BTS master clock tuning failure
FAULT ID
1818: EFaultId_Ov_OscAl
MEANING
The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is less than or equal to the Min.OcxoControlValue.Alarm.Set value specified i
The master clock frequency is tuned to within 5% of its minimum or maximum offset. The Flexi Zone Micro BTS or Flexi Zone SFN Antenna does not use DAC tuning.
INSTRUCTIONS
1. Check the other alarms of the BTS and FTM and act accordingly.
2. If there are no other synchronization-related alarms active. Start the fast tuning with the BTS Site Manager.
3. Reset the site. Run fast tuning again.
4. Check the reference signal accuracy by measuring it with a frequency counter (requires a good timebase for the counter). The reference signal can be found from
This fault is most likely the result of a BTS hardware problem, or a reference source that is being followed by the BTS that is in a faulted condition, thereby pr
1. Identify the currently selected synchronization reference source of the BTS with the active 1818 fault. If it is a transport-based reference source that involv
2. If the BTS uses its GPS reference source while the 1818 fault, or if the 1818 fault, persists for more than two hours after correcting, and problems associated
FAULT NAME
BTS or unit temperature too high
FAULT ID
4182: EFaultId_BtsTempTooHighAl
MEANING
The temperature of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has exceeded the predefined threshold.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
GPS source:
FAULT NAME
BTS reset required
FAULT ID
MEANING
This fault notifies the operator that the BTS must be reset to solve a problem that has been discovered by the BTS O>M system, and that the BTS O>M will not trigg
5. The BTS O>M system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed
6. In BTS runtime, the BTS O>M system has detected resources necessary to cell setup that were not detected during BTS start-up, for example, commissioned radio m
7. BTS O>M has detected an extension baseband module, for example, FBBC, on the same QSFP port, which is different than the previously-removed baseband card, for
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
Carrier aggregation relation configuration error
FAULT ID
6291: EFaultId_CarrierAggregationRelationConfigurationErrorAl
MEANING
BTS has detected carrier aggregation relation misconfiguration. One or more of the configured carrier aggregation relation(s) points towards a cell that does not
INSTRUCTIONS
Perform the steps below in the listed order until the BTS fault disappears.
1. Check BTS commissioning that all the carrier aggregation relations are pointing towards a proper cell that exists within the carrier aggregation cluster. Modif
2. If an existing cell is totally missing from BTS within the carrier aggregation cluster, add the cell.
3. If there are no mismatches in the carrier aggregation relations, reset the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Control Plane IP Address Mismatch
FAULT ID
6816: EFaultId_CplaneIpAddressMismatchAl
MEANING
The value of the parameter "IPNO:cPlaneIpAddress" does not match the one configured in FxP, which is the IP address for either the nbcplane or nbmplane interface
INSTRUCTIONS
Correct the value of the parameter "IPNO:cPlaneIpAddress" to match the one configured in FxP.
12/21/2019 Alarms
FAULT NAME
CRAN inter-BTS connection loss alarm
FAULT ID
4275: EFaultId_CranInterBtsConnectionLossAl
MEANING
The connection between two BTSs in the Centralized Radio Access Network (CRAN) cluster is not detected or is lost.
INSTRUCTIONS
Check the optical connection between the extension baseband cards of the BTSs working in the same CRAN cluster.
FAULT NAME
CRAN intra-BTS FSP connection loss alarm
FAULT ID
4318: EFaultId_CranInterFspConnectionLossAl
MEANING
The connection between FSPs using CPRI front-haul communication within the BTS in CRAN operation is lost.
INSTRUCTIONS
Check the optical connection:
1) between the FSP cards or
2) between FSP card and system module card
supporting cells working in the same CRAN cluster.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Antenna.
SFN Antenna.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
3. REMOTE ACTIONS
FAULT NAME
FAULT ID
MEANING
baseband unit.
INSTRUCTIONS
FAULT NAME
Fatal OSE Error
FAULT ID
MEANING
Flexi BTS FDD/TDD:
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
Fault between FSM and FSP because of the lack of RP1 clock
FAULT ID
412: EFaultId_LostFrameSync
MEANING
Synchronization between the FCM/FCT and FSP is lost.
Synchronization between the FCT and ABIx is lost.
INSTRUCTIONS
2. If the BTS block/unblock does not help and the fault is reported by all FSP/ABIx modules or by FSP module on system module board, replace the system module. Ot
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Flash operation failure
FAULT ID
214: EFaultId_FlashWrAl
215: EFaultId_FlashRdAl
MEANING
A flash memory operation failure. If this fault continuously appears, the flash chip might be broken.
INSTRUCTIONS
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming
module.
2. Reset the alarming module. There are no recovery actions, therefore
reset can be tried once. If that does not help, replace the alarming
module.
FAULT NAME
FSP overheating
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FSP subunit lost
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms

FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
GTP tunnel setup for inter-site CA failed
FAULT ID
6296: EFaultId_PermanentGtpRoutesSetupFailureAl
MEANING
The GTP tunnel between two Flexi Zone Access Points is out of service.
INSTRUCTIONS
1. Reset the faulty Flexi Zone Access Points.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Inter eNB CA parameter(s) inconsistency in between eNBs
FAULT ID
6282: EFaultId_InterEnbCaParamsInconsistencyAl
MEANING
An inconsistency has been detected between cluster members, which prevents the
inter-eNB CA feature from being enabled.
INSTRUCTIONS
Re-configure parameters that are related to the "Inter eNB Carrier Aggregation" feature.
FAULT NAME
Inter eNB carrier aggregation configuration does not match available baseband HW
FAULT ID
4305: EFaultId_InterEnbCaConfNotMatchingBbHwAl
MEANING
The configuration of the inter-eNB carrier aggregation in the SCF of own eNB and peer eNBs cannot be supported with the detected HW.
INSTRUCTIONS
To clear the alarm, do any of the following:
- Switch off the inter-eNB carrier aggregation completely.
- Provide the necessary HW, configuration, or both, and reset the BTS.
- Replace the HW (which has been configured, but faulty) if the HW is the root
cause of the problem, and reset the BTS.
FAULT NAME
Inter eNB communication failure
FAULT ID
6284: EFaultId_InterEnbCommunicationFailureAl
MEANING
The application has detected a problem with inter-eNB link communication (SRIO, RP3-01, Ethernet, and so on). Features that depend on the inter-eNB communication,
INSTRUCTIONS
In cases wherein not enough link throughput has been detected, check the SFP module link speed capabilities and replace it if necessary. In other cases, no manual
FAULT NAME
Inter eNB SW inconsistency in between cluster members
FAULT ID
6283: EFaultId_InterEnbSwInconsistencyAl
MEANING
An SW incompatibility has been detected between cluster members, which prevents the inter-eNB CA feature from being enabled.
INSTRUCTIONS
Upgrade or downgrade SW so that the same version is in all eNBs that have the "Inter eNB Carrier Aggregation" feature.
12/21/2019 Alarms
FAULT NAME
Inter eNB synchronization loss
FAULT ID
6287: EFaultId_InterEnbSyncLossAl
MEANING
eNB is informed about sync loss of neighbor eNB in same cluster and as a consequence needs to deactivate Carrier Aggregation feature.
INSTRUCTIONS
Read partner eNB ID from diagnostic information and check alarms and synchronization status on partner eNB.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Inter-Site CA incorrect cluster configuration
FAULT ID
4289: EFaultId_InterSiteCaIncorrectClusterConfigurationAl
MEANING
An incorrect configuration of inter-site Carrier Aggregation cluster has been detected between an eNB and other eNBs related by inter-site Carrier Aggregation rel
INSTRUCTIONS
Change the configuration of all eNBs related by inter-site Carrier Aggregation relations so that every pair of related eNBs has the same value of LNBTS caClusterI
FAULT NAME
Inter-Site CA link establishment failure
FAULT ID
4290: EFaultId_InterSiteCaLinkEstablishmentFailureAl
MEANING
A dedicated link between an eNB and other eNBs related by inter-site Carrier Aggregation relation cannot be established, which prevents the inter-site Carrier Agg
INSTRUCTIONS
1. Check if the inter-site Carrier Aggregation feature is enabled on the partner eNB.
2. Check if network communication between specific dedicated ports on the eNB, and its partner eNB used for inter-site Carrier Aggregation proprietary interface m
3. Check if there are not other critical or major alarms on the eNB and its partner eNB.
4. Restart the inter-site Carrier Aggregation feature on the eNB and its partner eNB.
5. Reset the eNB and its partner eNB.
FAULT NAME
Inter-Site CA SW interface incompatibility
FAULT ID
4288: EFaultId_InterSiteCaInterfaceIncompatibilityAl
MEANING
An SW interface incompatibility has been detected between an eNB and other eNBs related by inter-site Carrier Aggregation relation, which prevents the inter-site
INSTRUCTIONS
Upgrade or downgrade SW so that the same version is on the eNBs related by inter-site Carrier Aggregation relations.
FAULT NAME
Inter-Site CA X2 link unavailability
FAULT ID
4291: EFaultId_InterSiteCaX2UnavailabilityAl
MEANING
There is no available X2 link between an eNB and other eNBs related by inter-site Carrier Aggregation relation, which prevents the inter-site Carrier Aggregation
INSTRUCTIONS
Provide X2 link connections between eNBs related by inter-site Carrier Aggregation relations.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
1. Reset the BTS.
FAULT NAME
MBMS subframe pattern share exceeds available share
FAULT ID
6852: EFaultId_MbmsSubframePatternExceededAl
12/21/2019 Alarms
MEANING
The deployed MBMS subframe pattern share is less than the required MBMS subframe pattern share, which is configured with the MBSFN parameter subfrPShareRequired.
INSTRUCTIONS
Perform the following steps until the alarm disappears:
1. Edit the delta plan file and set the MBMS subframe pattern share (subfrPShareRequired) to a value equal to or less than subfrPShareDeployed or modify other par
2. Push the delta plan file to the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi BTS FDD/TDD:
FAULT NAME
MS 1PPS control interface not available
FAULT ID
4207: EFaultId_Ms1PpsControlInterfaceNotAvailAl
MEANING
The reference clock monitoring on the Slave Flexi Zone Micro BTS or Flexi Zone Access Point board has detected a loss of Master or Slave 1PPS control link, convey
INSTRUCTIONS
1. Perform a (remote) Flexi Zone Micro BTS or Flexi Zone Access Point site reset.
2. Perform a power reset for the entire Flexi Zone Micro BTS or Flexi Zone Access Point.
FAULT NAME
MS 1PPS reference missing
FAULT ID
4206: EFaultId_Ms1PpsReferenceMissingAl
MEANING
The reference clock monitoring on the Slave Flexi Zone Micro BTS or Flexi Zone Access Point board has detected a loss of Master or Slave 1PPS reference clock sign
INSTRUCTIONS
1. Perform a (remote) Flexi Zone Micro BTS or Flexi Zone Access Point site reset.
2. Perform a power reset for the entire Flexi Zone Micro BTS or Flexi Zone Access Point.
3. There might be an HW fault in the 1PPS connection between the Master and Slave boards. Replace the Flexi Zone Micro BTS or Flexi Zone Access Point.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
No MME capacity assigned by Core Network
FAULT ID
6264: EFaultId_S1ZeroCapPlmns
MEANING
The BTS has encountered a few possibly misconfigured PLMNs, which cannot be used by the BTS for accepting calls from new UEs, which select those PLMNs.
The PLMNs that are considered misconfigured by the BTS are:
- currently configured at the BTS for one or more cells
- served by one or more MMEs and therefore currently broadcasted by the cells of the BTS. However, none of these PLMNs have serving MMEs with relative capacity gr
All previously registered UEs in these PLMNs remain unaffected.
INSTRUCTIONS
Check and ensure that the PLMNs that have been listed with this BTS fault, and that have been configured at the BTS for one or more cells, have at least one MME s
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
NTP Frequency Synchronization Server Not Reachable: $IP
FAULT ID
6821: EFaultID_NtPSyncServerNotReachableAl
MEANING
This fault indicates that the BTS cannot contact one or more Network Time Protocol (NTP) servers configured by the ntpSyncServers parameter, where $IP is the IP a
INSTRUCTIONS
1. Check the Ethernet interface functionality used by the Network Time Protocol. Check if other faults related to the Ethernet interface exist.
2. Check the Network Time Protocol configuration; ensure that the NTP Server IP address is configured properly.
3. Check the Network Time Protocol server functionality.
4. Check that the IP connection between the Network Time Protocol server and Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna is working.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Optical cable inter-BTS or inter FSP cards too long for CRAN
FAULT ID
4311: EFaultId_ OpticalCableInterFsmTooLongForCranAl
MEANING
The fault may be reported in FSMx only due to two root causes:
- The optical cable used to connect BTSs working in the same Centralized
Radio Access Network (CRAN) cluster exceeds the maximum supported length for CRAN.
- The optical cable used to connect the BTSs working in the same CRAN cluster is
not connected to the third port on the FBBC cards.
INSTRUCTIONS
1. Check if the optical cable is connected to the third port on the FBBC card in each BTS. If not, connect the cable to the third port.
2. If the cable is connected to the third port on the FBBC cards and the alarm with the fault is still reported, replace the cable with a shorter one (the maximum
FAULT NAME
Overload collision in transmitter
FAULT ID
2061: EFaultId_MuksuOverloadCollisionAl
MEANING
The transmitter has detected more data coming from a summing than the current link rate can support.
INSTRUCTIONS
2. Check the baseband bus configuration related to the RP3 link speeds.
FAULT NAME
Overload detected: max number of neighbor relation objects reached
FAULT ID
6285: EFaultId_MaxNumberAnrMoiReachedAl
MEANING
This fault is reported when the BTS detects that the number of neighbor-related objects (which represents the neighboring BTS, and its cells with the relationship
INSTRUCTIONS
Removing neighbor-related objects below the value of the parameter "maxNumAnrMoiAllowed" brings the BTS to full operational state.
FAULT NAME
POST test failed
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Radio slave has taken temporary radio master role
FAULT ID
4220: EFaultId_TemporaryRadioMasterAl
MEANING
The radio master is either missing at start-up or is lost at run-time.
The radio slave waits for a user-defined amount of time for the radio master
to become available again before taking a temporary radio master role.
An alarm due to the fault is reported when the radio master is not available after the user-defined amount of time, and the slave takes a temporary radio master r
INSTRUCTIONS
Check that the radio master is powered on, and that the RP3-01 cables of the radio master are properly attached. When the radio master is available, the radio sla
FAULT NAME
Reference clock missing in startup
FAULT ID
4153: EFaultId_PpsRefClcMissInStrtAl
MEANING
Phase synchronization has been commissioned at the btsSyncMode, but phase reference
clock is unavailable during a waiting period within the start-up procedure.
INSTRUCTIONS
Depending on the installed and commissioned synchronization sources, see the
commissioned synchronization options below and perform the steps in the listed
order until the BTS fault indication disappears:
eNB is Sync hub slave and RF sharing is enabled:
1. Check if sync master provides sync signal.
2. Check the connection between sync master and sync slave.
3. Check sync settings at sync slave.
eNB is a part of CRAN cluster:
Perform all the steps from above.
TRS reference (ToP as source):
1. Check that the signal is being received from the ToP Master.
BTS is Sync hub slave and RF sharing is enabled:
1. Remove the root cause that leads to the sync hub slave being not synchronized .
2) If there is a need to change settings, either perform remote re-commissioning through NetAct, or un-commission the BTS prior to re-commissioning using the Site
FAULT NAME
Resource pool configuration failed
FAULT ID
6292: EFaultId_ResourcePoolConfigurationFailedAl
MEANING
The pool configuration of the resource DSPs has failed between C-Plane and U-plane.
INSTRUCTIONS
FAULT NAME
RF Unit temperature too high
FAULT ID
4185: EFaultId_RfTempTooHighAl
MEANING
The validated sensor temperature on the PA is higher than the predefined HW temperature.
INSTRUCTIONS
3. If those do not help, replace the BTS.
FAULT NAME
RIBS Synchronization Not Available
FAULT ID
4319: EFaultId_RibsSourceEnodebNotAvailable
MEANING
This fault indicates that the Radio Interface Based Synchronization (RIBS) is not available, and is operating in synchronization holdover mode.
INSTRUCTIONS
Verify that a Stratum-0 TD-LTE BTS is within the reception range of the affected target BTS.
FAULT NAME
SRIO domain ID collision
FAULT ID
4263: EFaultId_SrioDomainIdCollisionAl
MEANING
The inter-eNB SRIO link cannot be established because the domain ID is not unique.
INSTRUCTIONS
For features related to Inter-eNB Carrier Aggregation, the value of the LNBTS.caClusterMemberId parameter must be unique for each eNB within all eNBs that belong
FAULT NAME
12/21/2019 Alarms
SRIO link outage
FAULT ID
4262: EFaultId_SrioLinkOutageAl
MEANING
SRIO link failure has been detected by the NE.
INSTRUCTIONS
Check the cable between the SRIO ports in the eNBs.
Automatic recovery process starts as soon as the fault has been detected.
FAULT NAME
SRIO topology failure
FAULT ID
6290: EFaultId_SrioTopologyFailureAl
MEANING
Inter eNB SRIO link couldn't be established due to DomainIds not being unique or other errors in cluster topology.
INSTRUCTIONS
If collission is detected:
For 'Inter eNB Carrier Aggregation'-related features, the LNBTS.caClusterMemberId parameter value must be unique for each eNB that belongs to the same cluster (LN
In other cases:
For 'Inter eNB Carrier Aggregation'-related features, the LNBTS.caClusterId and LNBTS.clusterNumEnb values must be identical for each eNB that belong to the same
FAULT NAME
Summing not enabled for message type
FAULT ID
2059: EFaultId_MuksuSummingNotEnabledAl
MEANING
Summing checks the headers of the messages to be summed. If the header is not an allowed type, summing is not performed and an empty message is sent instead.
INSTRUCTIONS
2. Check the logs for line code violation (LCV) errors related to optical links.
3. Verify Small Form-factor Pluggable (SFP) transceiver and fiber conditions.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
SW fallback
FAULT ID
MEANING
4082:
If BTS O>M has detected that the BTS can start with the previously-active SW version - BTS O>M processed consistent fallback and
Otherwise:
4083:
Otherwise:
4085:
Otherwise:
INSTRUCTIONS
12/21/2019 Alarms
Flexi Zone:
None
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
TD-SCDMA major alarm
FAULT ID
4178: EFaultId_TdscdmaMajorAl
MEANING
The Ir router has reported a major problem with TD-SCDMA. The TD-LTE performance is affected, and cells are disabled.
INSTRUCTIONS
FAULT NAME
Temperature alarm
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
toor4nsn Password Update failure
FAULT ID
4312: EFaultId_PasswordUpdateFailureAl
MEANING
The affected FZAP(s) failed to accept the latest service (toor4nsn) account password update.
INSTRUCTIONS
Check all the alarms posted by the Flexi Zone Access Point. The operator can initiate a password update request again, which might be successfully accepted by FZA
FAULT NAME
ToP clock tuning failure
FAULT ID
4186: EFaultId_TopClkTuningFailureAl
MEANING
The Timing over Packet (ToP) frequency adjustment is nearing its tuning limit. The DFS frequency offset is within 5% of its minimum or maximum supported range.
INSTRUCTIONS
1. Check the other alarms of the BTS and IEEE1588-2008 Master Clock, and act accordingly.
2. If the 1818: EFaultId_Ov_OscAl fault is also active, it is likely that the center frequency of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone
3. Reset the site and run fast tuning again.
4. If the condition persists, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Transmission parameters missing
FAULT ID
1825: EFaultId_PublicIPmissingAl
MEANING
A request to retrieve the public IP address information of the FCT (HW rel.3) from the FTM has failed, FCT (HW rel.4).
INSTRUCTIONS
Commission the BTS site with the correct IP addresses.
FAULT NAME
Transmission rule collision in Muksu
FAULT ID
2060: EFaultId_MuksuTransmissionRuleCollisionAI
MEANING
The transmitter has detected an RP3 message from a summing coincident with a transmission rule.
INSTRUCTIONS
FAULT NAME
FAULT ID
4208: EFaultId_RromIpConfigAl
MEANING
The RROM TRS IP configuring or reconfiguring has failed.
INSTRUCTIONS
Check the transport-related configuration (C-Plane address, U-Plane address, and Transport network ID). If the fault was raised at startup, correct the configurat
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
1. Reset the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unknown HW resource
FAULT ID
MEANING
INSTRUCTIONS
<
Table 12253: BASE_STATION_TRANSMISSION_ALARM
Name: BASE_STATION_TRANSMISSION_ALARM (11520) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BASE STATION TRANSMISSION ALARM FL16A
Package: racfl.BASE_STATION_TRANSMISSION_ALARM Implicitly cleared: true
Description: BASE STATION TRANSMISSION ALARM A transmission fault (or faults) has occured in the BTS. This alarm is an encapsulation alarm that is used to transfer the Flexi Transport Submodule (FTM) alarm data
over the BTS O&M connection through iOMS to NetAct. In NetAct this alarm is shown in opened format. This means that the alarm number, alarm text, and supplementary information are shown in the original FTM format.
Check the reason for the fault from the supplementary information fields and supplementary text field of the alarm. The effect of the fault on the functioning of the network element depends on the fault description. For more
information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
FAULT NAME
$Protocol Timing source lost [on unit $U] [, interface $IF]
FAULT ID
61059: FTM_TIMING_SOURCE_LOS
MEANING
One of the synchronization sources in the configured priority list is unavailable.
This can be the primary or the secondary clock source.
In the alarm: Protocol can be PDH, Timing over Packet (ToP), and Synchronuous ethernet.
Unit Number is optional:
- For PDH and Synchronous Ethernet, Unit number is 0 or 1.
- It is not present for Timing Over Packet(TOP).
The interface value is optional:
- For PDH, the value range depends on the hardware unit type: 1-16.
- For Synchonuous Ethernet, the value range is 1-3.
- It is not present for Timing over Packet.
INSTRUCTIONS
Use BTS Site Manager to check which interfaces have been configured as
synchronization sources. For all interfaces, do as follows:
1. Check that the cables are connected to the correct connectors.
2. Check whether the interface at the far end is switched on.
3. Check whether there are active alarms at the far end. If there are,
follow the instructions on handling those alarms.
4. Connect a loop cable and check whether the alarm disappears to verify that the hardware of the interface unit works correctly.
Monitor the quality of the received clock.
FAULT NAME
AIS on unit $U, interface $IF
FAULT ID
61151: FTM_AIS
MEANING
Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its received
All other transmission alarms related to this signal are suppressed.
Probable cause: There is a transmission problem somewhere in the intermediate network, and AIS is sent instead of user traffic.
INSTRUCTIONS
Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.
FAULT NAME
Automatic BTS Operator Certificate retrieval unsuccessful
FAULT ID
61510: NO_CERTIFICATE
MEANING
A requested certificate could not be retrieved from the certificate authority (CA).
A requested certificate could not be renewed from the certificate authority (CA).
A requested certificate could not be retrieved as the number of certificates received from repository server (RA) or certificate authority (CA) are more than expe
A requested certificate could not be stored in the remaining storage available on the BTS. Operator cleanup (e.g. via site manager or NetAct) of old, unused trust
12/21/2019 Alarms
INSTRUCTIONS
Provide the certificate.
FAULT NAME
Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
FAULT ID
61607: AUTO NEGO MIS MATCH
MEANING
This alarm indicates that there is a mismatch between the BTS configuration and the auto-negotiation result.
INSTRUCTIONS
Try with local management or site support equipment.
Confirm that the Ethernet Synchronization master/slave settings are correct on the Flexi Zone Micro BTS or Flexi Zone Access Point and backhaul equipment.
Note: The Flexi Zone Micro BTS and Flexi Zone Access Point only support slave mode.
FAULT NAME
BFD $session down, egress, $sourceIP to $destinationIP
FAULT ID
61606: BFD DOWN Egress
MEANING
The alarm is raised if the alarm is enabled, the BFD state of the session is not "AdminDown", and the BFD packet from the far end contains the diagnostic code ="
INSTRUCTIONS
Check the BFD configuration at the local end.
FAULT NAME
BFD $session down, ingress, $sourceIP to $destinationIP
FAULT ID
61605: BFD DOWN Ingress
MEANING
The alarm is raised if the alarm is enabled, the BFD state for the session is not "AdminDown", and nevertheless, no BFD packet is received at the local end during
INSTRUCTIONS
1. Check the network between both BFD peers for physical link failures or misconfigurations.
2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.
FAULT NAME
BFD group $bfdGrpId down
FAULT ID
61022: BFD DOWN
MEANING
The alarm is raised if the BFD service is not available on the BTS for all BFD sessions belonging to that BFD group.
INSTRUCTIONS
1. Check if the far end has BFD switched on.
2. Check the cabling and network connections of the far end.
FAULT NAME
Bluetooth enabled
FAULT ID
61520: BLUETOOTH_ENABLED
MEANING
If the actBluetoothTransAlarm parameter allows, this fault is raised to indicate that the bluetooth has been enabled because of any of the following:
- The bluetooth config mode set to explicitly enabled
- The bluetooth config mode AutoFallback logic, which automatically enables the bluetooth upon loss of connection to the iOMS or NetAct
INSTRUCTIONS
1. Determine if the bluetooth should be enabled.
2. If this action is unexpected, disable the bluetooth.
FAULT NAME
Bluetooth network connected
FAULT ID
61522: BLUETOOTH_CONNECTED
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point has detected a bluetooth network connection.
INSTRUCTIONS
FAULT NAME
Bluetooth Paired
FAULT ID
61521: BLUETOOTH_PAIRED
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point has detected a successful pairing.
INSTRUCTIONS
FAULT NAME
Bluetooth repeated authentication failure
FAULT ID
61523: BLUETOOTH_AUTH_FAIL
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point has detected repeated bluetooth authentication failures. This could signal that a passkey or pin guessing atta
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
BTS and/or peer trust anchor expired or due to expire
FAULT ID
61618: TRUST_ANCHOR_EXPIRING
MEANING
The network element stores trust anchors for its own trust chain and for peers. When its own or any trust anchors are about to expire or are expired, this alarm i
INSTRUCTIONS
Update the trust anchors.
FAULT NAME
BTS booted at $date due to $RCause
FAULT ID
61006: FTM_RESET
MEANING
The transport part of the BTS has been reset at the date and time given in the notification.
1. FSMr2 supports the following cause for the reset:
"trs power-on reset": Cold start
"trs watchdog reset": System overload
"trs startup failure": Failure during startup
"trs software failure": Software failure
"trs management reset": Reset triggered by management interface
"trs fallback": Fallback executed
FSMr3/AirScale supports the following cause for the reset:
"trs power-on reset": Cold start
"trs watchdog reset": System overload
"trs software failure": Software failure
"trs management reset": Reset triggered by management interface
"trs spurious reset": Reset reason detection failed
2. The "$date" format is the local time stamp (GMT+/-xx:xx). For example: 2014-04-12 00:51:26 GMT+0530
INSTRUCTIONS
No actions are required.
FAULT NAME
BTS Local OAM user account $A has been locked
FAULT ID
61642: FTM_SECURITY_USER_ACCOUNT
MEANING
A specific BTS local operator account has been locked.
The number of failed login attempts for a BTS local operator account has exceeded the threshold, and the account has been locked on the BTS. No further logins are
INSTRUCTIONS
Check the validity of the username and password of the account.
FAULT NAME
BTS reset required
FAULT ID
61010: FTM_BTS_RESET_REQUIRED
MEANING
A change to the BTS IP settings has been received from the BTS Site Manager. The BTS should be restarted to activate the change.
INSTRUCTIONS
Reset the BTS when all the required BTS IP settings have been set.
FAULT NAME
CCM fault level $ prio $p cause $c
FAULT ID
61410: Ethernet OAM CCM fault
MEANING
The alarm is triggered whenever a service OAM error related to the transmission of Continuity Check Messages (CCM) persists on a given Ethernet interface as soon
The following alarms are defined:
1. MDL_MISMATCH, priority 5 (highest priority): A CCM is received with an MDL that is lower than the highest configured one in the BTS, and does not match any of
Example: CCM fault level - prio 5 cause MDL_MISMATCH
Note: For MDL_MISMATCH cases, it might not be possible to display the local MDL where the fault was detected.
2. MAID_MISMATCH priority 5: A CCM is received with an MDL that is configured in the BTS, but with an MAID that does not match any MA configured in the BTS on thi
Example: CCM fault level 5 prio 5 cause MAID_MISMATCH
3. MAID_MISMATCH priority 5: A CCM is received with matching MDL and MAID, but the VLAN membership of the received frame does not match the VLAN configuration of
Example: CCM fault level 5 prio 5 cause MAID_MISMATCH
4. ERR_CCM, priority 4: A CCM is received with known MDL and MAID, but the MEPID is not configured in the Remote MEP list of the MA.
Example: CCM fault level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED
5. ERR_CCM, priority 4: A CCM is received with known MDL, MAID, and MEPID, but the CCM interval coded in the received CCM does not match the interval configured i
Ex: CCM fault level 5 prio 4 cause WRONG_CCM_INTERVAL
6. REMOTE_CCM, priority 3: A CCM was not received for 3.5 intervals from at least one remote MEP in the MA.
Ex: CCM fault level 5 prio 3 cause REMOTE_CCM_DEFECT
7. RDI_CCM, priority 1 (lowest priority): An RDI flag is detected in the CCM frames from one remote peer.
Example: CCM fault level 5 prio 1 cause REMOTE_DEFECT_INDICATION
The alarm displays the following information:
- Alarm Name
- Alarm Priority
- Alarm cause: if different sources produce the same alarm
- MD level at which the alarm was detected
INSTRUCTIONS
1. Check the cabling.
2. Check the CCM configuration at the remote peer.
12/21/2019 Alarms
FAULT NAME
Configuration change rejected by BTS
FAULT ID
61638: NEW_CONFIG_REJECTED
MEANING
This alarm is triggered once the new configuration file is rejected and the
M-Plane connection is established with fallback configuration as a result
of M-plane recovery action. It will be visible until next site reset.
INSTRUCTIONS
None
FAULT NAME
CRL Update Failure
FAULT ID
61074: CRL Update failure
MEANING
This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL). Please refer to PDDB parameter "CERTH::CRLInfo: CRLUpdateFailureReason" for f
INSTRUCTIONS
Execute general configuration checks:
- Configuration of CMP server IP address and port, and DNS server IP address.
- Configuration of routing entries towards remote peers.
- Configuration of IPSec policies towards remote peers.
Check remote peers and intermediate network elements interconnections.
Check the LDAP connection towards the Certificate Revocation List server.
Check DNS names.
Check the size of the file at the Certificate Revocation List server.
FAULT NAME
Dead Peer Detected
FAULT ID
61030: FTM_DPD
MEANING
A dead peer has been detected in one of the IPsec associations of the FTM.
There is no response to the requests sent to the peer during the IKE SA setup, the IPsec SA setup, or during DPD.
Note: When the IPSec backup tunnel feature is enabled, this alarm should not be raised because of failures when trying to set up primary IPSec tunnel in "Secondar
Possible reasons:
- a cable is cut or there is no cable connected to the interface
- the signal is excessively attenuated
- the port at the connected far end node is switched off
INSTRUCTIONS
2. Check that the interface at the far-end interface is switched on.
3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.
FAULT NAME
Dup Addr on {duplicateIpv6Address} {VID: id}
FAULT ID
61632: IPV6_DUPLICATE_ADDRESS_DETECTED
MEANING
During the IP address configuration of the BTS, it tests the directly-attached network whether other, already configured BTSs, on the network already uses the sam
INSTRUCTIONS
1.Check for duplicate IPv6 addresses configured in the BTS.
2.Change or delete the identified duplicate IPv6 addresses.
FAULT NAME
EBER on unit $U, interface $IF
FAULT ID
61104: FTM_EBER
MEANING
Excessive bit error rate: The measured bit error rate exceeds the threshold value of BER-3 (10E-3).
Probable causes:
- the signal level is too low (optical connectors or cables are dirty, electrical connectors or cables are corroded)
- the specified maximum length of the cable is exceeded
- the connector is not properly connected to the unit
- the receiver or the far-end transmitter has failed
INSTRUCTIONS
1. Clean the cables and connectors.
2. Check that the connectors are properly connected to the unit.
3. Check that the cable connected to the interface in question is not damaged and is within the specifications.
4. Follow the signal in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life). If they are, follow the instructio
FAULT NAME
ETH AIS fault interface $IF level $l mac $x
FAULT ID
61411: Ethernet OAM ETH_AIS_fault
MEANING
When an MEP receives a valid ETH-AIS frame and AIS is enabled, it shall trigger an AIS alarm containing the following information:
- receiving interface
- MD level
- Source MAC address
Note:For FSMr3/AirScale unit types, interface is provided as: "module type name" EIF "interface number".
For Flexi Zone Micro BTS, interface is provided as: EIF "interface number".
INSTRUCTIONS
1. Check cabling.
2. Check the configuration at the remote peer.
12/21/2019 Alarms
FAULT NAME
FTM Toggling <Fault name>
FAULT ID
61619: FTM_FAULT_TOGGLING
MEANING
An FTM fault, for which the fault name appears in the Fault name field, is toggling in the FTM. Toggling fault condition is informed to the user with this new FTM
INSTRUCTIONS
1. Check the fault name of the toggling FTM fault from the Fault name of
this fault.
2. Follow the instructions of the toggling FTM fault to clear the problem.
Note: Detailed information about the toggling frequency can be found in
alarm history file, which can be downloaded using the BTS Site Manager. The log file is available with Snapshot.
FAULT NAME
IPsec emergency bypass active
FAULT ID
61639: IPSEC_EMERGENCY_BYPASS_ACTIVE
MEANING
The BTS has entered the IPsec emergency bypass active state, where configured IPsec policies are ignored and the entire traffic is sent unprotected.
INSTRUCTIONS
Start IPsec emergency bypass by making the security gateway not reachable either
by plugging out the cable or configuring wrong security gateway address.
FAULT NAME
IPSec expert mode activated
FAULT ID
61647: IPSEC_EXPERT_MODE
MEANING
BTS is in IPSec Expert Mode. This mode allows online tuning of IPSec related parameters for troubleshooting or workaround implementation via BTS Site Manager. It
INSTRUCTIONS
None.
FAULT NAME
IPSec tunnel switchover
FAULT ID
61643: IPsec_tunnel_switchover
MEANING
This alarm will be triggered when at least one primary IPSec tunnel fails, and BTS has switched over to a secondary IPSec tunnel.
As a result of failure in at least one primary IPSec tunnel, BTS has automatically switched over to a secondary IPSec tunnel terminating on secondary security gat
INSTRUCTIONS
The operator can check the current remote tunnel endpoint parameter (ipSecBkupTunCurrRemoteEndpoint) on NetAct or BTS SM to verify the remote endpoint of a tunnel
FAULT NAME
IP Traffic Capturing Ongoing [port $port,] [mac $m]
FAULT ID
61641: IP_TRAFFIC_CAPTURE_ONGOING
MEANING
The base station is currently capturing an IP traffic towards a local port or into a file on the base station.
If the traffic capturing is happening towards a local port, a port and destination MAC address must be provided.
Port values can be LMP or < HW MODULE NAME >-<PORT ID>.
(For E.g: LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1)
INSTRUCTIONS
An IP Traffic Capturing session is ongoing and a base station traffic is captured to a local Ethernet interface or into a file on the base station.
FAULT NAME
Link OAM critical link event $E on unit $U, interface $F
FAULT ID
61077: Link OAM critical link event alarm
MEANING
A Link OAM PDU containing a critical link event flag was received on the Ethernet interface. The alarm is raised with the first detection of the flag.
The following critical link events are possible:
- Critical Event: either an Errored Symbol Period Event, an Errored Frame Event, an Errored Frame Period Event, or an Errored Frame Seconds Summary Event was dete
- Dying Gasp: either the local or the remote peer has a fatal error and is about to restart.
- Link Fault: the local peer has detected a physical link fault in receiving direction, for example, a LOS.
Note:
In case a received OAMPDU has more than one critical event flag set, the following shall be reported in the alarm:
Link Fault bit set |Dying Gasp bit set|Critical Event bit set| Reported
x x x Link Fault
x x Link Fault
x x Link Fault
x x Dying Gasp
Always the latest received critical link event shall be reported.
INSTRUCTIONS
1. Inspect details of the type of the critical event through online configuration management.
2. Check the Link OAM state information of the interface.
3. Check the cabling and network connections to the far end.
4. Check the Ethernet interface configuration at the local and remote sides.
5. Insert a Link OAM loopback.
FAULT NAME
Link OAM link lost on unit $U, interface $F
FAULT ID
61076: Link OAM link lost alarm
MEANING
On an interface for which the Link OAM functionality was switched on, no Link OAM PDUs were received during the period specified in configuration parameter "linkL
INSTRUCTIONS
12/21/2019 Alarms
1. Check the cabling and network connections to the far end.
2. Check the Link OAM event information and the Link OAM state information.
3. Check the Ethernet interface configuration at the local and remote sides.
4. Insert a Link OAM loopback.
FAULT NAME
Link OAM loopback inserted on unit $U, interface $F by $P peer
FAULT ID
61075: Link OAM loopback alarm
MEANING
A loopback is requested for an Ethernet interface either locally at the BTS, or the Link OAM client of the BTS is set into loopback mode by the remote Link OAM pe
INSTRUCTIONS
None
FAULT NAME
LMP Carrier State Detected
FAULT ID
61648: LMP_CARRIER_DETECTED
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point detects, using carrier state, that someone is locally connected to the small cell using LMP port.
INSTRUCTIONS
1. Determine if this event is expected: whether a qualified personnel is utilizing LMP ethernet port cable connection for diagnostic purposes.
2. Otherwise, it shall be treated as a security warning.
FAULT NAME
LOF on unit $U, interface $IF
FAULT ID
61028: FTM_LOF
MEANING
Loss of frame: It is not possible to carry traffic on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppres
Probable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface.
Probable cause for T1 interfaces: The interface at the far end is not configured to be a T1 interface.
INSTRUCTIONS
E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 interface. If this is not the case, reconfigure the int
JT1 interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. If this is not the case, reconfigure the interfac
FAULT NAME
LOMF on slot $U, interface $IF
FAULT ID
61150: FTM_LOMF
MEANING
Loss of multi-frame: The interface referenced in the alarm text has lost the multi-frame alignment.
Probable cause: The interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the configuration of the far-en
INSTRUCTIONS
Check that the configured interface type matches the configured interface type of the far-end interface. If this is the case, the problem is somewhere in the tran
FAULT NAME
LOS on unit $U, [Ethernet] interface $IF
FAULT ID
61029: FTM_LOS
MEANING
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:
No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed.
Probable causes for Ethernet interfaces:
- a cable is cut, or there is no cable connected to the interface
- the electrical signal is excessively reduced
- the port at the connected far-end node is switched off
No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed.
Probable causes for Ethernet interfaces:
- a cable is cut, or there is no cable connected to the interface
- the electrical signal is excessively reduced
- the port at the connected far-end node is switched off
The fault is generated only when the interface is not configured as LMP (that is, generated only when the interface is configured as the primary BH port, or when
INSTRUCTIONS
2. Check that the interface at the far-end interface is switched on.
3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.
FAULT NAME
Missing or non-compliant SFP module on unit $U, interface $I
FAULT ID
61050: FTM_SFP
MEANING
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:
The Small Form-Factor Pluggable (SFP) module detected in the interface connector does not comply with security requirements. It does not have a class 1 laser.
The Small Form-Factor Pluggable (SFP) module is not supported, not present, or could not be recognized.
The SFP module detected in the interface connector does not comply with the SFP module types supported by the BTS element. The SFP module type is checked to ensur
The SFP module was expected by the SW, but found missing.
Probable causes:
- No SFP module is inserted at the SFP-based Ethernet interface.
- The interface contacts of the SFP module are corroded or dirty, preventing either read access to the SFP module at the time of reading compliance data from the
- The SFP module type is not supported.
12/21/2019 Alarms
The fault is generated only when the interface is not configured as LMP (that is, generated only when the interface is configured as the primary BH port or when d
INSTRUCTIONS
Insert a Small Form-Factor Pluggable (SFP) module with the correct laser type (class 1) to the Gigabit Ethernet interface of the unit.
1. Plug-out and plug-in the SFP module.
2. Check for SFP validity (could be wrong type).
3. Insert a compliant SFP module.
FAULT NAME
NTP Server $IP unavailable
FAULT ID
61613: NTP_SERVER_UNREACHABLE
MEANING
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:
A BTS reports this alarm for each instance of the configured NTP server if that
particular NTP server is not accessible or cannot be used after waiting for
a threshold timeout defined by the INTP::ntpAlarmThreshold configuration parameter in PDDB.
The raised alarm displays the IP address of the NTP server that is not reachable
in the additional information field "alarmNotif::argumentInfo".
Note : For each NTP server instance, timers are started separately and a separate
alarm is raised. This threshold time is not used to clear the alarm.
Flexi Zone:
Flexi Zone Access Point reports this alarm for each instance of the configured
NTP server if that particular NTP server is not accessible or cannot be used
after waiting for a threshold time-out defined by the configuration parameter
INTP::ntpAlarmThreshold in PDDB.
The raised alarm displays the IP address of the NTP server that is not reachable
in the additional information field "alarmNotif::argumentInfo".
Note : For each NTS server instance, timers are started separately and a separate
alarm is raised. This threshold time is not used to clear the alarm.
INSTRUCTIONS
1. Check the connectivity to the NTP server.
2. Check the NTP server configuration at the BTS.
3. Check the configured threshold value for the NTP server.
FAULT NAME
RDI on unit $U, interface $IF
FAULT ID
61152: FTM_RDI
MEANING
Remote defect indication: It is sent by the intermediate or the far-end equipment because it detects a serious fault in the received signal.
Probable cause: The far end has a LOS, LOF, or AIS alarm on its receiving interface.
INSTRUCTIONS
1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.
2. Connect a loop cable and check that no alarms appear for this interface to check the transmit hardware.
FAULT NAME
SFP HW Failure
FAULT ID
61079: SFP HW Failure
MEANING
A malfunctioning of the SFP transceiver was detected.
The SFP has reported a transmission fault condition and has disabled the laser transmitter.
INSTRUCTIONS
Replace the faulty SFP. Note that only the SFP might be faulty, not necessarily the entire hardware unit.
FAULT NAME
SFP HW Warning/Alarm on unit $U, interface $IF, cause $FC
FAULT ID
61525: FTM_SFP_WARNING
MEANING
There is an issue with the SFP module used for backhaul. The fault is based on the SFP alarm and warning flags associated with temperature, supply voltage, TX bia
INSTRUCTIONS
Check the datasheet of the specific SFP used, whether the SFP warning flags are latching or non-latching. In case they are latching, reset the FZM or FZAP to dete
1. Check whether the alarm is caused by exceeded temperature, internal supply voltage, or TX BIAS/TX output power.
2. If exceeded temperature causes the alarm, investigate if the current operating conditions are outside the high or low temperature specifications for FZM or FZA
3. If the internal supply voltage causes the alarm, check if the FZM or FZAP power input voltage is within the supported operating voltage range. If the FZM or FZ
4. If the TX BIAS/TX output power causes the alarm, replace the SFP module.
FAULT NAME
SSH enabled
FAULT ID
61524: SSH_ENABLED
MEANING
The Flexi Zone Micro BTS or Flexi Zone Access Point detects that the SSH access to the site is enabled.
Note: The SSH access to the site is disabled by default. To mitigate the risk in field scenarios, SSH should only be enabled for limited periods time on an as-nee
INSTRUCTIONS
1. Determine if this event is expected.
Note: The SSH access to the site is disabled by the default. SHH should only be enabled for limited periods time on an as-needed basis.
FAULT NAME
SyncE Quality Level Degraded on unit $UID, interface $IF
FAULT ID
61624: SSM_POORQUALITY
MEANING
This alarm is raised when the received SSM indicates lower clock quality (for example, "do not use" or "EEC") than required.
12/21/2019 Alarms
Note: The interface numbering shall be similar to ETHLK.

E.g: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1,interface 4.
INSTRUCTIONS
Flexi Zone Micro FDD, AirScale BTS FDD/TDD, Flexi Zone Micro TDD, Flexi Zone:
1. Confirm that SyncE is desired as a synchronization source.
2. Confirm that eNB configuration settings for ssmEnabled are correct.
3. Troubleshoot with Backhaul provider on the reason SSM errors.
FAULT NAME
SyncE SSM Timed Out on unit $UID, interface $IF
FAULT ID
61623: SSM_TIMEOUT
MEANING
This alarm is raised if the incoming SSM is not received for a certain time period (configured through the parameter "ssmTimeout").
Note: The interface numbering is similar to ETHLK.
Example: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1, interface 4
INSTRUCTIONS
1. Confirm that SyncE is desired as a synchronization source.
2. Confirm that configuration settings for ssmEnabled are correct.
3. Troubleshoot with backhaul provider about the reason for SSM errors.
FAULT NAME
Synchronization lost
FAULT ID
61058: FTM_SYNC_LOSS
MEANING
Primary and secondary timing sources are lost. The LTE is utilizing the Global Navigation Satellite System (GNSS) source (if available) or in synchronization hold
The first and second synchronization sources from the configured priority list are unavailable. On failure, the LTE switches automatically to the next clock sourc
Probable cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example, LOS).
INSTRUCTIONS
Use the BTS Site Manager to check which interfaces have been configured as synchronization sources.
2. Check whether the interface at the far end is switched on.
3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms.
FAULT NAME
ToP master service $IP unusable
FAULT ID
61631: TOP_MASTER_UNUSABLE
MEANING
The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP:
- The eNB does not receive a reply from ToP Master within a certain time (5 sec) upon sending a sync request message.
- The eNB receives from ToP Master granted message rates (sync message rate, delay message rate), that do not match the requested rate by the eNB.
INSTRUCTIONS
1. Check the cable connectivity.
2. Check the TOP configuration.
FAULT NAME
Transport module missing: $unit
FAULT ID
61201: TRANSPORT_MODULE_MISSING
MEANING
A unit is missing. The slot has been configured to hold a unit, but the plug-in
unit is not physically present in the slot.
Probable causes:
- The unit has been configured but not detected.
- The unit is broken and therefore not detected.
- The unit has been configured but some other unit is detected.
NOTE: The unit variable should be replaced by appropriate HW names configured (unitTypeConfigured) during runtime reporting.
INSTRUCTIONS
Replacing a faulty hardware:
1. Plug in again the expected transport unit that is referenced in the alarm text.
2. In case there is a unit present in the slot, remove it from the slot
and plug it back in. If the unit is still not recognized and the alarm
remains, replace the faulty unit with a new one.
Decommissioning a previously commissioned hardware:
1. Recommission to remove the hardware unit referenced in the alarm text.
NOTE: Before recommissioning, the hardware unit must not be present in the slot.
FAULT NAME
TWAMP PLR Threshold Crossed
FAULT ID
61611: PLR_THRESHOLD_CROSSED
MEANING
The PLR threshold alarm shall be sent in case the configured value of PLR is exceeded.
INSTRUCTIONS
1. Check the backhaul usage and if other applications with the same or higher
PHB may compete against this TWAMP session about the capacity. An increase in
the priority of TWAMP session or of the backhaul capacity may clear the alarm.
2. Check if destination is unreachable by IP connectivity test. Send an ICMP
echo request (ping) to the UDP port of the TWAMP reflector at the destination
IP.If ICMP echo reply indicates that the destination is unreachable but you
have access to TWAMP reflector, you can check its status. If the status is disabled
or down try to activate it again and check if alarm disappears.
3. Check configured PLR threshold. Setting PLR to 0% should be avoided, because
every lost measurement packet will trigger the alarm and it cannot be cleared
again (PLR>=0).
12/21/2019 Alarms
FAULT NAME
TWAMP RTT Threshold Crossed
FAULT ID
61610: RTT_THRESHOLD_CROSSED
MEANING
The RTT threshold alarm is sent in case the average value of the RTT exceeds
the configured threshold.
INSTRUCTIONS
1. Check the backhaul usage and if other applications with the same or higher
PHB may compete against this TWAMP session about the capacity. An increase in
the priority of TWAMP session or of the backhaul capacity may clear the alarm.
2. Check the last measured RTT values of this TWAMP session and verify that
the configured RTT threshold value is not too close to average measured RTT
values, so that this alarm could be result of sporadic mis-measurement.
FAULT NAME
Unsupported HW device
FAULT ID
61634: UNSUPPORTED_HW_DEVICE
MEANING
The SW does not support the detected HW unit type.
Probable causes:
- The SW version of the system module is too old.
- The supported HW variant is not present in the system module.
INSTRUCTIONS
SW upgrading: Upgrade the FSM SW release to the latest version that includes the support for the new external transport device variant.
Unit variant replacement: Replace the unsupported device variant to another one that supports the currently running SW release.
FAULT NAME
Vendor BTS certificate is about to expire
FAULT ID
61616: VENDOR_CERTIFICATE_EXPIRING
MEANING
The BTS raises this alarm when the vendor BTS certificate is about to expire.
The period of advance notification is configurable, as well as the CA certificate expiry.
1 day ... 4999 days with default 90 days
Note: For Flexi Zone Controller, the period of advance notification is a non-configurable 90 days.
INSTRUCTIONS
Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Access Point, Flexi Zone Controller:
Check the vendor BTS certificate expiry date.
Replace the expired vendor BTS certificate if possible (for example, an older BTS like FSMr2).
Otherwise, contact Nokia to investigate the need for hardware replacement or return to resolve the possible end-of-life indication implied by the expired Nokia ve
For most BTS types (including at least FSMr3, Airscale, Flexi Zone Controller, FZAP, and Flexi Micro/Pico), a new vendor certificate can only be installed in the
FAULT NAME
Wi-Fi card invalid type
FAULT ID
61527: WIFI_CARD_INVALID_TYPE
MEANING
The internal Wi-Fi module type is invalid.
INSTRUCTIONS
1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported.
FAULT NAME
Wi-Fi card not present
FAULT ID
61526: WIFI_CARD_NOT_PRESENT
MEANING
The internal Wi-Fi module is not present.
INSTRUCTIONS
1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported.
2. Replace the Flexi Zone BTS."
Table 12254: BFD_DOWN
Name: BFD_DOWN (11521) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BFD DOWN FL16A
Package: racfl.BFD_DOWN Implicitly cleared: true
Description: BFD DOWN The alarm is raised if the BFD service is not available on the BTS for all BFD sessions belonging to that BFD group. The communication link between the BTS and the BFD peer is defective. No
communication is possible. The system cancels the alarm autonomously once the BFD functionality is available again.
Remedial action: 1. Check if the far end has BFD switched on. 2. Check the cabling and network connections of the far end.
Table 12255: BFD_DOWN_Egress
12/21/2019 Alarms
Name: BFD_DOWN_Egress (11522) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BFD DOWN Egress FL16A
Package: racfl.BFD_DOWN_Egress Implicitly cleared: true
Description: BFD DOWN Egress The alarm is raised if the alarm is enabled, the BFD state of the session is not 'AdminDown', and the BFD packet from the far end contains the diagnostic code =" 'Control Detection Time
Expired' and no ingress alarm is present. The communication link between the BTS and the BFD peer is defective. No communication is possible. The system cancels the alarm autonomously once the local BFD session
receives error-free BFD packets from its BFD peer."
Remedial action: Check the BFD configuration at the local end.
Table 12256: BFD_DOWN_Ingress
Name: BFD_DOWN_Ingress (11523) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BFD DOWN Ingress FL16A
Package: racfl.BFD_DOWN_Ingress Implicitly cleared: true
Description: BFD DOWN Ingress The alarm is raised if the alarm is enabled, the BFD state for the session is not 'AdminDown', and nevertheless, no BFD packet is received at the local end during the detection time. The
communication link between the BTS and the BTS peer is defective, or the peer itself is defective. No communication is possible. The system cancels the alarm autonomously if the local BFD peer receives BFD packets
from the remote BFD peer.
Remedial action: 1. Check the network between both BFD peers for physical link failures or misconfigurations. 2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers
match.
Table 12257: BLUETOOTH_AUTH_FAIL
Name: BLUETOOTH_AUTH_FAIL (11524) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_AUTH_FAIL FL16A
Package: racfl.BLUETOOTH_AUTH_FAIL Implicitly cleared: true
Description: BLUETOOTH_AUTH_FAIL The Flexi Zone Micro BTS or Flexi Zone Access Point has detected repeated bluetooth authentication failures. This could signal that a passkey or pin guessing attack is ongoing. To
prevent a DoS attack, this fault does not disable the bluetooth. Instead, the offending devices are subjected to exponential backoff for authentication attempts and might be blacklisted.
Remedial action: 1. Determine if this event is expected. Investigate audit logs as necessary. 2. If this action is unexpected, disable the bluetooth.
Table 12258: BLUETOOTH_CONNECTED

Name: BLUETOOTH_CONNECTED (11525) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_CONNECTED FL16A
Package: racfl.BLUETOOTH_CONNECTED Implicitly cleared: true
Description: BLUETOOTH_CONNECTED The Flexi Zone Micro BTS or Flexi Zone Access Point has detected a bluetooth network connection. None
Table 12259: BLUETOOTH_ENABLED
Name: BLUETOOTH_ENABLED (11526) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_ENABLED FL16A
Package: racfl.BLUETOOTH_ENABLED Implicitly cleared: true
Description: BLUETOOTH_ENABLED If the actBluetoothTransAlarm parameter allows, this fault is raised to indicate that the bluetooth has been enabled because of any of the following: - The bluetooth config mode set to
explicitly enabled - The bluetooth config mode AutoFallback logic, which automatically enables the bluetooth upon loss of connection to the iOMS or NetAct As a risk mitigation, this fault warns the operator that the bluetooth
is enabled. While the bluetooth is enabled, the site is open to wireless local maintenance over bluetooth.
Remedial action: 1. Determine if the bluetooth should be enabled. 2. If this action is unexpected, disable the bluetooth.
Table 12260: BLUETOOTH_PAIRED
Name: BLUETOOTH_PAIRED (11527) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_PAIRED FL16A
Package: racfl.BLUETOOTH_PAIRED Implicitly cleared: true
Description: BLUETOOTH_PAIRED The Flexi Zone Micro BTS or Flexi Zone Access Point has detected a successful pairing. None
Table 12261: BootableConfigBackupFailed

Name: BootableConfigBackupFailed (103) Severity: major Release:

Type: configurationAlarm Specific problem: Not Applicable FL16A
Package: sw.BootableConfigBackupFailed Implicitly cleared: true
Raised on class: sw.BackupRestoreManager Default probable cause: fileTransferFailure
12/21/2019 Alarms
Description: The alarm is raised when the 5620 SAM fails to back up a set of NE configuration files.
Raising condition: ('Backup State' EQUAL 'Failure')
Clearing condition: ('Backup State' EQUAL 'Success')
Remedial action: Investigation is required to resolve the following possible scenarios: insufficient disk space is available to accommodate the NE configuration files (additional SAM platform alarms will accompany this
alarm); the NE is unreachable (including underlying transport network issue); loss of connectivity to the NE during transfer; the FTP daemon on the NE may have stopped; FTP security credential issues.
Table 12262: BootableConfigRestoreFailed
Name: BootableConfigRestoreFailed (104) Severity: major Release:

Package: sw.BootableConfigRestoreFailed Implicitly cleared: true
Raised on class: sw.BackupRestoreManager Default probable cause: fileTransferFailure
Description: The alarm is raised when the 5620 SAM fails to restore a set of NE configuration files.
Raising condition: ('Restore State' EQUAL 'Failure')
Clearing condition: ('Restore State' EQUAL 'Success')
Remedial action: Investigation is required to resolve the following possible scenarios: the NE is unreachable (including underlying transport network issue); loss of connectivity to the NE during transfer; the FTP daemon on
the NE may have stopped; FTP security credential issues.
Table 12263: BootParametersMisconfigured
Name: BootParametersMisconfigured (35) Severity: critical Release:

Package: netw.BootParametersMisconfigured Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: persistentIndexFailure
Applicable probable causes:
persistentIndexFailure
configFileBootFailure
Description: The alarm is raised when the SNMP Index Boot Status on an NE is not set to Persistent.
Raising condition: (('isGenericNode' EQUAL 'false') AND ('State' NOT EQUAL 'Pre-provisioned') AND ((('Config File Status' NOT EQUAL 'Executed Successfully') AND ('Config File Status' NOT EQUAL
'configFileStatus_unspecified')) OR (('Persistent Index Status' NOT EQUAL 'Rebuild Succeeded') AND ('Persistent Index Status' NOT EQUAL 'persistentIndexStatus_unspecified'))))
Clearing condition: (('Config File Status' EQUAL 'Executed Successfully') AND ('Persistent Index Status' EQUAL 'Rebuild Succeeded'))
Remedial action: Ensure that "SNMP Index Boot Status" is persistent (using cli command "show system information" on the NE). If not, unmanage the network element from SAM, ensure that "persist on" is set in the bof
file, save the bof, save a config file, verify that an index file (.ndx) is saved as well, reboot the router, verify that SNMP Index Boot Status is persistent and finally remanage the router from SAM.
Table 12264: BTSHardwareResynchronization

Name: BTSHardwareResynchronization (11472) Severity: major Release:

Type: configurationAlarm Specific problem: Hardware Resynchronization Failure. FL16A
Package: netw.BTSHardwareResynchronization Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: FILE_ERROR
Description: The alarm is raised when the hardware configuration resynchronization failed. The detail of the error is set in the additional information of the alarm.
Remedial action: Investigation is required to resolve the following possible scenarios: the BTS or OMS is unreachable (including underlying transport network issue); loss of connectivity to the BTS or OMS during transfer;
CORBA and HTTP security credential issues; OMS or BTS internal errors. Once the problem solved in the system, the BTS hardware configuration has to be resynchronized from SAM using BTS full resynchronization.
Table 12265: CELL_FAULTY
Name: CELL_FAULTY (11528) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: CELL FAULTY FL16A
Package: racfl.CELL_FAULTY Implicitly cleared: true
Description: CELL FAULTY A critical fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm. The effect of
the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system automatically
cancels the alarm when the fault has been corrected.
------------------------------------------------
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna calibration error caused by transmission path failure
FAULT ID
1987: EFaultId_CalibrationErrorCausedByTransmissionPathFailureAl
MEANING
Antenna calibration has failed on at least 3 antennas because of a transmission path failure.
The path means all units between the signaling processor (DSP) and the antenna inside the radio module.
INSTRUCTIONS
1. Check if other alarms are not reported at the same time. If other alarms are reported, follow the necessary instructions to clear them.
2. Reset the radio module, which is the fault source.
3. Reset the BTS.
4. Replace the radio module, which is the fault source.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna line faulty
FAULT ID
4045: EFaultId_AntennaLineFaultyAl
MEANING
An alarm message has been received from the antenna line. The antenna line is faulty.
INSTRUCTIONS
The following instructions should be performed on the master RAT side:
1. Check the antenna line and antenna line device that causes the alarm.
2. Fix or replace the faulty parts or devices.
3. Perform a radio module reset (only the master RAT in sharing mode can request for such an operation to be performed).
FAULT NAME
FAULT ID
12/21/2019 Alarms
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
1. Restart the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
2. Reset the BTS.
3. Replace the BTS.
Flexi Zone:
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Baseband resources mapping to cells failure
FAULT ID
12: EFaultId_TcomConfigAl
MEANING
A failure is detected when the eNodeB O>M system presents available FSPs to C-plane software in order to map FSPs to a cell. The FSPs related to the faulty operat
INSTRUCTIONS
3. If steps 1 and 2 do not help, replace the module that is causing the
alarm.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Beamforming cell parameter mismatch
FAULT ID
4254: EFaultId_BfCellParaMismatchAl
MEANING
During BTS startup or BTS recomissioning, the BTSOAM has detected that
there are wrong combination of values for the beam-forming cell parameters "tddSpecSubfConf", "rxCalibrationConfiguration", "actReduceWimaxInterference" for the u
INSTRUCTIONS
1. Check values of the the parameters "TddSpecSubfConf", "rxCalibrationConfiguration", and "actReduceWimaxInterference" and the used beam-forming radio module typ
2. Commission different combination for the mentioned values, or change to a different beam-forming radio module type for the configuration.
FAULT NAME
BTS configuration error (not enough HW for LCR)
FAULT ID
1868: EFaultId_NotEnoughHwForLcrAl
MEANING
During BTS startup, BTS re-comissioning, or BTS resources re-assignment due to a failure, the BTSOAM has detected that there are not enough:
a. radio resources
b. FSP resources
c. cables between the system module and the radio module, or cables between the extension baseband module (FBBx/ABIx) and the radio module, to setup the cell acco
This fault is also detected when a unit that supported a cell is replaced by another unit, and the new unit might not be taken into use because its hardware diffe
The fault is also detected for cells with sufficient DSP resources, but are configured in the same carrier aggregation pool as the cell with missing DSP resources
INSTRUCTIONS
If "Not enough radio resources for cell detected." is displayed in the alarm diagnostic info,the cell might not be set up because not enough radio resources are d
or replace the radio module. Alternatively, re-commission the BTS with fewer cells.
If "Incorrect radio hardware for cell detected." is displayed in the alarm diagnostic info, the cell might not be set up because radio resources that do not enabl
to set the cell up, for example, the number and type of antenna ports, and use the radio module with the required hardware.
If "Not enough DSP resources for cell detected." is displayed in the
alarm diagnostic info, check if the BTS configuration is consistent with the used hardware. It is possible that there is not enough FSP resources to support cells
If re-commissioning does not resolve the issue and
a. extension baseband module (FBBx/ABIx) is used:
1. Ensure that all cables (Power and Baseband bus cables) are connected
to the FBBx/ABIx unit.
2. Block and unblock the system module.
3. If this does not help, replace the FBBx/ABIx unit.
If, at the same time, an alarm caused by fault 4001 (BTS reset) is reported,
a BTS reset might help.
b) extension baseband module (FBBx/ABIx) is not used:
1. Block and unblock the system module.
If "Not enough cables or SFP(s) for cell detected." is displayed in the alarm diagnostic info, the cell might not be set up because the detected cables do not pro
If "Detected hardware doesn't allow to setup cell according to configuration."
is displayed in the alarm diagnostic info, the cell might not be set up because hardware resources are detected but do not enable the cell setup. Check if the pla
FAULT NAME
BTS file error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
BTS reset required
FAULT ID
MEANING
This fault notifies the operator that the BTS must be reset to solve a problem that has been discovered by the BTS O>M system, and that the BTS O>M will not trigg
5. The BTS O>M system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed
6. In BTS runtime, the BTS O>M system has detected resources necessary to cell setup that were not detected during BTS start-up, for example, commissioned radio m
12/21/2019 Alarms
7. BTS O>M has detected an extension baseband module, for example, FBBC, on the same QSFP port, which is different than the previously-removed baseband card, for
INSTRUCTIONS
FAULT NAME
Calibration initialization failure
FAULT ID
4067: EFaultId_CalibrationInitAl
MEANING
Beamforming calibration configuration has failed.
INSTRUCTIONS
Note: Perform the steps below in the order listed until the fault disappears:
2. Replace the RF module.
FAULT NAME
Cell blocked
FAULT ID
49: EFaultId_CellBlockedAl
MEANING
The fault indicates that the user has blocked the cell using the BTS Site Manager.
The user has blocked the cell using the BTS Site Manager.
INSTRUCTIONS
Unblock the cell to cancel the fault.
FAULT NAME
Cell configuration data distribution failed
FAULT ID
6253: EFaultId_CellSetupFailed
MEANING
A BTS raises this fault if it experiences a problem in the internal configuration
data distribution (cell setup) to the C-Plane and U-Plane SW components.
The root cause of the fault may be an incorrect cell configuration in the site configuration file (scf).
INSTRUCTIONS
If it does not help:
1. Check and update the configuration parameters related to the cells.
1. Check and update the configuration parameters related to the cell bandwidth and channels.
2. Reset the BTS.
3. Retry configuration push.
Flexi Zone:
1. Check and update the configuration parameters related to the cell bandwidth and channels.
2. Reset the Flexi Zone Access Point serving the failed cell.
FAULT NAME
Cell disabled due to unknown problem; logs collected
FAULT ID
4261: EFaultId_CellStateAuditAl
MEANING
The cell state audit detected that the cell was unintentionally deactivated
without warning. The symptom data is automatically collected.
INSTRUCTIONS
Please inform the vendor if this alarm is reported. The vendor will do analysis
on the automatically-collected symptom data when the fault was detected.
Automatically collected symptom data (files) are stored in OMS or NetAct dedicated folder.
NetAct - Operating Documentation (Collecting symptom data from LTE to NetAct)
OMS - Administering and Security in LTE OMS (Sec. 13.9.3 OMS troubleshooting data collection for eNodeB).
FAULT NAME
12/21/2019 Alarms
Cell power failure
FAULT ID
4090: EFaultId_TxCarrierInputPowerLowAl
MEANING
The Flexi Radio Module has detected low downlink carrier input power from the System Module.
INSTRUCTIONS
1. Check the other active alarms and act accordingly.
2. If that does not help, block/unblock the system module.
3. a. FSMr2: If that does not help, replace the system module.
b. FSMr3: If the faulty cell is on the baseband extension module, replace the extension module.
FAULT NAME
Cell reconfiguration data distribution failed
FAULT ID
6257: EFaultId_CellReconfigurationFailed
MEANING
The BTS raises this fault if it experiences a problem in the internal configuration
data distribution (cell setup) to C-Plane and U-Plane SW components.
INSTRUCTIONS
1. Check and update configuration parameters related to cell bandwidth and channels.
2. Reset the BTS.
3. Retry configuration push.
Flexi Zone:
1. Check and update configuration parameters related to cell bandwidth and channels.
2. Reset the Flexi Zone Access Point that is serving the failed cell.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Compensation buffer is not enough for RF module delay difference
FAULT ID
4276: EFaultId_RelativeDistanceCompensationBufferNotEnoughAl
MEANING
The transmission delay difference between the radio module that needs to be compensated, and the radio module with the maximum transmission delay, is bigger than
The transmission delay includes the delay in the optical modules of both the system module and radio modules, the delay in the optical fibers and forward delay of
INSTRUCTIONS
Reduce the length of the cables used to connect the radio module to the system module. If the radio module works in the chain, you can also remove the previous ra
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
on FBBx.
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
on the FBBx/ABIx.
FAULT NAME
CPRI-A RF sharing mode conflict
FAULT ID
4375: EFaultId_CpriArfSharingModeConflictAl
MEANING
The LTE eNB has detected an RF sharing configuration conflict in the radio that is also connected to a CDMA BTS.
1. If the alarm diagnostic information contains "Incorrect mode configuration for CPRI-A RF Sharing", then one of the following invalid configurations is detected
1.1. The LTE eNB is in stand-alone mode and the CDMA BTS is in any mode.
1.2. The LTE eNB is in any mode and the CDMA BTS is in stand-alone mode.
1.3. The LTE eNB and CDMA BTS are both in secondary mode.
2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", then the LTE eNB is operating in a secondary
INSTRUCTIONS
1. If the alarm diagnostic information contains "Incorrect mode configuration for CPRI-A RF Sharing", then configure the correct CPRI-A RF sharing mode on the LTE
1.1. LTE eNB is in secondary mode and CDMA BTS is in primary mode.
1.2. LTE eNB is in stand-alone mode and CDMA BTS is disconnected from the radio.
2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", reconfigure the CDMA BTS to give both SW and
3. If the previous steps do not help, reset the alarming radio unit.
4. If the previous steps do not help, reset the LTE eNB and/or CDMA BTS.
FAULT NAME
Distributed site support not enabled
FAULT ID
4076: EFaultId_DistributedSiteSupportNotEnabledAl
MEANING
A long distance (high latency) between the FSM and antenna has been detected but the Distributed Site feature has not been enabled (actDistributedSite =" False).
INSTRUCTIONS
1. Either enable the actDistributedSite parameter or switch to a shorter fiber between the FSM or ABIx and the FR.
2. Restart the System module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Antenna.
SFN Antenna.
FAULT NAME
DSP loading failure
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
DSP U-Plane computing environment startup failed
FAULT ID
4335: EFaultId_DspUplaneComputingEnvironmentStartupFailedAl
MEANING
DSP U-plane computing environment startup has failed.
DSP U-plane computing environment covers U-plane applications and real-time platform services on DSP cores and MCU cores.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
3. REMOTE ACTIONS
FAULT NAME
Failure In Optical Interface <optIf ID>
FAULT ID
3012: EFaultId_FailureInOpticalInterface
MEANING
The SFP (Small Form-factor Pluggable) module might be missing, faulty, or mismatched.
INSTRUCTIONS
12/21/2019 Alarms
3. If that does not help, reset the site.
FAULT NAME
FAULT ID
MEANING
baseband unit.
INSTRUCTIONS
FAULT NAME
Fatal OSE Error
FAULT ID
MEANING
Flexi BTS FDD/TDD:
INSTRUCTIONS
FAULT NAME
Fault between FSM and FSP because of the lack of RP1 clock
FAULT ID
412: EFaultId_LostFrameSync
MEANING
Synchronization between the FCM/FCT and FSP is lost.
Synchronization between the FCT and ABIx is lost.
INSTRUCTIONS
2. If the BTS block/unblock does not help and the fault is reported by all FSP/ABIx modules or by FSP module on system module board, replace the system module. Ot
FAULT NAME
Fiber delay and antenna round trip delay exceeded
FAULT ID
4256: EFaultId_MaximumDelayExceededAl
MEANING
Fiber Delay and Antenna Round Trip Delay exceeds the supported capability of the BTS.
INSTRUCTIONS
1. Confirm if the existing applied configuration is within the configured FR hardware capabilities.
2. Reduce the length of the fiber cable to a length that is supported by the BTS and FR combination.
FAULT NAME
FAULT ID
MEANING
(unit faulty).
INSTRUCTIONS
FAULT NAME
Filter unit faulty
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FPGA R/W error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Frame clock missing
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FSP overheating
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FSP subunit lost
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Incoherence in cell configuration
FAULT ID
4000: EFaultId_IncoherencyInConfiguration
MEANING
Too many cells are commissioned to the BTS.
More LNCELs than the supported maximum number is configured, or too many LCRs are commissioned to one RF module.
INSTRUCTIONS
If other alarms are reported, re-commission the BTS with the correct number of cells per BTS.
Re-commission the BTS with the correct number of LCRs per RF module.
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Invalid frequency channel for the BTS HW
FAULT ID
1807: EFaultId_InvalidFrequencyChannelForBTSHW
MEANING
The radio channel that has been requested in the commissioning file is not supported by the detected BTS radio or MHA hardware because of an incorrect carrier ban
The requested channel in the start-up phase is not acceptable for the BTS hardware because of an incorrect frequency band, and/or a carrier spacing, and/or the nu
INSTRUCTIONS
Check the parameters of the frequencies against the BTS HW configuration. Check whether the connected radio supports the carrier bandwidth requested in the commis
FAULT NAME
Invalid sidelink transmit pool configuration
FAULT ID
6298: EFaultId_InvalidSidelinkTransmitPoolConfigurationAl
MEANING
The sidelink transmit resource pool configuration is invalid, and overlapping with PUCCH region or leaving insufficient resource for PRACH.
INSTRUCTIONS
Correct the site configuration file (scf) content and recommission the BTS by performing one or both of the following steps:
1. Adjust the sidelink direct communication transmit pool configuration in frequency domain in order to:
- not overlap with PUCCH
- reserve enough place for 6 consecutive UL RBs for PRACH and at least one additional PRB for Msg3 (see Note)
2. Reduce the maximal number of active UEs to be supported by adjusting the following parameters:
- maxNumActUe
- aPucchMinNumRrcNoDrb
- aPucchAddAUeRrHo, aPucchAddAUeTcHo
- aPucchMinNumEmergencySessions (if emergency handling is active)
Note: Sidelink direct communication configuration across eNBs on a given carrier has to be identical. Changing configuration on just one eNB is not recommended an
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
LTE-U Channel Change Failure
FAULT ID
6819: EFaultId_LteuChannelChangeFailed
MEANING
The LTE-U feature is enabled (actLteU is 'true') on the eNB and an attempted LTE-U channel (frequency) switch has failed.
INSTRUCTIONS
If the issue persists, perform the steps below in the listed order until the fault disappears.
1. Block/unblock the impacted cell.
2. Reset the Flexi Zone Micro BTS or Access Point.
3. Replace the Flexi Zone Micro BTS or Access Point.
FAULT NAME
LTE-U Duty Cycle Change Failure
FAULT ID
6820: EFaultId_LteuDutyCycleChangeFailed
MEANING
The LTE-U feature is enabled (actLteU is 'true') on the eNB and an attempted LTE-U Duty Cycle change on the same channel has failed.
INSTRUCTIONS
FAULT NAME
FAULT ID
12/21/2019 Alarms
MEANING
INSTRUCTIONS
1. Reset the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi BTS FDD/TDD:
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Module Clock faulty
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Multi-carrier cell disabled
FAULT ID
6815: EFaultId_MultiCarrierCellDisabledAl
MEANING
The multi-carrier cell is disabled because of the lock or block of the other multi-carrier cell.
INSTRUCTIONS
The other multi-carrier cell can be enabled by deleting the blocked or locked cell.
FAULT NAME
No connection to RP1 interface
FAULT ID
4189: EFaultId_NoRp1ConnectAl
MEANING
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone (Flexi Zone Access Point), Flexi Zone SFN Antenna:
The connection to the RP1 Transport (TRSW) or Radio Frequency (RFSW) interface has been lost.
12/21/2019 Alarms

The connection to RP1 Transport (TRSW) interface has been lost.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Not enough PUSCH resources for PRACH
FAULT ID
6294: EFaultId_PrachResourceNotConfigurableAl
MEANING
The configured PUSCH masking and/or PUCCH blanking size for the cell leads to a situation wherein there is no remaining resources for the PRACH allocation.
INSTRUCTIONS
Adjust PUSCH masking and/or PUCCH blanking to reserve enough place for 6 consecutive UL RBs for PRACH and at least one additional PRB for Msg3.
Reduce the maximal number of active UE to be supported by adjusting parameters
maxNumActUe, aPucchMinNumRrcNoDrb, aPucchAddAUeRrHo, aPucchAddAUeTcHo, and aPucchMinNumEmergencySessions if Emergency handling is active.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
PA Critical temperature threshold exceeded
FAULT ID
1980: EFaultId_PaCriTempThresExceedAl
MEANING
The temperature reported by the PA is beyond the critical temperature and fault recovery mechanism have not resulted in a lower temperature - so the RFSW is shutt
INSTRUCTIONS
1. Validate that the ambient temperature is within the specifications, and that no foreign debris has accumulated on the unit. Verify Solar shield if it is insta
3. If that does not help, replace the BTS or Flexi Zone SFN Antenna.
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
Periodic CAM Reports Not Received
FAULT ID
6818: EFaultId_CamReportMissing
MEANING
The LTE-U feature is enabled (actLteU is 'true') and the eNB does not receive Channel Activity Measurement (CAM) reports for 30 seconds. A report that is discarde
INSTRUCTIONS
FAULT NAME
Phase error exceeds 50 ns limit
FAULT ID
4320: EFaultId_PhaseSynchronizationError50nsAl
MEANING
This fault indicates that the absolute phase error between the OCXO (Oven Controlled Oscillator) output and the reference phase provided by the CPRI Ir interface
INSTRUCTIONS
1, Check if other alarms are active in the LTE BTS or SCDMA BTS.
2. Check the optical connection between the SCDMA and LTE BTS. Replace the optical cable and/or SFP(s).
3. If this does not help, reset LTE BTS.
4. If this does not help, reset SCDMA BTS.
5. If this does not help, replace FCT.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Post test failed
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
POST test failed
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Power level not supported
FAULT ID
4008: EFaultId_PowerLevelNotSupportedAl
MEANING
1. The power level that is defined in the radio network (RNW) part of the site configuration file (SCF) file is not supported by the HW.
2. Having different power levels for subcells of a combined supercells as defined in the RNW part of the SCF file is not supported by HW.
INSTRUCTIONS
Define a valid TX power level value in the radio network (RNW) configuration part of the site configuration file (SCF) and use the commissioning wizard of the BTS
Define a valid TX power level value in the RNW configuration file and use the commissioning wizard in the BTS Site Manager to send the file to the Flexi Zone Micr
12/21/2019 Alarms
FAULT NAME
Radio master conflict
FAULT ID
4038: EFaultId_RadioMasterConflictAl
MEANING
The BTSOAM has noticed that the connected radio unit already has another radio master defined apart from the System Module, which should be the radio master for t
INSTRUCTIONS
There might be three reasons for the fault:
1. The radio unit that should only be connected to the LTE Flexi System Module is
also connected to the WCDMA system module. In this case, disconnect the radio unit from the WCDMA system module.
2. There is an error in the commissioning file. In this case, create the commissioning file with the correct relation system module (radio unit), and send the fil
3. The radio master (LTE in LTE-GSM sharing or LTE-LTE sharing) is taking back radio control after, for example, a radio master restart, a master software update,
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
HW capabilities.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF data setup failure
FAULT ID
1997: EFaultId_RfSetupFaultAl
MEANING
A new carrier is being configured by LTE, or the technology sharing the radio unit, which requires the radio unit to retune its RF hardware. Note that the alarm
INSTRUCTIONS
1. In a CPRI-A RF sharing configuration, the CDMA BTS performs the needed recovery actions for this fault.
2. If the fault does not clear within 20 minutes, then reset the radio.
FAULT NAME
RF Module blocked
FAULT ID
12/21/2019 Alarms
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
FAULT NAME
RF Module failure
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF Module filter input power missing
FAULT ID
1910: EFaultId_FrFilterInputPowerMissing
MEANING
The RF Module filter has measured TX power that is too low.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RTWP level below threshold
FAULT ID
4333: EFaultId_RtwpLevelBelowThresholdAl
MEANING
The measured received total wideband power (RTWP) is below the threshold.
INSTRUCTIONS
The too low Rx signal level measured in the digital signal processor (DSP) on the system module or extension baseband module card might be detected because of fai
2. If the first step is completed and the fault is reported again, reset the BTS (block or unblock the BTS).
3. If the previous step is completed and the fault is reported again:
a. If the alarming Rx antenna has an MHA commissioned, then check that the MHA is actually connected to it.
b. If the alarming Rx antenna has an MHA connected, then check that the actual MHA gain matches the commissioned MHA gain.
c. Check that the actual Antenna Total Loss matches the commissioned Total Loss.
d. Check that the actual Antenna Additional Rx Gain matches the commissioned Additional Rx Gain.
4. If the previous steps have been completed and the fault is reported again, replace the optical cables and SFPs that are used to connect the alarming radio modu
12/21/2019 Alarms
5. If the previous steps have been completed and the fault is reported again, replace the MHA connected to the affected Rx antenna.
6. If the previous steps have been completed and the fault is reported again, replace the alarming radio module hardware.
7. If the previous steps have been completed and the fault is reported again, replace the system module hardware or extension baseband module hardware (depending
FAULT NAME
RX out of order
FAULT ID
MEANING
For SNMP interface:
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
SFN cell disabled due to feature disable
FAULT ID
4363: EFaultId_SfnCellDisabledDueToFeatDeactAl
MEANING
The cell using SFN resources is disabled since the feature actSfn is set to "false".
INSTRUCTIONS
None
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
SW corrupted
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
SW fallback
FAULT ID
MEANING
4082:
Otherwise:
4083:
Otherwise:
4085:
Otherwise:
INSTRUCTIONS
Flexi Zone:
None
FAULT NAME
FAULT ID
12/21/2019 Alarms
MEANING
INSTRUCTIONS
FAULT NAME
Temperature alarm
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
TX out of order
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
TX output overdrive
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unit blocked
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
1. Reset the BTS.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Unit unidentified
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unknown HW resource
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
VSWR major alarm
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
2. Reset the Flexi Zone SFN Antenna. If the alarm persists, replace the Flexi Zone SFN Antenna."
Table 12266: CELL_NOTIFICATION
Name: CELL_NOTIFICATION (11529) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: CELL NOTIFICATION FL16A
Package: racfl.CELL_NOTIFICATION Implicitly cleared: true
Description: CELL NOTIFICATION A minor fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm. The
effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The system
automatically cancels the alarm when the fault has been corrected.
Below is the list of BTS fault(s) which may have caused this alarm in BTS FL16A/TL16A release. In case of earlier SW release and in case you need more detailed fa
-------------------------------------------------------------
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna Line Device Operation Failure
12/21/2019 Alarms
FAULT ID
1871: EFaultId_BusyAl
1872: EFaultId_FormatErrorAl
1873: EFaultId_UnsupportedProcedureAl
1874: EFaultId_OutOfRangeAl
MEANING
The device is not working properly, the configuration is not valid, or a given parameter is incorrect.
INSTRUCTIONS
1. Check the functionality of the antenna line device.
2. Check the compatibility between the antenna line device and the BTS.
3. Check that the given parameters are in the valid range.
FAULT NAME
Antenna line device SW download failure
FAULT ID
4047: EFaultId_FileCrcErrorAl
4048: EFaultId_FileContentErrorAl
MEANING
An SW download to an antenna line device has failed because of an incorrect checksum or file format.
INSTRUCTIONS
1. Check the SW package.
2. Download the SW to the antenna line device again.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Correctable bit toggling error
FAULT ID
6700: EFaultId_CorrectableBitTogglingError
MEANING
A correctable bit toggling error is detected in DSP memory.
INSTRUCTIONS
The fault doesn't require any special action because it was already autonomously corrected.
FAULT NAME
Critical bit toggling error
FAULT ID
6701: EFaultId_CriticalBitTogglingError
MEANING
A non-correctable, bit-toggling error has been detected in the critical DSP memory.
INSTRUCTIONS
2. If the fault persists, Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
baseband unit.
INSTRUCTIONS
FAULT NAME
File corrupted in SW download
FAULT ID
28: EFaultId_SwPackageAl
MEANING
The download is corrupted, or the software is incompatible.
INSTRUCTIONS
2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.
12/21/2019 Alarms
FAULT NAME
FR not critical functionality not supported or are not configured correctly.
FAULT ID
4271: EFaultId_FrNotCriticalFunctionalityNotSupportedAl
MEANING
FR functions that are not critical for cell setup are not supported or are not configured correctly. The reason for this might be incompatible RFSW version.
INSTRUCTIONS
Check other active alarms.
FAULT NAME
High memory consumption
FAULT ID
6502: EFaultId_HighMemoryConsumptionAl
MEANING
The physical memory supervision has detected that memory usage has exceeded 90% (FCT (HW rel.3), ASIA) or 98% (FSP/ABIA).
INSTRUCTIONS
Source:
- FCT (HW rel.3)/AIA: Perform eNB reset.
- FSP/FBB/ABIA: Change the cell configuration to decrease call processing load.
None
FAULT NAME
Incoherency in cell configuration
FAULT ID
4044: EFaultId_IncoherencyCellConfigurationAl
MEANING
The cell configuration is not officially supported. Too many cells are assigned to the Tx group of the radio module.
The cell configuration is not officially supported. The configured cell, which has antenna paths in the resourceList antenna paths, does not map exclusively to on
INSTRUCTIONS
Check the configuration of the configured cell.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Link frame timing error
FAULT ID
1996: EFaultId_LinkFrameTimingErrorAl
MEANING
The radio unit has detected that the frame timing on the affected optical port is out of range relative to the clock reference source. In a CPRI-A RF sharing con
INSTRUCTIONS
1. Check the clock reference sources on all the System Modules connected to the radio.
2. If the previous step does not help, reset the radio unit.
3. If the previous steps do not help, replace the radio unit.
FAULT NAME
Maximum number of 1xRTT neighbor relations per cell exceeded
FAULT ID
5500: EFaultId_MaximumNumberOfRttNbRelsPerCellAl
MEANING
A neighbor relation, which is detected by a UE through measurements due to activated ANR features, could not be stored because the maximum number of neighbor rela
INSTRUCTIONS
The operator has to perform either of the following after receiving fault to recover the BTS to full operational state:
1. Manually remove the neighbor object below limit.
2. Reconfigure or change manually threshold limit.
FAULT NAME
Maximum number of 1xRTT NR per cell and carrier exceeded
FAULT ID
5501: EFaultId_MaximumNumberOfRttNbRelsPerCellAndCarrierAl
MEANING
A neighbor relation, which is detected by a UE through measurements due to activated ANR features, is created, but due to the 3GPP limits that max 32 cells can be
INSTRUCTIONS
The operator should do either of the following after receiving the fault to recover the BTS to full operational state:
1. Remove manually neighbor object below limit.
2. Reconfigure or manually change the threshold limit.
FAULT NAME
Micro DTX configuration failure
FAULT ID
4308: EFaultId_MdtxConfigurationFailureAl
MEANING
12/21/2019 Alarms
The micro DTX configuration in a radio module has failed.
INSTRUCTIONS
If the fault is raised during micro-DTX activation, deactivate the mDTX, and
then activate it again by recommissioning.
If the fault is raised during micro-DTX deactivation, activate the mDTX, and
then deactivate it again by recommissioning.
If the fault is not cleared because of repeated activation or deactivation of
the micro-DTX, a BTS site reset clears the fault.
FAULT NAME
Neighbor cell ambiguity detected
FAULT ID
6274: EFaultId_NeighborCellAmbiguityDetected
MEANING
A handover target cell cannot be uniquely selected because several candidates are available for a certain PCI value and carrier frequency.
INSTRUCTIONS
Add the LNREL object pointing to the correct neighbor to allow the handover, or enable the UE-based ANR.
FAULT NAME
Not critical bit toggling error
FAULT ID
6702: EFaultId_NotCriticalBitTogglingError
MEANING
A non-correctable bit toggling error is detected in the non-critical DSP memory area.
INSTRUCTIONS
1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN
Antenna.
2. If the fault persists, replace the Flexi Zone Micro BTS or Flexi
Zone Access Point.
FAULT NAME
OIC MCU Buffer Full
FAULT ID
2011: EFaultId_OIC_MCUBFullAl
MEANING
The control message traffic between the modules is malfunctioning.
INSTRUCTIONS
Check the alarms for the connected module.
FAULT NAME
PCI confusion detected
FAULT ID
6279: EFaultId_PciConfusionDetectedAl
MEANING
This fault occurs when CGI measurements indicate that two or more cells that operate on the same frequency use the same PCI.
INSTRUCTIONS
1. Check for E-UTRAN cells that operate on the same frequency layer, and use the same PCI, and those that are in close vicinity.
2. Re-assign PCIs for the discovered cells.
FAULT NAME
Phich Power Boost not applied
FAULT ID
6112: EFaultId_PhichPowerBoostAl
MEANING
The configured PHICH transmission power boost cannot be applied either partly or entirely because of a lack of remaining power after considering (boosted) cell-sp
INSTRUCTIONS
The Physical HARQ Indication Channel (PHICH) transmission power boost can be increased by reducing the configured boosts for cell-specific downlink reference sign
FAULT NAME
PUCCH configuration inconsistency
FAULT ID
6295: EFaultId_PucchConfigurationNotConsistentAl
MEANING
The automatic PUCCH allocation configuration cannot support the operator configuration.
INSTRUCTIONS
Reduce the maximal number of active UEs to be supported by adjusting the parameters
maxNumActUe, aPucchMinNumRrcNoDrb, aPucchAddAUeRrHo, aPucchAddAUeTcHo,
and aPucchMinNumEmergencySessions if emergency handling is active.
FAULT NAME
Radio memory consumption exceeds abnormal threshold
FAULT ID
4329: EFaultId_RadioMemAboveAbnormalThresholdAl
MEANING
Free memory on the radio module is limited.
INSTRUCTIONS
Recovery restart of the faulty radio module is highly recommended and should be scheduled in the nearest suitable time (for example, during low traffic period).
FAULT NAME
12/21/2019 Alarms
Radio module access panel open
FAULT ID
1991: EFaultId_FrAccessPanelOpenAl
MEANING
The Radio Module is reporting that the access door protecting the maintenance data port is open. The maintenance port allows local control of the Radio Module.
INSTRUCTIONS
Check access door and close if open.
FAULT NAME
Radio module internal communication failure
FAULT ID
1990: EFaultId_FrInternalCommunicationFailureAl
MEANING
The fault is reported in radio modules that consists of two separate hardware units connected by optical cable. The near end Radio Module subunit cannot communic
INSTRUCTIONS
2. If reset has not canceled the fault condition, replace the alarming radio unit hardware.
FAULT NAME
Radio module internal hardware configuration mismatch
FAULT ID
1992: EFaultId_FrInternalHwConfigurationMismatchAl
MEANING
The fault is reported by complex radio modules with multiple physical units where functionality is distributed. An incompatibility has been found between board r
INSTRUCTIONS
2. If a reset does not cancel the fault condition, replace one or both subunits so that they are both of the same type.
FAULT NAME
Radio module low optical signal level to next hop
FAULT ID
1995: EFaultId_FrLowOpticalSignalLevelToNextHopAl
MEANING
The received optical signal on the link port is unexpectedly low from the next hop (further from system module), though communication is still possible.
There is a poor CPRI link connection, bad CPRI cable, or failing CPRI transceiver at the next radio module connected to the cable reported as fault source.
INSTRUCTIONS
1. Reset the radio module reporting the fault (one with blinking red LED display) by blocking/unblocking it. The radio reporting the fault is the one on the cable
2. Reset the system module or radio on the other end of the cable reported as fault source.
6. Replace the radio module reporting the fault, one with blinking red LED display.
FAULT NAME
Radio module low optical signal level to upper hop
FAULT ID
1994: EFaultId_FrLowOpticalSignalLevelToUpperHopAl
MEANING
The received optical signal on the link port is unexpectedly low from upper hop (toward the system module), though communication is still possible.
There is a poor CPRI link connection, bad CPRI cable, or failing CPRI transceiver at the previous radio module or system module connected to the cable reported as
INSTRUCTIONS
1. Reset the radio module reporting the fault (the one with the blinking red LED display) by blocking/unblocking it. The radio reporting the fault is the one on t
2. Reset the system module or radio on the other end of the cable reported as the fault source.
6. Replace the radio module reporting the fault (the one with blinking red LED display).
FAULT NAME
Receive diversity expansion module communication failure
FAULT ID
1989: EFaultId_FrReceiveDiversityExpansionModuleCommunicationFailureAl
MEANING
The communication radio module with external Receive Diversity Expansion Module (RDEM) is lost. The cable to the external RDEM module may be broken or disconnecte
INSTRUCTIONS
1. Reset the alarming radio module.
2. If it does not help, replace the cable between the radio module and the Receive Diversity Expansion Module (RDEM).
3. If previous steps have not cancelled alarm reported due to the fault, replace the alarming radio module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
RRU power loss
FAULT ID
1972: EFaultId_RruAcPowerLossAl
MEANING
The RRU has lost its power supply.
INSTRUCTIONS
1. Check the power connection to the RF module.
FAULT NAME
Serial console activated
FAULT ID
4334: EFaultId_SerialConsoleActivatedAl
MEANING
Serial console is activated on BTS.
INSTRUCTIONS
Disable the serial console (set U-boot variable console_uart to -1).
FAULT NAME
System information broadcast parameters overflow
FAULT ID
6351: EFaultId_SystemInfoValueTagHandlingFailed
MEANING
The System Information Broadcast-related parameters have changed more than 32 times within three hours.
INSTRUCTIONS
This fault does not require any (special) actions.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Temperature alarm
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
Too long fiber for mDTX activation
FAULT ID
4304: EFaultId_TooLongFiberForMdtxAl
MEANING
The cable used between the system module and the radio module exceeds the maximum
supported length for micro DTX (the maximum supported link delay is 80 us; if the
radio module is directly connected to the system module or the extension baseband module, the longest supported cable length is approximately 16 km). The eNB powe
INSTRUCTIONS
Replace the cable with a shorter cable. If the radio module is connected
directly to the system module or the extension baseband module, the longest supported cable length for micro DTX is approximately 16 km.
FAULT NAME
Transmission path failure
FAULT ID
4003: EFaultId_TxFailureTurnMimoOffAl
MEANING
A TX path failure has caused the multiple-input multiple-output (MIMO) or beamforming functionality to be not operational or degraded in the cell that is related
INSTRUCTIONS
Software and hardware reconfiguration can be made to the setup where the faulty TX is not used.
Check the other active BTS faults and act accordingly.
FAULT NAME
Unit (module) temperature is high
FAULT ID
1936: EFaultId_FrTempHigh
MEANING
The validated RF module temperature is higher than or equal to the pre-defined maximum allowed value.
INSTRUCTIONS
FAULT NAME
Unit temperature is high
FAULT ID
2: EFaultId_UnitOverheatAl
MEANING
The temperature of a unit exceeds the threshold value.
INSTRUCTIONS
Check the active fan alarms and the air flow of the BTS.
FAULT NAME
U-plane overload detected
FAULT ID
6053: EFaultId_UplaneOverloadDetectedTrThreeAl
6120: EFaultId_UplaneOverloadDetectedTrOneAl
6121: EFaultId_UplaneOverloadDetectedTrTwoAl
MEANING
An overload situation has been detected by the scheduler on the user plane. Recovery actions are initiated to decrease the load level.
INSTRUCTIONS
The system has automatic actions by decreasing the traffic or the functionality on the traffic. No additional action is required from the operator.
FAULT NAME
VSWR major alarm
FAULT ID
MEANING
INSTRUCTIONS
Flexi Zone:
FAULT NAME
VSWR minor alarm
12/21/2019 Alarms
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
WCDMA PSC confusion detected
FAULT ID
6281: EFaultId_WcdmaPscConfusionDetectedAl
MEANING
This fault occurs when CGI measurements indicate that two or more WCDMA cells
that operate on the same carrier frequency use the same primary scrambling code (PSC).
INSTRUCTIONS
1. Check for UTRAN (FDD) cells that operate on the same frequency layer and
use the same PSC, and that are in close vicinity.
2. Reassign PSCs for the discovered cells.
Table 12267: CELL_OPERATION_DEGRADED
Name: CELL_OPERATION_DEGRADED (11530) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: CELL OPERATION DEGRADED FL16A
Package: racfl.CELL_OPERATION_DEGRADED Implicitly cleared: true
Description: CELL OPERATION DEGRADED A major fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the
alarm. The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries. Do not cancel the alarm. The
system automatically cancels the alarm when the fault has been corrected.
------------------------------------------------------------
FAULT NAME
10b8b coding error in optical interface device
FAULT ID
2004: EFaultId_OIC_LVDSRecAl
MEANING
The fiber cable is experiencing interference; data transmission is faulty.
A physical connection failure between the optical interface and the summing function has occurred.
The reason of the fault might be a low-quality or polluted SFP, or a low-quality optical cable used to connect radio module to system module/extension baseband mo
INSTRUCTIONS
1. Reset the radio module behind the cable reported as the fault source by blocking/unblocking it.
3. Replace the SFP on the radio module port where the cable reported as fault source is terminated.
4. Replace the SFP on the system module or extension baseband module port where the cable reported as fault source is terminated.
6. Replace the radio module behind the cable reported as fault source.
7. If the system module reset helped but the fault is reported again after some time or if the actions mentioned above have not cleared the fault situation, repla
FAULT NAME
3GPP/AISG communication administratively disabled
FAULT ID
4142: EFaultId_Communication3gppAdministrativelyDisabledAl
MEANING
The HDLC link has been disabled for the reporting Antenna Line or IUANT port.
INSTRUCTIONS
Enable the parameter "Communication3gppEnabled" for the reporting Antenna Line to revert changes.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Abnormal CPRI interface to upper hop <OptIf ID>
FAULT ID
1965: EFaultId_AbnormalCpriInterfaceToUpperHopAl
MEANING
The optical interface does not work properly. CPRI transmission to the upper hop does not work properly.
INSTRUCTIONS
Execute the following steps in the ordered sequence. If any of the step does not help, execute the next one:
12/21/2019 Alarms
1. Reset the radio module behind the cable reported as the fault source.
3. Replace the SFP on the radio module port where the cable reported as the fault source is terminated.
4. Replace the SFP on the system module or the extension baseband module port where the cable reported as the fault source is terminated.
5. Replace the optical cable reported as the fault source.
6. Replace the radio module behind the cable reported as the fault source.
7. If the actions mentioned above did not clear the faulty situation, replace the extension baseband module (if the fault is reported on the cable connected to th
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Address mismatch in summing
FAULT ID
2019: EFaultId_Muksu_SsubMmAl
MEANING
There is a baseband bus address mismatch in the summing. There are two possible causes:
1. A configuration error (two different baseband units functioning) - after an acknowledgement, the fault returns.
2. Data corruption on the bus - appears once when an unsynchronized data is sent by the baseband.
INSTRUCTIONS
Check the antenna mapping to the local cells in the commissioning file.
FAULT NAME
Antenna line device configuration failure
FAULT ID
1888: EFaultId_AlConfigurationFailureAl
MEANING
Antenna Line Device is not properly configured.
Antenna Line Device set-up fails, for example due to protocol error or interoperability problem.
INSTRUCTIONS
1. Check/correct the antenna line configuration.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna line device HW failure
FAULT ID
1847: EFaultId_HardwareErrorAl
MEANING
A hardware failure has been reported by ALD (RET, MHA).
INSTRUCTIONS
1. Reset the radio module to give a power-off reset to the antenna line devices.
2. If step 1 does not help, replace the antenna line device.
FAULT NAME
Antenna line device missing software
FAULT ID
1848: EFaultId_WorkingSoftwareMissingAl
MEANING
12/21/2019 Alarms
The unit is in download mode state. This fault is returned when an unsupported procedure occurs in download mode.
INSTRUCTIONS
1. Upload the correct SW to the device (if possible) or perform an ALD power reset (for example, by RF module reset).
FAULT NAME
Antenna line device operation failure
FAULT ID
4239: EFaultId_AldOperationFailureAl
MEANING
The radio module indicated an error upon execution of remote electrical tilt (RET)-related logical operation.
INSTRUCTIONS
1. Check the antenna line and RET devices. Fix or replace the faulty parts or devices.
2. To cancel the alarm, perform an RF module startup or BTS reset.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna line faulty
FAULT ID
4045: EFaultId_AntennaLineFaultyAl
MEANING
An alarm message has been received from the antenna line. The antenna line is faulty.
INSTRUCTIONS
The following instructions should be performed on the master RAT side:
1. Check the antenna line and antenna line device that causes the alarm.
2. Fix or replace the faulty parts or devices.
3. Perform a radio module reset (only the master RAT in sharing mode can request for such an operation to be performed).
FAULT NAME
Antenna line operation degraded
FAULT ID
4046: EFaultId_AntennaLineDegradedAl
MEANING
An alarm message has been received from the antenna line device. The antenna line operation is degraded.
INSTRUCTIONS
Perform the following steps on the MasterRAT side:
1. Check the antenna line and antenna line device that is causing the alarm.
2. Fix or replace the faulty parts and devices.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Antenna periodic calibration has failed
FAULT ID
1988: EFaultId_CalibrationPeriodicFailureAl
MEANING
Antenna periodic calibration result does not meet the requirements for amplitude and/or phase error.
INSTRUCTIONS
No action is required when this fault is reported.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
2. Reset the BTS.
3. Replace the BTS.
Flexi Zone:
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Beamforming calibration failure in RF data path
FAULT ID
6051: EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl
MEANING
Some problems in TX or RX path have caused beam-forming calibration to fail. The path means all units between the signaling processor (DSP), and the antenna line
INSTRUCTIONS
To get the diagnostic information of the alarm for the lists of information similar to the following: RMOD-a/RXb="NOK (Note: "a", "b" are Arabic numbers in practi
Based on the alarm's diagnostic info, one can try the following instructions
to recover from the fault:
1. Check whether the cell is set up under the following scenarios: co-existence with WiMAX in the same band; and co-existence with other LTE networks from other v
2. Check whether the cell is set up under a network using different LTE TDD eNB software releases. If so, then carefully review the calibration configurations in
3. Check whether the GPS or other synchronization sources (for example, synchronization servers) for this cell are working as expected.
4. Check whether the cell is set up under the sharing of RFM with TD-SCDMA.
If so, check whether the carrier configurations in TD-SCDMA and TD-LTE are not in conflict.
5. Check the RP3 links state, especially for the SFP as well as the fibers connecting the RFMs and the BBUs inside the eNB.
6. Block and unblock the cell.
7. Reset the BTS.
8. Examine the antenna cable connection between the RFM and the antenna element.
9. Exchange the cable connection between the antenna and the RFM to check whether the RRU port or the cable is faulty.
10. Replace the hardware(RRU/BBU).
FAULT NAME
BTS file error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
Flexi Zone:
FAULT NAME
BTS reset required
FAULT ID
MEANING
This fault notifies the operator that the BTS must be reset to solve a problem that has been discovered by the BTS O&M system, and that the BTS O&M will not trigg
5. The BTS O&M system detected that the speed of transmission on a baseband link has changed because of a hardware problem (for example, the SFP has been changed
6. In BTS runtime, the BTS O&M system has detected resources necessary to cell setup that were not detected during BTS start-up, for example, commissioned radio m
7. BTS O&M has detected an extension baseband module, for example, FBBC, on the same QSFP port, which is different than the previously-removed baseband card, for
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Buffer over/underflow in clock crossing logic
FAULT ID
2054: EFaultId_MuksuRxClkErrorAl
MEANING
The clock-crossing buffer underflow or overflow in the RX block, and the received data, might be invalid. The fault is an indication of either there is too large
INSTRUCTIONS
2. Check the alarming fiber connection.
FAULT NAME
Calibration initialization failure
12/21/2019 Alarms
FAULT ID
4067: EFaultId_CalibrationInitAl
MEANING
Beamforming calibration configuration has failed.
INSTRUCTIONS
Note: Perform the steps below in the order listed until the fault disappears:
2. Replace the RF module.
FAULT NAME
Cell power failure
FAULT ID
4090: EFaultId_TxCarrierInputPowerLowAl
MEANING
The Flexi Radio Module has detected low downlink carrier input power from the System Module.
INSTRUCTIONS
1. Check the other active alarms and act accordingly.
2. If that does not help, block/unblock the system module.
3. a. FSMr2: If that does not help, replace the system module.
b. FSMr3: If the faulty cell is on the baseband extension module, replace the extension module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Configuration file corrupted
FAULT ID
1924: EFaultId_FrConfigurationFileCorrupted
MEANING
The RF Module SW has detected conflicting or corrupted configuration data.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
on FBBx.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
on the FBBx/ABIx.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Distributed site support not enabled
FAULT ID
4076: EFaultId_DistributedSiteSupportNotEnabledAl
MEANING
A long distance (high latency) between the FSM and antenna has been detected but the Distributed Site feature has not been enabled (actDistributedSite = False). F
INSTRUCTIONS
1. Either enable the actDistributedSite parameter or switch to a shorter fiber between the FSM or ABIx and the FR.
2. Restart the System module.
FAULT NAME
DSP loading failure
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
3. REMOTE ACTIONS
FAULT NAME
Failure In Optical Interface <optIf ID>
FAULT ID
3012: EFaultId_FailureInOpticalInterface
MEANING
The SFP (Small Form-factor Pluggable) module might be missing, faulty, or mismatched.
INSTRUCTIONS
3. If that does not help, reset the site.
FAULT NAME
FAULT ID
MEANING
12/21/2019 Alarms
baseband unit.
INSTRUCTIONS
FAULT NAME
Fiber delay and antenna round trip delay exceeded
FAULT ID
4256: EFaultId_MaximumDelayExceededAl
MEANING
Fiber Delay and Antenna Round Trip Delay exceeds the supported capability of the BTS.
INSTRUCTIONS
1. Confirm if the existing applied configuration is within the configured FR hardware capabilities.
2. Reduce the length of the fiber cable to a length that is supported by the BTS and FR combination.
FAULT NAME
FAULT ID
MEANING
(unit faulty).
INSTRUCTIONS
FAULT NAME
Filter unit faulty
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Flash operation failure
FAULT ID
214: EFaultId_FlashWrAl
215: EFaultId_FlashRdAl
MEANING
A flash memory operation failure. If this fault continuously appears, the flash chip might be broken.
INSTRUCTIONS
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming
module.
2. Reset the alarming module. There are no recovery actions, therefore
reset can be tried once. If that does not help, replace the alarming
module.
FAULT NAME
FPGA R/W error
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FPGA SW update failed
FAULT ID
1928: EFaultId_FrFpgaSwUpdateFailed
MEANING
The FPGA software update in the RF module has failed.
INSTRUCTIONS
FAULT NAME
Frame clock missing
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
High interference to UL special subframe
FAULT ID
6118: EFaultId_HighInterferenceToUlSpecialSubframeAl
MEANING
The Received Interference Power (RIP) value per Physical Resource Block (PRB)
of the cell for UpPTS symbols exceeds the predefined threshold for at least the operator-configured alarmThresholdCrossingTime.
INSTRUCTIONS
Perform network optimization.
FAULT NAME
High interference to UL subframe
FAULT ID
6117: EFaultId_HighInterferenceToUlSubframeAl
MEANING
The received interference power (RIP) value per physical resource block (PRB) of the cell for UL subframes exceeds the predefined threshold for at least the opera
INSTRUCTIONS
Perform network optimization.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Increased BER detected on the optical connection to Radio Module
FAULT ID
1955: EFaultId_IncrBerOnRp3
MEANING
Increased bit error rate has been detected on the optical link to the radio module, which results in sporadic LCV errors in downlink baseband processing.
INSTRUCTIONS
Instructions are divided into three sections. Choose the appropriate section and perform the corresponding steps:
5. Clean the optical connectors that are connected to the SFP. Reset the RF hardware unit and check if this solves the problem.
4. Clean the optical connectors at the RF module end. Reset the RF hardware unit and check if this solves the problem.
2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the system module end. Check measuring equipment documentation for instructi
3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF module end. Check measuring equipment documentation for instructions.
the RF module.
FAULT NAME
Latency of the link for inter-site CA permanently exceeds threshold
FAULT ID
6297: EFaultId_LongLastingLinkLatencyOverTheLimitAl
MEANING
The link between eNBs or Flexi Zone Access Points, carrying the time critical for inter-site Carrier Aggregation data, permanently exceeds the maximum allowed lim
INSTRUCTIONS
Reduce the latency of the network connection between the two eNBs or Flexi Zone Access Points to fulfill the requirements for CA.
FAULT NAME
12/21/2019 Alarms
LNA in bypass mode
FAULT ID
4270: EFaultId_MhaBypassModeAl
MEANING
The MHA was unexpectedly set to bypass mode. The fault might be the result of a conflict in MHA management for a device that can be managed from more than one BTS
INSTRUCTIONS
If LNA is shared between two BTSs and it supports separate AISG ports
for each BTS, check if the LNA is not switched to bypass mode by other BTSs.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Mast Head Amplifier fault
FAULT ID
3120: EFaultId_MastHeadAmplifierFault
MEANING
The FlexiBTS/AirScaleBTS has detected an abnormal operation, or a failure, in the Masthead Amplifier (MHA).
Note that the Tower Mounted Amplifier (TMA) is synonymous to the MHA, and is used by the Antenna Interface Standards Group (AISG).
INSTRUCTIONS
1. Check the cables related to the Masthead Amplifier (MHA).
2. Block and unblock the RF Module to which the MHA is connected to reset the alarming MHA module.
3. Replace the faulty devices.
FAULT NAME
Mast Head Amplifier fault above current window, <line>
FAULT ID
1834: EFaultId_AboveCurrentWindowAl
MEANING
The Masthead Amplifier (MHA) does not work properly. However, the system cannot determine the impact on the RX signal level.
INSTRUCTIONS
1. Check the antenna cables and connectors toward the MHA. Fix or replace the broken parts.
2. Restart the MHA by resetting the Flexi Radio (FR) Module.
Not: This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.
FAULT NAME
Mast Head Amplifier fault below current window, <line>
FAULT ID
1835: EFaultId_BelowCurrentWindowAl
MEANING
The Masthead Amplifier (MHA) does not work properly. Because of the low current drawn by the device, it is assumed that it does not provide gain in the RX signal
To stabilize the situation and keep the RX signal on the required level, there is a need to switch DC power off for the alarming MHA unit and perform FEG recalcul
INSTRUCTIONS
1. Check the antenna cables and connectors toward the MHA. Fix or replace the broken parts.
2. Restart the MHA by resetting the Flexi Radio (FR) Module.
Note: This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
Flexi BTS FDD/TDD:
FAULT NAME
MHA operation degraded
FAULT ID
1869: EFaultId_MinorTMAFaultAl
MEANING
12/21/2019 Alarms
A fault in the Masthead Amplifier (MHA) is detected. MHA functionality is degraded. The real impact cannot be determined.
INSTRUCTIONS
Reset the MHA (using Radio Module reset). If this does not help, replace the alarming module.
FAULT NAME
MHA operation failure
FAULT ID
1870: EFaultId_MajorTMAFaultAl
MEANING
A fault in the Masthead Amplifier (MHA) has been detected. The MHA is not working.
INSTRUCTIONS
1. Reset the MHA by using radio module reset.
2. If this does not solve the problem, replace the alarming module.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Module Clock faulty
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
No feedback signal
FAULT ID
1920: EFaultId_FrNoFeedBackSignal
MEANING
The feedback signal to predistortion is too weak or missing. The TX performance is degraded.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Optical interface data/control/ethernet buffer full
FAULT ID
2006: EFaultId_OIC_DBRxFullAl
2010: EFaultId_OIC_EBFullAl
MEANING
The RP3 or Ethernet buffering is not working, and the buffer becomes full. The
optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect initialization.
Fault 2006 may be detected in Flexi BTS TDD only.
Fault 2010 may be detected both in Flexi BTS FDD and TDD.
INSTRUCTIONS
1. Exchange the alarming and working links, and check where the alarm is reported
now.
2. If the alarming link remains the same, replace the System Module.
3. If the alarming link changes, replace the module behind that link.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Overload collision in transmitter
FAULT ID
2061: EFaultId_MuksuOverloadCollisionAl
MEANING
The transmitter has detected more data coming from a summing than the current link rate can support.
INSTRUCTIONS
2. Check the baseband bus configuration related to the RP3 link speeds.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Periodic CAM Report Inconsistency
FAULT ID
6817: EFaultId_CamReportInconsistency
MEANING
The LTE-U feature is enabled (actLteU is 'true') and the eNB has not received Channel Activity Measurement (CAM) reports for 10 seconds. A report that is discarde
INSTRUCTIONS
FAULT NAME
FAULT ID
12/21/2019 Alarms
MEANING
INSTRUCTIONS
FAULT NAME
Post test failed
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Radio memory consumption exceeds critical threshold
FAULT ID
4330: EFaultId_RadioMemAboveCriticalThresholdAl
MEANING
The radio module has no free memory.
INSTRUCTIONS
Recovery restart of the faulty radio module is highly recommended and should be done as soon as possible.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RET Antenna control failure
FAULT ID
1842: EFaultId_MotorJamAl
1843: EFaultId_ActuatorJamAl
1844: EFaultId_NotCalibratedAl
1845: EFaultId_NotConfiguredAl
1846: EFaultId_ActuatorInterferenceAl
MEANING
1845: TILT is not configured.
Others: Antenna tilting is not possible or might function incorrectly.
INSTRUCTIONS
Perform RET calibration. If that does not help, replace the RET unit.
In case of 1845: send a valid configuration file to the alarming device.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
HW capabilities.
FAULT NAME
RF BB bus connection transmission error
FAULT ID
1906: EFaultId_FrRfBbBusConnTransError
12/21/2019 Alarms
MEANING
There is an error in the baseband or optical bus.
INSTRUCTIONS
2. Check if the SFP (Small Form Factor Pluggable) is properly connected/mounted in the System Module. If the SFP connection/mounting is not correct, readjust the
1. Check if the optical cable(s) is/are not overly bent. If they are, replace them since overly bending the optical fiber cables damages them and can detach or da
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF data setup failure
FAULT ID
1997: EFaultId_RfSetupFaultAl
MEANING
A new carrier is being configured by LTE, or the technology sharing the radio unit, which requires the radio unit to retune its RF hardware. Note that the alarm
INSTRUCTIONS
1. In a CPRI-A RF sharing configuration, the CDMA BTS performs the needed recovery actions for this fault.
2. If the fault does not clear within 20 minutes, then reset the radio.
FAULT NAME
RF Module blocked
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
Flexi Zone:
FAULT NAME
RF Module failure
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF Module file not found
FAULT ID
1902: EFaultId_FrFileNotFound
MEANING
The RF Module SW has detected that a non-critical configuration file is missing.
INSTRUCTIONS
1. Check that the TEMP and CALI files are present. Upload any missing files. Reset the RF Module.
2. If the files are present, reset the FR HW unit.
3. If the problem is still observed after performing step 1, replace the FR HW unit.
1. Block and/or unblock BTS.
Flexi Zone:
FAULT NAME
RF Module filter input power missing
FAULT ID
1910: EFaultId_FrFilterInputPowerMissing
MEANING
The RF Module filter has measured TX power that is too low.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF Module power input faulty
FAULT ID
1959: EFaultId_FrPowerInputFaultAl
MEANING
Input voltage to the radio unit is outside of the expected range, but the radio unit power supply can still provide output voltages adequate for operation.
INSTRUCTIONS
1. Check the power supply to the affected radio module.
2. If the alarm persists, replace the radio module that is generating the alarm.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RF Power decreased
FAULT ID
1927: EFaultId_FrPowerDecreased
MEANING
The highest temperature exceeds the power decrease limit in the RF module.
INSTRUCTIONS
1. Check if the ambient temperature or environmental conditions are within the design limits for the radio module. When the ambient temperature or environmental c
2. Check if the air flow is not blocked by some objects. Make sure minimum thermal clearances are followed. Remove any objects that might be blocking the airflow,
3. Check if excessive sunlight is causing an overheat. Install sunshield following mounting instructions and recommendations.
FAULT NAME
RF RX AGC issues
FAULT ID
1977: EFaultId_RfRxAgcIssueAl
MEANING
The Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna is not able to receive the incoming signal properly. The uplink signal might be too l
INSTRUCTIONS
1. Check for the possible installation issues and co-located interference.
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
RTWP level below threshold
FAULT ID
4333: EFaultId_RtwpLevelBelowThresholdAl
MEANING
The measured received total wideband power (RTWP) is below the threshold.
INSTRUCTIONS
The too low Rx signal level measured in the digital signal processor (DSP) on the system module or extension baseband module card might be detected because of fai
2. If the first step is completed and the fault is reported again, reset the BTS (block or unblock the BTS).
3. If the previous step is completed and the fault is reported again:
a. If the alarming Rx antenna has an MHA commissioned, then check that the MHA is actually connected to it.
b. If the alarming Rx antenna has an MHA connected, then check that the actual MHA gain matches the commissioned MHA gain.
c. Check that the actual Antenna Total Loss matches the commissioned Total Loss.
d. Check that the actual Antenna Additional Rx Gain matches the commissioned Additional Rx Gain.
4. If the previous steps have been completed and the fault is reported again, replace the optical cables and SFPs that are used to connect the alarming radio modu
5. If the previous steps have been completed and the fault is reported again, replace the MHA connected to the affected Rx antenna.
6. If the previous steps have been completed and the fault is reported again, replace the alarming radio module hardware.
7. If the previous steps have been completed and the fault is reported again, replace the system module hardware or extension baseband module hardware (depending
FAULT NAME
RX out of order
FAULT ID
MEANING
For SNMP interface:
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Summing not enabled for message type
FAULT ID
2059: EFaultId_MuksuSummingNotEnabledAl
MEANING
Summing checks the headers of the messages to be summed. If the header is not an allowed type, summing is not performed and an empty message is sent instead.
INSTRUCTIONS
2. Check the logs for line code violation (LCV) errors related to optical links.
3. Verify Small Form-factor Pluggable (SFP) transceiver and fiber conditions.
FAULT NAME
SW corrupted
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Temperature alarm
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
12/21/2019 Alarms
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
toggling BTS fault.
INSTRUCTIONS
FAULT NAME
Too long optical cable between system module and radio module
FAULT ID
4277: EFaultId_OpticalCableFsmRfModuleTooLongAl
MEANING
The length of the optical cable between the system module and the radio module is too long.
INSTRUCTIONS
Reduce the length of the cable used to connect the radio module to the system module. If the radio module works in a chain, you can also remove the previous radio
FAULT NAME
Transmission quality deteriorated
FAULT ID
1921: EFaultId_FrTransmissionQualityDetoriated
MEANING
The TX signal adjustment has failed.
INSTRUCTIONS
FAULT NAME
Transmission rule collision in Muksu
FAULT ID
2060: EFaultId_MuksuTransmissionRuleCollisionAI
MEANING
The transmitter has detected an RP3 message from a summing coincident with a transmission rule.
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
TX input overdrive
FAULT ID
1985: EFaultId_FrTxInputOverdriveAl
MEANING
Hardware protection logic in the radio unit has activated overdrive protection on the TX path to avoid damage to hardware. Overdrive protection keeps the TX path
INSTRUCTIONS
1. Confirm if the existing applied configuration is within the configured FR HW capabilities.
3. Restart the radio unit.
4. If the fault condition persists after the radio restart, restart the BTS.
5. If the HW configuration is confirmed, then this problem is caused by the eNB SW. Check other active alarms.
FAULT NAME
TX out of order
FAULT ID
MEANING
12/21/2019 Alarms
INSTRUCTIONS
FAULT NAME
TX output overdrive
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unit blocked
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
Unit unidentified
FAULT ID
MEANING
INSTRUCTIONS
FAULT NAME
VSWR major alarm
FAULT ID
MEANING
INSTRUCTIONS
12/21/2019 Alarms
Flexi Zone:
FAULT NAME
VSWR minor alarm
FAULT ID
MEANING
INSTRUCTIONS
Table 12268: ClientDelegateServerStatus
Name: ClientDelegateServerStatus (731) Severity: critical Release:

Type: communicationsAlarm Specific problem: Not Applicable FL16A
Package: server.ClientDelegateServerStatus Implicitly cleared: true
Raised on class: server.ClientDelegateServer Default probable cause: systemFailed
Description: The alarm is raised when a client delegate server is unreachable.
Raising condition: ('Server Status' EQUAL 'Down')
Clearing condition: ('Server Status' EQUAL 'Up')
Remedial action: Informational - if the alarm persists or is occurring frequently then investigation is required to understand why the connectivity between the client delegate platform and SAM servers is unreliable or the
client delegate server itself is unreliable.
Table 12269: ContainingEquipmentAdministrativelyDown

Name: ContainingEquipmentAdministrativelyDown (466) Severity: minor Release:

Type: equipmentAlarm Specific problem: Not Applicable FL16A
Package: equipment.ContainingEquipmentAdministrativelyDown Implicitly cleared: true
Raised on class: equipment.Port Default probable cause: containingEquipmentAdministrativelyDown
Description: The alarm is raised when the compositeEquipmentState attribute has a value of containingEquipmentAdministrativelyDown.
Raising condition: (('Status' EQUAL 'Parent Admin Down') AND ('isTerminatable' EQUAL 'true'))
Clearing condition: (('Status' NOT EQUAL 'Parent Admin Down') OR ('isTerminatable' NOT EQUAL 'true'))
Remedial action: Informational - no corrective action required.
Table 12270: ContainingEquipmentMismatch
Name: ContainingEquipmentMismatch (464) Severity: major Release:

Package: equipment.ContainingEquipmentMismatch Implicitly cleared: true
Raised on class: equipment.Port Default probable cause: containingEquipmentMismatch
Description: The alarm is raised when the compositeEquipmentState attribute has a value of containingEquipmentMismatch.
Raising condition: (('Status' EQUAL 'Parent Type Mismatch') AND ('isTerminatable' EQUAL 'true'))
Clearing condition: (('Status' NOT EQUAL 'Parent Type Mismatch') OR ('isTerminatable' NOT EQUAL 'true'))
Remedial action: A configuration error has occurred which must be corrected. The card type configured for the slot identified in the alarm must match the installed card type.
Table 12271: ContainingEquipmentOperationallyDown
Name: ContainingEquipmentOperationallyDown (465) Severity: major Release:

Package: equipment.ContainingEquipmentOperationallyDown Implicitly cleared: true
Raised on class: equipment.Port Default probable cause: containingEquipmentDown
Description: The alarm is raised when the compositeEquipmentState attribute has a value of containingEquipmentOperationllyDown.
Raising condition: (('Status' EQUAL 'Parent Oper Down') AND ('isTerminatable' EQUAL 'true'))
Clearing condition: (('Status' NOT EQUAL 'Parent Oper Down') OR ('isTerminatable' NOT EQUAL 'true'))
Remedial action: The operational state of the equipment element indicated in the alarm is down. This may be due to the element's administrative state or it may indicate that the element has failed.
Table 12272: CRL_Update_failure

12/21/2019 Alarms
Name: CRL_Update_failure (11531) Severity: indeterminate

Type: communicationsAlarm Specific problem: CRL Update failure Release:
Package: racfl.CRL_Update_failure Implicitly cleared: true FL16A
Description: CRL Update failure This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL). Please refer to PDDB parameter 'CERTH::CRLInfo: CRLUpdateFailureReason' for failure reasons. The
Certificate Revocation List could not be updated. New revoked certificates remain unknown to the BTS. The alarm is cleared after a successful update of the Certificate Revocation List in a new attempt.
Remedial action: Execute general configuration checks: - Configuration of CMP server IP address and port, and DNS server IP address. - Configuration of routing entries towards remote peers. - Configuration of IPSec
policies towards remote peers. Check remote peers and intermediate network elements interconnections. Check the LDAP connection towards the Certificate Revocation List server. Check DNS names. Check the size of
the file at the Certificate Revocation List server.
Table 12273: downgradedCardAlarm
Name: downgradedCardAlarm (256) Severity: warning Release:

Type: softwareAlarm Specific problem: Not Applicable FL16A
Package: equipment.downgradedCardAlarm Implicitly cleared: true
Raised on class: equipment.Card Default probable cause: downgradedCard
Description: The alarm is raised when an IOM is not upgraded or reset after a device software upgrade of both CPMs. A device resets an IOM automatically after 120 minutes if the IOM is not manually reset after a CPM
upgrade.
Raising condition: ('operationalState' EQUAL 'Downgrade')
Clearing condition: ('operationalState' EQUAL 'Up')
Table 12274: EquipmentAdministrativelyDown
Name: EquipmentAdministrativelyDown (455) Severity: minor Release:

Package: equipment.EquipmentAdministrativelyDown Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: equipmentAdministrativelyDown
Description: The alarm is raised when the compositeEquipmentState attribute has a value of equipmentAdministrativelyDown.
Raising condition: ('compositeEquipmentState' EQUAL 'Admin Down')
Clearing condition: ('compositeEquipmentState' NOT EQUAL 'Admin Down')
Table 12275: EquipmentDown
Name: EquipmentDown (10) Severity: major Release:

Package: equipment.EquipmentDown Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: inoperableEquipment
Description: The alarm is raised when the compositeEquipmentState attribute has a value of equipmentOperationallyDown.
Raising condition: ('compositeEquipmentState' EQUAL 'Oper Down')
Clearing condition: ('compositeEquipmentState' NOT EQUAL 'Oper Down')
Remedial action: This alarm indicates that a card in the NE has failed. The card must be replaced.
Table 12276: EquipmentInTest
Name: EquipmentInTest (11) Severity: warning Release:

Package: equipment.EquipmentInTest Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: equipmentInTest
Description: The alarm is raised when equipment enters a diagnostic state.
Raising condition: ('compositeEquipmentState' EQUAL 'In Test')
Clearing condition: ('compositeEquipmentState' NOT EQUAL 'In Test')
Table 12277: EquipmentMismatch
12/21/2019 Alarms
Name: EquipmentMismatch (9) Severity: major Release:

Package: equipment.EquipmentMismatch Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: equipmentTypeMismatch
Description: The alarm is raised when the compositeEquipmentState attribute has a value of equipmentMismatch.
Raising condition: ('compositeEquipmentState' EQUAL 'Type Mismatch')
Clearing condition: ('compositeEquipmentState' NOT EQUAL 'Type Mismatch')
Remedial action: A configuration error has occurred which must be corrected. The card type configured for the slot identified in the alarm must match the installed card type.
Table 12278: Ethernet_OAM_CCM_fault

Name: Ethernet_OAM_CCM_fault (11558) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: Ethernet OAM CCM fault FL16A
Package: racfl.Ethernet_OAM_CCM_fault Implicitly cleared: true
Description: Ethernet OAM CCM fault The alarm is triggered whenever a service OAM error related to the transmission of Continuity Check Messages (CCM) persists on a given Ethernet interface as soon as one of the
error conditions below occur: The following alarms are defined: 1. MDL_MISMATCH, priority 5 (highest priority): A CCM is received with an MDL that is lower than the highest configured one in the BTS, and does not match
any of the configured ones. Example: CCM fault level - prio 5 cause MDL_MISMATCH Note: For MDL_MISMATCH cases, it might not be possible to display the local MDL where the fault was detected. 2.
MAID_MISMATCH priority 5: A CCM is received with an MDL that is configured in the BTS, but with an MAID that does not match any MA configured in the BTS on this MDL. Example: CCM fault level 5 prio 5 cause
MAID_MISMATCH 3. MAID_MISMATCH priority 5: A CCM is received with matching MDL and MAID, but the VLAN membership of the received frame does not match the VLAN configuration of the addressed MA.
Example: CCM fault level 5 prio 5 cause MAID_MISMATCH 4. ERR_CCM, priority 4: A CCM is received with known MDL and MAID, but the MEPID is not configured in the Remote MEP list of the MA. Example: CCM fault
level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED 5. ERR_CCM, priority 4: A CCM is received with known MDL, MAID, and MEPID, but the CCM interval coded in the received CCM does not match the interval
configured in the BTS. Ex: CCM fault level 5 prio 4 cause WRONG_CCM_INTERVAL 6. REMOTE_CCM, priority 3: A CCM was not received for 3.5 intervals from at least one remote MEP in the MA. Ex: CCM fault level 5
prio 3 cause REMOTE_CCM_DEFECT 7. RDI_CCM, priority 1 (lowest priority): An RDI flag is detected in the CCM frames from one remote peer. Example: CCM fault level 5 prio 1 cause REMOTE_DEFECT_INDICATION
The alarm displays the following information: - Alarm Name - Alarm Priority - Alarm cause: if different sources produce the same alarm - MD level at which the alarm was detected The transport connection toward the remote
peer might be defective. Traffic might get lost. The alarm is cleared when the CCM fault condition has stopped for at least 10 seconds, and no other CCM fault condition with a lower priority is active.
Remedial action: 1. Check the cabling. 2. Check the CCM configuration at the remote peer.
Table 12279: Ethernet_OAM_ETH_AIS_fault
Name: Ethernet_OAM_ETH_AIS_fault (11559) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: Ethernet OAM ETH_AIS_fault FL16A
Package: racfl.Ethernet_OAM_ETH_AIS_fault Implicitly cleared: true
Description: Ethernet OAM ETH_AIS_fault When an MEP receives a valid ETH-AIS frame and AIS is enabled, it shall trigger an AIS alarm containing the following information: - receiving interface - MD level - Source MAC
address Note:For FSMr3/AirScale unit types, interface is provided as: 'module type name' EIF 'interface number'. For Flexi Zone Micro BTS, interface is provided as: EIF 'interface number'. The transport connection towards
the remote peer may be defective. Traffic may get lost. The alarm is cancelled if no ETH_AIS message was received within 3.5 times the configurable ETH_AIS transmission period. This is either within 3.5 seconds or 3.5
minutes.
Remedial action: 1. Check cabling. 2. Check the configuration at the remote peer.
Table 12280: EXTERNAL_AL_1
Name: EXTERNAL_AL_1 (11532) Severity: indeterminate Release:

Type: environmentalAlarm Specific problem: EXTERNAL AL 1 FL16A
Package: racfl.EXTERNAL_AL_1 Implicitly cleared: true
Description: EXTERNAL AL 1 This is an external user-defined alarm. The alarm is defined by the user in a hardware database. Not applicable to Flexi Zone Micro platform and Flexi Zone platform. The effect of the alarm
depends on the purpose that was configured for the user-defined alarm input in the BTS. Do not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
Remedial action: The operation depends on the type of alarm that is used as external alarm number 1.



Description: EXTERNAL AL 11 This is an external user-defined alarm. The alarm is defined by the user in a hardware database. The effect of the alarm depends on the purpose that was configured for the user-defined
alarm input in the BTS. Do not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
12/21/2019 Alarms








12/21/2019 Alarms









12/21/2019 Alarms









12/21/2019 Alarms





Table 12306: FrameSizeProblem (netw)

Name: FrameSizeProblem (37) Severity: critical Release:

Package: netw.FrameSizeProblem Implicitly cleared: true
Raised on class: netw.StatefullConnectableInterface Default probable cause: frameSizeProblem
Description: The alarm is raised when a provisioned MTU size value is greater than the supported MTU size value.
Raising condition: (('mtuMismatch' EQUAL 'true') AND ('portId' NOT EQUAL '0L'))
Clearing condition: (('mtuMismatch' EQUAL 'false') OR ('portId' EQUAL '0L'))
Remedial action: A configuration error has been made which must be corrected. The MTU value must be changed such that is less than or equal to the supported MTU size value.
Table 12307: FTM_AIS
Name: FTM_AIS (11560) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_AIS FL16A
Package: racfl.FTM_AIS Implicitly cleared: true
Description: FTM_AIS Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its received signal. All other transmission alarms
related to this signal are suppressed. Probable cause: There is a transmission problem somewhere in the intermediate network, and AIS is sent instead of user traffic. Possible impact on the connections over the interface in
question: - no calls are possible - loss of remote management access to other network elements in the RAN
Remedial action: Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.
Table 12308: FTM_BTS_RESET_REQUIRED
12/21/2019 Alarms
Name: FTM_BTS_RESET_REQUIRED (11561) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_BTS_RESET_REQUIRED FL16A
Package: racfl.FTM_BTS_RESET_REQUIRED Implicitly cleared: true
Description: FTM_BTS_RESET_REQUIRED A change to the BTS IP settings has been received from the BTS Site Manager. The BTS should be restarted to activate the change. The BTS does not take the new settings
into use before a reset.
Remedial action: Reset the BTS when all the required BTS IP settings have been set.
Table 12309: FTM_DPD

Name: FTM_DPD (11562) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_DPD FL16A
Package: racfl.FTM_DPD Implicitly cleared: true
Description: FTM_DPD A dead peer has been detected in one of the IPsec associations of the FTM. There is no response to the requests sent to the peer during the IKE SA setup, the IPsec SA setup, or during DPD.
Note: When the IPSec backup tunnel feature is enabled, this alarm should not be raised because of failures when trying to set up primary IPSec tunnel in 'Secondary_Active_Probing_Primary' state. Possible reasons: - a
cable is cut or there is no cable connected to the interface - the signal is excessively attenuated - the port at the connected far end node is switched off Possible effects: - No calls are possible. - loss of remote management
access to other network elements in the RAN - loss of synchronization if the interface is used as a synchronization source - IKE SAs and IPSec SAs cannot be established or re-keyed. The alarm condition for a protect
policy does not exist anymore if the latest IKE message is answered by the peer. The alarm is canceled as soon as the alarm condition does not exist for any protect policy. Note: When the IPSec backup tunnel feature is
enabled, a DPD alarm caused by the primary tunnel failure is cleared when switch-over is successful for all primary tunnels (that is, all secondary tunnels are successfully established). Similarly, any DPD alarm raised
because of a secondary tunnel failure is cleared when switchback is successful for secondary tunnels (that is, all primary tunnels are successfully established).
Remedial action: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are,
follow the instructions for handling those alarms.
Table 12310: FTM_EBER
Name: FTM_EBER (11563) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_EBER FL16A
Package: racfl.FTM_EBER Implicitly cleared: true
Description: FTM_EBER Excessive bit error rate: The measured bit error rate exceeds the threshold value of BER-3 (10E-3). Probable causes: - the signal level is too low (optical connectors or cables are dirty, electrical
connectors or cables are corroded) - the specified maximum length of the cable is exceeded - the connector is not properly connected to the unit - the receiver or the far-end transmitter has failed Possible impact: - slow
management access to the WBTS and other network elements in the RAN - poor voice quality and data performance - if this interface is part of an IMA group, this IMA link should be temporarily suspended from operation
Remedial action: 1. Clean the cables and connectors. 2. Check that the connectors are properly connected to the unit. 3. Check that the cable connected to the interface in question is not damaged and is within the
specifications. 4. Follow the signal in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life). If they are, follow the instructions for handling those alarms.
Table 12311: FTM_FAULT_TOGGLING
Name: FTM_FAULT_TOGGLING (11564) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_FAULT_TOGGLING FL16A
Package: racfl.FTM_FAULT_TOGGLING Implicitly cleared: true
Description: FTM_FAULT_TOGGLING An FTM fault, for which the fault name appears in the Fault name field, is toggling in the FTM. Toggling fault condition is informed to the user with this new FTM fault. Toggling faults
are supressed until the toggling alarm condition is cleared. Severity of this FTM fault is the same as the severity of the toggling FTM fault.
Remedial action: 1. Check the fault name of the toggling FTM fault from the Fault name of this fault. 2. Follow the instructions of the toggling FTM fault to clear the problem. Note: Detailed information about the toggling
frequency can be found in alarm history file, which can be downloaded using the BTS Site Manager. The log file is available with Snapshot.
Table 12312: FTM_LOF

Name: FTM_LOF (11565) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOF FL16A
Package: racfl.FTM_LOF Implicitly cleared: true
Description: FTM_LOF Loss of frame: It is not possible to carry traffic on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed. Probable cause for E1 interfaces: The
interface at the far end is not configured to be a framed E1 interface. Probable cause for T1 interfaces: The interface at the far end is not configured to be a T1 interface. Possible impact on the connections over this
interface: - no calls are possible - loss of remote management access to other network elements in the RAN - loss of synchronization if the interface is used as synchronization source
Remedial action: E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 interface. If this is not the case, reconfigure the interfaces so that they match each other. JT1
interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. If this is not the case, reconfigure the interfaces so that they match each other.
Table 12313: FTM_LOMF
Name: FTM_LOMF (11566) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOMF FL16A
Package: racfl.FTM_LOMF Implicitly cleared: true
Description: FTM_LOMF Loss of multi-frame: The interface referenced in the alarm text has lost the multi-frame alignment. Probable cause: The interface type has not been configured to meet the framing of the interface
at the far end. For E1 interfaces, the configuration of the far-end node should be E1 Multiframe. Possible impact: The performance management data collected on this interface becomes invalid.
Remedial action: Check that the configured interface type matches the configured interface type of the far-end interface. If this is the case, the problem is somewhere in the transmission network.
Table 12314: FTM_LOS
12/21/2019 Alarms
Name: FTM_LOS (11567) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOS FL16A
Package: racfl.FTM_LOS Implicitly cleared: true
Description: FTM_LOS Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD: No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed.
Probable causes for Ethernet interfaces: - a cable is cut, or there is no cable connected to the interface - the electrical signal is excessively reduced - the port at the connected far-end node is switched off Flexi Zone Micro
FDD, Flexi Zone Micro TDD: No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed. Probable causes for Ethernet interfaces: - a cable is cut, or
there is no cable connected to the interface - the electrical signal is excessively reduced - the port at the connected far-end node is switched off The fault is generated only when the interface is not configured as LMP (that
is, generated only when the interface is configured as the primary BH port, or when daisy chaining (enableLayer2Switching) is enabled). Possible impacts on the connections over this interface are: - no calls are possible -
loss of remote management access to other network elements in the RAN - loss of synchronization if the interface is used as a synchronization source
Remedial action: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are,
follow the instructions for handling those alarms. 4. Connect a loop cable and check whether the alarm disappears to verify that the hardware of the interface unit works correctly.
Table 12315: FTM_RDI

Name: FTM_RDI (11568) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_RDI FL16A
Package: racfl.FTM_RDI Implicitly cleared: true
Description: FTM_RDI Remote defect indication: It is sent by the intermediate or the far-end equipment because it detects a serious fault in the received signal. Probable cause: The far end has a LOS, LOF, or AIS alarm
on its receiving interface. Possible impact on the connections over this interface: - no calls are possible - loss of remote management access to other network elements in the RAN - loss of synchronization if the interface is
used as a synchronization source
Remedial action: 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. Connect a loop cable and check that no alarms appear for this
interface to check the transmit hardware.
Table 12316: FTM_RESET
Name: FTM_RESET (11569) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_RESET FL16A
Package: racfl.FTM_RESET Implicitly cleared: true
Description: FTM_RESET The transport part of the BTS has been reset at the date and time given in the notification. 1. FSMr2 supports the following cause for the reset: 'trs power-on reset': Cold start 'trs watchdog reset':
System overload 'trs startup failure': Failure during startup 'trs software failure': Software failure 'trs management reset': Reset triggered by management interface 'trs fallback': Fallback executed FSMr3/AirScale supports
the following cause for the reset: 'trs power-on reset': Cold start 'trs watchdog reset': System overload 'trs software failure': Software failure 'trs management reset': Reset triggered by management interface 'trs spurious
reset': Reset reason detection failed 2. The '$date' format is the local time stamp (GMT+/-xx:xx). For example: 2014-04-12 00:51:26 GMT+0530 The fault has no further consequences.
Remedial action: No actions are required.
Table 12317: FTM_SECURITY_USER_ACCOUNT
Name: FTM_SECURITY_USER_ACCOUNT (11570) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SECURITY_USER_ACCOUNT FL16A
Package: racfl.FTM_SECURITY_USER_ACCOUNT Implicitly cleared: true
Description: FTM_SECURITY_USER_ACCOUNT A specific BTS local operator account has been locked. The number of failed login attempts for a BTS local operator account has exceeded the threshold, and the account
has been locked on the BTS. No further logins are permitted for this account until it is unlocked. No further logins are permitted for that account until it is unlocked.
Remedial action: Check the validity of the username and password of the account.
Table 12318: FTM_SFP

Name: FTM_SFP (11571) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SFP FL16A
Package: racfl.FTM_SFP Implicitly cleared: true
Description: FTM_SFP Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD: The Small Form-Factor Pluggable (SFP) module detected in the interface connector does not comply with security requirements. It does
not have a class 1 laser. Flexi Zone Micro FDD, Flexi Zone Micro TDD: The Small Form-Factor Pluggable (SFP) module is not supported, not present, or could not be recognized. The SFP module detected in the interface
connector does not comply with the SFP module types supported by the BTS element. The SFP module type is checked to ensure that only laser class 1-compliant standard Ethernet SFP modules are used. The SFP
module was expected by the SW, but found missing. Probable causes: - No SFP module is inserted at the SFP-based Ethernet interface. - The interface contacts of the SFP module are corroded or dirty, preventing either
read access to the SFP module at the time of reading compliance data from the SFP, or preventing detection of the module. - The SFP module type is not supported. The fault is generated only when the interface is not
configured as LMP (that is, generated only when the interface is configured as the primary BH port or when daisy chaining (enableLayer2Switching) is enabled). Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD: The
interface cannot be used for transmission. Flexi Zone Micro FDD, Flexi Zone Micro TDD: The interface cannot be used for transmission. Conditionally, Bluetooth is enabled when the backhaul goes down. The laser of the
SFP module is not switched on, or no SFP module was detected at all. The Ethernet Link is down. An Ethernet Link cannot be successfully established. No Ethernet data or clock information is exchanged between this
interface. Possible impact on the connections over this interface: - Voice calls or data connections cannot be established. - Remote management connectivity cannot be established. - Loss of synchronization if the interface
is used as a synchronization source. - Depending on use of the Ethernet interface, the above-described impact can occur for the local BTS and/or other BTS elements if they are chained through the Ethernet interface.
Remedial action: Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: Insert a Small Form-Factor Pluggable (SFP) module with the correct laser type (class 1) to the Gigabit Ethernet interface of the
unit. Flexi Zone Micro FDD, Flexi Zone Micro TDD: 1. Plug-out and plug-in the SFP module. 2. Check for SFP validity (could be wrong type). 3. Insert a compliant SFP module.
Table 12319: FTM_SFP_WARNING
Name: FTM_SFP_WARNING (11572) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SFP_WARNING FL16A
Package: racfl.FTM_SFP_WARNING Implicitly cleared: true
12/21/2019 Alarms
Description: FTM_SFP_WARNING There is an issue with the SFP module used for backhaul. The fault is based on the SFP alarm and warning flags associated with temperature, supply voltage, TX bias current, and TX
output power. Warning flags indicate conditions outside the normally-guaranteed bounds but not necessarily causes of immediate link failures while alarm flags can indicate pending, possible, or both pending and possible
failure conditions. Certain warning flags might also be defined by the manufacturer as end-of-life indicators (such as for higher than expected bias currents in a constant power control loop). Warning flags are provided as an
optional function with SFPs. The exact thresholds for the alarms and warnings are defined by the individual SFP manufacturer. The backhaul via the SFP is in a degraded condition. The FZM BTS must be monitored for
proper operation.
Remedial action: Check the datasheet of the specific SFP used, whether the SFP warning flags are latching or non-latching. In case they are latching, reset the FZM or FZAP to determine whether the fault persists before
taking further actions. 1. Check whether the alarm is caused by exceeded temperature, internal supply voltage, or TX BIAS/TX output power. 2. If exceeded temperature causes the alarm, investigate if the current operating
conditions are outside the high or low temperature specifications for FZM or FZAP. If so, the warning clears when the temperature is within range. If it is inside the FZM- or FZAP-specified range, replace the SFP with an
SFP supporting the full FZM or FZAP temperature range. 3. If the internal supply voltage causes the alarm, check if the FZM or FZAP power input voltage is within the supported operating voltage range. If the FZM or FZAP
power input is within the supported operating voltage range, then replace the SFP. Check the specifications of the SFP and whether it is interoperable with the FZM or FZAP. If the fault persists because of the internal supply
voltage, replace the FZM or FZAP. If the FZM or FZAP power input voltage is outside the supported operating voltage range of the FZM or FZAP, correct the FZMor FZAP power input voltage. 4. If the TX BIAS/TX output
power causes the alarm, replace the SFP module.
Table 12320: FTM_SYNC_LOSS
Name: FTM_SYNC_LOSS (11573) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SYNC_LOSS FL16A
Package: racfl.FTM_SYNC_LOSS Implicitly cleared: true
Description: FTM_SYNC_LOSS Primary and secondary timing sources are lost. The LTE is utilizing the Global Navigation Satellite System (GNSS) source (if available) or in synchronization hold-over mode. The first and
second synchronization sources from the configured priority list are unavailable. On failure, the LTE switches automatically to the next clock source in the priority list. Probable cause: The transmission links selected for clock
source are faulty. The reason can be alarms on the interfaces (for example, LOS). Possible impact: The BTS is not synchronized to the network anymore.
Remedial action: Use the BTS Site Manager to check which interfaces have been configured as synchronization sources. 1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at
the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. Connect a loop cable and check whether the alarm disappears to verify
that the hardware of the interface unit works correctly.
Table 12321: FTM_TIMING_SOURCE_LOS

Name: FTM_TIMING_SOURCE_LOS (11574) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_TIMING_SOURCE_LOS FL16A
Package: racfl.FTM_TIMING_SOURCE_LOS Implicitly cleared: true
Description: FTM_TIMING_SOURCE_LOS One of the synchronization sources in the configured priority list is unavailable. This can be the primary or the secondary clock source. In the alarm: Protocol can be PDH, Timing
over Packet (ToP), and Synchronuous ethernet. Unit Number is optional: - For PDH and Synchronous Ethernet, Unit number is 0 or 1. - It is not present for Timing Over Packet(TOP). The interface value is optional: - For
PDH, the value range depends on the hardware unit type: 1-16. - For Synchonuous Ethernet, the value range is 1-3. - It is not present for Timing over Packet. The BTS may have to use a synchronization interface that has a
lower clock quality: if the primary clock source has been lost, the BTS switches automatically to the secondary clock source. If both the primary and the secondary clock sources are lost, the BTS switches to the internal
clock.
Remedial action: Use BTS Site Manager to check which interfaces have been configured as synchronization sources. For all interfaces, do as follows: 1. Check that the cables are connected to the correct connectors. 2.
Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. Connect a loop cable and check whether
the alarm disappears to verify that the hardware of the interface unit works correctly. Monitor the quality of the received clock.
Table 12322: GaPeerDown
Name: GaPeerDown (3303) Severity: major Release:

Package: lteggsn.GaPeerDown Implicitly cleared: true
Raised on class: lteggsn.GaPeer Default probable cause: EPSPeerDown
Description: The alarm is raised when the path management state of a Ga peer changes to a state other than Up.
Raising condition: ('Path Management State' NOT EQUAL 'Active')
Clearing condition: ('Path Management State' EQUAL 'Active')
Remedial action: A Ga reference point (peer) is operationally down for one of the following reasons: the underlying IP or physical interface is down, the far end peer is down or the underlying transport between this NE and
the peer NE is down. To resolve the issue ensure that the IP/physical interface is up, check that the far end peer is operational and check that the underlying transport network is up.
Table 12323: IncompleteConfiguration
Name: IncompleteConfiguration (1942) Severity: warning Release:

Type: operationalViolation Specific problem: Not Applicable FL16A
Package: netw.IncompleteConfiguration Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: incompleteConfig
Description: The alarm is raised when a pre-provisioned NE has no objects configured beneath it.
Raising condition: (('State' EQUAL 'Pre-provisioned') AND ('eNodeB Equipment' EQUAL '\"\"'))
Clearing condition: (('State' EQUAL 'Pre-provisioned') AND ('eNodeB Equipment' NOT EQUAL '\"\"'))
Remedial action: A configuration error has been made which must be corrected. The configuration of the pre-provisioned NE is incomplete. A work order was not associated with the pre-provisioned NE and as a
consequence the attempt to auto-configure the NE failed.
Table 12324: IPSEC_EMERGENCY_BYPASS_ACTIVE

Name: IPSEC_EMERGENCY_BYPASS_ACTIVE (11575) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IPSEC_EMERGENCY_BYPASS_ACTIVE FL16A
Package: racfl.IPSEC_EMERGENCY_BYPASS_ACTIVE Implicitly cleared: true
12/21/2019 Alarms
Description: IPSEC_EMERGENCY_BYPASS_ACTIVE The BTS has entered the IPsec emergency bypass active state, where configured IPsec policies are ignored and the entire traffic is sent unprotected. Configured
IPsec policies are ignored, and the entire traffic is sent unprotected.
Remedial action: Start IPsec emergency bypass by making the security gateway not reachable either by plugging out the cable or configuring wrong security gateway address.
Table 12325: IPSEC_EXPERT_MODE
Name: IPSEC_EXPERT_MODE (11576) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IPSEC_EXPERT_MODE FL16A
Package: racfl.IPSEC_EXPERT_MODE Implicitly cleared: true
Description: IPSEC_EXPERT_MODE BTS is in IPSec Expert Mode. This mode allows online tuning of IPSec related parameters for troubleshooting or workaround implementation via BTS Site Manager. It is meant for
R&D troubleshooting only. When the fault is active, normal IPSec configuration changes are not recommended. IPSec expert settings can be configured on BTS via BTS Site Manager only if IPSec Expert Mode is activated.
Remedial action: None.
Table 12326: IPsec_tunnel_switchover
Name: IPsec_tunnel_switchover (11579) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IPsec_tunnel_switchover FL16A
Package: racfl.IPsec_tunnel_switchover Implicitly cleared: true
Description: IPsec_tunnel_switchover This alarm will be triggered when at least one primary IPSec tunnel fails, and BTS has switched over to a secondary IPSec tunnel. As a result of failure in at least one primary IPSec
tunnel, BTS has automatically switched over to a secondary IPSec tunnel terminating on secondary security gateway. BTS traffic has switched over from the primary IPSec tunnel to the secondary (backup) IPSec tunnel
terminating on secondary security gateway. The fault is cancelled when BTS has switched back all secondary tunnels to the primary IPSec tunnels due to automatic switchback or manual switchback request from the
operator. This applies to the following state transitions: - Secondary_Active_Probing_Primary --> Primary_Active - Secondary_Active_No_Probing_Primary --> Primary_Active Note: The clear should also be sent when
IPSec backup tunnel feature or IPSec feature is disabled, or BTS is rebooted.
Remedial action: The operator can check the current remote tunnel endpoint parameter (ipSecBkupTunCurrRemoteEndpoint) on NetAct or BTS SM to verify the remote endpoint of a tunnel. The alarm will be cleared when
the tunnel is switched back to the primary remote tunnel endpoint.
Table 12327: IPV6_DUPLICATE_ADDRESS_DETECTED

Name: IPV6_DUPLICATE_ADDRESS_DETECTED (11577) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IPV6_DUPLICATE_ADDRESS_DETECTED FL16A
Package: racfl.IPV6_DUPLICATE_ADDRESS_DETECTED Implicitly cleared: true
Description: IPV6_DUPLICATE_ADDRESS_DETECTED During the IP address configuration of the BTS, it tests the directly-attached network whether other, already configured BTSs, on the network already uses the
same IP addresses on their network IP interfaces. The DAD detects those duplicated IP addresses and prohibits the operation of these IP addresses in the BTS. The warning shall contain the corresponding IP address. A
separate reporting shall be indicated for each DAD event. The remote peer to come online with the same IP address on the same subnet as local peer would just disable their network interface and give an error until the
situation is resolved by the administrator. This allows the local peer to continue functioning without disruption, but completely breaks IP base communications for the connected network.
Remedial action: 1.Check for duplicate IPv6 addresses configured in the BTS. 2.Change or delete the identified duplicate IPv6 addresses.
Table 12328: IP_TRAFFIC_CAPTURE_ONGOING
Name: IP_TRAFFIC_CAPTURE_ONGOING (11578) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IP_TRAFFIC_CAPTURE_ONGOING FL16A
Package: racfl.IP_TRAFFIC_CAPTURE_ONGOING Implicitly cleared: true
Description: IP_TRAFFIC_CAPTURE_ONGOING The base station is currently capturing an IP traffic towards a local port or into a file on the base station. If the traffic capturing is happening towards a local port, a port and
destination MAC address must be provided. Port values can be LMP or < HW MODULE NAME >-<PORT ID>. (For E.g: LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1) None
Remedial action: An IP Traffic Capturing session is ongoing and a base station traffic is captured to a local Ethernet interface or into a file on the base station.
Table 12329: LinkDown (equipment)
Name: LinkDown (12) Severity: major Release:

Package: equipment.LinkDown Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: portLinkProblem
Description: The alarm is raised when a port has no associated physical link or remote end point is operationally down.
Raising condition: (('compositeEquipmentState' EQUAL 'Link Down') OR ('compositeEquipmentState' EQUAL 'Oper Down'))
Clearing condition: (('compositeEquipmentState' NOT EQUAL 'Link Down') AND ('compositeEquipmentState' NOT EQUAL 'Oper Down'))
Remedial action: Please make sure that port has physical link and remote end point is operationally up.
Table 12330: Link_OAM_critical_link_event__alarm

12/21/2019 Alarms
Name: Link_OAM_critical_link_event__alarm (11581) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: Link OAM critical link event alarm FL16A
Package: racfl.Link_OAM_critical_link_event__alarm Implicitly cleared: true
Description: Link OAM critical link event alarm A Link OAM PDU containing a critical link event flag was received on the Ethernet interface. The alarm is raised with the first detection of the flag. The following critical link
events are possible: - Critical Event: either an Errored Symbol Period Event, an Errored Frame Event, an Errored Frame Period Event, or an Errored Frame Seconds Summary Event was detected. - Dying Gasp: either the
local or the remote peer has a fatal error and is about to restart. - Link Fault: the local peer has detected a physical link fault in receiving direction, for example, a LOS. Note: In case a received OAMPDU has more than one
critical event flag set, the following shall be reported in the alarm: Link Fault bit set |Dying Gasp bit set|Critical Event bit set| Reported x x x Link Fault x x Link Fault x x Link Fault x x Dying Gasp Always the latest received
critical link event shall be reported. The Ethernet interface is defective, or the remote peer is defective. Traffic might get lost. The alarm shall be cleared only if OAMPDUs with cleared flag have been received for a
configurable period of time (this assumes that the remote peer clears the flag when the error condition was solved). It shall also be cleared when the Link OAM functionality on the interface is being reset.
Remedial action: 1. Inspect details of the type of the critical event through online configuration management. 2. Check the Link OAM state information of the interface. 3. Check the cabling and network connections to the
far end. 4. Check the Ethernet interface configuration at the local and remote sides. 5. Insert a Link OAM loopback.
Table 12331: Link_OAM_link_lost_alarm
Name: Link_OAM_link_lost_alarm (11582) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: Link OAM link lost alarm FL16A
Package: racfl.Link_OAM_link_lost_alarm Implicitly cleared: true
Description: Link OAM link lost alarm On an interface for which the Link OAM functionality was switched on, no Link OAM PDUs were received during the period specified in configuration parameter 'linkLostTime' (2-10
seconds, step 1 second). The Ethernet interface might be out of order, or the remote peer might be out of order. Traffic might get lost. The alarm is cleared automatically if link OAM PDUs are received continuously again
during the same period specified in the parameter 'linkLostTime' (2-10 seconds, step 1 second).
Remedial action: 1. Check the cabling and network connections to the far end. 2. Check the Link OAM event information and the Link OAM state information. 3. Check the Ethernet interface configuration at the local and
remote sides. 4. Insert a Link OAM loopback.
Table 12332: Link_OAM_loopback_alarm
Name: Link_OAM_loopback_alarm (11583) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: Link OAM loopback alarm FL16A
Package: racfl.Link_OAM_loopback_alarm Implicitly cleared: true
Description: Link OAM loopback alarm A loopback is requested for an Ethernet interface either locally at the BTS, or the Link OAM client of the BTS is set into loopback mode by the remote Link OAM peer. Normal traffic is
interrupted. Only loopback OAM frames are transmitted and received over the interface. If the test frame generator is switched on, test frames are transmitted. For a loopback inserted by the local peer, the alarm is
cancelled automatically after the loopback has ended by expiration of configured loopback time. For a loopback inserted at the remote peer, the alarm is cancelled after detecting loopback end from the remote peer.
Remedial action: None
Table 12333: LMP_CARRIER_DETECTED

Name: LMP_CARRIER_DETECTED (11580) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: LMP_CARRIER_DETECTED FL16A
Package: racfl.LMP_CARRIER_DETECTED Implicitly cleared: true
Description: LMP_CARRIER_DETECTED The Flexi Zone Micro BTS or Flexi Zone Access Point detects, using carrier state, that someone is locally connected to the small cell using LMP port. Update audit logs.
Remedial action: 1. Determine if this event is expected: whether a qualified personnel is utilizing LMP ethernet port cable connection for diagnostic purposes. 2. Otherwise, it shall be treated as a security warning.
Table 12334: MobileConnectorDown
Name: MobileConnectorDown (1064) Severity: minor Release:

Package: lteservice.MobileConnectorDown Implicitly cleared: true
Raised on class: lteservice.MobileServiceConnector Default probable cause: EpcDown
Description: The alarm is raised when the 5620 SAM no longer manages the EPS path instance of this mobile service site. As a result, the service must be regenerated.
Raising condition: ('EPS Path' EQUAL '\"\"')
Clearing condition: ('EPS Path' NOT EQUAL '\"\"')
Remedial action: The underlying transport network has gone down resulting in the deletion of a mobile service connector (EPS path). Correct the issue with the transport network and regenerate the mobile service
connector by clicking on the re-calculate button on the mobile service properties form.
Table 12335: NeManagementAndTrapManagementMismatch
Name: NeManagementAndTrapManagementMismatch (1079) Severity: warning Release:

Package: netw.NeManagementAndTrapManagementMismatch Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: neManagementChange
Description: This user-defined alarm is raised when the NE configuration is one of the following: - The Active Management IP is set to Out Of Band, and the Primary Route Preference is set to In Band. - The Active
Management IP is set to In Band, and the Primary Route Preference is set to Out of Band.
12/21/2019 Alarms
Raising condition: ((('Active Management IP' EQUAL 'In Band') AND (('Management IP Selection' EQUAL 'In Band Preferred') OR ('Management IP Selection' EQUAL 'In Band Only')) AND ('Primary Route Preference'
EQUAL 'Out Of Band') AND ('Secondary Route Preference' EQUAL 'In Band')) OR (('Active Management IP' EQUAL 'Out Of Band') AND (('Management IP Selection' EQUAL 'Out Of Band Preferred') OR ('Management IP
Selection' EQUAL 'Out Of Band Only')) AND ('Primary Route Preference' EQUAL 'In Band') AND ('Secondary Route Preference' EQUAL 'Out Of Band')))
Clearing condition: ((('Active Management IP' EQUAL 'In Band') AND (('Management IP Selection' EQUAL 'In Band Preferred') OR ('Management IP Selection' EQUAL 'In Band Only')) AND ('Primary Route Preference'
EQUAL 'In Band')) OR (('Active Management IP' EQUAL 'Out Of Band') AND (('Management IP Selection' EQUAL 'Out Of Band Preferred') OR ('Management IP Selection' EQUAL 'Out Of Band Only')) AND ('Primary Route
Preference' EQUAL 'Out Of Band')))
Remedial action: A configuration error has been made which must be corrected. The parameters described in the description for this alarm must match.
Table 12336: NEW_CONFIG_REJECTED

Name: NEW_CONFIG_REJECTED (11584) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: NEW_CONFIG_REJECTED FL16A
Package: racfl.NEW_CONFIG_REJECTED Implicitly cleared: true
Description: NEW_CONFIG_REJECTED This alarm is triggered once the new configuration file is rejected and the M-Plane connection is established with fallback configuration as a result of M-plane recovery action. It will
be visible until next site reset. The active base station configuration is not the same as requested in the configuration change.
Remedial action: None
Table 12337: NodeDatabaseFallbackDetected
Name: NodeDatabaseFallbackDetected (2923) Severity: major Release:

Package: netw.NodeDatabaseFallbackDetected Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: nodeDatabaseFallback
Description: The alarm is raised when a configuration fallback is detected on the node and comes back up with a previous configuration. To correct this situation it might be necessary to reconfigure the node, or perform full
resync its database with the 'fallback' configuration returned by the node.
Raising condition: ('State' EQUAL 'Node Configuration Fallback')
Clearing condition: ('State' EQUAL 'Managed')
Remedial action: the NE has come back to a previous configuration. Perform a manual Full Resync or a Reconfigure of the NE
Table 12338: NodeDatabaseMisalignmentDetected
Name: NodeDatabaseMisalignmentDetected (2924) Severity: major Release:

Package: netw.NodeDatabaseMisalignmentDetected Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: nodeDatabaseMisalignment
Description: The alarm is raised when a configuration misalignment has been detected on the node and comes back up with an unexpected configuration (configuration change triggered by external tool) To correct this
situation it might be necessary to reconfigure the node with the 5620 SAM's old configuration or accept the new configuration received from the node.
Raising condition: ('State' EQUAL 'Node Configuration Misalignment')
Clearing condition: ('State' EQUAL 'Managed')
Remedial action: the NE configuration is misaligned. Perform a resync in order to update SAM configuration according to the NE.
Table 12339: NodeSuspended
Name: NodeSuspended (5123) Severity: critical Release:

Package: netw.NodeSuspended Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: NodeSuspend
Description: The alarm is raised when the 5620 SAM detects an NE moved to suspend state as per user request.
Raising condition: ('SNMP Reachability' EQUAL 'Suspended')
Clearing condition: ('SNMP Reachability' NOT EQUAL 'Suspended')
Remedial action: This alarm is raised when user suspends the network element.The alarm will be cleared when the network element is managed back.
Table 12340: NO_CERTIFICATE
Name: NO_CERTIFICATE (11585) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: NO_CERTIFICATE FL16A
Package: racfl.NO_CERTIFICATE Implicitly cleared: true
Description: NO_CERTIFICATE A requested certificate could not be retrieved from the certificate authority (CA). A requested certificate could not be renewed from the certificate authority (CA). A requested certificate could
not be retrieved as the number of certificates received from repository server (RA) or certificate authority (CA) are more than expected. A requested certificate could not be stored in the remaining storage available on the
BTS. Operator cleanup (e.g. via site manager or NetAct) of old, unused trust chains may be required. The requested service is not available.
12/21/2019 Alarms
Remedial action: Provide the certificate.
Table 12341: NTP_SERVER_UNREACHABLE
Name: NTP_SERVER_UNREACHABLE (11586) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: NTP_SERVER_UNREACHABLE FL16A
Package: racfl.NTP_SERVER_UNREACHABLE Implicitly cleared: true
Description: NTP_SERVER_UNREACHABLE Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD: A BTS reports this alarm for each instance of the configured NTP
server if that particular NTP server is not accessible or cannot be used after waiting for a threshold timeout defined by the INTP::ntpAlarmThreshold configuration parameter in PDDB. The raised alarm displays the IP
address of the NTP server that is not reachable in the additional information field 'alarmNotif::argumentInfo'. Note : For each NTP server instance, timers are started separately and a separate alarm is raised. This threshold
time is not used to clear the alarm. Flexi Zone: Flexi Zone Access Point reports this alarm for each instance of the configured NTP server if that particular NTP server is not accessible or cannot be used after waiting for a
threshold time-out defined by the configuration parameter INTP::ntpAlarmThreshold in PDDB. The raised alarm displays the IP address of the NTP server that is not reachable in the additional information field
'alarmNotif::argumentInfo'. Note : For each NTS server instance, timers are started separately and a separate alarm is raised. This threshold time is not used to clear the alarm. The BTS might lose time synchronization if
there are problems with multiple NTP servers, or the BTS will have no time synchronization at all if all NTP servers are down. Flexi Zone: Flexi Zone Access Point might lose time synchronization if there are problems with
multiple NTP servers, or the BTS will have no time synchronization at all if all NTP servers are down.
Remedial action: 1. Check the connectivity to the NTP server. 2. Check the NTP server configuration at the BTS. 3. Check the configured threshold value for the NTP server.
Table 12342: PartialResyncProblem

Name: PartialResyncProblem (4401) Severity: warning Release:

Package: netw.PartialResyncProblem Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: partialResyncProblem
Description: The alarm is raised when a partial resync on an NE fails. For example, when resyncing only some MIB entries as opposed to a full resync. The periodic reachability test (sysUpTime) is not considered a partial
resync, neither is a full resync. However, a PartialResyncProblem alarm can only be reset by a FullResync.
Raising condition: ('partialResyncStatus' EQUAL 'Partial Resync Failed')
Clearing condition: ('partialResyncStatus' EQUAL 'Partial Resync Done')
Remedial action: Informational - if the alarm persists or is occurring frequently then investigation is required to understand a) why the underlying transport network is unreliable or b) why the NE is too busy to respond to
5620 SAM or c) has SNMP been disabled on the NE.
Table 12343: PartialVPRNEncryption
Name: PartialVPRNEncryption (8992) Severity: major Release:

Package: nge.PartialVPRNEncryption Implicitly cleared: true
Raised on class: nge.VprnEncryptService Default probable cause: ConfigMismatch
Description: The alarm is raised when one or more sites are not encryption enabled in a VPRN service.
Raising condition: (('VPRN Service Encryption Status' EQUAL 'Partial'))
Clearing condition: (('VPRN Service Encryption Status' NOT EQUAL 'Partial'))
Remedial action: This site is newly added to the VPRN service, Perform the encrypt operation on the KeyGroup to clear the alarm.
Table 12344: PersistentIndexParametersMisconfigured
Name: PersistentIndexParametersMisconfigured (173) Severity: major Release:

Package: netw.PersistentIndexParametersMisconfigured Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: persistentIndexConfigurationMismatch
Description: The alarm is raised when persistence is set to Off in the NE BOF.
Raising condition: (('Persistent SNMP Indices' EQUAL 'False') OR (('hasRedundantProcessorCards' EQUAL 'true') AND ('Redundant Synchronization Mode' EQUAL 'None')))
Clearing condition: (('Persistent SNMP Indices' EQUAL 'True') AND (('hasRedundantProcessorCards' EQUAL 'false') OR ('Redundant Synchronization Mode' NOT EQUAL 'None')))
Remedial action: A configuration error has occurred that must be corrected. Use the CLI on the NE to enable persistency in the BOF. The discovery process will complete on the next discovery scan. A re-scan can be
triggered immediately for the NE from within the discovery manager
Table 12345: PLR_THRESHOLD_CROSSED

Name: PLR_THRESHOLD_CROSSED (11587) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: PLR_THRESHOLD_CROSSED FL16A
Package: racfl.PLR_THRESHOLD_CROSSED Implicitly cleared: true
Description: PLR_THRESHOLD_CROSSED The alarm is raised if the packet loss ratio equals or exceeds the configured threshold value during the current observation interval of 15 minutes. This alarm is an indication
that the backhaul capacity for traffic with same profile as this TWAMP session (DSCP value, packet size), may be much too small, because some of the measurement packets seem to have been thrown away. The TWAMP
measurement packets are lost because of degraded traffic throughput.
12/21/2019 Alarms
Remedial action: 1. Check the backhaul usage and if other applications with the same or higher PHB may compete against this TWAMP session about the capacity. An increase in the priority of TWAMP session or of the
backhaul capacity may clear the alarm. 2. Check if destination is unreachable by IP connectivity test. Send an ICMP echo request (ping) to the UDP port of the TWAMP reflector at the destination IP.If ICMP echo reply
indicates that the destination is unreachable but you have access to TWAMP reflector, you can check its status. If the status is disabled or down try to activate it again and check if alarm disappears. 3. Check configured
PLR threshold. Setting PLR to 0% should be avoided, because every lost measurement packet will trigger the alarm and it cannot be cleared again (PLR>="0)."
Table 12346: PollerProblem
Name: PollerProblem (31) Severity: warning Release:

Package: netw.PollerProblem Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: resyncFailed
Description: The alarm is raised when the 5620 SAM is unable to poll a network object, for example, because of intermittent or no IP connectivity to an NE, incorrect SNMP or Netconf security parameters, or disabled
SNMP on the NE.
Raising condition: ('Resync Status' EQUAL 'Full Resync Failed')
Clearing condition: ('Resync Status' EQUAL 'Full Resync Done')
5620 SAM or c) has SNMP been disabled on the NE. Once the issue has been resolved SAM will automatically re-attempt.
Table 12347: PrimaryImageBootFailure
Name: PrimaryImageBootFailure (191) Severity: warning Release:

Package: sw.PrimaryImageBootFailure Implicitly cleared: true
Raised on class: sw.CardSoftware Default probable cause: bootOptionFileMisconfigured
Description: The alarm is raised when the primary software image specified in an NE BOF is unusable.
Raising condition: (('imageSource' NOT EQUAL 'Primary') AND ('imageSource' NOT EQUAL 'Unknown'))
Clearing condition: (('imageSource' EQUAL 'Primary') OR ('imageSource' EQUAL 'Unknown'))
Remedial action: The SW image on the NE may have been inadvertently corrupted. Download a new copy of the SW image to the NE. If the problem persists contact your Nokia support representative for assistance.
Table 12348: RadiusOperStatusDown

Name: RadiusOperStatusDown (3692) Severity: critical Release:

Type: radiusOperStatusDownAlarm Specific problem: Not Applicable FL16A
Package: netw.RadiusOperStatusDown Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: radiusOperationStatusDown
Description: The alarm is raised when all RADIUS servers have gone down.
Raising condition: ('Global RADIUS Operational State' EQUAL 'Down')
Clearing condition: ('Global RADIUS Operational State' EQUAL 'Up')
Remedial action: Verify the RADIUS server is properly configured and radius server state is up.Check the connectivity between SAM server and radius server configured on the Network element.
Table 12349: ReachabilityProblem
Name: ReachabilityProblem (243) Severity: major Release:

Package: netw.ReachabilityProblem Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: ReachabilityTestFailed
Description: The alarm is raised when a mediation poll of the SysUpTimeAlarm object on an NE fails, for example, because of network congestion or because the NE is too busy to respond. The probable cause is an
unreachable NE Mediation agent on the NE. The polling interval depends on the NE type and is configurable in nms-server.xml. By default, the 5620 SAM polls a managed NE every four minutes. If a poll fails, the alarm is
raised. The alarm clears when the 5620 SAM receives a response from the NE, and the 5620 SAM GUI icon that represents the NE turns from red to green.
Raising condition: ('SNMP Reachability' EQUAL 'Down')
Table 12350: ReconfigFailure
Name: ReconfigFailure (1949) Severity: critical Release:

Package: netw.ReconfigFailure Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: failedReconfig
Description: This alarm is raised when the reconfig action failed.
Raising condition: ('State' EQUAL 'Failed')
Clearing condition: ('State' NOT EQUAL 'Failed')
12/21/2019 Alarms
Remedial action: Verify that the object is configured as expected.
Table 12351: RTT_THRESHOLD_CROSSED

Name: RTT_THRESHOLD_CROSSED (11588) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: RTT_THRESHOLD_CROSSED FL16A
Package: racfl.RTT_THRESHOLD_CROSSED Implicitly cleared: true
Description: RTT_THRESHOLD_CROSSED The RTT threshold alarm is sent in case the average value of the RTT exceeds or equals the configured threshold for a 1-min period. This alarm is an indication that the
backhaul capacity for traffic with the same profile as this TWAMP session (DSCP value, packet size) may be too small, because the measurement packets are scheduled later than before.
Remedial action: 1. Check the backhaul usage and if other applications with the same or higher PHB may compete against this TWAMP session about the capacity. An increase in the priority of TWAMP session or of the
backhaul capacity may clear the alarm. 2. Check the last measured RTT values of this TWAMP session and verify that the configured RTT threshold value is not too close to average measured RTT values, so that this
alarm could be result of sporadic mis-measurement.
Table 12352: SaveConfigFailed
Name: SaveConfigFailed (105) Severity: major Release:

Package: sw.SaveConfigFailed Implicitly cleared: true
Raised on class: sw.BackupRestoreManager Default probable cause: fileAccessError
Description: The alarm is raised when the admin save command on an NE fails.
Raising condition: ('Config Save State' EQUAL 'Failure')
Clearing condition: ('Config Save State' EQUAL 'Success')
Remedial action: Attempt the admin save command a second time. If the problem persists please contact your Nokia support representative for assistance.
Table 12353: ScheduledPollerProblem
Name: ScheduledPollerProblem (4386) Severity: warning Release:

Package: netw.ScheduledPollerProblem Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: scheduledResyncFailed
Description: The alarm is raised when the 5620 SAM is unable to poll a network object, for example, because of intermittent or no IP connectivity to an NE, incorrect SNMP or Netconf security parameters, or disabled
SNMP on the NE.
Raising condition: ('Scheduled Resync Status' EQUAL 'Scheduled Resync Failed')
Clearing condition: ('Scheduled Resync Status' EQUAL 'Scheduled Resync Done')
Table 12354: SFP_HW_Failure

Name: SFP_HW_Failure (11589) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SFP HW Failure FL16A
Package: racfl.SFP_HW_Failure Implicitly cleared: true
Description: SFP HW Failure A malfunctioning of the SFP transceiver was detected. The SFP has reported a transmission fault condition and has disabled the laser transmitter. The SFP is not operational. The BTS checks
if the HW unit is working correctly.
Remedial action: Replace the faulty SFP. Note that only the SFP might be faulty, not necessarily the entire hardware unit.
Table 12355: SSH_ENABLED
Name: SSH_ENABLED (11590) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSH_ENABLED FL16A
Package: racfl.SSH_ENABLED Implicitly cleared: true
Description: SSH_ENABLED The Flexi Zone Micro BTS or Flexi Zone Access Point detects that the SSH access to the site is enabled. Note: The SSH access to the site is disabled by default. To mitigate the risk in field
scenarios, SSH should only be enabled for limited periods time on an as-needed basis. Update audit logs.
Remedial action: 1. Determine if this event is expected. Note: The SSH access to the site is disabled by the default. SHH should only be enabled for limited periods time on an as-needed basis.
Table 12356: SSM_POORQUALITY
Name: SSM_POORQUALITY (11591) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSM_POORQUALITY FL16A
Package: racfl.SSM_POORQUALITY Implicitly cleared: true
12/21/2019 Alarms
Description: SSM_POORQUALITY This alarm is raised when the received SSM indicates lower clock quality (for example, 'do not use' or 'EEC') than required. Note: The interface numbering shall be similar to ETHLK. E.g:
DN:SYNC-1/STPG-1/STPU-1-4 for unit 1,interface 4. Flexi Zone Micro FDD, Flexi Zone Micro TDD: SyncE is no longer a working synchronization source. The alarm is cleared if one SSM is received again showing
sufficient quality level.
Remedial action: Flexi Zone Micro FDD, AirScale BTS FDD/TDD, Flexi Zone Micro TDD, Flexi Zone: 1. Confirm that SyncE is desired as a synchronization source. 2. Confirm that eNB configuration settings for
ssmEnabled are correct. 3. Troubleshoot with Backhaul provider on the reason SSM errors.
Table 12357: SSM_TIMEOUT

Name: SSM_TIMEOUT (11592) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSM_TIMEOUT FL16A
Package: racfl.SSM_TIMEOUT Implicitly cleared: true
Description: SSM_TIMEOUT This alarm is raised if the incoming SSM is not received for a certain time period (configured through the parameter 'ssmTimeout'). Note: The interface numbering is similar to ETHLK.
Example: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1, interface 4 SyncE is no longer a working synchronization source.
Remedial action: 1. Confirm that SyncE is desired as a synchronization source. 2. Confirm that configuration settings for ssmEnabled are correct. 3. Troubleshoot with backhaul provider about the reason for SSM errors.
Table 12358: StatsRetrieveFailed
Name: StatsRetrieveFailed (244) Severity: major Release:

Package: sw.StatsRetrieveFailed Implicitly cleared: false
Raised on class: sw.AccountingStatsRetrievalManager Default probable cause: fileTransferFailure
Description: The alarm is raised when the 5620 SAM main or auxiliary server cannot transfer an accounting file from an NE.
Raising condition: (('Stats Retrieval State' NOT EQUAL 'Success') AND ('Stats Retrieval State' NOT EQUAL 'Not Attempted'))
Remedial action: Informational - if the alarm persists or is occurring frequently then investigation is required to understand a) why the underlying transport network is unreliable or b) why the NE is too busy or otherwise
cannot respond to the 5620 SAM main or auxiliary server.
Table 12359: SubscriberSystemNextHopUsageHigh
Name: SubscriberSystemNextHopUsageHigh (5157) Severity: minor Release:

Type: thresholdCrossed Specific problem: Not Applicable FL16A
Package: netw.SubscriberSystemNextHopUsageHigh Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: resourceFull
Description: The alarm is raised when the IP next-hop usage by subscriber managed routes reaches its high watermark, cleared when it reaches its low watermark again; the watermarks are derived from the limit specified
with the property subSysNextHopLimit.
Raising condition: ('IP Next Hop Usage High' EQUAL 'true')
Clearing condition: ('IP Next Hop Usage High' EQUAL 'false')
Remedial action: The alarm is raised when the IP next-hop usage by subscriber managed routes reaches its high watermark, cleared when it reaches its low watermark again; the watermarks are derived from the limit
specified with the property subSysNextHopLimit.There is no immediate effect, but when the usage actually hits the limit, new hosts will not get their managed routes.
Table 12360: TOP_MASTER_UNUSABLE

Name: TOP_MASTER_UNUSABLE (11593) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: TOP_MASTER_UNUSABLE FL16A
Package: racfl.TOP_MASTER_UNUSABLE Implicitly cleared: true
Description: TOP_MASTER_UNUSABLE The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP: - The eNB does not receive a reply from ToP Master
within a certain time (5 sec) upon sending a sync request message. - The eNB receives from ToP Master granted message rates (sync message rate, delay message rate), that do not match the requested rate by the eNB.
There might be another synchronization source available at eNB. In that case, the BTS switches automatically to the other clock source. If no other synchronization source is available at eNB, it runs in hold-over mode.
Please refer to status of '3080: EFaultId_BtsReferenceClockMissing'.
Remedial action: 1. Check the cable connectivity. 2. Check the TOP configuration.
Table 12361: TRANSPORT_MODULE_MISSING
Name: TRANSPORT_MODULE_MISSING (11594) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: TRANSPORT_MODULE_MISSING FL16A
Package: racfl.TRANSPORT_MODULE_MISSING Implicitly cleared: true
Description: TRANSPORT_MODULE_MISSING A unit is missing. The slot has been configured to hold a unit, but the plug-in unit is not physically present in the slot. Probable causes: - The unit has been configured but
not detected. - The unit is broken and therefore not detected. - The unit has been configured but some other unit is detected. NOTE: The unit variable should be replaced by appropriate HW names configured
(unitTypeConfigured) during runtime reporting. Possible impacts: - No calls are possible for the connections over this unit. - Remote management access to other network elements in the RAN is lost.
Remedial action: Replacing a faulty hardware: 1. Plug in again the expected transport unit that is referenced in the alarm text. 2. In case there is a unit present in the slot, remove it from the slot and plug it back in. If the
unit is still not recognized and the alarm remains, replace the faulty unit with a new one. Decommissioning a previously commissioned hardware: 1. Recommission to remove the hardware unit referenced in the alarm text.
NOTE: Before recommissioning, the hardware unit must not be present in the slot.
Table 12362: TrapDestinationMisconfigured
12/21/2019 Alarms
Name: TrapDestinationMisconfigured (33) Severity: major

Type: configurationAlarm Specific problem: Not Applicable Release:
Package: netw.TrapDestinationMisconfigured Implicitly cleared: true FL16A
Raised on class: netw.NetworkElement Default probable cause: trapDestinationMisconfigured
Applicable probable causes:
trapDestinationMisconfigured
duplicateTrapLogId
Description: The alarm is raised when the 5620 SAM cannot be added to the NE's SNMP trap destinations.
Raising condition: ('isTrapDestinationMisconfigured' EQUAL 'true')
Clearing condition: ('isTrapDestinationMisconfigured' EQUAL 'false')
Remedial action: A configuration error has been made which must be corrected. The SNMP trap destination on the NE must be configured to the IP address of the SAM server.
Table 12363: TrapReceivingFailure

Name: TrapReceivingFailure (1083) Severity: major Release:

Type: communications Specific problem: Not Applicable FL16A
Package: netw.TrapReceivingFailure Implicitly cleared: false
Raised on class: netw.NetworkElement Default probable cause: trapsWillNotBeSent
Description: This user-defined alarm is raised when the NE is unable to send traps because the NE configuration is one of the following: - The Management IP Selection is set to Out Of Band Only, the Primary Route
Preference is set to In Band, and the Secondary Route Preference is set to None. - The Management IP Selection is set to In Band Only, the Primary Route Preference is set to Out Of Band, and the Secondary Route
Preference is set to None.
Raising condition: ((('Active Management IP' EQUAL 'In Band') AND ('Management IP Selection' EQUAL 'In Band Only') AND ('Primary Route Preference' EQUAL 'Out Of Band') AND ('Secondary Route Preference'
EQUAL 'None')) OR (('Active Management IP' EQUAL 'Out Of Band') AND ('Management IP Selection' EQUAL 'Out Of Band Only') AND ('Primary Route Preference' EQUAL 'In Band') AND ('Secondary Route Preference'
EQUAL 'None')) OR (('Active Management IP' EQUAL 'Out Of Band') AND ('Management IP Selection' EQUAL 'In Band Preferred') AND ('Primary Route Preference' EQUAL 'In Band') AND ('Secondary Route Preference'
EQUAL 'None')) OR (('Active Management IP' EQUAL 'In Band') AND ('Management IP Selection' EQUAL 'Out Of Band Preferred') AND ('Primary Route Preference' EQUAL 'Out Of Band') AND ('Secondary Route
Preference' EQUAL 'None')))
Clearing condition: ((('Active Management IP' EQUAL 'In Band') AND ('Management IP Selection' EQUAL 'In Band Only') AND (('Primary Route Preference' EQUAL 'In Band') OR ('Secondary Route Preference' EQUAL 'In
Band'))) OR (('Active Management IP' EQUAL 'Out Of Band') AND ('Management IP Selection' EQUAL 'Out Of Band Only') AND (('Primary Route Preference' EQUAL 'Out Of Band') OR ('Secondary Route Preference'
EQUAL 'Out Of Band'))) OR (('Active Management IP' EQUAL 'Out Of Band') AND ('Management IP Selection' EQUAL 'In Band Preferred') AND (('Primary Route Preference' EQUAL 'Out Of Band') OR ('Secondary Route
Preference' EQUAL 'Out Of Band'))) OR (('Active Management IP' EQUAL 'In Band') AND ('Management IP Selection' EQUAL 'In Band Preferred') AND (('Primary Route Preference' EQUAL 'In Band') OR ('Secondary
Route Preference' EQUAL 'In Band'))) OR (('Active Management IP' EQUAL 'In Band') AND ('Management IP Selection' EQUAL 'Out Of Band Preferred') AND (('Primary Route Preference' EQUAL 'In Band') OR
('Secondary Route Preference' EQUAL 'In Band'))) OR (('Active Management IP' EQUAL 'Out Of Band') AND ('Management IP Selection' EQUAL 'Out Of Band Preferred') AND (('Primary Route Preference' EQUAL 'Out Of
Band') OR ('Secondary Route Preference' EQUAL 'Out Of Band'))))
Remedial action: A configuration error has been made which must be corrected. The configuration error must be corrected per the discussion in the description for this alarm.
Table 12364: TrapRoutePreferenceRedundancyMissing

Name: TrapRoutePreferenceRedundancyMissing (1084) Severity: warning Release:

Type: communications Specific problem: Not Applicable FL16A
Package: netw.TrapRoutePreferenceRedundancyMissing Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: trapsRedundancyMissing
Description: The user-defined alarm is raised when NE management redundancy is configured without trap route preference redundancy.
Raising condition: ((('Management IP Selection' EQUAL 'In Band Preferred') AND ('Active Management IP' EQUAL 'In Band') AND ('Primary Route Preference' EQUAL 'In Band') AND ('Secondary Route Preference'
EQUAL 'None')) OR (('Management IP Selection' EQUAL 'Out Of Band Preferred') AND ('Active Management IP' EQUAL 'Out Of Band') AND ('Primary Route Preference' EQUAL 'Out Of Band') AND ('Secondary Route
Preference' EQUAL 'None')))
Clearing condition: ((('Management IP Selection' EQUAL 'In Band Preferred') AND ('Active Management IP' EQUAL 'In Band') AND ('Secondary Route Preference' NOT EQUAL 'None')) OR (('Management IP Selection'
EQUAL 'Out Of Band Preferred') AND ('Active Management IP' EQUAL 'Out Of Band') AND ('Secondary Route Preference' NOT EQUAL 'None')))
Remedial action: A configuration error has been made which must be corrected. The IP address of the standby SAM server must be configured on the NE in question.
Table 12365: TRUST_ANCHOR_EXPIRING
Name: TRUST_ANCHOR_EXPIRING (11595) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: TRUST_ANCHOR_EXPIRING FL16A
Package: racfl.TRUST_ANCHOR_EXPIRING Implicitly cleared: true
Description: TRUST_ANCHOR_EXPIRING The network element stores trust anchors for its own trust chain and for peers. When its own or any trust anchors are about to expire or are expired, this alarm is sent. No
immediate effect. If at all certificate expires without any action from operator due to this fault, secure communication to remote peers may fail.
Remedial action: Update the trust anchors.
Table 12366: UNSUPPORTED_HW_DEVICE
Name: UNSUPPORTED_HW_DEVICE (11597) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: UNSUPPORTED_HW_DEVICE FL16A
Package: racfl.UNSUPPORTED_HW_DEVICE Implicitly cleared: true
Description: UNSUPPORTED_HW_DEVICE The SW does not support the detected HW unit type. Probable causes: - The SW version of the system module is too old. - The supported HW variant is not present in the
system module. The possible impact is that no calls are possible for the connections over this unit.
12/21/2019 Alarms
Remedial action: SW upgrading: Upgrade the FSM SW release to the latest version that includes the support for the new external transport device variant. Unit variant replacement: Replace the unsupported device variant
to another one that supports the currently running SW release.
Table 12367: UpgradedBuildVersionMismatch

Name: UpgradedBuildVersionMismatch (174) Severity: warning Release:

Package: netw.UpgradedBuildVersionMismatch Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: upgradedImageNotBooted
Description: The alarm is raised when the software version that an NE reports after a software upgrade does not match the version of the software used for the upgrade.
Raising condition: ('upgradedBuildVersionMismatch' EQUAL 'true')
Clearing condition: ('upgradedBuildVersionMismatch' EQUAL 'false')
Remedial action: Informational - if the alarm persists please contact your Nokia support representative for assistance
Table 12368: upgradedCardAlarm
Name: upgradedCardAlarm (255) Severity: warning Release:

Type: softwareAlarm Specific problem: Not Applicable FL16A
Package: equipment.upgradedCardAlarm Implicitly cleared: true
Raised on class: equipment.Card Default probable cause: upgradedCard
Description: The alarm is raised when the standby CPM is rebooted and operational after a software upgrade. A device resets an IOM automatically after 120 minutes if the IOM is not manually reset after a CPM upgrade.
Raising condition: ('operationalState' EQUAL 'Upgrade')
Clearing condition: ('operationalState' EQUAL 'Up')
Table 12369: UplinkDown
Name: UplinkDown (11062) Severity: major Release:

Type: virtualSwitchAlarm Specific problem: Not Applicable FL16A
Package: dctr.UplinkDown Implicitly cleared: true
Raised on class: dctr.AbstractUplink Default probable cause: ConnectionsAllDown
Description: The alarm is raised when all connections of the Uplink are down.
Raising condition: (('uplinkState' EQUAL '2'))
Clearing condition: (('uplinkState' NOT EQUAL '2'))
Remedial action: This alarm is raised when all connections associated to the uplink lost connectivity.
Table 12370: UplinkPartiallyDown

Name: UplinkPartiallyDown (11063) Severity: major Release:

Type: virtualSwitchAlarm Specific problem: Not Applicable FL16A
Package: dctr.UplinkPartiallyDown Implicitly cleared: true
Raised on class: dctr.AbstractUplink Default probable cause: ConnectionsDown
Description: The alarm is raised when some connections of the Uplink are down.
Raising condition: (('uplinkState' EQUAL '3'))
Clearing condition: (('uplinkState' NOT EQUAL '3'))
Remedial action: This alarm is raised when a connection of the uplink lost connectivity but at least one connection remains connected.
Table 12371: VENDOR_CERTIFICATE_EXPIRING
Name: VENDOR_CERTIFICATE_EXPIRING (11598) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: VENDOR_CERTIFICATE_EXPIRING FL16A
Package: racfl.VENDOR_CERTIFICATE_EXPIRING Implicitly cleared: true
Description: VENDOR_CERTIFICATE_EXPIRING The BTS raises this alarm when the vendor BTS certificate is about to expire. The period of advance notification is configurable, as well as the CA certificate expiry. 1 day
... 4999 days with default 90 days Note: For Flexi Zone Controller, the period of advance notification is a non-configurable 90 days. As long as BTS operator certificate is available and active on BTS, there is no impact.
However, if BTS is reset to factory default, since vendor certificate is expired, the BTS may fail to derive a new BTS operator certificate.
Remedial action: Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Access Point, Flexi Zone Controller: Check the vendor BTS certificate expiry date.
Replace the expired vendor BTS certificate if possible (for example, an older BTS like FSMr2). Otherwise, contact Nokia to investigate the need for hardware replacement or return to resolve the possible end-of-life
indication implied by the expired Nokia vendor certificate. For most BTS types (including at least FSMr3, Airscale, Flexi Zone Controller, FZAP, and Flexi Micro/Pico), a new vendor certificate can only be installed in the
Nokia factory.
12/21/2019 Alarms
Table 12372: VersionConfigRestoreFailed
Name: VersionConfigRestoreFailed (536) Severity: major Release:

Package: sw.VersionConfigRestoreFailed Implicitly cleared: true
Raised on class: sw.BackupRestoreManager Default probable cause: versionMismatch
Description: The alarm is raised when the restore procedure on an NE fails because of a mismatch between the backup file set version and the NE software version.
Raising condition: ('lastNmsVersionRestoreState' EQUAL 'Failure')
Clearing condition: ('lastNmsVersionRestoreState' EQUAL 'Success')
Remedial action: The backup files being restored do not match with the version of node software release. Download a new copy of the SW image to the NE. If the problem persists contact your Nokia support
representative for assistance.
Table 12373: WIFI_CARD_INVALID_TYPE
Name: WIFI_CARD_INVALID_TYPE (11599) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: WIFI_CARD_INVALID_TYPE FL16A
Package: racfl.WIFI_CARD_INVALID_TYPE Implicitly cleared: true
Description: WIFI_CARD_INVALID_TYPE The internal Wi-Fi module type is invalid. The internal Wi-Fi module might not be operational.
Remedial action: 1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported. 2. Replace the Flexi Zone Micro BTS.
Table 12374: WIFI_CARD_NOT_PRESENT

Name: WIFI_CARD_NOT_PRESENT (11600) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: WIFI_CARD_NOT_PRESENT FL16A
Package: racfl.WIFI_CARD_NOT_PRESENT Implicitly cleared: true
Description: WIFI_CARD_NOT_PRESENT The internal Wi-Fi module is not present. The internal Wi-Fi module might be not operational.
Remedial action: 1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported. 2. Replace the Flexi Zone BTS.
Table 12375: WrongCpaaSoftwareVersion
Name: WrongCpaaSoftwareVersion (791) Severity: critical Release:

Package: netw.WrongCpaaSoftwareVersion Implicitly cleared: true
Raised on class: netw.NetworkElement Default probable cause: wrongCpaaSoftwareVersion
Description: The alarm is raised when the 7701 CPAA software is the wrong version and requires an upgrade.
Raising condition: (('Software Version' EQUAL '\"TiMOS-B-3.0.Generic \"') AND ('Chassis Type' EQUAL '7701 CPAA'))
Clearing condition: (('Software Version' NOT EQUAL '\"TiMOS-B-3.0.Generic \"') AND ('Chassis Type' EQUAL '7701 CPAA'))
Remedial action: The SW version of the CPAA must be upgraded to the version compatible with CPAM version.

Nokia Help2 PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Nokia Help2 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

12/21/2019 Alarms

Alarm Reference > 33. Airscale FDD > Alarms

Table 12243: ActiveAbnormalCondition

Alarm Attributes Applicable major release

Name: ActiveAbnormalCondition (3938) Severity: major Release:

Description: The alarm is an indication for abnormal condition on NE.

Raising condition: ('abnormalCondition' EQUAL 'true')

Clearing condition: ('abnormalCondition' EQUAL 'false')

Table 12244: AGWDiameterPeerDown

Alarm Attributes Applicable major release

Name: AGWDiameterPeerDown (844) Severity: indeterminate Release:

Raising condition: ('Path Management State' NOT EQUAL 'Active')

Clearing condition: ('Path Management State' EQUAL 'Active')

Table 12245: AUTO_NEGO_MIS_MATCH

Name: AUTO_NEGO_MIS_MATCH (11513) Severity: indeterminate Release:

Table 12246: BareMetalReachabilityDown

Alarm Attributes Applicable major release

Name: BareMetalReachabilityDown (10273) Severity: major Release:

Raising condition: (('bgpReachabilityState' NOT EQUAL '0'))

Clearing condition: (('bgpReachabilityState' EQUAL '0'))

Table 12247: BASE_STATION_CONNECTIVITY_DEGRADED

Alarm Attributes Applicable major release

Name: BASE_STATION_CONNECTIVITY_DEGRADED (11514) Severity: indeterminate Release:

GTP-U Path Failure

1. Check the availability of the MME.

Alarm Attributes Applicable major release

Name: BASE_STATION_CONNECTIVITY_LOST (11515) Severity: indeterminate Release:

Table 12249: BASE_STATION_FAULTY

Alarm Attributes Applicable major release

Name: BASE_STATION_FAULTY (11516) Severity: indeterminate Release:

Alarm Attributes Applicable major release

Name: BASE_STATION_LICENSE_LIMITATION (11517) Severity: indeterminate Release:

Table 12251: BASE_STATION_NOTIFICATION

Alarm Attributes Applicable major release

Alarm Attributes Applicable major release

Name: BASE_STATION_NOTIFICATION (11518) Severity: indeterminate Release:

Alarm Attributes Applicable major release

Name: BASE_STATION_OPERATION_DEGRADED (11519) Severity: indeterminate Release:

Control Interface not available:

Alarm Attributes Applicable major release

Name: BASE_STATION_TRANSMISSION_ALARM (11520) Severity: indeterminate Release:

Note: The interface numbering shall be similar to ETHLK.

Alarm Attributes Applicable major release

Name: BFD_DOWN (11521) Severity: indeterminate Release:

Table 12255: BFD_DOWN_Egress

Alarm Attributes Applicable major release

Alarm Attributes Applicable major release

Name: BFD_DOWN_Egress (11522) Severity: indeterminate Release:

Remedial action: Check the BFD configuration at the local end.

Table 12256: BFD_DOWN_Ingress

Alarm Attributes Applicable major release

Name: BFD_DOWN_Ingress (11523) Severity: indeterminate Release:

Table 12257: BLUETOOTH_AUTH_FAIL

Alarm Attributes Applicable major release

Name: BLUETOOTH_AUTH_FAIL (11524) Severity: indeterminate Release:

Table 12258: BLUETOOTH_CONNECTED

Name: BLUETOOTH_CONNECTED (11525) Severity: indeterminate Release:

Table 12259: BLUETOOTH_ENABLED

Alarm Attributes Applicable major release

Name: BLUETOOTH_ENABLED (11526) Severity: indeterminate Release:

Table 12260: BLUETOOTH_PAIRED

Alarm Attributes Applicable major release