Nokia Help PDF

29/05/2020 Alarms
Alarm Reference > 38. FDD AirScale

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 Alcatel-Lucent effort. If the 5620 SAM raises an alarm against this device type, and the alarm is not described in this chapter, see
Chapter 37, Unspecified NE.
Table 38-1: 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 38-2: AGWDiameterPeerDown

major
release
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 38-3: AUTO_NEGO_MIS_MATCH

major
release
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\n\nThis alarm indicates that there is a mismatch between the BTS configuration and the auto-
negotiation result.\n\nIf the alarm is active, a synchronization loop is possible.\n\n
Remedial action: Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nTry with local management or site support
equipment.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:\nConfirm that the Ethernet Synchronization master/slave settings
are correct on the Flexi Zone Micro BTS or Flexi Zone Access Point and backhaul equipment. \nNote: The Flexi Zone Micro BTS and Flexi
Zone Access Point only support slave mode.
https://infocenter.nokia.com/public/5620SAM140R12A/index.jsp?topic=%2FSAM_AR%2Fhtml%2FNokiaFDDAirscale7983.html 1/101
29/05/2020 Alarms
Table 38-4: AuxiliaryServerStatus

major
release
Name: AuxiliaryServerStatus (311) Severity: critical Release:

Type: communicationsAlarm Specific problem: Not Applicable FL16A
Package: server.AuxiliaryServerStatus Implicitly cleared: true
Raised on class: server.AuxiliaryServer Default probable cause: systemFailed
Description: The alarm is raised when a 5620 SAM main server cannot communicate with an auxiliary server. The alarm clears when
communication is restored.
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 AUX and SAM servers is unreliable.
Table 38-5: BareMetalReachabilityDown

major
release
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 38-6: BASE_STATION_CONNECTIVITY_DEGRADED

major
release
Name: BASE_STATION_CONNECTIVITY_DEGRADED Severity: indeterminate Release:

(11514) Specific problem: BASE STATION CONNECTIVITY FL16A
Type: communicationsAlarm DEGRADED
Package: Implicitly cleared: true
racfl.BASE_STATION_CONNECTIVITY_DEGRADED Default probable cause: INDETERMINATE
Raised on class: racfl.MRBTS
Description: BASE STATION CONNECTIVITY DEGRADED\n\nA 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.\n\nThe 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.\n\nDo not cancel the
alarm. The system automatically cancels the alarm when the fault has been corrected.
Remedial action: FAULT NAME\nGTP-U Path Failure\n\nFAULT ID\n6150: EFaultId_GtpuPathFailure\n\nMEANING\nIn GTP-U supervision,
a network element did not respond to the GTP-U: Echo Request message within the allotted time.\n\nINSTRUCTIONS\n1. Check the GTP-U
path supervision configuration of the eNB. \n2. Check if the supervised network element is operating correctly.\n3. Check the communication
equipment between the eNB and the supervised network element.\n\nIn case actDualUPlaneIpAddress =" true, the S-GW might still be
reachable although an alarm caused by fault 6150 is reported.\nCheck 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 to the same S-GW are faulty, the S-GW is not
reachable anymore.\n\n\n\n\nFAULT NAME\nM3 interface recovery failure\n\nFAULT ID\n6850:
EFaultId_M3ResetRetryOut\n\nMEANING\nM3 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 connectivity, MME has failed, and so on.\n\nINSTRUCTIONS\nNote:
Perform the steps below in the listed order until the alarm disappears.\n\n1. Check the availability of MME.\n2. Check the connection with
MME.\n3. Disconnect and reconnect MME.\n\n\n\n\nFAULT NAME\nM3 interface setup failure\n\nFAULT ID\n6851:
29/05/2020 Alarms

major
release
EFaultId_M3SetupFailure\n\nMEANING\nThere 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 situation.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order
until the alarm disappears:\n\n1. Check availability of MME.\n2. Check other faults on MME and BTS.\n3. Check the parameters related to
M3 interface in the BTS and MME.\n4. Reset the BTS.\n\n\n\n\nFAULT NAME\nRIM interface error\n\nFAULT ID\n6323:
EFaultId_RimInterfaceError\n\nMEANING\n1. An RIM association could not be established because an RIM Error PDU has been received for
an RIM-enabled GERAN neighbor cell.\n2. An RIM Application Error has been detected.\n3. S1 links to all configured MMEs are active, but
the routing of RIM PDU to the RIM-enabled WCDMA neighbor cell is not available.\n\nINSTRUCTIONS\nCheck the value of the parameter
"rimStatus" in LNADJG or LNADJW (according to the alarm source) objects to find all impacted RIM associations.\n\nIf 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 correct.\n\nIf many LNADJG or LNADJW objects have "rimStatus" Unavailable, check the connectivity to GSM or WCDMA network
(MME<->SGSN<->BSC).\n\nNote 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 given time. The alarm is raised for the first LNAJDG or LNADJW where the fault is
detected. The alarm additional information contains the parameters of the first LNADJG or LNADJW, even if the RIM fault is already inactive
for the LNADJG or LNADJW, but the fault is still active for other LNADJG or LNADJW supporting the same PLMN.\n\n\n\n\nFAULT
NAME\nRIM interface timeout\n\nFAULT ID\n6322: EFaultId_RimInterfaceTimeout\n\nMEANING\nA 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
reliable.\n\nINSTRUCTIONS\nCheck the value of the parameter "rimStatus" in LNADJG or LNADJW (according to the alarm source) objects
to find all impacted RIM associations.\n\nIf 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 cells are correct.\n\nIf many LNADJG or LNADJW objects have
"rimStatus" Unavailable, check the connectivity to the GSM or WCDMA network (MME<->SGSN<->BSC).\n\nNote 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
given time. The alarm is raised for the first LNAJDG or LNADJW where the fault is detected. The alarm additional information contains the
parameters of the first LNADJG or LNADJW even if the RIM fault is already inactive for the LNADJG or LNADJW, but the fault is still active for
other LNADJG or LNADJW supporting the same PLMN.\n\n\n\n\nFAULT NAME\nS1 interface recovery failure\n\nFAULT ID\n6317:
EFaultId_S1ResetRetryOut\n\nMEANING\nThe 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 connectivity; MME has failed; and so on.\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the alarm disappears:\n\n1. Check the availability of the MME.\n2. Check the connection with the
MME.\n3. Disconnect and reconnect the MME.\n\n\n\n\nFAULT NAME\nS1 interface setup failure\n\nFAULT ID\n6308:
EFaultId_S1SetupRetryOut\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThere is no S1
connectivity to an MME. \n\nThe fault is generated if the S1 setup procedure has subsequently been attempted but failed the number of times
equal to "maxS1SetRetry".\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nThere 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 situation.\n\nINSTRUCTIONS\nNote: Perform the
steps below in the listed order until the alarm disappears:\n\n1. Check the availability of the MME.\n2. Check other faults on the MME and
BTS.\n3. Check the parameters related to the S1 interface in the BTS and MME.\n4. Reset the BTS.\n\n\n\n\nFAULT NAME\nS1 SCTP path
failure\n\nFAULT ID\n6204: EFaultId_S1SctpPathAl\n\nMEANING\nOne 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 path is available to continue
operation.\n\nINSTRUCTIONS\n1. Check whether the transport path is alive.\n2. Check the configuration of transport addresses at
MME.\n\n\n\n\nFAULT NAME\nToggling: <Fault name>\n\nFAULT ID\n4026: EFaultId_TogglingAl\n\nMEANING\nThis alarm is used to inform
the operator that another BTS fault (the original fault) is toggling.\nThe alarm that is related to the original fault is suppressed and the new
alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is raised.\n\nToggling alarms that are related to the original faults are
suppressed until the toggling condition is cleared.\n\nThe severity of this BTS fault is the same as the severity of the original\ntoggling BTS
fault.\n\nINSTRUCTIONS\n1. Check the fault name of the toggling BTS fault. \n2. Follow the instructions of the toggling BTS fault to clear the
problem.\n \nNote: 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 available with Snapshot.\n\n\n\n\nFAULT NAME\nTransport layer connection failure in M3
interface\n\nFAULT ID\n6205: EFaultId_M3SctpEndpointAl\n\nMEANING\nThe 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 operation on the faulty connection
with the MME.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears:\n1. Check the connection
with MME, particularly whether the M3 link is broken.\n2. Check if the MME is operational.\n3. 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 both "1000 Mbit/s Full
duplex".\n\nIf this fault happens right after a commissioning or a configuration change, verify the following configuration data: IP address of
the MME.\n\n\n\n\nFAULT NAME\nTransport layer connection failure in S1 interface\n\nFAULT ID\n6202:
EFaultId_S1SctpEndpointAl\n\nMEANING\nThe 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 continue operation on the faulty connection with the
MME.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears:\n\n1. Check the connection with the
MME, accordingly, based on whether the S1 link is broken.\n2. Check if the MME is operational.\n3. 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 "Autodetect" or both "1000
Mbit/s Full duplex").\n\nIf this fault happens right after a commissioning or a configuration change, verify the IP address of the
MME.\n\n\n\n\nFAULT NAME\nTransport layer connection failure in X2 interface \n\nFAULT ID\n6203:
EFaultId_X2SctpEndpointAl\n\nMEANING\nThe 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 available to continue operation on the faulty connection with the
adjacent BTS.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\n1. Check the
connection with the adjacent BTS based on whether the X2 link is broken.\n2. Check if the adjacent BTS is operational.\n\nIf this fault
happens right after a commissioning or a configuration change, verify the IP address of the adjacent BTS.\n\n\n\n\nFAULT NAME\nX2
interface recovery failure\n\nFAULT ID\n6303: EFaultId_X2ResetRetryOut\n\nMEANING\nThe X2 interface reset has failed after several
attempts. This indicates that a severe failure has occurred. For example, there is some configuration problem, there is no X2 connectivity, the
adjacent BTS has failed, and so on.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears:\n\n1.
Check the availability of the adjacent BTS.\n2. Check the connection with the adjacent BTS.\n3. Disconnect and reconnect the adjacent
BTS.\n\n\n\n\nFAULT NAME\nX2 interface setup failure\n\nFAULT ID\n6304: EFaultId_X2SetupRetryOut\n\nMEANING\nThere is no X2
connectivity to an adjacent BTS, the adjacent BTS has failed, and so on.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed
order until the alarm disappears:\n\n1. Check the connectivity to the related adjacent BTS.\n2. Check other faults.\n3. Check the parameters
related to the X2 interface of the adjacent BTS.\n4. Reset the BTS."
Table 38-7: BASE_STATION_CONNECTIVITY_LOST

major
release
29/05/2020 Alarms

major
release
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\n\nA critical fault (or faults) has occured in the base station interface.\nCheck the
reason for the fault from the supplementary text field of the\nalarm.\n\nThe 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.\n\nDo not cancel the
alarm. The system automatically cancels the alarm when\nthe fault has been corrected.
Remedial action: FAULT NAME\nS1 interface recovery failure\n\nFAULT ID\n6317: EFaultId_S1ResetRetryOut\n\nMEANING\nThe 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 connectivity; MME has failed; and so on.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm
disappears:\n\n1. Check the availability of the MME.\n2. Check the connection with the MME.\n3. Disconnect and reconnect the
MME.\n\n\n\n\nFAULT NAME\nS1 interface setup failure\n\nFAULT ID\n6308: EFaultId_S1SetupRetryOut\n\nMEANING\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThere is no S1 connectivity to an MME. \n\nThe fault is generated if the S1 setup
procedure has subsequently been attempted but failed the number of times equal to "maxS1SetRetry".\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD:\nThere 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 situation.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears:\n\n1.
Check the availability of the MME.\n2. Check other faults on the MME and BTS.\n3. Check the parameters related to the S1 interface in the
BTS and MME.\n4. Reset the BTS.\n\n\n\n\nFAULT NAME\nToggling: <Fault name>\n\nFAULT ID\n4026:
EFaultId_TogglingAl\n\nMEANING\nThis alarm is used to inform the operator that another BTS fault (the original fault) is toggling.\nThe alarm
that is related to the original fault is suppressed and the new alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is
raised.\n\nToggling alarms that are related to the original faults are suppressed until the toggling condition is cleared.\n\nThe severity of this
BTS fault is the same as the severity of the original\ntoggling BTS fault.\n\nINSTRUCTIONS\n1. Check the fault name of the toggling BTS
fault. \n2. Follow the instructions of the toggling BTS fault to clear the problem.\n \nNote: 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 available with
Snapshot.\n\n\n\n\nFAULT NAME\nTransport layer connection failure in S1 interface\n\nFAULT ID\n6202:
EFaultId_S1SctpEndpointAl\n\nMEANING\nThe 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 continue operation on the faulty connection with the
MME.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears:\n\n1. Check the connection with the
MME, accordingly, based on whether the S1 link is broken.\n2. Check if the MME is operational.\n3. 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 "Autodetect" or both "1000
Mbit/s Full duplex").\n\nIf this fault happens right after a commissioning or a configuration change, verify the IP address of the MME.
Table 38-8: BASE_STATION_FAULTY

major
release
Name: BASE_STATION_FAULTY (11516) Severity: indeterminate Release:

Type: equipmentAlarm Specific problem: BASE STATION FAULTY FL16A
Package: racfl.BASE_STATION_FAULTY Implicitly cleared: true
Description: BASE STATION FAULTY\n\nA critical fault (or faults) has occurred in the base station.\n\nCheck the reason for the fault from
the supplementary text field of the alarm.\n\nThe 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.\n\nDo not cancel the alarm. The system automatically
cancels the alarm when the fault has been corrected.
Remedial action: 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 not cause the fault.\n\nBefore 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/module. When an active alarm is a 'Start' alarm, a
site reset is required to cancel the alarm. If the site reset or module block/unblock does not help, replace the faulty unit/module (see the
source of the alarm and instructions fields of the corresponding alarms). \n\nIn 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 to continue functioning without a system
module. In such case replace the system module first and check if the modules previously marked as Faulty are now in Working
state.\n\n\nBelow 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 descriptions, LTE System Libraries. The BTS fault descriptions are also included in BTS SW
release documentation. If that does not help, contact your local customer support. \n\nFAULT NAME\nAntenna link is down\n\nFAULT
ID\n476: EFaultId_Rp3BusError\n\nMEANING\nThe antenna (RP3) link is down. The transmitter or receiver drops from
synchronization.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Restart the BTS.\n2. If
that does not help, replace the alarming module. \n\nFlexi 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. \n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD: If FBBx or ABIx is causing the alarm,
replace the FBBx or ABIx.\n\nFlexi 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 Antenna.\n\n\n\n\nFAULT NAME\nAP blocked\n\nFAULT ID\n4260:
EFaultId_ApBlockedAl\n\nMEANING\nThe 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 maintenance task.\n\nINSTRUCTIONS\nTo cancel the fault, unblock the
Flexi Zone Access Point.\n\n\n\n\nFAULT NAME\nBaseband bus configuration of <x> was rejected\n\nFAULT ID\n1811:
EFaultId_BbBus_ConfFailedAl\n\nMEANING\nThe baseband-bus-related configuration of <x> has been rejected by the HW SW, DSP, or RF
SW.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nReplace the alarming module.\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD:\n1. Download the correct configuration.\n2. Reset the BTS.\n3. Replace the BTS.\n\nFlexi Zone:\n1.
Download the correct configuration.\n2. Reset the Flexi Zone Access Point from the BTSSM.\n3. Replace the Flexi Zone Access
29/05/2020 Alarms

major
release
Point.\n\nFlexi Zone SFN Antenna:\n1. Download the correct configuration.\n2. Reset the Flexi Zone SFN Antenna from the BTSSM.\n3.
Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nBaseband bus failure\n\nFAULT ID\n3020:
EFaultId_BaseBandBusFailure\n\nMEANING\nThe Flexi BTS has detected an abnormal operation or a failure in the BTS\ninternal or external
(optical link) baseband bus. The failure cannot be\nattributed to a specific module and there are several possible fault
sources.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n\n1. Check the other active
BTS faults and act accordingly.\n\n2. Check the cables between the System Module and RF Module.\n\n3. Reset the RF Module and/or
System Module, depending on the alarm source:\n a. Reset the RF Module by blocking and unblocking it.\n b. Reset the System Module by
blocking and unblocking it.\n\n4. Replace the alarming RF Module.\n\n5. If the System Module is the source, or replacing the RF Module
does not clear the fault situation, replace the alarming System Module.\n\n\n\n\nFAULT NAME\nBaseband resources mapping to cells
failure\n\nFAULT ID\n12: EFaultId_TcomConfigAl\n\nMEANING\nA 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 operation cannot be taken into use. The reason for
the failure might be an internal problem in the eNodeB O&M system.\n\nINSTRUCTIONS\n1. Block and unblock the BTS.\n2. Perform a
power-off reset. \n3. If steps 1 and 2 do not help, replace the module that is causing the\nalarm. \n\n\n\n\nFAULT NAME\nBB bus reception
error (summing device)\n\nFAULT ID\n2016: EFaultId_Muksu_SMTimeOffAl\n\nMEANING\nThe 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 set into the wrong place (PI
delay), or the data itself is in the wrong place.\n\nINSTRUCTIONS\n1. 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 and the FBBx module.\n\n2. Replace
the unit that causes the alarm (system module or FBBx/ABIx).\n\n\n\n\nFAULT NAME\nBB bus transmission error\n\nFAULT ID\n2017:
EFaultId_Muksu_SRx10b8bAl\n\nMEANING\nA decoding error has been detected in the baseband internal link. The data packet is lost, or
the content is corrupted.\n\nThis situation also occurs when the links are not synchronized with each other.\n\nINSTRUCTIONS\n1. Check
the cables between the system module and the RF module, and the cable between the FBBx/ABIA module and the RF module.\n\n2. Reset
the system module.\n\n3. Replace the alarming module (system module).\n\n\n\n\nFAULT NAME\nBoot configuration inconsistency
detected\n\nFAULT ID\n4102: EFaultId_BootConfigurationInconsistencyAl\n\nMEANING\nDuring 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 compared at these periods:\n-
before SW download\n- during SW activation, before active and passive SW switch\n- during start-up\n\nINSTRUCTIONS\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD:\n1. Block/unblock the Flexi Zone Micro BTS to reset.\n2. If blocking or unblocking the Flexi Zone Micro BTS
does not solve the problem, replace the faulty Flexi Zone Micro BTS.\n\nFlexi Zone Access Point, Flexi Zone SFN
Antenna:\nNone\n\n\n\n\nFAULT NAME\nBTS blocked\n\nFAULT ID\n50: EFaultId_BTSBlockedAl\n\nMEANING\nThe BTS is blocked with
the BTS Site Manager. The purpose is to avoid fault indications that might be raised during a BTS maintenance
task.\n\nINSTRUCTIONS\nUnblock the BTS to cancel the fault. Unblocking the BTS causes a BTS reset.\n\n\n\n\nFAULT NAME\nBTS file
error\n\nFAULT ID\n1802: EFaultId_FileRequestFlashAl\n\nMEANING\nA software download to FSP, DSP, ABIx or FR has
failed.\n\nINSTRUCTIONS\nNote: Perform the following steps in the listed order until the fault disappears:\n\n1. Use BTS Site Manager to
perform a full commissioning to the BTS using the NetAct backup upload SCF file as template.\n\n2. Download two different software
packages so that the faulty file is removed from the BTS.\n\n3. Download the software again.\n\n4. Replace the System
Module.\n\n\n\n\nFAULT NAME\nBTS internal SW management problem\n\nFAULT ID\n3090:
EFaultId_BtsInternalSwManagementProblem\n\nMEANING\nA software update to a module or sub-assembly has failed, or a corrupted SW
file has been detected in the FLASH.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears:\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the other active BTS faults. If the ROM
disk is corrupted, change the alarming module.\n2. Reset the RF Module and/or System Module (depending on the fault source) by
blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n5. Replace the alarming module.\n\nFlexi Zone
Micro FDD, Flexi Zone Micro TDD:\n1. 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 Access Point.\n2. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point by
blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n\nFlexi Zone:\n1. Check the other active Flexi
Zone Access Point faults. If the ROM disk is corrupted, change the Flexi Zone Access Point.\n2. Reset the Flexi Zone Access Point to trigger
new SW load.\n3. Check the SW files.\n\nFlexi Zone SFN Antenna:\n1. Check the other active Flexi Zone SFN Antenna faults. If the ROM
disk is corrupted, change the Flexi Zone SFN Antenna.\n2. Reset the Flexi Zone SFN Antenna to trigger new SW load.\n3. Check the SW
files.\n\n\n\n\nFAULT NAME\nBTS Location Lock violation detected\n\nFAULT ID\n4284: EFaultId_LocationLockViolation\n\nMEANING\nA
Location Lock violation has been detected after a BTS reboot.\n1. 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.\n2. 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 values that are stored in the
Location Lock evidence file.\n\nThe integrity check of the Location Lock evidence data has failed after a BTS reboot.\n1. The Location Lock
evidence file is missing.\n2. The Location Lock evidence file has failed P7 signature validation.\n\nINSTRUCTIONS\n1. If the BTS detects a
Location Lock violation:\n- If the BTS has been relocated without authorization, the alarm is expected.\n- If the BTS relocation is authorized,
disable the Location Lock feature and then re-enable it to reacquire the correct Location Lock evidence.\n2. If the BTS detects a missing or
corrupted Location Lock evidence:\n- Disable the Location Lock feature and then re-enable it in order to recover.\n- If, during the above
operation, the BTS has reported fault 4283:EFaultId_LocationLockFailed, replace the faulty device.\n\n\n\n\nFAULT NAME\nBTS master
clock tuning failure\n\nFAULT ID\n1818: EFaultId_Ov_OscAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD: \nThe 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 in BPF, or greater than or equal to the Max.OcxoControlValue.Alarm.Set value specified in
BPF.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe 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.\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault
disappears:\n1. Check the other alarms of the BTS and FTM and act accordingly.\n2. If there are no other synchronization-related alarms
active. Start the fast tuning with the BTS Site Manager.\n3. Reset the site. Run fast tuning again.\n4. 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 the Sync Out
interface of the Flexi System Module: the required accuracy is +/-0.015ppm. If the reference accuracy is correct, run fast tuning.\n5. If that
does not help, replace the system module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThis 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 producing an inaccurate reference. Perform the following steps to isolate the cause of the fault:\n1. Identify the currently selected
synchronization reference source of the BTS with the active 1818 fault. If it is a transport-based reference source that involves a time source
distributed over the backhaul network (for example, Synchronous Ethernet or IEEE1588-2008 (Timing over Packet)), verify that there are no
alarms or faults associated with the respective time servers. If there is a fault associated with a network-based time server, it is also likely that
other FZMs being served by these devices will also be reporting the 1818 fault. Correct any identified faults associated with the associated
Synchronous Ethernet or IEEE1588-2008 master clock, and if the 1818 fault subsequently clears.\n2. 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 with the transport
reference source master clock, the BTS likely has an internal problem, which requires its replacement.\n\n\n\n\nFAULT NAME\nBTS or unit
temperature too high\n\nFAULT ID\n4182: EFaultId_BtsTempTooHighAl\n\nMEANING\nThe temperature of the Flexi Zone Micro BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna has exceeded the predefined threshold.\n\nINSTRUCTIONS\n1. Validate if the ambient
temperature is within the specifications and if no foreign debris has accumulated on the unit. \n\n\n\n\n\nFAULT NAME\nBTS or Unit
temperature too low\n\nFAULT ID\n4183: EFaultId_BtsTempTooLowAl\n\nMEANING\nThe temperature of the Flexi Zone Micro BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna has exceeded the thresholds for operation.\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT
NAME\nBTS reference clock missing\n\nFAULT ID\n3080: EFaultId_BtsReferenceClockMissing\n\nMEANING\nFlexi BTS FDD, Flexi BTS
29/05/2020 Alarms

major
release
TDD, AirScale BTS FDD, AirScale BTS TDD:\nThis BTS fault indication is generated if the reference clock monitoring function of the BTS
does not receive the configured synchronization reference signal, if all the synchronization reference signals are missing, or if the BTS has
been in holdover mode and holdover time has run out (TDD only). \n\nBackground information:\n\nThere is configurable synchronization
priority list in the FlexiBTS, AirScaleBTS.\n\nNormally, 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 sources are checked against the reference source priority list in the BTS
commissioning file and deviations regarding the missing source generate a faults.\n\nThe 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 Timing over Packet (ToP) in which
the timing information to BTS(s) is generated by a ToP master. The TRS reference source priority selection also user-selectable.
Furthermore, if a signal listed in the TRS references is not received, a BASE STATION TRANSMISSION ALARM is reported., \n\nFlexi Zone
Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe 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 GPS satellites, there is a loss of its 1 PPS clock or there is
a loss of communication with the receiver.\nThe BTS supports a ToP or SyncE reference source that has configurable priorities relative to
each other through the "synchroSourceList" parameter.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD:\nDepending on the installed and commissioned synchronization source(s) listed in the "Meaning" section, see the commissioned
synchronization option below and perform the steps in the listed order until the BTS fault indication disappears.\n\nGPS receiver (PPS
source):\n1. 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 which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does
not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS
antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then.\n\n2. There might
be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.\n\n3. There might be a malfunction in the BTS.
Perform a BTS site reset.\n\n4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors.\n\n5. There might
be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.\n\nExternal 2.048 MHz signal:\n1. 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, check the cables. Note that because the device type is not known, detailed instructions cannot be given - refer to the appropriate user
manual of the device for further actions.\n\n2. There might be a malfunction in the BTS. Perform a BTS site reset.\n\nFTM reference (TDM,
SyncE or ToP as source):\n1. 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 synchronization source, it turns off the clock reference signal which is normally delivered to the
BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) might be missing, causing the
FTM's internal clock to drop to holdover mode. In this case, the fault in the transmission NETWORK must be corrected (the FTM itself might
be working fine).\n\n2. Check the alarms of the FTM unit and act accordingly.\n\n3. Check the synchronization settings of the FTM unit.\n\n4.
There might be a malfunction in the BTS. Perform a BTS site reset.\n\n5. 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 failure, but there might be connection failures in the
transmission or packet network, causing the FTM clock to drop to holdover mode. Especially the BTS fault indication activity (frequent BTS
fault indication activations/cancels instead of a stable BTS fault indication state) points to the instability of the transmission network, not to a
failure in the unit.\n\nIf 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, replace the System Module.\n\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\nDepending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned
synchronization option below and perform the steps in the listed order until the BTS fault indication disappears.\n\nGPS source:\n1. 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) power reset of the GPS receiver. If the associated GPS receiver communication or 1 PPS clock fault is not cleared within
5 minutes after the remote power reset, a Flexi Zone Micro BTS replacement is recommended.\n\nSyncE or ToP as source:\n1. Check the
alarms of the Flexi Zone Micro BTS or Flexi Zone SFN Antenna unit and act accordingly.\n2. 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 the required
synchronization information to the Flexi Zone Micro BTS. Correct any associated PRC or master clock problems.\n3. 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
replacement might be necessary.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n4001:
EFaultId_BtsResetNeededAl\n\nMEANING\nThis 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 trigger an autonomous reset on its own.\n\n1. The BTS has detected a
commissioned (configured in SCF) extension baseband\nmodule (for example, FBBC) that was not detected during BTS startup. Thus, the
BTS must be reset to take the module into use.\n\n2. 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.\nNote: LCR supported by the FSP is reported as the fault
source in this case.\n\n3. 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.\n\n4. An internal problem has been detected, and the BTS cannot continue start-up\nwithout a BTS reset.\n\n5.
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 to an SFP that does not support the configured speed), and a BTS reset might be needed to solve the
problem.\nNote: The affected LCR is reported as the fault source in this case.\n\n6. 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 module (configured in SCF)
or optical cable. The BTS must be reset to set the cell up with the use of the detected radio module or cable. LCR is the fault source in this
case. \n\n7. 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 example, FBBA. The BTS must be reset to take the module into use.\n\n8. 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.\n\n9. The
BTS has cleared an alarm and triggers an autonomous BTS reset to enable\nnormal BTS operability, but the BTS reset counter has been
exceeded. The operator must perform a BTS reset to enable BTS operability.\n\n10. 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 the operator might solve this issue.\n\n11.
FDD only - Phase synchronization source was not available in BTS start-up,\nand alarm with fault 4153 was raised. Phase synchronization
source is available now. BTS reset is needed to activate features requiring network-level synchronization (OTDOA, eICIC, MBMS, inter-eNB
Carrier Aggregation).\n\n12. BTS cannot execute FSP or BTS autonomous recovery reset because of either of the following reasons:\n- It will
disable any working cell \n- An internal BTS limitation\n\n13. FSP card is lost or disconnected. A BTS reset is necessary to protect the BTS
from a crash after the card hot insert.\n\n14. FSP autonomous recovery reset has failed. A BTS reset is necessary to try to recover the
FSP.\n\n15. FSMr3 only - CRAN configuration for a cell has failed. A BTS reset is necessary to reconfigure CRAN.\nNote: The affected LCR
is reported as the fault source in this case.\n\n16. 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 case.\n\n17. FSP power on failed after fault 4077 (FSP overheated) is
canceled. A BTS reset is needed to try to take the FSP into use.\n\n18. 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-in and take new RF module resources into
use.\n\nOnly case #10 is applicable for FZM.\n\nINSTRUCTIONS\n1. Check the alarm diagnostic information for the reason of the fault report
before the reset.\n\n2. Reset (block and unblock) the BTS.\n\n\n\n\n\n\n\nFAULT NAME\nBTS RF BB energy too high\n\nFAULT ID\n1975:
EFaultId_BtsRfBbEnergyTooHighAl\n\nMEANING\nTX baseband power is too high.\n\nINSTRUCTIONS\n1. Reset the Flexi Zone Micro BTS,
Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n2. If that does not help, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or
Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nBTS startup temperature out of specification.\n\nFAULT ID\n4184:
EFaultId_BtsStartupTempOutOfSpecAl\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Validate that the ambient temperature is
within the specifications and that no foreign debris has accumulated on the unit.\n2. Verify if the solar shield is installed.\n\n\n\n\nFAULT
29/05/2020 Alarms

major
release
NAME\nBTS synchronization is missing during startup\n\nFAULT ID\n4160: EFaultId_BtsClockSourceOutOfSynchronizationDuringStartupAl
\n\nMEANING\nThe synchronization source of the BTS is not available when it works as synchronization slave during start-
up.\n\nINSTRUCTIONS\n1. Check the cable connection between the synchronization master and its GPS.\n2. Check the alarms in the
synchronization master system module and act accordingly. Since the synchronization master is a separate system from the synchronization
slave, check its own alarms and instructions for recovering the synchronization.\n3. Reset the synchronization master system
module.\n\n\n\n\nFAULT NAME\nBTS vendor-specific file fault\n\nFAULT ID\n6262: EFaultId_InvalidVendorSpecificFile\n\nMEANING\nThere
has been an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup.\n\nThe fault is also detected when a
vendor-specific file is missing.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault disappears:\n\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the other active BTS faults. \n2. Reset the System Module by
blocking and unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n5. Replace the System Module.\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:\n1. Check the other active BTS faults. \n2. Reset the BTS by blocking and unblocking
it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n5. Replace the Flexi Zone Micro BTS or Flexi Zone
Controller.\n\n\n\n\nFAULT NAME\nCommissioning error: <x>\n\nFAULT ID\n3060: EFaultId_CommissioningError\n\nMEANING\nSome of
the commissioning parameters are either missing or faulty, or there is a mismatch between them.\n\nINSTRUCTIONS\nNote: Perform the
steps below in the listed order until the BTS fault disappears.\n\n1. Check the commissioning parameters with the BTS Site Manager
Commissioning Wizard.\n\n2. Load the correct commissioning file to the BTS.\n\n\n\n\nFAULT NAME\nCommunication failure\n\nFAULT
ID\n1806: EFaultId_CommunicationFailureAl\n\nMEANING\nCommunication with an application has failed. It has not replied to the message
that has been sent/resent to it.\n\nINSTRUCTIONS\n1. 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 causing the alarm.\n2. Check the fault history.\n\n\n\n\nFAULT
NAME\nCommunication Loss on all S1 links and OAM link\n\nFAULT ID\n4295:
EFaultId_CommLossOnAllS1LinksAndOamLinkAl\n\nMEANING\nCommunication on all S1 links and OAM link has been
lost.\n\nINSTRUCTIONS\nIf this alarm is observed from the BTSSM, check the backhaul connection of the BTS.\n\n\n\n\nFAULT
NAME\nConfiguration and hardware mismatch\n\nFAULT ID\n4282: EFaultId_ConfigurationAndHardwareMismatchAl\n\nMEANING\nThe
detected hardware does not support the SCF configuration.\n\nINSTRUCTIONS\n1. Read the diagnostic information of the alarm.\n2. If the
diagnostic information is "IQ compression or forced link speed incorrect\nin site configuration file", check what configurations are supported
by\nNokia, correct IQ compression, or force link speed value in the Site Configuration File (SCF), and then re-commission the BTS.\n3. If the
diagnostic info is "Number of detected RET units in multiRET\nis 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 update the BTS.\n\n\n\n\nFAULT NAME\nConfiguration
error: <x>\n\nFAULT ID\n3070: EFaultId_ConfigurationError \n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the
steps below in the listed order until the BTS fault disappears:\n\n1. Check the installed HW/SW version compatibility and the HW compatibility
with the current BTS configuration.\n\n2. Check that the BTS cell parameters from the Network management system match\nthe BTS HW
configuration (for example, frequency, power).\n\n3. Check the Network management system alarms for the alarming local cell (LCR).\n\n4.
Recommission the BTS to ensure that all parameters are correctly configured.\n\n\n\n\nFAULT NAME\nConfiguration Failed\n\nFAULT
ID\n4265: EFaultId_ApConfFailedAl\n\nMEANING\nThe 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 SW errors, that is, the Flexi Zone Controller SW can still provide
service to other FZAPs in this zone.\n\nINSTRUCTIONS\n1. Check all alarms posted by the Flexi Zone Access Point prior to this fault.\n2.
Check the configuration of the FZAP against similarly-configured FZAPs of the same type.\n3. Reset the Flexi Zone Access Point.\n4. Reset
the Flexi Zone Controller.\n\n\n\n\nFAULT NAME\nConnection to ToP master missing\n\nFAULT ID\n4058:
EFaultId_TopRefClkMissingAl\n\nMEANING\nThe reference clock monitoring has detected a loss of the ToP reference clock signal received
from the master clock.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault disappears.\n\n1. Check the
Ethernet interface functionality used by Timing Over Packet. Check if other faults related to the Ethernet interface exist.\n\n2. Check Timing
Over Packet configuration. Ensure that the Master clock IP address is configured properly and that the Master clock supports the given
parameters.\n\n3. Check the Master clock functionality.\n\n4. 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.\n\n\n\n\nFAULT NAME\nDSP application fatal error\n\nFAULT
ID\n6707: EFaultId_DspApplicationFatalErrAl\n\nMEANING\nA fatal error of the DSP Application SW has occurred.\n\nFlexi BTS FDD, Flexi
BTS TDD:\nIf an FSP in the BTS generates this fault, there is a malfunction in\nthe corresponding FSP sub-module.\nIf all FSPs generate
this fault, there is a malfunction in the FSM.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:\nIf 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 Micro BTS,
Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n1. Reset the System Module.\n2. Replace the
System Module, or FBBx or ABIx module (according to the fault source).\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\nPerform the steps below in the listed order until the fault disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone
Access Point, or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nDSP concurrent crash error\n\nFAULT ID\n6709: EFaultId_DspConcurrentCrashErrAl\n\nMEANING\nA
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).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the
listed order until the fault disappears.\n1. Reset the System Module.\n2. Replace the System Module, or FBBx or ABIx module (according to
the fault source).\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nPerform the steps below in the
listed order until the fault disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN\nAntenna.\n2.
Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone\nSFN Antenna.\n\n\n\n\nFAULT NAME\nDSP platform fatal
error\n\nFAULT ID\n6706: EFaultId_DspPlatformFatalErrAl\n\nMEANING\nA fatal error of the DSP HWAPI SW has occurred.\n\nFlexi BTS
FDD, Flexi BTS TDD:\nIf an FSP in the BTS generates this fault, there is a malfunction in\nthe corresponding FSP sub-module.\nIf all FSPs
generate this fault, there is a malfunction in the FSM.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nIf 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 Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n1.
Reset the System Module.\n2. Replace the System Module, or FBBx or ABIx module (according to the fault source).\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nNote: Perform the steps below in the listed order until the fault
disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro
BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\neNB configuration failed\n\nFAULT ID\n6293:
EFaultId_EnbConfigurationFailedAl\n\nMEANING\nThe BTS configuration has failed in the C-Plane. \n\nINSTRUCTIONS\nBlock and
unblock the BTS.\n\n\n\n\n\n\nFAULT NAME\nExternal GPS receiver in holdover\n\nFAULT ID\n4210:
EFaultId_ExtGpsInHoldoverAl\n\nMEANING\nThe external GPS or GNSS receiver module has lost satellite visibility and is currently
operating in holdover mode.\n\nINSTRUCTIONS\n1. 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 properly, that is, the sky visibility is not good enough. Refer to
the documentation for installations, and if there are deviations with the actual installation, re-install the GPS or GNSS antenna. Note that even
when the GPS or GNSS antenna has good sky visibility, the problem might be caused by installing the GPS or GNSS antenna too close to
the transmitter antennas of the BTS, causing disturbances to the GPS or GNSS receiver. \n2. Check the other possible alarms or fault
indications of the GPS or GNSS receiver and the BTS, and act accordingly.\n3. There might be a malfunction in the GPS or GNSS receiver.
Perform a (remote) power reset for the GPS or GNSS receiver module.\n4. 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 settings. The power needs to be ON in
29/05/2020 Alarms

major
release
this case (while in shared configuration, one receiver feeds the power towards the antenna, and power feeding setting of the other receivers
is OFF).\n5. 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 or GNSS receivers, and one receiver might feed the power to the antenna. The fault indication
might be caused by a failure in another GPS or GNSS receiver. \n6. Perform a local or physical power reset for the alarming GPS or GNSS
receiver module.\n7. 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. Check the operation and change them if needed.\n8. 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.\n\n\n\n\nFAULT NAME\nExternally triggered
DSP fatal error\n\nFAULT ID\n6708: EFaultId_ExternallyTriggeredDspFatalErrAl\n\nMEANING\nThe BTS has purposely triggered a GPIO
reset for the DSP.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nIf an FSP in the BTS generates this fault,
there is a malfunction in the whole BTS.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n1. Reset the System Module.\n2. Replace the System
Module, or FBBx or ABIx module (according to the fault source)\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nPerform the steps below in the listed order until the fault disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nFailure in optical interface\n\nFAULT ID\n3030:
EFaultId_FailureInOptical_Rp3Interface\n\nMEANING\nThe AirScale/Flexi BTS (System Module) has detected an abnormal operation or a
failure\nin an optical RP3 interface between two modules . \nThe failure cannot be attributed to a specific module but there are
several\npossible fault sources, for example, fiber optical cable, SFP, or individual module.\n\nINSTRUCTIONS\n1. PROBLEM
IDENTIFICATION \nEnsure you have the latest documentation available: \nUse the Operating Documentation from of the
Released/Supported Configurations to\ncheck the SW and HW details.\nCheck the SW version, List of Generic Faults (LGF), and Technical
Notes for any\nknown faults related to SW in use. \nNote: Use the fault-specific troubleshoot instructions from NOLS;" Failure\nin optical RP3
interface trouble shooting" document as a detailed guidance\nfor remote and site-specific investigations; On Site Investigations and
Measurements.\n\n2. REMOTE INVESTIGATIONS \nCheck if anything has changed in the system. What triggered the alarm: \nSW updates,
configuration, commissioning or Carrier power changes, RF sharing\nactivations or HW unit swaps. If the alarm appeared after any changes,
revert to\nprevious status if possible and see if the problem disappeared.\nCheck if the alarm depends on traffic; compare to similar cases in
network. How\nwide is the problem (single case, one of few). If any other device or RFM\nrelated 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, in what order did they
appear. If any other active alarm occurs, follow the instructions of the particular alarm accordingly. \n\n3. REMOTE ACTIONS\nReset the
BTS. For ON-SITE INVESTIGATIONS and ON-SITE SPECIFIC MEASUREMENTS, see details to site investigation from the troubleshooting
document.\n\n\n\n\nFAULT NAME\nFailure in replaceable baseband unit\n\nFAULT ID\n3003: EFaultId_FbiaFailureAl\n\nMEANING\nThe
BTS has detected an abnormal operation or a failure in the BTS replaceable\nbaseband unit.\n\nINSTRUCTIONS\nNote: Perform the steps
below in the listed order until the BTS fault indication disappears:\n\n1. Check the other active BTS faults and act accordingly.\n2. Ensure that
the plug-in type baseband unit is installed correctly.\n3. Reset the alarming baseband unit.\n4. Replace the alarming baseband
unit.\n\n\n\n\nFAULT NAME\nFatal OSE Error\n\nFAULT ID\n418: EFaultId_OseFatalErr\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD,
AirScale BTS FDD, AirScale BTS TDD:\nThe operating system (OSE) goes into the error handler with a fatal status. This might be caused by
an out-of-memory situation.\n\nAirScale BTS FDD/TDD, Flexi BTS FDD/TDD: \nIf only one FSP/ABIx in the BTS generates this fault, there is
a malfunction in one of the FSP/ABIx submodules. \n\nFlexi BTS FDD/TDD: \nIf all FSPs generate this fault, there is a malfunction in the
FSM.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe operating system (OSE) goes into the error handler
with a fatal status. The cause can be, for example, an out of memory situation.\n\nINSTRUCTIONS\nNote: Perform the steps below in the
listed order until the fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System
Module.\n2. According to the fault source replace either: \n- the System Module (Flexi BTS FDD/TDD)\n- FBBx/ABIx module (AirScale BTS
FDD/TDD, Flexi BTS FDD/TDD).\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nReplace the Flexi
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFaulty configuration of system
modules\n\nFAULT ID\n1858: EFaultId_FaultyFcmConfigurationAl\n\nMEANING\nThe 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 slave system modules are not
connected to each other, or the module which is to be the slave is not configured as a slave in the SCF files.\n\nINSTRUCTIONS\nCheck that
the WCDMA master system module is connected to the system module when the SCF parameter "syncMaster" =" "FALSE".\n\n\n\n\nFAULT
NAME\nFile System access failed\n\nFAULT ID\n4088: EFaultId_FileSystemAccessFailedAl\n\nMEANING\nFile system access operations
like file system mounting or file opening have failed.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:\nUpdate the BTS SW, unless it is automatically updated by NetAct.\n\nFlexi Zone
Access Point, Flexi Zone SFN Antenna:\nNone\n\n\n\n\nFAULT NAME\nFirmware SW mismatch\n\nFAULT ID\n2056:
EFaultId_SwMismatchAl\n\nMEANING\nThe software update to the BTS has failed or the BTS software is
corrupted.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone
Micro TDD:\n1. Switch to the most recently-active BTS configuration.\n2. Retry the software update.\n\nFlexi Zone (Flexi Zone Access
Point):\n1. Reset the Flexi Zone Access Point to trigger SW upgrade again.\n2. Replace the Flexi Zone Access Point.\n\nFlexi Zone (Flexi
Zone Controller):\n1. Retry the embedded SW update manually. \n2. If this does not help, switch to the latest active BTS configuration.\n3.
Retry the SW update.\n\nFlexi Zone SFN Antenna:\n1. Reset the Flexi Zone SFN Antenna to trigger SW upgrade again.\n2. Replace the
Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFlexi Zone Micro BTS system clock missing\n\nFAULT ID\n4188:
EFaultId_FZMSysClkMissingAl\n\nMEANING\nSome of the generated system clock signals are missing, or the generated system clocks are
not locked.\n\nINSTRUCTIONS\nReplace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nFSP overheating\n\nFAULT ID\n4077: EFaultId_FspOverheatingAl\n\nMEANING\nThe temperature of the FSP/ABIx board has
exceeded the critical threshold value.\n\nINSTRUCTIONS\n1. Check the fans and ensure that the ambient temperature on the site is
acceptable.\n2. If that does not help, replace the alarming module.\n\n\n\n\nFAULT NAME\nFSP subunit lost\n\nFAULT ID\n4341:
EFaultId_FspSubunitLostAl\n\nMEANING\nAn FSP (ABIx) subunit is unavailable (lost).\n\nINSTRUCTIONS\nAirScale BTS FDD, AirScale
BTS TDD:\nNote: Perform the steps below in the listed order until the fault is resolved:\n1. Reset the BTS using block or unblock.\n2.
Replace the extension baseband module (ABIx) according to the fault source.\n\n\n\n\n\nFAULT NAME\nGPS Receiver alarm: control
interface not available\n\nFAULT ID\n4011: EFaultId_GPSSystemElementAl\n\nMEANING\nThe BTS has detected a communication problem
with the GPS receiver.\n\nThe fault is ignored until the GPS receiver has reached the commissioned state.\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform 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 minutes from the start of the fault prior to performing the actions
below).\n\nControl Interface not available:\n1. 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 interface. Otherwise, perform a (remote) power reset for the GPS
receiver.\n2. Perform a (remote) BTS site reset for the whole BTS.\n3. Perform a power reset for the whole BTS.\n4. 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 oxide
and other kind of dirt: the pin connection quality is good. \n5. The cable between the GPS receiver and the BTS might be faulty. Check the
situation and change the cable if needed.\n6. There might be a hardware fault in the GPS receiver. Check the operation and change the GPS
module if needed.\n7. There might be a hardware fault in the BTS System Module. Check the operation and change the System Module if
needed.\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nPerform the steps below in the listed
order until the fault disappears.\n\nControl Interface not available:\n1. 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 possible reason could be that BTS or access point, and
the GPS receiver does not support common interface. Otherwise, perform a (remote) power reset for the GPS receiver.\n2. Perform a
(remote) site reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. Perform a power reset for
29/05/2020 Alarms

major
release
the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n4. 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
Antenna.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: not tracking satellites\n\nFAULT ID\n4122:
EFaultId_GpsReceiverNotTrackingSatellitesAl\n\nMEANING\nThe fault indicates poor GPS antenna installation.\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform the steps below in the listed order until the fault
disappears.\nNot tracking satellites:\n1. 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 enough. Refer to the documentation for installations and if there are deviations with the
actual installation, re-install the GPS antenna. Note that even when the GPS antenna has a good sky visibility, the problem might be caused
by installing the GPS antenna too close to the transmitter antenna(s) of the BTS, causing disturbances for the GPS receiver. \n2. There might
be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.\n3. There might be an HW fault in the GPS
receiver. Check the operation and change the GPS module, if needed.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\nPerform the steps below in the listed order until the fault disappears.\nNot tracking satellites:\n1. 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 enough.
Refer to the documentation for installations and if there are deviations with the actual installation, re-install the GPS antenna. Note that even
when the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter
antenna(s) of the BTS, causing disturbances for the GPS receiver. \n2. There might be a malfunction in the GPS receiver. Perform a (remote)
power reset for the GPS receiver.\n\n\n\n\nFAULT NAME\nIncompatible SW version detected\n\nFAULT ID\n23:
EFaultId_IncompatibleSwVersionAl \n\nMEANING\nIncompatible software has been detected.\n\nINSTRUCTIONS\nUpdate 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
by NetAct.\n\nIn case of RF modules with factory SW loaded, SW update is a mandatory step.\n\n\n\n\nFAULT NAME\nIncorrect radio
network parameters\n\nFAULT ID\n6252: EFaultId_FailureInNetworkPlanFile\n\nMEANING\nThere was an opening, reading, or file content
problem with a radio network\nconfiguration 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, open, read, and write operations fail), as well as content problems (for example, no valid
RAML2.1 format).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi
Zone Micro TDD:\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n1. Check the commissioning parameters
with the BTS Site Manager Commissioning\nWizard.\n2. Load the correct commissioning file to the BTS.\n\nFlexi Zone, Flexi Zone SFN
Antenna: \n1. Check the Additional Info field of the fault and use it as guide to troubleshoot the faulty FZAP or Flexi Zone SFN Antenna. \n2.
Check the configuration of the FZAP or Flexi Zone SFN Antenna. \n3. Reset the Flexi Zone Access Point or Flexi Zone SFN Antenna. \n4.
Reset the Flexi Zone Controller, Flexi Zone Micro BTS, or Flexi Zone Access Point.\n\n\n\n\nFAULT NAME\nInternal MTU configuration
failure\n\nFAULT ID\n4025: EFaultId_MtuConfigurationFailureAl\n\nMEANING\nThe internal maximum transfer unit (MTU) configuration has
failed on the FSP or FBB/ABIx.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the
System Module that is causing the alarm.\n2. Replace the System Module that is causing the alarm.\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN
Antenna.\n2. Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nInvalid
configuration file\n\nFAULT ID\n4036: EFaultId_InvalidConfigurationFileAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nThe commissioning file is corrupted, or an incorrect SCF file has been detected during BTS startup as follows:\n1.
Commissioning data: The commissioning file is corrupted, or a parameter has a missing or incorrect value.\n2. 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 is
created," or invalid combination of cell parameters administrativeState and preventCellActivation.\n\nFlexi Zone Micro FDD, Flexi Zone Micro
TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThe commissioning file is missing, or an incorrect SCF file has been detected during BTS
startup as follows:\n1. Commissioning data: The commissioning file is missing, or a parameter has a missing or incorrect value.\n2. 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 cell managedObject is created," or invalid combination of cell parameters administrativeState and
preventCellActivation.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nCheck and correct the
contents of the commissioning file.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check and
correct the contents of the commissioning file.\n2. Recommission the BTS or Flexi Zone SFN Antenna with the valid commissioning
file.\n\n\n\n\nFAULT NAME\nMaster unit has lost connection to the slave unit\n\nFAULT ID\n4019:
EFaultId_KeepAliveStatusErrorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe connection to
the FSP/ABIx or DSP has been lost, or the sub-module reports an error situation.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi
Zone SFN Antenna:\nThe connection to the DSP module has been lost.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n\n1. Reset the BTS.\n2. Replace the
faulty module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS,
Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nMessage routing problem in receiver (RX)\n\nFAULT
ID\n2058: EFaultId_MuksuMsgRoutingFailedAl\n\nMEANING\nAn interrupt is generated if a message does not get routed.\n\nThis is
considered normal when DSPs are starting up and RP3 sync is done.\n\nINSTRUCTIONS\nIf OptIf is the source:\n\n1. Check the antenna
mapping to the local cells in the commissioning file.\n2. Depending which optical interface is notified as faulty check the cables between \n -
the System Module and RF Module, or the cable between the FBB module and the RF Module (Flexi BTS FDD/TDD),\n - the cable between
the ABIx module and the RF Module (AirScale BTS FDD/TDD).\n3. Block and unblock the RF Module.\n4. Perform a BTS reset. \n5. Replace
the RF module behind the optical link.\n\nFlexi BTS FDD/TDD:\nIf FSP is the source:\n1. Perform a System Module reset.\n2. If that does not
help, replace the System Module.\n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD:\nIf FBB/ABIx is the source:\n1. Perform a System
Module reset.\n2. If that does not help, replace the FBB/ABIx card.\n\n\n\n\nFAULT NAME\nNo connection to Flexi transport
submodule\n\nFAULT ID\n3511: EFaultId_NoConnectionToFtAl\n\nMEANING\nThe connection to the Flexi Transport sub-module (FTM) or
transport application is lost.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\nFlexi
BTS:\n1. Reset the site.\n2. Replace the Transport sub-module, which is located inside the System Module.\n\n\n\n\nFAULT NAME\nNo
connection to unit\n\nFAULT ID\n10: EFaultId_NoConnectionToUnitAl \n\nMEANING\nThe connection to a module that belongs to the BTS
configuration has been lost.\n\nIn case of SNMP radios, there is a problem with the optical interface or an internal fault, which results in a
radio reset.\n\nINSTRUCTIONS\n1. 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.\n\n2. Check the fault history.\n\n\n\n\nFAULT NAME\nNo downlink baseband data\n\nFAULT
ID\n1976: EFaultId_RfNoDownlinkBasebandDataAl\n\nMEANING\nThe 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 the problem might be a configuration-
related issue.\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT NAME\nNon-recoverable Synchronization Alignment Fault\n\nFAULT ID\n4273:
EFaultId_SyncAlignNonRecAl\n\nMEANING\nThe Flexi Zone Micro BTS/Flexi Zone Access Point/Flexi Zone SFN Antenna has encountered
a significant synchronization alignment fault requiring that the BTS undergo a reset to restore proper operation in a timely
fashion.\n\nINSTRUCTIONS\nCheck 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 operation when one or more synchronization reference sources are available a hardware defect
is likely present requiring that the affected FZM be replaced.\nA manual eNodeB reset and cell enable is necessary to acquire
synchronization in the RIBS configuration.\n\n\n\n\nFAULT NAME\nNot able to synchronize baseband bus with <x>\n\nFAULT ID\n1815:
EFaultId_BbBus_SyncFailedAl\n\nMEANING\nThe baseband bus synchronization towards <x> has failed.\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform the recovery in the following sequence:\n1. 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 modules.\n2. Replace the cable.\n3. Change the faulty module (FBBx/ABIx or FR).\n4. If it does not help, replace the FCM/FCT (system
module).\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nReplace the Flexi Zone Micro BTS or Flexi
29/05/2020 Alarms

major
release
Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nOven oscillator clock missing\n\nFAULT ID\n1819:
EFaultId_OcxoClkMissAl\n\nMEANING\nThe output signal of the OXCO is missing, and the FCM/FCT cannot deliver the 30.72 MHz System
Clock required by the other units.\n\nINSTRUCTIONS\n1. Block/unblock the System Module.\n\n2. Replace the System
Module.\n\n\n\n\nFAULT NAME\nOven oscillator heating failure\n\nFAULT ID\n1817: EFaultId_Ov_Osc_HeatAl \n\nMEANING\nThe 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 or it changes too fast.\n\nINSTRUCTIONS\nReplace the alarming System Module.\n\n \n\n\n\n\nFAULT NAME\nPOST
test failed\n\nFAULT ID\n69: EFaultId_Post_test_failedAl\n\nMEANING\nThe unit or module has been tested during the BTS power-on self
test (POST) and a failure has been detected.\n\nINSTRUCTIONS\n1. Reset the alarming unit or module.\n2. Remove or reinsert the alarming
unit or module.\n3. Replace the alarming unit or module.\n\n\n\n\nFAULT NAME\nPPS reference missing\n\nFAULT ID\n1898:
EFaultId_PpsRefMissAl\n\nMEANING\n1. The reference clock monitoring has detected a loss of PPS signal in the reference received from
the GPS receiver or the SyncHub master.\n2. (TDD only) The PPS signal from the SyncHub master is unusable because its reported phase
error is too large.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the GPS receiver
installation.\n2. Check the GPS receiver status.\n3. Check the connection between the GPS receiver and the FSM.\n4. Check the cable or
connection towards a SyncHub master when operating as SyncHub slave.\n5. Check the status of the SyncHub master.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the GPS receiver installation.\n2. Check the GPS receiver
status.\n\n\n\n\n\nFAULT NAME\nReference clock missing in startup\n\nFAULT ID\n4153:
EFaultId_PpsRefClcMissInStrtAl\n\nMEANING\nPhase synchronization has been commissioned at the btsSyncMode, but phase
reference\nclock is unavailable during a waiting period within the start-up procedure.\n\nINSTRUCTIONS\nDepending on the installed and
commissioned synchronization sources, see the\ncommissioned synchronization options below and perform the steps in the listed\norder
until the BTS fault indication disappears:\n\nGPS receiver (PPS source):\n1. Check the GPS receiver installation.\n2. Check the GPS
receiver status.\n3. Check the connection between the GPS receiver and FSM.\n\neNB is Sync hub slave and RF sharing is enabled:\n1.
Check if sync master provides sync signal.\n2. Check the connection between sync master and sync slave.\n3. Check sync settings at sync
slave.\n\neNB is a part of CRAN cluster:\nPerform all the steps from above.\n\nTRS reference (ToP as source):\n1. Check that the signal is
being received from the ToP Master.\n2. Check the TRS status.\n3. Check the synchronization settings of the TRS unit.\n\nBTS is Sync hub
slave and RF sharing is enabled:\n1. Remove the root cause that leads to the sync hub slave being not synchronized .\n2) 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 Element Manager.\n\n\n\n\nFAULT NAME\nRF Unit temperature too high\n\nFAULT ID\n4185:
EFaultId_RfTempTooHighAl\n\nMEANING\nThe validated sensor temperature on the PA is higher than the predefined HW
temperature.\n\nINSTRUCTIONS\n1. Validate if the ambient temperature is within the specifications and if no foreign debris has accumulated
on the unit. \n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. If those do not help, replace the
BTS.\n\n\n\n\nFAULT NAME\nSFN Antenna blocked\n\nFAULT ID\n4348: EFaultId_AntBlockedAl\n\nMEANING\nThe 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
maintenance task.\n\nINSTRUCTIONS\nUnblock the Flexi Zone SFN Antenna to cancel the fault.\n\n\n\n\nFAULT NAME\nSFN Antenna cell
deletion failure\n\nFAULT ID\n4356: EFaultId_SfnAntCellDeletionFailureAl\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access
Point failed to delete the cell on the Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Perform a reset of the Flexi Zone SFN Antenna.\n2. If
step above does not help, perform a reset of the BTS/FZAP.\n3. If steps above do not help, replace the alarming module.\n\n\n\n\nFAULT
NAME\nSFN Antenna cell reconfiguration failure\n\nFAULT ID\n4358: EFaultId_SfnAntCellReconfigurationFailureAl\n\nMEANING\nThe Flexi
Zone Micro BTS or Flexi Zone Access Point failed to reconfigure the cell on the Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Perform a
reset of the Flexi Zone SFN Antenna.\n2. If step above does not help, perform a reset of the BTS/FZAP.\n3. If steps above do not help,
replace the alarming module.\n\n\n\n\nFAULT NAME\nSFN Antenna cell setup failure\n\nFAULT ID\n4355:
EFaultId_SfnAntCellSetupFailureAl\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access Point failed to setup the cell on the Flexi
Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Perform a reset of the Flexi Zone SFN Antenna.\n2. If step above does not help, perform a reset
of the BTS/FZAP.\n3. If steps above do not help, replace the alarming module.\n\n\n\n\nFAULT NAME\nSFN Antenna cell shutdown
failure\n\nFAULT ID\n4357: EFaultId_SfnAntCellShutdownFailureAl\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access Point
failed to shut down the cell on the Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Perform a reset of the Flexi Zone SFN Antenna.\n2. If
step above does not help, perform a reset of the BTS/FZAP.\n3. If steps above do not help, replace the alarming module.\n\n\n\n\nFAULT
NAME\nSFN Antenna Configuration Failed\n\nFAULT ID\n4362: EFaultId_AntConfFailedAl\n\nMEANING\nThe 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 only
reported for non-fatal SW errors, that is, the Flexi Zone Micro BTS or Flexi Zone Access Point SW can still provide service to other Flexi Zone
SFN Antennas.\n\nINSTRUCTIONS\n1. Check all alarms posted by the Flexi Zone SFN Antenna prior to this fault.\n2. Check the
configuration of the Flexi Zone SFN Antenna against similarly-configured Flexi Zone SFN Antennas of the same type.\n3. Reset the Flexi
Zone SFN Antenna.\n4. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point.\n\n\n\n\nFAULT NAME\nSFN Antenna registration
failure\n\nFAULT ID\n4354: EFaultId_SfnAntRegistrationFailureAl\n\nMEANING\nTHe Flexi Zone Micro BTS or Flexi Zone Access Point
failed to register the Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Perform a reset of the Flexi Zone SFN Antenna.\n2. If step above
does not help, perform a reset of the BTS/FZAP.\n3. If steps above do not help, replace the alarming module.\n\n\n\n\nFAULT NAME\nSFN
Master initialization failure\n\nFAULT ID\n4359: EFaultId_PhyProxyIpConfigAl\n\nMEANING\nSFN Master PhyProxy module initialization has
failed.\n\n\nINSTRUCTIONS\n1. Perform a reset of the BTS or FZAP.\n2. If step above does not help, replace the alarming
module.\n\n\n\n\nFAULT NAME\nSumming service default initialization failed\n\nFAULT ID\n4092:
EFaultId_MurkkuDefaultInitFailedAl\n\nMEANING\nThe summing service default configuration has failed.\n\nINSTRUCTIONS\nIf FSM is the
fault source:\n1. Reset the system module. (Note that all cells, including those that are operational, will be reset.)\n2. If a reset does not
resolve the fault situation, replace the system module.\n\nIf FBB/ABIx is the fault source:\n1. Reset the system module. (Note that all cells,
including those that are operational, will be reset.)\n2. If a reset does not resolve the fault situation, replace the FBBx/ABIx
module.\n\n\n\n\nFAULT NAME\nSW corrupted\n\nFAULT ID\n1850: EFaultId_SwCorruptedAl\n\nMEANING\nA corrupted SW file in the
FLASH has been detected.\nThe unit cannot complete start-up.\n\nINSTRUCTIONS\nUpdate the SW to the BTS.\n\n\n\n\nFAULT
NAME\nSWDistributionFailure\n\nFAULT ID\n4259: EFaultId_SwDistributionAl\n\nMEANING\nThe 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 startup, or some other
internal failure at the Flexi Zone Access Point.\n\nINSTRUCTIONS\n1. When the Flexi Zone Access Point (FZAP) has failed to join the zone,
restart HTTPD RG (through SCLI) and then reset the failed FZAPs.\n2. When the SW upgrade has failed, retry the software load.\n3. Restart
the Zone Controller.\n4. Replace the faulty device.\n\n\n\n\nFAULT NAME\nSW fallback\n\nFAULT ID\n4082:
EfaultId_FallbackDueToMaxResetLoopCounterValueAl\n4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl\n4085:
EfaultId_FallbackDueToTransportRequestAl\n\nMEANING\n4082:\n\nThe source unit has reached the maximum number of reset retries, that
is, the source unit cannot successfully finish start-up after the SW update.\nIf BTS O&M has detected that the BTS can start with the
previously-active SW version - BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW
units in the BTS and\n2. the BTS is up and running.\nOtherwise:\n1. the previously-active SW version is not running in all HW units in the
BTS and\n2. the BTS is not up and running (recovery SW update is still supported).\n\nFault 4082 for FSP fallback can be canceled due to
SW upgrade on FSP only.\nIn this case, an FSP reset to activate the new version of SW may cancel the fault.\nThe state of the fault is
start/cancel for FSP SW fallback only.\n\n4083:\n\nThe 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 failure or the SCF check tool in BTS OM has detected SCF
failure and the BTS cannot operate with that SCF.\n\nIf BTS O&M has detected that the BTS can start with the previously-active SW
version - BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW units in the BTS and\n2.
the BTS is up and running. \nOtherwise:\n1. the previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not
up and running (recovery SW update is still supported).\n\n\n4085:\n\nTransport SW on the source unit has indicated the need for a software
29/05/2020 Alarms

major
release
fallback.\nIf BTS O&M has detected that the BTS can start with the previously-active SW version - BTS O&M processed consistent
fallback and\n1. the previously-active SW version is running in all HW units in the BTS and\n2. the BTS is up and running. \nOtherwise:\n1.
the previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not up and running (recovery SW update is still
supported).\n\nINSTRUCTIONS\nThe BTS start-up was not successful. \n\nIf 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 activation for the BTS to the SW version
running on BTS. If this is not possible, the operator must update the SW update immediate activation for the BTS to the SW version running
on the BTS. After successful SW update:\n1. The BTS will be onAir with the previously-running SW.\n2. The SW will be consistent in
BTS.\n3. The BTS will report active SW fallback fault but with alarm 7651.\n\nIf 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 successful SW update:\n1. The BTS will be
onAir with requested SW running.\n2. The SW will be consistent in BTS.\n3. SW fallback fault and the related alarm will be canceled.\n\nFlexi
Zone:\nNone\n\n\n\n\nFAULT NAME\nSynchronization holdover time expired\n\nFAULT ID\n4187:
EFaultId_SyncHoldoverTimeExpiredAl\n\nMEANING\nThe 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 of all configured synchronization reference sources) for a
period beyond which the carrier frequency accuracy or phase alignment requirements can be guaranteed.\n\nINSTRUCTIONS\nAddress
faults associated with any and all configured synchronization reference sources. This fault will clear, and RF transmissions can resume when
the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna has one (1) or more available synchronization reference
sources.\n\n\n\n\nFAULT NAME\nSynchronization master missing\n\nFAULT ID\n4114:
EFaultId_SynchronizationMasterMissingAl\n\nMEANING\nSynchronization is lost when the system module is working as a synchronization
slave system module. This usually indicates that a synchronization master system module has been reset, or that there is a problem with the
optical cable between the master system module and the slave system module.\n\nINSTRUCTIONS\nPerform the steps in the listed order
until the fault is resolved.\n\n1. Wait for the startup to be completed if a synchronization master system module has been reset.\n2. If fault
1858: EFaultId_FaultyFcmConfigurationAl is active, check the RP3-01 optical cable between the synchronization master and synchronization
slave system module and follow the instructions for fault 1858.\n3. Check the alarms in the synchronization master system module and act
accordingly.\n4. Reset the synchronization master system module.\n5. 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 configured on the master system module,
supported by the radio module(s) might be temporary disabled.\n\n\n\n\nFAULT NAME\nSystem Module failure\n\nFAULT ID\n3000:
EFaultId_SystemModuleFailure\n\nMEANING\nThe BTS has detected an abnormal operation or a failure in the internal functionality of the
System Module.\n\n\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System Module.\n2. Replace the System Module.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi
Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nTD-SCDMA major alarm\n\nFAULT ID\n4178: EFaultId_TdscdmaMajorAl\n\nMEANING\nThe Ir router has reported a major problem
with TD-SCDMA. The TD-LTE performance is affected, and cells are disabled.\n\nINSTRUCTIONS\nCheck the TD-SCDMA for active
alarms.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT ID\n3040: EFaultId_TemperatureAlarm\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n\n1. Check the other
BTS faults and act accordingly.\n\n2. 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, that is, the BTS modules are not covered with anything. If the ambient
temperature is too low, it takes a while for the BTS or the other modules to heat themselves to the threshold value.\n\n3. Block and unblock
the alarming module to reset it.\n\n4. Replace the alarming module.\n\n\n\n\nFAULT NAME\nToggling: <Fault name>\n\nFAULT ID\n4026:
Snapshot.\n\n\n\n\nFAULT NAME\nTransmission clock missing\n\nFAULT ID\n1816: EFaultId_Trans_Clk_MsgAl\n\nMEANING\nThe
reference clock monitoring has detected a loss of signal in the reference received from the FT.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check that the signal is being received from the reference clock source.\n2. Check the
TRS status.\n3. Check the synchronization settings of the TRS unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\nCheck the backhaul connection.\n\n\n\n\nFAULT NAME\nUnit initialization failure\n\nFAULT ID\n4040:
EFaultId_InitFaultManAl\n\nMEANING\nA module initialization has failed.\n\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale
BTS FDD, AirScale BTS TDD:\n\n1. Block/unblock the alarming module.\n\n2. 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 that does not help, perform a power-off
reset. \n\n3. If steps 1 and 2 do not help, replace the alarming module.\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\n\n1. Reset the BTS.\n\n2. Perform a power-off reset.\n\n3. If steps 1 and 2 do not help, replace the alarming
module.\n\n\n\n\nFAULT NAME\nUnit initialization failure\n\nFAULT ID\n4208: EFaultId_RromIpConfigAl \n\nMEANING\nThe RROM TRS IP
configuring or reconfiguring has failed.\n\nINSTRUCTIONS\nCheck the transport-related configuration (C-Plane address, U-Plane address,
and Transport network ID). If the fault was raised at startup, correct the configuration and reset the BTS. If the fault was raised during eNB
runtime, correct the configuration and apply the changes at the BTS.\n\n\n\n\nFAULT NAME\nUnit not supported by current BTS SW
version\n\nFAULT ID\n95: EFaultId_NotSupportedUnit\n\nMEANING\nAn 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 does not support the new unit version, is in
use.\n\nINSTRUCTIONS\n1. Upgrade the system module SW.\n2. Replace the unit.\n\n\n\n\n\nFAULT NAME\nUnit SW download
failed\n\nFAULT ID\n6: EFaultId_SwDownloadAl\n\nMEANING\nA software update in the module or submodule has
failed.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro
TDD, Flexi Zone (Flexi Zone Controller):\n1. Download the BTS SW again.\n2. Reset (block and unblock) the BTS.\n3. If step 2 does not
help, replace the alarming module.\n\nFlexi Zone (Flexi Zone Access Point):\n1. Check other alarms associated with software upgrade.\n2.
Reset the AP to trigger software upgrade.\n3. If step 2 does not help, replace the Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1.
Check other alarms associated with software upgrade.\n2. Reset the SFN ANT to trigger software upgrade.\n3. If step 2 does not help,
replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nUnit synchronization failed\n\nFAULT ID\n16:
EFaultId_SynchronizationAl\n\nMEANING\nThe FCM or FSP, FCT (HW rel.4) or ABIx synchronization has failed.\n\n\nINSTRUCTIONS\n1.
Block or unblock the module that is causing the alarm.\n2. Replace the module that is causing the alarm.\n\n\n\n\nFAULT NAME\nUnknown
HW resource\n\nFAULT ID\n94: EFaultId_UnknownUnitType\n\nMEANING\nA unit cannot be identified by its product code or by its physical
device address (object ID).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nReplace the
alarming unit or module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nReplace the BTS or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nU-Plane Computing Environment Container Failure\n\nFAULT ID\n4339:
EFaultId_UplaneComputingEnvironmentContainerFailureAl\n\nMEANING\nAn error has been detected during the start-up or normal run-time
operation of the 2CE virtual container.\n\nINSTRUCTIONS\nPerform the following steps in the listed order until the fault disappears:\n1.
Reset the Flexi Zone Micro BTS/Flexi Zone Access Point.\n2. Replace the Flexi Zone Micro BTS/Flexi Zone Access Point.\n\n\n\n\nFAULT
NAME\nValidation of signed file failed\n\nFAULT ID\n4145: EFaultId_SignatureValidationFailedAl\n\nMEANING\nSW file validation against its
signature has failed.\n\nINSTRUCTIONS\nUpdate the BTS to the required SW version.\nIf 7650 is active, immediate activation is
mandatory.\n\n\n\n\nFAULT NAME\nZ1 Link Failure\n\nFAULT ID\n4258: EFaultId_Z1LinkFailureAl\n\nMEANING\nThe Z1 link between the
29/05/2020 Alarms

major
release
Flexi Zone Controller and the Flexi Zone Access Point is out of service.\n\nINSTRUCTIONS\nCheck all the alarms posted by the Flexi Zone
Access Point prior to the Z1 link failure.\n\n\n\n\nFAULT NAME\nZ3 Link Failure\n\nFAULT ID\n4344:
EFaultId_Z3LinkFailureAl\n\nMEANING\nThe Z3 link between the Flexi Zone Micro BTS, or Flexi Zone Access Point, and the Flexi Zone SFN
Antenna is out of service.\n\nINSTRUCTIONS\nCheck all the alarms posted by the Flexi Zone SFN Antenna prior to the Z3 link failure."
Table 38-9: BASE_STATION_LICENSE_LIMITATION

major
release
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\n\nA 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.\n\nThe effect of the fault on the functioning of the network
element depends on\nthe fault description. For more information, see base station fault descriptions\nin LTE System Libraries.\n\nDo not
cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
Remedial action: FAULT NAME\nActive users license limitation\n\nFAULT ID\n4337: EFaultId_ActiveUsersLimitAl \n\nMEANING\nThe eNB
enters capacity limited mode due to missing licenses. Calls from excess users will be rejected except for handover and emergency
calls.\n\nINSTRUCTIONS\nAdd licenses to the Centralized License Server to avoid call limitation.\nSee "Centralized License Server Help"
document in NOLS for details.\n\n\n\n\n\nFAULT NAME\nCell Shutdown Due To Baseband Capacity License Limit\n\nFAULT ID\n4349:
EFaultId_CellShutdownDueToBasebandCapacityLicenseLimitAl\n\nMEANING\nThe cell is shut down because it occupies baseband capacity
that is over the licensed limit.\n\n\nINSTRUCTIONS\nAdd licenses to the Centralized License Server to avoid the traffic limitation.\nSee
"Centralized License Server Help" document in NOLS for details.\n\n\n\n\n\nFAULT NAME\nIP Traffic Capacity Limit\n\nFAULT ID\n4293:
EFaultId_IPTrafficCapacityLimitAl\n\nMEANING\nThe user's eNB IP traffic is throttled because of a missing
license.\n\nINSTRUCTIONS\nRead 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.\n\nAdd licenses to CLS to avoid the traffic limitation.\n\nIf licenses are not added, the
level will be decreased to the lowest level, which is 50% of peak rate.
Table 38-10: BASE_STATION_NOTIFICATION

major
release
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\n\nA minor fault (or faults) has occurred in the base station.\n\nCheck the reason for the fault
from the supplementary text field of the alarm.\n\nThe 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.\n\nDo not cancel the alarm. The system
automatically cancels the alarm when the fault has been corrected.
site reset is required to cancel the alarm. If the site reset or module block/unblock does not help, replace the faulty unit/module (see source of
the alarm and instructions fields of the corresponding alarms). \n\nBelow 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 fault descriptions refer to LTE System Libraries. The
BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local customer support. \n\n----
-------------------------------------------\nFAULT NAME\n# autonomous reset as recovery action\n\nFAULT ID\n52:
EFaultId_UnitAutonomousResetAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe 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. \nIn case of an RF
module reset in RF chaining configuration, the BTS also resets all RF modules that are further in the chain.\n\nFlexi Zone Micro FDD, Flexi
Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThe BTS tries to recover from a fault situation by performing a site
reset.\n\nINSTRUCTIONS\nCheck the fault history and other active faults of the unit.\n\nNote: This fault does not require any (special)
actions.\n\n\n\n\nFAULT NAME\n10b8b coding error in optical interface device\n\nFAULT ID\n2004:
EFaultId_OIC_LVDSRecAl\n\nMEANING\nThe fiber cable is experiencing interference; data transmission is faulty.\n\nA physical connection
failure between the optical interface and the summing function has occurred.\n\nThe 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
module.\n\n\nINSTRUCTIONS\nNote: Perform the steps in the listed order until the fault is resolved.\n\n1. Reset the radio module behind the
cable reported as the fault source by blocking/unblocking it. \n2. Reset the system module. \n3. Replace the SFP on the radio module port
where the cable reported as fault source is terminated.\n4. Replace the SFP on the system module or extension baseband module port
where the cable reported as fault source is terminated.\n5. Replace the optical cable reported as fault source.\n6. Replace the radio module
behind the cable reported as fault source.\n7. 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, replace the extension baseband module (if the fault is reported on the cable
connected to the baseband module) or the system module (if the fault is reported on the cable connected to the system
module).\n\n\n\n\nFAULT NAME\n2M external reference missing\n\nFAULT ID\n1899: EFaultId_2MExtRefMissAl\n\nMEANING\nThe
29/05/2020 Alarms

major
release
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 Module.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears.\n\n1.
Check the cabling (connected to Sync In interface).\n\n2. Check if the 2.048 MHz reference source is working normally, and the 2.048 MHz
signal is available.\n\n3. Replace the alarming module.\n\n\n\n\nFAULT NAME\n3GPP/AISG communication administratively
disabled\n\nFAULT ID\n4142: EFaultId_Communication3gppAdministrativelyDisabledAl\n\nMEANING\nThe HDLC link has been disabled for
the reporting Antenna Line or IUANT port.\n\nINSTRUCTIONS\nEnable the parameter "Communication3gppEnabled" for the reporting
Antenna Line to revert changes.\n\n\n\n\nFAULT NAME\nAbnormal CPRI interface to next hop <OptIf ID>\n\nFAULT ID\n1974:
EFaultId_AbnormalCpriInterfaceToNextHopAl\n\nMEANING\nThe optical interface is not working properly.\nThe CPRI transmission is not
working properly.\nThis fault is valid only for radio modules in a chain configuration.\nNote: The Optif is from the perspective of the previous
radio.\n\nINSTRUCTIONS\n1. 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. \n2. Reset the RF module. \n3. If that does not help, block or unblock the site. \n4. 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).\n\n\n\n\nFAULT NAME\nAbnormal CPRI interface to upper hop <OptIf ID>\n\nFAULT ID\n1965:
EFaultId_AbnormalCpriInterfaceToUpperHopAl\n\nMEANING\nThe optical interface does not work properly. CPRI transmission to the upper
hop does not work properly.\n\nINSTRUCTIONS\nExecute the following steps in the ordered sequence. If any of the step does not help,
execute the next one:\n\n1. Reset the radio module behind the cable reported as the fault source. \n2. Reset the system module. \n3.
Replace the SFP on the radio module port where the cable reported as the fault source is terminated.\n4. Replace the SFP on the system
module or the extension baseband module port where the cable reported as the fault source is terminated.\n5. Replace the optical cable
reported as the fault source.\n6. Replace the radio module behind the cable reported as the fault source.\n7. 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 the baseband
module) or the system module (if the fault is reported on the cable connected to the system module).\n\n\n\n\nFAULT NAME\nAbnormal
reception on SFP to next hop <OptIf ID>\n\nFAULT ID\n1973: EFaultId_AbnormalReceptionOnSfpToNextHopAl\n\nMEANING\nThe optical
interface is not working properly.\nThis fault is valid only for radio modules in a chain configuration.\nNote: The Optif is from the perspective of
the previous radio.\n\nINSTRUCTIONS\n1. 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. \n2. Reset the RF module. \n3. If that does not help, block or unblock the site. \n4. If that does
not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nAbnormal reception on SFP to upper hop <OptIf
ID>\n\nFAULT ID\n1971: EFaultId_AbnormalReceptionOnSfpToUpperHopAl\n\nMEANING\nThe 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
configuration.\n\nINSTRUCTIONS\n1. Check the cables between the system module and the RF module. \n2. Reset the RF module. \n3. If
those do not help, block and unblock the site. \n4. If those do not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT
NAME\nAccess panel port(s) enabled\n\nFAULT ID\n234: EFaultId_AccessPanelPortEnaAl\n\nMEANING\nThe FlexiZone Micro BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna has detected that one or more access panel ports is enabled.\n\nThis state of elevated
security risk is not expected in field conditions.\n\nINSTRUCTIONS\n1. Determine if this event is expected. Investigate audit logs as
necessary.\n2. If this action is unexpected, use SSH to disable access panel port(s) and/or physically inspect site installation.\n\n\n\n\nFAULT
NAME\nALD port configuration failure\n\nFAULT ID\n4255: EFaultId_AldPortFailureAl\n\nMEANING\nThe Radio Module has detected switch
configuration mismatch on the ALD port.\n\nINSTRUCTIONS\n1. Check the configuration of the ALD port.\n\n2. The alarm is cancelled only
when the RF Module is reset, or the BTS is reset.\n\n\n\n\nFAULT NAME\nALD Port power failure\n\nFAULT ID\n4069:
EFaultId_Rs485PowerFailureAl\n\nMEANING\nOBSAI interface:\nThe Radio Module has detected an over-current condition in the RS485
IUANT port.\nSome 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.\n\nCPRI/Ir interface:\n\nOvercurrent case:\nThe Radio Module has detected over-current on the ALD port. Some
antenna line device is causing overload. Depending on hardware implementation, antenna line devices powered by the RS485 IUANT, or
powered by the antenna line, are out of order.\n\nUndercurrent case:\nThe Radio Module has detected undercurrent on the ALD port. There
is a problem with ALD port connection. Depending on hardware implementation, antenna line devices powered by the RS485 IUANT, or
powered by the antenna line, are out of order.\n\nINSTRUCTIONS\n1. Check the ALD interface and antenna line devices. Fix or replace the
faulty parts or devices.\n\n2. The alarm is cancelled only when the RF Module is reset, or if the BTS is reset.\n\n\n\n\nFAULT
NAME\nAntenna line device configuration failure\n\nFAULT ID\n1888: EFaultId_AlConfigurationFailureAl\n\nMEANING\nAntenna Line Device
is not properly configured.\nAntenna Line Device set-up fails, for example due to protocol error or interoperability
problem.\n\nINSTRUCTIONS\n1. Check/correct the antenna line configuration.\n\n2. If that does not help, replace the antenna line
device.\n\n\n\n\nFAULT NAME\nAntenna Line Device failure\n\nFAULT ID\n3100: EFaultId_AntennaLineFailure\n\nMEANING\nThe System
Module, or the device itself, has detected an abnormal operation or a failure in the antenna line device.\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the BTS fault disappears.\n\n1. Check the antenna line and antenna line devices. Ensure that the
antenna line connectors are in the right torque.\n\n2. Block and unblock the alarming RF module to reset it.\n\n3. Replace the faulty parts
and/or devices along the antenna line.\n\n4. Replace the RF Module.\n\n\n\n\nFAULT NAME\nAntenna line device HW failure\n\nFAULT
ID\n1847: EFaultId_HardwareErrorAl\n\nMEANING\nA hardware failure has been reported by ALD (RET, MHA).\n\nINSTRUCTIONS\n1.
Reset the radio module to give a power-off reset to the antenna line devices.\n2. If step 1 does not help, replace the antenna line
device.\n\n\n\n\nFAULT NAME\nAntenna line device missing software\n\nFAULT ID\n1848: EFaultId_WorkingSoftwareMissingAl
\n\nMEANING\nThe unit is in download mode state. This fault is returned when an unsupported procedure occurs in download
mode.\n\nINSTRUCTIONS\n1. Upload the correct SW to the device (if possible) or perform an ALD power reset (for example, by RF module
reset).\n2. If that does not help, replace the antenna line device.\n\n\n\n\nFAULT NAME\nAntenna line device operation failure\n\nFAULT
ID\n4239: EFaultId_AldOperationFailureAl\n\nMEANING\nThe radio module indicated an error upon execution of remote electrical tilt (RET)-
related logical operation.\n\nINSTRUCTIONS\n1. Check the antenna line and RET devices. Fix or replace the faulty parts or devices.\n2. To
cancel the alarm, perform an RF module startup or BTS reset.\n\n\n\n\nFAULT NAME\nAntenna Line Device Operation Failure\n\nFAULT
ID\n1871: EFaultId_BusyAl\n1872: EFaultId_FormatErrorAl \n1873: EFaultId_UnsupportedProcedureAl \n1874: EFaultId_OutOfRangeAl
\n\nMEANING\nThe device is not working properly, the configuration is not valid, or a given parameter is incorrect.\n\nINSTRUCTIONS\n1.
Check the functionality of the antenna line device.\n\n2. Check the compatibility between the antenna line device and the BTS.\n\n3. Check
that the given parameters are in the valid range.\n\n\n\n\nFAULT NAME\nAntenna line device SW download failure\n\nFAULT ID\n4047:
EFaultId_FileCrcErrorAl\n4048: EFaultId_FileContentErrorAl\n\nMEANING\nAn SW download to an antenna line device has failed because
of an incorrect checksum or file format.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears:\n\n1. Check the SW package.\n2. Download the SW to the antenna line device again.\n\n\n\n\nFAULT NAME\nAntenna line
failure\n\nFAULT ID\n1836: EFaultId_ALOvercurrentAl\n\nMEANING\nThe 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 causing overload. All antenna line devices powered
by the antenna line are out of order.\n\nINSTRUCTIONS\n1. Check the antenna line and antenna line devices. Fix or replace the faulty parts
or devices.\n2. 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 cancel automatically after the fault condition is cleared regardless of when the condition is cleared. If the fault
is not canceled automatically, the fault is canceled when the RF module is blocked or unblocked, or when the RF module or the BTS is reset.
\n3. For all other radios, the fault is canceled only when the RF module or the BTS is reset.\n\n\n\n\nFAULT NAME\nAntenna line operation
degraded\n\nFAULT ID\n4046: EFaultId_AntennaLineDegradedAl\n\nMEANING\nAn alarm message has been received from the antenna
line device. The antenna line operation is degraded.\n\nINSTRUCTIONS\nPerform the following steps on the MasterRAT side:\n\n1. Check
the antenna line and antenna line device that is causing the alarm.\n2. Fix or replace the faulty parts and devices.\n\n\n\n\nFAULT
NAME\nAntenna line setup failure\n\nFAULT ID\n4238: EFaultId_AntennaLineSetupFailureAl\n\nMEANING\nAn antenna line or antenna line
device is not properly configured.\nThe antenna line setup and device scan fails because of exceeded time limit or too many ALDs detected
from the ALD port.\nThe radio module reports the fault when the antenna line starts.\n\nINSTRUCTIONS\n1. Check or correct the RET
29/05/2020 Alarms

major
release
device configuration (that is, the RET connected to the radio module generating the alarm).\n2. If that does not help, replace the antenna line
device.\n\n\n\n\nFAULT NAME\nAntenna line switched off due to high VSWR\n\nFAULT ID\n1957:
EFaultId_AntennaLineSwitchedOffAl\n\nMEANING\nTx in the RF module has been switched off to protect the radio module hardware, which
might be damaged because of high-reflection (VSWR) conditions.\n\nINSTRUCTIONS\n1. The VSWR measured at the RF (transmitter)
exceeds values that are acceptable by the RF module.\n2. Check the impedance matching of the Antenna Line System (replace elements
that cause mismatch).\n3. To check if the above-mentioned steps have solved the problem, reset the RF module.\n\n*Forcing the RF HW to
work under such conditions might result in permanent damage to the RF HW.\n\n\n\n\nFAULT NAME\nAP Discovery Failure Due to
Misconfiguration\n\nFAULT ID\n4281: EFaultId_ApDiscFailMisconf\n\nMEANING\nThis fault denotes the inability to identify the FZAP based
on the information provisioned in APMOD.\n\nINSTRUCTIONS\n1. Verify if the APMOD provisioning data have been correctly entered.\n2.
Verify if the siteID provisioned on the FZAP was entered correctly.\n\n\n\n\n\nFAULT NAME\nBaseband bus configuration of <x> was
rejected\n\nFAULT ID\n1811: EFaultId_BbBus_ConfFailedAl\n\nMEANING\nThe baseband-bus-related configuration of <x> has been
rejected by the HW SW, DSP, or RF SW.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nReplace the alarming module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Download the correct configuration.\n2. Reset the
BTS.\n3. Replace the BTS.\n\nFlexi Zone:\n1. Download the correct configuration.\n2. Reset the Flexi Zone Access Point from the
BTSSM.\n3. Replace the Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1. Download the correct configuration.\n2. Reset the Flexi
Zone SFN Antenna from the BTSSM.\n3. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nBaseband bus failure\n\nFAULT
ID\n3020: EFaultId_BaseBandBusFailure\n\nMEANING\nThe Flexi BTS has detected an abnormal operation or a failure in the BTS\ninternal
or external (optical link) baseband bus. The failure cannot be\nattributed to a specific module and there are several possible fault
does not clear the fault situation, replace the alarming System Module.\n\n\n\n\nFAULT NAME\nBB bus reception error (summing
device)\n\nFAULT ID\n2016: EFaultId_Muksu_SMTimeOffAl\n\nMEANING\nThe 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 set into the wrong place (PI delay), or the
data itself is in the wrong place.\n\nINSTRUCTIONS\n1. 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 and the FBBx module.\n\n2. Replace the unit
that causes the alarm (system module or FBBx/ABIx).\n\n\n\n\nFAULT NAME\nBB bus transmission error\n\nFAULT ID\n2017:
the system module.\n\n3. Replace the alarming module (system module).\n\n\n\n\nFAULT NAME\nBoot configuration inconsistency
detected\n\nFAULT ID\n4102: EFaultId_BootConfigurationInconsistencyAl\n\nMEANING\nDuring 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 compared at these periods:\n-
before SW download\n- during SW activation, before active and passive SW switch\n- during start-up\n\nINSTRUCTIONS\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD:\n1. Block/unblock the Flexi Zone Micro BTS to reset.\n2. If blocking or unblocking the Flexi Zone Micro BTS
does not solve the problem, replace the faulty Flexi Zone Micro BTS.\n\nFlexi Zone Access Point, Flexi Zone SFN
Antenna:\nNone\n\n\n\n\nFAULT NAME\nBTS file error\n\nFAULT ID\n1802: EFaultId_FileRequestFlashAl\n\nMEANING\nA software
download to FSP, DSP, ABIx or FR has failed.\n\nINSTRUCTIONS\nNote: Perform the following steps in the listed order until the fault
disappears:\n\n1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as
template.\n\n2. Download two different software packages so that the faulty file is removed from the BTS.\n\n3. Download the software
again.\n\n4. Replace the System Module.\n\n\n\n\nFAULT NAME\nBTS internal SW management problem\n\nFAULT ID\n3090:
files.\n\n\n\n\nFAULT NAME\nBTS is uncommissioned\n\nFAULT ID\n4030: EFaultId_NoCommDataAl\n\nMEANING\nFlexi BTS FDD, Flexi
BTS TDD:, AirScale BTS FDD, AirScale BTS TDD\nThe commissioning file download has not been started from the BTS Site Manager or
from NetAct during auto-configuration. Either the auto-configuration might not be enabled in the NetAct, or the commissioning file is not
found.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Controller:\nThe commissioning file download has not been started from
the BTS Site Manager or from NetAct during auto-configuration. The auto-configuration might not be enabled in the NetAct, the license is
missing, or the commissioning file is not found.\n\nFlexi Zone Access Point:\nThe 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 might not be successful. This fault is visible
only at the BTSSM that is connected to Flexi Zone Access.\n\nFlexi Zone SFN Antenna:\nThe 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 Flexi Zone Micro
BTS or Flexi Zone Access Point might not be successful. This fault is visible only at the BTSSM that is connected to the Flexi Zone SFN
Antenna.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone Controller:\n1. In NetAct, check if auto-configuration is enabled and if the required license and commissioning files are
available.\n2. Check the auto-connection or auto-configuration information using the BTS Site Manager.\n3. Load the correct commissioning
file to the BTS.\n\nFlexi Zone Access Point:\n1. Check the connectivity of the access point to the Flexi Zone Controller.\n2. Reset the Flexi
Zone Access Point from the BTSSM connected to the FZAP.\n3. Reset the Flexi Zone Controller.\n4. Contact Nokia.\n\nFlexi Zone SFN
Antenna:\n1. Check the connectivity of the Flexi Zone SFN Antenna to the Flexi Zone Micro BTS or Flexi Zone Access Point.\n2. Reset the
Flexi Zone SFN Antenna from the BTSSM.\n3. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point.\n4. Contact
Nokia.\n\n\n\n\nFAULT NAME\nBTS Location Lock failed\n\nFAULT ID\n4283: EFaultId_LocationLockFailed\n\nMEANING\nThe Location
Lock has failed. \n\n1. The BTS was not able to acquire Location Lock evidence data after feature activation. Depending on the configured
detection methods: \n- The BTS might time out while waiting for GNSS coordinates. \n- 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 hop.\n\n2. The BTS has failed to
update the Location Lock evidence file because of a flash file system error.\n\nINSTRUCTIONS\n1. If the BTS cannot acquire GNSS
coordinates: \n- Disable the Location Lock feature. \n- Fix the problem with the GNSS receiver. Alternatively, configure the detection method
to a method other than GNSS.\n- Re-enable the Location Lock feature.\n\n2. If the BTS cannot acquire network configuration parameters:\n-
Disable the Location Lock feature.\n- Fix the problem with network configuration. \n- Re-enable the Location Lock feature. \n\n3. If the BTS
failed to update the Location Lock evidence:\n- Disable and then re-enable the Location Lock feature.\n- If the problem persists, replace the
faulty device.\n\n\n\n\nFAULT NAME\nBTS Location Lock violation detected\n\nFAULT ID\n4284:
EFaultId_LocationLockViolation\n\nMEANING\nA Location Lock violation has been detected after a BTS reboot.\n1. 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.\n2. The
29/05/2020 Alarms

major
release
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 values that are stored in the Location Lock evidence file.\n\nThe integrity check of the Location Lock evidence data
has failed after a BTS reboot.\n1. The Location Lock evidence file is missing.\n2. The Location Lock evidence file has failed P7 signature
validation.\n\nINSTRUCTIONS\n1. If the BTS detects a Location Lock violation:\n- If the BTS has been relocated without authorization, the
alarm is expected.\n- If the BTS relocation is authorized, disable the Location Lock feature and then re-enable it to reacquire the correct
Location Lock evidence.\n2. If the BTS detects a missing or corrupted Location Lock evidence:\n- Disable the Location Lock feature and then
re-enable it in order to recover.\n- If, during the above operation, the BTS has reported fault 4283:EFaultId_LocationLockFailed, replace the
faulty device.\n\n\n\n\nFAULT NAME\nBTS power cycle detected\n\nFAULT ID\n237: EFaultId_PowerCycleDetectedAl\n\nMEANING\nA
power cycle is detected. This fault is raised at BTS startup after the power cycle.\n\nINSTRUCTIONS\nIf the problem persists, verify the
power source of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nBTS power voltage
rail failure\n\nFAULT ID\n4190: EFaultId_PowerVoltageRailFailureAl \n\nMEANING\nThe potential power down condition of the Flexi Zone
Micro BTS or Flexi Zone Access Point.\n\nINSTRUCTIONS\n1. Check the power supply. \n2. 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 device is powered down.\n3.
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.\n\n\n\n\nFAULT NAME\nBTS reference clock missing\n\nFAULT ID\n3080: EFaultId_BtsReferenceClockMissing\n\nMEANING\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThis BTS fault indication is generated if the reference clock monitoring
function of the BTS does not receive the configured synchronization reference signal, if all the synchronization reference signals are missing,
or if the BTS has been in holdover mode and holdover time has run out (TDD only). \n\nBackground information:\n\nThere is configurable
synchronization priority list in the FlexiBTS, AirScaleBTS.\n\nNormally, 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 sources are checked against the reference source priority
list in the BTS commissioning file and deviations regarding the missing source generate a faults.\n\nThe 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 Timing over Packet
(ToP) in which the timing information to BTS(s) is generated by a ToP master. The TRS reference source priority selection also user-
selectable. Furthermore, if a signal listed in the TRS references is not received, a BASE STATION TRANSMISSION ALARM is reported.,
\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe 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 GPS satellites, there is a loss of its 1 PPS
clock or there is a loss of communication with the receiver.\nThe BTS supports a ToP or SyncE reference source that has configurable
priorities relative to each other through the "synchroSourceList" parameter.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale
BTS FDD, AirScale BTS TDD:\nDepending on the installed and commissioned synchronization source(s) listed in the "Meaning" section, see
the commissioned synchronization option below and perform the steps in the listed order until the BTS fault indication disappears.\n\nGPS
receiver (PPS source):\n1. 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 which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS
receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change
the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then.\n\n2.
There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.\n\n3. There might be a malfunction
in the BTS. Perform a BTS site reset.\n\n4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors.\n\n5.
There might be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.\n\nExternal 2.048 MHz signal:\n1. 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, check the cables. Note that because the device type is not known, detailed instructions cannot be given - refer to the
appropriate user manual of the device for further actions.\n\n2. There might be a malfunction in the BTS. Perform a BTS site reset.\n\nFTM
reference (TDM, SyncE or ToP as source):\n1. 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 synchronization source, it turns off the clock reference signal which is normally
delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) might be missing,
causing the FTM's internal clock to drop to holdover mode. In this case, the fault in the transmission NETWORK must be corrected (the FTM
itself might be working fine).\n\n2. Check the alarms of the FTM unit and act accordingly.\n\n3. Check the synchronization settings of the FTM
unit.\n\n4. There might be a malfunction in the BTS. Perform a BTS site reset.\n\n5. 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 failure, but there might be connection
failures in the transmission or packet network, causing the FTM clock to drop to holdover mode. Especially the BTS fault indication activity
(frequent BTS fault indication activations/cancels instead of a stable BTS fault indication state) points to the instability of the transmission
network, not to a failure in the unit.\n\nIf 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, replace the System Module.\n\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD,
Flexi Zone SFN Antenna:\nDepending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the
commissioned synchronization option below and perform the steps in the listed order until the BTS fault indication disappears.\n\nGPS
source:\n1. 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) power reset of the GPS receiver. If the associated GPS receiver communication or 1 PPS clock fault is not
cleared within 5 minutes after the remote power reset, a Flexi Zone Micro BTS replacement is recommended.\n\nSyncE or ToP as
source:\n1. Check the alarms of the Flexi Zone Micro BTS or Flexi Zone SFN Antenna unit and act accordingly.\n2. 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
the required synchronization information to the Flexi Zone Micro BTS. Correct any associated PRC or master clock problems.\n3. 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 replacement might be necessary.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n4001:
29/05/2020 Alarms

major
release
before the reset.\n\n2. Reset (block and unblock) the BTS.\n\n\n\n\n\n\n\nFAULT NAME\nBTS reset time increased\n\nFAULT ID\n4091:
EFaultId_BtsResetTimeIncreasedAl\n\nMEANING\nDuring 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 the BTS. Therefore, the BTS reset lasts longer. This fault
notifies the operator that the BTS reset will be extended.\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT NAME\nBTS SW download or activation
failed\n\nFAULT ID\n29: EFaultId_FileCorruptionAl\n30: EFaultId_SwUpdateAl\n\nMEANING\nThe 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
system.\n\n\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Retry the SW update.\n2. If
other flash memory-related faults are active for the alarming module at the same time, replace the alarming module.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone Controller:\n1. Retry the SW update.\n2. If other flash memory-related faults are active for the BTS at
the same time, replace the BTS.\n\nFlexi Zone Access Point:\n1. Retry the SW update by resetting the Flexi Zone Access Point using the
BTS SM.\n2. If other flash memory-related faults are active for the Flexi Zone Access Point at the same time, replace the Access
Point.\n\nFlexi Zone SFN Antenna:\n1. Retry the SW update by resetting the Flexi Zone SFN Antenna using the BTS SM.\n2. If other flash
memory-related faults are active for the Flexi Zone SFN Antenna at the same time, replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nBTS time not corrected\n\nFAULT ID\n26: EFaultId_NtpTimeNotSetAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nThe SNTP time or GPS time cannot be fetched within the time limit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro
TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThe UTC time source is not available in the BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\nINSTRUCTIONS\n1. Check the NTP setting.\n\n2. Check the stratum parameter on the NTP server.\n\n3. Check that a GNSS is
configured and connected.\n\n\n\n\nFAULT NAME\nBuffer over/underflow in clock crossing logic\n\nFAULT ID\n2054:
EFaultId_MuksuRxClkErrorAl\n\nMEANING\nThe 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 a clock drift between the received signal and the internal clock, or the RX rate
setting is wrong.\n\nINSTRUCTIONS\n1. Check the status of the module behind the faulty link (power on, and so on).\n\n2. Check the
alarming fiber connection.\n\n\n\n\nFAULT NAME\nCommissioning error: <x>\n\nFAULT ID\n3060:
EFaultId_CommissioningError\n\nMEANING\nSome of the commissioning parameters are either missing or faulty, or there is a mismatch
between them.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n\n1. Check the
commissioning parameters with the BTS Site Manager Commissioning Wizard.\n\n2. Load the correct commissioning file to the
BTS.\n\n\n\n\nFAULT NAME\nCommunication failure\n\nFAULT ID\n1806: EFaultId_CommunicationFailureAl\n\nMEANING\nCommunication
with an application has failed. It has not replied to the message that has been sent/resent to it.\n\nINSTRUCTIONS\n1. 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 causing
the alarm.\n2. Check the fault history.\n\n\n\n\nFAULT NAME\nCompensation buffer is not enough for RF module delay difference\n\nFAULT
ID\n4276: EFaultId_RelativeDistanceCompensationBufferNotEnoughAl\n\nMEANING\nThe 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 capacity of the
compensation buffers. This fault is reported for the maximum transmission delay radio module.\nThe 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 the previous hop radio
modules, and the internal delay of the radio module.\n\n\nINSTRUCTIONS\nReduce 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 radio modules to remove the delay
introduced by the previous radio modules.\n\n\n\n\nFAULT NAME\nConfiguration and hardware mismatch\n\nFAULT ID\n4282:
EFaultId_ConfigurationAndHardwareMismatchAl\n\nMEANING\nThe detected hardware does not support the SCF
configuration.\n\nINSTRUCTIONS\n1. Read the diagnostic information of the alarm.\n2. If the diagnostic information is "IQ compression or
forced link speed incorrect\nin site configuration file", check what configurations are supported by\nNokia, correct IQ compression, or force
link speed value in the Site Configuration File (SCF), and then re-commission the BTS.\n3. If the diagnostic info is "Number of detected RET
units in multiRET\nis 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 update the BTS.\n\n\n\n\nFAULT NAME\nConfiguration error: <x>\n\nFAULT ID\n3070:
EFaultId_ConfigurationError \n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed
order until the BTS fault disappears:\n\n1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS
configuration.\n\n2. Check that the BTS cell parameters from the Network management system match\nthe BTS HW configuration (for
example, frequency, power).\n\n3. Check the Network management system alarms for the alarming local cell (LCR).\n\n4. Recommission the
BTS to ensure that all parameters are correctly configured.\n\n\n\n\nFAULT NAME\nConfiguration file corrupted\n\nFAULT ID\n1924:
EFaultId_FrConfigurationFileCorrupted\n\nMEANING\nThe RF Module SW has detected conflicting or corrupted configuration
data.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If problem
is still observed after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n2. If that does not help, replace the
Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nConfiguration reset\n\nFAULT
ID\n4181: EFaultId_ConfigResetAl\n\nMEANING\nThe Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna detects
that configuration reset has been invoked.\n\nINSTRUCTIONS\n1. Determine if this event is expected. Investigate audit logs as
necessary.\n2. If this action is unexpected, use SSH to disable maintenance port(s) and/or physically inspect site installation.\n\n\n\n\nFAULT
NAME\nConnection to ToP master missing\n\nFAULT ID\n4058: EFaultId_TopRefClkMissingAl\n\nMEANING\nThe reference clock monitoring
has detected a loss of the ToP reference clock signal received from the master clock.\n\nINSTRUCTIONS\nNote: Perform the steps below in
the listed order until the fault disappears.\n\n1. Check the Ethernet interface functionality used by Timing Over Packet. Check if other faults
related to the Ethernet interface exist.\n\n2. Check Timing Over Packet configuration. Ensure that the Master clock IP address is configured
properly and that the Master clock supports the given parameters.\n\n3. Check the Master clock functionality.\n\n4. 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.\n\n\n\n\nFAULT NAME\nConnection Unstable At 3Gbps \n\nFAULT ID\n4310:
EFaultId_ConnectionUnstableAt3Gbps\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nPerform the recovery in the
following sequence:\n1. Check if the optical transmission network connecting the system module with the radio module, or the extension
baseband module (FBBx) and the radio module, supports 6 Gbps transmission.\n2. 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 firmly to the modules.\n3. Replace the
cable.\n4. Change the radio module where the unstable link is terminated.\n5. If this does not help, replace the FBBx if the unstable link is
terminated\non FBBx.\n6. If this does not help, replace the FCT (system module).\n\nIf an alarm with fault 4038 (Radio master conflict) is
reported at the same time,\nfollow the instructions of fault 4038 because in some cases fault 4038 might be the root cause of fault
4310.\n\n\n\n\nFAULT NAME\nConnection Unstable At 6Gbps\n\nFAULT ID\n4309:
EFaultId_ConnectionUnstableAt6Gbps\n\nMEANING\nThe 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 Gbps.\n\nINSTRUCTIONS\nPerform the
29/05/2020 Alarms

major
release
recovery in the following sequence:\n1. Check if the optical transmission network connecting the system module and\nthe radio module, or
the extension baseband module (FBBx/ABIx) and the radio module,\nsupports 6 Gbps transmission.\n2. Check if the cable connecting the
system module and the radio module, or the\ncable connecting the extension baseband module and the radio module, is connected\nfirmly to
the modules.\n3. Replace the cable.\n4. Change the radio module where the unstable link is terminated.\n5. If this does not help, replace the
FBBx/ABIx if the unstable link is terminated\non the FBBx/ABIx.\n6. If this does not help, replace the FCT (system module).\n\nIf an alarm
with fault 4038 (Radio master conflict) is reported at the same\ntime, follow the instructions of fault 4038 because in some cases fault 4038
might\nbe the root cause of fault 4309.\n\n\n\n\nFAULT NAME\nConstellation mode not supported\n\nFAULT ID\n4296:
EFaultId_ConstellationModeNotSupportedAl\n\nMEANING\nThe BTS has detected an incompatible operator-selected constellation mode
for\nthe GNSS receiver.\n\nINSTRUCTIONS\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nConfigure a valid GNSS constellation mode supported by the GNSS receiver to\ncancel the fault (wait for 60
seconds).\n\n\n\n\nFAULT NAME\nCooling fan broken\n\nFAULT ID\n4078: EFaultId_FanBrokenAl\n\nMEANING\nOne 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).\n\nINSTRUCTIONS\n1. Check that the fan or airflow is not blocked by any object.\n2. Check that the fan connector is properly
mounted.\n3. If that does not help, replace the fan.\n\n\n\n\nFAULT NAME\nCooling fan broken: <X>\n\nFAULT ID\n1933:
EFaultId_FrFanBroken\n\nMEANING\nFan(s) in the RF module is/are not running.\n\nINSTRUCTIONS\n1. Check if the fan or air flow is
blocked by any object. Remove any objects that might be blocking the fan or air flow.\n2. Check if the fan connector is properly mounted.
Mount the fan connector properly.\n3. If the alarm continues, reset the radio module.\n4. If the alarm continues, replace the fan
module.\n\n\n\n\nFAULT NAME\nCooling fan has reduced from the set speed \n\nFAULT ID\n1934:
EFaultId_FrFanReducedSetSpeed\n\nMEANING\nFan(s) in RF module is/are rotating slower than requested.\n\nINSTRUCTIONS\n1. Check
if the fan or air flow is blocked by any object. Remove any objects\nthat might be blocking the fan or air flow.\n2. Check if the fan connector is
properly mounted. Mount the fan connector\nproperly.\n3. If the alarm continues, reset the radio module.\n4. If the alarm continues, replace
the fan module.\n\n\n\n\nFAULT NAME\nCooling fan is over speeding\n\nFAULT ID\n4080: EFaultId_FanOverSpeedAl\n\nMEANING\nOne or
more fans are running faster than requested.\n\nINSTRUCTIONS\nReplace the fans.\n\n\n\n\nFAULT NAME\nCooling fan is over speeding
\n\nFAULT ID\n1935: EFaultId_FrFanOverSpeed\n\nMEANING\nFan(s) in the RF module rotate faster than required.\n\nINSTRUCTIONS\n1.
Check if the fan or air flow is blocked by any object. Remove any objects that might be blocking the fan or air flow.\n2. Check if the fan
connector is properly mounted. Mount the fan connector properly.\n3. If the alarm continues, reset the radio module.\n4. If the alarm
continues, replace the fan module.\n\n\n\n\nFAULT NAME\nCooling fan speed decreased\n\nFAULT ID\n4079:
EFaultId_CoolingFanSpeedDecreasedAl\n\nMEANING\nThe speed of one or more fans is excessively deviating from the requested
control.\n\nINSTRUCTIONS\n1. Check if the fan or airflow is not blocked by any object.\n2. Check if the fan connector is properly
mounted.\n3. If that does not help, replace the fan.\n\n\n\n\nFAULT NAME\nCorrectable bit toggling error\n\nFAULT ID\n6700:
EFaultId_CorrectableBitTogglingError\n\nMEANING\nA correctable bit toggling error is detected in DSP memory.\n\nINSTRUCTIONS\nThe
fault doesn't require any special action because it was already autonomously corrected.\n\n\n\n\nFAULT NAME\nCPRI-A RF sharing mode
conflict\n\nFAULT ID\n4375: EFaultId_CpriArfSharingModeConflictAl\n\nMEANING\nThe LTE eNB has detected an RF sharing configuration
conflict in the radio that is also connected to a CDMA BTS. \n1. If the alarm diagnostic information contains "Incorrect mode configuration for
CPRI-A RF Sharing", then one of the following invalid configurations is detected:\n1.1. The LTE eNB is in stand-alone mode and the CDMA
BTS is in any mode. \n1.2. The LTE eNB is in any mode and the CDMA BTS is in stand-alone mode. \n1.3. The LTE eNB and CDMA BTS are
both in secondary mode.\n2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing",
then the LTE eNB is operating in a secondary mode, and the SW and/or AISG management functions is owned by the CDMA
BTS.\n\nINSTRUCTIONS\n1. 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 and/or CDMA System Modules. The following mode combinations are allowed:
\n1.1. LTE eNB is in secondary mode and CDMA BTS is in primary mode.\n1.2. LTE eNB is in stand-alone mode and CDMA BTS is
disconnected from the radio.\n2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF
Sharing", reconfigure the CDMA BTS to give both SW and AISG management function control to the secondary controller (LTE eNB).\n3. If
the previous steps do not help, reset the alarming radio unit.\n4. If the previous steps do not help, reset the LTE eNB and/or CDMA
BTS.\n\n\n\n\nFAULT NAME\nCRAN configuration alarm\n\nFAULT ID\n4274: EFaultId_CranIncorrectConfigurationAl\n\nMEANING\nThe
Centralized Radio Access Network (CRAN) configuration and the exchanged information between the connected BTSs show conflicts. CRAN
functionality between the alarming BTSs cannot be established.\n\nINSTRUCTIONS\n1. Read the diagnostic information in the alarm to find
out detailed information about the fault reason.\n2. Correct the site configuration file of own BTS or neighbor BTS according to the diagnostic
information.\n3. Re-commission the BTS and neighbor BTS using the valid commissioning files.\n\n\n\n\nFAULT NAME\nCritical BER
detected on the optical connection to Radio Module\n\nFAULT ID\n1956: EFaultId_CritBerOnRp3\n\nMEANING\nAn 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 stream
cannot be successfully processed by FRM. This is caused by the burst of consecutive LCV errors.\n\nINSTRUCTIONS\nInstructions are
divided into three sections. Execute steps from the chosen section based on best knowledge and common sense to minimize the cost
and\ntime effort. \n\nSection A: Check on system module side:\n1. Check if the connector seal is properly mounted and is firmly in place. \n2.
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 the connection/mounting.\n3. Check if the LED indicates that the SFP is faulty (connected to system module). Replace the
SFP if it is faulty.\n4. Check if the optical cable is properly connected/mounted in the SFP.\n5. Clean the optical connectors that are
connected to the SFP. Reset the RF HW\nunit and check if this solves the problem.\n\nSection B: Check on the radio module side:\n1. Check
if the connector seal is properly mounted and is firmly in place.\n2. 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 connection/mounting.\n3. Check if the
optical cable is properly connected/mounted in the SFP.\n4. Clean the optical connectors at the RF module end. Reset the RF HW unit and
check if this solves the problem.\n\nSection C: Check the optical connection:\n1. 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 can detach or damage the connectors. \n2.
OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the system module end. Check the measuring equipment
documentation for instructions.\n3. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF module end.
Check the measuring equipment documentation for instructions.\n\nIf the alarm continues after executing steps from sections A,B, and C,
replace\nthe RF module.\n\n\n\n\nFAULT NAME\nCritical bit toggling error\n\nFAULT ID\n6701:
EFaultId_CriticalBitTogglingError\n\nMEANING\nA non-correctable, bit-toggling error has been detected in the critical DSP
memory.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD,
AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System/Baseband Module.\n2. Replace the System/Baseband Module.\n\nFlexi Zone
Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or
Flexi Zone SFN Antenna.\n2. If the fault persists, Replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nDC voltage administratively disabled\n\nFAULT ID\n4141: EFaultId_DcVoltageAdministrativelyDisabledAl
\n\nMEANING\nThe feeding voltage is disabled for the selected antenna line.\n\nINSTRUCTIONS\nTo revert the changes, the DC voltage
should be enabled for the reporting antenna line.\n\n\n\n\nFAULT NAME\nDiagnostic Files collected \n\nFAULT ID\n6450:
EFaultId_TechnicalLogUploadRecommended\n\nMEANING\nAfter a DSP crash, the eNB collects core dumps and DSP memory dumps from
the crashed DSP.\nAfter an FCT or an FSP crash, the eNB collects core dumps from the crashed unit. \nFault 6450 notifies the operator that
the logs are stored in the eNB and can be collected in the snapshot.\n\n\nINSTRUCTIONS\nCollect technical logs from the BTS to clear the
alarm raised by this fault.\nInternal logs collected by this process can only be analyzed by Nokia R&D.\n\nAdditionally:\n- Check the alarm
history to confirm the frequency of fault 6450 in a specific eNB.\n- Check the alarm history for other alarms in the same eNB that might be
related, especially alarms with:\na. FSP or FBBB alarm source \nb. with the following fault IDs: 418, 6706-6709, 12, 476, 1806, 1811, 4019\n-
Check the eNB for any performance issues.\n\nIf an alarm with fault 6450 frequently occurs in the same eNB, there are alarms with the same
29/05/2020 Alarms

major
release
faults mentioned above in the same eNB, or the eNB performance is degraded, then collect a snapshot and open a case for Nokia R&D log
analysis.\n\nTake 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 6450 related to the next DSP is reported when logs from the first DSP are
collected.\n\n\n\n\nFAULT NAME\nDifference between BTS master clock and reference frequency\n\nFAULT ID\n9:
EFaultId_DacWordChangeAl\n\nMEANING\nFlexi BTS FDD, AirScale BTS FDD:\nThe 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) during the measurement
period as compared to the BTS master clock frequency. \n\nThe cause of the alarm can be:\n\n1. 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 error. Note that if
the network synchronization malfunction lasts for a long time, the alarm is cancelled when the BTS frequency reaches the faulty reference
synchronization. The alarm can also be activated if the faulty reference synchronization is corrected and there is, again, a difference of 0.2
ppm or more. The alarm is cancelled whenever the difference becomes less than 0.2 ppm.\n\n2. The reference frequency fluctuates
continuously because of a significant amount of jitter or wander in the transmission network. The alarm is continuously activated or cancelled
(however, the alarming state might predominate). There is always some jitter or wander in the transmission network; the limits are defined in
ITU-T G.823/824/825.\n\n3. If the BTS-integrated transport part receives the synchronization information through the 2.048 MHz
synchronization input (external clock source), the alarm situation might be caused by a fault of that signal. In that case, the alarm behavior
notifications listed with the Iub signal (see above) are also valid.\n\n4. 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 behavior (see the descriptions above).\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThe reference frequency that the BTS master clock receives
has experienced a significant change during the measurement period as compared to the BTS master clock frequency. \n\nThe cause of the
alarm can be:\n\n1. 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 error. Note that if the network synchronization malfunction lasts for a long time, the alarm is
cancelled when the BTS frequency reaches the faulty reference synchronization. The alarm can also be activated if the faulty reference
synchronization is corrected and there is, again, a difference of 0.2 ppm or more. The alarm is canceled whenever the difference is less than
0.2 ppm.\n\n2. The reference frequency fluctuates continuously because of a significant amount of jitter or wander in the transmission
network. The alarm is continuously activated or cancelled (however, the alarming state might predominate). There is always some jitter or
wander in the transmission network; the limits are defined in ITU-T G.823/824/825.\n\n3. If the BTS-integrated transport part receives the
synchronization information through the 2.048 MHz synchronization input (external clock source), the alarm situation might be caused by a
fault of that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid.\n\n4. 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 behavior (see the descriptions above).\n\n\nINSTRUCTIONS\nBecause there are several possibilities for the alarm activation, a BTS
Clock Frequency History feature has been developed. You can access the stored history data through the BTS Site Manager. You can use
the history data as a tool for finding out the reason for the fault or alarm situation (for further instructions about the history feature, see the
online help of BTS Site Manager). Depending on the possible reason, follow the instructions below:\n\n1. 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 0.015 ppm or
better (check the correct Iub accuracy by measuring it). No actions on the BTS are necessary.\n\n2. 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 correct the synchronization of
the transmission network. The limits for the jitter or wander are defined in the ITU-T G.823/824/825. No actions on the BTS are needed.\n\n3.
In case of a BTS equipment fault, the location might be:\n\nTransport part:\n\n- First, check the alarms of the TRS with the BTS Site Manager
and act accordingly.\n- If there are no alarms, check the TRS synchronization settings.\n\nFCM unit:\n\n- 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.\n- 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.\n- If that does not help,
replace the FCM unit.\n\nNote that if the reason is in the transmission network synchronization, replacing the faulty unit does not solve the
problem. Furthermore, the alarm activity (frequent alarms or cancels) points to instability in the transmission\nnetwork, not to a fault in the
unit.\n\n4. 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 the tuning:\n\n- manually by changing the DAC word (during a site visit)\n- 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)\n \nNote, 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 into a totally incorrect value, causing serious problems in the network performance.\n\nBackground information: The principle is that in
the mobile network, the synchronization goes from S1 interface. But in reality, that chain might be broken somewhere and, for example, when
using leased lines, the BTS might take the reference synchronization from the transmission network of another operator. This does not harm
the system if the synchronization of the leased line service provider is also accurate or stable enough. The BTS uses the incoming
synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.\n\n\n\n\nFAULT NAME\nDSP
loading failure\n\nFAULT ID\n1962: EFaultId_RruDspLoadingFailure\n\nMEANING\nDSP loading has failed.\n\nINSTRUCTIONS\n1. Reset
the RF module.\n \n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nError in file server
during file download\n\nFAULT ID\n27: EFaultId_FileServerAl \n\nMEANING\nThe 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 incorrect. A possible error in the DCN and Iub,
or a user administration error (an invalid username or password, or the user does not have access rights to the files) has
occurred.\n\n\nINSTRUCTIONS\n1. Retry the file update for a few times.\n2. Check the FTP account user settings.\n3. Check the file and
path names.\n4. Check the administration log on the file server. \n\n\n\n\n\n\nFAULT NAME\nExternal GPS receiver in holdover\n\nFAULT
ID\n4210: EFaultId_ExtGpsInHoldoverAl\n\nMEANING\nThe external GPS or GNSS receiver module has lost satellite visibility and is
currently operating in holdover mode.\n\nINSTRUCTIONS\n1. 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 properly, that is, the sky visibility is not good enough.
Refer to the documentation for installations, and if there are deviations with the actual installation, re-install the GPS or GNSS antenna. Note
that even when the GPS or GNSS antenna has good sky visibility, the problem might be caused by installing the GPS or GNSS antenna too
close to the transmitter antennas of the BTS, causing disturbances to the GPS or GNSS receiver. \n2. Check the other possible alarms or
fault indications of the GPS or GNSS receiver and the BTS, and act accordingly.\n3. There might be a malfunction in the GPS or GNSS
receiver. Perform a (remote) power reset for the GPS or GNSS receiver module.\n4. 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 settings. The power needs
to be ON in this case (while in shared configuration, one receiver feeds the power towards the antenna, and power feeding setting of the
other receivers is OFF).\n5. 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 or GNSS receivers, and one receiver might feed the power to the antenna. The
fault indication might be caused by a failure in another GPS or GNSS receiver. \n6. Perform a local or physical power reset for the alarming
GPS or GNSS receiver module.\n7. 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. Check the operation and change them if needed.\n8. 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.\n\n\n\n\nFAULT
NAME\nFailure in connection between BTS and iOMS or 3rd party tool\n\nFAULT ID\n6261:
EFaultId_TraceConnectionFaultyAl\n\nMEANING\nA failure has occurred in the trace connection between the BTS and the iOMS, or a third-
party tool.\n\nINSTRUCTIONS\nCheck the connection with the iOMS or the third-party tool.\n\n\n\n\nFAULT NAME\nFailure in connection to
Real-time PM Collection Entity\n\nFAULT ID\n4203: EFaultId_RtpmConnectionFaultAl\n\nMEANING\nA failure has occurred in the
connection to the configured Real-time Performance Management (RTPM) entity, for example, the Traffica Network Element Server
(TNES).\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault disappears:\n1. Verify if the IP address is
properly configured at the BTS.\n2. Verify if the Real-time Performance Management (RTPM) entity is operational and available.\n3. If the
29/05/2020 Alarms

major
release
above have been verified, the operator can reset the BTS at a suitable time.\n\n\n\n\nFAULT NAME\nFailure in log file gathering\n\nFAULT
ID\n4176: EFaultId_LogGatheringFailureAl\n\nMEANING\nGathering logs from the unit has failed, and one or more log files from a particular
RF module is not available in the BTS snapshot.\n\nINSTRUCTIONS\nRestart the faulty unit and retry the BTS snapshot request using the
BTS Site Manager.\n\n\n\n\nFAULT NAME\nFailure in optical interface\n\nFAULT ID\n3030:
unit.\n\n\n\n\nFAULT NAME\nFailure in trace session\n\nFAULT ID\n6263: EFaultId_TraceSessionAl\n\nMEANING\nA failure has occurred
during activation or de-activation of a trace session (subscriber trace, cell trace, or interface trace session).\n\nIn case of subscriber trace, the
possible reasons are:\n- The Subscriber Trace feature is not enabled in the BTS.\n- The ID used for the subscriber trace session is already in
use for another active subscriber trace session.\n- 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.\n- The handover in the BTS is ongoing for the UE to be traced.\n\nIn case of
cell and interface trace, the possible reasons are:\n- The Cell Trace feature is not enabled in the BTS.\n- The ID used for the cell and
interface trace session is already in use for another active cell and interface trace session.\n- 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.\n\nINSTRUCTIONS\nFor 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, the following must be done: \n- "Subscriber & Equipment Trace feature not enabled": Enable the
subscriber trace feature in the BTS. Any events corresponding to the failed subscriber trace, and any other subscriber traces started later,
which must be recorded, will be recorded in the BTS after the feature is enabled.\n- "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 Management System (NMS) used to
activate the subscriber trace. The error means that there is already an active subscriber trace in the BTS that is using the same Trace
Reference Number. A possible solution is to try de-activating all subscriber traces and activating them again.\n- "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 the
Network Management System (NMS) used for subscriber trace activation. This error indicates that there are already 60 active subscriber
trace sessions (which is the maximum number of active subscriber traces supported in the BTS at any point in time) in the BTS. Try to stop
an already active subscriber trace session in the NMS before activating any new subscriber traces.\n- "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 out of the scope
of what can be fixed in the BTS. This problem is transient. A possible solution is to re-try activation of the failed subscriber trace in the
NMS.\n\nFor 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, the following must be done: \n- "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. The feature flag used for activating the cell trace and interface
trace is the same.\n- "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 Management System (NMS) used to activate the cell or interface trace. The error means that there is already
an active cell or interface trace in the BTS that is using the same Trace Reference Number. A possible solution is to try de-activating all cell
and interfaces traces. Afterwards, try activating them again. \n- "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 the scope of the Network Management System (NMS)
used for cell or interface trace activation. This error indicates that there are already 12 active cell or interface trace sessions (which is the
maximum number of active cell and interface trace sessions, put together, supported in the BTS at any point in time) at the BTS. Try to stop
an already active cell or interface trace session in the NMS before activating any new cell or interface traces.\n\n\n\n\nFAULT NAME\nFailure
to download software due to missing software signature\n\nFAULT ID\n4269: EFaultId_SwBuildSignatureMissingAl\n\nMEANING\nThere 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 there is no software signature for the release, and only signed software can be installed.\n\nINSTRUCTIONS\nRetry the SW
update.\n\n\n\n\n\nFAULT NAME\nFailure to verify a signed software release\n\nFAULT ID\n4267:
EFaultId_SwBuildElementSignatureVerificationAl \n\nMEANING\nThere 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 software release that has just been requested to be
downloaded to the BTS system module. This is because the hash value of the questioned SW file is missing, or the BTSOM fails to verify the
hash of the questioned SW file.\n\nINSTRUCTIONS\nRetry the SW update.\n\n\n\n\n\nFAULT NAME\nFailure to verify the signature of a
signed software release\n\nFAULT ID\n4266: EFaultId_SwBuildSignatureVerificationAl\n\nMEANING\nThere 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 module. This is
because the information of either the Hash Container file or the Hash Container Signature file is not present in the downloaded TargetBD.xml,
or the verification of the software signature files has failed.\n\n\nINSTRUCTIONS\nRetry the SW update.\n\n\n\n\nFAULT NAME\nFan
failure\n\nFAULT ID\n3050: EFaultId_FanFailure\n\nMEANING\nA 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 not available for the fans. The reason for this fault can be a
broken fan. The condition for alarm activation is HW-dependent.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until
the BTS fault disappears.\n\n1. Check if fan or air flow is blocked by any object(s). Remove any blocking\nobject(s).\n2. Check if the fan
connector is properly mounted. Mount the fan connector properly.\n3. If the alarm is still observed, reset the radio module by using
block/unblock.\n4. If the alarm is still observed, replace the fan module.\n\n\n\n\nFAULT NAME\nFan vendor not detected\n\nFAULT
ID\n4073: EFaultId_FanVendorNotDetectedAl\n\nMEANING\nA fan delivered by an unknown vendor is detected (system module hardware
rel.2),\nor the fan speed is too low for successful detection. Another detection attempt\noccurs after the fan test timer expires (system module
hardware rel.3).\n\nThis fault is reported for both operational and non-operational fans in hardware\ndetection phase
only.\n\nINSTRUCTIONS\n1. Check the fan and the connector.\n2. Replace the fan.\n\n\n\n\nFAULT NAME\nFile corrupted in SW
download\n\nFAULT ID\n28: EFaultId_SwPackageAl \n\nMEANING\nThe download is corrupted, or the software is
incompatible.\n\nINSTRUCTIONS\n1. Retry the SW update.\n2. Save the snapshot and check the download status from the BTS
SWDLreport in the snapshot file.\n\n\n\n\nFAULT NAME\nFile System access failed\n\nFAULT ID\n4088:
EFaultId_FileSystemAccessFailedAl\n\nMEANING\nFile system access operations like file system mounting or file opening have
TDD:\nUpdate the BTS SW, unless it is automatically updated by NetAct.\n\nFlexi Zone Access Point, Flexi Zone SFN
29/05/2020 Alarms

major
release
Antenna:\nNone\n\n\n\n\nFAULT NAME\nFilter tuning failure\n\nFAULT ID\n1840: EFaultId_TuningFailureAl\n\nMEANING\nThe Radio
Module is unable to tune to a required sub-band properly (tuning\nfailure), or another major failure has been detected by the Radio
Module\n(unit faulty).\n\nINSTRUCTIONS\nReplace the alarming Radio Module/MultiRadio Combiner.\n\n\n\n\nFAULT NAME\nFilter unit
faulty\n\nFAULT ID\n1841: EFaultId_UnitFaultyAl\n\nMEANING\nThe radio module has detected an internal filter
failure.\n\nINSTRUCTIONS\n1. Reset the radio module.\n2. If resetting the radio module does not help, replace the alarming radio
module.\n\n\n\n\nFAULT NAME\nFirmware SW mismatch\n\nFAULT ID\n2056: EFaultId_SwMismatchAl\n\nMEANING\nThe software update
to the BTS has failed or the BTS software is corrupted.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Switch to the most recently-active BTS configuration.\n2. Retry the software
update.\n\nFlexi Zone (Flexi Zone Access Point):\n1. Reset the Flexi Zone Access Point to trigger SW upgrade again.\n2. Replace the Flexi
Zone Access Point.\n\nFlexi Zone (Flexi Zone Controller):\n1. Retry the embedded SW update manually. \n2. If this does not help, switch to
the latest active BTS configuration.\n3. Retry the SW update.\n\nFlexi Zone SFN Antenna:\n1. Reset the Flexi Zone SFN Antenna to trigger
SW upgrade again.\n2. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFPGA R/W error\n\nFAULT ID\n1963:
EFaultId_FpgaRwErrorAl\n\nMEANING\nAn error has occurred during a read/write attempt on the FPGA.\n\nINSTRUCTIONS\n1. Reset the
RF Module. \n2. If that does not help, replace the alarming RF Module.\n\n\n\n\nFAULT NAME\nFPGA SW update failed\n\nFAULT ID\n1928:
EFaultId_FrFpgaSwUpdateFailed\n\nMEANING\nThe FPGA software update in the RF module has failed.\n\nINSTRUCTIONS\n1. Reset the
RF HW unit.\n2. If problem is still observed after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nFrame clock
missing\n\nFAULT ID\n1903: EFaultId_FrFrameClockMissing\n\nMEANING\nThe System Module clock reference differs from the RF Module
clock.\n\nINSTRUCTIONS\nInstructions 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 effort.\n\nSection A: Check on the system module side:\n1. Check if the
connector seal is properly mounted and firmly in place. \n2. Check if the Small Form Factor Pluggable (SFP) is properly connected/mounted
in the System Module. If SFP connection/mounting is incorrect, readjust the connection/mounting.\n3. Check if the LED indicates the faulty
SFP (connected to System Module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly connected/mounted in the
SFP.\n5. Clean the optical connectors that are connected to the SFP. Reset the RF HW and check if this solves the problem.\n\nSection B:
Check on the radio module side:\n1. Check if connector seal is properly mounted and firmly in place.\n2. 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/mounting.\n3. Check if the optical cable is properly connected/mounted in the SFP.\n4. Clean the optical connectors at the RF
module end. Reset the RF HW unit and check if this solves the problem.\n\nSection C: Check the optical connection:\n1. 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 can
detach or damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System
Module end. Check the measuring equipment documentation for instruction details.\n3. OPTIONAL: Test the fiber cable (for example,
measure the optical attenuation) from the RF Module end. Check the measuring equipment documentation for instruction details.\n\nIf the
alarm still persists after executing the steps from sections A, B, and C, replace the RF module.\n\n\n\n\nFAULT NAME\nFR module reset
requested\n\nFAULT ID\n1981: EFaultId_FrResetRequestedAl\n\nMEANING\nThe FR module has detected a transient problem that requires
a reset recovery.\n\nINSTRUCTIONS\nNo actions are needed since the BTS recovers independently. If the alarm occurs multiple times,
check other active alarms to determine the root cause.\n\n\n\n\nFAULT NAME\nFR not critical functionality not supported or are not
configured correctly.\n\nFAULT ID\n4271: EFaultId_FrNotCriticalFunctionalityNotSupportedAl\n\nMEANING\nFR 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.\n\nINSTRUCTIONS\nCheck other active alarms. \n\n\n\n\n\nFAULT NAME\nFZAP Not Connected Successfully\n\nFAULT ID\n4322:
EFaultId_FzapNotConnectedSuccessfullyAl\n\nMEANING\nThe 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 not exist, or an FZAP or FZC fault prevents the
FZAP from successfully connecting to the FZC.\n\nINSTRUCTIONS\nIf the target FZAP does not physically exist, ignore this fault or clean it
up by deleting the target FZAP. Otherwise, perform the following steps:\n1. Check all other alarms posted against the target FZAP on
FZC.\n2. Check the alarms raised on the FZAP through WebUI or FZAP BTSSM. \n\n\n\n\nFAULT NAME\nFZC LTE time out of
sync\n\nFAULT ID\n4331: EFaultId_FzcLteTimeOutOfSyncAl\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nThis 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 of the
following:\n\n1. None of the FZAPs are connected anymore.\n2. All of its connected FZAPs has lost sync with their time source. \n\nPerform
actions to ensure that the FZAPs are connected to the FZC and/or recover the time sync with their time source.\n\n\n\n\n\nFAULT
NAME\nGPS Receiver alarm: control interface not available\n\nFAULT ID\n4011: EFaultId_GPSSystemElementAl\n\nMEANING\nThe BTS
has detected a communication problem with the GPS receiver.\n\nThe fault is ignored until the GPS receiver has reached the commissioned
state.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform 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 minutes from the start
of the fault prior to performing the actions below).\n\nControl Interface not available:\n1. 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 interface. Otherwise,
perform a (remote) power reset for the GPS receiver.\n2. Perform a (remote) BTS site reset for the whole BTS.\n3. Perform a power reset for
the whole BTS.\n4. 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 oxide and other kind of dirt: the pin connection quality is good. \n5. The cable between the GPS receiver
and the BTS might be faulty. Check the situation and change the cable if needed.\n6. There might be a hardware fault in the GPS receiver.
Check the operation and change the GPS module if needed.\n7. There might be a hardware fault in the BTS System Module. Check the
operation and change the System Module if needed.\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nPerform the steps below in the listed order until the fault disappears.\n\nControl Interface not available:\n1. 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
possible reason could be that BTS or access point, and the GPS receiver does not support common interface. Otherwise, perform a (remote)
power reset for the GPS receiver.\n2. Perform a (remote) site reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna.\n3. Perform a power reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n4.
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 Antenna.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: EEPROM invalid\n\nFAULT ID\n4126:
EFaultId_GpsReceiverEepromInvalidAl\n\nMEANING\nThe GPS receiver has detected that one or more EEPROM segments were corrupted
at reset, and had to be set to their factory default settings.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the fault
disappears:\n\nEEPROM invalid:\n1. The GPS receiver has detected a malfunction in its EEPROM memory. Perform a (remote) power reset
for the GPS receiver.\n2. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module if
needed.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: no stored position\n\nFAULT ID\n4124:
EFaultId_GpsReceiverNoStoredPositionAl\n\nMEANING\nThere is no accurate position stored in the EEPROM.\n\nINSTRUCTIONS\nNo
stored position:\nOne 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 memory. If there is no tick mark in the position storage selection, the GPS receiver runs the site or self
survey every time the GPS receiver is reset (either by manager command, by power outage, or by a GPS recovery reset). This means that if
the GPS receiver installation quality is only an average - and especially if the installation is a poor one - the GPS receiver turns the PPS
reference OFF every now and then during the site survey. This means the BTS master clock drops to holdover mode much easier during the
survey than during the normal operation.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: not tracking satellites\n\nFAULT ID\n4122:
EFaultId_GpsReceiverNotTrackingSatellitesAl\n\nMEANING\nThe fault indicates poor GPS antenna installation.\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform the steps below in the listed order until the fault
29/05/2020 Alarms

major
release
be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.\n3. There might be an HW fault in the GPS
receiver. Check the operation and change the GPS module, if needed.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\nPerform the steps below in the listed order until the fault disappears.\nNot tracking satellites:\n1. 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 enough.
Refer to the documentation for installations and if there are deviations with the actual installation, re-install the GPS antenna. Note that even
when the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter
antenna(s) of the BTS, causing disturbances for the GPS receiver. \n2. There might be a malfunction in the GPS receiver. Perform a (remote)
power reset for the GPS receiver.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: position questionable\n\nFAULT ID\n4125:
EFaultId_GpsReceiverPositionQuestionableAl\n\nMEANING\nThe receiver is used in stored position, but has been moved to a new position
after that.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the fault disappears:\n\nPosition questionable:\n1. 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
this fault indication might be that the GPS antenna installation has not been done properly, that is, the sky visibility is not good enough. Refer
to the documentation for instructions, and if there are deviations with the actual installation, re-install the GPS antenna. Note that even when
the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antennas
of the BTS, causing disturbances to the GPS receiver. \n2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset
for the GPS receiver.\n3. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module if
needed.\n\n\n\n\nFAULT NAME\nGPS receiver alarm: recommended firmware is not in use\n\nFAULT ID\n4272:
EFaultId_IncompatibleGpsSwVersionAl\n\nMEANING\nA 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 according to the software build that is loaded to the
BTS.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\n1. Reset the GPS or GNSS
module. \n2. Block and unblock the BTS to activate a BTS reset.\n3. Trigger a software update procedure for the GPS or GNSS module from
NetAct or BTS Site Manager.\n4. Replace the alarming GPS or GNSS module.\n\n\n\n\n\nFAULT NAME\nGPS receiver alarm: survey in
progress\n\nFAULT ID\n4123: EFaultId_GpsReceiverSurveyInProgressAl\n\nMEANING\nThe GPS receiver is running a site or self
survey.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the fault disappears:\n\nSurvey in progress:\n1. No actions
required as the the alarm is only informative. Normally, the GPS receiver runs the survey for two reasons: \na. Somebody has started the
survey manually.\nb. The GPS receiver has noticed that the position has changed, and the receiver has started an automatic survey. \nNote
also that automatic survey takes place every time during the first start-up.\n2. 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 satellites, the GPS receiver concludes that the position has
changed. In this case, check the activity of the other faults (BTS fault history data), and if found feasible, re-install the GPS antenna.\n3. 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 (remote) power reset for the GPS receiver.\n4. 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 GPS module if needed.\n\n\n\n\nFAULT NAME\nGPS reference
source indicates antenna short or overcurrent\n\nFAULT ID\n6803: EFaultId_GpsAntennaCurrentHighAl\n\nMEANING\nThe 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 Antenna. This alarm means the GPS antenna is drawing too much current.\n\n\n\nINSTRUCTIONS\n1. 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 connection between
the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna and the antenna is causing the problem.\n\n2. Consider
other alarms that might be occurring or configuration changes that were made just prior to this alarm as possible sources for this alarm.\n\n3.
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 Antenna.\n\n4. If not using an external GPS antenna, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna. \n\n\n\n\nFAULT NAME\nHigh memory consumption\n\nFAULT ID\n6502:
EFaultId_HighMemoryConsumptionAl\n\nMEANING\nThe physical memory supervision has detected that memory usage has exceeded 90%
(FCT (HW rel.3), ASIA) or 98% (FSP/ABIA).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nSource: \n- FCT (HW rel.3)/AIA: Perform eNB reset.\n- FSP/FBB/ABIA: Change the cell configuration to decrease call processing
load.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nNone\n\n\n\n\nFAULT NAME\nIncoherence in
cell configuration\n\nFAULT ID\n4000: EFaultId_IncoherencyInConfiguration\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nToo many cells are commissioned to the BTS.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nMore LNCELs
than the supported maximum number is configured, or too many LCRs are commissioned to one RF module.\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nIf other alarms are reported, re-commission the BTS with the correct number
of cells per BTS.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nRe-commission the BTS with the correct number of LCRs per RF
module.\n\n\n\n\nFAULT NAME\nIncompatible SW version detected\n\nFAULT ID\n23: EFaultId_IncompatibleSwVersionAl
\n\nMEANING\nIncompatible software has been detected.\n\nINSTRUCTIONS\nUpdate 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 by NetAct.\n\nIn case of RF
modules with factory SW loaded, SW update is a mandatory step.\n\n\n\n\nFAULT NAME\nIncreased BER detected on the optical connection
to Radio Module\n\nFAULT ID\n1955: EFaultId_IncrBerOnRp3\n\nMEANING\nIncreased bit error rate has been detected on the optical link to
the radio module, which results in sporadic LCV errors in downlink baseband processing.\n\nINSTRUCTIONS\nInstructions are divided into
three sections. Choose the appropriate section and perform the corresponding steps:\n\nSection A: Check on the system module side:\n1.
Check if the connector seal is properly mounted and is firmly in place. \n2. 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 the connection/mounting.\n3. Check if the
LED indicates that the SFP is faulty (connected to system module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly
connected/mounted in the SFP.\n5. Clean the optical connectors that are connected to the SFP. Reset the RF hardware unit and check if this
solves the problem.\n\nSection B: Check on the radio module side:\n1. Check if the connector seal is properly mounted and is firmly in
place.\n2. 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 connection/mounting.\n3. Check if the optical cable is properly connected/mounted in the SFP.\n4. Clean the
optical connectors at the RF module end. Reset the RF hardware unit and check if this solves the problem.\n\nSection C: Check the optical
connection:\n1. 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 can detach or damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the
optical attenuation) from the system module end. Check measuring equipment documentation for instructions.\n3. OPTIONAL: Test the fiber
cable (for example, measure the optical attenuation) from the RF module end. Check measuring equipment documentation for
instructions.\n\nIf the alarm continues after executing steps from sections A,B, and C, replace\nthe RF module.\n\n\n\n\nFAULT NAME\nInter-
core communication failure\n\nFAULT ID\n6814: EFaultId_InterCoreCommFailure\n\nMEANING\nA failure has been detected in the internal
communication between cores.\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT NAME\nInvalid configuration file\n\nFAULT ID\n4036:
EFaultId_InvalidConfigurationFileAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe
commissioning file is corrupted, or an incorrect SCF file has been detected during BTS startup as follows:\n1. Commissioning data: The
commissioning file is corrupted, or a parameter has a missing or incorrect value.\n2. 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 is created," or invalid
combination of cell parameters administrativeState and preventCellActivation.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone,
Flexi Zone SFN Antenna:\nThe commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows:\n1.
Commissioning data: The commissioning file is missing, or a parameter has a missing or incorrect value.\n2. RNW data: "RNW not found,"
29/05/2020 Alarms

major
release
"RNW has wrong format," "RNW could not be parsed," "RNW has wrong schema," "Validation failed due to incompatible data," "no RNW cell
managedObject is created," or invalid combination of cell parameters administrativeState and
preventCellActivation.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nCheck and correct the
contents of the commissioning file.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check and
correct the contents of the commissioning file.\n2. Recommission the BTS or Flexi Zone SFN Antenna with the valid commissioning
file.\n\n\n\n\nFAULT NAME\nLNA in bypass mode\n\nFAULT ID\n4270: EFaultId_MhaBypassModeAl\n\nMEANING\nThe 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 at the same time.\n\nINSTRUCTIONS\nIf LNA is shared between two BTSs and it supports separate AISG ports\nfor
each BTS, check if the LNA is not switched to bypass mode by other BTSs.\n\n\n\n\n\nFAULT NAME\nLow noise amplifier failure\n\nFAULT
ID\n1839: EFaultId_LNAFailureAl\n\nMEANING\nThe Radio Module has detected a malfunction of an internal LNA
unit.\n\nINSTRUCTIONS\nReplace the alarming Radio Module.\n\n\n\n\nFAULT NAME\nLTE-LTE RF sharing configuration alarm \n\nFAULT
ID\n4336: EFaultId_LteLteRfSharingIncorrectConfigurationAl\n\nMEANING\nThe LTE-LTE RF Sharing configuration and the exchanged
information between the two LTE BTSs show conflicts.\n\nINSTRUCTIONS\n1. Read the diagnostic information in the alarm to find out
detailed information\nabout the fault reason.\n2. For the following reason, update BTS SW to correct version:
IncompatibleConfigNeighborEnbSwVersionMismatch.\n\n\n\n\nFAULT NAME\nM3 SCTP path failure\n\nFAULT ID\n6206:
EFaultId_M3SctpPathAl\n\nMEANING\nOne 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. An alternate transport path is available to pursue
operation.\n\nINSTRUCTIONS\n1. Check whether the transport path is alive.\n2. Check the configuration of transport addresses at
MME.\n\n\n\n\nFAULT NAME\nManual location entry not supported\n\nFAULT ID\n4328:
EFaultId_ManualLocationEntryNotSupportedAl\n\nMEANING\nThe BTS has detected that the GNSS receiver does not support the operator-
selected manual location entry.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nChange the
GNSS location mode to automatic to cancel the fault. The fault is canceled after 60 seconds.\n\n\n\n\n\n\n\n\n\nFAULT NAME\nMast Head
Amplifier fault\n\nFAULT ID\n3120: EFaultId_MastHeadAmplifierFault\n\nMEANING\nThe FlexiBTS/AirScaleBTS has detected an abnormal
operation, or a failure, in the Masthead Amplifier (MHA).\n\nNote that the Tower Mounted Amplifier (TMA) is synonymous to the MHA, and is
used by the Antenna Interface Standards Group (AISG).\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS
fault disappears.\n\n1. Check the cables related to the Masthead Amplifier (MHA).\n\n2. Block and unblock the RF Module to which the MHA
is connected to reset the alarming MHA module.\n\n3. Replace the faulty devices.\n\n\n\n\nFAULT NAME\nMaximum number
handover/emergency call UEs are connected to the eNB Zone\n\nFAULT ID\n6325:
EFaultId_MaxNumUePerClusterReachedForEmergencyOrHandoverCall\n\nMEANING\nThe operator-configured maximum number of UEs
connecting through an emergency call or through an incoming handover (MaxNumClusterUe + 10% reserve) has been reached. Until one or
more of the currently connected UEs is released, subsequent UEs that attempt to connect through normal call or emergency call are released
immediately after completion of RRC connection establishment, and requests for incoming inter-eNB or inter-RAT handovers are
rejected.\n\nINSTRUCTIONS\nThis fault does not require any actions. This alarm clears automatically when the number of connected UEs
remains below maxNumClusterUe + 10% reserve for at least 20 seconds.\n\n\n\n\nFAULT NAME\nMaximum number normal call UEs are
connected to the eNB Zone\n\nFAULT ID\n6324: EFaultId_MaxNumUePerClusterReachedForNormalCall\n\nMEANING\nThe operator-
configured maximum number of UEs connecting through a normal call (maxNumClusterUe) has been reached. Until one or more of the
currently connected UEs is released, subsequent UEs that attempt to connect through normal call are released immediately after completion
of the RRC connection establishment.\n\nINSTRUCTIONS\nThis fault does not require any actions. This alarm clears automatically when the
number of connected UEs remains below maxNumClusterUe for at least 20 seconds.\n\n\n\n\nFAULT NAME\nMaximum number of 1xRTT
neighbor cells exceeded\n\nFAULT ID\n6299: EFaultId_MaximumNumberOfRttNbCellsAl \n\nMEANING\nA 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 cells
(LNADJX instances) is already reached. Neighbor cell information needs to be cleaned up manually by the operator through the plan
file.\n\nINSTRUCTIONS\nThe operator should do either of the following after receiving fault to recover the BTS to full operational:\n1.
Manually remove the neighbor object below limit.\n2. Reconfigure or manually change the threshold limit.\n\n\n\n\nFAULT NAME\nMaximum
number of neighbor eNBs/cells exceeded\n\nFAULT ID\n6265:
EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded\n\nMEANING\nThis 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
stored.\n\nINSTRUCTIONS\n1.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 LNADJ information.\n\n2.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 deleted. This makes space for
new LNADJ information.\n\n\n\n\nFAULT NAME\nMaximum number of WCDMA neighbor cells is exceeded\n\nFAULT ID\n6268:
EfaultId_MaximumNumberOfWcdmaNbCellsAl\n\nMEANING\nThis 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 LNADJW instances is already reached. The
additional alarm info holds the UTRAN CGI of the reported WCDMA cell, which could not be stored in the form of:\n"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 reached. WCDMA neighbour cell information needs be cleaned up manually by the operator via plan file (WCDMA cell CGI {rncId ="
%d, CellId = %d, ecgiPlmnId: MNC= %s, MCC= %d})".\n\n\nINSTRUCTIONS\nCheck 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.\n\n\n\n\nFAULT
NAME\nMaximum number of WCDMA neighbor relations is exceeded\n\nFAULT ID\n6269:
EfaultId_MaximumNumberOfWcdmaNbRelsAI\n\nMEANING\nThis 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 of neighbor relations per cell is already
reached. The additional alarm info holds the ECGI of the LTE cell and the UTRAN CGI of the related WCDMA neighbor cell in the
form:\n"LTE cell ECGI{ecgiAdjEnbId = %d, ecgiLcrId = %d, ecgiPlmnId = { %d, %d, %d}} , WCDMA cell CGI {rncId= %d, CellId= %d,
cgiPlmnId = { %d, %d, %d}}".\n\nINSTRUCTIONS\nCheck 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 LNRELW objects.\n\n\n\n\nFAULT NAME\nMaximum
number of WCDMA neighbor relations per cell and carrier is exceeded\n\nFAULT ID\n6270:
EfaultId_MaximumNumberOfWcdmaNbRelsPerCellAndCarrierAl\n\nMEANING\nThis alarm indicates that a WCDMA neighbor relation, which
is reported by a\nUE because of activated UTRAN ANR feature, has been stored but at least one\nof the mobility parameters of LNRELW
(csfbPsHoAllowed, psHoAllowed, srvccAllowed)\nhas been set to "forbidden" because the number of neighbor relations\n(LNRELW
instances) exceeds the maximum number of WCDMA neighbor cells, which\nmight be used by the eNB in measurement configurations (for
psHoAllowed or srvccAllowed, limit in 3GPP 36.331 is (32); for csfbPsHoAllowed is LNHOW::maxNumCsfbTargets).\nThe additional alarm
info holds the ARFCN of the affected carrier frequency as well as the LNCEL and LNRELW instance number in the form of:\n"Affected
WCDMA ARFCN carrier = %d, LTE cell ECGI{ecgiAdjEnbId = %d, ecgiLcrId = %d, ecgiPlmnId = { %d, %d, %d}} , WCDMA cell CGI {rncId=
%d, CellId= %d, cgiPlmnId = { %d, %d, %d}}"\n\nINSTRUCTIONS\nCheck that the maximum number of mobility parameters (either of:
csfbPsHoAllowed, psHoAllowed, srvccAllowed) of LNRELW per cell and WCDMA carrier frequency is below the limit (for psHoAllowed or
srvccAllowed, limit in 3GPP 36.331 is (32); for csfbPsHoAllowed is LNHOW::maxNumCsfbTargets). \n\n\n\n\nFAULT NAME\nMBMS session
cannot be resumed\n\nFAULT ID\n6853: EFaultId_MbmsSessionSuspendedAl\n\nMEANING\nAt least one suspended MBMS session cannot
be resumed because of insufficient MBMS resources.\n\nINSTRUCTIONS\nThis fault is a warning and cannot be cleared. The sessions that
cannot be resumed are automatically cleared using M3 Partial Reset procedures.\n\n\n\n\nFAULT NAME\nMCE configuration update
failure\n\nFAULT ID\n6854: EFaultId_MceConfigFailureAl\n\nMEANING\nMCE configuration update has finally failed.\n\nThe MME could not
be informed about the modification of at least one of the following MCE configuration data:\n- global MCE ID\n- MCE name\n- supported
MBMS service area identities\n\nINSTRUCTIONS\n\n\n\n\nFAULT NAME\nMFBI cell configuration conflict\n\nFAULT ID\n6278:
29/05/2020 Alarms

major
release
EFaultId_MfbiCellConfigurationConflict\n\nMEANING\nThe 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 is violated).\nAs 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 is activated and the X2
link is available, there will be continuous retries to resolve the ECGI.\n\nINSTRUCTIONS\nBlock and unblock the BTS.\n\n\n\n\nFAULT
NAME\nMHA operation degraded\n\nFAULT ID\n1869: EFaultId_MinorTMAFaultAl\n\nMEANING\nA fault in the Masthead Amplifier (MHA) is
detected. MHA functionality is degraded. The real impact cannot be determined.\n\nINSTRUCTIONS\nReset the MHA (using Radio Module
reset). If this does not help, replace the alarming module.\n\n\n\n\nFAULT NAME\nMHA operation failure\n\nFAULT ID\n1870:
EFaultId_MajorTMAFaultAl\n\nMEANING\nA fault in the Masthead Amplifier (MHA) has been detected. The MHA is not
working.\n\nINSTRUCTIONS\n1. Reset the MHA by using radio module reset.\n\n2. If this does not solve the problem, replace the alarming
module.\n\n\n\n\nFAULT NAME\nMismatched RRU optical module <optif ID>\n\nFAULT ID\n1969:
EFaultId_MismatchedSfpAl\n\nMEANING\nThe small form-factor pluggable (SFP) module is mismatched.\n\nINSTRUCTIONS\nReplace the
faulty SFP.\n\n\n\n\nFAULT NAME\nModule Clock faulty\n\nFAULT ID\n1926: EFaultId_FrModuleClockFaulty\n\nMEANING\nThe RF module
has lost lock to the incoming clock.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nInstructions 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 effort. \n\nSection A: Check on the system module side:\n1. Check if the connector seal is properly mounted
and firmly in place. \n2. 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, readjust the connection or mounting.\n3. Check if the LED indicates the faulty SFP (connected to
System Module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly connected or mounted in the SFP.\n5. Clean the
optical connectors that are connected to the SFP. Reset the RF HW unit and check if this solves the problem.\n\nSection B: Check on the
radio module side:\n1. Check if the connector seal is properly mounted and firmly in place.\n2. 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 connection or
mounting.\n3. Check if the optical cable is properly connected or mounted in the SFP.\n4. Clean the optical connectors at the FR module end.
Reset the FR HW unit and check if this solves the problem.\n\nSection C: Check the optical connection:\n1. 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 can detach or
damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System Module's end.
Check the documentation of the measuring equipment for instruction details.\n3. 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 instruction details.\n\nIf the alarm
continues after executing the steps from sections A, B, and C, replace the FR module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi
Zone, Flexi Zone SFN Antenna:\nReplace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nNo connection to RP1 interface\n\nFAULT ID\n4189: EFaultId_NoRp1ConnectAl\n\nMEANING\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone (Flexi Zone Access Point), Flexi Zone SFN Antenna:\nThe connection to the RP1 Transport (TRSW) or Radio
Frequency (RFSW) interface has been lost.\n\nFlexi Zone (Flexi Zone Controller):\nThe connection to RP1 Transport (TRSW) interface has
been lost.\n\nINSTRUCTIONS\n\n\n\n\nFAULT NAME\nNo connection to unit\n\nFAULT ID\n10: EFaultId_NoConnectionToUnitAl
\n\nMEANING\nThe connection to a module that belongs to the BTS configuration has been lost.\n\nIn case of SNMP radios, there is a
problem with the optical interface or an internal fault, which results in a radio reset.\n\nINSTRUCTIONS\n1. 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.\n\n2. Check the
fault history.\n\n\n\n\nFAULT NAME\nNo feedback signal\n\nFAULT ID\n1920: EFaultId_FrNoFeedBackSignal \n\nMEANING\nThe feedback
signal to predistortion is too weak or missing. The TX performance is degraded.\n\nINSTRUCTIONS\n1. Reset the RF HW unit.\n2. If
problem is still observed after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nNo module fan detected\n\nFAULT
ID\n1932: EFaultId_FrNoFansDetected\n\nMEANING\nThe RF module cannot identify the fan vendor or the fan is not
installed.\n\nINSTRUCTIONS\n1. Check if the fan or air flow is blocked by any object. Remove any objects that might be blocking the fan or
air flow.\n2. Check if the fan connector is properly mounted. Mount the fan connector properly.\n3. If the alarm continues, reset the radio
module.\n4. If alarm continues, replace the fan module.\n\n\n\n\nFAULT NAME\nNot able to synchronize baseband bus with <x>\n\nFAULT
ID\n1815: EFaultId_BbBus_SyncFailedAl\n\nMEANING\nThe baseband bus synchronization towards <x> has
failed.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform the recovery in the following
sequence:\n1. 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 modules.\n2. Replace the cable.\n3. Change the faulty module (FBBx/ABIx or FR).\n4. If it does not
help, replace the FCM/FCT (system module).\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nReplace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nNot critical bit
toggling error\n\nFAULT ID\n6702: EFaultId_NotCriticalBitTogglingError\n\nMEANING\nA non-correctable bit toggling error is detected in the
non-critical DSP memory area.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the
System/Baseband Module.\n2. Replace the System/Baseband Module.\nNote: Perform the steps below in the listed order until the fault
disappears.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or
Flexi Zone Access Point or Flexi Zone SFN\nAntenna.\n2. If the fault persists, replace the Flexi Zone Micro BTS or Flexi\nZone Access
Point.\n\n\n\n\n\nFAULT NAME\nNTP Frequency Synchronization OCXO Calibration Expired\n\nFAULT ID\n6822:
EFaultId_NtpSyncOcxoCalibrationExpiredAl\n\nMEANING\nThis fault indicates that the BTS reference oscillator calibration has expired. The
reference oscillator calibration is used to minimize the BTS initialization time.\nWhen operating with the Network Time Protocol (NTP)
frequency synchronization reference source, long initialization times can be required when the reference oscillator calibration has
expired.\n\nINSTRUCTIONS\nPerform the following steps in order until the fault disappears.\n1. Check the Ethernet interface functionality
used by Network Time Protocol. Check if other faults related to the Ethernet interface exist.\n2. Check the Network Time Protocol
configuration. Ensure that the NTP Server IP address is configured properly.\n3. Check the Network Time Protocol server functionality.\n4.
Check that the IP connection between the Network Time Protocol server and Flexi Zone Micro BTS or Flexi Zone Access Point is
working.\n\n\n\n\nFAULT NAME\nObsolete SW version detected\n\nFAULT ID\n24: EFaultId_ObsoleteSwVersionAl\n\nMEANING\nThere is
an attempt to download an unsupported SW version.\n\nINSTRUCTIONS\nUpdate 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 NetAct.\n\n\n\n\nFAULT NAME\nOIC
MCU Buffer Full\n\nFAULT ID\n2011: EFaultId_OIC_MCUBFullAl\n\nMEANING\nThe control message traffic between the modules is
malfunctioning.\n\nINSTRUCTIONS\nCheck the alarms for the connected module.\n\n\n\n\nFAULT NAME\nOperation on shared optical port
failed\n\nFAULT ID\n4180: EFaultId_OperationOnSharedOpticalPortFailedAl\n\nMEANING\nThe shared OptIF mode cannot be read from or
changed in the FBBC card.\n\nINSTRUCTIONS\nFault 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 can decide whether to change the FBBC card or not.\n\n\n\n\nFAULT
NAME\nOptical interface data/control/ethernet buffer full\n\nFAULT ID\n2006: EFaultId_OIC_DBRxFullAl\n2010:
EFaultId_OIC_EBFullAl\n\nMEANING\nThe RP3 or Ethernet buffering is not working, and the buffer becomes full. The\noptical device is
malfunctioning. The fault might be generated because of synchronization problems or incorrect initialization.\nFault 2006 may be detected in
Flexi BTS TDD only.\nFault 2010 may be detected both in Flexi BTS FDD and TDD.\n\nINSTRUCTIONS\n1. Exchange the alarming and
working links, and check where the alarm is reported\nnow.\n\n2. If the alarming link remains the same, replace the System Module.\n\n3. If
the alarming link changes, replace the module behind that link.\n\n\n\n\nFAULT NAME\nOptical Interface faulty\n\nFAULT ID\n2000:
EFaultId_OIC_TxAl\n2001: EFaultId_OIC_PresAl\n\nMEANING\nA 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 (fault 2001). The SFP is a part of the fiber cable
package.\n\nINSTRUCTIONS\n1. Check that the small form-factor pluggable (SFP) is properly connected to the System Module.\n\n2.
Replace the SFP module.\n\n\n\n\nFAULT NAME\nOptical link speed change failure\n\nFAULT ID\n4342:
EFaultId_OptLinkSpeedChangeFailedAl\n\nMEANING\nThe optical interface is not operating at the maximum speed. Not all cell
configurations are supported.\n\nINSTRUCTIONS\n1. Check the optical cable and the SFPs on both ends of the optical interface and replace
29/05/2020 Alarms

major
release
hardware if needed.\n2. Restart the radio unit connected to the affected optical interface.\n\n\n\n\nFAULT NAME\nOverload monitoring: High
number of neighbor related objects\n\nFAULT ID\n6286: EFaultId_HighNumberAnrMoiReachedAl\n\nMEANING\nThis 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
objects) in its database is equal to or above an internal threshold based on the configured value of the parameter "maxNumAnrMoiAllowed" in
LNBTS.\n\nINSTRUCTIONS\nRemoving neighbor-related objects below the internal threshold turns off the notification alarm. The BTS stays
in full operational state.\n\n\n\n\nFAULT NAME\nParallel optical link length mismatch\n\nFAULT ID\n4072:
EFaultId_ParallelLinkDifferenceTooLargeAl \n\nMEANING\n- 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 RRU). The main link is considered as a reference and the
secondary link is compared to the main link. \n- 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 module-shared RF is too large.\n\nThe additional info in
the alarm about difference in length should be delivered in the alarm only when LTE is radio master.\n\nThe information consists of: \n- The
number of physical port on the system module where primary link starts.\n- The number of physical port on the system module where
secondary too long/too short link starts.\n- The difference in lengths with information if secondary link is too short or too long.\n- The
difference in delays in nanoseconds.\n\nINSTRUCTIONS\nIf the fault is detected in non-sharing configuration:\n1. 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.\n2. 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 60 meters in OBSAI RRU, or 146 meters in CPRI RRU. \n\nIf the fault is triggered because of an incorrect RF sharing
configuration, check that the RF sharing feature is enabled on synchronization master system module.\n\nIf the alarm with fault 4038 (Radio
master conflict) is reported at the same time,\nfollow the instruction for fault 4038 because in some cases, 4038 may be the root cause of
fault 4072.\n\n\n\n\nFAULT NAME\nPeer system module connection lost\n\nFAULT ID\n4110:
EFaultId_PeerSystemModuleConnectionLostAl\n\nMEANING\nThe master system module has lost optical or sync connection to the peer
system module.\n\nINSTRUCTIONS\nCheck the reported alarms of the peer system module.\nCheck the optical connection between the
master LTE and peer system modules.\n\nIn a BTS configuration where one system module provides PPS synchronization signal to another
system module over a separate sync cable (sync hub configuration), check all optical and sync connections between all system
modules.\n\n\n\n\n\nFAULT NAME\nPhase error exceeds 5 us limit\n\nFAULT ID\n6280:
EFaultId_PhaseSynchronizationErrorAl\n\nMEANING\nThis 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 can occur when:\n- the absolute value of the estimated phase error
of an eNB has exceeded the limit of 5 us.\n- the eNB is more than 6 hours in holdover mode which means that the estimated\nphase error
value might not be reliable. It is assumed in this case that\nthe real absolute value of phase error is greater than 5 us.\n- 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\nthe real absolute value of phase error is greater than 5 us.\n- 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 the Sync Slave exceeds the 5 us
limit.\n\nINSTRUCTIONS\nIf GPS is configured as the reference clock, do the following:\n1. Check the GPS receiver installation.\n2. Check
the GPS receiver status.\n3. Check the connection between the GPS receiver and FSM.\n\nIf the TOP signal is configured as the reference
clock, check the connection to the TOP server.\n\n\n\n\nFAULT NAME\nPipe dangerously overheating \n\nFAULT ID\n1938:
EFaultId_FrPipeOverheat\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Check if the ambient temperature or environmental conditions are
within the design limits of the radio module. When the ambient temperature or environmental conditions are out of limits, the alarm is
expected and no further actions are needed.\n\n2. 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 flow, and mount the module according to the instructions and
recommendations.\n\n3. Check if excessive sunlight is causing an overheat. Install sunshield following the mounting instructions and
recommendations.\n\n\n\n\nFAULT NAME\nPost test failed\n\nFAULT ID\n1925: EFaultId_FrPostTestFailed\n\nMEANING\nAn RF module's
power-on self-test has failed at start-up.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1.
Reset the RF HW unit.\n2. If the problem continues after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nPower on #smodLogicalId #pwrLineId line switched off at the front panel\n\nFAULT ID\n4365:
EFaultId_RfPowerSwitchedOffFromFrontPanelAl \n\nMEANING\nPower feeding for the given Radio Module has been switched off by the
user from\nthe front panel of the PDU.\n\nINSTRUCTIONS\nEnable power feeding towards the Radio Module by switching RF power on in
the BTS Site Manager or at the front panel of the PDU.\n\n\n\n\nFAULT NAME\nPower on #smodLogicalId #pwrLineId line switched off
remotely by user\n\nFAULT ID\n4107: EFaultId_RfPowerSwitchedOffFromBtsSmAl\n\nMEANING\nPower feeding for the given radio module
has been remotely switched off using BTS Site Manager.\n\nINSTRUCTIONS\nEnable power feeding toward the radio module by switching
RF power on in BTS Site Manager.\n\n\n\n\nFAULT NAME\nPPS reference missing\n\nFAULT ID\n1898:
EFaultId_PpsRefMissAl\n\nMEANING\n1. The reference clock monitoring has detected a loss of PPS signal in the reference received from
the GPS receiver or the SyncHub master.\n2. (TDD only) The PPS signal from the SyncHub master is unusable because its reported phase
error is too large.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the GPS receiver
installation.\n2. Check the GPS receiver status.\n3. Check the connection between the GPS receiver and the FSM.\n4. Check the cable or
connection towards a SyncHub master when operating as SyncHub slave.\n5. Check the status of the SyncHub master.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the GPS receiver installation.\n2. Check the GPS receiver
status.\n\n\n\n\n\nFAULT NAME\nPreviously downloaded plan [planId] was overwritten by a new plan [planId]\n\nFAULT ID\n4340:
EFaultId_PreviouslyDownloadedPlanOverwrittenAl\n\nMEANING\nPreviously downloaded plan[Id] was overwritten by a new
plan[Id].\n\nINSTRUCTIONS\nNo action is required.\n\n\n\n\nFAULT NAME\nRadio memory consumption exceeds abnormal
threshold\n\nFAULT ID\n4329: EFaultId_RadioMemAboveAbnormalThresholdAl\n\nMEANING\nFree memory on the radio module is
limited.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nRecovery restart of the faulty radio
module is highly recommended and should be scheduled in the nearest suitable time (for example, during low traffic period).\n\n\n\n\nFAULT
NAME\nRadio memory consumption exceeds critical threshold\n\nFAULT ID\n4330:
EFaultId_RadioMemAboveCriticalThresholdAl\n\nMEANING\nThe radio module has no free memory.\n\nINSTRUCTIONS\nRecovery restart
of the faulty radio module is highly recommended and should be done as soon as possible.\n\n\n\n\nFAULT NAME\nRadio module access
panel open\n\nFAULT ID\n1991: EFaultId_FrAccessPanelOpenAl\n\nMEANING\nThe 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. \n\nINSTRUCTIONS\nCheck
access door and close if open.\n\n\n\n\nFAULT NAME\nRadio module internal communication failure\n\nFAULT ID\n1990:
EFaultId_FrInternalCommunicationFailureAl\n\nMEANING\nThe fault is reported in radio modules that consists of two separate hardware
units connected by optical cable. The near end Radio Module subunit cannot communicate with the far end subunit, possibly due to failed
CPRI link between the two subunits, or a failed far end subunit. \n\nINSTRUCTIONS\n1. Reset the alarming radio unit.\n2. If reset has not
canceled the fault condition, replace the alarming radio unit hardware.\n\n\n\n\n\nFAULT NAME\nRadio module internal hardware assignment
indeterminate\n\nFAULT ID\n1993: EFaultId_FrInternalHwAssignmentIndeterminateAl\n\nMEANING\nThe fault is reported by complex radio
modules with multiple physical units where functionality is distributed. An incompatibility has been found with the identification
method.\n\nINSTRUCTIONS\n1. Reset the alarming radio unit.\n2. 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 have a user alarm cable or nothing at all), and
ensure that the Secondary subunit has an Alarm Cap on the ASIG ALM connector. The secondary radio is the one that serves antenna ports
3 and 4.\n\n\n\n\nFAULT NAME\nRadio module internal hardware configuration mismatch\n\nFAULT ID\n1992:
EFaultId_FrInternalHwConfigurationMismatchAl\n\nMEANING\nThe fault is reported by complex radio modules with multiple physical units
where functionality is distributed. An incompatibility has been found between board revisions.\n\nINSTRUCTIONS\n1. Reset the alarming
29/05/2020 Alarms

major
release
radio unit.\n2. If a reset does not cancel the fault condition, replace one or both subunits so that they are both of the same
type.\n\n\n\n\nFAULT NAME\nRadio module low optical signal level to next hop\n\nFAULT ID\n1995:
EFaultId_FrLowOpticalSignalLevelToNextHopAl\n\nMEANING\nThe received optical signal on the link port is unexpectedly low from the next
hop (further from system module), though communication is still possible.\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the steps in
the listed order until the fault is resolved.\n1. 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 reported as the fault source.\n2. Reset the system module or radio
on the other end of the cable reported as fault source.\n3. Replace the SFP on the radio module port of the radio reporting the fault.\n4.
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.
\n5. Replace the optical cable reported as fault source.\n6. Replace the radio module reporting the fault, one with blinking red LED
display.\n7. 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 actions mentioned above have not cleared the fault situation, replace the extension baseband module (if the fault is
reported on the cable connected to the baseband module), the system module (if the fault is reported on the cable connected to the system
module), or the radio on the other end of the cable reported as fault source. \n\n\n\n\nFAULT NAME\nRadio module low optical signal level to
upper hop\n\nFAULT ID\n1994: EFaultId_FrLowOpticalSignalLevelToUpperHopAl\n\nMEANING\nThe received optical signal on the link port
is unexpectedly low from upper hop (toward the system module), though communication is still possible.\nThere 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
the fault source.\n\nINSTRUCTIONS\nNote: Perform the steps in the listed order until the fault is resolved.\n1. 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 the cable
reported as the fault source.\n2. Reset the system module or radio on the other end of the cable reported as the fault source. \n3. Replace
the SFP on the radio module port of the radio reporting the fault.\n4. 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. \n5. Replace the optical cable reported as fault source.\n6. Replace the
radio module reporting the fault (the one with blinking red LED display).\n7. 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 actions mentioned above have not cleared the fault
situation, replace the extension baseband module (if the fault is reported on the cable connected to the baseband module), the system
module (if the fault is reported on the cable connected to the system module), or the radio on the other end of the cable reported as fault
source. \n\n\n\n\nFAULT NAME\nReceive diversity expansion module communication failure\n\nFAULT ID\n1989:
EFaultId_FrReceiveDiversityExpansionModuleCommunicationFailureAl\n\nMEANING\nThe communication radio module with external
Receive Diversity Expansion Module (RDEM) is lost. The cable to the external RDEM module may be broken or disconnected, and external
module may have failed.\n\nINSTRUCTIONS\n1. Reset the alarming radio module.\n2. If it does not help, replace the cable between the
radio module and the Receive Diversity Expansion Module (RDEM).\n3. If previous steps have not cancelled alarm reported due to the fault,
replace the alarming radio module.\n\n\n\n\nFAULT NAME\nReceiving failure in Optical Interface\n\nFAULT ID\n2002:
EFaultId_OIC_RxAl\n\nMEANING\nThe incoming optical signal to the Small Form-Factor Pluggable (SFP) is missing, too weak, or the fiber
cable has been detached.\n\nThe 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 broken.\n\nINSTRUCTIONS\n1. Check the status of the module behind the
faulty link (power on, and so on).\n\n2. 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 faulty SFP. Replace the SFP if it is faulty.\n\n3. Clean the connectors, test the
fiber cable, and replace it if it is faulty.\n\n4. If the previous steps do not help, replace the module behind the faulty link.\n\n\n\n\nFAULT
NAME\nRET Antenna control failure\n\nFAULT ID\n1842: EFaultId_MotorJamAl\n1843: EFaultId_ActuatorJamAl\n1844:
EFaultId_NotCalibratedAl\n1845: EFaultId_NotConfiguredAl\n1846: EFaultId_ActuatorInterferenceAl\n\nMEANING\n1845: TILT is not
configured.\nOthers: Antenna tilting is not possible or might function incorrectly.\n\nINSTRUCTIONS\nPerform RET calibration. If that does
not help, replace the RET unit.\nIn case of 1845: send a valid configuration file to the alarming device.\n\n\n\n\nFAULT NAME\nRF BB bus
configuration error\n\nFAULT ID\n1905: EFaultId_FrRfBbBusConfigError\n\nMEANING\nThe RF Module baseband bus was configured
incorrectly.\n\nINSTRUCTIONS\n1. Confirm if the existing applied configuration is within the configured RF\nHW capabilities.\n2. Check BTS
connections and commissioning settings.\n3. Block or unblock the BTS.\n4. If HW configuration is confirmed, then this problem is caused by
eNB\nSW. Check other active alarms.\n\n\n\n\nFAULT NAME\nRF BB bus synchronization error\n\nFAULT ID\n1904:
EFaultId_FrRfBbBusSynchError \n\nMEANING\nThe baseband bus between the System Module and RF Module is out of
synchronization.\n\nINSTRUCTIONS\nInstructions 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. \n\nSection A: Check on the system module side:\n1. Check if the
connector seal is properly mounted and firmly in place. \n2. 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 connection/mounting.\n3. Check if the LED indicates the
faulty SFP (connected to System Module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly connected/mounted in the
SFP.\n5. Clean the optical connectors that are connected to the SFP. Reset the RF HW unit and check if this solves the problem.\n\nSection
B: Check on the radio module side:\n1. Check if the connector seal is properly mounted and firmly in place.\n2. 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
cables are not overly bent. If they are, replace them since overly bending the optical fiber cables damages them and can detach or damage
the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System Module end. Check the
measuring equipment documentation for instructions.\n3. OPTIONAL: Test the fiber cable (for example measure the optical attenuation) from
the RF Module end. Check the measuring equipment documentation for instructions.\n\nIf the alarm is still observed after executing steps
from sections A, B, and C, replace the RF module.\n\n\n\n\nFAULT NAME\nRF Module blocked\n\nFAULT ID\n1931:
EFaultId_FrBlocked\n\nMEANING\nThis 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 fault means that FR is blocked. When a LTE FSM/ASIA plays the role
of the master, or a LTE system module shares CPRI/Ir radio module with a SCDMA system module (dual mode configuration), and FR is
blocked, fault 48:EFaultId_UnitBlockedAl is detected, not 1931.\n\nINSTRUCTIONS\nNo action is needed.\n\n\n\n\nFAULT NAME\nRF
Module configuring failed\n\nFAULT ID\n1900: EFaultId_FrConfiguringFailed\n\nMEANING\nThe RF module configuration has failed because
of an HW or SW fault.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nFor URGA, URCB,
URCC, and URKA radio variants, if the fault is preceded by a\ndual 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 proceeding with the following steps:\nFor all radio variants:\n1.
Confirm if the currently applied configuration is within the configured RF HW capabilities.\nIn LTE-LTE sharing, check if the configuration of
both eNBs is consistent with the shared radio capability. Correct the configuration, recommission the eNBs, and reset the radio where fault
1900 is reported.\n2. Check BTS connections and commissioning settings.\n3. Block/unblock the BTS.\n4. If the HW configuration is
confirmed as correct, this problem is caused by the eNB SW. Check other active alarms.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD,
Flexi Zone, Flexi Zone SFN Antenna:\nReplace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF Module critical file not found\n\nFAULT ID\n1901: EFaultId_FrCriticalFileNotFound\n\nMEANING\nA
critical configuration file is missing from the RF Module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD:\n1. Verify if the HWP1 file is present in the FR module. Download the file if it is missing. Reset the FR module.\n2. If the file is
present, block/unblock the RF HW unit.\n3. If the problem continues after performing step 2, replace the FR HW unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD:\n1. Block/unblock the BTS.\n2. Replace the Flexi Zone Micro BTS.\n\nFlexi Zone:\n1. Reset Flexi Zone Access
Point.\n2. Replace the Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1. Reset Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone
SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module failure\n\nFAULT ID\n3010: EFaultId_RfModuleFailure\n\nMEANING\nThe BTS has
29/05/2020 Alarms

major
release
detected an abnormal operation or a failure in the internal functionality of the RF Module.\n\nINSTRUCTIONS\nNote: Perform the steps
below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset
the RF HW unit.\n2. If the problem still persists after step 1 has been performed, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi
Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the other active Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna faults and act accordingly.\n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3.
If that does not help, replace the faulty Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nRF Module faulty primary optical link\n\nFAULT ID\n1984: EFaultId_FrPrimaryLinkLossAl\n\nMEANING\nThe radio unit has detected
a failure on its optical connection to the system module or an upstream radio unit (chaining case).\n\nINSTRUCTIONS\n1. 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.\n2.
Clean the connectors, test the fiber cable, and replace them if they are faulty.\n3. If the previous steps do not help, replace the alarming radio
unit hardware.\n\n\n\n\nFAULT NAME\nRF Module file not found\n\nFAULT ID\n1902: EFaultId_FrFileNotFound\n\nMEANING\nThe RF
Module SW has detected that a non-critical configuration file is missing.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\n1. Check that the TEMP and CALI files are present. Upload any missing files. Reset the RF Module.\n2. If the files
are present, reset the FR HW unit.\n3. If the problem is still observed after performing step 1, replace the FR HW unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD:\n1. Block and/or unblock BTS.\n2. Replace the Flexi Zone Micro BTS.\n\nFlexi Zone:\n1. Reset the Flexi Zone
Access Point.\n2. Replace the Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1. Reset the Flexi Zone SFN Antenna.\n2. Replace the
Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module gain adjusting failure\n\nFAULT ID\n1908:
EFaultId_FrGainAdjust\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe TX output power
adjustment has failed.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nCLGC convergence has failed. Gain
target cannot be achieved.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF
HW unit.\n2. If the problem is still observed after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD,
Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the configuration. \n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna. \n3. If that does not help, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF Module out of order\n\nFAULT ID\n1912: EFaultId_FrOutOfOrder\n\nMEANING\nThe RF module is out
of order because of a software or hardware fault.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after step 1 has been performed, replace the RF HW unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module power input faulty \n\nFAULT ID\n1959:
EFaultId_FrPowerInputFaultAl\n\nMEANING\nInput 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.\n\nINSTRUCTIONS\n1. Check the power supply to the affected radio module.\n2. If
the alarm persists, replace the radio module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRF Module power supply output
faulty\n\nFAULT ID\n1918: EFaultId_FrPowerOutputFault\n\nMEANING\nThe power supply supervision has detected an overvoltage,
undervoltage, or overcurrent in the RF module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi
Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF module unauthorized\n\nFAULT ID\n4278: EFaultId_RfModuleUnauthorizedAl\n\nMEANING\nRFM
product authorization has failed because of missing RFM properties. RFM\nis not supported by the current BTS software release and the
BTS did not find\nrelevant 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.\n\nINSTRUCTIONS\n1. Make sure that the corresponding RFM plug-in module has been
installed on the network server in NMS (NetAct SW Archive).\n\n2. Update the corresponding RFM plug-in software module in the BTS/eNB
from NetAct. \n\n3. Supply the RFM plug-in software module to BTS/eNB locally via BTS Site Manager if NetAct connection is not available.
\n\n4. Block/unblock the BTS.\n\nNote: You need to commission the radio module before it can be taken into use. \n\n\n\n\nFAULT
NAME\nRF Power decreased \n\nFAULT ID\n1927: EFaultId_FrPowerDecreased\n\nMEANING\nThe highest temperature exceeds the
power decrease limit in the RF module.\n\nINSTRUCTIONS\n1. Check if the ambient temperature or environmental conditions are within the
design limits for the radio module. When the ambient temperature or environmental conditions are out of limits, the alarm is expected and no
further actions are needed.\n\n2. 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, and mount the module according to instructions and recommendations.\n\n3. Check if
excessive sunlight is causing an overheat. Install sunshield following mounting instructions and recommendations.\n\n\n\n\nFAULT
NAME\nRP3 routing collisions are detected on FR module\n\nFAULT ID\n1958: EFaultId_Rp3CollisionOnFr\n\nMEANING\nThe FR module
has detected permanent RP3 routing collisions in either downlink (TX), or uplink (RX) transmission directions.\n\nINSTRUCTIONS\n1. Check
the BTS connections and commissioning settings.\n2. Block and unblock the BTS (using the local BTS Site Manager connection if a remote
connection is not possible).\n\n\n\n\nFAULT NAME\nRRU CPU and DSP link failure\n\nFAULT ID\n1961:
DspLinkFailureAl\n\nMEANING\nThe CPU cannot connect to the DSP.\n\nINSTRUCTIONS\n1. Reset the RF Module.\n2. If that does not
help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRRU DPD self test failure\n\nFAULT ID\n1960:
EFaultId_DpdTestFailureAl\n\nMEANING\nThe RRU digital pre-distortion (DPD) has failed during self test.\n\nINSTRUCTIONS\n1. Reset the
RF Module. \n2. If that does not help, replace the RF Module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRRU power
loss\n\nFAULT ID\n1972: EFaultId_RruAcPowerLossAl\n\nMEANING\nThe RRU has lost its power supply.\n\nINSTRUCTIONS\n1. Check
the power connection to the RF module.\n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT
NAME\nRX out of order\n\nFAULT ID\n1911: EFaultId_FrRxOutOfOrder\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nThe RX RF synthesizer of the RF module is not locked.\nFor SNMP interface:\nThe received power is low for the
RRH.\nFor CPRI-A interface:\nThe RX path in the FR module is faulty.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\nThe RX path in the FR module is faulty.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD:\n1. Reset the RF HW unit.\n2. If the
problem continues after resetting the RF HW unit, replace the RF HW unit.\n3. In case of SNMP radio, the only way to clear the fault is to
reset the radio or replace the unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the HW
unit.\n2. If the problem continues after resetting the HW unit, replace the HW unit.\n\n\n\n\nFAULT NAME\nS1 eNB configuration update
failure\n\nFAULT ID\n6321: EFaultId_S1EnbConfigurationUpdate\n\nMEANING\nThe S1 eNB configuration update procedure has
failed.\n\nThe MME could not be informed about the modification of at least one of the following eNB configuration data:\n- eNB Name\n-
Supported TAs (TAC, PLMN Identities)\n- Default paging DRX\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the
alarm disappears:\n\n1. Check the availability of the MME.\n2. Check the connection with the MME.\n3. Disconnect and reconnect the
MME.\n\n\n\n\nFAULT NAME\nSerial console activated\n\nFAULT ID\n4334: EFaultId_SerialConsoleActivatedAl\n\nMEANING\nSerial
console is activated on BTS.\n\nINSTRUCTIONS\nDisable the serial console (set U-boot variable console_uart to -1).\n\n\n\n\nFAULT
NAME\nSevere SFP performance aggravation <optIf ID>\n\nFAULT ID\n1966:
EFaultId_SevereSfpPerformanceAggravationAl\n\nMEANING\nThe optical interface is not working properly; performance aggravation is
high.\n\nINSTRUCTIONS\n1. Check the cables between the System Module or ABIA and RF Module. \n\n2. Reset the RF Module. \n\n3. If
those do not help, block and unblock the site. \n\n4. If those do not help, replace the RF module that is causing the alarm.\n\n\n\n\nFAULT
NAME\nSevere SFP reception power aggravation <optIf ID>\n\nFAULT ID\n1967:
EFaultId_SevereSfpReceptionPowerAggravationAl\n\nMEANING\nThe optical interface is not working properly. The received power
aggravation is high. \n\nINSTRUCTIONS\n1. Check the cables between the System Module or ABIA and RF Module. \n\n2. Reset the RF
Module. \n\n3. If those do not help, block and unblock the site.\n\n4. If those do not help, replace the RF module that is causing the
alarm.\n\n\n\n\nFAULT NAME\nSFN Antenna Discovery Failure Due to Misconfiguration\n\nFAULT ID\n4346:
EFaultId_AntDiscFailMisconfAl\n\nMEANING\nThis denotes the inability to identify the SFN Antenna based on the information provisioned in
ANTMOD or APANTMOD.\n\nINSTRUCTIONS\n1. Verify that the ANTMOD or APANTMOD provisioning data have been correctly
29/05/2020 Alarms

major
release
entered.\n2. Verify if the siteID provisioned on the SFN Antenna was entered correctly.\n\n\n\n\n\nFAULT NAME\nSFN Antenna Not
Connected Successfully\n\nFAULT ID\n4347: EFaultId_AntNotConnectedSuccessfullyAl\n\nMEANING\nThe 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 Antenna does
not exist; or an SFN Antenna fault, Flexi Zone Micro BTS fault, or Flexi Zone Access Point fault prevents the SFN Antenna from successfully
connecting to the Flexi Zone Micro or Flexi Zone Access Point.\n\nINSTRUCTIONS\nIf 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:\n1. Check all other alarms posted
against the target SFN Antenna.\n2. Check the alarms raised on the SFN Antenna through WebUI.\n\n\n\n\nFAULT NAME\nSFP Failure
<optIf ID>\n\nFAULT ID\n1948: EFaultId_AbnormalOpticalSfpOfIrInterfaceAl\n\nMEANING\nThe optical interface is not working
properly.\nThe small form-factor pluggable (SFP) module might be missing or faulty.\n\nINSTRUCTIONS\nReplace the faulty
SFP.\n\n\n\n\nFAULT NAME\nSFP missing <OptIf ID>\n\nFAULT ID\n1964: EFaultId_SfpMissingAl\n\nMEANING\nThe optical interface is not
working properly. The Small Form-factor Pluggable (SFP) module might be missing, or it might be faulty.\n\nINSTRUCTIONS\nReplace the
faulty SFP.\n\n\n\n\nFAULT NAME\nSFP on RF Module faulty or unsupported\n\nFAULT ID\n1986:
EFaultId_SfpOnRadioModuleFaultyOrUnsupportedAl\n\nMEANING\nThe SFP on the radio unit is either faulty or not
supported.\n\nINSTRUCTIONS\n1. 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.\n2. Reset the affected radio unit.\n\n\n\n\nFAULT NAME\nShared radio not synchronized to
Radio Master\n\nFAULT ID\n4253: EFaultId_SharedRadioNotSyncToMasterAl\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nPerform
following actions until the problem is solved:\n1. Check the optical connection between the radio master system module and the shared
radio.\n2. Check the alarms in the radio master system module and act accordingly. \n3. Reset the radio master system
module.\n\n\n\n\n\nFAULT NAME\nSystem Module failure\n\nFAULT ID\n3000: EFaultId_SystemModuleFailure\n\nMEANING\nThe BTS has
detected an abnormal operation or a failure in the internal functionality of the System Module.\n\n\n\nINSTRUCTIONS\nNote: Perform the
steps below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1.
Reset the System Module.\n2. Replace the System Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS
or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTD-SCDMA minor alarm\n\nFAULT ID\n4179:
EFaultId_TdscdmaMinorAl\n\nMEANING\nThe Ir router has reported a minor alarm that is caused by TD-SCDMA. TD-LTE performance
might be affected.\n\nINSTRUCTIONS\nCheck the TD-SCDMA for active alarms.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT
ID\n3040: EFaultId_TemperatureAlarm\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the
listed order until the BTS fault disappears.\n\n1. Check the other BTS faults and act accordingly.\n\n2. 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, that is, the BTS
modules are not covered with anything. If the ambient temperature is too low, it takes a while for the BTS or the other modules to heat
themselves to the threshold value.\n\n3. Block and unblock the alarming module to reset it.\n\n4. Replace the alarming
module.\n\n\n\n\nFAULT NAME\nTemperature too low (Heating ongoing)\n\nFAULT ID\n1922: EFaultId_FrTemperatureTooLow
\n\nMEANING\nOut of order unit status: The radio unit is too cold for proper operation. Heating of the module is ongoing.\n\nWorking unit
status: The radio unit is below its normal operating temperature but is still capable of transmitting. Problems might
occur.\n\nINSTRUCTIONS\nWait until the alarm is canceled. This might take up to 30 minutes.\n\nIf the alarm is not canceled, check if the
ambient temperature is within the design limits for the radio module.\nIf the ambient temperature is out of limits, then the alarm is expected
and no further actions are needed.\n\n\n\n\nFAULT NAME\nToggling: <Fault name>\n\nFAULT ID\n4026:
Snapshot.\n\n\n\n\nFAULT NAME\nTransmission clock missing\n\nFAULT ID\n1816: EFaultId_Trans_Clk_MsgAl\n\nMEANING\nThe
reference clock monitoring has detected a loss of signal in the reference received from the FT.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check that the signal is being received from the reference clock source.\n2. Check the
TRS status.\n3. Check the synchronization settings of the TRS unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\nCheck the backhaul connection.\n\n\n\n\nFAULT NAME\nTransmission quality deteriorated\n\nFAULT ID\n1921:
EFaultId_FrTransmissionQualityDetoriated\n\nMEANING\nThe TX signal adjustment has failed.\n\nINSTRUCTIONS\n1. Reset the RF HW
unit.\n2. If the problem still persists after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nTuning frequency out of
range\n\nFAULT ID\n4043: EFaultId_TuningFrequencyOutOfRangeAl\n\nMEANING\nThe Radio Module has detected that the requested
frequency does not fit the capabilities offered by Radio Module.\n\nINSTRUCTIONS\nRe-configure the frequency settings in a proper way
with respect to the capabilities of the Radio Module.\n\n\n\n\nFAULT NAME\nTX input overdrive\n\nFAULT ID\n1985:
EFaultId_FrTxInputOverdriveAl\n\nMEANING\nHardware 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 operational but with degraded performance.\n\nINSTRUCTIONS\n1.
Confirm if the existing applied configuration is within the configured FR HW capabilities.\n2. Check the BTS connections and commissioning
settings.\n3. Restart the radio unit.\n4. If the fault condition persists after the radio restart, restart the BTS.\n5. If the HW configuration is
confirmed, then this problem is caused by the eNB SW. Check other active alarms.\n\n\n\n\nFAULT NAME\nTX out of order\n\nFAULT
ID\n1907: EFaultId_FrTxOutOfOrder\n\nMEANING\nThe RF module's TX path cannot be used.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after step 1 has been performed,
replace the RF HW unit.\n3. In case of SNMP radio, the only way to clear the fault is to reset the radio or replace the unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the connection and integrity of the antenna connector, cable,
and antenna.\n2. 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.\n3. Reset the BTS device. If the alarm persists, replace the Flexi Zone Micro BTS or Flexi Zone Access Point
or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTX output overdrive\n\nFAULT ID\n1983:
EFaultId_FrTxOutputOverdriveAl\n\nMEANING\nHardware 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 circuitry.\n\nINSTRUCTIONS\n1. 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 the
instructions for handling those alarms.\n2. Reset the alarming radio unit.\n3. If previous steps have not canceled the fault condition, replace
the alarming radio unit hardware.\n\n\n\n\nFAULT NAME\nUnit (module) dangerously overheating \n\nFAULT ID\n1937:
EFaultId_FrDangerouslyOverheat\n\nMEANING\nThe validated RF sensor temperature is greater than or equal to the pre-defined value in
the unit property file.\n\nINSTRUCTIONS\n1. Check if the ambient temperature/environmental conditions are within the design limits of the
radio module. When the ambient temperature/environmental conditions are out of limits, the alarm is expected and no further actions are
needed.\n\n2. 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 flow, and mount the module according to the instructions and recommendations.\n\n3. Check if
excessive sunlight is causing an overheat. Install sunshield, following the mounting instructions and recommendations.\n\n\n\n\nFAULT
NAME\nUnit (module) temperature is high \n\nFAULT ID\n1936: EFaultId_FrTempHigh\n\nMEANING\nThe validated RF module temperature
is higher than or equal to the pre-defined maximum allowed value.\n\nINSTRUCTIONS\n1. Check if the ambient temperature/environmental
conditions are within the design limits of the radio module. When the ambient temperature/environmental conditions are out of limits, the
alarm is expected and no further actions are needed.\n\n2. Check if the air flow is not blocked by some objects. Make sure the minimum
29/05/2020 Alarms

major
release
thermal clearances are followed. Remove any objects that might be blocking the air flow, and mount the module according to the instructions
and recommendations.\n\n3. Check if excessive sunlight is causing an overheat. Install sunshield, following the mounting instructions and
recommendations.\n\n\n\n\nFAULT NAME\nUnit blocked\n\nFAULT ID\n48: EFaultId_UnitBlockedAl\n\nMEANING\nA module is blocked with
the BTS Site Manager. \nThe purpose is to avoid fault indications that might be raised during the module maintenance task.\nThe 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 module with an SCDMA system module (dual mode configuration). In other cases, that is, when a WCDMA system module is
the master agent for the blocked shared (WCDMA/LTE) radio module, fault:1931 is raised.\n\nINSTRUCTIONS\nUnblock the module with the
BTS Site Manager.\n\n\n\n\nFAULT NAME\nUnit not supported by current BTS SW version\n\nFAULT ID\n95:
EFaultId_NotSupportedUnit\n\nMEANING\nAn 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 does not support the new unit version, is in
replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nUnit temperature is high\n\nFAULT ID\n2: EFaultId_UnitOverheatAl
\n\nMEANING\nThe temperature of a unit exceeds the threshold value.\n\nINSTRUCTIONS\nCheck the active fan alarms and the air flow of
the BTS.\n\n\n\n\nFAULT NAME\nUnit unidentified\n\nFAULT ID\n1923: EFaultId_FrUnitUnidentified\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the
problem still persists after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\n1. Check the configuration. Download the updated configuration if required.\n2. Reset the BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.\n3. Replace the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nUnsigned software release has been successfully downloaded\n\nFAULT ID\n4268:
EFaultId_UnsignedSwReleaseAl\n\nMEANING\nAn unsigned software release has been downloaded to a BTS system module that is
currently running a software release that implements software signature checking.\n\nINSTRUCTIONS\nNo manual action is needed from the
operator.\n\n\n\n\nFAULT NAME\nValidation of signed file failed\n\nFAULT ID\n4145:
EFaultId_SignatureValidationFailedAl\n\nMEANING\nSW file validation against its signature has failed.\n\nINSTRUCTIONS\nUpdate the BTS
to the required SW version.\nIf 7650 is active, immediate activation is mandatory.\n\n\n\n\nFAULT NAME\nVSWR major alarm\n\nFAULT
ID\n1837: EFaultId_VSWRMajorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe 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 radio module requires.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe detected VSWR
exceeds the predefined threshold. The antenna, antenna feed line, or both are disconnected, mismatched, or
damaged.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: \n1. Check the antenna cables,
connectors, antenna, and antenna line devices that can interfere with the RF signal. \n2. Check the antenna line (TX-cable-antenna)
impedance matching. \n\nNote: 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 means that the alarm is reported because of short or accidental peak of the VSWR value. The
alarm is cancelled if the condition is cleared at the radio or if fault 1957 is reported. \n\nFor 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 VSWR value is not
reflected in the alarm. To cancel the alarm, a radio reset or radio disconnection or power off is necessary. \n\nFlexi Zone Micro FDD, Flexi
Zone Micro TDD: \n1. Check the connection and integrity of antenna connectors, cable, and antenna. \n2. Reset the BTS device. If the alarm
persists, replace the BTS. \n\nFlexi Zone: \n1. Check the connection and integrity of the antenna connector, cable, and antenna. \n2. Reset
the Flexi Zone Access Point. If the alarm persists, replace the Flexi Zone Access Point. \n\nFlexi Zone SFN Antenna: \n1. Check the
connection and integrity of the antenna connector, cable, and antenna. \n2. Reset the Flexi Zone SFN Antenna. If the alarm persists, replace
the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nVSWR minor alarm\n\nFAULT ID\n1838: EFaultId_VSWRMinorAl\n\nMEANING\nThe
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 Module.\n\nINSTRUCTIONS\n1. Check the antenna cables, connectors, antenna, and antenna line devices that might
cause interference with the RF signal. \n\n2. Check the antenna line (TX-cable-antenna) impedance matching. \n\nNote: 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
alarm is reported due to short/accidental peak of VSWR value. \nFor 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 will not be reflected in the alarm."
Table 38-11: BASE_STATION_OPERATION_DEGRADED

major
release
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\n\nA major fault (or faults) has occurred in the base station.\n\nCheck the reason
for the fault from the supplementary text field of the alarm.\n\nThe 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.\n\nDo not cancel the alarm. The system
automatically cancels the alarm when the fault has been corrected.
source of the alarm and instructions fields of the corresponding alarms). \n\nBelow 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 descriptions refer to LTE System
Libraries. The BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local customer
support. \n\nFAULT NAME\n2M external reference missing\n\nFAULT ID\n1899: EFaultId_2MExtRefMissAl\n\nMEANING\nThe reference
29/05/2020 Alarms

major
release
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 Module.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the alarm disappears.\n\n1. Check the cabling
(connected to Sync In interface).\n\n2. Check if the 2.048 MHz reference source is working normally, and the 2.048 MHz signal is
available.\n\n3. Replace the alarming module.\n\n\n\n\nFAULT NAME\nAddress mismatch in summing\n\nFAULT ID\n2019:
EFaultId_Muksu_SsubMmAl\n\nMEANING\nThere is a baseband bus address mismatch in the summing. There are two possible
causes:\n\n1. A configuration error (two different baseband units functioning) - after an acknowledgement, the fault returns.\n\n2. Data
corruption on the bus - appears once when an unsynchronized data is sent by the baseband.\n\nINSTRUCTIONS\nCheck the antenna
mapping to the local cells in the commissioning file.\n\n\n\n\nFAULT NAME\nAntenna link is down\n\nFAULT ID\n476:
EFaultId_Rp3BusError\n\nMEANING\nThe antenna (RP3) link is down. The transmitter or receiver drops from
synchronization.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Restart the BTS.\n2. If
that does not help, replace the alarming module. \n\nFlexi 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. \n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD: If FBBx or ABIx is causing the alarm,
replace the FBBx or ABIx.\n\nFlexi 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 Antenna.\n\n\n\n\nFAULT NAME\nBaseband bus configuration of <x> was
rejected\n\nFAULT ID\n1811: EFaultId_BbBus_ConfFailedAl\n\nMEANING\nThe baseband-bus-related configuration of <x> has been
rejected by the HW SW, DSP, or RF SW.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
that causes the alarm (system module or FBBx/ABIx).\n\n\n\n\nFAULT NAME\nBB bus transmission error\n\nFAULT ID\n2017:
the system module.\n\n3. Replace the alarming module (system module).\n\n\n\n\nFAULT NAME\nBTS file error\n\nFAULT ID\n1802:
EFaultId_FileRequestFlashAl\n\nMEANING\nA software download to FSP, DSP, ABIx or FR has failed.\n\nINSTRUCTIONS\nNote: Perform
the following steps in the listed order until the fault disappears:\n\n1. Use BTS Site Manager to perform a full commissioning to the BTS using
the NetAct backup upload SCF file as template.\n\n2. Download two different software packages so that the faulty file is removed from the
BTS.\n\n3. Download the software again.\n\n4. Replace the System Module.\n\n\n\n\nFAULT NAME\nBTS internal SW management
problem\n\nFAULT ID\n3090: EFaultId_BtsInternalSwManagementProblem\n\nMEANING\nA software update to a module or sub-assembly
has failed, or a corrupted SW file has been detected in the FLASH.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order
until the BTS fault disappears:\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the other active BTS
faults. If the ROM disk is corrupted, change the alarming module.\n2. Reset the RF Module and/or System Module (depending on the fault
source) by blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n5. Replace the alarming
module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. 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 Access Point.\n2. Reset the Flexi Zone Micro BTS or Flexi Zone
Access Point by blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n\nFlexi Zone:\n1. Check the
other active Flexi Zone Access Point faults. If the ROM disk is corrupted, change the Flexi Zone Access Point.\n2. Reset the Flexi Zone
Access Point to trigger new SW load.\n3. Check the SW files.\n\nFlexi Zone SFN Antenna:\n1. Check the other active Flexi Zone SFN
Antenna faults. If the ROM disk is corrupted, change the Flexi Zone SFN Antenna.\n2. Reset the Flexi Zone SFN Antenna to trigger new SW
load.\n3. Check the SW files.\n\n\n\n\nFAULT NAME\nBTS master clock tuning failure\n\nFAULT ID\n1818:
EFaultId_Ov_OscAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: \nThe 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 in
BPF, or greater than or equal to the Max.OcxoControlValue.Alarm.Set value specified in BPF.\n\nFlexi Zone Micro FDD, Flexi Zone Micro
TDD, Flexi Zone SFN Antenna:\nThe 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.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault disappears:\n1. Check the other alarms of the BTS and
FTM and act accordingly.\n2. If there are no other synchronization-related alarms active. Start the fast tuning with the BTS Site Manager.\n3.
Reset the site. Run fast tuning again.\n4. 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 the Sync Out interface of the Flexi System Module: the required accuracy
is +/-0.015ppm. If the reference accuracy is correct, run fast tuning.\n5. If that does not help, replace the system module.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nThis 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 producing an inaccurate reference. Perform the
following steps to isolate the cause of the fault:\n1. Identify the currently selected synchronization reference source of the BTS with the active
1818 fault. If it is a transport-based reference source that involves a time source distributed over the backhaul network (for example,
Synchronous Ethernet or IEEE1588-2008 (Timing over Packet)), verify that there are no alarms or faults associated with the respective time
servers. If there is a fault associated with a network-based time server, it is also likely that other FZMs being served by these devices will also
be reporting the 1818 fault. Correct any identified faults associated with the associated Synchronous Ethernet or IEEE1588-2008 master
clock, and if the 1818 fault subsequently clears.\n2. 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 with the transport reference source master clock, the BTS likely
has an internal problem, which requires its replacement.\n\n\n\n\nFAULT NAME\nBTS or unit temperature too high\n\nFAULT ID\n4182:
EFaultId_BtsTempTooHighAl\n\nMEANING\nThe temperature of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna has exceeded the predefined threshold.\n\nINSTRUCTIONS\n1. Validate if the ambient temperature is within the specifications and
if no foreign debris has accumulated on the unit. \n\n\n\n\n\nFAULT NAME\nBTS reference clock missing\n\nFAULT ID\n3080:
EFaultId_BtsReferenceClockMissing\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThis BTS fault
indication is generated if the reference clock monitoring function of the BTS does not receive the configured synchronization reference signal,
if all the synchronization reference signals are missing, or if the BTS has been in holdover mode and holdover time has run out (TDD only).
\n\nBackground information:\n\nThere is configurable synchronization priority list in the FlexiBTS, AirScaleBTS.\n\nNormally, 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
sources are checked against the reference source priority list in the BTS commissioning file and deviations regarding the missing source
generate a faults.\n\nThe source for the TRS can be TDM interface signal (for example, E1, T1, and so on), physical layer Synchronous
29/05/2020 Alarms

major
release
Ethernet (SyncE) signal or application layer Timing over Packet (ToP) in which the timing information to BTS(s) is generated by a ToP master.
The TRS reference source priority selection also user-selectable. Furthermore, if a signal listed in the TRS references is not received, a
BASE STATION TRANSMISSION ALARM is reported., \n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe
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 GPS satellites, there is a loss of its 1 PPS clock or there is a loss of communication with the receiver.\nThe BTS supports a
ToP or SyncE reference source that has configurable priorities relative to each other through the "synchroSourceList"
parameter.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nDepending on the installed and
commissioned synchronization source(s) listed in the "Meaning" section, see the commissioned synchronization option below and perform
the steps in the listed order until the BTS fault indication disappears.\n\nGPS receiver (PPS source):\n1. 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 which is
normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of
poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a
fairly poor sky visibility is that the BTS fault is activated/canceled every now and then.\n\n2. There might be a malfunction in the GPS
receiver. Perform a (remote) power reset for the GPS receiver.\n\n3. There might be a malfunction in the BTS. Perform a BTS site reset.\n\n4.
The GPS cable and/or connectors might be damaged. Check the cable and the connectors.\n\n5. There might be a HW fault in the GPS
receiver. Check the operation and change the HW, if needed.\n\nExternal 2.048 MHz signal:\n1. 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, check the cables. Note
that because the device type is not known, detailed instructions cannot be given - refer to the appropriate user manual of the device for
further actions.\n\n2. There might be a malfunction in the BTS. Perform a BTS site reset.\n\nFTM reference (TDM, SyncE or ToP as
source):\n1. 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 synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The
synchronization source of the FTM (set by the FTM synchronization priority setting) might be missing, causing the FTM's internal clock to
drop to holdover mode. In this case, the fault in the transmission NETWORK must be corrected (the FTM itself might be working fine).\n\n2.
Check the alarms of the FTM unit and act accordingly.\n\n3. Check the synchronization settings of the FTM unit.\n\n4. There might be a
malfunction in the BTS. Perform a BTS site reset.\n\n5. 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 failure, but there might be connection failures in the transmission
or packet network, causing the FTM clock to drop to holdover mode. Especially the BTS fault indication activity (frequent BTS fault indication
activations/cancels instead of a stable BTS fault indication state) points to the instability of the transmission network, not to a failure in the
unit.\n\nIf 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, replace the System Module.\n\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\nDepending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned
synchronization option below and perform the steps in the listed order until the BTS fault indication disappears.\n\nGPS source:\n1. 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) power reset of the GPS receiver. If the associated GPS receiver communication or 1 PPS clock fault is not cleared within
5 minutes after the remote power reset, a Flexi Zone Micro BTS replacement is recommended.\n\nSyncE or ToP as source:\n1. Check the
alarms of the Flexi Zone Micro BTS or Flexi Zone SFN Antenna unit and act accordingly.\n2. 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 the required
synchronization information to the Flexi Zone Micro BTS. Correct any associated PRC or master clock problems.\n3. 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
replacement might be necessary.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n4001:
before the reset.\n\n2. Reset (block and unblock) the BTS.\n\n\n\n\n\n\n\nFAULT NAME\nBTS SW download or activation failed\n\nFAULT
ID\n29: EFaultId_FileCorruptionAl\n30: EFaultId_SwUpdateAl\n\nMEANING\nThe 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 system.\n\n\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Retry the SW update.\n2. If other flash memory-related faults are
active for the alarming module at the same time, replace the alarming module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone
Controller:\n1. Retry the SW update.\n2. If other flash memory-related faults are active for the BTS at the same time, replace the
BTS.\n\nFlexi Zone Access Point:\n1. Retry the SW update by resetting the Flexi Zone Access Point using the BTS SM.\n2. If other flash
memory-related faults are active for the Flexi Zone Access Point at the same time, replace the Access Point.\n\nFlexi Zone SFN Antenna:\n1.
Retry the SW update by resetting the Flexi Zone SFN Antenna using the BTS SM.\n2. If other flash memory-related faults are active for the
Flexi Zone SFN Antenna at the same time, replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nCarrier aggregation relation
configuration error\n\nFAULT ID\n6291: EFaultId_CarrierAggregationRelationConfigurationErrorAl\n\nMEANING\nBTS has detected carrier
aggregation relation misconfiguration. One or more of the configured carrier aggregation relation(s) points towards a cell that does not exist in
any of the BTSs within the configured carrier aggregation cluster.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the
29/05/2020 Alarms

major
release
BTS fault disappears.\n\n1. Check BTS commissioning that all the carrier aggregation relations are pointing towards a proper cell that exists
within the carrier aggregation cluster. Modify or delete the mismatching relations.\n2. If an existing cell is totally missing from BTS within the
carrier aggregation cluster, add the cell.\n3. If there are no mismatches in the carrier aggregation relations, reset the BTS.\n\n\n\n\nFAULT
NAME\nCommissioning error: <x>\n\nFAULT ID\n3060: EFaultId_CommissioningError\n\nMEANING\nSome of the commissioning
parameters are either missing or faulty, or there is a mismatch between them.\n\nINSTRUCTIONS\nNote: Perform the steps below in the
listed order until the BTS fault disappears.\n\n1. Check the commissioning parameters with the BTS Site Manager Commissioning
Wizard.\n\n2. Load the correct commissioning file to the BTS.\n\n\n\n\nFAULT NAME\nCommunication failure\n\nFAULT ID\n1806:
EFaultId_CommunicationFailureAl\n\nMEANING\nCommunication with an application has failed. It has not replied to the message that has
been sent/resent to it.\n\nINSTRUCTIONS\n1. 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 causing the alarm.\n2. Check the fault history.\n\n\n\n\nFAULT
NAME\nConfiguration error: <x>\n\nFAULT ID\n3070: EFaultId_ConfigurationError \n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\n1. Check the installed
HW/SW version compatibility and the HW compatibility with the current BTS configuration.\n\n2. Check that the BTS cell parameters from the
Network management system match\nthe BTS HW configuration (for example, frequency, power).\n\n3. Check the Network management
system alarms for the alarming local cell (LCR).\n\n4. Recommission the BTS to ensure that all parameters are correctly
configured.\n\n\n\n\nFAULT NAME\nConnection to ToP master missing\n\nFAULT ID\n4058:
EFaultId_TopRefClkMissingAl\n\nMEANING\nThe reference clock monitoring has detected a loss of the ToP reference clock signal received
from the master clock.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault disappears.\n\n1. Check the
Ethernet interface functionality used by Timing Over Packet. Check if other faults related to the Ethernet interface exist.\n\n2. Check Timing
Over Packet configuration. Ensure that the Master clock IP address is configured properly and that the Master clock supports the given
parameters.\n\n3. Check the Master clock functionality.\n\n4. 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.\n\n\n\n\nFAULT NAME\nControl Plane IP Address
Mismatch\n\nFAULT ID\n6816: EFaultId_CplaneIpAddressMismatchAl\n\nMEANING\nThe 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 (the same IP is used for both
C and M planes).\n\nINSTRUCTIONS\nCorrect the value of the parameter "IPNO:cPlaneIpAddress" to match the one configured in
FxP.\n\n\n\n\nFAULT NAME\nCRAN inter-BTS connection loss alarm\n\nFAULT ID\n4275:
EFaultId_CranInterBtsConnectionLossAl\n\nMEANING\nThe connection between two BTSs in the Centralized Radio Access Network
(CRAN) cluster is not detected or is lost.\n\nINSTRUCTIONS\nCheck the optical connection between the extension baseband cards of the
BTSs working in the same CRAN cluster.\n\n\n\n\nFAULT NAME\nCRAN intra-BTS FSP connection loss alarm\n\nFAULT ID\n4318:
EFaultId_CranInterFspConnectionLossAl \n\nMEANING\nThe connection between FSPs using CPRI front-haul communication within the
BTS in CRAN operation is lost.\n\nINSTRUCTIONS\nCheck the optical connection:\n1) between the FSP cards or \n2) between FSP card
and system module card \nsupporting cells working in the same CRAN cluster.\n\n\n\n\nFAULT NAME\nDSP application fatal error\n\nFAULT
Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone\nSFN Antenna.\n\n\n\n\nFAULT NAME\nDSP platform fatal
BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nExternal GPS receiver in holdover\n\nFAULT ID\n4210:
EFaultId_ExtGpsInHoldoverAl\n\nMEANING\nThe external GPS or GNSS receiver module has lost satellite visibility and is currently
operating in holdover mode.\n\nINSTRUCTIONS\n1. 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 properly, that is, the sky visibility is not good enough. Refer to
the documentation for installations, and if there are deviations with the actual installation, re-install the GPS or GNSS antenna. Note that even
when the GPS or GNSS antenna has good sky visibility, the problem might be caused by installing the GPS or GNSS antenna too close to
the transmitter antennas of the BTS, causing disturbances to the GPS or GNSS receiver. \n2. Check the other possible alarms or fault
indications of the GPS or GNSS receiver and the BTS, and act accordingly.\n3. There might be a malfunction in the GPS or GNSS receiver.
Perform a (remote) power reset for the GPS or GNSS receiver module.\n4. 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 settings. The power needs to be ON in
this case (while in shared configuration, one receiver feeds the power towards the antenna, and power feeding setting of the other receivers
is OFF).\n5. 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 or GNSS receivers, and one receiver might feed the power to the antenna. The fault indication
might be caused by a failure in another GPS or GNSS receiver. \n6. Perform a local or physical power reset for the alarming GPS or GNSS
receiver module.\n7. 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. Check the operation and change them if needed.\n8. 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.\n\n\n\n\nFAULT NAME\nExternally triggered
DSP fatal error\n\nFAULT ID\n6708: EFaultId_ExternallyTriggeredDspFatalErrAl\n\nMEANING\nThe BTS has purposely triggered a GPIO
reset for the DSP.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nIf an FSP in the BTS generates this fault,
there is a malfunction in the whole BTS.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n1. Reset the System Module.\n2. Replace the System
Module, or FBBx or ABIx module (according to the fault source)\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nPerform the steps below in the listed order until the fault disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
29/05/2020 Alarms

major
release
Antenna.\n\n\n\n\nFAULT NAME\nFailure in optical interface\n\nFAULT ID\n3030:
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFault between FSM and FSP because of the
lack of RP1 clock\n\nFAULT ID\n412: EFaultId_LostFrameSync\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD:\nSynchronization between
the FCM/FCT and FSP is lost.\n\nAirScale BTS FDD, AirScale BTS TDD:\nSynchronization between the FCT and ABIx is
lost.\n\nINSTRUCTIONS\n1. Block/unblock the BTS.\n2. 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. Otherwise, replace the extension baseband module
reporting the fault.\n\n\n\n\nFAULT NAME\nFirmware SW mismatch\n\nFAULT ID\n2056: EFaultId_SwMismatchAl\n\nMEANING\nThe
software update to the BTS has failed or the BTS software is corrupted.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Switch to the most recently-active BTS configuration.\n2. Retry
the software update.\n\nFlexi Zone (Flexi Zone Access Point):\n1. Reset the Flexi Zone Access Point to trigger SW upgrade again.\n2.
Replace the Flexi Zone Access Point.\n\nFlexi Zone (Flexi Zone Controller):\n1. Retry the embedded SW update manually. \n2. If this does
not help, switch to the latest active BTS configuration.\n3. Retry the SW update.\n\nFlexi Zone SFN Antenna:\n1. Reset the Flexi Zone SFN
Antenna to trigger SW upgrade again.\n2. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFlash operation failure\n\nFAULT
ID\n214: EFaultId_FlashWrAl\n215: EFaultId_FlashRdAl\n\nMEANING\nA flash memory operation failure. If this fault continuously appears,
the flash chip might be broken.\n\nINSTRUCTIONS\n1. Check the other active alarms. If the ROM disk is corrupted, change the
alarming\nmodule.\n\n2. Reset the alarming module. There are no recovery actions, therefore\nreset can be tried once. If that does not help,
replace the alarming\nmodule.\n\n\n\n\n\nFAULT NAME\nFSP overheating\n\nFAULT ID\n4077:
EFaultId_FspOverheatingAl\n\nMEANING\nThe temperature of the FSP/ABIx board has exceeded the critical threshold
value.\n\nINSTRUCTIONS\n1. Check the fans and ensure that the ambient temperature on the site is acceptable.\n2. If that does not help,
replace the alarming module.\n\n\n\n\nFAULT NAME\nFSP subunit lost\n\nFAULT ID\n4341: EFaultId_FspSubunitLostAl\n\nMEANING\nAn
FSP (ABIx) subunit is unavailable (lost).\n\nINSTRUCTIONS\nAirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the
listed order until the fault is resolved:\n1. Reset the BTS using block or unblock.\n2. Replace the extension baseband module (ABIx)
according to the fault source.\n\n\n\n\n\nFAULT NAME\nGPS Receiver alarm: control interface not available\n\nFAULT ID\n4011:
EFaultId_GPSSystemElementAl\n\nMEANING\nThe BTS has detected a communication problem with the GPS receiver.\n\nThe fault is
ignored until the GPS receiver has reached the commissioned state.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nPerform 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 minutes from the start of the fault prior to performing the actions below).\n\nControl Interface not
available:\n1. 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 interface. Otherwise, perform a (remote) power reset for the GPS receiver.\n2. Perform a (remote)
BTS site reset for the whole BTS.\n3. Perform a power reset for the whole BTS.\n4. 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 oxide and other kind of dirt: the pin
connection quality is good. \n5. The cable between the GPS receiver and the BTS might be faulty. Check the situation and change the cable if
needed.\n6. There might be a hardware fault in the GPS receiver. Check the operation and change the GPS module if needed.\n7. There
might be a hardware fault in the BTS System Module. Check the operation and change the System Module if needed.\n\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nPerform the steps below in the listed order until the fault
disappears.\n\nControl Interface not available:\n1. 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 possible reason could be that BTS or access point, and the GPS
receiver does not support common interface. Otherwise, perform a (remote) power reset for the GPS receiver.\n2. Perform a (remote) site
reset for the entire Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. Perform a power reset for the entire Flexi
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n4. 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 Antenna.\n\n\n\n\nFAULT NAME\nGPS
receiver alarm: not tracking satellites\n\nFAULT ID\n4122: EFaultId_GpsReceiverNotTrackingSatellitesAl\n\nMEANING\nThe fault indicates
poor GPS antenna installation.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nPerform the
steps below in the listed order until the fault disappears.\nNot tracking satellites:\n1. 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 enough. Refer to the documentation for
installations and if there are deviations with the actual installation, re-install the GPS antenna. Note that even when the GPS antenna has a
good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antenna(s) of the BTS, causing
disturbances for the GPS receiver. \n2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS
receiver.\n3. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module, if needed.\n\nFlexi Zone
Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nPerform the steps below in the listed order until the fault
be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.\n\n\n\n\nFAULT NAME\nGTP tunnel setup for
29/05/2020 Alarms

major
release
inter-site CA failed\n\nFAULT ID\n6296: EFaultId_PermanentGtpRoutesSetupFailureAl\n\nMEANING\nThe GTP tunnel between two Flexi
Zone Access Points is out of service.\n\nINSTRUCTIONS\n1. Reset the faulty Flexi Zone Access Points.\n2. Reset the Flexi Zone
Controller.\n\n\n\n\nFAULT NAME\nIncompatible SW version detected\n\nFAULT ID\n23: EFaultId_IncompatibleSwVersionAl
modules with factory SW loaded, SW update is a mandatory step.\n\n\n\n\nFAULT NAME\nInter eNB CA parameter(s) inconsistency in
between eNBs\n\nFAULT ID\n6282: EFaultId_InterEnbCaParamsInconsistencyAl\n\nMEANING\nAn inconsistency has been detected
between cluster members, which prevents the\ninter-eNB CA feature from being enabled.\n\nINSTRUCTIONS\nRe-configure parameters
that are related to the "Inter eNB Carrier Aggregation" feature.\n\n\n\n\nFAULT NAME\nInter eNB carrier aggregation configuration does not
match available baseband HW\n\nFAULT ID\n4305: EFaultId_InterEnbCaConfNotMatchingBbHwAl\n\nMEANING\nThe configuration of the
inter-eNB carrier aggregation in the SCF of own eNB and peer eNBs cannot be supported with the detected HW.\n\nINSTRUCTIONS\nTo
clear the alarm, do any of the following:\n- Switch off the inter-eNB carrier aggregation completely.\n- Provide the necessary HW,
configuration, or both, and reset the BTS.\n- Replace the HW (which has been configured, but faulty) if the HW is the root\ncause of the
problem, and reset the BTS.\n\n\n\n\n\nFAULT NAME\nInter eNB communication failure\n\nFAULT ID\n6284:
EFaultId_InterEnbCommunicationFailureAl\n\nMEANING\nThe 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, like the "Inter eNB Carrier aggregation" feature, are
disabled.\n\nINSTRUCTIONS\nIn 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 actions are needed from the operator.\n\n\n\n\nFAULT NAME\nInter eNB
SW inconsistency in between cluster members\n\nFAULT ID\n6283: EFaultId_InterEnbSwInconsistencyAl\n\nMEANING\nAn SW
incompatibility has been detected between cluster members, which prevents the inter-eNB CA feature from being
enabled.\n\nINSTRUCTIONS\nUpgrade or downgrade SW so that the same version is in all eNBs that have the "Inter eNB Carrier
Aggregation" feature.\n\n\n\n\nFAULT NAME\nInter eNB synchronization loss\n\nFAULT ID\n6287:
EFaultId_InterEnbSyncLossAl\n\nMEANING\neNB is informed about sync loss of neighbor eNB in same cluster and as a consequence
needs to deactivate Carrier Aggregation feature.\n\nINSTRUCTIONS\nRead partner eNB ID from diagnostic information and check alarms
and synchronization status on partner eNB.\n\n\n\n\nFAULT NAME\nInternal MTU configuration failure\n\nFAULT ID\n4025:
EFaultId_MtuConfigurationFailureAl\n\nMEANING\nThe internal maximum transfer unit (MTU) configuration has failed on the FSP or
FBB/ABIx.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System Module that
is causing the alarm.\n2. Replace the System Module that is causing the alarm.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone,
Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. Replace the Flexi
Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nInter-Site CA incorrect cluster
configuration\n\nFAULT ID\n4289: EFaultId_InterSiteCaIncorrectClusterConfigurationAl\n\nMEANING\nAn incorrect configuration of inter-site
Carrier Aggregation cluster has been detected between an eNB and other eNBs related by inter-site Carrier Aggregation relation, which
prevents the inter-site Carrier Aggregation feature from being enabled.\n\nINSTRUCTIONS\nChange 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 caClusterId, and so that values of
LNBTS caClusterMemberId are unique on eNBs that have the same value of LNBTS caClusterId.\n\n\n\n\nFAULT NAME\nInter-Site CA link
establishment failure\n\nFAULT ID\n4290: EFaultId_InterSiteCaLinkEstablishmentFailureAl\n\nMEANING\nA dedicated link between an eNB
and other eNBs related by inter-site Carrier Aggregation relation cannot be established, which prevents the inter-site Carrier Aggregation
feature from being enabled.\n\nINSTRUCTIONS\n1. Check if the inter-site Carrier Aggregation feature is enabled on the partner eNB.\n2.
Check if network communication between specific dedicated ports on the eNB, and its partner eNB used for inter-site Carrier Aggregation
proprietary interface messaging, is possible and not blocked (for example, by firewall filtering rules).\n3. Check if there are not other critical or
major alarms on the eNB and its partner eNB.\n4. Restart the inter-site Carrier Aggregation feature on the eNB and its partner eNB.\n5.
Reset the eNB and its partner eNB.\n\n\n\n\nFAULT NAME\nInter-Site CA SW interface incompatibility\n\nFAULT ID\n4288:
EFaultId_InterSiteCaInterfaceIncompatibilityAl\n\nMEANING\nAn SW interface incompatibility has been detected between an eNB and other
eNBs related by inter-site Carrier Aggregation relation, which prevents the inter-site Carrier Aggregation feature from being
enabled.\n\nINSTRUCTIONS\nUpgrade or downgrade SW so that the same version is on the eNBs related by inter-site Carrier Aggregation
relations.\n\n\n\n\nFAULT NAME\nInter-Site CA X2 link unavailability\n\nFAULT ID\n4291:
EFaultId_InterSiteCaX2UnavailabilityAl\n\nMEANING\nThere 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 feature from being enabled.\n\nINSTRUCTIONS\nProvide X2
link connections between eNBs related by inter-site Carrier Aggregation relations.\n\n\n\n\nFAULT NAME\nMaster unit has lost connection to
the slave unit\n\nFAULT ID\n4019: EFaultId_KeepAliveStatusErrorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nThe connection to the FSP/ABIx or DSP has been lost, or the sub-module reports an error situation.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe connection to the DSP module has been lost.\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault
disappears.\n\n1. Reset the BTS.\n2. Replace the faulty module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nMBMS
subframe pattern share exceeds available share\n\nFAULT ID\n6852: EFaultId_MbmsSubframePatternExceededAl\n\nMEANING\nThe
deployed MBMS subframe pattern share is less than the required MBMS subframe pattern share, which is configured with the MBSFN
parameter subfrPShareRequired.\n\nINSTRUCTIONS\nPerform the following steps until the alarm disappears:\n\n1. 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
parameters to get additional subframe resources.\n2. Push the delta plan file to the BTS.\n\n\n\n\nFAULT NAME\nMessage routing problem
in receiver (RX)\n\nFAULT ID\n2058: EFaultId_MuksuMsgRoutingFailedAl\n\nMEANING\nAn interrupt is generated if a message does not get
routed.\n\nThis is considered normal when DSPs are starting up and RP3 sync is done.\n\nINSTRUCTIONS\nIf OptIf is the source:\n\n1.
Check the antenna mapping to the local cells in the commissioning file.\n2. Depending which optical interface is notified as faulty check the
cables between \n - the System Module and RF Module, or the cable between the FBB module and the RF Module (Flexi BTS FDD/TDD),\n -
the cable between the ABIx module and the RF Module (AirScale BTS FDD/TDD).\n3. Block and unblock the RF Module.\n4. Perform a BTS
reset. \n5. Replace the RF module behind the optical link.\n\nFlexi BTS FDD/TDD:\nIf FSP is the source:\n1. Perform a System Module
reset.\n2. If that does not help, replace the System Module.\n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD:\nIf FBB/ABIx is the source:\n1.
Perform a System Module reset.\n2. If that does not help, replace the FBB/ABIx card.\n\n\n\n\nFAULT NAME\nMS 1PPS control interface not
available\n\nFAULT ID\n4207: EFaultId_Ms1PpsControlInterfaceNotAvailAl\n\nMEANING\nThe 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, conveying Time of Day
information, from the Master Flexi Zone Micro BTS or Flexi Zone Access Point board.\n\nINSTRUCTIONS\n1. Perform a (remote) Flexi Zone
Micro BTS or Flexi Zone Access Point site reset.\n2. Perform a power reset for the entire Flexi Zone Micro BTS or Flexi Zone Access
Point.\n\n\n\n\nFAULT NAME\nMS 1PPS reference missing\n\nFAULT ID\n4206: EFaultId_Ms1PpsReferenceMissingAl\n\nMEANING\nThe
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 signal received from the Master Flexi Zone Micro BTS or Flexi Zone Access Point board.\n\nINSTRUCTIONS\n1.
Perform a (remote) Flexi Zone Micro BTS or Flexi Zone Access Point site reset.\n2. Perform a power reset for the entire Flexi Zone Micro
BTS or Flexi Zone Access Point.\n3. 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.\n\n\n\n\nFAULT NAME\nNo connection to unit\n\nFAULT ID\n10:
EFaultId_NoConnectionToUnitAl \n\nMEANING\nThe connection to a module that belongs to the BTS configuration has been lost.\n\nIn case
of SNMP radios, there is a problem with the optical interface or an internal fault, which results in a radio reset.\n\nINSTRUCTIONS\n1.
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.\n\n2. Check the fault history.\n\n\n\n\nFAULT NAME\nNo MME capacity assigned by Core Network\n\nFAULT ID\n6264:
29/05/2020 Alarms

major
release
EFaultId_S1ZeroCapPlmns\n\nMEANING\nThe 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.\n\nThe PLMNs that are considered misconfigured by the BTS are:\n-
currently configured at the BTS for one or more cells\n- 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 greater than zero. Because of this, the BTS cannot select
any of these MMEs for any new UEs attempting registration in these PLMNs.\n\nAll previously registered UEs in these PLMNs remain
unaffected.\n\nINSTRUCTIONS\nCheck 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 serving them and that the relative capacity of that MME is greater than
zero.\n\n\n\n\nFAULT NAME\nNot able to synchronize baseband bus with <x>\n\nFAULT ID\n1815:
Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nNTP Frequency Synchronization Server Not Reachable:
$IP\n\nFAULT ID\n6821: EFaultID_NtPSyncServerNotReachableAl\n\nMEANING\nThis 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 address of the affected NTP
server.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the fault disappears.\n1. Check the Ethernet interface
functionality used by the Network Time Protocol. Check if other faults related to the Ethernet interface exist.\n2. Check the Network Time
Protocol configuration; ensure that the NTP Server IP address is configured properly.\n3. Check the Network Time Protocol server
functionality.\n4. 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.\n\n\n\n\nFAULT NAME\nOperation on shared optical port failed\n\nFAULT ID\n4180:
EFaultId_OperationOnSharedOpticalPortFailedAl\n\nMEANING\nThe shared OptIF mode cannot be read from or changed in the FBBC
card.\n\nINSTRUCTIONS\nFault 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 can decide whether to change the FBBC card or not.\n\n\n\n\nFAULT NAME\nOptical cable inter-
BTS or inter FSP cards too long for CRAN\n\nFAULT ID\n4311: EFaultId_ OpticalCableInterFsmTooLongForCranAl\n\nMEANING\nThe fault
may be reported in FSMx only due to two root causes:\n- The optical cable used to connect BTSs working in the same Centralized\nRadio
Access Network (CRAN) cluster exceeds the maximum supported length for CRAN.\n- The optical cable used to connect the BTSs working in
the same CRAN cluster is\nnot connected to the third port on the FBBC cards.\n\n\nINSTRUCTIONS\n1. 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.\n2. 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 supported length is
20 m).\n\n\n\n\nFAULT NAME\nOverload collision in transmitter\n\nFAULT ID\n2061: EFaultId_MuksuOverloadCollisionAl\n\nMEANING\nThe
transmitter has detected more data coming from a summing than the current link rate can support.\n\nINSTRUCTIONS\n1. Block and unblock
the BTS. \n\n2. Check the baseband bus configuration related to the RP3 link speeds.\n\n\n\n\nFAULT NAME\nOverload detected: max
number of neighbor relation objects reached\n\nFAULT ID\n6285: EFaultId_MaxNumberAnrMoiReachedAl\n\nMEANING\nThis 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 objects) in its database are equal to or above the configured value of the parameter "maxNumAnrMoiAllowed" in
LNBTS.\n\nINSTRUCTIONS\nRemoving neighbor-related objects below the value of the parameter "maxNumAnrMoiAllowed" brings the BTS
to full operational state.\n\n\n\n\nFAULT NAME\nPOST test failed\n\nFAULT ID\n69: EFaultId_Post_test_failedAl\n\nMEANING\nThe unit or
module has been tested during the BTS power-on self test (POST) and a failure has been detected.\n\nINSTRUCTIONS\n1. Reset the
alarming unit or module.\n2. Remove or reinsert the alarming unit or module.\n3. Replace the alarming unit or module.\n\n\n\n\nFAULT
NAME\nPPS reference missing\n\nFAULT ID\n1898: EFaultId_PpsRefMissAl\n\nMEANING\n1. The reference clock monitoring has detected
a loss of PPS signal in the reference received from the GPS receiver or the SyncHub master.\n2. (TDD only) The PPS signal from the
SyncHub master is unusable because its reported phase error is too large.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale
BTS FDD, AirScale BTS TDD:\n1. Check the GPS receiver installation.\n2. Check the GPS receiver status.\n3. Check the connection
between the GPS receiver and the FSM.\n4. Check the cable or connection towards a SyncHub master when operating as SyncHub
slave.\n5. Check the status of the SyncHub master.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\n1. Check the GPS receiver installation.\n2. Check the GPS receiver status.\n\n\n\n\n\nFAULT NAME\nRadio slave has taken
temporary radio master role\n\nFAULT ID\n4220: EFaultId_TemporaryRadioMasterAl\n\nMEANING\nThe radio master is either missing at
start-up or is lost at run-time.\n\nThe radio slave waits for a user-defined amount of time for the radio master\nto become available again
before taking a temporary radio master role.\n\nAn 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 role.\n\nINSTRUCTIONS\nCheck 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 slave will wait for a user-
defined amount of time for the radio master to stay available before giving up the temporary radio master role.\n\n\n\n\nFAULT
NAME\nReference clock missing in startup\n\nFAULT ID\n4153: EFaultId_PpsRefClcMissInStrtAl\n\nMEANING\nPhase synchronization has
been commissioned at the btsSyncMode, but phase reference\nclock is unavailable during a waiting period within the start-up
procedure.\n\nINSTRUCTIONS\nDepending on the installed and commissioned synchronization sources, see the\ncommissioned
synchronization options below and perform the steps in the listed\norder until the BTS fault indication disappears:\n\nGPS receiver (PPS
source):\n1. Check the GPS receiver installation.\n2. Check the GPS receiver status.\n3. Check the connection between the GPS receiver
and FSM.\n\neNB is Sync hub slave and RF sharing is enabled:\n1. Check if sync master provides sync signal.\n2. Check the connection
between sync master and sync slave.\n3. Check sync settings at sync slave.\n\neNB is a part of CRAN cluster:\nPerform all the steps from
above.\n\nTRS reference (ToP as source):\n1. Check that the signal is being received from the ToP Master.\n2. Check the TRS status.\n3.
Check the synchronization settings of the TRS unit.\n\nBTS is Sync hub slave and RF sharing is enabled:\n1. Remove the root cause that
leads to the sync hub slave being not synchronized .\n2) 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 Element Manager.\n\n\n\n\nFAULT NAME\nResource
pool configuration failed\n\nFAULT ID\n6292: EFaultId_ResourcePoolConfigurationFailedAl\n\nMEANING\nThe pool configuration of the
resource DSPs has failed between C-Plane and U-plane.\n\nINSTRUCTIONS\nBlock and unblock the BTS.\n\n\n\n\n\n\nFAULT NAME\nRF
Unit temperature too high\n\nFAULT ID\n4185: EFaultId_RfTempTooHighAl\n\nMEANING\nThe validated sensor temperature on the PA is
higher than the predefined HW temperature.\n\nINSTRUCTIONS\n1. Validate if the ambient temperature is within the specifications and if no
foreign debris has accumulated on the unit. \n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. If
those do not help, replace the BTS.\n\n\n\n\nFAULT NAME\nRIBS Synchronization Not Available\n\nFAULT ID\n4319:
EFaultId_RibsSourceEnodebNotAvailable\n\nMEANING\nThis fault indicates that the Radio Interface Based Synchronization (RIBS) is not
available, and is operating in synchronization holdover mode.\n\nINSTRUCTIONS\nVerify that a Stratum-0 TD-LTE BTS is within the
reception range of the affected target BTS.\n\n\n\n\nFAULT NAME\nSRIO domain ID collision\n\nFAULT ID\n4263:
EFaultId_SrioDomainIdCollisionAl\n\nMEANING\nThe inter-eNB SRIO link cannot be established because the domain ID is not
unique.\n\nINSTRUCTIONS\nFor 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 to the same cluster (LNBTS.caClusterId). Otherwise, change this parameter value
so that it is unique with the particular cluster.\n\n\n\n\nFAULT NAME\nSRIO link outage\n\nFAULT ID\n4262:
EFaultId_SrioLinkOutageAl\n\nMEANING\nSRIO link failure has been detected by the NE.\n\nINSTRUCTIONS\nCheck the cable between
the SRIO ports in the eNBs.\nAutomatic recovery process starts as soon as the fault has been detected.\n\n\n\n\nFAULT NAME\nSRIO
topology failure\n\nFAULT ID\n6290: EFaultId_SrioTopologyFailureAl\n\nMEANING\nInter eNB SRIO link couldn't be established due to
DomainIds not being unique or other errors in cluster topology.\n\nINSTRUCTIONS\nIf collission is detected:\nFor 'Inter eNB Carrier
Aggregation'-related features, the LNBTS.caClusterMemberId parameter value must be unique for each eNB that belongs to the same cluster
29/05/2020 Alarms

major
release
(LNBTS.caClusterId). If not, change this parameter value so that it is unique for that particular cluster.\n\nIn other cases:\nFor 'Inter eNB
Carrier Aggregation'-related features, the LNBTS.caClusterId and LNBTS.clusterNumEnb values must be identical for each eNB that belong
to the same cluster. If not, change the parameter values so that they are identical.\n\n\n\n\n\n\nFAULT NAME\nSumming not enabled for
message type\n\nFAULT ID\n2059: EFaultId_MuksuSummingNotEnabledAl\n\nMEANING\nSumming 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.\n\nINSTRUCTIONS\n1.
Block and unblock the BTS.\n\n2. Check the logs for line code violation (LCV) errors related to optical links. \n\n3. Verify Small Form-factor
Pluggable (SFP) transceiver and fiber conditions. \n\n\n\n\nFAULT NAME\nSumming service default initialization failed\n\nFAULT ID\n4092:
module.\n\n\n\n\nFAULT NAME\nSW fallback\n\nFAULT ID\n4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl\n4083:
EFaultId_FallbackDueToConfigurationDataMigrationFailureAl\n4085:
previously-active SW version - BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW units in
the BTS and\n2. the BTS is up and running.\nOtherwise:\n1. the previously-active SW version is not running in all HW units in the BTS
and\n2. the BTS is not up and running (recovery SW update is still supported).\n\nFault 4082 for FSP fallback can be canceled due to SW
upgrade on FSP only.\nIn this case, an FSP reset to activate the new version of SW may cancel the fault.\nThe state of the fault is
failure and the BTS cannot operate with that SCF.\n\nIf BTS O&M has detected that the BTS can start with the previously-active SW version -
BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW units in the BTS and\n2. the BTS is up
and running. \nOtherwise:\n1. the previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not up and
running (recovery SW update is still supported).\n\n\n4085:\n\nTransport SW on the source unit has indicated the need for a software
fallback.\nIf BTS O&M has detected that the BTS can start with the previously-active SW version - BTS O&M processed consistent fallback
and\n1. the previously-active SW version is running in all HW units in the BTS and\n2. the BTS is up and running. \nOtherwise:\n1. the
previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not up and running (recovery SW update is still
Zone:\nNone\n\n\n\n\nFAULT NAME\nSystem Module failure\n\nFAULT ID\n3000: EFaultId_SystemModuleFailure\n\nMEANING\nThe BTS
has detected an abnormal operation or a failure in the internal functionality of the System Module.\n\n\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\n1. Reset the System Module.\n2. Replace the System Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone
Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTD-SCDMA major alarm\n\nFAULT ID\n4178:
EFaultId_TdscdmaMajorAl\n\nMEANING\nThe Ir router has reported a major problem with TD-SCDMA. The TD-LTE performance is affected,
and cells are disabled.\n\nINSTRUCTIONS\nCheck the TD-SCDMA for active alarms.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT
ID\n3040: EFaultId_TemperatureAlarm\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the
listed order until the BTS fault disappears.\n\n1. Check the other BTS faults and act accordingly.\n\n2. 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, that is, the BTS
module.\n\n\n\n\nFAULT NAME\nToggling: <Fault name>\n\nFAULT ID\n4026: EFaultId_TogglingAl\n\nMEANING\nThis alarm is used to
inform the operator that another BTS fault (the original fault) is toggling.\nThe alarm that is related to the original fault is suppressed and the
new alarm, which is related to fault 4026: EFaultId_TogglingAlFault, is raised.\n\nToggling alarms that are related to the original faults are
suppressed until the toggling condition is cleared.\n\nThe severity of this BTS fault is the same as the severity of the original\ntoggling BTS
fault.\n\nINSTRUCTIONS\n1. Check the fault name of the toggling BTS fault. \n2. Follow the instructions of the toggling BTS fault to clear the
problem.\n \nNote: 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 available with Snapshot.\n\n\n\n\nFAULT NAME\ntoor4nsn Password Update failure\n\nFAULT ID\n4312:
EFaultId_PasswordUpdateFailureAl\n\nMEANING\nThe affected FZAP(s) failed to accept the latest service (toor4nsn) account password
update.\n\nINSTRUCTIONS\nCheck 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 FZAPs clearing the alarm.\n\n\n\n\nFAULT NAME\nToP clock tuning
failure\n\nFAULT ID\n4186: EFaultId_TopClkTuningFailureAl\n\nMEANING\nThe 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.\n\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the fault disappears.\n\n1. Check the other alarms of the BTS and IEEE1588-2008 Master Clock, and
act accordingly.\n\n2. 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 SFN Antenna reference oscillator has demonstrated excessive drift forcing the replacement or repair
of the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna unit. If there are no other synchronization-related alarms
active, start the fast tuning with BTS Site Manager.\n\n3. Reset the site and run fast tuning again.\n\n4. If the condition persists, replace the
Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTransmission clock missing\n\nFAULT
ID\n1816: EFaultId_Trans_Clk_MsgAl\n\nMEANING\nThe reference clock monitoring has detected a loss of signal in the reference received
from the FT.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check that the signal is being
received from the reference clock source.\n2. Check the TRS status.\n3. Check the synchronization settings of the TRS unit.\n\nFlexi Zone
Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nCheck the backhaul connection.\n\n\n\n\nFAULT
NAME\nTransmission parameters missing\n\nFAULT ID\n1825: EFaultId_PublicIPmissingAl\n\nMEANING\nA request to retrieve the public IP
address information of the FCT (HW rel.3) from the FTM has failed, FCT (HW rel.4).\n\nINSTRUCTIONS\nCommission the BTS site with the
correct IP addresses.\n\n\n\n\nFAULT NAME\nTransmission rule collision in Muksu\n\nFAULT ID\n2060:
EFaultId_MuksuTransmissionRuleCollisionAI\n\nMEANING\nThe transmitter has detected an RP3 message from a summing coincident with
a transmission rule.\n\nINSTRUCTIONS\n1. Block and unblock the BTS. \n\n2. Check the configuration.\n\n\n\n\nFAULT NAME\nUnit
initialization failure\n\nFAULT ID\n4208: EFaultId_RromIpConfigAl \n\nMEANING\nThe RROM TRS IP configuring or reconfiguring has
failed.\n\nINSTRUCTIONS\nCheck the transport-related configuration (C-Plane address, U-Plane address, and Transport network ID). If the
fault was raised at startup, correct the configuration and reset the BTS. If the fault was raised during eNB runtime, correct the configuration
and apply the changes at the BTS.\n\n\n\n\nFAULT NAME\nUnit initialization failure\n\nFAULT ID\n4040:
EFaultId_InitFaultManAl\n\nMEANING\nA module initialization has failed.\n\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale
BTS FDD, AirScale BTS TDD:\n\n1. Block/unblock the alarming module.\n\n2. If FSP or FBB or ABIx is the fault source, perform FSP or FBB
29/05/2020 Alarms

major
release
or ABIx reset recovery. If FCM/FCT is the fault source, perform system module reset recovery. If that does not help, perform a power-off
reset. \n\n3. If steps 1 and 2 do not help, replace the alarming module.\n\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Zone SFN Antenna:\n\n1. Reset the BTS.\n\n2. Perform a power-off reset.\n\n3. If steps 1 and 2 do not help, replace the alarming
module.\n\n\n\n\nFAULT NAME\nUnit not supported by current BTS SW version\n\nFAULT ID\n95:
Block or unblock the module that is causing the alarm.\n2. Replace the module that is causing the alarm.\n\n\n\n\nFAULT NAME\nUnknown
HW resource\n\nFAULT ID\n94: EFaultId_UnknownUnitType\n\nMEANING\nA unit cannot be identified by its product code or by its physical
device address (object ID).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nReplace the
alarming unit or module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nReplace the BTS or Flexi Zone SFN
Antenna.
Table 38-12: BASE_STATION_TRANSMISSION_ALARM

major
release
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\n\nA 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.\n\nThe 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.\n\nDo not cancel the alarm. The system automatically cancels the alarm when the fault has
been corrected.
Remedial action: FAULT NAME\n$Protocol Timing source lost [on unit $U] [, interface $IF]\n\nFAULT ID\n61059:
FTM_TIMING_SOURCE_LOS\n\nMEANING\nOne of the synchronization sources in the configured priority list is unavailable.\nThis can be
the primary or the secondary clock source.\n\nIn the alarm: Protocol can be PDH, Timing over Packet (ToP), and Synchronuous
ethernet.\n\nUnit Number is optional:\n- For PDH and Synchronous Ethernet, Unit number is 0 or 1.\n- It is not present for Timing Over
Packet(TOP).\n\nThe interface value is optional:\n- For PDH, the value range depends on the hardware unit type: 1-16.\n- For Synchonuous
Ethernet, the value range is 1-3.\n- It is not present for Timing over Packet.\n\nINSTRUCTIONS\nUse BTS Site Manager to check which
interfaces have been configured as\nsynchronization sources. For all interfaces, do as follows:\n\n1. Check that the cables are connected to
the correct connectors.\n2. Check whether the interface at the far end is switched on.\n3. Check whether there are active alarms at the far
end. If there are,\nfollow the instructions on handling those alarms.\n4. Connect a loop cable and check whether the alarm disappears to
verify that the hardware of the interface unit works correctly.\n\nMonitor the quality of the received clock.\n\n\n\n\nFAULT NAME\nAIS on unit
$U, interface $IF\n\nFAULT ID\n61151: FTM_AIS\n\nMEANING\nAlarm 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.\n\nAll other transmission alarms related
to this signal are suppressed.\n\nProbable cause: There is a transmission problem somewhere in the intermediate network, and AIS is sent
instead of user traffic.\n\nINSTRUCTIONS\nCheck the intermediate transmission network for alarms indicating the root cause and follow the
instructions for handling these alarms.\n\n\n\n\nFAULT NAME\nAutomatic BTS Operator Certificate retrieval unsuccessful\n\nFAULT
ID\n61510: NO_CERTIFICATE\n\nMEANING\nA requested certificate could not be retrieved from the certificate authority (CA).\nA requested
certificate could not be renewed from the certificate authority (CA).\n\nA requested certificate could not be retrieved as the number of
certificates received from repository server (RA) or certificate authority (CA) are more than expected.\n\nA 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.\n\nINSTRUCTIONS\nProvide the certificate.\n\n\n\n\nFAULT NAME\nAuto-negotiation mismatch, on unit $U, Ethernet interface
$IF\n\nFAULT ID\n61607: AUTO NEGO MIS MATCH\n\nMEANING\nThis alarm indicates that there is a mismatch between the BTS
configuration and the auto-negotiation result.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nTry with local management or site support equipment.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:\nConfirm that the
Ethernet Synchronization master/slave settings are correct on the Flexi Zone Micro BTS or Flexi Zone Access Point and backhaul equipment.
\nNote: The Flexi Zone Micro BTS and Flexi Zone Access Point only support slave mode.\n\n\n\n\nFAULT NAME\nBFD $session down,
egress, $sourceIP to $destinationIP\n\nFAULT ID\n61606: BFD DOWN Egress\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nCheck the BFD configuration at the local end.\n\n\n\n\n\nFAULT NAME\nBFD
$session down, ingress, $sourceIP to $destinationIP\n\nFAULT ID\n61605: BFD DOWN Ingress\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Check the network between both BFD peers for physical link failures or misconfigurations.\n\n2.
Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.\n\n\n\n\nFAULT NAME\nBFD
group $bfdGrpId down\n\nFAULT ID\n61022: BFD DOWN\n\nMEANING\nThe alarm is raised if the BFD service is not available on the BTS
for all BFD sessions belonging to that BFD group.\n\nINSTRUCTIONS\n1. Check if the far end has BFD switched on.\n2. Check the cabling
and network connections of the far end.\n\n\n\n\nFAULT NAME\nBluetooth enabled\n\nFAULT ID\n61520:
BLUETOOTH_ENABLED\n\nMEANING\nIf the actBluetoothTransAlarm parameter allows, this fault is raised to indicate that the bluetooth
has been enabled because of any of the following:\n- The bluetooth config mode set to explicitly enabled\n- The bluetooth config mode
AutoFallback logic, which automatically enables the bluetooth upon loss of connection to the iOMS or NetAct\n\nINSTRUCTIONS\n1.
29/05/2020 Alarms

major
release
Determine if the bluetooth should be enabled.\n2. If this action is unexpected, disable the bluetooth.\n\n\n\n\nFAULT NAME\nBluetooth
network connected\n\nFAULT ID\n61522: BLUETOOTH_CONNECTED\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access Point
has detected a bluetooth network connection.\n\nINSTRUCTIONS\n1. Determine if this event is expected. Investigate audit logs as
necessary.\n2. If this action is unexpected, disable the bluetooth.\n\n\n\n\nFAULT NAME\nBluetooth Paired\n\nFAULT ID\n61521:
BLUETOOTH_PAIRED\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access Point has detected a successful
pairing.\n\nINSTRUCTIONS\n1. Determine if this event is expected. Investigate audit logs as necessary.\n2. If this action is unexpected,
disable the bluetooth.\n\n\n\n\nFAULT NAME\nBluetooth repeated authentication failure\n\nFAULT ID\n61523:
BLUETOOTH_AUTH_FAIL\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Determine if this event is
expected. Investigate audit logs as necessary.\n2. If this action is unexpected, disable the bluetooth.\n\n\n\n\nFAULT NAME\nBTS and/or
peer trust anchor expired or due to expire\n\nFAULT ID\n61618: TRUST_ANCHOR_EXPIRING\n\nMEANING\nThe 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.\n\n\nINSTRUCTIONS\nUpdate the trust anchors.\n\n\n\n\nFAULT NAME\nBTS booted at $date due to $RCause\n\nFAULT ID\n61006:
FTM_RESET\n\nMEANING\nThe transport part of the BTS has been reset at the date and time given in the notification.\n\n1. FSMr2
supports the following cause for the reset:\n\n"trs power-on reset": Cold start \n"trs watchdog reset": System overload\n"trs startup failure":
Failure during startup \n"trs software failure": Software failure\n"trs management reset": Reset triggered by management interface\n"trs
fallback": Fallback executed\n\nFSMr3/AirScale supports the following cause for the reset:\n\n"trs power-on reset": Cold start\n"trs watchdog
reset": System overload\n"trs software failure": Software failure\n"trs management reset": Reset triggered by management interface\n"trs
spurious reset": Reset reason detection failed\n\n2. The "$date" format is the local time stamp (GMT+/-xx:xx). For example: 2014-04-12
00:51:26 GMT+0530\n\nINSTRUCTIONS\nNo actions are required.\n\n\n\n\nFAULT NAME\nBTS Local OAM user account $A has been
locked\n\nFAULT ID\n61642: FTM_SECURITY_USER_ACCOUNT\n\nMEANING\nA specific BTS local operator account has been
locked.\nThe 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.\n\nINSTRUCTIONS\nCheck the validity of the username and
password of the account.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n61010:
FTM_BTS_RESET_REQUIRED\n\nMEANING\nA change to the BTS IP settings has been received from the BTS Site Manager. The BTS
should be restarted to activate the change.\n\nINSTRUCTIONS\nReset the BTS when all the required BTS IP settings have been
set.\n\n\n\n\nFAULT NAME\nCCM fault level $ prio $p cause $c\n\nFAULT ID\n61410: Ethernet OAM CCM fault\n\nMEANING\nThe 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:\n\nThe following alarms are defined:\n\n1. 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.\nExample: CCM fault level - prio 5 cause MDL_MISMATCH\nNote: For MDL_MISMATCH cases, it might not be possible to display the
local MDL where the fault was detected.\n\n2. 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.\nExample: CCM fault level 5 prio 5 cause
MAID_MISMATCH\n\n3. 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.\nExample: CCM fault level 5 prio 5 cause
MAID_MISMATCH\n\n4. 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.\nExample: CCM fault level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED\n\n5. 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.\nEx: CCM fault level 5 prio 4 cause WRONG_CCM_INTERVAL \n\n6. REMOTE_CCM, priority 3: A CCM was not
received for 3.5 intervals from at least one remote MEP in the MA.\nEx: CCM fault level 5 prio 3 cause REMOTE_CCM_DEFECT \n\n7.
RDI_CCM, priority 1 (lowest priority): An RDI flag is detected in the CCM frames from one remote peer.\nExample: CCM fault level 5 prio 1
cause REMOTE_DEFECT_INDICATION\n\nThe alarm displays the following information:\n- Alarm Name\n- Alarm Priority\n- Alarm cause: if
different sources produce the same alarm\n- MD level at which the alarm was detected\n\nINSTRUCTIONS\n1. Check the cabling.\n2. Check
the CCM configuration at the remote peer.\n\n\n\n\nFAULT NAME\nConfiguration change rejected by BTS\n\nFAULT ID\n61638:
NEW_CONFIG_REJECTED\n\nMEANING\nThis alarm is triggered once the new configuration file is rejected and the\nM-Plane connection
is established with fallback configuration as a result\nof M-plane recovery action. It will be visible until next site
reset.\n\n\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT NAME\nCRL Update Failure\n\nFAULT ID\n61074: CRL Update
failure\n\nMEANING\nThis alarm is raised if the BTS cannot update the Certificate Revocation List (CRL). Please refer to PDDB parameter
"CERTH::CRLInfo: CRLUpdateFailureReason" for failure reasons.\n\n\nINSTRUCTIONS\nExecute general configuration checks:\n-
Configuration of CMP server IP address and port, and DNS server IP address.\n- Configuration of routing entries towards remote peers.\n-
Configuration of IPSec policies towards remote peers.\nCheck remote peers and intermediate network elements interconnections.\nCheck
the LDAP connection towards the Certificate Revocation List server.\nCheck DNS names.\nCheck the size of the file at the Certificate
Revocation List server.\n\n\n\n\nFAULT NAME\nDead Peer Detected\n\nFAULT ID\n61030: FTM_DPD\n\nMEANING\nA dead peer has been
detected in one of the IPsec associations of the FTM.\nThere is no response to the requests sent to the peer during the IKE SA setup, the
IPsec SA setup, or during DPD.\n\nNote: 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.\n\nPossible reasons:\n- a cable is cut or
there is no cable connected to the interface\n- the signal is excessively attenuated\n- the port at the connected far end node is switched
off\n\nINSTRUCTIONS\n1. Check that the cables are connected to the correct connectors.\n2. Check that the interface at the far-end
interface is switched on.\n3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those
alarms.\n\n\n\n\nFAULT NAME\nDup Addr on {duplicateIpv6Address} {VID: id}\n\nFAULT ID\n61632:
IPV6_DUPLICATE_ADDRESS_DETECTED\n\nMEANING\nDuring 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.\n\n\nINSTRUCTIONS\n1.Check for duplicate IPv6
addresses configured in the BTS.\n2.Change or delete the identified duplicate IPv6 addresses.\n\n\n\n\nFAULT NAME\nEBER on unit $U,
interface $IF\n\nFAULT ID\n61104: FTM_EBER\n\nMEANING\nExcessive bit error rate: The measured bit error rate exceeds the threshold
value of BER-3 (10E-3).\n\nProbable causes:\n- the signal level is too low (optical connectors or cables are dirty, electrical connectors or
cables are corroded)\n- the specified maximum length of the cable is exceeded\n- the connector is not properly connected to the unit\n- the
receiver or the far-end transmitter has failed\n\nINSTRUCTIONS\n1. Clean the cables and connectors.\n\n2. Check that the connectors are
properly connected to the unit.\n\n3. Check that the cable connected to the interface in question is not damaged and is within the
specifications.\n\n4. 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.\n\n\n\n\nFAULT NAME\nETH AIS fault interface $IF level $l mac
$x\n\nFAULT ID\n61411: Ethernet OAM ETH_AIS_fault\n\nMEANING\nWhen an MEP receives a valid ETH-AIS frame and AIS is enabled, it
shall trigger an AIS alarm containing the following information:\n- receiving interface\n- MD level\n- Source MAC address\n\nNote:For
FSMr3/AirScale unit types, interface is provided as: "module type name" EIF "interface number". \nFor Flexi Zone Micro BTS, interface is
provided as: EIF "interface number".\n\nINSTRUCTIONS\n1. Check cabling.\n2. Check the configuration at the remote peer.\n\n\n\n\nFAULT
NAME\nFTM Toggling <Fault name>\n\nFAULT ID\n61619: FTM_FAULT_TOGGLING\n\nMEANING\nAn 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.\n\n\nINSTRUCTIONS\n1. Check the fault name of the toggling FTM fault from the Fault name of\nthis fault.\n2. Follow the instructions
of the toggling FTM fault to clear the problem.\n \nNote: Detailed information about the toggling frequency can be found in\nalarm history file,
which can be downloaded using the BTS Site Manager. The log file is available with Snapshot.\n\n\n\n\nFAULT NAME\nIPsec emergency
29/05/2020 Alarms

major
release
bypass active\n\nFAULT ID\n61639: IPSEC_EMERGENCY_BYPASS_ACTIVE\n\nMEANING\nThe BTS has entered the IPsec emergency
bypass active state, where configured IPsec policies are ignored and the entire traffic is sent unprotected.\n\nINSTRUCTIONS\nStart IPsec
emergency bypass by making the security gateway not reachable either\nby plugging out the cable or configuring wrong security gateway
address.\n\n\n\n\nFAULT NAME\nIPSec expert mode activated\n\nFAULT ID\n61647: IPSEC_EXPERT_MODE\n\nMEANING\nBTS 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.\n\nINSTRUCTIONS\nNone.\n\n\n\n\nFAULT NAME\nIPSec tunnel switchover\n\nFAULT ID\n61643:
IPsec_tunnel_switchover\n\nMEANING\nThis alarm will be triggered when at least one primary IPSec tunnel fails, and BTS has switched
over to a secondary IPSec tunnel.\nAs 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.\n\nINSTRUCTIONS\nThe 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.\n\n\n\n\nFAULT NAME\nIP Traffic Capturing Ongoing [port
$port,] [mac $m]\n\nFAULT ID\n61641: IP_TRAFFIC_CAPTURE_ONGOING\n\nMEANING\nThe base station is currently capturing an IP
traffic towards a local port or into a file on the base station.\nIf the traffic capturing is happening towards a local port, a port and destination
MAC address must be provided.\nPort values can be LMP or < HW MODULE NAME >-<PORT ID>.\n(For E.g: LMP or FSM-EIF1, FSM-EIF2
or FTIF-EIF1)\n\nINSTRUCTIONS\nAn 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.\n\n\n\n\n\nFAULT NAME\nLink OAM critical link event $E on unit $U, interface $F\n\nFAULT
ID\n61077: Link OAM critical link event alarm\n\nMEANING\nA 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.\n\nThe following critical link events are possible:\n- 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.\n- Dying Gasp: either the local or the remote peer has a fatal error and is about to restart.\n- Link Fault: the local peer
has detected a physical link fault in receiving direction, for example, a LOS.\n\nNote:\nIn case a received OAMPDU has more than one
critical event flag set, the following shall be reported in the alarm:\nLink Fault bit set |Dying Gasp bit set|Critical Event bit set| Reported\n x x x
Link Fault\n x x Link Fault\n x x Link Fault\n x x Dying Gasp\n\nAlways the latest received critical link event shall be
reported.\n\nINSTRUCTIONS\n1. Inspect details of the type of the critical event through online configuration management.\n2. Check the
Link OAM state information of the interface.\n3. Check the cabling and network connections to the far end.\n4. Check the Ethernet interface
configuration at the local and remote sides.\n5. Insert a Link OAM loopback.\n\n\n\n\nFAULT NAME\nLink OAM link lost on unit $U, interface
$F\n\nFAULT ID\n61076: Link OAM link lost alarm\n\nMEANING\nOn 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).\n\nINSTRUCTIONS\n1. Check the cabling and network connections to the far end.\n2. Check the Link OAM event information and
the Link OAM state information.\n3. Check the Ethernet interface configuration at the local and remote sides.\n4. Insert a Link OAM
loopback.\n\n\n\n\nFAULT NAME\nLink OAM loopback inserted on unit $U, interface $F by $P peer\n\nFAULT ID\n61075: Link OAM
loopback alarm\n\nMEANING\nA 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.\n\nINSTRUCTIONS\nNone\n\n\n\n\nFAULT NAME\nLMP Carrier State
Detected\n\nFAULT ID\n61648: LMP_CARRIER_DETECTED\n\nMEANING\nThe 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. \n\nINSTRUCTIONS\n1. Determine if this event is
expected: whether a qualified personnel is utilizing LMP ethernet port cable connection for diagnostic purposes. \n2. Otherwise, it shall be
treated as a security warning.\n\n\n\n\nFAULT NAME\nLOF on unit $U, interface $IF\n\nFAULT ID\n61028: FTM_LOF\n\nMEANING\nLoss 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.\n\nProbable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface.\n\nProbable
cause for T1 interfaces: The interface at the far end is not configured to be a T1 interface.\n\nINSTRUCTIONS\nE1 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.\n\nJT1 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.\n\n\n\n\nFAULT NAME\nLOMF on slot $U, interface $IF\n\nFAULT
ID\n61150: FTM_LOMF\n\nMEANING\nLoss of multi-frame: The interface referenced in the alarm text has lost the multi-frame
alignment.\n\nProbable 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.\n\nINSTRUCTIONS\nCheck 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.\n\n\n\n\nFAULT NAME\nLOS on unit $U, [Ethernet] interface $IF\n\nFAULT ID\n61029: FTM_LOS\n\nMEANING\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD/TDD:\nNo signal is received on the interface referenced in the alarm text. All other transmission alarms
related to this signal are suppressed.\n\nProbable causes for Ethernet interfaces:\n- a cable is cut, or there is no cable connected to the
interface\n- the electrical signal is excessively reduced\n- the port at the connected far-end node is switched off\n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD:\nNo signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal
are suppressed.\n\nProbable causes for Ethernet interfaces:\n- a cable is cut, or there is no cable connected to the interface\n- the electrical
signal is excessively reduced\n- the port at the connected far-end node is switched off\n\nThe 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).\n\nINSTRUCTIONS\n1. Check that the cables are connected to the correct connectors.\n\n2. Check
that the interface at the far-end interface is switched on.\n\n3. Check whether there are active alarms at the far end. If there are, follow the
instructions for handling those alarms.\n\n4. Connect a loop cable and check whether the alarm disappears to verify that the hardware of the
interface unit works correctly.\n\n\n\n\nFAULT NAME\nMissing or non-compliant SFP module on unit $U, interface $I\n\nFAULT ID\n61050:
FTM_SFP\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:\nThe 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.\n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD:\nThe Small Form-Factor Pluggable (SFP) module is not supported, not present, or could not be recognized.\nThe
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.\nThe SFP module was
expected by the SW, but found missing.\nProbable causes:\n- No SFP module is inserted at the SFP-based Ethernet interface.\n- 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.\n- The SFP module type is not supported.\n\nThe 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).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nInsert a Small Form-Factor Pluggable (SFP) module with the correct laser type (class 1) to the Gigabit Ethernet interface of the
unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Plug-out and plug-in the SFP module.\n2. Check for SFP validity (could be wrong
type).\n3. Insert a compliant SFP module.\n\n\n\n\nFAULT NAME\nNTP Server $IP unavailable\n\nFAULT ID\n61613:
NTP_SERVER_UNREACHABLE\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone
Micro TDD:\nA BTS reports this alarm for each instance of the configured NTP server if that\nparticular NTP server is not accessible or
cannot be used after waiting for\na threshold timeout defined by the INTP::ntpAlarmThreshold configuration parameter in PDDB.\n\nThe
raised alarm displays the IP address of the NTP server that is not reachable\nin the additional information field
"alarmNotif::argumentInfo".\n\nNote : For each NTP server instance, timers are started separately and a separate\nalarm is raised. This
threshold time is not used to clear the alarm.\n\nFlexi Zone:\nFlexi Zone Access Point reports this alarm for each instance of the
configured\nNTP server if that particular NTP server is not accessible or cannot be used\nafter waiting for a threshold time-out defined by the
configuration parameter\nINTP::ntpAlarmThreshold in PDDB.\n\nThe raised alarm displays the IP address of the NTP server that is not
reachable\nin the additional information field "alarmNotif::argumentInfo".\n\nNote : For each NTS server instance, timers are started
29/05/2020 Alarms

major
release
separately and a separate\nalarm is raised. This threshold time is not used to clear the alarm.\n\n\nINSTRUCTIONS\n1. Check the
connectivity to the NTP server.\n2. Check the NTP server configuration at the BTS.\n3. Check the configured threshold value for the NTP
server.\n\n\n\n\nFAULT NAME\nRDI on unit $U, interface $IF\n\nFAULT ID\n61152: FTM_RDI\n\nMEANING\nRemote defect indication: It is
sent by the intermediate or the far-end equipment because it detects a serious fault in the received signal.\n\nProbable cause: The far end
has a LOS, LOF, or AIS alarm on its receiving interface.\n\nINSTRUCTIONS\n1. Check the intermediate transmission network for alarms
indicating the root cause and follow the instructions for handling these alarms.\n\n2. Connect a loop cable and check that no alarms appear
for this interface to check the transmit hardware.\n\n\n\n\nFAULT NAME\nSFP HW Failure\n\nFAULT ID\n61079: SFP HW
Failure\n\nMEANING\nA malfunctioning of the SFP transceiver was detected. \nThe SFP has reported a transmission fault condition and has
disabled the laser transmitter.\n\nINSTRUCTIONS\nReplace the faulty SFP. Note that only the SFP might be faulty, not necessarily the entire
hardware unit.\n\n\n\n\nFAULT NAME\nSFP HW Warning/Alarm on unit $U, interface $IF, cause $FC\n\nFAULT ID\n61525:
FTM_SFP_WARNING\n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nCheck 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.\n1. Check whether the alarm is caused by exceeded temperature, internal
supply voltage, or TX BIAS/TX output power.\n2. 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.\n3. 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.\n4. If the TX BIAS/TX output power causes the alarm, replace the SFP module.\n\n\n\n\nFAULT NAME\nSSH enabled\n\nFAULT
ID\n61524: SSH_ENABLED\n\nMEANING\nThe Flexi Zone Micro BTS or Flexi Zone Access Point detects that the SSH access to the site is
enabled.\n\nNote: 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.\n\nINSTRUCTIONS\n1. Determine if this event is expected.\nNote: 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.\n\n\n\n\nFAULT NAME\nSyncE Quality
Level Degraded on unit $UID, interface $IF\n\nFAULT ID\n61624: SSM_POORQUALITY\n\nMEANING\nThis alarm is raised when the
received SSM indicates lower clock quality (for example, "do not use" or "EEC") than required.\n\nNote: The interface numbering shall be
similar to ETHLK.\nE.g: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1,interface 4.\n\nINSTRUCTIONS\nFlexi Zone Micro FDD, AirScale BTS
FDD/TDD, Flexi Zone Micro TDD, Flexi Zone:\n1. Confirm that SyncE is desired as a synchronization source.\n2. Confirm that eNB
configuration settings for ssmEnabled are correct.\n3. Troubleshoot with Backhaul provider on the reason SSM errors.\n\n\n\n\nFAULT
NAME\nSyncE SSM Timed Out on unit $UID, interface $IF\n\nFAULT ID\n61623: SSM_TIMEOUT\n\nMEANING\nThis alarm is raised if the
incoming SSM is not received for a certain time period (configured through the parameter "ssmTimeout").\n\nNote: The interface numbering
is similar to ETHLK.\nExample: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1, interface 4\n\nINSTRUCTIONS\n1. Confirm that SyncE is desired
as a synchronization source.\n2. Confirm that configuration settings for ssmEnabled are correct.\n3. Troubleshoot with backhaul provider
about the reason for SSM errors.\n\n\n\n\nFAULT NAME\nSynchronization lost\n\nFAULT ID\n61058:
FTM_SYNC_LOSS\n\nMEANING\nPrimary 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.\n\nThe 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.\n\nProbable cause: The
transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example,
LOS).\n\nINSTRUCTIONS\nUse the BTS Site Manager to check which interfaces have been configured as synchronization sources.\n\n1.
Check that the cables are connected to the correct connectors.\n2. Check whether the interface at the far end is switched on.\n3. Check
whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms.\n4. Connect a loop cable and
check whether the alarm disappears to verify that the hardware of the interface unit works correctly.\n\n\n\n\nFAULT NAME\nToP master
service $IP unusable\n\nFAULT ID\n61631: TOP_MASTER_UNUSABLE\n\nMEANING\nThe reference clock monitoring has detected a loss
of ToP reference clock signal received from the master clock behind $IP:\n- The eNB does not receive a reply from ToP Master within a
certain time (5 sec) upon sending a sync request message.\n- 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.\n\nINSTRUCTIONS\n1. Check the cable connectivity.\n2. Check
the TOP configuration.\n\n\n\n\n\nFAULT NAME\nTransport module missing: $unit\n\nFAULT ID\n61201:
TRANSPORT_MODULE_MISSING\n\nMEANING\nA unit is missing. The slot has been configured to hold a unit, but the plug-in\nunit is not
physically present in the slot.\n\nProbable causes:\n\n- The unit has been configured but not detected.\n- The unit is broken and therefore not
detected.\n- The unit has been configured but some other unit is detected.\n\nNOTE: The unit variable should be replaced by appropriate HW
names configured (unitTypeConfigured) during runtime reporting.\n\nINSTRUCTIONS\nReplacing a faulty hardware:\n1. Plug in again the
expected transport unit that is referenced in the alarm text.\n2. In case there is a unit present in the slot, remove it from the slot\nand plug it
back in. If the unit is still not recognized and the alarm\nremains, replace the faulty unit with a new one. \n\nDecommissioning a previously
commissioned hardware:\n1. Recommission to remove the hardware unit referenced in the alarm text.\n\nNOTE: Before recommissioning,
the hardware unit must not be present in the slot.\n\n\n\n\nFAULT NAME\nTWAMP PLR Threshold Crossed\n\nFAULT ID\n61611:
PLR_THRESHOLD_CROSSED\n\nMEANING\nThe PLR threshold alarm shall be sent in case the configured value of PLR is
exceeded.\n\nINSTRUCTIONS\n1. Check the backhaul usage and if other applications with the same or higher\nPHB may compete against
this TWAMP session about the capacity. An increase in\nthe priority of TWAMP session or of the backhaul capacity may clear the
alarm.\n\n2. Check if destination is unreachable by IP connectivity test. Send an ICMP\necho request (ping) to the UDP port of the TWAMP
reflector at the destination\nIP.If ICMP echo reply indicates that the destination is unreachable but you\nhave access to TWAMP reflector, you
can check its status. If the status is disabled\nor down try to activate it again and check if alarm disappears.\n\n3. Check configured PLR
threshold. Setting PLR to 0% should be avoided, because\nevery lost measurement packet will trigger the alarm and it cannot be
cleared\nagain (PLR>=0).\n\n\n\n\nFAULT NAME\nTWAMP RTT Threshold Crossed\n\nFAULT ID\n61610:
RTT_THRESHOLD_CROSSED\n\nMEANING\nThe RTT threshold alarm is sent in case the average value of the RTT exceeds\nthe
configured threshold.\n\nINSTRUCTIONS\n1. Check the backhaul usage and if other applications with the same or higher\nPHB may
compete against this TWAMP session about the capacity. An increase in\nthe priority of TWAMP session or of the backhaul capacity may
clear the alarm.\n\n2. Check the last measured RTT values of this TWAMP session and verify that\nthe configured RTT threshold value is not
too close to average measured RTT\nvalues, so that this alarm could be result of sporadic mis-measurement.\n\n\n\n\nFAULT
NAME\nUnsupported HW device\n\nFAULT ID\n61634: UNSUPPORTED_HW_DEVICE\n\nMEANING\nThe SW does not support the
detected HW unit type.\n\nProbable causes:\n\n- The SW version of the system module is too old.\n- The supported HW variant is not
present in the system module.\n\nINSTRUCTIONS\nSW upgrading: Upgrade the FSM SW release to the latest version that includes the
support for the new external transport device variant.\n\nUnit variant replacement: Replace the unsupported device variant to another one
that supports the currently running SW release.\n\n\n\n\nFAULT NAME\nVendor BTS certificate is about to expire\n\nFAULT ID\n61616:
VENDOR_CERTIFICATE_EXPIRING\n\nMEANING\nThe BTS raises this alarm when the vendor BTS certificate is about to expire.\n\nThe
period of advance notification is configurable, as well as the CA certificate expiry.\n\n1 day ... 4999 days with default 90 days\n\nNote: For
Flexi Zone Controller, the period of advance notification is a non-configurable 90 days.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD,
29/05/2020 Alarms

major
release
AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone Access Point, Flexi Zone Controller:\nCheck the vendor
BTS certificate expiry date. \nReplace the expired vendor BTS certificate if possible (for example, an older BTS like FSMr2).\nOtherwise,
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.\n\nFor 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.\n\n\n\n\nFAULT NAME\nWi-Fi card invalid type\n\nFAULT ID\n61527:
WIFI_CARD_INVALID_TYPE\n\nMEANING\nThe internal Wi-Fi module type is invalid.\n\nINSTRUCTIONS\n1. Check the release notes of
the downloaded BTS software if any known Wi-Fi module issues are reported.\n2. Replace the Flexi Zone Micro BTS.\n\n\n\n\nFAULT
NAME\nWi-Fi card not present\n\nFAULT ID\n61526: WIFI_CARD_NOT_PRESENT\n\nMEANING\nThe internal Wi-Fi module is not
present.\n\nINSTRUCTIONS\n1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are
reported.\n2. Replace the Flexi Zone BTS."
Table 38-13: BFD_DOWN

major
release
Name: BFD_DOWN (11521) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BFD DOWN FL16A
Package: racfl.BFD_DOWN Implicitly cleared: true
Description: BFD DOWN\n\nThe alarm is raised if the BFD service is not available on the BTS for all BFD sessions belonging to that BFD
group.\n\nThe communication link between the BTS and the BFD peer is defective. No communication is possible.\n\nThe system cancels
the alarm autonomously once the BFD functionality is available again.
Remedial action: 1. Check if the far end has BFD switched on.\n2. Check the cabling and network connections of the far end.
Table 38-14: BFD_DOWN_Egress

major
release
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\n\nThe 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.\n\nThe
communication link between the BTS and the BFD peer is defective. No communication is possible.\n\nThe 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 38-15: BFD_DOWN_Ingress

major
release
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\n\nThe 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.\n\nThe communication link between the BTS and the BTS
peer is defective, or the peer itself is defective. No communication is possible.\n\nThe 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.\n\n2. Check if the BFD
functionality in the peer is switched on and that the configurations of the BFD peers match.
Table 38-16: BLUETOOTH_AUTH_FAIL
29/05/2020 Alarms

major
release
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\n\nThe 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.\n\nTo 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.\n\n
Remedial action: 1. Determine if this event is expected. Investigate audit logs as necessary.\n2. If this action is unexpected, disable the
bluetooth.
Table 38-17: BLUETOOTH_CONNECTED

major
release
Name: BLUETOOTH_CONNECTED (11525) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_CONNECTED FL16A
Package: racfl.BLUETOOTH_CONNECTED Implicitly cleared: true
Description: BLUETOOTH_CONNECTED\n\nThe Flexi Zone Micro BTS or Flexi Zone Access Point has detected a bluetooth network
connection.\n\nNone\n\n
bluetooth.
Table 38-18: BLUETOOTH_ENABLED

major
release
Name: BLUETOOTH_ENABLED (11526) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_ENABLED FL16A
Package: racfl.BLUETOOTH_ENABLED Implicitly cleared: true
Description: BLUETOOTH_ENABLED\n\nIf the actBluetoothTransAlarm parameter allows, this fault is raised to indicate that the bluetooth
has been enabled because of any of the following:\n- The bluetooth config mode set to explicitly enabled\n- The bluetooth config mode
AutoFallback logic, which automatically enables the bluetooth upon loss of connection to the iOMS or NetAct\n\nAs 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.\n\n
Remedial action: 1. Determine if the bluetooth should be enabled.\n2. If this action is unexpected, disable the bluetooth.
Table 38-19: BLUETOOTH_PAIRED

major
release
Name: BLUETOOTH_PAIRED (11527) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: BLUETOOTH_PAIRED FL16A
Package: racfl.BLUETOOTH_PAIRED Implicitly cleared: true
Description: BLUETOOTH_PAIRED\n\nThe Flexi Zone Micro BTS or Flexi Zone Access Point has detected a successful
pairing.\n\nNone\n\n
29/05/2020 Alarms

major
release
bluetooth.
Table 38-20: BootableConfigBackupFailed

major
release
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
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 38-21: BootableConfigRestoreFailed

major
release
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 38-22: BootParametersMisconfigured

major
release
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'))))
29/05/2020 Alarms

major
release
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 38-23: BTSHardwareResynchronization

major
release
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 38-24: CELL_FAULTY

major
release
Name: CELL_FAULTY (11528) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: CELL FAULTY FL16A
Package: racfl.CELL_FAULTY Implicitly cleared: true
Description: CELL FAULTY\n\nA critical fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the
alarm.\n\nCheck the reason for the fault from the supplementary text field of the alarm.\n\nThe 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.\n\nDo
not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
support. \n------------------------------------------------\n\nFAULT NAME\nAbnormal CPRI interface to next hop <OptIf ID>\n\nFAULT ID\n1974:
module).\n\n\n\n\nFAULT NAME\nAbnormal reception on SFP to next hop <OptIf ID>\n\nFAULT ID\n1973:
EFaultId_AbnormalReceptionOnSfpToNextHopAl\n\nMEANING\nThe optical interface is not working properly.\nThis fault is valid only for
radio modules in a chain configuration.\nNote: The Optif is from the perspective of the previous radio.\n\nINSTRUCTIONS\n1. 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. \n2. Reset
the RF module. \n3. If that does not help, block or unblock the site. \n4. If that does not help, replace the RF module that is generating the
alarm.\n\n\n\n\nFAULT NAME\nAbnormal reception on SFP to upper hop <OptIf ID>\n\nFAULT ID\n1971:
EFaultId_AbnormalReceptionOnSfpToUpperHopAl\n\nMEANING\nThe 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 configuration.\n\nINSTRUCTIONS\n1. Check the cables
between the system module and the RF module. \n2. Reset the RF module. \n3. If those do not help, block and unblock the site. \n4. If those
do not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nAntenna calibration error caused by transmission
path failure \n\nFAULT ID\n1987: EFaultId_CalibrationErrorCausedByTransmissionPathFailureAl\n\nMEANING\nAntenna calibration has
failed on at least 3 antennas because of a transmission path failure.\n\nThe path means all units between the signaling processor (DSP) and
the antenna inside the radio module.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault is resolved:\n1.
Check if other alarms are not reported at the same time. If other alarms are reported, follow the necessary instructions to clear them.\n2.
Reset the radio module, which is the fault source.\n3. Reset the BTS.\n4. Replace the radio module, which is the fault
source.\n\n\n\n\nFAULT NAME\nAntenna Line Device failure\n\nFAULT ID\n3100: EFaultId_AntennaLineFailure\n\nMEANING\nThe System
Module, or the device itself, has detected an abnormal operation or a failure in the antenna line device.\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the BTS fault disappears.\n\n1. Check the antenna line and antenna line devices. Ensure that the
29/05/2020 Alarms

major
release
antenna line connectors are in the right torque.\n\n2. Block and unblock the alarming RF module to reset it.\n\n3. Replace the faulty parts
and/or devices along the antenna line.\n\n4. Replace the RF Module.\n\n\n\n\nFAULT NAME\nAntenna line failure\n\nFAULT ID\n1836:
EFaultId_ALOvercurrentAl\n\nMEANING\nThe 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 causing overload. All antenna line devices powered by the antenna line are out of
order.\n\nINSTRUCTIONS\n1. Check the antenna line and antenna line devices. Fix or replace the faulty parts or devices.\n2. 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 cancel automatically after the fault condition is cleared regardless of when the condition is cleared. If the fault is not canceled
automatically, the fault is canceled when the RF module is blocked or unblocked, or when the RF module or the BTS is reset. \n3. For all
other radios, the fault is canceled only when the RF module or the BTS is reset.\n\n\n\n\nFAULT NAME\nAntenna line faulty \n\nFAULT
ID\n4045: EFaultId_AntennaLineFaultyAl\n\nMEANING\nAn alarm message has been received from the antenna line. The antenna line is
faulty.\n\nINSTRUCTIONS\nThe following instructions should be performed on the master RAT side:\n\n1. Check the antenna line and
antenna line device that causes the alarm.\n2. Fix or replace the faulty parts or devices.\n3. Perform a radio module reset (only the master
RAT in sharing mode can request for such an operation to be performed).\n\n\n\n\nFAULT NAME\nAntenna line switched off due to high
VSWR\n\nFAULT ID\n1957: EFaultId_AntennaLineSwitchedOffAl\n\nMEANING\nTx in the RF module has been switched off to protect the
radio module hardware, which might be damaged because of high-reflection (VSWR) conditions.\n\nINSTRUCTIONS\n1. The VSWR
measured at the RF (transmitter) exceeds values that are acceptable by the RF module.\n2. Check the impedance matching of the Antenna
Line System (replace elements that cause mismatch).\n3. To check if the above-mentioned steps have solved the problem, reset the RF
module.\n\n*Forcing the RF HW to work under such conditions might result in permanent damage to the RF HW.\n\n\n\n\nFAULT
NAME\nAntenna link is down\n\nFAULT ID\n476: EFaultId_Rp3BusError\n\nMEANING\nThe antenna (RP3) link is down. The transmitter or
receiver drops from synchronization.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1.
Restart the BTS.\n2. If that does not help, replace the alarming module. \n\nFlexi 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. \n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD: If FBBx or
ABIx is causing the alarm, replace the FBBx or ABIx.\n\nFlexi 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 Antenna.\n\n\n\n\nFAULT NAME\nBaseband bus
configuration of <x> was rejected\n\nFAULT ID\n1811: EFaultId_BbBus_ConfFailedAl\n\nMEANING\nThe baseband-bus-related
configuration of <x> has been rejected by the HW SW, DSP, or RF SW.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nReplace the alarming module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Download the correct
configuration.\n2. Reset the BTS.\n3. Replace the BTS.\n\nFlexi Zone:\n1. Download the correct configuration.\n2. Reset the Flexi Zone
Access Point from the BTSSM.\n3. Replace the Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1. Download the correct
configuration.\n2. Reset the Flexi Zone SFN Antenna from the BTSSM.\n3. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nBaseband bus failure\n\nFAULT ID\n3020: EFaultId_BaseBandBusFailure\n\nMEANING\nThe Flexi BTS has detected an abnormal
operation or a failure in the BTS\ninternal or external (optical link) baseband bus. The failure cannot be\nattributed to a specific module and
there are several possible fault sources.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears.\n\n1. Check the other active BTS faults and act accordingly.\n\n2. Check the cables between the System Module and RF
Module.\n\n3. Reset the RF Module and/or System Module, depending on the alarm source:\n a. Reset the RF Module by blocking and
unblocking it.\n b. Reset the System Module by blocking and unblocking it.\n\n4. Replace the alarming RF Module.\n\n5. If the System
Module is the source, or replacing the RF Module does not clear the fault situation, replace the alarming System Module.\n\n\n\n\nFAULT
NAME\nBaseband resources mapping to cells failure\n\nFAULT ID\n12: EFaultId_TcomConfigAl\n\nMEANING\nA 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
operation cannot be taken into use. The reason for the failure might be an internal problem in the eNodeB O&M
system.\n\nINSTRUCTIONS\n1. Block and unblock the BTS.\n2. Perform a power-off reset. \n3. If steps 1 and 2 do not help, replace the
module that is causing the\nalarm. \n\n\n\n\nFAULT NAME\nBB bus reception error (summing device)\n\nFAULT ID\n2016:
EFaultId_Muksu_SMTimeOffAl\n\nMEANING\nThe 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 set into the wrong place (PI delay), or the data itself is in the wrong
place.\n\nINSTRUCTIONS\n1. 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 and the FBBx module.\n\n2. Replace the unit that causes the alarm (system
module or FBBx/ABIx).\n\n\n\n\nFAULT NAME\nBB bus transmission error\n\nFAULT ID\n2017:
the system module.\n\n3. Replace the alarming module (system module).\n\n\n\n\nFAULT NAME\nBeamforming cell parameter
mismatch\n\nFAULT ID\n4254: EFaultId_BfCellParaMismatchAl\n\nMEANING\nDuring BTS startup or BTS recomissioning, the BTSOAM has
detected that\nthere are wrong combination of values for the beam-forming cell parameters "tddSpecSubfConf", "rxCalibrationConfiguration",
"actReduceWimaxInterference" for the used beam-forming radio module. \n\nINSTRUCTIONS\n1. Check values of the the parameters
"TddSpecSubfConf", "rxCalibrationConfiguration", and "actReduceWimaxInterference" and the used beam-forming radio module type.\n2.
Commission different combination for the mentioned values, or change to a different beam-forming radio module type for the
configuration.\n\n\n\n\n\nFAULT NAME\nBTS configuration error (not enough HW for LCR)\n\nFAULT ID\n1868:
EFaultId_NotEnoughHwForLcrAl\n\nMEANING\nDuring BTS startup, BTS re-comissioning, or BTS resources re-assignment due to a failure,
the BTSOAM has detected that there are not enough:\na. radio resources\nb. FSP resources\nc. 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 according to the
configuration requested in the site configuration file\n\nThis 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 differs from the hardware of the previous unit (different capacity, type of
ports, and so on), or might not be taken into use without a BTS reset.\n\nThe 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.\n\nINSTRUCTIONS\nIf "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
detected. Check if all cables and SFPs connecting the radio modules to the system module (or to the extension baseband module -
FBBx/ABIx) are working correctly,\nor replace the radio module. Alternatively, re-commission the BTS with fewer cells.\n\nIf "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 enable
the cell setup are detected. Check what radio hardware is necessary\nto set the cell up, for example, the number and type of antenna ports,
and use the radio module with the required hardware. \n\nIf "Not enough DSP resources for cell detected." is displayed in the\nalarm
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 configured in SCF. Try to recommission the BTS with fewer cells or add FBBx/ABIx card.\n\nIf re-commissioning does not
resolve the issue and\na. extension baseband module (FBBx/ABIx) is used:\n1. Ensure that all cables (Power and Baseband bus cables) are
connected\nto the FBBx/ABIx unit.\n2. Block and unblock the system module.\n3. If this does not help, replace the FBBx/ABIx unit.\nIf, at the
same time, an alarm caused by fault 4001 (BTS reset) is reported,\na BTS reset might help.\n\nb) extension baseband module (FBBx/ABIx)
is not used:\n1. Block and unblock the system module.\n2. If that does not help, replace the system module.\n\nIf "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 provide the
required throughput. Add or replace the cables and/or SFP(s).\n\nIf "Detected hardware doesn't allow to setup cell according to
configuration."\nis 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 planned configuration is supported by Nokia, or if the used hardware is capable to support the planned
configuration.\n\n\n\n\nFAULT NAME\nBTS file error\n\nFAULT ID\n1802: EFaultId_FileRequestFlashAl\n\nMEANING\nA software download
to FSP, DSP, ABIx or FR has failed.\n\nINSTRUCTIONS\nNote: Perform the following steps in the listed order until the fault disappears:\n\n1.
29/05/2020 Alarms

major
release
Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template.\n\n2. Download two
different software packages so that the faulty file is removed from the BTS.\n\n3. Download the software again.\n\n4. Replace the System
Module.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n4001: EFaultId_BtsResetNeededAl\n\nMEANING\nThis 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
trigger an autonomous reset on its own.\n\n1. The BTS has detected a commissioned (configured in SCF) extension baseband\nmodule (for
example, FBBC) that was not detected during BTS startup. Thus, the BTS must be reset to take the module into use.\n\n2. 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.\nNote: LCR supported by the FSP is reported as the fault source in this case.\n\n3. 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.\n\n4. An internal problem has been
detected, and the BTS cannot continue start-up\nwithout a BTS reset.\n\n5. 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 to an SFP that does not support
the configured speed), and a BTS reset might be needed to solve the problem.\nNote: The affected LCR is reported as the fault source in this
case.\n\n6. 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 module (configured in SCF) or optical cable. The BTS must be reset to set the cell up with the use of the
detected radio module or cable. LCR is the fault source in this case. \n\n7. 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 example, FBBA. The BTS must
be reset to take the module into use.\n\n8. 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.\n\n9. The BTS has cleared an alarm and triggers an autonomous BTS reset to
enable\nnormal BTS operability, but the BTS reset counter has been exceeded. The operator must perform a BTS reset to enable BTS
operability.\n\n10. 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 the operator might solve this issue.\n\n11. FDD only - Phase synchronization source was not available in
BTS start-up,\nand alarm with fault 4153 was raised. Phase synchronization source is available now. BTS reset is needed to activate features
requiring network-level synchronization (OTDOA, eICIC, MBMS, inter-eNB Carrier Aggregation).\n\n12. BTS cannot execute FSP or BTS
autonomous recovery reset because of either of the following reasons:\n- It will disable any working cell \n- An internal BTS limitation\n\n13.
FSP card is lost or disconnected. A BTS reset is necessary to protect the BTS from a crash after the card hot insert.\n\n14. FSP autonomous
recovery reset has failed. A BTS reset is necessary to try to recover the FSP.\n\n15. FSMr3 only - CRAN configuration for a cell has failed. A
BTS reset is necessary to reconfigure CRAN.\nNote: The affected LCR is reported as the fault source in this case.\n\n16. 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
case.\n\n17. FSP power on failed after fault 4077 (FSP overheated) is canceled. A BTS reset is needed to try to take the FSP into use.\n\n18.
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-in and take new RF module resources into use.\n\nOnly case #10 is applicable for FZM.\n\nINSTRUCTIONS\n1.
Check the alarm diagnostic information for the reason of the fault report before the reset.\n\n2. Reset (block and unblock) the
BTS.\n\n\n\n\n\n\n\nFAULT NAME\nCalibration initialization failure\n\nFAULT ID\n4067:
EFaultId_CalibrationInitAl\n\nMEANING\nBeamforming calibration configuration has failed.\n\nINSTRUCTIONS\nNote: Perform the steps
below in the order listed until the fault disappears:\n\n1. Reset the RF module.\n2. Replace the RF module.\n\n\n\n\nFAULT NAME\nCell
blocked\n\nFAULT ID\n49: EFaultId_CellBlockedAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nThe fault indicates that the user has blocked the cell using the BTS Site Manager.\n\nFlexi Zone Micro FDD, Flexi Zone Micro
TDD:\nThe user has blocked the cell using the BTS Site Manager.\n\nINSTRUCTIONS\nUnblock the cell to cancel the fault.\n\n\n\n\nFAULT
NAME\nCell configuration data distribution failed\n\nFAULT ID\n6253: EFaultId_CellSetupFailed\n\nMEANING\nA BTS raises this fault if it
experiences a problem in the internal configuration\ndata distribution (cell setup) to the C-Plane and U-Plane SW components.\nThe root
cause of the fault may be an incorrect cell configuration in the site configuration file (scf).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS
TDD, AirScale BTS FDD, AirScale BTS TDD:\nBlock and unblock the BTS.\nIf it does not help:\n1. Check and update the configuration
parameters related to the cells.\n2. Load the correct commissioning file to the BTS.\n3. Block and unblock the BTS.\n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD:\n1. Check and update the configuration parameters related to the cell bandwidth and channels.\n2. Reset the
BTS.\n3. Retry configuration push.\n\nFlexi Zone:\n1. Check and update the configuration parameters related to the cell bandwidth and
channels.\n2. Reset the Flexi Zone Access Point serving the failed cell.\n\n\n\n\nFAULT NAME\nCell disabled due to unknown problem; logs
collected\n\nFAULT ID\n4261: EFaultId_CellStateAuditAl\n\nMEANING\nThe cell state audit detected that the cell was unintentionally
deactivated\nwithout warning. The symptom data is automatically collected.\n\n\nINSTRUCTIONS\nPlease inform the vendor if this alarm is
reported. The vendor will do analysis\non the automatically-collected symptom data when the fault was detected.\nAutomatically collected
symptom data (files) are stored in OMS or NetAct dedicated folder. \nNetAct - Operating Documentation (Collecting symptom data from LTE
to NetAct)\nOMS - Administering and Security in LTE OMS (Sec. 13.9.3 OMS troubleshooting data collection for eNodeB).\n\n\n\n\n\nFAULT
NAME\nCell power failure\n\nFAULT ID\n4090: EFaultId_TxCarrierInputPowerLowAl\n\nMEANING\nThe Flexi Radio Module has detected
low downlink carrier input power from the System Module.\n\nINSTRUCTIONS\n1. Check the other active alarms and act accordingly.\n2. If
that does not help, block/unblock the system module.\n3. a. FSMr2: If that does not help, replace the system module.\nb. FSMr3: If the faulty
cell is on the baseband extension module, replace the extension module.\n\n\n\n\nFAULT NAME\nCell reconfiguration data distribution
failed\n\nFAULT ID\n6257: EFaultId_CellReconfigurationFailed\n\nMEANING\nThe BTS raises this fault if it experiences a problem in the
internal configuration\ndata distribution (cell setup) to C-Plane and U-Plane SW components.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nBlock and unblock the BTS.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Check
and update configuration parameters related to cell bandwidth and channels.\n2. Reset the BTS.\n3. Retry configuration push.\n\nFlexi
Zone:\n1. Check and update configuration parameters related to cell bandwidth and channels.\n2. Reset the Flexi Zone Access Point that is
serving the failed cell.\n\n\n\n\nFAULT NAME\nCommunication failure\n\nFAULT ID\n1806:
NAME\nCompensation buffer is not enough for RF module delay difference\n\nFAULT ID\n4276:
EFaultId_RelativeDistanceCompensationBufferNotEnoughAl\n\nMEANING\nThe 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 capacity of the compensation
buffers. This fault is reported for the maximum transmission delay radio module.\nThe 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 the previous hop radio modules,
and the internal delay of the radio module.\n\n\nINSTRUCTIONS\nReduce 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 radio modules to remove the delay introduced by
the previous radio modules.\n\n\n\n\nFAULT NAME\nConfiguration error: <x>\n\nFAULT ID\n3070: EFaultId_ConfigurationError
\n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears:\n\n1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration.\n\n2. Check
that the BTS cell parameters from the Network management system match\nthe BTS HW configuration (for example, frequency,
power).\n\n3. Check the Network management system alarms for the alarming local cell (LCR).\n\n4. Recommission the BTS to ensure that
all parameters are correctly configured.\n\n\n\n\nFAULT NAME\nConnection Unstable At 3Gbps \n\nFAULT ID\n4310:
EFaultId_ConnectionUnstableAt3Gbps\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nPerform the recovery in the
following sequence:\n1. Check if the optical transmission network connecting the system module with the radio module, or the extension
baseband module (FBBx) and the radio module, supports 6 Gbps transmission.\n2. Check if the cable connecting the system module and the
29/05/2020 Alarms

major
release
radio module, or the cable connecting the extension baseband module and the radio module is fixed firmly to the modules.\n3. Replace the
cable.\n4. Change the radio module where the unstable link is terminated.\n5. If this does not help, replace the FBBx if the unstable link is
terminated\non FBBx.\n6. If this does not help, replace the FCT (system module).\n\nIf an alarm with fault 4038 (Radio master conflict) is
reported at the same time,\nfollow the instructions of fault 4038 because in some cases fault 4038 might be the root cause of fault
4310.\n\n\n\n\nFAULT NAME\nConnection Unstable At 6Gbps\n\nFAULT ID\n4309:
might\nbe the root cause of fault 4309.\n\n\n\n\nFAULT NAME\nCPRI-A RF sharing mode conflict\n\nFAULT ID\n4375:
EFaultId_CpriArfSharingModeConflictAl\n\nMEANING\nThe LTE eNB has detected an RF sharing configuration conflict in the radio that is
also connected to a CDMA BTS. \n1. If the alarm diagnostic information contains "Incorrect mode configuration for CPRI-A RF Sharing", then
one of the following invalid configurations is detected:\n1.1. The LTE eNB is in stand-alone mode and the CDMA BTS is in any mode. \n1.2.
The LTE eNB is in any mode and the CDMA BTS is in stand-alone mode. \n1.3. The LTE eNB and CDMA BTS are both in secondary
mode.\n2. If the alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", then the LTE eNB
is operating in a secondary mode, and the SW and/or AISG management functions is owned by the CDMA BTS.\n\nINSTRUCTIONS\n1. 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 and/or CDMA System Modules. The following mode combinations are allowed: \n1.1. LTE eNB is in secondary
mode and CDMA BTS is in primary mode.\n1.2. LTE eNB is in stand-alone mode and CDMA BTS is disconnected from the radio.\n2. If the
alarm additional information contains "Incorrect secondary functions configuration for CPRI-A RF Sharing", reconfigure the CDMA BTS to
give both SW and AISG management function control to the secondary controller (LTE eNB).\n3. If the previous steps do not help, reset the
alarming radio unit.\n4. If the previous steps do not help, reset the LTE eNB and/or CDMA BTS.\n\n\n\n\nFAULT NAME\nDistributed site
support not enabled\n\nFAULT ID\n4076: EFaultId_DistributedSiteSupportNotEnabledAl\n\nMEANING\nA long distance (high latency)
between the FSM and antenna has been detected but the Distributed Site feature has not been enabled (actDistributedSite =" False). For
FHCC modules, this fault means that there is a long distance between the FSM and the customer's device.\n\nINSTRUCTIONS\nPerform the
steps below in the listed order until the fault disappears:\n1. Either enable the actDistributedSite parameter or switch to a shorter fiber
between the FSM or ABIx and the FR.\n2. Restart the System module.\n\n\n\n\nFAULT NAME\nDSP application fatal error\n\nFAULT
Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone\nSFN Antenna.\n\n\n\n\nFAULT NAME\nDSP loading
failure\n\nFAULT ID\n1962: EFaultId_RruDspLoadingFailure\n\nMEANING\nDSP loading has failed.\n\nINSTRUCTIONS\n1. Reset the RF
module.\n \n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nDSP platform fatal
BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nDSP U-Plane computing environment startup
failed\n\nFAULT ID\n4335: EFaultId_DspUplaneComputingEnvironmentStartupFailedAl\n\nMEANING\nDSP U-plane computing environment
startup has failed.\n\nDSP U-plane computing environment covers U-plane applications and real-time platform services on DSP cores and
MCU cores.\n\nINSTRUCTIONS\nAirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault
disappears:\n1. Reset the BTS using block or unblock.\n2. Replace the extension baseband module (ABIx) according to the fault
source.\n\n\n\n\n\nFAULT NAME\nExternally triggered DSP fatal error\n\nFAULT ID\n6708:
EFaultId_ExternallyTriggeredDspFatalErrAl\n\nMEANING\nThe BTS has purposely triggered a GPIO reset for the DSP.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nIf an FSP in the BTS generates this fault, there is a malfunction in the whole
BTS.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the
the fault source)\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nPerform the steps below in the
listed order until the fault disappears.\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n2. Replace
the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFailure in optical
interface\n\nFAULT ID\n3030: EFaultId_FailureInOptical_Rp3Interface\n\nMEANING\nThe AirScale/Flexi BTS (System Module) has detected
an abnormal operation or a failure\nin an optical RP3 interface between two modules . \nThe failure cannot be attributed to a specific module
but there are several\npossible fault sources, for example, fiber optical cable, SFP, or individual module.\n\nINSTRUCTIONS\n1. PROBLEM
29/05/2020 Alarms

major
release
document.\n\n\n\n\nFAULT NAME\nFailure In Optical Interface <optIf ID>\n\nFAULT ID\n3012:
EFaultId_FailureInOpticalInterface\n\nMEANING\nThe optical interface is not working properly.\nThe SFP (Small Form-factor Pluggable)
module might be missing, faulty, or mismatched.\n\nINSTRUCTIONS\n1. Check the cables between the System Module and RF Module.
\n\n2. Reset the RF Module. \n\n3. If that does not help, reset the site. \n\n4. If that does not help, replace the RF module that is generating
the alarm.\n\n\n\n\nFAULT NAME\nFailure in replaceable baseband unit\n\nFAULT ID\n3003: EFaultId_FbiaFailureAl\n\nMEANING\nThe
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nFault between FSM and FSP because of the
lack of RP1 clock\n\nFAULT ID\n412: EFaultId_LostFrameSync\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD:\nSynchronization between
the FCM/FCT and FSP is lost.\n\nAirScale BTS FDD, AirScale BTS TDD:\nSynchronization between the FCT and ABIx is
lost.\n\nINSTRUCTIONS\n1. Block/unblock the BTS.\n2. 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. Otherwise, replace the extension baseband module
reporting the fault.\n\n\n\n\nFAULT NAME\nFiber delay and antenna round trip delay exceeded\n\nFAULT ID\n4256:
EFaultId_MaximumDelayExceededAl\n\nMEANING\nFiber Delay and Antenna Round Trip Delay exceeds the supported capability of the
BTS.\n\nINSTRUCTIONS\n1. Confirm if the existing applied configuration is within the configured FR hardware capabilities. \n2. Reduce the
length of the fiber cable to a length that is supported by the BTS and FR combination.\n\n\n\n\nFAULT NAME\nFilter tuning failure\n\nFAULT
ID\n1840: EFaultId_TuningFailureAl\n\nMEANING\nThe Radio Module is unable to tune to a required sub-band properly (tuning\nfailure), or
another major failure has been detected by the Radio Module\n(unit faulty).\n\nINSTRUCTIONS\nReplace the alarming Radio
Module/MultiRadio Combiner.\n\n\n\n\nFAULT NAME\nFilter unit faulty\n\nFAULT ID\n1841: EFaultId_UnitFaultyAl\n\nMEANING\nThe radio
module has detected an internal filter failure.\n\nINSTRUCTIONS\n1. Reset the radio module.\n2. If resetting the radio module does not help,
replace the alarming radio module.\n\n\n\n\nFAULT NAME\nFPGA R/W error\n\nFAULT ID\n1963:
EFaultId_FpgaRwErrorAl\n\nMEANING\nAn error has occurred during a read/write attempt on the FPGA.\n\nINSTRUCTIONS\n1. Reset the
RF Module. \n2. If that does not help, replace the alarming RF Module.\n\n\n\n\nFAULT NAME\nFrame clock missing\n\nFAULT ID\n1903:
EFaultId_FrFrameClockMissing\n\nMEANING\nThe System Module clock reference differs from the RF Module
check other active alarms to determine the root cause.\n\n\n\n\nFAULT NAME\nFSP overheating\n\nFAULT ID\n4077:
EFaultId_FspOverheatingAl\n\nMEANING\nThe temperature of the FSP/ABIx board has exceeded the critical threshold
value.\n\nINSTRUCTIONS\n1. Check the fans and ensure that the ambient temperature on the site is acceptable.\n2. If that does not help,
replace the alarming module.\n\n\n\n\nFAULT NAME\nFSP subunit lost\n\nFAULT ID\n4341: EFaultId_FspSubunitLostAl\n\nMEANING\nAn
FSP (ABIx) subunit is unavailable (lost).\n\nINSTRUCTIONS\nAirScale BTS FDD, AirScale BTS TDD:\nNote: Perform the steps below in the
listed order until the fault is resolved:\n1. Reset the BTS using block or unblock.\n2. Replace the extension baseband module (ABIx)
according to the fault source.\n\n\n\n\n\nFAULT NAME\nIncoherence in cell configuration\n\nFAULT ID\n4000:
EFaultId_IncoherencyInConfiguration\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nToo many
cells are commissioned to the BTS.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nMore LNCELs than the supported maximum number
is configured, or too many LCRs are commissioned to one RF module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nIf other alarms are reported, re-commission the BTS with the correct number of cells per BTS.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD:\nRe-commission the BTS with the correct number of LCRs per RF module.\n\n\n\n\nFAULT
NAME\nIncompatible SW version detected\n\nFAULT ID\n23: EFaultId_IncompatibleSwVersionAl \n\nMEANING\nIncompatible software has
been detected.\n\nINSTRUCTIONS\nUpdate 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 by NetAct.\n\nIn case of RF modules with factory SW loaded, SW update is
a mandatory step.\n\n\n\n\nFAULT NAME\nInternal MTU configuration failure\n\nFAULT ID\n4025:
EFaultId_MtuConfigurationFailureAl\n\nMEANING\nThe internal maximum transfer unit (MTU) configuration has failed on the FSP or
FBB/ABIx.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System Module that
is causing the alarm.\n2. Replace the System Module that is causing the alarm.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone,
Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. Replace the Flexi
Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nInvalid frequency channel for the BTS
HW\n\nFAULT ID\n1807: EFaultId_InvalidFrequencyChannelForBTSHW\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nThe 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 bandwidth or incorrect center frequency.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi
Zone SFN Antenna:\nThe 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 number of carriers.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna: \nCheck the parameters of the frequencies
against the BTS HW configuration. Check whether the connected radio supports the carrier bandwidth requested in the commissioning file,
29/05/2020 Alarms

major
release
and whether the requested in commissioning file central frequencies of the TX and RX are correct. There are different types of variations of
the HW that might have limitations in the supported frequency range and bandwidth.\n\n\n\n\nFAULT NAME\nInvalid sidelink transmit pool
configuration\n\nFAULT ID\n6298: EFaultId_InvalidSidelinkTransmitPoolConfigurationAl\n\nMEANING\nThe sidelink transmit resource pool
configuration is invalid, and overlapping with PUCCH region or leaving insufficient resource for PRACH.\n\nINSTRUCTIONS\nCorrect the site
configuration file (scf) content and recommission the BTS by performing one or both of the following steps:\n1. Adjust the sidelink direct
communication transmit pool configuration in frequency domain in order to:\n- not overlap with PUCCH\n- reserve enough place for 6
consecutive UL RBs for PRACH and at least one additional PRB for Msg3 (see Note)\n2. Reduce the maximal number of active UEs to be
supported by adjusting the following parameters:\n- maxNumActUe\n- aPucchMinNumRrcNoDrb\n- aPucchAddAUeRrHo,
aPucchAddAUeTcHo \n- aPucchMinNumEmergencySessions (if emergency handling is active)\n\nNote: Sidelink direct communication
configuration across eNBs on a given carrier has to be identical. Changing configuration on just one eNB is not recommended and has to be
done across the network where LTE2612 feature is enabled.\n\n\n\n\nFAULT NAME\nLow noise amplifier failure\n\nFAULT ID\n1839:
EFaultId_LNAFailureAl\n\nMEANING\nThe Radio Module has detected a malfunction of an internal LNA unit.\n\nINSTRUCTIONS\nReplace
the alarming Radio Module.\n\n\n\n\nFAULT NAME\nLTE-U Channel Change Failure\n\nFAULT ID\n6819:
EFaultId_LteuChannelChangeFailed\n\nMEANING\nThe LTE-U feature is enabled (actLteU is 'true') on the eNB and an attempted LTE-U
channel (frequency) switch has failed.\n\nINSTRUCTIONS\nIf the issue persists, perform the steps below in the listed order until the fault
disappears.\n1. Block/unblock the impacted cell.\n2. Reset the Flexi Zone Micro BTS or Access Point.\n3. Replace the Flexi Zone Micro BTS
or Access Point.\n\n\n\n\nFAULT NAME\nLTE-U Duty Cycle Change Failure\n\nFAULT ID\n6820:
EFaultId_LteuDutyCycleChangeFailed\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nIf the issue persists, perform the steps below in the listed order
until the fault disappears.\n1. Block/unblock the impacted cell.\n2. Reset the Flexi Zone Micro BTS or Access Point.\n3. Replace the Flexi
Zone Micro BTS or Access Point.\n\n\n\n\nFAULT NAME\nMaster unit has lost connection to the slave unit\n\nFAULT ID\n4019:
EFaultId_KeepAliveStatusErrorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe connection to
the FSP/ABIx or DSP has been lost, or the sub-module reports an error situation.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi
Zone SFN Antenna:\nThe connection to the DSP module has been lost.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\nNote: Perform the steps below in the listed order until the fault disappears.\n\n1. Reset the BTS.\n2. Replace the
faulty module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS,
Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nMessage routing problem in receiver (RX)\n\nFAULT
ID\n2058: EFaultId_MuksuMsgRoutingFailedAl\n\nMEANING\nAn interrupt is generated if a message does not get routed.\n\nThis is
considered normal when DSPs are starting up and RP3 sync is done.\n\nINSTRUCTIONS\nIf OptIf is the source:\n\n1. Check the antenna
mapping to the local cells in the commissioning file.\n2. Depending which optical interface is notified as faulty check the cables between \n -
the System Module and RF Module, or the cable between the FBB module and the RF Module (Flexi BTS FDD/TDD),\n - the cable between
the ABIx module and the RF Module (AirScale BTS FDD/TDD).\n3. Block and unblock the RF Module.\n4. Perform a BTS reset. \n5. Replace
the RF module behind the optical link.\n\nFlexi BTS FDD/TDD:\nIf FSP is the source:\n1. Perform a System Module reset.\n2. If that does not
help, replace the System Module.\n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD:\nIf FBB/ABIx is the source:\n1. Perform a System
Module reset.\n2. If that does not help, replace the FBB/ABIx card.\n\n\n\n\nFAULT NAME\nMismatched RRU optical module <optif
ID>\n\nFAULT ID\n1969: EFaultId_MismatchedSfpAl\n\nMEANING\nThe small form-factor pluggable (SFP) module is
mismatched.\n\nINSTRUCTIONS\nReplace the faulty SFP.\n\n\n\n\nFAULT NAME\nModule Clock faulty\n\nFAULT ID\n1926:
EFaultId_FrModuleClockFaulty\n\nMEANING\nThe RF module has lost lock to the incoming clock.\n\nINSTRUCTIONS\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nInstructions 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 effort. \n\nSection A: Check on the system module
side:\n1. Check if the connector seal is properly mounted and firmly in place. \n2. 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, readjust the connection or mounting.\n3.
Check if the LED indicates the faulty SFP (connected to System Module). Replace the SFP if it is faulty.\n4. Check if the optical cable is
properly connected or mounted in the SFP.\n5. Clean the optical connectors that are connected to the SFP. Reset the RF HW unit and check
if this solves the problem.\n\nSection B: Check on the radio module side:\n1. Check if the connector seal is properly mounted and firmly in
place.\n2. 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 connection or mounting.\n3. Check if the optical cable is properly connected or mounted in the SFP.\n4.
Clean the optical connectors at the FR module end. Reset the FR HW unit and check if this solves the problem.\n\nSection C: Check the
optical connection:\n1. 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 can detach or damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the
optical attenuation) from the System Module's end. Check the documentation of the measuring equipment for instruction details.\n3.
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 instruction details.\n\nIf the alarm continues after executing the steps from sections A, B, and C, replace the FR
module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nReplace the Flexi Zone Micro BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nMulti-carrier cell disabled\n\nFAULT ID\n6815:
EFaultId_MultiCarrierCellDisabledAl\n\nMEANING\nThe multi-carrier cell is disabled because of the lock or block of the other multi-carrier
cell.\n\nINSTRUCTIONS\nThe other multi-carrier cell can be enabled by deleting the blocked or locked cell.\n\n\n\n\nFAULT NAME\nNo
connection to RP1 interface\n\nFAULT ID\n4189: EFaultId_NoRp1ConnectAl\n\nMEANING\nFlexi Zone Micro FDD, Flexi Zone Micro TDD,
Flexi Zone (Flexi Zone Access Point), Flexi Zone SFN Antenna:\nThe connection to the RP1 Transport (TRSW) or Radio Frequency (RFSW)
interface has been lost.\n\nFlexi Zone (Flexi Zone Controller):\nThe connection to RP1 Transport (TRSW) interface has been
lost.\n\nINSTRUCTIONS\n\n\n\n\nFAULT NAME\nNo connection to unit\n\nFAULT ID\n10: EFaultId_NoConnectionToUnitAl
\n\nMEANING\nThe connection to a module that belongs to the BTS configuration has been lost.\n\nIn case of SNMP radios, there is a
problem with the optical interface or an internal fault, which results in a radio reset.\n\nINSTRUCTIONS\n1. 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.\n\n2. Check the
fault history.\n\n\n\n\nFAULT NAME\nNot able to synchronize baseband bus with <x>\n\nFAULT ID\n1815:
Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nNot enough PUSCH resources for PRACH\n\nFAULT ID\n6294:
EFaultId_PrachResourceNotConfigurableAl\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nAdjust 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.\n\nReduce the
maximal number of active UE to be supported by adjusting parameters \nmaxNumActUe, aPucchMinNumRrcNoDrb, aPucchAddAUeRrHo,
aPucchAddAUeTcHo, and aPucchMinNumEmergencySessions if Emergency handling is active.\n\n\n\n\nFAULT NAME\nOperation on
shared optical port failed\n\nFAULT ID\n4180: EFaultId_OperationOnSharedOpticalPortFailedAl\n\nMEANING\nThe shared OptIF mode
cannot be read from or changed in the FBBC card.\n\nINSTRUCTIONS\nFault 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 can decide whether to change the FBBC card or
not.\n\n\n\n\nFAULT NAME\nOptical Interface faulty\n\nFAULT ID\n2000: EFaultId_OIC_TxAl\n2001: EFaultId_OIC_PresAl\n\nMEANING\nA
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 (fault 2001). The SFP is a part of the fiber cable package.\n\nINSTRUCTIONS\n1. Check that the small form-factor
29/05/2020 Alarms

major
release
pluggable (SFP) is properly connected to the System Module.\n\n2. Replace the SFP module.\n\n\n\n\nFAULT NAME\nPA Critical
temperature threshold exceeded\n\nFAULT ID\n1980: EFaultId_PaCriTempThresExceedAl\n\nMEANING\nThe 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 shutting down
the PA on its own.\n\nINSTRUCTIONS\n1. 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 installed.\n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n3. If that does not help, replace the BTS or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nParallel optical link length
mismatch\n\nFAULT ID\n4072: EFaultId_ParallelLinkDifferenceTooLargeAl \n\nMEANING\n- 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 RRU). The main link is
considered as a reference and the secondary link is compared to the main link. \n- 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 module-shared RF
is too large.\n\nThe additional info in the alarm about difference in length should be delivered in the alarm only when LTE is radio
master.\n\nThe information consists of: \n- The number of physical port on the system module where primary link starts.\n- The number of
physical port on the system module where secondary too long/too short link starts.\n- The difference in lengths with information if secondary
link is too short or too long.\n- The difference in delays in nanoseconds.\n\nINSTRUCTIONS\nIf the fault is detected in non-sharing
configuration:\n1. 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.\n2. 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 60 meters in OBSAI RRU, or 146 meters in CPRI RRU. \n\nIf the fault is
triggered because of an incorrect RF sharing configuration, check that the RF sharing feature is enabled on synchronization master system
module.\n\nIf the alarm with fault 4038 (Radio master conflict) is reported at the same time,\nfollow the instruction for fault 4038 because in
some cases, 4038 may be the root cause of fault 4072.\n\n\n\n\nFAULT NAME\nPeriodic CAM Reports Not Received\n\nFAULT ID\n6818:
EFaultId_CamReportMissing\n\nMEANING\nThe 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 discarded because it is outside of the expected range is not considered as a
missing report.\n\nINSTRUCTIONS\nIf the issue persists, perform the steps below in the listed order until the fault disappears.\n1.
Block/unblock the impacted cell.\n2. Reset the Flexi Zone Micro BTS or Access Point.\n3. Replace the Flexi Zone Micro BTS or Access
Point.\n\n\n\n\nFAULT NAME\nPhase error exceeds 50 ns limit\n\nFAULT ID\n4320:
EFaultId_PhaseSynchronizationError50nsAl\n\nMEANING\nThis fault indicates that the absolute phase error between the OCXO (Oven
Controlled Oscillator) output and the reference phase provided by the CPRI Ir interface exceeds the limit of 50ns.\n\nINSTRUCTIONS\n1,
Check if other alarms are active in the LTE BTS or SCDMA BTS.\n2. Check the optical connection between the SCDMA and LTE BTS.
Replace the optical cable and/or SFP(s).\n3. If this does not help, reset LTE BTS.\n4. If this does not help, reset SCDMA BTS.\n5. If this does
not help, replace FCT.\n\n\n\n\n\n\n\nFAULT NAME\nPipe dangerously overheating \n\nFAULT ID\n1938:
EFaultId_FrPipeOverheat\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Check if the ambient temperature or environmental conditions are
within the design limits of the radio module. When the ambient temperature or environmental conditions are out of limits, the alarm is
expected and no further actions are needed.\n\n2. 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 flow, and mount the module according to the instructions and
recommendations.\n\n3. Check if excessive sunlight is causing an overheat. Install sunshield following the mounting instructions and
recommendations.\n\n\n\n\nFAULT NAME\nPost test failed\n\nFAULT ID\n1925: EFaultId_FrPostTestFailed\n\nMEANING\nAn RF module's
power-on self-test has failed at start-up.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1.
Reset the RF HW unit.\n2. If the problem continues after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nPOST test failed\n\nFAULT ID\n69: EFaultId_Post_test_failedAl\n\nMEANING\nThe unit or module has
been tested during the BTS power-on self test (POST) and a failure has been detected.\n\nINSTRUCTIONS\n1. Reset the alarming unit or
module.\n2. Remove or reinsert the alarming unit or module.\n3. Replace the alarming unit or module.\n\n\n\n\nFAULT NAME\nPower level
not supported\n\nFAULT ID\n4008: EFaultId_PowerLevelNotSupportedAl\n\nMEANING\n1. 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.\n2. 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.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS
TDD, AirScale BTS FDD, AirScale BTS TDD:\nDefine 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 site manager to send the file to the BTS.\n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nDefine 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 Micro BTS, Flexi Zone Controller, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRadio master conflict\n\nFAULT ID\n4038: EFaultId_RadioMasterConflictAl\n\nMEANING\nThe 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 the connected radio unit.\n\nINSTRUCTIONS\nThere might be three reasons for the fault:\n1. The radio unit that should only be
connected to the LTE Flexi System Module is\nalso connected to the WCDMA system module. In this case, disconnect the radio unit from the
WCDMA system module.\n2. 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 file to the BTS. Note that only one system module can be set as master for one radio unit.\n3. 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, or a master power on. A temporary alarm with fault 4038 is the expected behavior and should be ignored. No action is
necessary in this case. \n\n\n\n\nFAULT NAME\nRadio module internal hardware assignment indeterminate\n\nFAULT ID\n1993:
EFaultId_FrInternalHwAssignmentIndeterminateAl\n\nMEANING\nThe fault is reported by complex radio modules with multiple physical units
where functionality is distributed. An incompatibility has been found with the identification method.\n\nINSTRUCTIONS\n1. Reset the
alarming radio unit.\n2. 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 have a user alarm cable or nothing at all), and ensure that the Secondary subunit has an
Alarm Cap on the ASIG ALM connector. The secondary radio is the one that serves antenna ports 3 and 4.\n\n\n\n\nFAULT
NAME\nReceiving failure in Optical Interface\n\nFAULT ID\n2002: EFaultId_OIC_RxAl\n\nMEANING\nThe incoming optical signal to the
Small Form-Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached.\n\nThe 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
broken.\n\nINSTRUCTIONS\n1. Check the status of the module behind the faulty link (power on, and so on).\n\n2. 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
faulty SFP. Replace the SFP if it is faulty.\n\n3. Clean the connectors, test the fiber cable, and replace it if it is faulty.\n\n4. If the previous
steps do not help, replace the module behind the faulty link.\n\n\n\n\nFAULT NAME\nRF BB bus configuration error\n\nFAULT ID\n1905:
EFaultId_FrRfBbBusConfigError\n\nMEANING\nThe RF Module baseband bus was configured incorrectly.\n\nINSTRUCTIONS\n1. Confirm if
the existing applied configuration is within the configured RF\nHW capabilities.\n2. Check BTS connections and commissioning settings.\n3.
Block or unblock the BTS.\n4. If HW configuration is confirmed, then this problem is caused by eNB\nSW. Check other active
alarms.\n\n\n\n\nFAULT NAME\nRF BB bus synchronization error\n\nFAULT ID\n1904: EFaultId_FrRfBbBusSynchError \n\nMEANING\nThe
baseband bus between the System Module and RF Module is out of synchronization.\n\nINSTRUCTIONS\nInstructions 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.
\n\nSection A: Check on the system module side:\n1. Check if the connector seal is properly mounted and firmly in place. \n2. 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 connection/mounting.\n3. Check if the LED indicates the faulty SFP (connected to System Module). Replace the SFP if it is
faulty.\n4. Check if the optical cable is properly connected/mounted in the SFP.\n5. Clean the optical connectors that are connected to the
SFP. Reset the RF HW unit and check if this solves the problem.\n\nSection B: Check on the radio module side:\n1. Check if the connector
29/05/2020 Alarms

major
release
seal is properly mounted and firmly in place.\n2. 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 connection/mounting.\n3. Check if the optical cable is properly
connected/mounted in the SFP.\n4. Clean the optical connectors at the RF module end. Reset the RF HW unit and check if this solves the
problem.\n\nSection C: Check the optical connection:\n1. 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 the connectors. \n2. OPTIONAL: Test the fiber cable (for example,
measure the optical attenuation) from the System Module end. Check the measuring equipment documentation for instructions.\n3.
OPTIONAL: Test the fiber cable (for example measure the optical attenuation) from the RF Module end. Check the measuring equipment
documentation for instructions.\n\nIf the alarm is still observed after executing steps from sections A, B, and C, replace the RF
module.\n\n\n\n\nFAULT NAME\nRF data setup failure\n\nFAULT ID\n1997: EFaultId_RfSetupFaultAl\n\nMEANING\nA 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 with
this fault is automatically canceled once the autonomous recovery actions are completed.\n\nINSTRUCTIONS\n1. In a CPRI-A RF sharing
configuration, the CDMA BTS performs the needed recovery actions for this fault.\n2. If the fault does not clear within 20 minutes, then reset
the radio.\n\n\n\n\nFAULT NAME\nRF Module blocked\n\nFAULT ID\n1931: EFaultId_FrBlocked\n\nMEANING\nThis 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 fault means that FR is blocked. When a LTE FSM/ASIA plays the role of the master, or a LTE system module shares CPRI/Ir radio
module with a SCDMA system module (dual mode configuration), and FR is blocked, fault 48:EFaultId_UnitBlockedAl is detected, not
1931.\n\nINSTRUCTIONS\nNo action is needed.\n\n\n\n\nFAULT NAME\nRF Module configuring failed\n\nFAULT ID\n1900:
EFaultId_FrConfiguringFailed\n\nMEANING\nThe RF module configuration has failed because of an HW or SW
fault.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nFor URGA, URCB, URCC, and URKA
radio variants, if the fault is preceded by a\ndual 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 proceeding with the following steps:\nFor all radio variants:\n1. Confirm if the currently
applied configuration is within the configured RF HW capabilities.\nIn LTE-LTE sharing, check if the configuration of both eNBs is consistent
with the shared radio capability. Correct the configuration, recommission the eNBs, and reset the radio where fault 1900 is reported.\n2.
Check BTS connections and commissioning settings.\n3. Block/unblock the BTS.\n4. If the HW configuration is confirmed as correct, this
problem is caused by the eNB SW. Check other active alarms.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN
Antenna:\nReplace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module
critical file not found\n\nFAULT ID\n1901: EFaultId_FrCriticalFileNotFound\n\nMEANING\nA critical configuration file is missing from the RF
Module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Verify if the HWP1 file is present
in the FR module. Download the file if it is missing. Reset the FR module.\n2. If the file is present, block/unblock the RF HW unit.\n3. If the
problem continues after performing step 2, replace the FR HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Block/unblock the
BTS.\n2. Replace the Flexi Zone Micro BTS.\n\nFlexi Zone:\n1. Reset Flexi Zone Access Point.\n2. Replace the Flexi Zone Access
Point.\n\nFlexi Zone SFN Antenna:\n1. Reset Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nRF Module failure\n\nFAULT ID\n3010: EFaultId_RfModuleFailure\n\nMEANING\nThe BTS has detected an abnormal operation or a
failure in the internal functionality of the RF Module.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem still
persists after step 1 has been performed, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\n1. Check the other active Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna faults and act
accordingly.\n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. If that does not help, replace the
faulty Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module faulty primary optical
link\n\nFAULT ID\n1984: EFaultId_FrPrimaryLinkLossAl\n\nMEANING\nThe radio unit has detected a failure on its optical connection to the
system module or an upstream radio unit (chaining case).\n\nINSTRUCTIONS\n1. 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.\n2. Clean the connectors, test the fiber cable,
and replace them if they are faulty.\n3. If the previous steps do not help, replace the alarming radio unit hardware.\n\n\n\n\nFAULT
NAME\nRF Module filter input power missing\n\nFAULT ID\n1910: EFaultId_FrFilterInputPowerMissing\n\nMEANING\nThe RF Module filter
has measured TX power that is too low.\n\nINSTRUCTIONS\n1. Reset the RF HW unit.\n2. If problem is still observed after performing step
1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nRF Module gain adjusting failure\n\nFAULT ID\n1908:
EFaultId_FrGainAdjust\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe TX output power
adjustment has failed.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nCLGC convergence has failed. Gain
target cannot be achieved.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF
HW unit.\n2. If the problem is still observed after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD,
Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the configuration. \n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna. \n3. If that does not help, replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF Module out of order\n\nFAULT ID\n1912: EFaultId_FrOutOfOrder\n\nMEANING\nThe RF module is out
of order because of a software or hardware fault.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after step 1 has been performed, replace the RF HW unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi
Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module power supply output faulty\n\nFAULT ID\n1918:
EFaultId_FrPowerOutputFault\n\nMEANING\nThe power supply supervision has detected an overvoltage, undervoltage, or overcurrent in the
RF module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If
the problem continues after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone, Flexi Zone SFN Antenna:\n1.
Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF module
unauthorized\n\nFAULT ID\n4278: EFaultId_RfModuleUnauthorizedAl\n\nMEANING\nRFM product authorization has failed because of
missing RFM properties. RFM\nis not supported by the current BTS software release and the BTS did not find\nrelevant 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.\n\nINSTRUCTIONS\n1. Make sure that the corresponding RFM plug-in module has been installed on the network server in NMS
(NetAct SW Archive).\n\n2. Update the corresponding RFM plug-in software module in the BTS/eNB from NetAct. \n\n3. Supply the RFM
plug-in software module to BTS/eNB locally via BTS Site Manager if NetAct connection is not available. \n\n4. Block/unblock the
BTS.\n\nNote: You need to commission the radio module before it can be taken into use. \n\n\n\n\nFAULT NAME\nRRU CPU and DSP link
failure\n\nFAULT ID\n1961: DspLinkFailureAl\n\nMEANING\nThe CPU cannot connect to the DSP.\n\nINSTRUCTIONS\n1. Reset the RF
Module.\n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRRU DPD self test
failure\n\nFAULT ID\n1960: EFaultId_DpdTestFailureAl\n\nMEANING\nThe RRU digital pre-distortion (DPD) has failed during self
test.\n\nINSTRUCTIONS\n1. Reset the RF Module. \n2. If that does not help, replace the RF Module that is generating the
alarm.\n\n\n\n\nFAULT NAME\nRTWP level below threshold\n\nFAULT ID\n4333: EFaultId_RtwpLevelBelowThresholdAl\n\nMEANING\nThe
measured received total wideband power (RTWP) is below the threshold.\n\nINSTRUCTIONS\nThe 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 failure of any unit on
the path between the Rx antenna line port on the radio module or MHA and the DSP. Execute the following actions in the presented
sequence to recover from the fault:\n1. Reset the alarming radio unit.\n2. If the first step is completed and the fault is reported again, reset the
BTS (block or unblock the BTS).\n3. If the previous step is completed and the fault is reported again: \n a. If the alarming Rx antenna has an
MHA commissioned, then check that the MHA is actually connected to it.\n b. If the alarming Rx antenna has an MHA connected, then check
that the actual MHA gain matches the commissioned MHA gain. \n c. Check that the actual Antenna Total Loss matches the commissioned
Total Loss. \n d. Check that the actual Antenna Additional Rx Gain matches the commissioned Additional Rx Gain. \n4. 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 module
29/05/2020 Alarms

major
release
to the system module or extension baseband module.\n5. If the previous steps have been completed and the fault is reported again, replace
the MHA connected to the affected Rx antenna.\n6. If the previous steps have been completed and the fault is reported again, replace the
alarming radio module hardware.\n7. If the previous steps have been completed and the fault is reported again, replace the system module
hardware or extension baseband module hardware (depending on where the alarming radio module is connected).\n\n\n\n\nFAULT
NAME\nRX out of order\n\nFAULT ID\n1911: EFaultId_FrRxOutOfOrder\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nThe RX RF synthesizer of the RF module is not locked.\nFor SNMP interface:\nThe received power is low for the
RRH.\nFor CPRI-A interface:\nThe RX path in the FR module is faulty.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\nThe RX path in the FR module is faulty.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD:\n1. Reset the RF HW unit.\n2. If the
problem continues after resetting the RF HW unit, replace the RF HW unit.\n3. In case of SNMP radio, the only way to clear the fault is to
reset the radio or replace the unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the HW
unit.\n2. If the problem continues after resetting the HW unit, replace the HW unit.\n\n\n\n\nFAULT NAME\nSevere SFP performance
aggravation <optIf ID>\n\nFAULT ID\n1966: EFaultId_SevereSfpPerformanceAggravationAl\n\nMEANING\nThe optical interface is not
working properly; performance aggravation is high.\n\nINSTRUCTIONS\n1. Check the cables between the System Module or ABIA and RF
Module. \n\n2. Reset the RF Module. \n\n3. If those do not help, block and unblock the site. \n\n4. If those do not help, replace the RF module
that is causing the alarm.\n\n\n\n\nFAULT NAME\nSevere SFP reception power aggravation <optIf ID>\n\nFAULT ID\n1967:
alarm.\n\n\n\n\nFAULT NAME\nSFN cell disabled due to feature disable\n\nFAULT ID\n4363:
EFaultId_SfnCellDisabledDueToFeatDeactAl\n\nMEANING\nThe cell using SFN resources is disabled since the feature actSfn is set to
"false".\n\nINSTRUCTIONS\nNone\n\n\n\n\n\nFAULT NAME\nSFP Failure <optIf ID>\n\nFAULT ID\n1948:
EFaultId_AbnormalOpticalSfpOfIrInterfaceAl\n\nMEANING\nThe optical interface is not working properly.\nThe small form-factor pluggable
(SFP) module might be missing or faulty.\n\nINSTRUCTIONS\nReplace the faulty SFP.\n\n\n\n\nFAULT NAME\nSFP missing <OptIf
ID>\n\nFAULT ID\n1964: EFaultId_SfpMissingAl\n\nMEANING\nThe optical interface is not working properly. The Small Form-factor
Pluggable (SFP) module might be missing, or it might be faulty.\n\nINSTRUCTIONS\nReplace the faulty SFP.\n\n\n\n\nFAULT NAME\nSFP
on RF Module faulty or unsupported\n\nFAULT ID\n1986: EFaultId_SfpOnRadioModuleFaultyOrUnsupportedAl\n\nMEANING\nThe SFP on
the radio unit is either faulty or not supported.\n\nINSTRUCTIONS\n1. 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.\n2. Reset the affected radio unit.\n\n\n\n\nFAULT
NAME\nShared radio not synchronized to Radio Master\n\nFAULT ID\n4253: EFaultId_SharedRadioNotSyncToMasterAl\n\nMEANING\nThe
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.\n\nINSTRUCTIONS\nPerform following actions until the problem is solved:\n1. Check the optical connection between the radio
master system module and the shared radio.\n2. Check the alarms in the radio master system module and act accordingly. \n3. Reset the
radio master system module.\n\n\n\n\n\nFAULT NAME\nSumming service default initialization failed\n\nFAULT ID\n4092:
module.\n\n\n\n\nFAULT NAME\nSW corrupted\n\nFAULT ID\n1850: EFaultId_SwCorruptedAl\n\nMEANING\nA corrupted SW file in the
FLASH has been detected.\nThe unit cannot complete start-up.\n\nINSTRUCTIONS\nUpdate the SW to the BTS.\n\n\n\n\nFAULT
NAME\nSW fallback\n\nFAULT ID\n4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl\n4083:
EFaultId_FallbackDueToConfigurationDataMigrationFailureAl\n4085:
previously-active SW version - BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW
units in the BTS and\n2. the BTS is up and running.\nOtherwise:\n1. the previously-active SW version is not running in all HW units in the
BTS and\n2. the BTS is not up and running (recovery SW update is still supported).\n\nFault 4082 for FSP fallback can be canceled due to
SW upgrade on FSP only.\nIn this case, an FSP reset to activate the new version of SW may cancel the fault.\nThe state of the fault is
failure and the BTS cannot operate with that SCF.\n\nIf BTS O&M has detected that the BTS can start with the previously-active SW
version - BTS O&M processed consistent fallback and\n1. the previously-active SW version is running in all HW units in the BTS and\n2.
the BTS is up and running. \nOtherwise:\n1. the previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not
up and running (recovery SW update is still supported).\n\n\n4085:\n\nTransport SW on the source unit has indicated the need for a software
fallback.\nIf BTS O&M has detected that the BTS can start with the previously-active SW version - BTS O&M processed consistent
fallback and\n1. the previously-active SW version is running in all HW units in the BTS and\n2. the BTS is up and running. \nOtherwise:\n1.
the previously-active SW version is not running in all HW units in the BTS and\n2. the BTS is not up and running (recovery SW update is still
Zone:\nNone\n\n\n\n\nFAULT NAME\nSystem Module failure\n\nFAULT ID\n3000: EFaultId_SystemModuleFailure\n\nMEANING\nThe BTS
has detected an abnormal operation or a failure in the internal functionality of the System Module.\n\n\n\nINSTRUCTIONS\nNote: Perform
the steps below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\n1. Reset the System Module.\n2. Replace the System Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT ID\n3040:
EFaultId_TemperatureAlarm\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed
order until the BTS fault disappears.\n\n1. Check the other BTS faults and act accordingly.\n\n2. 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, that is, the BTS
29/05/2020 Alarms

major
release
Snapshot.\n\n\n\n\nFAULT NAME\nTuning frequency out of range\n\nFAULT ID\n4043:
EFaultId_TuningFrequencyOutOfRangeAl\n\nMEANING\nThe Radio Module has detected that the requested frequency does not fit the
capabilities offered by Radio Module.\n\nINSTRUCTIONS\nRe-configure the frequency settings in a proper way with respect to the
capabilities of the Radio Module.\n\n\n\n\nFAULT NAME\nTX out of order\n\nFAULT ID\n1907: EFaultId_FrTxOutOfOrder\n\nMEANING\nThe
RF module's TX path cannot be used.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1.
Reset the RF HW unit.\n2. If the problem continues after step 1 has been performed, replace the RF HW unit.\n3. In case of SNMP radio, the
only way to clear the fault is to reset the radio or replace the unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\n1. Check the connection and integrity of the antenna connector, cable, and antenna.\n2. 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.\n3. Reset the BTS
device. If the alarm persists, replace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nTX output overdrive\n\nFAULT ID\n1983: EFaultId_FrTxOutputOverdriveAl\n\nMEANING\nHardware 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
circuitry.\n\nINSTRUCTIONS\n1. 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 the instructions for handling those alarms.\n2. Reset the alarming radio unit.\n3. If
previous steps have not canceled the fault condition, replace the alarming radio unit hardware.\n\n\n\n\nFAULT NAME\nUnit (module)
dangerously overheating \n\nFAULT ID\n1937: EFaultId_FrDangerouslyOverheat\n\nMEANING\nThe validated RF sensor temperature is
greater than or equal to the pre-defined value in the unit property file.\n\nINSTRUCTIONS\n1. Check if the ambient
temperature/environmental conditions are within the design limits of the radio module. When the ambient temperature/environmental
conditions are out of limits, the alarm is expected and no further actions are needed.\n\n2. 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 flow, and mount the
module according to the instructions and recommendations.\n\n3. Check if excessive sunlight is causing an overheat. Install sunshield,
following the mounting instructions and recommendations.\n\n\n\n\nFAULT NAME\nUnit blocked\n\nFAULT ID\n48:
EFaultId_UnitBlockedAl\n\nMEANING\nA module is blocked with the BTS Site Manager. \nThe purpose is to avoid fault indications that might
be raised during the module maintenance task.\nThe 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 module with an SCDMA system module (dual mode
configuration). In other cases, that is, when a WCDMA system module is the master agent for the blocked shared (WCDMA/LTE) radio
module, fault:1931 is raised.\n\nINSTRUCTIONS\nUnblock the module with the BTS Site Manager.\n\n\n\n\nFAULT NAME\nUnit initialization
failure\n\nFAULT ID\n4040: EFaultId_InitFaultManAl\n\nMEANING\nA module initialization has failed.\n\n\nINSTRUCTIONS\nFlexi BTS FDD,
Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n\n1. Block/unblock the alarming module.\n\n2. 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 that does not
help, perform a power-off reset. \n\n3. If steps 1 and 2 do not help, replace the alarming module.\n\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n\n1. Reset the BTS.\n\n2. Perform a power-off reset.\n\n3. If steps 1 and 2 do not help,
replace the alarming module.\n\n\n\n\nFAULT NAME\nUnit not supported by current BTS SW version\n\nFAULT ID\n95:
Block or unblock the module that is causing the alarm.\n2. Replace the module that is causing the alarm.\n\n\n\n\nFAULT NAME\nUnit
unidentified\n\nFAULT ID\n1923: EFaultId_FrUnitUnidentified\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS
TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem still persists after performing step 1, replace the
RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the configuration. Download
the updated configuration if required.\n2. Reset the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. Replace the BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nUnknown HW resource\n\nFAULT ID\n94:
EFaultId_UnknownUnitType\n\nMEANING\nA unit cannot be identified by its product code or by its physical device address (object
ID).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nReplace the alarming unit or
module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nReplace the BTS or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nVSWR major alarm\n\nFAULT ID\n1837: EFaultId_VSWRMajorAl\n\nMEANING\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe 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 radio module requires.\n\nFlexi Zone Micro FDD, Flexi Zone Micro
TDD, Flexi Zone SFN Antenna:\nThe detected VSWR exceeds the predefined threshold. The antenna, antenna feed line, or both are
disconnected, mismatched, or damaged.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: \n1.
Check the antenna cables, connectors, antenna, and antenna line devices that can interfere with the RF signal. \n2. Check the antenna line
(TX-cable-antenna) impedance matching. \n\nNote: 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 means that the alarm is reported because of short or accidental peak of the
VSWR value. The alarm is cancelled if the condition is cleared at the radio or if fault 1957 is reported. \n\nFor 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 VSWR value
is not reflected in the alarm. To cancel the alarm, a radio reset or radio disconnection or power off is necessary. \n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD: \n1. Check the connection and integrity of antenna connectors, cable, and antenna. \n2. Reset the BTS device. If the
alarm persists, replace the BTS. \n\nFlexi Zone: \n1. Check the connection and integrity of the antenna connector, cable, and antenna. \n2.
Reset the Flexi Zone Access Point. If the alarm persists, replace the Flexi Zone Access Point. \n\nFlexi Zone SFN Antenna: \n1. Check the
the Flexi Zone SFN Antenna."
Table 38-25: CELL_NOTIFICATION

major
release
29/05/2020 Alarms

major
release
Name: CELL_NOTIFICATION (11529) Severity: indeterminate Release:

Type: qualityOfServiceAlarm Specific problem: CELL NOTIFICATION FL16A
Package: racfl.CELL_NOTIFICATION Implicitly cleared: true
Description: CELL NOTIFICATION\n\nA minor fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the
alarm.\n\nCheck the reason for the fault from the supplementary text field of the alarm.\n\nThe 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.\n\nDo
not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
source of the alarm and instructions fields of the corresponding alarms). \n\nBelow is the list of BTS fault(s) which may have caused this
support. \n\n-------------------------------------------------------------\n\nFAULT NAME\nAntenna Line Device failure\n\nFAULT ID\n3100:
EFaultId_AntennaLineFailure\n\nMEANING\nThe System Module, or the device itself, has detected an abnormal operation or a failure in the
antenna line device.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears.\n\n1. Check the
antenna line and antenna line devices. Ensure that the antenna line connectors are in the right torque.\n\n2. Block and unblock the alarming
RF module to reset it.\n\n3. Replace the faulty parts and/or devices along the antenna line.\n\n4. Replace the RF Module.\n\n\n\n\nFAULT
NAME\nAntenna Line Device Operation Failure\n\nFAULT ID\n1871: EFaultId_BusyAl\n1872: EFaultId_FormatErrorAl \n1873:
EFaultId_UnsupportedProcedureAl \n1874: EFaultId_OutOfRangeAl \n\nMEANING\nThe device is not working properly, the configuration is
not valid, or a given parameter is incorrect.\n\nINSTRUCTIONS\n1. Check the functionality of the antenna line device.\n\n2. Check the
compatibility between the antenna line device and the BTS.\n\n3. Check that the given parameters are in the valid range.\n\n\n\n\nFAULT
NAME\nAntenna line device SW download failure\n\nFAULT ID\n4047: EFaultId_FileCrcErrorAl\n4048:
EFaultId_FileContentErrorAl\n\nMEANING\nAn SW download to an antenna line device has failed because of an incorrect checksum or file
format.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\n1. Check the SW
package.\n2. Download the SW to the antenna line device again.\n\n\n\n\nFAULT NAME\nAntenna line failure\n\nFAULT ID\n1836:
other radios, the fault is canceled only when the RF module or the BTS is reset.\n\n\n\n\nFAULT NAME\nBaseband bus failure\n\nFAULT
does not clear the fault situation, replace the alarming System Module.\n\n\n\n\nFAULT NAME\nBTS internal SW management
problem\n\nFAULT ID\n3090: EFaultId_BtsInternalSwManagementProblem\n\nMEANING\nA software update to a module or sub-assembly
has failed, or a corrupted SW file has been detected in the FLASH.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order
until the BTS fault disappears:\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check the other active BTS
faults. If the ROM disk is corrupted, change the alarming module.\n2. Reset the RF Module and/or System Module (depending on the fault
source) by blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n5. Replace the alarming
module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. 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 Access Point.\n2. Reset the Flexi Zone Micro BTS or Flexi Zone
Access Point by blocking/unblocking it.\n3. Update and activate the SW to the BTS.\n4. Check the SW files.\n\nFlexi Zone:\n1. Check the
other active Flexi Zone Access Point faults. If the ROM disk is corrupted, change the Flexi Zone Access Point.\n2. Reset the Flexi Zone
Access Point to trigger new SW load.\n3. Check the SW files.\n\nFlexi Zone SFN Antenna:\n1. Check the other active Flexi Zone SFN
Antenna faults. If the ROM disk is corrupted, change the Flexi Zone SFN Antenna.\n2. Reset the Flexi Zone SFN Antenna to trigger new SW
load.\n3. Check the SW files.\n\n\n\n\nFAULT NAME\nBTS SW download or activation failed\n\nFAULT ID\n29:
EFaultId_FileCorruptionAl\n30: EFaultId_SwUpdateAl\n\nMEANING\nThe 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 system.\n\n\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Retry the SW update.\n2. If other flash memory-related faults are active for
the alarming module at the same time, replace the alarming module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone
Flexi Zone SFN Antenna at the same time, replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nConfiguration error: <x>\n\nFAULT
ID\n3070: EFaultId_ConfigurationError \n\nMEANING\nThere 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.\n\nINSTRUCTIONS\nNote: Perform the steps below in
the listed order until the BTS fault disappears:\n\n1. Check the installed HW/SW version compatibility and the HW compatibility with the
current BTS configuration.\n\n2. Check that the BTS cell parameters from the Network management system match\nthe BTS HW
configuration (for example, frequency, power).\n\n3. Check the Network management system alarms for the alarming local cell (LCR).\n\n4.
Recommission the BTS to ensure that all parameters are correctly configured.\n\n\n\n\nFAULT NAME\nCorrectable bit toggling
error\n\nFAULT ID\n6700: EFaultId_CorrectableBitTogglingError\n\nMEANING\nA correctable bit toggling error is detected in DSP
memory.\n\nINSTRUCTIONS\nThe fault doesn't require any special action because it was already autonomously corrected.\n\n\n\n\nFAULT
NAME\nCritical bit toggling error\n\nFAULT ID\n6701: EFaultId_CriticalBitTogglingError\n\nMEANING\nA non-correctable, bit-toggling error
has been detected in the critical DSP memory.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the fault
disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System/Baseband Module.\n2.
Replace the System/Baseband Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the
Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. If the fault persists, Replace the Flexi Zone Micro BTS or
Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nDC voltage administratively disabled\n\nFAULT ID\n4141:
29/05/2020 Alarms

major
release
EFaultId_DcVoltageAdministrativelyDisabledAl \n\nMEANING\nThe feeding voltage is disabled for the selected antenna
line.\n\nINSTRUCTIONS\nTo revert the changes, the DC voltage should be enabled for the reporting antenna line.\n\n\n\n\nFAULT
NAME\nFailure in replaceable baseband unit\n\nFAULT ID\n3003: EFaultId_FbiaFailureAl\n\nMEANING\nThe BTS has detected an abnormal
operation or a failure in the BTS replaceable\nbaseband unit.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the
BTS fault indication disappears:\n\n1. Check the other active BTS faults and act accordingly.\n2. Ensure that the plug-in type baseband unit is
installed correctly.\n3. Reset the alarming baseband unit.\n4. Replace the alarming baseband unit.\n\n\n\n\nFAULT NAME\nFile corrupted in
SW download\n\nFAULT ID\n28: EFaultId_SwPackageAl \n\nMEANING\nThe download is corrupted, or the software is
incompatible.\n\nINSTRUCTIONS\n1. Retry the SW update.\n2. Save the snapshot and check the download status from the BTS
SWDLreport in the snapshot file.\n\n\n\n\nFAULT NAME\nFR not critical functionality not supported or are not configured correctly.\n\nFAULT
ID\n4271: EFaultId_FrNotCriticalFunctionalityNotSupportedAl\n\nMEANING\nFR 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.\n\nINSTRUCTIONS\nCheck other active alarms.
\n\n\n\n\n\nFAULT NAME\nHigh memory consumption\n\nFAULT ID\n6502: EFaultId_HighMemoryConsumptionAl\n\nMEANING\nThe
physical memory supervision has detected that memory usage has exceeded 90% (FCT (HW rel.3), ASIA) or 98%
(FSP/ABIA).\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nSource: \n- FCT (HW rel.3)/AIA:
Perform eNB reset.\n- FSP/FBB/ABIA: Change the cell configuration to decrease call processing load.\n\nFlexi Zone Micro FDD, Flexi Zone
Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\nNone\n\n\n\n\nFAULT NAME\nIncoherency in cell configuration\n\nFAULT ID\n4044:
EFaultId_IncoherencyCellConfigurationAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe cell
configuration is not officially supported. Too many cells are assigned to the Tx group of the radio module.\n\nFlexi Zone Micro FDD, Flexi
Zone Micro TDD, Flexi Zone:\nThe cell configuration is not officially supported. The configured cell, which has antenna paths in the
resourceList antenna paths, does not map exclusively to one RMOD.\n\nINSTRUCTIONS\nCheck the configuration of the configured
cell.\n\n\n\n\nFAULT NAME\nIncompatible SW version detected\n\nFAULT ID\n23: EFaultId_IncompatibleSwVersionAl
modules with factory SW loaded, SW update is a mandatory step.\n\n\n\n\nFAULT NAME\nLink frame timing error\n\nFAULT ID\n1996:
EFaultId_LinkFrameTimingErrorAl\n\nMEANING\nThe 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 configuration, the clock circuitry for one, or both, of the System Modules
connected to this radio unit is not properly synchronized to its reference source.\n\nINSTRUCTIONS\n1. Check the clock reference sources
on all the System Modules connected to the radio.\n2. If the previous step does not help, reset the radio unit.\n3. If the previous steps do not
help, replace the radio unit.\n\n\n\n\nFAULT NAME\nMaximum number of 1xRTT neighbor relations per cell exceeded\n\nFAULT ID\n5500:
EFaultId_MaximumNumberOfRttNbRelsPerCellAl \n\nMEANING\nA 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 relations (LNRELX instances) per cell is already
reached. Neighbor relation information needs to be cleaned up manually by the operator through the plan file.\n\nINSTRUCTIONS\nThe
operator has to perform either of the following after receiving fault to recover the BTS to full operational state:\n1. Manually remove the
neighbor object below limit.\n2. Reconfigure or change manually threshold limit.\n\n\n\n\nFAULT NAME\nMaximum number of 1xRTT NR per
cell and carrier exceeded\n\nFAULT ID\n5501: EFaultId_MaximumNumberOfRttNbRelsPerCellAndCarrierAl \n\nMEANING\nA 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 configured per frequency object or the O&M configured maximum number of e1xCSFB target cells per frequency, it is not
provided for measurement by the UEs.\n\nINSTRUCTIONS\nThe operator should do either of the following after receiving the fault to recover
the BTS to full operational state:\n1. Remove manually neighbor object below limit.\n2. Reconfigure or manually change the threshold
limit.\n\n\n\n\nFAULT NAME\nMicro DTX configuration failure\n\nFAULT ID\n4308: EFaultId_MdtxConfigurationFailureAl\n\nMEANING\nThe
micro DTX configuration in a radio module has failed.\n\nINSTRUCTIONS\nIf the fault is raised during micro-DTX activation, deactivate the
mDTX, and\nthen activate it again by recommissioning.\nIf the fault is raised during micro-DTX deactivation, activate the mDTX, and\nthen
deactivate it again by recommissioning.\nIf the fault is not cleared because of repeated activation or deactivation of\nthe micro-DTX, a BTS
site reset clears the fault.\n\n\n\n\nFAULT NAME\nNeighbor cell ambiguity detected\n\nFAULT ID\n6274:
EFaultId_NeighborCellAmbiguityDetected\n\nMEANING\nA handover target cell cannot be uniquely selected because several candidates are
available for a certain PCI value and carrier frequency.\n\nINSTRUCTIONS\nAdd the LNREL object pointing to the correct neighbor to allow
the handover, or enable the UE-based ANR.\n\n\n\n\nFAULT NAME\nNot critical bit toggling error\n\nFAULT ID\n6702:
EFaultId_NotCriticalBitTogglingError\n\nMEANING\nA non-correctable bit toggling error is detected in the non-critical DSP memory
area.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System/Baseband
Module.\n2. Replace the System/Baseband Module.\nNote: Perform the steps below in the listed order until the fault disappears.\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the Flexi Zone Micro BTS or Flexi Zone Access
Point or Flexi Zone SFN\nAntenna.\n2. If the fault persists, replace the Flexi Zone Micro BTS or Flexi\nZone Access Point.\n\n\n\n\n\nFAULT
NAME\nOIC MCU Buffer Full\n\nFAULT ID\n2011: EFaultId_OIC_MCUBFullAl\n\nMEANING\nThe control message traffic between the
modules is malfunctioning.\n\nINSTRUCTIONS\nCheck the alarms for the connected module.\n\n\n\n\nFAULT NAME\nPCI confusion
detected\n\nFAULT ID\n6279: EFaultId_PciConfusionDetectedAl\n\nMEANING\nThis fault occurs when CGI measurements indicate that two
or more cells that operate on the same frequency use the same PCI.\n\nINSTRUCTIONS\n1. Check for E-UTRAN cells that operate on the
same frequency layer, and use the same PCI, and those that are in close vicinity.\n2. Re-assign PCIs for the discovered
cells.\n\n\n\n\nFAULT NAME\nPhich Power Boost not applied\n\nFAULT ID\n6112: EFaultId_PhichPowerBoostAl\n\nMEANING\nThe
configured PHICH transmission power boost cannot be applied either partly or entirely because of a lack of remaining power after considering
(boosted) cell-specific DL RS power, (boosted) PCFICH power, and minimum reserved power for PDCCH.\n\nINSTRUCTIONS\nThe Physical
HARQ Indication Channel (PHICH) transmission power boost can be increased by reducing the configured boosts for cell-specific downlink
reference signal and/or PCFICH.\n\n\n\n\nFAULT NAME\nPUCCH configuration inconsistency\n\nFAULT ID\n6295:
EFaultId_PucchConfigurationNotConsistentAl\n\nMEANING\nThe automatic PUCCH allocation configuration cannot support the operator
configuration.\n\nINSTRUCTIONS\nReduce the maximal number of active UEs to be supported by adjusting the parameters
\nmaxNumActUe, aPucchMinNumRrcNoDrb, aPucchAddAUeRrHo, aPucchAddAUeTcHo, \nand aPucchMinNumEmergencySessions if
emergency handling is active.\n\n\n\n\nFAULT NAME\nRadio memory consumption exceeds abnormal threshold\n\nFAULT ID\n4329:
EFaultId_RadioMemAboveAbnormalThresholdAl\n\nMEANING\nFree memory on the radio module is limited.\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nRecovery restart of the faulty radio module is highly recommended and
should be scheduled in the nearest suitable time (for example, during low traffic period).\n\n\n\n\nFAULT NAME\nRadio module access panel
open\n\nFAULT ID\n1991: EFaultId_FrAccessPanelOpenAl\n\nMEANING\nThe 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. \n\nINSTRUCTIONS\nCheck access door
and close if open.\n\n\n\n\nFAULT NAME\nRadio module internal communication failure\n\nFAULT ID\n1990:
EFaultId_FrInternalCommunicationFailureAl\n\nMEANING\nThe fault is reported in radio modules that consists of two separate hardware
units connected by optical cable. The near end Radio Module subunit cannot communicate with the far end subunit, possibly due to failed
CPRI link between the two subunits, or a failed far end subunit. \n\nINSTRUCTIONS\n1. Reset the alarming radio unit.\n2. If reset has not
canceled the fault condition, replace the alarming radio unit hardware.\n\n\n\n\n\nFAULT NAME\nRadio module internal hardware
configuration mismatch\n\nFAULT ID\n1992: EFaultId_FrInternalHwConfigurationMismatchAl\n\nMEANING\nThe fault is reported by complex
radio modules with multiple physical units where functionality is distributed. An incompatibility has been found between board
revisions.\n\nINSTRUCTIONS\n1. Reset the alarming radio unit.\n2. If a reset does not cancel the fault condition, replace one or both
subunits so that they are both of the same type.\n\n\n\n\nFAULT NAME\nRadio module low optical signal level to next hop\n\nFAULT
ID\n1995: EFaultId_FrLowOpticalSignalLevelToNextHopAl\n\nMEANING\nThe received optical signal on the link port is unexpectedly low
from the next hop (further from system module), though communication is still possible.\nThere is a poor CPRI link connection, bad CPRI
29/05/2020 Alarms

major
release
cable, or failing CPRI transceiver at the next radio module connected to the cable reported as fault source.\n\nINSTRUCTIONS\nNote:
Perform the steps in the listed order until the fault is resolved.\n1. 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 reported as the fault source.\n2. Reset the system
module or radio on the other end of the cable reported as fault source.\n3. Replace the SFP on the radio module port of the radio reporting
the fault.\n4. 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. \n5. Replace the optical cable reported as fault source.\n6. Replace the radio module reporting the fault, one with blinking red
LED display.\n7. 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 actions mentioned above have not cleared the fault situation, replace the extension baseband module (if the fault is
reported on the cable connected to the baseband module), the system module (if the fault is reported on the cable connected to the system
module), or the radio on the other end of the cable reported as fault source. \n\n\n\n\nFAULT NAME\nRadio module low optical signal level to
upper hop\n\nFAULT ID\n1994: EFaultId_FrLowOpticalSignalLevelToUpperHopAl\n\nMEANING\nThe received optical signal on the link port
is unexpectedly low from upper hop (toward the system module), though communication is still possible.\nThere 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
the fault source.\n\nINSTRUCTIONS\nNote: Perform the steps in the listed order until the fault is resolved.\n1. 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 the cable
reported as the fault source.\n2. Reset the system module or radio on the other end of the cable reported as the fault source. \n3. Replace
the SFP on the radio module port of the radio reporting the fault.\n4. 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. \n5. Replace the optical cable reported as fault source.\n6. Replace the
radio module reporting the fault (the one with blinking red LED display).\n7. 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 actions mentioned above have not cleared the fault
situation, replace the extension baseband module (if the fault is reported on the cable connected to the baseband module), the system
module (if the fault is reported on the cable connected to the system module), or the radio on the other end of the cable reported as fault
source. \n\n\n\n\nFAULT NAME\nReceive diversity expansion module communication failure\n\nFAULT ID\n1989:
EFaultId_FrReceiveDiversityExpansionModuleCommunicationFailureAl\n\nMEANING\nThe communication radio module with external
Receive Diversity Expansion Module (RDEM) is lost. The cable to the external RDEM module may be broken or disconnected, and external
module may have failed.\n\nINSTRUCTIONS\n1. Reset the alarming radio module.\n2. If it does not help, replace the cable between the
radio module and the Receive Diversity Expansion Module (RDEM).\n3. If previous steps have not cancelled alarm reported due to the fault,
replace the alarming radio module.\n\n\n\n\nFAULT NAME\nRF Module configuring failed\n\nFAULT ID\n1900:
Antenna:\nReplace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRRU power
loss\n\nFAULT ID\n1972: EFaultId_RruAcPowerLossAl\n\nMEANING\nThe RRU has lost its power supply.\n\nINSTRUCTIONS\n1. Check
the power connection to the RF module.\n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT
NAME\nSerial console activated\n\nFAULT ID\n4334: EFaultId_SerialConsoleActivatedAl\n\nMEANING\nSerial console is activated on
BTS.\n\nINSTRUCTIONS\nDisable the serial console (set U-boot variable console_uart to -1).\n\n\n\n\nFAULT NAME\nSystem information
broadcast parameters overflow\n\nFAULT ID\n6351: EFaultId_SystemInfoValueTagHandlingFailed\n\nMEANING\nThe System Information
Broadcast-related parameters have changed more than 32 times within three hours.\n\nINSTRUCTIONS\nThis fault does not require any
(special) actions.\n\n\n\n\nFAULT NAME\nSystem Module failure\n\nFAULT ID\n3000: EFaultId_SystemModuleFailure\n\nMEANING\nThe
BTS has detected an abnormal operation or a failure in the internal functionality of the System Module.\n\n\n\nINSTRUCTIONS\nNote:
Perform the steps below in the listed order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale
BTS TDD:\n1. Reset the System Module.\n2. Replace the System Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi
Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT ID\n3040:
Snapshot.\n\n\n\n\nFAULT NAME\nToo long fiber for mDTX activation\n\nFAULT ID\n4304:
EFaultId_TooLongFiberForMdtxAl\n\nMEANING\nThe cable used between the system module and the radio module exceeds the
maximum\nsupported length for micro DTX (the maximum supported link delay is 80 us; if the\nradio module is directly connected to the
system module or the extension baseband module, the longest supported cable length is approximately 16 km). The eNB power saving (that
is, the micro DTX functionality) can no longer be provided.\n\nINSTRUCTIONS\nReplace the cable with a shorter cable. If the radio module is
connected\ndirectly to the system module or the extension baseband module, the longest supported cable length for micro DTX is
approximately 16 km.\n\n\n\n\nFAULT NAME\nTransmission path failure\n\nFAULT ID\n4003:
EFaultId_TxFailureTurnMimoOffAl\n\nMEANING\nA 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 to the faulty TX. This fault is not reported in super cell
cases.\n\nINSTRUCTIONS\nSoftware and hardware reconfiguration can be made to the setup where the faulty TX is not used.\nCheck the
other active BTS faults and act accordingly.\n\n\n\n\nFAULT NAME\nUnit (module) temperature is high \n\nFAULT ID\n1936:
EFaultId_FrTempHigh\n\nMEANING\nThe validated RF module temperature is higher than or equal to the pre-defined maximum allowed
value.\n\nINSTRUCTIONS\n1. Check if the ambient temperature/environmental conditions are within the design limits of the radio module.
When the ambient temperature/environmental conditions are out of limits, the alarm is expected and no further actions are needed.\n\n2.
Check if the air flow is not blocked by some objects. Make sure the minimum thermal clearances are followed. Remove any objects that might
29/05/2020 Alarms

major
release
be blocking the air flow, and mount the module according to the instructions and recommendations.\n\n3. Check if excessive sunlight is
causing an overheat. Install sunshield, following the mounting instructions and recommendations.\n\n\n\n\nFAULT NAME\nUnit temperature
is high\n\nFAULT ID\n2: EFaultId_UnitOverheatAl \n\nMEANING\nThe temperature of a unit exceeds the threshold
value.\n\nINSTRUCTIONS\nCheck the active fan alarms and the air flow of the BTS.\n\n\n\n\nFAULT NAME\nU-plane overload
detected\n\nFAULT ID\n6053: EFaultId_UplaneOverloadDetectedTrThreeAl\n6120: EFaultId_UplaneOverloadDetectedTrOneAl\n6121:
EFaultId_UplaneOverloadDetectedTrTwoAl\n\nMEANING\nAn overload situation has been detected by the scheduler on the user plane.
Recovery actions are initiated to decrease the load level.\n\nINSTRUCTIONS\nThe system has automatic actions by decreasing the traffic or
the functionality on the traffic. No additional action is required from the operator.\n\n\n\n\nFAULT NAME\nVSWR major alarm\n\nFAULT
ID\n1837: EFaultId_VSWRMajorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe 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 radio module requires.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe detected VSWR
exceeds the predefined threshold. The antenna, antenna feed line, or both are disconnected, mismatched, or
damaged.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD: \n1. Check the antenna cables,
connectors, antenna, and antenna line devices that can interfere with the RF signal. \n2. Check the antenna line (TX-cable-antenna)
impedance matching. \n\nNote: 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 means that the alarm is reported because of short or accidental peak of the VSWR value. The
alarm is cancelled if the condition is cleared at the radio or if fault 1957 is reported. \n\nFor 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 VSWR value is not
reflected in the alarm. To cancel the alarm, a radio reset or radio disconnection or power off is necessary. \n\nFlexi Zone Micro FDD, Flexi
Zone Micro TDD: \n1. Check the connection and integrity of antenna connectors, cable, and antenna. \n2. Reset the BTS device. If the alarm
persists, replace the BTS. \n\nFlexi Zone: \n1. Check the connection and integrity of the antenna connector, cable, and antenna. \n2. Reset
the Flexi Zone Access Point. If the alarm persists, replace the Flexi Zone Access Point. \n\nFlexi Zone SFN Antenna: \n1. Check the
the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nVSWR minor alarm\n\nFAULT ID\n1838: EFaultId_VSWRMinorAl\n\nMEANING\nThe
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 Module.\n\nINSTRUCTIONS\n1. Check the antenna cables, connectors, antenna, and antenna line devices that might
cause interference with the RF signal. \n\n2. Check the antenna line (TX-cable-antenna) impedance matching. \n\nNote: 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
alarm is reported due to short/accidental peak of VSWR value. \nFor 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 will not be reflected in the alarm.
\n\n\n\n\nFAULT NAME\nWCDMA PSC confusion detected\n\nFAULT ID\n6281:
EFaultId_WcdmaPscConfusionDetectedAl\n\nMEANING\nThis fault occurs when CGI measurements indicate that two or more WCDMA
cells\nthat operate on the same carrier frequency use the same primary scrambling code (PSC).\n\nINSTRUCTIONS\n1. Check for UTRAN
(FDD) cells that operate on the same frequency layer and\nuse the same PSC, and that are in close vicinity.\n2. Reassign PSCs for the
discovered cells.
Table 38-26: CELL_OPERATION_DEGRADED

major
release
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\n\nA major fault (or faults) has occurred in a unit (or units) that belong to the sector indicated
in the alarm.\n\nCheck the reason for the fault from the supplementary text field of the alarm.\n\nThe 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.\n\nDo not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.
support. \n\n------------------------------------------------------------\n\nFAULT NAME\n10b8b coding error in optical interface device\n\nFAULT
ID\n2004: EFaultId_OIC_LVDSRecAl\n\nMEANING\nThe fiber cable is experiencing interference; data transmission is faulty.\n\nA physical
connection failure between the optical interface and the summing function has occurred.\n\nThe 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
module.\n\n\nINSTRUCTIONS\nNote: Perform the steps in the listed order until the fault is resolved.\n\n1. Reset the radio module behind the
cable reported as the fault source by blocking/unblocking it. \n2. Reset the system module. \n3. Replace the SFP on the radio module port
where the cable reported as fault source is terminated.\n4. Replace the SFP on the system module or extension baseband module port
where the cable reported as fault source is terminated.\n5. Replace the optical cable reported as fault source.\n6. Replace the radio module
behind the cable reported as fault source.\n7. 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, replace the extension baseband module (if the fault is reported on the cable
connected to the baseband module) or the system module (if the fault is reported on the cable connected to the system
module).\n\n\n\n\nFAULT NAME\n3GPP/AISG communication administratively disabled\n\nFAULT ID\n4142:
EFaultId_Communication3gppAdministrativelyDisabledAl\n\nMEANING\nThe HDLC link has been disabled for the reporting Antenna Line or
IUANT port.\n\nINSTRUCTIONS\nEnable the parameter "Communication3gppEnabled" for the reporting Antenna Line to revert
changes.\n\n\n\n\nFAULT NAME\nAbnormal CPRI interface to next hop <OptIf ID>\n\nFAULT ID\n1974:
29/05/2020 Alarms

major
release
module).\n\n\n\n\nFAULT NAME\nAbnormal CPRI interface to upper hop <OptIf ID>\n\nFAULT ID\n1965:
EFaultId_AbnormalCpriInterfaceToUpperHopAl\n\nMEANING\nThe optical interface does not work properly. CPRI transmission to the upper
hop does not work properly.\n\nINSTRUCTIONS\nExecute the following steps in the ordered sequence. If any of the step does not help,
execute the next one:\n\n1. Reset the radio module behind the cable reported as the fault source. \n2. Reset the system module. \n3.
Replace the SFP on the radio module port where the cable reported as the fault source is terminated.\n4. Replace the SFP on the system
module or the extension baseband module port where the cable reported as the fault source is terminated.\n5. Replace the optical cable
reported as the fault source.\n6. Replace the radio module behind the cable reported as the fault source.\n7. 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 the baseband
module) or the system module (if the fault is reported on the cable connected to the system module).\n\n\n\n\nFAULT NAME\nAbnormal
reception on SFP to next hop <OptIf ID>\n\nFAULT ID\n1973: EFaultId_AbnormalReceptionOnSfpToNextHopAl\n\nMEANING\nThe optical
interface is not working properly.\nThis fault is valid only for radio modules in a chain configuration.\nNote: The Optif is from the perspective of
the previous radio.\n\nINSTRUCTIONS\n1. 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. \n2. Reset the RF module. \n3. If that does not help, block or unblock the site. \n4. If that does
not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nAbnormal reception on SFP to upper hop <OptIf
ID>\n\nFAULT ID\n1971: EFaultId_AbnormalReceptionOnSfpToUpperHopAl\n\nMEANING\nThe 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
configuration.\n\nINSTRUCTIONS\n1. Check the cables between the system module and the RF module. \n2. Reset the RF module. \n3. If
those do not help, block and unblock the site. \n4. If those do not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT
NAME\nAddress mismatch in summing\n\nFAULT ID\n2019: EFaultId_Muksu_SsubMmAl\n\nMEANING\nThere is a baseband bus address
mismatch in the summing. There are two possible causes:\n\n1. A configuration error (two different baseband units functioning) - after an
acknowledgement, the fault returns.\n\n2. Data corruption on the bus - appears once when an unsynchronized data is sent by the
baseband.\n\nINSTRUCTIONS\nCheck the antenna mapping to the local cells in the commissioning file.\n\n\n\n\nFAULT NAME\nAntenna
line device configuration failure\n\nFAULT ID\n1888: EFaultId_AlConfigurationFailureAl\n\nMEANING\nAntenna Line Device is not properly
configured.\nAntenna Line Device set-up fails, for example due to protocol error or interoperability problem.\n\nINSTRUCTIONS\n1.
Check/correct the antenna line configuration.\n\n2. If that does not help, replace the antenna line device.\n\n\n\n\nFAULT NAME\nAntenna
Line Device failure\n\nFAULT ID\n3100: EFaultId_AntennaLineFailure\n\nMEANING\nThe System Module, or the device itself, has detected
an abnormal operation or a failure in the antenna line device.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the
BTS fault disappears.\n\n1. Check the antenna line and antenna line devices. Ensure that the antenna line connectors are in the right
torque.\n\n2. Block and unblock the alarming RF module to reset it.\n\n3. Replace the faulty parts and/or devices along the antenna
line.\n\n4. Replace the RF Module.\n\n\n\n\nFAULT NAME\nAntenna line device HW failure\n\nFAULT ID\n1847:
EFaultId_HardwareErrorAl\n\nMEANING\nA hardware failure has been reported by ALD (RET, MHA).\n\nINSTRUCTIONS\n1. Reset the
radio module to give a power-off reset to the antenna line devices.\n2. If step 1 does not help, replace the antenna line
device.\n\n\n\n\nFAULT NAME\nAntenna line device missing software\n\nFAULT ID\n1848: EFaultId_WorkingSoftwareMissingAl
\n\nMEANING\nThe unit is in download mode state. This fault is returned when an unsupported procedure occurs in download
mode.\n\nINSTRUCTIONS\n1. Upload the correct SW to the device (if possible) or perform an ALD power reset (for example, by RF module
reset).\n2. If that does not help, replace the antenna line device.\n\n\n\n\nFAULT NAME\nAntenna line device operation failure\n\nFAULT
ID\n4239: EFaultId_AldOperationFailureAl\n\nMEANING\nThe radio module indicated an error upon execution of remote electrical tilt (RET)-
related logical operation.\n\nINSTRUCTIONS\n1. Check the antenna line and RET devices. Fix or replace the faulty parts or devices.\n2. To
cancel the alarm, perform an RF module startup or BTS reset.\n\n\n\n\nFAULT NAME\nAntenna line failure\n\nFAULT ID\n1836:
other radios, the fault is canceled only when the RF module or the BTS is reset.\n\n\n\n\nFAULT NAME\nAntenna line faulty \n\nFAULT
ID\n4045: EFaultId_AntennaLineFaultyAl\n\nMEANING\nAn alarm message has been received from the antenna line. The antenna line is
faulty.\n\nINSTRUCTIONS\nThe following instructions should be performed on the master RAT side:\n\n1. Check the antenna line and
antenna line device that causes the alarm.\n2. Fix or replace the faulty parts or devices.\n3. Perform a radio module reset (only the master
RAT in sharing mode can request for such an operation to be performed).\n\n\n\n\nFAULT NAME\nAntenna line operation
degraded\n\nFAULT ID\n4046: EFaultId_AntennaLineDegradedAl\n\nMEANING\nAn alarm message has been received from the antenna
line device. The antenna line operation is degraded.\n\nINSTRUCTIONS\nPerform the following steps on the MasterRAT side:\n\n1. Check
the antenna line and antenna line device that is causing the alarm.\n2. Fix or replace the faulty parts and devices.\n\n\n\n\nFAULT
NAME\nAntenna line switched off due to high VSWR\n\nFAULT ID\n1957: EFaultId_AntennaLineSwitchedOffAl\n\nMEANING\nTx in the RF
module has been switched off to protect the radio module hardware, which might be damaged because of high-reflection (VSWR)
conditions.\n\nINSTRUCTIONS\n1. The VSWR measured at the RF (transmitter) exceeds values that are acceptable by the RF module.\n2.
Check the impedance matching of the Antenna Line System (replace elements that cause mismatch).\n3. To check if the above-mentioned
steps have solved the problem, reset the RF module.\n\n*Forcing the RF HW to work under such conditions might result in permanent
damage to the RF HW.\n\n\n\n\nFAULT NAME\nAntenna periodic calibration has failed\n\nFAULT ID\n1988:
EFaultId_CalibrationPeriodicFailureAl\n\nMEANING\nAntenna periodic calibration result does not meet the requirements for amplitude and/or
phase error.\n\nINSTRUCTIONS\nNo action is required when this fault is reported.\n\n\n\n\nFAULT NAME\nBaseband bus configuration of
<x> was rejected\n\nFAULT ID\n1811: EFaultId_BbBus_ConfFailedAl\n\nMEANING\nThe baseband-bus-related configuration of <x> has
been rejected by the HW SW, DSP, or RF SW.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
that causes the alarm (system module or FBBx/ABIx).\n\n\n\n\nFAULT NAME\nBeamforming calibration failure in RF data path\n\nFAULT
ID\n6051: EFaultId_PhyRxBfCalibrationDetectContinuousExceptionAl\n\nMEANING\nSome 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 that processes data
29/05/2020 Alarms

major
release
transmitted (TX) by BTS or received (RX) by BTS.\n\nINSTRUCTIONS\nTo 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 practice), if such information is
available.\n\nBased on the alarm's diagnostic info, one can try the following instructions\nto recover from the fault:\n1. 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
vendors. If so, check whether the synchronization between networks are correctly configured.\n2. 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 the vendor files among
different LTE TDD eNB software releases.\n3. Check whether the GPS or other synchronization sources (for example, synchronization
servers) for this cell are working as expected.\n4. Check whether the cell is set up under the sharing of RFM with TD-SCDMA.\nIf so, check
whether the carrier configurations in TD-SCDMA and TD-LTE are not in conflict.\n5. Check the RP3 links state, especially for the SFP as well
as the fibers connecting the RFMs and the BBUs inside the eNB.\n6. Block and unblock the cell.\n7. Reset the BTS. \n8. Examine the
antenna cable connection between the RFM and the antenna element.\n9. Exchange the cable connection between the antenna and the
RFM to check whether the RRU port or the cable is faulty.\n10. Replace the hardware(RRU/BBU).\n\n\n\n\nFAULT NAME\nBTS file
error\n\nFAULT ID\n1802: EFaultId_FileRequestFlashAl\n\nMEANING\nA software download to FSP, DSP, ABIx or FR has
failed.\n\nINSTRUCTIONS\nNote: Perform the following steps in the listed order until the fault disappears:\n\n1. Use BTS Site Manager to
perform a full commissioning to the BTS using the NetAct backup upload SCF file as template.\n\n2. Download two different software
packages so that the faulty file is removed from the BTS.\n\n3. Download the software again.\n\n4. Replace the System
Module.\n\n\n\n\nFAULT NAME\nBTS internal SW management problem\n\nFAULT ID\n3090:
files.\n\n\n\n\nFAULT NAME\nBTS reset required\n\nFAULT ID\n4001: EFaultId_BtsResetNeededAl\n\nMEANING\nThis 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 trigger an autonomous reset on its own.\n\n1. The BTS has detected a commissioned (configured in SCF) extension
baseband\nmodule (for example, FBBC) that was not detected during BTS startup. Thus, the BTS must be reset to take the module into
use.\n\n2. 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.\nNote: LCR supported by the FSP is reported as the fault source in this case.\n\n3. 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.\n\n4. An internal
problem has been detected, and the BTS cannot continue start-up\nwithout a BTS reset.\n\n5. 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 to an SFP
that does not support the configured speed), and a BTS reset might be needed to solve the problem.\nNote: The affected LCR is reported as
the fault source in this case.\n\n6. 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 module (configured in SCF) or optical cable. The BTS must be reset to set
the cell up with the use of the detected radio module or cable. LCR is the fault source in this case. \n\n7. 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
example, FBBA. The BTS must be reset to take the module into use.\n\n8. 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.\n\n9. The BTS has cleared an alarm and triggers an
autonomous BTS reset to enable\nnormal BTS operability, but the BTS reset counter has been exceeded. The operator must perform a BTS
reset to enable BTS operability.\n\n10. 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 the operator might solve this issue.\n\n11. FDD only - Phase synchronization
source was not available in BTS start-up,\nand alarm with fault 4153 was raised. Phase synchronization source is available now. BTS reset is
needed to activate features requiring network-level synchronization (OTDOA, eICIC, MBMS, inter-eNB Carrier Aggregation).\n\n12. BTS
cannot execute FSP or BTS autonomous recovery reset because of either of the following reasons:\n- It will disable any working cell \n- An
internal BTS limitation\n\n13. FSP card is lost or disconnected. A BTS reset is necessary to protect the BTS from a crash after the card hot
insert.\n\n14. FSP autonomous recovery reset has failed. A BTS reset is necessary to try to recover the FSP.\n\n15. FSMr3 only - CRAN
configuration for a cell has failed. A BTS reset is necessary to reconfigure CRAN.\nNote: The affected LCR is reported as the fault source in
this case.\n\n16. 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 case.\n\n17. FSP power on failed after fault 4077 (FSP overheated) is canceled. A BTS reset is needed to
try to take the FSP into use.\n\n18. 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-in and take new RF module resources into use.\n\nOnly case #10 is
applicable for FZM.\n\nINSTRUCTIONS\n1. Check the alarm diagnostic information for the reason of the fault report before the reset.\n\n2.
Reset (block and unblock) the BTS.\n\n\n\n\n\n\n\nFAULT NAME\nBTS SW download or activation failed\n\nFAULT ID\n29:
EFaultId_FileCorruptionAl\n30: EFaultId_SwUpdateAl\n\nMEANING\nThe 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 system.\n\n\n\nINSTRUCTIONS\nFlexi BTS
FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Retry the SW update.\n2. If other flash memory-related faults are active for
the alarming module at the same time, replace the alarming module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone
Flexi Zone SFN Antenna at the same time, replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nBuffer over/underflow in clock
crossing logic\n\nFAULT ID\n2054: EFaultId_MuksuRxClkErrorAl\n\nMEANING\nThe 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 a clock drift between the received signal
and the internal clock, or the RX rate setting is wrong.\n\nINSTRUCTIONS\n1. Check the status of the module behind the faulty link (power
on, and so on).\n\n2. Check the alarming fiber connection.\n\n\n\n\nFAULT NAME\nCalibration initialization failure\n\nFAULT ID\n4067:
EFaultId_CalibrationInitAl\n\nMEANING\nBeamforming calibration configuration has failed.\n\nINSTRUCTIONS\nNote: Perform the steps
below in the order listed until the fault disappears:\n\n1. Reset the RF module.\n2. Replace the RF module.\n\n\n\n\nFAULT NAME\nCell
power failure\n\nFAULT ID\n4090: EFaultId_TxCarrierInputPowerLowAl\n\nMEANING\nThe Flexi Radio Module has detected low downlink
carrier input power from the System Module.\n\nINSTRUCTIONS\n1. Check the other active alarms and act accordingly.\n2. If that does not
help, block/unblock the system module.\n3. a. FSMr2: If that does not help, replace the system module.\nb. FSMr3: If the faulty cell is on the
baseband extension module, replace the extension module.\n\n\n\n\nFAULT NAME\nCommunication failure\n\nFAULT ID\n1806:
NAME\nConfiguration error: <x>\n\nFAULT ID\n3070: EFaultId_ConfigurationError \n\nMEANING\nThere is a compatibility problem in the
29/05/2020 Alarms

major
release
BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch in the BTS
configuration.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault disappears:\n\n1. Check the installed
HW/SW version compatibility and the HW compatibility with the current BTS configuration.\n\n2. Check that the BTS cell parameters from the
Network management system match\nthe BTS HW configuration (for example, frequency, power).\n\n3. Check the Network management
system alarms for the alarming local cell (LCR).\n\n4. Recommission the BTS to ensure that all parameters are correctly
configured.\n\n\n\n\nFAULT NAME\nConfiguration file corrupted\n\nFAULT ID\n1924:
EFaultId_FrConfigurationFileCorrupted\n\nMEANING\nThe RF Module SW has detected conflicting or corrupted configuration
data.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If problem
is still observed after performing step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\n1. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n2. If that does not help, replace the
Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nConnection Unstable At 3Gbps
\n\nFAULT ID\n4310: EFaultId_ConnectionUnstableAt3Gbps\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nPerform the
recovery in the following sequence:\n1. Check if the optical transmission network connecting the system module with the radio module, or the
extension baseband module (FBBx) and the radio module, supports 6 Gbps transmission.\n2. 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 firmly to the
modules.\n3. Replace the cable.\n4. Change the radio module where the unstable link is terminated.\n5. If this does not help, replace the
FBBx if the unstable link is terminated\non FBBx.\n6. If this does not help, replace the FCT (system module).\n\nIf an alarm with fault 4038
(Radio master conflict) is reported at the same time,\nfollow the instructions of fault 4038 because in some cases fault 4038 might be the root
cause of fault 4310.\n\n\n\n\nFAULT NAME\nConnection Unstable At 6Gbps\n\nFAULT ID\n4309:
might\nbe the root cause of fault 4309.\n\n\n\n\nFAULT NAME\nDC voltage administratively disabled\n\nFAULT ID\n4141:
EFaultId_DcVoltageAdministrativelyDisabledAl \n\nMEANING\nThe feeding voltage is disabled for the selected antenna
line.\n\nINSTRUCTIONS\nTo revert the changes, the DC voltage should be enabled for the reporting antenna line.\n\n\n\n\nFAULT
NAME\nDistributed site support not enabled\n\nFAULT ID\n4076: EFaultId_DistributedSiteSupportNotEnabledAl\n\nMEANING\nA long
distance (high latency) between the FSM and antenna has been detected but the Distributed Site feature has not been enabled
(actDistributedSite = False). For FHCC modules, this fault means that there is a long distance between the FSM and the customer's
device.\n\nINSTRUCTIONS\nPerform the steps below in the listed order until the fault disappears:\n1. Either enable the actDistributedSite
parameter or switch to a shorter fiber between the FSM or ABIx and the FR.\n2. Restart the System module.\n\n\n\n\nFAULT NAME\nDSP
loading failure\n\nFAULT ID\n1962: EFaultId_RruDspLoadingFailure\n\nMEANING\nDSP loading has failed.\n\nINSTRUCTIONS\n1. Reset
the RF module.\n \n2. If that does not help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nFailure in optical
interface\n\nFAULT ID\n3030: EFaultId_FailureInOptical_Rp3Interface\n\nMEANING\nThe AirScale/Flexi BTS (System Module) has detected
an abnormal operation or a failure\nin an optical RP3 interface between two modules . \nThe failure cannot be attributed to a specific module
but there are several\npossible fault sources, for example, fiber optical cable, SFP, or individual module.\n\nINSTRUCTIONS\n1. PROBLEM
document.\n\n\n\n\nFAULT NAME\nFailure In Optical Interface <optIf ID>\n\nFAULT ID\n3012:
EFaultId_FailureInOpticalInterface\n\nMEANING\nThe optical interface is not working properly.\nThe SFP (Small Form-factor Pluggable)
module might be missing, faulty, or mismatched.\n\nINSTRUCTIONS\n1. Check the cables between the System Module and RF Module.
\n\n2. Reset the RF Module. \n\n3. If that does not help, reset the site. \n\n4. If that does not help, replace the RF module that is generating
the alarm.\n\n\n\n\nFAULT NAME\nFailure in replaceable baseband unit\n\nFAULT ID\n3003: EFaultId_FbiaFailureAl\n\nMEANING\nThe
unit.\n\n\n\n\nFAULT NAME\nFiber delay and antenna round trip delay exceeded\n\nFAULT ID\n4256:
EFaultId_MaximumDelayExceededAl\n\nMEANING\nFiber Delay and Antenna Round Trip Delay exceeds the supported capability of the
BTS.\n\nINSTRUCTIONS\n1. Confirm if the existing applied configuration is within the configured FR hardware capabilities. \n2. Reduce the
length of the fiber cable to a length that is supported by the BTS and FR combination.\n\n\n\n\nFAULT NAME\nFilter tuning failure\n\nFAULT
ID\n1840: EFaultId_TuningFailureAl\n\nMEANING\nThe Radio Module is unable to tune to a required sub-band properly (tuning\nfailure), or
another major failure has been detected by the Radio Module\n(unit faulty).\n\nINSTRUCTIONS\nReplace the alarming Radio
Module/MultiRadio Combiner.\n\n\n\n\nFAULT NAME\nFilter unit faulty\n\nFAULT ID\n1841: EFaultId_UnitFaultyAl\n\nMEANING\nThe radio
module has detected an internal filter failure.\n\nINSTRUCTIONS\n1. Reset the radio module.\n2. If resetting the radio module does not help,
replace the alarming radio module.\n\n\n\n\nFAULT NAME\nFlash operation failure\n\nFAULT ID\n214: EFaultId_FlashWrAl\n215:
EFaultId_FlashRdAl\n\nMEANING\nA flash memory operation failure. If this fault continuously appears, the flash chip might be
broken.\n\nINSTRUCTIONS\n1. Check the other active alarms. If the ROM disk is corrupted, change the alarming\nmodule.\n\n2. Reset the
alarming module. There are no recovery actions, therefore\nreset can be tried once. If that does not help, replace the
alarming\nmodule.\n\n\n\n\n\nFAULT NAME\nFPGA R/W error\n\nFAULT ID\n1963: EFaultId_FpgaRwErrorAl\n\nMEANING\nAn error has
occurred during a read/write attempt on the FPGA.\n\nINSTRUCTIONS\n1. Reset the RF Module. \n2. If that does not help, replace the
alarming RF Module.\n\n\n\n\nFAULT NAME\nFPGA SW update failed\n\nFAULT ID\n1928:
EFaultId_FrFpgaSwUpdateFailed\n\nMEANING\nThe FPGA software update in the RF module has failed.\n\nINSTRUCTIONS\n1. Reset the
RF HW unit.\n2. If problem is still observed after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nFrame clock
missing\n\nFAULT ID\n1903: EFaultId_FrFrameClockMissing\n\nMEANING\nThe System Module clock reference differs from the RF Module
29/05/2020 Alarms

major
release
check other active alarms to determine the root cause.\n\n\n\n\nFAULT NAME\nHigh interference to UL special subframe\n\nFAULT
ID\n6118: EFaultId_HighInterferenceToUlSpecialSubframeAl\n\nMEANING\nThe Received Interference Power (RIP) value per Physical
Resource Block (PRB)\nof the cell for UpPTS symbols exceeds the predefined threshold for at least the operator-configured
alarmThresholdCrossingTime.\n\nINSTRUCTIONS\nPerform network optimization.\n\n\n\n\nFAULT NAME\nHigh interference to UL
subframe\n\nFAULT ID\n6117: EFaultId_HighInterferenceToUlSubframeAl\n\nMEANING\nThe received interference power (RIP) value per
physical resource block (PRB) of the cell for UL subframes exceeds the predefined threshold for at least the operator-configured
alarmThresholdCrossingTime. \n\nINSTRUCTIONS\nPerform network optimization.\n\n\n\n\nFAULT NAME\nIncompatible SW version
detected\n\nFAULT ID\n23: EFaultId_IncompatibleSwVersionAl \n\nMEANING\nIncompatible software has been
detected.\n\nINSTRUCTIONS\nUpdate 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 by NetAct.\n\nIn case of RF modules with factory SW loaded, SW update is a
mandatory step.\n\n\n\n\nFAULT NAME\nIncreased BER detected on the optical connection to Radio Module\n\nFAULT ID\n1955:
EFaultId_IncrBerOnRp3\n\nMEANING\nIncreased bit error rate has been detected on the optical link to the radio module, which results in
sporadic LCV errors in downlink baseband processing.\n\nINSTRUCTIONS\nInstructions are divided into three sections. Choose the
appropriate section and perform the corresponding steps:\n\nSection A: Check on the system module side:\n1. Check if the connector seal is
properly mounted and is firmly in place. \n2. 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 the connection/mounting.\n3. Check if the LED indicates that the SFP is
faulty (connected to system module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly connected/mounted in the
SFP.\n5. Clean the optical connectors that are connected to the SFP. Reset the RF hardware unit and check if this solves the
problem.\n\nSection B: Check on the radio module side:\n1. Check if the connector seal is properly mounted and is firmly in place.\n2. 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 connection/mounting.\n3. Check if the optical cable is properly connected/mounted in the SFP.\n4. Clean the optical connectors
at the RF module end. Reset the RF hardware unit and check if this solves the problem.\n\nSection C: Check the optical connection:\n1.
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 can detach or damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation)
from the system module end. Check measuring equipment documentation for instructions.\n3. OPTIONAL: Test the fiber cable (for example,
measure the optical attenuation) from the RF module end. Check measuring equipment documentation for instructions.\n\nIf the alarm
continues after executing steps from sections A,B, and C, replace\nthe RF module.\n\n\n\n\nFAULT NAME\nLatency of the link for inter-site
CA permanently exceeds threshold\n\nFAULT ID\n6297: EFaultId_LongLastingLinkLatencyOverTheLimitAl\n\nMEANING\nThe link between
eNBs or Flexi Zone Access Points, carrying the time critical for inter-site Carrier Aggregation data, permanently exceeds the maximum
allowed limit.\n\nINSTRUCTIONS\nReduce the latency of the network connection between the two eNBs or Flexi Zone Access Points to fulfill
the requirements for CA.\n\n\n\n\nFAULT NAME\nLNA in bypass mode\n\nFAULT ID\n4270:
EFaultId_MhaBypassModeAl\n\nMEANING\nThe 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 at the same time.\n\nINSTRUCTIONS\nIf LNA is shared
between two BTSs and it supports separate AISG ports\nfor each BTS, check if the LNA is not switched to bypass mode by other
BTSs.\n\n\n\n\n\nFAULT NAME\nLow noise amplifier failure\n\nFAULT ID\n1839: EFaultId_LNAFailureAl\n\nMEANING\nThe Radio Module
has detected a malfunction of an internal LNA unit.\n\nINSTRUCTIONS\nReplace the alarming Radio Module.\n\n\n\n\nFAULT NAME\nMast
Head Amplifier fault\n\nFAULT ID\n3120: EFaultId_MastHeadAmplifierFault\n\nMEANING\nThe FlexiBTS/AirScaleBTS has detected an
abnormal operation, or a failure, in the Masthead Amplifier (MHA).\n\nNote that the Tower Mounted Amplifier (TMA) is synonymous to the
MHA, and is used by the Antenna Interface Standards Group (AISG).\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order
until the BTS fault disappears.\n\n1. Check the cables related to the Masthead Amplifier (MHA).\n\n2. Block and unblock the RF Module to
which the MHA is connected to reset the alarming MHA module.\n\n3. Replace the faulty devices.\n\n\n\n\nFAULT NAME\nMast Head
Amplifier fault above current window, <line>\n\nFAULT ID\n1834: EFaultId_AboveCurrentWindowAl\n\nMEANING\nThe Masthead Amplifier
(MHA) does not work properly. However, the system cannot determine the impact on the RX signal level.\n\nINSTRUCTIONS\n1. Check the
antenna cables and connectors toward the MHA. Fix or replace the broken parts. \n2. Restart the MHA by resetting the Flexi Radio (FR)
Module.\n\nNot: 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.\n\n\n\n\nFAULT NAME\nMast Head Amplifier fault below current window, <line>\n\nFAULT ID\n1835:
EFaultId_BelowCurrentWindowAl \n\nMEANING\nThe 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 path, and therefore the received RF signal level is decreased.\nTo
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 recalculation for all Antenna Lines that use LNAs of the MHA that is not being provided enough power so that all required gain
is provided by the LNA in the Radio Module.\n\nINSTRUCTIONS\n1. Check the antenna cables and connectors toward the MHA. Fix or
replace the broken parts.\n2. Restart the MHA by resetting the Flexi Radio (FR) Module. \n\nNote: 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.\n\n\n\n\nFAULT NAME\nMessage
routing problem in receiver (RX)\n\nFAULT ID\n2058: EFaultId_MuksuMsgRoutingFailedAl\n\nMEANING\nAn interrupt is generated if a
message does not get routed.\n\nThis is considered normal when DSPs are starting up and RP3 sync is done.\n\nINSTRUCTIONS\nIf OptIf
is the source:\n\n1. Check the antenna mapping to the local cells in the commissioning file.\n2. Depending which optical interface is notified
as faulty check the cables between \n - the System Module and RF Module, or the cable between the FBB module and the RF Module (Flexi
BTS FDD/TDD),\n - the cable between the ABIx module and the RF Module (AirScale BTS FDD/TDD).\n3. Block and unblock the RF
Module.\n4. Perform a BTS reset. \n5. Replace the RF module behind the optical link.\n\nFlexi BTS FDD/TDD:\nIf FSP is the source:\n1.
Perform a System Module reset.\n2. If that does not help, replace the System Module.\n\nFlexi BTS FDD/TDD, AirScale BTS FDD/TDD:\nIf
FBB/ABIx is the source:\n1. Perform a System Module reset.\n2. If that does not help, replace the FBB/ABIx card.\n\n\n\n\nFAULT
NAME\nMHA operation degraded\n\nFAULT ID\n1869: EFaultId_MinorTMAFaultAl\n\nMEANING\nA fault in the Masthead Amplifier (MHA) is
detected. MHA functionality is degraded. The real impact cannot be determined.\n\nINSTRUCTIONS\nReset the MHA (using Radio Module
reset). If this does not help, replace the alarming module.\n\n\n\n\nFAULT NAME\nMHA operation failure\n\nFAULT ID\n1870:
EFaultId_MajorTMAFaultAl\n\nMEANING\nA fault in the Masthead Amplifier (MHA) has been detected. The MHA is not
working.\n\nINSTRUCTIONS\n1. Reset the MHA by using radio module reset.\n\n2. If this does not solve the problem, replace the alarming
module.\n\n\n\n\nFAULT NAME\nMismatched RRU optical module <optif ID>\n\nFAULT ID\n1969:
EFaultId_MismatchedSfpAl\n\nMEANING\nThe small form-factor pluggable (SFP) module is mismatched.\n\nINSTRUCTIONS\nReplace the
faulty SFP.\n\n\n\n\nFAULT NAME\nModule Clock faulty\n\nFAULT ID\n1926: EFaultId_FrModuleClockFaulty\n\nMEANING\nThe RF module
29/05/2020 Alarms

major
release
has lost lock to the incoming clock.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS
TDD:\nInstructions 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 effort. \n\nSection A: Check on the system module side:\n1. Check if the connector seal is properly mounted
and firmly in place. \n2. 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, readjust the connection or mounting.\n3. Check if the LED indicates the faulty SFP (connected to
System Module). Replace the SFP if it is faulty.\n4. Check if the optical cable is properly connected or mounted in the SFP.\n5. Clean the
optical connectors that are connected to the SFP. Reset the RF HW unit and check if this solves the problem.\n\nSection B: Check on the
radio module side:\n1. Check if the connector seal is properly mounted and firmly in place.\n2. 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 connection or
mounting.\n3. Check if the optical cable is properly connected or mounted in the SFP.\n4. Clean the optical connectors at the FR module end.
Reset the FR HW unit and check if this solves the problem.\n\nSection C: Check the optical connection:\n1. 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 can detach or
damage the connectors. \n2. OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the System Module's end.
Check the documentation of the measuring equipment for instruction details.\n3. 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 instruction details.\n\nIf the alarm
continues after executing the steps from sections A, B, and C, replace the FR module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi
Zone, Flexi Zone SFN Antenna:\nReplace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nNo connection to unit\n\nFAULT ID\n10: EFaultId_NoConnectionToUnitAl \n\nMEANING\nThe connection to a module that belongs to
the BTS configuration has been lost.\n\nIn case of SNMP radios, there is a problem with the optical interface or an internal fault, which results
in a radio reset.\n\nINSTRUCTIONS\n1. 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.\n\n2. Check the fault history.\n\n\n\n\nFAULT NAME\nNo feedback signal\n\nFAULT
ID\n1920: EFaultId_FrNoFeedBackSignal \n\nMEANING\nThe feedback signal to predistortion is too weak or missing. The TX performance is
degraded.\n\nINSTRUCTIONS\n1. Reset the RF HW unit.\n2. If problem is still observed after performing step 1, replace the RF HW
unit.\n\n\n\n\nFAULT NAME\nNot able to synchronize baseband bus with <x>\n\nFAULT ID\n1815:
Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nOperation on shared optical port failed\n\nFAULT ID\n4180:
EFaultId_OperationOnSharedOpticalPortFailedAl\n\nMEANING\nThe shared OptIF mode cannot be read from or changed in the FBBC
card.\n\nINSTRUCTIONS\nFault 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 can decide whether to change the FBBC card or not.\n\n\n\n\nFAULT NAME\nOptical interface
data/control/ethernet buffer full\n\nFAULT ID\n2006: EFaultId_OIC_DBRxFullAl\n2010: EFaultId_OIC_EBFullAl\n\nMEANING\nThe RP3 or
Ethernet buffering is not working, and the buffer becomes full. The\noptical device is malfunctioning. The fault might be generated because of
synchronization problems or incorrect initialization.\nFault 2006 may be detected in Flexi BTS TDD only.\nFault 2010 may be detected both in
Flexi BTS FDD and TDD.\n\nINSTRUCTIONS\n1. Exchange the alarming and working links, and check where the alarm is
reported\nnow.\n\n2. If the alarming link remains the same, replace the System Module.\n\n3. If the alarming link changes, replace the
module behind that link.\n\n\n\n\nFAULT NAME\nOptical Interface faulty\n\nFAULT ID\n2000: EFaultId_OIC_TxAl\n2001:
EFaultId_OIC_PresAl\n\nMEANING\nA 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 (fault 2001). The SFP is a part of the fiber cable package.\n\nINSTRUCTIONS\n1.
Check that the small form-factor pluggable (SFP) is properly connected to the System Module.\n\n2. Replace the SFP
module.\n\n\n\n\nFAULT NAME\nOverload collision in transmitter\n\nFAULT ID\n2061:
EFaultId_MuksuOverloadCollisionAl\n\nMEANING\nThe transmitter has detected more data coming from a summing than the current link
rate can support.\n\nINSTRUCTIONS\n1. Block and unblock the BTS. \n\n2. Check the baseband bus configuration related to the RP3 link
speeds.\n\n\n\n\nFAULT NAME\nParallel optical link length mismatch\n\nFAULT ID\n4072: EFaultId_ParallelLinkDifferenceTooLargeAl
\n\nMEANING\n- 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 RRU). The main link is considered as a reference and the secondary link is compared to the main
link. \n- 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 module-shared RF is too large.\n\nThe additional info in the alarm about difference in length should
be delivered in the alarm only when LTE is radio master.\n\nThe information consists of: \n- The number of physical port on the system
module where primary link starts.\n- The number of physical port on the system module where secondary too long/too short link starts.\n- The
difference in lengths with information if secondary link is too short or too long.\n- The difference in delays in
nanoseconds.\n\nINSTRUCTIONS\nIf the fault is detected in non-sharing configuration:\n1. 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.\n2. 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 60
meters in OBSAI RRU, or 146 meters in CPRI RRU. \n\nIf the fault is triggered because of an incorrect RF sharing configuration, check that
the RF sharing feature is enabled on synchronization master system module.\n\nIf the alarm with fault 4038 (Radio master conflict) is
reported at the same time,\nfollow the instruction for fault 4038 because in some cases, 4038 may be the root cause of fault
4072.\n\n\n\n\nFAULT NAME\nPeriodic CAM Report Inconsistency\n\nFAULT ID\n6817:
EFaultId_CamReportInconsistency\n\nMEANING\nThe 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 discarded because it is outside of the expected range is not considered
as a missing report.\n\nINSTRUCTIONS\nIf the issue persists, perform the steps below in the listed order until the fault disappears.\n1.
Block/unblock the impacted cell.\n2. Reset the Flexi Zone Micro BTS or Access Point.\n3. Replace the Flexi Zone Micro BTS or Access
Point.\n\n\n\n\nFAULT NAME\nPipe dangerously overheating \n\nFAULT ID\n1938: EFaultId_FrPipeOverheat\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\n1. Check if the ambient temperature or environmental conditions are within the design limits of the radio module.
When the ambient temperature or environmental conditions are out of limits, the alarm is expected and no further actions are needed.\n\n2.
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 flow, and mount the module according to the instructions and recommendations.\n\n3. Check if excessive sunlight is causing
an overheat. Install sunshield following the mounting instructions and recommendations.\n\n\n\n\nFAULT NAME\nPost test failed\n\nFAULT
ID\n1925: EFaultId_FrPostTestFailed\n\nMEANING\nAn RF module's power-on self-test has failed at start-up.\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after performing
step 1, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRadio memory consumption exceeds critical
threshold\n\nFAULT ID\n4330: EFaultId_RadioMemAboveCriticalThresholdAl\n\nMEANING\nThe radio module has no free
memory.\n\nINSTRUCTIONS\nRecovery restart of the faulty radio module is highly recommended and should be done as soon as
possible.\n\n\n\n\nFAULT NAME\nRadio module internal hardware assignment indeterminate\n\nFAULT ID\n1993:
EFaultId_FrInternalHwAssignmentIndeterminateAl\n\nMEANING\nThe fault is reported by complex radio modules with multiple physical units
where functionality is distributed. An incompatibility has been found with the identification method.\n\nINSTRUCTIONS\n1. Reset the
alarming radio unit.\n2. 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 have a user alarm cable or nothing at all), and ensure that the Secondary subunit has an
29/05/2020 Alarms

major
release
Alarm Cap on the ASIG ALM connector. The secondary radio is the one that serves antenna ports 3 and 4.\n\n\n\n\nFAULT
NAME\nReceiving failure in Optical Interface\n\nFAULT ID\n2002: EFaultId_OIC_RxAl\n\nMEANING\nThe incoming optical signal to the
Small Form-Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached.\n\nThe 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
broken.\n\nINSTRUCTIONS\n1. Check the status of the module behind the faulty link (power on, and so on).\n\n2. 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
faulty SFP. Replace the SFP if it is faulty.\n\n3. Clean the connectors, test the fiber cable, and replace it if it is faulty.\n\n4. If the previous
steps do not help, replace the module behind the faulty link.\n\n\n\n\nFAULT NAME\nRET Antenna control failure\n\nFAULT ID\n1842:
EFaultId_MotorJamAl\n1843: EFaultId_ActuatorJamAl\n1844: EFaultId_NotCalibratedAl\n1845: EFaultId_NotConfiguredAl\n1846:
EFaultId_ActuatorInterferenceAl\n\nMEANING\n1845: TILT is not configured.\nOthers: Antenna tilting is not possible or might function
incorrectly.\n\nINSTRUCTIONS\nPerform RET calibration. If that does not help, replace the RET unit.\nIn case of 1845: send a valid
configuration file to the alarming device.\n\n\n\n\nFAULT NAME\nRF BB bus configuration error\n\nFAULT ID\n1905:
EFaultId_FrRfBbBusConfigError\n\nMEANING\nThe RF Module baseband bus was configured incorrectly.\n\nINSTRUCTIONS\n1. Confirm if
the existing applied configuration is within the configured RF\nHW capabilities.\n2. Check BTS connections and commissioning settings.\n3.
Block or unblock the BTS.\n4. If HW configuration is confirmed, then this problem is caused by eNB\nSW. Check other active
alarms.\n\n\n\n\nFAULT NAME\nRF BB bus connection transmission error\n\nFAULT ID\n1906:
EFaultId_FrRfBbBusConnTransError\n\nMEANING\nThere is an error in the baseband or optical bus.\n\nINSTRUCTIONS\nInstructions 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.\n\nSection A: Check on the system module side:\n1. Check if the connector seal is properly mounted and firmly in place. \n2.
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 connection/mounting.\n3. Check if the LED indicates the faulty SFP (connected to System Module). Replace the SFP if it
is faulty.\n4. Check if the optical cable is properly connected/mounted in the SFP.\n5. Clean the optical connectors that are connected to the
problem.\n\nSection C: Check the optical connection:\n1. 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 damage the connectors.\n2. OPTIONAL: Test the fiber cable (for
example, measure the optical attenuation) from the System Module end. Check the measuring equipment documentation for instructions.\n3.
OPTIONAL: Test the fiber cable (for example, measure the optical attenuation) from the RF Module end. Check the measuring equipment
module.\n\n\n\n\nFAULT NAME\nRF BB bus synchronization error\n\nFAULT ID\n1904: EFaultId_FrRfBbBusSynchError \n\nMEANING\nThe
baseband bus between the System Module and RF Module is out of synchronization.\n\nINSTRUCTIONS\nInstructions 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.
\n\nSection A: Check on the system module side:\n1. Check if the connector seal is properly mounted and firmly in place. \n2. 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 connection/mounting.\n3. Check if the LED indicates the faulty SFP (connected to System Module). Replace the SFP if it is
faulty.\n4. Check if the optical cable is properly connected/mounted in the SFP.\n5. Clean the optical connectors that are connected to the
problem.\n\nSection C: Check the optical connection:\n1. 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 the connectors. \n2. OPTIONAL: Test the fiber cable (for example,
measure the optical attenuation) from the System Module end. Check the measuring equipment documentation for instructions.\n3.
OPTIONAL: Test the fiber cable (for example measure the optical attenuation) from the RF Module end. Check the measuring equipment
module.\n\n\n\n\nFAULT NAME\nRF data setup failure\n\nFAULT ID\n1997: EFaultId_RfSetupFaultAl\n\nMEANING\nA 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 with
this fault is automatically canceled once the autonomous recovery actions are completed.\n\nINSTRUCTIONS\n1. In a CPRI-A RF sharing
configuration, the CDMA BTS performs the needed recovery actions for this fault.\n2. If the fault does not clear within 20 minutes, then reset
the radio.\n\n\n\n\nFAULT NAME\nRF Module blocked\n\nFAULT ID\n1931: EFaultId_FrBlocked\n\nMEANING\nThis 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 fault means that FR is blocked. When a LTE FSM/ASIA plays the role of the master, or a LTE system module shares CPRI/Ir radio
module with a SCDMA system module (dual mode configuration), and FR is blocked, fault 48:EFaultId_UnitBlockedAl is detected, not
1931.\n\nINSTRUCTIONS\nNo action is needed.\n\n\n\n\nFAULT NAME\nRF Module configuring failed\n\nFAULT ID\n1900:
Antenna:\nReplace the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module
critical file not found\n\nFAULT ID\n1901: EFaultId_FrCriticalFileNotFound\n\nMEANING\nA critical configuration file is missing from the RF
Module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Verify if the HWP1 file is present
in the FR module. Download the file if it is missing. Reset the FR module.\n2. If the file is present, block/unblock the RF HW unit.\n3. If the
problem continues after performing step 2, replace the FR HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1. Block/unblock the
BTS.\n2. Replace the Flexi Zone Micro BTS.\n\nFlexi Zone:\n1. Reset Flexi Zone Access Point.\n2. Replace the Flexi Zone Access
Point.\n\nFlexi Zone SFN Antenna:\n1. Reset Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT
NAME\nRF Module failure\n\nFAULT ID\n3010: EFaultId_RfModuleFailure\n\nMEANING\nThe BTS has detected an abnormal operation or a
failure in the internal functionality of the RF Module.\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed order until the BTS fault
disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem still
persists after step 1 has been performed, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone
SFN Antenna:\n1. Check the other active Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna faults and act
accordingly.\n2. Reset the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. If that does not help, replace the
faulty Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module faulty primary optical
link\n\nFAULT ID\n1984: EFaultId_FrPrimaryLinkLossAl\n\nMEANING\nThe radio unit has detected a failure on its optical connection to the
system module or an upstream radio unit (chaining case).\n\nINSTRUCTIONS\n1. 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.\n2. Clean the connectors, test the fiber cable,
and replace them if they are faulty.\n3. If the previous steps do not help, replace the alarming radio unit hardware.\n\n\n\n\nFAULT
29/05/2020 Alarms

major
release
NAME\nRF Module file not found\n\nFAULT ID\n1902: EFaultId_FrFileNotFound\n\nMEANING\nThe RF Module SW has detected that a non-
critical configuration file is missing.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Check
that the TEMP and CALI files are present. Upload any missing files. Reset the RF Module.\n2. If the files are present, reset the FR HW
unit.\n3. If the problem is still observed after performing step 1, replace the FR HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1.
Block and/or unblock BTS.\n2. Replace the Flexi Zone Micro BTS.\n\nFlexi Zone:\n1. Reset the Flexi Zone Access Point.\n2. Replace the
Flexi Zone Access Point.\n\nFlexi Zone SFN Antenna:\n1. Reset the Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF Module filter input power missing\n\nFAULT ID\n1910:
EFaultId_FrFilterInputPowerMissing\n\nMEANING\nThe RF Module filter has measured TX power that is too low.\n\nINSTRUCTIONS\n1.
Reset the RF HW unit.\n2. If problem is still observed after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nRF Module
gain adjusting failure\n\nFAULT ID\n1908: EFaultId_FrGainAdjust\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\nThe TX output power adjustment has failed.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN
Antenna:\nCLGC convergence has failed. Gain target cannot be achieved.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale
BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem is still observed after performing step 1, replace the RF HW
unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the configuration. \n2. Reset the Flexi
Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna. \n3. If that does not help, replace the Flexi Zone Micro BTS, Flexi
Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module out of order\n\nFAULT ID\n1912:
EFaultId_FrOutOfOrder\n\nMEANING\nThe RF module is out of order because of a software or hardware fault.\n\nINSTRUCTIONS\nFlexi
BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after step 1 has
been performed, replace the RF HW unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace
the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRF Module power input faulty
\n\nFAULT ID\n1959: EFaultId_FrPowerInputFaultAl\n\nMEANING\nInput 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.\n\nINSTRUCTIONS\n1. Check the power supply to the
affected radio module.\n2. If the alarm persists, replace the radio module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRF Module
power supply output faulty\n\nFAULT ID\n1918: EFaultId_FrPowerOutputFault\n\nMEANING\nThe power supply supervision has detected an
overvoltage, undervoltage, or overcurrent in the RF module.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD,
AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after performing step 1, replace the RF HW unit.\n\nFlexi Zone
Micro FDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Replace the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN
Antenna.\n\n\n\n\nFAULT NAME\nRF module unauthorized\n\nFAULT ID\n4278: EFaultId_RfModuleUnauthorizedAl\n\nMEANING\nRFM
product authorization has failed because of missing RFM properties. RFM\nis not supported by the current BTS software release and the
BTS did not find\nrelevant 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.\n\nINSTRUCTIONS\n1. Make sure that the corresponding RFM plug-in module has been
installed on the network server in NMS (NetAct SW Archive).\n\n2. Update the corresponding RFM plug-in software module in the BTS/eNB
from NetAct. \n\n3. Supply the RFM plug-in software module to BTS/eNB locally via BTS Site Manager if NetAct connection is not available.
\n\n4. Block/unblock the BTS.\n\nNote: You need to commission the radio module before it can be taken into use. \n\n\n\n\nFAULT
NAME\nRF Power decreased \n\nFAULT ID\n1927: EFaultId_FrPowerDecreased\n\nMEANING\nThe highest temperature exceeds the
power decrease limit in the RF module.\n\nINSTRUCTIONS\n1. Check if the ambient temperature or environmental conditions are within the
design limits for the radio module. When the ambient temperature or environmental conditions are out of limits, the alarm is expected and no
further actions are needed.\n\n2. 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, and mount the module according to instructions and recommendations.\n\n3. Check if
excessive sunlight is causing an overheat. Install sunshield following mounting instructions and recommendations.\n\n\n\n\nFAULT
NAME\nRF RX AGC issues\n\nFAULT ID\n1977: EFaultId_RfRxAgcIssueAl\n\nMEANING\nThe 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 large for the Flexi Zone
Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna; or there might be a fault in the Flexi Zone Micro BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.\n\nINSTRUCTIONS\n1. Check for the possible installation issues and co-located interference.\n\n2. Reset
the Flexi Zone Micro BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n3. If that does not help, replace the Flexi Zone Micro
BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nRRU CPU and DSP link failure\n\nFAULT ID\n1961:
DspLinkFailureAl\n\nMEANING\nThe CPU cannot connect to the DSP.\n\nINSTRUCTIONS\n1. Reset the RF Module.\n2. If that does not
help, replace the RF module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRRU DPD self test failure\n\nFAULT ID\n1960:
EFaultId_DpdTestFailureAl\n\nMEANING\nThe RRU digital pre-distortion (DPD) has failed during self test.\n\nINSTRUCTIONS\n1. Reset the
RF Module. \n2. If that does not help, replace the RF Module that is generating the alarm.\n\n\n\n\nFAULT NAME\nRTWP level below
threshold\n\nFAULT ID\n4333: EFaultId_RtwpLevelBelowThresholdAl\n\nMEANING\nThe measured received total wideband power (RTWP)
is below the threshold.\n\nINSTRUCTIONS\nThe 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 failure of any unit on the path between the Rx antenna line port on
the radio module or MHA and the DSP. Execute the following actions in the presented sequence to recover from the fault:\n1. Reset the
alarming radio unit.\n2. If the first step is completed and the fault is reported again, reset the BTS (block or unblock the BTS).\n3. If the
previous step is completed and the fault is reported again: \n a. If the alarming Rx antenna has an MHA commissioned, then check that the
MHA is actually connected to it.\n b. If the alarming Rx antenna has an MHA connected, then check that the actual MHA gain matches the
commissioned MHA gain. \n c. Check that the actual Antenna Total Loss matches the commissioned Total Loss. \n d. Check that the actual
Antenna Additional Rx Gain matches the commissioned Additional Rx Gain. \n4. 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 module to the system module or extension
baseband module.\n5. If the previous steps have been completed and the fault is reported again, replace the MHA connected to the affected
Rx antenna.\n6. If the previous steps have been completed and the fault is reported again, replace the alarming radio module hardware.\n7. If
the previous steps have been completed and the fault is reported again, replace the system module hardware or extension baseband module
hardware (depending on where the alarming radio module is connected).\n\n\n\n\nFAULT NAME\nRX out of order\n\nFAULT ID\n1911:
EFaultId_FrRxOutOfOrder\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe RX RF synthesizer
of the RF module is not locked.\nFor SNMP interface:\nThe received power is low for the RRH.\nFor CPRI-A interface:\nThe RX path in the
FR module is faulty.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe RX path in the FR module is
faulty.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after resetting the RF
HW unit, replace the RF HW unit.\n3. In case of SNMP radio, the only way to clear the fault is to reset the radio or replace the unit.\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset the HW unit.\n2. If the problem continues after
resetting the HW unit, replace the HW unit.\n\n\n\n\nFAULT NAME\nSevere SFP performance aggravation <optIf ID>\n\nFAULT ID\n1966:
EFaultId_SevereSfpPerformanceAggravationAl\n\nMEANING\nThe optical interface is not working properly; performance aggravation is
high.\n\nINSTRUCTIONS\n1. Check the cables between the System Module or ABIA and RF Module. \n\n2. Reset the RF Module. \n\n3. If
those do not help, block and unblock the site. \n\n4. If those do not help, replace the RF module that is causing the alarm.\n\n\n\n\nFAULT
NAME\nSevere SFP reception power aggravation <optIf ID>\n\nFAULT ID\n1967:
alarm.\n\n\n\n\nFAULT NAME\nSFP Failure <optIf ID>\n\nFAULT ID\n1948: EFaultId_AbnormalOpticalSfpOfIrInterfaceAl\n\nMEANING\nThe
optical interface is not working properly.\nThe small form-factor pluggable (SFP) module might be missing or
faulty.\n\nINSTRUCTIONS\nReplace the faulty SFP.\n\n\n\n\nFAULT NAME\nSFP missing <OptIf ID>\n\nFAULT ID\n1964:
EFaultId_SfpMissingAl\n\nMEANING\nThe optical interface is not working properly. The Small Form-factor Pluggable (SFP) module might be
29/05/2020 Alarms

major
release
missing, or it might be faulty.\n\nINSTRUCTIONS\nReplace the faulty SFP.\n\n\n\n\nFAULT NAME\nSFP on RF Module faulty or
unsupported\n\nFAULT ID\n1986: EFaultId_SfpOnRadioModuleFaultyOrUnsupportedAl\n\nMEANING\nThe SFP on the radio unit is either
faulty or not supported.\n\nINSTRUCTIONS\n1. 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.\n2. Reset the affected radio unit.\n\n\n\n\nFAULT NAME\nShared radio not
synchronized to Radio Master\n\nFAULT ID\n4253: EFaultId_SharedRadioNotSyncToMasterAl\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nPerform following actions until the problem is solved:\n1. Check the optical connection between the radio master
system module and the shared radio.\n2. Check the alarms in the radio master system module and act accordingly. \n3. Reset the radio
master system module.\n\n\n\n\n\nFAULT NAME\nSumming not enabled for message type\n\nFAULT ID\n2059:
EFaultId_MuksuSummingNotEnabledAl\n\nMEANING\nSumming 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.\n\nINSTRUCTIONS\n1. Block and unblock the BTS.\n\n2.
Check the logs for line code violation (LCV) errors related to optical links. \n\n3. Verify Small Form-factor Pluggable (SFP) transceiver and
fiber conditions. \n\n\n\n\nFAULT NAME\nSW corrupted\n\nFAULT ID\n1850: EFaultId_SwCorruptedAl\n\nMEANING\nA corrupted SW file in
the FLASH has been detected.\nThe unit cannot complete start-up.\n\nINSTRUCTIONS\nUpdate the SW to the BTS.\n\n\n\n\nFAULT
NAME\nSystem Module failure\n\nFAULT ID\n3000: EFaultId_SystemModuleFailure\n\nMEANING\nThe BTS has detected an abnormal
operation or a failure in the internal functionality of the System Module.\n\n\n\nINSTRUCTIONS\nNote: Perform the steps below in the listed
order until the BTS fault disappears.\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the System
Module.\n2. Replace the System Module.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Reset
the Flexi Zone Micro BTS or Flexi Zone Access Point or Flexi Zone SFN Antenna.\n2. Replace the Flexi Zone Micro BTS or Flexi Zone
Access Point or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTemperature alarm\n\nFAULT ID\n3040:
Snapshot.\n\n\n\n\nFAULT NAME\nToo long optical cable between system module and radio module\n\nFAULT ID\n4277:
EFaultId_OpticalCableFsmRfModuleTooLongAl\n\nMEANING\nThe length of the optical cable between the system module and the radio
module is too long. \n\nINSTRUCTIONS\nReduce 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 modules to remove the delay introduced by the previous radio
modules.\n\n\n\n\n\nFAULT NAME\nTransmission quality deteriorated\n\nFAULT ID\n1921:
EFaultId_FrTransmissionQualityDetoriated\n\nMEANING\nThe TX signal adjustment has failed.\n\nINSTRUCTIONS\n1. Reset the RF HW
unit.\n2. If the problem still persists after performing step 1, replace the RF HW unit.\n\n\n\n\nFAULT NAME\nTransmission rule collision in
Muksu\n\nFAULT ID\n2060: EFaultId_MuksuTransmissionRuleCollisionAI\n\nMEANING\nThe transmitter has detected an RP3 message
from a summing coincident with a transmission rule.\n\nINSTRUCTIONS\n1. Block and unblock the BTS. \n\n2. Check the
configuration.\n\n\n\n\nFAULT NAME\nTuning frequency out of range\n\nFAULT ID\n4043:
EFaultId_TuningFrequencyOutOfRangeAl\n\nMEANING\nThe Radio Module has detected that the requested frequency does not fit the
capabilities offered by Radio Module.\n\nINSTRUCTIONS\nRe-configure the frequency settings in a proper way with respect to the
capabilities of the Radio Module.\n\n\n\n\nFAULT NAME\nTX input overdrive\n\nFAULT ID\n1985:
EFaultId_FrTxInputOverdriveAl\n\nMEANING\nHardware 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 operational but with degraded performance.\n\nINSTRUCTIONS\n1.
Confirm if the existing applied configuration is within the configured FR HW capabilities.\n2. Check the BTS connections and commissioning
settings.\n3. Restart the radio unit.\n4. If the fault condition persists after the radio restart, restart the BTS.\n5. If the HW configuration is
confirmed, then this problem is caused by the eNB SW. Check other active alarms.\n\n\n\n\nFAULT NAME\nTX out of order\n\nFAULT
ID\n1907: EFaultId_FrTxOutOfOrder\n\nMEANING\nThe RF module's TX path cannot be used.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem continues after step 1 has been performed,
replace the RF HW unit.\n3. In case of SNMP radio, the only way to clear the fault is to reset the radio or replace the unit.\n\nFlexi Zone Micro
FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the connection and integrity of the antenna connector, cable,
and antenna.\n2. 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.\n3. Reset the BTS device. If the alarm persists, replace the Flexi Zone Micro BTS or Flexi Zone Access Point
or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nTX output overdrive\n\nFAULT ID\n1983:
EFaultId_FrTxOutputOverdriveAl\n\nMEANING\nHardware 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 circuitry.\n\nINSTRUCTIONS\n1. 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 the
instructions for handling those alarms.\n2. Reset the alarming radio unit.\n3. If previous steps have not canceled the fault condition, replace
the alarming radio unit hardware.\n\n\n\n\nFAULT NAME\nUnit (module) dangerously overheating \n\nFAULT ID\n1937:
EFaultId_FrDangerouslyOverheat\n\nMEANING\nThe validated RF sensor temperature is greater than or equal to the pre-defined value in
the unit property file.\n\nINSTRUCTIONS\n1. Check if the ambient temperature/environmental conditions are within the design limits of the
radio module. When the ambient temperature/environmental conditions are out of limits, the alarm is expected and no further actions are
needed.\n\n2. 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 flow, and mount the module according to the instructions and recommendations.\n\n3. Check if
excessive sunlight is causing an overheat. Install sunshield, following the mounting instructions and recommendations.\n\n\n\n\nFAULT
NAME\nUnit blocked\n\nFAULT ID\n48: EFaultId_UnitBlockedAl\n\nMEANING\nA module is blocked with the BTS Site Manager. \nThe
purpose is to avoid fault indications that might be raised during the module maintenance task.\nThe 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 module with an
SCDMA system module (dual mode configuration). In other cases, that is, when a WCDMA system module is the master agent for the
blocked shared (WCDMA/LTE) radio module, fault:1931 is raised.\n\nINSTRUCTIONS\nUnblock the module with the BTS Site
Manager.\n\n\n\n\nFAULT NAME\nUnit not supported by current BTS SW version\n\nFAULT ID\n95:
29/05/2020 Alarms

major
release
use.\n\nINSTRUCTIONS\n1. Upgrade the system module SW.\n2. Replace the unit.\n\n\n\n\n\nFAULT NAME\nUnit unidentified\n\nFAULT
ID\n1923: EFaultId_FrUnitUnidentified\n\nMEANING\nThe 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.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS
FDD, AirScale BTS TDD:\n1. Reset the RF HW unit.\n2. If the problem still persists after performing step 1, replace the RF HW unit.\n\nFlexi
Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone, Flexi Zone SFN Antenna:\n1. Check the configuration. Download the updated
configuration if required.\n2. Reset the BTS, Flexi Zone Access Point, or Flexi Zone SFN Antenna.\n3. Replace the BTS, Flexi Zone Access
Point, or Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nVSWR major alarm\n\nFAULT ID\n1837:
EFaultId_VSWRMajorAl\n\nMEANING\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nThe 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 radio
module requires.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone SFN Antenna:\nThe detected VSWR exceeds the predefined
threshold. The antenna, antenna feed line, or both are disconnected, mismatched, or damaged.\n\nINSTRUCTIONS\nFlexi BTS FDD, Flexi
BTS TDD, AirScale BTS FDD, AirScale BTS TDD: \n1. Check the antenna cables, connectors, antenna, and antenna line devices that can
interfere with the RF signal. \n2. Check the antenna line (TX-cable-antenna) impedance matching. \n\nNote: 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 means that the
alarm is reported because of short or accidental peak of the VSWR value. The alarm is cancelled if the condition is cleared at the radio or if
fault 1957 is reported. \n\nFor 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 VSWR value is not reflected in the alarm. To cancel the alarm, a radio reset or radio
disconnection or power off is necessary. \n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD: \n1. Check the connection and integrity of antenna
connectors, cable, and antenna. \n2. Reset the BTS device. If the alarm persists, replace the BTS. \n\nFlexi Zone: \n1. Check the connection
and integrity of the antenna connector, cable, and antenna. \n2. Reset the Flexi Zone Access Point. If the alarm persists, replace the Flexi
Zone Access Point. \n\nFlexi Zone SFN Antenna: \n1. Check the connection and integrity of the antenna connector, cable, and antenna. \n2.
Reset the Flexi Zone SFN Antenna. If the alarm persists, replace the Flexi Zone SFN Antenna.\n\n\n\n\nFAULT NAME\nVSWR minor
alarm\n\nFAULT ID\n1838: EFaultId_VSWRMinorAl\n\nMEANING\nThe 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 Module.\n\nINSTRUCTIONS\n1. Check the
antenna cables, connectors, antenna, and antenna line devices that might cause interference with the RF signal. \n\n2. Check the antenna
line (TX-cable-antenna) impedance matching. \n\nNote: 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 alarm is reported due to short/accidental peak of VSWR value. \nFor
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 will not be reflected in the alarm."
Table 38-27: ClientDelegateServerStatus

major
release
Name: ClientDelegateServerStatus (731) Severity: critical Release:

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 38-28: CmuManagementFailed

major
release
Name: CmuManagementFailed (10040) Severity: major Release:

Package: lte.CmuManagementFailed Implicitly cleared: true
Raised on class: lte.CompactMobilityUnit Default probable cause: ftpFailed
Description: The alarm is raised when SAM fails to manage a 9430 Compact Mobility Unit due to an FTP failure.
Raising condition: ('Management State' EQUAL 'FTP Failed')
Clearing condition: ('Management State' EQUAL 'Managed')
Remedial action: Verify FTP connectivity between the 5620 SAM and the 9430 Compact Mobility Unit, then re-attempt to manage.
29/05/2020 Alarms
Table 38-29: ContainingEquipmentAdministrativelyDown

major
release
Name: ContainingEquipmentAdministrativelyDown (466) Severity: minor Release:

Type: equipmentAlarm Specific problem: Not Applicable FL16A
Package: Implicitly cleared: true
equipment.ContainingEquipmentAdministrativelyDown Default probable cause:
Raised on class: equipment.Port 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 38-30: ContainingEquipmentMismatch

major
release
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 38-31: ContainingEquipmentOperationallyDown

major
release
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 38-32: CorruptImageFile

major
release
29/05/2020 Alarms

major
release
Name: CorruptImageFile (171) Severity: critical Release:

Package: mediation.CorruptImageFile Implicitly cleared: true
Raised on class: mediation.AbstractSoftwareFolderDescriptor Default probable cause: invalidOrCorruptImageFile
Description: The alarm is raised when one or more files in the 5620 SAM software image specified for a device software upgrade is invalid,
corrupt or absent. The 5620 SAM validates a device software file set before it imports the file set and distributes it to an NE. Ensure that the
file set downloads properly to the NE and is not tampered with before you re-attempt the upgrade. The alarm clears when a valid file set is on
the NE and the 5620 SAM activates the software image in the file set.
Raising condition: ('isImageValid' EQUAL 'false')
Clearing condition: ('isImageValid' EQUAL 'true')
Remedial action: The existing SW image in the SAM database should be replaced with an image that is known to be complete and valid.
Table 38-33: CRL_Update_failure

major
release
Name: CRL_Update_failure (11531) Severity: indeterminate Release:

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

major
release
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 38-35: EquipmentAdministrativelyDown

major
release
29/05/2020 Alarms

major
release
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 38-36: EquipmentDown

major
release
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 38-37: EquipmentInTest

major
release
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 38-38: EquipmentMismatch

major
release
Name: EquipmentMismatch (9) Severity: major Release:

Package: equipment.EquipmentMismatch Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: equipmentTypeMismatch
29/05/2020 Alarms

major
release
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 38-39: EquipmentRemoved

major
release
Name: EquipmentRemoved (8) Severity: major Release:

Package: equipment.EquipmentRemoved Implicitly cleared: true
Raised on class: equipment.Equipment Default probable cause: replaceableEquipmentRemoved
Description: The alarm is raised when the compositeEquipmentState attribute has a value of equipmentMissing.
Raising condition: ((('isEquipped' EQUAL 'false') OR ('compositeEquipmentState' EQUAL 'Removed')) AND ('isEquipmentInserted' EQUAL
'true'))
Clearing condition: (('compositeEquipmentState' NOT EQUAL 'Removed') AND ('isEquipped' EQUAL 'true'))
Remedial action: Informational - this alarm is raised when a card is removed.
Table 38-40: Ethernet_OAM_CCM_fault

major
release
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\n\nThe 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:\n\nThe following alarms
are defined:\n\n1. 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.\nExample: CCM fault level - prio 5 cause MDL_MISMATCH\nNote: For
MDL_MISMATCH cases, it might not be possible to display the local MDL where the fault was detected.\n\n2. 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.\nExample: CCM fault level 5 prio 5 cause MAID_MISMATCH\n\n3. 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.\nExample: CCM
fault level 5 prio 5 cause MAID_MISMATCH\n\n4. 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.\nExample: CCM fault level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED\n\n5.
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.\nEx: CCM fault level 5 prio 4 cause WRONG_CCM_INTERVAL \n\n6. REMOTE_CCM, priority 3: A
CCM was not received for 3.5 intervals from at least one remote MEP in the MA.\nEx: CCM fault level 5 prio 3 cause
REMOTE_CCM_DEFECT \n\n7. RDI_CCM, priority 1 (lowest priority): An RDI flag is detected in the CCM frames from one remote
peer.\nExample: CCM fault level 5 prio 1 cause REMOTE_DEFECT_INDICATION\n\nThe alarm displays the following information:\n- Alarm
Name\n- Alarm Priority\n- Alarm cause: if different sources produce the same alarm\n- MD level at which the alarm was detected\n\nThe
transport connection toward the remote peer might be defective. Traffic might get lost.\n\nThe 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.\n2. Check the CCM configuration at the remote peer.
Table 38-41: Ethernet_OAM_ETH_AIS_fault

major
release
29/05/2020 Alarms

major
release
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\n\nWhen an MEP receives a valid ETH-AIS frame and AIS is enabled, it shall trigger an AIS
alarm containing the following information:\n- receiving interface\n- MD level\n- Source MAC address\n\nNote:For FSMr3/AirScale unit types,
interface is provided as: 'module type name' EIF 'interface number'. \nFor Flexi Zone Micro BTS, interface is provided as: EIF 'interface
number'.\n\nThe transport connection towards the remote peer may be defective. Traffic may get lost.\n\nThe 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.\n2. Check the configuration at the remote peer.
Table 38-42: EXTERNAL_AL_1

major
release
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\n\nThis 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.\n\nThe effect of the alarm depends on the purpose that was configured for
the user-defined alarm input in the BTS.\n\nDo 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.

major
release

corrected.

major
release

Description: EXTERNAL AL 11\n\nThis is an external user-defined alarm. The alarm is defined by the user in a hardware database.\n\nThe
effect of the alarm depends on the purpose that was configured for the user-defined alarm input in the BTS.\n\nDo not cancel the alarm. The
system automatically cancels the alarm when the fault has been corrected.
29/05/2020 Alarms

major
release

major
release


major
release


major
release

corrected.

major
release

29/05/2020 Alarms

major
release
corrected.

major
release


major
release

corrected.

major
release


major
release
29/05/2020 Alarms

major
release


major
release

corrected.

major
release

corrected.

major
release

29/05/2020 Alarms

major
release

corrected.

major
release

corrected.

major
release

corrected.

major
release

Description: EXTERNAL AL 25\n\nThis is an external user-defined alarm. The alarm is defined by the user\nin a hardware database.\n\nThe
effect of the alarm depends on the purpose that was configured for\nthe user-defined alarm input in the BTS.\n\nDo not cancel the alarm. The
system automatically cancels the alarm when\nthe fault has been corrected.
29/05/2020 Alarms

major
release
Remedial action: The operation depends on the type of alarm that is used as external alarm\nnumber 25.

major
release

Description: EXTERNAL AL 26\n\nThis is an external user-defined alarm. The alarm is defined by the user\nin a hardware database.\n\nThe
effect of the alarm depends on the purpose that was configured for\nthe user-defined alarm input in the BTS.\n\nDo not cancel the alarm. The
system automatically cancels the alarm when\nthe fault has been corrected.
Remedial action: The operation depends on the type of alarm that is used as external alarm\nnumber 26.

major
release

corrected.

major
release


major
release

29/05/2020 Alarms

major
release
corrected.

major
release


major
release


major
release

corrected.

major
release
29/05/2020 Alarms

major
release

corrected.
Table 38-68: FrameSizeProblem (netw)

major
release
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 38-69: FTM_AIS

major
release
Name: FTM_AIS (11560) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_AIS FL16A
Package: racfl.FTM_AIS Implicitly cleared: true
Description: FTM_AIS\n\nAlarm 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.\n\nAll other transmission alarms related to this signal are
suppressed.\n\nProbable cause: There is a transmission problem somewhere in the intermediate network, and AIS is sent instead of user
traffic.\n\nPossible impact on the connections over the interface in question:\n- no calls are possible\n- loss of remote management access to
other network elements in the RAN\n\n
Remedial action: Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling
these alarms.
Table 38-70: FTM_BTS_RESET_REQUIRED

major
release
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
29/05/2020 Alarms

major
release
Description: FTM_BTS_RESET_REQUIRED\n\nA change to the BTS IP settings has been received from the BTS Site Manager. The BTS
should be restarted to activate the change.\n\nThe BTS does not take the new settings into use before a reset.\n\n
Remedial action: Reset the BTS when all the required BTS IP settings have been set.
Table 38-71: FTM_DPD

major
release
Name: FTM_DPD (11562) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_DPD FL16A
Package: racfl.FTM_DPD Implicitly cleared: true
Description: FTM_DPD\n\nA dead peer has been detected in one of the IPsec associations of the FTM.\nThere is no response to the
requests sent to the peer during the IKE SA setup, the IPsec SA setup, or during DPD.\n\nNote: 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.\n\nPossible reasons:\n- a cable is cut or there is no cable connected to the interface\n- the signal
is excessively attenuated\n- the port at the connected far end node is switched off\n\nPossible effects:\n- No calls are possible.\n- loss of
remote management access to other network elements in the RAN\n- loss of synchronization if the interface is used as a synchronization
source\n- IKE SAs and IPSec SAs cannot be established or re-keyed.\n\nThe alarm condition for a protect policy does not exist anymore if
the latest IKE message is answered by the peer.\n\nThe alarm is canceled as soon as the alarm condition does not exist for any protect
policy.\n\nNote: 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).\nSimilarly, 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.\n2. Check that the interface at the far-end interface is
switched on.\n3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.
Table 38-72: FTM_EBER

major
release
Name: FTM_EBER (11563) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_EBER FL16A
Package: racfl.FTM_EBER Implicitly cleared: true
Description: FTM_EBER\n\nExcessive bit error rate: The measured bit error rate exceeds the threshold value of BER-3 (10E-
3).\n\nProbable causes:\n- the signal level is too low (optical connectors or cables are dirty, electrical connectors or cables are corroded)\n-
the specified maximum length of the cable is exceeded\n- the connector is not properly connected to the unit\n- the receiver or the far-end
transmitter has failed\n\nPossible impact:\n- slow management access to the WBTS and other network elements in the RAN\n- poor voice
quality and data performance\n- if this interface is part of an IMA group, this IMA link should be temporarily suspended from operation\n\n
Remedial action: 1. Clean the cables and connectors.\n\n2. Check that the connectors are properly connected to the unit.\n\n3. Check that
the cable connected to the interface in question is not damaged and is within the specifications.\n\n4. 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 38-73: FTM_FAULT_TOGGLING

major
release
Name: FTM_FAULT_TOGGLING (11564) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_FAULT_TOGGLING FL16A
Package: racfl.FTM_FAULT_TOGGLING Implicitly cleared: true
29/05/2020 Alarms

major
release
Description: FTM_FAULT_TOGGLING\n\nAn 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.\n\n\n\n
Remedial action: 1. Check the fault name of the toggling FTM fault from the Fault name of\nthis fault.\n2. Follow the instructions of the
toggling FTM fault to clear the problem.\n \nNote: Detailed information about the toggling frequency can be found in\nalarm history file, which
can be downloaded using the BTS Site Manager. The log file is available with Snapshot.
Table 38-74: FTM_LOF

major
release
Name: FTM_LOF (11565) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOF FL16A
Package: racfl.FTM_LOF Implicitly cleared: true
Description: FTM_LOF\n\nLoss 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.\n\nProbable cause for E1 interfaces: The interface at the far end is not configured to be a
framed E1 interface.\n\nProbable cause for T1 interfaces: The interface at the far end is not configured to be a T1 interface.\n\nPossible
impact on the connections over this interface:\n- no calls are possible\n- loss of remote management access to other network elements in the
RAN\n- loss of synchronization if the interface is used as synchronization source\n\n
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.\n\nJT1 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 38-75: FTM_LOMF

major
release
Name: FTM_LOMF (11566) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOMF FL16A
Package: racfl.FTM_LOMF Implicitly cleared: true
Description: FTM_LOMF\n\nLoss of multi-frame: The interface referenced in the alarm text has lost the multi-frame alignment.\n\nProbable
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.\n\nPossible impact: The performance management data collected on this interface becomes
invalid.\n\n
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 38-76: FTM_LOS

major
release
Name: FTM_LOS (11567) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_LOS FL16A
Package: racfl.FTM_LOS Implicitly cleared: true
29/05/2020 Alarms

major
release
Description: FTM_LOS\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:\nNo signal is received on the interface referenced in
the alarm text. All other transmission alarms related to this signal are suppressed.\n\nProbable causes for Ethernet interfaces:\n- a cable is
cut, or there is no cable connected to the interface\n- the electrical signal is excessively reduced\n- the port at the connected far-end node is
switched off\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nNo signal is received on the interface referenced in the alarm text. All other
transmission alarms related to this signal are suppressed.\n\nProbable causes for Ethernet interfaces:\n- a cable is cut, or there is no cable
connected to the interface\n- the electrical signal is excessively reduced\n- the port at the connected far-end node is switched off\n\nThe 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).\n\nPossible impacts on the connections over this interface are:\n- no calls
are possible\n- loss of remote management access to other network elements in the RAN\n- loss of synchronization if the interface is used as
a synchronization source\n\n
Remedial action: 1. Check that the cables are connected to the correct connectors.\n\n2. Check that the interface at the far-end interface is
switched on.\n\n3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.\n\n4.
Connect a loop cable and check whether the alarm disappears to verify that the hardware of the interface unit works correctly.
Table 38-77: FTM_RDI

major
release
Name: FTM_RDI (11568) Severity: indeterminate Release:

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

major
release
Name: FTM_RESET (11569) Severity: indeterminate Release:

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

major
release
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
29/05/2020 Alarms

major
release
Description: FTM_SECURITY_USER_ACCOUNT\n\nA specific BTS local operator account has been locked.\nThe 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.\n\nNo further logins are permitted for that account until it is unlocked.\n\n
Remedial action: Check the validity of the username and password of the account.
Table 38-80: FTM_SFP

major
release
Name: FTM_SFP (11571) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SFP FL16A
Package: racfl.FTM_SFP Implicitly cleared: true
Description: FTM_SFP\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:\nThe 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.\n\nFlexi Zone Micro FDD,
Flexi Zone Micro TDD:\nThe Small Form-Factor Pluggable (SFP) module is not supported, not present, or could not be recognized.\nThe
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.\nThe SFP module was
expected by the SW, but found missing.\nProbable causes:\n- No SFP module is inserted at the SFP-based Ethernet interface.\n- 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.\n- The SFP module type is not supported.\n\nThe 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).\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD:\nThe interface cannot be
used for transmission.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nThe interface cannot be used for transmission. Conditionally,
Bluetooth is enabled when the backhaul goes down.\nThe laser of the SFP module is not switched on, or no SFP module was detected at
all.\nThe Ethernet Link is down.\nAn Ethernet Link cannot be successfully established.\nNo Ethernet data or clock information is exchanged
between this interface.\n\nPossible impact on the connections over this interface:\n- Voice calls or data connections cannot be established.\n-
Remote management connectivity cannot be established.\n- Loss of synchronization if the interface is used as a synchronization source.\n-
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.\n\n
Remedial action: Flexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD, AirScale BTS TDD:\nInsert a Small Form-Factor Pluggable (SFP)
module with the correct laser type (class 1) to the Gigabit Ethernet interface of the unit.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\n1.
Plug-out and plug-in the SFP module.\n2. Check for SFP validity (could be wrong type).\n3. Insert a compliant SFP module.
Table 38-81: FTM_SFP_WARNING

major
release
Name: FTM_SFP_WARNING (11572) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: FTM_SFP_WARNING FL16A
Package: racfl.FTM_SFP_WARNING Implicitly cleared: true
Description: FTM_SFP_WARNING\n\nThere 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.\n\nThe backhaul via the SFP is in a
degraded condition. The FZM BTS must be monitored for proper operation.\n\n
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.\n1. Check whether the alarm is
caused by exceeded temperature, internal supply voltage, or TX BIAS/TX output power.\n2. 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.\n3. 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.\n4. If the TX BIAS/TX output power causes the alarm, replace the SFP module.
Table 38-82: FTM_SYNC_LOSS
29/05/2020 Alarms

major
release
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\n\nPrimary 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.\n\nThe 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.\n\nProbable
cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example,
LOS).\n\nPossible impact: The BTS is not synchronized to the network anymore.\n\n
Remedial action: Use the BTS Site Manager to check which interfaces have been configured as synchronization sources.\n\n1. Check that
the cables are connected to the correct connectors.\n2. Check whether the interface at the far end is switched on.\n3. Check whether there
are active alarms at the far end. If there are, follow the instructions on handling those alarms.\n4. Connect a loop cable and check whether
the alarm disappears to verify that the hardware of the interface unit works correctly.
Table 38-83: FTM_TIMING_SOURCE_LOS

major
release
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\n\nOne of the synchronization sources in the configured priority list is unavailable.\nThis can be
the primary or the secondary clock source.\n\nIn the alarm: Protocol can be PDH, Timing over Packet (ToP), and Synchronuous
ethernet.\n\nUnit Number is optional:\n- For PDH and Synchronous Ethernet, Unit number is 0 or 1.\n- It is not present for Timing Over
Packet(TOP).\n\nThe interface value is optional:\n- For PDH, the value range depends on the hardware unit type: 1-16.\n- For Synchonuous
Ethernet, the value range is 1-3.\n- It is not present for Timing over Packet.\n\nThe BTS may have to use a synchronization interface that has
a lower clock\nquality: if the primary clock source has been lost, the BTS switches\nautomatically to the secondary clock source. If both the
primary and the\nsecondary clock sources are lost, the BTS switches to the internal clock.\n\n
Remedial action: Use BTS Site Manager to check which interfaces have been configured as\nsynchronization sources. For all interfaces, do
as follows:\n\n1. Check that the cables are connected to the correct connectors.\n2. Check whether the interface at the far end is switched
on.\n3. Check whether there are active alarms at the far end. If there are,\nfollow the instructions on handling those alarms.\n4. Connect a
loop cable and check whether the alarm disappears to verify that the hardware of the interface unit works correctly.\n\nMonitor the quality of
the received clock.
Table 38-84: GaPeerDown

major
release
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 38-85: IncompleteConfiguration

major
release
29/05/2020 Alarms

major
release
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 38-86: IPSEC_EMERGENCY_BYPASS_ACTIVE

major
release
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
Description: IPSEC_EMERGENCY_BYPASS_ACTIVE\n\nThe BTS has entered the IPsec emergency bypass active state, where
configured IPsec policies are ignored and the entire traffic is sent unprotected.\n\nConfigured IPsec policies are ignored, and the entire traffic
is sent unprotected.\n\n
Remedial action: Start IPsec emergency bypass by making the security gateway not reachable either\nby plugging out the cable or
configuring wrong security gateway address.
Table 38-87: IPSEC_EXPERT_MODE

major
release
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\n\nBTS 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.\n\nIPSec expert settings can be configured on BTS via BTS Site Manager only if
IPSec Expert Mode is activated.\n\n
Remedial action: None.
Table 38-88: IPsec_tunnel_switchover

major
release
Name: IPsec_tunnel_switchover (11579) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: IPsec_tunnel_switchover FL16A
Package: racfl.IPsec_tunnel_switchover Implicitly cleared: true
29/05/2020 Alarms

major
release
Description: IPsec_tunnel_switchover\n\nThis alarm will be triggered when at least one primary IPSec tunnel fails, and BTS has switched
over to a secondary IPSec tunnel.\nAs 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.\n\nBTS traffic has switched over from the primary IPSec tunnel to the
secondary (backup) IPSec tunnel terminating on secondary security gateway.\n\nThe 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:\n- Secondary_Active_Probing_Primary --> Primary_Active\n- Secondary_Active_No_Probing_Primary -->
Primary_Active\n\nNote: 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 38-89: IPV6_DUPLICATE_ADDRESS_DETECTED

major
release
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\n\nDuring 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.\n\nThe remote peer to come online with the same IP
address on the same subnet as\nlocal peer would just disable their network interface and give an error until\nthe situation is resolved by the
administrator.\nThis allows the local peer to continue functioning without disruption, but completely breaks IP base communications for the
connected network.\n\n
Remedial action: 1.Check for duplicate IPv6 addresses configured in the BTS.\n2.Change or delete the identified duplicate IPv6 addresses.
Table 38-90: IP_TRAFFIC_CAPTURE_ONGOING

major
release
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\n\nThe base station is currently capturing an IP traffic towards a local port or into a file on
the base station.\nIf the traffic capturing is happening towards a local port, a port and destination MAC address must be provided.\nPort
values can be LMP or < HW MODULE NAME >-<PORT ID>.\n(For E.g: LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1)\n\nNone\n\n
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 38-91: LicensedLimitExceeded

major
release
Name: LicensedLimitExceeded (127) Severity: critical Release:

Type: licensingAlarm Specific problem: Not Applicable FL16A
Package: security.LicensedLimitExceeded Implicitly cleared: true
Raised on class: security.SamLicensePoints Default probable cause: licensedLimitExceeded
Description: The alarm is raised when the license items in the network exceeds 100 percent of the license capacity.
Raising condition: ('Exceeded' EQUAL 'true')
29/05/2020 Alarms

major
release
Clearing condition: ('Exceeded' NOT EQUAL 'true')
Remedial action: Informational - The number of SAM licenses purchased and available on the SAM server is insufficient as compared to the
number of NEs/MDA/Cells under management in the network. Please contact your Nokia sales representative to purchase additional
licenses.
Table 38-92: LinkDown (equipment)

major
release
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 38-93: Link_OAM_critical_link_event__alarm

major
release
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\n\nA 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.\n\nThe following critical link events are possible:\n- 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.\n- Dying Gasp: either the local or the remote peer has a fatal error and is about to restart.\n- Link Fault: the local peer has detected
a physical link fault in receiving direction, for example, a LOS.\n\nNote:\nIn case a received OAMPDU has more than one critical event flag
set, the following shall be reported in the alarm:\nLink Fault bit set |Dying Gasp bit set|Critical Event bit set| Reported\n x x x Link Fault\n x x
Link Fault\n x x Link Fault\n x x Dying Gasp\n\nAlways the latest received critical link event shall be reported.\n\nThe Ethernet interface is
defective, or the remote peer is defective. Traffic might get lost.\n\nThe 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).\nIt 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.\n2. Check the Link OAM state
information of the interface.\n3. Check the cabling and network connections to the far end.\n4. Check the Ethernet interface configuration at
the local and remote sides.\n5. Insert a Link OAM loopback.
Table 38-94: Link_OAM_link_lost_alarm

major
release
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\n\nOn 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).\n\nThe Ethernet interface might
be out of order, or the remote peer might be out of order. Traffic might get lost.\n\nThe 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).
29/05/2020 Alarms

major
release
Remedial action: 1. Check the cabling and network connections to the far end.\n2. Check the Link OAM event information and the Link OAM
state information.\n3. Check the Ethernet interface configuration at the local and remote sides.\n4. Insert a Link OAM loopback.
Table 38-95: Link_OAM_loopback_alarm

major
release
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\n\nA 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.\n\nNormal 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.\n\nFor 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 38-96: LMP_CARRIER_DETECTED

major
release
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\n\nThe 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.\n\nUpdate audit logs.\n\n
Remedial action: 1. Determine if this event is expected: whether a qualified personnel is utilizing LMP ethernet port cable connection for
diagnostic purposes. \n2. Otherwise, it shall be treated as a security warning.
Table 38-97: MobileConnectorDown

major
release
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 38-98: NeManagementAndTrapManagementMismatch
29/05/2020 Alarms

major
release
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.
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 38-99: NewSsh2ServerKeyDetected

major
release
Name: NewSsh2ServerKeyDetected (285) Severity: warning Release:

Package: security.NewSsh2ServerKeyDetected Implicitly cleared: true
Raised on class: security.KnownHostKey Default probable cause: ssh2ServerKeyMismatch
Description: The alarm is raised when a 5620 SAM main server detects a new public SSH key.
Raising condition: ('SSH2 Server Key Status' EQUAL 'Mismatch SSH2 Host Key')
Clearing condition: ('SSH2 Server Key Status' EQUAL 'Active SSH2 Host Key')
Remedial action: Informational - possible security breach. The SSH key of the router is different from the one known to the SAM server.
Table 38-100: NEW_CONFIG_REJECTED

major
release
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\n\nThis alarm is triggered once the new configuration file is rejected and the\nM-Plane connection
is established with fallback configuration as a result\nof M-plane recovery action. It will be visible until next site reset.\n\nThe active base
station configuration is not the same as requested in the configuration change.\n\n
Remedial action: None
Table 38-101: NodeDatabaseFallbackDetected

major
release
29/05/2020 Alarms

major
release
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 38-102: NodeDatabaseMisalignmentDetected

major
release
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 38-103: NodeSuspended

major
release
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 38-104: NO_CERTIFICATE

major
release
29/05/2020 Alarms

major
release
Name: NO_CERTIFICATE (11585) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: NO_CERTIFICATE FL16A
Package: racfl.NO_CERTIFICATE Implicitly cleared: true
Description: NO_CERTIFICATE\n\nA requested certificate could not be retrieved from the certificate authority (CA).\nA requested certificate
could not be renewed from the certificate authority (CA).\n\nA requested certificate could not be retrieved as the number of certificates
received from repository server (RA) or certificate authority (CA) are more than expected.\n\nA 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.\n\nThe requested service is not available.\n\n
Remedial action: Provide the certificate.
Table 38-105: NTP_SERVER_UNREACHABLE

major
release
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\n\nFlexi BTS FDD, Flexi BTS TDD, AirScale BTS FDD/TDD, Flexi Zone Micro FDD, Flexi
Zone Micro TDD:\nA BTS reports this alarm for each instance of the configured NTP server if that\nparticular NTP server is not accessible or
cannot be used after waiting for\na threshold timeout defined by the INTP::ntpAlarmThreshold configuration parameter in PDDB.\n\nThe
raised alarm displays the IP address of the NTP server that is not reachable\nin the additional information field
'alarmNotif::argumentInfo'.\n\nNote : For each NTP server instance, timers are started separately and a separate\nalarm is raised. This
threshold time is not used to clear the alarm.\n\nFlexi Zone:\nFlexi Zone Access Point reports this alarm for each instance of the
configured\nNTP server if that particular NTP server is not accessible or cannot be used\nafter waiting for a threshold time-out defined by the
configuration parameter\nINTP::ntpAlarmThreshold in PDDB.\n\nThe raised alarm displays the IP address of the NTP server that is not
reachable\nin the additional information field 'alarmNotif::argumentInfo'.\n\nNote : For each NTS server instance, timers are started
separately and a separate\nalarm is raised. This threshold time is not used to clear the alarm.\n\nThe 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.\n\nFlexi
Zone:\nFlexi 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.\n\n
Remedial action: 1. Check the connectivity to the NTP server.\n2. Check the NTP server configuration at the BTS.\n3. Check the configured
threshold value for the NTP server.
Table 38-106: PartialResyncProblem

major
release
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 38-107: PartialVPRNEncryption
29/05/2020 Alarms

major
release
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 38-108: PersistentIndexParametersMisconfigured

major
release
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 38-109: PLR_THRESHOLD_CROSSED

major
release
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\n\nThe alarm is raised if the packet loss ratio equals or exceeds the configured\nthreshold
value during the current observation interval of 15 minutes.\n\nThis alarm is an indication that the backhaul capacity for traffic with
same\nprofile as this TWAMP session (DSCP value, packet size), may be much too small,\nbecause some of the measurement packets
seem to have been thrown away.\n\nThe TWAMP measurement packets are lost because of degraded traffic throughput.\n\n
Remedial action: 1. Check the backhaul usage and if other applications with the same or higher\nPHB may compete against this TWAMP
session about the capacity. An increase in\nthe priority of TWAMP session or of the backhaul capacity may clear the alarm.\n\n2. Check if
destination is unreachable by IP connectivity test. Send an ICMP\necho request (ping) to the UDP port of the TWAMP reflector at the
destination\nIP.If ICMP echo reply indicates that the destination is unreachable but you\nhave access to TWAMP reflector, you can check its
status. If the status is disabled\nor down try to activate it again and check if alarm disappears.\n\n3. Check configured PLR threshold. Setting
PLR to 0% should be avoided, because\nevery lost measurement packet will trigger the alarm and it cannot be cleared\nagain (PLR>="0)."
Table 38-110: PollerProblem

major
release
29/05/2020 Alarms

major
release
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')
Once the issue has been resolved SAM will automatically re-attempt.
Table 38-111: PrimaryImageBootFailure

major
release
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 38-112: RadiusOperStatusDown

major
release
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 38-113: ReachabilityProblem

major
release
29/05/2020 Alarms

major
release
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 38-114: ReconfigFailure

major
release
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')
Remedial action: Verify that the object is configured as expected.
Table 38-115: RTT_THRESHOLD_CROSSED

major
release
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\n\nThe RTT threshold alarm is sent in case the average value of the RTT exceeds or equals
the configured threshold for a 1-min period.\n\nThis alarm is an indication that the backhaul capacity for traffic with the\nsame profile as this
TWAMP session (DSCP value, packet size) may be too small,\nbecause the measurement packets are scheduled later than before.\n\n
Remedial action: 1. Check the backhaul usage and if other applications with the same or higher\nPHB may compete against this TWAMP
session about the capacity. An increase in\nthe priority of TWAMP session or of the backhaul capacity may clear the alarm.\n\n2. Check the
last measured RTT values of this TWAMP session and verify that\nthe configured RTT threshold value is not too close to average measured
RTT\nvalues, so that this alarm could be result of sporadic mis-measurement.
Table 38-116: SaveConfigFailed

major
release
29/05/2020 Alarms

major
release
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 38-117: ScheduledPollerProblem

major
release
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 38-118: SFP_HW_Failure

major
release
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\n\nA malfunctioning of the SFP transceiver was detected. \nThe SFP has reported a transmission fault
condition and has disabled the laser transmitter.\n\nThe SFP is not operational.\n\nThe 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 38-119: SSH_ENABLED

major
release
Name: SSH_ENABLED (11590) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSH_ENABLED FL16A
Package: racfl.SSH_ENABLED Implicitly cleared: true
29/05/2020 Alarms

major
release
Description: SSH_ENABLED\n\nThe Flexi Zone Micro BTS or Flexi Zone Access Point detects that the SSH access to the site is
enabled.\n\nNote: 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.\n\nUpdate audit logs.\n\n
Remedial action: 1. Determine if this event is expected.\nNote: 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 38-120: SSM_POORQUALITY

major
release
Name: SSM_POORQUALITY (11591) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSM_POORQUALITY FL16A
Package: racfl.SSM_POORQUALITY Implicitly cleared: true
Description: SSM_POORQUALITY\n\nThis alarm is raised when the received SSM indicates lower clock quality (for example, 'do not use' or
'EEC') than required.\n\nNote: The interface numbering shall be similar to ETHLK.\nE.g: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1,interface
4.\n\nFlexi Zone Micro FDD, Flexi Zone Micro TDD:\nSyncE is no longer a working synchronization source.\n\nThe 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:\n1. Confirm that SyncE is desired as a
synchronization source.\n2. Confirm that eNB configuration settings for ssmEnabled are correct.\n3. Troubleshoot with Backhaul provider on
the reason SSM errors.
Table 38-121: SSM_TIMEOUT

major
release
Name: SSM_TIMEOUT (11592) Severity: indeterminate Release:

Type: communicationsAlarm Specific problem: SSM_TIMEOUT FL16A
Package: racfl.SSM_TIMEOUT Implicitly cleared: true
Description: SSM_TIMEOUT\n\nThis alarm is raised if the incoming SSM is not received for a certain time period (configured through the
parameter 'ssmTimeout').\n\nNote: The interface numbering is similar to ETHLK.\nExample: DN:SYNC-1/STPG-1/STPU-1-4 for unit 1,
interface 4\n\nSyncE is no longer a working synchronization source.\n\n
Remedial action: 1. Confirm that SyncE is desired as a synchronization source.\n2. Confirm that configuration settings for ssmEnabled are
correct.\n3. Troubleshoot with backhaul provider about the reason for SSM errors.
Table 38-122: StatsRetrieveFailed

major
release
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'))
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 38-123: SubscriberSystemNextHopUsageHigh
29/05/2020 Alarms

major
release
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 38-124: TOP_MASTER_UNUSABLE

major
release
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\n\nThe reference clock monitoring has detected a loss of ToP reference clock signal received from
the master clock behind $IP:\n- The eNB does not receive a reply from ToP Master within a certain time (5 sec) upon sending a sync request
message.\n- 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.\n\nThere might be another synchronization source available at eNB. In that case, the BTS switches automatically
to the other clock source.\n\nIf no other synchronization source is available at eNB, it runs in hold-over mode. \n\nPlease refer to status of
'3080: EFaultId_BtsReferenceClockMissing'.\n\n
Remedial action: 1. Check the cable connectivity.\n2. Check the TOP configuration.
Table 38-125: TRANSPORT_MODULE_MISSING

major
release
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\n\nA unit is missing. The slot has been configured to hold a unit, but the plug-in\nunit is not
physically present in the slot.\n\nProbable causes:\n\n- The unit has been configured but not detected.\n- The unit is broken and therefore not
detected.\n- The unit has been configured but some other unit is detected.\n\nNOTE: The unit variable should be replaced by appropriate HW
names configured (unitTypeConfigured) during runtime reporting.\n\nPossible impacts:\n- No calls are possible for the connections over this
unit.\n- Remote management access to other network elements in the RAN is lost.\n\n
Remedial action: Replacing a faulty hardware:\n1. Plug in again the expected transport unit that is referenced in the alarm text.\n2. In case
there is a unit present in the slot, remove it from the slot\nand plug it back in. If the unit is still not recognized and the alarm\nremains, replace
the faulty unit with a new one. \n\nDecommissioning a previously commissioned hardware:\n1. Recommission to remove the hardware unit
referenced in the alarm text.\n\nNOTE: Before recommissioning, the hardware unit must not be present in the slot.
Table 38-126: TrapDestinationMisconfigured

major
release
29/05/2020 Alarms

major
release
Name: TrapDestinationMisconfigured (33) Severity: major Release:

Package: netw.TrapDestinationMisconfigured Implicitly cleared: true
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 38-127: TrapReceivingFailure

major
release
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 38-128: TrapRoutePreferenceRedundancyMissing

major
release
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
29/05/2020 Alarms

major
release
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 38-129: TRUST_ANCHOR_EXPIRING

major
release
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\n\nThe 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.\n\nNo immediate effect. If at all certificate expires without any
action from operator due to this fault, secure communication to remote peers may fail.\n\n
Remedial action: Update the trust anchors.
Table 38-130: UnidentifiedNode

major
release
Name: UnidentifiedNode (1922) Severity: major Release:

Package: netw.UnidentifiedNode Implicitly cleared: true
Raised on class: netw.DiscoveredNode Default probable cause: unidentifiedNode
Description: The alarm is raised when the node being discovered can not be properly identified.
Raising condition: ('State' EQUAL 'Pending Identification')
Clearing condition: ('State' NOT EQUAL 'Pending Identification')
Remedial action: A configuration error has occurred that must be corrected. The eNodeB does not have a system name. The name can be
configured by selecting the alarm, opening the associated properties form for the alarmed object and configuring the system name.
Table 38-131: UnmanageFailed

major
release
Name: UnmanageFailed (300) Severity: warning Release:

Type: discoveryControlAlarm Specific problem: Not Applicable FL16A
Package: netw.UnmanageFailed Implicitly cleared: true
Raised on class: netw.NodeDiscoveryControl Default probable cause: unableToDeleteNode
Description: The alarm is raised when an attempt to unmanage an NE fails.
29/05/2020 Alarms

major
release
Raising condition: ('Site State' EQUAL 'Unmanage Failed')
Clearing condition: ('Site State' NOT EQUAL 'Unmanage Failed')
Remedial action: Informational - if the alarm persists please contact your Nokia support representative for assistance
Table 38-132: UNSUPPORTED_HW_DEVICE

major
release
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\n\nThe SW does not support the detected HW unit type.\n\nProbable causes:\n\n- The SW
version of the system module is too old.\n- The supported HW variant is not present in the system module.\n\nThe possible impact is that no
calls are possible for the connections over this unit.\n\n
Remedial action: SW upgrading: Upgrade the FSM SW release to the latest version that includes the support for the new external transport
device variant.\n\nUnit variant replacement: Replace the unsupported device variant to another one that supports the currently running SW
release.
Table 38-133: UpgradedBuildVersionMismatch

major
release
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 38-134: upgradedCardAlarm

major
release
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')
29/05/2020 Alarms

major
release
Table 38-135: UplinkDown

major
release
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 38-136: UplinkPartiallyDown

major
release
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 38-137: VENDOR_CERTIFICATE_EXPIRING

major
release
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\n\nThe BTS raises this alarm when the vendor BTS certificate is about to expire.\n\nThe
period of advance notification is configurable, as well as the CA certificate expiry.\n\n1 day ... 4999 days with default 90 days\n\nNote: For
Flexi Zone Controller, the period of advance notification is a non-configurable 90 days.\n\nAs 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.\n\n
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:\nCheck the vendor BTS certificate expiry date. \nReplace the expired vendor BTS certificate if possible
(for example, an older BTS like FSMr2).\nOtherwise, 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.\n\nFor 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.
Table 38-138: VersionConfigRestoreFailed

29/05/2020 Alarms

major
release
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 38-139: WIFI_CARD_INVALID_TYPE

major
release
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\n\nThe internal Wi-Fi module type is invalid.\n\nThe internal Wi-Fi module might not be
operational.\n\n
Remedial action: 1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported.\n2. Replace
the Flexi Zone Micro BTS.
Table 38-140: WIFI_CARD_NOT_PRESENT

major
release
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\n\nThe internal Wi-Fi module is not present.\n\nThe internal Wi-Fi module might be not
operational.\n\n
Remedial action: 1. Check the release notes of the downloaded BTS software if any known Wi-Fi module issues are reported.\n2. Replace
the Flexi Zone BTS.
Table 38-141: WrongCpaaSoftwareVersion

major
release
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'))
29/05/2020 Alarms

major
release
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 Help PDF

Uploaded by

Copyright:

Available Formats

Nokia Help PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nokia Help PDF

Uploaded by

Copyright:

Available Formats

What are some common alarms that could occur in a network?

What are some common alarms that could occur in a network?

What causes the AGWDiameterPeerDown alarm?

What causes the AGWDiameterPeerDown alarm?

29/05/2020 Alarms

Alarm Reference > 38. FDD AirScale

Table 38-1: ActiveAbnormalCondition

Alarm Attributes Applicable

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 38-2: AGWDiameterPeerDown

Alarm Attributes Applicable

Name: AGWDiameterPeerDown (844) Severity: indeterminate Release:

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

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

Table 38-3: AUTO_NEGO_MIS_MATCH

Alarm Attributes Applicable

Name: AUTO_NEGO_MIS_MATCH (11513) Severity: indeterminate Release:

Alarm Attributes Applicable

Name: AuxiliaryServerStatus (311) Severity: critical Release:

Raising condition: ('Server Status' EQUAL 'Down')

Clearing condition: ('Server Status' EQUAL 'Up')

Table 38-5: BareMetalReachabilityDown

Alarm Attributes Applicable

Name: BareMetalReachabilityDown (10273) Severity: major Release:

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

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

Table 38-6: BASE_STATION_CONNECTIVITY_DEGRADED

Alarm Attributes Applicable

Name: BASE_STATION_CONNECTIVITY_DEGRADED Severity: indeterminate Release:

Alarm Attributes Applicable

Table 38-7: BASE_STATION_CONNECTIVITY_LOST

Alarm Attributes Applicable

Alarm Attributes Applicable

Name: BASE_STATION_CONNECTIVITY_LOST (11515) Severity: indeterminate Release:

Remedial action: FAULT NAME\nS1 interface recovery failure\n\nFAULT ID\n6317: EFaultId_S1ResetRetryOut\n\nMEANING\nThe S1

Table 38-8: BASE_STATION_FAULTY

Alarm Attributes Applicable

Name: BASE_STATION_FAULTY (11516) Severity: indeterminate Release:

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Table 38-9: BASE_STATION_LICENSE_LIMITATION

Alarm Attributes Applicable

Name: BASE_STATION_LICENSE_LIMITATION (11517) Severity: indeterminate Release:

Table 38-10: BASE_STATION_NOTIFICATION

Alarm Attributes Applicable

Name: BASE_STATION_NOTIFICATION (11518) Severity: indeterminate Release:

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable

Alarm Attributes Applicable