LTE_BTS_Faults(TDLTE基站告警大全)

Fault name# autonomous reset as recovery action$Protocol Timing source lost on unit $U [, interface $IF]10b8b coding error in Optical Interface device <opt link/RP3>2M external reference missingAIS on unit $U, interface $IFAddress mismatch in summingAntenna Carrier configuration failureAntenna Line Device Operation FailureAntenna Line Device failureAntenna Line Operation DegradedAntenna Line failureAntenna line device HW failureAntenna link is downAutomatic BTS Operator Certificate retrieval unsuccessfulBB bus message collision errorBB bus reception error (summing device)BB bus transmission errorBFD Session down in egress direction for session $SBFD Session down in ingress direction for session $SBFD group $bfdGrpId downBTS BlockedBTS Master Clock tuning failureBTS SW download or activation failedBTS config error (Not enough HW for LCR)BTS file errorBTS internal SW management problemBTS is uncommissionedBTS reference clock missingBTS reset requiredBTS reset requiredBTS reset time increasedBTS time not correctedBTS vendor specific file faultBaseband Bus failureBaseband bus configuration of <x> was rejectedBoot configuration inconsistency detectedBuffer over/underflow in clock crossing logicCCM fault md $d level $ fault $f prio $p cause $cCRL update failure due to cause $CCell blockedCell configuration data distribution failedCell power failureCommissioning error: <x>Communication failureConfiguration error: <x>Configuration file corruptedCooling fan brokenCooling fan has reduced from the set speedCooling fan is over speedingCritical BER detected on the optical connection to Radio Module Dead Peer DetectedDifference between BTS master clock and reference frequency Distributed site support not enabledEBER on unit $U, interface $IFETH AIS fault mac $xError in file server during file download type <fileTypeNumber> FPGA SW update failedFSP in resetting stateFTM Toggling <Fault name>FTM booted at $date due to $RCauseFailure during cell activationFailure in connection between BTS and iOMS or 3rd party tool Failure in optical RP3 interfaceFailure in trace sessionFan failureFan module faultyFan module operation degradedFatal OSE ErrorFile System access failedFile corrupted in SW downloadFilter unit operation failedFive failed logins to FTM due to wrong user name or password Flash operation failureFrame Clock MissingFrame clock deviation faultFrame number synchronization error in optical interfaceGPS Receiver alarm: <x>GTP-U Path FailureHeating element not workingIP address conflictIncoherency In Cell ConfigurationIncoherency in cell configurationIncoherency in cell configurationIncoherency with RF ModulesIncompatible SW version detectedIncorrect radio network parametersIncreased BER detected on the optical connection to Radio Module Inproper optIf configurationInternal MTU configuration failureInvalid Configuration fileInvalid frequency channel for the BTS HWLOF on unit $U, interface $IFLOMF on slot $U, interface $IFLOS on unit $U, [ethernet] interface $IFLicense missing for feature $feature on interface $ifLink OAM critical link event $E on unit $U, interface $FLink OAM link lost on unit $U, interface $FLink OAM loopback inserted on unit $U, interface $F by $P peer Low noise amplifier failureMHA unit operation failureMast Head Amplifier faultMast Head Amplifier fault above current window, <line>Mast Head Amplifier fault below current window, <line>Master unit has lost connection to the slave unitMaximum number of neighbour eNBs/cells exceededMissing RNW parameterMissing RP3-01 linkMissing or non-compliant SFP module on unit $U, interface $I Module Clock FaultyModule dangerously overheatingNTP server is not accessibleNo MME capacity assigned by Core NetworkNo connection to Flexi transport submoduleNo connection to unitNo feedback signalNo module fan detectedNot able to synchronize baseband bus with <x>OIC MCU Buffer FullOptical Interface Data/Control/Ethernet Buffer FullOptical Interface faultyOven oscillator Missing PulseOven oscillator clock missingOven oscillator heating failurePOST test failedPPS reference missingParallel RP3-01 link length mismatchPeer system module connection lostPhich Power Boost not appliedPipe dangerously overheatingPost test failedPower level not supportedRDI on unit $U, interface $IFRET Antenna control failureRF BB Bus Configuration ErrorRF BB Bus Connection Transmission ErrorRF BB Bus Synchronization ErrorRF Loss of secondary optical interfaceRF Module Filter input power missingRF Module Gain adjusting failureRF Module Power output faultyRF Module blockedRF Module configuring failedRF Module critical file not foundRF Module failureRF Module file not foundRF Module out of orderRF Module overvoltage protection faultyRF Power decreasedRNW parameter mismatchRP3-01 Link ConflictRX out of orderRadio Master ConflictRadio resources switched offReceiving failure in Optical InterfaceRouting misconfiguration for application $aS1 SCTP path failureS1 interface recovery failureS1 interface setup failureSRAM operation failureSRIO chain configuration was rejectedSW corruptedSW fallbackStarting temperature below minimumSynchronization failure in Optical Interface <opt link/RP3 link> Synchronization lostSystem Module failureSystem information broadcast parameters overflowTWAMP PLR Threshold CrossedTWAMP RTT Threshold CrossedTX failure in MIMOTX out of orderTechnical log buffer freezingTemperature alarmTemperature too low (Heating ongoing) Toggling: <Fault name>Transmission clock missingTransmission parameters missing Transmission quality deterioratedTransport layer connection failure in S1 interface Transport layer connection failure in X2 interface Unit (module) dangerously overheatingUnit (module) temperature is highUnit SW download failedUnit blockedUnit initialization failureUnit not supported by current BTS SW version Unit synchronization failedUnit temperature is highUnit unidentifiedUnknown HW resourceUnknown product codeVSWR alarmVSWR alarmVendor BTS certificate due to expireX2 interface recovery failureX2 interface setup failureX2 neighbor cell configuration inconsistency [User defined]Fault ID and name Used in products - 52: EFaultId_UnitAutonomousResetAl- LTE- 61059: FTM_TIMING_SOURCE_LOS- LTE- 2004: EFaultId_OIC_LVDSRecAl- LTE- 1899: EFaultId_2MExtRefMissAl- LTE- 61151: FTM_AIS- LTE- 2019: EFaultId_Muksu_SsubMmAl- LTE- 6259: EFaultId_AntennaCarrierMessageFailed- LTE- 1871: EFaultId_BusyAl- 1872: EFaultId_FormatErrorAl - LTE- 3100: EFaultId_AntennaLineFailure- LTE - 4046: EFaultId_AntennaLineDegradedAl- LTE- 1836: EFaultId_ALOvercurrentAl- 4045: EFaultId_AntennaLineFaultyAl - LTE- 1847: EFaultId_HardwareErrorAl- LTE - 476: EFaultId_Rp3BusError- LTE - 61510: NO_CERTIFICATE- LTE - 2018: EFaultId_Muksu_StxPortCollAl- LTE - 2016: EFaultId_Muksu_SMTimeOffAl- LTE - 2017: EFaultId_Muksu_SRx10b8bAl- LTE - 61606: BFD DOWN Egress- LTE - 61605: BFD DOWN Ingress- LTE - 61022: BFD DOWN- LTE - 50: EFaultId_BTSBlockedAl- LTE - 1818: EFaultId_Ov_OscAl- LTE- 29: EFaultId_FileCorruptionAl - 30: EFaultId_SwUpdateAl - LTE- 1868: EFaultId_NotEnoughHwForLcrAl- LTE- 1802: EFaultId_FileRequestFlashAl - 1803: EFaultId_FileParsingFailedAl - LTE- 3090: EFaultId_BtsInternalSwManagementProblem- LTE- 4030: EFaultId_NoCommDataAl- LTE- 3080: EFaultId_BtsReferenceClockMissing- LTE- 4001: EFaultId_BtsResetNeededAl- LTE- 61010: FTM_BTS_RESET_REQUIRED- LTE- 4091: EFaultId_BtsResetTimeIncreasedAl- FlexiBTS- 26: EFaultId_NtpTimeNotSetAl- LTE- 6262: EFaultId_InvalidVendorSpecificFile- LTE- 3020: EFaultId_BaseBandBusFailure- LTE- 1811: EFaultId_BbBus_ConfFailedAl- LTE- 4102: EFaultId_BootConfigurationInconsistencyAl- FlexiBTS- FlexiLiteBTS - 2054: EFaultId_MuksuRxClkErrorAl- LTE- 61410: Ethernet OAM CCM fault- LTE- 61074: CRL Update failure- LTE- 49: EFaultId_CellBlockedAl- LTE- 6253: EFaultId_CellSetupFailed- LTE- 4090: EFaultId_TxCarrierInputPowerLowAl- LTE- 3060: EFaultId_CommissioningError- LTE- 1806: EFaultId_CommunicationFailureAl- LTE- 3070: EFaultId_ConfigurationError- LTE- 1924: EFaultId_FrConfigurationFileCorrupted- FlexiBTS- 1933: EFaultId_FrFanBroken- LTE- 1934: EFaultId_FrFanReducedSetSpeed- LTE- 1935: EFaultId_FrFanOverSpeed- LTE- 1956: EFaultId_CritBerOnRp3- LTE- 61030: FTM_DPD- LTE- 9: EFaultId_DacWordChangeAl- FlexiBTS- LTE- 4076: EFaultId_DistributedSiteSupportNotEnabledAl- 61104: FTM_EBER- LTE- 61411: Ethernet OAM ETH_AIS_fault- LTE- 27: EFaultId_FileServerAl- FlexiBTS- MetroSite - 1928: EFaultId_FrFpgaSwUpdateFailed- FlexiBTS - 4068: EFaultId_FspResetAl- LTE- 61619: FTM_FAULT_TOGGLING- LTE- 61006: FTM_RESET- LTE- 6267: EFaultId_CellActivationFailedAl- LTE- 6261: EFaultId_TraceConnectionFaultyAl- LTE- 3030: EFaultId_FailureInOptical_Rp3Interface- LTE- 6263: EFaultId_TraceSessionAl- LTE- 3050: EFaultId_FanFailure- LTE- 1: EFaultId_FanPowerAl- LTE- 0: EFaultId_ChangeFanAl- LTE- 418: EFaultId_OseFatalErr- LTE- 4088: EFaultId_FileSystemAccessFailedAl- LTE- 28: EFaultId_SwPackageAl- LTE- 1840: EFaultId_TuningFailureAl - 1841: EFaultId_UnitFaultyAl - LTE- 61500: FTM_SECURITY- LTE- 214: EFaultId_FlashWrAl - 215: EFaultId_FlashRdAl - LTE- 1903: EFaultId_FrFrameClockMissing- FlexiBTS - 2014: EFaultId_Muksu_SFCRCompDevAl- LTE- 2047: EFaultId_OIC_FrSyncLostAl- LTE- 4011: EFaultId_GPSSystemElementAl- LTE- 6150: EFaultId_GtpuPathFailure- LTE- 1860: EFaultId_HeatingMatNotWorkingAl- LTE- 4144: EFaultId_IpAddressConflict- FlexiBTS - 4044: EFaultId_IncoherencyCellConfigurationAl- LTE- 4000: EFaultId_IncoherencyInConfiguration- LTE- 1856: EFaultId_IncoherencyInCellConfigurationAl- LTE- 1857: EFaultId_IncoherencyWithRFModulesAl- LTE- 23: EFaultId_IncompatibleSwVersionAl - 24: EFaultId_ObsoleteSwVersionAl - LTE- 6252: EFaultId_FailureInNetworkPlanFile- LTE- 1955: EFaultId_IncrBerOnRp3- LTE- 4099: EFaultId_InproperOptIfConfig- FlexiBTS - 4025: EFaultId_MtuConfigurationFailureAl- LTE- 4036: EFaultId_InvalidConfigurationFileAl- LTE- 1807: EFaultId_InvalidFrequencyChannelForBTSHW- LTE- 61028: FTM_LOF- LTE- 61150: FTM_LOMF- LTE- 61029: FTM_LOS- LTE- 61400: FTM_LICENSE_MISSING- LTE- 61077: Link OAM critical link event alarm- LTE- 61076: Link OAM link lost alarm- LTE- 61075: Link OAM loopback alarm- LTE- 1839: EFaultId_LNAFailureAl- LTE- 1869: EFaultId_MinorTMAFaultAl - 1870: EFaultId_MajorTMAFaultAl - LTE- 3120: EFaultId_MastHeadAmplifierFault- LTE- 1834: EFaultId_AboveCurrentWindowAl- LTE- 1835: EFaultId_BelowCurrentWindowAl- LTE- 4019: EFaultId_KeepAliveStatusErrorAl- LTE- 6265: EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded- LTE- 4009: EFaultId_RnwParameterMissingAl- LTE- 4064: EFaultId_MissingRp301LinkAl- LTE- 61050: FTM_SFP- LTE- 1926: EFaultId_FrModuleClockFaulty- FlexiBTS - 4071: EFaultId_SysDangerouslyOverheatAl- LTE- 61613: NTP_SERVER_UNREACHABLE- LTE- 6264: EFaultId_S1ZeroCapPlmns- LTE- 3511: EFaultId_NoConnectionToFtAl- LTE- 10: EFaultId_NoConnectionToUnitAl- LTE- 1920: EFaultId_FrNoFeedBackSignal- FlexiBTS - 1932: EFaultId_FrNoFansDetected- LTE- 1815: EFaultId_BbBus_SyncFailedAl- LTE- 2011: EFaultId_OIC_MCUBFullAl- LTE- 2007: EFaultId_OIC_DBTxFullAl - 2008: EFaultId_OIC_CBRxFullAl - LTE- 2000: EFaultId_OIC_TxAl - 2001: EFaultId_OIC_PresAl - LTE- 1820: EFaultId_OcxoPulseMissingAl- LTE- 1819: EFaultId_OcxoClkMissAl- LTE- 1817: EFaultId_Ov_Osc_HeatAl- LTE- 69: EFaultId_Post_test_failedAl- LTE- 1898: EFaultId_PpsRefMissAl- LTE- 4072: EFaultId_ParallelLinkDifferenceTooLargeAl - LTE- 4110: EFaultId_PeerSystemModuleConnectionLostAl- LTE- 6112: EFaultId_PhichPowerBoostAl- LTE- 1938: EFaultId_FrPipeOverheat- LTE- 1925: EFaultId_FrPostTestFailed- FlexiBTS - 4008: EFaultId_PowerLevelNotSupportedAl- LTE- 61152: FTM_RDI- LTE- 1842: EFaultId_MotorJamAl - 1843: EFaultId_ActuatorJamAl - LTE- 1905: EFaultId_FrRfBbBusConfigError- FlexiBTS - 1906: EFaultId_FrRfBbBusConnTransError- FlexiBTS - 1904: EFaultId_FrRfBbBusSynchError- FlexiBTS - 1930: EFaultId_FRLossOfSecondaryOptIf- LTE- 1910: EFaultId_FrFilterInputPowerMissing- FlexiBTS - 1908: EFaultId_FrGainAdjust- FlexiBTS - 1918: EFaultId_FrPowerOutputFault- FlexiBTS - 1931: EFaultId_FrBlocked- LTE- 1900: EFaultId_FrConfiguringFailed- FlexiBTS - 1901: EFaultId_FrCriticalFileNotFound- FlexiBTS - 3010: EFaultId_RfModuleFailure- LTE- 1902: EFaultId_FrFileNotFound- FlexiBTS - 1912: EFaultId_FrOutOfOrder- FlexiBTS - 1942: EFaultId_FrOverVoltageProtectionFaulty- FlexiBTS - 1927: EFaultId_FrPowerDecreased- FlexiBTS - 1896: EFaultId_RnwParameterMismatchAl- LTE- 4039: EFaultId_Rp301LinkConflictAl- LTE- 1911: EFaultId_FrRxOutOfOrder- FlexiBTS - 4038: EFaultId_RadioMasterConflictAl- LTE- 4057: EfaultId_RfSwitchedOffAl- LTE- 2002: EFaultId_OIC_RxAl- LTE- 61073: ROUTING_MISCONFIGURATION- LTE- 6204: EFaultId_S1SctpPathAl- LTE- 6317: EFaultId_S1ResetRetryOut- LTE- 6308: EFaultId_S1SetupRetryOut- LTE- 1875: EFaultId_SRAMRdAl - 1876: EFaultId_SRAMWrAl - LTE- 4015: EFaultId_Srio_ConfFailedAl- LTE- 1850: EFaultId_SwCorruptedAl- 4029: EFaultId_SwCorruptedPermanentAl - LTE- 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl- 4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl - LTE- 1827: EFaultId_StartTempBelowMinAl- LTE- 2005: EFaultId_OIC_SyncChAl- LTE- 61058: FTM_SYNC_LOSS- LTE- 3000: EFaultId_SystemModuleFailure- LTE- 6351: EFaultId_SystemInfoValueTagHandlingFailed- LTE- 61611: PLR_THRESHOLD_CROSSED- LTE- 61610: RTT_THRESHOLD_CROSSED- LTE- 4003: EFaultId_TxFailureTurnMimoOffAl- LTE- 1907: EFaultId_FrTxOutOfOrder- FlexiBTS- 6450: EFaultId_TechnicalLogUploadRecommended- LTE- 3040: EFaultId_TemperatureAlarm- LTE- 1922: EFaultId_FrTemperatureTooLow- LTE- 4026: EFaultId_TogglingAl- LTE- 1816: EFaultId_Trans_Clk_MsgAl- LTE- 1825: EFaultId_PublicIPmissingAl- LTE- 1921: EFaultId_FrTransmissionQualityDetoriated- FlexiBTS - 6202: EFaultId_S1SctpEndpointAl- LTE- 6203: EFaultId_X2SctpEndpointAl- LTE- 1937: EFaultId_FrDangerouslyOverheat- LTE- 1936: EFaultId_FrTempHigh- LTE- 6: EFaultId_SwDownloadAl- LTE- 48: EFaultId_UnitBlockedAl- LTE- 12: EFaultId_TcomConfigAl- 4040: EFaultId_InitFaultManAl - LTE- 95: EFaultId_NotSupportedUnit- LTE- 16: EFaultId_SynchronizationAl- LTE- 2: EFaultId_UnitOverheatAl- LTE- 1923: EFaultId_FrUnitUnidentified- FlexiBTS - 94: EFaultId_UnknownUnitType- LTE- 93: EFaultId_UnknownProductCode- LTE- 1838: EFaultId_VSWRMinorAl- LTE- 1837: EFaultId_VSWRMajorAl- LTE- 61616: VENDOR_CERTIFICATE_EXPIRING- LTE- 6303: EFaultId_X2ResetRetryOut- LTE- 6304: EFaultId_X2SetupRetryOut- LTE- 6307: EFaultId_X2NeighbourCellInfoInconsistency- LTE- 1400: EFaultId_ExtAl0- 1401: EFaultId_ExtAl1- LTEDetecting unitFCM/ FCTFTLB, FTIBFCMFCMFTLB, FTIBFCMFCMFSMFSM, Antenna Line Device itselfFRFlexi Filter, FRFF, TILTFlexiBTS: FSPCFTLB, FTIBFCMFCMFCMFTIB, FTLB, FTFBFTIB, FTLB, FTFBFTIB, FTLB, FTFBFCMFCMFCMFCMFCM/ FCTFSMFCMFSMFSMFTLB, FTIBFSMFCMFSMFSM, FRFSM/FCM, FSM/FSPFlexiBTS (FSMr2): FCM, (FSMr3): FCT; FlexiLiteBTS: SCR FCMFTIB, FTFB, FTLBFTLB, FTIBFSMFCMFSMFSM, FRFCMFSMFRx/LTXFR/RFSWFR/RFSWFR/RFSWFRx / LTXFTLB, FTIBFlexiBTS: FCMFSMFTLB, FTIBFTIB, FTFB, FTLBUltraSite, MetroSite, MetroSite 50, Triple-mode: WAM; FlexiBTS: FCM; UltraSite/EUBB: WAMA FRM2/LTXFCMFTLB, FTIB, FSM, FTIFFTLB, FTIBFCM [FSM Rel2] / FCT [FSM Rel3] / CC&T [FQGA]FCMFSM, FRFCMFSM, FRFCMFCMFSPFCM, FCTFCMFlexi Filter, External Filter, RFMFTLB, FTIBFCMFRx / LTXFCMFCMFSMFCMFCMFCMFSMFCMFCMFCMFCMFSMFRx / LTXFCMFCMFCMFCMFTLB, FTIBFTLB, FTIBFTLB, FTIBFTLB, FTIBFTIB, FTLB, FTFBFTIB, FTFB, FTLBFTIB, FTFB, FTLBFlexi FilterAISG MHAFSM, FRFRFRFSMFCMFSMFCMFTLB, FTIBFRx/LTXFCMINTPFCMFSMFCMFRx/LTXFR/RFSWFCM, FSPFCMFCMFCMFCMFCMFCMFCM, FTFCMFCMFCMFSMFRFRx/LTXFSMFTLB, FTIBTILTFRx / LTXFRx/LTXFRx / LTXFRx/LTXFRx/LTXFRx/LTXFRM1/LTXFRx/LTXFRx/LTXFRx/LTXFSM, FRFRx/LTXFRx/LTXFRFRM2/LTXFCMFCMFRx/LTXFCMFCMFCMFTLB, FTIBFSMFSMFCMFSMFSMFCMFSMr2: FCM, FSMr3: FCT FCMFCMFTLB, FTIBFSMFSPFTIB, FTLBFTIB, FTLBFSMFRx/LTXFSPFSM, FRFRx/LTX FSMFCMFCMFRx/LTX FSMFSMFR/RFSWFR/RFSW FCMFSMFCMFCMFCMFCMFRx/LTX FCMFCMFlexi Filter, FR Flexi Filter, FR FTIB,FTLB FSMFCMFCMFCMSourceFCM/FCT, RFSW, FSPSTPGOptIFFCMPPTTFCM, FSPTX1-n/RX1-nFlexi Filter, FA, AISG MHA, TILT FR, MHA, TILT, EFILMHA, RET, EFilAntenna connectorFF, TILT, MHA, EFILFlexiBTS: FSPC, FSMC, FSMD CERTHFCMFSP, FRFCMBFDBFDBFDGRPFCMFCMFCM, FRLCRFCM/FCTFSM, FCT, FR, FT, FSP, Faraday FSMFSMFRFTMFSMFCMFSMFSM, FROptical interfaces 1-5, FSP, FCM FlexiBTSFSMr2: FCM, FSP MCU, FSMr3: FCT OptIfOAMMEPCERTHLCRFCMLCRFSM, FR, FTFCM, FSP, FTM, FR, FF, MHA, RET FSM, FR, AntennaLine, LCR, LCG LTX/TX1-n/RX1-nFan supervisionFan supervision.RFSWFRIKESAFlexiBTS: FCMOptIFPPTTOAMMEPUltraSite, MetroSite, MetroSite 50, Triple-mode: WAM LTXFSPFTMFTMLCRFCMFSM, FRFCMFSM/FAN, FRFANFANFSPFCM, FCTFCM, FRTX1-n / RX1-nFTMFCM, FSPLTX, RX1-nFCMFSM, OptIFFSMGTP-UFCMOptIFLCRFSM, LCRFRFRFCM, FR, FF, FA, FSP, FTMFSMFRFRFCM, FSPFCMLCRPPTTPPTTETHLKPPTT, FTMETHLKETHLKETHLKRX1-nAISG MHAFF, AISG MHAMHAMHAFSM, FSPFCMLCRRX, TXETHLKLTXFSPINTPFCMFTMFSP, FT, FF, MHA, TILT, FR, FA, extension FSM, FSM FANs TX1-nRFSWFSP, FCM, OptIFFCMOptIFOptIFFCMFCMFCMFSP, FT, FCMFCMOptIFFCMFSPTX1-nLTXLCRPPTTTILTLTX, TX1-n, RX1-nModule or antenna lineLTX, TX1-n, RX1-nModuleTX1-nTX1-nLTX/TX1-nLTXLTXLTXFRLTXLTXLTXTX1-nFCMFRAntenna lineFRAntenna lineOptIFIEIF and IVIFSCTP link on S1 interfaceLNMMELNMMEFSMFSPCFilter, FR, FTM4082:FSMr2: FCM, FSP MCUBTSOptIFSTPGFSMLCRTWAMPTWAMPLCRTX1-nFSPFSM, FRLTXFSM, FRFCMFTTX1-nSCTP link for S1 interface. SCTP link for X2 interface. RFSWRFSWFCM, FSP, FR, FaradayFRFCM, FSPAll possible units.FCM, FSPFCM, FSPLTX- FSP (fixed and plug-in cards) - FRFSM, FSP, FT, FRAntenna connectorAntenna connectorCERTHLNADJLNADJFCMFCMMeaningThe BTS tries to correct a fault situation by performing a recovery reset to a unit, the site or the BTS.One of the synchronisation sources in the configured priority list is unavailable.This can be the primary or the secondary clock source.The fibre cable has an interference; the data becomes faulty.The reference clock monitoring has detected a loss of 2.048MHz signal received from an external reference source, connected to Sync In interface of the System Module.Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its receive signal.There is a baseband bus address mismatch in the summing. There are two possible causes:Antenna carrier resources were not successfully set up during cell setup or cell deletion procedure because of failure of RX or TX resource. Affected cell might be not operational.The device is not working properly, the configuration is not valid, or a given parameter is incorrect.The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.An alarm message has been received from the antenna line device. The antenna line operation is degraded.Radio Module (60W RRH) or Filter (all others) has detected overcurrent on the antenna line (note: antenna line term here also refers to theRS485 i/f). The antenna line might be damaged (short circuit) or some antenna line device is causing overload. All antenna line devices powered A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).Antenna (RP3) link is down: transmitter or receiver drops from synchronization.A requested certificate could not be retrieved from the certificate authority (CA).A requested certificate could not be renewed from the certificate authority (CA).Routed baseband bus messages towards the connected module have collided; the data in the output baseband internal link is lost because the baseband bus is incorrectly configured.The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.A decoding error has been detected in the baseband internal link. The data packet is lost, or the content is corrupted.The alarm is raised if the alarm is enabled, the BFD state of the session is not AdminDown and the BFD packet from the far end contains the diagnostic code = 'Control Detection Time Expired' AND no ingress alarm is present.The alarm is raised if the alarm is enabled, the BFD state for the session is not AdminDown and nevertheless no BFD packet is received at the local end during the detection time.The alarm is raised if the BFD service is not available anymore on the BTS for a particular interface (plain Ethernet or VLAN interface). In case only 1 BFD session is configured and activated for the interface, the alarm is raised if BFD on this session fails in either ingress or egressThe BTS is blocked with BTS Site Manager. The purpose is to avoid fault indications that may be raised during a BTS maintenance task.The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is lower than 205 or greater than 3891 (5% of the total adjustment area). The range for the DAC word is 0 - 4095.The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem in the module or a corrupted flash file system.RF Module cannot serve all cells commissioned to the RF module.The BTS module properties data or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing. The Fault diagnostics rule file is missing or its parsing has failed. The SCF migration failed in the SW upgrade to a newer release.A software update to a module or sub-assembly has failed, or a corrupted SW file has been detected in the FLASH.Commissioning file download has been started neither from BTS Site Manager nor NetAct during Autoconfiguration. Autoconfiguration might not be enabled in NetAct, the license is missing or the commissioning file is not found.This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configured synchronization reference signal or if all the synchronization reference signals are missing. The BTS fault is not generated if the highestThe BTS detected an RF Module that cannot be taken into use without a BTS reset. The RF Module type differs from the previous one or the RF module was not present during startup.A change to the BTS IP settings has been received from the BTS Site Manager. To activate the change, the BTS needs to be restarted.BTS has detected RF module power cycle failure and is trying to recover from the failure during BTS reset procedure.BTS reset will last longer due to additional actions performed by BTS to recover from faulty situation.The SNTP time cannot be fetched from the transport system (FTM) within the time limit.There was an opening, reading, or file content problem with a BTS vendor- specific file at BTS startup.The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific module but there are several possible fault sources.The baseband bus related configuration of <x> was rejected by the HW SW, DSP or LTX.During SW update it was detected that configurations of active and passive SW in HW unit are same. Active and passive SW configuration are compared:Clock crossing buffer underflow or overflow in RX block and the received data might not be valid. The fault is an indication of either too large clock drift between received signal and internal clock or wrong RX rate setting.The alarm is triggered whenever a service OAM error related to the transmission of Continuity Check Messages (CCM) persists on a given Ethernet interface over the period 2,5 s.This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL) for one of the following reasons:- the LDAP binding failsThe user has blocked the cell with BTS Site Manager.BTS raises this fault if it experiences a problem in internal configuration data distribution (cell setup) to C- and U-Plane SW components.Flexi Radio Module has detected low downlink carrier input power from the Flexi System Module.Some of the commissioning parameters are either missing or faulty, or there is a mismatch between them.Communication with an application failed. It has not replied to the message that has been sent/resent to it.There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch in the BTS configuration.The RF Module SW detected conflicting or corrupted configuration data.Fan(s) are not rotating.Fan(s) are rotating slower than requested.Fan(s) rotate faster than requested.Abnormally high bit error rate has been detected on the optical link to radio module which results in permanent baseband processing failure. I/Q data stream cannot be successfully processed by FRM due to the burst of consecutive LCV errors.A dead peer was detected in one of the IPsec associations of the FTM.The reference frequency that the BTS master clock receives has changed by about 0.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) during the measurement period, compared to the BTS master clock frequency.Long fiber between FSM and FR detected but Distributed Site feature not enabled (actDistributedSite = False).Excessive bit error rate. The measured bit error rate exceeds the threshold value of BER-3 (10E-3).A Maintenance Endpoint (MEP) received a valid ETH-AIS frame.。