Alarm NSN

Changes between issues 01 and 01A Changes between releases RL60 and RL70
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
New
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed New
New
Changed
New
Changed Changed
New
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
New
New
Changed New
Changed Changed
Changed
Changed
Changed New
Changed New
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed Changed
Changed
Changed
New
New
New
Changed
Changed Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed
Changed Changed
Changed
Changed
Changed
New
Removed Removed
Removed Removed
Removed Removed
Removed Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Removed
Fault ID and Name
2:EFaultId_UnitOverheatAl
6:EFaultId_SwDownloadAl
9:EFaultId_DacWordChangeAl
10:EFaultId_NoConnectionToUnitAl
12:EFaultId_TcomConfigAl
16:EFaultId_SynchronizationAl
23:EFaultId_IncompatibleSwVersionAl
24:EFaultId_ObsoleteSwVersionAl
26:EFaultId_NtpTimeNotSetAl
27:EFaultId_FileServerAl
28:EFaultId_SwPackageAl
29:EFaultId_FileCorruptionAl
48:EFaultId_UnitBlockedAl
49:EFaultId_CellBlockedAl
50:EFaultId_BTSBlockedAl
52:EFaultId_UnitAutonomousResetAl
69:EFaultId_Post_test_failedAl
94:EFaultId_UnknownUnitType
95:EFaultId_NotSupportedUnit
214:EFaultId_FlashWrAl
215:EFaultId_FlashRdAl
216:EFaultId_FlashEraseAl
217:EFaultId_FlashDrvAl
218:EFaultId_FlashDbChksumAl
412:EFaultId_LostFrameSync
418:EFaultId_OseFatalErr
476:EFaultId_Rp3BusError
1400:EFaultId_ExtAl0
1802:EFaultId_FileRequestFlashAl
1806:EFaultId_CommunicationFailureAl
1807:EFaultId_InvalidFrequencyChannelForBTSHW
1811:EFaultId_BbBus_ConfFailedAl
1815:EFaultId_BbBus_SyncFailedAl
1816:EFaultId_Trans_Clk_MsgAl
1817:EFaultId_Ov_Osc_HeatAl
1818:EFaultId_Ov_OscAl
1819:EFaultId_OcxoClkMissAl
1825:EFaultId_PublicIPmissingAl
1827:EFaultId_StartTempBelowMinAl
1834:EFaultId_AboveCurrentWindowAl
1835:EFaultId_BelowCurrentWindowAl
1836:EFaultId_ALOvercurrentAl
1837:EFaultId_VSWRMajorAl
1838:EFaultId_VSWRMinorAl
1839:EFaultId_LNAFailureAl
1840:EFaultId_TuningFailureAl
1841:EFaultId_UnitFaultyAl
1842:EFaultId_MotorJamAl
1843:EFaultId_ActuatorJamAl
1844:EFaultId_NotCalibratedAl
1845:EFaultId_NotConfiguredAl
1846:EFaultId_ActuatorInterferenceAl
1847:EFaultId_HardwareErrorAl
1848:EFaultId_WorkingSoftwareMissingAl
1850:EFaultId_SwCorruptedAl
1858:EFaultId_FaultyFcmConfigurationAl
1860:EFaultId_HeatingMatNotWorkingAl
1868:EFaultId_NotEnoughHwForLcrAl
1869:EFaultId_MinorTMAFaultAl
1870:EFaultId_MajorTMAFaultAl
1871:EFaultId_BusyAl
1872:EFaultId_FormatErrorAl
1873:EFaultId_UnsupportedProcedureAl
1874:EFaultId_OutOfRangeAl
1875:EFaultId_SRAMRdAl
1876:EFaultId_SRAMWrAl
1898:EFaultId_PpsRefMissAl
1899:EFaultId_2MExtRefMissAl
1900:EFaultId_FrConfiguringFailed
1901:EFaultId_FrCriticalFileNotFound
1902:EFaultId_FrFileNotFound
1903:EFaultId_FrFrameClockMissing
1904:EFaultId_FrRfBbBusSynchError
1905:EFaultId_FrRfBbBusConfigError
1906:EFaultId_FrRfBbBusConnTransError
1907:EFaultId_FrTxOutOfOrder
1908:EFaultId_FrGainAdjust
1910:EFaultId_FrFilterInputPowerMissing
1911:EFaultId_FrRxOutOfOrder
1912:EFaultId_FrOutOfOrder
1918:EFaultId_FrPowerOutputFault
1920:EFaultId_FrNoFeedBackSignal
1921:EFaultId_FrTransmissionQualityDetoriated
1922:EFaultId_FrTemperatureTooLow
1923:EFaultId_FrUnitUnidentified
1924:EFaultId_FrConfigurationFileCorrupted
1925:EFaultId_FrPostTestFailed
1926:EFaultId_FrModuleClockFaulty
1927:EFaultId_FrPowerDecreased
1928:EFaultId_FrFpgaSwUpdateFailed
1931:EFaultId_FrBlocked
1932:EFaultId_FrNoFansDetected
1933:EFaultId_FrFanBroken
1934:EFaultId_FrFanReducedSetSpeed
1935:EFaultId_FrFanOverSpeed
1936:EFaultId_FrTempHigh
1937:EFaultId_FrDangerouslyOverheat
1938:EFaultId_FrPipeOverheat
1955:EFaultId_IncrBerOnRp3
1956:EFaultId_CritBerOnRp3
1957:EFaultId_AntennaLineSwitchedOffAl
1958:EFaultId_Rp3CollisionOnFr
2000:EFaultId_OIC_TxAl
2001:EFaultId_OIC_PresAl
2002:EFaultId_OIC_RxAl
2004:EFaultId_OIC_LVDSRecAl
2005:EFaultId_OIC_SyncChAl
2006:EFaultId_OIC_DBRxFullAl
2007:EFaultId_OIC_DBTxFullAl
2010:EFaultId_OIC_EBFullAl
2011:EFaultId_OIC_MCUBFullAl
2014:EFaultId_Muksu_SFCRCompDevAl
2016:EFaultId_Muksu_SMTimeOffAl
2017:EFaultId_Muksu_SRx10b8bAl
2019:EFaultId_Muksu_SsubMmAl
2048:EFaultId_Casa2Rp1CrcAl
2049:EFaultId_Casa2Rp1FramePhaseAl
2054:EFaultId_MuksuRxClkErrorAl
2056:EFaultId_SwMismatchAl
2057:EFaultId_MuksuMsgInWrongSlotAl
2058:EFaultId_MuksuMsgRoutingFailedAl
2059:EFaultId_MuksuSummingNotEnabledAl
2060:EFaultId_MuksuTransmissionRuleCollisionAI
2061:EFaultId_MuksuOverloadCollisionAl
3000:EFaultId_SystemModuleFailure
3003:EFaultId_FbiaFailureAl
3010:EFaultId_RfModuleFailure
3050:EFaultId_FanFailure
3070:EFaultId_ConfigurationError
3080:EFaultId_BtsReferenceClockMissing
4000:EFaultId_IncoherencyInConfiguration
4001:EFaultId_BtsResetNeededAl
4003:EFaultId_TxFailureTurnMimoOffAl
4008:EFaultId_PowerLevelNotSupportedAl
4011:EFaultId_GPSSystemElementAl
4015:EFaultId_Srio_ConfFailedAl
4019:EFaultId_KeepAliveStatusErrorAl
4025:EFaultId_MtuConfigurationFailureAl
4026:EFaultId_TogglingAl
4030:EFaultId_NoCommDataAl
4036:EFaultId_InvalidConfigurationFileAl
4038:EFaultId_RadioMasterConflictAl
4040:EFaultId_InitFaultManAl
4043:EFaultId_TuningFrequencyOutOfRangeAl
4044:EFaultId_IncoherencyCellConfigurationAl
4045:EFaultId_AntennaLineFaultyAl
4046:EFaultId_AntennaLineDegradedAl
4069:EFaultId_Rs485PowerFailureAl
4071:EFaultId_SysDangerouslyOverheatAl
4072:EFaultId_ParallelLinkDifferenceTooLargeAl
4073:EFaultId_FanVendorNotDetectedAl
4076:EFaultId_DistributedSiteSupportNotEnabledAl
4077:EFaultId_FspOverheatingAl
4078:EFaultId_FanBrokenAl
4079:EFaultId_CoolingFanSpeedDecreasedAl
4080:EFaultId_FanOverSpeedAl
4082:EfaultId_FallbackDueToMaxResetLoopCounterValueAl
4083:EFaultId_FallbackDueToConfigurationDataMigrationFailureAl
4085:EfaultId_FallbackDueToTransportRequestAl
4088:EFaultId_FileSystemAccessFailedAl
4090:EFaultId_TxCarrierInputPowerLowAl
4091:EFaultId_BtsResetTimeIncreasedAl
4092:EFaultId_MurkkuDefaultInitFailedAl
4110:EFaultId_PeerSystemModuleConnectionLostAl
4114:EFaultId_SynchronizationMasterMissingAl
4122:EFaultId_GpsReceiverNotTrackingSatellitesAl
4123:EFaultId_GpsReceiverSurveyInProgressAl
4124:EFaultId_GpsReceiverNoStoredPositionAl
4125:EFaultId_GpsReceiverPositionQuestionableAl
4126:EFaultId_GpsReceiverEepromInvalidAl
4141:EFaultId_DcVoltageAdministrativelyDisabledAl
4142:EFaultId_Communication3gppAdministrativelyDisabledAl
4145:EFaultId_SignatureValidationFailedAl
4153:EFaultId_PpsRefClcMissInStrtAl
4180:EFaultId_OperationOnSharedOpticalPortFailedAl
4203:EFaultId_RtpmConnectionFaultAl
4208:EFaultId_RromIpConfigAl
4210:EFaultId_ExtGpsInHoldoverAl
6112:EFaultId_PhichPowerBoostAl
6117:EFaultId_HighInterferenceToUlSubframeAl
6150:EFaultId_GtpuPathFailure
6202:EFaultId_S1SctpEndpointAl
6203:EFaultId_X2SctpEndpointAl
6204:EFaultId_S1SctpPathAl
6252:EFaultId_FailureInNetworkPlanFile
6253:EFaultId_CellSetupFailed
6257:EFaultId_CellReconfigurationFailed
6261:EFaultId_TraceConnectionFaultyAl
6262:EFaultId_InvalidVendorSpecificFile
6263:EFaultId_TraceSessionAl
6264:EFaultId_S1ZeroCapPlmns
6265:EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded
6268:EfaultId_MaximumNumberOfWcdmaNbCellsAI
6269:EfaultId_MaximumNumberOfWcdmaNbRelsAI
6270:EfaultId_MaximumNumberOfWcdmaNbRelsPerCellAndCarrierAl
6274:EFaultId_NeighborCellAmbiguityDetected
6277:EFaultId_AutomaticCellRecoveryNotPossible
6278:EFaultId_MfbiCellConfigurationConflict
6279:EFaultId_PciConfusionDetectedAl
6280:EFaultId_PhaseSynchronizationErrorAl
6303:EFaultId_X2ResetRetryOut
6304:EFaultId_X2SetupRetryOut
6308:EFaultId_S1SetupRetryOut
6317:EFaultId_S1ResetRetryOut
6320:EFaultId_CellS1UnavailabilityAl
6321:EFaultId_S1EnbConfigurationUpdate
6322:EFaultId_RimInterfaceTimeout
6323:EFaultId_RimInterfaceError
6351:EFaultId_SystemInfoValueTagHandlingFailed
6450:EFaultId_TechnicalLogUploadRecommended
6502:EFaultId_HighMemoryConsumptionAl
6701:EFaultId_CriticalBitTogglingError
6706:EFaultId_DspPlatformFatalErrAl
6707:EFaultId_DspApplicationFatalErrAl
6708:EFaultId_ExternallyTriggeredDspFatalErrAl
61006:FTM_RESET
61010:FTM_BTS_RESET_REQUIRED
61022:BFD DOWN
61028:FTM_LOF
61029:FTM_LOS
61030:FTM_DPD
61050:FTM_SFP
61058:FTM_SYNC_LOSS
61059:FTM_TIMING_SOURCE_LOS
61074:CRL Update failure
61075:Link OAM loopback alarm
61076:Link OAM link lost alarm
61077:Link OAM critical link event alarm
61079:SFP HW Failure
61104:FTM_EBER
61150:FTM_LOMF
61151:FTM_AIS
61152:FTM_RDI
61201:TRANSPORT_MODULE_MISSING
61410:Ethernet OAM CCM fault
61411:Ethernet OAM ETH_AIS_fault
61500:FTM_SECURITY
61510:NO_CERTIFICATE
61605:BFD DOWN Ingress
61606:BFD DOWN Egress
61607:AUTO NEGO MIS MATCH
61610:RTT_THRESHOLD_CROSSED
61611:PLR_THRESHOLD_CROSSED
61613:NTP_SERVER_UNREACHABLE
61616:VENDOR_CERTIFICATE_EXPIRING
61618:TRUST_ANCHOR_EXPIRING
61619:FTM_FAULT_TOGGLING
61623:SSM_TIMEOUT
61624:SSM_POORQUALITY
61631:TOP_MASTER_UNUSABLE
61632:IPV6_DUPLICATE_ADDRESS_DETECTED
61634:UNSUPPORTED_HW_DEVICE
61639:IPSEC_EMERGENCY_BYPASS_ACTIVE
61641:IP_TRAFFIC_CAPTURE_ONGOING
61643:IPsec_tunnel_switchover
1857:EFaultId_IncoherencyWithRFModulesAl
4097:EFaultId_BtsConfNotSupportedAl
4198:EFaultId_UnitAutonomousResetDelayedOrAbandonedAl
6259:EFaultId_AntennaCarrierMessageFailed
0:EFaultId_ChangeFanAl
1:EFaultId_FanPowerAl
30:EFaultId_SwUpdateAl
4081:EFaultId_MurkkuReleaseFromResetFailedAl
6267:EFaultId_CellActivationFailedAl
1820:EFaultId_OcxoPulseMissingAl
1831:EFaultId_ActiveClkTuningAl
1856:EFaultId_IncoherencyInCellConfigurationAl
1866:EFaultId_RulesMissingAl
1867:EFaultId_RulesParsingAl
1896:EFaultId_RnwParameterMismatchAl
1930:EFaultId_FRLossOfSecondaryOptIf
2008:EFaultId_OIC_CBRxFullAl
2009:EFaultId_OIC_CBTxFullAl
3020:EFaultId_BaseBandBusFailure
3030:EFaultId_FailureInOptical_Rp3Interface
3040:EFaultId_TemperatureAlarm
3060: EFaultId_CommissioningError
3090:EFaultId_BtsInternalSwManagementProblem
3100:EFaultId_AntennaLineFailure
3120: EFaultId_MastHeadAmplifierFault
3511:EFaultId_NoConnectionToFtAl
4009:EFaultId_RnwParameterMissingAl
4010:EFaultId_PLLStatusNotLockedAl
4029:EFaultId_SwCorruptedPermanentAl
4039:EFaultId_Rp301LinkConflictAl
4057:EfaultId_RfSwitchedOffAl
4064:EFaultId_MissingRp301LinkAl
4068:EFaultId_FspResetAl
4102:EFaultId_BootConfigurationInconsistencyAl
4107:EFaultId_RfPowerSwitchedOffFromBtsSmAl
4144:EFaultId_IpAddressConflict
4152:EFaultId_PowerLevelNotSuitableAl
4161:EFaultId_LossOfPrimaryOptIfAl
Fault Name
Unit temperature is high
Unit SW download failed
Difference between BTS master clock and reference frequency
No connection to unit
Baseband resources mapping to cells failure
Unit synchronization failed
Incompatible SW version detected
Obsolete SW version detected
BTS time not corrected
Error in file server during file download
File corrupted in SW download
BTS SW download or activation failed
Unit blocked
Cell blocked
BTS blocked
# autonomous reset as recovery action
POST test failed
Unknown HW resource
Unit not supported by current BTS SW version
Flash operation failure
Fault between FSM and FSP because of the lack of RP1 clock
Fatal OSE Error
Antenna link is down
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
BTS file error
Communication failure
Invalid frequency channel for the BTS HW
Baseband bus configuration of <x> was rejected
Not able to synchronize baseband bus with <x>
Transmission clock missing
Oven oscillator heating failure
BTS master clock tuning failure
Oven oscillator clock missing
Transmission parameters missing
Starting temperature below minimum
Mast Head Amplifier fault above current window, <line>
Mast Head Amplifier fault below current window, <line>
Antenna line failure
VSWR major alarm
VSWR minor alarm
Low noise amplifier failure
Filter tuning failure
Filter unit faulty
RET Antenna control failure
Antenna line device HW failure
Antenna line device missing software
SW corrupted
Faulty configuration of system modules
Heating element not working
BTS configuration error (not enough HW for LCR)
MHA operation degraded
MHA operation failure
Antenna Line Device Operation Failure
SRAM operation failure
PPS reference missing
2M external reference missing
RF Module configuring failed
RF Module critical file not found
RF Module file not found
Frame clock missing
RF BB bus synchronization error
RF BB bus configuration error
RF BB bus connection transmission error
TX out of order
RF Module gain adjusting failure
RF Module filter input power missing
RX out of order
RF Module out of order
RF Module power supply output faulty
No feedback signal
Transmission quality deteriorated
Temperature too low (Heating ongoing)
Unit unidentified
Configuration file corrupted
Post test failed
Module Clock faulty
RF Power decreased
FPGA SW update failed
RF Module blocked
No module fan detected
Cooling fan broken: <X>
Cooling fan has reduced from the set speed
Cooling fan is over speeding
Unit (module) temperature is high
Unit (module) dangerously overheating
Pipe dangerously overheating
Increased BER detected on the optical connection to Radio Module
Critical BER detected on the optical connection to Radio Module
Antenna line switched off
RP3 routing collisions are detected on FR module
Optical Interface faulty
Receiving failure in Optical Interface
10b8b coding error in optical interface device <opt link/RP3>
Synchronization failure in Optical Interface <opt link/RP3 link>
Optical Interface Data/Control/Ethernet Buffer Full
OIC MCU Buffer Full
Frame clock deviation fault
BB bus reception error (summing device)
BB bus transmission error
Address mismatch in summing
Synchronization error in RP1 receiver
Buffer over/underflow in clock crossing logic
Firmware SW mismatch
BB bus message in the wrong slot
Message routing problem in receiver (RX)
Summing not enabled for message type
Transmission rule collision in Muksu
Overload collision in transmitter
System Module failure
Failure in replaceable baseband unit
RF Module failure
Fan failure
Configuration error: <x>
BTS reference clock missing
Incoherence in cell configuration
BTS reset required
TX failure in MIMO
Power level not supported
GPS Receiver alarm: control interface not available
SRIO chain configuration was rejected
Master unit has lost connection to the slave unit
Internal MTU configuration failure
Toggling: <Fault name>
BTS is uncommissioned
Invalid configuration file
Radio master conflict
Unit initialization failure
Tuning frequency out of range
Incoherency in cell configuration
Antenna line faulty
Antenna line operation degraded
RS485 IUANT port failure
Module dangerously overheating
Parallel RP3-01 link length mismatch
Fan vendor not detected
Distributed site support not enabled
FSP overheating
Cooling fan broken
Cooling fan speed decreased
SW fallback
SW fallback
SW fallback
File System access failed
Cell power failure
BTS reset time increased
Summing service default initialization failed
Peer system module connection lost
Synchronization master missing
GPS receiver alarm: not tracking satellites
GPS receiver alarm: survey in progress
GPS receiver alarm: no stored position
GPS receiver alarm: position questionable
GPS receiver alarm: EEPROM invalid
DC voltage administratively disabled
3GPP/AISG communication administratively disabled
Validation of signed file failed
Reference clock missing in startup
Operation on shared optical port failed
Failure in connection to Real-time PM Collection Entity
External GPS receiver in holdover
Phich Power Boost not applied
High interference to UL subframe
GTP-U Path Failure
Transport layer connection failure in S1 interface
Transport layer connection failure in X2 interface
S1 SCTP path failure
Incorrect radio network parameters
Cell configuration data distribution failed
Cell reconfiguration data distribution failed
Failure in connection between BTS and iOMS or 3rd party tool
BTS vendor-specific file fault
Failure in trace session
No MME capacity assigned by Core Network
Maximum number of neighbor eNBs/cells exceeded
Maximum number of WCDMA neighbor cells is exceeded
Maximum number of WCDMA neighbor relations is exceeded
Maximum number of WCDMA neighbor relations per cell and carrier is exceeded
Neighbor cell ambiguity detected
Automatic cell recovery not possible
MFBI cell configuration conflict
PCI confusion detected
Phase error exceeds 5 us limit
X2 interface recovery failure
X2 interface setup failure
S1 interface setup failure
S1 interface recovery failure
Cell lost S1 availability
S1 eNB configuration update
RIM interface timeout
RIM interface error
System information broadcast parameters overflow
Diagnostic Files collected
High memory consumption
Critical bit toggling error
DSP platform fatal error
DSP application fatal error
Externally triggered DSP fatal error
BTS booted at $date due to $RCause
BTS reset required
BFD group $bfdGrpId down
LOF on unit $U, interface $IF
LOS on unit $U, [Ethernet] interface $IF
Dead Peer Detected
Missing or non-compliant SFP module on unit $U, interface $I
Synchronization lost
$Protocol Timing source lost [on unit $U] [, interface $IF]
CRL update failure
Link OAM loopback inserted on unit $U, interface $F by $P peer
Link OAM link lost on unit $U, interface $F
Link OAM critical link event $E on unit $U, interface $F
SFP HW Failure
EBER on unit $U, interface $IF
LOMF on slot $U, interface $IF
AIS on unit $U, interface $IF
RDI on unit $U, interface $IF
Transport module missing: $unit
CCM fault level $ prio $p cause $c
ETH AIS fault interface $IF level $l mac $x
Five failed logins to FTM due to wrong user name or password.
Automatic BTS Operator Certificate retrieval unsuccessful
BFD $session down, ingress, $sourceIP to $destinationIP
BFD $session down, egress, $sourceIP to $destinationIP
Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
TWAMP RTT Threshold Crossed
TWAMP PLR Threshold Crossed
NTP server is not accessible
Vendor BTS certificate is about to expire
BTS and/or peer trust anchor expired or due to expire
FTM Toggling <Fault name>
SyncE SSM Timed Out on unit $UID, interface $IF
SyncE Quality Level Degraded on unit $UID, interface $IF
ToP master service $IP unusable
Dup Addr on {duplicateIpv6Address} {VID: id}
Unsupported HW device
IPsec emergency bypass active
IP Traffic Capturing Ongoing [port $port,] [mac $m]
IPsec tunnel switchover
Incoherency with RF Modules
BTS configuration not supported
Notification about autonomous recovery reset delayed or abandoned
Antenna Carrier configuration failure
Fan module operation degraded: <X>
Fan module faulty: <X>
Summing service release from reset failed
Failure during cell activation
Oven oscillator Missing Pulse
Active clock tuning fault
Fault diagnostics rule file error
Fault diagnostics rule file error
RNW parameter mismatch
RF loss of secondary optical interface
Baseband bus failure
Failure in optical RP3 interface
Temperature alarm
Commissioning error: <x>
BTS internal SW management problem
Antenna Line Device failure
Mast Head Amplifier fault
No connection to Flexi transport submodule
Missing RNW parameter
PLL status not locked
SW corrupted
RP3-01 link conflict
Radio resources switched off
Missing RP3-01 link
FSP in resetting state
Boot configuration inconsistency detected
Power on #smodLogicalId #pwrLineId line switched off remotely by user
IP address conflict
Power level not supported for cells using the same radio module
Loss of primary Opt IF
Fault Name in issue 01
Unit temperature is high
Unit SW download failed
Difference between BTS master clock and reference frequency
No connection to unit
Baseband resources mapping to cells failure
Unit synchronization failed
Incompatible SW version detected
Obsolete SW version detected
BTS time not corrected
Error in file server during file download
File corrupted in SW download
Unit blocked
Cell blocked
BTS blocked
# autonomous reset as recovery action
POST test failed
Unknown HW resource
Unit not supported by current BTS SW version
Fault between FSM and FSP because of the lack of RP1 clock
Fatal OSE Error
Antenna link is down
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
BTS file error
Communication failure
Invalid frequency channel for the BTS HW
Baseband bus configuration of <x> was rejected
Not able to synchronize baseband bus with <x>
Transmission clock missing
Oven oscillator heating failure
BTS master clock tuning failure
Oven oscillator clock missing
Transmission parameters missing
Starting temperature below minimum
Mast Head Amplifier fault above current window, <line>
Mast Head Amplifier fault below current window, <line>
Antenna line failure
VSWR major alarm
VSWR minor alarm
Low noise amplifier failure
Filter tuning failure
Filter unit faulty
Antenna line device HW failure
Antenna line device missing software
SW corrupted
Faulty configuration of system modules
Heating element not working
BTS configuration error (not enough HW for LCR)
MHA operation degraded
MHA operation failure
PPS reference missing
2M external reference missing
RF Module configuring failed
RF Module critical file not found
RF Module file not found
Frame clock missing
RF BB bus synchronization error
RF BB bus configuration error
RF BB bus connection transmission error
TX out of order
RF Module gain adjusting failure
RF Module filter input power missing
RX out of order
RF Module out of order
RF Module power supply output faulty
No feedback signal
Transmission quality deteriorated
Temperature too low (Heating ongoing)
Unit unidentified
Configuration file corrupted
Post test failed
Module Clock faulty
RF Power decreased
FPGA SW update failed
RF Module blocked
No module fan detected
Cooling fan broken: <X>
Cooling fan has reduced from the set speed
Unit (module) temperature is high
Unit (module) dangerously overheating
Pipe dangerously overheating
Increased BER detected on the optical connection to Radio Module
Critical BER detected on the optical connection to Radio Module
Antenna line switched off
RP3 routing collisions are detected on FR module
Receiving failure in Optical Interface
10b8b coding error in optical interface device <opt link/RP3>
Synchronization failure in Optical Interface <opt link/RP3 link>
OIC MCU Buffer Full
Frame clock deviation fault
BB bus reception error (summing device)
BB bus transmission error
Address mismatch in summing
Buffer over/underflow in clock crossing logic
Firmware SW mismatch
BB bus message in the wrong slot
Message routing problem in receiver (RX)
Summing not enabled for message type
Transmission rule collision in Muksu
Overload collision in transmitter
System Module failure
Failure in replaceable baseband unit
RF Module failure
Fan failure
Configuration error: <x>
BTS reference clock missing
Incoherence in cell configuration
BTS reset required
TX failure in MIMO
Power level not supported
GPS Receiver alarm: control interface not available
SRIO chain configuration was rejected
Master unit has lost connection to the slave unit
Internal MTU configuration failure
Toggling: <Fault name>
BTS is uncommissioned
Invalid configuration file
Radio master conflict
Tuning frequency out of range
Antenna line faulty
Antenna line operation degraded
RS485 IUANT port failure
Module dangerously overheating
Parallel RP3-01 link length mismatch
Fan vendor not detected
Distributed site support not enabled
FSP overheating
Cooling fan broken
Cooling fan speed decreased
SW fallback
SW fallback
SW fallback
File System access failed
Cell power failure
BTS reset time increased
Summing service default initialization failed
Peer system module connection lost
Synchronization master missing
GPS receiver alarm: not tracking satellites
GPS receiver alarm: survey in progress
GPS receiver alarm: no stored position
GPS receiver alarm: position questionable
GPS receiver alarm: EEPROM invalid
DC voltage administratively disabled
3GPP/AISG communication administratively disabled
Validation of signed file failed
Reference clock missing in startup
Operation on shared optical port failed
Failure in connection to Real-time PM Collection Entity
External GPS receiver in holdover
Phich Power Boost not applied
High interference to UL subframe
GTP-U Path Failure
Transport layer connection failure in S1 interface
Transport layer connection failure in X2 interface
S1 SCTP path failure
Incorrect radio network parameters
Cell configuration data distribution failed
Cell reconfiguration data distribution failed
Failure in connection between BTS and iOMS or 3rd party tool
BTS vendor-specific file fault
Failure in trace session
No MME capacity assigned by Core Network
Maximum number of neighbor eNBs/cells exceeded
Maximum number of WCDMA neighbor cells is exceeded
Maximum number of WCDMA neighbor relations is exceeded
Maximum number of WCDMA neighbor relations per cell and carrier is exceeded
Neighbor cell ambiguity detected
Automatic cell recovery not possible
MFBI cell configuration conflict
PCI confusion detected
Phase error exceeds 5 us limit
X2 interface recovery failure
X2 interface setup failure
S1 interface setup failure
S1 interface recovery failure
Cell lost S1 availability
S1 eNB configuration update
RIM interface timeout
RIM interface error
System information broadcast parameters overflow
Diagnostic Files collected
High memory consumption
Critical bit toggling error
DSP platform fatal error
DSP application fatal error
Externally triggered DSP fatal error
BTS booted at $date due to $RCause
BTS reset required
BFD group $bfdGrpId down
LOF on unit $U, interface $IF
LOS on unit $U, [Ethernet] interface $IF
Dead Peer Detected
Missing or non-compliant SFP module on unit $U, interface $I
Synchronization lost
$Protocol Timing source lost [on unit $U] [, interface $IF]
CRL update failure
Link OAM loopback inserted on unit $U, interface $F by $P peer
Link OAM link lost on unit $U, interface $F
Link OAM critical link event $E on unit $U, interface $F
SFP HW Failure
EBER on unit $U, interface $IF
LOMF on slot $U, interface $IF
AIS on unit $U, interface $IF
RDI on unit $U, interface $IF
Transport module missing: $unit
CCM fault level $ prio $p cause $c
ETH AIS fault interface $IF level $l mac $x
Five failed logins to FTM due to wrong user name or password
Automatic BTS Operator Certificate retrieval unsuccessful
BFD $session down, ingress, $sourceIP to $destinationIP
BFD $session down, egress, $sourceIP to $destinationIP
Auto-negotiation mismatch, on unit $U, Ethernet interface $IF
TWAMP RTT Threshold Crossed
TWAMP PLR Threshold Crossed
NTP server is not accessible
Vendor BTS certificate is about to expire
BTS and/or peer trust anchor expired or due to expire
FTM Toggling <Fault name>
SyncE SSM Timed Out on unit $UID, interface $IF
SyncE Quality Level Degraded on unit $UID, interface $IF
ToP master service $IP unusable
Dup Addr on {duplicateIpv6Address} {VID: id}
Unsupported HW device
IPsec emergency bypass active
IP Traffic Capturing Ongoing [port $port,] [mac $m]
IPsec tunnel switchover
Fault Name in release RL60 Used in Product
Unit temperature is high Base Station
Unit SW download failed Base Station
Difference between BTS master clock and reference frequency Base Station
No connection to unit Base Station
Unit initialization failure Base Station
Unit synchronization failed Base Station
Incompatible SW version detected Base Station
Incompatible SW version detected Base Station
BTS time not corrected Base Station
Base Station
File corrupted in SW download Base Station
Base Station
Unit blocked Base Station
Cell blocked Base Station
BTS blocked Base Station
Base Station
POST test failed Base Station
Unknown HW resource Base Station
Unit not supported by current BTS SW version Base Station
Flash operation failure Base Station
Fault between FSM and FSP because of the lack of RP1 clock Base Station
Fatal OSE Error Base Station
Antenna link is down Base Station
[User defined] Base Station
BTS file error Base Station
Communication failure Base Station
Invalid frequency channel for the BTS HW Base Station
Baseband bus configuration of <x> was rejected Base Station
Not able to synchronize baseband bus with <x> Base Station
Base Station
Oven oscillator heating failure Base Station
BTS master clock tuning failure Base Station
Oven oscillator clock missing Base Station
Transmission parameters missing Base Station
Starting temperature below minimum Base Station
Mast Head Amplifier fault above current window, <line> Base Station
Mast Head Amplifier fault below current window, <line> Base Station
Antenna line failure Base Station
VSWR major alarm Base Station
VSWR minor alarm Base Station
Low noise amplifier failure Base Station
Base Station
Base Station
RET Antenna control failure Base Station
Antenna line device HW failure Base Station
Base Station
SW corrupted Base Station
Faulty configuration of system modules Base Station
Heating element not working Base Station
BTS config error (not enough HW for LCR) Base Station
Base Station
MHA unit operation failure Base Station
Antenna Line Device Operation Failure Base Station
SRAM operation failure Base Station
SRAM operation failure Base Station
Base Station
2M external reference missing Base Station
RF Module configuring failed Base Station
RF Module critical file not found Base Station
RF Module file not found Base Station
Frame clock missing Base Station
RF BB bus synchronization error Base Station
RF BB bus configuration error Base Station
RF BB bus connection transmission error Base Station
TX out of order Base Station
RF Module gain adjusting failure Base Station
RF Module filter input power missing Base Station
RX out of order Base Station
RF Module out of order Base Station
RF Module power output faulty Base Station
No feedback signal Base Station
Transmission quality deteriorated Base Station
Temperature too low (Heating ongoing) Base Station
Unit unidentified Base Station
Configuration file corrupted Base Station
Post test failed Base Station
Module Clock faulty Base Station
RF Power decreased Base Station
FPGA SW update failed Base Station
RF Module blocked Base Station
No module fan detected Base Station
Cooling fan broken: <X> Base Station
Cooling fan has reduced from the set speed Base Station
Cooling fan is over speeding Base Station
Unit (module) temperature is high Base Station
Unit (module) dangerously overheating Base Station
Pipe dangerously overheating Base Station
Increased BER detected on the optical connection to Radio Module Base Station
Critical BER detected on the optical connection to Radio Module Base Station
Antenna line switched off Base Station
RP3 routing collisions are detected on FR module Base Station
Optical Interface faulty Base Station
Optical Interface faulty Base Station
Receiving failure in Optical Interface Base Station
10b8b coding error in optical interface device <opt link/RP3> Base Station
Synchronization failure in Optical Interface <opt link/RP3 link> Base Station
#N/A Base Station
Optical Interface Data/Control/Ethernet Buffer Full Base Station
Optical Interface Data/Control/Ethernet Buffer Full Base Station
OIC MCU Buffer Full Base Station
Frame clock deviation fault Base Station
BB bus reception error (summing device) Base Station
BB bus transmission error Base Station
Address mismatch in summing Base Station
Synchronization error in RP1 receiver Base Station
Synchronization error in RP1 receiver Base Station
Buffer over/underflow in clock crossing logic Base Station
Firmware SW mismatch Base Station
BB bus message in the wrong slot Base Station
Message routing problem in receiver (RX) Base Station
Summing not enabled for message type Base Station
Transmission rule collision in Muksu Base Station
Overload collision in transmitter Base Station
System Module failure Base Station
Failure in replaceable baseband unit Base Station
Base Station
Base Station
Base Station
BTS reference clock missing Base Station
Incoherency in cell configuration Base Station
BTS reset required Base Station
TX failure in MIMO Base Station
Power level not supported Base Station
GPS Receiver alarm: control interface not available Base Station
SRIO chain configuration was rejected Base Station
Master unit has lost connection to the slave unit Base Station
Internal MTU configuration failure Base Station
Toggling: <Fault name> Base Station
BTS is uncommissioned Base Station
Invalid configuration file Base Station
Radio master conflict Base Station
Base Station
Filter unit operation failed Base Station
Base Station
Antenna line faulty Base Station
Antenna line operation degraded Base Station
RS485 IUANT port failure Base Station
Module dangerously overheating Base Station
Parallel RP3-01 link length mismatch Base Station
Fan vendor not detected Base Station
Distributed site support not enabled Base Station
FSP overheating Base Station
Cooling fan broken Base Station
Cooling fan speed decreased Base Station
Cooling fan is over speeding Base Station
SW fallback Base Station
File System access failed Base Station
Cell power failure Base Station
BTS reset time increased Base Station
Summing service default initialization failed Base Station
Peer system module connection lost Base Station
Synchronization master missing Base Station
GPS receiver alarm: not tracking satellites Base Station
GPS receiver alarm: survey in progress Base Station
GPS receiver alarm: no stored position Base Station
GPS receiver alarm: position questionable Base Station
GPS receiver alarm: EEPROM invalid Base Station
DC voltage administratively disabled Base Station
3GPP/AISG communication administratively disabled Base Station
Validation of signed file failed Base Station
Base Station
#N/A Base Station
#N/A Base Station
Unit initialization failure Base Station
#N/A Base Station
Phich Power Boost not applied Base Station
#N/A Base Station
GTP-U Path Failure Base Station
Transport layer connection failure in S1 interface Base Station
Transport layer connection failure in X2 interface Base Station
S1 SCTP path failure Base Station
Incorrect radio network parameters Base Station
Cell configuration data distribution failed Base Station
Cell reconfiguration data distribution failed Base Station
Failure in connection between BTS and iOMS or 3rd party tool Base Station
BTS vendor-specific file fault Base Station
Failure in trace session Base Station
No MME capacity assigned by Core Network Base Station
Maximum number of neighbor eNBs/cells exceeded Base Station
#N/A Base Station
#N/A Base Station
#N/A Base Station
Neighbor cell ambiguity detected Base Station
Automatic cell recovery not possible Base Station
MFBI cell configuration conflict Base Station
#N/A Base Station
#N/A Base Station
X2 interface recovery failure Base Station
X2 interface setup failure Base Station
S1 interface setup failure Base Station
S1 interface recovery failure Base Station
Cell lost S1 availability Base Station
S1 eNB configuration update Base Station
RIM interface timeout Base Station
RIM interface error Base Station
System information broadcast parameters overflow Base Station
Technical log buffer freezing Base Station
High memory consumption Base Station
Critical bit toggling error Base Station
#N/A Base Station
#N/A Base Station
#N/A Base Station
BTS booted at $date due to $RCause Base Station
BTS reset required Base Station
BFD group $bfdGrpId down Base Station
LOF on unit $U, interface $IF Base Station
LOS on unit $U, [Ethernet] interface $IF Base Station
Dead Peer Detected Base Station
Missing or non-compliant SFP module on unit $U, interface $I Base Station
Synchronization lost Base Station
$Protocol Timing source lost [on unit $U] [, interface $IF] Base Station
CRL update failure Base Station
Link OAM loopback inserted on unit $U, interface $F by $P peer Base Station
Link OAM link lost on unit $U, interface $F Base Station
Link OAM critical link event $E on unit $U, interface $F Base Station
SFP HW Failure Base Station
EBER on unit $U, interface $IF Base Station
LOMF on slot $U, interface $IF Base Station
AIS on unit $U, interface $IF Base Station
RDI on unit $U, interface $IF Base Station
Transport module missing: $unit Base Station
CCM fault level $ prio $p cause $c Base Station
ETH AIS fault interface $IF level $l mac $x Base Station
Five failed logins to FTM due to wrong user name or password Base Station
Automatic BTS Operator Certificate retrieval unsuccessful Base Station
BFD $session down, ingress, $sourceIP to $destinationIP Base Station
BFD $session down, egress, $sourceIP to $destinationIP Base Station
Auto-negotiation mismatch, on unit $U, Ethernet interface $IF Base Station
TWAMP RTT Threshold Crossed Base Station
TWAMP PLR Threshold Crossed Base Station
NTP server is not accessible Base Station
Vendor BTS certificate due to expire Base Station
BTS and/or peer trust anchor expired or due to expire Base Station
FTM Toggling <Fault name> Base Station
SyncE SSM Timed Out on unit $UID, interface $IF Base Station
SyncE Quality Level Degraded on unit $UID, interface $IF Base Station
ToP master service $IP unusable Base Station
Dup Addr on {duplicateIpv6Address} {VID: id} Base Station
Unsupported HW device Base Station
IPsec emergency bypass active Base Station
IP Traffic Capturing Ongoing [port $port,] [mac $m] Base Station
#N/A Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Used in Product in issue 01 Used in Product in release RL60
Base Station Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station #N/A
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Base Station #N/A
Detecting Unit
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FCM, FCT
FCM, FCT
FCM
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT, FTM; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FSP, FBB
Flexi BTS FDD, Flexi BTS TDD: FSP, FBB; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT, FSP, FBB; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FCM, FCT
FCM
FR
FR
FR
Flexi BTS FDD, Flexi BTS TDD: FR; Flexi Zone Micro: Flexi Zone Micro BTS
FR
FR
FR
FR
RET
RET
RET
RET
RET
FR, RET, MHA
MHA, RET
FCM, FCT
FCM, FCT
FCM
FCM, FCT
MHA in AISG mode
MHA in AISG mode
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD: FCM; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD: FCM; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT. FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM
FCM
FCM, FCT, FBB
Flexi BTS FDD, Flexi BTS TDD: FCT; Flexi Zone Micro: Flexi Zone Micro BTS
FCM
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
Flexi BTS FDD, Flexi BTS TDD: FSM; Flexi Zone Micro: Flexi Zone Micro BTS
FCT, FBB
Flexi BTS FDD, Flexi BTS TDD: FSM, FR; Flexi Zone Micro: Flexi Zone Micro BTS
FSM, FR
FCM, FCT
FCM
FCM, FCT
FR
FR
FR
FR
FCM
FCM, FCT
FCM, FCT
FCM, FCT
FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCT, FBB
FCM, FCT
FCM, FCT
FCM/FCT
FCM/FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FBBC
Flexi BTS FDD,Flexi BTS TDD,Flexi Zone Micro FDD,Flexi Zone Micro TDD
Flexi BTS FDD, Flexi BTS TDD: FCM,FCT; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FSP, FBB
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT; Flexi Zone Micro FDD, Flexi Zone Micro TDD: Flexi Zone Micro BTS
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: LNADJ; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD: FCT; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FCM, FST; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FCM/FCT; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: FZC, FZAP
Flexi BTS FDD, Flexi BTS TDD: FSP; Flexi Zone Micro: Flexi Zone Micro BTS
FTLB, FTIB, FSM, FTIF
Flexi BTS FDD, Flexi BTS TDD: FTLB, FTIB, FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FTLB, FTIB, FSM, FTIF, FSIH; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FIIB, FILB, FSIB, FTIA, FTIB, FTLB, FTFB, FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS
FSM, FTIF
Flexi BTS FDD, Flexi BTS TDD: FTIB, FTFB, FTLB, FSM, FSI, FTIF, FIIF; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FTIB, FTFB, FTLB; Flexi Zone Micro: Flexi Zone Micro BTS
FSM, FTIF
Flexi BTS FDD, Flexi BTS TDD: FSM, FSI, FTIF, FIIF, FTLB, FTIB; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS
FSM
FTLB, FTIB, FSM, FTIF, FSIH; Flexi Zone Micro BTS.
FCM,FCT
FCT
FCM, FCT
FCM
FCM
FCT, FBB
FCM, FCT
FSM
FCM
FCM [FSMr2] / FCT [FSMr3]
FCM [FSMr2] / FCT [FSMr3]
FCM / FCT
FRx/LTX
FCM, FCT
FCM, FCT
FSM, FR
FSM, FR
FSM, FR
FSM, FR
FSM
FSM, Antenna Line Device itself
FSM, FR
FSM
FSM
FCM
FCM/FCT
FCM
FCM, FCT
FCM
FCM/FCT
(FSMr2): FCM, (FSMr3): FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM/FCT
Detecting Unit in issue 01
FCM, FCT
Flexi BTS FDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FCM, FCT
FCM, FCT
FCM
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Controller, Flexi Zo
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Controller, Flexi Zo
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT, FTM; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FCM, FCT
FSP, FBB
Flexi BTS FDD, Flexi BTS TDD: FSP, FBB; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT, FR
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD: FCM, FCT Flexi Zone: FZC, FZAP
Flexi BTS FDD, Flexi BTS TDD: FCM, FCT, FSP; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FCM, FCT
FCM, FCT
FCM
FR
FR
FR
FR
FR
FR
FR
RET
RET
RET
RET
RET
FR, RET, MHA
MHA, RET
FCM, FCT
FCM, FCT
FCM
FCM, FCT
MHA in AISG mode
MHA in AISG mode
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FCM; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
Flexi BTS FDD, Flexi BTS TDD: FCM; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: FR; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Access Point
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FR
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT. FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM
FCM
FCM, FCT, FBB
FCM
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCM, FCT, FBB
FCT, FBB
FSM, FR
FSM, FR
FCM, FCT
FCM
FCM, FCT
FR
FR
FR
FR
FCM
FCM, FCT
FCM, FCT
FCM, FCT
FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCT, FBB
FCM, FCT
FCM, FCT
FCM/FCT
FCM/FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FBBC
Flexi BTS FDD,Flexi BTS TDD,Flexi Zone Micro FDD,Flexi Zone Micro TDD
Flexi BTS FDD, Flexi BTS TDD: FCM,FCT; Flexi Zone Micro: Flexi Zone Micro BTS
FCM, FCT
FSP, FBB
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
FCM, FCT
Flexi BTS FDD, Flexi BTS TDD: LNADJ; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD: FCT; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FCM, FST; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FCM/FCT; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FSP; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FTLB, FTIB, FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Acces
Flexi BTS FDD, Flexi BTS TDD: FTLB, FTIB, FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS; Flexi Zone: Flexi Zone Acces
Flexi BTS FDD, Flexi BTS TDD: FTLB, FTIB, FSM, FTIF, FSIH; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FIIB, FILB, FSIB, FTIA, FTIB, FTLB, FTFB, FSM, FTIF; Flexi Zone Micro: Flexi Zone Micro BTS
FSM, FTIF
Flexi BTS FDD, Flexi BTS TDD: FTIB, FTFB, FTLB, FSM, FSI, FTIF, FIIF; Flexi Zone Micro: Flexi Zone Micro BTS
Flexi BTS FDD, Flexi BTS TDD: FTIB, FTFB, FTLB; Flexi Zone Micro: Flexi Zone Micro BTS
FSM, FTIF
Flexi BTS FDD, Flexi BTS TDD: FSM, FSI, FTIF, FIIF, FTLB, FTIB; Flexi Zone Micro: Flexi Zone Micro BTS
FSM
FTLB, FTIB, FSM, FTIF, FSIH; Flexi Zone Micro BTS.
Detecting Unit in release RL60 Source
FCM, FCT FCM, FCT, FSP, FTM, FBB_x000D_
FCM/FCT Flexi BTS FDD, Flexi BTS TDD:_x000D_
FCM -Flexi FCM_x000D_
BTS FDD:_x000D_
-- FCT_x000D_ FCM_x000D_
FCM/FCT --- FSP_x000D_ FSP_x000D_
-Flexi FCT_x000D_
FBB_x000D_
FCM/FCT -_x000D_ FBB_x000D_
BTS FDD, Flexi BTS TDD:_x000D_
-FCM_x000D_
-Flexi FTM_x000D_
DSP_x000D_
FCM/FCT FCM,
-FCT_x000D_ Zone
FCT, Micro
MHA_x000D_ FDD, Flexi Zone Micro
FSP, FBB
_x000D_
TDD:_x000D_
FCM -_x000D_
FCM,
Flexi RET_x000D_
FCT, Micro
Zone FR, FSP,
FDD, FTM
Flexi Zone Micro
-- FSP_x000D_ FR_x000D_
FCM TDD:_x000D_
Flexi
FCM Zone Micro FDD, Flexi Zone Micro
FCM / FCT -Flexi
TDD:_x000D_ FlexiBTS
Zone Micro BTS
FDD, Flexi BTS TDD:_x000D_
Flexi
-FCM,FCT_x000D_ Zone Micro BTS
FCM_x000D_
- FCT _x000D_
FCM/FCT FCM,
_x000D_ FCT, FR
Flexi Zone MicroFlexi
BTS FDD, FDD,BTSFlexi Zone Micro
TDD:_x000D_
FSM -TDD:_x000D_
FR FCM_x000D_
- FCT_x000D_ FSP
FSM LCR
- FR_x000D_
FCM/FCT _x000D_
Flexi BTS FDD, Flexi BTS TDD:_x000D_
-Flexi
Flexi Zone FCM_x000D_MicroFlexi
BTS FDD, FDD,BTSFlexi Zone Micro
TDD:_x000D_
-TDD:_x000D_
-Flexi FCT_x000D_
FCM_x000D_
FCM/FCT, FT -- FSP
_x000D_ BTS FDD, Flexi BTS TDD:_x000D_
-Flexi FCT_x000D_
FSP_x000D_
FCM/FCT -- FR_x000D_ ZoneFDD,
BTS MicroFlexi
FDD,BTSFlexi Zone Micro
TDD:_x000D_
-TDD:_x000D_ DSP_x000D_
FSP_x000D_
FCM/FCT -- FSP_x000D_
FSP, FBB, FR, FTM
-- FTM_x000D_ Flexi Zone Micro BTS
FBB_x000D_
FBB_x000D_
FCM/FCT --Flexi FCM_x000D_
FR_x000D_
_x000D_
-Flexi FCT_x000D_
FCM_x000D_
FCM/FCT -_x000D_ FTM_x000D_
-_x000D_
-Flexi FBB_x000D_
FCT_x000D_
FCM_x000D_
FCM/FCT -_x000D_ ZoneFDD,
BTS
FSP_x000D_MicroFlexi
TDD:_x000D_
-Flexi
TDD:_x000D_
-Flexi Zone Micro FDD, Flexi Zone Micro
FCT_x000D_
FCM_x000D_
FCM/FCT _x000D_
-TDD:_x000D_ ZoneFDD,
BTS
FSP_x000D_MicroFlexi
TDD:_x000D_
-TDD:_x000D_ FSP_x000D_
FCT_x000D_
FCM/FCT --Flexi
_x000D_
Flexi Zone
FCM_x000D_
Flexi Zone
BTS
Flexi
--TDD:_x000D_
Micro
Micro
FDD,
Zone
FSP_x000D_
FDD,
BTS
Flexi
Micro BTS
Flexi Zone Micro
BTS TDD:_x000D_
-Flexi FSP
FCT_x000D_
Zone
FCM_x000D_Micro FDD, Flexi Zone Micro
FSP _x000D_
FSP,FBB FSP
--TDD:_x000D_
FSP_x000D_
Flexi FCT_x000D_
Zone Micro FDD, Flexi Zone Micro
FSP _x000D_
FSP, FSPFBB
-TDD:_x000D_
FSP_x000D_
FSPC Flexi
_x000D_
Flexi Zone Micro FDD, Flexi Zone Micro
FSPBTS FDD, Flexi BTS TDD:_x000D_
-TDD:_x000D_
FCM, FCT -Flexi Zone Micro FDD, Flexi Zone Micro
FSP_x000D_
FCM,FCT,FR_x000D_
--TDD:_x000D_
FSP
FBB_x000D_
FCM, FCT FCM,FCT,FR_x000D_
- FSP
_x000D_
FCM, FCT Flexi Zone Micro FDD, Flexi Zone Micro
FCM,FCT,FR_x000D_
FCM, FCT TDD:_x000D_
FCM,FCT,FR_x000D_
- FSP_x000D_
FCM [FSMr2] / FCT [FSMr3] FCM, FCT, FSP (rel.2), FR
FCM -LCR FCM_x000D_
- FCT_x000D_
FCM/FCT, FSP -Flexi BTS FDD, Flexi BTS TDD:_x000D_
FTM_x000D_
FCM/FCT, FSP -Flexi
- FCM_x000D_ FSP_x000D_
-- FCT_x000D_ FR_x000D_
FSP_x000D_
Flexi
-- FSP_x000D_ BTS FDD, Flexi BTS TDD:_x000D_
-FCM, FBB_x000D_
OptIF_x000D_
FCM_x000D_
FCM, FCT -- FR_x000D_ FCT _x000D_
MHA_x000D_
FBB_x000D_
-_x000D_
--Flexi FCT_x000D_
OptIF_x000D_
FCM/FCT _x000D_
_x000D_ RET_x000D_
--Flexi
_x000D_ FBB_x000D_
Zone Micro
FCM, FCT Flexi
FCM,
_x000D_
FCM_x000D_
Zone Micro FDD,
FCT_x000D_FDD, Flexi
Flexi Zone
Zone Micro
Micro
Flexi
-TDD:_x000D_ Zone
FCT_x000D_
TDD:_x000D_
_x000D_ Micro FDD, Flexi Zone Micro
FCM/FCT Flexi
-TDD:_x000D_
_x000D_FSP ZoneFDD,
BTS MicroFlexi
FDD,BTS
Flexi Zone Micro
TDD:_x000D_
--TDD:_x000D_
Flexi Zone Micro BTS
FTM_x000D_
FCM - FSP_x000D_
Flexi
FCM Zone Micro FDD, Flexi Zone Micro
FSP
-TDD:_x000D_
FCT_x000D_
FR, FF MHA
_x000D_
- FSP
FR, FF Flexi
MHA Zone Micro FDD, Flexi Zone Micro
Flexi Filter, FR TDD:_x000D_
Antenna line
- Flexi Zone Micro BTS
Flexi Filter, FR Flexi BTS FDD, Flexi BTS TDD:_x000D_
Flexi Filter, FR -Antenna
Antennaline
Line_x000D_
_x000D_
Flexi Filter RX1-n
TDD:_x000D_
TX1-n, RX1-n
-TX1-n
Antenna Line
_x000D_
TILT RX1-n
RET
TILT RET
TILT RET
TILT RET
TILT RET
FR, TILT RX1-n, TX1-n, RET, MHA
MHA, RET
FCM/FCT FR, FTM
FCM/FCT - FCM_x000D_
FCM -FCM
FCT
FCM, FCT LCR
MHA in AISG mode
AISG MHA MHA in AISG mode_x000D_
FSM FR, MHA AISG, RET
FSM Flexi BTS FDD:_x000D_
FSM -Flexi FCM_x000D_
BTS FDD:_x000D_
_x000D_
-Flexi FCM_x000D_
Flexi BTS
ZoneFDD,
MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
_x000D_
-TDD:_x000D_
FCM_x000D_
FCM/FCT FCM,
Flexi FCT
Zone Micro FDD, Flexi Zone Micro
-- FCT_x000D_
FSP
FRx/LTX TDD:_x000D_
FR
_x000D_
FRx/LTX -Flexi
FR FSPZone Micro FDD, Flexi Zone Micro
FRx/LTX TDD:_x000D_
FR
FRx / LTX FR, RX1-n
FRx / LTX FR, TX1-n, RX1-n
FRx/LTX FR, TX1-n, RX1-n
FRx/LTX FR, TX1-n
FRx/LTX Flexi BTS FDD, Flexi BTS TDD:_x000D_
FRx/LTX -Flexi TX1-n_x000D_
_x000D_
-TX1-n FR_x000D_
FRx/LTX Flexi Zone Micro FDD, Flexi Zone Micro
- TX1-n_x000D_
FRx/LTX TDD:_x000D_
Flexi
FRx/LTX FR ZoneLine
-FlexiAntenna
RX1-n_x000D_
Micro FDD, Flexi Zone Micro
_x000D_
TDD:_x000D_
FR Flexi Zone
Flexi BTS FDD,
MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
-- FR_x000D_
FR_x000D_
FRx/LTX TDD:_x000D_
TX1-n
-- Antenna Line
TX1-n_x000D_
-TX1-n
Antenna Line
FRx/LTX _x000D_
FRx/LTX Flexi
FR Zone Micro FDD, Flexi Zone Micro
FRx/LTX TDD:_x000D_
FR
- FR
FRx/LTX FR, TX1-n, RX1-n
FRx/LTX FR
FRx/LTX FR
FRM2/LTX TX1-n
FRM2/LTX FR
FRx/LTX FR
FR/RFSW FR
FR/RFSW FAN, FAN_GROUP
FR/RFSW FR
FR/RFSW RFM connected over OBSAI RP1
FR interface:_x000D_
TX1-n
FR_x000D_
FRx / LTX FR
_x000D_
FRx / LTX RRU
FR connected over CPRI Ir
FR interface:_x000D_
Antenna line
FR, TX1-n
FR FR
FCM, FCT OptIF
FCM, FCT OptIF
FCM, FCT OptIF
FCM, FCT OptIF
FCM, FCT OptIF
#N/A OptIF
FCM, FCT OptIF
FCM, FCT OptIF
FCM, FCT FCM, FCT, FBB
FCM, FCT FCM
FCM, FCT FSP, FBB, OptIf
FCM, FCT, FSP FCM, FCT, FBB
FCM, FCT FCM, FCT, FBB
FCM FCM
FCM FCM
FCM OptIf
FCT, FSP Flexi BTS FDD, Flexi BTS TDD:_x000D_
FCM, FCT -FSP,OptIF FCT_x000D_
_x000D_
FCM, FCT FSP,FBB,OptIF
FCM, FCT TDD:_x000D_
FCM,FCT,FBB
FCM, FCT -FCM,FCT,FBB FSP
FCM, FCT FCM,FCT,FBB
FSM Flexi BTS FDD, Flexi BTS TDD:_x000D_
FSM -FBB FSM_x000D_
_x000D_
FR
TDD:_x000D_
FSM/FAN, FR
-Flexi FlexiBTS
Zone Micro
FDD, BTS
Flexi BTS TDD:_x000D_
FSM -Flexi FSM_x000D_
-- FR_x000D_ FSM_x000D_
FCM Flexi
-_x000D_ BTS Line_x000D_
Antenna FDD, Flexi BTS TDD:_x000D_
FSM --FR, FCM_x000D_
LCR_x000D_
FSP,
Flexi
-- FCT_x000D_ ZoneFBB, FCM,
Micro FDD, FCT
Flexi Zone Micro
FSM TDD:_x000D_
LCR LCG_x000D_
_x000D_
_x000D_
-LCR
Flexi Flexi ZoneMicro
Micro BTS Flexi Zone Micro
FSM Flexi Zone Zone Micro FDD,
FDD, Flexi Zone Micro
FCM/FCT TDD:_x000D_
TDD:_x000D_
-- Flexi Flexi Zone
Zone Micro
GNSS_x000D_ Micro BTS_x000D_
BTS
FSM FSP
-_x000D_ LCR
FCM/FCT Flexi
Flexi BTS ZoneFDD,MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
FCM -TDD:_x000D_ FCM [FSMr2]_x000D_
Flexi BTS FDD, Flexi BTS TDD: _x000D_
-- FCT [FSMr3]_x000D_
FlexiBTS
Zone
FCM_x000D_ Micro BTS
FSM Flexi
-- FSP_x000D_ FDD, Flexi BTS TDD:_x000D_
All FCT_x000D_
units_x000D_
FCM / FCT -- FBB_x000D_
FSP_x000D_
_x000D_
-Flexi DSP_x000D_
FCM_x000D_
FCM / FCT -Flexi FBB_x000D_
BTS
ZoneFDD,MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
_x000D_
-_x000D_ FCT_x000D_
-TDD:_x000D_
FCM_x000D_
FCM FR
Flexi Zone Micro FDD, Flexi
_x000D_
-Flexi
-Flexi FlexiZone
FCT_x000D_
Zone Micro
MicroFDD,
BTS Flexi Zone
Zone Micro
Micro
TDD:_x000D_
Zone
BTS
TDD:_x000D_
_x000D_ Micro
FDD, FDD,
Flexi Flexi
BTS Zone Micro
TDD:_x000D_
Flexi Filter, External Filter, RFM FlexiFSP
-TDD:_x000D_
- FCM_x000D_
FSPZone Micro FDD, Flexi Zone Micro
TX1-n_x000D_
-RX1-n
FCT_x000D_
TDD:_x000D_
LCR
-- FSP_x000D_
FR -Antenna
FBB_x000D_
line
FR _x000D_
Antenna Line
Flexi Filter, FR Antenna
TDD:_x000D_line
FCM -FSP
FSP
FCM OptIF
FCT FAN1-n
FSM Optif
FCT FSP, FBB
FCT Fan/Fan group
FCT Fan/Fan group
FCT Fan/Fan group
FSMr2: FCM, FSMr3: FCT Flexi BTS FDD, Flexi BTS TDD:_x000D_
FSMr2: FCM, FSMr3: FCT 4082:_x000D_
-4082:_x000D_ FSMr2: FCM, FSP_x000D_
FSMr2: FCM, FSMr3: FCT -Flexi BTS FDD, Flexi BTS TDD:_x000D_
FSMr3:
-4082:_x000D_ FSMr2: FCT_x000D_
FCM, FSP_x000D_
FCM, FCT _x000D_
Flexi
-- FSMr3: BTSFCT_x000D_
-4083:_x000D_ FSMr2:
FCM_x000D_FCM, FSP_x000D_
FSM _x000D_
LCR
-- FSMr3:
4083:_x000D_ FSMr2: FCT_x000D_
FCT_x000D_FCM_x000D_
FSM -_x000D_
-- FCM_x000D_
_x000D_ FSMr3: FCT_x000D_
4083:_x000D_
-Flexi FSMr2:
FCTFBB FCM_x000D_
FCT _x000D_
-FCT, Zone
FSMr3: Micro FDD, Flexi Zone Micro
FCT_x000D_
-TDD:_x000D_
4085: FSMr2:(forFCM_x000D_
FSMr3
FCM, FCT _x000D_
FCM,
-- FSMr3: FCT, Optif only)_x000D_
FCT_x000D_
4085: FSMr3:
FSP FCT_x000D_
(for FSMr3
FCM _x000D_
FCM,
_x000D_ FCT, OptIF only)_x000D_
-4085: FSMr3: FCT_x000D_
(for FSMr3 only)_x000D_
FCM/FCT Flexi
_x000D_ Zone
BTS MicroFlexi
FDD, FDD, Flexi
BTS Zone Micro
TDD:_x000D_
-TDD:
-Flexi FSMr3: FCT_x000D_
_x000D_
GNSS_x000D_
FCM/FCT GNSS
_x000D_ Zone Micro FDD, Flexi Zone Micro
-TDD: 4082:
_x000D_ FSP_x000D_
_x000D_
FCM/FCT Flexi
GNSS
-- 4083:
Flexi Zone
Zone Micro
Flexi ZoneFDD,
Micro Flexi
Micro
FDD, Zone
Zone Micro
BTS_x000D_
Flexi Micro
TDD: 4082: FSP_x000D_
_x000D_
FCM/FCT -- 4085:
TDD:_x000D_
GNSS Flexi Zone Micro BTS
-- 4083: Flexi
4082:Zone Zone Micro BTS_x000D_
FSP_x000D_
FCM/FCT -- Flexi
4085:
GNSS Flexi Micro
4083: Flexi Zone
BTS BTS
Zone Micro
Micro BTS_x000D_
FCM, FCT -Antenna
4085: Flexi
LineZone Micro BTS
FCM, FCT Antenna Line
FCT Flexi BTS FDD, Flexi BTS TDD:_x000D_
-FCM, FCT_x000D_
FCT
_x000D_
#N/A FBBC
#N/A TDD:_x000D_
FCM/FCT -Flexi FSPBTS FDD, Flexi BTS TDD:_x000D_
FCM_x000D_
-- FCT_x000D_ FCM_x000D_
#N/A GNSS
_x000D_
- FCT_x000D_
FSM Flexi
_x000D_ Zone MicroFlexi
BTS FDD, FDD,BTS
Flexi Zone Micro
TDD:_x000D_
#N/A TDD:_x000D_
LCR_x000D_
Flexi
LCR Zone Micro FDD, Flexi Zone Micro
-TDD:_x000D_
_x000D_ Flexi Zone Micro BTS
FCM,FCT GTP-U
Flexi
- FlexiZone ZoneMicro
MicroFDD,
BTS Flexi Zone Micro
FCM/FCT TDD:_x000D_
LNMME
FCM,FCT LCR
LNADJ
FCM/FCT LNMME
FCM,FCT -LCR FCM_x000D_
- FCT_x000D_
FCM,FCT LCR
_x000D_
FCM/FCT Flexi BTS ZoneFDD,
MicroFlexi
FDD,BTS
Flexi Zone Micro
TDD:_x000D_
FCM/FCT -TDD:_x000D_
FCM_x000D_
Flexi
-- FCT_x000D_ Zone Micro BTS
FCM_x000D_
FCM, FCT Flexi
-- FCT_x000D_
FCM_x000D_
FCM Flexi
_x000D_ ZoneFDD,
BTS MicroFlexi
FDD,BTS
Flexi Zone Micro
TDD:_x000D_
--TDD:_x000D_
FCT_x000D_
FCM_x000D_
FCM/FCT Flexi
_x000D_ ZoneFDD,
BTS MicroFlexi
FDD,BTS
Flexi Zone Micro
TDD:_x000D_
--TDD:_x000D_
FCT_x000D_
FCM_x000D_
#N/A Flexi
FCM,
_x000D_ Zone
FCT Micro FDD, Flexi Zone Micro
-TDD:_x000D_
FCT_x000D_
#N/A Flexi
FCM,
_x000D_Zone
FCT Micro FDD, Flexi Zone Micro
TDD:_x000D_
#N/A Flexi
FCM,ZoneFCT Micro FDD, Flexi Zone Micro
-TDD:_x000D_
FSP LCR
FCT LCR
LNADJ LNADJ
#N/A LNCEL
#N/A Flexi BTS FDD:_x000D_
FCM,FCT -LNADJ
FCM, FCT_x000D_
_x000D_
FCM,FCT LNADJ
Flexi Zone Micro:_x000D_
FCM,FCT -LNMME
FCM,FCT LNMME
FSM Flexi BTS FDD, Flexi BTS TDD:_x000D_
FCM LCR_x000D_
_x000D_
-Flexi FCM_x000D_
FCM,FCT Flexi BTS
ZoneFDD,
MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
-LNADJG_x000D_ FCT_x000D_
FCM,FCT TDD:_x000D_
_x000D_
Flexi
lcrId
LNADJG_x000D_ Zone
of the Micro
cell FDD, Flexi Zone Micro
FSP Flexi
LCR
TDD:_x000D_ Zone Micro FDD, Flexi Zone Micro
_x000D_
TDD:_x000D_
FSP, FSM -Flexi
Flexi FlexiBTS
Zone
Zone Micro
FDD,
MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro
-- FCM FCM/FCT_x000D_
FSM TDD:_x000D_
_x000D_
-FSP,FBB Flexi Zone Micro
FCM_x000D_
FSP Flexi Zone Micro FDD, Flexi Zone Micro
- FCT_x000D_
#N/A TDD,
Flexi
- FSP_x000D_ FlexiFDD,
BTS Zone:_x000D_
#N/A -Flexi FSP
FSP_x000D_
- FBB_x000D_ BTS FDD, Flexi BTS TDD:_x000D_
--_x000D_ FBB_x000D_
FSP_x000D_
#N/A Flexi
-Flexi
-Flexi Zone Micro FDD, Flexi Zone Micro
FBB_x000D_
FSP_x000D_
FTLB, FTIB, FSM, FTIF NE-FTM-1 Zone Micro FDD, Flexi Zone Micro
TDD:_x000D_
_x000D_
-TDD:_x000D_
FBB_x000D_
FTLB, FTIB, FSM, FTIF -FTM FSPZone Micro FDD, Flexi Zone Micro
Flexi
_x000D_
-TDD:_x000D_
FSP
FTLB, FTIB, FSM, FTIF Flexi Zone Micro FDD, Flexi Zone Micro
BFDGRP
-TDD:_x000D_
FSP
FTLB, FTIB, FSM, FTIF PPTT
- FSP
FTLB, FTIB, FSM, FTIF ETHLK
FTLB, FTIB, FSM, FTIF IKESA
FTLB, FTIB, FSM, FTIF STPG
FTLB, FTIB, FSM, FTIF STPG
FTLB, FTIB, FSM, FTIF CERTH
FIIB, FILB, FSIB, FTIA, FTIB, FTLB, FTFB, FSM, FTIF ETHLK
FSM, FTIF UNIT
FTLB, FTIB, FSM, FTIF OAMMA, OAMMD
FTIB, FTFB, FTLB, FSM, FSI, FTIF, FIIF OAMMEP
FTLB, FTIB, FSM, FTIF NE-FTM-1
FTLB, FTIB, FSM, FTIF BFD
FTLB, FTIB, FSM, FTIF BFD
FTIB, FTFB, FTLB ETHLK
FTLB, FTIB, FSM, FTIF TWAMP
FTLB, FTIB, FSM, FTIF TWAMP
FSM, FTIF INTP
FTLB, FTIB, FSM, FTIF FTM
STPG
STPG
FSM,FSI,FTIF,FIIF,FTLB,FTIB TOPM_x000D_
FSM,FTIF IEIF,IVIF_x000D_
FSM UNIT
FTLB, FTIB, FSM, FTIF IPSECC
FSM,FTIF IPNO
#N/A IPSECC
FR
FSP, FBB
FCM, FCT, FR, FTM, FSP
-FAN TX_x000D_
- RX_x000D_
FAN
_x000D_
Flexi BTSZoneFDD,
MicroFlexi
FDD,BTS
Flexi Zone Micro
TDD:_x000D_
-TDD:_x000D_
FCM_x000D_
- FCT_x000D_
-- TX1-n_x000D_
FCT_x000D_
FBB
LCR
RX1-n_x000D_
- FR_x000D_
_x000D_
FCM, FCT
Flexi
FSM Zone Micro FDD, Flexi Zone Micro
TDD:_x000D_
FR
- FSP
FCM [FSMr2]/FCT [FSMr3]
FCM [FSMr2]/FCT [FSMr3]
FlexiBTS: FCM (FSMr2) / FCT (FSMr3)
FR
OptIF
OptIF
FSM, FR
FSM, FR
FSM, FR
FSM, FR, FT
FSM, FCT, FR, FT, FSP, Faraday
FR, MHA, TILT, EFIL
FF, AISG MHA
FTM
LCR
FSP
Filter, FR, FTM/FCT
OptIF
Antenna line
RX, TX
FSP
FSMr2: FCM, FSP MCU
FSMr3: FCT
FCM, FCT
FCM, FCT
LCR
RF
Source in issue 01 Source in release RL60
FCM, FCT, FSP, FTM, FCM, FCT, FSP, FTM_x000D_
FBB_x000D_
Flexi BTS FDD, Flexi BTS FCM/FCT, FSP, FR, Faraday / Nyquist
TDD:_x000D_
Flexi BTS FDD:_x000D_ FCM_x000D_
-- FCM_x000D_ FCM_x000D_ _x000D_
--- FCT_x000D_ FSP_x000D_
FCT_x000D_
FSP, FT, FF, MHA, TILT, FR, FA, extension
-FSP_x000D_
-_x000D_ FBB_x000D_
FSP_x000D_ FSM_x000D_
FCM/FCT, FSP_x000D_
-FBB_x000D_
-FCM, FTM_x000D_
FBB_x000D_ _x000D_
_x000D_
Flexi
-_x000D_ Zone
FCT, Micro
MHA_x000D_ FDD, Flexi
FSP, FBB FCM/FCT, FSP, DSP
-Zone DSP_x000D_
Micro TDD:_x000D_
-Flexi
FCM,
_x000D_ RET_x000D_
FCT, Micro
Zone FR, FSP,
FDD, FTM
Flexi FCM, FR, FF, FA, FSP, FTM
-- FSP_x000D_ FR_x000D_
Flexi
Zone
FCM Zone
Micro Micro FDD,
TDD:_x000D_ Flexi FCM, FR, FF, FA, FSP, FTM
-Zone
Flexi BTS FDD, Flexi BTS FSP Micro TDD:_x000D_ FCM/FCT _x000D_
-TDD:_x000D_ Flexi Zone Micro BTS
FCM,FCT_x000D_
- FCM_x000D_
FCM,
- FCT FCT, FR
_x000D_ FlexiBTS: FCM (FSMr2) / FCT (FSMr3),
_x000D_
Flexi BTS FDD, Flexi BTS FR
Flexi
FR Zone Micro FDD, Flexi
TDD:_x000D_ FR
-Zone Micro TDD, Flexi
FCM_x000D_
LCR
-Zone:_x000D_ FCT_x000D_ LCR
- FR_x000D_
Flexi FSPBTS FDD, Flexi BTS FCM (FSMr2), FCT (FSMr3)
_x000D_
TDD:_x000D_
Flexi BTS FDD, Flexi BTS
-Flexi
TDD:_x000D_ Zone Micro FDD, Flexi
FCM_x000D_
Flexi
-Zone BTS
MicroFDD,
FCT_x000D_ Flexi BTS
TDD:_x000D_ FSP, DSP, FT, FCM/FCT
-TDD:_x000D_ FCM_x000D_
-- FSP
_x000D_
FCT_x000D_ - FSP (fixed and plug-in cards)
-TDD:_x000D_
Flexi FSP_x000D_
Zone FR,
Micro FDD, Flexi -All
FR
-FSP,
--Zone FR_x000D_
FBB,
DSP_x000D_ FTM possible units.
Micro
FSP_x000D_ TDD:_x000D_ - FTM
---Flexi FSP_x000D_
FTM_x000D_
BTS
Flexi FDD,
Zone
FBB_x000D_ Flexi BTS
Micro -FCM/FCT,
FF FSP
-TDD:_x000D_
-Flexi FBB_x000D_
FCM_x000D_
-BTS_x000D_
_x000D_ FR_x000D_
BTS FDD, Flexi BTS FCM/FCT, FSP
-TDD:_x000D_
-_x000D_ FCT_x000D_
FCM_x000D_
FTM_x000D_
_x000D_
Flexi
--_x000D_ BTS FDD, Flexi BTS
FBB_x000D_
FCT_x000D_ FCM/FCT, FSP
Flexi
Flexi
TDD:_x000D_ Zone:
FCM_x000D_
Zone _x000D_
Micro FDD,BTSFlexi
-_x000D_
Flexi
-Flexi FSP_x000D_
BTS
Flexi FDD,
Zone
Zone
FCT_x000D_MicroFlexi
FDD, Flexi FCM/FCT, FSP
Zone
-Flexi Micro
FCM_x000D_
Zone TDD:_x000D_
Micro FDD, Flexi
-_x000D_
TDD:_x000D_
Controller_x000D_
Zone
-Flexi MicroFDD,
FSP_x000D_
BTS
FSP_x000D_
FCT_x000D_ TDD:_x000D_
Flexi BTS FCM/FCT, FSP
Zone
-Flexi
--FSP,FBB Micro
Zone
FCM_x000D_
Flexi Zone TDD,
Micro Flexi
FDD,
Access
Micro Flexi
Point
_x000D_
TDD:_x000D_
Zone:_x000D_
-Zone Flexi
FSP_x000D_
Micro
FCT_x000D_ Micro BTS
ZoneTDD:_x000D_
BTS FSP
-Flexi
_x000D_ Zone Micro FDD, Flexi
FCM_x000D_
-FSP,
-Zone FSP
FSP_x000D_
FBB
MicroMicro
FCT_x000D_ TDD:_x000D_ FSP
Flexi
_x000D_ Zone FDD, Flexi
-Zone
Flexi FSPBTS
FSP_x000D_
MicroFDD, Flexi BTS
TDD:_x000D_ FSP, FSM
Flexi
_x000D_
TDD:_x000D_Zone Micro FDD, Flexi
-FCM,FCT,FR_x000D_
Zone FSPMicro TDD:_x000D_ FCM, FCT
-Flexi Zone Micro FDD, Flexi
FSP_x000D_
--Zone
FSP
FCM,FCT,FR_x000D_
Micro TDD:_x000D_
FBB_x000D_ FCM, FCT
FSP
- FCM_x000D_
FCM,FCT,FR_x000D_ FCM, FCT
-FCM,FCT,FR_x000D_
FCT_x000D_ FCM, FCT
_x000D_
FCM,FCT,FR_x000D_
Flexi Zone Micro FDD, Flexi FCM, FCT
Zone Micro TDD:_x000D_
-FCM,FCT,FR_x000D_
FSP_x000D_ FCM, FCT
FCM, FCT, FSP (rel.2), FR FCM, FSP [FSMr2] / FCT, FSP [FSMr3]
Flexi BTS FDD, Flexi BTS FCM/FCT, FSP, FTM, FR, FF, MHA,
TDD:_x000D_
LCR RET_x000D_
LCR
- FCM_x000D_
-Flexi BTS FDD, Flexi BTS
FCT_x000D_ FSM/FCT, FSP, OptIF
TDD:_x000D_
- FTM_x000D_
Flexi BTS FDD, Flexi BTS FSP, FCM/FCT, OptIF
-TDD:_x000D_
-Flexi FCM_x000D_
FSP_x000D_
-- FCT_x000D_ BTS FDD, Flexi BTS
TDD:_x000D_ FR_x000D_
FSP_x000D_
-- FSP_x000D_
FCM, FCT _x000D_
FBB_x000D_
OptIF_x000D_ FCM, FCT _x000D_
-_x000D_ FCM_x000D_
---Flexi FR_x000D_
MHA_x000D_
FBB_x000D_
BTS FDD, Flexi BTS
FCT_x000D_
_x000D_
FCM/FCT
-TDD:_x000D_
-FCM,
_x000D_ OptIF_x000D_
RET_x000D_
_x000D_
--Flexi FCT_x000D_
FBB_x000D_ FCM, FCT_x000D_
_x000D_
Flexi
_x000D_ Zone
FCM_x000D_
Zone Micro FDD,
MicroFlexi Flexi
FDD,BTS
Flexi _x000D_
_x000D_
Flexi
Flexi
-Zone BTS
Zone
Micro
FCT_x000D_FDD,
Micro
TDD, FDD,
Flexi Flexi FT, FCT
Zone
Flexi
TDD:_x000D_ Micro
Zone TDD:_x000D_
Micro FDD, Flexi
Zone
Zone:_x000D_
_x000D_
FCM
--Zone FlexiMicro TDD, Flexi
ZoneTDD:_x000D_
Micro Zone BTS
-(Flexi
Flexi FSP Micro
FTM_x000D_
Zone Access
Zone Micro FDD, Flexi
BTS_x000D_
MHA
-Zone FSPMicro TDD, Flexi
FCT_x000D_ MHA
Point):_x000D_
_x000D_
_x000D_
MHA
-Flexi FSP_x000D_
Zone:_x000D_ MHA
Flexi Zone:_x000D_
-_x000D_
-ZoneFSP
Antenna line
FlexiMicro
Zone Access Point Antenna line
Flexi Zone TDD:_x000D_
(Flexi ZoneBTS
Flexi BTS FDD,
- Flexi Zone Micro Flexi Antenna line
Controller):_x000D_
TDD:_x000D_
BTS_x000D_
Antenna
Flexi Zoneline Antenna connector
-_x000D_
Antenna Line_x000D_
Controller_x000D_
RX1-n
_x000D_ RX1-n
Flexi Zone:_x000D_
Flexi
- FlexiZone
TX1-n, RX1-n
Zone Micro
Acces FDD,
PointFlexi
Zone Micro
TX1-n _x000D_ TDD:_x000D_
-RX1-n
Antenna Line
RET TILT
RET TILT
RET TILT
RET TILT
RET TILT
RX1-n, TX1-n, RET, MHA RX, TX, TILT, MHA, EFIL
MHA, RET
FR, FTM Filter, FR, FTM/FCT
- FCM_x000D_ FCM/FCT
-FCM
FCT FCM
LCR LCR
MHA in AISG mode
MHA in AISG mode_x000D_ AISG MHA
FR, MHA AISG, RET Flexi Filter, FA, AISG MHA, TILT
Flexi BTS FDD:_x000D_ FSM
-Flexi FCM_x000D_
BTS FDD:_x000D_ FSM
_x000D_
-Flexi FCM_x000D_
Flexi BTS
ZoneFDD,
MicroFlexi
FDD,BTS
Flexi
_x000D_
TDD:_x000D_
Zone
FCM,
Flexi Micro
FCT TDD, Flexi
Zone Micro FDD, Flexi FCM/FCT
-Zone:_x000D_FCM_x000D_
Zone
-FR Micro TDD, Flexi
FCT_x000D_ LTX
-Zone:_x000D_
FSP
_x000D_
FR LTX
-Flexi FSP
FR Zone Micro FDD, Flexi LTX
FR,
- Flexi RX1-n
Zone Micro BTS LTX, RX1-n
FR, TX1-n, RX1-n LTX, TX1-n, RX1-n
FR, TX1-n, RX1-n LTX, TX1-n, RX1-n
FR, TX1-n LTX / TX1-n
Flexi BTS FDD, Flexi BTS TX1-n
TDD:_x000D_
Flexi BTS FDD, Flexi BTS TX1-n
-TDD:_x000D_
TX1-n_x000D_
TX1-n
_x000D_ TX1-n
- FR_x000D_
Flexi ZoneFDD,
BTS
- TX1-n_x000D_ MicroFlexi
FDD,BTS
Flexi LTX, RX1-n
Zone
TDD:_x000D_
_x000D_
FR Micro TDD:_x000D_ LTX
-Flexi Antenna Line
RX1-n_x000D_
Flexi Zone
_x000D_
MicroFlexi
BTS FDD, FDD,BTS
Flexi FR, TX1-n
Zone
TDD:_x000D_ Micro TDD:_x000D_
Flexi
TX1-n Zone Micro FDD, Flexi
-- FR_x000D_ TX1-n
Zone FR_x000D_
MicroLine_x000D_
TDD:_x000D_
-TX1-n
-- Antenna
TX1-n_x000D_ TX1-n
Antenna
_x000D_ Line_x000D_
_x000D_
FR
_x000D_ LTX
Flexi
Flexi Zone:_x000D_
Flexi
-FR FlexiZone:_x000D_
ZoneTDD,
AccesFlexi
Point LTX
Zone
-FR,
FlexiMicro
ZoneRX1-n
Acces Point
TX1-n,
Zone:_x000D_ LTX/TX1-n/RX1-n
-FR
FR LTX
FR LTX
TX1-n TX1-n
FR LTX
FR LTX
FR RFSW
FAN, FAN_GROUP FAN, FAN_GROUP
FAN, FAN_GROUP Fan supervision
FAN, FAN_GROUP RFSW
FR RFSW
FR RFSW
TX1-n TX1-n
FR FR
FR FR
Antenna line Antenna line
FR FR
OptIF OptIF
OptIF OptIF
OptIF OptIF
OptIF OptIF
OptIF OptIF
OptIF #N/A
OptIF OptIF
OptIF OptIF
FCM, FCT, FBB FCM, FCT
FCM FCM, FCT
FSP, FBB, OptIf FSP, OptIF
FCM, FCT, FBB FCM, FCT, FSP
FCM, FCT, FBB FCM, FCT, FSP
FCM FSM
FCM FSM
OptIf OptIf
Flexi BTS FDD, Flexi BTS FCT, PSP
TDD:_x000D_
FSP,OptIF FSP, OptIF
- FCT_x000D_
FSP,FBB,OptIF
_x000D_ FSP, OptIF
Flexi
FCM,FCT,FBB Zone Micro FDD, Flexi FCM (MUKSU2), FCT (MURKKU2)
Zone
FCM,FCT,FBB Micro TDD:_x000D_ FCM (MUKSU2), FCT (MURKKU2)
- FSP
FCM,FCT,FBB FCM (MUKSU2), FCT (MURKKU2)
Flexi BTS FDD, Flexi BTS FSM
TDD:_x000D_
FBB FBB
- FSM_x000D_
FR
_x000D_
Flexi
FSM/FAN, Zone FR Micro FDD, Flexi
Zone
Flexi BTS FDD, Micro TDD:_x000D_
Flexi BTS
-TDD:_x000D_ Flexi Zone Micro BTS
-TDD:_x000D_ FSM_x000D_
Flexi
-- FR_x000D_ BTS FDD, Flexi BTS FSM, LCR
TDD:_x000D_ FSM_x000D_
-FR,
_x000D_ Antenna Line_x000D_
FSP, FBB, FCM, FCT FR, FSP
-- FCM_x000D_ LCR_x000D_
Flexi
LCR
-- FCT_x000D_ Zone Micro FDD, Flexi LCR
LCG_x000D_
-Zone
LCR
_x000D_
Micro TDD:_x000D_
FR_x000D_ LCR
-_x000D_ Flexi Zone Micro BTS
FDD,BTS
Flexi FCM/FCT
Flexi
Zone
TDD:_x000D_ Zone
Micro Micro FDD, Flexi
TDD:_x000D_
FSP
Zone FSPC
- GNSS_x000D_ FlexiMicro
ZoneTDD:_x000D_
Micro BTS
-_x000D_
Flexi FlexiBTS
Zone Micro
FDD, Flexi BTS FCM [FSMr2], FCT [FSMr3], FSP, DSP
BTS_x000D_
TDD:_x000D_
Flexi Zone Micro
BTS FDD, FlexiFDD,BTS
Flexi FCM, FSP
-TDD:
Zone LCRMicro
FCM [FSMr2]_x000D_
_x000D_ TDD:_x000D_
Flexi
-- FCT BTS FDD, Flexi BTS FSM, FR
TDD:_x000D_ Flexi [FSMr3]_x000D_
Zone Micro BTS
FCM_x000D_
-- FSP_x000D_
FCT_x000D_ FCM (FSMr2) / FCT (FSMr3)
All
-Flexi
TDD:_x000D_ units_x000D_
FBB_x000D_
-_x000D_ FSP_x000D_
BTS FDD, Flexi BTS FCM (FSMr2) / FCT (FSMr3)
--TDD:_x000D_DSP_x000D_
FCM_x000D_
FBB_x000D_
Flexi
FR
-_x000D_ Zone Micro FDD, Flexi
FCT_x000D_ FR
-_x000D_
Zone FCM_x000D_
MicroFDD,
TDD:_x000D_
_x000D_
Flexi
-Flexi Zone
BTS
Zone Micro
Micro FDD,BTS
Flexi Flexi
Flexi
FCT_x000D_
-TDD:_x000D_
Zone Flexi Zone
Micro
Zone MicroFDD,
BTS Flexi
TDD:_x000D_
Micro FDD, Flexi
_x000D_
TX1-n_x000D_ TX1-n / RX1-n
-Zone
-LCR
Flexi
RX1-nFSP Micro
FCM_x000D_ TDD:_x000D_
FSPZone Micro FDD, Flexi
-ZoneFlexiMicro
ZoneTDD:_x000D_
FCT_x000D_ Micro BTS
-Antenna
- FSP_x000D_lineMicro BTS
Flexi Zone Antenna line
-Antenna
FBB_x000D_
Line Antenna Line
_x000D_
Antenna
Flexi Zone line
Micro FDD, Flexi Antenna line
Zone
FSP Micro TDD:_x000D_ FSP
-OptIF
FSP OptIF
FAN1-n FAN1-n
Optif FR
FSP, FBB FSP
Fan/Fan group Fan/Fan group
Flexi BTS FDD, Flexi BTS 4082:
TDD:_x000D_
Flexi BTS FDD, Flexi BTS FSMr2:
4082: FCM, FSP MCU
4082:_x000D_
TDD:_x000D_ FSMr3:
FSMr2: FCT
-Flexi BTSFCM,
FSMr2: FDD, Flexi BTS 4082: FCM, FSP MCU
4082:_x000D_
TDD:_x000D_ FSMr3:
FSMr2: FCT
FCM, FSP MCU
FSP_x000D_
Flexi
-4082:_x000D_ BTS
FSMr2: FCM,FDD, Flexi BTS 4083:
FCM, FCT
-FSP_x000D_
TDD:_x000D_ FSMr3: FCT_x000D_ FSMr3:
FSMr2: FCT
FCM
LCR
--_x000D_ FSMr2: FCM, 4083:
LCR
--FSP_x000D_ FCM_x000D_
FSMr3: FCT_x000D_ FSMr3:
FSMr2: FCT
-4083:_x000D_ FCM_x000D_
FCT_x000D_ FSM FCM
4083:
_x000D_ FSMr3: FSMr3: FCT
-_x000D_
-4083:_x000D_
FCT, FCT FBBFCT_x000D_
FSMr2: FCM_x000D_ FSMr2:
4085:
FCT (forFCMFSMr3 only)
_x000D_
--FCM,
Flexi FSMr3:
Zone FCT_x000D_
Micro FSMr3:
FSMr3: FCT
FCT
4083:_x000D_ FSMr2:
FCT, Optif FDD, Flexi
FCM_x000D_ 4085: (for FSMr3 only)
FCM, FCT
_x000D_
Zone
--FCM, Micro
FSMr3: TDD, Flexi
FCT_x000D_ FSMr3: FCT
4085:
Zone:_x000D_ FSMr2:
FCT,
(forFCM_x000D_
OptIF
FSMr3 4085: (for
FSM FSMr3 only)
_x000D_
-Flexi FSMr3: FCT_x000D_ FSMr3: FCT
-only)_x000D_
4085: FSPBTS FDD, Flexi BTS
(for FSMr3 FCM/FCT
_x000D_
-TDD:_x000D_ FSMr3: FCT_x000D_
only)_x000D_
GNSS
4085: (for FSMr3 FCM/FCT
-_x000D_
-only)_x000D_ GNSS_x000D_
FSMr3: FCT_x000D_
GNSS
Flexi
_x000D_ Zone Micro FDD, Flexi FCM/FCT
_x000D_
-Flexi FSMr3: FCT_x000D_
Zone
GNSS
Flexi Micro
Zone
Zone TDD: FDD,
Micro
Micro _x000D_
FDD, Flexi
Flexi FCM/FCT
_x000D_
-GNSS
Zone 4082: FSP_x000D_
Micro TDD:_x000D_
Zone Micro TDD: _x000D_ FCM/FCT
-Flexi
-Zone
Zone
4083:
Flexi
4082: Zone Micro
Flexi ZoneFDD,
Micro
FSP_x000D_
Flexi
Micro
BTS
Antenna
BTS_x000D_ Micro TDD: _x000D_
Line Antenna Line, ALD
-- 4083: 4082: Flexi Zone Micro
-BTS_x000D_
Antenna 4085: FSP_x000D_
Flexi
LineZone Micro ALD
-BTS 4083: Flexi Zone Micro
-BTS_x000D_
Flexi 4085:
BTS Flexi Zone
FDD, Micro
Flexi BTS FCT
BTS
TDD:_x000D_
- 4085:FCT
FCM, Flexi Zone Micro
-BTS FCT_x000D_
FBBC
_x000D_ #N/A
FDD,BTS
Flexi #N/A
Zone
TDD:_x000D_ Micro
Flexi BTS FDD, Flexi BTS TDD:_x000D_ FCM/FCT
-TDD:_x000D_ FSP
FCM_x000D_
GNSS
-- FCT_x000D_ #N/A
FCM_x000D_
_x000D_
Flexi
- FCT_x000D_ BTS FDD, Flexi BTS FSP
Flexi
LCR Zone Micro FDD, Flexi
TDD:_x000D_
_x000D_ #N/A
-Zone
Flexi MicroMicro
FSP_x000D_
Zone TDD:_x000D_
FDD, Flexi
GTP-U
-Zone FlexiMicro
ZoneTDD:_x000D_
FBB_x000D_ Micro BTS GTP-U
_x000D_
LNMME
- Flexi Zone Micro BTS LNMME
Flexi
LNADJ Zone Micro FDD, Flexi LNADJ
LNMME
- FSP LNMME
TDD:_x000D_
LCR LCR
- FCM_x000D_
LCR
- FCT_x000D_ LCR
_x000D_
Flexi BTS FDD, Flexi BTS FCM_x000D_
Flexi
Flexi Zone
TDD:_x000D_ BTS FDD,MicroFlexi
FDD,BTS
Flexi FSM
-Zone
TDD:_x000D_ Micro
FCM_x000D_ TDD:_x000D_
Flexi BTS
Flexi
-- FCT_x000D_ ZoneFDD, Flexi
Micro BTSBTS FCM, FCT
FCM_x000D_
TDD:_x000D_
_x000D_
Flexi
-- FCT_x000D_ BTS FDD, Flexi BTS FCM
Flexi FCM_x000D_
TDD:_x000D_ Zone Micro FDD, Flexi
_x000D_
Flexi
--Zone BTS FDD, Flexi BTS
FCT_x000D_ FCM
Flexi
TDD:_x000D_ Micro
FCM_x000D_
Zone TDD:_x000D_
Micro FDD, Flexi
_x000D_
FCM,
--Zone FlexiFCT
ZoneTDD:_x000D_
FCT_x000D_ Micro BTS #N/A
Flexi Micro
FCM_x000D_
_x000D_
FCM,
-Zone FCT
FlexiMicro
ZoneTDD:_x000D_
FCT_x000D_ Micro BTS #N/A
Flexi
_x000D_
FCM, Zone
FCT Micro FDD, Flexi #N/A
-Zone
FlexiMicro
ZoneTDD:_x000D_
Micro BTS
Flexi
LCR Zone Micro FDD, Flexi LCR
-Zone
FlexiMicro
ZoneTDD:_x000D_
Micro BTS
LCR
- Flexi Zone Micro BTS LCR
LNADJ LNADJ
LNCEL #N/A
Flexi BTS FDD:_x000D_ #N/A
-LNADJ
FCM, FCT_x000D_ LNADJ
_x000D_
LNADJ
Flexi Zone Micro:_x000D_ LNADJ
-LNMME
Flexi Zone Micro BTS LNMME
LNMME LNMME
Flexi BTS FDD, Flexi BTS lcrId of the cell
TDD:_x000D_
Flexi BTS FDD, Flexi BTS FCM
LCR_x000D_
TDD:_x000D_
Flexi
_x000D_ BTS FDD, Flexi BTS FCM,FCT
-TDD:_x000D_ FCM_x000D_
Flexi
-LNADJG_x000D_ Zone MicroFlexi
BTS FDD,
FCT_x000D_ FDD,BTS
Flexi FCM,FCT
Zone
TDD:_x000D_
_x000D_
LCR Micro TDD:_x000D_ LCR
Flexi
-lcrId Zone
of the Micro
FCM_x000D_cell FDD, Flexi
Flexi
Zone
Flexi Zone
Micro
BTS Micro FDD,BTS
TDD:_x000D_
FDD, Flexi Flexi FSP, FSM
-Zone FCT_x000D_
Micro TDD:_x000D_
-Flexi
TDD:_x000D_
_x000D_ FlexiBTS
Zone Micro
FDD, Flexi BTS FCM/FCT, FSP
-- FCM FCM/FCT_x000D_
Flexi
TDD:_x000D_
FSP,FBB Zone Micro FDD, Flexi FSP
_x000D_
-Zone Micro TDD:_x000D_
FCM_x000D_
Flexi
- FCT_x000D_ Zone
FlexiBTS Micro
FDD,
Zone FDD,BTS
Flexi
Micro Flexi #N/A
Zone
TDD:_x000D_
- FSP_x000D_
Flexi Micro TDD:_x000D_
BTS FDD, Flexi BTS #N/A
-TDD:_x000D_
-Flexi FSP
FSP_x000D_
FBB_x000D_
--_x000D_ BTS FDD, Flexi BTS
FBB_x000D_ #N/A
FSP_x000D_
TDD:_x000D_
_x000D_
NE-FTM-1
-Flexi Zone Micro FDD, Flexi
FBB_x000D_ NE-FTM-1
-Flexi FSP_x000D_
Zone
Zone
_x000D_
FTM
-Zone MicroMicro
FBB_x000D_
FDD, Flexi
TDD:_x000D_ FTM
-_x000D_ Micro TDD:_x000D_
FSPZone Micro FDD, Flexi
Flexi
BFDGRP
-Zone
FSPMicro TDD:_x000D_ BFDGRP
Flexi
PPTT Zone Micro FDD, Flexi PPTT
-Zone
FSPMicro TDD:_x000D_
-ETHLK
FSP ETHLK
IKESA IKESA
ETHLK ETHLK
STPG STPG
STPG STPG
CERTH CERTH
ETHLK ETHLK
ETHLK ETHLK
ETHLK ETHLK
ETHLK ETHLK
PPTT PPTT
PPTT PPTT
PPTT PPTT
PPTT PPTT
UNIT UNIT
OAMMA, OAMMD OAMMA, OAMMD
OAMMEP OAMMEP
NE-FTM-1 NE-FTM-1
CERTH CERTH
BFD BFD
BFD BFD
ETHLK ETHLK
TWAMP TWAMP
TWAMP TWAMP
INTP INTP
CERTH CERTH
CERTH CERTH
FTM FTM
STPG STPG
STPG STPG
TOPF TOPF
IEIF,IVIF_x000D_ IEIF,IVIF_x000D_
UNIT UNIT
IPSECC IPSECC
IPNO IPNO
IPSECC #N/A
Meaning
The temperature of a unit exceeds the threshold value.
A software update in the module or submodule has failed.
Flexi BTS FDD:_x000D_
The reference
Connection to afrequency
module that thatbelongs
the BTStomaster the BTS clock receives has
configuration haschanged
been lost.by about 0.2 ppm or more (which equals the change
_x000D_
Failure
The cause wasofdetected
the alarm when
might eNodeB
be:_x000D_O&M system presented available FSPs to Cplane software in order to map FSPs to cell. Th
_x000D_
FCM/FSP synchronization has failed.
1. The reference
Incompatible frequency
software has beenhas changed
detected.because of a fault in the transmission network synchronization (which in turn is cause
reference synchronization. The alarm can also be activated if the faulty reference synchronization is corrected and there is, aga
The file system format of the downloaded software is incompatible with the file system format used in the BTS.
_x000D_
2. TheBTS
Flexi reference
FDD, Flexi frequency fluctuates continuously because of a significant amount of jitter/wander in the transmission network
BTS TDD:_x000D_
T
TheG.823/824/825._x000D_
The BTS is unable to obtain acannot
SNTP time or GPS time file frombe the
fetched within(error
file server the timein FTP limit._x000D_
open or FTP get). The file server is down, the file is missing,
_x000D_
occured.
The
Flexi downloaded
3. If the
ZoneBTS-integrated
Micro FDD, SW isFlexi
corrupted
transport
Zonepart or isreceives
Micro incorrectly theformed.
TDD:_x000D_ synchronization information via the 2.048 MHz synchronization input (extern
case._x000D_
UTC time source is not
Flexi BTS FDD, Flexi BTS TDD:_x000D_available in the BTS.
_x000D_
Setting
A module non-active
is blocked SW block(s)
with BTS Site thatManager.
contain a_x000D_
new SW version as active has failed during new SW version activation._x000D_
4. There
_x000D_
The is
purpose an equipment
is to avoid fault
fault in the BTS. The
indications that might equipment
be raised fault is, however,
during not the
the module most common
maintenance task.reason.
_x000D_ Normally, the reason
Flexi
_x000D_
Flexi BTS
Zone FDD,
Micro Flexi
FDD, BTS
Flexi TDD:_x000D_
The
The fault
fault is raisedthat
notifies onlythe
when
user anhas LTE systemthe
blocked module
cell (FSM)
with BTS isSite
theManager._x000D_
master agent of the blocked radio module (FR) or when an LT
Flexi
The
blocked Zone
SW
BTS isMicro
update
sharedblocked toFDD,
the Flexi
BTS
with
(WCDMA/LTE) BTS Zone
hasSite
radioMicro
failed. The
Manager. TDD:_x000D_
module, error
The might
purpose
fault:1931 beiscaused
is to avoid
raised. by fault
a module reset during
indications the SW
that might update,
be raised a hardware
during problem
a BTS mainten
_x000D_
The reference frequency that the BTS master clock receives has experienced a significant change during the measurement per
Flexi Zone
Flexi BTS FDD, MicroFlexi FDD,BTS Flexi TDD:_x000D_
_x000D_
The fault informs thehasoperator that BTS
the BTS isManager.
trying
The
The user
unit
cause has
or blocked
module
of the alarmthe beencelltested
might with Sitethe
during BTS to correct a
power-on fault
self testsituation
(POST)by andperforming a recovery
a failure has reset to a unit, the site,
been detected.
In case of an RF module resetbe:_x000D_
in RF chaining configuration, the BTS also resets all RF modules that are further in the chain._x0
_x000D_
A unit cannot be identified by its product code or by its physical device address (object ID).
_x000D_
1. TheZone
Flexi reference
A non-supported Micro frequency
FDD,has
unit Flexi has
beenZone changed because
Micro TDD:_x000D_
detected in the System of a fault
Module.in the transmission
Typically, networkwhen
this happens synchronization (which in
a new unit version is turn is cause
installed whil
reference
The BTS synchronization.
tries to recover a The
fault alarm
situationcan byalso be activated
performing a site if the
reset. faulty reference synchronization is corrected and there is, aga
A flash memory operation failure has occurred. If this alarm continuously appears, the flash chip might be broken.
_x000D_
2. The reference
A flash memory operation frequencyfailure
fluctuates continuously
has occurred. because
If this of a significant
alarm continuously amountthe
appears, of flash
jitter/wander in the
chip might be transmission
broken. network
T G.823/824/825._x000D_
_x000D_
A flash
3. If thememory operation
BTS integrated failure has
transport partoccurred.
receives the If this alarm continuously
synchronization appears,
information via the
the flash
2.048chipMHzmight be broken. input (extern
synchronization
case._x000D_
_x000D_
Synchronization between the FCM/FCT and FSP is lost.
4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason
The
Antennaoperating
(RP3)system (OSE)the
link is down: goes into the error
transmitter handlerdrops
or receiver with a fromfatalsynchronization.
status. The cause might be, for example, an out of memory
_x000D_
The
If onlystate
oneofFSP the inexternal
the BTS alarm line shows
generates that an
this fault, external
there alarm is notified._x000D_
is malfunction in one of the FSP submodules. If all FSPs generate this fau
_x000D_
_x000D_
The state of the external alarm line shows that an external alarm is notified._x000D_
The
Flexi user
Zonespecifies, during commissioning, the alarm number, severity, and polarity that indicates the fault.
_x000D_
The state ofMicro FDD,
the external Flexi
alarmZone lineMicro
shows TDD:_x000D_
that an external alarm is notified._x000D_
The
_x000D_operating
user system
specifies, (OSE)
during goes into the the
commissioning, error handler
alarm with aseverity,
number, fatal status. The cause
and polarity thatmight be, for
indicates theexample,
fault. an out of memory
The
_x000D_user specifies, during commissioning, the alarm number, severity, and polarity that indicates the fault.
The
The
The
The
The
The
The
The
The
The
The
The
The
The user specifies, during commissioning, the alarm number, severity, and polarity that indicates the fault.
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
Software download to FSP, DSP, or FR has failed.
Communication with an application has failed. It has not replied to the message that has been sent/resent to it.
The
The radio channel
baseband busthat has configuration
related been requested in the
of <x> commissioning
was rejected by the fileHW
is not
SW,supported supported
DSP, or RF SW. by the detected BTS radio or M
_x000D_
The
Flexibaseband
Zone Microbus synchronization
FDD, toward
Flexi Zone Micro <x> has failed.
TDD:_x000D_
The requested channel
reference clock in the start-up
monitoring phase is
has detected not acceptable
a loss of signal infor
thethe BTS hardware,
reference receivedbecause
from theof an incorrect frequency band a
FT.
The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from power-on. The
The
The OCXO adjustment
output signal of thearea
OXCO is reaching
is missingitsand
limitthe
value. The DAC
FCM/FCT worddeliver
cannot value the
of the OCXO
30.72 MHzisSystem
lower than or required
Clock equal to the Min.Ocxo
by the other
_x000D_
A request
Flexi ZonetoMicro
retrieve
FDD,theFlexi
public IP address
Zone information of the FCM/FCT from the FTM has failed.
Micro TDD:_x000D_
Master
The clock frequency
temperature is tuned
measured fromto within
the sensor5%specified
of its minimum or maximum offset. Flexi
in "Temp.Cold.Start.Sensor" Zone Micro
(= FSP)is BTS "Temp.Cold.Start.Limit"_
less than does not use DAC tuning
The BTS cannot start properly because the FSPs cannot be powered up at conditions that are too cold.
The Masthead Amplifier (MHA) does not work properly. However, the system cannot determine the impact on the RX signal leve
The Masthead Amplifier (MHA) does not work properly. Because of the low current drawn by the device, it is assumed that it do
To
Thestabilize the situation
Radio Module (60W and
RRH) keep the RX
or Filter (allsignal onhas
others) the detected
required level, there is
overcurrent onathe
need to switch
antenna line.DC
Thepower off for
antenna linealarming MHA
might be dam
Module.
The
The VSWR
VSWR valuevalue exceeds
exceeds thethe level
level defined
defined as as criterion
criterion for
for VSWR
VSWR Major
Minor event.
event. The
The impedance
impedance of of the
the antenna
antenna line
line does
does not
not ma
ma
_x000D_
The Radio Module has detected a malfunction
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ of an internal LNA unit.
detected
The Radio VSWR
Module is exceeds
unable tothetunedefined threshold.
to a required The antenna
sub-band properlyand/or antenna feed line is disconnected, mismatched, or da
(tuning_x000D_
failure), or another major failure has been detected
The Radio Module has detected an internal filter failure. by the Radio Module_x000D_
(unit faulty).
1845: TILT is not configured._x000D_
Others:
1845: TILTAntenna
is not tilting is not possible or might function incorrectly.
configured._x000D_
Others:
1845: TILTAntenna
configured._x000D_
Others:
1845: TILTAntenna
configured._x000D_
Others:
1845: Antenna
TILT is not tilting is not possible or might function incorrectly.
configured._x000D_
Others:
A hardware failure has is
Antenna tilting not reported
been possible orby might function
ALD (RET, MHA)incorrectly.
or by RFSW (Filter) ._x000D_
Note: Filter in Radio Module is considered as ALD even
The unit is in download mode state. This fault is returned when an though it isunsupported
an internal part of FR. occurs in download mode.
procedure
A corrupted SW file in the FLASH has been detected._x000D_
The
The unit cannot complete
synchronization set-upthe start-up.
between a BTS configured as slave and a BTS working as master has failed during BTS startup. A
The heater control connection of the FSM is faulty, there is no heater, or the heater is faulty.
During BTS startup or BTS recomissioning, the BTSOAM has detected that there are not enough: _x000D_
a) radioinresources
A fault or _x000D_
the Masthead Amplifier (MHA) is detected. MHA functionality is degraded. The real impact cannot be determined.
b) FSP resources or_x000D_
A fault in the Masthead Amplifier
c) cables between the system (MHA)and
module is detected.
the radio MHA is not
module working._x000D_
or cables between the extension baseband module (FBBx) and the
The device is not working properly, the configuration is not valid, or a given parameter is incorrect.
SRAM memory operation failure has occurred. If this fault appears continuously, the SRAM chip might be broken.
The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.
The reference clock monitoring has detected a loss of 2.048 MHz signal received from an external reference source, connected
The RF module configuration has failed because of HW or SW fault.
A critical configuration file is missing from the RF Module.
The RF Module SW detected that a non-critical configuration file is missing.
The System Module clock reference differs from the RF Module clock.
The baseband bus between the System Module and RF Module is out of synchronization.
The RF Module baseband bus is configured incorrectly.
There is an error in the baseband or optical bus.
The RF module's TX path is not usable.
The
The TX
RF output
Modulepower adjustment
filter has measured failed._x000D_
too low TX power.
_x000D_
Flexi
Flexi BTS
ZoneFDD,
MicroFlexi
FDD,BTS TDD:_x000D_
Flexi Zone Micro TDD:_x000D_
The
CLGC RF module's
The RFconvergence RX RF
module is outfailed, synthesizer
targetiscannot
gainbecause
of order not
of alocked._x000D_
be achieved.
software or hardware fault.
_x000D_
The power
Flexi supplyFDD,
Zone Micro supervision has Micro
Flexi Zone detected an overvoltage, undervoltage, or overcurrent in the RF module.
TDD:_x000D_
The RX path insignal
feedback the FR to module is faulty.
predistortion is too weak or missing. The TX performance is degraded.
The TX signal adjustment fails.
During RF startup: The temperature inside the RF Module is too low. Heating of module is ongoing. Wait until the alarm is cance
_x000D_
The permanent memory in the RF module is corrupted and the module product code or serial number is missing, or the module
During RF runtime: The temperature inside the RF module is going too low. Problem might occur.
The RF Module SW detected conflicting or corrupted configuration data.
An RF module's power-on self-test has failed at start-up.
The RF module has lost lock to the incoming clock.
The highest temperature exceeds the power decrease limit in the RF module.
The FPGA software update has failed in RF module.
The fault is detected in a radio sharing configuration wherein a WCDMA FSM is_x000D_
the
Themaster FSM and
radio module an LTE
cannot FSMthe
identify is the
fanslave FSM.
type that is The
usedfault means
or the fan isthat
notFR is blocked._x000D_
installed at all.
In case the LTE FSM is the master FSM or the LTE system module shares CPRI/Ir radio module with the SCDMA system modu
Fan(s) are not running in RF module.
Fan(s) in RF module are rotating slower than requested.
Fan(s) in RF module rotate faster than required.
The validated RF module temperature is higher than the predefined maximum allowed value.
The validated RF sensor temperature is greater than or equal to the predefined value on the unit property file.
The validated temperature of any PA sensor in RF module is higher than or equal to the predefined value on unit property file.
Increased bit error rate has been detected on the optical link to the radio module, which results in sporadical LCV errors in dow
Abnormally high bit error rate has been detected on the optical link to the radio module, which results in permanent baseband p
The Tx in the RF module has been switched off to protect the radio module hardware, which might be damaged because of hig
The FR module detected permanent RP3 routing collisions in either downlink (TX), or uplink (RX) transmission directions.
The Small Form Factor Pluggable (SFP) malfunction has occurred (fault 2000), or the SFP module is not physically present (the
The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detache
_x000D_
The data is faulty because there is interference in the fiber cable._x000D_
The connection between the System Module and the RF Module is broken OR connection between the Baseband Module (for e
_x000D_
The RP3 channel has lost the frame synchronization state that it had achieved.
A physical connection failure has occurred between the optical interface and the summing function (for example, caused by bad
The RP3 or Ethernet buffering is not working, and the buffer becomes full. The optical device is malfunctioning. The fault might
FaultRP3
The 2006ormay be detected
Ethernet in is
buffering Flexi
not BTS TDDand
working, only._x000D_
the buffer becomes full. The optical device is malfunctioning. The fault might
Fault
Fault 2007
2006 may
may bebe detected
detected inin Flexi
Flexi BTS FDD only._x000D_
BTS TDD only._x000D_
Fault
Fault 2010
2007 may
may bebe detected
detected both
in Flexiin Flexi BTS FDD
BTS FDD and TDD.
only._x000D_
Fault 2010 may be detected both in Flexi BTS FDD and TDD.
Fault 2006 may
The control messagebe detected in Flexi BTS
traffic between TDD only._x000D_
the modules is malfunctioning.
Fault 2007 may be detected in Flexi BTS FDD only._x000D_
The
Faultsynchronization
2010 may be detected to the clock bothcontrol
in Flexiunit BTS frame
FDDpulse
and TDD.that has been achieved earlier differs from the currently received fram
The master frame in the received baseband bus frame is not in the correct place related to the internally-generated master fram
A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted._x000D_
_x000D_
There is a baseband bus address mismatch in the summing. There are two possible causes:_x000D_
This
_x000D_ situation is also triggered when the links do not synchronize with each other.
The frame alignment has been lost or the frame burst has a CRC error when the_x000D_
1. A configuration
System Module is error
working (twoasdifferent
a lost baseband units functioning)
synchronization - after an acknowledgement, the fault returns._x000D_
The
_x000D_frame alignment has been or the frame slave system
burst has a CRCmodule._x000D_
error when the_x000D_
System
2. Module is working
on the as
bus a
- synchronization
The clock crossing buffer underflow or overflow in the RX block and data
Data corruption appears once whenslave system
unsynchronized module._x000D_ is sent by
the received datathemight
baseband.
be not valid. The fault is an indicati
The SW update to the BTS has failed or the BTS SW is corrupted.
The baseband bus message multiplexing slot for the message cannot be fulfilled.
An interrupt is generated if a message does not get routed._x000D_
_x000D_
Summing checks the headers of the messages to be summed. If the header is not an allowed type, summing is not performed a
This is considered normal when Faradays are starting up and RP3 sync is done.
The transmitter has detected an RP3 message from a summing coincident with a transmission rule.
The transmitter has detected more data coming from a summing than the current link rate can support.
The BTS has detected an abnormal operation or a failure in the internal functionality of the System Module._x000D_
_x000D_
The BTS has detected an abnormal operation or a failure in the BTS replaceable_x000D_
baseband
The BTS has unit.detected an abnormal operation or a failure in the internal functionality of the RF Module.
A fan, all the fans or more than one fan in the same fan group are rotating slower or faster than requested, are not rotating at al
There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a m
This
Flexi BTSBTS fault
FDD,indication
Flexi BTSisTDD:_x000D_
generated if the reference clock monitoring function of the BTS does not receive the configured sync
_x000D_
Too many cellsdetected
are commissioned to BTS. _x000D_
The BTS has
Background information:_x000D_an RF Module that cannot be put into use without a BTS reset._x000D_
_x000D_
_x000D_
There
A
Flexi is a failure
TX Zone
path fixed
Microsynchronization
has
FDD, occurred,
Flexi Zone priority
which list in in
results thethe
FlexiBTS:_x000D_
Multiple Input Multiple Output (MIMO) functionality not being operational or
An FSP overheat
_x000D_ has occurred. In Micro
order TDD:_x000D_
to put the card back into use, the FSP must be restored to normal temperature and the
More
The power level that is defined in the RNW part of the SCForfile
_x000D_ LNCELs than the supported maximum is configured tooismany LCRs areby
not supported commissioned
the HW. to one RF Module._x000D_
-Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. No
The
_x000D_BTS has detected a ancommunication
FSP Module that cannotwith
problem be the
put GPSinto use without a BTS reset.
receiver._x000D_
_x000D_
-Priority
The 2: external 2.048MHz
baseband-bus-related SRIO signal connectedfor
configuration to Faraday
the Synccore In interface
has been (NOTE:
rejected Notbyused in phaseSW.
the platform synchronization mode)._x00
The
_x000D_fault is ignored until the GPS receiver has reached commissioned state.
-Priority
The 3: the reference signal coming from the
lostintegrated transmission unit (FTM) (NOTE: Only ToP is used in phase synchron
The connection
_x000D_internal maximum to the FSP transferor DSPunit has
(MTU) been or the submodule
configuration has failed on reports
FCM,an FSP,error
or situation._x000D_
FBB.
_x000D_
Normally,
4026: all the FlexiBTS
EFaultId_TogglingAlFault sources
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ is are
used not
to in
informuse at
the the same
operator time
that (it depends
another_x000D_ on the network planning and BTS configuration).
generate
BTS fault
The connection
Flexi a fault.
(the
BTS FDD, to During
original
FlexitheBTS runtime
fault) is
DSPTDD:_x000D_ operation,
toggling._x000D_
module has been lost. the BTS fault functionality runs autonomously - notices also added/vanished source
_x000D_
The
The alarm that
commissioning is related
file to the
download original fault is suppressed and the new
has been started neither from BTS Site Manager, nor from NetActalarm, which is related to fault 4026:autoconfiguration.
during EFaultId_TogglingA
Flexi
The
_x000D_ BTS FDD,
source for Flexi
the FTM BTS TDD:_x000D_
(which is the priority 3 source for the FlexiBTS) can be TDM interface signal (e.g. E1, T1...), physical la
_x000D_
The BTSOAM
commissioning file isrelated
corrupted or original
an incorrect SCF file hasif been detected during BTSdefined
startup as isfollows:_x000D_
priority
Toggling
The
Flexi selection
alarms has is
that not
are
noticedfixed but
that user-selectable.
to
the
Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ the
connected Furthermore,
faults
radio are
unit suppressed
already a signal
has untillisted
another the in the
toggling
radio FTM
master references
condition is not received,
cleared._x000D_
apart from the FlexiaSystem
BASE SM
_x000D_
_x000D_
The
A
1. commissioning
module initialization
Commissioning filehas
data: download
the has been file
failed._x000D_ started neither from BTS Site Manager, nor from NetAct during autoconfiguration. A
Flexi
The
_x000D_ Zone Micro
severity of this FDD,BTSFlexi faultcommissioning
Zone
is theMicro as theisseverity
sameTDD:_x000D_ corrupted or aoriginal_x000D_
of the parameter has a missing or incorrect value._x000D_
_x000D_
The
The Radio
GPSBTS
toggling Module
source
fault. (ifhas detected that
provisioned) is thethe requested
highest frequency
priority reference is source.
not compatible
The GPS with the capabilities
source is considered offered
to bebyunusable
the Radio asModu
a ref
2.
The RNW
BTS data: "RNW
supports a has
ToP
Flexi BTS FDD, Flexi BTS TDD:_x000D_ wrong
or SyncE format",
reference"RNW could
source not
that be
have parsed", "RNW
configurable has wrong
priorities schema",
relative to "Validation
each other failed
through due
the to incom
"synchro
_x000D_
The cell configuration
An alarm
_x000D_ message hasisbeen not officially
received supported.
from the antenna Too many cells
line. The are assigned
antenna linetoisthe Tx group of the radio module._x000D_
faulty.
_x000D_
Flexi
An
Flexi Zone
alarm Micro
Micro FDD,
Zonemessage has Flexi
FDD, beenZone
Flexi received
Zone Micro
Micro TDD:_x000D_
from the antenna line device. The antenna line operation is degraded.
TDD:_x000D_
The commissioning
cell configuration
The Radio file
Module hasisdetected is missing,
not officially or an incorrect
supported. condition
an overcurrent SCF
The fileon
configuredhas been
RS485 detected
cell ,IUANT
which has during
antenna
port._x000D_ BTSpaths
startup as follows:_x000D_
in the resourceList antenna path
_x000D_
Some antenna line device is causing overload. Antenna line devices powered by the RS485 IUANT are out of order because of
The highest validated
1. Commissioning data: temperature
the commissioning value onfile theisFSP boardorexceeds
missing a parameter the threshold
has a missing value.or incorrect value._x000D_
-_x000D_
The mutual length difference of the parallel RP3-01/CPRI links toward one radio module is too large (more than 60 meters in O
-2.
FanRNW
RF data:has
sharing
delivered "RNW
by been not
unknown found",
disabledvendor "RNW
with has wrong
is master
detected WCDMA format",
(system because
module "RNW the could
mutual
hardware not be or
length
rel.2) parsed",
difference
_x000D_ "RNW has wrong
between schema",
the cables "Validation
of the WCDMA
the fandistance
A long speed is(high too low for successful
latency) between detection.
the FSM and Another
antenna detection
has been attempt occurs
detected butafter
the the fan test timer
Distributed expireshas
Site feature (system modu
not been e
_x000D_
The
Faulttemperature
is reported both on the forFSP board has
operational andexceeded
non-operationalthe criticalfansthreshold
in hardware value. detection phase only.
Fan(s) are not running although the temperature (indicated by Tcontrol) is higher than the value of the T.start parameter in the B
Fan(s) speed is deviating too much from the requested control.
Fan(s) are running faster than requested.
4082:_x000D_
The source unit has reached the maximum number of reset retries, that is, the source unit cannot successfully finish start-up af
4082:_x000D_
If
TheBTS O&Munit
source hashasdetected
reached thatthe
themaximum
BTS can number start withofpreviously-active
reset retries, thatSW version
is, the source- BTS
unitO&M processed
cannot consistent
successfully fallbackaf
finish start-up a
4082:_x000D_
1. previously-active SW version is running instart
all HW units in the BTS and_x000D_
If
TheBTS O&M
source has detected that the BTS can with previously-active SW version - BTS O&M processed consistent fallback a
2.
File
1. the BTS isunit
system up has
access
previously-active
reached
andoperations
SWrunning.
version
the
like
is
maximum
_x000D_ file system
running in
number
allmounting
HW
of reset
units
retries,
orinfile
theopening
BTS
thathave
is, the
and_x000D_
source unit cannot successfully finish start-up af
failed.
If BTS O&M has detected that the BTS can start with previously-active SW version - BTS O&M processed consistent fallback a
Otherwise:_x000D_
2.
The
1. the BTSRadio
Flexi is up Module
previously-active and running. _x000D_
has detected low downlink carrier ininput power from the Flexi System Module.
1. previously-active SW
Otherwise:_x000D_ SW version
version is is running
not running in allinHW all HWunitsunits the
in BTS
BTS and_x000D_
and,_x000D_
2.
2. the
During
the BTS
BTS is
reset,
is up
the
not and
BTS
up running.
andhasrunning_x000D_
detected that an SW
(recovery RF module
update connected
is still to the system module is affected by a power cycle failure and
supported)._x000D_
1. previously-active SW version is not running in all HW units in BTS and,_x000D_
Otherwise:_x000D_
_x000D_
The
2. summing
the BTS is not service
up SW
anddefault configuration
running has
SWinfailed.
1. previously-active
_x000D_ version is(recovery
not running update
all HWisunitsstill supported)._x000D_
in BTS and,_x000D_
_x000D_
1.The
2. the master
BTS is system
not up module
and runninghas lost optical
(recovery SW connection
update is to the
still peer system module._x000D_
supported)._x000D_
4083:_x000D_
_x000D_
2.In BTS configuration where one system module provides PPS synchronization slavesignalsystem
to another system module (sync hub co
_x000D_
Synchronization
The source is lost
unitmodule
has when theSW
requested system
fallback module
because is working as a synchronization
of a critical problem that has occurred module.
during This
start-up usually
after indicates
the SW updateth
4083:_x000D_
master
_x000D_ system does not work, that is, it is in reset state or powered off.
_x000D_
The
The fault
source indicates
unit haspoor GPS antenna
requested SW fallback installation.
because of a critical problem that has occurred during start-up after the SW update
4083:_x000D_
If BTS O&M has detected that the BTS can start with previously-active SW version - BTS O&M processed consistent fallback a
_x000D_
The source
The GPS receiver
unit hasis requested
running a site/self
SW survey.
fallback because of a critical problem that has occurred during start-up after the SW update
1.
If previously-active
BTS O&M SW version
has detected is running
thatstored
the BTS canin all HW
start withunits in the BTS
previously-active and_x000D_
SW version - BTS O&M processed consistent fallback a
_x000D_
There
2. the is no accurate
BTS is up andSW position
running. _x000D_ in the EEPROM.
1.
BTS O&M has detected version is running
that position
the BTSbut instart
canhas all HW withunits in the BTS and_x000D_
previously-active SW version - BTS O&M processed consistent fallback a
Otherwise:_x000D_
The
2. receiver
the BTS is is
upused
and in stored
running. _x000D_ been moved to a new position after that.
1.
previously-active SW version
SWdetected
version is is running
notonerunningin all HW
in all units in the
HW unitssegments BTS
in the BTSand_x000D_
and,_x000D_
Otherwise:_x000D_
The
2. theGPS
the BTSreceiver
is not
up andhas running. that
_x000D_ or more EEPROM have been found to be corrupted at reset and had to be s
2.
1. BTS is
previously-active up SW
and running
version is(recovery
not running SWinupdateall HW isunits
still supported)._x000D_
in the BTS and,_x000D_
Otherwise:_x000D_
Feeding voltage is disabled for the selected Antenna Line.
_x000D_
2.
1. the BTS is not up SW
previously-active andversion
runningis(recovery
nottherunning SWinupdate HWisunits
allAntenna still supported)._x000D_
in the BTS and,_x000D_
_x000D_
The HDLC link has been
_x000D_ disabled for reporting Line or IUANT port.
2. the BTS
4085:_x000D_ is not up and running (recovery SW update is still supported)._x000D_
_x000D_
SW file validation against its signature has failed.
_x000D_
Transport
4085:_x000D_ SW on the source unit has indicated the need for software fallback._x000D_
_x000D_
Phase
If BTS O&M synchronization
has hasthat
been commissioned at thepreviously-active
btsSyncMode, but SWPPS and/or ToPO&M
reference clock has not become avai
Transport
4085:_x000D_ SW ondetected
the source thehas
unit BTS can startthe
indicated withneed version
for software fallback._x000D_ - BTS processed consistent fallback a
1.
Shared
BTS O&M OptIFhas mode SW version
cannotthat
detected be theis running
read/changed
BTS in all
can start HW
from/in
with units
FBBC in the
card.BTS
previously-active and_x000D_
SW version - BTS O&M processed consistent fallback a
Transport
2. the BTS SW onand
the running.
is occurred
up source unit has
_x000D_ indicated the need for software fallback._x000D_
1.
A
has SW inversion
the is running
connection to in
theall HW
configuredunits in
BTS O&M has detected that the BTS can start with previously-active SW versionManagement
failure the
Real-timeBTS and_x000D_
Performance (RTPM) entity,
- BTS O&M processed for example,
consistent the
fallback a
Otherwise:_x000D_
2. the BTS is up and running. _x000D_
1.
TRS
IP configuring SW
or version is
re-configuring running
by RROMin all HW
has units
failed.
previously-active SW version is not running in all HW units in the BTS and,_x000D_ in the BTS and_x000D_
Otherwise:_x000D_
2. the BTS is
2. the
External
1. BTS is up
notand
GPS/GNSS
previously-active up SWrunning.
and running
receiver
version
_x000D_
is(recovery
module not has
running SWin
lost update
the HWisunits
allsatellite still supported).
visibility
in theand
BTSand is currently operating in holdover mode.
and,_x000D_
Otherwise:_x000D_
2.
The
1. the BTS is not
configured PHICH
previously-active up and running
SWtransmission (recovery
version is notpower running SW
boost update
cannot
in all is
HW unitsstill supported).
be applied either
in the BTS partly or at all because of a lack of remaining power
and,_x000D_
2. the
The RIPBTS is not upInterference
(Received and runningPower) (recovery valueSWper update
Physicalis still supported).
Resource Block (PRB) of the cell for UL subframes exceeds the pre
In GTP-U supervision, a network element did not respond to the GTP-U: Echo Request message within time.
The transport path (SCTP) for connection to MME is broken. This might be because of an unplugged cable to MME. There is no
The transport path (SCTP) for connection to an adjacent BTS is broken. This might be because of an unplugged cable to the ad
One of the transport paths (SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is support
There was an opening, reading, or file content problem with a radio network_x000D_
configuration
A BTS raises file thisat theifBTS
fault startup or at
it experiences activationinofinternal
a problem delta configuration_x000D_
configuration_x000D_
file.
data BTS The detected
distribution problem
(cellfault
setup) canto be a file
C- and U-Planehandling problem
SW components. (for example,_x000D_
The raises this if it experiences
open, read, and write operations fail) as well as a content problems a problem in internal configuration_x000D_
(for example,_x000D_
data
nofailure
A distribution
valid RAML2.1
has occurred (cell setup)
format). to C-Plane and U-Plane SW components.
in the trace connection between the BTS and the iOMS or a third party tool._x000D_
_x000D_
There was an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup._x000D_
The
A failure faulthas
is also detected
occurred when
during a vendor-specific fileofis trace
activation/deactivation missing.session (subscriber trace, cell trace, or interface trace session)._x0
_x000D_
The BTS has encountered a few possibly misconfigured PLMNs, which cannot be used by the BTS for accepting calls from new
In
_x000D_ case of subscriber trace, the possible reasons are:_x000D_
This
-These Thealarm indicates
Subscriber Tracethatfeature
the maximumis not numberatofthe
enabled LNADJ and/or LNADJL objects was exceeded in the eNB and that the new o
PLMNs that are considered misconfigured by BTS._x000D_
the BTS are:_x000D_
-- The
This Id used
alarm
currently for the that
indicates
configured subscriber
at the BTStrace
a WCDMA session
for neighbor
one or more is already
cell, which in is use
cells_x000D_ for another
reported by an UE active
via subscriber
ANR specific trace session._x000D_
measurements could not be stor
-This
form The
- served number
of:_x000D_ of
byindicates
alarm subscriber
one or more that MMEs trace
a WCDMA sessions
and therefore at the BTS has
currentlywhich
neighbor relation, reached
broadcast the maximum
by BTS's
is reported by a cells. number
However,
UE via of subscriber trace
none ofmeasurements,
ANR specific sessions
these PLMNs have couldsupporte
serving
not be
-neighbor
"A Handover
neighbour
_x000D_ cellat the
WCDMA BTS is
cell
in the form:_x000D_ongoing
which for
is the
reportedUE to
by be
an traced._x000D_
UE due to activated ANR feature(s) could not be stored because the maximu
This
_x000D_
%d, alarm indicates
ecgiPlmnId: that
MNC= %s, a WCDMA neighbor relation, which is reported by a UE because of activated UTRAN ANR feature:_x0
All
"LTE
-In previously
cell registered
ECGI{ecgiAdjEnbId UEsMCC= in
=onethese
%d, %d})"._x000D_
PLMNs =
ofecgiLcrId remain
%d, unaffected.
ecgiPlmnId = { %d, %d, %d}} , WCDMA cell CGI {rncId= %d,toCellId= %d, c
Ahascasebeen stored
target but
cell at
of cell/interface
handover least
trace,
cannot theuniquely
be LNRELW's
possible reasons
selected mobility parameters
are:_x000D_
because (psHoAllowed,
several candidates srvccAllowed)
are available for a has been
certain PCIsetvalue 'forbidden',
and carrierb
(limit
-The in
Thebase3GPP
Cell Trace 36.331
feature (32)).
is not_x000D_
enabled at the BTS._x000D_
The station
additional has info
alarm executed
holds the baseband
ARFCN board
of theis(FSP)
affectedrecovery activities. All baseband boards areandavailable again but notnumb
all c
- The Id used for the cell/interface trace session already carrier
in use forfrequency
anotheras well cell/interface
active as the LNCEL LNRELW
trace session._x000D_ instance
"Affected
The
- TheEARFCN WCDMA
number anARFCN
of cell
of LTE carrier cell
and neighbor
interface = %d,
trace aLTE
is sessionscell ECGI{ecgiAdjEnbId
mapped atEARFCN
the BTS has according = to
reached %d,theecgiLcrId
the = %d,
MFBI-profile
maximum ecgiPlmnId
configuration
number of cell and= { interface
%d,
(that is, %d, %d}}
trace ,sess
the requiremenWC
As a fault
This consequence,
occurs when HOCGI to this neighbor cellindicate
measurements is not possible
that twoand call drop
or more cellsrate
thatmight increase
operate on theifsame
there frequency
is no otheruse suitable handov
the same PC
This fault indicates that:_x000D_
1.
The TheX2absolute
interfacevalue resetof has estimated
failed after phase several errorattempts.
of an eNB, Thiswhich is in holdover,
indicates that a severe has exceeded
failure hasthe limit of 5forus,_x000D_
occurred, example there is s
or_x000D_
There
2. eNBisisno more X2 connectivity
than 6 hourstoisan adjacent
holdover mode BTS,what the means
adjacent BTS
that has failed,
estimated and error
phase so on. value may be not credible. It is assumed
There
S1 interface is no S1 resetconnectivity
has failedtoafter an MME. several _x000D_
attempts. This indicates that a severe failure has occurred, for example there is some
_x000D_
The cell is deactivated
Fault is generated if S1 setup procedure has subsequently because S1 is unavailable (that is, none beenofattempted
the PLMNs and configured for the cell currently
failed "maxS1SetRetry" number have a serving M
of times._x000
provided.
_x000D_
The Otherwise, the period
S1 eNB configuration update procedure has failed._x000D_ length is set to 15 min. _x000D_
_x000D_
Flexi
_x000D_
A
Note: RIMZone request
Ais cell
Micro
is to FDD,
the serving Flexi Zone BSS S1 Micro
has TDD:_x000D_
failed after several attempts. This means that System Information for the is related GERAN
There
The MME nocouldS1considered
connectivity
not be informed toto haveanaboutMME, availability MMEwhen
themodification
the there
of at is
has failed, and at least
least sooneon.one
ofIftheconfigured
the PLMN
fault is canceled,
following of autonomous
the cell which
eNB configuration currently
recovery
data:_x000D_ serve
actions (r
availability.
-AeNB RIM Name_x000D_
association could not be established because a RIM Error PDU has been received or a RIM Application Error has been d
-System-Information-Broadcast-related
Supported TAs (TAC, PLMN Identities)_x000D_ parameters have changed more than 32 times within three hours.
-Diagnostic Default paging DRX
Files have been collected for an internal reason and are available in the BTS.
Physical memory supervision has detected that memory usage has exceeded 90%(FCM/FCT)/98%(FSP).
A non-correctable bit-toggling error has been detected in the critical DSP memory.
A fatal error of the DSP HWAPI SW has occurred._x000D_
_x000D_
A fatal error of the DSP Application SW has occurred._x000D_
Flexi
The
If an BTS
FSP hasthe purposely triggered a GPIO reset is forathe DSP._x000D_
Flexi
_x000D_ BTS in FDD, BTS Flexi generates
BTS TDD:_x000D_ this fault, there malfunction in_x000D_
a
The
If corresponding
an transport
FSP in thepart FSP
BTS of the sub-module._x000D_
generates BTS has thisbeen fault, reset
there atisthe a date and time
malfunction given in the notification._x000D_
in_x000D_
_x000D_
If
_x000D_ all FSPstogenerate this fault, there isbeena malfunction in thethe FSM._x000D_
a
A
Flexi corresponding
change
Zone the
Micro FDD, FSP
BTS IPsub-module._x000D_
settings
Flexi Zone has Micro received
TDD:_x000D_ from BTS Site Manager. To activate the change, the BTS needs to be re
_x000D_
1.FSMr2
If all FSPs supports
generate the this following
fault, cause
there is formalfunction
a the reset:_x000D_ in the FSM._x000D_
If
The
Flexi
_x000D_ an alarm
FSP
Zoneinis the
MicroraisedBTSFDD,if generates
the Flexi BFD thisMicro
service
Zone fault, there
is TDD:_x000D_
not is a malfunction
available anymore on in thethe whole
BTS for BTS.all BFD sessions belonging to that BFD group.
_x000D_
If
"trs
Loss
Flexi anpower-on
FSP inMicro
of frame.
Zone the ItBTS
reset":
is not
FDD, generates
Coldpossible
Flexi startZone this
:to_x000D_ fault,traffic
carry
Micro thereon
TDD:_x000D_ is the
a malfunction in the whole
interface referenced BTS.
in the alarm text. All other transmission alarms related
"trs
If an watchdog
Flexi BTS FDD, Flexi BTS TDD:FSP in the reset":
BTS System
generates overload_x000D_
this fault, there is a malfunction in the whole BTS.
"trs
Probable
No startup
signal isfailure":
cause receivedfor E1 Failure
oninterfaces:
theinduring
interface startup
The referenced _x000D_
interface atinthethefar end text.
alarm is notAllconfigured to be a framed
other transmission alarmsE1related
interface.
to this signal are suppre
A
"trs dead peer
software was
failure":detectedSoftware one of the
failure_x000D_ IPsec associations of the FTM._x000D_
There
"trs
Probable
Flexi is no
management
BTS cause
FDD,response for reset":
Flexi T1 tointerfaces:
BTS the
Reset requests
TDD: Thesent
triggered bytomanagement
interface theatpeer, either
the far during
is not the
interface:_x000D_
end IKE SA to
configured setup,
be a the IPsec SA setup or during DPD._x000
T1 interface.
Probable
Note: When causes IPSec for Ethernet
backup interfaces:
tunnel feature is enabled, this alarm should not be raised due
"trs
The
-_x000D_
Primary fallback":
small
a cable and cut Fallback
isform-factoror therepluggable
secondary executed_x000D_
is
timingno cable (SFP)
source connected module
lost. Thetodetected
LTE in the on
theisinterface
running interface
internalconnector
clock or in does not failures
to
hold-over comply
modewith
whensecurity
trying torequirements.
and no timing
setup primar
signal is sen
_x000D_
-One the ofelectrical signal is excessively attenuated
Possible
FSMr3
Flexi Zone reasons:_x000D_
the Micro
supportssynchronisation
the
FDD, following
Flexifar sources
cause
Zone in
Microfor the the
TDD: configured
reset:_x000D_ priority list is unavailable.
-This
The
-This the port
first
a cable
can atcut
and
is
be the
second
or connected
there synchronization
isorBTS
no end
thecable node sources
connected is switched
from off
the
toissource.
the configured priority list are unavailable. On failure, the LTE switches auto
interface_x000D_
_x000D_
The small
alarm isthe
form-factor
raisedprimary pluggable
if the secondary
(SFP)
cannot module
update clock the not supported,
Certificate not present,
Revocation or could
List (CRL). not berefer
Please recognized.
PDDB parameter CERTH::CR
-The
"trs thepower-on
signalform-factor
small is excessively
reset": Cold
pluggable attenuated_x000D_
start_x000D_
(SFP) module detected in the interface connector does not comply
Flexi
Probable
A
-The
In Zone
loopback
the
the port
alarm:at Micro
cause:
isthe FDD,transmission
The
requested
connected Flexi
forfaranZoneEthernet
end Micro
links selected
node TDD:
interface
is switched for clock
either
off source
locally are BTS
at the faulty.orThe
the reason
Link OAM canclient of with
be alarms theon the
BTS theSFP setmodule
isinterfaces types
(for
into loopbackexa
"trs
No watchdog
SFP
signal module
is reset":
received was onSystem
expected
the overload_x000D_
by
interface the SW,
referenced but found
in themissing.
alarm text. All other transmission alarms related to this signal are suppre
Protocol
On
"trs an
Probable software can
interface
causes: be forPDH,
failure": which Timing
Software over
the Link Packet
OAM
failure_x000D_ (ToP) and Synchronuous
functionality was switched on, ethernet.
no Link OAM PDUs were received during the period spe
-"trs
A Link OAM
Probable No management
SFP module
causes PDU for reset":
is inserted
containing Reset at
Ethernetainterfaces: triggered
the SFP-based by management
Ethernet interface_x000D_
interface.
critical link event flag was received on the Ethernet interface. The alarm is raised with the first de
Unit
-"trs The Number
spurious
SFPismodule's is optional:
reset": Reset
interface reason
contacts detection are failed_x000D_
corroded
--For
A amalfunctioning
cable
PDH and cut or there
of
Synchronousthe is
SFP no cable
transceiver
Ethernet, connected
Unit was to theisor
detected.
number
dirty, preventing either read access to the SFP module at the time of rea
interface
0 or 1.
-_x000D_
The
-Excessive
The The
the SFP
following
electrical module critical
signal type link is not
events
isaexcessively supported.
are possible:
attenuated
-It
-2. is SFP
not
"$date"
hasbit reported
present error for Timing
is rate. anThe
transmission
Over
measured Packet(TOP).faultbitPeriodcondition
error rate and has disabled
exceeds the threshold the laser
valuetransmitter.
of BER-3
Errored(10E-3).
- Critical the atformat
portEvent: the either local
connected time
far stamp
Errored endSymbol node (GMT+/-xx:xx)
is switched .off
Event, E.g:an2014-04-12
Errored Frame 00:51:26
Event GMT+0530_x000D_
an Frame Period Event or an Errored
_x000D_
-The
Loss Dyingfault is generated
of Gasp:
multiframe. eitherThe the only localwhen
interface or the the interface
remote
referenced inisthe
peer not
has configured
a fatal
alarm texterror
has asand LMP
lost is
the(that
about is,togenerated
multiframe restart. only when the interface is configured
alignment.
The
Probable
-Alarm Linkinterface
Fault: causes:
thevaluelocal ispeeroptional: has detected a physical link fault byin receiving direction, e.g.device
a LOS.
The
-ProbableForfault
the PDH
signal isthe
indication generated
level valuesignal
is toorangeonly
low when
is received.
depends
(optical the This
oninterface
signal
the is
is not
hardware configured
generated
unitaretype: aselectrical
an
1..16 LMP (that
intermediate is,PDH
generated only
in thewhen the interface
forward direction is configured
because it d
cause: the interface type connectors
has not been or cables
configured dirty,
to meet the framingconnectors or cables
of the interface atare
thecorroded)
far end. For E1 interfaces
- the
Remote For specified
Synchonuous
defectmaximum Ethernet
indication. It isthe
length sentofvalue
the
by cable range
the is=exceeded
1..3
intermediate or the far end equipment because it detects a serious fault in the receive
All
-Unit It other
the not transmission
ismissing.present
connector is for
not alarmsover
Timing
properly related Packet.
connected to this to signal
the unit are suppressed.
The slot has been configured to hold a unit but the plug-in_x000D_
-unit theisreceiver
Probable not cause: or the
physically Thefar farend
present endtransmitter
has
in the a slot._x000D_
LOS, has LOF failedor AIS alarm on its receiving interface.
Probable
The alarmcause: is triggered There is a transmission
whenever a service problem
OAM error somewhere
related to in the
the transmission
intermediate network and AIS is sent instead of user traffic.
_x000D_
of Continuity Check Messages (CCM) persists on aAIS given Ethernetitinterface
When
Probable a MEP receives
causes:_x000D_ a valid ETH-AIS frame and is enabled, shall trigger an AIS alarm containing the following informati
as soon as
-receiving one interface
of the error condtions below occurs.
_x000D_
Five consecutive
The following alarms failed arelogin attempts to the FTM have been performed.
defined:
-A the -MD
unit levelbeen
has configured
1)requested
MDL_MISMATCH,
-Source certificate
MAC address priority
could not 5 but benot
(highest detected_x000D_
retrieved priority): from CCM the is receivedauthority
certificate with MDL (CA).
-A the
lower unit
than
requested is broken
the highest
certificate and therefore
configured
could not not
beone detected_x000D_
in
renewed the BTS
from and
the not matching
certificate any
authority of (CA).
The
-the alarm
theconfigured
unit has is raised
been if the alarmbut
configured is enabled,
some other theunit BFDisstate for the session is not AdminDown and nevertheless no BFD packet is
detected_x000D_
NOTE: In FSMr2, ones. pure number interface arethe used (eg. 1,2,3). But for FSMr3 unit types, interface is provided as: from
"module type n
_x000D_
The
Ex:
A alarm
CCM
requested is
fault raised
level
certificate if the
- prio could alarm
5 BTS,
cause
not beis enabled,
MDL_MISMATCH
retrieved BFD
as the number state of the session
of"interface
certificates is received
not AdminDown and the
from repository BFD
serverpacket
(RA) or the far
certificate end
au
NOTE:
NOTE: In Flexi
unitindicates Zone
variable should Micro interface
be5:replaced is provided
by appropriate as: EIF
HW which
namesisconfigured number". (unitTypeConfigured)
2)
This MAID_MISMATCH
alarm priority
that there isCCM a mismatchis received between with MDL BTS configuration configured
and auto-negotiation result.during runtime reporting.
in
The theRTTBTS, but withalarm
threshold MAIDisnot sent matching
in case any the MA average configured
value of in the
the RTT BTS exceeds_x000D_
on
this
the MDL.
configured threshold. shall be sent in case the configured value of PLR is exceeded.
The
Ex:CCM PLR faultthreshold level 5alarm prio 5 cause MAID_MISMATCH
3) MAID_MISMATCH
BTS shall report this alarm priority 5:CCM
if the NTPisserver received is not with matchingorMDL
accessible if theand NTP MAID,
server cannot be used._x000D_
but the
Note 1: VLAN
Filtering membership
time is not of the to
used received
clear the frame does not match the VLAN configuration of the addressed MA.
alarm._x000D_
Ex:CCM
Note fault level
2: Filtering time 5 prio
is not 5 cause
applicable MAID_MISMATCH
for FSMr2._x000D_
4)may
It ERR_CCM,
take up to priority
1 minute 4:CCM is received
to raise the alarm withon knownFSMr2. MDL and MAID, but MEPID
is not configured in the Remote MEP list of the MA.
Ex: CCM fault level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED
5) ERR_CCM, priority 4: CCM is received with known MDL, MAID and MEPID,but CCM interval coded in the received CCM doe
The BTS shall raise a "Vendor BTS certificate due to expire" alarm when the Vendor BTS certificate is about to expire._x000D_
_x000D_
NE stores trust anchors for its own trust chain and for peers. When own or any trust anchors are about to expire/expired this al
The period of notification in advance is configurable and the same as for CA certificate expiry._x000D_
FTM
_x000D_ Fault, for which fault name is mentioned in the Fault name field, is toggling in the FTM. Toggling fault condition is informed
Fault._x000D_
1
Inday case...the
4999 days with
incoming SSM default
is not 1825
receiveddays._x000D_
for a certain time period (configured via "ssmTimeout" parameter) this an alarm is rais
This alarm is raised when the received SSM indicates lower clock quality (e.g. "do not use" or "EEC") than required.
The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP._x
-During
The eNB the does
BTS IP notaddress
receiveconfiguration
a reply from ToP Master
the BTS testswithin a certain
the direct time (5
attached sec) upon
network it hasother,
whether sent a sync request
already message_x00
configured BTSs, on
-warning
The eNB receives
shall contain fromthe ToP Master
corresponding a granted
IP message
address. For rates
each (sync
DAD message
event a rate,
separate delay message
reporting shall rate),
be that does
indicated._x000D_not match
SW does not support the detected HW unit type._x000D_
_x000D_
BTS has entered IPsec emergency bypass active state.
Probable
BTS causes:_x000D_
has entered IPsec emergency bypass active state where
The
_x000D_base station is currently capturing IP traffic towards a localconfigured
port or intoIPsec
a file policies are ignored
on the base station. and all traffic is sent unprot
ifThis
thealarm
- The traffic
system capturing
module's
will isSW
be triggered happening
when attowards
version isleast a local
too old_x000D_
one port,
primary port tunnel
IPsec and destination mac has
fails and BTS address needs
switched to be
over to provided.
secondary IPsec tunnel.
Port
As values
-Incorrect
Supported
a result can
HW
of be LMP
variant
failure in or
not
at < HW MODULE
present
least one in system
primary NAME
module>-<PORT ID>.
i.e LMP orcell configuration
FSM-EIF1, for RFor
FSM-EIF2 modules
FTIF-EIF1 with a different frequency. The same cell is configured for two RF IPsec
IPsec tunnel, BTS has automatically switched over to secondary modules tunnel
thattermin
are n
_x000D_
The FSP does not support the requested BTS configuration.
In case of multiband RF variants, the Tx and Rx frequencies and channel numbers must always be in the same operating band
The BTS has tried to correct a fault situation by performing a recovery unit, site or BTS reset, but some reason, the recovery is
Antenna carrier resources were not successfully set up during cell setup or cell deletion procedure because of the failure of RX
A fan is not rotating or is rotating more slowly than the requested speed, or the RPM information for the fan is not available.
All the fans or more than one fan in the same fan group are rotating more slowly than requested.
The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem i
_x000D_
The summing service release from reset has failed.
Cell activation procedure has failed because of an error in the processing of cell configuration data. The corresponding cell can
The output signal of the OXCO has some problems and one or more clock pulses are missed.
The sample set of phase measurement not fulfilled the filtering criteria. _x000D_
The
Moretuning
than oneof oscillator is not able totypes
sector configuration calculate
(A, G,theH)new
are DAC value.to the same RF Module.
configured
The Fault diagnostics rule file is missing or its parsing has failed.
The Fault diagnostics rule file is missing or its parsing has failed.
The RNW configuration data contains a request to create a cell for a non-existing LCR: the LCR ID parameter associated with t
Secondary optical link between the System Module and RF Module is lost.
The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be attribute
The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. The failure can
The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the m
Some of the commissioning parameters are either missing or faulty, or there is a mismatch between them.
A software update to a module or sub-assembly has failed, or a corrupted SW file has been detected in the FLASH.
The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.
The FlexiBTS has detected an abnormal operation or a failure in the Masthead Amplifier (MHA).
The connection to the Flexi Transport submodule (FTM) is lost.
Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group
Mandatory parameter missing in the radio network configuration data.
The BTS monitors the FSP phase-locked loop (PLL) lock status and PLL locking fails.
The
FSMunit cannot
notices complete
a shared radiothemodule
start-up.
is connected to different OptIF connectors on peer system modules.
The cells, whose TX carriers are served by the affected Antenna Lines are deactivated to reduce the power transmitted by the P
mismatch).
Not enough RP3-01 links connected between FSM and FR. Commissioned cells cannot be routed via existing RP3-01 links.
FSP is undergoing a cold reset.
During SW update it was detected that configurations of active and passive SW in HW unit are same. Active and passive SW co
- before SW download
- during SW activation before active and passive SW switch
- during start-up
Power feeding for given Radio Module has been switched off by user from BTS Site Manager remotely.
RF module cannot be detected due to IP address conflict between RP3-01 nodes.
Power level is too high for at least one of the cells using the same radio module while at the same time at least one of the cells
FSM notices that a primary optical link connection to the Radio Module has been lost and the radio has been detected only via
Meaning in issue 01
A software update in the module or submodule has failed.
The reference
Connection to afrequency
module that thatbelongs
the BTStomasterthe BTS clock receives has
configuration haschanged
been lost.by about 0.2 ppm or more (which equals the change
_x000D_
Failure
The cause wasofdetected
the alarm while
mightoperation
be:_x000D_ when eNodeB O&M system presents available FSP to Cplane software in order to map FS
_x000D_ synchronization has failed._x000D_
FCM/FSP
1. The reference
Incompatible frequency
software has beenhas changed
detected.because of a fault in the transmission network synchronization (which in turn is cause
reference synchronization. The alarm can also be activated if the faulty reference synchronization is corrected and there is, aga
The file system format of the downloaded software is incompatible with the file system format used in the BTS.
_x000D_
2. TheBTS
Flexi reference
FDD, Flexi frequency fluctuates continuously because of a significant amount of jitter/wander in the transmission network
BTS TDD:_x000D_
T
TheG.823/824/825._x000D_
The BTS is unable to obtain acannot
SNTP time or GPS time file frombe the
fetched within(error
file server the time
in FTP limit._x000D_
open or FTP get). The file server is down, the file is missing,
_x000D_
occured.
The
Flexi downloaded
3. If the
ZoneBTS-integrated
Micro FDD, SW isFlexi
corrupted
transport
Zonepart or isreceives
Microincorrectly
TDD, Flexi theformed.
synchronization
Zone:_x000D_ information via the 2.048 MHz synchronization input (extern
case._x000D_
UTC time source is not available
Flexi BTS FDD, Flexi BTS TDD:_x000D_ in BTS or Flexi Zone Access Point.
_x000D_
Setting
A module non-active
is blocked SW block(s)
with BTS Site thatManager._x000D_
contain a new SW version as active has failed during new SW version activation._x000D_
4. There
_x000D_
_x000D_ is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason
Flexi
_x000D_
Flexi BTS
Zone FDD,
Micro Flexi
FDD, BTS
Flexi TDD:_x000D_
The
The purpose
fault is tothat
notifies avoid
thefault
user indications
has blocked that themight
cell be
withraised
BTS during
Site the module maintenance task._x000D_
Manager._x000D_
Flexi
The
The Zone
SW
BTS
fault is
is Micro
updateblocked
raised FDD,
to the
only Flexi
BTS
with BTS
when Zone
hasSite
an LTEMicro
failed. The
Manager.TDD:_x000D_
system error
The might
modulepurpose be
(FSM) caused
is to
is avoid
the by a module
fault
master reset
of theduring
indications
agent that theradio
might
blocked SW update,
be raised
module a(FR).
hardware
during a In
BTS problem
mainten
other case
_x000D_
The reference frequency that the BTS master clock receives has experienced a significant change during the measurement per
Flexi Zone
Flexi BTS FDD, Micro Flexi
FDD, BTS
Flexi TDD:_x000D_
_x000D_
The fault informs thehas
operator that BTS
the BTS isManager.
trying
The
The user
unit
cause has
or blocked
module
of the alarmthebeencelltested
might with Sitethe
during BTS to correct a
power-on fault
self testsituation
(POST)by performing
and a recovery
a failure has reset to a unit, the site,
been detected.
In case of an RF module resetbe:_x000D_
in RF chaining configuration, the BTS also resets all RF modules that are further in the chain._x0
_x000D_
_x000D_
1. TheZone
Flexi reference
A non-supported Micro frequency
FDD,has
unit Flexi has
beenZone changed because
Micro TDD:_x000D_
detected in the System of a fault in the
Module. transmission
Typically, networkwhen
this happens synchronization (which in
a new unit version is turn is cause
installed whil
reference
The BTS synchronization.
tries to recover a The
fault alarm can
situation byalso be activated
performing a siteif the
reset. faulty reference synchronization is corrected and there is, aga
_x000D_
2. The reference
A flash memory operationfrequencyfailure
fluctuates continuously
has occurred. because
If this of a significant
alarm continuously amountthe
appears, of flash
jitter/wander in the
chip might be transmission
broken. network
T G.823/824/825._x000D_
_x000D_
A flash
3. If thememory operation
BTS integrated failure has
transport partoccurred.
receives the If this alarm continuously
synchronization appears,
information via the
the flash
2.048chipMHzmight be broken. input (extern
synchronization
case._x000D_
_x000D_
4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason
The
Antennaoperating
(RP3)system (OSE)the
link is down: goes into the error
transmitter handlerdrops
or receiver with a fromfatalsynchronization.
status. The cause can be, for example, an out of memory s
_x000D_
The
If onlystate
oneofFSP the inexternal
the BTS alarm line shows
generates that an
this fault, external
there alarm is notified._x000D_
is malfunction in one of the FSP submodules. If all FSPs generate this fau
_x000D_
_x000D_
The
Flexi user
Zonespecifies, during commissioning, the alarm number, severity, and polarity that indicates the fault.
_x000D_
The state ofMicro FDD,
the external Flexi
alarmZone lineMicro
shows TDD:_x000D_
that an external alarm is notified._x000D_
The
_x000D_operating
user system
specifies, (OSE)
during goes into the the
commissioning, error handler
alarm with aseverity,
number, fatal status. The cause
and polarity thatcan be, forthe
indicates example,
fault. an out of memory s
The
The
The
The
The
The
The
The
The
The
The
The
The
The
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
Software download to FSP, DSP, or FR has failed.
Communication with an application has failed. It has not replied to the message that has been sent/resent to it.
The
The radio channel
baseband busthat has configuration
related been requested in the
of <x> commissioning
was rejected by the fileHW
is not
SW,supported supported
DSP, or RF SW. by the detected BTS radio or M
_x000D_
The
Flexibaseband
Zone Microbus synchronization
FDD, toward
Flexi Zone Micro <x> has failed.
TDD:_x000D_
The requested channel
reference clock in the start-up
monitoring phase is
has detected not acceptable
a loss of signal infor
thethe BTS hardware,
reference receivedbecause
from theof an incorrect frequency band a
FT.
The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from power-on. The
The
The OCXO adjustment
output signal of thearea
OXCO is reaching
is missingitsand
limitthe
value. The DAC
FCM/FCT worddeliver
cannot value the
of the OCXO
30.72 MHzisSystem
lower than or required
Clock equal to the Min.Ocxo
by the other
_x000D_
A request
Flexi ZonetoMicro
retrieve
FDD,theFlexi
public IP address
Zone information of the FCM/FCT from the FTM has failed.
Micro TDD:_x000D_
Master
The clock frequency
temperature is tuned
measured fromto within
the sensor5%specified
of its minimum or maximum offset. Flexi
in "Temp.Cold.Start.Sensor" Zone Micro
(= FSP)is BTS "Temp.Cold.Start.Limit"_
less than does not use DAC tuning
The BTS cannot start properly because the FSPs cannot be powered up at conditions that are too cold.
The Masthead Amplifier (MHA) does not work properly. However, the system cannot determine the impact on the RX signal leve
The Masthead Amplifier (MHA) does not work properly. Because of the low current drawn by the device, it is assumed that it do
To
Thestabilize the situation
Radio Module (60W and
RRH) keep the RX
or Filter (allsignal onhas
others) the detected
required level, there is
overcurrent onathe
need to switch
antenna line.DC
Thepower off for
antenna linealarming MHA
might be dam
Module.
The
The VSWR
VSWR valuevalue exceeds
exceeds thethe level
level defined
defined as as criterion
criterion for
for VSWR
VSWR MajorMinor event.
event. The
The impedance
impedance of of the
the antenna
antenna line
line does
does not
not ma
ma
_x000D_
The Radio Module has detected a malfunction
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ of an internal LNA unit.
detected
The Radio VSWR
Module is exceeds
unable tothetunedefined threshold.
to a required The antenna
sub-band properlyand/or antenna feed line is disconnected, mismatched, or da
(tuning_x000D_
failure), or another major failure has been
Radio Module has detected internal filter failure. detected by the Radio Module_x000D_
(unit faulty).
1845: TILT is not configured._x000D_
Others:
1845: TILTAntenna
configured._x000D_
Others:
1845: TILTAntenna
configured._x000D_
Others:
1845: TILTAntenna
configured._x000D_
Others:
1845: Antenna
TILT is not tilting is not possible or might function incorrectly.
configured._x000D_
Others:
A hardware failure has is
Antenna tilting not reported
been possible orby might function
ALD (RET, incorrectly.
MHA) or by RFSW (Filter) ._x000D_
Note: Filter in Radio Module is considered as ALD even
The unit is in download mode state. This fault is returned when an though it isunsupported
an internal part of FR. occurs in download mode.
procedure
The
The unit cannot complete
synchronization set-upthe start-up.
between a BTS configured as slave and a BTS working as master has failed during BTS startup. A
The heater control connection of the FSM is faulty, there is no heater, or the heater is faulty.
During BTS startup or BTS recomissioning, the BTSOAM has detected that there are not enough: _x000D_
a) radioinresources
A fault or _x000D_
the Masthead Amplifier (MHA) is detected. MHA functionality is degraded. The real impact cannot be determined.
b) FSP resources or_x000D_
A fault in the Masthead Amplifier
c) cables between the system (MHA)and
module is detected.
the radio MHA is not
module working._x000D_
or cables between the extension baseband module (FBBx) and the
The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.
The RF module configuration has failed because of HW or SW fault.
The RF module's TX path is not usable.
The
The TX
RF output
Modulepower adjustment
filter has measured failed._x000D_
too low TX power.
_x000D_
Flexi
Flexi BTS
ZoneFDD,
MicroFlexi
FDD,BTS TDD:_x000D_
The
CLGC RF module's
The RFconvergence RX RF
module is outfailed, synthesizer
targetiscannot
gainbecause
of order not
of alocked._x000D_
be achieved.
software or hardware fault.
_x000D_
The power
Flexi supplyFDD,
Zone Micro supervision has Micro
Flexi Zone detected an overvoltage, undervoltage, or overcurrent in the RF module.
TDD:_x000D_
The RX path insignal
feedback the FR to module is faulty.
predistortion is too weak or missing. The TX performance is degraded.
_x000D_
The permanent memory in the RF module is corrupted and the module product code or serial number is missing, or the module
An RF module's power-on self-test failed at start-up.
The RF module has lost lock to the incoming clock.
The highest temperature exceeds the power decrease limit in RF module.
The FPGA software update has failed in RF module.
The fault is detected in radio sharing configuration where WCDMA FSM is master FSM and LTE FSM is slave FSM. The fault m
In
Thethe casemodule
radio where cannot
LTE is master
identifyFSM
the fanandtype
FR that
is blocked
is usedfault 48:EFaultId_UnitBlockedAl
or the fan is not installed at all. is detected, not 1931.
Fan(s) are not running in RF module.
Fan(s) in RF module are rotating slower than requested.
Fan(s) in RF module rotate faster than required.
The validated RF module temperature is higher than the predefined maximum allowed value.
The validated RF sensor temperature is greater than or equal to the predefined value on the unit property file.
The validated temperature of any PA sensor in RF module is higher than or equal to the predefined value on unit property file.
Increased bit error rate has been detected on the optical link to the radio module, which results in sporadical LCV errors in dow
Abnormally high bit error rate has been detected on the optical link to the radio module, which results in permanent baseband p
The Tx in the RF module has been switched off to protect the radio module hardware, which might be damaged because of hig
The FR module detected permanent RP3 routing collisions in either downlink (TX), or uplink (RX) transmission directions.
The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detache
_x000D_
The data is faulty because there is interference in the fiber cable._x000D_
The connection between the System Module and the RF Module is broken OR connection between the Baseband Module (for e
_x000D_
The RP3 channel has lost the frame synchronization state that it had achieved.
A physical connection failure has occurred between the optical interface and the summing function (for example, caused by bad
FaultRP3
The 2006ormay be detected
Ethernet in is
buffering Flexi
not BTS TDDand
working, only._x000D_
the buffer becomes full. The optical device is malfunctioning. The fault might
Fault
Fault 2007
2006 may
may bebe detected
detected inin Flexi
Flexi BTS FDD only._x000D_
BTS TDD only._x000D_
Fault
Fault 2010
2007 may
may bebe detected
detected both
in Flexiin Flexi BTS FDD
BTS FDD and TDD.
only._x000D_
Fault 2010 may be detected both in Flexi BTS FDD and TDD.
Fault 2006 may
The control message be detected in Flexi BTS
traffic between TDD only._x000D_
the modules is malfunctioning.
Fault 2007 may be detected in Flexi BTS FDD only._x000D_
The
Faultsynchronization
2010 may be detected to the clock bothcontrol
in Flexiunit BTS frame
FDDpulseand TDD. that has been achieved earlier differs from the currently received fram
The master frame in the received baseband bus frame is not in the correct place related to the internally generated master fram
A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted._x000D_
_x000D_
There is a baseband bus address mismatch in the summing. There are two possible causes:_x000D_
This
_x000D_situation is also triggered when the links do not synchronize with each other.
The frame alignment has been lost or the frame burst has a CRC error when the_x000D_
1. A configuration
working (twoasdifferent
a lost baseband units functioning)
synchronization - after an acknowledgement, the fault returns._x000D_
The frame
_x000D_ alignment has been or the frame slave burst hassystema CRCmodule._x000D_
error when the_x000D_
System
2. Module is working
on the as
bus a
- synchronization
The clock crossing buffer underflow or overflow in the RX block and data
Data corruption appears once whenslave system
unsynchronized module._x000D_ is sent by
the received datathemight
baseband.
be not valid. The fault is an indicati
The SW update to the BTS has failed or the BTS SW is corrupted.
The baseband bus message multiplexing slot for the message cannot be fulfilled.
An interrupt is generated if a message does not get routed._x000D_
_x000D_
Summing checks the headers of the messages to be summed. If the header is not an allowed type, summing is not performed a
This is considered normal when Faradays are starting up and RP3 sync is done.
The transmitter has detected an RP3 message from a summing coincident with a transmission rule.
The transmitter has detected more data coming from a summing than the current link rate can support.
The BTS has detected an abnormal operation or a failure in the internal functionality of the System Module._x000D_
_x000D_
baseband
The FlexiBTS unit.has detected an abnormal operation or a failure in the internal functionality of the RF Module.
A fan, all the fans or more than one fan in the same fan group are rotating slower than requested, are not rotating at all, or the R
There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a m
This
Flexi BTS
BTS fault
FDD,indication
Flexi BTSisTDD:_x000D_
generated if the reference clock monitoring function of the BTS does not receive the configured sync
_x000D_
1.Too many
The BTS
Background hascells
detectedare commissioned
information:_x000D_an RF Moduletothat BTS. _x000D_
cannot be put into use without a BTS reset._x000D_
2.Cable
_x000D_ between system module and radio module or between extension baseband module and radio module presented in site
There
A is a failure
TX path
_x000D_ fixed synchronization
has occurred, which priority list in in
results thethe
FlexiBTS:_x000D_
Multiple Input Multiple Output (MIMO) functionality not being operational or
An FSP overheat has occurred. In order to put the card back into use, the FSP must be restored to normal temperature and the
_x000D_
Flexi Zone Micro
The power
_x000D_ level that FDD, is Flexi
defined Zone Micro
in the RNW TDD:_x000D_
part of the SCF file is not supported by the HW.
-Priority
More 1: PPSthan
LNCELs (Pulse the Per Second)
supported signal connected
maximum is configured to theorSynchronization
too many LCRs Input interface (Sync
are commissioned to In)
oneofRF theModule._x000D_
System Module. No
The BTS
_x000D_ has detected an
a FSP Module
communication that cannot
problem be the
with put GPS
into use without
receiver._x000D_a BTS reset.
_x000D_
-Priority
The 2: external 2.048MHz
baseband-bus-related SRIO signal connectedfor
configuration to Faraday
the Synccore In interface
has been (NOTE:
rejected Notbyused in phaseSW.
the platform synchronization mode)._x00
The fault is ignored until the GPS receiver has reached commissioned state.
_x000D_
-Priority
The 3: the reference signal coming from the
lostintegrated transmission unit (FTM) (NOTE: Only ToP is used in phase synchron
The connection
internal maximum
_x000D_
to the FSP transferor DSPunit has
(MTU) been or the submodule
configuration has failed on reports
FCM,an FSP,error
or situation._x000D_
FBB.
_x000D_
Normally,
4026: all the FlexiBTS
EFaultId_TogglingAlFault sources
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ is are
used not
to in
informuse at
the the same
operator time
that (it depends
other_x000D_ on the network planning and BTS configuration).
generate
BTS fault a fault.
(original
The connection
Flexi BTS FDD, to During
Flexifault)
theBTS runtime
is operation,
toggling._x000D_
DSPTDD:_x000D_
module has been lost. the BTS fault functionality runs autonomously - notices also added/vanished source
_x000D_
The
The alarm related
commissioning to the
file original
download fault is suppressed and the new alarm_x000D_
has been started neither from BTS Site Manager, nor from NetAct during autoconfiguration. A
Flexi
The
related BTS
source FDD,
to theforfault
theFlexi FTM
4026:BTS TDD:_x000D_
(which is the priority 3 source
EFaultId_TogglingAlFault for the FlexiBTS) can be TDM interface signal (e.g. E1, T1...), physical la
is raised._x000D_
_x000D_
The BTSOAM
commissioning filefixed
is corrupted or an incorrect SCF file hasif been detected during BTSdefined
startup apart
as is
follows:_x000D_
priority
_x000D_
The
Flexi selection has
Zone Micro FDD, is not
noticed but
that user-selectable.
the connected Furthermore,
radio unit already a signal
has listed
another in
radiothe FTM
master references not
fromreceived,
the FlexiaSystem
BASE SM
1. Commissioning
_x000D_
Toggling alarms data:Flexi
related thethe
to
commissioning
original faults file
are issuppressed
corrupted oruntil a parameter
the_x000D_ has a missing or incorrect value._x000D_
The
A
2. commissioning
module
RNW initialization
data: "RNW file download
has
has has been
failed._x000D_
wrong format", "RNW startedcould neither
not befrom BTS Site
parsed", "RNW Manager,
has wrong nor schema",
from NetAct during autoconfiguration.
"Validation A
failed due to incom
Flexi
toggling
_x000D_ Zone Micro
condition FDD, Flexi
is cleared._x000D_Zone Micro TDD:_x000D_
_x000D_
Radio
The GPS
_x000D_ Module
source has(ifdetected
provisioned) that requested
is the highest frequency
priority doesn't
reference fit to the capabilities
source. The GPS offeredsource is byconsidered
Radio Module.
to be unusable as a ref
_x000D_
The BTS
Severity
Flexi supports
BTSofFDD,
this BTS a ToP
FlexiFault or SyncE
BTSisTDD:_x000D_ reference source that
the same as the severity of the original_x000D_ have configurable priorities relative to each other through the "synchro
Flexi
toggling
ThealarmZone
cell BTSMicro
Fault
configuration FDD,isFlexi Zone Micro
not officially TDD:_x000D_
supported. Too many cells are assigned
An
The message
commissioning has
file isbeen received
missing, or an from the antenna
incorrect SCF file line.
hasThebeenantenna
detected linetoisthe Tx group of the radio module._x000D_
faulty.
during BTS startup as follows:_x000D_
_x000D_
_x000D_
An alarm message has been received
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ from the antenna line device. The antenna line operation is degraded.
1. Commissioning
cell configuration
The Radio data:
Module hasisdetected the commissioning
not officially file is
supported. condition
an overcurrent missing or a
The cell configured, parameter
on RS485 IUANT has
which has a antenna or
missing
port._x000D_ incorrect
paths in thevalue._x000D_
resourceList antenna paths
_x000D_
Some antenna line device is causing overload. Antenna line devices powered by the RS485 IUANT are out of order because of
The
2. RNWhighest
data:validated
"RNW not temperature
found", "RNW valuehas on wrong
the FSP board "RNW
format", exceeds the not
could threshold value."RNW has wrong
be parsed", schema", "Validation
- The mutual length difference of the parallel RP3-01/CPRI links toward one radio module is too large (more than 60 meters in O
-The
RF fan
sharing
speed hasis been
too low disabled with master
for successful WCDMA
detection. because
Another the mutual
detection attempt length
occursdifference
after thebetween
fan test the
timercables of the WCDMA
expires.
A long distance (high latency) between the FSM and antenna has been detected but the Distributed Site feature has not been e
The temperature on the FSP board has exceeded the critical threshold value.
Fan(s) are not running although the temperature (indicated by Tcontrol) is higher than the value of the T.start parameter in the B
4082:_x000D_
4082:_x000D_
_x000D_
4082:_x000D_
4083:_x000D_
_x000D_
The source
The
File source unit
system
4083:_x000D_ unit
accesshas reached
requests SW the
operations maximum
fallback
like file because
system number of reset
of a critical
mounting retries,
or problem
file opening that is,
hasthe
thathave source during
occurred
failed. unit cannot successfully
start-up after the SW finish start-up
update, af
that
_x000D_
_x000D_
The source
Flexi
4083:_x000D_ unit requests
Radio Module has SWdetected
fallback because
low downlink of a carrier
critical input
problem powerthatfrom
has the
occurred during start-up
Flexi System Module.after the SW update, that
4085:_x000D_
_x000D_
The
During
Transport source
reset,
SWunitonrequests
the BTS hasSW
the source fallback
detected
unit because
that
indicates antheRFneedof a critical
module problem
for connected
software tothat
thehas
fallback. occurred
system moduleduring start-upbyafter
is affected the SW
a power update,
cycle failurethat
and
4085:_x000D_
_x000D_
The summing
Transport SW service defaultunit
on the source configuration
indicates the hasneedfailed. for software fallback.
4085:_x000D_
The
Transport SW on the source unit indicates the need for to
master system module has lost optical connection the peer
software system module.
fallback.
Synchronization is lost when the system module is working as a synchronization slave system module. This usually indicates th
The fault indicates poor GPS antenna installation.
The GPS receiver is running a site/self survey.
There is no accurate position stored in the EEPROM.
The receiver is used in stored position but has been moved to a new position after that.
The GPS receiver has detected that one or more EEPROM segments have been found to be corrupted at reset and had to be s
Feeding voltage is disabled for the selected Antenna Line.
The HDLC link has been disabled for the reporting Antenna Line or IUANT port.
SW file validation against its signature has failed.
Phase synchronization has been commissioned at the btsSyncMode, but PPS and/or ToP reference clock has not become avai
Shared OptIF mode cannot be read/changed from/in FBBC card.
A failure has occurred in the connection to the configured Real-time Performance Management (RTPM) entity, for example, the
TRS IP configuring or re-configuring by RROM has failed.
External GPS/GNSS receiver module has lost the satellite visibility and and is currently operating in holdover mode.
The configured PHICH transmission power boost cannot be applied either partly or at all because of a lack of remaining power
The RIP (Received Interference Power) value per Physical Resource Block (PRB) of the cell for UL subframes exceeds the pre
The transport path (SCTP) for connection to MME is broken. This might be because of an unplugged cable to MME. There is no
The transport path (SCTP) for connection to an adjacent BTS is broken. This might be because of an unplugged cable to the ad
There was an opening, reading, or file content problem with a radio network_x000D_
configuration
A BTS raises file thisat theifBTS
fault startup or at
it experiences activationinofinternal
a problem delta configuration_x000D_
configuration_x000D_
file.
data BTS The detected
distribution problem
(cellfault
setup) canto be a file
C- and U-Planehandling problem
SW components. (for example,_x000D_
The raises this if it experiences
open, read, and write operations fail) as well as a content problemsa problem in internal configuration_x000D_
(for example,_x000D_
data
nofailure
A distribution
valid RAML2.1 (cell
has occurred setup)
format). to C-Plane and U-Plane SW components.
in the trace connection between the BTS and the iOMS or a third party tool._x000D_
_x000D_
There was an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup._x000D_
The
A failure faulthas
is also detected
occurred when
during a vendor-specific fileofis trace
activation/deactivation missing.session (subscriber trace, cell trace, or interface trace session)._x0
_x000D_
The BTS has encountered a few possibly misconfigured PLMNs, which cannot be used by the BTS for accepting calls from new
In
_x000D_ case of subscriber trace, the possible reasons are:_x000D_
This
-These Thealarm indicates
Subscriber Tracethatfeature
the maximumis not numberatofthe
enabled LNADJ and/or LNADJL objects was exceeded in the eNB and that the new o
PLMNs that are considered misconfigured by BTS._x000D_
the BTS are:_x000D_
-- The
This Id used
alarm
currently for the that
indicates
configured subscriber BTStrace
a WCDMA
at the session
for neighbor
one or more is already
cell, which in is use
cells_x000D_ for another
reported by an UE active
via subscriber
ANR specific trace session._x000D_
measurements could not be stor
-This
formThe
- served number
of:_x000D_
alarm of
byindicatessubscriber
one or more that MMEs trace
a WCDMA sessions
and therefore at the BTS has
currentlywhich
neighbor relation, reached
broadcast the
by BTS's
is reported maximum
by a cells. number
However,
UE via of subscriber trace
none ofmeasurements,
ANR specific sessions
these PLMNs have couldsupporte
serving
not be
-neighbor
"A Handover
neighbour
_x000D_ at
cell the
WCDMA BTS is
cell
in the form:_x000D_ongoing
which for
is the
reportedUE to
by be
an traced._x000D_
UE due to activated ANR feature(s) could not be stored because the maximu
This
_x000D_
%d, alarm indicates
ecgiPlmnId: that
MNC= %s, a WCDMA
MCC= neighbor
%d})"._x000D_ relation, which is reported by a UE because of activated UTRAN ANR feature:_x0
All
"LTE
1) previously
has cell
not beenregistered
ECGI{ecgiAdjEnbId
stored inUEs
casein these
= the
%d, PLMNs
ecgiLcrId
actual number =remain unaffected.
%d, LNRELW
ecgiPlmnId = cell
{ %d, %d, %d}} , WCDMAcarriercell CGI(in{rncId= %d,profile)is
CellId= %d,equac
In case
A handover of cell/interface
target trace,
cell cannot theuniquely
be possible reasonsofbecause
selected are:_x000D_ per
several (LNCEL)
candidates per
are UTRAN
available for a certainANRPRW
PCI value and carrier
2)
-ThehasCell
The been stored
Trace but atisleast
feature one of LNRELW's
not enabled at the mobility parameters (psHoAllowed, srvccAllowed) has been set to 'forbidden',
BTS._x000D_
(limitbase
in station
3GPP has executed
36.331 (32)). baseband
_x000D_ board (FSP) recovery activities. All baseband boards are available again but not all c
- The Id used for the cell/interface trace session is already in use for another active cell/interface trace session._x000D_
The additional
- TheEARFCN
number of alarm
of an LTE
cell infoneighbor
and holds thecell
interface ARFCN
trace of the at
is sessions
a mapped affected
EARFCN
the BTS carrier frequency
according
has reached theasmaximum
to the well as the
MFBI-profile LNCEL ofand
cell LNRELW
configuration
number (that
and instance
is, the
interface tracenumb
requiremen
sess
"Affected
As a fault
This WCDMA
consequence,
occurs when ARFCN
HOCGI carrier
to this = %d,cell
neighbor
measurements LTE iscell
notECGI{ecgiAdjEnbId
indicate possible
that twoand call drop
or more = %d,
cellsrate ecgiLcrId
thatmight
operate =on
%d,
increasetheecgiPlmnId
ifsame is no=other
{ %d,use
there frequency %d,
suitable
the%d}} , WC
handov
same PC
This fault indicates that the estimated phase error of an eNB, which is in holdover, has exceeded the limit of 5 us.
The X2 interface reset has failed after several attempts. This indicates that a severe failure has occurred, for example there is s
There is no X2 connectivity to an adjacent BTS, the adjacent BTS has failed, and so on.
There
S1 interface is no S1 resetconnectivity
has failedtoafter an MME. several _x000D_
attempts. This indicates that a severe failure has occurred, for example there is some
_x000D_
The cell is deactivated
Fault is generated if S1 setup procedure has subsequently because S1 is unavailable (that is, none beenofattempted
the PLMNs and configured for the cell currently
failed "maxS1SetRetry" number have a serving M
of times._x000
provided.
_x000D_
The Otherwise, the period
S1 eNB configuration update procedure has failed._x000D_ length is set to 15 min. _x000D_
_x000D_
Flexi
_x000D_
A
Note: RIMZone request
Ais cell
Micro
is to FDD,
the serving Flexi Zone BSS S1 Micro
has TDD:_x000D_
failed after several attempts. This means that System Information for the is related GERAN
There
The MME nocouldS1considered
connectivity
not be informed toto haveanaboutMME, availability MMEwhen
themodification
the there
of at is
has failed, andat least
least so
one on.one
ofIftheconfigured
the PLMN
fault is canceled,
following of autonomous
the cell which
eNB configuration currently
recovery
data:_x000D_ serve
actions (r
availability.
-AeNB RIM Name_x000D_
association could not be established because a RIM Error PDU has been received or a RIM Application Error has been d
-System-Information-Broadcast-related
Supported TAs (TAC, PLMN Identities)_x000D_ parameters have changed more than 32 times within three hours.
-Diagnostic Default paging DRX
Files have been collected for an internal reason and are available in the BTS.
Physical memory supervision has detected that memory usage has exceeded 90%(FCM/FCT)/98%(FSP).
A non-correctable bit-toggling error has been detected in the critical DSP memory.
A fatal error of the DSP HWAPI SW has occurred._x000D_
_x000D_
A fatal error of the DSP Application SW has occurred._x000D_
Flexi
The
If an BTS
FSP hasthe purposely triggered a GPIO reset is forathe DSP._x000D_
Flexi
_x000D_ BTS in FDD, BTS Flexi generates
BTS TDD:_x000D_ this fault, there malfunction in_x000D_
a
The
If corresponding
an transport
FSP in thepart FSP
BTS of the sub-module._x000D_
generates BTS has thisbeen fault, reset
there atisthe a date and time
malfunction given in the notification._x000D_
in_x000D_
_x000D_
If
_x000D_ all FSPstogenerate this fault, there isbeena malfunction in thethe FSM._x000D_
a
A
Flexi corresponding
change
Zone the
Micro FDD, FSP
BTS IPsub-module._x000D_
settings
Flexi Zone has Micro received
TDD:_x000D_ from BTS Site Manager. To activate the change, the BTS needs to be re
_x000D_
1.FSMr2
If all FSPs supports
generate the this following
fault, cause
there is formalfunction
a the reset:_x000D_ in the FSM._x000D_
If
The
Flexi
_x000D_ an alarm
FSP
Zoneinis the
MicroraisedBTSFDD,if generates
the Flexi BFD thisMicro
service
Zone fault, there
is TDD:_x000D_
not is a malfunction
available anymore on in thethe whole
BTS for BTS.all BFD sessions belonging to that BFD group.
_x000D_
If
"trs
Loss
Flexi anpower-on
FSP inMicro
of frame.
Zone the ItBTS
reset":
is not
FDD, generates
Coldpossible
Flexi startZone this
:to_x000D_ fault,traffic
carry
Micro thereon
TDD:_x000D_ is the
a malfunction in the whole
interface referenced BTS.
in the alarm text. All other transmission alarms related
"trs
If an watchdog
FSP
Flexi BTS FDD, Flexi BTS TDD:_x000D_ in the reset":
BTS System
generates overload_x000D_
this fault, there is a malfunction in the whole BTS.
"trs
Probable
No startup
signal isfailure":
cause receivedfor E1 Failure
oninterfaces:
theinduring
interface startup
The referenced _x000D_
interface atinthe
thefar end text.
alarm is notAllconfigured to be a framed
other transmission alarmsE1related
interface.
to this signal are suppre
A
"trs dead peer
software was
failure":detectedSoftware one of the
failure_x000D_ IPsec associations of the FTM._x000D_
_x000D_
There is no response tointerfaces:
the requests
"trs
Probable
Flexi
Probable management
BTS cause
FDD,
causes for reset":
Flexi
for T1 BTS
Ethernet Reset
TDD: Thesent
triggered
interfaces:_x000D_ bytomanagement
interface theatpeer, either
the far end during
is not the
interface:_x000D_ IKE SA to
configured setup,
be a the IPsec SA setup or during DPD._x000
T1 interface.
Note:
"trs
The When
fallback":
small IPSec
Fallback backup tunnel
executed_x000D_ feature is enabled, this alarm should not be raised duenot failures
to whensecurity
trying torequirements.
setup primar
-_x000D_
Primary a cable isform-factor
and cut or therepluggable
secondary is
timingno cable (SFP)
source connected module
lost. Thetodetected
LTE in the on
theisinterface_x000D_
running interface
internalconnector
clock or in does
hold-over comply
modewith and no timing signal is sen
_x000D_
-One the ofelectrical signal is excessively attenuated_x000D_
Possible
FSMr3
Flexi Zone reasons:_x000D_
the Micro
supportssynchronisation
the
FDD, following
Flexifar sources
cause
Zone in
Microfor the the
TDD: configured
reset:_x000D_ priority list is unavailable.
-This
The
-This the port
first
a cable
can atcut
and
is
be the
second
the or connected
there
primary synchronization
isorBTS
no end
thecable
secondary node sources
connected is switched
clock from
toissource.
the off_x000D_
the configured priority list are unavailable. On failure, the LTE switches auto
interface_x000D_
_x000D_
The
_x000D_ small
alarm form-factor
is raised if pluggable
the (SFP)
cannot module
update the not supported,
Certificate not present,
Revocation or could
List (CRL). not berefer
Please recognized.
PDDB parameter CERTH::CR
-The
"trs thepower-on
signalform-factor
small is excessively
reset": Cold
pluggable attenuated_x000D_
start_x000D_
(SFP) module detected in the interface connector does not comply
Flexi
Probable
A
-The
In Zone
loopback
the
the port
alarm:at Micro
cause:
isthe FDD,transmission
The
requested
connected Flexi
forfaranZoneEthernet
end Micro
links selected
node TDD:_x000D_
interface
is switched for clock
either
off source
locally are BTS
at the faulty.orThe
the reason
Link OAM canclient of with
be alarms theon the
BTS theSFP setmodule
isinterfaces types
(for
into loopbackexa
"trs
No watchdog
SFP
signal module
is reset":
received was onSystem
expected
the overload_x000D_
by
interface the SW,
referenced but found
in themissing.
alarm text. All other transmission alarms related to this signal are suppre
Protocol
On
"trs
Probable an
software can
interface
causes: be forPDH,
failure": which Timing
Software over
the Link Packet
OAM
failure_x000D_ (ToP) and Synchronuous
_x000D_
-"trs
A
Probable No management
SFP
Link OAM module
causes PDU for reset":
is inserted
containing Reset at triggered
the
Ethernetainterfaces:_x000D_ SFP-based by management
Ethernet interface_x000D_
interface.
critical link event flag was received on the Ethernet interface. The alarm is raised with the first de
Unit
-"trs The Number
spurious
SFPismodule's is optional:
reset": Reset
interface reason
contacts detection are failed_x000D_
corroded
--For
A amalfunctioning
cable
PDH and cut or there
of
Synchronousthe is
SFP no cable
transceiver
Ethernet, connected
Unit was to theisor
detected.
number
dirty, preventing either read access to the SFP module at the time of rea
interface_x000D_
0 or 1.
-_x000D_
The
-Excessive
The The
the SFP
following
electrical module critical
signal type link is not
events
isaexcessively supported.
are possible:
attenuated_x000D_
-It
-2. is SFP
not
"$date"
hasbit reported
present error for Timing
is rate. anThe
transmission
Over
measured Packet(TOP).faultbitPeriodcondition
error rate and has disabled
exceeds the threshold the laser
valuetransmitter.
of BER-3
Errored(10E-3).
- Critical the atformat
portEvent: the either local
connected time
far stamp
Errored endSymbol node (GMT+/-xx:xx)
is switched .off_x000D_
Event,E.g:an2014-04-12
Errored Frame 00:51:26
Event GMT+0530_x000D_
an Frame Period Event or an Errored
_x000D_
-The
Loss
_x000D_ Dyingfault is generated
of Gasp:
multiframe. eitherThe the only localwhen
interface or the the interface
remote
referenced inisthe
peer not
has configured
a fatal
alarm texterror
has asand LMP
lost is
the(that
about is,togenerated
multiframe restart. only when the interface is configured
alignment.
The
Probable
Fault: causes:
thevaluelocal ispeeroptional: has detected a physical link fault byin receiving direction, e.g.device
a LOS.
The
-ProbableForfault
the PDH
signal isthe
indication generated
level valuesignal
is toorangeonly
low when
is received.
depends
(optical the This
oninterface
signal
the is
is not
hardware configured
generated
unitaretype: aselectrical
an
1..16 LMP (that
intermediate is,PDH
generated only
in thewhen the interface
forward direction is configured
because it d
has not been or cables
configured dirty,
to meet the framingconnectors or cables
of the interface atare
thecorroded)
- the
Remote For specified
Synchonuous
length sentofvalue
the
by cable range
the is=exceeded
1..3
All
-Unit It other
the not transmission
ismissing.present
connector is for
not alarmsover
Timing
properly related Packet.
connected to this to signal
the unitare suppressed.
The slot has been configured to hold a unit but the plug-in_x000D_
-unit theisreceiver
has
in the a slot._x000D_
LOS, has LOF failedor AIS alarm on its receiving interface.
Probable
The alarmcause: is triggered There is a transmission
whenever a service problem
OAM error somewhere
related to in the
the transmission
_x000D_
of Continuity Check Messages (CCM) persists on aAIS given Ethernetitinterface
When
Probable a MEP receives
causes:_x000D_ a valid ETH-AIS frame and is enabled, shall trigger an AIS alarm containing the following informati
as soon as
-receiving one interface
_x000D_
Five consecutive
The following alarms failed arelogin attempts to the FTM have been performed.
defined:
-A the -MD
unit levelbeen
has configured
1)requested
MDL_MISMATCH,
-Source certificate
MAC address priority
(highest detected_x000D_
retrieved priority): from CCMthe is receivedauthority
-A the
lower unit
than
requested is broken
the highest
certificate and therefore
configured
could not not
beone detected_x000D_
in
renewed the BTS
from and
the not matching
certificate any
authority of (CA).
The
-the alarm
theconfigured
unit has is raised
been if the alarmbut
configured is enabled,
some other theunit BFDisstate for the session is not AdminDown and nevertheless no BFD packet is
detected_x000D_
NOTE: In FSMr2, ones. pure number interface arethe used (eg. 1,2,3). But for FSMr3 unit types, interface is provided as: from
"module type n
_x000D_
The
Ex:
A alarm
CCM
requested is
fault raised
level
certificate if the
- prio could alarm
5 BTS,
cause
not beis enabled,
MDL_MISMATCH
retrieved BFD
as the numberstate of the session
of"interface
certificates is received
from repository BFD
server packet
(RA) or the far
certificate end
au
NOTE:
NOTE: In Flexi
unitindicates Zone
variable should Micro interface
be5:replaced is provided
by appropriate as: EIF
HW which
namesisconfigured number". (unitTypeConfigured)
2)
This MAID_MISMATCH
alarm priority
that there isCCM a mismatchis received between with MDL BTS configuration configured
and auto-negotiation result.during runtime reporting.
in
The theRTTBTS, but withalarm
threshold MAIDisnot sent matching
in case any the MA average configured
value of in the
the RTTBTS exceeds_x000D_
on
this
the MDL.
configured threshold. shall be sent in case the configured value of PLR is exceeded.
The
Ex:CCM PLR faultthreshold level 5alarm prio 5 cause MAID_MISMATCH
3) MAID_MISMATCH
accessible if theand NTP MAID,
server cannot be used._x000D_
but the
Note 1: VLAN
Filtering membership
time is not of the to
used received
clear the frame does not match the VLAN configuration of the addressed MA.
alarm._x000D_
Ex:CCM
Note fault level
2: Filtering time 5 prio
is not 5 cause
applicable MAID_MISMATCH
for FSMr2._x000D_
4)may
It ERR_CCM,
take up to priority
1 minute 4:CCM is received
to raise the alarm withon knownFSMr2. MDL and MAID, but MEPID
_x000D_
The period of notification in advance is configurable and the same as for CA certificate expiry._x000D_
FTM
_x000D_ Fault, for which fault name is mentioned in the Fault name field, is toggling in the FTM. Toggling fault condition is informed
Fault._x000D_
1
Inday case...the
4999 days with
incoming SSM default
is not 1825
receiveddays._x000D_
for a certain time period (configured via "ssmTimeout" parameter) this an alarm is rais
This alarm is raised when the received SSM indicates lower clock quality (e.g. "do not use" or "EEC") than required.
The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP.
-During
The eNBthe does
BTS IP notaddress
the BTS within
tests a certain
the direct time (5
attached sec) upon
already message
configured BTSs, on
-warning
The eNB receives
shall contain fromthe ToP Master
IP message
address. For rates
each (sync
DAD message
event a rate,
be that does not match
indicated._x000D_
SW does not support the detected HW unit type._x000D_
_x000D_
Probable
BTS causes:_x000D_
has entered IPsec emergency bypass active state where
The
_x000D_base station is currently capturing IP traffic towards a localconfigured
port or intoIPsec
a file policies are ignored
on the base station. and all traffic is sent unprot
ifThis
thealarm
- The traffic
system capturing
module's
will isSW
be triggeredhappening
when attowards
version isleast a local
too old_x000D_
one port,
primary port tunnel
IPsec and destination mac has
fails and BTS address needs
switched to be
over to provided.
secondary IPsec tunnel.
Port values
- Supported
As can
a result ofHW be LMP
variant
failure or
in atnot < HW MODULE
present
least in system
one primary NAME >-<PORT
module
IPsec ID>.
tunnel, BTS has automatically switched over to secondary IPsec tunnel termin
i.e LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1
Meaning in release RL60
Software update in the module or submodule has failed.
The reference frequency that the BTS master clock receives has changed by about 0.2 ppm or more (which equals the change
_x000D_
Connection to a module that belongs to the BTS configuration has been lost.
The cause of the alarm might be:_x000D_
A module initialization has failed._x000D_
_x000D_
1. The reference
FCM/FSP frequencyhas
synchronization hasfailed._x000D_
changed because of a fault in the transmission network synchronization (which in turn is cause
reference synchronization. The
A new module with incompatible SW hasalarm canprobably
also be activated if the in
been inserted faulty reference synchronization is corrected and there is agai
the BTS.
_x000D_
A new
2. The module
referencewith incompatible
frequency SW has
fluctuates probably been
continuously inserted
because in the amount
of a great BTS. of jitter/wander in the transmission network. The
G.823/824/825._x000D_
The SNTP time cannot be fetched from the transport system (FTM) within the time limit.
_x000D_
3. If the BTS-integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (extern
The downloaded SW is corrupted or incorrectly formed.
case._x000D_
_x000D_
4. There isisan
A module equipment
blocked fault Site
with BTS in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason
Manager._x000D_
_x000D_
The user has blocked the cell with BTS Site Manager.
The purpose is to avoid fault indications that might be raised during the module maintenance task.
The BTS is blocked with BTS Site Manager. The purpose is to avoid fault indications that might be raised during a BTS mainten
The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected.
A non-supported unit has been detected in the System Module. Typically, this happens when a new unit version is installed whil
A flash memory operation failure. If this alarm continuously appears, the flash chip might be broken.
The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, an out of memory s
_x000D_
Antenna (RP3) link is down: transmitter or receiver drops from synchronization.
If only one FSP in BTS generates this fault, there is malfunction in one of the FSP submodules. If all FSPs generate this fault, th
High or low voltage on the external alarm line.
The user specifies the fault text during commissioning.
BPF file or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing.
Communication with an application failed. It has not replied to the message that has been sent/resent to it.
The requested channel in the startup phase is not acceptable for the BTS hardware, because of an incorrect frequency band an
The baseband bus related configuration of <x> was rejected by the HW SW, DSP, or RF SW.
The baseband bus synchronization towards <x> failed.
The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the power-on.
The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is lower than 205 or greater than 3891
The output signal of the OXCO is missing and the FCM/FCT cannot deliver the 30.72 MHz System Clock required by the other
A request to retrieve the public IP address information of the FCM/FCT from the FTM fails.
The temperature measured from sensor specified in "Temp.Cold.Start.Sensor" (= FSP)is less than "Temp.Cold.Start.Limit"
The
The BTS cannot
Masthead start properly,
Amplifier (MHA) because
does not the FSPs
work cannot
properly. bereceived
The poweredRF
upsignal
at too level
cold conditions.
is decreased.
The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased.
If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to by-pass mode. In by-pass mode, the MHA has no
Radio
or just Module
one (60W RRH) or Filter (all others) has detected overcurrent on the antenna line. The antenna line might be damage
of them.
If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to by-pass mode. In by-pass mode, the MHA has no
VSWR
branches value exceeds
or just one ofthe defined level. The antenna line is mismatched or damaged.
them.
Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is sl
The filter has detected a malfunction in the LNA unit.
Antenna tilting is not possible or might function incorrectly.

A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).

The unit
Synch cannot
slave BTScomplete the start-up.
has not detected incoming synch.
The heater control connection of the FSM is faulty, there is no heater or the heater is faulty.
RF Module cannot serve all cells commissioned to the RF module, there are not enough FSP resources for commissioned cells
A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the MHA fro
The SRAM memory operation failure. If this fault appears continuously, the SRAM chip might be broken.
The SRAM memory operation failure. If this fault appears continuously, the SRAM chip might be broken.
The RF Module configuration failed because of HW or SW fault.
The RF Module TX path is not usable.
The TX output power adjustment failed.
The RF Module filter has measured too low TX power.
The RF Module RX RF synthesizer is not locked.
The RF Module is out of order because of a software or hardware fault.
The Power Supply has detected an overvoltage, undervoltage or overcurrent in the RF Module.
The feedback signal to predistortion is too weak or missing. The TX performance is degraded.
The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module pro
An RF Module power-on self-test failed at start-up.
The RF Module lost lock to the incoming clock.
The highest temperature exceeds the power decrease limit.
The FPGA software update has failed.
A shared (Medusa) FR is blocked.
Radio Module cannot identify the used fan type or the fan is not installed at all.
Fan(s) are not running.
Fan(s) are rotating slower than requested.
Fan(s) rotate faster than requested.
Validated module temperature is higher than the predefined maximum allowed value.
Validated sensor temperature is greater than or equal to the predefined value on unit property file.
The validated temperature of any PA sensor is higher than or equal to the predefined value on unit property file.
Increased bit error rate has been detected on the optical link to radio module which results in sporadical LCV errors in downlink
Abnormally high bit error rate has been detected on the optical link to radio module which results in permanent baseband proce
Antenna line has been disabled to protect HW
FR module detected permanent RP3 routing collisions either in downlink (TX), or in uplink (RX) transmission direction.
The Small Form Factor Pluggable (SFP) malfunction has occurred, or the SFP module is not physically present (there is no elec
The Small Form Factor Pluggable (SFP) malfunction has occurred, or the SFP module is not physically present (there is no elec
The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fibre cable has been detache
The fibre cable has an interference; the data becomes faulty.
The connection between the System Module and the RF Module units (Linear Transceiver, Antenna Filter or Antenna Line Devi
The RP3 channel lost the frame synchronization state that it had achieved.
A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example)
#N/A
The control message traffic between the modules is malfunctioning.
Synchronization to the clock control unit frame pulse has been achieved earlier, but it differs from the currently received frame p
The master frame in the received baseband bus frame is not in the correct place related to the internally generated master fram
A decoding error has been detected in the baseband internal link. The data packet is lost, or the content is corrupted._x000D_
_x000D_
There is a baseband bus address mismatch in the summing. There are two possible causes:
This situation is also triggered when the links do not synchronize with each other.
The frame alignment is lost or the frame burst has a CRC error when the_x000D_
1. A configuration
working(two different baseband units functioning) - after an acknowledgement the fault returns.
The frame alignment is lostas
or athe
synchronization slave
frame burst has system
a CRC errormodule._x000D_
when the_x000D_
System
2.
Clock Modulebuffer
Datacrossing is working
corruption as -aappears
on underflow
the bus synchronization
or overflow RXslave
onceinwhen system module._x000D_
unsynchronized
block and the data is
received sent
data by the
might be baseband.
not valid. The fault is an indication of ei
The SW update to the BTS has failed or BTS SW corrupted.
Baseband bus message multiplexing slot for the message is not possible to be fulfilled.
If a message does not get routed, an interrupt is generated._x000D_
_x000D_
Summing checks headers of the messages to be summed. If the header is none of the allowed types, no summing is performed
Considered normal when Faradays are starting up and RP3 sync done.
Transmitter detected an RP3 message from a summing coincident with a transmission rule.
Transmitter detected more data coming from a summing than the current link rate can support.
The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the System Module._x000D_
_x000D_
baseband unit.
This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configu
matter
Too many whatLCRsthe lower level source statuses
are commissioned to one RF are.
Module.
The BTS detected
Background an RF Module that cannot be put into use without a BTS reset. The RF Module type differs from the previous
information:
_x000D_
There
Because is aoffixed synchronization
TX path failure MIMOpriority list Input
(Multiple in the Multiple
FlexiBTS: Output) functionality is not operational or is degraded in the cell relate
FSP overheat occurred. Restoring the FSP normal temperature and resetting BTS is needed in order to put the card back into u
The power level defined in the RNW file is not supported by the HW.
_x000D_
-Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. No
startup:
BTS has No FSP
detected units detected
communication by the time
problem RP3GPS
with the configuration starts._x000D_
receiver._x000D_
_x000D_
-Priority
The 2: external
baseband 2.048MHz
bus related SRIO signal connectedfor
configuration toFaraday
the Synccore In interface.
was rejected by the platform SW.
The BTS
Fault detected
is ignored anthe
until FSP Module
GPS thathas
receiver cannot be put
reached theinto use without astate.
commissioned BTS reset. The FSP Module product code differs from t
Connection to the DSP submodule has been lost or the submodule reports an error situation.
-Priority 3: the reference signal coming from the integrated transmission unit (FTM).
Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP.
Normally,
BTS Fault,allwhich
the FlexiBTS
fault name sources are not in
is mentioned in the
use"Fault
at thename"
same timefield,(itisdepends onthe
toggling in theBTS.
network planning
Toggling alarmand BTS configuration).
condition is informed
generate
Fault. a fault. During runtime operation, the BTS fault functionality runs autonomously -
Commissioning file download has been started neither from BTS Site Manager, nor from NetAct during autoconfiguration. notices also added/vanished source
Autoc
The source
The commissioning file is(which
for the FTM missing, or an
is the incorrect
priority SCFfor
3 source filethe
hasFlexiBTS)
been detected
can beduring BTS startup
TDM interface as follows:
signal (e.g. E1, T1...), physical la
priority selection
FSM should is not
be the radiofixed but user-selectable.
master for RFSW, but noticesFurthermore,
that RFSW if a signal
alreadylisted
hasinanother
the FTM references
radio is not received, a BASE S
master defined.
1. Commissioning data: the commissioning file is missing or a parameter has a missing or incorrect value.
2. RNWhas
A filter data:
not"RNW not found",
been able to tune"RNW
on an has wrong format",
appropriate "RNW
sub-band could(tuning
properly not befailure),
parsed",or"RNW hasmajor
another wrong schema",
failure "Validation
has been detecte
An alarm message has been received from the antenna line. The antenna line is faulty.
An alarm message has been received from the antenna line device. The antenna line operation is degraded.
Radio Module or Filter (all others) has detected overcurrent on RS485 IUANT
port. Some antenna
The highest validatedline device is causing
temperature value onoverload.
the FSP Depending on HW
board exceeds theimplementation
threshold value.antenna line devices powered by the R
-Overcurrent
The parallelwasRP3-01 linkson
detected towards
RS485one radioport.
IUANT module have
Some too large
antenna line mutual
device length difference
is causing (more
overload than 60exists
or shortcut meters).
on The
port.main
Ante
-Fan
RF speed
sharingis has been disabled on master WCDMA.
too low for successful detection. Detection attempt takes place again after the fan test timer expires.
A long distance (high latency) between the FSM and the antenna has been detected, but the Distributed Site feature is not enab
Temperature on FSP board exceeds critical threshold value.
Fan(s) are not running although the control is higher than 0.
4082:
Source
4082: unit reached maximum number of reset retries, that is the source unit cannot finish successfully start-up after SW updat
Source
4082: unit reached maximum number of reset retries, that is the source unit cannot finish successfully start-up after SW updat
4083:
Source
Source
File unit
unit reached
System requests maximum
SW fallback
access operations number
likedue
file toofcritical
resetmounting
System retries,
problemthat is the
which
or file sourcefailed.
occurred
opening inunit cannotafter
start-up finish
SW successfully
update, thatstart-up after SW data
is configuration updatm
4083:
Source
Flexi
4083: unit Module
Radio requestshasSWdetected
fallback lowduedownlink
to criticalcarrier
problem which
input power occurred in start-up
from the after SW
Flexi System update, that is configuration data m
Module.
4085:
Source
BTS hasunit
Transport requests
detected
SW RFSW
on source fallback
module
unit powerduecycle
indicates to critical
need failureproblem which
and is trying
for software occurred
to
fallback. recoverinfrom
start-up after SW
the failure update,
during BTS that
resetisprocedure.
configuration data m
4085:
BTS reset will last longer due to additional actions performed by BTS to recover from faulty situation.
Summing service
Transport default unit
SW on source configuration
indicates needhas failed.
for software fallback.
4085:
The master system module has lost optical
Transport SW on source unit indicates need for softwareconnection tofallback.
the peer system module.
Synchronization is lost when the System Module is working as a synchronization slave System Module. This indicates usually th
Poor GPS antenna installation
The GPS receiver is running a site/self survey
There is no accurate position stored in EEPROM.
The receiver is used in stored position but has been moved to a new position after that.
GPS receiver has detected that one or more EEPROM segments have been found to be corrupted at reset and had to be set to
Feeding voltage is disabled for selected Antenna Line.
HDLC link is disabled for reporting Antenna Line or IUANT port.
SW file validation against its signature failed.
#N/A
#N/A
Application of LTE505 feature related transport network configuration or re-configuration has failed.
#N/A
Configured PHICH transmission power boost cannot be applied either partly or at all due to a lack of remaining power after con
#N/A
The transport path (SCTP) for connection to MME has broken. The reason for this can be an unplugged cable to MME. No tran
The transport path (SCTP) for connection to an adjacent BTS has broken. The reason for this might be an unplugged cable to t
There was an opening, reading, or file content problem with a radio network configuration file at the BTS startup or at activation
RAML2.1
BTS raisesformat).this fault if it experiences a problem in internal configuration
data raises
BTS distribution (cellifsetup)
this fault to C- andaU-Plane
it experiences problemSW components
in internal configuration
data distribution (cell setup) to C-Plane and U-Plane SW components.
This fault defines a failure in the trace connection between the BTS and the iOMS or a third party tool._x000D_
_x000D_
There was an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup.
Failure has occurred during activation/deactivation of Trace Session (Subscriber trace or Cell trace or Interface trace session)._
_x000D_
BTS has encountered few possibly misconfigured PLMNs that cannot be used by BTS for accepting calls from new UEs selecti
In case of Subscriber trace, the possible reasons are:_x000D_
This
-These alarm indicates
Subscriber Trace that the maximum number
enabledofat LNADJ and/or LNADJL was exceeded in the eNB and that the new object wa
PLMNs that feature has
are considered not been
misconfigured bythe
BTSBTS._x000D_
are:
-#N/A
- Id used for
currently the subscriber
configured at BTS trace session
for one is already
or more cells in use for another active subscriber trace session._x000D_
-#N/A
Count of subscriber trace sessions at
- served by one or more MMEs and therefore currentlythe BTS has reached the maximum
broadcast number of subscriber trace sessions supported by t
by BTS's cells
- Handover
but none of at
theseBTSPLMNs
is ongoing
have for the UEMME(s)
serving to be traced_x000D_
with relative capacity greater than zero. Because of this, BTS cannot select any
#N/A
_x000D_
In
A case of Cell/Interface
Allhandover
previously target
registered trace,
cell cannot
UEs in the
be possible
uniquely
these PLMNs reasons
selected
remain are:_x000D_
because several candidates are available for a certain PCI value and carrier
unaffected.
-Base
Cell station
Trace feature has not been enabled at the BTS._x000D_
executed baseband board (FSP) recovery activities. All baseband boards are available again but not all cells could
- Id used for the cell/interface trace session is already in use for another active cell/interface trace session._x000D_
The EARFCN
- Count of cell of a LTE
and neighbor
interface tracecell is a mapped
sessions EARFCN
at the BTS according
has reached thetomaximum
the MFBI-profile
numberconfiguration, that is, trace
of cell and interface the requirement
sessions s
As
#N/Aa consequence HO to this neighbor cell is not possible and call drop rate might increase in case no other suitable handover
#N/A
The X2 interface reset has failed after several attempts. This indicates that a severe failure has occurred, for example there is s
There is no X2 connectivity to an adjacent BTS, the adjacent BTS has failed, and so on.
There is no S1 connectivity to an MME, the MME has failed, etc. If the fault is canceled, autonomous recovery actions (reset) so
S1 interface reset has failed after several attempts. This indicates that a severe failure has occurred, for example there is some
Cell is deactivated due to no S1 availability (that is, none of the PLMNs configured for the cell have a serving MME currently) fo
Otherwise,
S1 eNB configuration the period update length isprocedure
set to 15 has min.failed.
A
Note: RIMArequest
cellcould to the serving
is considered BSS S1
to have failed after several
availability when attempts.
there atThis
is one leastmeans
one that System
configured Information for which
the related GERAN neig
The MME not be informed about modification of at least of the following eNBPLMN of the cell
configuration data: is currently serve
S1
-An eNBavailability.
RIM association could not be established because an RIM Error PDU has been received or an RIM Application Error has be
Name
-System Supported TAs (TAC,
Information PLMN Identities)
Broadcast related parameters have changed more than 32 times within 3 hours.
-The Default paging DRX
technical log buffer has been frozen in the BTS for an internal reason.
Physical memory supervision detects that usage of memory has exceeded 90%(FCM/FCT)/ 98%(FSP).
Non correctable bit toggling error is detected in the critical DSP memory.
#N/A
#N/A
#N/A
The transport part of the BTS has been reset at the date and time given in the notification.
A change to the BTS IP settings has been received from the BTS Site Manager. To activate the change, the BTS needs to be re
1.FSMr2 supports the following cause for the reset:
The alarm is raised if the BFD service is not available anymore on the BTS for all BFD sessions belonging to that BFD group.
"trs power-on
Loss of frame.reset": It is not Cold start :to carry traffic on the interface referenced in the alarm text. All other transmission alarms related
possible
"trs watchdog
No signal is received on the interfacereset": System overloadreferenced in the alarm text. All other transmission alarms related to this signal are suppre
"trs startup
Probable failure":
cause for E1Failure during The
interfaces: startup interface at the far end is not configured to be a framed E1 interface.
A
"trs dead peer was
software failure":detected
Software in one of the IPsec associations of the FTM.
failure
Probable causes for Ethernet interfaces:
"trs
Probable
The
-Possibly management
smallis
a cable cause
cut orfor
form-factor reset":
there isReset
T1pluggable
interfaces:
no cable triggered
The
(SFP) by management
interface
module
connected atthe
theinterface
todetected interface:
farinend
theisinterface
not configured
connector to be a T1
does notinterface.
comply with security requirements.
"trs
-- the
Primary fallback":
electrical
and Fallback
signal
secondary executed
is excessively
timing source attenuated
lost. ThetoLTE
a cable is cut or there is no cable connected theisinterface
running on internal clock or in hold-over mode and no timing signal is sen
--FSMr3 the
the
One of supports port
signal at isthe connected
excessively
the synchronisationthe following
far end
attenuated
sources
cause in
node
for the is switched
theconfigured
reset:
off
priority list is unavailable.
The
-This
This thefirst
portand
can atisthe
be second connected
primary synchronization
far end nodesourcesisclock from
switched the
off configured priority list are unavailable. On failure, the LTE switches auto
alarm raised if theorBTS the secondary
cannot update thesource.
Certificate Revocation_x000D_
"trs
List
Probable
A power-on
(CRL).cause:
loopback reset":
Please The
is requested refer Cold for start
PDDB
transmission parameter
an Ethernet links selectedCERTH::CRLInfo:
interface for clock
either CRLUpdateFailureReason_x000D_
source
locally are BTS
at the faulty.orThe
the reason
Link OAM canclient
be alarms
of theon theisinterfaces
BTS (for exa
set into loopback
In
"trsthe
for alarm:
watchdog
failure reasons. reset": System overload
Protocol
On
"trs an can failure":
interface
software be for PDH, which Timing
Software over
the Link failure Packet
OAM (ToP) and Synchronuous
"trs management reset": Reset triggered by management interface
A Link OAM PDU containing a critical link event flag was received on the Ethernet interface. The alarm is raised with the first de
Unit
"trs Number reset":
spurious is optional: Reset
A
-For malfunctioning
PDH and of the
Synchronous SFPreasontransceiver
Ethernet,
detection
Unitwas failed
detected.
number is 0 or 1.
The
The following
SFP has critical
reported linka events
transmission are possible:
fault condition and has disabled the laser
-It
Excessive
-2.Criticalis not present
The "$time" bit error
Event:format for Timing
rate.
either is The
anGMT. Over
Errored Packet(TOP).
measured
E.g.Symbol bit
2013-03-07 error
Period rate
00:51:26
Event, exceeds
GMT
an the threshold
Errored Frame Event valuetransmitter.
of BER-3
an Errored(10E-3).
Frame Period Event or an Errored
- Dying
Loss of Gasp:
multiframe. eitherThe the interface
local or the remote peer
referenced in the has a fatal
alarm texterror
has and lost is
theabout to restart.
multiframe alignment.
The
Probable
Fault:causes:
thevaluelocal ispeer
optional:has detected a physical link fault by in receiving direction, e.g.device
a LOS.
-Probable
the indication
For signal
PDH the
level valuesignal
is toorangeis received.
low depends
(optical This
on not signal
the is generated
hardware unitare
type: an
1..16intermediate PDH in theare
forward direction because it d
has been or cables
configured dirty,
to meet electrical
the framingconnectors or cables
of the interface at thecorroded)
- the
RemoteFor specified
Synchonuous
length sentofvalue
the range
by cable
the is=exceeded
1..3
All It other
not transmission
ismissing.present is for alarmsover related to this signal are suppressed.
-Unit the connector The slotTiming
not properly
has been Packet.
connected
configured toto theholdunit a unit but the plug-in
-unittheisreceiver
has
in the a slot.
LOS, has LOFfailedor AIS alarm on its receiving interface.
Probable
The alarmcause:is triggered Therewhenever
is a transmission a service problem
OAM error somewhere
related to in the
the transmission
of Continuity
When a MEP Check
receives Messages
a valid (CCM) persists
ETH-AIS frame on aAIS
and given
is Ethernetitinterface
enabled, shall trigger an AIS alarm containing the following informati
Probable
as soon ascauses:
one interface
Five -receiving
consecutive failed
The following
-MD levelbeen alarms arelogin attempts to the FTM have been performed.
defined:
-A the unit
1)requested has
MDL_MISMATCH, certificate configured
priority
(highest detected
priority):
retrieved from CCM the is receivedauthority
-A the -Source
unit is MAC address
broken and therefore not detected
lower than
requested the highest
certificate configured
could not be one in
renewed the BTS
from and
the not matching
certificate any
authority
The alarm is raised if the alarm is enabled, the BFD state for the session is not AdminDown and nevertheless no BFD packet is of (CA).
the configured
NOTE: In FSMr2, ones. purethe number interface areappropriate
used (eg. 1,2,3). But for FSMr3 unit types, interface is provided as: from
"module type n
NOTE:
The
Ex:
A alarm
CCM
requestedunit isvariable
fault level -ifshould
raised
certificate prio
could benot
alarm
5 cause replaced
isbe enabled, by
MDL_MISMATCH
retrieved the asBFD the state HW
number ofnames
the configured
session
of certificates (unitTypeConfigured)
is received
from repository during
BFD
server runtime
packet
(RA) reporting.
the far
or certificate end
au
2)
ThisMAID_MISMATCH
alarm indicates that priority
there5:isCCM is received
a mismatch between with MDL BTS which is configured
configuration and auto-negotiation result.
in the BTS, but with MAID not matching any MA configured
The RTT threshold alarm is sent in case the average value of the RTT exceeds the configured threshold. in the BTS on
this MDL.
The
Ex:CCM PLR faultthresholdlevel 5alarm prio 5shall cause be MAID_MISMATCH
sent in case the configured value of PLR is exceeded.
3) MAID_MISMATCH
accessible if theandNTP MAID,
server cannot be used.
but theFiltering
Note: VLAN membershiptime is related of only
the received
to startupframe does notthe
and starting match
alarmthe notVLAN configuration
for clearing of the addressed MA.
the alarm.
Ex:CCM fault level 5 prio 5 cause MAID_MISMATCH
4) ERR_CCM, priority 4:CCM is received with known MDL and MAID, but MEPID
_x000D_
The period of notificaton in advance is configurable and the same as for CA certificate expiary described in WBTS_SEC_46333
FTM
_x000D_ Fault, for which fault name is mentioned in the Fault name -field, is toggling
in
1
Inday the
caseFTM.
...the
4999 Toggling
days with
incoming fault
SSM condition
default is informed
is not 1825 to user time
days._x000D_
received for a certain with this new
period (configured via "ssmTimeout" parameter) this an alarm is rais
FTM Fault. Toggling faults are supressed until the toggling alarm condition
This
is alarm Severity
cleared. is raised of
whenthis the
FTMreceived
Fault is SSM indicates
the same than lower clock quality
the severity of (e.g. "do not use" or "EEC") than required.
the toggling
The reference FTM Fault.
clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP.
-During
The eNB the does
BTS IP notaddress
the BTS within
tests a certain
the direct time (5
attached sec) upon
already message
configured BTSs, on
-warning
The eNB receives
shall containfrom
the ToP Master
IP message
address. For rates
each (sync
DAD message
event a rate,
be that does not match
indicated._x000D_
SW does not support the detected HW unit type.
Probable
BTS causes: IPsec emergency bypass active state where configured IPsec policies are ignored and all traffic is sent unprot
has entered
The base station is currently capturing IP traffic towards a local port or into a file on the base station.
if-#N/A
the traffic
The system capturing
module'sisSW happening
version towards
is too olda local port, port and destination mac address needs to be provided.
Port values can be LMP or < HW
- Supported HW variant not present in system MODULE NAME >-<PORT ID>.
module
i.e LMP or FSM-EIF1, FSM-EIF2 or FTIF-EIF1
State State in issue 01 State in release RL60 Unit Status
Start / Cancel Start / Cancel Start / Cancel Working
Start Start Start Out of order
Start / Cancel Start / Cancel Start / Cancel Out of order
Start Start Start / Cancel Out of order
Start / Cancel Start / Cancel Working
Start / Cancel Start / Cancel Degraded,Working
Transient Transient Working
Start Start Start Degraded,Out of order
Start Start Start Degraded
Start Start Start Out of order,Working
Start / Cancel Start / Cancel Start Out of order
Start / Cancel Start / Cancel Degraded,Out of order,Working
Start / Cancel Start / Cancel Start / Cancel Degraded,Out of order
Start / Cancel Start / Cancel Start / Cancel Degraded
Start Start Start / Cancel Degraded,Out of order
Start / Cancel Start / Cancel Start / Cancel Degraded,Out of order,Working
Start / Cancel Start / Cancel Start / Cancel Degraded,Working
Start / Cancel Start / Cancel Out of order
Start Start / Cancel Out of order
Start / Cancel Start / Cancel Degraded
Start / Cancel Start Start Out of order
Start / Cancel Start / Cancel Degraded,Out of order,Working
Start / Cancel Start / Cancel Start / Cancel Degraded,Working
Start / Cancel Start / Cancel Start / Cancel Out of order,Working
Start / Cancel Start Start Working
Start / Cancel Start / Cancel #N/A Degraded
Start Start Start Out of order,Working
Start / Cancel Start / Cancel Start / Cancel N/A
Start / Cancel Start / Cancel N/A
Start / Cancel Start / Cancel N/A
Start Start N/A
Start Start Start Working
Start Start Out of order
Start Start Working
Start / Cancel Start / Cancel Start / Cancel Degraded,Out of order,Working
Start Start #N/A Degraded
Start / Cancel Start / Cancel #N/A Working
Start / Cancel Start / Cancel #N/A Degraded,Out of order,Working
Transient Transient Transient Working
Start / Cancel Start / Cancel #N/A Degraded
Transient Transient #N/A Working
Start / Cancel Start / Cancel #N/A Working
Start / Cancel Start / Cancel Transient Working
Start Start #N/A Out of order
Transient Transient Transient Minor
Start Start Start Major
Start / Cancel Start / Cancel Start / Cancel Critical
Start / Cancel Start / Cancel Start / Cancel Major
Start / Cancel Start / Cancel Start / Cancel Minor
Transient Transient Transient Warning
Start / Cancel Start / Cancel Start / Cancel
Start / Cancel Start / Cancel #N/A Major
Start / Cancel Out of order
Start Out of order
Transient Working
Start Out of order
Start / Cancel Degraded,Out of order
Start / Cancel Degraded,Working
Start Out of order
Start Out of order
Start / Cancel Degraded
Start Out of order
Start Out of order
Start / Cancel Working
Start / Cancel N/A
Start / Cancel N/A
Start / Cancel N/A
Start N/A
Start N/A
Start / Cancel N/A
Start / Cancel N/A
Start / Cancel N/A
Start Out of order
Start Working
Start Out of order
Start Out of order
Unit Status in issue 01 Unit Status in release RL60
Working Working
Out of order Out of order
Working Working
Out of order Out of order,Working
Working Out of order,Working
Working Working
Working
Working Working
Degraded,Working
Out of order Working
Working
Degraded,Out of order Out of order
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Working Working
Out of order,Working Out of order,Working
Degraded,Out of order,Working
Degraded,Out of order Degraded
Degraded Degraded
Degraded Out of order
Degraded,Out of order,Working Out of order
Degraded,Working Degraded
Out of order
Out of order
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded
Working Working
Degraded
Out of order Degraded,Out of order
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded,Out of order,Working
Degraded,Working Degraded,Working
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Working Working
Degraded Degraded,Out of order
Degraded Degraded
Working Working
Working Working
Degraded,Out of order Degraded,Out of order
Degraded Degraded
Working Working
Degraded Degraded
Degraded #N/A
Degraded Degraded
Degraded Degraded
Working Working
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
Degraded Degraded
N/A N/A
N/A N/A
N/A
N/A
N/A
N/A N/A
Working Working
Degraded,Out of order Working
N/A N/A
Working Working
Degraded Degraded
Out of order
Working
Degraded Degraded
Degraded Degraded
Working Working
Degraded Degraded
Degraded Degraded
Out of order,Working Out of order
Working Working
Working Working
Degraded,Out of order,Working Working
Degraded Out of order,Working
Degraded
Degraded #N/A
Working #N/A
Degraded,Out of order,Working #N/A
Working Working
Degraded #N/A
Degraded Degraded
Degraded Degraded
Degraded Degraded
Working Working
Working Working
Degraded Working
Working Working
Working #N/A
Working #N/A
Working #N/A
Working Working
Working Working
Working #N/A
Working #N/A
Degraded Degraded
Degraded Degraded
Working Working
Degraded Degraded
Degraded Degraded
Working Working
Working Working
Working Working
Working Working
Out of order #N/A
Out of order #N/A
Out of order #N/A
Minor Minor
Major Major
Critical Critical
Critical Critical
Critical Critical
Major Major
Critical Critical
Major Major
Minor Minor
Major Major
Major Major
Major Major
Major Major
Critical Critical
Major Major
Major Major
Major Major
Major Major
Critical Critical
Major Major
Major Major
Warning Warning
Major Major
Major Major
Major Major
Major Major
Major Major
Major Major
Major Major
Major Major
Major Major
Minor Minor
Minor Minor
Minor Minor
Minor Minor
Critical Critical
Major Major
Minor Minor
Major #N/A
Unit Status Attributes

Degraded_x000D_
_x000D_
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
Working

Out of order._x000D_
_x000D_
Degraded (When some post tests failed, but BTS is still able to provide service)_x000D_
Out of order (Post failure is causing BTS not to come into service)
Working if the fault is notified by FR, out of order in other cases.
Degraded - when no other reference clock sources are available_x000D_

Working - when there is at least one more working reference clock source available._x000D_
Out of Order (Flexi BTS TDD) - Holdover not possible because of insufficient data or phase error in holdover exceeds 3 us
Degraded: the DAC word value of the OCXO is lower or equal Min.OcxoControlValue.Alarm.Set or the DAC word value of the O
higher or equal Max.OcxoControlValue.Alarm.Set._x000D_
Out of order (Flexi BTS TDD only): the DAC word value of the OCXO is equal Min.Accept.OcxoControlValue or equal
Max.Accept.OcxoControlValue._x000D_
Degraded
Degraded (RF using RP1 protocol)_x000D_

Out
FlexiorBTS
order (RFFlexi
FDD, usingBTS
Ir protocol)
TDD:_x000D_
Out of order - in normal BTS operation_x000D_
Degraded - in normal BTS operation_x000D_
Working
Working -- while
while VSWR
VSWR thresholds
thresholds tuning_x000D_
tuning
_x000D_
Degraded (if cell can still operate because it still has enough available and needed resources: both Tx and Rx)_x000D_
Out of order (cell cannot operate because there are not enough available and needed resources: Tx or Rx). _x000D_
See Reference for details.
Degraded (other clock is not available)_x000D_
Working (other clock is available)

_x000D_
Degraded
Flexi (if cellFlexi
BTS FDD, can still
BTSoperate because it still has enough available and needed resources: both Tx and Rx)_x000D_
TDD:_x000D_
order (cell cannot operate because of not enough available and needed resources: Tx or Rx). _x000D_
_x000D_
Out of order (cell cannot operate because of not enough available and needed resources: Tx or Rx). _x000D_
Out of order during RF startup_x000D_
Working
Flexi BTSduring
FDD, RF runtime
Degraded_x000D_
_x000D_
Out of order
Not all fans failed: Module = Degraded, Fan group = Degraded_x000D_

All fans failed:
Module ModuleFan
= Degraded, = Degraded, Fan group = Out Of Order
group = degraded
Degraded - Validated temperature of any PA sensor is greater than or equal to Tdanger (when any TX/RX resources are availab
alarming FRM)_x000D_
_x000D_
Out of order - dangerously high temperature occurs longer than tT+danger and PA is turned off (when no RX/TX resources are
on alarming FRM)
Working - if raised for SSD firmware update._x000D_
Out of order - in any other case._x000D_
_x000D_
Out of order

Working_x000D_
_x000D_
Working (Flexi Zone Micro BTS)_x000D_
Out
FlexiofBTS
Order (LCR)
Out of order_x000D_
_x000D_
Degraded
Flexi BTS FDD,(7651)_x000D_
-Working (7652)
Out of order_x000D_
_x000D_
- Degraded
Flexi (not Flexi
BTS FDD, all DSPs
BTSare faulty)_x000D_
TDD:_x000D_
-Out
Outofoforder:
orderwhen
(all DSPs are faulty)prevents BTS to reach operational state (wrong or missing RNW data/active commissioning da
the problems
readable)._x000D_
_x000D_
Out of order: when the problems prevents BTS to reach operational state (wrong or missing RNW data/active commissioning da
readable)._x000D_
_x000D_
Working: if there have been problems with commissioning data in SW package but still BTS is operational.
Not all fans failed: alarming fan = out of order, fan group = degraded_x000D_
All fans failed: all fans and fan group = out of order
Alarming fan = degraded, fan group = degraded
Flexi BTS FDD, Flexi BTS TDD (macro)_x000D_

-Flexi
Out-of-order
BTS FDD, - in case
Flexi of inconsistent
BTS SW after SW fallback_x000D_
TDD (macro)_x000D_
-- Degraded
Out-of-orderin - case
- in caseof consistent SW
of inconsistent afterafter
SW SW SW fallback_x000D_
fallback_x000D_
Flexi
_x000D_ BTS FDD, Flexi BTS TDD (macro)_x000D_
-- Degraded
Out-of-orderin -
- case
in caseof consistent
of SW
inconsistent after
SW SW
after fallback_x000D_
SW fallback_x000D_
Flexi
_x000D_Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
-Degraded
Degraded in - case of consistent SW after SW fallback_x000D_
Flexi
Out ofZone
_x000D_orderMicro
- the FDD, Flexi
cell can notZone Micro
operate TDD:_x000D_
because downlink carrier which transmits PSS/SSS signals is failed._x000D_
Degraded
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_carrier which transmists PSS/SSS signals is still working.
- the cell can still operate because downlink
Degraded

Out of order_x000D_
_x000D_
Working (When no other reference clock sources are available)_x000D_
Degraded (When at least there is one more working reference clock source)
The card may be used (e.g. radio may be connected to port 1 and provide services for some cells) and this is why it is "Degrade
Status "degraded" is used for failure during BTS runtime_x000D_

Status "outFDD:_x000D_
Flexi BTS of order" is used for failure during BTS startup.
Working:_x000D_
-other valid synchronization reference source is available_x000D_
_x000D_
Degraded:_x000D_
-otherwise_x000D_
_x000D_
Working:_x000D_
_x000D_
Degraded:_x000D_
-there is no other valid synchronization reference source available_x000D_
-external GPS receiver is in holdover but the holdover threshold value is not expired yet_x000D_
_x000D_
Out of order:_x000D_
-external GPS receiver is in holdover and the holdover threshold value is expired
Unit status is Degraded if at least one other S1 interface is operational, or else the Unit status is Out of order.
Unit status is Degraded if at least one other S1 interface is operational, or else the Unit status is Out of order
Severity of this FTM Fault is the same than the severity of_x000D_
the toggling FTM Fault._x000D_
alarming fan = out of order, fan group = degraded

Degraded_x000D_
_x000D_
Working
Out of order (LCR)
Unit Status Attributes in issue 01

Degraded_x000D_
_x000D_
Working

_x000D_
_x000D_
_x000D_
_x000D_
_x000D_
Degraded (When some post tests failed, but BTS is still able to provide service)_x000D_
_x000D_
Out of order (Post failure is causing BTS not to come into service)
Working if the fault is notified by FR, out of order in other cases.
Degraded - when no other reference clock sources are available_x000D_

Working - when there is at least one more working reference clock source available._x000D_
Out of Order (Flexi BTS TDD) - Holdover not possible because of insufficient data or phase error in holdover exceeds 3 us
Degraded: the DAC word value of the OCXO is lower or equal Min.OcxoControlValue.Alarm.Set or the DAC word value of the O
higher or equal Max.OcxoControlValue.Alarm.Set._x000D_
Out of order (Flexi BTS TDD only): the DAC word value of the OCXO is equal Min.Accept.OcxoControlValue or equal
Max.Accept.OcxoControlValue._x000D_
Degraded
Degraded (RF using RP1 protocol)_x000D_

Out
FlexiorBTS
order (RFFlexi
FDD, usingBTS
Ir protocol)
TDD:_x000D_
Out of order - in normal BTS operation_x000D_
Degraded - in normal BTS operation_x000D_
Working
Working -- while
while VSWR
VSWR thresholds
thresholds tuning_x000D_
tuning
_x000D_
Out of order (cell cannot operate because there are not enough available and needed resources: Tx or Rx). _x000D_
Degraded (other clock is not available)_x000D_
Working (other clock is available)

_x000D_
Degraded
Flexi (if cellFlexi
BTS FDD, can still
BTSoperate because it still has enough available and needed resources: both Tx and Rx)_x000D_
TDD:_x000D_
order (cell cannot operate because of not enough available and needed resources: Tx or Rx). _x000D_
_x000D_
Out of order (cell cannot operate because of not enough available and needed resources: Tx or Rx). _x000D_
Out of order during RF startup_x000D_
Working
Flexi BTSduring
FDD, RF runtime
Degraded_x000D_
_x000D_
Out of order
Not all fans failed: Module = Degraded, Fan group = Degraded_x000D_

All fans failed:
Module ModuleFan
group = degraded
Degraded - Validated temperature of any PA sensor is greater than or equal to Tdanger (when any TX/RX resources are availab
alarming FRM)_x000D_
_x000D_
Out of order - dangerously high temperature occurs longer than tT+danger and PA is turned off (when no RX/TX resources are
on alarming FRM)
Working - if raised for SSD firmware update._x000D_
Out of order - in any other case._x000D_
_x000D_
Out of order

Working (FSM)_x000D_
Working (FR - although the FR is not faulty, it is taken out of use due to inconsistency with the site configuration file)_x000D_
_x000D_
Working
Flexi BTS(Flexi
FDD,Zone
FlexiMicro BTS)_x000D_
BTS TDD:_x000D_
Out of Order (LCR)
Out of order_x000D_
_x000D_
Degraded
Flexi BTS FDD,(7651)_x000D_
-Working (7652)
Out of order_x000D_
_x000D_
- Degraded
Flexi (not Flexi
BTS FDD, all DSPs
BTSare faulty)_x000D_
TDD:_x000D_
-Out
Outofoforder:
orderwhen
(all DSPs are faulty)prevents BTS to reach operational state (wrong or missing RNW data/active commissioning da
the problems
readable)._x000D_
_x000D_
Out of order: when the problems prevents BTS to reach operational state (wrong or missing RNW data/active commissioning da
readable)._x000D_
_x000D_
Not all fans failed: alarming fan = out of order, fan group = degraded_x000D_

Out
FlexiofBTS
order_x000D_
_x000D_
Out of order_x000D_
Flexi Zone
Flexi BTS FDD,
MicroFlexi
FDD,BTS
FlexiTDD:_x000D_
_x000D_
Out of order_x000D_
Degraded
FZM:_x000D_
_x000D_
Out of Order_x000D_
Degraded
Out
Flexiof orderMicro
Zone - the FDD,
cell can notZone
Flexi operate because
Micro downlink carrier which transmits PSS/SSS signals is failed._x000D_
TDD:_x000D_
_x000D_
Degraded - the cell can still operate because downlink carrier which transmists PSS/SSS signals is still working.
Degraded
FZAP:_x000D_
working
The master system module works properly.

Out of order_x000D_
_x000D_
Working (When no other reference clock sources are available)_x000D_
Degraded (When at least there is one more working reference clock source)
The card may be used (e.g. radio may be connected to port 1 and provide services for some cells) and this is why it is "Degrade
Status "degraded" is used for failure during BTS runtime_x000D_

Status "outFDD:_x000D_
Flexi BTS of order" is used for failure during BTS startup.
Working:_x000D_
_x000D_
Degraded:_x000D_
-otherwise_x000D_
_x000D_
Working:_x000D_
_x000D_
Degraded:_x000D_
-external GPS receiver is in holdover but the holdover threshold value is not expired yet_x000D_
_x000D_
Out of order:_x000D_
-external GPS receiver is in holdover and the holdover threshold value is expired
Severity of this FTM Fault is the same than the severity of_x000D_
the toggling FTM Fault._x000D_
Unit Status Attributes in release RL60
Working (FCM detected unsupported fsType value in TargetBD downloaded in SW update)

Out of Order
Working (FCM (Otherwise)
detected unsupported fsType value in TargetBD downloaded in SW update)
Out of Order (Otherwise)
Working if there have been problems with the files in the SW package but the BTS is still operational.
Out of order when the problems prevents the BTS from reaching the operational state.
Degraded (MinorTMAFault)
Out of order (MajorTMAFault)

Out of order during RF startup
Working during RF runtime
Not all fans failed: Module = Working, Fan group = degraded_x000D_

All fans failed:
Module ModuleFan
group = degraded
Degraded - Validated temperature of any PA sensor is greater than or equal to Tdanger (when any TX/RX
resources are available on alarming FRM)
Out of order - dangerously high temperature occurs longer than tT+danger and PA is turned off (when no RX/TX
resources are available on alarming FRM)
#N/A
Working - if raised for SSD firmware update.
Out of order - in any other case.

One of the links is faulty/broken or is getting incorrect messages._x000D_
FSM becomes degraded when any FSP is out of order._x000D_
FSP becomes out of order if at least one Faraday is out of order._x000D_
FSM becomes out of order if all FSPs are out of order.
Working (FSM)
Out of Order (LCR)
Out of order: when the problems prevents BTS to reach operational state (wrong or missing RNW data/active
commissioning data not readable).
Not all fans failed: alarming fan = out of order, fan group = degraded
The master system module works properly.
Out of order (ALD)

Working (Antenna Line)
#N/A
#N/A
Status "degraded" is used for failure of LTE505 re-configuration during eNB runtime._x000D_
Status
#N/A "out of order" is used for failure of LTE505 configuration at eNB startup.
#N/A
Unit status is "Degraded" if the fault is on an S1 interface with at least one other S1 interface available for use.
_x000D_
Unit status is "Out of Order" when all S1 interfaces are faulty.
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
Severity of this FTM Fault is the same than the severity of
the toggling FTM Fault.
#N/A
Effect
The operation of the BTS possibly decreases.
If thefault
This FSPdoesupdate notfails, the BTS affect
immediately capacitythe drops.
operationsIf theofoptical
the BTS,interface
but it FPGA SW update
is a notification thatfails,
the communication
BTS master clock to radio modules
frequency dev
_x000D_
The BTS master clock tuning continues regardless of the alarm, but because the BTS master clock adjustment is quite slow to
The module
Flexi Zone Micro in question
FDD, Flexiis outZone
of use. This
Micro fault cancels all the active faults for the same module.
TDD:_x000D_
The BTSare
All cells is not
not operational._x000D_
operational.
The BTS capacity possibly decreases. Some cells might become disabled._x000D_
The BTS is provided
Resources out of order. by the module cannot be used, which means that some features might not work._x000D_
_x000D_
Resources provided by the module cannot be used, which means that some features might not work._x000D_
If the fault is reported for FR module, BTSOM does not know the real FR module state, and thus BTS SM keeps FR LED displa
_x000D_
Real time isthe
Therefore, notRF available.
LEDforand Alarms,SM logs, and all reports have incorrect time._x000D_
If the fault is
_x000D_ reported FRBTSmodule, LED display
the BTSOM status
does notcannot
knowbe aligned.
the FR module's real state, and thus the BTS SM keeps the F
The BTS continues
situation. Therefore,its operation
there with the old
is no possibility file. the RF LED and BTS SM LED display status.
When btsSyncMode is PhaseSync and thetoalarm
align occurs during startup, the BTS will not go onAir as long as the alarm is active
The
_x000D_BTS continues its operation with the old software.
When
If the SW btsSyncMode
download to is any
Phase HWSync, the failed,
unit has alarm is thecanceled during startup,
eNB continues operating and thethe
with alarm is present
currently for more
running than five minutes, th
SW version._x000D_
_x000D_
The BTS does not send faults related to the blocked module to the network management system (NMS). The fault sending to B
If the SW activation has failed on FCM/FCT in the master FSM, the eNB continues operating with the currently running SW vers
_x000D_
The
_x000D_BTS does not send any faults related to the blocked cell or the modules commissioned to the blocked cell to the network m
It is not possible to establish phone calls through the blocked module. In the case of dual mode configuration, that is, the radio
_x000D_
If
The
BTStheBTS SW does
OAM activation
system not is has
send failed on another
any other
needed. HW unit
faults other than(for example,
transport RFtounit),
faults then:_x000D_
the network management system (NMS) when the BTS is
Calls
1. The
_x000D_ through
eNB the blocked
restarts and cell are with
operates transferred
the new toSWanother cell.installed._x000D_
version It is not possible to establish new calls through the blocked cell.
2.
All
The Eventually,
cells if the SM
are disabled.
operator (BTS eNBand is integrated
OMS/NetAct) to theis NetAct,
informedafter thethe
about automatic recovery SW update,
autonomously-triggered the eNB
recovery restarts and operates wit
reset._x000D_
Flexi
_x000D_
FCM/FCT or FTM is fault source: BTS startup is terminated._x000D_
Flexi
Flexi Zone
BTS
Zone Micro
FDD,
Micro FDD,
Flexi
FDD, BTSFlexi
Flexi Zone
ZoneisMicro
TDD:_x000D_
Micro TDD:_x000D_
TDD:_x000D_
FSP
The or
SW DSP is fault source: FSP not taken into use._x000D_
The BTSupdate
Depending
Depending
_x000D_ is on theto reported
operational.
on the this BTS severity,
reported might notthe
severity, beBTS
the possible
BTS capacity
capacitywithout special
might
might have actions.
have decreased
decreased The(BASE
BTS continues
(BASE STATIONits
STATION operation with
OPERATION
OPERATION the old software
DEGRADED,
DEGRADED, CEL
CEL
_x000D_
For resources that are not in use (not commissioned) lack of support_x000D_
Flexi
The BTS
Flexi Zone Micro
Zonememory
Micro FDD, Flexi
operations,
FDD, Zone Micro
for example
the software download and parameter updates, are not stable._x000D_
TDD:_x000D_
is
BTS reported
service byisminor
degradedseverity alarm
or out (BASE STATION NOTIFICATION).
_x000D_
BTS BTS
The is notmemory
operational.operations, forofexample
service. the software download and parameter updates, are not stable._x000D_
The
_x000D_ISTI (In Service Time Indicator) value for HW Repair Center might not be correct or readable.
The BTS memory operations, for example the software download and parameter updates, are not stable._x000D_
The
The
The
The BTS capacity decreases. The digital signal processing (DSP) does not work correctly.
The ISTI (In Service Time Indicator) value for HW Repair Center might not be correct or readable.
The BTS capacity decreases or the BTS is not operational. The Digital Signal Processing (DSP) does not work correctly.
The
There BTS is not
is no actual operational
effect to BTSor thefunctionality.
capacity is degraded._x000D_
This is user-specific.
_x000D_
There is no actual effect to BTS functionality.
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ This is user-specific.
The
There BTS is not
is no actual operational.
effect to BTS functionality. This is user-specific.
There is no actual effect to BTS functionality. This is user-specific.
The BTS is not operational.
Some action inside the BTS is interrupted. The BTS does not operate normally. The fault is in the unit reported in the fault sourc
The
This BTS
fault capacity
preventspossibly
the BTSdecreases.
from functioning. The cell with incorrect
Depending configuration
on <x>, some processing is not working._x000D_
resources, some cells, or the whole BTS are
_x000D_
This fault can prevent the BTS from
Flexi Zone Micro FDD, Flexi Zone Micro TDD: _x000D_ functioning when the RF Module is needed for the required cell configuration.
The BTS
Flexi BTScapacity
FDD, Flexi possibly decreases.
BTS TDD:_x000D_
_x000D_
The system clock frequency starts drifting and the air interface frequency accuracy starts to degrade. The BTS might work prop
FDD:_x000D_
Flexi BTS
If other FDD, Flexi
references areBTS TDD:_x000D_
available, the synchronization reference source changes to another source. Tuning then follows this new
The
If
The BTS
other
BTS can
is notoperate
references areproperly for months
not available,
operational. the BTS or even
master a year
clockwhen being
(OCXO) in theis5%
tuning margin
halted andarea, but eventually
the BTS the DAC
synchronization dropsvalue reac
to holdo
synchronization
_x000D_ setting defined in the BTS commissioning._x000D_
The BTS is not commissioned or integrated to the network. The BTS cannot be accessed or configured remotely._x000D_
_x000D_
TDD:_x000D_
_x000D_
Effects
The BTS
If other in FDD Frequency
cannot
references goare
to the Synchronization
operational
available, state.mode:_x000D_
the synchronization reference source changes to another source. Tuning then follows this new
Assuming
The MHA is degraded and the RX signal has
If no other that
valid the BTS
reference reference
available, signal
BTS correct
tuning
level mode
might accuracy
bemoves whennormal
from
decreased. the DAC
The size value
to of
holdover.reaches
the cell the
be adjustment
If holdover
might limit 0because
is not possible
reduced. or 4095 (mea
of ins
not met any more. Even in that stage the BTS might still be operational but the system performance might drop, affecting, for ex
_x000D_
The MHA is faulty and the RX performance might be degraded. The size of the cell might be reduced.
_x000D_
Effects
The
Tuning in FDD
antenna
does not Phase
line is notSynchronization
follow operating
the external mode:_x000D_
correctly. The cell capacity might be decreased.
reference._x000D_
When
ClockBTS
Flexi the
tuningDAC
FDD, value
is halted reaches
and the
Flexi BTS the adjustment
BTS continues its
TDD:_x000D_ limit 0 or 4095,
operation the basic
based on theLTE system
internal ovenoperation effects are the same as in Freque
oscillator._x000D_
more._x000D_
The air interface accuracy of 0.05 ppm is kept for at least 24 hours. Within that time, the BTS can work properly but
In
The VSWR
outputThreshold
_x000D_ power at Tuning modeis- there
the antenna decreased is no impact
because toof
the state
the of the of
reflection cell/radio
the signalmodule._x000D_
in the TX path. The antenna is the
not network
working
_x000D_
Flexi
The Zone
RX pathMicro FDD,
operating Flexi Zone
performance
In case of not CPRI/IR radios:_x000D_ Micro
is TDD:_x000D_
decreased.
This
TXs faultgo
that
The signal ispath
an indication
through thatThe
the affected
is unusable. theantenna
system
cells thatclock
line
arearetuning range is unit
disabled._x000D_
using the faulty nearing
might itsnot
limitwork.
after which the system clock frequency can longe
the
As Flexi
asignal Zone
result:_x000D_ Micro BTS must be scheduled for replacement. The amount of time between the reporting of the 1818 fault and
The
cannot be path is unusable.
supported. However,Theif cells
there using
is a the faulty
defect unit might
associated withnot
thework.
system clock, a much shorter period might be available.
- The cell that has lost its only TX or has no Primary TX available is disabled._x000D_
The
- TheBTScellcapacity
that still might
has itsbe decreased.
Primary TX available, but has lost its Secondary TX, is degraded. Such a cell also loses its MIMO/VA
- theBTS
The radio modulemight
capacity becomes degraded_x000D_
be decreased.
_x000D_
The BTS capacity might be decreased.
In case of CPRI/IR radios:_x000D_
The
TXs BTS
that gocapacity
through might be decreased.
the affected antenna line are not disabled._x000D_
As
TheaBTSresult:_x000D_
capacity might be decreased.
- radio
The module
antenna lineautonomously
device does not reduces
work RF power.The
properly. _x000D_
cell operation is degraded.
_x000D_
The device is out of use.
_x000D_
Flexi Zone Micro
The module mightFDD,haveFlexi
beenZone
startedMicrowithTDD:_x000D_
an old SW version and is therefore not compatible with other modules.
The
The cell
BTSiscapacity
disabled._x000D_
is lost.
Downlink signal transmission on the given antenna line is disabled and the corresponding FR transmitter is unusable. Thus, the
Heating from the heating element is not available. The module temperature might not reach the working level or might reach it v
The BTS capacity drops. The cell is not operational.
The MHA's gain might be decreased. The cell performance might be decreased as well. The real level of gain provided by MHA
MHA doesn't provide gain in RX path. The cell performance might be decreased. Within recovery action missing gain is compen
Some antenna line device functions might not work properly.
The BTS functionality is degraded and/or resources are unavailable.
_x000D_
If other references are available, the synchronization reference source changes to another source. Tuning then follows this new
FDD:_x000D_
_x000D_
Calls
If are not possible through thethe affected cell(s).
If other
other references
references are are available,
not available, synchronization
the BTS master clock reference
(OCXO)source changes
tuning to another
is halted and thesource, the tuning follows
BTS synchronization thistonew
drops r
holdo
_x000D_
Calls are not possible through the affected cell(s).
If
Theother
RF references are not available,
Module is configured tuning does
using defaults and the not performance
follow the external
is not asreference any more. Clock tuning is halted and the BTS
expected.
_x000D_
Calls
If the are
FCMnot possible
[FSMr3: through
FCT] the affected
is approaching thecell(s)
end of (7653 CELL but
its lifetime FAULTY)._x000D_
the reference frequency is still correct, the BTS and system p
_x000D_
_x000D_
Calls are not possible through the affected cell(s) (7653 CELL FAULTY)._x000D_
There might be problems in the calls through the affected cell(s) (7654 CELL OPERATION DEGRADED).
TDD:_x000D_
_x000D_
If othermight
There
_x000D_ references are available,
be problems the synchronization
in the calls through the affected reference
cell(s)source
(7654 changes to another DEGRADED)._x000D_
CELL OPERATION source. Tuning then follows this new
There
_x000D_ can be problems in the phone calls through the affected cell(s) or calls can be impossible.
There can be problems in calls through the affected cell(s) (7654 CELL OPERATION DEGRADED)._x000D_
If
No noimpact
Flexi
_x000D_other valid
on
BTS FDD, reference
system (7652
Flexi BTS available,
BASE STATION
TDD:_x000D_ BTS tuning mode moves from normal to holdover. If holdover is not possible because of ins
NOTIFICATION).
_x000D_
Calls
No are
impact not
on possible
system through
(7652 the
BASE affected
STATION cell(s)._x000D_
NOTIFICATION)
There might be problems in the calls through the affected cell(s).
_x000D_
Calls
The BTS
Flexi are not
Zone possible
supports
Micro through
an integrated
FDD, Flexi Zone theGPS affected
Micro cell(s).
receiver. If there is a prolonged loss of the GPS 1PPS clock there is likely a hardware fail
TDD:_x000D_
The Flexi
Calls Zone
are not Micro BTS
possible through RX theis disabled
affectedand the (7653
cell(s) cell is CELL
unusable, the BTS is rebooted (7653 CELL FAULTY)._x000D_
FAULTY)._x000D_
The Flexi
_x000D_ Zone Micro BTS RX is disabled, calls are
The TX/RX paths of the RF module are out of order and phone calls throughpossible using the remaining RX, but cell
the affected capacity
cell(s) are notand performance might d
possible.
The problems might occur in the calls through the affected cell(s) (7654 CELL OPERATION DEGRADED).
The
There TXcan
partbeisproblems
out of power in the and calls
calls are notthe
through possible
affected through
cell(s).the affected cell(s)._x000D_
_x000D_
There mightMicro
Flexi Zone be problems
FDD, Flexi in the
Zone calls through
Micro the affected cell(s).
TDD:_x000D_
Callsfault
This are not possible
should cancel through the affected cell.
itself. _x000D_
Heating of the module is ongoing._x000D_
The RF Module configuration might fail and cause another fault, and there can be problems in the calls through the affected cel
During RF startup affected cell resources are not reported to RROM.
The default configuration is used and the cell TX and/or RX performance is degraded. There can be problems in the calls throu
The cell's TX and/or RX performance might be degraded because of the failure or calls are not possible through the affected ce
The
The TXcommunication
power level is between
decreased the System
and there Module
can beand RF module
problems with might
phonebe corrupted.
calls through Calls are not cell(s).
the affected possible through the affecte
_x000D_
There can be
Flexi Zone problems
Micro FDD, Flexiin callsZonethrough
Microthe affected cell(s).
TDD:_x000D_
The
It communication
is not betweenphone
possible to establish the System Module the
calls through andblocked
RF module might be corrupted. Calls are not possible through the affecte
FR._x000D_
_x000D_
The fault may mean that FAN in radio module is not working. In this case_x000D_
The
radio BTS doesmay not be
send faults that are related to the blocked Flexi Radio module (FR) to the network management system (NM
If the module
fans do not rotate overheated._x000D_
as required, the module's temperature might rise too high.
_x000D_
If
Thethefault
fanscando be
notcanceled
rotate as only required,
for somethe module
types oftemperature
radio modules might
i.e. rise too high.
the_x000D_
radio
If the modules
fans rotate where
fasterfans
than are detected
required, based
they cause on unnecessary
speed response algorithm_x000D_
noise.
(FRM3.x, FRGT from version 102 and FRGS from version X21)_x000D_
The RF module might overheat, but there is no immediate effect on the module's operation.
There might be problems with calls made through the affected cell(s).
Calls and data transmissions are possible with degraded quality and lower bandwidth because of increased bit error rate on opt
Calls and data transmissions are not possible through the affected cell(s).
The cell, using the RF module which notified the fault, is disabled._x000D_
_x000D_
The Flexi BTS unit in question is transmitting or receiving data with degraded performance. The fault does not trigger special ac
Downlink signal transmission on the given antenna line is disabled and the corresponding FR transmitter is unusable. Hence, th
The traffic between the System Module and the connected radio module is interrupted. The cell operation is faulty._x000D_
_x000D_
The traffic between the Baseband Module (for example, FBBC) and the connected radio module is interrupted. The cell operatio
_x000D_
The cell(s) of the RF Module behind the broken connection are not operational and the RF Module cannot be used.
_x000D_
If
Thethecell
_x000D_ fault is reported
operation for primaryThe
is degraded. optical interface,
optical connection
interface to radio modulesif further
loses its synchronization in theofchain
the amount is exceeds
errors affected the
by what is indicat
defined limit.
If
RP3thetraffic
fault istoreported for primary
the connected optical is
RF Module interface, connection
malfunctioning. Thetorelated
radio modules
cell(s) arefurther in the chain is affected by what is indicat
not operational.
Baseband bus RP3 traffic to the RF Module is not working. Cell operation is degraded._x000D_
There is possibly no immediate effect on the BTS operation, but it might cause an optical interface alarm.
The traffic between the System Module and RF Module is unreliable. Some calls or other connections might be lost.
The connection to the associated link is lost. The data is partially or completely lost. The worst-case fault effect can expand furt
_x000D_
Data traffic to the connected RF Module is malfunctioning. BTS operation is faulty._x000D_
This fault can prevent the BTS operation when the RF Module is needed for the required cell configuration._x000D_
RP3 traffic from the baseband is malfunctioning. The System Module or FBBx Module operation is degraded.
_x000D_
fault is visible
The System Moduleonly for the
is out first radio
of order in the
and the BTSchain.
is outFault 10 sends for the other FRs when pooling breaks because of the lost
of order._x000D_
The System Module is out of order and the BTS is out of order._x000D_
Baseband bus RP3/RP3-01 traffic might work incorrectly. The cell operation is degraded.
An SW update is needed.
The BTS operation is degraded because some of the BTS resources are not available.
The BTS operation is degraded because some of the BTS resources are not_x000D_
available.
Depending on the reported alarms, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED) or the
Depending on the reported severity, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED), or th
Depending on the reported alarms, the BTS capacity might have decreased (CELL OPERATION DEGRADED or CELL FAULTY
If the fans are not rotating as expected, there is a risk that the module_x000D_
temperature
Depending on orthe
acoustic
reported noise levelsthe
alarms, risefault
toosituation
high. Formight
example,
haveano Temperature_x000D_
impact on the operation (BASE STATION NOTIFICATION),
fault
(BASE might be
STATION generated
FAULTY). from the alarming module.
_x000D_
FDD:_x000D_
The BTS capacity or might have
The
1. newreported
If the installed alarm failed HWdecreased._x000D_
is 7652 resources
BASE STATION are notNOTIFICATION,
available beforethe theBTSBTSishasusingbeen
thereset.
lower priority synchronization source as a
_x000D_
2.
Any If the reported
attempt by thealarm is
operator 7651to BASE
configure
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ STATION
modes OPERATION
other than DEGRADED,
single TX mode the
for BTS
the has
cell willno
bevalid synchronization sources as a
unsuccessful.
fault situation
Configured lasts
LNCELs
The cells remain down. for a long
greater time,
than the
the accuracy
maximum starts
allowed to drift
are slowly.
ignored. However,
Configured it might
Cells take
that several
exceed weeks
the beforeallowed
maximum the BTS/RAN
numb
_x000D_
The fault has no direct impact on the operation (BASE STATION NOTIFICATION).
TDD:_x000D_
1.
The If the
BTSreported
does notalarmfunctionis 7652 BASESome
correctly. STATION NOTIFICATION,
BB processing resourcesthe BTS
in theisBTS
usingaretheoutlower priority synchronization source as a
of use.
depends on the quality of the used lower
The BTS resources have decreased or the BTS is faulty. level source._x000D_
_x000D_
Flexi
The BTSreported
2. If the
Depending operation
on thealarm is degraded
reported is 7651
alarm, (FSP
BASEthe is faulty,
STATION
fault alarm 7651),not
OPERATION
situation might orDEGRADED,
a cellan
have of impact
the BTStheonis outhas
BTS
the of order (FSP
no valid
operation is faulty, alarm
synchronization
(BASE STATION 7653),
orsources or
asthe
CELL NOTI a
_x000D_
fault
FAULTY).situation lasts for a long time, the accuracy starts to drift slowly. However, it might take several weeks before the BTS/RAN
The
Flexi BTS
ZoneisMicro
not commissioned.
FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
The
Flexi
_x000D_BTS
BTSoperation
FDD, Flexi is BTS
degraded (FSP) or the BTS is not operational (FCM/all FSPs).
TDD:_x000D_
BTS
This startup
If thefault canisprevent
reported interrupted
alarm isthe
7650 andBASE
BTS the
fromBTS is out of
STATION
functioning order._x000D_
FAULTY,
when theradio
the BTS unit
has isbeen in holdover mode and holdover time is run out. BTS is
needed_x000D_
_x000D_
_x000D_
for the required cell configuration.
The
Flexi BTS isMicro
not operational or is degraded.
Flexi Zone
Zone Micro FDD, FDD, Flexi
Flexi Zone
Zone MicroMicro TDD:_x000D_
TDD:_x000D_
The
None BTS
signalcapacity
path is might
unusable. decrease
The or there
cells usingmight be interference
the faulty in calls
unit might not work.(commissioning data)._x000D_
BTS startup is interrupted and the BTS is out of order (RNW data).
This cell-specific fault does not prevent cell configuration. It is for informative purposes only.
The antenna line is not operating correctly. The cell is disabled. _x000D_
The antenna line is not operating correctly. The cell capacity decreases.
The RS485 interface is not operating correctly. Communication with TILT devices is not possible.
BB resources are shut down, the BTS operation will be faulty. _x000D_
FCM
Cells and FTM
are not are kept Itpowered.
activated. relates to cells that were going to use the radio unit connected to the system module via the faulty fibe
Fan control is not optimized. _x000D_
The
The effect
Radio to noise/temperature
Module connected tolevel is marginal.
this OptIF is not started.
The FSP resource is shut down and the BTS operation is degraded or faulty._x000D_
The
If theFCTfansand possibly
do not rotateother FSPs thatthe
as requested, aremodule
not alarming are kept
temperature powered.
might rise too high.
If the fan(s) do not rotate as requested, the module temperature might rise too high.
If the fans rotate faster than requested, unnecessary noise is emitted.
The source unit has an inconsistent SW version.
The
The module cannot:_x000D_
cell is disabled (the downlink carrier that transmits PSS/SSS signals has failed)._x000D_
1.
The savecell to
is file the cause
degraded ofdownlink
(thewill the SW carrier
fallbackthat
on transmits
request_x000D_PSS/SSS signals is working)._x000D_
The ongoing BTS reset
or_x000D_ last longer.
2.
The mount
cell orthe BTS passive
is notfile system and
operational or isthus read the cause of the SW fallback on request from the file._x000D_
degraded.
_x000D_
1.Other than sync hub configuration: the master system module works properly._x000D_
Flexi
2.In Zonehub
sync Micro FDD, Flexi the
configuration: Zone Microradio
shared TDD:_x000D_
module
The
The system module
BTS cannot:_x000D_ is out of order and the BTS is outmight
of order.be lost and the cell that is supported by the radio module might be d
1.
The savefaulttohasfile no
thedirect
causeimpact
of the onSWthe fallback on request_x000D_
operation (BASE STATION NOTIFICATION).
or_x000D_
2. mount the passive file system and thus read the cause of the SW fallback on request from the file.
DC voltage is disabled on reporting Antenna Line.
The HDLC link will be disabled on the reporting Antenna Line or IUANT port.
In case of problem detection in SW activation, the SW activation and consequent reset are aborted._x000D_
In
Whencasethe of eNB
problem detection
is sync in start-up,
hub slave the BTS
and rfsharing is remains
enabled,out of order.
start-up RollbackOtherwise,
is stopped. to the previous SWisand
start-up anotherwithout
continued SW download
the refe
The radio unit that is connected to port 3 or 4 of FBBC card cannot provide services to cell/cells and the cell/cells are degraded
The BTS is operational.
When the fault is detected during startup, the BTS is not operational. When the fault is detected during runtime, the requested n
If
Theanother
PHICH synchronization
transmission power sourceis isnot
available,
boostedthe BTS or
enough starts
at alltocompared
use that for tothe
theBTS reference.
operator's Then there are no effects to the
setting.
_x000D_
Cell operation
If there are no is downgraded.
other synchronization sources available, the external GPS/GNSS receiver module continues providing the refere
of
Forthe S1:phase
The eNB drifting,
lost the
the phase deviation
connection is considered
to S-GW. to reach
All calls using thethe threshold
failed GTP-Uvalue and then
data path the features
are released, andrequiring phase
new GTP-U sync
data tun
still within the required limits,
The S1 interface is unavailable. _x000D_ typically over several months._x000D_
_x000D_
_x000D_
The X2 interface is unavailable. Handover of calls to or from cells of the associated adjacent BTS is not possible. Base station (
_x000D_
If no other S1 interface is available for use, BTS operation is considered faulty and no calls can be set up. _x000D_
Flexi
One
_x000D_ BTS
of theTDD:_x000D_
transport paths(SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is supporte
If another
If there
BTS synchronization
is atconfigured
is not othersource
least one according toisradio
available,
S1 interface BTS
available
network starts
for
plan file.toBTS
use, useisthat for the
operation is BTS reference.
considered
waiting_x000D_ Then there
degraded areBTS
and the no effects to the BT
can continue op
_x000D_
for the correct radio network configuration file.
The
If therecellareis disabled.
no other synchronization sources available, the external GPS/GNSS receiver module continues providing the refere
because
The cell isofdisabled.
the phase drifting, the phase deviation is considered to reach the threshold value and then the air interface (cells) a
In the case of subscriber trace activation, if the failed trace connection was used for sending the trace reports, the BTS conside
_x000D_
BTS startup is interrupted and the BTS is not operational.
In the case of cell trace and interface trace, if the failed trace connection was used for sending the trace reports, the BTS does
Trace session (for subscriber/cell/interface) cannot be activated/deactivated.
The BTS cannot accept new UEs attempting registration in any of the reported misconfigured PLMNs. Such an attempt by new
_x000D_
The fault has no effect on the base station operation but the LNADJ and/or LNADJL object was not stored in the eNB.
The UEs that might have already registered in misconfigured PLMN(s) remain unimpacted.
The fault has no effect on the base station operation but LNADJW object with newly learnt WCDMA neighbor cell configuration
The fault has no effect on the base station operation but LNRELW object with newly-learnt WCDMA neighbor relation configura
The fault has no effect on the base station operation. The WCDMA neighbor relation, which is reported by a UE because of acti
1)
Nohas not been
handover canstored because to
be performed the actual
cells withnumber of LNRELW
the affected PCI andper cell (LNCEL) per UTRAN carrier (in ANRPRW profile) is equ
frequency.
2) has been stored but at least one of LNRELW's mobility paremeters (psHoAllowed, srvccAllowed) has been set to 'forbidden'
The cell that cannot be recovered remains unavailable.
If an X2 link is available, no type of handover to the neighbor cell is possible at all._x000D_
If
Thethehandover
UE-basedfailure
ANR rate
is activated, there will
for the affected bemight
cell continuous retries to resolve the ECGI.
be increased.
All eICIC partnerships are terminated.
Handovers from or to cells of the related adjacent BTS are not possible.
Handovers to cells of the related adjacent BTS are not possible.
The S1 interface is not available for call setup and existing calls are released.
The S1 interface is unavailable and the BTS is not available for call setup.
The cell is deactivated (switched off) until S1 availability is regained.
If the update of the TAC or PLMN identities was not successful, the eNB performs S1 setup which means service loss for affect
System Information for the related GERAN neighbor cells is not reliable and will not be provided to UEs, which are released wit
Some of the UEs with a complete set of system information of the cell stored that has left the cell and has come back within thre
This fault has no effect on BTS operation.
There is high memory usage, which might result in memory outage.
Critical
The BTS impact on FSP
capacity operation._x000D_
decreases or the BTS is not operational. The Digital Signal_x000D_
_x000D_
Processing (DSP) does not work correctly.
The
FlexiBTS Zonecapacity
Micro FDD, decreases
Flexi Zone or the BTS TDD:_x000D_
Micro is not operational. The Digital Signal_x000D_
Processing
Critical
The BTS impact (DSP)
on the
capacity does not
operation.
decreases work correctly.
or the BTS is not operational. The Digital Signal_x000D_
Processing (DSP)
The fault has no further consequences. does not work correctly.
The BTS does not take the new settings into use before a reset.
The communication link between the BTS and the BFD peer is defective. No communication is possible.
Possible impact on the connections over this interface:
-Possible no calls impact
are possible
on the connections over this interface:
-- loss no of remote
calls management
are possible anymore access to other network elements in the RAN
Possible
-- loss of effects:_x000D_
synchronization if the interface
-Flexi loss of remote
no calls are management access
possible._x000D_ to isother
usednetwork
as synchronization source.
elements in the RAN
-- loss BTS
of FDD, Flexi
synchronization BTS if TDD:
the interface is used as a synchronization source
The lossinterface
of remote management
cannot access to other network elements in the RAN_x000D_
Possible impact:
- loss of synchronization The be BTS used
if is
for
thenot
transmission.
synchronized
interface is usedtoasthe network anymore.
a synchronization source._x000D_
-Flexi
The BTS IKE SAs
Zonemay and
MicroIPSec
haveFDD, SAs
to use
Flexi cannot
a Zone be established
synchronization or re-keyed
Micro TDD:interface that has a lower clock
quality:
The Certificate if the primary
interface cannot
Revocationclock
be used source
Listfor hasnotbeen
transmission.
could lost, the BTSNewswitches
Conditionally,
be updated. Bluetooth
revoked is enabled when the backhaul goes down.
certificates_x000D_
automatically
The
remain SFP unknown to
module's the
to secondary
laser
the is
BTS. not clock
switchedsource.
on orIf
noboth
SFP the primary
module anddetected
was the at all.
Normal
secondary traffic is interrupted.
clock areOnlylost, loopback OAM frames are transmitted
clock.and received over the interface. If the test frame gener
The Ethernet Linksources
is down. the BTS switches to the internal
The
An Ethernet EthernetLink interface
cannot might be out of order
be successfully or the remote peer might be out of order. Traffic might get lost.
established.
No Ethernet data or clock information
The Ethernet interface is defected or the remote peer is exchanged viaisthis interface.
defective. Traffic might get lost.
The SFP is not operational.
Possible
- voice calls impact:
or data connections cannot be established.
--Possibleslow management
impact: the access
remote management to the management
connectivity
performance WBTS
cannotand be other
datanetwork
established.
collected elements in the RAN
on this interface becomes invalid.
-- poor loss voice
of quality and data
synchronization if theperformance
interface is used as a synchronization source
Possible
-- ifDepending impact
this interface on the
is part connections
of an IMA group, over the interface
this IMA in question:
-Possible areon
no calls impact use
possible of the Ethernet interface, the link
aboveis todescribed
be temporarily
impactsuspended from
can occur for operation
the local BTS and/or other BTS elemen
-- loss of remote
no calls management access to other network elements in the RAN
are possible
Possible impact:_x000D_
-_x000D_
loss of remote management access to other network elements in the RAN
The
-- losstransport connection towards
of synchronization the remote peer
as amay be defective. source
Traffic may get lost.
no calls are possible forifthe theconnections
interface is used
over this synchronization
unit_x000D_
The transport
_x000D_ connection towards the remote peer may be defective. Traffic may get lost.
-None
The requested service is not available.
The communication link between the BTS and the BTS peer is defective. Or the peer is defective. No communication is possibl
If the alarm is active, then potentially there is a synchronization loop
None
None
BTS will not have time synchronisation.
Flexi Zone Micro FDD, Flexi Zone Micro TDD:
SyncE is no longer
There might a working
be available synchronization
another synchronizationsource.
source at eNB; in that case the BTS switches automatically to the other clock
_x000D_
If no other synchronization source is available at eNB, it runs in hold-over mode; _x000D_
Possible
_x000D_ impact:_x000D_
_x000D_
Please
Configured referIPsec
to status of 3080:
policies EFaultId_BtsReferenceClockMissing
are ignored and all traffic is sent unprotected.
- No calls are possible for the connections over this unit
None
BTS traffic has switched over from the primary IPsec tunnel to secondary (backup) IPsec tunnel terminating on secondary secu
The capacity drops. Cell(s) might remain down.
BTS baseband processing power is decreased. If all FSPs are faulty, the BTS is not operational.
The
If theaffected
redundant cellfans
might not becool
cannot fullythe
operational._x000D_
module sufficiently, the unit might overheat. For example, a temperature fault from the FC
_x000D_
If the Zone
Flexi fans are
Micro notFDD,
rotating
FlexiasZone
requested, the module temperature might rise too high.
Micro TDD:_x000D_
The
If thecell
SWisdownload
not operationalto anyand
HWtherefore, the BTS
unit has failed, the is not continues
eNB operational.operating with the currently running SW version._x000D_
_x000D_
The cell or BTS is not operational or is degraded.
The BTS continues to operate with the remaining cells on air or goes to IntegratedToRAN state if there are no more "enabled" c
_x000D_
If the
The BTS SW is activation has failed on another HW unit (for example, RF unit), then:_x000D_
not operational.
1. The eNB restarts
The BTS is not operational and operates
if no any with the new within
regulation SW version installed._x000D_
a days._x000D_
2.
The Eventually,
time if the
(days/weeks) eNB is integrated
howmight
long last to the NetAct,
untildown. after the
not meet the +/- 50ppbautomatic recovery
frequency SW update,
accuracy the eNB
requirement restartson
is depend and
theoperates wit
conditions
The capacity
_x000D_ drops. Cell(s) remain
Flexi
The BTSZonedoesMicro notFDD, Flexi Zone Micro TDD:_x000D_
operate.
The
The BTS does not operate. might not be possible without special actions. The BTS continues its operation with the old software
SW update to this BTS
The BTS resumes the startup but the cells assigned to non-existing LCR IDs are discarded.
Calls through the affected cell(s) are not possible
Baseband bus RP3 traffic to the RF Module is not working. Cell operation is degraded.
Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFIC
FAULTY).
Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTIFICATION)
(BASE STATION
Depending on theFAULTY).
reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTIFICATION),
Depending on the reported alarms,the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFIC
Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTIFICATION),
The related cell remains down.
The BTS is not operational or the capacity is degraded.
The module might have been started with an old SW version and is, therefore, not compatible with other modules.
This fault can prevent BTS from functioning when the RF Module is needed for the required cell configuration.
The affected cells are disabled.
Not enough RP3-01 capacity for commissioned cells. Commissioned cells using the missing RP3-01 link are not activated.
Newly downloaded SW will overwrite active SW. Therefore, SW download and activation are not allowed. Currently active SW i
Radio module is powered off, therefore calls/data transfers cannot be served by that module.
IP address conflict has been reported between RP3-01 nodes.
When
All cellsthere is the
using the same
IP address
radio conflict,
module arethe conflicting
down. (later identified) RP3-01 node is not detected and thus it is not seen on the
This fault prevents the impacted RF unit from working.
Effect in issue 01
If thefault
This FSPdoesupdate notfails, the BTS affect
immediately capacitythe drops.
operationsIf theofoptical
the BTS, interface
but it FPGA SW update
is a notification thatfails,
the communication
BTS master clock to radio modules
frequency dev
_x000D_
The BTS master clock tuning continues regardless of the alarm, but because the BTS master clock adjustment is quite slow to
The module
Flexi Zone Micro in question is outZone
FDD, Flexi of use. This
Micro fault cancels all the active faults for the same module.
TDD:_x000D_
The BTScell orisall
notcellsoperational._x000D_
are not operational.
The BTS is provided
Resources out of order. by the module cannot be used, which means that some features might not work._x000D_
_x000D_
Resources provided by the module cannot be used, which means that some features might not work._x000D_
_x000D_
Real time isthe
Therefore, notRF available.
LEDforand Alarms,SM logs, and all reports have incorrect time.
If the fault is reported FRBTSmodule, LED display
the BTSOM status
does not cannot
knowbe aligned.
the FR module's real state, and thus the BTS SM keeps the F
The BTS continues
situation. Therefore,its operation
there with the old
is no possibility file. the RF LED and BTS SM LED display status.
to align
The BTS continues its operation with the old software.
If the SW download to any HW unit has failed, the eNB continues operating with the currently running SW version._x000D_
_x000D_
_x000D_
The
_x000D_BTS does not send any faults related to the blocked cell or the modules commissioned to the blocked cell to the network m
It is not possible to establish phone calls through the blocked module.
_x000D_
If theBTS
The SW does
activation has failed
not send on another
any other HW unit
faults other than(for example,
transport RFtounit),
faults then:_x000D_
the network management system (NMS) when the BTS is
Calls
1. The
_x000D_ through
eNB the blocked
restarts and cell are with
operates transferred
the new toSWanother
versioncell.installed._x000D_
It is not possible to establish new calls through the blocked cell.
2.
All
The Eventually,
cells if the SM
are disabled.
operator (BTS eNBandis integrated
OMS/NetAct) to theis NetAct,
informedafter aboutthetheautomatic recovery SW update,
autonomously-triggered the eNB
recovery restarts and operates wit
reset._x000D_
Flexi
_x000D_
FCM/FCT or FTM is fault source: BTS startup is terminated._x000D_
Flexi
Flexi Zone
BTS
Zone Micro
FDD,
Micro FDD,
Flexi
FDD, Flexi
BTS
Flexi Zone
ZoneisMicro
TDD:_x000D_
Micro TDD:_x000D_
TDD:_x000D_
FSP
The or
SW DSP is fault source: FSP not taken into use._x000D_
The BTSupdate
Depending
Depending
_x000D_ is on theto reported
operational.
on the this BTS severity,
reported might notthe
severity, beBTS
the possible
BTS capacity
capacitywithout
might
mightspecial
have actions.
have decreased
decreased The(BASE
BTS continues
(BASE STATIONits
STATION operation with
OPERATION
OPERATION the old software
DEGRADED,
DEGRADED, CEL
CEL
_x000D_
For resources that are not in use (not commissioned) lack of support_x000D_
Flexi
The BTS
Flexi Zone Micro
Zonememory
Micro FDD, Flexi
operations,
FDD, Zone Micro
for example
TDD:_x000D_
is
BTS reported
service byisminor
degradedseverity alarm
or out (BASE STATION NOTIFICATION).
_x000D_
BTS BTS
The is notmemory
operational.operations, forofexample
service._x000D_
_x000D_
The
The
Flexi BTS memory operations, for example the software download and parameter updates, are not stable._x000D_
Zone:_x000D_
The
FlexiBTS
The Zonememory
Accessoperations,
Point service forisexample
degraded theorsoftware
out of service.
download and parameter updates, are not stable._x000D_
The
The
The BTS capacity decreases. The digital signal processing (DSP) does not work correctly.
The ISTI (In Service Time Indicator) value for HW Repair Center might not be correct or readable.
Flexi BTS FDD, Flexi BTS TDD, Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
The
FlexiBTS BTScapacity
FDD, Flexi decreases or BTS is not operational. The Digital Signal Processing (DSP) does not work correctly._x000D_
BTS TDD:_x000D_
_x000D_
The BTS is not operational or thefunctionality.
capacity is degraded._x000D_
There
Flexi is no actual
Zone:_x000D_ effect to BTS This is user-specific.
_x000D_
The
There overall
is no Flexi
actual Zone Controller
effect to BTS capacity
functionality.
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ has decreased
This since the Flexi Zone Access Point is not operational.
is user-specific.
The BTS
There is not
is no actual operational.
effect to BTS functionality. This is user-specific.
Some action inside the BTS is interrupted. The BTS does not operate normally. The fault is in the unit reported in the fault sourc
The
This BTSfault capacity
preventspossibly
the BTSdecreases.
from functioning. The cell with incorrect
Depending configuration
on <x>, some processing is not working._x000D_
resources, some cells, or the whole BTS are
_x000D_
This fault can prevent the BTS from functioning
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone: _x000D_ when the RF Module is needed for the required cell configuration.
The BTS
Flexi BTScapacity
FDD, Flexi possibly decreases.
BTS TDD:_x000D_
_x000D_
FDD:_x000D_
Flexi
If other BTS FDD, Flexi
references areBTS TDD:_x000D_
available, the synchronization reference source changes to another source. Tuning then follows this new
The
If
The BTS
other
BTS can
is notoperate
references areproperly for months
not available,
operational. the BTS or even
master a year
clockwhen being
(OCXO) in theis5%
tuning margin
halted andarea, but eventually
the BTS the DAC
synchronization drops value reac
to holdo
synchronization
_x000D_ setting defined in the BTS commissioning._x000D_
The
_x000D_ BTS is not commissioned or integrated to the network. The BTS cannot be accessed or configured remotely._x000D_
TDD:_x000D_
_x000D_
Effects
The
If otherBTS in FDD Frequency
cannot
references goare
to the Synchronization
operational
available, state.mode:_x000D_
the synchronization reference source changes to another source. Tuning then follows this new
Assuming
The MHA is degraded and the RX signal has
If no other that
validthe BTS
reference reference
available, signal
BTS correct
tuning
level mode
might accuracy
bemoves whennormal
from
decreased. the DAC
The size value
to of
holdover.reaches
the cell the
be adjustment
If holdover
might limit 0because
is not possible
reduced. or 4095 (mea
of ins
not
_x000D_met any more. Even in that stage the BTS might still be operational but the system performance might drop, affecting, for ex
The
_x000D_ MHA is faulty and the RX performance might be degraded. The size of the cell might be reduced.
Flexi Zone Micro FDD, Flexi Zone Micro TDD, Flexi Zone:_x000D_
Effects
The
Tuning in FDD
antenna
does not Phase
line is notSynchronization
follow operating
the external mode:_x000D_
correctly. The cell capacity might be decreased.
reference._x000D_
When
ClockBTS
Flexi the
tuningDAC value
is halted
FDD, reaches
and the
Flexi BTS the adjustment
BTS continues its
TDD:_x000D_ limit 0 or 4095,
operation the basic
based on theLTE system
internal ovenoperation effects are the same as in Freque
oscillator._x000D_
more._x000D_
The air interface accuracy of 0.05 ppm is kept for at least 24 hours. Within that time, the BTS can work properly but
In
The VSWR
_x000D_ outputThreshold
power at Tuning modeis- no
the antenna impact tobecause
decreased the state ofof the
the cell/Radio
reflection Module._x000D_
of the signal in the TX path. The antenna is the
not network
working
Otherwise TXes that go through the affected Antenna Line are disabled._x000D_
Flexi
The Zone
RX path
In result:_x000D_ Micro FDD,
operating Flexi Zone
performance Micro
is TDD:_x000D_
decreased.
This
-The fault
thesignal ispath
cell thatanhasindication
is lost thatThe
its only
unusable. the or
TX system
hasusing
cells noclock
thetuning
faulty range
PrimaryTx is nearing
available
unit might isnot its limit after which the system clock frequency can longe
disabled_x000D_
work.
the
-The Flexi
thesignal Zone
cell that Micro
stillishas BTS must
PrimaryThe be
TX cells scheduled
available, butfor replacement. The amount
TX isof time betweenSuchthe reporting of the
its 1818 fault and
cannot be path
supported. unusable.
However, if there using
is a thehas
defectfaultylostunit
its might
associated
Secondary
withnot
thework.
system
degraded.
clock, a much
a cell
shorter
also loses
period might
MIMO/VAM
be available.
ca
- the Radio Module becomes degraded_x000D_
_x000D_
Flexi
The BTSZonecapacity
Micro FDD,mightFlexi Zone Micro TDD:_x000D_
be decreased.
The cell is disabled._x000D_
Downlink signal transmission on the given antenna line is disabled and the corresponding FR transmitter is unusable. Thus, the
The antenna line device does not work properly. The cell operation is degraded.
The device is out of use.
The module might have been started with an old SW version and is therefore not compatible with other modules.
The BTS capacity is lost.
The BTS capacity drops. The cell is not operational.
The MHA's gain might be decreased. The cell performance might be decreased as well. The real level of gain provided by MHA
MHA doesn't provide gain in RX path. The cell performance might be decreased. Within recovery action missing gain is compen
_x000D_
FDD:_x000D_
_x000D_
Calls
If are not possible through thethe affected cell(s).
If other
other references
references are are available,
not available, synchronization
the BTS master clock reference source
(OCXO) changes
tuning to another
is halted and thesource, the tuning follows
BTS synchronization thistonew
drops holdor
_x000D_
If
Theother
RF references are not available,
Module is configured tuning does
using defaults and thenot performance
follow the external reference
is not as any more. Clock tuning is halted and the BTS
expected.
_x000D_
Calls
If the are
FCMnot possible
[FSMr3: through
FCT] the affected
is approaching thecell(s)
end of (7653 CELL but
its lifetime FAULTY)._x000D_
the reference frequency is still correct, the BTS and system p
_x000D_
_x000D_
TDD:_x000D_
_x000D_
If othermight
There
_x000D_ references are available,
be problems the synchronization
in the calls through the affected reference
cell(s)source
(7654 changes to another DEGRADED)._x000D_
CELL OPERATION source. Tuning then follows this new
There
_x000D_ can be problems in the phone calls through the affected cell(s) or calls can be impossible.
There can be problems in calls through the affected cell(s) (7654 CELL OPERATION DEGRADED)._x000D_
If
No noimpact
Flexi
_x000D_other valid
on
BTS FDD, reference
system (7652
Flexi BTS available,
BASE STATION
TDD:_x000D_ BTS tuning mode moves from normal to holdover. If holdover is not possible because of ins
NOTIFICATION).
_x000D_
Calls
No are
impact not
on possible
system through
(7652 the
BASE affected
STATION cell(s)._x000D_
NOTIFICATION)
There might be problems in the calls through the affected cell(s).
_x000D_
Calls
The BTS
Flexi are not
Zone possible
supports
Micro through
an integrated
FDD, Flexi Zone theGPS affected
Micro cell(s).
receiver. If there is a prolonged loss of the GPS 1PPS clock there is likely a hardware fail
TDD:_x000D_
The Flexi
Calls Zone
are not Micro BTS
possible through RX theis disabled
affectedand the (7653
cell(s) cell is CELL
unusable, the BTS is rebooted (7653 CELL FAULTY)._x000D_
FAULTY)._x000D_
The Flexi
_x000D_ Zone Micro BTS RX is disabled, calls are possible
The TX/RX paths of the RF module are out of order and phone calls through using the remaining RX, but cell
the affected capacity
cell(s) are notand performance might d
possible.
The
There TXcanpartbeisproblems
out of powerin the and calls
calls are notthe
through possible
affected through
cell(s).the affected cell(s)._x000D_
_x000D_
There can be
Flexi Zone problems
Micro FDD, Flexiin theZonecallsMicro
through the affected cell(s).
TDD:_x000D_
Callsfault
This are not
shouldpossible
cancel through the affected cell.
itself. _x000D_
Heating of the module is ongoing._x000D_
The RF Module configuration might fail and cause another fault, and there can be problems in the calls through the affected cel
The cell's TX and/or RX performance might be degraded because of the failure or calls are not possible through the affected ce
The
The TXcommunication
power level is between
decreased the System
and there Module
can beand RF module
problems with might
phonebe corrupted.
calls through Calls are not cell(s).
the affected possible through the affecte
_x000D_
There can be
Flexi Zone problems
Micro FDD, Flexiin callsZonethrough
Microthe affected cell(s).
TDD:_x000D_
The
It communication
is not betweenphone
possible to establish the System Module the
calls through andblocked
RF module might be corrupted. Calls are not possible through the affecte
FR._x000D_
_x000D_
Default values for fan parameters are to be used.
The BTS does not send faults related to the blocked Flexi Radio module (FR) to the network management system (NMS). Fault
If the fans do not rotate as required, the module's temperature might rise too high.
If the fans do not rotate as required, the module temperature might rise too high.
If the fans rotate faster than required, they cause unnecessary noise.
The RF module might overheat, but there is no immediate effect on the module's operation.
There might be problems with calls made through the affected cell(s).
The cell, using the RF module which notified the fault, is disabled._x000D_
_x000D_
The Flexi BTS unit in question is transmitting or receiving data with degraded performance. The fault does not trigger special ac
Downlink signal transmission on the given antenna line is disabled and the corresponding FR transmitter is unusable. Hence, th
_x000D_
_x000D_
_x000D_
If
Thethecell
_x000D_ fault is reported
operation for primaryThe
is degraded. optical interface,
optical interface connection to radio modulesif further
loses its synchronization in theofchain
the amount is exceeds
errors affected the
by what is indicat
defined limit.
If
RP3thetraffic
fault istoreported for primary
the connected optical is
RF Module interface, connection
malfunctioning. Thetorelated
radio modules
cell(s) arefurther in the chain is affected by what is indicat
not operational.
The connection to the associated link is lost. The data is partially or completely lost. The worst-case fault effect can expand furt
_x000D_
RP3 traffic from the baseband is malfunctioning. The System Module or FBBx Module operation is degraded.
_x000D_
fault is visible
The System Moduleonly for the
is out first radio
of order in the
and the BTSchain.
is outFault 10 sends for the other FRs when pooling breaks because of the lost
of order._x000D_
The System Module is out of order and the BTS is out of order._x000D_
An SW update is needed.
available.
Depending on the reported alarms, the BTS capacity might have decreased (CELL OPERATION DEGRADED or CELL FAULTY
If the fans are not rotating as expected, there is a risk that the module temperature rises too high. For example, a Temperature
Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTIFICATION),
(BASE
Flexi BTS STATION FAULTY).
_x000D_
FDD:_x000D_
The BTS capacity or might have
The
1. newreported
If the installed alarm failed HWdecreased._x000D_
is 7652 resources
BASE STATION are notNOTIFICATION,
available beforethe theBTS
BTSishasusingbeen
thereset.
lower priority synchronization source as a
_x000D_
2.
Any If the reported
attempt by thealarm is
operator 7651to BASE
configure
Flexi Zone Micro FDD, Flexi Zone Micro TDD:_x000D_ STATION
modes OPERATION
other than DEGRADED,
single TX mode the
for BTS
the has
cell willno
bevalid synchronization sources as a
unsuccessful.
fault situation
Configured lasts
LNCELs
The cells remain down. for a long
greater time,
than the
the accuracy
maximum starts
allowed to drift
are slowly.
ignored. However,
Configured it might
Cells take
that several
exceed weeks
the beforeallowed
maximum the BTS/RAN
numb
_x000D_
TDD:_x000D_
1.
The If the
BTSreported
does notalarmfunctionis 7652 BASESome
correctly. STATION NOTIFICATION,
BB processing resourcesthe BTS
in theisBTS
usingaretheoutlower priority synchronization source as a
of use.
depends on the quality of the used lower
The BTS resources have decreased or the BTS is faulty. level source._x000D_
_x000D_
Flexi
The BTSreported
2. If the
Depending operation
on thealarm is degraded
reported is 7651
alarm, (FSP
BASEthe is faulty,
STATION
fault alarm 7651)have
OPERATION
situation might or a cell of the BTS
DEGRADED,
no impact onthe isBTS
the out has
of order
operation (FSP
no(BASE
valid is faulty, alarm
synchronization
STATION 7653) oras
sources
or CELL thea
NOTIFIC
_x000D_
fault situation
FAULTY).
The
Flexi BTS notlasts
ZoneisMicro
for a long time, the accuracy starts to drift slowly. However, it might take several weeks before the BTS/RAN
commissioned.
FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
The
Flexi
_x000D_BTS
BTSoperation
FDD, Flexi is BTS
degraded (FSP) or the BTS is not operational (FCM/all FSPs).
TDD:_x000D_
BTS
This startup
If thefault canisprevent
reported interrupted
alarm isthe
7650 andBASE
BTS the
fromBTS is out of
STATION
functioning order._x000D_
FAULTY,
when theradio
the BTS unit
has isbeen in holdover mode and holdover time is run out. BTS is
needed_x000D_
_x000D_
_x000D_
The
Flexi BTS isMicro
not operational or is degraded.
Flexi Zone
Zone Micro FDD, FDD, Flexi
Flexi Zone
Zone Micro
Micro TDD:_x000D_
TDD:_x000D_
The
None BTS
signalcapacity
path is might
unusable. decrease
The or there
cells usingmight be interference
the faulty in calls
unit might not work.(commissioning data)._x000D_
BTS startup is interrupted and the BTS is out of order (RNW data).
This cell-specific fault does not prevent cell configuration. It is for informative purposes only.
The antenna line is not operating correctly. The cell is disabled. _x000D_
The RS485 interface is not operating correctly. Communication with TILT devices is not possible.
BB resources are shut down, the BTS operation will be faulty. _x000D_
FCM
Cells and FTM
are not are kept Itpowered.
activated. relates to cells that were going to use the radio unit connected to the system module via the faulty fibe
Fan control is not optimized. _x000D_
The
The effect
Radio to noise/temperature
Module connected tolevel is marginal.
this OptIF is not started.
The FSP resource is shut down and the BTS operation will be degraded or faulty._x000D_
The
If theFCTfansand possibly
do not rotateother FSPs thatthe
as requested, aremodule
not alarming are kept
temperature powered.
might rise too high.
If the fan(s) do not rotate as requested, the module temperature might rise too high.
If the fans rotate faster than requested, unnecessary noise is emitted.
Module
The cell cannot:_x000D_
is disabled (the downlink carrier that transmits PSS/SSS signals has failed)._x000D_
1.
The savecell in
is file a cause(the
degraded of the SW fallback
downlink carrieron thatrequest_x000D_
transmits PSS/SSS signals is working)._x000D_
The ongoing
or_x000D_ BTS reset will last longer.
2.
The mount
cell orpassive
BTS isfile notsystem thus read
operational the cause of SW fallback on request from the file._x000D_
or is degraded.
_x000D_
None
The system
BTS/Flexi Zonemodule is out
Access of order
Point and the BTS is out of order.
cannot:_x000D_
1.
The savefaultinhasfile no
a cause
directof the SW
impact on fallback on request_x000D_
the operation (BASE STATION NOTIFICATION).
or_x000D_
2. mount passive File System thus read the cause of SW fallback on request from the file.
The HDLC link will be disabled on the reporting Antenna Line or IUANT port.
In case of problem detection in SW activation, the SW activation and consequent reset are aborted._x000D_
In case is
Startup of continued
problem detection in start-up,clock
without reference the BTSbut BTSremains
is notout of order.
directed Rollback to the previous SW and another SW download
to OnAir.
Radio unit connected to port 3 or 4 of FBBC card cannot provide services to cell/cells and the cell/cells are degraded or not ope
When the fault is detected during startup, the BTS is not operational. When the fault is detected during runtime, the requested n
If
Theanother
PHICH synchronization
transmission power sourceis isnotavailable,
boostedthe BTS or
enough starts
at alltocompared
use that for tothe
theBTS reference.
operator's Then there are no effects to the
setting.
_x000D_
Cell operation
If there are no is downgraded.
other synchronization sources available, the external GPS/GNSS receiver module continues providing the refere
of
Forthe S1:phase
The eNB drifting,
lost the
the phase deviation
connection is considered
to S-GW. to reach
All calls using thethe threshold
failed GTP-Uvalue and then
data path the features
are released, andrequiring phase
new GTP-U sync
data tun
still within the required limits,
The S1 interface is unavailable. _x000D_ typically over several months._x000D_
_x000D_
_x000D_
The X2 interface is unavailable. Handover of calls to or from cells of the associated adjacent BTS is not possible. Base station (
_x000D_
If no other S1 interface is available for use, BTS operation is considered faulty and no calls can be set up. _x000D_
Flexi
One
_x000D_ BTS
of theTDD:_x000D_
transport paths(SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is supporte
If another
If there
BTS synchronization
is atconfigured
is not othersource
least one according toisradio
available,
S1 interface available
network BTS starts
for
plan file.toBTS
use, useisthat for the
operation is BTS reference.
considered
waiting_x000D_ Then there
degraded areBTS
and the no effects to the BT
can continue op
_x000D_
for the correct radio network configuration file.
The
If therecellareis disabled.
no other synchronization sources available, the external GPS/GNSS receiver module continues providing the refere
because
The cell isofdisabled.
the phase drifting, the phase deviation is considered to reach the threshold value and then the air interface (cells) a
In the case of subscriber trace activation, if the failed trace connection was used for sending the trace reports, the BTS conside
_x000D_
In the case of cell trace and interface trace, if the failed trace connection was used for sending the trace reports, the BTS does
Trace session (for subscriber/cell/interface) cannot be activated/deactivated.
The BTS cannot accept new UEs attempting registration in any of the reported misconfigured PLMNs. Such an attempt by new
_x000D_
The fault has no effect on the base station operation but the LNADJ and/or LNADJL object was not stored in the eNB.
The UEs that might have already registered in misconfigured PLMN(s) remain unimpacted.
The fault has no effect on the base station operation but LNADJW object with newly learnt WCDMA neighbor cell configuration
The fault has no effect on the base station operation but LNRELW object with newly-learnt WCDMA neighbor relation configura
The fault has no effect on the base station operation. The WCDMA neighbor relation, which is reported by a UE because of acti
1)
Nohas not been
handover canstored because to
be performed the actual
cells withnumber of LNRELW
the affected PCI andper cell (LNCEL) per UTRAN carrier (in ANRPRW profile) is equ
frequency.
2) has been stored but at least one of LNRELW's mobility paremeters (psHoAllowed, srvccAllowed) has been set to 'forbidden'
If
Thethehandover
UE-basedfailure
ANR rate
is activated, there will
for the affected bemight
cell continuous retries to resolve the ECGI.
be increased.
The following feature(s), which require phase sync, are taken out of service: _x000D_
LTE1113
Handovers eICIC
from or to cells of the related adjacent BTS are not possible.
The cell is deactivated (switched off) until S1 availability is regained.
If the update of the TAC or PLMN identities was not successful, the eNB performs S1 setup which means service loss for affect
Some of the UEs with a complete set of system information of the cell stored that has left the cell and has come back within thre
There is high memory usage, which might result in memory outage.
Critical
The BTS impact on FSP
capacity operation._x000D_
decreases or the BTS is not operational. The Digital Signal_x000D_
_x000D_
Processing (DSP) does not work correctly.
The
FlexiBTS Zonecapacity
Micro FDD, decreases
Flexi Zone or the BTS TDD:_x000D_
Micro is not operational. The Digital Signal_x000D_
Processing
Critical
The BTS impact (DSP)
on the
capacity does not
operation.
decreases work correctly.
or the BTS is not operational. The Digital Signal_x000D_
Processing (DSP)
The fault has no further consequences. does not work correctly.
are possible
on the connections over this interface:_x000D_
calls management
are possible access to other network elements in the RAN
anymore_x000D_
Possible
-- loss of effects:_x000D_
-Flexi loss of remote
no calls are management access
possible._x000D_ to isother
usednetwork
elements in the RAN_x000D_
-- loss BTS
of FDD, Flexi
synchronization BTS if TDD:
the interface is used as a synchronization source
The lossinterface
of remote management
cannot access to other network elements in the RAN_x000D_
Possible impact:
- loss of synchronization The be BTS used
if is
for
thenot
transmission.
synchronized
a synchronization source._x000D_
-Flexi
The BTS IKE SAs
Zonemay and
MicroIPSec
haveFDD, SAs
to use
Flexi cannot
a Zone be established
synchronization or re-keyed
Micro TDD:interface that has a lower clock
quality:
The Certificate if the primary
interface cannot
Revocationclock
be used source
Listfor hasnotbeen
transmission.
could lost, the BTSNewswitches
Conditionally,
be updated. Bluetooth
revoked is enabled when the backhaul goes down.
certificates_x000D_
automatically
The
remain SFP unknown to
module's the
to secondary
laser
the is
BTS. not clock
switchedsource.
on orIf
noboth
SFP the primary
module anddetected
was the at all.
Normal
clock areOnlylost, loopback OAM frames are transmitted
clock.and received over the interface. If the test frame gener
The Ethernet Linksources
is down. the BTS switches to the internal
The
An Ethernet EthernetLink interface
cannot might be out of order
be successfully or the remote peer might be out of order. Traffic might get lost.
established.
No Ethernet data or clock information
The Ethernet interface is defected or the remote peer is exchanged viaisthis interface.
defective. Traffic might get lost.
Possible
- voice calls impact:
or data connections cannot be established.
--Possibleslow management
impact: the access
remote management to the management
connectivity
performance WBTS
cannotand be other
datanetwork
established.
collected elements in the RAN
-- poor loss voice
of quality and data
synchronization if theperformance
Possible
-- ifDepending impact
this interface on the
is part connections
of an IMA group, over the interface
this IMA in question:
-Possible areon
no calls impact use
possible of the Ethernet interface, the link
aboveis todescribed
be temporarily
impactsuspended from
can occur for operation
the local BTS and/or other BTS elemen
-- loss of remote
no calls management access to other network elements in the RAN
are possible
-_x000D_
The
-- losstransport connection towards
no calls are possible forifthe theconnections
interface is used
unit_x000D_
The transport
_x000D_ connection towards the remote peer may be defective. Traffic may get lost.
-None
None
None
SyncE is no longer
There might a working
be available synchronization
another source.
synchronization source at eNB; in that case the BTS switches automatically to the other clock
If no other synchronization source is available at eNB, it runs in hold-over mode;

_x000D_
Please referIPsec
Configured to status of 3080:
None
BTS traffic has switched over from the primary IPsec tunnel to secondary (backup) IPsec tunnel terminating on secondary secu
Effect in release RL60
If the FSP update fails, the BTS capacity drops. If the optical interface FPGA SW update fails, communication to radio modules
This fault does not immediately affect the operations of the BTS, but it is a notification that the BTS master clock frequency dev
The
The BTS master
module clock tuning
in question is out continues in spite
of use. This of the alarm,
fault cancels all thebut because
active faultsthe
for BTS master
the same clock adjustment is quite slow to filte
module.
The BTS is not operational or degraded.
The BTS is provided
Resources out of order.
by the module cannot be used, which means that some features might not work.
Resources provided by the module cannot be used, which means that some features might not work.
Real
there time
is nois not available. Incorrect time is BTS
included in alarms, logs, and all reports.
If the fault ispossibility
reported to
foralign RF LED
FR module, and
BTSOM SM LED
does display
not know thestatus.
real FR module state, and thus BTS SM keeps FR LED displa
there is no possibility to align RF LED and BTS SM LED display status.
The BTS continues its operation with the old software.
_x000D_
The BTS does not send any faults related to the blocked cell or the modules commissioned to the blocked cell to the network m
It is not possible to establish phone calls through the blocked module.
The BTS does not send faults to the network management system (NMS) when the BTS is blocked. The fault cancellations are
Calls through the blocked cell are transferred to another cell. It is not possible to establish new calls through the blocked cell.
All cells are disabled.
Because the faulty FSP is not configured, the BTS capacity decreases or the BTS is faulty.
Depending on the reported severity, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED, CEL
Depending on the reported severity, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED, CEL
For
The resources
BTS memory thatoperations,
are not in use
for (not commissioned)
example lack
the software of support
download and parameter updates, are not stable.
is reported by minor severity alarm (BASE STATION NOTIFICATION).
The BTS memory operations, for example the software download and parameter updates, are not stable.
ISTI (In Service Time Indicator) value for HW Repair Center might not be correct or readable.
BTS capacity decreases. The digital signal processing (DSP) does not work correctly.
The BTS capacity decreases or BTS is not operational. The Digital Signal Processing (DSP) does not work correctly.
BTS is not operational or the capacity is degraded.
No actual effect to BTS functionality. This is user-specific.
The BTS is not operating.
Some activities inside the BTS are interrupted. The BTS does not operate normally. The fault is in the unit reported in the fault s
The BTS capacity possibly decreases.
This fault prevents the BTS from functioning. Depending on <x>, some processing resources, some cells, or the whole BTS are
This fault can prevent the BTS from functioning when the RF Module is needed for the required cell configuration.
The BTS can operate properly for months or even a year when being in the 5% margin area, but eventually the DAC value reac
synchronization setting defined in the BTS commissioning._x000D_
_x000D_
The BTS
Effects in is not Frequency
FDD commissioned or integratedmode:_x000D_
Synchronization to the network. The BTS cannot be accessed or configured remotely.
Assuming that thestart
The BTS cannot BTStoreference signal state.
the operational has correct accuracy when the DAC value reaches the adjustment limit 0 or 4095 (mea
not
If the MHA is faulty, the RX performance isBTS
met any more. Even in that stage the might still
degraded. The besize
operational but
of the cell the system
might performance might drop, affecting for ex
be reduced.
_x000D_
If the MHA
Effects is faulty,
in FDD PhasetheSynchronization
RX performance is degraded. The size of the cell might be reduced.
mode:_x000D_
When the DAC
The antenna value
line reaches
is not thecorrectly.
operating adjustment Thelimit
cell0capacity
or 4095 decreases.
the basic LTE system operation effects are the same as in Freque
The cell is disabled._x000D_
Downlink
The outputsignal transmission
power on the
at the antenna given antenna
is decreased line antenna
and the is disabled andworking
is not corresponding FR transmitter is unusable. Thus, the ove
optimally.
The RX path operating performance has decreased.

The antenna line device is not working properly. The cell operation is degraded.
The module might have been started with an old SW version and is, therefore, not compatible with other modules.
The BTS capacity is lost.
The BTS capacity drops.
The MHA gain is decreased or even producing a loss. The cell performance is decreased.
Some antenna line device functions may not work properly.
_x000D_
The calls are not possible through the affected cell(s).
If other references are not available, the BTS master clock (OCXO) tuning is halted and the BTS synchronization drops to holdo
The calls are not possible through the affected cell(s).
The RF Module is configured using defaults and the performance is not as expected.
Calls are not possible through the affected cell(s) (7653 CELL FAULTY).
There can be problems in the phone calls through the affected cell(s) or calls can be impossible.
There can be problems in calls through the affected cell(s) (7654 CELL OPERATION DEGRADED).
No
Callsimpact onpossible
are not system (7652 BASE
through STATION
the affected NOTIFICATION)
cell(s).
No
There might be problems in the calls through NOTIFICATION)
impact on system (7652 BASE STATION the affected cell(s).
The TX/RX paths of the RF Module are out of order and phone calls through the affected cell(s) are not possible.
The TX part is out of power and calls are not possible through the affected cell(s).
There can be problems in the calls through the affected cell(s).
There can be problems in the calls through the affected cell(s).
This fault should cancel itself.
Heating of the module
The RF Module is ongoing.
configuration might fail and cause another fault, and there can be problems in the calls through the affected cel
The cell TX and/or RX performance might be degraded because the failure or calls are not possible through the affected cell(s)
The communication between the System Module and RF Module might be corrupted. The calls are not possible through the aff
The TX power level is decreased and there can be problems with phone calls through the affected cell(s).
There can be problems in calls through the affected cell(s).
It is not possible to establish phone calls through the blocked FR.
Default values for fan parameters are to be used.
The BTS does not send faults related to the blocked Flexi Radio module (FR) to the network management system (NMS). Fault
If the fans do not rotate as requested, there is a risk that the module temperature rises too high.
If the fans do not rotate as requested, there is a risk that the module temperature rises too high.
If the fans rotate faster than requested, they cause unnecessary noise.
The RF Module may overheat, but there is no immediate effect on the module operation.
Calls are not possible through the affected cell(s)
There can be problems with calls made through the affected cell(s).
The cell is disabled.
Flexi BTS unit in question is transmitting or receiving data with degraded performance. Fault does not trigger special action on B
Downlink signal transmission on the given antenna line is disabled and corresponding FR transmitter is unusable, hence overal
The traffic between the System Module and the connected module is interrupted. The cell operation is faulty._x000D_
_x000D_
The traffic between the System Module and the connected module is interrupted. The cell operation is faulty._x000D_
If the fault is reported for primary optical interface, then connection to further radio modules in chain is affected what is indicated
_x000D_
If the fault is reported for primary optical interface, then connection to further radio modules in chain is affected what is indicated
The cell operation is degraded. The optical interface loses its synchronization if the amount of errors exceeds the defined limit.
RP3 traffic to the connected RF Module is malfunctioning. The related cell(s) are not operational.
#N/A
The connection to the associated link is lost. The data is partly/completely lost. The worst-case fault effect can expand further fr
_x000D_
RP3 traffic from the baseband is malfunctioning. The System Module operation is degraded.
_x000D_
Fault is visibleModule
The System for the is
first
outradio in chain
of order and only. Fault
the BTS is 10
outisofsending_x000D_
order._x000D_
for the other FRs, when pooling breaks because of the lost
The System Module is out of order and the BTS is out of order._x000D_sync.
SW update needed.
available.
The BTS operation is degraded, because some of the BTS resources are not available.
If the reported alarm is 7652 BASE STATION NOTIFICATION, the BTS is using the lower level synchronization source as a refe
The BTS capacity may have decreased.
If the reported alarm is 7651 BASE STATION OPERATION DEGRADED, the BTS has no valid synchronization sources as a re
The new lasts
situation installed
for aorlong
failed HWthe
time, resources
accuracyare not available
starts before
to drift slowly. the BTSit has
However, been
might takereset.
several weeks before the BTS/RAN oper
Because of TX failure MIMO (Multiple Input Multiple Output) functionality is not operational or degraded for the cell related to th
Cells remain down.
The BTS does not function correctly. Some BB processing resources in the BTS are out of use.
The BTS resources decreased or the BTS is faulty.
The BTS operation is degraded (FSP) or the BTS is not operational (FCM/all FSPs).
Depending on the reported alarm, the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFIC
FAULTY).
The BTS is not commissioned.
The BTS capacity might decrease or there might be interference in calls (commissioning data).
BTS fault
This startup
canisprevent
interrupted
BTSandfromthe BTS is outwhen
functioning of order (RNW
the RF data).is needed
Module
The signal path is unusable. The cells using the faulty unit might not work.
The antenna line is not operating correctly. The cell is disabled.

The RS485 i/f is not operating correctly. The cell capacity decreases.
BB resources are shut down, the BTS operation will be faulty.
FCM and FTM are cells
No commissioned kept are
powered.
activated.
Fan control is not optimized.
Effect to noise/temperature
The Radio level is marginal.
Module that is connected to this OptIF is not started.
FSP resource is shut down, the BTS operation will be degraded or faulty.
FCT
If theand
fanspossible other as
do not rotate notrequested,
alarming FSPs
thereare
is akept
risk powered.
that the module temperature rises too high.
If the fan(s) do not rotate as requested, there is a risk that the module temperature rises too high.
If the fans rotate faster than requested, unnecessary noise appears.
Source unit has inconsistent SW version.
Module cannot:
1.
The save
cellin
is file a cause of the SW fallback on request
disabled.
or
Ongoing
2. mount BTSpassivereset willSystem
File last longer.
thus read the cause of SW fallback on request from the file.
BTS is not operational.
None
The System Module is out of order and the BTS is out of order.
HDLC link will be disabled on reporting Antenna Line or IUANT port.
In case of problem detection in SW activation - the SW activation and consequent reset are aborted.
In case of problem detection in Start-up, BTS remains out of order. Rollback to previous SW and another SW download must be
#N/A
#N/A
The BTS is not operational or degraded.
#N/A
PHICH transmission power is not boosted enough or at all compared to operator's setting.
#N/A
For S1: The eNB lost the connection to S-GW. All calls using the failed GTP-U data path are released, and new GTP-U data tun
S1 interface is unavailable. _x000D_
_x000D_
X2 interface is unavailable. Handover of calls to or from cells of the associated adjacent BTS is not possible. Base station(BTS)
If there is no other S1 interface available for use then BTS operation is considered faulty and no calls can be setup. _x000D_
One of the transport paths(SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is supporte
_x000D_
If
BTSthere is atconfigured
is not least one according
other S1 interface
to radio available for use
network plan file.then
BTSBTS operation
is waiting is considered
for the correct radiodegraded
network and BTS can file.
configuration continue op
Cell is disabled
Cell is disabled
In the case of subscriber trace activation, if the failed trace connection was used for sending the trace reports, then the BTS co
_x000D_
In the case of cell trace and interface trace, if the failed trace connection was used for sending the trace reports, then the BTS d
Trace session (for Subscriber/cell/interface) cannot be activated/deactivated.
BTS cannot accept new UEs attempting registration in any of the reported misconfigured PLMNs. Such an attempt by new UEs
The fault has no effect on the base station operation but LNADJ and/or LNADJL object was not stored in the eNB.
The existing UEs that might have already registered in misconfigured PLMN(s) remain unimpacted.
#N/A
#N/A
#N/A
No handover can be performed to cells with the affected PCI and frequency.
If the UE-based ANR is activated, there will be continuous retries to resolve the ECGI.
#N/A
#N/A
Handovers from or to cells of the related adjacent BTS are not possible.
Cell is deactivated(switched off) until S1 availability is regained again.
If the update of TAC or PLMN identities was not successful eNB performs S1 setup which means service loss for affected cell(s
System Information for the related GERAN neighbor cells is not reliable and will not be provided to UEs that are released with r
System Information for the related GERAN neighbor cells is not reliable and will not be provided to the UEs that are released w
Some of the UEs with a complete set of system information of the cell stored that has left cell and has come back within 3 hours
High memory usage (memory outage risk).
Critical impact on FSP operation.
#N/A
#N/A
#N/A
The fault has no further consequences.
are possible
calls management
are possible anymore access to other network elements in the RAN
Possible
-- loss of effects:
-The loss of remote
no calls management
are possible anymore access to isother
usednetwork
elements in the RAN
-- loss interface
of cannot
synchronization be used
if the for transmission.
Possible impact: The BTSif is
- loss of synchronisation thenot synchronized
a synchronisation source.
The BTS may have to use a synchronization interface that has a lower clock
quality: if the primary
The Certificate clock source
Revocation List could hasnot
been lost, the BTS
be updated. Newswitches
revoked certificates_x000D_
automatically
remain unknown to the
to secondary
the BTS. clock source. If both the primary and the
Normal
clock sources areOnly lost, loopback OAM frames
the BTS switches are
to the transmitted
internal clock.and received over the interface. If the test frame gener
The Ethernet interface might be out of order or the remote peer might be out of order. Traffic might get lost.
The Ethernet interface is defected or the remote peer is defective. Traffic might get lost.
Possible impact:
-Possible
slow management
impact: the access to the management
performance WBTS and other datanetwork elements
collected in the RAN
- poor voice quality and data performance
Possible impact on the connections over the interface in question:
- if this interface is part of an IMA group, this IMA link is to be temporarily suspended from operation
-Possible
no calls impact
are possible
-- loss
no of
callsremote
are management access to other network elements in the RAN
possible
Possible impact:
- loss of remote management access to other network elements in the RAN
The transport
-- loss connection towards
no calls are possible forifthetheconnections
interface is used
unit
The transport connection towards the remote peer may be defective. Traffic may get lost.
-None
None
None
There might be available another synchronization source at eNB; in that case the BTS switches automatically to the other clock
If no other synchronization source is available at eNB, it runs in hold-over mode;

Possible impact:
Please referIPsec
Configured to status of 3080:
None
#N/A
Reported Alarms Reported Alarms in issue 01
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION
7652 BASE STATION NOTIFICATION
7655
7650 CELL
7650 BASE STATION FAULTY
7651 BASE STATION OPERATION NOTIFICATION
DEGRADED7653
BASE CELL FAULTY
STATION FAULTY
7652 BASE STATION NOTIFICATION 7651 BASE STATION OPERATION
7652 BASE STATION NOTIFICATION DEGRADED
7653 CELL FAULTY
7651 BASE STATION OPERATION DEGRADED7652
7650 BASE BASE STATION NOTIFICATION7653 CELL FAULTY
76
STATION FAULTY
7651 BASE STATION OPERATION
7650 BASE STATION FAULTY DEGRADED
7652
7651 BASE
BASE STATION
STATION NOTIFICATION
7650
7653 BASE
CELL STATION OPERATION
DEGRADED7653
FAULTY CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL FAULTY
7654 BASE
7650 CELL
BASE STATION
STATION OPERATION
DEGRADED7653
OPERATION CELL DEGRADED
FAULTY
7654
DEGRADED
FAULTY CELL OPERATION DEGRADED
7653
7651 CELL
BASE FAULTY
STATION OPERATION DEGRADED
7652 BASE STATION NOTIFICATION 7652 BASE STATION NOTIFICATION
7653 CELL FAULTY
7652 BASE STATION NOTIFICATION 7652
CELL OPERATION DEGRADED
7651 BASE STATION OPERATION DEGRADED7654 CELL7655
7651 CELL
BASE NOTIFICATION
OPERATION DEGRADED7655
STATION CELL NOTIFICATION
OPERATION DEGRADED
7654
7652 BASE STATION NOTIFICATION7653 CELL FAULTY
7654 CELL
7652 CELL
BASE OPERATION
OPERATION DEGRADED
DEGRADED
7655
7653 CELL NOTIFICATION
7653 CELL FAULTY
7653 CELL
CELL FAULTY
FAULTY
7654 CELL OPERATION DEGRADED
7650 BASE CELL FAULTY
STATION FAULTY
7651
7651 BASE STATION OPERATIONBASE STATION
DEGRADED7652
7650 BASE OPERATION
BASE STATION
STATION FAULTY DEGRADED
NOTIFICATION7653 CELL FAULTY
76
7653
7651 CELL
BASE FAULTY
7650 BASE BASE STATION NOTIFICATION7653 CELL FAULTY
76
STATION FAULTY
7651
7653
BASE
OPERATION
BASE
CELL
STATION
OPERATION
DEGRADED
FAULTY DEGRADED
7652
7654 BASE
CELL STATION NOTIFICATION
OPERATION DEGRADED
7651 BASE STATION OPERATION DEGRADED7654 CELL7651OPERATION
7654 CELL
BASE DEGRADED
OPERATION
STATION
7653 CELL FAULTY DEGRADED
OPERATION DEGRADED
7654
7654 CELL
OPERATIONOPERATION
DEGRADED
CELL OPERATION
BASE STATION DEGRADED
DEGRADED
OPERATION DEGRADED
7654
7651 BASE STATION OPERATION DEGRADED7654 CELL7651 CELL
OPERATIONOPERATION
DEGRADED
OPERATION DEGRADED
OPERATIONOPERATION
DEGRADED DEGRADED
7651 BASE STATION OPERATION DEGRADED
7654
7651 BASE STATION OPERATIONCELL OPERATION
DEGRADED7653
7650 BASE DEGRADED
CELL
STATION FAULTY FAULTY
7651
7650 BASE
7651 BASE STATION OPERATION STATION
STATION OPERATION
DEGRADED7653
BASE CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL FAULTY
7650 BASE
STATION OPERATION
DEGRADED7653
BASE CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL
BASE FAULTY
7653 CELL FAULTY
7650 BASE BASE STATION NOTIFICATION7655 CELL NOTIFICA
STATION FAULTY
7651
7651 BASE STATION OPERATION BASE STATION
DEGRADED7652
7650 BASE OPERATION DEGRADED
BASE STATION
STATION FAULTY NOTIFICATION7653 CELL FAULTY
76
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7653 CELL FAULTY
7653
7655 CELL FAULTY
7652 CELL
BASE NOTIFICATION
7650 DEGRADED7652
7653 BASE
CELL BASE STATION NOTIFICATION7653 CELL FAULTY
76
STATION FAULTY
FAULTY
7651
7651 BASE STATION OPERATION BASE
7654 BASE
7650 CELL STATION
DEGRADED7652
OPERATION OPERATION
BASE DEGRADED
STATION
DEGRADED
76
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7650
7653 DEGRADED7652
BASE
CELL BASE STATION NOTIFICATION
STATION FAULTY
FAULTY
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7654
7650
7653 CELL
BASE OPERATION DEGRADED
STATION FAULTY
7652 CELL
BASE FAULTY
7654 DEGRADED
7650 CELL
STATION FAULTY
7651 BASE STATION OPERATION DEGRADED 7651 BASE STATION OPERATION DEGRADED
7654 CELL OPERATION DEGRADED 7654 CELL OPERATION DEGRADED
7654 CELL OPERATION DEGRADED 7654 CELL OPERATION DEGRADED
7654
7652 CELL
7653 CELL
7652 BASE STATION NOTIFICATION7653 FAULTY
CELL FAULTY
7654
7650 BASE STATION FAULTY CELL OPERATION DEGRADED7655 CELL N
7654
7652 BASE STATION NOTIFICATION7654 CELL OPERATION7652 BASE STATION NOTIFICATION
BASE STATION
DEGRADED7655 CELL NOTIFICATION
NOTIFICATION
7653
7654 CELL
CELL FAULTY
OPERATION DEGRADED
7654
7652
7654 CELL
BASE
OPERATION DEGRADED
7655
7653 CELL
CELL NOTIFICATION
FAULTY
7654
7655 CELL
7652 CELLOPERATION
BASE DEGRADED
NOTIFICATION
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7652 CELL
7654
7653 CELL
7652 BASE STATION NOTIFICATION7654 CELL OPERATION BASE FAULTY
7652DEGRADED
7654
7654 CELL
7652 BASE STATION NOTIFICATION7654 CELL OPERATION BASE OPERATION
7652DEGRADED DEGRADED
7652 BASE STATION NOTIFICATION7654 CELL OPERATION7654 CELL
BASE OPERATION
BASE OPERATION
7652 BASE STATION NOTIFICATION7654 CELL OPERATION7654DEGRADED
7652 CELL OPERATION
BASE DEGRADED
7652 BASE STATION NOTIFICATION7654 CELL OPERATION7654 CELL OPERATION
BASE STATION NOTIFICATION
BASE OPERATION
7654
7653 CELL FAULTY
7654 CELL CELL
BASE OPERATION
OPERATION
7650 DEGRADED
STATION DEGRADED
FAULTY
7653
7650 CELL
BASE FAULTY
STATION FAULTY
7653 CELL FAULTY
7653 CELL FAULTY
7652 CELL OPERATION
BASE DEGRADED
7654
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION CELL OPERATION DEGRADED
7655
7652 CELL
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION BASE NOTIFICATION
7655
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION CELL NOTIFICATION
7655 BASE
7650 BASE BASE STATION NOTIFICATION
STATION FAULTY
7651 BASE STATION OPERATION DEGRADED7652 BASE 7651 BASE
STATION
7651 STATION
OPERATION
BASENOTIFICATION DEGRADED
7652
7652 BASE
BASE STATION
NOTIFICATION
7654
7650 BASE STATION FAULTY CELL OPERATION DEGRADED
7652 BASE STATION
7652 BASE STATION NOTIFICATION7653 NOTIFICATION
CELL FAULTY
7654
7653
7652 CELL
BASE FAULTY
STATION
7652 BASE STATION NOTIFICATION7654 CELL OPERATION
7652
7654 CELL STATION NOTIFICATION
DEGRADED
BASE OPERATIONNOTIFICATION
DEGRADED
7653
7654 CELL
CELL FAULTY
OPERATION DEGRADED
7654
7652 CELL
BASEOPERATION
STATION DEGRADED
NOTIFICATION
7653
7654 CELL
7652 CELL
BASE FAULTY
OPERATION DEGRADED
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7652 CELL
BASEOPERATION DEGRADED
7654
7654 CELL OPERATION DEGRADED 7654 CELL
CELL FAULTY
OPERATION DEGRADED
7654
7652
7652 BASE STATION NOTIFICATION7654 CELL OPERATION BASE STATION
DEGRADED NOTIFICATION
7653 CELL FAULTY
7653 CELL FAULTY
7654 CELL OPERATION DEGRADED 7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7650 CELL
BASE OPERATION
7652 BASE STATION NOTIFICATION7653 DEGRADED
CELL FAULTY
7654
STATION FAULTY CELL OPERATION DEGRADED
7652 BASE STATION
CELL FAULTY
7654
7653
7652 CELL
BASE FAULTY
STATION
7650
7654 BASE
7654
OPERATIONFAULTY CELL OPERATION DEGRADED
DEGRADED
7653
7652 CELL
BASE FAULTY
7652
7654 DEGRADED
BASE
OPERATION DEGRADED
7653
7654 CELL
CELL FAULTY
OPERATION DEGRADED
7652 DEGRADED
7654
7654 CELL
7652 CELL
BASE OPERATION
OPERATION DEGRADED CELL NOTIFICATION
DEGRADED7655
7653
7654 CELL
7652 CELL
BASE FAULTY
OPERATION DEGRADED
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7652
7655 DEGRADED
BASE
NOTIFICATION
7654
7650 CELL
BASE OPERATION
7652 BASE STATION NOTIFICATION7653 DEGRADED
CELL FAULTY
7654
7652 BASE STATION
CELL FAULTY
7654
7653
7652 CELL
BASE FAULTY
STATION
7652
DEGRADED
BASE OPERATIONNOTIFICATION
DEGRADED
7653
7654 CELL
CELL FAULTY
OPERATION DEGRADED
7652 DEGRADED
7654
7654 CELL
7652 CELL
BASE OPERATION
OPERATION DEGRADED
DEGRADED
7652 CELL
BASE FAULTY
7655 CELL
7654
7652 CELLOPERATION
BASE NOTIFICATION
DEGRADED
7653
7654 CELL
7652 CELL
BASE FAULTY
OPERATION DEGRADED
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7652DEGRADED
7654
7652 BASE STATION NOTIFICATION 7652 CELL
7654
7652 CELL
7652 BASE STATION NOTIFICATION 7653 CELL FAULTY
7654
7652 CELL
7653
7654 CELL
7652 CELL
BASE FAULTY
OPERATION DEGRADED
7654 CELL
7653 CELL OPERATION
CELLOPERATION
FAULTY DEGRADED
7654
7652 BASE DEGRADED
7654
7653 CELL
7652 BASE STATION NOTIFICATION7654 CELL OPERATION BASE FAULTY
7652DEGRADED
7654
7654 CELL
CELL OPERATION
OPERATION DEGRADED
DEGRADED
7654
7652 CELL
7653
7652 BASE STATION NOTIFICATION7654 CELL OPERATION CELL
BASE FAULTY
7652DEGRADED
7654 CELL
CELL OPERATION
7654DEGRADED
OPERATION DEGRADED
DEGRADED
7652DEGRADED
7654
7652 CELL
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATION BASE OPERATION DEGRADED
7655
7650 CELL
BASE NOTIFICATION
STATION FAULTY
STATION FAULTY
7651
DEGRADED7653 OPERATION
CELL FAULTY
DEGRADED
7653
7651 CELL
BASE FAULTY
7651 BASE STATION OPERATION DEGRADED7654 CELL7651OPERATION
7654 BASE
CELL DEGRADED
STATION
OPERATIONOPERATION
DEGRADED DEGRADED
7653
7654 CELL
CELL FAULTY
OPERATION DEGRADED
7652DEGRADED
7654
7650 CELL
BASE OPERATION
STATION FAULTY
7652
7650 BASE
DEGRADED7653
BASE CELL FAULTY
FAULTY
7651
DEGRADED7653
7650 BASE OPERATION DEGRADED
CELL FAULTY
7654
7653 CELL FAULTY
7651
7654
BASE
OPERATION STATION OPERATION
DEGRADED
BASE OPERATION
DEGRADED
7653 CELL
CELL FAULTY DEGRADED
7651 CELL
OPERATION
BASE OPERATION
DEGRADED
STATION DEGRADED
OPERATION
7654 CELL OPERATION DEGRADED DEGRADED
7654
OPERATION OPERATION
DEGRADED
OPERATION DEGRADED
7654
7651 BASE STATION OPERATION CELL OPERATION
DEGRADED7652
7650 BASE DEGRADED
BASE
STATION FAULTY STATION NOTIFICATION7653 CELL FAULTY
76
7651
7651 BASE STATION OPERATION BASE STATION OPERATION
7650 BASE STATION FAULTYSTATION
DEGRADED7652 BASE DEGRADED
NOTIFICATION7653 CELL FAULTY
76
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7654
7652
7653 CELL
BASE
FAULTY
7652
7653 BASE
FAULTY
7652
7653 CELL
BASE
FAULTY
7654
7655 CELL
NOTIFICATION
7650 DEGRADED7652
7654 BASE
CELL OPERATION BASE STATION NOTIFICATION7653 CELL FAULTY
76
DEGRADED
STATION FAULTY
7655
7651
7651 BASE STATION OPERATION CELL
BASE NOTIFICATION
STATION OPERATION
7650 BASE STATION FAULTYSTATION
DEGRADED7652 BASE DEGRADED
NOTIFICATION
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7652
7653 BASE
FAULTY
7652
7653 BASE
FAULTY
7650 DEGRADED7652
7654 BASE
CELL OPERATION BASE STATION NOTIFICATION7653 CELL FAULTY
76
DEGRADED
STATION FAULTY
7655 CELL NOTIFICATION 7655
7651 CELL
BASE NOTIFICATION
STATION OPERATION
7655 CELL NOTIFICATION DEGRADED
7653 CELL FAULTY
7653 CELL
7653 CELL FAULTY
FAULTY
7651 BASE STATION OPERATION DEGRADED7652 BASE STATION
7654
7651 CELLNOTIFICATION
7652
DEGRADED7653
7650 BASE NOTIFICATION
CELL FAULTY
STATION FAULTY
7651
DEGRADED7653
7650 BASE OPERATION
CELL FAULTY
DEGRADED
STATION FAULTY
7653
7651 CELL FAULTY
7650 BASE
STATION OPERATION
DEGRADED7653
BASE CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL
BASE FAULTY
7650 BASE BASE STATION
76
7653
7651 CELL
BASE FAULTY
7650
CELL FAULTY
7653 CELL FAULTY
7652
7653 BASE
7654 STATION NOTIFICATION
CELL OPERATION
FAULTY DEGRADED
7655
7651 BASE STATION OPERATION CELL NOTIFICATION
DEGRADED
7656
7651 BASE
BASE STATION
STATION CONNECTIVITY LOST
7654
7652 CELL
BASE STATION OPERATION
OPERATION DEGRADED DEGRADED
NOTIFICATION
7655 CELL NOTIFICATION 7653
7653 CELL
CELL FAULTY
FAULTY
7654
7655 CELL
NOTIFICATION
7653 CELL FAULTY
7654 CELL OPERATION DEGRADED 7653 CELL FAULTY
7654
BASE OPERATION
7654
BASE OPERATION
7654
7650 CELL
7651 BASE STATION OPERATION OPERATION
DEGRADED7653
BASE DEGRADED
CELL
7651 CELL
7654
7652 BASE
OPERATION
STATION OPERATION
DEGRADED DEGRADED
7653
7653 CELL FAULTY
7652 BASE STATION NOTIFICATION 7652 CELL
BASE FAULTY
7653 CELL FAULTY
7654 CELL OPERATION DEGRADED 7653 CELL FAULTY
7654
7650 CELL
7651 BASE STATION OPERATION OPERATION
DEGRADED7653
BASE DEGRADED
CELL

7652 BASE
BASE STATION
STATION OPERATION
NOTIFICATION DEGRADED
7653 CELL FAULTY
STATION FAULTY
7651
DEGRADED7653
7650 BASE OPERATION
CELL FAULTY
DEGRADED
STATION FAULTY
7653
7651 CELL FAULTY
7650 BASE
STATION OPERATION
DEGRADED7653
BASE CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL
BASE FAULTY
7653 CELL FAULTY
7653 CELL FAULTY
7654 CELL OPERATION DEGRADED 7652
CELL FAULTY
7652 CELL
STATION FAULTY
7652 BASE STATION NOTIFICATION 7651 BASE STATION OPERATION
7653 CELL FAULTY
7651 BASE STATION OPERATION DEGRADED7652 BASE STATION
7651 BASENOTIFICATION
7652 BASE STATION
NOTIFICATION
7652DEGRADED7655
BASE STATIONCELL NOTIFICATION
NOTIFICATION
7654
7652 BASE STATION NOTIFICATION7654 CELL OPERATION CELL OPERATION
7655
7650 CELL
BASE OPERATION
STATION FAULTY
7651 BASE STATION OPERATION DEGRADED 7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFICATION7653
7651 BASE STATION OPERATION CELL DEGRADED
FAULTY
7654 CELL OPERATION DEGRA
7653 CELL FAULTY
7650 DEGRADED
7654 BASE
CELL STATION FAULTY
OPERATION DEGRADED
7651
STATION OPERATION
DEGRADED7652
FAULTY DEGRADED
NOTIFICATION
7655 CELL NOTIFICATION 7651 BASE STATION OPERATION
7652
7655 BASE NOTIFICATION
7654 CELL OPERATION DEGRADED 7654 CELL
7657 BASE STATION CONNECTIVITY
DEGRADED 7657 BASE STATION CONNECTIVITY DEGRADED
LOST7657 BASE STATION CONNECTIVITY
7656 BASE DEGRADED

DEGRADED 7657
7657 BASE STATION CONNECTIVITY DEGRADED
BASE STATION CONNECTIVITY DEGRADED
7653 CELL FAULTY
7653 CELL FAULTY
7653 CELL FAULTY
7653 CELL FAULTY
7655 CELL NOTIFICATION 7655 CELL NOTIFICATION
7653 CELL FAULTY
7653 CELL FAULTY
LOST7657 BASE STATION CONNECTIVITY
7656 BASE DEGRADED

7657 BASE
LOST7657 BASE STATION STATION CONNECTIVITY
CONNECTIVITY
DEGRADED
7656 BASE STATION CONNECTIVITY LOST DEGRADED
7653 CELL FAULTY
7657 BASE STATION
7653 CELL FAULTY CONNECTIVITY DEGRADED
7655
7652 CELL
7652 BASE STATION NOTIFICATION7655 CELL NOTIFICATIONBASE NOTIFICATION
7655
7650 CELL
7651 BASE STATION OPERATION NOTIFICATION
DEGRADED7653
BASE CELL FAULTY
STATION FAULTY
7651
7651 BASE STATION OPERATIONBASE STATION
DEGRADED7653
7650 BASE OPERATION
CELL FAULTY
DEGRADED
STATION FAULTY
7653
7651 CELL FAULTY
7650 BASE
STATION OPERATION
DEGRADED7653
BASE CELL FAULTY
DEGRADED
FAULTY
7653
7651 CELL FAULTY
7665 BASE STATION TRANSMISSION ALARM 7665 BASE
BASE STATION OPERATION DEGRADED
STATION TRANSMISSION ALARM
7653 CELL FAULTY
7665 BASE STATION TRANSMISSION ALARM 7665 BASE STATION TRANSMISSION ALARM
7653 CELL FAULTY

7651 BASE STATION OPERATION DEGRADED7653 CELL FAULTY

7653 CELL FAULTY
7651 BASE STATION OPERATION DEGRADED7654 CELL OPERATION DEGRADED7655 CELL NOTIFICATION
7651 BASE STATION OPERATION DEGRADED7653 CELL FAULTY
7653 CELL FAULTY

7653 CELL FAULTY

7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFICATION7653 CELL FAULTY
76
76
76
7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFICATION
7651 BASE STATION OPERATION DEGRADED7652 BASE STATION NOTIFICATION7654 CELL OPERATIO
7654 CELL OPERATION DEGRADED7655 CELL NOTIFICATION
7652 BASE STATION NOTIFICATION7654 CELL OPERATION DEGRADED
7653 CELL FAULTY

7653 CELL FAULTY
7653 CELL FAULTY
7653 CELL FAULTY
7653 CELL FAULTY

Reported Alarms in release RL60
7651
7652 BASE
BASE STATION
STATION OPERATION
NOTIFICATIONDEGRADED
7653 CELL FAULTY
7650 CELL
7654 BASE OPERATION
STATION FAULTY
DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7652
7651 BASE STATION
7650
CELL FAULTY FAULTY DEGRADED
7651
7654 BASE
7650 STATION
STATION OPERATION
CELL OPERATION
BASE DEGRADED
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7652
7651 BASE
BASE STATION
OPERATION DEGRADED
7652
7653 BASE FAULTY
7652 CELL
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654 BASE
7653
7653 CELL
CELL FAULTY
FAULTY

7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7652
7651 BASE
7653
STATION
STATION OPERATION
BASE FAULTY OPERATION DEGRADED
DEGRADED
7652 CELL
7654
7651 CELL
BASE OPERATION
STATION
7653 CELL FAULTY DEGRADED
OPERATION DEGRADED
7654
7651 CELL
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7652
CELL FAULTY
7653 CELL FAULTY
7650 CELL
7654 BASE OPERATION
STATION FAULTY
DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7653 CELL FAULTY
7654
7652 CELL
7653
7653 CELL
CELL FAULTY
FAULTY
7653 CELL FAULTY

7654
7652 CELL
7654
7652 CELL
7654
7652 CELL
7654 BASE
7653
7650 CELL
BASE FAULTY
STATION FAULTY
7653 CELL FAULTY

7654
7652 CELL
7655
7652 CELL
BASE NOTIFICATION
7655 BASE

7652
7652 BASE
BASE STATION
NOTIFICATION
7653 CELL FAULTY
7654
7652 CELL
BASE FAULTY
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7654
7652 CELL
BASE FAULTY
7654
7653 CELL
CELL FAULTY
FAULTY
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7652 CELL
BASE FAULTY
7654
7652 CELL
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7654
7654 CELL
CELL OPERATION
OPERATION DEGRADED
DEGRADED
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654
7652 CELL
7654
7652 CELL
7653
7652 CELL
BASE FAULTY
7655 BASE
7653 CELL FAULTY
7654
7652 CELL
BASE FAULTY
7654
7654 CELL
CELL OPERATION
OPERATION DEGRADED
DEGRADED
7653
7652 CELL
BASE FAULTY
7653 CELL FAULTY
7654
7653 CELL
CELL OPERATION
FAULTY DEGRADED
7654 CELL
7653 CELL FAULTY
OPERATION DEGRADED
7654
7654 CELL OPERATION
DEGRADED
7653 CELL FAULTY
#N/A
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7653
7651 CELL
BASE FAULTY
7651
CELL OPERATION DEGRADED DEGRADED
7652
7650 BASE
BASE STATION
FAULTY
7651
BASE STATION FAULTY DEGRADED
7653
7651 CELL FAULTY
7651 BASE
7654
STATION
STATION OPERATION
BASE OPERATION
OPERATION DEGRADED
DEGRADED
7653 CELL
CELL FAULTY DEGRADED
7654 CELL OPERATION DEGRADED DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED

7652
7652 BASE
BASE STATION
NOTIFICATION
7653 CELL FAULTY
7651
CELL NOTIFICATION
7653 CELL FAULTY
7653 CELL
7654 CELL OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7652 BASE
BASE STATION
NOTIFICATION
7650
CELL FAULTY
7652
7651 BASE
7654 CELL STATION
OPERATION DEGRADED
7656 BASE STATION CONNECTIVITY LOST
7653 CELL FAULTY
7653 CELL FAULTY
7654
7652 CELL
7654
7654 CELL
CELL OPERATION
OPERATION DEGRADED
DEGRADED
7653
7652 CELL
BASE FAULTY
7653 CELL FAULTY
7654
7650 CELL
STATION FAULTY
7651
7652 BASE
BASE STATION
NOTIFICATION
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY DEGRADED
7653 CELL FAULTY
7654
7652 CELL
7655
7650 CELL
STATION FAULTY
#N/A
#N/A
7651
#N/A BASE STATION OPERATION DEGRADED
#N/A
7657
7657 BASE
BASE STATION
STATION CONNECTIVITY
CONNECTIVITY DEGRADED
DEGRADED
7653 CELL FAULTY
7653 CELL FAULTY
#N/A
#N/A
#N/A
7653 CELL FAULTY
#N/A
#N/A
7657
7656 BASE
BASE STATION CONNECTIVITYLOST
STATION CONNECTIVITY DEGRADED
7657 BASE STATION
7653 CELL FAULTY CONNECTIVITY DEGRADED
#N/A
#N/A
#N/A
7665 BASE STATION TRANSMISSION ALARM
#N/A
Reported Alarms Description
7652 BASE STATION NOTIFICATION (for FCM, FCT, FTM,
and
FlexiFSP
BTSwhen FDD,working
Flexi BTS FSP is not mapped to any
TDD:_x000D_
cell)_x000D_
7650 BASE STATION FAULTY (1.FSM, 2.The faulty FSP is
not mapped to any cell and all (forFSPs
FBB in andBTSFSP arewhen working
FSP
7650 isBASEmapped
faulty)_x000D_ to any FAULTY
STATION cell) (FT)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (the faulty
7650
FSP isBASE STATION
not mapped FAULTY
to any (theatfaulty
cell and least FSP isother
onefaulty not mapped
FSP is is
7650
to any BASE
cell STATION
and all FSPs FAULTY
in BTS (1.FSM,
are 2.The
faulty)_x000D_ FSP
operational)_x000D_
not mapped to any cellFAULTY
and all FSPs in- Unit BTSstatus
are in "Out of
_x000D_
7650
7653 BASE
CELL FAULTYSTATION (the faulty (FCM FSP is mapped to the
faulty)_x000D_
7651
order", BASEFTM STATION OPERATION DEGRADED (The faulty
or all FSPs)_x000D_
cell)._x000D_
7651 BASE STATION OPERATION DEGRADED (theFSP
faulty
FSP
7651 isBASE
_x000D_ not mapped
STATION to any cell and at
DEGRADED least one other
( FSP)_x000D_ is
FSP is not mapped
operational)_x000D_
7653 CELL FAULTY to any
(FR,(the cell and
cell at
cannotleast one
operate other FSP
because is
operational)_x000D_
_x000D_
not
7650 enough
BASE available and
STATION(faulty needed resources: Tx or
FAULTY_x000D_
7653
7652 CELL FAULTY FSP is mapped toFAN, the cell).
7652 BASE STATION NOTIFICATION (FSM
BASE
Rx))_x000D_ STATION NOTIFICATION (FCM/FCT)_x000D_ external
ALD)_x000D_
7654
7655 CELL
CELLFDD, OPERATION
(FR)_x000D_ (FR, (the cell can still
Flexi BTS
_x000D_
operate becauseFlexi BTS TDD:_x000D_
still have enough available and needed
_x000D_
resources:
7653 CELLboth FAULTYTx and (FR
(The Rx))cell cannotDEGRADED
(cell operate because of it not
(FCM/FCT)_x000D_
enough
does notavailable
have enough and needed
available resources:
and needed Tx or Rx); MHA,
resources: Tx
7654
TILT,
or CELL
(but
Rx)_x000D_ OPERATION
cell already faulty DEGRADED
because of(FR)_x000D_
other
_x000D_
faults))_x000D_
7654 CELL OPERATION DEGRADED (The cell can still
Flexi
_x000D_
operateZone Micro FDD,
because Flexienough
it still has Zone Micro TDD:_x000D_
available and needed
7655
7653 CELL
CELL
resources: NOTIFICATION
FAULTY
both Tx (faulty
and FSP
Rx)_x000D_ is mapped to the
cell)._x000D_
7652
7650 BASE
BASE STATION
FAULTY (Radio Module
(1.FSM, 2.FT 3.The faulty is not
Flexi
_x000D_BTS
commissioned) FDD, Flexi BTS TDD:_x000D_
FSP
7650 isBASEnot mapped
STATION to any cell and all FSPs in faulty
BTS are
7654
7650
faulty) CELL
BASE
_x000D_ STATION FAULTY
OPERATION DEGRADED
FAULTY (1.FTM,
(1.FTM,(FR, 2.The
2.The (cell canFSP
faulty still is
FSP is
not
not mapped
operate
mapped to
because any it cell
still and
has
to any cellOPERATION all FSPs
enough in BTS
available
and all FSPsDEGRADED are
and
in BTS are (the needed
7651 BASE
faulty))_x000D_ STATION faulty
(1.FSM.
resources:
faulty))_x000D_
FSP
2.FSP isBASEnot
is both
mapped
not Tx and
mapped toto Rx),
any
any MHA,
cell and TILT)
atDEGRADED
cell)_x000D_ least one other FSP is
7651
STATION OPERATION DEGRADED (the
(the faulty
(1.FSM.
faulty
operational)_x000D_
7654
FSP
2.FSP isCELLnot
is notOPERATION
mapped
mapped to any
to anyDEGRADED
cell and at
cell)_x000D_ (FSP
least oneis mapped
other FSP to is
FSP
7651
7653
the isBASE
CELL
cell) not mapped
STATION
FAULTY to any cell
OPERATION
(the faulty and
FSP at least
DEGRADED
is mappedone other
to FSP
(1.FSM.
the is
operational)_x000D_
7654
2.FSP CELL
is notOPERATION
operational)_x000D_ mapped to anyDEGRADED
cell)_x000D_ (FSP is mapped to
cell)_x000D_
7651
7652 BASE
BASE STATION
STATION OPERATION
(FR, (1.FSM.
the
7652
7654 cell)
_x000D_
2.FSP BASE
CELL
is not STATION
OPERATION
mapped NOTIFICATION
to anyDEGRADED
cell)_x000D_ (FSPwhen
(FR, when the
the unit
is mapped to is
unit is
not
7651
not
the commissioned)_x000D_
BASE STATION OPERATION DEGRADED (1.FSM.
commissioned)_x000D_
cell)
Flexi
7654
7653 Zone
CELL
CELL Micro
is notFAULTY FDD,
OPERATION
mapped(1.FR, Flexi
any(theZone
DEGRADED cellMicro TDD:_x000D_
(FSP
cannot is mapped
operate to
2.FSP
7653
7650
7650
the CELL
BASE
BASE
cell) FAULTY
STATION
STATION
to
(1.FR,
FAULTY
FAULTY
cell)_x000D_
(the cell faulty
(the cannot
(Critical FSP
POST is notbecause
operate
test because
mapped
there
7654
there
to any are
CELL
are
cellnot
not
and enough
OPERATION
enough
all FSPs available
DEGRADED
available
in BTS and
and
are needed
needed(FSP resources:
is mappedTx
resources:
faulty)_x000D_ to or
Tx or
failures)_x000D_
Flexi
Rx),
the BTS FDD,
2.FSP
cell) when Flexi
faultyBTS FSP TDD:_x000D_
is mapped to the cell)._x000D_
Rx),
7651
7651
7650 2.FSP
BASE
BASE when
STATION
STATIONfaulty FSP
OPERATION
OPERATION
FAULTY is mapped to
DEGRADED
DEGRADED
(the faulty the cell)._x000D_
FSP cell (the
not faulty
is (non-critical
7654
Flexi
7654
FSP isCELL
BTS
CELLnot OPERATION
FDD,
mapped Flexi
OPERATION toBTS
any DEGRADED
TDD:_x000D_
DEGRADED
cell and at (FR(the
(FR(the
least one cell
othercan
canFSP still
stillis
POST
mapped
operate
7650 test
BASE to failure)
any
because cell
STATION and
there all
is FSPs
still
FAULTY enoughin
(The the BTS
available
faulty are
FSP and
is notneeded
operate because
operational)_x000D_ there are
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
faulty)_x000D_ still enough available and needed
resources:
mapped
resources: to both
any Tx
Tx and
cell and Rx))_x000D_
allfaulty
FSPsFSP in the BTS areto the
7653
7651
7401
_x000D_ - 7426both
CELL
BASE
faulty)_x000D_
FAULTY
STATION and
(EAC1=7401, (the Rx))
OPERATION
EAC2=7402 is mapped
DEGRADED
etc) (the faulty
cell)._x000D_
FSP is not mapped to any cell and at least one other
Flexi
7401 Zone
7651 - 7426Micro
BASE FDD,OPERATION
STATION
(EAC1=7401, FlexiEAC2=7402
DEGRADED
etc) (TheFSP is
faulty
operational)_x000D_
7650
FSP isBASE STATION
not mapped FAULTY
to any cell and at least
7401
7653 -CELL
7426 (EAC1=7401,
FAULTY EAC2=7402
(the faulty FSP is mappedetc)one other
to the
is
operational)_x000D_
cell)._x000D_
7401
7653 -CELL 7426FAULTY
(EAC1=7401, EAC2=7402
(The faulty etc)
FSP is mapped to the
_x000D_
cell)_x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
Flexi
_x000D_Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
7401
7650 -BASE
7426 STATION
(EAC1=7401, EAC2=7402 etc)
Flexi Zone Micro FDD,FAULTY Flexi Zone Micro TDD:_x000D_
7401
7650 -BASE 7426 STATION
(EAC1=7401, EAC2=7402 etc)
FAULTY_x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7650 BASE STATION FAULTY (1.FSM, 2.The faulty FSP is
not
Fleximapped
BTS FDD, to any cellBTS
Flexi andTDD:_x000D_
all FSPs in BTS are
faulty))_x000D_
7650 BASE STATION FAULTY (FCM out of order, FTM out of
order)_x000D_
FSP
7650is
Flexi notFDD,
BTS
BASE mapped
STATIONFlexitoBTSany
FAULTY cell and
(theatfaulty
TDD:_x000D_ leastFSP one isother FSP is
not mapped
operational)_x000D_
(Depends
to anyBTS
Flexi on
cell FDD, <x>)_x000D_
and all FSPs
Flexi BTS in BTS
TDD:_x000D_are faulty)_x000D_
7652
7650
7651
7650 BASE
BASE STATION
FAULTY
OPERATION
FAULTY (1.
(the FSM. (FR,
DEGRADED
faulty 2.FSP when
The themapped
isfaulty
(The
not unit
FSP
faulty isis
Flexi
not BTS FDD,
mapped to Flexi
any cellBTSand TDD:_x000D_
all FSPs in the BTS are
FSP
to any is cell
FDD:_x000D_not and
mapped to any
all FSPs in cell
BTSand are at least one other FSP is
faulty)_x000D_
7653 CELL
faulty)_x000D_
operational)_x000D_
7651 BASE FAULTY
STATION (1.FR,
OPERATION (the cell DEGRADED
cannot operate (the because
faulty
7651
there
7651 BASE
are
BASE not STATION
enough
STATION OPERATION
available
OPERATION and DEGRADED
needed
DEGRADED resources:(When
(FSP, Tx no or
OptIF
7652
FSP
Flexi
other BASE
is not
BTS STATION
mapped
FDD, clock
reference to
Flexi BTS NOTIFICATION
any
sources cell and
TDD:_x000D_
are at (1.uncommissioned
least one
available)._x000D_ other FSP is
Rx),
used
FR,
7650 2.FSP
2.for
MHA
operational)_x000D_
BASE when
or RET
STATION faulty
RF-sharing,)_x000D_
workingFSP
FAULTY: is
for mapped
other
When to the
BTS)_x000D_
the cell)._x000D_
absolute OCXO
7652
7654
7651 BASE
CELL
BASE STATION
OPERATION
DEGRADED
OPERATION (When
(FR(the
DEGRADED there
cell(The is at
can least
still
faulty
7653
7652 CELL
BASE
adjustment
one more FAULTY
STATION
limit
working value (FR(min
reference out
NOTIFICATION ofmax)
orclock order has (cell
source (OptIF
beencannot operate
connected
available)._x000D_ to
operate
FSP
because
FR: the because
is not mapped
there
faulty
reached._x000D_ arethere
opticalnot are cell
tointeface
any
enough stillis enough
and atused
available
not available
least andtoone and FSP
other
needed
provide needed is
_x000D_
resources: both
operational)_x000D_ Tx and Rx))
resources:
7651 BASETx
transmission
TDD:_x000D_ or any
for
STATION Rx))_x000D_
cell)_x000D_
OPERATION DEGRADED:
7652
7653 BASE FAULTY
CELL
Otherwise._x000D_ STATION(OptIF NOTIFICATION
(the faulty FSP is mapped
connected (1.
to FR:uncommisioned
Theto the
cell cannot
7650
FR. BASE
2.optical STATION
interface FAULTY
that is not (Holdover
used to is not
provide possible
cell)._x000D_
operate
_x000D_
because because there
of insufficient data or phase error in holdoverneeded
are not enough available and
transmission
7654 CELL
resources:
Flexi Zone Tx
Microfor
or any
OPERATION cell)_x000D_
Rx)_x000D_
FDD, DEGRADED
Flexi Zone Micro(FR out of order (the
TDD:_x000D_
exceeds
7653 CELL 3 us)_x000D_
FAULTY (OptIF connected to FR: The cell cannot
cell
7653
7651
7652
7651 can
CELL
BASE
BASEstill operate
FAULTY
STATION
STATION because
(the faulty
OPERATION
NOTIFICATION
OPERATION there
FSP are
is still
mapped
DEGRADED enough
(Uncommissioned
DEGRADED available
to (Holdover
the
operate
and needed
cell)._x000D_
source because there
resources:
or Antenna Line are
both
with not enough
Tx and
LNA available
Rx), MHA, for other
commissioned and needed
is possible)_x000D_
Flexi BTS
resources: FDD,
Tx orFlexi BTS
Rx)_x000D_ TDD:_x000D_
RET)_x000D_
7654 CELL
BTS)_x000D_
7652 BASE OPERATION
STATION DEGRADED
NOTIFICATION (OptIF connected to
7653
7653
7652The
_x000D_
FR:
7654
CELL
CELL
BASE
CELLcell
FAULTY
FAULTY
STATION
can
OPERATIONstill
(No
(The VSWR
faulty
NOTIFICATION
operate DEGRADED FSP
because isit(When
Threshold mapped
(fault
still
there
Tuning
source
has
(Otherwise, to
enough
is
is at
mode
the
for RF
least
is
one
active,more workingresource)_x000D_
mandatory
cell)._x000D_
uncommissioned reference clock
resources for thesource
cell are available)._x000D_
lost)_x000D_
Flexi
available
using
7653
_x000D_
7654 Zone
RP1and
CELL
CELL Micro
FAULTY
OPERATIONFDD,
needed
protocol Flexi
resources:
only)_x000D_
(All RX Zoneboth
CHANNELs
DEGRADED Micro Tx(NoTDD:_x000D_
and
usedVSWR Rx)_x000D_
by the cell are
Threshold
7654
_x000D_
7650
_x000D_
7653 CELL
BASE
CELL
affected)_x000D_ OPERATION
STATION
FAULTY DEGRADED
FAULTY
(Otherwise, for RF (OptIF
using connected
IR protocol to
Flexi
Tuning
7653
FR:
7655 Zone
The mode
CELL
CELLcellMicro
can FDD,
is active,
FAULTY still
NOTIFICATION (theFlexi
the
operate cell
cell Zone canMicro
cannot
because
(VSWR still
remain
it TDD:_x000D_
operate
still
Threshold because
operational
has enough
Tuning modeit
Flexi
only)
_x000D_
7651
has Zone
BASE
enough Micro
STATION FDD,
required Flexi Zone
OPERATION
resources Micro
DEGRADED TDD:_x000D_ (When no
because
available
is active.
7653
7650
7654 CELL
BASE
CELL
there
and
Reported
FAULTYis not
needed
STATION
OPERATION
enough
resources:
toward
(in case
FAULTY local
DEGRADED theavailable)_x000D_
available
BTSboth
cell RX
Tx
Site
cannot
(At andand/or
Manager
remain
least
TX
Rx)_x000D_
one RXmode
other
7655 reference
CELL
resources)_x000D_
_x000D_
only)_x000D_
operational becauseclock
NOTIFICATION sources
there (VSWR
isisnot are available)._x000D_
enoughThresholdavailable Tuning RX and/or
CHANNEL
7654
7652
is CELL
BASE
active.
_x000D_ used
STATION
Reported by the
OPERATION cell
DEGRADED
NOTIFICATION
toward local notBTS affected)_x000D_
(TILT
(When
Site failure
Managerthere affects
is at least
Flexi
_x000D_
TX Zone Micro
resources)_x000D_
_x000D_
antenna carrier ofFDD,
a cell Flexi
within Zone same Micro TDD:_x000D_
BTS)_x000D_
one
7650
7654
_x000D_more
only)_x000D_
7654 CELL
BASE
CELL working
OPERATION
STATION
OPERATION reference clock
DEGRADED
FAULTY_x000D_
DEGRADED (no source (the
(TILTavailable).
cell
(Otherwise) can
failure still
affects
7652
7652
remain
antenna BASE
BASE STATION
STATION
operational
carrier of a NOTIFICATION
NOTIFICATION
because
cell within it still
same has (fault
(fault
enough
BTS)_x000D_ source
impact
source onis
available iscells RX
7654
within CELL
uncommissioned
the OPERATION
same resource)
BTS, for DEGRADED
example, TILT (in
(TILT cases
serves failure
for that affects
antennas
uncommissioned
and/or
7652
regardless
antenna TX
BASE of STATION
carrier resource)_x000D_
resources)_x000D_
theofBTS/RAT;
detected NOTIFICATION
a cell within issue the cell
same (no impact
still has
BTS)_x000D_ on
enough cells
used
7654
_x000D_
within by
thedifferent
CELL OPERATION
same BTS,TX for uncommissioned
DEGRADED
example, TILT (TILT
serves source)
failure
foron affects
antennas
available
7652
antenna BASE RX
carrier and/or
STATION
ofFDD,
a cell resources
NOTIFICATION
within same to remain
(no
BTS)_x000D_impact cells
Flexi
7652
used
7654 Zone
BASE
by
CELL Micro
operational)_x000D_
within the same STATION
different
OPERATIONBTS/RAT;
BTS, for Flexi Zone
NOTIFICATION Micro
uncommissioned
DEGRADED
example, TILT(no TDD:_x000D_
(fault
(TILT
serves source
source)
failure
foron is
affects
antennas
7652
7654 BASE
CELL
uncommissioned
antenna STATION
OPERATION
carrier unit)
ofBTS/RAT;
a cell NOTIFICATION
DEGRADED
within impact
(cell can
same BTS)_x000D_ cells
stillisoperate
_x000D_
used
7652
within by
BASE
thedifferent
sameSTATIONBTS, for uncommissioned
NOTIFICATION
example, TILT (ALD
serves source)
whichfor serving
antennas
because
7652
7652
for BASE
BASE it still
different hasuncommissioned
STATION
STATION
BTS; enough availablesource)_x000D_
NOTIFICATION
NOTIFICATION and(no
(in needed
impact
case resources:
faultonsource
cells is
used
7652
both
within by
BASE
Txthedifferent
andsameSTATION BTS/RAT;
Rx)_x000D_
BTS, for uncommissioned
NOTIFICATION
example, TILT(ALD serves source)
which is serving
for antennas
uncomissioned
_x000D_
for different BTS; unit)
uncommissioned source)_x000D_
7653
used
7650
7654 CELL
by
BASE
CELL FAULTY
different
STATION
OPERATION (cell
BTS/RAT; cannot
FAULTY operate
uncommissioned
DEGRADED (FTM/FCT)_x000D_ because
(RX,TX, source)
TILT,thereMHA) are
_x000D_
not
7653 enough
CELL FAULTYavailable(FR, and FF needed (The resources:
cell cannotTx or Rx, but
operate
7654
other CELL
because cell(s)
thereOPERATION
canare provide
not enough DEGRADED available(MHA,
service)_x000D_ and neededTILT)
7650 BASETx
resources: STATION FAULTY (no cell can provide service)
or Rx))_x000D_
7654 CELL OPERATION DEGRADED (FR, FF (The cell can
still
7652 operate
BASE because
STATIONitNOTIFICATION
has enough available (ALD which and neededis serving
resources:
for different both Tx and Rx))
7652 BASE BTS, STATION uncommissioned
NOTIFICATION resource)_x000D_
(ALD which is serving
_x000D_
for different BTS, uncommissioned resource)_x000D_
7652
7654 BASE STATION
CELL OPERATION NOTIFICATION
DEGRADED (ALD is working for
(otherwise)
_x000D_
different BTS)_x000D_
7652
CELL OPERATION DEGRADED (ALD is working for
(otherwise)_x000D_
_x000D_
7652
CELL NOTIFICATION (Flexi Filter,(ALD AISG is MHA,
working RET) for
_x000D_
7652
CELL NOTIFICATION (Flexi Filter, AISG MHA, RET) (ALD is working for
_x000D_
7655
_x000D_ CELL NOTIFICATION (Flexi Filter, AISG MHA, RET)
7655 CELL NOTIFICATION (Flexi Filter, AISG MHA, RET)
FDD:_x000D_
7652 BASE STATION NOTIFICATION (if other clock is
7652 BASE STATION NOTIFICATION (if other valid
available)_x000D_
Flexi BTS source
reference FDD, Flexi BTS TDD:_x000D_
is available)_x000D_
7651
7652 BASE
BASE STATION
STATION OPERATION
(Uncommissioned (other
7651
Flexi
case) BASE
BTS STATION
FDD, Flexi OPERATION
BTS TDD:_x000D_ DEGRADED (other
source)_x000D_
cases)_x000D_
7652 BASE STATION NOTIFICATION (Uncommissioned
Flexi
7653 BTS
CELLFDD, FAULTY Flexi(cell
BTScannot
TDD:_x000D_
operate because of not
_x000D_
source)_x000D_
enough
7652 BASE
TDD:_x000D_
7653 available
STATION and needed resources:
NOTIFICATION
CELL FAULTY (cell cannot operate Tx or Rx)_x000D_
(Uncommissioned
because of not
source)_x000D_
7654 CELL
source)_x000D_ OPERATION DEGRADED (cell can stillofoperate
7650
enough BASE
7653 CELL
7654 STATION
available
CELL OPERATION and FAULTY
needed
FAULTY (Cell DEGRADED (Holdover
resources:
cannot operate not
Tx orpossible
because Rx)_x000D_
(Otherwise)_x000D_ not
because
7653
because
7654
enough CELL
CELL itofstill hasand
FAULTY
insufficient
OPERATION
available enough
(Thedata available
cell
orcannot
DEGRADED
needed phase
resources:and
operate
error
(cell needed
Txincan resources:
because
holdover
or still of
operate
Rx)_x000D_
_x000D_
7653
both
there CELL
Tx
are and FAULTY
Rx)_x000D_
enough (Cell
available cannot
and operate
needed because
resources: of
Tx not
or
exceeds
because
_x000D_
Flexi
enough Zone 3it still
us)_x000D_
Micro
available has FDD,enough
and Flexi
needed available
Zone andTDD:_x000D_
Micro
resources: needed resources:
Tx or Rx)_x000D_
_x000D_
Rx)_x000D_
7654
7651
both
7654 CELL
BASE
Tx
CELLand OPERATION
STATION
Rx)_x000D_
OPERATION DEGRADED
OPERATION
DEGRADED -(Cell
DEGRADED dedicated
can radio
(Holdover
still operate
7654
_x000D_
Flexi
7654 CELL
Zone
CELL
resources orOPERATION
Micro
OPERATION
sharedFDD, radio DEGRADED_x000D_
Flexi Zone
DEGRADED
resources, Micro TDD:_x000D_
(The
where cell
LTE can
is still
master
possible)_x000D_
_x000D_
because
Flexi
7654 BTS
CELL it still
FDD, hasFlexi
OPERATION enough
BTS available
TDD:_x000D_
DEGRADED and (Cellneeded
can resources:
still operate
7650
operate
SM;
7652
Flexi
both BASE
cell
BASE
Zonebecause
can STATION
still
STATION
Micro it still
operate
FDD, FAULTY
has enough
because
NOTIFICATION
Flexi Zone(no cell
cell
Micro can
available
has
(if provide
and
enough
other
TDD:_x000D_ needed
valid available
Flexi Tx
becauseBTS and
it FDD,
service)_x000D_
resources:
Rx)
still
both has_x000D_
Flexi
Tx enough
BTS available and
Rx)TDD:_x000D_
(Uncommissioned
needed resources:
required
reference
7650
_x000D_BASE Tx
source)_x000D_
both
7652 Tx
BASEand source
STATION is and
resources_x000D_
Rx)_x000D_
STATION available)_x000D_
FAULTY
NOTIFICATION (no cell (Uncommissioned
can provide
7653
_x000D_CELL
BASE FAULTY
service)_x000D_
7652
7653 CELL STATION(cell
FAULTY (other
(The cellcannot
cannot
NOTIFICATION
cell can provide
operate service)_x000D_
because
(Uncommissioned
operate becauseof not there
_x000D_
source)_x000D_
enough available and needed resources: Tx or Rx)_x000D_
7653
source)
are
Flexi
7652 Zone
CELL
not
BTSenough
BASE Micro
FAULTY
FDD, FDD,
available
Flexi BTSFlexi
(other
STATION NOTIFICATION and Zone
cell can
needed
TDD:_x000D_ Micro
provide TDD:_x000D_
resources: service)_x000D_
Tx or
7654
7654 CELL
CELL
Rx)_x000D_
7652 BASE
OPERATION
OPERATION
STATION DEGRADED (Uncommissioned
DEGRADED
NOTIFICATION
(Otherwise)_x000D_
(cell
(if canvalid
other
(Uncommissioned still operate
source)
_x000D_
Flexi
becauseBTS it FDD,
still hasFlexi BTS
enough TDD:_x000D_
available and needed resources:
reference
7654 CELL
source)_x000D_
Flexi
7652 Zone
BASE source
OPERATION
Micro
STATION is available)_x000D_
FDD,BTS DEGRADED
Flexi (The
Zone Micro(Uncommissioned
NOTIFICATION cell can
TDD:_x000D_ still
both
Flexi
7651
7653 Tx
operateBTS
BASE
CELLand FDD,
because Rx)_x000D_
STATION
FAULTY Flexi
it still
(cellhas TDD:_x000D_
OPERATION
enough
cannot DEGRADED
available
operate and
because (other
needed
of not
7654
7652 CELL
source)_x000D_
BASE OPERATION
STATION DEGRADED_x000D_
NOTIFICATION (Uncommissioned
cases)
resources:
enough
7652
7653 BASE
CELL both
available
STATION
FAULTY Txandand Rx)_x000D_
needed resources:
NOTIFICATION
(cell cannot operate Tx or Rx)_x000D_
(Uncommissioned
because of not
source)_x000D_
_x000D_
7654 CELL
source)_x000D_ OPERATION DEGRADED (cell can still operate
enough
7652
7653 BASE
CELLavailable
STATION
FAULTY and needed
(The resources:
NOTIFICATION
cell cannot Tx or
(Uncommissioned
operate Rx)_x000D_
because there
Flexi
because
_x000D_
7654 Zone
CELL
source)_x000D_ Micro
it still has
OPERATIONFDD,enough Flexi Zone
available
DEGRADED Micro
and TDD:_x000D_
(cellneeded
can stillresources:
operate
are
7652
both
7654 not
Tx enough
BASE
CELLand available
STATION
Rx)_x000D_
OPERATION and needed
NOTIFICATION resources:
(Uncommissioned
(The Tx
cell can or
still
because
7654 CELL
Rx)_x000D_ it still
source)_x000D_ has enoughDEGRADED
OPERATION available and
DEGRADED (Otherwise)_x000D_
needed
(Otherwise)_x000D_resources:
operate
_x000D_
Flexi Tx
both BTS because
and FDD, it stillBTS
Flexi
Rx)_x000D_ hasTDD:_x000D_
enough available and needed
7654
7653 CELL
resources:
Flexi
7652 Zone
BASE OPERATION
FAULTY
both
Micro
STATIONTx
FDD, (during
and DEGRADED
FR
Rx)_x000D_
Flexi Zone
NOTIFICATION startup (The cellcell
ifTDD:_x000D_
Micro(Uncommissioned can still
cannot operate
_x000D_
Flexi
operate
becauseBTS of FDD,
becausenot Flexi
it
enough BTS
still has TDD:_x000D_
enough
available and available
needed and needed
resources: Tx
7653
7654 CELL
source)_x000D_
Flexi
7652 Zone
BASE FAULTY
OPERATION
Micro
STATION FDD, (The cellZone
Flexi cannot
DEGRADED
NOTIFICATION operate
Micro (cell canbecause
TDD:_x000D_
(Uncommissioned there
still operate
resources:
or
areRx)_x000D_
Flexi
because
7654 BTS
not enough
CELL both
FDD,
it still hasTx
Flexi
OPERATION and
available BTS
enough Rx)_x000D_
TDD:_x000D_
and needed
available
DEGRADED resources:
and needed Tx
(Otherwise)_x000D_ or Rx,
resources:
7653
7652 CELL
source)_x000D_
_x000D_
7654 CELL
BASE FAULTY
OPERATION
STATION (cell cannot
DEGRADED
NOTIFICATION operate because
(during
(Uncommissioned not
FR startup if
but
both other
enough
7654 Tx
_x000D_
Flexi BTS
CELLand cell(s)
FDD,
available can
Rx)_x000D_
Flexi
OPERATION provide
BTS
andbecause
needed service)_x000D_
TDD:_x000D_
resources:
DEGRADED Tx or Rx,
(Otherwise)_x000D_ but other
Flexi
cell
7650
7653
Flexi Zone
can
BASE
CELLstill
operate
STATION
FAULTY FDD, Flexi
FAULTY
(cell Zone
cannotit still
(no Micro
has
cell
operate in TDD:_x000D_
enough
BTS
because available
can provide
of not and
7652 Zone
7652
cell(s)
_x000D_
7650
needed
7653 can
BASE
BASE
CELL
Micro
provide
STATION
STATION
resources:
FAULTY
FDD,
both
Flexi Zone Micro(Uncommissioned
NOTIFICATION
service)_x000D_
NOTIFICATION
FAULTY
(duringTx and (no
Rx_x000D_
RFresources:
start-up can
TDD:_x000D_
cell (Uncommissioned
ifTx provide
the
service)
enough
7653 CELLavailable
source)_x000D_
7650 BASE and
FAULTY_x000D_
STATION needed
FAULTY (no cell can orcell
provideRx,cannot
but other
Flexi
7652
cell(s)
7653
Zone
source)_x000D_
service)_x000D_
7655
operateCell
BASE
can
CELL
Micro
STATION
provide
FAULTY
FDD,
Notification
because there Flexi
(during
are notZone
FR
NOTIFICATION
service)_x000D_
(The cell
Micro
runtime)
enough
cannot
TDD:_x000D_
available
(Uncommissioned
operate andservice)
because needed
there
7654
_x000D_
7653 CELL
CELL
resources:
source)_x000D_ OPERATION
FAULTY
Tx or (The
Rx)_x000D_ DEGRADED_x000D_
cell cannot operate because there
7650
are
7652
7654 not enough
BASE
CELL available
STATION
OPERATION FAULTY
and
NOTIFICATION
DEGRADED (no
needed cell can
resources: provide
(Uncommissioned Tx
(Otherwise)_x000D_ service)
or
are
7654 not enough
CELL
Rx)_x000D_
source)_x000D_ available
DEGRADED resources:
(during RF Tx
start-up if
but
the other
cell can cell(s)
7654 CELL FAULTY
7653 still can
operate
OPERATION provide
because
(The DEGRADEDservice)
it still
cell cannot operate has enough
(The cell available
can stillthere
because
and
is notneeded
operate because
enough resources:
available bothenough
it still has
and Tx andavailable
needed Rx)_x000D_
resources: and Txneeded
or
_x000D_
resources: both Tx and Rx)_x000D_
Rx)_x000D_
Flexi
_x000D_
7654 Zone
CELLMicro OPERATIONFDD, Flexi Zone Micro(The
DEGRADED TDD:_x000D_
cell can still
7650
operateBASE
Flexi Zone STATION
Micro FDD,
because the cell FAULTY
Flexi
stillZone(no cell can provide and
Micro TDD:_x000D_
has enough available
service)_x000D_
7652
7650 BASE
needed BASE STATION
STATION
resources: both NOTIFICATION
FAULTY
Tx and(no Rx)cell (Uncommissioned
can provide
7653 CELL
BASE FAULTY
source)_x000D_
service)_x000D_
7652 STATION(other cell(s) can provide
NOTIFICATION (Uncommissioned
service)_x000D_
7655
7653 CELL NOTIFICATION (Otherwise)_x000D_
7652 CELL
BASE FAULTY
source)_x000D_ STATION(other cell(s)
NOTIFICATION can provide
(Uncommissioned
service)_x000D_
7653 CELL
source)_x000D_ FAULTY (The cell cannot operate because there
7652
are BASE
not enough STATION
available NOTIFICATION (Uncommissioned
7653 CELL
source)_x000D_ FAULTY (cell and
cannot needed
operate resources:
becauseTx ofornot
Rx)_x000D_
enough available and needed resources: Tx or Rx)_x000D_
7654
7654 CELL OPERATION DEGRADED (Otherwise_x000D_
7654 CELL
7652 CELL OPERATION
BASE OPERATION
STATION NOTIFICATION DEGRADED (The
DEGRADED (Uncommissioned
(cell can cell still
canoperate
still
operate because it still has enough available
because it still has enough available and needed resources:
source)_x000D_ and needed
resources:
both Tx
7653 CELLandboth Tx and
Rx)_x000D_
FAULTY (The Rx) cell cannot operate because there
7653 CELL FAULTY
are not enough available and (The cell needed
cannot operate
resources: because
Tx or there
are not
Rx)_x000D_
7653 enough available and needed
CELL FAULTY (The cell cannot operate because resources: Tx or there
Rx)_x000D_
7654
are notCELL
enough OPERATION
available DEGRADED
and needed resources: (The cell can
Tx still
or
7652
7654 BASE
CELL STATION
OPERATION NOTIFICATION
DEGRADED (the
(Thefaultycell SFP
can works
still
operate
Rx)_x000D_
on opticalbecause
interface it still
that has
is enough
not used available
to provide and needed
transmission
operate
7652 BASE
resources:
7654 CELLbecause STATION
both Tx
OPERATION it still has
Rx) enough available
andNOTIFICATION
DEGRADED (the
(Thefaulty andcan
cell needed
optical
still
for any
resources:
interface cell)_x000D_
is both
not Tx
used andto Rx)_x000D_
provide transmission for any
operate
7652
7653 BASE
CELLbecause STATION
FAULTY it still
(The has enough
NOTIFICATION available
cell cannot operate (The and
faulty needed
becauseopticalthere
7652 BASE
cell)_x000D_
resources:
interface STATION
is both
not Tx and
used toNOTIFICATION
Rx)_x000D_
provide transmission(the faultyfor any SFP works
are
7652
on
7654 not enough
BASE
optical
CELL interfaceavailable
STATION
OPERATION and
thatNOTIFICATIONneeded
NOTIFICATION
isDEGRADED resources:
not used to provide (the faulty
(the faulty Tx or
optical
transmission
faulty optical
7652 BASE
cell.)_x000D_
Rx)_x000D_
interface is STATION
not used toNOTIFICATION
provide transmission(the for any SFP works
for
7652
on
7653any
interface cell)
BASE
optical
CELL isinterface
used
STATION
FAULTY to provide
that
(The is transmission
not
cell used
cannot to (the
provide
operate forfaulty
any opticalthere
transmission
because
7654 CELL
cell)_x000D_
cell)_x000D_
interface OPERATION
is not used DEGRADED
to provide transmission (The cell can
for any still
for
are any
not
operate
7654 cell)
enough
CELLbecause available
OPERATION it still has and needed
enough
DEGRADED resources:
available
(the faultyand Tx or
needed
optical
cell)_x000D_
Rx.)_x000D_
resources:
interface
7654 CELL is both
usedTx to and Rx)_x000D_
provide transmission forfaulty any optical
7654 CELL OPERATION
cell)_x000D_ OPERATION DEGRADED DEGRADED (the (The cell can still
interface is used to
operate because provide
it still transmission
has enough available for anyand needed
cell)_x000D_
resources: both Tx and Rx.)_x000D_
7652 BASE STATION NOTIFICATION (the faulty optical
interface
7652 BASE is not used toNOTIFICATION
STATION provide transmission (1.FSM, for2. any FSP on
cell)_x000D_
FBB not mapped to any cell)_x000D_
7654
7655 CELL CELL OPERATION
(FSP on FBB (themapped
faulty optical to the
interface
7650
cell.) BASE is used
STATION to provideFAULTY transmission
(FSP and for
FBB: anythe faulty FSP
cell)_x000D_
is not BASE
7650 mapped to any cell
STATION FAULTYand all(1.FSM, FSPs in2.FBB: the BTS theare faulty faulty).
_x000D_
FSP is not mapped to any cell and all FSPs in BTS are
7651
7651 BASE
BASE STATION STATION OPERATION OPERATION DEGRADED DEGRADED (1.FSM, (FSP and
faulty)_x000D_
2.FBB when FSP on FBB is not mapped tocell
anyand at least
FBB:
7651 the faulty FSP is not
BASE STATION OPERATION DEGRADED (FBB: the mapped to any
cell)._x000D_
one other
faulty
7654 FSPFSP
CELL
is mapped
isOPERATION
not operational). to any
DEGRADED
_x000D_
cell and at least one other
7653
FSP isCELL FAULTY
operational). (1.
_x000D_ FSP and FBB: (FSP the faulty on FBB FSPisis
mapped
7654 CELL
mapped to the
to the cell)
OPERATION
cell. 2.OptIf: DEGRADED
thefaulty
cell cannot (the operate
faulty optical
7653
interface CELL is FAULTY
used (FBB: the
to provide transmission FSPfor mappedbecause
is any to the
there
Flexi
cell). are
BTS not
FDD, enough
Flexi available
BTS and
TDD:_x000D_ needed resources: Tx or
cell)_x000D_
Rx
7652 )._x000D_
BASE STATION NOTIFICATION (SSD firmware
7650
7652 BASE
BASE STATION
STATION FAULTY NOTIFICATION (FSP: The (the faulty
faulty FSP
optical is not
7654 CELL
update)_x000D_
mapped to OPERATION
any cell and DEGRADED
all FSPs in the (OptIf
BTS (thefaulty).
are cell can still
interface
7650
operate
7650 BASE
BASE is not
because used
STATION
STATION it stilltoFAULTY
provide
has
FAULTY enough transmission
(FSP and FBB:
available
(otherwise)_x000D_ for
and Theany cell)
faulty
needed
_x000D_
FSP is not mapped to any cell and all FSPs in the BTS are
resources:
_x000D_
7651 BASE
7651 both
BASE STATION Tx and
STATION OPERATION Rx))_x000D_
OPERATION DEGRADED DEGRADED (FSP: (1.FSM, The
faulty).
Flexi
2.FBB Zone_x000D_
when MicroFSP FDD,
on FBB Flexi is Zone
not Micro
mapped TDD:_x000D_
to any
faulty
7651
7651 FSP
BASE
BASE is not
STATION
STATION mapped to
OPERATION
OPERATION any cell and
DEGRADED at least
DEGRADED (FSP and one
(1.FSM, other
7650
2.FBB BASE
cell)._x000D_
FSP isThe
when STATION
operational).
FSP on_x000D_
FBB FAULTY ismapped
not mapped tocell
anyand(1.FSM,
FBB:
7651
7654 BASE
CELL faultySTATION
OPERATIONFSP is not
OPERATION
DEGRADED to any
DEGRADED
(FSP onmappedFBBatisleast
7653
2.FBB CELL
cell)._x000D_
one otherwhen FSPFAULTY
FSP is (1.FSP:
operational).
on FBB is The
not faulty
_x000D_
mapped FSP
to is
any to the
mapped
7650
cell.
7654 BASE
2.OptIf:
CELL to the The cell)
STATION
OPERATION cell FAULTY
cannot (1. The
operate
DEGRADED System
because
(FSP on Module
thereFBB are
is not
7653 CELL
cell)._x000D_
internal FAULTY (1. or
communication FSP and FBB: Theproblem.
synchronization faulty FSP All issignal
enough
mapped
7650 CELL
mapped
7654 BASEavailable
to
to the
the cell.
OPERATION and
cell)_x000D_
STATION 2. needed
FAULTY
OptIf: The
DEGRADED resources:
(thecell faulty
cannot
(FSP Tx
FBB or Rx
is
operate
on FBBnot )._x000D_
mapped
because
is
processors
7654
to anyBTS CELL
cell inside
OPERATION
and all the System
FSPs inDEGRADED
BTS Module are
(OptIf
are faulty)_x000D_ unstable.
(The cell 2. The can
there
mapped
Flexi
FSP onare tonotthe
FDD,
system enough
cell)
Flexi
module available
BTS is and
TDD:_x000D_
faulty, the needed
FSP is resources:
not mapped Tx toor
still
7651
Rx
7653 operate
BASE
)._x000D_
CELL because
STATION
FAULTY it
(A still
OPERATION
criticalhas enough
HW/SW available
DEGRADED
fault inside and
(1.The
the needed
RF
any
7652 cell
resources:
faulty BASE
FBB andisbothall
notFSPs
STATIONTxmappedand inNOTIFICATION
BTS
Rx))to any are cellfaulty.)_x000D_
and atit least
7654
Module.
_x000D_ CELL The OPERATION
cell cannot DEGRADED
operate because (OptIf (Theone
does not other
cellhave can
FSP
Flexi
still
enough is
BTS
operateoperational.
FDD,
availablebecause Flexi
and 2 The
BTS
it still
needed degraded
TDD:_x000D_
has enough
resources: FBB is mapped
available
Tx or and
Rx)_x000D_ to any
needed
7651
7650 BASE
cell)_x000D_
BASE STATION
STATION OPERATION
FAULTY (The DEGRADED
System Module (1.The cannot
resources:
7654
7651 BASE
System CELLModuleboth
OPERATION
STATIONTx
internaland Rx))
DEGRADED
OPERATION
communication (The
DEGRADED cell
or synchronizationcan still
(No valid
7652
be
reference BASE
identified
operate because STATION
by its_x000D_
sources still NOTIFICATION
it available.hasTDD:_x000D_
enough
The BTS (working
available
OCXO is FBB
and in needed is not
holdover
problem,
Flexi
mapped
product BTS or
to
code FDD,the
any but BTS
Flexi memory
cell)._x000D_
is knownBTS by operations
its physical are not
device stable.
address At(by
resources:
mode.)_x000D_
least
7652 one
BASE both
signalSTATIONTx andNOTIFICATION_x000D_
processor Rx)_x000D_
inside the System Module is
7653
object
7650
7652 CELL
ID), orFAULTY
BASE
BASE there is(faulty
STATION
STATION aFAULTY
System FBB(1.The is mapped
Module toFSP
subassembly
faulty the is not (FSP)
_x000D_
working.2.
_x000D_
cell)._x000D_
allocation
mapped to The FSP
failure.)_x000D_
any cell onNOTIFICATION
and system
all FSPs module
in the
(Uncommissioned
is faulty,
BTS are the
faulty FSP isunit
source
7652
not
Flexi mapped
ZoneTx/RxSTATION
BASE tofilter)_x000D_
any cellNOTIFICATION
and atZone
leastMicro one(According
FSP in BTS to is the
7654
_x000D_ CELLMicro
2.FCT/FCM)_x000D_
_x000D_
synchronization OPERATION FDD, Flexi
priorityNOTIFICATIONDEGRADED
list, the synchronization
TDD:_x000D_
(degraded FBB
reference is
operational
7652
mapped
7651 BASE
BASE faulty.)_x000D_
to Micro
theSTATION
cell)._x000D_
STATION OPERATION (Flexi
DEGRADED Zone Micro
(Afollows
(the faulty
Flexi
source
_x000D_ Zone
BTS)_x000D_ has been FDD,
changed Flexi to Zone
lower Micro
source. TDD:_x000D_
Tuning
7655
subassembly
FSP
Flexi
7653
this is
new CELL
BTS not
CELL NOTIFICATION
mapped
FDD, (FSP)
FAULTY Flexi
reference._x000D_ inside
to(A any
BTS the
critical (working
cell and
TDD:_x000D_
HW/SW at FBB
System_x000D_ faultisone
least mappes
inside other the toRF
FSP theis
7652
7653
cell)
Module BASE
CELLcannot
operational)_x000D_
7652 BASE STATION
FAULTY be
(LCR)_x000D_
identified by
NOTIFICATION its product (The
_x000D_ working
code but FSP
is known is
Module.
_x000D_
7650
not BASE
mapped TheSTATIONcell
to any cannot operate(the
FAULTY
cell)._x000D_ because
faulty FSP it does is notnot mapped
have
by
7652
Flexi
to its BTS
_x000D_
enough
any physical_x000D_
BASEavailable
cell TDD
and STATION
only:
all and
FSPs 7650NOTIFICATION
needed BASE
in the resources:
BTS are(if
STATION other or alarm,
TxFAULTY
faulty)_x000D_ Rx)_x000D_ where
_x000D_
Flexi
device
fault
Flexi BTS
4001
Zone FDD,
address
is not
Micro Flexi
(by
the
FDD, BTS
object
alarm Flexi TDD:_x000D_
ID),
source,or
Zone thefor
Micro number
the same of
TDD:_x000D_ FSPs
FSP, in
FBB, theor
7654
(Holdover
7651
7653
7650 CELL
BASE
CELL
BASE OPERATION
time
FAULTY run out.)
STATION
STATION (The DEGRADED
OPERATION
FAULTY FSP on system
(1.FSM. (The
DEGRADED cell
module
2.The can
faulty (the still
is faulty
FSP faulty is
BTS
FR
7651
Flexi
operate
FSP is
isisBTS too_x000D_
active)_x000D_
BASE FDD,
because
not STATION
mapped Flexi
it still
to OPERATION
BTShas
any TDD:_x000D_
enough
cell and DEGRADED
available
at least one and other (When
needed FSP nois
and
not
small,
7653
other
7650 the
mappedor
CELLFSPunit
reference
BASE is
toor
FAULTY mapped
any
STATIONan
clock cell
IP tofaulty
and
address
(the
sources
FAULTY the cell)._x000D_
all are
FSPs inmapped
initialization
FSP
(1. is BTS
available)_x000D_
FSM.2. has
The arefaulty
to the FSP isin
resources:
operational)_x000D_
7650
_x000D_ BASE
faulty)_x000D_ bothSTATIONTx and Rx)
FAULTY (Level BTS fault is toggling
failed.)_x000D_
cell)._x000D_
7652
not
7653
the BASE
mapped
CELL
BTS.)_x000D_ STATION
to any cell
FAULTY (theNOTIFICATION
and all FSPs
faulty (When
isinmapped
FSP DEGRADED the BTS thereare
to the is cell).
at least
7654
7651
_x000D_
7653
one CELL
BASE
CELL
more
faulty)_x000D_ OPERATION
STATION
FAULTY
working (FR(the
reference DEGRADED
OPERATION cell
clock cannot
source) (The
operate degraded (the
because FSP is
faulty
_x000D_
mapped
FSP is notto the
mapped cell.)_x000D_
to any cell and at least one other FSP is
7652
there
7651
Flexi
7651 are not
BASE
BTS
BASE FDD, enough
STATION
STATIONFlexi availableNOTIFICATION
OPERATION
BTS and needed
TDD:_x000D_
OPERATION (An unsupported
DEGRADED
DEGRADED resources: (the
(Level TxBTS
faulty or
_x000D_
operational)_x000D_
module
Rx))_x000D_
FSP is
7650isBASE was
not found
mapped
STATION into the_x000D_
any cell
FAULTY_x000D_ and at least one other FSP is
fault
7655
7653 toggling
CELL FAULTY in the(the
NOTIFICATION BTS.)_x000D_
faulty(The FSP working
is mapped FSP isto mapped
thecan still to
BTS.
7654 Typically
CELL
operational)_x000D_
_x000D_
_x000D_ this
OPERATION happens when
DEGRADED a new (FR module
(the version
cell is
the
7653
Flexi cell.)_x000D_
cell)._x000D_
Flexi
installed
operate BTS
CELL
Zone FDD,
and_x000D_
becauseFAULTY
Micro Flexi
it still
FDD, BTS
(the has TDD:_x000D_
enough
faulty
Flexi Zone FSP available
is mapped
Micro and
TDD:_x000D_ to needed
the
7652
_x000D_
7650 BASE
BASE STATION
FAULTY (1.FCM/FCT, (Level BTS
2.FSP fault
(allis is
FSPs
there
resources:
7653
toggling is
cell)._x000D_
7650 BASE
CELLan
in older
bothSTATION
FAULTY
the BTS
Tx and
BTS.)_x000D_ SW
(in Rx))
FAULTY
case in use
the that
(Flexi
cell does
Zone
cannot not
Micro support
remain BTS the out
Flexi
in
new BTS
_x000D_
of Zone
moduleareMicro
order)_x000D_
operational FDD,
faulty))_x000D_
version.)_x000D_
because thereFlexi is Zone
not Micro TDD:_x000D_
enough available RX and/or
_x000D_
7650
OPERATION DEGRADED (FSP, not
_x000D_
Flexi
7652
TX
7653 Zone
BASEMicro
resources)_x000D_
CELL STATION
FAULTY FDD, FlexiBTS
NOTIFICATION
(Level Zonefault Micro TDD:_x000D_
is(Flexi
toggling Zone in Micro
the there BTS
all
7653
7653
7650
is FSPs
working)
_x000D_ CELL
CELL
BASE in BTSFAULTY
FAULTY
STATIONare faulty)_x000D_
(the
(The cell
FAULTY RF cannot
Module
(all DSPsoperate
or Filter
are because
cannot
faulty)_x000D_ be
BTS.)_x000D_
_x000D_
are not enough available and needed resources: Tx orall
identified
7651
7654
7652
_x000D_ CELL
BASE byOPERATION
its product_x000D_
STATION OPERATION
DEGRADED
(in case that
(Uncommissioned (not
Flexi
Rx)_x000D_
code
DSPs
regardlessZone
but
areisfaulty)
known
of FDD,by its
the detected Flexi
physicalZone
issue the Micro
device TDD:_x000D_
address
cell(Uncommissioned
still has (by is
enough
7654
7652
7650
7654 CELL
BASE
BASE
CELL OPERATION
STATION
STATION
OPERATION DEGRADED
NOTIFICATION
FAULTY_x000D_
DEGRADED (Level
(the cellBTS canfault still
object_ID),
available
7654
toggling CELL RX
in theor an_x000D_
and/or
OPERATION
BTS.)_x000D_ TX resources
DEGRADED so it can remain
(Otherwise)_x000D_
source)_x000D_
_x000D_
operate
7650 BASE because STATION there are
FAULTY enough (the available
faulty FSP and is needed
not mapped
RF Module
operational)_x000D_
_x000D_ with incompatible frequency has been detected,
7654
resources:
to any CELL
cell OPERATION
both
and_x000D_ Tx and DEGRADED (Otherwise)
Rx)_x000D_
or
7653
7655both
_x000D_ CELL
CELLsector_x000D_
FAULTY
NOTIFICATION - radio sharing is disabled
(Level BTS fault is toggling in the with the
all
7652FSPs
types
WCDMA BASE in
(A and the
system B)BTS
STATIONare
module areNOTIFICATION
faulty)_x000D_
configured and the to LTE
the same RF Module
(in cannot
cell case faultoperatesource in the is
BTS.)_x000D_
two-carrier_x000D_
uncomissioned
because
_x000D_ there unit)
are not enough available and needed
FSP
7653
case, isCELL
resources: ornot mapped
a dual
TxFAULTY
orPA RF to(the
Rx._x000D_ any_x000D_
cell cannot
module has been operate replaced because withBTS there
a
7656
cell
are and
not BASE at
enough STATION
least one
available CONNECTIVITY
other andFSP is
needed LOST
operational)_x000D_
resources: (Level Tx or
single
_x000D_
7650
fault is PA
BASE RF
toggling module,_x000D_
STATION
in the FAULTY (the faulty FSP is not mapped
BTS.)_x000D_
7653
Rx)_x000D_
and
7654
to any CELL
it CELL
cannot
cell and FAULTY
serve
OPERATION
all FSPs all(the infaulty
cells FSPare
commissioned
DEGRADED
the BTS is mapped to the
-faulty)_x000D_
radio toRF
sharing themodule,cell).
is
_x000D_
_x000D_
or
7651
7401the
disabled cell
BASE cannot
with the
STATION
- 7426OPERATION
EXTERNAL ALoperate
WCDMA because
system
OPERATION (EAC1=7401, it
moduledoes
DEGRADED not
but have
the
EAC2=7402 LTE
(the enoughcell
faulty
etc)
7654
available
can
FSP isCELL
still and
operate
not mapped needed
because anyDEGRADED
to resources:
there
cell and are Txatenough (the
orleast cell other
Rx)_x000D_
available
one can still and
FSP is
operate because it still
_x000D_resources:
needed
operational)_x000D_ bothhas Tx enough
and Rx._x000D_ available and needed
resources:
7654 CELL both
OPERATIONTx
_x000D_ FAULTY (the faulty FSP is mapped
7653 and Rx)_x000D_
DEGRADED (The Mast to Head
the cell).
Amplifier
7652 BASE (MHA) STATION or TILT cannot_x000D_
NOTIFICATION:_x000D_
beRadio
1. identified sharing by itsisproductdisabledcode withbut theisWCDMA known by system its physicalmodule
4082:_x000D_
In case of inconsistent SW after fallback_x000D_
4082:_x000D_
Flexi BTS
7650 BASE FDD,
STATIONFlexi BTS FAULTY TDD:_x000D_
In case
4082:_x000D_ of inconsistent SW after(1.FCM/FCT,
fallback_x000D_ 2.The faulty
FSP
7650 is not
BASE mapped
STATION FAULTYto any cell and all FSPs in BTS faultyare
In case of inconsistent
faulty))_x000D_ SW after(1.FCM/FCT,
fallback_x000D_ 2.The
FSP
7653
7650 is-BASE
not cell
the mapped to any
is disabled
STATION FAULTY cell and
because all
theFSPs
(1.FCM/FCT, in2.The
downlink BTS are that
carrier
faulty
7651 BASE
faulty))_x000D_
transmits STATION
PSS/SSS OPERATION
signals has DEGRADED
failed_x000D_ (FSP - the
FSP
faultyisFSP not mapped
is not to anytocell
mapped anyandcellalland
FSPsat in BTS
least one are
other
7651
7654 -BASE
the cell
faulty))_x000D_ STATION
is degraded OPERATION
because DEGRADED
the downlink (FSP carrier- thethat
FSP
7650
faultyisBASE
transmits operational)_x000D_
FSP isSTATION
not mapped
PSS/SSS FAULTY
signals toisany (1. FSM.
cell and 2.
working_x000D_ at The
leastfaulty
one FBB is
other
7651
7653 BASE STATION OPERATION DEGRADED (FSP - the
not
FSP isCELL
mapped
faulty
FAULTY
to any cell
operational)_x000D_
FSP
(FSPandwhen faultyand
all FSPs FSP
is not mapped to any cell and at least one other
is mapped
FBBs in the BTS to the
cell)._x000D_
are
7653 faulty)_x000D_
FSP isCELL
_x000D_
7651 BASE
FAULTY (FSP when faulty FSP is mapped to the
operational)_x000D_
STATION OPERATION DEGRADED (the faulty
cell)._x000D_
7653 CELL FAULTY
In
FBBcase
Flexi is
_x000D_BTS of
not consistent
mapped
FDD, Flexi to(FSP
SW
BTS when
anyafter andfaulty
TDD:_x000D_ FSPone
cell fallback_x000D_
at least is mapped
other FSP to theor
cell)._x000D_
7651
FBB
7652 BASE STATION
is operational)_x000D_ OPERATION
_x000D_ (FCM/FCT,
In case
_x000D_ of consistent SW after fallback_x000D_
FSP)_x000D_
7653
_x000D_
7651 CELL
BASE FAULTY
STATION(the faulty FBB DEGRADED
OPERATION is mapped to (FCM/FCT,the cell).
In case
_x000D_
Flexi Zone of consistent
Micro FDD, SW after
Flexi fallback_x000D_
FSP)_x000D_
7651 BASE
BASE STATION
4083:_x000D_
7651
_x000D_ STATION OPERATION OPERATION DEGRADED DEGRADED (FCM/FCT, (When no
FSP)_x000D_
In case
other of inconsistent
reference clock SW
sources afterarefallback_x000D_
available)_x000D_
4083:_x000D_
_x000D_
7650
7652
In case BASE STATION FAULTY
of inconsistent SW after(FCM/FCT)_x000D_
NOTIFICATION (When at least there is
fallback_x000D_
4083:_x000D_
7652
In
onecase
moreBASE
of STATION
consistent
working SWNOTIFICATION
reference after (Antenna line without
fallback_x000D_
clock source)
7650
In case
relation BASE
of STATION
to inconsistent
cell and without FAULTY
SWDEGRADED (FCM/FCT)_x000D_
afteror
ALD fallback_x000D_
ALD not related
7651
7654
In case BASE
CELL STATION
OPERATION
of consistent SWOPERATION DEGRADED
(HDLC
after fallback_x000D_ link todisabled
7650
for BASE
cell)_x000D_
(FCM/FCT)_x000D_
working STATION
ALD with FAULTY
relation to (FCM/FCT)_x000D_
cell)_x000D_
7651
Flexi
In case
_x000D_BTSBASE
of FDD,STATION
consistentFlexi SW OPERATION
BTS TDD:_x000D_
after DEGRADED
fallback_x000D_
_x000D_
7652
7650 BASE
(FCM/FCT)_x000D_
- The STATION
BTS is faulty NOTIFICATION
because of the(HDLC
problem linkwith
disabled
file
7651
7654 BASEALD
CELL
4085:_x000D_
for working STATION
OPERATIONwithout OPERATION
DEGRADED
relation to DEGRADED
cell)(DC voltage disabled
_x000D_
signature.
(FCM/FCT)_x000D_
for ALD Rollback
utilized to previous
by cell)_x000D_ SW is required._x000D_
In case
7653
4085:_x000D_
7652 of
CELL
- The inconsistent
FAULTY
BTS (the
is working SW after
radio
on thefallback_x000D_
unit connected
current SW. to New portSW #3 or
_x000D_
7650
#4 on BASE
FBBC STATION
might not FAULTY
be used (FCT)_x000D_
because of a problem related
In case
cannot
4085:_x000D_
7655 of
be
CELL inconsistent
activated
NOTIFICATION SW
because after
of fallback_x000D_
file
(Antenna signature
In
to case
port
7650 of or
#3
BASE
mismatch._x000D_ consistent
#4 configuration
STATION SW after
FAULTY on FBBCline
fallback_x000D_
(FCT)_x000D_cardrelated
and the to cell
cell
In case
without
7650
7651
cannot of
ALD)
BASE
BASE inconsistent
operateSTATION
STATION
because SW
FAULTY after
OPERATION
it does fallback_x000D_
(configuration
not DEGRADED
have enough failure at BTS
available
In case
_x000D_
7650 of consistent
BASE STATION SW after fallback_x000D_
FAULTY (FCT)_x000D_
startup)_x000D_
(FCT)_x000D_
and
Flexi needed
BTS resources:
FDD:_x000D_ Tx orZoneRx)_x000D_
7651
Flexi
In case BASE
Zone of STATION
Micro
consistent FDD, SWOPERATION
Flexi
after DEGRADED
Micro
fallback_x000D_TDD:_x000D_
7651
_x000D_
7654 -BASE
7652 BASE
CELL STATION
OPERATION
STATION OPERATION
DEGRADED
(the radioGPS (re-
unit
(FCT)_x000D_
7650
7651 The
BASE
configuration BTS
STATION is
failure faulty because
OPERATION
during BTS of the(External
problem
DEGRADED
runtime) with loading
_x000D_
connected
receiver
_x000D_
the DSP has
SW to port
lost
into #3
the
the or #4
satellite
proper on FBBC
visibility
memory might
but
place. not
there be
is
Rollback used
another
to
(FCT)_x000D_
Flexi
becauseZone of Micro
a isproblemFDD,related
Flexi Zone to for Micro
port #3 TDD:_x000D_
or #4 configuration
valid
_x000D_reference
previous SW source available
required._x000D_ use)_x000D_
_x000D_
7651
on FBBC BASE cardSTATION
but the OPERATION
cell can still DEGRADED
operate because it still has
_x000D_
Flexi
7652 Zone
- The Micro
BTS isFDD, working Flexion Zone Micro TDD:_x000D_
the current SW. New SW
_x000D_
enough available and needed resources: both Tx and
7651
7651
cannot
7656 BASE
BASE STATION
STATION
be activated OPERATION
OPERATION
because
CONNECTIVITY DEGRADED
DEGRADED
of fileMicro
signature
LOST (External
mismatch.
(Transport
Flexi Zone
Rx)_x000D_ Micro FDD, Flexi Zone TDD:_x000D_
GPS receiver
path(SCTP) for has
S1lost the
is broken. satellite visibility
No other and thereavailable
S1 interface are no
7651
7652 BASE
BASE STATION
STATION OPERATION
(the radio unit
other other valid
for use)._x000D_ reference sources available)_x000D_
connected
_x000D_ to port #3 or #4 on FBBC is not
_x000D_
_x000D_
7651
Flexi BTS
(TransportBASE STATION DEGRADED
TDD:_x000D_
path(SCTP) for S1 is broken (otherbutcase)_x000D_
there is at least
one other S1 interface available for use). (External GPS
receiver has lost the satellite visibility but there is another
valid reference source available for use)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (External
GPS receiver has lost the satellite visibility and there are no
other other valid reference sources available. The holdover
threshold value is not expired yet)_x000D_
_x000D_
7650 BASE STATION FAULTY (External GPS receiver has
lost the satellite visibility and there are no other other valid
reference sources available. The holdover threshold value is
expired)
The estimated phase error in holdover has exceeded 5 us.
7656 BASE STATION CONNECTIVITY LOST(No other S1

interface
7656 BASE is operational.)_x000D_
STATION CONNECTIVITY LOST(No other S1
_x000D_
interface is operational)_x000D_
7657
_x000D_BASE STATION CONNECTIVITY DEGRADED (An
other S1 interface
7657 BASE is operational.)
STATION CONNECTIVITY DEGRADED (An
other S1 interface is operational)
7652 BASE STATION NOTIFICATION (1.FSM. 2.FSP or FBB

is not BASE
7652 mapped to any cell)_x000D_
STATION NOTIFICATION (FSP or FBB is not
7655
mapped CELL
to NOTIFICATION
any cell)_x000D_ (FSP or FBB is mapped to the
Flexi BTS
cell)_x000D_ FDD, Flexi BTS TDD:_x000D_
7655
7650 CELL
BASE NOTIFICATION
STATION FAULTY (FSP orfaulty
(the FBB is mapped
FSP is not to the
mapped
Flexi BTS
cell)_x000D_ FDD, Flexi BTS TDD:_x000D_
to anyBASE
7650 cell and all FSPs
STATION in the BTS
FAULTY (the are
faultyfaulty)_x000D_
FSP is not mapped
Flexi
7651 BTS
BASE FDD, Flexi BTS
STATION TDD:_x000D_
OPERATION DEGRADED (the faulty
to any
7650 cell and all FSPs in the BTS are faulty)_x000D_
FSP
7651 isBASE
BASE
STATION
not mapped
STATION
FAULTY
to any (theatfaulty
cell and
OPERATION leastFSP
DEGRADED one isother
not mapped
(theFSP is
faulty
to any cell and all FSPs in the BTS are faulty)_x000D_
operational)_x000D_
FSP
7651 isBASE
not mapped
STATION to any cell and at least one other
OPERATION FSP is
7653 CELL FAULTY
operational)_x000D_ (the faulty FSP DEGRADED
is mapped to (thethe faulty
FSP is not mapped to any cell and at least one other FSP is
cell)._x000D_
7653 CELL FAULTY (the faulty FSP is mapped to the
operational)_x000D_
_x000D_
cell)._x000D_
7653
Flexi CELLMicro
Zone FAULTY (the
FDD, faulty
Flexi ZoneFSP is mapped
Micro to the
TDD:_x000D_
_x000D_
cell)._x000D_
7650
Flexi BASE STATION FAULTY
Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
7650 BASEMicro
Flexi Zone STATION
FDD,FAULTY
-
7650 BASE STATION FAULTY (the faulty FSP is not mapped
to any cell and all FSPs in the BTS are faulty)_x000D_
Flexi
FSP is BTS
notFDD, Flexi
mapped toBTS TDD:_x000D_
any cell and at least one other FSP is
7653 (cell cannot
operational)_x000D_ operate because of not enough available
and needed resources: Tx or Rx)_x000D_
7653 CELL FAULTY (the faulty FSP is mapped to the cell).
7654 (cell can still operate because it still has enough
available
Flexi BTSandFDD,needed resources:
Flexi BTS both Tx and Rx)_x000D_
TDD:_x000D_
_x000D_
7650 BASE STATION FAULTY (1. FSM.2. DEGRADED
The faulty FBB is
Flexi
not mapped to any cell and all FSPs andTDD:_x000D_
Zone Micro
(FCM/FCT)_x000D_ FDD, Flexi Zone Micro FBBs in the BTS
7653
7654 FAULTY (otherDEGRADED
CELL OPERATION
are faulty)_x000D_ cell(s) can provide
(FR)_x000D_
service)_x000D_
7655
7651 CELL
BASE NOTIFICATION
STATION OPERATION (FR, if incompatible
DEGRADEDSW (theversion
faulty
7650
FBB is not mapped to any cell and at least one otherservice)
has BASE
been STATION
detected on FAULTY
a (no
unit)_x000D_ cell can provide FSP or
_x000D_
FBB is operational)_x000D_
Flexi
7653 Zone
CELLMicro FDD,
FAULTY Flexi
(the Zone
faulty FBB Micro TDD:_x000D_
is mapped to the
7655 CELL
cell)._x000D_ NOTIFICATION

source)_x000D_
7653 CELL FAULTY (Otherwise)_x000D_
7654 CELL OPERATION DEGRADED (Otherwise)_x000D_
7650 BASE STATION FAULTY (The System Module internal
baseband
7650 BASEbus is out ofFAULTY
STATION synchronization.)_x000D_
(A synchronization failure in
_x000D_
the optical RP3 interface.)_x000D_
7650
7651 BASE
BASE STATIONSTATION FAULTY OPERATION (The DEGRADED
temperature measured (The
_x000D_
at theBASEFSMisisdegraded
lower than -10 BTS Centigrade. The BTS
operation
7650
7651 BASE STATION
STATION in the
FAULTY
OPERATION (Theinternal
software
DEGRADED does(Acannot
baseband bus
not
CRC
start
between
support properly,
the
the new because
System the FSPs
Module
commissioning and cannot
RF
file Module,
loaded beto powered
or
the the
BTS.) on in
failure,
7650
too cold synchronization
BASE STATION FAULTY
conditions.) problems or an incorrect initialization
synchronization
in
(ThetheBTS opticalunit RP3 is interface.)_x000D_
lost in downlink
properties data is invalid or in uplink.)_x000D_
or missing.
7652
_x000D_
7651 BASE
BASE STATION
OPERATION (BTS
DEGRADED fault from (An the
_x000D_
Or
7651 the
External optical
BASE Antenna interface
STATION Line FPGA
OPERATION
Device file
(ALD) is invalid
DEGRADED
is or missing.
reported as BTS
incorrect
7652
7652
Or BASE
BASE
a Flash commissioning
STATION
STATION
memory parameter
NOTIFICATION
NOTIFICATION
operation failurevalue (Data
(A
(The an
fault
incritical
FCM, corruption
or control
orinerror
inthe in
Mast
message
all on
the
FSPs.
(Temperature
notification)
the System
commissioning on
Module FSP
file. board
internal
Or the exceeds
baseband
transmission threshold
bus.)_x000D_
parameters value.)
Head theAmplifier
traffic
Or isBTS-internal (MHA)
malfunctioning SW isbetween
detected.
update the
has The fault
System
failed orreduces
and RFhave
a corrupted the not
gain
SW
_x000D_
been commissioned
performance
Modules.)_x000D_
file has but
beenFAULTY or
maintains properlyits set.)
function. The alarming MHA
7652
7653
7653 BASE
CELL
CELL STATION
FAULTYBTS.)(RF NOTIFICATION
(The (cell cannot operate
RF Module (The System
internal because Module
not
serves
_x000D_
detected
temperature
enough
another
in the Flash
exceeds
available and memory
the
needed thresholdin FCM
resources: or in
value.) Tx allorbaseband
FSPs.)
Rx))
bus
is
7653 CELL FAULTY (The Small Form Factor Pluggable of
7652
7650out of
BASE synchronization.
STATION or
NOTIFICATION
FAULTY cell cannot
(all FSPs operate
(There
are havebecause
been
faulty)_x000D_
not
7654
7651
(SFP)
7651
7650 enough
problems CELL
BASE withavailable
OPERATION
malfunction
BASE STATION
STATION and
commissioning needed
OPERATION
occurred
OPERATION
FAULTY ordata
DEGRADED the resources:
inDEGRADED
SFP SW (The
module
DEGRADED
(FTM/FCT)_x000D_ Txisor(at
package
Mast but
Head
not still
least
7653
7654
Rx)_x000D_
BTS
one is
Amplifier CELL FAULTY
OPERATION
operational.)
working does FSP)not (The
work temperature
DEGRADED
properly. The inside
(A HWthe
received RF specific
failure signal RF
physically
(A
7653 Flash
Module
detected CELLisbypresent
memory
tooFAULTY
anhigh. (no
antenna Or electrical
operation
(FR,the FF
line failure
cell (cellconnection
cannot
device. in
cannot at least
Oroperate exists),
one
operate
communication FSPor
because
because the
orthere
with of
_x000D_
level
incoming
Faraday.
not is
enough decreased.
optical
available The
signal and alarming
is and
missing/too
needed MHA serves
weak.
resources: Or this
Tx the
or BTS.)
fibre
are
the
7654
7652 not enough
application
CELL available
MHA
OPERATION or TILT needed
failed.
DEGRADED Or resources:
the cell
(There can
is a Tx or
still Rx)
cable
Or theBASE
Rx))_x000D_
operate
STATION
isBTS-internal
detached.
becausefailure The
thereSW NOTIFICATION
System
update
are enough Module
hasavailable (Uncommissioned
failed clock
or a reference
and corrupted
neededSW
synchronization
source)_x000D_
differs
file
7654
7653 has from
CELLbeen the RF
OPERATION
FAULTY Module
(Cellin the RF
clock,
DEGRADED
cannot Module
or
operatethe internal
RF
(FR, Module
FF
because baseband
(cell lost
notcan lock
still
7654
resources:
bus,
7655 orCELL
cell
CELL OPERATION
both
can Tx and
still
NOTIFICATION operate Rx)DEGRADED
because (Thehas
it still
(Otherwise)_x000D_ temperature
enough
to the
detected
operate
enough
insideBASE
7650 incoming
in the
because
available
theand specific clock,
Flash
STATION it
and or
memory
still has
needed
RF Module cell cannot
in
enough
FAULTYis(all at
resources:
too operate
least
available
low
FSPs one
Tx
orare because
FSP
and
or
thefaulty) or
needed
Rx)_x000D_
highest not
available
enough
Faraday)
resources:
7654 CELLavailable
bothneeded
Txand
OPERATION and resources:
needed
Rx))
DEGRADED both
resources: Tx and
Tx
(Cell orRx)_x000D_
can Rx)_x000D_
temperature
7655
_x000D_
7650 CELL
BASE exceeds
NOTIFICATION
STATION the
FAULTY power (The decrease
antenna
(FCM/FCT/SCR, limit,
line orstill
device
allthe operate
cell
is
FSPs) not
_x000D_
because
can
working
7651 still
BASE still
operate have
properly,
STATION enough
because
the available
there
configuration
OPERATION are is and
enough
not
DEGRADED needed
available
valid or resources:
a given
(at and
least
7655
7651
7654 CELL
BASE
CELL NOTIFICATION
STATION DEGRADED (Data corruption
(FSP) on the RF
7652
both
needed Tx
parameter
one
Module
BASE
workingand isOPERATION
STATION
Rx)
resources:
internal incorrect.
FSP) both
baseband OrTx DEGRADED
NOTIFICATION
and Rx)Filter
External
bus.)
(The
(The System
SW
is missing being Module
from
clock
downloadedreference
Antenna line.) to differs
FSM is from
corrupted the RF or Module
incorrectly clock in
formed.)part of
RX, or cell can still operate
7655 CELL NOTIFICATION (Validated RF module because it still has enough
available
7654 CELL
temperature and isneeded
OPERATION
higher thanresources:
DEGRADED both Tx
the predefined (Theand SW
maximumRx)downloading
allowed
to the
value.) RF Module has failed.)
7653 CELL FAULTY (the cell cannot operate because there
are not enough available and needed resources: Tx or
Rx)_x000D_
_x000D_
7654 CELL OPERATION DEGRADED (the cell can still
operate because there are enough available and needed
Reported Alarms Description in issue 01 Reported Alarms Description in release RL60
7652 BASE STATION NOTIFICATION (for FCM, FCT, FTM,
and
FlexiFSP
BTSwhen FDD,working
Flexi BTS FSP is not mapped to any
TDD:_x000D_ 7650 BASE STATION FAULTY (FCM, all FSPs)
cell)_x000D_
7650 BASE STATION FAULTY (1.FSM, 2.The faulty FSP is 7651 BASE STATION OPERATION DEGRADED (at
not mapped to any cell and all (forFSPs
FBB in andBTSFSP arewhen working least one FSP, Faraday)
FSP
7650 isBASEmapped
faulty)_x000D_ to any FAULTY
STATION cell) (FT)_x000D_ 7650
7653 BASE
CELL FAULTY STATION(FR FAULTY
(the cell (FT)_x000D_
cannot operate
_x000D_
7650 OPERATION DEGRADED
(the faulty FSP is not (themapped
faulty _x000D_
because there are not enough available and
FlexiBTS:_x000D_
7650
FSP
to anyisBASEnot
cell STATION
mapped
and all to
FSPs FAULTY
any
in cell
BTS (the
and
are faulty
at least FSP
one
faulty)_x000D_ isother
not mapped
FSP is 7651
needed
7650 BASE
BASE STATION
resources:
STATION Tx OPERATION DEGRADED
or Rx)) (FCM/FCT)_x000D_
FAULTY
7650
to anyBASE cell and STATION
all FSPs FAULTY
in BTS (1.FSM, 2.The faulty FSP is
are faulty)_x000D_ 7650
(FSP, BASE
extension STATION FAULTY
FSM)_x000D_ (FCM or all
operational)_x000D_
_x000D_
not mapped to any cellFAULTYand all FSPs in Unit
BTSstatus
are in "Out of 7654
7651 CELL OPERATION
BASE
FSP's)_x000D_ STATION OPERATION DEGRADED (FR (the cell
DEGRADED
_x000D_
7650
7653
7651 BASE
CELL FAULTY
BASE STATION
STATION(the faulty (FCM
OPERATION ismapped
FSP DEGRADED to (the
the faulty _x000D_
7650
can
(FSP) BASE
still operate STATION
because FAULTY
there (FCM
are - Unit status in
enough
faulty)_x000D_
7651 7651 BASE STATION OPERATION DEGRADED
FSP
7651 isBASE
order",
BASEnot STATION
FTMmapped
cell)._x000D_ STATION
OPERATION
or all FSPs)_x000D_
to any cell and atDEGRADED
OPERATION least one other
DEGRADED
(TheFSP
(the
faulty
faulty is 7652
"Out
7650of BASE
available
BASE
(FSP)_x000D_ andSTATION
order", needed
FTM orresources:
all FSPs)(FCM
FAULTY both-Tx (FSM
Unitand FAN,
Rx)) in
status
FSP
7651 isBASE
_x000D_ not mapped
operational)_x000D_ STATION to any cell and at
DEGRADED least one other FSP
( FSP)_x000D_ is external
7651 BASE ALD, FR)_x000D_
STATION
"Out of order", FTM or all FSPs) DEGRADED (extended FCM,
FSP isCELLnot mapped
operational)_x000D_
7653 FAULTY to(FR,(the
any cellcell andcannot
at least one other
operate FSP is
because _x000D_
FSP)
Flexi
7653 Zone
CELLMicro
operational)_x000D_FAULTY FDD, FlexiFSP
(faulty Zone is Micro
mapped TDD:_x000D_
to the 7651 BASE STATION DEGRADED (extended FCM,
_x000D_
not
7650 enough
BASE
cell)._x000D_ available
STATION and needed resources: Tx or
FAULTY_x000D_ 7653
7652 CELL FAULTY
FSP) BASE STATION(FR, FF (The cell cannot- Unit
NOTIFICATION(FCM
7653
7652 CELL
BASE FAULTY (faulty FSP is mapped toFAN, the cell).
BASE STATION
Rx))_x000D_
_x000D_
7652 STATION NOTIFICATION
NOTIFICATION (FSM (FCM/FCT)_x000D_ external operate
status in because
"Working") there
7652 BASE STATION NOTIFICATION are not enough (FCM/FCT)
NOTIFICATION(FCM available
- Unit
ALD)_x000D_
7654
_x000D_
7655 CELL
CELLFDD, OPERATION
(FR)_x000D_ (FR, (the cell can still and
7653 needed
CELL
statusCELL
7655 resources:
FAULTY
in "Working") (FR,
NOTIFICATION (FR) Tx FFor Rx);
(the MHA,
cell TILT, FA
cannot
Flexi BTS
_x000D_ Flexi BTS TDD:_x000D_ (but
operate
Flexi
_x000D_
7651 Zone
BASE
because
Micro
STATION
still have
FDD, Flexienough
OPERATIONZone available
Micro and needed
TDD:_x000D_
DEGRADED 7653the
operateCELL cell
becauseis already
FAULTY not (FR, faulty
enough FF because
available
(the ofand
other
cell cannot needed
resources:
7653
7650 BASEboth
CELL FAULTY Tx and
STATION (FR
(Cell (cell
Rx))
cannot
FAULTY cannot operate
operate because
because of not
of not faults))_x000D_
resources:
7653 CELL Tx or
FAULTY Rx)) (Cell cannot
operate because not enough available and needed operate because
(FCM/FCT)_x000D_
enough available and needed resources: Tx or Rx)_x000D_ Rx); MHA, _x000D_
7654
of notCELL
enough OPERATION
available DEGRADED (FR, FF (the
7654 CELL OPERATION DEGRADED resources: Tx or Rx)) and needed resources: Tx
TILT, (but
7654 CELL cell already faulty
OPERATION because of(FR)_x000D_
DEGRADED othercan still operate
(Cell 7654
cell
or CELL
can still
Rx)_x000D_ OPERATION
operate because DEGRADED
7654 CELL OPERATION DEGRADED (FR, FF (the still have (FR,
enough FF (The
_x000D_
faults))_x000D_ cell
because
Flexi Zone
it still has enough available and needed resources: cell can
available
7654 CELL
can still
and
still operate
neededbecause
OPERATION
operate resources:
because itstill
DEGRADED still hasTx
both
have enough
andcan
(Cell
enough Rx))
still
_x000D_
both Tx andMicro FDD, Flexi Zone Micro TDD:_x000D_
Rx)_x000D_ available
operate and
and needed
availablebecause it stillresources:
needed has enough
resources: both Tx
Tx and
available
both andandRx),
Rx))
7655
Flexi BTS FDD, Flexi(faulty
7652 CELL
BASE FAULTY
STATION FSP is mapped
NOTIFICATION
BTS TDD:_x000D_ (Radioto Module
the is not MHA,
needed TILT,
FlexiBTS: FA)
cell)._x000D_
commissioned)
7650 BASE STATION FAULTY (1.FSM, 2.FT 3.The faulty 7652 BASE STATION NOTIFICATION (Radio
Flexi
_x000D_BTS FDD, Flexi BTS TDD:_x000D_ 7650
Module BASEis notSTATION
commissioned)FAULTY (FTM, all FSP)
FSP
7650 isBASEnot mapped
STATION to any cell and all FSPs in faulty
BTS are 7650 BASE STATION FAULTY (FT, ifDEGRADED all FSPs are
7654
7650
faulty) CELL
BASE
_x000D_ STATION FAULTY
OPERATION DEGRADED
FAULTY (1.FTM,
(1.FTM,(FR, 2.The
2.The (cell canFSP
faulty still is
FSP is 7651
7650
faulty)
BASE
BASE STATION OPERATION
STATION FAULTY (all FSPs faulty,
not mapped
operate
not mapped becauseto any it cell
still and
has
to any cellOPERATION all
enoughFSPs in BTS
available
and all FSPsDEGRADED are
and
in BTS are (the needed (FSP,
FCM) extension FCM)
7651 BASE
faulty))_x000D_ STATION faulty
(1.FSM. 7652 BASE STATION NOTIFICATION (FR, TX, RX,
resources:
faulty))_x000D_
FSP
2.FSP isBASEnot
is notboth
mapped Tx and
mapped toto Rx),
any
any MHA,
cell and TILT)
atDEGRADED
cell)_x000D_ least one other FSP is 7651
7651 BASE
BASE STATION
STATION OPERATION
OPERATION DEGRADED
DEGRADED (if
7651
STATION OPERATION DEGRADED (the
(the faulty
(1.FSM.
faulty FF when
(FSP) the unit is not commissioned)
operational)_x000D_
7654
FSP isCELLnot OPERATION
mapped to any DEGRADED
cell and at (FSP
least oneis mapped
other FSP to is a working FSP
7653 exists)
2.FSP
FSP
7651
7653
the is is
BASE
CELL
cell) notnot mapped
mapped
STATION
FAULTY to to any
any
OPERATION
(the
cell)_x000D_
cell
faulty and
FSP at least
DEGRADED
is one
mapped other
to the FSP
(1.FSM. is 7652 CELL
BASE FAULTY STATION(FR, FF (the cell cannot
NOTIFICATION (FR, TX, RX,
operational)_x000D_
7654 CELL
operational)_x000D_
2.FSP is not OPERATION
mapped to anyDEGRADED
cell)_x000D_ (FSP is mapped to operate
FF, LTX when the unit is not available and needed
because not enough
cell)_x000D_
7651
7652 BASE
BASE STATION
STATION OPERATION
(FR, (1.FSM.
the
7652
7654 cell)
_x000D_
2.FSP BASE
CELL
is not STATION
OPERATION
mapped NOTIFICATION
to anyDEGRADED
cell)_x000D_ (FSPwhen
(FR, when the
the unit
is mapped unitto is
is resources:
commissioned) Tx or Rx))
not
7651
not
the commissioned)_x000D_
BASE STATION OPERATION DEGRADED (1.FSM.
cell) 7654
7653 CELL
CELL OPERATION
FAULTY (FR, DEGRADED TX, RX, FF (Cell (FR,cannot
FF (the
Flexi
7654
7653 Zone
CELL
CELL Micro
is notFAULTY FDD,
OPERATION
mapped(1.FR, Flexi
any(theZone
DEGRADED cellMicro TDD:_x000D_
(FSP
cannot is mapped
operate to
2.FSP
7653
7650
7650
the CELL
BASE
BASE
cell) FAULTY
STATION
STATION
to
(1.FR,
FAULTY
FAULTY
cell)_x000D_
(the cell faulty
(the cannot
(Critical FSP
POST is notbecause
operate
test because
mapped cell
7650 can
operateBASE still operate
becauseSTATION because
not enough
FAULTY still
availablehave
(all FSPs enough
andin needed
the
there
7654
there
to any are
CELL
are
cell not
not
and enough
OPERATION
enough
all FSPs available
in DEGRADED
available
BTS and
and
are needed
needed(FSP resources:
is mappedTx
resources:
faulty)_x000D_ Txto or
or available
resources:
master FSM and
Tx orneeded
or Rx))
all FSPs resources:
in the BTS both
are Tx and Rx))
faulty)
failures)_x000D_
Flexi
Rx),
the BTS FDD,
2.FSP
cell) when Flexi
faulty BTSFSP TDD:_x000D_
is mapped to the cell)._x000D_ FlexiBTS:_x000D_
Rx),
7651
7651
7650 2.FSP
BASE
BASE when
STATION
STATION faulty FSP
OPERATION
OPERATION
FAULTY is mapped to
DEGRADED
DEGRADED
(the faulty the cell)._x000D_
FSP cell (the
not faulty
is (non-critical 7654
_x000D_CELL OPERATION DEGRADED (FR, TX, RX,
7654
Flexi
7654 CELL
BTS
CELL OPERATION
FDD, Flexi
OPERATION toBTS DEGRADED
TDD:_x000D_
DEGRADED (FR(the
(FR(the cell can
can still
stillis 7650
FF BASE
(Cell canSTATION
still operate FAULTY
because (FSM or all FSPs
FSP
POST
mappedis
operate
7650 BASE
not
testto mapped
failure)
any
because cell
STATION and
there
any
all
is
cell
FSPs
still
FAULTY
and
enoughin at
the least
BTS one
available
(FSM)_x000D_ are other
and
FSP
needed
7651
7650
are
BASE
BASE
alarming)
STATION
STATION OPERATION
FAULTY (allstill
FSPs have
DEGRADED enough
in the (at
operate because
operational)_x000D_ there are
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
faulty)_x000D_ still enough available and needed available
least
master one
7401 - 7426
FSM and
working
orneeded
all FSP)
(EAC1=7401,
FSPs resources:
in EAC2=7402
the BTS both
are Tx and Rx))
etc)
resources:
7650 BASE
resources:
7653 CELL both
both
FAULTY Tx
Tx and
STATION and(theRx))_x000D_
FAULTY
Rx))
faulty (The faulty
FSP DEGRADED
is FSP is not
mapped 7651 BASE STATION OPERATION DEGARDED (at
7651
7401
_x000D_
mapped BASE
- 7426to STATION
(EAC1=7401,
any cell and OPERATION
all EAC2=7402
FSPs in the etc) areto (the
BTS
the faulty faulty)_x000D_
7401 - 7426
least one (EAC1=7401,
working FSP) EAC2=7402 etc)
cell)._x000D_
FSP
7401is
Flexi Zone not mapped
faulty)_x000D_
- 7426 Micro FDD,
(EAC1=7401, to any
Flexicell
ZoneandMicro
EAC2=7402 at least one other FSP is
TDD:_x000D_
etc) _x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
operational)_x000D_
7650
OPERATION DEGRADED 7651 BASE STATION OPERATION DEGRADED (at
7401
7653 - 7426FAULTY(EAC1=7401, EAC2=7402 etc)to the (The faulty 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
FSP isCELL not mapped to(faulty FSP
any cell andis mapped
at least one other is least one working FSP)_x000D_
cell)._x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
operational)_x000D_ _x000D_
7401 - 7426 (EAC1=7401, EAC2=7402 etc)
_x000D_
7653
7401 CELL
- 7426FAULTY(EAC1=7401, (The faulty FSP is mapped
EAC2=7402 etc) to the 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
cell)_x000D_
7401
7650 -BASE
7426 STATION
(EAC1=7401, FAULTY EAC2=7402 etc) 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
_x000D_
7401 - 7426Micro
Flexi Zone (EAC1=7401,
FDD, FlexiEAC2=7402
Zone Microetc) TDD:_x000D_ 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7650
7401 BASE- 7426 STATION
(EAC1=7401, FAULTY_x000D_
EAC2=7402 etc) 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7401 - 7426 (EAC1=7401, EAC2=7402 etc) 7401 - 7426 (EAC1=7401, EAC2=7402 etc)
7650 BASE STATION FAULTY (1.FSM, 2.The faulty FSP is [FSM Rel2]:
not
Fleximapped
BTS FDD, to anyFlexi cellBTSandTDD:_x000D_
all FSPs in BTS are 7652
FAULTY (FCM out (FCM, when
of order,
faulty))_x000D_
7650 BASE STATION FAULTY (FCM out of order, FTM out of FTM out of order)_x000D_ unit status is working)
7651 BASE STATION OPERATION DEGRADED (the faulty 7651
order)_x000D_ 7651 BASE BASE STATION
STATION OPERATION
OPERATION DEGRADED DEGRADED
FSP
7650is
Flexi notFDD,
BTS
BASE mapped
STATIONFlexi toBTS
any
FAULTY cell and
(theatfaulty
TDD:_x000D_ leastFSP one isother FSP is (FSP)
not mapped (Depends
(FSP out ofonorder/degraded)_x000D_
<x>)_x000D_
operational)_x000D_
(Depends
to anyBTS
Flexi on
and<x>)_x000D_
cell FDD, all FSPs
Flexi BTS in BTS are faulty)_x000D_
TDD:_x000D_ 7650
7653 BASE
7650 CELL FAULTY
BASE STATION
STATION(FR FAULTY
or FF out
FAULTY (all
(all FSPs,
(FCM)_x000D_
of order
FSPs FCM,
are (cell
faulty)
7652
7650
7651
7650 BASE
BASE STATION
FAULTY
OPERATION
FAULTY (1.
(theFSM. (FR,
DEGRADED
faulty 2.FSP when
The is the
faulty
(The
not unit
FSP
faulty
mapped isis when
7651
cannot unit
BASE status
operate STATIONis out
because of order)
OPERATION
of not enough DEGRADED
available
Flexi
not BTS FDD,
mapped to anyFlexi cellBTSand TDD:_x000D_
all and
FSPs inleast
the oneBTSother are FSP is (FSP, OptIF STATION
used for RF-sharing)_x000D_
FSP
to any is cell
FDD:_x000D_not and
mapped all FSPs to any in cell
BTS are at
faulty)_x000D_ and needed
7651 BASE resources: Tx or Rx))_x000D_
OPERATION DEGRADED
7653 CELL
faulty)_x000D_
operational)_x000D_
7651 BASE FAULTY
STATION (1.FR,
OPERATION(the cell cannot
DEGRADED operate (the because
faulty [FSM
7653
7654
(FSP) Rel3]:
CELL
CELL FAULTY
OPERATION (OptIF connected to
DEGRADED FR: The
(MHA, RET;
7651
there
7651 BASE
are
BASE not STATION
enough
STATION OPERATION
available
OPERATION and DEGRADED
needed
DEGRADED resources:(When
(FSP, Tx no or
OptIF 7652
cell BASE
cannot STATION
operate NOTIFICATION
because of not (FCT
enough when
7652
FSP
Flexi
other BASE
is not
BTS STATION
mapped
FDD, clock
reference to
Flexi BTS NOTIFICATION
any
sources cell and
TDD:_x000D_
are at (1.uncommissioned
least one
available)._x000D_ other FSP is FR or FF out of order (cell can still operate because
Rx),
used
FR, 2.FSP
2.for
MHA when faulty
RF-sharing,)_x000D_
or RET FSP for
working is mapped
other to absolute
WhenBTS)_x000D_ the cell)._x000D_ unitstillstatus
available has and is working)
needed resources: Tx or Rx)_x000D_
operational)_x000D_
7650
7652
7654
7651
BASE
BASE
CELL
BASE
STATION
STATION
OPERATION
STATION
FAULTY:
NOTIFICATION
DEGRADED
OPERATION
the
(When
(FR(the
DEGRADED there
cell
(The
OCXO
is at
can least it7654
still
faulty 7651 BASE
CELL
enough
STATION
OPERATION
OPERATION
DEGRADED
resources:
DEGRADED
(OptIF
7653
7652 CELL
BASE
adjustment
one more FAULTY
STATION
limit
working value (FR(min
reference out
NOTIFICATION
or of order
max)
clock has(cell
source (OptIF
beencannot operate
connected
available)._x000D_ to both Tx and Rx)_x000D_
operate
FSP
because
FR: the because
is not mapped
there
faulty
reached._x000D_ arethere
optical not are cell
tointeface
any
enough still enough
andnotatused
available
is available
leastandtoone and FSP
other
needed
provide needed (FSP)
is connected to FR: The cell can still operate because
_x000D_
resources: both
operational)_x000D_ Tx and Rx)) 7650
it still BASE
has STATION
enough FAULTY
available and(all FSPs,resources:
needed FCT,
resources:
7651 BASETx
transmission
TDD:_x000D_ or any
for
STATION Rx))_x000D_
cell)_x000D_
OPERATION DEGRADED:
7652
7653 BASE
CELL
Otherwise._x000D_ STATION
FAULTY NOTIFICATION
(the
(OptIF faulty FSP
connected is (1.uncommisioned
mapped
to FR: Theto the
cell cannot when
both unit
Tx andstatus is
Rx)_x000D_out of order)
7650
FR. BASE STATION
2.optical inteface FAULTY (Holdover is not possible
cell)._x000D_
operate
_x000D_
because because
of therethat
insufficient areisnot
data
notenough
or
used toavailable
phase error
provide transmission
and needed
in holdover
for
7654 any
resources:
Flexi cell)_x000D_
CELL
Zone TxOPERATION
Micro or Rx)_x000D_
FDD, DEGRADED
Flexi Zone Micro (FR out
TDD:_x000D_ of order (the
exceeds
7653 CELL 3 us)_x000D_
FAULTY (OptIF connected to FR: The cell cannot 7652 BASE STATION NOTIFICATION
cell
7653
7651
7652
7651 can
CELL
BASE
BASEstill operate
FAULTY
STATION
STATION because
(the faulty
OPERATION
NOTIFICATION
OPERATION there
FSP are
is still
mapped
DEGRADED enough
(Uncommissioned
DEGRADED to theavailable
(Holdover
operate
and needed
cell)._x000D_
source because
or Antenna there
resources: Line are
both
with not enough
Tx and
LNA available
Rx), MHA, for other
commissioned and needed (Uncommissioned source ortuning
Antenna Line with LNA
is possible)_x000D_
Flexi BTS
resources: FDD,
Tx orFlexi BTS
Rx)_x000D_ TDD:_x000D_ 7653 CELL FAULTY(When is not ongoing -
RET)_x000D_
7654
7652
7653 CELL
BTS)_x000D_
BASE
CELL OPERATION
STATION
FAULTY (No DEGRADED
NOTIFICATION
VSWR Threshold (OptIF
(When Tuningconnected
there is
mode at to
least
is commissioned
fault 1810 is not for other
present; BTS)_x000D_
the cell cannot operate
7653
7652The
_x000D_
FR: CELL
BASEcell FAULTY
STATION
can still (The
operate faulty
NOTIFICATION FSP
because is mapped
(fault sourceto theis RF 7654 CELL CELL OPERATION
OPERATION DEGRADED DEGRADED (Otherwise)
(when tuning
7654
one
active, CELL
more OPERATION
working
mandatory
cell)._x000D_
uncommissioned reference
resources DEGRADED
resource)_x000D_ clock
for cellit(Otherwise,
thesource still
are has enough
lost)_x000D_ for
available)._x000D_ 7654
because
is not CELL of not-enough
ongoing fault (All
1810available
is not and needed
present)
Flexi
available
using
7653
_x000D_
7654 Zone
RP1
CELL
CELL Micro
and needed
protocol
FAULTY
OPERATION FDD, (AllFlexi
resources:
only)_x000D_
RX Zone
CHANNELs
DEGRADED Micro
both Tx TDD:_x000D_
(No and
used VSWR Rx)_x000D_
by the cell
Threshold are 7653 FAULTY LNAs faulty within the cell)
7654
_x000D_
7650
_x000D_
7653 CELL
BASE
CELL
affected)_x000D_ OPERATION
STATION
FAULTY DEGRADED
FAULTY
(Otherwise, for RF (OptIF
using connected
IR protocol to resources:
7653 CELLTx or Rx)_x000D_
FAULTY (If cell is already faulty)
Flexi
Tuning
7653
FR:
7655 Zone
CELL
The
CELLcellMicro
mode FAULTY
can FDD,
is active,
still
NOTIFICATION (theFlexi
the
operatecell Zone
cell canMicro
cannot
because still
remain TDD:_x000D_
itoperate
still because
operational
has enough it _x000D_
Flexi
only)
_x000D_
7651
has
because Zone
BASE
enough Micro
there STATION
required
is FDD,
not Flexi (VSWR
OPERATION
resources
enough Zone
available
Threshold
Micro
available)_x000D_
RX and/or
Tuning
(When
TX
mode
no
7655
7654
7654
CELL
CELL
CELL
NOTIFICATION
OPERATION
OPERATION
(when tuning isleast
DEGRADED
DEGRADED (At
ongoing
(When one
available
is active.
7653
7650
7654 CELL
BASE
CELL and
Reportedneeded
FAULTY
STATION
OPERATION (inresources:
toward case
FAULTY local
DEGRADEDcell both
BTS
cannot Tx
Site and
Manager
remain Rx)_x000D_
(At leastTuning operational
one RXmode LNA - fault 1810
working iswithin the cell) 1810 is not present; the
other
7655 reference
CELL
resources)_x000D_
_x000D_
only)_x000D_
because there isclock
NOTIFICATION
notthe sources
enough are available)._x000D_
(VSWR Threshold tuning
present) is not ongoing - fault
CHANNEL
7654
7652
is
_x000D_ CELL
BASE
active. used
OPERATION
STATION
Reported by cell isavailable
DEGRADED
NOTIFICATION
toward local notBTS RX
affected)_x000D_
(TILT
(When
Site
and/or
failure
Manager there
TXaffects
is at least 7654can
cell CELLstill OPERATION
operate because DEGRADED
it still has (TILT
enough failure
Flexi
_x000D_
antenna Zone
resources)_x000D_
_x000D_ MicroofFDD,
carrier cellFlexi
areferencewithin Zone same Micro TDD:_x000D_
BTS)_x000D_ 7652
affects BASE
antenna STATION NOTIFICATION
carrierresources:
of a cell within (At
same least
BTS) one
one
7654
7650
7654
_x000D_more
only)_x000D_
CELL
BASE
CELL working
OPERATION
STATION
OPERATION clock
DEGRADED
FAULTY_x000D_
DEGRADED (no source (the
(TILTavailable).
cell
(Otherwise) can
failure still
affects available
7654 CELL and needed
OPERATION DEGRADED both Tx and
(TILT failure
7652
7652
remain
antenna BASE
BASE STATION
STATION
operational
carrier of abecauseNOTIFICATION
NOTIFICATION
cell within it still
same (fault
(fault
hasBTS)_x000D_
enough source
impact
source on
availableiscells
is RXto affects LNA
7652
Rx)_x000D_which
BASE is
antenna not
STATION used by
carrier of a any
NOTIFICATION
cell within same (no impact
7654
within CELL
uncommissioned
the sameOPERATION resource)
BTS, for DEGRADED
example, TILT(no (in
(TILTcase
serves regardless
failure
for affects
antennas 7654
cell
on isCELL
cells faulty)
withinOPERATION
same BTS, DEGRADED (TILTBTS)
e.g. TILT connected failure
in
uncommissioned
and/or
7652
detected
antenna TX
BASE issue
carrier cell
of resource)_x000D_
resources)_x000D_
STATION a is NOTIFICATION
still
cell having
within enough
same impact
available
BTS)_x000D_ on
RX cells
and / _x000D_
7652
affects BASE
antenna STATION
carrier NOTIFICATION
of a cell within (no
same impact
BTS)
used
7654 by
CELLdifferent
OPERATION BTS/RAT; uncommissioned
DEGRADED (TILT source)
failure affects external
7654
7655 CELL
CELLmode, impact
OPERATION
NOTIFICATION on cells
DEGRADED
(Whenfrom other
TILT tuning (TILTBTS/RAT
failure
_x000D_
within
or
7652
antenna
the same
TX BASE
resources STATION
carrier
BTS,
ofso
for
aitcell
can example,
remain
NOTIFICATION
within same
TILT(no serves
operational)_x000D_
BTS)_x000D_impact foronantennas
cells on
7652 cells
affectsBASE
served
within
by TILT
antenna
same BTS,
STATION
is
e.g.
NOTIFICATION
unknown;
carrier of a uncommissioned
cell within (no is
connected
same impact
BTS)
in
Flexi
7652
used
7654
_x000D_
within Zone
BASE
by
CELL
the Micro
same STATION
different
OPERATION FDD,
BTS/RAT;
BTS, Flexi
for Zone
NOTIFICATION
DEGRADED
example, Micro
uncommissioned
TILT TDD:_x000D_
(fault
(TILT
serves source
source)
failure
for is
affects
antennas ongoing
external
7654
on cells CELL- fault
mode,
within 1810
impact
OPERATION
same is present.
on
BTS, cells
DEGRADED
e.g. Reported
from
TILT other
(TILT
connectedtowards
BTS/RAT
failure
in
7652
7654 BASE
CELL
uncommissioned
antenna STATION
OPERATION
carrier unit)
ofBTS/RAT;
a cell NOTIFICATION
DEGRADED
within (no
(cell
same BTS)_x000D_ impact
can onoperate
still cells source)
7652
BTS
served
affects BASE
Siteby STATION
Manager
TILT
antenna is NOTIFICATION
only)_x000D_
unknown;
carrier uncommissioned
of acells
cell (no impact
withinother
same BTS)
used
7652
within by
BASEdifferent
theitsame STATIONBTS, for uncommissioned
NOTIFICATION
example, TILT (in
(ALD case
serves whichfault
source) is source
serving
forresources:
antennas is external
7652
on cells BASEmode,
within impact
STATION
same BTS, on
NOTIFICATION from BTS/RAT
(external
e.g. TILT connected in
because
7652 BASE
uncomissioned
for different still
BTS; has
STATION
unit) enough
uncommissioned available
NOTIFICATION and (no needed
source)_x000D_impact on cells _x000D_
source)
7652
served
AISG BASE
by
MHA, TILTSTATION
is
external NOTIFICATION
unknown;
TILT) uncommissioned (no impact
used
7652
both
within by
BASE
Txthedifferent
and
same STATION BTS/RAT;
Rx)_x000D_ uncommissioned
NOTIFICATION (ALD
BTS, for example, TILT serves for antennas on source)
which is serving external
7652 cells BASEmode,
within impact
STATION
same BTS, on cells
NOTIFICATION from other BTS/RAT
(fault source
e.g. TILT connected in
_x000D_
for different BTS; uncommissioned source)_x000D_ source)
served by TILT is unknown; uncommissioned
7653
used
7650
7654 CELL
by
BASE FAULTY
different
STATION (cell
BTS/RAT; cannot
FAULTY operate
uncommissioned
(FTM/FCT)_x000D_
CELL OPERATION DEGRADED (RX,TX, TILT, MHA) 7654 because source) there are is uncommissioned
external
7650 BASEmode, impact
STATION or external
on cells
FAULTY
CELL OPERATION DEGRADED (RX,TX, unit)
from other
(FTM/FCT)_x000D_BTS/RAT
_x000D_
not
7653 enough
CELL FAULTYavailable(FR, and FF needed(The resources:
cell cannotTx or Rx, but
operate source)
served
7653 MHA) by TILT
CELL FAULTYis unknown;
(FR, FFuncommissioned
(cell cannot operate
7654 CELL OPERATION DEGRADED (MHA, TILT) TILT,
other cell(s)
because there canare provide service)_x000D_
not enough available and needed source) of not enough available and needed
because
7650 BASETx
resources: STATION
or Rx))_x000D_FAULTY (no cell can provide service) resources: Tx or Rx))_x000D_
7654 CELL OPERATION DEGRADED (FR, FF (The cell can 7654 CELL OPERATION DEGRADED (FR, FF (cell
still
7652 operate
BASE because
STATIONitNOTIFICATION
has enough available (ALD which and needed
is serving can still operate because it still has enough
resources:
for different both Tx and Rx)) available and needed resources: both Tx and Rx))
7652 BASE BTS, STATION uncommissioned
NOTIFICATION resource)_x000D_
(ALD which is serving 7652 BASE STATION NOTIFICATION (The
_x000D_
for different BTS, uncommissioned resource)_x000D_ alarming MHA serves another BTS) (external
7652
7654 BASE STATION
CELL OPERATION NOTIFICATION
DEGRADED (ALD is working for
(otherwise) 7652 BASE STATION NOTIFICATION
_x000D_
different BTS)_x000D_ ALD)
7652
CELL OPERATION DEGRADED (ALD is working for
(otherwise)_x000D_ 7652
CELL OPERATION DEGRADED (external (The
_x000D_
7652
CELL NOTIFICATION (Flexi Filter, AISG MHA, RET) (ALD is working for alarming
7652 BASE MHA serves
STATION this BTS)
NOTIFICATION
7655 CELL NOTIFICATION (Flexi Filter, COMB, (external
_x000D_
7652
7655 BASE
NOTIFICATION (Flexi Filter, (ALD
AISG is MHA,
working RET) for AISG
7652
7655 BASE MHA, NOTIFICATION
CELL TILT)
STATION NOTIFICATION (Flexi Filter,(external
COMB,
_x000D_
7655 CELL NOTIFICATION (Flexi Filter, AISG MHA, RET) AISG MHA, TILT)
7655 CELL NOTIFICATION (Flexi Filter, COMB,
_x000D_
7655 CELL NOTIFICATION (Flexi Filter, AISG MHA, RET) AISG
7655 CELL MHA, NOTIFICATION
TILT) (Flexi Filter, COMB,
AISG MHA, TILT)
FDD:_x000D_
7652 BASE STATION NOTIFICATION (if other clock is 7652 BASE STATION NOTIFICATION (if FTM clock
7652 BASE STATION NOTIFICATION (if other valid
available)_x000D_ is available)_x000D_
Flexi BTS source
reference FDD, Flexi BTS TDD:_x000D_
is available)_x000D_ 7652 BASE STATION NOTIFICATION
7651
7652 BASE
BASE STATION
STATION OPERATION
(Uncommissioned (other 7651 BASE STATION
(Uncommissioned OPERATION DEGRADED
source)
7651
Flexi
case) BASE
BTS STATION
FDD, Flexi OPERATION
BTS TDD:_x000D_ DEGRADED (other 7652
(other BASE
cases) STATION NOTIFICATION
source)_x000D_
cases)_x000D_
7652 BASE STATION NOTIFICATION (Uncommissioned 7653 CELL FAULTY
(Uncommissioned (cell cannot operate because
source)
Flexi
7653 BTS
CELLFDD, FAULTY Flexi(cell
BTScannot
TDD:_x000D_
operate because of not 7652
of notBASE
enough STATION
available NOTIFICATION
_x000D_
source)_x000D_
7652 BASE STATION NOTIFICATION (Uncommissioned 7653 CELL
(UncommissionedFAULTY (celland
source)
needed
cannot resources:
operate because Tx
enough
7652 BASE
TDD:_x000D_
7653 available
STATION and needed resources:
NOTIFICATION
CELL FAULTY (cell cannot operate Tx or Rx)_x000D_
(Uncommissioned
because of not or Rx)
of not enough available and needed resources: Tx
source)_x000D_
7654 CELL OPERATION DEGRADED (cell can stillofoperate 7654
source)_x000D_
7650
enough BASE
7653 CELL
7654 STATION
available
CELL OPERATION and FAULTY
needed
FAULTY (Cell DEGRADED (Holdover
resources:
cannot operate not
Tx orpossible
because Rx)_x000D_
(Otherwise)_x000D_ not or Rx)CELL
7653
7654 CELL OPERATION
(Uncommissioned
CELL FAULTY
OPERATION (Cell DEGRADED
source) cannot operate
DEGRADED
(cell can still
because
(Otherwise)
because
7653
because
7654
enough CELL
CELL itofstill hasand
FAULTY
insufficient
OPERATION
available enough
(The data available
cell
orcannot
DEGRADED
needed phase
resources:and
operate
error
(cell needed
Txincan resources:
because
holdover
or still of
operate
Rx)_x000D_ operate
7653
7654
of not because
CELL
CELL
enough FAULTYit still
OPERATION
available has
(Cell enough
cannot
DEGRADED
and needed available
operate
(cell
resources: and
because
can still
Tx
_x000D_
7653
both
there CELL
Tx
are and FAULTY
Rx)_x000D_
enough (Cell
available cannot
and operate
needed because
resources: of
Tx not
or 7653
needed
of not CELL FAULTY
resources:
enough (Cell
both
available Tx
andcannot
and
needed operate
Rx) because
resources: Tx
exceeds
because
_x000D_
Flexi
enough Zone 3it still
us)_x000D_
Micro
available has FDD,enough
and Flexi
neededavailable
Zone andTDD:_x000D_
Micro
resources: needed resources:
Tx or Rx)_x000D_ operate
or
of Rx)
not because
enough it still
available has enough
and needed available and
resources: Tx
_x000D_
Rx)_x000D_
7654
7651
both
7654 CELL
BASE
Tx
CELLand OPERATION
STATION
Rx)_x000D_
OPERATION DEGRADED
OPERATION
DEGRADED -(Cell
DEGRADED dedicated
can radio
(Holdover
still operate or Rx)CELL
7653
needed FAULTY
resources: - shared
both Tx andradio
Rx)resources,
7654
_x000D_
Flexi
7654 CELL
Zone
CELL OPERATION
Micro
OPERATIONFDD, DEGRADED_x000D_
Flexi Zone
DEGRADED Micro TDD:_x000D_
(The cell can still or Rx)
7654
resources
possible)_x000D_
_x000D_
because
Flexi
7654 BTS
CELL it or
FDD, shared
still hasFlexi
OPERATION
radio
enough
BTS resources,
available
TDD:_x000D_
DEGRADED
where
and (Cell
LTE
needed
can
is master
resources:
still operate 7654 CELL
where
7652 LTE is
CELL
BASE OPERATION
slave SM;
OPERATION
STATION DEGRADED
cell cannot operate
DEGRADED
NOTIFICATION (Cell
(Cell cancan still
still
7650
operate
SM;
7652
Flexi
both BASE
cell
BASE
Zonebecause
can STATION
still
STATION
Micro it still
operate
FDD, FAULTY
has enough
because
NOTIFICATION
Flexi Zone (no cell
cell
Micro can
available
has
(if provide
and
enough
other
TDD:_x000D_ needed
valid available operate
because because
of not it
enoughstill has enough
available available
required Tx and
Flexi Tx
becauseBTS and
it FDD,
service)_x000D_
resources:
Rx)
still
both has_x000D_
Flexi
Tx enough
BTS available and
Rx)TDD:_x000D_
(Uncommissioned
needed resources: operate
7654
7652 because
(Uncommissioned
CELL
BASE it
OPERATION
STATION still
source)has enough
DEGRADED
(Cell and
can still
required
reference
7650
_x000D_BASE Tx
source)_x000D_
both
7652 Tx
BASEand STATION is and
resources_x000D_
source
Rx)_x000D_
STATION available)_x000D_
FAULTY
NOTIFICATION (no cell (Uncommissioned
can provide needed
resources
needed
7653
operate
resources:
resources:
CELL FAULTY
because
(Uncommissioned it
both
both
(cell
still
source)
Tx
Tx
has
and
and Rx)
cannot
enough Rx)
operate because
available and
7653
_x000D_CELL
BASE FAULTY
service)_x000D_
7652
7653 CELL STATION(cell
FAULTY (other
(The cellcannot
cannot
NOTIFICATION
cell can provide
operate service)_x000D_
because
(Uncommissioned
operate becauseof not there 7654
7653
of notCELL
enough OPERATION
FAULTY
available DEGRADED
(cell cannot operate- dedicated
because
_x000D_
source)_x000D_
enough available and needed resources: Tx or Rx)_x000D_ needed
7654
radio
of not resources:
CELL
resources
enough OPERATION
or both and
shared
available Tx
and
needed
and
DEGRADED
radio
neededRx) resources:
(Otherwise)
resources, where
resources:
Tx
Tx
7653
source)
are
Flexi
7652 Zone
CELL
not
BTSenough
BASE Micro
FAULTY
FDD, FDD,
available
Flexi BTSFlexi
(other
STATION NOTIFICATION and Zone
cell can
needed
TDD:_x000D_ Micro
provide TDD:_x000D_
resources: service)_x000D_
Tx or or Rx)BASE STATION NOTIFICATION
7652
7654
7654 CELL
CELL
Rx)_x000D_
7652 BASE
OPERATION
OPERATION
STATION DEGRADED (Uncommissioned
DEGRADED
NOTIFICATION
(Otherwise)_x000D_
(cell
(if canvalid
other
(Uncommissioned still operate LTE
or is
Rx)
7654 master
CELL
(Uncommissioned SM;
OPERATIONcell
source)can still operate because
DEGRADED (cell can still cell
source)
_x000D_
Flexi
becauseBTS it FDD,
still hasFlexi BTS
enough TDD:_x000D_
available and needed resources: 7652
has
7654 BASE
enough
CELL STATION
available
required
DEGRADEDTx resources
(cell can still
reference
7654 CELL
source)_x000D_
Flexi
7652 Zone
BASE source
OPERATION
Micro
STATION is available)_x000D_
FDD,BTS DEGRADED
Flexi (The
Zone Micro(Uncommissioned
NOTIFICATION cell can
TDD:_x000D_ still operate
7653 because
CELL
(UncommissionedFAULTYitsource)
still has
(cell enough
cannot available
operate and
because
both
Flexi
7651
7653 Tx
operateBTS
BASE
CELLand FDD,
because Rx)_x000D_
STATION
FAULTY Flexi
it still
(cellhas TDD:_x000D_
OPERATION
enough
cannot DEGRADED
available
operate and
because (other
needed
of not operate
7652
notBASE
needed
of because
resources:
enough it still
STATION both
available has
Tx
and enough
NOTIFICATION
and
neededRx) available
resources: and
Tx
7654
7652 CELL
source)_x000D_
BASE OPERATION
STATION DEGRADED_x000D_
NOTIFICATION (Uncommissioned 7653
needed CELL FAULTY
resources:
(Uncommissioned (cell
both
source) cannot
Tx and operate
Rx) because
cases)
resources:
enough
7652
7653 BASE
CELL both
available
STATION
FAULTY Txandand
(cell Rx)_x000D_
needed
cannot resources:
NOTIFICATION operate Tx or Rx)_x000D_
(Uncommissioned
because of not or Rx)
7652
of BASE
notCELL
enough STATION
source)_x000D_
_x000D_
7654 CELL
source)_x000D_ OPERATION DEGRADED (cell can still operate 7653
7654 CELL
(UncommissionedFAULTY
OPERATION (celland
source)
needed
cannot
DEGRADED
resources:
operate because
(cell
Tx
can still
enough
7652
7653 BASE
CELLavailable
STATION
FAULTY and (Theneeded
cell resources:
NOTIFICATION
cannot operate Tx or
(Uncommissioned Rx)_x000D_
because there or
of Rx)
7652 BASE
not enough STATION
andenough
neededavailable
resources: Tx
Flexi
because
_x000D_
7654 Zone
CELL
it still has
OPERATIONFDD,enough Flexi Zone
available
DEGRADED Micro
and TDD:_x000D_
(cellneeded
can stillresources:
operate operate
7654 because
CELL
(Uncommissioned itsource)
OPERATION still hasDEGRADED (cell can andstill
are
7652
both
7654 not
Tx enough
BASE
CELLand available
STATION
Rx)_x000D_
NOTIFICATION resources:
(Uncommissioned
(The Tx
cell can or
still or Rx)
7652
needed BASE STATION
resources: NOTIFICATION
bothhas Tx and Rx) available
because
7654 CELL
Rx)_x000D_ it still has enoughDEGRADED
OPERATION available and
DEGRADED (Otherwise)_x000D_
needed
(Otherwise)_x000D_resources: 7654
operate
7654
7654
CELL
CELL OPERATION
because it
OPERATION still DEGRADED
enough
DEGRADED (Otherwise)
and
(Otherwise)
source)_x000D_
operate
_x000D_
Flexi Tx
both BTS because
and FDD, it stillBTS
Flexi
Rx)_x000D_ hasTDD:_x000D_
enough available and needed 7652 CELL
(Uncommissioned
needed BASE OPERATION
STATION
resources:
source)
both
DEGRADED (cell can still
NOTIFICATION
Tx enough
and
7654
7653 CELL
resources:
Flexi
7652 Zone
BASE OPERATION
FAULTY
both
Micro
STATIONTx
FDD, (during
and DEGRADED
FR
Rx)_x000D_
Flexi Zone
NOTIFICATION startup (The cellcell
ifTDD:_x000D_
Micro(Uncommissioned can still
cannot operate operate
7653 because
CELL
(UncommissionedFAULTYitsource)
still has
(during RF Rx) available
startup if cell and
cannot
_x000D_
Flexi
operate
becauseBTS of FDD,
becausenot Flexi
it
enough BTS
still has TDD:_x000D_
enough
available and available
needed and needed
resources: Tx 7652
needed
operateBASE STATION
resources:
because of both
not NOTIFICATION
Tx and
enough Rx)
available and
7653
7654
Flexi
7652 CELL
source)_x000D_
Zone
BASE FAULTY
OPERATION
Micro
STATION FDD, (The cellZone
Flexi cannot
DEGRADED
NOTIFICATION operate
Micro (cell canbecause
TDD:_x000D_
(Uncommissioned there
still operate 7654 CELL OPERATION
(Uncommissioned source) DEGRADED (Otherwise)
resources:
or Rx)_x000D_
Flexi
are
7654 BTS
not
because enough
CELL both
FDD,
it still Tx
Flexiand
available
has
OPERATION BTS
enough Rx)_x000D_
TDD:_x000D_
and needed
available
DEGRADED resources:
and needed Tx
resources: needed
7652 resources:
BASE STATION Tx NOTIFICATION
or Rx)
7653
_x000D_
7654 CELL
source)_x000D_
CELL FAULTY
OPERATION (cell cannot
DEGRADED operate because
(during not
FR startup if 7654
DEGRADED (Otherwise)
7652
but
both
_x000D_
Flexi
enough
7654
BASE
other
Tx
BTS
CELLand STATION
cell(s)
FDD,
available can
Rx)_x000D_
Flexi
OPERATION
NOTIFICATION
provide
BTS
andbecause
needed service)_x000D_
TDD:_x000D_
resources:
DEGRADED
(Uncommissioned
Tx or Rx,
(Otherwise)_x000D_ but other 7652 CELL
BASE OPERATION
(UncommissionedSTATION source)
NOTIFICATION (during RF
Flexi
cell Zone
can still
source)_x000D_
7650
7653
Flexi BASE
CELL Micro
operate
STATION
FAULTY FDD, Flexi
FAULTY
(cell Zone
cannotit still
(no Micro
has
cell
operate in TDD:_x000D_
enough
BTS
because available
can ofprovide
not and startup
7653 if
CELL cell can
FAULTYstill operate
(during RFbecause
startup it
ifstill
cellhas
cannot
7652 Zone
7652
cell(s)
_x000D_
7650
needed
7653 can
BASE
BASE
CELL
Micro
provide
STATION
STATION
resources:
FAULTY
FDD,
both
Flexi Zone Micro(Uncommissioned
NOTIFICATION
service)_x000D_
NOTIFICATION
FAULTY
(duringTx and (no
Rx_x000D_
RFresources:
start-up can
TDD:_x000D_
cell (Uncommissioned
ifTx provide
the
(Uncommissioned
7652
enough BASE STATION
available
source)
and NOTIFICATION
needed resources: both
and Tx
service)
enough
7653 CELLavailable
source)_x000D_
7650 BASE and
FAULTY_x000D_
STATION needed
FAULTY (no cell can orcell
provideRx,cannot
but other operate
7653 because
CELL FAULTYof not
(cellenough
cannot available
operate because
Flexi
operate
7652
cell(s)
7653
Zone
source)_x000D_
service)_x000D_
7655 Cell
BASE
can
CELL
Micro
STATION
provide
FAULTY
FDD,
Notification
because there Flexi
(during
are Zone
not FR
NOTIFICATION
service)_x000D_
(The cell cannot
Micro
runtime)
enough TDD:_x000D_
available
(Uncommissioned
operate andservice)
because needed
there
(Uncommissioned
and Rx
needed
7652
of not resources:
BASE
enough STATION source)
Tx NOTIFICATION
available orand
Rx)needed resources: Tx
7654
_x000D_
7653 CELL
CELL
resources:
source)_x000D_ OPERATION
FAULTY
Tx or (The
Rx)_x000D_ DEGRADED_x000D_
cell cannot operate because there 7655
7654 Cell
CELL Notification
(UncommissionedOPERATION (during
source) RF runtime)
DEGRADED (during RF
7650
are
7652
7654 not enough
BASE
CELL available
STATION
OPERATION FAULTY
and
NOTIFICATION
DEGRADED (no
needed cell can
resources: provide
(Uncommissioned Tx
(Otherwise)_x000D_ service)
or or Rx)BASE
7652
OPERATION DEGRADED (Otherwise)
are
7654 not enough
CELL
Rx)_x000D_
source)_x000D_ available
DEGRADED resources:
(during RF Tx
(Otherwise)_x000D_ or
start-upRx, if startup
7654 if
CELL cell can still
OPERATION
7654 CELL OPERATION
(Uncommissioned operate because
source)DEGRADED (Otherwise)
DEGRADED it stillcan
(cell hasstill
but
the other
cell can cell(s)
7654 CELL FAULTY
7653 still can
operate
OPERATION provide service)
because
(Cell DEGRADED it
cannot operatestill has
(The enough available
cell canthere
because still is enough
operate
7653 available
because
CELL FAULTY and
it stillneeded
hascannot
(Cell resources:
enough both
available
operate Tx
and
because
and
not needed
operate
enoughbecause resources:
availableit stillandboth
has Tx and
enough
needed Rx)_x000D_
available
resources: and
Tx orneeded and Rx)
needed
there resources:
is not enoughboth Tx and
available and Rx)
needed
_x000D_
Rx)_x000D_ resources: Tx or Rx)
Flexi
_x000D_
7654 Zone
CELLMicro OPERATIONFDD, Flexi Zone Micro(Cell
can still operate 7654 CELL OPERATION DEGRADED (Cell can still
7650
becauseBASE
Flexi Zone still STATION
Micro FDD,
the cell has FAULTY
Flexi (no cell
Zoneavailable
enough can provide
Micro TDD:_x000D_
and needed operate because still the cell has enough available
service)_x000D_
7652
7650 BASE
BASEboth
resources: STATION
STATIONTx andNOTIFICATION
FAULTY
Rx) (no cell (Uncommissioned
can provide 7652 BASE STATION
and needed resources:NOTIFICATION
both Tx and Rx)
7653 CELL
BASE FAULTY
source)_x000D_
service)_x000D_
7652 STATION(other cell(s) can provide
NOTIFICATION (Uncommissioned (Uncommissioned
7652 BASE STATION source)
NOTIFICATION
service)_x000D_
7655
7653 CELL
CELL
source)_x000D_ NOTIFICATION
FAULTY (other (Otherwise)_x000D_
cell(s) can provide 7655 CELL NOTIFICATION
(Uncommissioned source) (Otherwise)
7652 BASE STATION NOTIFICATION (Uncommissioned 7652 BASE STATION NOTIFICATION
service)_x000D_
7653 CELL FAULTY (The cell cannot operate because there
source)_x000D_ 7653 CELL FAULTY
(Uncommissioned (Cell cannot operate because
source)
7652
are BASE
not enough STATION
available NOTIFICATION (Uncommissioned 7652 BASE STATION NOTIFICATION
7653 CELL
source)_x000D_ FAULTY (cell and
cannotneeded
operate resources:
becauseTx ofor not of not
7653 enough
CELL FAULTY
(Uncommissioned
available(celland
source)
needed
cannot resources:
operate because Tx
Rx)_x000D_
enough available and needed resources: Tx or Rx)_x000D_ or
of Rx)
notCELL
enough available and needed resources: Tx
7654
7654 CELL OPERATION DEGRADED (Otherwise_x000D_ 7654 OPERATION DEGRADED
DEGRADED (Otherwise
7654 CELL
7652 CELL OPERATION
BASE OPERATION
STATION NOTIFICATION DEGRADED (The
DEGRADED (Uncommissioned
(cell can cell still
canoperate
still 7654
or Rx)CELL
7652 BASE OPERATION
STATION NOTIFICATION (Cell can still
operate because it still has enough available
because it still has enough available and needed resources:
source)_x000D_ and needed operate because
7654 CELL OPERATION
(Uncommissioned it still has enough available
source)DEGRADED (cell can andstill
resources:
both Tx
7653 CELLandbothFAULTY Tx and
Rx)_x000D_ (The Rx)cell cannot operate because there needed
operate
7653 resources:
because
CELL FAULTY both
it still Tx and
hascannot
(Cell enough Rx) available
operate and
because
7653 CELL FAULTY
are not enough available and (The cell needed
cannot operate
resources: because
Tx or there 7653
notCELL
needed
of FAULTY
resources:
enough (Cell
both
available Txcannot
and and
needed operate
Rx) because
resources: Tx
are not
Rx)_x000D_
7653 enough available and needed
CELL FAULTY (The cell cannot operate because resources: Tx or there of
or not enough
Rx)CELL
7653 available
FAULTY (Celland needed
cannot resources:
operate because Tx
Rx)_x000D_
7654
are notCELL
enough OPERATION
available DEGRADED
and needed resources: (The cell can
Tx still
or or Rx)_x000D_
7654 CELL
of notCELL
enough OPERATION
available DEGRADED
and needed (Cell
resources: can still
Tx
7652
7654 BASE
CELL STATION
DEGRADED (the
(Thefaultycell SFP
can works
still 7653
7654 CELL FAULTY
OPERATION (Cell cannot
DEGRADED operate because
(Cell can still
operate
Rx)_x000D_
on opticalbecause
interface it still
that has
is enough
not used available
to provide and needed
transmission operate
or
not because
Rx)_x000D_
enough it
available still
andhas enough
needed available
resources: and
Tx or
operate
7652 BASE
resources:
7654 CELLbecause STATION
both Tx
OPERATION it still has
Rx) enough available
andNOTIFICATION
DEGRADED (the
(Thefaulty andcan
cell needed
optical
still operate
needed
7654 because
resources:
CELL it
OPERATION still has
both Tx enough
and Rx)
DEGRADED available and
(Cell can still
for any
resources:
interface cell)_x000D_
is both
not Tx
used andto Rx)_x000D_
provide transmission for any Rx)
needed resources: bothhas Tx enough
and Rx) available and
operate
7652
7653 BASE
CELLbecause STATION
FAULTY it still
(The has enough
cell cannot operate (The and
faulty needed
becauseoptical there operate because it still
7654 CELL OPERATION DEGRADED (Cell can still
7652 BASE
cell)_x000D_
resources: STATION
is both Tx and toNOTIFICATION
Rx)_x000D_ (the faulty SFP works needed
interface
are
7652
on
7654 not enough
BASE
optical
CELL
not used
available
STATION
interface
OPERATION
provide
and
NOTIFICATION
thatNOTIFICATION
isDEGRADED
transmission
needed resources:
not used to provide (the for any
faulty
(the faulty Tx or
optical
transmission
faulty optical #N/A resources:
operate because still both
have Txenough
and Rx)available and
7652 BASE
cell.)_x000D_
Rx)_x000D_
interface is STATION
not used toNOTIFICATION
provide transmission(the for any SFP works needed resources: both Tx and Rx)
for
7652
on
7653any
interface cell)
BASE
optical
CELL isinterface
used
STATION
FAULTY to provide
that
(The is transmission
not
cell used
cannot to (the
provide
operate forfaulty
any opticalthere
transmission
because
7654 CELL
cell)_x000D_
cell)_x000D_
interface OPERATION
is not used DEGRADED
to provide transmission (The cell can
for any still
for
are any
not
operate
7654 cell)
enough
CELLbecause available
OPERATION it still has and needed
enough
DEGRADED resources:
available
(the faultyand Tx or
needed
optical
cell)_x000D_
Rx.)_x000D_
resources:
interface
7654 CELL is both
usedTx to and
provideRx)_x000D_
transmission forfaulty any optical
7654 CELL OPERATION
cell)_x000D_ OPERATION DEGRADED DEGRADED (the (The cell can still
interface is used to
operate because provide
it still transmission
has enough available for anyand needed
cell)_x000D_
resources: both Tx and Rx.)_x000D_
7652 BASE STATION NOTIFICATION (the faulty optical
interface
7652 BASE is not used toNOTIFICATION
STATION provide transmission (1.FSM, for2. any FSP on
cell)_x000D_
FBB not mapped to any cell)_x000D_
7654
7655 CELL CELL OPERATION
(FSP on FBB (themappedfaulty optical to the
interface
7650
cell.) BASE is used
STATION to provide
FAULTY transmission
(FSP and for
FBB: anythe faulty FSP 7650 BASE STATION FAULTY (All FSPs in System
cell)_x000D_
is not BASE
7650 mapped to any cell
STATION FAULTY and all(1.FSM,FSPs in2.FBB: BTS are thefaulty).
faulty Module)_x000D_
7650 BASE STATION FAULTY - If all FSPs are
_x000D_
FSP is not mapped to any cell and all FSPs in BTS are _x000D_
faulty or FCT is faulty._x000D_
7651
7651 BASE
BASE STATION
STATION OPERATION
OPERATION DEGRADED
DEGRADED (1.FSM,
(FSP and 7651
faulty)_x000D_
2.FBB when FSP onisFBB is not mapped tocellanyand at least 7651 BASE BASE STATION
STATION OPERATION OPERATION DEGRADED DEGRADED - If
FBB:
7651 the
BASE faulty FSP
STATION not
OPERATIONmapped to any
DEGRADED (FBB: the (FSP)_x000D_
part of FSPs are faulty.
cell)._x000D_
one other
faulty
7654 FSPFSP
CELL
is mapped
isOPERATION
not operational). to any
DEGRADED
_x000D_
cell and (FSPat least on FBB one is other _x000D_
7653
FSP CELL FAULTY (1.FSP and FBB: the faulty FSP is 7653 CELL FAULTY (OptIf(cell cannot operate
7654isCELL
mapped
mapped
operational).
to
to the
the cell)
OPERATION _x000D_
cell. 2.OptIf: DEGRADED
thefaulty
cell cannot (the operate
faulty optical because because of not enough available and needed
7653
interface CELL is FAULTY
used (FBB:
to provide the
transmission FSP is mapped
for resources:
any to the
there
Flexi
cell). are
BTS not
FDD, enough
Flexi available
BTS and
TDD:_x000D_ needed Tx or resources:
7650 BASETx or Rx))_x000D_
STATION FAULTY (otherwise)
cell)_x000D_
Rx
7652 )._x000D_
BASE STATION NOTIFICATION (SSD firmware _x000D_
7650
7652 BASE
BASE STATION
STATION FAULTY NOTIFICATION (FSP: The (the faulty
faulty FSP
optical is not 7650 BASE STATION NOTIFICATION
7652 BASE STATION FAULTY (all FSPs (SSD
are faulty)
7654
mapped CELL
update)_x000D_ to OPERATION
any cell and allDEGRADED
FSPs in the (OptIf
BTS (the
are cell
faulty). can still 7654
firmware
7651 CELL
BASE OPERATION
update)
STATION DEGRADED
OPERATION (OptIf (cell
DEGRADED
interface
7650
operate
7650 BASE
BASE is not
because used
STATION
STATION it stilltoFAULTY
provide
has
FAULTY enough transmission
(FSP and FBB:
available
(otherwise)_x000D_ for
and any
The neededcell)
faulty 7650
can BASE
still operateSTATION because FAULTY (all FSPs
it still has enough are
_x000D_
FSP is not mapped to any cell and all FSPs in the BTS are (At least
faulty)_x000D_ one FSP is still operational)
resources:
_x000D_
7651 BASE
7651 both
BASE STATION Tx and
STATION OPERATION Rx))_x000D_
OPERATION DEGRADED DEGRADED (FSP: (1.FSM, The 7653 available and needed resources: both Tx and Rx))
faulty).
Flexi
2.FBB Zone_x000D_
when Micro
FSP FDD,
on FBB Flexi is Zone
not Micro
mapped TDD:_x000D_
to any 7651 CELL BASE FAULTYSTATION(OptIF OPERATION (Cell cannot operate
DEGRADED
faulty
7651
7651 FSP isSTATION
BASE
BASE not mapped
STATION to any cell DEGRADED
OPERATION
OPERATION and at least one
DEGRADED (1.FSM,
(FSP other
and because (At least one not enough
FSP is still available and needed
operational)_x000D_
7650
FSP
2.FBB isBASE
cell)._x000D_when STATION
operational).
FSP on FBBFAULTY
_x000D_ is not mapped to any resources: Tx or Rx))
FBB:
7651
7654 The
BASE
CELL faultySTATION
OPERATIONFSP isOPERATION notDEGRADED
mapped to any cell
DEGRADED onand atisleast
(1.FSM, 7653 CELL FAULTY (OptIF (Cell cannot operate
7653
2.FBB CELL
cell)._x000D_
one otherwhen FSPFAULTY
FSP is (1.FSP:
operational).
on FBB is The
not faulty(FSP
_x000D_
mapped FSP
to anyis FBB
mapped to the 7654 because CELL OPERATION
of not enoughFAULTY DEGRADED
available andSystem(OptIF (Cell
needed
mapped
7650
cell.
7654 BASE
2.OptIf:
CELL to the The cell)
STATION
OPERATION cell FAULTY
cannot (1. The
operate
DEGRADED System
because
(FSP on Module
there
FBB are
is not 7650
can BASE
still operateSTATION because still (The
have enough Module
available
7653
internal CELL
cell)._x000D_ FAULTY (1. or
communication FSP and FBB: Theproblem.
synchronization faulty FSP All issignal resources:
internal Tx or Rx))_x000D_
communication or synchronization problem.
enough
mapped
7650
mapped BASE available
to the
to the STATION and
cell)_x000D_
cell.the needed
FAULTY
2. System
OptIf: resources:
The(the cellfaulty
cannot Tx
FBB or Rx
onisFBB
operate )._x000D_
not because
mapped 7650 and
7654 needed
BASE
CELL resources:
STATION FAULTY
OPERATION both Tx
DEGRADED and Rx))
(There are no (Cell
7654
processors
7654
to anyCELL
CELL
cell
OPERATION
inside
OPERATION
and all FSPs
DEGRADED
BTSModule
inDEGRADED
(FSP
are
(OptIf
are faulty)_x000D_ unstable.
(The cell 2.isThe
can All signal
working processors
baseband inside
resources the System(OptIF
available inModule
the are
there
mapped
7653
FSP onare
CELL tonot
systemthe enough
FAULTYcell)
module (Aavailable
critical
is faulty, and
HW/SW needed
the DEGRADED
FSP fault resources:
inside
is not mapped the Tx
RF to or can still operate
unstable.)_x000D_ because it still has enough
still
7651
Rx operate
BASE
)._x000D_
Module. Thebecause
STATION
cellFSPscannot itOPERATION
still has enough
operate because available
ofSystem and
not enough(1.The needed BTS.)_x000D_
available and needed resources: both Tx and Rx))
any
7652
faulty cell
resources: BASE
FBB and is all
STATION
bothnot Tx and
mapped in BTS
NOTIFICATION
Rx)) to are
any faulty.)_x000D_
cell and(The at least one Module
other _x000D_
_x000D_
7654
available
_x000D_ CELL and OPERATION
needed DEGRADED
resources: Tx or (OptIf
Rx) (The cell can 7651
cooling
FSP
Flexi
still is
BTS
operate
fanFDD,is notFlexi
operational.
because
rotating
2 itThe
BTS atTDD:_x000D_
the specified
stilldegraded
has enough FBB speed.)
is
availablemapped and toneeded
any 7651 BASE BASE STATION
STATION OPERATION OPERATION DEGRADED DEGRADED
7651
7655 BASE
CELL
cell)_x000D_
7650 BASE STATION
NOTIFICATION
STATION OPERATION
FAULTY (The (The RF DEGRADED
Module
System cooling
Module (1.The fan
cannot is (The
(The System
replaceable Module internal
baseband communication
unit is faulty or
but some
resources:
7654
7651
System
not CELL
BASE
rotating Moduleboth
OPERATION
STATION
at the Tx and
internal
specified Rx))DEGRADED
OPERATION speed.) DEGRADED
communication (The cell
or synchronization can still
(No valid 7651 BASE STATION
synchronization problem, OPERATION
or the BTS DEGRADED
memory
7652
be BASE
identified
operate
reference because STATION
by
sources its_x000D_ NOTIFICATION
it available.
still hasTDD:_x000D_
enough
The BTS (working
available
OCXOnot and FBB
is inneeded is
holdover not of the BTS baseband resources are still working.)
problem,
Flexi
mapped
product BTS or
to
codeFDD,the
any but BTS
Flexi memory
cell)._x000D_
is and
knownBTS by operations
its physicalare device stable. address At(by (No 7652 valid
operationsBASE reference
are
STATION sources
not stable. At available.
NOTIFICATIONleast one The signal
(FSM) BTS
resources:
mode.)_x000D_
least one both
signal Tx
processor Rx) inside OCXO is in holdover mode.)
7652
7653
object
7650
_x000D_
BASE
CELL
BASE STATION
FAULTY
ID)._x000D_ STATION NOTIFICATION
(faulty
FAULTY FBB(1.Theisthe System
mapped (FSM)_x000D_
faulty Module
toFSPthe is not is processor
7653 CELLinside FAULTY the (FRSystem (theModule
cell cannotis working.)
operate
working.2.
7653
mapped CELL
cell)._x000D_
Or there is
to The
aFAULTY
any FSP
System
cell on
and system
(FR)_x000D_
Module
all FSPs module
subassembly
in the is
BTS faulty,
(FSP)
are the FSP
allocation
faulty is 7653
because CELL not FAULTY
enough (LCR)
7652
not
_x000D_ BASE STATION
mapped to any cellNOTIFICATIONand (Uncommissioned
at least one(According FSP in BTS to is the unit 7652 BASE STATION NOTIFICATION (According to
7654
source CELL
failure.)_x000D_
2.FCT/FCM)_x000D_
Tx/Rx
synchronization OPERATION
filter)
priority DEGRADED
list, the (degraded
synchronization FBB
reference is resources:
the synchronizationTx or Rx))_x000D_
priority list, the synchronization
operational
Flexi
mapped
_x000D_
7651 Zone
BASE to thefaulty.)_x000D_
Micro FDD,
cell)._x000D_
STATION Flexi
OPERATION Zone Micro
DEGRADEDTDD:_x000D_ (the faulty 7654 CELL OPERATION DEGRADED
source
_x000D_
7652 has
BASE been
STATION changed to
NOTIFICATION lower source.
(Flexi Tuning
Zone follows
Micro reference source has been changed to (FR lower (the cell
7655
7651
FSP
Flexi
this is
new CELL
BASE
BTS not NOTIFICATION
FDD, STATION
mapped Flexi
reference._x000D_ to OPERATION
any
BTS (working
cell and
TDD:_x000D_ at FBB
DEGRADED
least is
one mappes (A
other to
FSP the is can still operate because still have enough available
7652
BTS)_x000D_
cell)
subassemblyBASE
operational)_x000D_
7652 BASE STATION
(FSP) inside
the System_x000D_
NOTIFICATION (The
_x000D_ working FSP is source. and needed
Tuning follows this new reference.)
resources:FAULTY both Tx(all andFSP Rx))_x000D_
_x000D_
7650
not
7653 BASE
mapped
CELL STATION
to any
FAULTY FAULTY
cell)._x000D_
(LCR)_x000D_ (the faulty FSP is not mapped 7650 BASE STATION are faulty)
Module
7652
_x000D_
Flexi
to any BASE
BTS cannot
cell TDD
and be
STATION
only:
all identified
FSPs NOTIFICATION
7650 in by
BASE
the its
BTS product
STATION
are (if code
otherFAULTY
faulty)_x000D_ but
alarm, is known
where 7651 BASE STATION OPERATION DEGRADED
_x000D_
Flexi
by
fault
Flexi BTS
its4001
Zone FDD,
physical_x000D_
isMicro
notrun Flexi
the
FDD, BTS
alarm Flexi TDD:_x000D_
source,
Zone Micro for theTDD:_x000D_
same FSP, FBB, or 7650
(FSP, BASE
at leastSTATION
one FSPFAULTY (all FSPs or
still working)_x000D_
(Holdover
7651
7653
7650 BASE
CELL
BASE time STATION
FAULTY
STATION out.) OPERATION
(The
FAULTY FSP on DEGRADED
system
(1.FSM. 2.Themodule faulty (the
is faulty
faulty
FSP is 7651
FCM/FCT BASE areSTATION
faulty)_x000D_OPERATION DEGRADED (at
device
FR
7651
Flexi
FSP is BTS
is address
active)_x000D_
BASE
not FDD,
mapped (by
STATIONFlexi object
toBTS ID).
OPERATION
any Or
TDD:_x000D_
cell and the number
DEGRADED
atinleast one of FSPs
(When in
other FSP is least the
no 7650 BASE
one STATION
working FAULTY
FSP)OPERATION (FSP,
(FCM no working
or all FSPs
and
not
BTS
7653
other
7650 the
mapped
is FSP
too_x000D_
CELL
reference
BASE is
to
FAULTY mapped
any
clock
STATION cell(the to
and
sources
FAULTY the
all
faulty cell)._x000D_
FSPs
FSP
are is BTS
mapped
available)_x000D_
(1.FSM.2.The are to
faulty the FSP is 7651
FSPs
are BASE
in
faulty) BTS STATION
) DEGRADED (at
operational)_x000D_
7650
_x000D_ BASE
faulty)_x000D_ STATION FAULTY (Level BTS Fault is toggling in 7650 BASE STATION FAULTY (Level BTS Fault is
small.
cell)._x000D_
7652
not
7653
the Or unit
BASE
mapped
CELL
BTS.)_x000D_ toorany
STATION
FAULTY an cellIP(theaddress
NOTIFICATION
and initialization
all FSPs
faulty FSP (When
inmapped
is the BTS hasthere are
to the at least least
is cell). toggling
one working FSP)
in the BTS.)_x000D_
7654
7651
7653
one CELL
BASE
failed.)_x000D_
CELL
more
faulty)_x000D_ OPERATION
STATION
FAULTY
working (FR(the
reference DEGRADED
OPERATION cell cannot
clock source) (The
DEGRADEDoperate degraded (the faulty
because FSP is 7651 BASE STATION OPERATION DEGRADED
_x000D_
mapped
FSP is notto the
mapped cell.)_x000D_
to any cell and at least one other FSP is _x000D_
_x000D_
there
7651
Flexi
7651 are not
BASE
BTS
BASE FDD, enough
STATION
STATIONFlexi available
OPERATION
BTS
TDD:_x000D_ DEGRADED
DEGRADED resources: (the
(Level TxBTS
faulty or (FSP)
7650
STATION FAULTY OPERATION (FCMDEGRADED
is out of order)
_x000D_
operational)_x000D_
7652
Rx))_x000D_
FSP
7650 BASE
isis not STATION
mapped to anyNOTIFICATION
cell and at least
FAULTY_x000D_ (An unsupported
one other FSP is 7652 BASE STATION NOTIFICATION (FCM is
Fault
7655 toggling in
NOTIFICATION the BTS.)_x000D_
(The working (Level BTS Fault is toggling in the BTS.)_x000D_
7653
module
7654 CELL
CELLwasFAULTY
operational)_x000D_
_x000D_
_x000D_ found in(the
OPERATION faulty
the_x000D_
DEGRADED FSP (FRFSP
is mapped (theisto mapped
thecan still
cell to working)
_x000D_
the
BTS. cell.)_x000D_
cell)._x000D_
Flexi BTS
TypicallyFDD, Flexi
this it happensBTS TDD:_x000D_
when aavailable
new module toversion
operate
7653
Flexi
7652
_x000D_
7650
CELL
Zone
BASE
BASE
becauseFAULTY
Micro
STATION
STATION
FDD, still
(thehas
Flexi enough
faulty
NOTIFICATION
FAULTY
Zone FSP is mapped
Micro
(1.FCM/FCT,
TDD:_x000D_
(Level and
BTS
2.FSP
needed
the
Fault
(allisFSPs isis 7652 BASE STATION NOTIFICATION (Level BTS
installed
resources:
cell)._x000D_
7650
7653
toggling BASE
CELL and_x000D_
in theboth
STATION
FAULTY Tx and
BTS.)_x000D_ (in Rx))
FAULTY
case (Flexi
cell cannot Zone remainMicro BTS
operational out 7653 Fault is CELL FAULTY
toggling in the (Unit source TX filter (the cell
BTS.)_x000D_
Flexi
in BTS
there
_x000D_
of Zone
is are
an
order)_x000D_
because Micro
there is FDD,
faulty))_x000D_
older BTS
not SWFlexi
enough in Zone
use
available Micro
that does
RX TDD:_x000D_
not
and/or support
TX the cannot operate because not enough available and
_x000D_
Flexi
7650
7651 BTS
BASE FDD, STATIONFlexi BTS FAULTY
OPERATIONTDD:_x000D_ DEGRADED (FSP, not _x000D_
new
Flexi
7652 module
Zone
BASE
resources)_x000D_
7653 CELL version.)_x000D_
Micro
STATION
FAULTY FDD, Flexi
NOTIFICATION
(Level Zone
BTS Micro
Fault is TDD:_x000D_
(Flexi
toggling Zone in Micro
the BTS needed resources: Tx or Rx))
all
7653
7650
is FSPs
working)
_x000D_ CELL
BASE in BTSFAULTY_x000D_
FAULTY
STATIONare faulty)_x000D_
(the
FAULTYcell cannot(all DSPs operate are because
faulty)_x000D_ there 7653 CELL FAULTY (cell cannot Fault
7653 CELL FAULTY (Level BTS operate is toggling
becausein
BTS.)_x000D_
_x000D_
_x000D_
are not enough available and needed resources: Tx orbe the BTS.)_x000D_
7653
7651
7654
7652
_x000D_
Flexi CELL
BASE
Zone FAULTY
OPERATION
STATION
Micro FDD, (The RFZone
OPERATION
DEGRADED
NOTIFICATION
Flexi Module Micro or
DEGRADED
(inFilter
casecannot
(Uncommissioned
TDD:_x000D_ (not
regardless all to there 7654
7652
_x000D_
are notOPERATION
CELL
BASE enough available
STATION DEGRADED
NOTIFICATION and needed (Unit source
Flexi
Rx)_x000D_
identified
DSPs
detected Zone
are
source)_x000D_ by Micro
its
faulty)
issue cellFDD,
product_x000D_
is Flexi
still havingZone Micro
enough TDD:_x000D_
available RX and / resources:
diversity
(Uncommissioned RX Tx or
filter Rx)
or TX
source) filter (the cell can still BTS
7654
7655
7652
7650
7654 CELL
BASE
BASE
CELL OPERATION
NOTIFICATION
STATION
STATION
OPERATION DEGRADED
NOTIFICATION
FAULTY_x000D_
DEGRADED (Level
(Uncommissioned
(the cell BTS can Fault
still is 7654
7654 CELL
CELL OPERATION
OPERATION DEGRADED
DEGRADED (Level
(cell can
code
or
7654TX
toggling but
CELL
source)_x000D_ is
resources
in theknown
OPERATION so by
BTS.)_x000D_it its
can physical
remain
DEGRADED device address
operational)_x000D_
(Otherwise)_x000D_ (by operate
7654
Fault CELL because
OPERATION
is toggling still
inthere have enough
DEGRADED
the BTS.)_x000D_ available andstill
(Otherwise)
_x000D_
operate
7650
object_ID).
_x000D_ BASE because
Or STATION there
an_x000D_ are
FAULTY enough (the available
faulty FSP and is needed
not mapped operate
needed because
resources: both Tx and Rx))are enough available and
_x000D_
7654
resources:
to any CELL OPERATION
both
cell and_x000D_ Tx and DEGRADED (Otherwise)
Rx)_x000D_ _x000D_
needed resources: both Tx and Rx) DEGRADED (at
RF
7652
7653
7655 Module
BASE
CELL
CELL with
STATION
FAULTY incompatible
NOTIFICATION - NOTIFICATION
radio frequency
sharing is (inhas
disabledcase
(Level BTS Fault is toggling in been fault
with detected.
source
the is 7651 BASE STATION OPERATION
7655 CELL NOTIFICATION (Level BTS Fault is
all
Or FSPs
WCDMAboth
uncomissioned in the
sector_x000D_
system BTS
unit)
module are faulty)_x000D_
and the LTE cell cannot operate 7652
BTS BASE
start-up) STATION NOTIFICATION
the
7651 BTS.)_x000D_
BASE STATION OPERATION DEGRADED (the faulty toggling in the BTS.)_x000D_
types
because
_x000D_ (A and
there B) are
are notconfigured
enough to the
available same and RFneededModule in the (Uncommisisoned
7653 CELL FAULTY unit(at source
BTS start-upTx/Rx filter)
or runtime, the
FSP
7653 isCELL
not mapped
two-carrier_x000D_
resources: FAULTY
Tx or to(the
Rx._x000D_ cell cannot operate because there _x000D_
any_x000D_ 7653
cell CELL operate
cannot FAULTYbecause (The cellnot cannot
enough operate
available
7656
cell
are and
not BASE at
enough STATION
least one
available CONNECTIVITY
other andFSP is
needed LOST (Level
operational)_x000D_
resources: Tx orBTS 7656
because BASE thereSTATION
are not CONNECTIVITY
enough available LOST
and
case.
_x000D_
7650
Fault Or
BASE
is a dual
toggling PA
STATION in RF
the module
FAULTY
BTS.)_x000D_ has been replaced
(the faulty FSP is not mapped 7650 with a and
(Level needed
all
BTSFSP resources:
resources
Fault is togglingTx
lostorinRx) the BTS.)_x000D_
7653
Rx)_x000D_
single
7654
to anyCELLCELL
PA
cellRF FAULTY
module,_x000D_
OPERATION
and all FSPs (theinfaulty
DEGRADED
the BTS FSPare is mapped
-faulty)_x000D_
radio sharing to the cell). is needed
7654
7651 notresources:
CELL all OPERATION
FSP resourcesTx or Rx)_x000D_
DEGRADED
lost (at BTS
_x000D_
_x000D_ _x000D_
_x000D_
and
disabled
7651
7401 it cannot
BASE with serve
the
STATION
- 7426OPERATION WCDMA
EXTERNAL AL all cells
OPERATION commissioned
system
(EAC1=7401, module
DEGRADED to
but the
the RFLTE
(the module.
cell
faulty start-up or runtime, the cell can still operate
7654
Or cell
can
FSP isCELL
still cannot_x000D_
operate
not mapped becauseto anyDEGRADED
there
cell and are at enough (theEAC2=7402
least cell other
available
one can still and
etc) 7401 -CELL
FSP is 7654 because
7426OPERATION
EXTERNAL AL
have enoughDEGRADED
still etc)
(EAC1=7401, cell can
available and(The needed
operate because EAC2=7402
because itnot
operate resources:
needed
operational)_x000D_ still
both has
enoughTx enough
and available available
Rx._x000D_ and needed and needed still operateboth
resources: because Tx and it still
Rx)has enough available
resources:
resources:
_x000D_
7653 CELLTx both orTx
FAULTY and (theRx)_x000D_
Rx)_x000D_ faulty FSP is mapped to the cell). and needed resources: both Tx and Rx)_x000D_
_x000D_
7652 BASE STATION NOTIFICATION:_x000D_
7654
1. Radio CELL OPERATION
sharing is disabled DEGRADED
with the WCDMA (The Mast system Head module
Flexi BTS FDD, Flexi BTS TDD:_x000D_ 4082:
4082:_x000D_
Flexi BTS FDD, Flexi BTS TDD:_x000D_ 7650
4082:BASE STATION FAULTY (FCM/FCT, all FSPs)
In case
4082:_x000D_ of inconsistent SW after fallback_x000D_ 7651
7650 BASE
BASE STATION
STATION OPERATION
FAULTY (FCM/FCT, DEGRADED all FSPs)
Flexi BTS
7650 BASE FDD,STATIONFlexi BTS FAULTY TDD:_x000D_
(1.FCM/FCT, 2.The faulty 4082:
(FSP)
In case
4082:_x000D_ of inconsistent SW after fallback_x000D_ 7651
7650 BASE
BASE STATION OPERATION DEGRADED
FSP
Flexi
7650 is
Zone
BASEnot mapped
Micro
STATION FDD,to any
Flexi
FAULTY cell
Zoneand all FSPs
Micro
(1.FCM/FCT, TDD, in2.The
BTS faulty
Flexi are
Zone 7650
(FSP) BASE STATION FAULTY (FCM, FCT)all FSPs)
STATION FAULTY (FCM/FCT,
In case
faulty))_x000D_ of inconsistent SW after fallback_x000D_ 7651 BASE STATION OPERATION DEGRADED
Controller:_x000D_
FSP
7653
7650 is-BASEnot cell
the mapped to any
is disabled
STATION FAULTY cell and
because all
theFSPs
(1.FCM/FCT, in2.The
downlink BTS are that 4083:
carrier
faulty (FSP)
7651
7650 BASE
faulty))_x000D_
transmits STATION OPERATION
FAULTY_x000D_ DEGRADED (FSP - the 7650 4083:BASE STATION FAULTY (FCM/FCT)
FSP
faulty
_x000D_isFSP notPSS/SSS
mapped
is not
signals
to
mapped
hasand
anytocellany
failed_x000D_
alland
cell FSPs at in BTS
least one are
other
7651
7654 -BASE
the cell
faulty))_x000D_ STATION
is degraded OPERATION
because DEGRADED
the downlink (FSP carrier- the
that 7650 BASE STATION FAULTY (FCM/FCT)
FSP
Flexi
7650
faulty is
Zone
transmits operational)_x000D_
BASE
FSP Access
isSTATION
PSS/SSSnot mappedPoint:_x000D_
FAULTY
signals toisany (1. FSM.
cell and 2.
working_x000D_ at The
leastfaulty
one FBB is 4083:
other 4085:
7651
7653 BASE
CELL STATION
FAULTY OPERATION
(FSP when DEGRADED
faulty FSP is mapped (FSP -
to the
the 7650
7650 BASE STATION FAULTY (FCM/FCT)
7652
not
FSP mapped
faulty
BASE
isFSP STATION
to any
operational)_x000D_
is not
cell
mapped
NOTIFICATION
and
to
all
any
FSPs
cell
and
and
FBBs
at least
in the
one
BTS
other 4085:BASE STATION FAULTY (FCT)
cell)._x000D_
are
7653 faulty)_x000D_
FSP
_x000D_
7651 isCELL FAULTY (FSP when faulty FSP is mapped to the 7650
operational)_x000D_
BASE STATION OPERATION DEGRADED (the faulty 4085:
BASE STATION FAULTY (FCT)
cell)._x000D_
7653 CELL FAULTY
In
FBBcase
Flexi
_x000D_is
BTS of FDD,
not consistent
mapped Flexi to(FSP
SW
BTS when
anyafter faulty FSPone
cell fallback_x000D_
and
TDD:_x000D_ at least is mapped
other FSP to the
or 7650 BASE STATION FAULTY (FCT)
cell)._x000D_
7651
FBB
7652 BASE STATION
is operational)_x000D_ OPERATION
_x000D_ (FCM/FCT,
In case
_x000D_ of consistent SW after fallback_x000D_
FSP)_x000D_
7653
_x000D_
7651 CELL
BASE FAULTY
STATION (the faulty FBB DEGRADED
OPERATION is mapped to (FCM/FCT,the cell).
In case
_x000D_
Flexi Zone of consistent
Micro FDD, SW after
Flexi Zone fallback_x000D_
Micro TDD:_x000D_
FSP)_x000D_
7651 BASE
BASE STATION
4083:_x000D_
7651
_x000D_ STATION OPERATION OPERATION DEGRADED DEGRADED (FCM/FCT, (When no
FSP)_x000D_
In case
other of inconsistent
reference clock SW
sources after
are fallback_x000D_
available)_x000D_
4083:_x000D_
_x000D_
7650
7652
In case BASE STATION FAULTY
of inconsistent SW after(FCM/FCT)_x000D_
NOTIFICATION (When at least there is
fallback_x000D_
4083:_x000D_
7652
In
onecase
more BASE of STATION
consistent
working NOTIFICATION
SW
reference after (Antenna line without 7652 BASE STATION NOTIFICATION ((Antenna
fallback_x000D_
clock source)
7650
In case
relation BASE of STATION
to inconsistent
cell and without FAULTY
SWDEGRADED
afteror
ALD (FCM/FCT)_x000D_
fallback_x000D_
ALD not related
7651
7654
In case BASE
CELL STATION
OPERATION
of consistent OPERATION
SW DEGRADED
after fallback_x000D_ (HDLC link todisabled line 7654without relation to cellDEGRADED
CELL OPERATION and without ALD) (HDLC or link
(ALD
7650workingBASE
cell)_x000D_
(FCM/FCT)_x000D_
for STATION
ALD FAULTY
with relation (FCM/FCT)_x000D_
to cell)_x000D_ not related
disabled for is
working ALD withof relation to cell)with file
7651
Flexi
In case
_x000D_ BTSBASE of FDD,STATION
consistent Flexi OPERATION
BTS
SW TDD:_x000D_
after DEGRADED
fallback_x000D_ 7650
to - BTS
cell)) faulty because the problem
_x000D_
7652 BASE
(FCM/FCT)_x000D_
7650 -CELL
The BTS STATION is faulty NOTIFICATION
because (HDLC
of DEGRADED
the(DCproblem link disabled
with file 7652 BASE STATION NOTIFICATION
signature. Rollback to previous SW is required. (HDLC link
7651
7654
4085:_x000D_
for working BASE STATION
OPERATION
ALD without OPERATION
DEGRADED
relation to cell) voltage disabled disabled for working ALD without relation to cell)
_x000D_
signature.
(FCM/FCT)_x000D_
for ALD Rollback
utilized to previous SW is required._x000D_
by cell)_x000D_ 7652 -CELL
BTS OPERATION
is working on DEGRADED
current SW. New (DC SW
In case
7653
4085:_x000D_
7652 CELL
- of
The inconsistent
FAULTY
BTS is workingSW unit
(radio after
on the fallback_x000D_
connected
current to port
SW. New #3SW or #4 on 7654
#N/A be activated
cannot due to file signature
voltage
mismatch.
_x000D_
7650
FBBC BASE
may STATION
not be used FAULTY
due to (FCT)_x000D_
problem related to port #3 or disabled for ALD utilized by cell)
In case
cannot
4085:_x000D_
7655 CELLof inconsistent
be activated
NOTIFICATION SW after
because (Antennafallback_x000D_
of file signature
line related to cell #N/A
In
#4 case
7650 BASE
mismatch._x000D_of consistent
configuration STATION on FBBC SW after
FAULTY card fallback_x000D_
and cell
(FCT)_x000D_ cannot operate
In case
without
7650
7651
because BASEofofinconsistent
ALD)
BASE STATION
STATION
not enough SW
FAULTY after(configuration
OPERATION
available fallback_x000D_
needed failure
andDEGRADED resources: at BTS 7655 BASE
Tx 7650 CELL NOTIFICATION
STATION FAULTY (Antenna
(LTE505 line related to
In case
_x000D_
7650 BASEof consistent
STATION SW after fallback_x000D_
FAULTY (FCT)_x000D_ cell and without ALD)
startup)_x000D_
(FCT)_x000D_
or Rx)_x000D_
Flexi BTS FDD:_x000D_ configuration
#N/A failure at eNB startup)_x000D_
7651
Flexi
In case ZoneBASE STATION
Micro
of consistent FDD, OPERATION
SWFlexi Zone
after DEGRADED
Micro
fallback_x000D_TDD:_x000D_
7651
_x000D_
7654
7652 BASE
CELL
BASE STATION
OPERATION
STATION OPERATION
DEGRADED
(radio
(External unit (re-
connected
GPS 7651 BASE STATION OPERATION DEGRADED
(FCT)_x000D_
7650
7652 BASE
7651 - The BTS
BASE STATION
STATION is faulty because
NOTIFICATION
OPERATION of the problem
(FSP or FBB is not
DEGRADED with loading
configuration
_x000D_
to port
receiver #3 or
has #4failure
lost onthe during
FBBC may
satellite BTS runtime)
not
visibilitybe used
but due
there to
is problem
another (LTE505 re-configuration failure during eNB runtime
_x000D_
the DSP to
mapped
(FCT)_x000D_ SW anyinto the proper memory place. Rollback to
cell)_x000D_
Flexi
related
valid
_x000D_
previous
7655
Zone toSW
reference
CELL
Micro
port is #3 FDD,
source Flexi
or #4available
required._x000D_
NOTIFICATION
Zone Micro
configuration on TDD:_x000D_
(FSPfororuse)_x000D_
FBB FBBC
is mapped card butto thecell #N/A
_x000D_
7651
can still BASEoperateSTATION because OPERATION
it on
still DEGRADED
hascurrent
enough available and
_x000D_
Flexi
7652
cell) Zone- The Micro
BTS isFDD,
workingFlexi Zone
the Micro TDD:_x000D_
SW. New SW
_x000D_
needed resources: both Tx and Rx)_x000D_
7651
7651
cannot
7656 BASE
BASE STATION
STATION
be activated OPERATION
OPERATION
because DEGRADED
DEGRADED
of fileMicro
CONNECTIVITY signature
LOST (External
mismatch.
(Transport 7656 BASE STATION CONNECTIVITY LOST
Flexi
7652 ZoneBASEMicro STATION FDD, Flexi Zone
NOTIFICATION TDD:_x000D_
(radio unit connected
GPS receiver
path(SCTP) for hasS1lost the
is broken. satellite
No other visibility and
S1 interface there are no (Transport path(SCTP) for S1 is broken. No other
available
7651
to BASE STATION OPERATION DEGRADED
forport
other #3 orvalid
other
use)._x000D_ #4 on FBBC issources
reference not commissioned)_x000D_
available)_x000D_ S1 interface available for use)._x000D_
7651
_x000D_
_x000D_ BASE STATION DEGRADED (other case)_x000D_ _x000D_
_x000D_
7657 BASE STATION CONNECTIVITY DEGRADED 7657 BASE STATION CONNECTIVITY
(Transport path(SCTP) for S1 is broken but there is at least DEGRADED (Transport path(SCTP) for S1 is
7652
one other BASE S1STATION
interface NOTIFICATION
available for use). (External GPS broken but there is at least one other S1 interface
receiver has lost the satellite visibility but there is another available for use).
valid reference source available for use)_x000D_
_x000D_
7651 BASE STATION OPERATION DEGRADED (External
GPS receiver has lost the satellite visibility and there are no
other other valid reference sources available. The holdover
threshold value is not expired yet)_x000D_
_x000D_
7650 BASE STATION FAULTY (External GPS receiver has #N/A
lost the satellite visibility and there are no other other valid #N/A
reference sources available. The holdover threshold value is
expired) #N/A
#N/A
The estimated phase error in holdover has exceeded 5 us. #N/A
7656 BASE STATION CONNECTIVITY LOST(No other S1 7656 BASE STATION CONNECTIVITY LOST(No
interface
7656 BASE is operational.)_x000D_
STATION CONNECTIVITY LOST(No other S1 other S1 interface
7656 BASE is operational)_x000D_
STATION CONNECTIVITY LOST(No
_x000D_
interface is operational)_x000D_ _x000D_
other S1 interface is operational)_x000D_
7657
_x000D_BASE STATION CONNECTIVITY DEGRADED (An 7657 BASE STATION CONNECTIVITY
_x000D_
other S1 interface
7657 BASE is operational.)
STATION CONNECTIVITY DEGRADED (An DEGRADED (An otherCONNECTIVITY
7657 BASE STATION S1 interface is operational)
other S1 interface is operational) DEGRADED (An other S1 interface is operational)
7652 BASE STATION NOTIFICATION (1.FSM. 2.FSP or FBB

is not BASE
7652 mapped to any cell)_x000D_
STATION NOTIFICATION (FSP or FBB is not
7655
mapped CELL
to NOTIFICATION
any cell)_x000D_ (FSP or FBB is mapped to the
Flexi BTS
cell)_x000D_ FDD, Flexi BTS TDD:_x000D_ #N/A
7655
7650 CELL
BASE NOTIFICATION
STATION FAULTY (FSP orfaulty
(the FBB is mapped
FSP is not to the
mapped
cell)_x000D_ #N/A
to anyBASE
7650 cell and all FSPs
STATION in the BTS
FAULTY (the are faulty)_x000D_
faulty FSP is not mapped
Flexi
7651 BTS FDD, Flexi BTS TDD:_x000D_ (the faulty #N/A
to anyBASE
7650 BASE
STATION
cell and all FSPs
STATION
OPERATION
in the BTS
FAULTY (theat
DEGRADED
are faulty)_x000D_
faulty FSP isother
not mapped
FSP
7651 is not mapped to any cell and least one (theFSP is
to anyBASE STATION
cell and
operational)_x000D_all FSPsOPERATION
in the BTS are DEGRADED
faulty)_x000D_ faulty
FSP
7651 isBASE
not mapped
STATION to any cell and at least one other
OPERATION FSP is
7653 CELL FAULTY
operational)_x000D_ (the faulty FSP DEGRADED
is mapped to (thethe faulty
FSP is not mapped to any cell and at least one other FSP is
cell)._x000D_
7653 CELL FAULTY (the faulty FSP is mapped to the
operational)_x000D_
_x000D_
cell)._x000D_
7653
Flexi CELLMicro
Zone FAULTY (the
FDD, faulty
Flexi ZoneFSP is mapped
Micro to the
TDD:_x000D_
_x000D_
cell)._x000D_
7650
Flexi BASE STATION FAULTY
Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
7650 BASEMicro
Flexi Zone STATIONFDD,FAULTY
- -
#N/A
LED Display
Stable green
Stable red (FBB) Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653-otherwise)
Stable green
Stable red (7650; 7653), blinking red (7651; 7653), alt. red and green (7653 and 7654 [MHA, TILT]), stable green (7652)
Stable red
Stable red (7650, 7653), blinking red (7651, 7654)
Blinking yellow
Stable green
Stable green
Stable green
Blinking red (7651, 7654),Stable green (7655)
Stable yellow
Stable green
Stable green
Stable green
Stable red (FBB) Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653 -otherwise)
Stable red (7650), Blinking red (7651), N/A (7652, 7653, 7654)
Stable red (7650), Blinking red (7651), N/A (7652, 7653)
Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
Stable red (FBB) Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653-otherwise).
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Stable red (7650), Blinking red (7651), Stable green (7652)
Stable red (7650; 7653; 7654), Blinking red (7651; 7653; 7654), Stable green(7652)
Stable green
Stable red (7650; 7653; 7654), blinking red (7651; 7653; 7654)
Optical port LED: stable red
Stable red (7650); Blinking red (7651), Stable Green (7652)
Stable red
Stable red (7650), Blinking red (7651)
Stable red
Blinking red
Stable red
Stable red (RF module faulty), Alternating red and green (RF module working, MHA faulty)
Alternating red and green (RF working, Antenna Line faulty)(description only for RF module using RP1 protocol)
Stable red (all Antenna Lines of RF faulty); Blinking red (otherwise) (description only for RF using RP1 protocol)
Blinking red (description only for RF module using RP1 protocol)
Stable red (if all LNAs of the RF module are faulty); Blinking red (if some, but not all LNAs of the RF module are faulty)
Stable red (all DL and UL antenna-carriers activated on the FR are faulty); Blinking red (otherwise)
Stable red
Alternating red and green (RF module working, MHA faulty)
Stable Green (7652) Alternating Red and Green (7654)
N/A
Stable red
Stable red
Stable green
Stable green
Alternating red and green (RF working, MHA degraded)
Alternating red and green (RF working, MHA faulty)
Blinking red (Filter), Stable green (other)
Blinking red
Blinking red
Stable red; Blinking red; Stable green
Blinking red (7651), green (7652)
Stable red
Stable red
Blinking red
Stable red (7653), Blinking red (7654)(description only for RF module using RP1 protocol)
Stable red (all Antenna Lines of the RF module are faulty); Blinking red (not all Antenna Lines of the RF module are faulty)
Blinking red
Blinking red
Blinking red (7654), Stable red (7653, 7650).
Stable red
RP1 RF only:Stable red-all activated antenna-carriers faulty; Blinking red- at least 1 activated ant.-carrier faulty or degraded
Blinking red
Blinking red
Stable red (7653)
Flexi BTS FDD&TDD:Blinking red (description only for RF module using RP1 protocol) Flexi Zone Micro FDD&TDD: Stable red
Blinking red
Stable red (description only for RF module using RP1 protocol)
Blinking red
Blinking red
Stable red
Stable or blinking red (Fan)
FR module LED: Stable green (7652, Fan Group Degraded), Blinking red (7652, Fan Group Out of Order).
Stable/Blinking Yellow
Stable green
Stable green
RFM connected over OBSAI RP1 interface: Stable red; RRU connected over CPRI Ir interface:N/A
Blinking red (FR unit status: degraded), Stable Red (FR unit status: out of order)
Blinking red
Blinking red
Stable red (all activated carriers TX & RX of RF are faulty); Blinking red (not all activated carriers TX & RX of RF are faulty)
Stable green
Stable red (optical interfaces)
Blinking red(optical interfaces)
Stable red (optical interface)
Blinking red
Blinking red
Blinking red
Stable green
Stable red
Stable red (1.FBB, 2. Oprical Int. 3.FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Stable red (FBB) Stable red (FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Blinking red
Stable red
Stable red
Blinking red
Stable red (7650), Stable green (7652)
Stable red (1.Oprical Int. 2.FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Blinking Red (7651)
Blinking Red (7651)
Blinking Red (7651)
N/A
N/A
N/A
N/A
N/A
N/A
Stable green
Stable green
Stable red
Stable green
LED display should remain unchanged.
N/A
Stable red
FSM led: Blinking red
Stable red (7650), blinking red (7651)
Stable red
Stable green
Periodic red and green
Periodic red and green (RF working, Antenna Line degraded)
Alternating red and green
Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653-otherwise)
FSM Optif led: stable red.
Stable green (fan LED)
FSM Optif led: blinking red
Stable Red(Fan Group Out Of Order), Stable Yellow(FAN Group Degraded)
Stable Yellow
Stable Yellow
Stable red (7650), Blinking red (7651, 7653)
Stable red (7650)
Stable green
Stable red (FBB) Stable red (FSM:7650,7653-all FSPs and FBBs faulty) Blinking red (FSM:7651,7653-otherwise)
N/A
Stable red
Stable green
Stable green
Stable green
Stable green
Stable green
Stable green
Stable green
Stable red (7650) Stable green (7652)
Blinking red
N/A
Stable green
Stable green (7652), Blinking red (7651), Stable red (7650)
Stable green
N/A
N/A
N/A
N/A
N/A
Stable red
Flexi BTS FDD, Flexi BTS TDD:N/A Flexi Zone Micro FDD, Flexi Zone Micro TDD:Stable red
Flexi BTS FDD, Flexi BTS TDD:N/AFlexi Zone Micro FDD, Flexi Zone Micro TDD:Stable red
Stable green
Stable red
N/A
Blinking red
Stable Green
Stable Green
Stable Green
Stable Green
Stable green
N/A
Stable green
Stable green
N/A
N/A
N/A
N/A
N/A
Stable green
Blinking red
Blinking red
Stable green
None
Stable green
Stable green
Stable Green
Blinking Red
Stable red
Stable red
Stable red
Blinking red
Stable red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking Red
Blinking red
Stable red
Blinking red
Blinking red
Blinking red
Blinking red
Stable red
Blinking red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking red
Blinking Red
Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
Stable Green
Flexi BTS FDD, Flexi BTS TDD:
Stable
Stable Green
Green
Stable Green
Blinking red
Stable red
Blinking red
Stable Green
Blinking red
Stable green
Stable green
NORA: Blinking Red, Flexi: Stable Yellow (Fan Group Degraded)

Stable red
N/A
Stable red
N/A
Stable green
Stable red (7650)
Stable red (7650)
Stable green
Stable red
Blinking red
Blinking red
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Stable red
Blinking red (7651), Stable red (7650)
Stable red
Blinking red
Stable red (7653, RF state faulty), Blinking red (7653, RF state degraded), Stable green (7655)
Blinking red
Blinking red (7651), Stable red (7650)
stable red (7650) , blinking red (7651)
Stable green
N/A
Stable green (refers to detecting unit)
N/A
LED Display in issue 01
Stable green
Stable green
Stable green (FBB) Stable red (FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Blinking yellow
Stable green
Stable green
Stable green
Stable yellow
Stable green
Stable green
Stable green
Stable red (FBB) Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653 -otherwise)
Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Stable red (7650; 7653; 7654), Blinking red (7651; 7653; 7654), Stable green(7652)
Stable green
Stable red (7650); Blinking red (7651), Stable Green (7652)
Stable red
Stable red
Blinking red
Stable red
Alternating red and green (RF working, Antenna Line faulty)(description only for RF module using RP1 protocol)
Stable red (all Antenna Lines of RF faulty); Blinking red (otherwise) (description only for RF using RP1 protocol)
Blinking red (description only for RF module using RP1 protocol)
Stable red (if all LNAs of the RF module are faulty); Blinking red (if some, but not all LNAs of the RF module are faulty)
Stable red
Stable red
N/A
Stable red
Stable red
Stable green
Stable green
Alternating red and green (RF working, MHA degraded)
Blinking red
Blinking red
Stable red; Blinking red; Stable green
Blinking red (7651), green (7652)
Stable red
Stable red
Blinking red
Stable red (7653), Blinking red (7654)(description only for RF module using RP1 protocol)
Blinking red
Blinking red
Blinking red (7654), Stable red (7653, 7650).
Stable red
RP1 RF only:Stable red-all activated antenna-carriers faulty; Blinking red- at least 1 activated ant.-carrier faulty or degraded
Blinking red
Blinking red
Stable red (7653)
Flexi BTS FDD&TDD:Blinking red (description only for RF module using RP1 protocol) Flexi Zone Micro FDD&TDD: Stable red
Blinking red
Blinking red
Blinking red
Stable red
Stable green
Stable green
Blinking red
Blinking red
Stable red (all activated carriers TX & RX of RF are faulty); Blinking red (not all activated carriers TX & RX of RF are faulty)
Stable green
Stable red (optical interface)
Blinking red
Blinking red
Blinking red
Stable green
Stable red
Stable red (FBB) Stable red (FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Blinking red
Stable red
Stable red
Blinking red
Stable red (1.Oprical Int. 2.FSM-7650,7653 all FSP faulty).Blinking red (FSM-7651,7653-otherwise)
Blinking Red (7651)
Blinking Red (7651)
Blinking Red (7651)
N/A
N/A
N/A
N/A
N/A
N/A
Stable green
Stable green
Stable red
Stable green
N/A
Stable red
FSM led: Blinking red
Stable red
Stable green
Stable red (FSM:7650,7653-all FSPs faulty) Blinking red (FSM:7651,7653-otherwise)
FSM Optif led: stable red.
Stable green
FSM Optif led: blinking red
Stable Yellow
None
Stable red (7650)
Stable green
N/A
Stable red
Stable green
Stable green
Stable green
Stable green
Stable green
Stable green
Stable green
Blinking red
N/A
Stable green
Stable green (7652), Blinking red (7651), Stable red (7650)
Stable green
N/A
N/A
N/A
N/A
N/A
Stable red
Flexi BTS FDD, Flexi BTS TDD:N/A Flexi Zone Micro FDD, Flexi Zone Micro TDD:Stable red
Flexi BTS FDD, Flexi BTS TDD:N/AFlexi Zone Micro FDD, Flexi Zone Micro TDD:Stable red
Stable green
Stable red
N/A
Blinking red
Stable Green
Stable Green
Stable Green
Stable Green
Stable green
N/A
Blinking yellow
Stable green
N/A
N/A
N/A
N/A
N/A
Stable green
Blinking red
Blinking red
Stable green
None
Stable green
Stable green
Stable Green
Blinking Red
Stable red
Stable red
Stable red
Blinking red
Stable red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking Red
Blinking red
Stable red
Blinking red
Blinking red
Blinking red
Blinking red
Stable red
Blinking red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking red
Blinking Red
Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
Stable Green
Stable
Stable Green
Green
Stable Green
Blinking red
Stable red
Blinking red
Stable Green
Blinking red
LED Display in release RL60
Stable green
Stable red ( 7650), Blinking Red ( 7651,7653)
Stable green
Stable red (FCM/FCT on MSM or all FSPs); Blinking red (not all FSPs)
Stable green
Stable green
Stable yellow
Stable green
Stable green
Stable red ( 7650) , Blinking red ( 7651)

Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Stable red (7650) / (7653), Blinking red (7651) / (7654)
Stable green
Stable red ( 7650); Blinking Red (7651)
Stable red(7650): Blinking red (7651)
Stable red
Blinking red
Stable red
Blinking red
Stable red
Alternating red and green (RF working, Antenna Line faulty)
Stable red (all DL and UL antenna-carriers activated on the RF are faulty); Blinking red (otherwise)
Blinking red
Stable red (if all LNAs of the RF module are faulty); Blinking red (if not all LNAs of the RF module are faulty)

Stable red
Stable red
Stable green
Stable green

Blinking red
Blinking red
Blinking red
Stable red
Stable red
Blinking red
Blinking red
Blinking red
Blinking red (7654), Stable red (7653).
Stable red
Stable red (all activated antenna-carriers faulty); Blinking red (at least one activated antenna-carrier faulty or degraded )
Blinking red
Blinking red
Stable red (7653)
Blinking red
Blinking red
Stable red
Stable red
Blinking red
Blinking red
Stable red
None
Stable green
Stable red
Blinking red
Blinking red
Stable red (all antenna lines of the RF module are faulty); Blinking red (not all antenna lines of the RF module are faulty)
N/A
Stable red (optical interfaces 1-5 leds)
Stable red (optical interfaces 1-5 leds)
Stable red (appropriate OptIF led 1-5)
Stable red (SFP led)
#N/A
Blinking red
Blinking red
Stable green
Stable red
Stable red
FSM LED: 7650:stable red, 7651:blinking red, plugin FSP LED: stable red if FSP faulty, blinking red if FSP degrade
Blinking red
Stable red
Stable red

Stable Red (7650), Blinking Red (7651), Stable Red (7653, 7654)
Stable Red (7650), Blinking Red (7651), Stable Red (7653, 7654)
Blinking Red (7651)
Blinking Red (7651)
Blinking Red (7651)
N/A
N/A
N/A
Stable green
Source FSP, FR RP1 IF v.1.x: Stable red. Source FR RP1 IF v.2.x: N/A
Stable green
Stable green
Stable green
Stable red
Stable red (7650) , Blinking red (7651)
N/A
Blinking red
Stable red

Stable red
Stable red
Stable green
Not Applicable
Stable red (FSP)
Stable Yellow
None
Stable red (7650)
Stable green
Stable red
N/A
Stable red
Stable green
Stable green
Stable green
Stable green
Stable green
Stable green
STABLE GREEN
#N/A
#N/A
#N/A
None
#N/A
N/A
N/A
N/A
N/A
Stable red
N/A
N/A
N/A
Stable red
N/A
N/A
Stable Green
#N/A
#N/A
#N/A
Stable green
N/A
#N/A
#N/A
N/A
N/A
N/A
N/A
N/A
Stable green
Blinking red
Blinking red
Stable green
None
Stable green
Stable green
#N/A
#N/A
#N/A
Stable Green
Blinking Red
Stable red
Stable red
Stable red
Blinking red
Stable red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking Red
Blinking red
Stable red
Blinking red
Blinking red
Blinking red
Blinking red
Stable red
Blinking red
Blinking red
Stable Green
Blinking red
Blinking red
Blinking red
Blinking Red
Blinking red
Blinking red
Blinking red
Blinking red
Blinking red
Stable Green
Stable Green
Stable Green
Stable Green
Stable red
Blinking red
Stable Green
#N/A
Instructions
Check the active fan alarms and the air flow of the BTS.
1. Download the BTS SW again._x000D_
2.
There Reset are(block/unblock)
several possibilities the BTS._x000D_
for the alarm activation. Therefore, a BTS Clock Frequency History feature has been developed.
3.
history If step 2
feature,does not
see help,
the replace
online help the alarming
of BTS Site module._x000D_
Manager).
1. Make sure that the module is properly
_x000D_ connected. If the Depending
module LEDondoes the possible reason,
not light up, follow the
the module instructions
is faulty. Checkbelow:_x00
the modul
_x000D_
2. Check the fault history._x000D_
1.
1. Block/unblock the BTS._x000D_
In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term a
_x000D_
2. Perform a power-off reset. that_x000D_
_x000D_
1. Block/unblock the module is causing the alarm._x000D_
3. If
If steps
the 1
basic and 2 do
accuracy not of help,
the replace
Iub signal the module but
is alarm.
correct, thatthere
is causing
istotoo the
muchalarm.
instability,
2. Replace the
Update the BTS with compatible SWmodule that is causing the
(check the SW versions see the active SW that is, the
version, jitter
and or wander
update is outside
the active the acc
SW version),
needed._x000D_
Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), un
_x000D_
3. Check
1. In casethe of aNTP BTSsetting._x000D_
equipment fault, the location might be:_x000D_
_x000D_
1.Retry the file update a few times._x000D_
Transport
2.
2.Check Checkthe part:_x000D_
the stratum
FTP accountparameter on the NTP server._x000D_
user settings._x000D_
1.
_x000D_ Retry the SW update._x000D_
3.Check thesnapshot
file and path names._x000D_
-2.
3.
Flexi
4.Check
Save
First,
Check
BTS the
checkthat
theFDD, the alarms
a GNSS
Flexi
administration
and
is of
BTS check
the
log TRS
configured
TDD:_x000D_the with
on the
download
and BTS status
Site
fileconnected.
server.
from the
Manager
_x000D_ andBTS act SWDLreport in the snapshot file.
accordingly._x000D_
-_x000D_
1. If there
Retry are
the no
SW alarms,
update._x000D_
Unblock the module with BTS Site Manager. check the TRS synchronization settings._x000D_
_x000D_
2. If other flash memory-related faults are currently active for the module that is causing the alarm, replace this module._x000D
To
FCM
_x000D_ cancel the fault, unblock the cell.
unit:_x000D_
_x000D_
Flexi
To cancel Zonethe Micro FDD,
fault, unblockFlexithe Zone BTS.Micro TDD:_x000D_
Unblocking the BTS causes a BTS reset.
-1. If the
Retry TDM
the reference
SW signal
update._x000D_ accuracy
Check the fault history and other active faults of the unit._x000D_ and the TRS are in order but the FCM unit is still alarming, run the fast tuning with BTS S
-_x000D_
2. IfIfthe alarm
other flash is still active after the
memory-related fastare
faults tuning is finished,
currently active reset
for the the site.replace
BTS, If the problem
the BTS. does not disappear in a few minutes, res
1. IfBlock/unblock
-Note: thatThis
does not the alarming
help, replace unit/module._x000D_
the FCM unit._x000D_
2. fault doesthe
Remove/reinsert notalarming
require any (special) actions.
unit/module._x000D_
_x000D_
3.
Note Replace
thatthe if the
the alarming
reason is unit/module.
in the transmission
Replace
1. Upgrade alarming
the systemunit/module._x000D_
module SW._x000D_network synchronization, replacing the faulty unit does not solve the problem. Furth
network,
_x000D_
2. not to a fault in the unit._x000D_
1. Replace
Check
_x000D_
Flexi Zonethe
the
Micro
unit._x000D_
otherFDD,active alarms.
Flexi ZoneIfMicro the ROM disk is corrupted, change the alarming module._x000D_
TDD:_x000D_
_x000D_
_x000D_
4. After
Replace
1. Check the thefault
the BTS. situation
other active has alarms.been If cleared,
the ROMyou diskmight need to tune
is corrupted, changethetheBTS master module._x000D_
alarming clock because the BTS master clock adjus
2. Block/unblock the alarming module. There are no recovery actions, therefore block/unblock can be tried once. If that does no
_x000D_
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module._x000D_
-_x000D_
2. manually
Block/unblock by changing
the alarmingthe DAC word (during
module. There are a site
no visit)_x000D_
recovery actions, therefore block/unblock can be tried once. If that does no
1.
-2.orCheck
with the tuning,
fast other active
in whichalarms.
the If themaster
BTS ROM disk clock isiscorrupted, achange
tuned in actions, the alarming
few minutes module._x000D_
automatically nearcan
thebeIub reference
once. If(normal tunin
Block/unblock the alarming module. There are no recovery
_x000D_ therefore block/unblock tried that does no
Note, however, that you should only use the fast tuning in case
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module._x000D_ the Iub reference signal is known to be a good one. Otherwise,
2. Block/unblock
_x000D_ the alarming module. There are no recovery actions, therefore block/unblock can be tried once. If that does no
1. Block/unblock the FSM._x000D_
Background
2. Block/unblock information:
the alarming The principle
module. is that in
There arethenomobile
recoverynetwork,
actions, thetherefore
synchronization goes from
block/unblock can be thetried
S1 interface. However,
once. If that does noin
2. If that
Note! does not
Perform the help,
steps replace
belowthe inthe
thefaulty
listed module.
order until the fault disappears._x000D_
operator. This does not harm system if the synchronization of the leased line service provider is also accurate or stable eno
_x000D_
Flexi
1. BTS FDD,
Restart Flexi BTS TDD:_x000D_
the BTS._x000D_
[User
1. defined]
2. Reset the System
If that does not help, Module._x000D_
replace the alarming module.In the case that FSP is alarming object, replace FSM because the alarm is
2. Replace
[User
_x000D_ defined] the System Module or FBBx module (according to fault source)._x000D_
_x000D_
Flexi Zone
[User defined] Micro FDD, Flexi Zone Micro TDD:_x000D_
Flexi
1. Zone Micro
Replace the FlexiFDD, ZoneFlexi Zone
Micro Micro TDD:_x000D_
BTS.
[User defined]
1. Replace the Flexi Zone Micro BTS.
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
Note: Perform the following steps in the listed order until the fault disappears:_x000D_
_x000D_
1. Make sure that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. Che
1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template._x0
_x000D_
Flexi
2. BTS FDD, Flexi
Download BTSsoftware
TDD:_x000D_
2. Check the two
_x000D_ faultdifferent
history._x000D_ packages so that the faulty file is removed from the BTS._x000D_
3. Download the software
_x000D_ again._x000D_
Flexi
_x000D_
1. Zone Micro
Replace FDD, Flexi
the alarming Zone Micro TDD: _x000D_
module._x000D_
Flexi
Check BTS
the FDD, Flexi BTS
frequencies' TDD:_x000D_
parameters against the BTS HW configuration. Check whether the connected radio supports the carrier
4. Replace
_x000D_
Perform the the SysteminModule.
recovery theTDD:_x000D_
following sequence:_x000D_
HW
Flexi
Flexi that
BTS might
FDD,
Zoneif Micro have
Flexi
FDD, limitations
BTSFlexi Zonethe in the
Microsupported
TDD:_x000D_ frequency range and bandwidth.
1.
1. Check
Check if the
the cable
signal connecting
is being recieved system module and radio module or the cable connecting the extension baseband module
1. Download
Replace
2. Replace thethe thecable._x000D_
correct
alarming Module._x000D_ reference clock source._x000D_
configuration._x000D_
System from the
2.
2. Check
Reset the BTS._x000D_
FTM status._x000D_
_x000D_
3.
Flexi
3. CheckBTSthe
Change thesynchronization
FDD,
the faulty
Fleximodule (FBBx
BTS TDD:_x000D_settings or of FR)._x000D_
the FTM unit._x000D_
3.
4. Replace
If
Note! this does
Perform the BTS._x000D_
not
the help,
steps replace
below FCM/FCT
in the listed (system
order untilmodule)._x000D_
the fault disappears._x000D_
_x000D_
1. Block/unblock the System Module._x000D_
_x000D_
1. Check
Flexi the
Zone Micro other alarms
FDD,site Flexi of the
Zone BTS
Micro and FTM and act accordingly._x000D_
_x000D_
Commission
Flexi
2. If Zone
there are the
Microno BTS
FDD,
other FlexiwithZonecorrect
Micro
synchronization-related IP TDD:_x000D_
addresses.
TDD:_x000D_alarms active, start the fast tuning with BTS Site Manager._x000D_
1. Replace
2. Check the thebackhaul
System connection.
Module.
Replace
3.
1. Resetuntil
Wait the theBTS.
site.the
Run fast tuning
module again._x000D_
is automatically heated to the required start-up temperature._x000D_
4.
1. Check
Check the
_x000D_ the reference
antenna cables signaland accuracy
connectors by measuring
toward the it with
MHA.a frequency counter
Fix or replace the (note:
brokenrequires a good timebase for the counte
parts. _x000D_
tuning._x000D_
2. If the fault has been active for more than two hours, check the environmental conditions of the site.
_x000D_
1.
5. Check
If the antenna
that does not help, cables
replace and theconnectors
system toward the MHA. Fix or replace the broken parts. _x000D_
module._x000D_
2. Restart
_x000D_ the MHA by blocking and unblocking the Flexi Radio (FR) Module._x000D_
_x000D_
1. Check
NOTE! theoperation
This antenna line affectsandall antenna
antenna line devices.
lines and Fix related
cells or replace theFR
to the faulty parts/devices._x000D_
Module, not just the faulty one. If the alarm reappears
2.
2. Restart
Flexi
The Zone
alarm the
Micro
isMHA FDD,by blocking
cancelled FlexionlyZoneatand
RF unblocking
Micro
Module TDD:_x000D_
resettheorFlexi
BTS Radio
reset. (FR) Module. _x000D_
Flexi
NOTE! BTSThis FDD, Flexi
operation BTS
affectsTDD:_x000D_
all antenna
This
1. fault is most likelycables,
the result of a BTSlines and cells
hardware related
problem or to the FR Module,
aline
reference source not just
that the faulty
is being one. Ifbythe
followed thealarm
BTS reappears
that is in a
1. Check
1. Check the
Identify the
the
antenna
antenna
currently cables,
selected
connectors,
connectors,
synchronization
antenna,
antenna, and
and antenna
reference antenna
source line
of
devices
devices
the BTS
that
that
with
can
might
the
interfere
cause
active
with RF signal._x000D_
interference
1818 fault. If it with
is a the RF signal._
transport-based
2. Check
_x000D_ the antenna line (TX-cable-antenna) impedance matching._x000D_
alarms
Replace
_x000D_ orthe
faults associated
alarming Radiowith Module.the respective time servers (If there is a fault associated with a network-based time server, it is
2. Check the antenna
IEEE1588-2008 master line (TX-cable-antenna)
clock impedance matching.
Flexi
Replace Zone theMicro
alarmingFDD,Radio Zone ifMicro
and the 1818
Flexi Module/MultiRadio fault
TDD:_x000D_ subsequently
Combiner. clears._x000D_
2.
1. If the
CheckatheBTS uses its
connection GPS reference source while the 1818 fault or ifand
the antenna.
1818 fault_x000D_
persists for more than two hours after corre
Perform Radio Module and resetintegrity of antenna
(block/unblock). connectors,
If this does notcable,
help, replace the alarming Radio Module.
2. Reset the BTS device. If the alarm persists, replace the BTS.
Perform RET calibration. If that does not help, replace the RET unit._x000D_
In case of
Perform RET1845: send valid
calibration. configuration
If that does not help, file toreplace
the alarming
the RET device.
unit._x000D_
In case of 1845: send valid configuration file
Perform RET calibration. If that does not help, replace the RET unit._x000D_ to the alarming device.
In case of
the alarming
the RET device.
unit._x000D_
In case of
the alarming
the RET device.
unit._x000D_
In case of 1845: send valid configuration file to the alarming
1. Block/unblock the radio module to give a power-off reset to the antenna line devices._x000D_ device.
If
1.that
Uploaddoesthe notcorrect
help, replace
SW to the thedevice
antenna (if line device.
possible) or Note:
perform if the
an fault
ALD source is RX/TX,
power reset replace the
(for example radio
by RF module.
blocking/unblocking)._x0
2. If thatthe
Update does SWnot to help,
the BTS. replace the antenna line device.
Check that the WCDMA master system module is connected to the system module when the SCF parameter "syncMaster" = "F
1. Check whether the heating element exists at all._x000D_
2.
"NotCheck
enough the radio
heaterresources
control connection and thatdisplayed
for cell detected." the heaterinisthe working._x000D_
alarm additional info:_x000D_
3. Replace
_x000D_ the alarming component.
Reset the MHA (by Radio Module block/unblock). If this does not help, replace the alarming module.
The cell might not be set up because not enough radio resources are detected._x000D_
Reset
Check MHA (by Radio
if all cables andModule block/unblock).
SFPs connecting In case
the radio this wont
modules help
to the - replace
system module the alarming
(or to the module._x000D_
extension baseband module - FBBx
Alternatively,
1. recommission
Check the functionality of the
the BTSantennawith line fewer cells._x000D_
device._x000D_
_x000D_
1. Check the functionality of the antenna line device._x000D_
"Not
2. enough
Check
_x000D_ the DSP resources
compatibility for cellthe
between detected."
antennadisplayedline device in and
the alarm additional info:_x000D_
the BTS._x000D_
1.
If Check thebaseband
extension
_x000D_ functionality moduleof the(FBBx)
antenna is line device._x000D_
used:_x000D_
2. Check the compatibility between the antenna line device and the BTS._x000D_
_x000D_
1.Ensure
3.
1. Check the
_x000D_ all cables
thatfunctionality
the (Power
of the and
given parameters Baseband
are
antenna inline bus range.
cables) have been connected _x000D_
thedevice._x000D_
valid
2.
to Check
the
_x000D_ FBBx theunit._x000D_
compatibility between the antenna line device and the BTS._x000D_
3. Check that the given parameters are in the valid range.
_x000D_
Block and
2. Check the unblock
compatibility the system
between module._x000D_
the antenna line device and the BTS._x000D_
3.
3. Check that the
If this does
_x000D_ not given parameters
help, replace are inunit._x000D_
the FBBx the valid range.
_x000D_
If extension baseband module (FBBx) is not used:_x000D_
1.Block and unblock the system module._x000D_
1. Check the other active faults._x000D_
2.
1. Replace
Check the the alarming
other activemodule._x000D_
faults._x000D_
_x000D_
2. Replace the alarming module._x000D_
_x000D_
1. Check the GPS receiver installation._x000D_
Note! Perform the steps below in the listed order until the alarm disappears._x000D_
2. Check
_x000D_ the GPS receiver status._x000D_
Flexi
3. CheckBTSthe FDD, Flexi BTS
connection TDD:_x000D_
between
1.
1. Check
Confirm the cabling
if the current (connected
applied tothe SyncGPS
configuration In receiver and FSM._x000D_
interface)._x000D_
is within the configured RF HW capabilities._x000D_
_x000D_
Flexi
2.
1. Check
Flexi Zone
Verify BTS Micro connections
FDD, Flexi and
Zone commissioning
Micro theTDD:_x000D_ settings._x000D_the file if it is missing. Reset the FR module._x000D_
2. Check
Flexi
3. BTSififFDD,
Block/unblock
the
theHWP1 2.048
Flexi
the
file
MHz
BTS isreference
BTS._x000D_
present
TDD:_x000D_ insource FRismodule.
workingDownload normally and the 2.048 MHz signal is available._x000D_
1.
2.
1. Check
If
_x000D_ the file
Check the
that isGPS
present,
TEMP receiver
and CALI installation._x000D_
block/unblock files arethepresent
RF HWand unit._x000D_
upload missing file(s). Reset the RFbased
Module._x000D_
4.
2.
3. If HW
Instructions
Check
If the configuration
the
problem are
GPS divided
receiver
continues isinto
confirmed
threestep
status._x000D_
after as2correct,
sections.has been thisperformed,
Execute problem
the steps is caused
from the
replace bysection
the eNB
FR HW SW.
chosenCheck
unit._x000D_otheronactive
the bestalarms._x000D_
knowledge and comm
3.
2. Replace
If
_x000D_ the files the are alarming
present: module.
block/unblock FR HW unit._x000D_
_x000D_
Instructions
3. If the problem are divided
is into threeafter sections. 1Execute
replacesteps from section chosen based on best knowledge and common sense t
Flexi
Section
Flexi
_x000D_ Zone
Zone A: Micro
Check
Micro onstill
FDD,
FDD, theobserved
Flexi
system
Flexi Zone
Zone Micro
module step
Micro TDD:_x000D_
side:_x000D_
TDD:_x000D_
FR HW unit._x000D_
_x000D_
1. Confirm
Replace if existing
Flexi applied configuration is within the configured RF_x000D_
1.
1. Check
Section
Flexi
HW Zone A:if Check
Block/unblock the connector
Micro
capabilities._x000D_ on Zone
the
FDD, BTS._x000D_
system
Flexi
Micro
seal is BTS.
module
Zone
properly
Micro
mounted and firmly in place.
side:_x000D_
TDD:_x000D_
_x000D_
2.
2.
1. Check
Instructions
Replace
Check if
ifBTS the
are Small
divided
theconnections
Flexi
connector Form
Zone into
seal Micro Factor
three
isand Pluggable
sections.
BTS. mounted and
properly (SFP)
Execute is properly
steps from
firmly in place. _x000D_connected/mounted
section chosen based in the System
on best Module. and
knowledge If SFP connection/mo
common sense t
1.
2.
3. Block/unblock
Check
Check
_x000D_ if the LEDBTS._x000D_
indicates the commissioning
faulty SFP settings._x000D_
(connected to System Module). Replace the SFP if it is faulty._x000D_
2.
2.
3. Check
Flexi BTSifFDD,
Replace
Block/unblock the
the SFP Flexi
Flexi
the (Small
BTS Micro
Zone
BTS._x000D_ Form BTS.
TDD:_x000D_ Factor Pluggable) is properly connected/mounted in the System Module. If SFP connection/mo
4.
3.
1. Check
Section
Check A:ifif Check
Block/unblock the
the optical
LEDthe RFcable
onindicates
system HW is properly
module
the faulty
unit._x000D_ connected/mounted
side:_x000D_
SFP (connected to Systemin the SFP._x000D_
Module). Replace the SFP if it is faulty._x000D_
4.
1. If
Flexi
5. HW
Clean
CheckBTStheconfiguration
ififFDD,
connector is
Flexiconnectors
optical BTS
seal confirmed
TDD:_x000D_
is that
properly then
are this problem
connected
mounted and to is
the
firmly caused
SFP.
in in place. by eNB_x000D_
Reset the RF
_x000D_ RF HW HW unit._x000D_
unit by using block/unblock procedures and ch
4.
2.
SW.
1. Check
If the
Checkproblem
Block/unblock the
other optical
continues
active
RF HW cablealarms. is
after properly
unit._x000D_ step 1 connected/mounted
has been performed, the
replace SFP._x000D_
the
_x000D_
2.
1.
5. Check if
Block/unblock
Clean
_x000D_ the
the optical SFPRF (Small
HW
connectors Form
unit._x000D_ Factor
thatstep are1, Pluggable)
connected is
to HWproperly
SFP.unit._x000D_ connected/mounted
Reset RF HW unit by block/unblock in the System Module. Ifand
procedures SFPcheckconnection/mo
if this sol
2. If
Section
3.
_x000D_ problem
Check B:if Check
the is LED
stillonobserved
the
indicates radio after
module
the faulty SFP replace
side:_x000D_
(connectedRF to System Module). Replace the SFP if it is faulty._x000D_
_x000D_
Flexi
1. Zone
Block/unblock
_x000D_ Micro FDD,
the RF Flexi
HW Zone Micro
unit._x000D_ TDD:_x000D_
1.
4.
2. Check
If
Section
1. Check
_x000D_ B:ifthe
problem connector
the
Checkis optical
stillon
connection seal
cable
observed
radio andis isproperly
properly
after
module
integrity step mounted
of1,
side:_x000D_
thereplace
antennaandRF
connected/mounted firmly
HW in
connector,unit.place._x000D_
in the SFP._x000D_
cable, and antenna._x000D_
Flexi
2. CheckZone
BTS if Micro
FDD,
the FDD,
Flexi
Small BTS
FormFlexi Zone
TDD:_x000D_
Factor Micro
Pluggable TDD:_x000D_
(SFP) is properly connected/mounted inthat
the isRF module.
5.
1.
2. Clean
Check
If there
problem
Check
the
if are optical
connector
more
continues connectors
than seal two
after is RF
step that
properlyunits
1 are
has connected
mounted
within
been the and
BTS,
performed,to SFP.
firmly in Reset
block/unblock
replace place._x000D_RF
the HWRF
the
RF HW unit
HW byunit
unit.block/unblock causing theIf alarm._x000D_
procedures SFPand connection/mounti
check if this sol
1.
3.
2.
3. Check
_x000D_
Flexi
Check
ResetBTSthe ifthe
Block/unblock
if the
FDD,
the
configuration.
BTS SFP
the RF
optical
Flexi cable
BTS
(Small
device.
HW
If
_x000D_
isunit._x000D_
properly
TDD:_x000D_
Form
the Factor
alarm connected/mounted
Pluggable)
persists, replace is properly
the BTS.in the SFP._x000D_ in the RF module. If SFP connection/mounti
connected/mounted
2.
4. Reset
If the B:
Clean BTS.
problem
the _x000D_
opticalcontinues
onconnectors after step
at the 1RFhas been performed,
module end. Resetinreplace the the RF unitHW unit._x000D_
Section
1.
3.
1.
3. if Check
Block/unblock
Check
Block/unblock
If
_x000D_ that does the not
the
optical
RF help,
radio
RF
HW cable HW
replace
module
isunit._x000D_
properly
unit._x000D_ the
side:_x000D_
Flexi connected/mounted
Zone Micro BTS._x000D_ theRF HW
SFP._x000D_ by using block/unblock procedures and check if th
_x000D_
1.
2.
4. Check
If the
Clean
_x000D_ if
problem connector
theMicro opticalcontinues seal
connectors is properly
after step
at RF 1mounted
has
module been and firmly
peformed, in place._x000D_
replace the RF HW unit._x000D_
end. Reset RF HW unit by block/unblock procedures and check if this solves the
Flexi
1.
2. CheckZone
Block/unblock
Section C:if Check
the SFP FDD,
thethe RF Flexi
HW
optical
(Small Zone
Form Micro
unit._x000D_
connection:_x000D_
Factor TDD:_x000D_
Pluggable) is HW
properly
_x000D_
_x000D_
2.
1. If problem
Replace
_x000D_ is still
the optical
BTS. observed after step 1, replace RF unit. connected/mounted in the RF module. If SFP connection/mounti
1.
3.
In Check
Flexi
Section Zone
startup: if the
Micro
Wait FDD,
until thecables
cable
Flexi
alarm isare
Zoneis not
properlyMicro
canceled.overly bent.
connected/mounted
TDD:_x000D_
This If
might they takeare, upinreplace
the30
to the optical cables since overly bending the optical fiber ca
SFP._x000D_
minutes._x000D_
2.
2. If the C:
OPTIONAL: problemCheckstill
Test
of optical
thepersists
fiber
connection:_x000D_
after
cable step
(for 1, replace
example, the
measure RF HW the unit.
optical attenuation)
4.
1.
1. Clean
Replace
_x000D_
Check the
if the optical
optical BTS.
Flexi BTS FDD, Flexi BTS TDD:_x000D_ connectors
cables are not at RF
over module
bend. If end.
yes, Reset
replace RF the HW unit
optical by
cable sincefrom
block/unblock overthe System
procedures
bending theModule
and
optical end.
check
fiberif Check
this the
solves
cables mea
the
damage
3. OPTIONAL:
_x000D_
If
2.
1. the alarm
OPTIONAL:
Block/unblock is Test
not
Test the fiber
canceled:_x000D_
thethe RF fiber
HW cable
cable
unit._x000D_(for example, measure the optical attenuation)
(for example, measure the optical attenuation) from System Module end. Check measuring e from the RF Module end. Check the measurin
Flexi
_x000D_
Section
check BTS
if C: FDD,
Check
environment Flexi
ofthe BTS
optical
temperatureTDD:_x000D_
connection:_x000D_
is within design limits for radio module._x000D_
3.
2.
1. OPTIONAL:
If the problem
Block/unblock Test
still
RF fiber
persists
HW cable
after
unit._x000D_ (for
step example
1 has beenmeasure
performed, the optical
replace attenuation)
the RF HWfrom RF Module end. Check measuring equip
unit._x000D_
If
1. the
WhenCheck
Flexi
_x000D_ alarm if
environment
BTS still
optical
FDD, persists
Flexicables
temperature
BTS after
are executing
not
TDD:_x000D_ isover
out ofthe
bend. steps
limits If yes
thenfrom
then
alarmsections
replace
is A,
expectedthe B,optical
and
andC,no replace
cable since
further the RF bending
over
actions module._x000D_
are needed. the optical fiber cables dam
2.
1. If
_x000D_
2. problem is Test
OPTIONAL:
Block/unblock still
the observed
theRF fiber
HW after step
cable
unit._x000D_(for 1, replacemeasure
example, RF HW unit._x000D_
the optical attenuation) from System Module end. Check measuring e
If alarm
Flexi
_x000D_ Zone
BTS is still
Micro
FDD, observed
FDD,BTS
Flexi after
Flexi executing
Zone
TDD:_x000D_ Microsteps TDD:_x000D_from sections: A,B,C replace the RF module._x000D_
3.
2.
1. OPTIONAL:
If the problem Test the
persists fiber
after cable
step (for
1 hasexample,
been measure
performed, the
replaceoptical the attenuation)
RF HW from RF
unit._x000D_ Module end. Check measuring equip
1. Check
Flexi
Check
_x000D_ Zonethe
Instructions if Micro
the configuration
are divided
FDD, Flexi
ambient intoand three
Zone
temperature download
sections.
Micro updated
Execute
TDD:_x000D_
is within design configuration
the
limits stepsfor the from if radio
required._x000D_
the module.
section chosen
When the based on best
ambient knowledge
temperature isand
out common
of limits, t
2.
1. Block/unblock
_x000D_
Block/unblock
_x000D_ the
the BTS._x000D_
BTS._x000D_
If
3. alarm
Flexi
1. Zone is still
Block/unblock
Replace
Section A: Micro
the
Check observed
FDD,
RF
BTS. on HW
the after
Flexi executing
Zone
unit._x000D_
system Microsteps
module TDD:_x000D_from sections: A,B,C replace the RF module._x000D_
side:_x000D_
2.
1. If that
Check
Replace
_x000D_ does
if air
the not
flow
BTS. help,
is notreplace
blocked the byBTS.some objects or walls. Remove any objects that are blocking air flow and mount the modul
1.
No Check
actionifisthe
_x000D_ connector seal is properly mounted and firmly in place. _x000D_
needed.
2.
2. If problem
Check if the is Small
still observed after Pluggable
step 1, replace RF is HW unit. connected/mounted in the System Module. If the SFP's connecti
3. Check if the
1. fan or Form
excessive sunlight
air flow Factor
isisblocked
causingby any (SFP)
overheating. object. properly
Install
Remove sunshield
any objects following mounting
that might instructions
be blocking the fanandor recommendations.
air flow._x000D_
3.
2. Check
Check ifif the
the LED
fan indicates is
connector theproperly
faulty SFP mounted.(connected Mount tothe Systemfan Module).properly._x000D_
connector Replace the SFP if it is faulty._x000D_
1.
4. Check
Check ifif the fan
thecontinues,
optical or air cable flowisisproperly
blockedconnected/mounted
by any object. Remove in the any objects that might be blocking the fan or air flow._x000D_
SFP._x000D_
3.
2. If the alarm
Check ifif the fan connector resetisthe radio mounted.
properly module byMount using the block/unblock._x000D_
fan connector
5.
1.
4. Clean
Check
If alarm the the optical
continues,fan or connectors
air
replaceflow is
the that
blocked
fan are connected
by
module. any object.to the SFP.
Remove Reset
any the RFproperly._x000D_
objects_x000D_ HW unit by using block/unblock procedures and ch
3. If
_x000D_
that the
might alarm be continues,
blocking the reset
fan orthe air radio module
flow._x000D_ by using block/unblock._x000D_
1.
4. Check
If the B: if thecontinues,
alarm fan or air flow replaceis blocked
the fan by any object. Remove any objects that might be blocking the fan or air flow._x000D_
module.
Section
2.
2. Check
Check ifif Check
the
the fan
fan on the radio
connector
connector is
is module
properly
properly side:_x000D_
mounted.
mounted. Mount the the fan connector_x000D_
1.
1. Check
Check
properly._x000D_ifif the
the environmental
connector seal temperature
is properly is withinMount
mounted the design
and firmly
fan
in limitsconnector
of the radio
place._x000D_
properly._x000D_
module. If the environmental temperature is be
3. If
_x000D_ the alarm continues, reset the radio module by using block/unblock._x000D_
2.
3.
1.
4. If the
Check
If alarm
if
the alarm the Small
continues,
environmental
continues, Form Factor
reset
replace the Pluggable
temperatureradio
the fan module
is
module. (SFP)
withinby is
the properly
using design connected/mounted
block/unblock._x000D_
limits of the radio in the IfRF
module. themodule.
environmentalIf SFP connection/mounti
temperature is ou
2.
3.
4. Check
Check
If
_x000D_ the ifif the
alarm the air flowcable
optical
continues, is not is
replaceblocked
properly
the byconnected/mounted
fan any
module.object or walls. in Remove
the any_x000D_
SFP._x000D_
1. Check
objects if the environmental temperature is within the designaccording limits of the radio module. If the environmental temperature is ou
4.
2. Cleanthat
Check
_x000D_ the
if the might
optical beconnectors
air flow blocking
is not blocked air atflow
theby and
FR any mount
objectthe
module end.ormodule
ResetRemove
walls. the FR HW tounit
instructions
any_x000D_ by using and recommendations._x000D_
block/unblock procedures and check if th
_x000D_
Instructions
_x000D_
objects that are
might divided
be into three
blocking air sections.
flow and Execute
mount the steps
module from the section_x000D_
according to instructions and recommendations._x000D_
2.
3. Check
Checkbased if air flow is not blocked by any object or walls. toRemove any_x000D_
chosen
Section
_x000D_
Instructions
objects C:if Check
that
excessive
are
might
on best
the
divided
be
sunlight
knowledge
optical
into three
blocking
is causing
and
connection:_x000D_
air sections.
flow and
overheating.
common Execute
mount
sense
the
Install
steps
module
minimize
from sunshield,
thethe
according
following
cost
section_x000D_ mounting instructions and recommendations.
and_x000D_
to instructions and recommendations._x000D_
time
1. effort. _x000D_
the optical cables are not overly bent. If they are, replace the optical cable,
3. Check
chosen
_x000D_
1. The VSWR
_x000D_
if excessive
based measured sunlight
on best knowledge is
at the RFand causing overheating.
common exceeds
(transmitter) Install
sense to values minimize sunshield,_x000D_
that the arecost and_x000D_
acceptable by since
the RF overly
module. bending_x000D_the optical fiber cab
2. OPTIONAL:
following
time
3.
2. Checkeffort.mounting
ifthe_x000D_ Test
excessive the fiber
instructions
sunlight cable and
isand (for
causing example,
recommendations.
the overheating. measure Install the optical
sunshield,_x000D_ attenuation) from the System Module end. Check the mea
Section
1.
3. Check
OPTIONAL:
_x000D_ A:the Checkimpedance
BTS Test on thesystem
connections matching
fiber module
cable
of
(for
Antenna Line
side:_x000D_
commisionning
example, measure
System
settings._x000D_
the
(replace elements that cause mismatch)._x000D_
optical attenuation) from the FR Module end. Check the measurin
following
3.
1.
2. To
Checkcheck mounting
ifthat
Block/unblock if the
the connector
the instructions
above-mentioned
BTS seal
(using isand recommendations.
thesteps
properlylocal have
mounted
BTS Site solved and
Managerthe problem,
isproperly
firmly block/unblock
inconnected
connection place. if_x000D_
a remote the RF module._x000D_
connection is not possible).
_x000D_
Section
1. Check
_x000D_ A: Check the on
Small system Form module
Factor side:_x000D_
Pluggable (SFP) is in the System Module._x000D_
2.
If Check
the alarm ifif the small
continues form-factor
after is pluggable (SFP) isand properly connected/mounted_x000D_
1.
1.
in
Check
_x000D_
Note:
Check
the Forcing
systemthat the theconnector
the
module. RF HW
Small If Form
thetoexecuting
seal work
Factor
SFP's
properly
under steps
such
Pluggable from
mounted
connection/mounting
sections
conditions
(SFP) isisis A, B,
firmly
might
properly
not
and
result
correct,
C,inreplace
inconnected
place. _x000D_
permanentin the
the FR
readjust_x000D_
module._x000D_
damage
System to the RF HW.
Module._x000D_
_x000D_
2. Check
Replace
_x000D_ if the small
SFP form-factor
module. pluggable (SFP) is properly connected/mounted_x000D_
the
1.
Flexi
in theconnection/mounting._x000D_
CheckZone
systemthe Microstatus FDD, of the
IfFlexi module
Zone Micro behind the faulty link (power
TDD:_x000D_ is not correct, readjust_x000D_ on, and so on)._x000D_
2.
3. Replace themodule.
SFP module. the SFP's connection/mounting
theCheck
_x000D_
1. Replace
Reset if the
the the RFLED
BTS.
connection/mounting._x000D_
Module indicates behind that thethe SFPoptical
faulty is faulty (connected
interface to system module)._x000D_
by blocking/unblocking it._x000D_
Replace
2.
3. Check
Check
_x000D_ the
the
if theSFP
Small
LED if it
Formis faulty._x000D_
indicates Factor that Pluggable
the SFP (SFP)
is faulty from both
(connected ends to (the
system System Module and the module behind the faulty link). Th
module)._x000D_
1.
4. Exchange
Check if the the alarming
optical and working links, and check where the SFP._x000D_
alarm is reported now._x000D_
_x000D_
Replace
2. the
If that does
_x000D_ SFPnot it iscable
ifclear is properly
faulty._x000D_
the fault situation, connected/mounted
replace the RF Module in the that causes the alarm._x000D_
5.
3.
1.
4. Clean the
Exchange optical
connectors,
the alarmingconnectors test
andisthe that
fiber
working arecable,
connected
links, to thewhere
replace
and check itSFP. Reset
ifinit the
is
the the is
faulty._x000D_
alarm RF HW_x000D_
reported now._x000D_
2. Check
_x000D_
unitIf by
_x000D_
if the
theblock/unblock
alarming optical cable
link remains
procedures
properly
the same,
and
connected/mounted
checkreplace thisthe
ifand System
solves the Module._x000D_
SFP._x000D_
problem._x000D_
5.
3.
1. Clean
Reset
Exchange
_x000D_ the optical
System
the alarmingconnectors
Module._x000D_
and that
working are connected
links, to
check the SFP.
where Reset
the alarm the isRF HW_x000D_
_x000D_
4.
2.
unitIf by
_x000D_ previous steps
theblock/unblock
alarming link remains do not the
procedures help, replace
same,
and check the
replaceif module
thisthe System
solves behind
the the faulty link.
Module._x000D_
problem._x000D_
3. If the B:
Section
_x000D_ alarming
CheckModule link
on radio changes, module replace the module behind that link.
side:_x000D_
_x000D_
4.
2. System
If the alarming link remainsis the onlysame,
the source causing
replace thethe alarm,Module._x000D_
System or if the actions mentioned above do not clear the fault situation,
1.
3. Check
If
Section
_x000D_ the B: if Check
alarmingthe connector
link
on radio changes, seal
moduleisreplace
properly themounted
side:_x000D_ module and behind is firmly
that link. in place._x000D_
2.
3. Check
1. If
Check if the small
if the connector
the alarming form-factor
link changes, seal isreplacepluggable
properly (SFP)
themounted
module and is properly
behind is firmly connected/mounted_x000D_
in
2. the
Check RF ifmodule.the small If the SFP's connection/mounting
form-factor pluggable (SFP) is properly is not correct, readjust the_x000D_
connected/mounted_x000D_
in the RF module. If the SFP's connection/mounting is not correct, readjust the_x000D_
1. Exchange the alarming and working links, and check where the alarm is reported now._x000D_
_x000D_
Check the alarms for the connected module.
2. If the alarming link remains the same, replace the System Module._x000D_
1. Check the cables between the System Module and the RF Module._x000D_
_x000D_
_x000D_
3. Check
1. If the alarming
the cables linkbetween
changes,the replace
System theModule
moduleand behind
the RF thatModule,
link. the cable between the FBBx Module and the RF Module,
2. Reset the alarming System Module._x000D_
_x000D_
1. Check the cables between the System Module and the RF Module, and the cable between the FBBx Module and the RF Mo
_x000D_
2. Replace the unit that causes the alarm (System Module or FBBx).
_x000D_
3. Reset
Check thethe site._x000D_
antenna mapping to the local cells in the commissioning file.
2. Reset the System Module._x000D_
_x000D_
1. Check the RP3-01 cable between the synchronization master and synchronization_x000D_
_x000D_
4. Replace
slave system themodules._x000D_
alarming System Module.
3. Check
1. Replace the the alarming
RP3-01 cable module
between (System Module).
the synchronization master and synchronization_x000D_
2. Check
slave system the alarms
modules._x000D_ in the synchronization master system module and act accordingly._x000D_
1. Reset
3. Check the the status of the module behind themodule._x000D_
faulty link (power on, and so on)._x000D_
2. Check the synchronization
_x000D_ alarms in the synchronization master system master system module and act accordingly._x000D_
1.
3. Switch
Reset to the recently active BTS configuration._x000D_
2. Check the
_x000D_ the synchronization
alarming fiber connection. master system module._x000D_
If OptIf is the source:_x000D_
2. Retry the SW update.
_x000D_
1. Check antenna mapping to the local cells in the commissioning file._x000D_
_x000D_
1. Check
2. Block/unblock the between
BTS._x000D_
1. Check the
_x000D_ antennacables mapping to the the System
local cells Module
in theand RF Module or
commissioning the cable between the FBB module and the RF Module (it
file._x000D_
3.
1.
2. Perform
Block/unblock
Check theblock/unblock
cables the BTS.
between on the
_x000D_ RF
the System Module._x000D_
Modulerelated and RF
2.
4. Check
Perform
_x000D_ loga for
BTS line code
reset. violation
_x000D_ (LCV) errors to Module or the_x000D_
optical links. cable between the FBB module and the RF Module (it
3.
1. Perform
Block/unblock
_x000D_ block/unblock
the BTS. on the
_x000D_ RF Module._x000D_
5.
2.
4. Replace
Check
Perform theathe RF module
configuration.
BTS behind the optical link._x000D_
_x000D_
3. Verify
Note:
_x000D_ SFP
Perform the reset.
(small steps _x000D_
form-factor
below inpluggablethe listedtransceiver)
order until the andBTS fiberfault
conditions.
disappears._x000D_
5.
2. Replace
Check
_x000D_ the the RF module
baseband busbehind
configurationthe optical relatedlink._x000D_
to RP3 link speeds.
If FSP
Note:
_x000D_ is the source:_x000D_
Perform the steps below in the listed order until the BTS fault indication disappears._x000D_
Flexi BTSthe
Perform FDD, Flexi BTSBTS TDD:_x000D_
1.
If
1.
Check
FSP
Note:
Reset thea System
is the
Perform System
other
source:_x000D_
the steps Module
active below
Module._x000D_
reset._x000D_
faults
in the and listed actorder
accordingly._x000D_
until the BTS fault disappears._x000D_
2.
1. If
Makethat
Perform
_x000D_ does
sure a not
that
System help,
the replace
plug-in
Module type the System
baseband
reset._x000D_ Module.
unit is installed correctly._x000D_
2.
3. Replace
Note:
Reset Perform
the the System
the
alarming steps Module._x000D_
below inunit._x000D_
baseband the listed order until the BTS fault disappears._x000D_
2. If that
Flexi
_x000D_ BTSdoes FDD, not Flexihelp, BTS replace the System Module._x000D_
TDD:_x000D_
4. Replace
Note:
_x000D_
1. Perform
Block/unblock the thealarmingsteps baseband
below in the unit.
listed order until the BTS fault disappears._x000D_
Flexi
1. Check
_x000D_ Zoneif Microfan orthe FDD, RFFlexi
air flow HW unit._x000D_
Zone
is blocked Micro
by some TDD:_x000D_
objects. Remove any blocking_x000D_
If
2. FBB
If
Flexi
1. the
Reset is
BTSthe
objects._x000D_ the
problem
FDD, source:_x000D_
still persists
BTS._x000D_ after step 1, replace the RF HW unit._x000D_
1.
1. Check
Perform
_x000D_
Depending theafaninstalled
onSystem
the HW/SW
Module
installed and version
reset._x000D_
commissioned compatibility and the HWsource(s)
synchronization compatibility listedwith the current
in section BTS configuration._x000D_
"Meaning", see the commissioned syn
2. Replace
Check
Flexi
_x000D_ BTSifFDD, the Flexi
connector
Flexi Zone
BTSisMicro properly
TDD:_x000D_BTS.mounted. Mount fan connector properly._x000D_
2.
3.
If If
Flexi
_x000D_
If
otherthat
Zone
alarm does Micro not
is still
alarms are help,
FDD,
observed
reported replace
Flexi Zone
then the FBB
Micro
reset radio
- recommission card.
TDD:_x000D_
module
the BTS bywith
the correct number
2.
1.
GPS Check
Reset
Checkreceiverthat
the the
(block/unblock)
other
(PPS BTSactive cellBTS
the parameters
BTS._x000D_
source):_x000D_ faults and from the
actfan Network
accordingly._x000D_ management systemofmatch_x000D_
cells per BTS_x000D_
4. If
_x000D_
the alarm
BTS HW is still observed
configuration then replace the module.
2.
1. Reset
If
Software
Flexi there
Zone the
and aBTS
isMicro GPS
hardware byreceiver
FDD, can(for
Flexi be
Zone
example,
blocking/unblocking
commissioned
reconfigured frequency,
it._x000D_
Micro TDD:_x000D_ atforthetheBTS power)._x000D_
setup site,where
note the following:
faulty TX isIf not the used._x000D_
GPS receiver is not locked to any satellite,
_x000D_
3.
The If that
installation
cells does
will(poornot
then help,
skyoperate replace
visibility).
in For
singlethe faulty
this,
mode the BTS.only
unless permanent
all the TX's cure
relatedis totochange
the the
proper GPS
cell antenna
are location. One indication of a fai
faulty._x000D_
Recommission
Flexi
3. CheckBTSthe FDD, the BTS
Flexi BTS
Network with the
TDD:_x000D_
management correct
system number of LCRs per RF Module.
alarms for the alarming local cell (LCR)._x000D_
_x000D_
Check
Define the
a other
valid TX active
power BTSlevel faults
value and in act radio
the accordingly.
network (RNW) configuration part of the site configuration file (SCF) and use th
_x000D_
Flexi
2. ThereBTSmight FDD,be Flexi BTS TDD:_x000D_
a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver._x000D_
_x000D_
4. Recommission
Perform the steps the
below BTSinto theensure
listed that order alluntil
parameters
the fault are correctly Ifconfigured.
disappears. after autonomous GPS power reset, the fault does not g
_x000D_
Replace
Flexi Zone theMicroalarming FDD,unit. Flexi Zone Micro TDD:_x000D_
_x000D_
3. There might be a malfunction in the BTS. Perform a BTS site configuration
reset._x000D_
Define
Flexi
Control BTS aInterface
valid
FDD, TX power
Flexi
not BTS level value
TDD:_x000D_
available:_x000D_ in the radio network (RNW) file and use the commissioning wizard in the BTS
_x000D_
Note! Perform the steps below in the listed order until the fault disappears._x000D_
1. The
Flexi
4. TheBTS BTS
GPS FDD,has
cable detected
Flexi and/or a malfunction
BTSconnectors
TDD:_x000D_ in the control interface of the GPS
might be damaged. Check the cable and the connectors._x000D_ receiver. A possible reason is that the BTS and the G
_x000D_
2.
1. Perform
Reset the a (remote)
System BTS
Module site
that reset
is for
causing the whole
the BTS._x000D_
alarm._x000D_
_x000D_
1.
1. Check
the fault name of the toggling BTS fault._x000D_
3.
2.
5.
2. Perform
Replace
There
Follow theathe
might powerSystem
be aifreset
instructions HW for
Module
fault the
of the whole
in that
the GPS
toggling BTS._x000D_
is causing receiver.
BTS the Check
fault alarm._x000D_
to clear the
the operation
problem._x000D_ and change the HW, if needed._x000D_
2.
1.
4. Replace
Check
The
_x000D_ cablein the
NetActfaulty
autoconfiguration
the GPS receiver isand enabled
the and
BTS if the
might required
be working license and commissioning
incorrectly. Check if the pins file of
arethe available._x000D_
connectors (on both
_x000D_
_x000D_
2. Check the autoconnection/autoconfiguration information with BTS Site Manager._x000D_
5. The
Flexi
External
Note! BTScable
Zone between
Micro
FDD,
2.048MHz
Detailed FDD,
Flexi
information the
BTSFlexi GPS
signal:_x000D_ Zone receiver
TDD:_x000D_
about the Microtogglingand the
TDD:_x000D_ BTS might be faulty. Check the situation and
frequency can be found in the alarm history file, which can be downloaded change the cable, if needed._x00
using
Flexi
3.
6.
1. Load
There
Reset
Check Zone the
and the Micro
might correct
be FDD,
BTS._x000D_
correct Flexi
faultZone
commissioning
atheHW contents of Micro
in the file
GPS
the toTDD:_x000D_
the BTS.
receiver.
commissioning Check the operation
file._x000D_ and change the the
GPS module, ifofneeded._x000D_
1. If
There
1. there
Replacemight is an
be
the external
two
BTS. reasons 2.048MHzfor the signal
fault:_x000D_ source commissioned at the BTS site, check BTS faults that device and act acc
7.
2. There
Replace
_x000D_
further
1. The mightthe
actions._x000D_
radio unit be
BTS. a HW
that shouldfaultonlyin the beBTS connected SystemtoModule. LTE Flexi CheckSystem the Module
operation is and
alsochange
connectedthe toSystem
WCDMA Module,
system if needed._x000
module. _x00
Flexi
_x000D_
Flexi BTS
Zone FDD,
Micro Flexi
FDD, BTSFlexi TDD:_x000D_
_x000D_
In
1. this case,
Block/unblock disconnect
the alarming the radio unit
module._x000D_ from the WCDMA system module._x000D_
_x000D_
1.
2. Check is
Reconfigure
There and
might correct
anthe befrequency
error a in the
thecontents
malfunction settings in of
commissioning the the
correctly
BTS. commissioning
with respect
Perform
file._x000D_ a BTS file._x000D_
to site
the Radio Module's capabilities.
reset._x000D_
_x000D_
Flexi
_x000D_ Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
In this
Check
2. If FSPcase, create
theorconfiguration the fault
commissioning
of the configured filecell.
with theorcorrect relation system If module - radio
is theunit and send the file tosystem
the BTS. Note
Perform
2.
FTM the FBB
Recommission
reference steps isthe
(TDM,
the
below BTS
SyncE
source,
inwith
the orlisted
the perform
ToPvalid order
as
FSP
until
commissioning
source):_x000D_
FBBfile.
the fault reset recovery.
disappears._x000D_ FCM/FCT fault source, perform module
_x000D_
To be
_x000D_ performed on the master RAT side:_x000D_
1.
3.
1. If
Ifbethere
steps
Check is
the an
1 and integrated
antenna2on dothe not
line transmission
help, replace
and antenna unitalarming
the
line (FTM) commissioned
device causes theatalarm._x000D_
module._x000D_
that the BTS site, note the following: The FTM unit operates so
Control
To
the FTM Interface
performed
synchronization not available:_x000D_
MasterRAT
priority side:_x000D_
setting) might be missing, causing the FTM's internal clock to drop to holdover mode. In this ca
_x000D_
2.
1. Fix
The
Check orBTSreplace
the has
antenna the faulty
detected lineaand parts/devices._x000D_
malfunction
antenna in antenna
line the control
device thatinterface
is causing ofFixthe
the GPS receiver.
alarm._x000D_ A possible reason is that the BTS and the G
_x000D_
1. Check
_x000D_
3. Perform thea RS485
radio IUANT
module interface
reset (onlyfor and
thethe master RATline devices. or
in sharing mode can request replace the faulty parts/devices._x000D_
for such an operation to be performed).
2.
2. Perform
Fix
Check or
TheZone alarm a
replace
the (remote)
alarms
isthe the
canceled ofBTS
faulty
the site
FTM
onlyZone reset
parts/devices.
when unit and
the RFact whole BTS._x000D_
accordingly._x000D_
Module is reset or ifdisappears.
the BTS is _x000D_ reset.
Flexi
Note!
3. Perform
Perform Micro
a power FDD,
steps
reset Flexi
below
for theinwhole Micro
the listed TDD:_x000D_
order
BTS._x000D_ until the fault
_x000D_
_x000D_
4. There
Replace might
parallel beRP3-01/CPRI
a HW fault in the GPS
fiber linksthe Receiver
toward oneor radio
the BTS. Replace
module so that thetheFlexi Zone Micro
maximum BTS.
mutual length difference between fiber
3. Check
Performthe synchronization settings the of
2. a power-off reset. _x000D_ FTM unit._x000D_
1. Check
synchronization the fans and ensure
master system that
module. ambient temperature on the site is acceptable. _x000D_
_x000D_
1.
3. Check the fan
2. stepsdoes
If that 1 and not2and do the
help, not connector._x000D_
help, replace
replace the alarming the module module. that is causing the alarm.
4. There
2. Replace mightthe be
fan. a malfunction in the BTS. Perform a BTS site reset._x000D_
Perform the steps below in the listed order until the fault disappears:_x000D_
_x000D_
1. Either
1. There
Check might enable
the fans the parameter actDistributedSite or switch toona the shorter fiber between the FSM and FR._x000D_
5. be and ensure that
an equipment the ambient
failure in the FTM temperature
unit. Check the operation site is acceptable._x000D_
and replace the unit, if needed. Note: Normally, the
2.
2. Restart
If that does the FSM.
not (frequent
help,
indication
1. Check activity
that the fan is replace
not BTS the
fault
blocked._x000D_ alarming
indication module.
activations/cancels instead of a stable BTS fault indication state) points to the in
_x000D_
2. Check that the fan connector is properly mounted._x000D_
If the
3. previous
If that does not steps help, do replace
not help,the there
fan.might be an equipment failure in the System Module. Check the operation and if perform
_x000D_
_x000D_
_x000D_
1. Check if the fan is not blocked._x000D_
2. Checkthe
Replace if the fan connector is properly mounted._x000D_
fan(s).
3. If that does not help, replace the fan.
The BTS did not start up successfully. _x000D_
_x000D_
The BTS did not start up successfully. _x000D_
If the fault is reported with alarm 7650 and SW is not consistent in the BTS, NetAct autonomously triggers an SW update with im
_x000D_
The BTSon
running did not startAfter up successfully. _x000D_
If the fault isthe
_x000D_
BTS.
reported with aalarm succesful 7650 SW andupdate:
SW is not _x000D_consistent in the BTS, NetAct autonomously triggers an SW update with im
1.
UpdateThe
running BTS
the
on will
BTS
the beSW,
BTS. onAir
unless
After with
a itthe
is
succesful previously-running
automatically
SW update:updated SW._x000D_
_x000D_ by NetAct.
If
2. the
SW fault
will is reported
be consistent with in alarm
the 7650 and SW is not consistent in the BTS, NetAct autonomously triggers an SW update with im
BTS._x000D_
1. The
Check
running BTS
on the will
the be onAir
other
BTS. active
After with
alarms the and
a succesful previously-running
act
SWaccordingly._x000D_
update: SW._x000D_
_x000D_
3.
2. The
SW
If that BTS
will
does be will report
consistent
not help, an in active
the
block/unblock SW fallback
BTS._x000D_ the systemfault, module._x000D_
but with alarm 7561. _x000D_
1.
None The BTS will be onAir with the previously-running SW._x000D_
_x000D_
3.
2. The
FSMr2:
SWis BTSbe
will If will
that report
does an
consistent notinactive
help, SW fallback
replace
the BTS._x000D_ the systemfault, but with alarm 7561. _x000D_
module._x000D_
If
FSM the
_x000D_
FSMr3: fault
fault
If the is source:_x000D_
reported
faulty cellwith alarm
is active
on theSW 7651
baseband and SW is consistent
extension module, in replace
the BTS,the theextension
operator module. must trigger an SW update to any availabl
3.
1. The
The
Reset BTS
BTS the will
will
Systemreport
be onAir an
Module with the
(note fallback
requested
that all fault,
SW
cells, but
running.
even with_x000D_
those alarm
that 7561.
are also _x000D_
operational, will betrigger
reset)._x000D_
If
Checkthe fault
_x000D_ the is reported
optical with alarm
connection between7651 and SW is consistent
the master LTE and peer in the GSM BTS, the operator
system modules._x000D_must an SW update to any availabl
2.
1. The
If
The
_x000D_ a SW
reset
BTS will
does
will be
be consistent
not resolve
onAir with in
the
the the faultBTS.
requested _x000D_
situation, SW replace
running. the System
_x000D_ Module._x000D_
If
1.
3. the
Wait
The
_x000D_ fault
for is
SW reported
start-up
fallback to with
be
fault alarm
completed
and the 7651
relatedif aand SWwill is consistent
synchronization
alarm master
be canceled._x000D_in the BTS,module
system the operator has been mustreset._x000D_
trigger an SW update to any availabl
2.
In
1.
2. The
the
The
If there SW
site
BTS is will
sharing
will
1858: be
be consistent
configuration
onAir with in
the the
where BTS.
requested
EFaultId_FaultyFcmConfigurationAl the _x000D_
LTE
SW system
running. module
_x000D_
after is connected to
synchronization the GSM
slave's recoverysystem module
reset, check viathe
theRP3-01
WCDMA system
cable be
_x000D_
FBB
Flexi
3. The
modules is
BTSfault
SW 2) FDD, source:_x000D_
fallback
the Flexi
optical BTS
fault and TDD:_x000D_
connection the related
between alarm the will
WCDMAbe canceled._x000D_
and LTE system modules._x000D_
2.
3.
If
1. The
Check
the
Reset the
Perform SW
fault the is
the stepswill be
alarms
reported
System consistent
in
below withthe
Module in in
(note the
synchronization
alarm 7651 BTS.
that _x000D_
(source master
all cells, as system
FSP)
even or
those module
7653 and
(source act
as accordingly._x000D_
FSP) in the
that are also operational, will be reset)._x000D_ BTS, NetAct autonomously triggers an S
_x000D_
Perform
3.
4. The
Reset SW the
the steps
fallback below
fault
synchronization in the
and thethe
listed
listed
master related
order
order
system alarm
until
until the
the
will
module. be
fault
fault disappears._x000D_
disappears._x000D_
canceled._x000D_
to
2.
Not
If
In the
If
the
sync
_x000D_ a SW
reset
tracking
fault
hub version
does not
isconfiguration,
reported running
resolve
satellites:_x000D_withincheckon
alarm the
the BTS.
fault
7651
alsoorder situation,
if(source
the until
radio replace
as FSP)
master the FBBx module._x000D_
ordisappears._x000D_
7653 (source
system module as FSP) in the
(WCDMA) BTS, NetAct autonomously triggers an S
is working.
_x000D_
Perform
OR_x000D_
1. The the
most steps
common below reason the for listed
this fault indication the fault
is that the GPS antenna installation has not been done properly, that is, the
to
Survey
If the
the
_x000D_ SW in
fault version
progress:_x000D_
isthereported running
with on
alarm the BTS.
7651 (source as FSP) ordisappears._x000D_
7653 by (source as FSP) in the BTS, NetAct autonomously triggersantenan S
1. Replace
antenna
Perform
1. Do has
the
nothing. steps FBBx
a The
good belowmodule.
sky
alarm visibility,
in
isonthe listed
informative the order
problem
only.until might
the
Normally, bethe
fault caused
GPS receiver installing runsthe theGPS survey antenna
for two tooreasons:
close toa) the transmitter
somebody has star
to
No
2. the
There
_x000D_ SW
stored might version
position:_x000D_
be running
abelow
malfunction the BTS.
in theorder GPSuntil receiver. Perform a (remote) power reset for the GPS receiver._x000D_
time
Perform
1. One during
ofthe the first
steps
GPS start-up._x000D_
receiver in the listed
settings is incorrect. the
Using fault disappears._x000D_
the manager SWand of the GPS the receiver, module,
set the receiver to store the positi
3. There
Position
2. Ifrevert might be
questionable:_x000D_
the isautomatic a HW
survey fault
takes in the GPS
placestorage every receiver.
now andCheck then, the operation change that GPS if needed._x000D_
_x000D_
If
Tothere
_x000D_
1. The GPS noreceiver
changes, tick mark DC has in the
Voltage
valid position
should
position be
data enabled
butselection,
it isfor not the itGPS
reporting
properly
mightAntenna
in
be an
receiver
line
indication
runs
Line.
with the the site/self
information
thesurvey
sky visibility
estimated every
from
is
timepoor
thethe and
GPS
actual
according
receivervt
satellite
install
EEPROM
installation the GPS a antenna._x000D_
invalid:_x000D_
is poor one - the GPS receiver turns the PPS reference OFF every now and then during the site survey. This mean
Flexi
instructions
To
3. The
1. theZone
Ifrevert GPS
GPS Micro
changes, and ifFDD,
there
the
installation
receiver has Flexi
are
parameter
is Zonebut
deviations
good
detected Microthewith TDD:_x000D_
the actual
Communication3gppEnabled
automatic
a malfunction theinstallation,
in survey must
still takes
EEPROM re-install
memoryplace ofthe
be enabled theGPS
every for antenna.
now
GPS the
and then,Note
reporting
receiver. that
Antenna
there
Perform might even bewhen
Line.
a (remote) the GPS
a malfunction
power an
in
reset
Perform
_x000D_
4.
2. There
Trigger the
If the aactions
might
SW updatesteps be below
detailed
a HW for in in
fault
BTS the
thein listed
toprevious
the
the GPS order steps
requested until
receiver. dothe
SW not fault
Check
version. disappears._x000D_
correct thethe situation,
operation andtherechange might thebeGPS a HW fault inifthe
module, GPS receiver. Check
needed.
NotThere
2. tracking might satellites:_x000D_
be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver._x000D_
Depending
1. There
3. The most might on the
be ainstalled
common HW reason fault and in commissioned
for thisGPS
the faultreceiver.
indicationsynchronization
is thatthe
Check source(s),
theoperation
GPS andsee
antenna the commissioned
installation
change the GPS has not synchronization
been
module, ifdone
needed. properly,optionthatbelow
is, the
_x000D_
antenna has a good sky visibility, the problem might be caused
Fault 4180 is raised if switch setting is not successful. After the fourth try, group fault 3003 is raised. If there are other working by installing the GPS antenna too close to the transmitter antenc
GPS
2. There receiver
might (PPS
be a source):_x000D_
malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver.
Note:
1. Check Perform the GPS the steps
receiver below in the listed order until the fault disappears._x000D_
installation._x000D_
1)
2.
Check Verify
Check if
thethe the IP address
GPS receiver
transport is properly
related status._x000D_
configuration configured
(C-Plane at the
address, BTS._x000D_
U-Plane address, Transport network id). If the fault was raised at s
2)
3. Verify
Check if the the Real-time
connection Performance
between the Management
GPS receiver entity
and is operational and available._x000D_
FSM._x000D_
1.
3) One
If theofabove the most havecommon been verified, reasons thefor this fault
operator canindication
reset the(especially
BTS at a suitable occasional time. indications) is that the GPS/GNSS antenna i
_x000D_
the GPS/GNSS antenna. Note that even when the GPS/GNSS antenna has a good sky visibility, the problem
The PHICH
FTM reference (Physical asHARQ
(ToPpossible Indication Channel) transmission power boost can be increased
source):_x000D_ by reducing the might
configuredbe caused
boosts
2. Check the other alarms/fault indications of the GPS/GNSS receiver and BTS and act accordingly._x000D_
1. Check
Perform that
network the signal
optimization. is being received from the ToP
3. There might be a malfunction in the GPS/GNSS receiver. Perform a (remote) power reset for the GPS/GNSS receiver modul Master._x000D_
2.
4. Check
1) If therethe
Check the is only FTM
GTP-U thestatus._x000D_
alarming
path supervision GPS/GNSS receiver connected
configuration of the eNB.to_x000D_ the GPS/GNSS antenna, check the antenna power feeding se
3.
of
2) Check
the
Check other the
the synchronization
receivers
supervised is OFF)._x000D_
network settings element of the for FTM
proper unit._x000D_
operation._x000D_
Note:
_x000D_ Perform the steps below in the listed order until the alarm disappears:_x000D_
5.
3)
1. Check
Check the
the hub connection
communication
connection between
with equipment
MME, GPS/GNSS in between receiver thethe module
eNB S1and and theGPS/GNSS
supervised antenna. Note that one antenna might be share
network element._x000D_
eNB is
Note: Perform
receiver. Sync_x000D_ theslavestepsand below in thebased
rfsharing is on whether
enabled:_x000D_
listed order until the BTS link
faultisdisappears:_x000D_
broken accordingly._x000D_
2.
1) Check
Remove
1.Check theif the
the MME
rootthe
connection is
cause operational._x000D_
with that ispath
adjacent leading to a SyncHub slave from being linksynchronized._x000D_
6.
1.
3. Perform
Check
Check ififisathe
whether local/physical
speed transport
and power
duplex reset isBTS,
setting forofthe
based
alive._x000D_
theperform
on whether
alarming
eNB S1remote GPS/GNSS
port
the X2 receiver
is re-commissioning
consistent
is broken respectively._x000D_
withmodule._x000D_
the switch portorthat is connectedthe directly to thetoeN
2)
2.
7.
2. If
Check
There
Checkthere might thea need
adjacent
be asteps
the configuration to change
HW below BTS
fault is settings,
ininthe
of transport GPS/GNSSeither
operational._x000D_
addresses antenna
at MME._x000D_ and/or possible antennavia lineNetAct
splitter, un-commission
possible line amplifier eNB prior
or lightning r
_x000D_
Note:
_x000D_ Perform the the listed order until the BTS fault disappears._x000D_
8.
If There might be a HW fault ina the GPS/GNSS receiver module. Check theverify operation and change the GPS/GNSS IPreceiver
addressmo
If this
_x000D_
FlexithisBTS fault
fault FDD, happens
happens Flexiright BTSafter
right after a commissioning
TDD:_x000D_ commissioning or or a a configuration
configuration change, change, verify the the following
IP address configuration
of the adjacent data: BTS. of
1. Check
Block/unblock the commissioning parameters with the BTS Site Manager Commissioning_x000D_
Flexi BTS FDD,the
Wizard._x000D_
BTS._x000D_
_x000D_
Block/unblock the BTS._x000D_
_x000D_
Check
Flexi the connection
Zone Micro FDD,with Flexithe Zone iOMS Micro or the third party tool.
TDD:_x000D_
_x000D_
2. Load the correct commissioning file to the BTS.
1.
Note:
Flexi Check Perform
Zone and Micro update
theFDD, stepsconfiguration
below
Flexi Zone in the parameters
Micro listed order
TDD:_x000D_ related
until the to cell
BTSbandwidth and channels._x000D_
2.
For Reset
_x000D_
1. Check failureand the BTS._x000D_
update configuration
in subscriber trace session parameters related to cell bandwidth
activation/deactivation, based on the anderror
channels._x000D_
cause provided as part of the additional info fo
3.
Flexi
2. Retry
Reset
- "SubscriberBTS configuration
the FDD, Flexi BTS
BTS._x000D_
& Equipment push._x000D_
TDD:_x000D_
Trace feature not enabled": Enable theBTS subscriber trace feature at theconfigured
BTS. Any at events correspondin
Check
1. Check and ensure
the otherinactive that the PLMNs
BTS faults. that have been listed with this fault and that have been BTS for one or mo
-3."trace
Retryreference
configuration use,push. trace cannot_x000D_ be started": This problem is out of the scope of what can be fixed at the BTS, and is with
2.
same Reset
1.Check Traceifthe the System
maximum
Reference Module number
Number. by blocking/unblocking
Aofpossible
LNADJ solution objects has isit._x000D_
tobeen reached. If all
try deactivating yes, check if there
subscriber traces areand LNADJ objects
activating them that can be man
again._x000D
3. Update
_x000D_
-Check
"max ifnumber maximum and activate
of UE number the SW
trace sessionof LNADJWto the BTS._x000D_
reached, trace cannot
was reached. If yes,becheck
started": This are
if there problemLNADJW is outobjects
of the scope
that can of bewhat can be deleted.
manually fixed at tT
4. Checkif(which
2.Check
sessions the theSW is files._x000D_
maximum the number number
maximum of LNADJL of objects
active has beentraces
subscriber reached. If yes, check
supported at the ifBTS
there
at are
any LNADJL
point in objects
time) at related
the BTS. with Lt
Tryca
Check
5. Replace if theFSM._x000D_
maximum number of LNRELW objects has been reached. If it has been, check if there are LNRELW objects that
- "Trace session cannot be started due to ongoing handover for the UE" OR "Trace session cannot be stopped due to ongoing
_x000D_
Check
NMS._x000D_ if:_x000D_
Flexi
1) the
_x000D_ Zone
Add the LNRELmaximum Microobject FDD, pointing
number Flexi Zone
of LNRELW to the Micro per TDD:_x000D_
correctcell neighbor
and WCDMA carrier
to allow thefrequency
handover has already
or enable thebeen reached
UE-based ANR. (is greater than or equa
1.
For Check
makes failure spacethe other
for new
in cell/interface activeLNRELW BTS faults.
object
tracetosession _x000D_
per cell and WCDMA
activation/deactivation, carrier frequency._x000D_
based on the error cause provided as part of the additional info
Reset
2.
2) Reset (block/unblock)
the maximum the feature BTSnumber the BTS
byisBlocking/Unblocking recover the faulty
it._x000D_ cell.of: psHoAllowed,
- "Cell trace notofenabled":
mobility parameters
Enable (either
the cell trace feature at the BTS. srvccAllowed)
Afterwards,oftry LNRELW
again toper cell and
activate theWCDMA
requiredcarrie cell/in
3. Update
Block/unblock and activate
the BTS. the SW to the BTS._x000D_
- "trace reference in use, trace cannot be started": This problem is out of the scope of what can be fixed at the BTS and is within
4.
theCheck
1. same the
Check forTrace SWReference
E-UTRAN files._x000D_cellsNumber.
that operate A possibleon thesolution
same frequency is to try deactivating
layer and use all cell
the sameand interfaces
PCI and that traces.areAfterwards, try activat
in close vicinity._x00
5.
2. Replace
- "max
Reassign number Flexi
PCIs Zone Micro
of cell/interface
for the BTS.
discovered trace cells. sessions reached, trace cannot be started": This problem is out of the scope of what can b
cell/interface trace sessions (which is the maximum number of active cell and interface trace sessions put together supported a
If the GPS is configured as reference clock, perform the following:_x000D_
1.
Note: Check the GPS
Perform receiver
the steps belowinstallation._x000D_
in the listed order until the alarm disappears._x000D_
2.
1. Check
Check the
the GPS receiver
availability of status._x000D_
the adjacent BTS._x000D_
Note:
3. Check Perform
the the steps below
connection between in the
thelisted order
GPSBTS._x000D_
receiveruntil theFSM._x000D_
and alarm disappears._x000D_
2.
1. Check
Check the connection
connectivity to with
the the
related adjacent
adjacent BTS._x000D_
_x000D_
Note:
3. Perform and
Disconnect the steps
reconnectbelowthe in adjacent
the listedBTS.
order until the alarm disappears:_x000D_
2.
If
1. Check
the
CheckTOP other
signalfaults._x000D_
is
availability configured
of MME._x000D_ as reference clock,until
perform the following:_x000D_
Note:
3. Check Perform the steps below in to
thethe
listed order tothe
thealarm disappears._x000D_
Check
2.
1. Check
Check thethe
other
the
parameters
connection
faults on
availability to ofrelated
the
MME TOP
and
MME._x000D_server.X2 interface
BTS._x000D_ adjacent BTS._x000D_
4.
Check
3. Reset
Check the
the BTS.
root cause reported in the fault. Based on the root cause, these necessary actions must be taken:_x000D_
2. Check the
_x000D_ the parameters
connection with related to S1 interface in the BTS and MME._x000D_
MME._x000D_
4.
Note:
3. Reset the BTS.
Perform
and belowMME. in the listed order until the alarm disappears._x000D_
1.
1. "S1
Check linkthe
failure" -reconnect
Check
availability of for any active 6202 "Transport layer connection failure in S1 interface" faults. Take necessary action
MME._x000D_
Check
2. the value of the "rimStatus"
"Network parameter
- Checkinthe LNADJG objects to findreconfiguration
all impacted RIM associations._x000D_
2. Check theReconfiguration
_x000D_ connection withInduced" MME._x000D_ most recent network made w.r.t changes in the list of PLMNs
3.
Check
3. "MME Configuration
the value
Disconnect and Changes"
ofreconnect
the "rimStatus" MME. - Check the most recent configuration changes made at MME(s) with which the eNB is conne
parameter in LNADJG objects to find all impacted RIM associations._x000D_
If only a few LNADJG objects have "rimStatus" Unavailable, check if LNADJG identifiers (cell global id) of related GERAN cells
_x000D_
This
_x000D_ fault does not require any (special) actions.
If many Technical
Collect
_x000D_ LNADJG Logs objects fromhaveBTS "rimStatus"
to clear anUnavailable,
alarm raisedcheck by this thefault.
connectivity to GSM network (MME<->SGSN<->BSC)._x000
If many
Flexi BTSLNADJG
FDD, Flexi objects
BTShave "rimStatus" Unavailable, check the connectivity to GSM network (MME<->SGSN<->BSC)._x000
TDD:_x000D_
Source: _x000D_
-_x000D_
FCM/FCT: Perform eNB reset._x000D_
Flexi
-Flexi
FSP/FBB:BTS FDD, Flexithe
Change BTS cellTDD:_x000D_
configuration to decrease call processing load._x000D_
Note: BTS FDD,
Perform Flexi
the stepsBTS TDD:_x000D_
below in the listed order until the fault disappears._x000D_
_x000D_
Flexi
Note! BTS FDD,
Perform Flexi
the steps BTS TDD:_x000D_
1. Reset
Flexi
Note: Zonethe
Perform System
MicrotheFDD, Module._x000D_
steps Flexi
below Zone Micro TDD:_x000D_
inModule._x000D_
the listed order until the fault disappears._x000D_
1.
2. Reset
Flexi BTS
Replace the
FDD, System/Baseband
the Flexi
System BTS TDD:_x000D_
Module or FBBx module (according to the fault source)_x000D_
None
1.
NoReplace
Note:
_x000D_
2.
Perform
actions
Replace
the the
are
the
System/Baseband
steps below in the
required
System
Module._x000D_
listed order until the fault disappears._x000D_
_x000D_
1. Reset
Flexi ZonetheMicro
System
FDD, Module._x000D_
_x000D_
Reset
Flexi
2. the BTS
Zone
Replace Micro when
the theFDD,
System allFlexi
required
Module ZoneorBTSMicro
FBBx IPmodule
settings(according
TDD:_x000D_ have beentoset. the fault source)_x000D_
Note:
Flexi Perform
Zone Micro steps
FDD, below
Flexi in
Zone the listed
Micro order until the fault
TDD:_x000D_ disappears._x000D_
1.
1. Reset
_x000D_
1) Check
Reset thethe
if BTS._x000D_
the
the steps far end
BTS._x000D_ has BFD switched on._x000D_
Perform
2. If
Flexi
2) the
Check fault
Zone Micro
cabling below
persists,
FDD,
and in the
replace
Flexi
network listed
the
Zone BTS.order
Micro
connections until the fault
TDD:_x000D_
toofthe end.disappears._x000D_
2.
E1
1. Replace
interfaces:
Reset the the Flexi
Check
BTS._x000D_Zone
that Micro
the BTS.
interface type thefar
far-end interface is also configured to be a framed E1 interface. If this is not t
Perform the steps below in the listed order until the fault disappears._x000D_
2.
1.
1. Replace
Check
Reset the Flexi
thatBTS._x000D_
the Zone Micro BTS.
the cables are connected to the correct connectors.
JT1 interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. If this is not the ca
2. Check
1. Replace thatthethe
Flexi Zoneare
cables Micro BTS._x000D_
connected to the correct connectors._x000D_
2.
2. Check
Check that
that the
the interface
interface at
at the
the far-end
far-end interface
interface is is switched
switched on. on._x000D_
3.
1. Check whether there are active alarms at the far end. If there are, follow Ethernet
the instructions forofhandling
the unit.those alarms._x000D_
3. Insert
Use Check an
the BTS SFP
Sitemodule
whether there are
Manager withto the
active
checkcorrect
alarms
whichlaserthetype
far (class
atinterfaces end. If 1)
have to the
there
been are,Gigabit
follow the
configured interface
as instructions for handling
synchronization sources. those alarms.
Use
Flexi BTS
Zone Site
Micro Manager
FDD, to check
Flexi which interfaces have been configured as
4.
1. To verify
Check
synchronizationthat thatthethe hardware
cables
sources. are Zoneof theMicro
connected TDD:
interface
to theunit works
correct correctly, connect a loop cable and check whether the alarm disappear
connectors.
1. Plug-out/plug-in
Execute general SFP
configuration module. checks:_x000D_
2. Check whether the interface at the far end is switched on.
-2.
3. Checkwhether
Configuration
Check
None. for SFP validity
of CMP
there are (could
server IP be
active wrongat
address
alarms type).
and theport
farand
end.DNS server
If there are,IPfollow
address._x000D_
the instructions on handling those alarms.
For
-3. all interfaces,
Insert a
Configuration compliant
of do as
routingSFP follows:
module.
entries towards remote peers._x000D_
4. To
1)Checkverify that
cablingofand the hardware
network of the interface
connections unit
to the far works
end. correctly, connect a loop cable and check whether the alarm disappear
- Configuration IPSec policies towards remote peers._x000D_
1. Check
2)Check
Check
1)Inspect that
Link
remotedetailsthe
OAM
peerscables
of event-
theand are
type andconnected
Linkcritical
intermediate
of the OAM tostate
networkthe correct
event elements
through connectors.
information. interconnections._x000D_
online configuration management.
2. Check
3)Check
Check
2)Check the whether
Ethernet
Link LDAP OAM the interface
interface
connection
state at theof
configuration
towards
information farthe
the end
at is switched
local
Certificate on. side.
andRevocation
interface. remote Listnecessarily
server._x000D_
Replace
3. Check the
whetherfaulty SFP.
there Note that
are active only the
alarms at SFP might be faulty, not the entire hardware unit.
4)Insert
Check
3)Check acabling
DNS Link OAM
names._x000D_
and loopback.
network connections tothethefarfarend.
end.If there are,
follow
1. Clean
Check
4)Check the
thetheinstructions
cables
size
Ethernet of the and onconnectors.
file
interface handling
at those alarms.
the Certificate
configuration atRevocation
local and remoteList server.
side.
4. To verify
5)Insert
Check that a Link that
the OAMthe hardware
loopback.
configured of the
interface type interface
matches unit works correctly,interface
the configured connect type of the far end. If this is the case, the problem is
a
2.loop
Check cable
thatand the check
connectors whether arethe alarm connected
properly disappears.to the unit.
Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these
Monitor
3.
1. Checkthe that
the received
the cable
intermediate clock quality. to thenetwork
connected
transmission interface forinalarms
question is not damaged
indicating and isand
the root cause within the the
follow specifications.
instructions for handling thes
Replacing faulty hardware:_x000D_
4.
2.
1. Follow
To check the signal
inthe in thehardware,
thetransmit network and check
connect whether
a loop inany
cable andother alarms
check that concerning the fault
no alarms appear forare
thisoninterface.
(such as Laser End of Life).
1) Re-Plug
Check cabling. expected transport unit referenced the alarm text._x000D_
_x000D_
2) Check
Check CCM configuration at remote peer.
1)
2. In casecabling.
there is a unit present in the slot, remove it from the slot_x000D_
2)
and Check
Check plug
youritconfiguration
back in. If the
username atunit
and remote peer.
is still
password. not recognised and the alarm_x000D_
remains, replace
Provide the certificate. the faulty unit with a new one. _x000D_
_x000D_
1. Check the network
De-commissioning betweencommissioned
previously both BFD peers for physical link failures or misconfigurations.
hardware:_x000D_
1. Re-commission
Check the BFD configurationto remove the hardware
at local end. unit referenced in the alarm text._x000D_
2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.
_x000D_
Note 1: Before
Try with re-commissioning,
local management or site the hardware
support equipment.unit must not be present in the slot._x000D_
Note 2: "Send all parameters" is required for re-commissioning.
Confirm
check that
the Ethernet Synchronization
connectivity master/slave setting are correct on the BTS and backhaul equipment.
to NTP server_x000D_
Note: Flexi
check Zone
the NTP Microconfiguration
server BTS only supports
at BTS.slave mode.
check that the vendor BTS certificate expiry date and renew it.
Update trust anchors.
1. Check the fault name of the toggling FTM fault from the Fault name of_x000D_
this fault._x000D_
_x000D_
Flexi
2. Follow Zonethe Micro FDD, Flexi
instructions of theZone Micro FTM
toggling TDD:fault to clear the problem._x000D_
1. Confirm
_x000D_
Check that SyncE
the cable is desired as a synchronization source.
connectivity._x000D_
2.
Note!
CheckConfirm Detailed
the TOP that information
eNB configuration
configuration._x000D_about the settings
toggling for frequency
ssmEnabled canisbe correct.
found in_x000D_
3. Troubleshoot with Backhaul provider on the reason SSM errors.
alarm history file, which can be downloaded using BTS Site Manager. The log file is available with Snapshot._x000D_
SW upgrading:_x000D_
- Upgrade the FSM SW release to the latest version that includes the support for the new external tranport device variant._x000
_x000D_
An
UnitIPvariantTrafficreplacement:_x000D_
Capturing session is ongoing and base station traffic is captured to a local Ethernet interface or into a file on the ba
-Operator
Replacecan the check
unsupportedthe current device variant
remote to another
tunnel endpoint oneparameter
that the currently running SW release supports. on NetAct or BTS SM
(ipSecBkupTunCurrRemoteEndpoint)
1. Check which Radio Modules are in an incorrect frequency._x000D_
2. Replace
Note! Perform the theincompatible
steps below Radio
in the Module(s).
1. Change the BTS configuration._x000D_
Note: This fault does not require any (special) actions._x000D_
2. Reset
Check thethe BTS.
fault history andTDD:_x000D_
other active faults of the unit._x000D_
Perform
1. Checkthe thesteps
fan and below in the listed order until the BTS fault disappears._x000D_
connector._x000D_
1.Check
2. the cables toward the radio module._x000D_
1. Replace
Checkthe
2.Reset the thefans
radio
fanandmodule.connector._x000D_
module._x000D_
2. Replace
3.Remove
Flexi BTS FDD, the faulty
the fan module.
Flexi unit._x000D_
BTS TDD:_x000D_
_x000D_
1. Retry the SW update._x000D_
If the FSM is the fault source:_x000D_
Flexi
2.
1. If
Reset Zone
other the Micro
flashSystem FDD,
memory-relatedFlexi Zone
Module (note Micro
faults
thatare allTDD:_x000D_
active for the
cells, even alarming
those whichmodule are also atoperational,
the same time,will replace the alarming module._x000D
be reset)._x000D_
1. Try
1.Remove
_x000D_ to block/unblock
the faulty the cell.
unit. _x000D_
2.
2. If a to reset does not resolve the fault situation, replace the System Module._x000D_
1. Try
Flexi Zone block/unblock
Block/unblock
_x000D_ Micro the FDD, the
FlexiFR
System module._x000D_
Zone
Module. Micro TDD:_x000D_
3.
1. If it
Retry doesthe not
SW help, reset
update._x000D_ the BTS.
If the
1. RunFBB fastistuning
the fault withsource:_x000D_
BTS Site Manager._x000D_
2.
1. If otherthe
Replace flash
the memory-related
System Module. faults thatare all active for the BTSwhich at the same alsotime, replace the BTS.
Recommission the LCRs in a(note
Reset
_x000D_ System Module way that only cells,
one even
sectorthosetype is usedare in one operational,
RF Module. will be reset)._x000D_
If a reset does the
2. Block/unblock not alarming
resolve the fault situation, replace the FBBx module._x000D_
unit._x000D_
Note:
OR_x000D_
_x000D_ Perform the following steps in the listed order until the fault disappears:
1.
3. Replace
Note: Perform the theFBBx
alarming module.
following unit._x000D_
steps in the listed order until the fault disappears:
1. Download two different software packages so that the faulty file is removed from the BTS.
1. Check that each cell object is assigned to an existing LCR ID in the Configuration file and make corrections if necessary.
1. Download two different software packages so that the faulty file is removed from the BTS.
2. Downloadare
Instructions thedivided
software into again.
three sections. Execute steps from section_x000D_
2. Download
chosen based theon corrected
best knowledge Configuration file andsense
reset to BTS.
2. Swap
the alarming and again.working and links, common
and check whereminimize
the alarmthe is cost and_x000D_
reported now.
3. Replace
time the System Module.
effort. _x000D_
1. Swap the alarming and working links, and check where the alarm is reported now.
_x000D_
3. If
2. Replace
the alarming the Systemlink remainsModule. the same, replace the System Module.
Section
Note: A: Check
Perform theon stepssystem below module
in the side:_x000D_
2.
1. If the alarming
Check if connector link remains
seal is the same,
properly replaceand
mounted thefirmly
System Module.
_x000D_
3. If the
Note: alarming
Perform thelinksteps changes,
below in replace
the listedthe order
module the in
behind
until place.
that
BTS link._x000D_
2.
1. Check
_x000D_ if
the the SFP
other (Small
active BTSForm Factor
faults and Pluggable)
act is properly
accordingly._x000D_ connected/mounted_x000D_
3. If the
Note:
in alarming
Perform thelinksteps changes,
If below replace
in the listedthe order
module behind
until that fault
the correct
BTS link. disappears.
1. the
_x000D_
Check Systemthe otherModule. active SFP
BTSconnection/mounting
faults and act accordingly._x000D_ is not readjust_x000D_
the
2.
Note:
_x000D_connection/mounting._x000D_
Check the
Perform cables
the between
steps below thein System
the listed Module
order and
until RF
the Module._x000D_
BTS fault disappears.
1.
3. Check
Check
_x000D_ the
if theother
LED BTS
indicatesfaults the andfaultyact accordingly.
SFP (connected to System Module)._x000D_
2. Check
Note: the cables
Perform the steps between belowthe System
in the listedModule and the
order until RF BTS Module. faultNote that dirty optical connectors might cause the signal leve
disappears.
Replace
3.
1. Reset the
Check
_x000D_ theSFPRF if it is faulty._x000D_
Module
commissioning and/or System Module,
parameters with thedepending
BTS Site Manager on the alarm source:_x000D_
Commissioning Wizard.
2.
4. Check
Note:
Check
a. Resetthe
Perform
if theambient
the
the steps
optical
RF temperature
cable
Module below is
by properlyof listed
the BTS/modules.
inblocking/unblocking
the theIf BTS
order untilit._x000D_
connected/mounted the in ambient temperature is too high, make sure the airflow to the BTS
faultSFP._x000D_
the disappears.
3.
1. Depending
Check
threshold the
value. on the
other fault BTS
active source, faults.reset the ROM
If the RF Module
disk isand/or
corrupted, System changeModulethe by blocking/unblocking
alarming module. it._x000D_
5.
2. Clean
Load
Note:
_x000D_ b.Performthe
Reset
the optical
the
theSystem
correct connectors
commissioning
steps Module
below inthat are
byfile
the toconnected
blocking/unblocking
listed theorder
BTS.untilto SFP. Reset
theit._x000D_
BTS faultRFdisappears.
HW_x000D_
1.
unitCheck
byPerform the antenna procedures
block/unblock line and antenna and line devices.
check if Factor
this Makethe
solves sure that the antenna line connectors are in the right torque.
_x000D_
4.
2. Replace
Reset
Note:
3. Reset the
the the
RF alarming
the Module
alarming steps modulemodule's
and/or
below byin Small
System
the listedForm
Module,
order
blocking/unblocking until Pluggable
dependingthe BTS
it. onproblem._x000D_
the(SFP).
fault BTS Check also the SFP in the other end and replace it if ne
fault source:
disappears.
_x000D_
4.
1. Replace
Check
_x000D_
a. Reset the the
the alarming
cables
RF related
Module RF byModule._x000D_
to the Masthead
blocking/unblocking Amplifier
it. (MHA).
2.
1. ResetB:
Check
Section the
thatalarming
all mandatory RF module parameters by blocking/unblocking
exist in the radio it. network data for the specific cell.
5. b. ResetCheck
_x000D_
Replace
FlexiBTS:
4. Replace the
the
on radio
alarming
System
alarming RF
Modulemodule
module.
side:_x000D_
Module._x000D_
by blocking/unblocking it.
5.
2.
1. Check
If the System
Reset
Block/Unblock
_x000D_
1. Reset if connector
the
the Module
alarming
site. seal
MHA
the FSM._x000D_ ismodule
is the properly
source bymounted
or replacing andthe
blocking/unblocking firmly
RF in place._x000D_
Module
the RFdoesModule not which
clear the
the fault
MHAsituation, replace
is connected to. the alarming System
3.
2.
2. Replace
Download
Check
If blocking if the
theand
or faulty
SFP partsthe
activate
(Small
unblocking and/or
Form
thecorrected
FSM devices
Factordoes along
commissioning
Pluggable)
not theis
help, antenna
file to
properly
replace theline.
the BTS.
FSM.
6.
3. If the the
Update
Update System
and Module
SWactivate
to the BTS. is the
the SWonly to the alarming
BTS. source or replacing the RF Module does not clear the fault situation, replace the al
in
3. the
2. Replace
Replace RF module.the If SFP
the Transport
faulty device(s).connection/mounting
submodule, is not correct
whichtois shared
located inside readjust
the System the_x000D_
Module.
4. Replace
RP3-01 cablingthe
connection/mounting._x000D_ RF
from Module.
peer system modules radio module is to be corrected._x000D_
4. Check the SW files.
3. Check the
1. if theantenna
optical lines:
cable antennas,
is properlyantenna connected/mounted
cables, connector in the torques,
SFP._x000D_ and antenna line devices._x000D_
4.
2. Clean
Check
5. Replace
4064 the
the
triggered optical
antenna
the during
alarmingconnectors
line
BTS at RF
(TX-cable-antenna)
module.
startup:_x000D_ module end. Reset
impedance RF HW
matching. unit by block/unblock_x000D_
procedures
Note! andthe check if below
this solves the problem._x000D_
Note! Perform the steps below in
_x000D_
Perform steps in the
the listed
listed order
order until
until the
the fault
disappears:
1. Check if other BTS fault indications are active. _x000D_
Section
Replace
2. Make C:the
sure Check
faulty of optical
unit. connection:_x000D_
that all RP3-01 fiber links and SFP transceivers between system module and radio module are properly connecte
1.
1. Reset
Check the
ifthe BTS.
optical cables are not over bend. If yes then replace the optical_x000D_
3.
2. Restart
Replace the Radio
faulty Module._x000D_
module/unit.
cable since over
4. Restart the BTS._x000D_ bending the optical fiber cables damages the cables and_x000D_
can
_x000D_detach or damage the connectors. _x000D_
2. OPTIONAL: Test the
4064 triggered during BTS runtime:_x000D_ fiber cable (f.ex. measure the optical attenuation)_x000D_
from
Change the faulty optical cable. check measuring equipment documentation_x000D_
System Module end. Please
for instruction details._x000D_
Enable power feeding towards Radio Module by switching RF power on in BTS Site Manager.
Update compatible SW for all conflicting RP3-01 nodes (check the SW versions to see the active SW version and update the ac
Note
Definethat in case
a valid TX of chained
power levelradio
valuemodules, the SW
in the Radio update
Network in this particular
configuration RNWcase can onlyforbealldone
parameters cellsone-by-one alongradio
using the same the RF ch
modu
In case the IP conflict situation is not solved, check the conflicting RP3-01 node on the site and ensure the SW update procedu
Optical cabling from the System Module to the Radio Module needs to be corrected.
Instructions in issue 01
Check the active fan alarms and the air flow of the BTS.
1. Download the BTS SW again._x000D_
2.
several possibilities the BTS._x000D_
for the alarm activation. Therefore, a BTS Clock Frequency History feature has been developed.
3.
history If step 2
feature,does not
see help,
the replace
of BTS Site module._x000D_
Manager).
1. Make sure that the module is properly
_x000D_ connected. If the Depending
module LEDondoes the possible reason,
not light up, follow the
the module instructions
is faulty. Checkbelow:_x00
the modul
_x000D_
1.Block/unblock
1. BTS._x000D_
In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term a
_x000D_
2.If it doesn't helpthe replace thethat
module which the is causing the alarm. _x000D_
_x000D_
1. Block/unblock module is causing alarm._x000D_
_x000D_ If the thebasic accuracy of the Iub signal theis alarm.
correct,
2.
Update
Flexi
Replace
Zone Micro
the
BTS module
with
FDD,
that
compatible is causing
Flexi ZoneSW (check
Micro the SWbut
TDD:_x000D_
there istotoo
versions much
see instability,
the active SW that is, the
version, jitter
and or wander
update is outside
the active the acc
SW version),
needed._x000D_
1.
Update
_x000D_ Block/unblock
compatible theSW BTS._x000D_
to the BTS (check the SW versions to see the active SW version, and update the active SW version), un
2.
3. Check
1. Perform
In casethe a power-off
of aNTP reset. _x000D_
BTSsetting._x000D_
equipment fault, the location might be:_x000D_
3.
_x000D_ If steps 1 and 2 do not help, replace the module that is causing the alarm.
1.Retry the file update a few times._x000D_
Transport
2.
2.Check Checkthe part:_x000D_
the stratum
FTP accountparameter on the NTP server._x000D_
user settings._x000D_
1.
_x000D_ Retry the SW update._x000D_
3.Check thesnapshot
file and path names._x000D_
-2.
3.
Flexi
4.Check
Save
First,
Check BTS the
checkthat
theFDD, the alarms
a GNSS
Flexi
administration
and
is of
BTS check
the
log TRS
configured the with
TDD:_x000D_
on the
download
and BTS
fileconnected.
server.
status
Site from the
Manager
_x000D_ andBTS
act SWDLreport in the snapshot file.
accordingly._x000D_
-_x000D_
1. If there
Retry are
the no
SW alarms,
update._x000D_
Unblock the module with BTS Site Manager. check the TRS synchronization settings._x000D_
_x000D_
2. If other flash memory-related faults are currently active for the module that is causing the alarm, replace this module._x000D
To
FCM
_x000D_ cancel the fault, unblock the cell.
unit:_x000D_
_x000D_
Flexi
To cancel Zonethe Micro FDD,
fault, unblockFlexithe Zone BTS.Micro TDD:_x000D_
Unblocking the BTS causes a BTS reset.
-1. If the
Retry TDM
the reference
SW signal
update._x000D_ accuracy
Check the fault history and other active faults of the unit._x000D_ and the TRS are in order but the FCM unit is still alarming, run the fast tuning with BTS S
-_x000D_
2. IfIfthe alarm
other flash is still active after the
memory-related fastare
faults tuning is finished,
currently active reset the
for the site.replace
BTS, If the problem
the BTS. does not disappear in a few minutes, res
1. IfBlock/unblock
-Note: thatThis
does not the alarming
help, replace unit/module._x000D_
the FCM unit._x000D_
2. Remove/reinsertfault doesthe notalarming
require any (special) actions.
unit/module._x000D_
_x000D_
3.
Note Replace
thattheif the
the alarming
reason is unit/module.
in the transmission
Replace
1. Upgrade alarming
the systemunit/module._x000D_
module SW._x000D_network synchronization, replacing the faulty unit does not solve the problem. Furth
network,
_x000D_
2. not to a fault in the unit._x000D_
1. Replace
Check
_x000D_
Flexi Zonethe
the
Micro
unit._x000D_
otherFDD,active alarms.
Flexi ZoneIfMicro the ROM disk is corrupted, change the alarming module._x000D_
TDD:_x000D_
_x000D_
_x000D_
4. After
Replace
1. Check the thefault
the BTS. situation
other active has alarms.been If cleared,
the ROMyou diskmight need to tune
is corrupted, changethetheBTS master module._x000D_
alarming clock because the BTS master clock adjus
_x000D_
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module._x000D_
_x000D_
-_x000D_
2.manually
Block/unblock by changing
the alarmingthe DAC word (during
module. There are a site
no visit)_x000D_
recovery actions, therefore block/unblock can be tried once. If that does no
1. Check
-_x000D_
or with the tuning,
fast other active
in whichalarms.
the If themaster
BTS ROM disk clock isiscorrupted, achange
tuned in actions, the alarming
few minutes module._x000D_
automatically nearcan
thebeIub reference
once. If(normal tunin
2. Block/unblock the alarming module. There are no recovery
_x000D_ therefore block/unblock tried that does no
Note,
1. however, that you should only use the fast tuning in case
Check the other active alarms. If the ROM disk is corrupted, change the alarming module._x000D_ the Iub reference signal is known to be a good one. Otherwise,
_x000D_
_x000D_
1. Block/unblock the FSM._x000D_
_x000D_
Background
2. Block/unblock information:
the alarming The principle
module. is that in
There arethenomobile
recovery network, thetherefore
actions, synchronization goes from
block/unblock can be thetried
S1 interface. However,
once. If that does noin
2. If that
Note! does not
Perform the help,
steps replace
belowthe inthe
thefaulty
listed module.
operator.
_x000D_ This does not harm system if the synchronization of the leased line service provider is also accurate or stable eno
_x000D_
Flexi
1. If theBTS FDD, Flexi
alarming module BTSisTDD:_x000D_
the System Module (FSM1), restart the BTS._x000D_
[User
1. defined]
2. Reset
If that doesthe Systemnot help, Module._x000D_
replace the alarming FSM._x000D_
2. Replace
[User
_x000D_ defined] the System Module or FBBx module (according to fault source)._x000D_
_x000D_
Flexi Zone
[User defined] Micro FDD, Flexi Zone Micro TDD:_x000D_
Flexi
1. Zone Micro
Replace the BTS. FDD, Flexi Zone Micro TDD, Flexi Zone:_x000D_
[User
1. Replacedefined] the Flexi Zone Micro BTS.
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
Note: Perform the following steps in the listed order until the fault disappears:_x000D_
_x000D_
1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template._x0
_x000D_
Flexi
2. BTS FDD, Flexi
Download BTSsoftware
TDD:_x000D_
2. Check the two
_x000D_ faultdifferent
history._x000D_ packages so that the faulty file is removed from the BTS._x000D_
_x000D_ again._x000D_
Flexi
_x000D_
1. Zone Micro
Replace FDD, Flexi
the alarming Zone Micro TDD: _x000D_
module._x000D_
Flexi
Check BTS
the FDD, Flexi BTS
frequencies' TDD:_x000D_
parameters against the BTS HW configuration. Check whether the connected radio supports the carrier
4. Replace
_x000D_
Perform the the SysteminModule.
recovery theTDD:_x000D_
following sequence:_x000D_
HW
Flexi
Flexi that
BTS might
FDD,
Zoneif Micro have
Flexi
FDD, limitations
BTSFlexi Zonethe in the
Microsupported
TDD:_x000D_ frequency range and bandwidth.
1.
1. Check
Check if the
the cable
signal connecting
is being recieved system module and radio module or the cable connecting the extension baseband module
1. Download
Replace
2. Replace thethe thecable._x000D_
correct
alarming Module._x000D_ reference clock source._x000D_
configuration._x000D_
System from the
2.
2. Check
FTM status._x000D_
_x000D_
3.
Flexi
3. CheckBTSthe
Change thesynchronization
FDD,
the faulty
Fleximodule (FBBx
BTS TDD:_x000D_settings or of FR)._x000D_
the FTM unit._x000D_
3.
4.
Note!Replace
If it does
Perform the
not BTS._x000D_
help,
the replace
steps below FCM/FCT
in the (system
listed ordermodule)._x000D_
until the fault disappears._x000D_
_x000D_
_x000D_
1.
FlexiCheck the
Zone Micro other alarms
FDD,site Flexi of the
Zone BTS
Micro and FTM and act accordingly._x000D_
_x000D_
Commission
Flexi
2. If Zone
there are the
Microno BTS
FDD,
other FlexiwithZonecorrect
Micro
synchronization-related IP TDD,
addresses.
TDD,
Flexi Zone:_x000D_
Flexi
alarms Zone:_x000D_
active, start the fast tuning with BTS Site Manager._x000D_
1. Replace
2. Check the thebackhaul
System connection.
Module.
Replace
3.
1. Resetuntil
Wait the theBTS.
site.the
Run fast tuning
module again._x000D_
is automatically heated to the required start-up temperature._x000D_
4.
1. Check
Check the
_x000D_ the reference
antenna cables signaland accuracy
connectors by measuring
toward the it with
MHA. a frequency
Fix or replacecounter
the (note:
brokenrequires a good timebase for the counte
parts. _x000D_
tuning._x000D_
2. If the fault has been active for more than two hours, check the environmental conditions of the site.
_x000D_
1.
5. Check
If the antenna
that does not help, cables
replace and theconnectors
system toward the MHA. Fix or replace the broken parts. _x000D_
module._x000D_
2. Restart
_x000D_ the MHA by blocking and unblocking the Flexi Radio (FR) Module._x000D_
_x000D_
1.
NOTE!Check theoperation
This antenna line affectsandall antenna
antenna line devices.
lines and Fix related
cells or replace theFR
to the faulty parts/devices._x000D_
Module, not just the faulty one. If the alarm reappears
2.
Flexi
2. Restart
The Zone
alarm the
Micro
isMHA FDD,by blocking
cancelled FlexionlyZoneatand
RF unblocking
Micro
Module TDD, theor
Flexi
reset Flexi Radio
Zone:_x000D_
BTS reset. (FR) Module. _x000D_
Flexi
NOTE! BTSThis FDD, Flexi
operation BTS
affectsTDD:_x000D_
all antenna
This
1. fault is most likelycables,
the result of a BTSlines hardwareand cells related
problem or to the FR Module,
aline
reference source not just
that the faulty
is being one. Ifbythe
followed thealarm
BTS reappears
that is in a
1. Check
1. Check the
Identify the
the
antenna
antenna
currently cables,
selected
connectors,
connectors,
synchronization
antenna,
antenna, and
and antenna
reference antenna
source line
of
devices
devices
the BTS
that
that
with
can
might
the
interfere
cause
active
with RF signal._x000D_
interference
1818 fault. If it with
is a the RF signal._
transport-based
2. Check
_x000D_ the antenna line (TX-cable-antenna) impedance matching._x000D_
alarms
Replace
_x000D_ orthe
faults associated
alarming Radiowith Module.the respective time servers (If there is a fault associated with a network-based time server, it is
2. Check the antenna
IEEE1588-2008 master line (TX-cable-antenna)
clock impedance matching.
Flexi
Replace Zone theMicro
alarmingFDD,Radio Zone ifMicro
and the 1818
Flexi Module/MultiRadio fault
TDD:_x000D_ subsequently
Combiner. clears._x000D_
2.
1. If the BTS
CheckRadio uses
the connection its GPS reference
and (block
integrity source
of antenna while the 1818
connectors, fault or ifand
cable, the antenna.
1818 fault_x000D_
persists for more than two hours after corre
Perform Module reset / unblock). If this doesn't help - replace alarming Radio Module.
2. Reset the BTS device. If the alarm persists, replace the BTS.
Perform RET calibration. If that does not help, replace the RET unit._x000D_
In case of
the alarming
the RET device.
unit._x000D_
In case of 1845: send valid configuration file
Perform RET calibration. If that does not help, replace the RET unit._x000D_ to the alarming device.
In case of
the alarming
the RET device.
unit._x000D_
In case of
the alarming
the RET device.
unit._x000D_
In case of 1845: send valid configuration file to the alarming
1. Block/unblock the radio module to give a power-off reset to the antenna line devices._x000D_ device.
.1.IfUpload
that does thenot help,SW
correct replace
to thethe antenna
device line device.
(if possible) Note: if an
or perform theALDfaultpower
sourcereset
is RX/TX, replaceby
(for example theRFradio module.
blocking/unblocking)._x0
2. If thatthe
Update does SWnot to help,
the BTS. replace the antenna line device.
Check that the WCDMA master system module is connected to the system module when the SCF parameter "syncMaster" = "F
1. Check whether the heating element exists at all._x000D_
2.
"NotCheck
enough the radio
heaterresources
control connection and thatdisplayed
for cell detected." the heaterinisthe working._x000D_
alarm additional info:_x000D_
3. Replace
_x000D_ the alarming component.
Reset the MHA (by Radio Module block/unblock). If this does not help, replace the alarming module.
The cell might not be set up because not enough radio resources are detected._x000D_
Reset
Check MHA (by Radio
if all cables andModule block/unblock).
SFPs connecting the radioIn case this wont
modules to thehelp - replace
system module the alarming
(or to the module._x000D_
extension baseband module - FBBx
Alternatively,
1. recommission
Check the functionality of the
the BTSantennawith line fewer cells._x000D_
device._x000D_
_x000D_
1. Check the functionality of the antenna line device._x000D_
"Not
2. enough
Check
_x000D_ the DSP resources
compatibility for cellthe
between detected."
antennadisplayed line device in and
the alarm additional info:_x000D_
the BTS._x000D_
1.
If Check thebaseband
extension
_x000D_ functionality of the(FBBx)
module antenna is line device._x000D_
used:_x000D_
2. Check the compatibility between the antenna line device and the BTS._x000D_
_x000D_
1.Ensure
3.
1. Check the
_x000D_ all cables
thatfunctionality
the (Power
of the and
given parameters Baseband
are
antenna inline bus range.
cables) have been connected _x000D_
thedevice._x000D_
valid
2.
to Check
the
_x000D_ FBBx theunit._x000D_
compatibility between the antenna line device and the BTS._x000D_
_x000D_
Block and
2. Check the unblock
compatibility the system
the antenna line device and the BTS._x000D_
3.
3. Check that the
If this does
_x000D_ not given parameters
help, replace are inunit._x000D_
_x000D_
If extension baseband module (FBBx) is not used:_x000D_
1.Block and unblock the system module._x000D_
1. Check the other active faults._x000D_
2.
1. Replace
Check the the alarming
other activemodule._x000D_
faults._x000D_
_x000D_
2. Replace the alarming module._x000D_
_x000D_
1. Check the GPS receiver installation._x000D_
Note! Perform the steps below in the listed order until the alarm disappears._x000D_
2. Check
_x000D_ the GPS receiver status._x000D_
Flexi
3. CheckBTSthe FDD, Flexi BTS
connection TDD:_x000D_
between
1.
1. Check
Confirm the cabling
if the current (connected
applied tothe SyncGPS
configuration In receiver and FSM._x000D_
interface)._x000D_
is within the configured RF HW capabilities._x000D_
_x000D_
Flexi
2.
1. Check
Flexi Zone
Verify BTS Micro connections
FDD, Flexi and
Zone commissioning
Micro theTDD:_x000D_ settings._x000D_the file if it is missing. Reset the FR module._x000D_
2. Check
Flexi
3. BTSififFDD,
Block/unblock
the
theHWP1 2.048
Flexi
the
file
MHz
BTS isreference
BTS._x000D_
present
TDD:_x000D_ insource FRismodule.
workingDownload normally and the 2.048 MHz signal is available._x000D_
1.
2.
1. Check
If
_x000D_ the file
Check the
that isGPS
present,
TEMP receiver
and CALI installation._x000D_
block/unblock files arethepresent
RF HWand unit._x000D_
upload missing file(s). Reset the RFbased
Module._x000D_
4.
2.
3. If HW
Instructions
Check
If the configuration
the
problem are
GPS divided
receiver
continues isinto
confirmed
threestep
status._x000D_
after as2correct,
sections.has been thisperformed,
Execute problem
the steps is caused
from the
replace bysection
the eNB
FR HW SW.
chosenCheck
unit._x000D_otheronactive
the bestalarms._x000D_
knowledge and comm
3.
2. Replace
If
_x000D_ the files the are alarming
present: module.
block/unblock FR HW unit._x000D_
_x000D_
Instructions
3. If the problem are divided
is into threeafter sections. 1Execute steps from section chosen based on best knowledge and common sense t
Flexi
Section
Flexi
_x000D_ Zone
Zone A: Micro
Check
Micro onstill
FDD,
FDD, theobserved
Flexi
system
Flexi Zone
Zone Micro
module step
Micro TDD,
replace
TDD:_x000D_
FR HW
Flexi Zone:_x000D_
side:_x000D_ unit._x000D_
_x000D_
1. Confirm
Replace if existing
Flexi applied configuration is within the configured RF_x000D_
1.
1. Check
Section
Flexi
HW Zone A:if Check
Block/unblock the connector
Micro
capabilities._x000D_ on Zone
the
FDD, BTS._x000D_
system
Flexi
Micro
seal is BTS.
module
Zone
properly
Micro
mounted and firmly in place.
side:_x000D_
TDD:_x000D_
_x000D_
2.
2.
1. Check
Instructions
Replace
Check if
ifBTS the
are Small
divided
theconnections
Flexi
connector Form
Zone into
seal Micro Factor
three
isand Pluggable
sections.
BTS._x000D_
properly (SFP)
Execute
mounted and is properly
steps from connected/mounted
firmly in place. _x000D_ section chosen based in the System
on best Module. and
common sense t
1.
2.
3. Block/unblock
Check
Check
_x000D_ if the LEDBTS._x000D_
indicates the commissioning
faulty SFP settings._x000D_
(connected to System Module). Replace the SFP if it is faulty._x000D_
_x000D_
2.
2.
3. Check
Flexi BTSifFDD,
Replace
Block/unblock the
the SFP Flexi
Flexi
the (Small
BTS Micro
Zone
BTS._x000D_ Form BTS._x000D_
TDD:_x000D_ Factor Pluggable) is properly connected/mounted in the System Module. If SFP connection/mo
4.
3.
1. Check
Section
Flexi
Check A:ifif Check
Zone:_x000D_
Block/unblock the
the optical
LEDthe RFcable
onindicates
system HW is properly
module
the faulty
unit._x000D_ connected/mounted
side:_x000D_
SFP (connected in the SFP._x000D_
to System Module). Replace the SFP if it is faulty._x000D_
_x000D_
4.
1. If
Flexi
5. HW
Clean
CheckBTStheconfiguration
ififFDD,
connector is
Flexiconnectors
optical BTS
seal confirmed
TDD:_x000D_
is that
properly then
are this problem
connected
mounted and to is
the
firmly caused
SFP.
in in place. by eNB_x000D_
Reset the RF
_x000D_ RF HW HW unit._x000D_
unit by using block/unblock procedures and ch
1.
4.
2. Block/unblock
Check
If
Flexi
SW.
1. the problem
Zone:_x000D_
Check
Block/unblock the
other Flexi
optical
continues
active
RF HW Zone
cablealarms. Access
is
after properly
unit._x000D_ step Point._x000D_
1 connected/mounted
has been performed, the
replace SFP._x000D_
the
_x000D_
2.
1.
2.
5. Check
Replace
Clean
_x000D_ if
Block/unblock
thethe the SFPRF
Flexi
optical (Small
HW
Zone
connectors Form
unit._x000D_
Access Factor
that Point.
are1, Pluggable)
connected is
to HWproperly
SFP.unit._x000D_ connected/mounted
procedures SFPcheckconnection/mo
if this sol
1.
2.
3. Block/unblock
If
Section problem
Check
_x000D_ B:if Check
the is LED Flexi
still
on Zone
observed
the
indicates radio Access
after
module
the step
faulty Point._x000D_
replace
side:_x000D_
SFP (connectedRF to System Module). Replace the SFP if it is faulty._x000D_
_x000D_
Flexi
1.
2. Zone
Block/unblock
Replace
_x000D_ Micro
the FDD,
the
Flexi RF
Zone Flexi
HW Zone
Access Micro
unit._x000D_
Point. TDD:_x000D_
1.
4.
2. Check
If
Section
1. Check
_x000D_ B:ifthe
problem connector
the
Checkis optical
stillon
connection seal
cable
observed
radio andis isproperly
properly
after
module
integrity step mounted
of1,
side:_x000D_
thereplace
antennaandRF
connected/mounted firmly
HW in
connector, place._x000D_
in
unit. the SFP._x000D_
cable, and antenna._x000D_
Flexi
2. CheckZone
BTS if Micro
FDD,
the FDD,
Flexi
Small BTS
FormFlexi Zone
TDD:_x000D_
Factor Micro
Pluggable TDD, Flexito
(SFP) Zone:_x000D_
is properly connected/mounted inthat
the isRF module.
5.
1.
2. Clean
Check
If there
problem
Check
the
if are optical
connector
more
continues connectors
than seal two
after is RF
step that
properlyunits
1 are
has connected
mounted
within
been the and
BTS,
performed, SFP.
firmly in Reset
replaceplace._x000D_
block/unblock RF
the HWRF
the
RF HW unit
HW byunit
unit.block/unblock causing theIf alarm._x000D_
procedures SFPand connection/mounti
check if this sol
1.
3.
2.
3. Check
_x000D_
Flexi
Check
ResetBTSthe ifthe
Block/unblock
if the
FDD,
the
configuration.
BTS SFP
the RF
optical
Flexi cable
BTS
(Small
device.
HW
If
_x000D_
isunit._x000D_
properly
TDD:_x000D_
Form
the Factor
alarm connected/mounted
Pluggable)
persists, replace is properly
the in the
BTS. SFP._x000D_ in the RF module. If SFP connection/mounti
connected/mounted
2.
4. Reset
If the B:
Clean BTS.
problem
the _x000D_
opticalcontinues
onconnectors after step
at the 1RFhas been performed,
module end. Resetinreplace the the RF unitHW unit._x000D_
Section
1.
3.
1.
3. if Check
Block/unblock
Check
Block/unblock
If
_x000D_ that does the not
the
optical
RF help,
radio
RF
HW cable HW
replace
module
isunit._x000D_
properly
unit._x000D_ the
side:_x000D_
Flexi connected/mounted
Zone Micro BTS._x000D_ theRF HW
SFP._x000D_ by using block/unblock procedures and check if th
_x000D_
1.
2.
4. Check
If the
Clean if
problem connector
theMicro opticalcontinues seal
connectors is properly
after step
at RF 1mounted
has
module been and firmly
peformed, in place._x000D_
replace the RF HW unit._x000D_
_x000D_
Flexi
1.
Section
2. Check
_x000D_ Zone
Block/unblock
C:if Check
the SFP FDD,
RF the HW Flexi
optical
(Small Zone
unit._x000D_
Form Micro
connection:_x000D_
Factor TDD, end.
Pluggable) FlexiResetis
RF HW unit by block/unblock procedures and check if this solves the
Zone:_x000D_
properly connected/mounted in the RF module. If SFP connection/mounti
_x000D_
2.
1. If problem
Replace
_x000D_ is still
the optical
Flexi observed
Zone Microafter BTS step 1, replace
orconnected/mounted
Flexi Zone RF HW
Access unit.
Point.
1.
3.
In Check
Flexi Zone
startup:
Section if the
Micro
Wait
C: Check FDD,
until thecables
cable
Flexi
alarm isare
Zoneis not
properlyMicro
canceled.overly
TDD, bent.
This FlexiIf
might they are,
Zone:_x000D_
take upinreplace
the
to 30 the optical cables since overly bending the optical fiber ca
SFP._x000D_
minutes._x000D_
2.
2. If problem
OPTIONAL: stillofobserved
is Test optical connection:_x000D_
the fiber after
cable step
(for 1,Flexi
replace
example, RF
measure HW RF unit.
the optical attenuation)
4.
1. Clean
Replace
_x000D_
1. Check the
if the optical
optical Flexi
Flexi BTS FDD, Flexi BTS TDD:_x000D_ connectors
Zone
cables Micro
are not at
BTS RF
over module
or
bend. If end.
Zone
yes, Reset
Access
replace HW
Point.
the unit
optical by
cable sincefrom
block/unblock overthe System
procedures
bending theModule
and
optical end.
check
fiber if Check
this
cables the
solves mea
the
damage
3. OPTIONAL:
_x000D_
If
2.
1. the alarm
OPTIONAL:
Block/unblock is Test
not
Test the fiber
canceled:_x000D_
thethe RF fiber
HW cable
cable
unit._x000D_(for example, measure the optical attenuation)
(for example, measure the optical attenuation) from System Module end. Check measuring efrom the RF Module end. Check the measurin
Flexi
_x000D_
Section
check BTS
if C: FDD,
Check
environment Flexi
ofthe BTS
optical
temperatureTDD:_x000D_
connection:_x000D_
is within design limits for radio module._x000D_
3.
2.
1. OPTIONAL:
If the problem
Block/unblock Test
still
RF fiber
persists
HW cable
after
unit._x000D_ (for
step example
1 has beenmeasure
the RF HWfrom RF Module end. Check measuring equip
unit._x000D_
If
1. the
WhenCheck
Flexi
_x000D_ alarm if
environment
BTS still
optical
FDD, persists
Flexicables
temperature
BTS after
are executing
not
TDD:_x000D_ isover
out ofthe
bend. steps
limits If yes
thenfrom
then
alarmsections
replace
is A,
expectedthe B,optical
and
andC,no replace
cable since
further the RF bending
over
actions module._x000D_
are needed. the optical fiber cables dam
2.
1. If
_x000D_
2. problem is Test
OPTIONAL:
Block/unblock still
the observed
theRF fiber
HW after step
cable
unit._x000D_(for 1, replacemeasure
example, RF HW unit._x000D_
the optical attenuation) from System Module end. Check measuring e
If alarm
Flexi
_x000D_ Zone
BTS is still
Micro
FDD, observed
FDD,BTS
Flexi after
Flexi executing
Zone
TDD:_x000D_ Microsteps TDD:_x000D_from sections: A,B,C replace the RF module._x000D_
3.
2.
1. OPTIONAL:
If the problem Test the
continues fiber cable
after step (for 1 example,
has been measure
the RF HW from RF
unit._x000D_ Module end. Check measuring equip
1. Check
Flexi
Check
_x000D_ Zonethe
Instructions if Micro configuration
are divided
environment FDD, Flexi into and
three
Zone
temperature download
sections.
Micro updated
Execute
TDD:_x000D_
is within design configuration
the
limitssteps for from
radioif required._x000D_
the section
module. chosen
When based ontemperature
environment best knowledge is out and common
of limits then
2. Block/unblock
_x000D_
1. Block/unblock
_x000D_ the
the BTS._x000D_
Flexi Zone Micro BTS or from
the Flexi Zone A,B,C Access Point._x000D_
If
1.
3. alarm
Flexi Zone is
Block/unblock
Replace
Section still
Micro
thenotobserved
FDD,
RF
BTS. HW after
Flexi executing
Zone
unit._x000D_ Micro steps
TDD, Flexi sections:
Zone:_x000D_ replace the RF module._x000D_
2.
1. If thatA:
Check
Replace
_x000D_ if Check
does airflow
the Flexi
on
help, thereplace
is Zone
not systemthe
blocked
Micro
module
by Flexi
BTS some side:_x000D_
Zone
objects
or Flexi Micro
Zone BTS orRemove
orAccess
walls. the Flexi
Point. any Zone
objectsAccess Point.airflow and mount module according to
blocking
1.
No Check
action
_x000D_ if is the connector
needed. seal is properly mounted and firmly in place. _x000D_
2.
2. If problem is Small
still observed after Pluggable
step 1, replace RF is HW unit. connected/mounted in the System Module. If the SFP's connecti
3. Check
1. Check ifif the the fan or Form
excessive sunlight
air flow Factor
isisblocked
causingby any (SFP)
overheating. object. properly
Install
Remove sunshield
any objects following mounting
that might instructions
be blocking the fanandor recommendations.
air flow._x000D_
3.
2. Check
Check ifif the
the LED
fan indicates is
connector theproperly
faulty SFP mounted.(connected Mount tothe System
fan Module).properly._x000D_
connector Replace the SFP if it is faulty._x000D_
1.
4. Check
Check ifif the fan
thecontinues,
optical or air cable flowisisproperly
blockedconnected/mounted
by any object. Remove in the any objects that might be blocking the fan or air flow._x000D_
SFP._x000D_
3.
2. If the alarm
Check ifif the fan connector resetisthe radio mounted.
properly module byMount using the block/unblock._x000D_
fan connector
5.
1.
4. Clean
Check
If alarm the the optical
continues,fan or connectors
air
replaceflow is
the that
blocked
fan are connected
by
module. any object.to the SFP.
Remove Reset
any the RFproperly._x000D_
objects_x000D_ HW unit by using block/unblock procedures and ch
3. If
_x000D_
that the
might alarm be continues,
blocking the reset
fan orthe air radio module
flow._x000D_ by using block/unblock._x000D_
1.
4. Check
If the B: if thecontinues,
alarm fan or air flow replaceis blocked
the fan by any object. Remove any objects that might be blocking the fan or air flow._x000D_
module.
Section
2.
2. Check
Check ifif Check
the
the fan
fan on the radio
connector
connector is
is module
properly
properly side:_x000D_
mounted.
mounted. Mount the the fan connector_x000D_
1.
1. Check
Check
properly._x000D_ifif the
the environmental
connector seal temperature
is properly is withinMount
mounted the design
and firmly
fan
in limitsconnector
of the radio
place._x000D_
properly._x000D_
module. If the environmental temperature is be
3. If
_x000D_ the alarm continues, reset the radio module by using block/unblock._x000D_
2.
3.
1.
4. If the
Check
If alarm
if
the alarm the Small
continues,
environmental
continues, Form Factor
reset
replace the Pluggable
temperatureradio
the fan module
is
module. (SFP)
withinby is
the properly
using design connected/mounted
limits of the radio in the IfRF
module. themodule.
environmentalIf SFP connection/mounti
temperature is ou
2.
3.
4. Check
Check
If
_x000D_ the ifif the
alarm the air flowcable
optical
continues, is not is
replaceblocked
properly
the byconnected/mounted
fan any
module.object or walls. in Remove
the any_x000D_
SFP._x000D_
1. Check
objects if the environmental temperature is within the designaccording limits of the radio module. If the environmental temperature is ou
4.
2. Cleanthat
Check
_x000D_ the
if the might
optical beconnectors
air flow blocking
is not blocked air atflow
theby and
FR any mount
objectthe
module end.ormodule
ResetRemove
walls. the FR HW tounit
instructions
any_x000D_ by using and recommendations._x000D_
block/unblock procedures and check if th
_x000D_
Instructions
_x000D_
objects that are
might divided
be into three
blocking air sections.
flow and Execute
mount the steps
module from the section_x000D_
according to instructions and recommendations._x000D_
2.
3. Check
Checkbased if air flow is not blocked by any object or walls. toRemove any_x000D_
chosen
Section
_x000D_
Instructions
objects C:if Check
that
excessive
are
might
on best
the
divided
be
sunlight
knowledge
optical
into three
blocking
is causing
and
connection:_x000D_
air sections.
flow and
overheating.
common Execute
mount
sense
the
Install
steps
module
minimize
fromsunshield,
thethe
according
following
cost
section_x000D_ mounting instructions and recommendations.
and_x000D_
to instructions and recommendations._x000D_
time
1. effort. _x000D_
the optical cables are not overly bent. If they are, replace the optical cable,
3. Check
chosen
_x000D_
1. The VSWR
_x000D_
if excessive
based measured sunlight
on best knowledge is
at the RFand causing overheating.
common exceeds
(transmitter) Install
sense to values minimizesunshield,_x000D_
that the arecost and_x000D_
acceptable by since
the RF overly
module. bending_x000D_the optical fiber cab
2. OPTIONAL:
following
time
3.
2. Checkeffort.mounting
ifthe_x000D_ Test
excessive the fiber
instructions
sunlight cable and
isand (for
causing example,
recommendations.
the overheating. measure Install the optical
sunshield,_x000D_ attenuation) from the System Module end. Check the mea
Section
1.
3. Check
OPTIONAL:
_x000D_ A:the Checkimpedance
BTS Test on thesystem
connections matching
fiber module
cable
of
(for
Antenna Line
side:_x000D_
commisionning
example, measure
System
settings._x000D_
the
(replace elements that cause mismatch)._x000D_
optical attenuation) from the FR Module end. Check the measurin
following
3.
1.
2. To
Checkcheck mounting
ifthat
Block/unblock if the
the connector
the instructions
above-mentioned
BTS seal
(using isand recommendations.
thesteps
properlylocal have
mounted
BTS Site solved and
Managerthe problem,
isproperly
firmly block/unblock
inconnected
connection place. if_x000D_
a remote the RF module._x000D_
connection is not possible).
_x000D_
Section
1. Check
_x000D_ A: Check the on
Small system Form module
Factor side:_x000D_
Pluggable (SFP) is in the System Module._x000D_
2.
If Check
the alarm ifif the small
continues form-factor
after is pluggable (SFP) isand properly connected/mounted_x000D_
1.
1.
in
Check
_x000D_
Note:
Check
the Forcing
systemthat the theconnector
the
module. RF HW
Small If Form
thetoexecuting
seal work
Factor
SFP's
properly
under steps
such
Pluggable from
mounted
connection/mounting
sections
conditions
(SFP) isisis A, B,
firmly
might
properly
not
and
result
correct,
C,inreplace
inconnected
place. _x000D_
permanentin the
the FR
readjust_x000D_
module._x000D_
damage
System to the RF HW.
Module._x000D_
_x000D_
2. Check
Replace
_x000D_ if the small
SFP form-factor
module. pluggable (SFP) is properly connected/mounted_x000D_
the
1.
Flexi
in theconnection/mounting._x000D_
CheckZone
systemthe Microstatus FDD, of the
IfFlexi module
Zone Micro behind the faulty link
TDD, Flexi Zone:_x000D_ (power on, and so on)._x000D_
2.
3. Replace themodule.
SFP module. the SFP's connection/mounting is not correct, readjust_x000D_
theCheck
_x000D_
1. Replace
Reset if the
the the RFLED
BTS.
Module indicates behind that thethe SFPoptical
faulty is faulty (connected
interface to system module)._x000D_
by blocking/unblocking it._x000D_
Replace
2.
3. Check
Check
_x000D_ the
the
if theSFP
Small
LED if it
Formis faulty._x000D_
indicates Factor that Pluggable
the SFP (SFP)
is faulty from both
(connected ends to (the
system System Module and the module behind the faulty link). Th
module)._x000D_
1.
4. Exchange
Check if the the alarming
optical and working links, and check where the SFP._x000D_
alarm is reported now._x000D_
_x000D_
Replace
2. the
If that does
_x000D_ SFPnot it iscable
ifclear is properly
faulty._x000D_
the fault situation, connected/mounted
replace the RF Module in the that causes the alarm._x000D_
5.
3.
1.
4. Clean the
Exchange optical
connectors,
the alarmingconnectors test
andisthe that
fiber
working arecable,
connected
links, to thewhere
replace
and check itSFP. Reset
ifinit the
is
the the is
faulty._x000D_
alarm RF HW_x000D_
2. Check
_x000D_
unitIf by
_x000D_
if the
theblock/unblock
alarming optical cable
link remains
procedures
properly
the same,
and
connected/mounted
checkreplace thisthe
ifand System
solves the Module._x000D_
SFP._x000D_
problem._x000D_
5.
3.
1. Clean
Reset
Exchange
_x000D_ the optical
System
the alarmingconnectors
Module._x000D_
and that
working are connected
links, to
check the SFP.
where Reset
the alarm the isRF HW_x000D_
_x000D_
4.
2.
unitIf by
_x000D_ previous steps
theblock/unblock
alarming link remains do not the
procedures help, replace
same,
and check the
replaceif module
thisthe System
solves behind
Module._x000D_
problem._x000D_
3. If the B:
Section
_x000D_ alarming
CheckModule link
on radio changes, module replace the module behind that link.
side:_x000D_
_x000D_
4.
2. System
If the alarming link remainsis the onlysame,
the source causing
replace thethe alarm,Module._x000D_
System or if the actions mentioned above do not clear the fault situation,
1.
3. Check
If
Section
_x000D_ the B: if Check
alarmingthe connector
link
on radio changes, seal
moduleisreplace
properly themounted
side:_x000D_ module and behind is firmly
2.
3. Check
1. If
Check if the small
if the connector
the alarming form-factor
link changes, seal isreplacepluggable
properly (SFP)
themounted
module and is properly
behind is firmly connected/mounted_x000D_
in
2. the
Check RF ifmodule.the small If the SFP's connection/mounting
form-factor pluggable (SFP) is properly is not correct, readjust the_x000D_
in the RF module. If the SFP's connection/mounting is not correct, readjust the_x000D_
1. Exchange the alarming and working links, and check where the alarm is reported now._x000D_
_x000D_
2. If the alarming link remains the same, replace the System Module._x000D_
1. Check the cables between the System Module and the RF Module._x000D_
_x000D_
_x000D_
3. Check
1. If the alarming
changes,the replace
System theModule
moduleand behind
the RF thatModule,
link. the cable between the FBBx Module and the RF Module,
_x000D_
1. Check the cables between the System Module and the RF Module, and the cable between the FBBx Module and the RF Mo
_x000D_
2. Replace the unit that causes the alarm (System Module or FBBx).
_x000D_
3. Reset
_x000D_
_x000D_
4. Replace
3. Check
1. Replace the the alarming
RP3-01 cable module
between (System Module).
2. Check
slave system the alarms
modules._x000D_ in the synchronization master system module and act accordingly._x000D_
1. Reset
3. Check the the status of the module behind themodule._x000D_
faulty link (power on, and so on)._x000D_
2. Check the synchronization
_x000D_ alarms in the synchronization master system master system module and act accordingly._x000D_
1.
3. Switch
Reset to the recently active BTS configuration._x000D_
2. Check the
_x000D_ the synchronization
alarming fiber connection. master system module._x000D_
_x000D_
1. Check antenna mapping to the local cells in the commissioning file._x000D_
_x000D_
1. Check
BTS._x000D_
1. Check the
_x000D_ antennacables mapping to the the System
local cells Modulein theand RF Module or
commissioning the cable between the FBB module and the RF Module (it
file._x000D_
3.
1.
2. Perform
Block/unblock
Check theblock/unblock
cables the BTS.
between on the
_x000D_ RF
the System Module._x000D_
Modulerelated and RF
2.
4. Check
Perform
_x000D_ loga for
BTS line code
reset. violation
_x000D_ (LCV) errors to Module or the_x000D_
optical links. cable between the FBB module and the RF Module (it
3.
1. Perform
Block/unblock
_x000D_ block/unblockthe BTS. on the
_x000D_ RF Module._x000D_
5.
2.
4. Replace
Check
Perform theathe RF module
configuration.
BTS behind the optical link._x000D_
_x000D_
3. Verify
Note:
_x000D_ SFP
Perform the reset.
(small steps _x000D_
form-factor
below inpluggable the listedtransceiver)
order until the andBTS fiberfault
conditions.
disappears._x000D_
5.
2. Replace
Check
_x000D_ the the RF module
baseband busbehind
configuration the optical relatedlink._x000D_
to RP3 link speeds.
If FSP
Note:
Perform the steps below in the listed order until the BTS fault indication disappears._x000D_
Flexi BTSthe
Perform FDD, Flexi BTSBTS TDD:_x000D_
1.
If
1.
Check
FSP
Note:
Reset is the
Performthea System
System
other
source:_x000D_
the steps Module
active below
Module._x000D_
reset._x000D_
faults
in the and listed actorderaccordingly._x000D_
until the BTS fault disappears.
2.
1. If
Makethat
Perform does
sure a not
that
System help,
the replace
plug-in
Module type the System
baseband
reset._x000D_ Module.
unit is installed correctly._x000D_
2.
3. Replace
Note:
Reset Performthethe System
the
alarming steps Module._x000D_
below inunit._x000D_
baseband the listed order until the BTS fault disappears.
2.
1. If that does
Block/unblock
_x000D_ notRF help,HW replace
unit. the System Module._x000D_
4. Replace
Note:
_x000D_ Perform the the alarmingsteps belowbaseband in the unit.
Flexi
1. Check
_x000D_ Zoneif Micro fan or FDD, air flow Flexi Zone Micro
is blocked by some TDD:_x000D_
objects. Remove any blocking
If
2. FBB
If
Flexi
1. Reset
objects. is
problem
BTSthe the
FDD, source:_x000D_
is still observed
BTS._x000D_ after step 1 replace RF HW unit.
1.
1. Check
Perform
Depending theafaninstalled
onSystem
the HW/SW
Module
installed and version
reset._x000D_
commissioned compatibility and the HWsource(s)
synchronization compatibility listedwith the current
in section BTS configuration._x000D_
"Meaning", see the commissioned syn
2. Replace
Check
Flexi
_x000D_ BTSifFDD, the Flexi
connector
Flexi Zone
BTSisMicro properly
TDD:_x000D_BTS.mounted. Mount fan connector properly.
2.
If If
_x000D_
3. If
FSM that
alarm doesis still
is fault not
source help,
observed andreplace
then
other the
reset
alarms FBB radio card.
are module
reported by- recommission
block/unblock. thesystem
BTS with the correct number of cells per BTS_x000D_
2. Check
Reset
GPS that
(block/unblock)
receiver the
(PPS BTS cellBTS._x000D_
the parameters
source):_x000D_ from the Network management match_x000D_
4.
If
the If
FR alarm
is fault is still
source observed
- correct thenthe replace
cables the fan
connection module.to be consistent with site configuration file. There shall be cable between FS
1. IfBTS
Software
_x000D_ thereHW is aconfiguration
and GPS receiver
hardware can(for be example,
commissioned
reconfigured frequency,
atforthetheBTS power)._x000D_
setup site,where
note the following:
faulty TX isIf not the used._x000D_
GPS receiver is not locked to any satellite,
_x000D_
installation
The cells will(poor
then sky visibility).
operate For this,
in single mode theunless
only permanent
all the TX'scure related is totochange
the properthe GPScell areantenna location. One indication of a fai
faulty._x000D_
_x000D_
Flexi
3. CheckBTSthe FDD, NetworkFlexi BTS TDD:_x000D_
management system alarms for the alarming local cell (LCR)._x000D_
_x000D_
Check
Flexi
Define the
Zonea other
Micro
valid TX active
FDD,
power BTS
Flexi
level faults
Zone
value and
Micro
in act
the accordingly.
TDD:_x000D_
radio network (RNW) configuration part of the site configuration file (SCF) and use th
_x000D_
Flexi
2. ThereBTSmight FDD,be FlexiaBTS BTS TDD:_x000D_
malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver._x000D_
Recommission
_x000D_
4. Recommission
Perform the steps the the
below with
BTSinto the
theensure correct
listed that order number
alluntil of
parameters LCRs
the fault are per RF Module.
correctly Ifconfigured.
disappears. after autonomous GPS power reset, the fault does not g
_x000D_
Replace
Flexi Zone theMicroalarming FDD,unit. Flexi Zone Micro TDD:_x000D_
_x000D_
3. There might be a malfunction in the BTS. Perform a BTS site configuration
reset._x000D_
Define
Flexi
Control BTS aInterface
valid
FDD, TX power
Flexi
not BTS level value
TDD:_x000D_
available:_x000D_ in the radio network (RNW) file and use the commissioning wizard in the BTS
_x000D_
1. The
Flexi
4. TheBTS BTS
GPS FDD,has
cable detected
Flexi a malfunction
BTSconnectors
and/or TDD:_x000D_ in the control interface of the GPS
might be damaged. Check the cable and the connectors._x000D_ receiver. A possible reason is that the BTS and the G
_x000D_
2.
1. Perform
Reset the a (remote)
System BTS
Module site
that resetis for
causing the whole
the BTS._x000D_
alarm._x000D_
_x000D_
1.
1. Check
the fault name of the toggling BTS fault._x000D_
3.
2.
5.
2. Perform
Replace
There
Follow theathe
might power System
be aifreset
instructions HW for
Module
fault the
of the whole
in that
the
togglingGPS BTS._x000D_
is causing receiver.
BTS the Check
fault alarm._x000D_
to clear the
the operation
problem._x000D_ and change the HW, if needed._x000D_
2.
1.
4. Replace
Check
The cable in the
NetAct faulty
autoconfiguration
the GPS receiver isand enabled
the and
BTS if the
might required
be working license and commissioning
incorrectly. Check file of
aretheavailable._x000D_
_x000D_
_x000D_
Note!
_x000D_
2. Check Detailedthe information about
autoconnection/autoconfiguration the toggling frequency
information can be
with found
BTS in
Site alarm history
Manager._x000D_ file,ifwhich
the pins can be connectorsusing
downloaded (on both
BTS
5. TheBTS
Flexi
External cable
Zone FDD,
2.048MHzbetween
Micro FDD,
Flexi the
BTSFlexi GPS Zone receiver
TDD:_x000D_
signal:_x000D_ Micro and the BTS might be faulty. Check the situation and change the cable, if needed._x00
TDD:_x000D_
Flexi
3.
6. Load
ThereZone the Micro
might correctbe FDD, Flexi
faultZone
commissioning of Micro
file toTDD:_x000D_
the BTS. Check
1.
1. Reset
Check
If
There
1.
and
there
Replacemight the
isthe
an
be twoathe
BTS._x000D_
correct external
BTS.
HW contents
reasons 2.048MHz in the
for the GPS
the
signal
fault:_x000D_receiver.
commissioning
source commissioned the operation
file._x000D_ at the BTS and change
site, check the the
GPS BTS module,
faults ifofneeded._x000D_
that device and act acc
7.
2. There
Replace
_x000D_
further
1. The mightthe
actions._x000D_
radio unit be
BTS. a
that HW shouldfault in
only the be BTSconnected System Module.
to LTE Check
Flexi System the operation
Module is and
also change
connected the System
to WCDMA Module,
system if needed._x000
module. _x00
Flexi
_x000D_
Flexi BTS
Zone FDD,
Micro Flexi
FDD, BTSFlexi TDD:_x000D_
_x000D_
In
1. this case,
Block/unblock disconnectthe alarming the radio unit
module._x000D_ from the WCDMA system module._x000D_
_x000D_
1.
2. Check is
Reconfigure
There and
mightanthecorrect
befrequency
error a in the
thecontents
malfunction settings in of
commissioning inthe
the aBTS. commissioning
proper way with
Perform
file._x000D_ a BTS file._x000D_
respect to Radio Module capabilities.
site reset._x000D_
_x000D_
Flexi
_x000D_ Zone Micro FDD, Flexi Zone Micro TDD:_x000D_
_x000D_
In this
Check
2. If FSPcase, create
theorconfiguration the fault
commissioning
of the configured filecell.
with theorcorrect relation system If module - radio
is theunit and send the file tosystem
the BTS. Note
Perform
2.
FTM Recommissionthe FBB
reference steps isthe
(TDM,
the
belowBTS
SyncE
source,
inwith
the orlisted
the
ToPvalid
perform
order
as
FSP
until
commissioning
source):_x000D_
FBBfile.
the fault reset recovery.
disappears._x000D_ FCM/FCT fault source, perform module
_x000D_
To be
_x000D_ performed on the master RAT side:_x000D_
1.
3.
1. If
Ifbethere
steps
Check is
the an
1 and integrated
antenna 2on dothe not
line transmission
help, replace
and antenna unitalarming
the
line (FTM) commissioned
device causes theatalarm._x000D_
module._x000D_
that the BTS site, note the following: The FTM unit operates so
Control
To
the FTM Interface
performed
synchronization not available:_x000D_
MasterRAT
priority side:_x000D_
setting) might be missing, causing the FTM's internal clock to drop to holdover mode. In this ca
_x000D_
2.
1. Fix
The
Check orBTS replace
the has
antenna the faulty
detected lineaand parts/devices._x000D_
malfunction
antenna in antenna
line the control
device thatinterface
is causing ofFix the
the GPS receiver.
alarm._x000D_ A possible reason is that the BTS and the G
_x000D_
1. Check
_x000D_
3. Perform thea RS485
radio IUANT
module interface
reset (onlyfor and
thethe master RATline devices. or
in sharing mode can request replace the faulty
for suchparts/devices._x000D_
an operation to be performed).
2.
2. Perform
Fix
Check or
TheZone alarm a
replace
the (remote)
alarms
isthe the
canceled ofBTS
faulty
the site
FTM
onlyZone reset
parts/devices.
when unit and
the RFact whole BTS._x000D_
accordingly._x000D_
Module is reset or ifdisappears.
the BTS is _x000D_ reset.
Flexi
Note!
3. Perform
Perform Micro
a power FDD,
steps
reset Flexi
below
for theinwhole Micro
the listed TDD:_x000D_
order
BTS._x000D_ until the fault
_x000D_
_x000D_
4. There
Replace might
parallel beRP3-01/CPRI
a HW fault in the GPS
fiber linksthe Receiver
toward oneor radio
the BTS. Replace
module so that thetheFlexi Zone Micro
maximum mutual BTS.length difference between fiber
3. Check
Performthe synchronization settings the of
2. a power-off reset. _x000D_ FTM unit._x000D_
1. Check
synchronization the fans and ensure
master system that
module. ambient temperature on the site is acceptable. _x000D_
_x000D_
1.
3. Check the fan
2. stepsdoes
If that 1 and not2and do the
help, not connector._x000D_
help, replace
replace the alarming the module module. that is causing the alarm.
4. There
2. Replace mightthe be
fan. a malfunction in the BTS. Perform a BTS site reset._x000D_
_x000D_
1. Either
1. There
Check might enable
the fans the parameter actDistributedSite or switch toona the shorter fiber between the FSM and FR._x000D_
5. be and ensure that
an equipment the ambient
failure in the FTM temperature
unit. Check the operation site is acceptable._x000D_
and replace the unit, if needed. Note: Normally, the
2.
2. Restart
If that does the FSM.
not (frequent
help,
indication
1. Check activity
that the fan is replace
not BTS the
fault
blocked._x000D_ alarming
indication module.
activations/cancels instead of a stable BTS fault indication state) points to the in
_x000D_
2. Check that the fan connector is properly mounted._x000D_
If the
3. previous
If that does not steps help,do replace
not help,the therefan.might be an equipment failure in the System Module. Check the operation and if perform
_x000D_
_x000D_
_x000D_
1. Check if the fan is not blocked._x000D_
2. Checkthe
Replace if the fan connector is properly mounted._x000D_
fan(s).
If the BTS is not automatically updated by the NetAct: Update the BTS SW with the SW version running on the BTS before the
Update the BTS SW, unless it is automatically updated by NetAct.
1. Check the other active alarms and act accordingly._x000D_
2.
None If that does not help, block/unblock the system module._x000D_
3. FSMr2: If that does not help, replace the system module._x000D_
FSM is fault
FSMr3: If thesource:_x000D_
faulty cell is on the baseband extension module, replace the extension module.
1.
Check Reset thethe System
optical Module (note
connection between that the all cells,
master even andthose peer thatsystem are modules.
also operational, will be reset)._x000D_
2. If a reset does not resolve the fault situation, replace the System Module._x000D_
1. Wait for start-up to be completed if a synchronization master system module has been reset._x000D_
_x000D_
2.
FBB
Flexi If there
is
BTSfault is
FDD, 1858: EFaultId_FaultyFcmConfigurationAl
source:_x000D_
Flexi BTS TDD:_x000D_ after synchronization slave's recovery reset, check the RP3-01 cable be
3.
1. Check
Reset the
Perform the
the steps alarms
System in
below the
Module in synchronization
(note that master
all cells, even system those module
that areand alsoact accordingly._x000D_
operational, will be reset)._x000D_
Perform
4. Reset the
thedoes steps below
synchronization in the
the listed
listed
master
order
order
system
until
until the
the
module.
fault
disappears._x000D_
2.
Not If
_x000D_ a reset
tracking not resolve
satellites:_x000D_ the fault situation, replace the FBBx module._x000D_
Perform
OR_x000D_
1. The most the steps common below reason in the forlisted orderindication
this fault until the fault is that disappears._x000D_
the GPS antenna installation has not been done properly, that is, the
Survey
_x000D_ in progress:_x000D_
1. Replace
antenna
Perform
1. Do has
the
nothing. the a
steps FBBx belowmodule.
The alarm is informative only. Normally, the GPS by
good sky visibility,
in the listedthe problem
order until might
the be
fault caused
disappears._x000D_installing
receiver runsthe theGPS survey antenna
for twotooreasons:
close toa) the transmitter
somebody anten
has star
No
2.
_x000D_ stored
There might position:_x000D_
time
Perform
1. during the first
One ofquestionable:_x000D_steps
the GPS start-up._x000D_
below
settings order
is incorrect.until the
Using fault disappears._x000D_
thethe manager SWand of the GPS the receiver, module,
3. There
Position
2. Ifrevert might
the isautomatic be asurveyHW fault takes in the
place GPS every receiver.
now and Check then, operation change that GPS if needed._x000D_
_x000D_
If
Tothere
_x000D_
changes, tick mark DC has in the
Voltage
valid position
should
position storage
be
data enabled
butselection,
it isfor not the itGPS
reporting
properly
might be an
receiver
Antenna
in line
indication
runs
Line.
with the the site/self
information
thesurvey
sky visibility
estimated everyfrom
is
timepoor
thethe and
GPS
actual
according
receivervt
satellite
install
EEPROM
installation the GPS a antenna._x000D_
invalid:_x000D_
is poor one - the GPS receiver turns the PPS reference OFF every now and then during the site survey. This mean
Flexi
instructions
To
3. The
1. Zone
Ifrevert
the GPS
GPS changes,Micro
and ifFDD,
there
the
installation
receiver has Flexi
are
parameter
is Zonebut
deviations
good
detected Micro
thewithTDD:_x000D_
the actual
automatic
a malfunction theinstallation,
in survey EEPROM must
still takes re-install
memoryplace ofthe
be enabled theGPS
every for antenna.
now
GPS the
and then,Note
reporting
receiver. that
Antenna
there
Perform mighteven bewhen
Line.
a (remote) the GPS
a malfunction
power an
in
reset
Perform
_x000D_
4.
2. There
Trigger the
If the aactions
might
SW update steps be below
detailed
a HW for in in
fault
BTS the
thein listed
toprevious
the
the GPS ordersteps
requested until
receiver.dothe
SW not fault
Check
version. disappears._x000D_
correct thethe situation,
operation andtherechange might thebeGPS a HW fault inifthe
module, GPS receiver. Check
needed.
NotThere
2. tracking might satellites:_x000D_
Depending
1. There
3. The most might on the
commonbe ainstalled
HW reason fault and in commissioned
for thisGPS
the faultreceiver. synchronization
indication is thatthe
Check source(s),
theoperation
GPS andsee
antenna the commissioned
installation
change the GPS has not synchronization
been
module, ifdone
needed.properly,option
thatbelow
is, the
_x000D_
antenna
Fault 4180 is raised if switch setting is not succesfull. After fourth try a group fault 3003 is raised. If there are other workinganten
has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter cells
GPS
2. There receiver
might(PPS be astepssource):_x000D_
malfunction inthethelisted
GPSorder receiver. Perform adisappears._x000D_
(remote) power reset for the GPS receiver.
Note: Perform the
1. Check the GPS receiver installation._x000D_ below in until the fault
1) Verify
_x000D_
Check theif the transportIP address related is configuration
properly configured (C-Plane at theaddress, BTS._x000D_U-Plane address, Transport network id). If the fault was raised at s
2)
2. Verify
Check if the the Real-time
GPS receiver Performance
status._x000D_ Management entity is operational and available._x000D_
1.
3) One
If theofabove the most havecommon been verified, reasons thefor this fault
operator can indication
reset the(especially
BTS at a suitable occasional time.indications) is that the GPS/GNSS antenna i
_x000D_
the GPS/GNSS antenna. Note that even when the GPS/GNSS antenna has a good sky visibility, the problem
The
3. PHICH (Physical HARQ Indication Channel) transmission power boost can be increased by reducing the might be caused
configured boosts
2. Check
Check the the connectionother possible between
alarms/fault the GPS receiver
indications and
of theFSM._x000D_
GPS/GNSS receiver and BTS and act accordingly._x000D_
_x000D_
Perform network optimization.
3. There might be a malfunction in the GPS/GNSS receiver. Perform a (remote) power reset for the GPS/GNSS receiver modul
FTM
4. If
1) Check reference
there the is only (ToP
GTP-U the as path source):_x000D_
alarming GPS/GNSS
supervision receiver connected
configuration of the eNB.to_x000D_ the GPS/GNSS antenna, check the antenna power feeding se
1.
of
2) Check
the
Check other the
the signal
receivers
supervised is being
is recieved
OFF)._x000D_
network element from for theproper
ToP Master._x000D_
operation._x000D_
Note:
_x000D_ Perform the steps below in the listed order until the alarm disappears:_x000D_
5.
3)
1. Check
Check the
the connectioncommunication
connection between
with equipment
MME, GPS/GNSS in between receiver thethe module
eNB S1and andtheGPS/GNSS
supervised antenna. Note that one antenna might be share
network element._x000D_
2. Check
Note: Perform
receiver. the
_x000D_ FTM status._x000D_
the steps below in thebased listed on orderwhether
until the BTS link
faultisdisappears:_x000D_
broken accordingly._x000D_
2. Check
_x000D_
1.Check theif the MME
connection is operational._x000D_
with adjacent
6.
1.
3. Perform
Check
Check whether
ififthe athe local/physical
speed the and transport power
duplex path resetisBTS,
setting forofthe
based
alive._x000D_
the eNB
on whether
alarming S1 port GPS/GNSS the X2receiver
is consistent
link is broken respectively._x000D_
withmodule._x000D_
the switch port that is connected directly to the eN
3.
2.
7. Check
There might the synchronization
adjacent
be asteps HW below BTS
fault settings
is of
operational._x000D_
ininthe the FTM unit.
2. Check
_x000D_
Note:
_x000D_ Perform the configuration
the of transport theGPS/GNSS
listed orderantenna
addresses theand/or
at MME._x000D_
until BTS fault possible antenna line splitter, possible line amplifier or lightning
disappears._x000D_
8.
If There might be a HW fault in the GPS/GNSS receiver module. Check the operation and change the GPS/GNSS IPreceiver
addressmo
If this
_x000D_
FlexithisBTS fault
fault FDD, happens
happens Flexiright BTSafter
right after a
a commissioning
TDD:_x000D_ commissioning or or a a configuration
configuration change, change, verify verify thethe following
of the adjacent data: BTS. of
1. Check
Block/unblock the commissioning parameters with the BTS Site Manager Commissioning_x000D_
Flexi BTS FDD,the
Wizard._x000D_
BTS._x000D_
_x000D_
Block/unblock the BTS._x000D_
_x000D_
Check
Flexi the connection
Zone Micro FDD,with Flexithe ZoneiOMS Microor the third party tool.
TDD:_x000D_
_x000D_
1.
Note:
Flexi Check Perform
Zone and Micro update
theFDD, stepsconfiguration
below
Flexi Zone in the parameters
Microlisted order
TDD:_x000D_ related
until the to cell
BTSbandwidth and channels._x000D_
2.
For Reset
_x000D_
1. Check failureandthe BTS._x000D_
update configuration
in subscriber trace session parameters related to cell bandwidth
activation/deactivation, based on the anderror
channels._x000D_
cause provided as part of the additional info fo
3.
Flexi
2. Retry
Reset BTS
- "Subscriber configuration
the FDD, Flexi BTS
BTS._x000D_
& Equipment push._x000D_
TDD:_x000D_
Trace feature not enabled": Enable theBTSsubscriber trace feature at theconfigured
BTS. Any at events correspondin
Check
1. Check and ensure
the otherinactive that the PLMNs
BTS faults. that have been listed with this fault and that have been BTS for one or mo
-3."trace
Retryreference
configuration use,push. trace cannot_x000D_ be started": This problem is out of the scope of what can be fixed at the BTS, and is with
2.
same Reset
1.Check Traceifthe the System
maximum
Reference Module number
Number. by blocking/unblocking
Aofpossible
LNADJ solution objects has isit._x000D_
tobeen reached. If all
try deactivating yes, check if there
subscriber tracesareandLNADJ objects
activating them that can be man
again._x000D
3. Update
_x000D_
-Check
"max ifnumber maximum and activate
of UE number the SW
trace session to
of LNADJW the BTS._x000D_
reached, trace cannot
was reached. If yes, becheck
started": This are
if there problemLNADJW is outobjects
of the scope
that can of be
what can be deleted.
manually fixed at tT
4. Checkif(which
2.Check
sessions the theSW is files._x000D_
maximum the number number
maximum of LNADJL of objects
active has beentraces
subscriber reached. If yes, check
supported at the ifBTS
there
at are
any LNADJL
point in objects
time) at related
the BTS.with Lt
Tryca
Check
5. Replace if theFSM._x000D_maximum number of LNRELW objects has been reached. If it has been, check if there are LNRELW objects that
_x000D_
Check
NMS._x000D_ if:_x000D_
Flexi
1) the
_x000D_ Zone
maximum
Add the LNREL Microobject FDD, pointing
number Flexi Zone
of LNRELW to the Micro per TDD:_x000D_
cell neighbor
correct and WCDMA to allowcarrier
thefrequency
handover has already
or enable thebeen reached
UE-based ANR.(is greater than or equa
1.
For Check
makes failurespacethe other
for new
in cell/interface activeLNRELW BTS faults.
object
tracetosession _x000D_
per cell and WCDMA
activation/deactivation, carrier frequency._x000D_
based on the error cause provided as part of the additional info
Reset
2.
2) Reset (block/unblock)
the maximum the feature BTSnumber the BTS
byisBlocking/Unblocking recover the faulty
it._x000D_ cell.of: psHoAllowed,
- "Cell trace notofenabled":
mobility parameters
Enable (either
the cell trace feature at the BTS. srvccAllowed)
Afterwards,oftry LNRELW
again toper cell and
activate theWCDMA
requiredcarrie
cell/in
3. Update
Block/unblock and activate
the BTS. the SW to the BTS._x000D_
- "trace reference in use, trace cannot be started": This problem is out of the scope of what can be fixed at the BTS and is within
4.
theCheck
1. same the
Check for Trace SWReference
E-UTRAN files._x000D_cellsNumber.
that operate A possibleon thesolution
same frequency is to try deactivating
layer and use all cell and interfaces
the same PCI and that traces.areAfterwards, try activat
in close vicinity._x00
5.
2. Replace
- "max
Reassign number Flexi
PCIs Zone Micro
of cell/interface
for the BTS.
discovered trace cells. sessions reached, trace cannot be started": This problem is out of the scope of what can b
cell/interface trace sessions (which is the maximum number of active cell and interface trace sessions put together supported a
If the GPS is configured as reference clock, perform the following:_x000D_
1.
Note: Check the GPS
Perform receiver
the steps below installation._x000D_
in the listed order until the alarm disappears._x000D_
2.
1. Check
Check the
the GPS receiver
availability of status._x000D_
the adjacent BTS._x000D_
Note:
3. Check Perform
the the steps below
connection between in thethelisted order
GPSBTS._x000D_
receiver until and theFSM._x000D_
alarm disappears._x000D_
2.
1. Check
the the
related adjacent
_x000D_
Note:
3. Perform and
reconnect belowthe in adjacent
the listedBTS. order until the alarm disappears:_x000D_
2.
If
1. Check
the
CheckTOP other
signal
availabilityfaults._x000D_
is configured
of MME._x000D_ as reference clock,until
perform the following:_x000D_
Note:
3. Check Perform the steps below in tothethe listed order tothethealarm disappears._x000D_
Check
2.
1. Check
Check thethe
other
the
parameters
connection
faults on
availability to of related
the
MME TOP and
MME._x000D_ server. X2 interface
BTS._x000D_ adjacent BTS._x000D_
4.
Check
3. Reset
Check thethe rootBTS.cause reported in the fault. Based on the root cause, these necessary actions must be taken:_x000D_
2.
_x000D_ Check the the parameters
connection with related to S1 interface in the BTS and MME._x000D_
MME._x000D_
4.
Note:
3. Reset
Disconnect the BTS.
Perform the steps
and belowMME. in the listed order until the alarm disappears._x000D_
1.
1. "S1
Check linkthe failure" -reconnect
Check
availability of for any active 6202 "Transport layer connection failure in S1 interface" faults. Take necessary action
MME._x000D_
Check
2. "Networkthe value of the "rimStatus" parameter
- Checkinthe LNADJG objects to findreconfiguration
all impacted RIM associations._x000D_
2.
_x000D_ Check theReconfiguration
connection withInduced" MME._x000D_ most recent network made w.r.t changes in the list of PLMNs
3.
Check
3. "MME Configuration
the value
Disconnect and ofreconnectChanges"
the "rimStatus" MME. - Check the most recent configuration changes made
parameter in LNADJG objects to find all impacted RIM associations._x000D_ at MME(s) with which the eNB is conne
If
_x000D_only a few LNADJG objects have "rimStatus" Unavailable, check if LNADJG identifiers (cell global id) of related GERAN cells
This
_x000D_ fault does not require any (special) actions.
If
Collect
_x000D_many Technical
LNADJG Logs objects from have BTS "rimStatus"
to clear anUnavailable,
alarm raisedcheck by this thefault.
connectivity
Until the to GSMisnetwork
alarm (MME<->SGSN<->BSC)._x000
active collecting of next memory dumps
If many
Flexi BTS LNADJGFDD, Flexi objectsBTShave "rimStatus" Unavailable, check the connectivity to GSM network (MME<->SGSN<->BSC)._x000
TDD:_x000D_
Source: _x000D_
-_x000D_
FCM/FCT: Perform eNB reset._x000D_
Flexi
-Flexi BTS FDD,
FSP/FBB: Change Flexithe BTS cellTDD:_x000D_
configuration to decrease call processing load._x000D_
Note: BTS
Perform FDD, theFlexi
steps BTS TDD:_x000D_
_x000D_
Flexi
Note! BTS
Perform FDD, Flexi
the steps BTS TDD:_x000D_
1.
Flexi
Note: ResetZone the
Perform System
Micro the FDD,
stepsModule._x000D_
Flexi
below Zone Micro
inModule._x000D_
the listedTDD:_x000D_
1.
Flexi
2. ResetBTS
Replace the FDD,
theSystem/Baseband
Flexi
System BTS Module TDD:_x000D_or FBBx module (according to the fault source)_x000D_
None
1.
NoReplace
Note:
_x000D_
2.
Perform
actions
Replace
the the
are
the
System/Baseband
steps below in the
required
System
Module._x000D_
_x000D_
1.
Flexi ResetZone theMicro System FDD, Module._x000D_
_x000D_
Reset
Flexi
2. the BTS
Zone
Replace Micro
the thewhen
FDD,
System allFlexi
required
Module Zone orBTSMicro
FBBx IPmodule
settings(according
TDD:_x000D_ have beentoset. the fault source)_x000D_
Note:
Flexi Perform
Zone Micro steps
FDD, below
Flexi Zone in the
Microlisted order until the fault
TDD:_x000D_ disappears._x000D_
1.
1. Reset
_x000D_
1) Check
Reset the the
if the
the stepsBTS._x000D_
far end
BTS._x000D_ has BFD switched on._x000D_
Perform
2.
Flexi
2) If the
CheckZonefault Micro
cabling below
persists,
FDD,
and replace
Flexi
networkin the the
Zone listed
BTS.
Micro
connections order until
TDD:_x000D_
toofthethe faultend.disappears._x000D_
2.
E1
1. Replace
interfaces:
Reset the the Flexi
Check
BTS._x000D_ Zone
that Micro
the BTS.
interface type thefar far-end interface is also configured to be a framed E1 interface. If this is not t
Perform the steps below in the listed order until the fault disappears._x000D_
2.
1.
1. Replace
Check
Reset the Flexi
thatBTS._x000D_
the Zone Micro BTS.
the cables are connected to the correct connectors._x000D_
JT1
_x000D_ interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. If this is not the ca
2. Check
1. Replace that thethe Flexi Zoneare
cables Micro BTS._x000D_
connected to the correct connectors._x000D_
2.
2. Check
Check that
that the
the interface
interface at
at the
the far-end
far-end interface
interface is is switched
switched on._x000D_
on._x000D_
Flexi
_x000D_ BTS FDD, Flexi BTS TDD:
3.
1. Check whether there are active alarms at the far end. If there are, follow Ethernet
the instructions forofhandling
the unit.those alarms._x000D_
3. Insert
Use Check
the BTSan
whetherSFP
Sitemodule
there are
Manager with to the
active
check correct
alarms
which laser thetype
far (class
atinterfaces end. have If 1) to the
there
been are, Gigabit
follow the
configured interface
as instructions for handling
synchronization sources. those alarms._x000D_
_x000D_
Use BTS Site Manager to check which interfaces have been configured as
Flexi
4.
1. To
CheckZone
verify thatMicro
that the FDD,
the Flexi
hardware
cables are Zone of theMicro
connected TDD:
interface
to theunit works
connectors.
synchronization
1.
ExecutePlug-out/plug-in
general sources.
SFP
configuration module. checks:_x000D_
2. Check whether the interface at the far end is switched on.
-2.
3.
None. Checkwhether
Configuration
Check for SFP validity
of CMP
there server
are (could IP be
active wrongat
address
alarms type).
and theport
farand
end.DNS server
If there are,IPfollow
address._x000D_
For
-3. all interfaces,
Insert
Configuration a compliant
of do as
routingSFP follows:
module.
entries towards remote peers._x000D_
4. To
1)Check verify that
network of the
connections interface unit
to the far worksend. correctly, connect a loop cable and check whether the alarm disappear
1. Check
2)Check
Check
1)Inspect that
Link
remotedetails the
OAM
peerscables
of event-
theand typeareand connected
Linkcritical
intermediate
of the OAM tostate
networkthe correct
event information.
elements
through connectors.
interconnections._x000D_
2. Check
3)Check
Check
2)Check the whether
Ethernet
interface
connection
state at theof
configuration
towards
information farthe
the end
at is switched
local
Certificate andRevocation
interface. remoteon. side. Listnecessarily
server._x000D_
Replace
3. Check the
whether faulty SFP.
there Note
are active that only the
4)Insert
Check
3)Check acabling
DNS Link OAM
names._x000D_
and loopback.
end.If there are,
follow
1. Clean
Check
4)Check the
thetheinstructions
size
Ethernet cables
of the and onconnectors.
file
interface handling
at those alarms.
the Certificate
local and remote List server.
side.
4. To
5)Insert verify
the OAM the hardware
loopback.
configured of the
interface type interface
a
2.loop
Check cablethatand the check
Monitor
3.
1. Checkthe that
the received
the cable
connected
Replacing faulty hardware:_x000D_
4.
2.
1. Follow
To check the signal
thetransmit network and
connectcheck whether
a loop inany
cable and other alarms
thisoninterface.
1) Re-Plug
Check cabling. expected transport unit referenced the alarm text._x000D_
_x000D_
2) Check
Check CCM configuration at remote peer.
1)
2. In casecabling. there is a unit present in the slot, remove it from the slot_x000D_
2)
and Check
Check plug youritconfiguration
back in. If the
username atunit
and remote is still
password. peer.not recognised and the alarm_x000D_
remains, replace
Provide the certificate. the faulty unit with a new one. _x000D_
_x000D_
hardware:_x000D_
1. Re-commission
Check the BFD configuration to remove the at localhardware
end. unit referenced in the alarm text._x000D_
_x000D_
Note
Try with 1: Before re-commissioning,
local management or site the supporthardware
equipment.unit must not be present in the slot._x000D_
Note 2: "Send all parameters" is required for re-commissioning.
Confirm
check that
the Ethernet Synchronization
connectivity master/slave setting are correct on the BTS and backhaul equipment.
to NTP server_x000D_
Note: Flexi
check Zone
the NTP Microconfiguration
server BTS only supports
at BTS.slave mode.
1. Check the fault name of the toggling FTM fault from the Fault name of_x000D_
this fault._x000D_
_x000D_
Flexi Zonethe
2. Follow Micro FDD, Flexi
instructions Zone
of the Micro FTM
toggling TDD:fault to clear the problem._x000D_
1. Confirm
_x000D_
Check that SyncE
the cable is desired as a synchronization source.
connectivity.
2. Confirm
Note!
Check that information
Detailed
the TOP eNB configuration settings
about the
configuration. for frequency
toggling ssmEnabled
canisbe
correct.
found in_x000D_
3. Troubleshoot with Backhaul provider on the reason SSM errors.
alarm history file, which can be downloaded using BTS Site Manager. The log file is available with Snapshot._x000D_
SW upgrading:_x000D_
- Upgrade the FSM SW release to the latest version that includes the support for the new external tranport device variant._x000
_x000D_
An
UnitIPvariant
Trafficreplacement:_x000D_
-Operator
Replacecan the check
unsupported device
the current variant
remote to another
tunnel oneparameter
endpoint that the currently running SW release supports. on NetAct or BTS SM
(ipSecBkupTunCurrRemoteEndpoint)
Instructions in release RL60
Check the active fan alarms and the airflow of the BTS.
1. Download the BTS SW again.
2.
several possibilities the BTS.
for the alarm activation, therefore a BTS Clock Frequency History feature has been developed. Y
3. If
history Step 2
feature,does not
see help,
the replace
of BTS module. Depending on the possible reason, follow the instructions below:_x00
Site Manager).
1. Make sure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarmi
_x000D_
FlexiBTS:_x000D_
1. In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term a
_x000D_
1. Block/unblock
Block/unblock the
_x000D_
1.
Note:_x000D_ the alarming
alarming module._x000D_
module._x000D_
_x000D_
If the basic accuracy of the Iub signal isreset
in order, but thereto is too much
2.
If
Update
2.
Replace
Fault
If FSP 10 the
isfor
theFR
compatible alarming
is SW
fault activemodule._x000D_
after
to the
source, LTE
BTS
perform FSM
(check
the FSPthe andversions
SW
reset LTE-2G
recovery. RF Sharing
Ifsee the
FCM/FCT isinstability,
isinthe
active use,
SW that is,
check
version,
fault source,
theupdate
if and
alarm jitter/wander
7602the
perform BCF
the is outside
NOTIFICATION
active
system SW the accep
version),
module (Sh
reset un
r
needed._x000D_
_x000D_
_x000D_
Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), un
_x000D_
3.
3. If
1. InStep
casethe
Check 1ofandaNTP2 does
BTS not help,fault,
equipment
setting._x000D_ replace the alarming
the location mightmodule._x000D_
be:_x000D_
_x000D_
Transport
2. Check the part:_x000D_
stratum parameter on the NTP server._x000D_
_x000D_
2. Savecheck
- First, the snapshot
the alarms andofcheck
the TRSthe with
download
BTS Sitestatus from the
Manager andBTS
act SWDLreport in the snapshot file.
accordingly._x000D_
-Unblock
If there theare module
no alarms, check the TRS
with BTS Site Manager. synchronization settings._x000D_
_x000D_
To
FCM cancel the fault, unblock the cell.
unit:_x000D_
_x000D_
To cancel the fault, unblock the BTS. Unblocking the BTS causes a Site Reset (FSMr3) or BTS Reset (FSMr2).
- If the TDM reference signal accuracy and the TRS are in order but the FCM unit is still alarming, run the fast tuning with BTS S
- 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, res
FlexiBTS:
- If that does not help, replace the FCM unit._x000D_
_x000D_the alarming unit/module.
Replace
1.
Note Block/unblock
that if the the alarming
in theunit/module.
1. Upgrade the reason
system is module transmission
SW. network synchronization, replacing the faulty unit does not solve the problem. Furth
_x000D_
2. Replace the unit.active
2.
4. Remove/reinsert
1. After
Check thethe other
fault the alarming
situation alarms.
has beenunit/module.
If cleared,
the ROMyou diskmight
is corrupted,
need to tunechangethethe
BTS alarming
master module.
clock because the BTS master clock adjus
_x000D_
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module.
3.
2. Replace by
Block/unblock
-1.manually thechanging
alarming unit/module.
the alarming
the module.
DAC word There are no visit)_x000D_
recovery actions and because of that the block/unblock can be tried once.
If the(during a site
Check the other active alarms. ROM disk is corrupted, change the alarming module.
- orBlock/unblock
2. with fast tuning, the in which the
alarming BTS master
module. There areclocknoisrecovery
tuned in actions
a few minutes automatically
and because of that the near the Iub reference
block/unblock (normal
can be tunin
tried once.
1. Check
Note, the other active alarms. If the ROM disktuning
is corrupted, change the alarming module.
2. Block/unblock the alarming module. There are no recovery actions and because of that the block/unblock can be tried once. t
however, that you should only use the fast in case the Iub reference signal is known to be a good one. Otherwise
_x000D_
1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module.
2. Block/unblock
Background the alarming
information: module. is
The principle There arethe
that in nomobile
recovery actionsthe
network, and because of that
synchronization goesthe from
block/unblock can be tried
the S1 interface. once.in
However,
1. If only one FSP in the BTS generates this alarm, the FSP is faulty.
operator.
2. This does
Block/unblock thenot harm the
alarming system
module. if theare
There synchronization
no recovery actions of the leased line service
and because of thatprovider is also accurate
the block/unblock can beortried
stable eno
once.
2. If all FSPs generate this alarm, the FSM is faulty.
_x000D_
1. If the alarming module is the System Module (FSM1), restart BTS.
1.
2. Reset
If that the System
does notthe Module._x000D_
help, replace the alarming FSM.
3. Block/unblock
[User
_x000D_ defined] FSM.
2. Replace
[User defined] the System Module._x000D_
4. If that does not help, replace the faulty module.
_x000D_
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
[User defined]
Note: Perform the following steps in the listed order until the fault disappears:
1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template.
_x000D_
Check the frequencies' parameters against the BTS HW configuration. The frequency is out of the min/max limit of the HW, or t
2. Check the
frequency fault history._x000D_
range
2. Download
Replace
_x000D_ the two and
alarming bandwidth.
different software packages so that the faulty file is removed from the BTS.
module.
Change the faulty module.
3. Download the software again.
4. Replace
Replace thethe SystemSystem
alarming Module. Module._x000D_
_x000D_
_x000D_
1. Check the other alarms of the BTS and FTM and act accordingly._x000D_
_x000D_
Commission
_x000D_ the BTS site with correct IP addresses.
2. Replace the System Module.
2. Wait
1. If there arethe
until nothe
other synchronization-related
module alarms
is automatically heated active,
to the start the
required fast tuning
start-up with BTS Site Manager._x000D_
temperature.
_x000D_
1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts.
3. If
2. Reset the site.
the fault Run fast
has been tuning
active again._x000D_
for more than two hours, check the environmental conditions of the site.
1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts.
_x000D_
2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module.
4.
1. Check
NOTE! This referenceline
theoperation
antenna signal
andall
affects accuracy
antenna
antennabylines
linemeasuring
devices.
and it with
Fix
cells a frequency
or replace
related theFR
to the counter
faulty (note: requires
parts/devices._x000D_
Module, not just a good
the faulty one.timebase for the
If the alarm counte
reappears
2. Restart the
tuning._x000D_
2. Alarm is MHA byonly
cancelled blocking
at RF and unblocking
Module reset orthe
BTSFlexi Radio (FR)
reset. Module.
1. Check
NOTE! theoperation
This antenna cables, connectors,
affects all antenna,
antenna lines and possible
and cells related toantenna line devices._x000D_
the FR Module, not just the faulty one. If the alarm reappears
_x000D_
_x000D_
1.
5. Check
If that the antenna
does not cables,
help, replace connectors,
the system antenna,
module. and possible antenna line devices.
2. Check the antenna line (TX-cable-antenna) impedance matching.
Replace the alarming Radio module.
2. Check the antenna line (TX-cable-antenna) impedance matching.
1. Recalibrate the RET antenna.

2. If that does not help, replace the RET unit.
1. Block/unblock the Radio module to give a power-off reset to the antenna line devices.
2. If that does not help, replace the antenna line device.
Update the SW to the BTS.
Check that Wn master module is connected to FSMr2: OptIf #4 FSMr3: OptIf #6 when SCF parameter "syncMaster" = "FALSE"
1. Check whether the heating element exists at all.
RF module:_x000D_
2. Checkthe
Replace thesingle
heaterorcontrol connection
dual PA RF module and that
with a the heater
triple PA RFis module._x000D_
working.
Alternatively, recommission the BTS with fewer cells._x000D_
3. Replace
Replace
_x000D_ thethe alarming
alarming component.
module.
FSP:_x000D_
1. Check the functionality of the antenna line device.
1.Block
1. Checkand theunblock the system
functionality module._x000D_
of the antenna line device.
2.IfCheck
2. that does not help, replace
the compatibility the system
the antenna line device and the BTS.
1. Check the functionality of the antenna line device.
_x000D_
2. Check the compatibility between the antenna line device and the BTS.
FBBx:_x000D_
3.
1. thatfunctionality
Check the the given parameters are inline
of the antenna thedevice.
valid range.
2. Check the
1.Ensure thatcompatibility
all cables between
(Power and the antennabus
Baseband linecables)
device have
and the BTS.
been connected to FBBx unit._x000D_
2.Block
2. Checkandtheunblock the system
compatibility betweenmodule._x000D_
the antenna line device and the BTS.
3.
3.IfCheck that not
this does the help,
givenreplace
parameters are inunit._x000D_
_x000D_
Ensure that there has been installed enough DSP capacity (FSP/FBBx) to BTS if a failure occurs in BTS start up phase._x000D
Alternatively, recommission the BTS with fewer cells._x000D_
1. Check the other active faults.
2.
1. Replace the
Check the alarming
other activemodule.
faults.
2. Replace the alarming module.
Perform the steps in the listed order until the BTS fault indication disappears._x000D_
_x000D_
1. Confirm if existing applied configuration is within the configured RF HW capabilities.
1.
2. Check
Check the
BTScabling connections (connected to Sync Input interface)._x000D_
and commissioning settings.
1. Block/unblock
_x000D_ RF HW unit.
3. Block/unblock the BTS.
2.
1.
4. Check if the 2.048
Block/unblock
If RF HW MHz referencethen
unit. source is workingis normally (check also the alarms of the source device) and if the 2.048 M
2. If HW
_x000D_
configuration
problem is still observed is confirmed after step 1this problem
replace RF HW caused
unit. by eNB SW. Check other active alarms.
Instructions are divided into three sections. Execute steps from section chosen based on best knowledge and common sense t
3. There
2. If problemmight is be
stillaobserved
malfunction after in step
the BTS. Perform
1 replace RF a HW BTSunit. site reset._x000D_
Instructions
4. If the A:previous are divided do intonotthree sections. Execute steps from section chosen based on best knowledge and common sense t
Section Check steps on system help,
module there
side: might be an equipment failure in the System Module. Check the operation and if perfo
1.
1. Confirm
CheckA:if Check ifconnector
existing applied seal is moduleconfiguration
properly mounted is withinand the
firmly configured
in place. RF
Section
HW capabilities. on system side:
2.
1. Check
Instructions
Check ifif theareSFP
connectordivided (Small
sealintoisForm
three Factor
properly sections. Pluggable)
mounted Execute and is properly
steps
firmly infrom connected/mounted
place. section chosen based in the System
on best Module. and
common sense t
2.
3. Check
Check BTS
if the connections
LED indicates and the commissioning
faulty SFP settings.
(connected to System Module). Replace the SFP if it is faulty.
2.
1.
3. Check if the SFP
Block/unblock
Block/unblock RF
the (Small
HW
BTS. Form Factor Pluggable) is properly connected/mounted in the System Module. If SFP connection/mo
unit.
4.
3. Check
Section
Check A:ifif Check
the
the optical
LED cable is
onindicates
system properly
module
the faulty connected/mounted
side:
SFP (connected in the SFP.
to System Module). Replace the SFP if it is faulty.
4.
5. If
1. Check HW
Clean configuration
Block/unblock
the opticalRFconnectors
HW is confirmed
unit. then
thatstep
are this problem
connected to is caused
SFP. inReset by eNB
1.
4.
2.
SW. Check
If problem
Check
ifif connector
the is
otheroptical
still observed
active
seal
cable isisproperly
alarms. properly
after mounted
1 replace and
connected/mounted RF firmly
HW unit. the RF
place.
in SFP.HW unit by block/unblock procedures and check if this sol
2.
1.
5. Check if
Block/unblock
Clean the
the optical SFPRF (Small
HW
connectors Form
unit. Factor
thatstep Pluggable)
are1connected is
toHW properly
SFP.unit. connected/mounted
procedures SFPcheck
connection/mo
if this sol
2. If
Section
3. problem
Check B:if Check
the is LED
stillon
observed
radio
indicates after
modulethe side:
faulty SFP replace RF
(connected to System Module). Replace the SFP if it is faulty.
1. Block/unblock RF HW unit.
1.
4.
2. Check
If
Section problem connector
B:if Check
the is optical
stillon
observedseal
cableis
radio isproperly
properly
after
module step
side:mounted and
connected/mounted
1 replace RFfirmly
HW unit. in inplace.
the SFP.
1.
2.
5. Block/unblock
Check
Clean if
the the SFP
opticalRFconnectors
HW
(Small unit.
Form Factor
that are Pluggable)
connected is
to properly
SFP. Reset connected/mounted in the RF module.
RF HW unit by block/unblock proceduresIf SFPandconnection/mounti
check if this sol
1. If
2. Check
problemif connector
is still observed seal is properly
after stepmounted 1 replace andRFfirmly
HW unit. in place.
3.
1.
2. Check
Check ifif the
Block/unblock the optical
SFPRF(Small HW cable unit. is properly
Form Factor connected/mounted
Pluggable) is properly in the SFP.
connected/mounted in the RF module. If SFP connection/mounti
2.
4. If problem is stillonobserved after step 1 replace end.RF HW unit.
3. Clean
Section
1. CheckB: the
if Check
Block/unblock theopticalRFconnectors
optical radio
HW cable module
unit. at RF
is properly side: module
connected/mounted Reset RFinHW the unit
SFP.by block/unblock procedures and check if this solves the
1.
2.
4. Check
If problem
Clean if connector
the opticalis still observedseal is properly
after step mounted
1 replace andRF firmly
HW in
unit. place.
1. Block/unblock
Section C:if Check RFconnectors
HW unit. at RF module end. Reset RF HW unit by block/unblock procedures and check if this solves the
2.
2. Check
If problem the stillofobserved
is SFP optical
(Small connection:
FormafterFactor
step 1Pluggable)
replace RFisHW properly
unit. connected/mounted in the RF module. If SFP connection/mounti
3.
1. Check
Section if
C: Checkoptical
the
environment cables
optical cable are isnot
temperature over
properly isbend. If yes
connected/mounted
within design then replace
limits in radio
for the theSFP.
optical
module. cable since over bending the optical fiber cables dam
2.
2. If problem
OPTIONAL: stillofobserved
is Test optical connection:
the fiber after
cable step
(f.ex. 1measure
replace RF
the HW unit.
optical attenuation) from System
4.
When
1. Clean
Check the
environment
if optical
optical
Block/unblock RF HW unit. connectors
temperature
cables are not at
is RF
out
over module
of
bend.limitsIf end.
then
yes, Reset
alarm
replace RF
is HW
expected
the unit
optical by
and
cable since overModule
block/unblock bendingend.
procedures theandPlease
optical check
check
fiber measuring
if this solves
cables theeq
damage
3.
no
2. OPTIONAL:
further
OPTIONAL: actions Test
Test arethe fiber
needed. cable (f.ex. measure the optical attenuation) from RF Module end. Please check measuring equipm
1. Block/unblock
Section C: Check RFthe HWfiber unit.cable (for example, measure the optical attenuation) from System Module end. Check measuring e
3. If
2. OPTIONAL:
problem stillofobserved
is Test optical
the fiberconnection:
cable
after step(for example
1 replacemeasure RF HW unit. the optical attenuation) from RF Module end. Check measuring equip
If alarm
2.
1. Checkisifstill
Block/unblock air observed
optical
flowRF cables
isHW notafter are executing
blocked
unit. not over by some steps
bend. Iffrom
objectsyes or sections:
then replace
walls. A,B,C
Remove thereplace
optical the RFsince
any cable module.
over bending the optical fiber cables dam
2.
2. If problem
OPTIONAL: is Test
still observed
the fiber after step
cable (f.ex. 1measure
replace RF
the HW unit.attenuation)
optical from System Module end. Please check measuring
objects
Instructions blocking
If alarm is still are airflow
observed
divided into and mount
afterthree
executing module
sections. steps according
Execute to
from sections: instructions
steps from A,B,C and
replace
section the RF
chosen module.
based on best knowledge and common senseeq t
3. OPTIONAL:
If problem is Test
recommendations.
2. the fiber cable
still observed after step(f.ex.1measure
replace RF theHW optical
unit.attenuation) from RF Module end. Please check measuring equipm
1. Check if environment temperature is within design limits for radio module. When environment temperature is out of limits then
Section A: Check on system module side:
If
3.
1.
1. alarm
Check isififstill
Block/unblock
Check observed
excessive RF HW after
sunlight
unit. executing
is causing steps from
overheating.andorsections: A,B,C
Installplace.
sunshield replace the RF module.
2.
following if connector
Check mounting airflow isinstructions
notseal is properly
blocked and
mounted
by recommendations.
some objects firmly
walls.inRemove any objects blocking airflow and mount module according to
2.
NoCheckactionifisthe SFP (Small Form Factor Pluggable) is properly connected/mounted in the System Module. If SFP connection/mo
needed.
2.
3. If problem is LED
still observed after step 1SFP replace RF HWtounit.
3. Check
1. Check ifif the fan or airindicates
excessive sunlight
flow the
is blocked faulty
is causingby some (connected
overheating.
objects. RemoveInstall System any Module).
sunshield Replace
following
blocking the SFP
mounting
objects. if it is faulty.
instructions and recommendations.
4.
2. Check
Check if
if the
fan optical
connector cable is is properly
properly connected/mounted
mounted. Mount fan in
connector the SFP.
properly.
1.
5. Check
Clean if fan or airconnectors
flow is blocked by some objects. Remove anyRF blocking objects._x000D_
3.
2. If alarmthe
Check ififisfan
optical
stillconnector
observedisthen properly
that
resetare connected
radio
mounted. module Mount
to
by SFP. Reset
block/unblock.
fan connector
HW unit by block/unblock procedures and check if this sol
properly._x000D_
1.
4. Check
If alarm fan
is still or air
observed flow is blocked
then replace by some
the moduleobjects.
fan module. Remove any blocking objects.
3.
2. If
Section alarm
Check B:ififis stillconnector
Check
fan observed
on flowradiois isthen
module
properlyresetside:radio
mounted. Mount by fanblock/unblock._x000D_
connector properly.objects._x000D_
1.
4. Check
If alarm isfan or
still air
observed blocked
then replaceby some
the fan objects.
module. Remove any blocking
1.
3.
2. Check
If alarm
Check if isconnector
ifif fan still observed seal
connectortemperature is
then properly
reset
is properly mounted. mounted
radio module and firmly
by
Mount limits in place.
block/unblock.
fan connector properly._x000D_
1.
2.
4. Check
Check
If alarm ifis environment
the SFP
still (Small then
observed FormreplaceFactor is within fandesign
Pluggable)
the is properly
module. for radio module.
connected/mounted in the RF module. If SFP connection/mounti
3.
When If alarm is
environment still observed
temperature then reset radio module
is outisofconnected/mounted
limitsdesign by
then alarm block/unblock._x000D_
3.
1.
4. Check
If alarm the optical
ifisenvironment
still observed cable is properly
temperature
then replace within
the fan module. limitsisfor expected
in the SFP.
radio and
module.
no
4. further actions are needed. at
1. Clean
When Check the
environment optical
if environment connectors
temperaturetemperature is RF
outismodule
ofwithin end.
thenReset
limitsdesign limitsRF
alarm isfor HW
expected
radio unit by
andblock/unblock procedures and check if this solves the
module.
no
When further actions
environment are needed.
2. Check
Instructions
Section C:ifactions
air
areflow
Check istemperature
divided
of notinto
optical threeisby
blocked
connection:
out of limits
some
sections. objects
Executethenoralarm
walls.is
steps expected
Remove
from section and
any
no
chosenfurther
objects blocking
based are
airflow needed.
and mount module according totoreplace
instructions and
1. Check
2.
Instructions areon
optical
if airflow best
cables
is
divided notknowledge
arethree
blocked
into not by and
oversome common
bend.
sections. If yes
objects
Execute sense
then
or walls.
steps minimize
Remove
from thethe cost cable
optical
any
section and since over bending the optical fiber cables dam
recommendations.
time
2.
objects
chosen effort.
OPTIONAL:
blocking Test the
airflow fiber
and cable
mount (f.ex.
module measure
according the optical
to attenuation)
instructions and from
andSystem Module end. Please check measuring eq
2.
1. Checkbased
VSWR ifmeasured on best
airflow is at notknowledge
RF blocked byand
(transmitter) some commonobjects
exceeds sense
or walls.
values toacceptable
minimize
Removethe costmodule.
anyRF
by
3. OPTIONAL:
recommendations.
time
objects
2. effort.
blocking Test the
airflow fiber
andand cable
mount (f.ex.
module measure
according the
Lineto optical attenuation)
instructions from
andelements RFthat
Module end. Please check measuring equipm
3. Please
Section
1. Check ifcheck
A:BTS excessive
Check impedance
on system
connections sunlight matching
module of Antenna
iscommisionning
causing side: overheating.settings. System
Install (replace
sunshield cause mismatch).
recommendations.
3. In
following ordermounting
to check ifBTS
above is mentioned steps solved the problem please ifblock/unblock RF module.
1.
2.
If
3. Check
alarm
Section
1. CheckA:
*2.Forcing isifthat
Block/unblock
ifRF connector
still
excessive
Check the
HW oninstructions
the
observed
SFP
to work
seal
sunlight
system
(Small (using
after
under isand
properly
executing
module
Form recommendations.
causing
such
mounted
theFactor
local
side: BTS
steps
overheating.andsections:
Site
from
Pluggable)
conditions might
firmly
Manager in place.
Install
is properly
results
connection
A,B,C
sunshield
in RF replace
connected
HW
athe
remote
in the
permament
connection
RF module.
System
damage
is not possible).
Module._x000D_
Check
following if the
mounting SFP (Small
instructions Form Factor Pluggable) is properly connected/mounted
1.
1.
in
Check
_x000D_
3. Check
the
ifthat
if connector
System excessive
the SFP
Module.
seal
sunlight
(Small
If SFP isand
is properly
Form recommendations.
causing mounted
Factor
connection/mounting overheating.and firmly
Pluggable) is
in place.
Install
is properly
not sunshield
correct connected in the System Module._x000D_
readjust
2. Check
Replace
following
_x000D_ if the
mounting SFP (Small
module.
instructions Form andFactor Pluggable)
recommendations. is properly connected/mounted
the
1.
in the connection/mounting.
Check the
System status of the module behind the faulty link (power on, and so on).
2.
3. Replace
Check if theModule.
the SFP indicates
LED module.If SFP connection/mounting is not correct readjust
the faulty SFP (connected to System Module).
theReset
1. connection/mounting.
the RF Module behind the faulty optical interface by blocking/unblocking it.
Replace
2.
3. Check
Check the
the
if theSFP
SFPLED if it
(Small is faulty.
indicates Form theFactor
faulty Pluggable)
SFP from
(connected both
to ends
System (the System Module and the module behind the faulty link). Th
Module).
1.
4. Swap
Check the
if the alarming
optical and working links,connected/mounted
and check where the in alarm is reported now.
Replace
2. the
If that does SFPnot it iscable
ifclear faulty.
the faultis properly
situation, replace the RF Module the that
SFP. causes the alarm.
5.
3.
#N/A
4. Clean
Check the
if theoptical
connectors,
optical connectors
cable testisthe that arecable,
fibre
properly connected to SFP.it Reset
and replace
connected/mounted ifinit the RF
is faulty.
SFP.HW
2.
unitIf by
the alarming link remains the andsame, replace thisthe System Module.
3.
1. Cleanblock/unblock
5. Swap
Reset optical connectors
the alarming
the System procedures
Module.
and working thatlinks,
are check
and ifcheck
connected solves
to SFP.the
where Reset
the problem.
alarm RFisHW reported now.
4.
unitIf the
by previous
block/unblock steps do
proceduresnot help, andreplace
check the
if module
this solves behind
problem.
3. If the alarming
Section link changes, replace the module behind that link.
4. If the B:
2. System CheckModule
alarming on radio
link remains module
is the the side:
onlysame,source causing
replace thethe alarm,Module.
System or actions mentioned above do not clear the fault situation, replac
1. CheckB:if Check
Section connector on radio seal is properly
module side:mounted and firmly in place.
2.
1. Check
3. Check
If ifif the
the alarming SFP
connector link(Small seal is
changes, Form Factor
properly
replace Pluggable)
mounted
the module is
and behindproperly
firmly inthat connected/mounted
place. link.
in
2. the
Check RF ifmodule.
the SFPIf (Small SFP connection/mounting
Form Factor Pluggable) is notiscorrect
properly readjust the
connected/mounted
connection/mounting.
in the RF module. If SFP connection/mounting is not correct re-adjust the
1. Swap the alarming and working links, and check where the alarm is reported now.
2. If the alarming link remains the same, replace the System Module.
1. Check the cables between the System Module and RF Module._x000D_
_x000D_
3. Check
1. If the alarming
changes,thereplace
System theModule
moduleand behind that link. module._x000D_
the connected
_x000D_
1. Check the cables between the System Module and RF Module._x000D_
_x000D_
2. Replace the unit that causes the alarm (System Module).
_x000D_
3. Reset
_x000D_
_x000D_
4. Replace
3. Check
1. Replace the
the alarming
RP3-01 module
cable (System
between Module).
2. Check
slave alarms
system in the synchronization master system module and act accordingly._x000D_
modules._x000D_
1. Reset
3. Check the the synchronization
status of the module master behind themodule._x000D_
system faulty link (power on, and so on)._x000D_
2. Check alarms
_x000D_ in the synchronization master system module and act accordingly._x000D_
1.
3. Switch
Reset to
the recently active
synchronization BTS configuration.
master system module._x000D_
2. Check the alarming fiber connection.
If RF is the source:
If OptIF connected to FR is the source:_x000D_
1. Check antenna mapping to the local cells in the commissioning file.
_x000D_
1. Check
BTS._x000D_
1. Check the
_x000D_
cables
antenna mapping to the
the System Module
local cells in theand RF Module. file._x000D_
commissioning
3.
1.
2. RF
Checkblock/unblock
Block/unblock
the BTS.
optical _x000D_
2.
4. Check
BTS
_x000D_ log for
reset line cables between
code violation the System
(LCV) Moduletoand
errors related FR Module._x000D_
optical links. _x000D_
3.
1. Perform FR
Block/unblock
_x000D_ block/unblock._x000D_
BTS. _x000D_
5.
2.
4. Replace
Check the alarming
configuration. module.
3. Perform
_x000D_
Verify
Note: SFP
PerformBTS reset._x000D_
(small
the form-factor
steps below inpluggable
the listedtransceiver) andBTS
order until the fiberfault
conditions.
disappears._x000D_
5.
2. Replace
Check
_x000D_ the alarming
baseband module._x000D_
bus configuration related to RP3 link speeds.
If FSP is the source:
Note: Perform the steps below in the listed order until the BTS fault indication disappears._x000D_
_x000D_
1.
1. Reset
Check the
the System
other activeModule._x000D_
BTS faults and act accordingly._x000D_
If FSP
System
2. Make
_x000D_ Module
sure reset
that the should
plug-in be performed.
type baseband unit is installed correctly._x000D_
2.
3. Replace
Reset thethe Systembaseband
alarming Module. unit._x000D_
System Module reset should be performed.
4. Replace the alarming baseband unit.
Depending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned syn
Recommission the BTS with a correct number of LCRs per RF Module.
GPS receiver (PPS source):
1.
1. Reset
If there(block/unblock)
is a GPS receiver the commissioned
BTS._x000D_ at the BTS site, note the following: If the GPS receiver is not locked to any satellite,
installationand
Software (poor sky visibility).
hardware For this, can
reconfiguration the only permanent
be made, to the cure
setupiswhere
to changefaultytheTXGPSis notantenna
used. location. One indication of a fai
Then
Define a valid TX power level value in the Radio Network configuration file (RNW) and use are
the cells will operate in the single mode unless all the TXes related to the proper cell the faulty.
Commissioning Wizard in BTS S
2. There
Check themight
otherbeactive
a malfunction
BTS faults inand
the GPS receiver. Perform a (remote) power reset for the GPS receiver.
act accordingly.
Perform the steps below in the listed order until the fault disappears. If after autonomous GPS power reset, fault does not get c
_x000D_
3. There the
Replace might be a malfunction
alarming unit. in the BTS. Perform a BTS site reset.
Control Interface not available:_x000D_
Perform
1. The the steps below ina the listed order until the fault disappears._x000D_
4. The BTS
_x000D_ GPS has cable detected malfunction
and/or connectors in the
might becontrol
damaged.interface
Checkofthe thecable
GPS and receiver. Possible reason could be that BTS and GPS
the connectors.
2. Perform a (remote) BTS
1. Reset the alarming System Module. site reset for the whole BTS._x000D_
1.
3. Reset
Perform thea BTS._x000D_
power
5.
1.
2. There
Check
Replace might
thethe be
fault a reset
HW
name
faulty
forthe
fault
of
module.
the whole
intoggling
the GPS BTS._x000D_
BTS receiver. Check the operation and change the HW, if needed.
fault._x000D_
4.
2. The
Replace
_x000D_ cable between
the alarming the GPS
System receiver
Module and the BTS might work improperly. Check the pins of the connectors (both ends of the
1.
5. Check
The in NetAct
cable thattheautoconfiguration is enabled and theberequired licensethe and commissioning file are
the available.
External
2. Follow the between
2.048MHz signal:of
instructions GPSthe receiver
toggling andBTSthe faultBTS might
to clear faulty. Check
the problem._x000D_ situation and change cable, if needed._x00
6.
1.
1. There
Check
If there
_x000D_ might
and
is an be a
correct HW
externalthe fault
contents
2.048MHz in the GPS
of the
signal receiver.
commissioning
source Check the
file.
commissioned operation
at the and
BTS change
site, the
check GPS
the BTSmodule,
faults if
ofneeded._x000D_
that device and act acc
2.
7. Check might
There the autoconnection/autoconfiguration
be a HW fault in System
the information with BTS Site Manager.
further
Note: actions.information
Detailed
Commissioning error. Only about
one theBTS System
toggling
Module Module.
frequency
can can
be set Check the operation
asbemaster
found in alarm
for and change
history
a particular the System
can beModule,
file, resource.
radio which if needed._x000
downloaded using BTS
2. Recommission the BTS with the valid commissioning file.
2. There might be a malfunction in the BTS. Perform a BTS site reset.
In case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the frequency settings.
FTM reference (TDM, SyncE or ToP as source):
In
1. case of is1840:EFaultId_TuningFailureAl, unit1841:EFaultId_UnitFaultyAl: the replace thenote
filterthe
unit.
1. If there
Check thean integrated
antenna line transmission
and antenna line (FTM) commissioned
device that causes theatalarm. BTS site, following: The FTM unit operates so
the
2. FTM synchronization priority setting) might be missing, causing the FTM's internal clock to drop to holdover mode. In this ca
1. Fix
Check or replace
the antennathe faulty parts/devices.
line and antenna line device that causes the alarm.
2.
2. Fix
1. Check or replace
the RS485 the faulty
alarms of the parts/devices.
IUANT FTM
i/f and unitantenna
and actline accordingly.
devices. Fix or replace the faulty parts/devices.
Note! Perform the steps below in the listed order until the fault disappears.
3. Checkisthe
2. Alarm synchronization
canceled only at RF settings
Moduleofresetthe FTMor theunit.
BTS reset.
Replace parallel RP3-01 fiber links towards one radio module so that the maximum mutual length difference between fibers is le
1. Check the fans and ensure that the ambient temperature on the site is acceptable.
4.
2. There might beanda malfunction in the BTS. Perform
1. Check the fan
If that does not thereplace
help, connector. the alarming module.a BTS site reset.
2. Replace the fan.
5. There might be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally, the
1.
1. Either
Check enable
the fanstheandactDistributedSite
ensure that parameter
theindication
ambient or switch toona the
temperature shorter
site fiber
is between FSM and FR._x000D_
acceptable.
indication activity (frequent BTS fault activations/cancels instead of a stable BTS fault indication state) points to the in
2. Restart
2. Check
If that doesFSM. not fan
help,
1. that the is replace
not blocked. the alarming module.
If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if perform
2. Check that the fan connector is properly mounted.

1. Check if the fan is not blocked.
Replace the fan(s).
2. Check if the fan connector is properly mounted.
In case BTS is not automatically updated by NetAct: Update SW to the BTS with SW version running on BTS before SW updat
3.
In If casethatBTS doesisnot nothelp, replace the
automatically fan. by NetAct: Update SW to the BTS with SW version running on BTS before SW updat
updated
In case BTS is not automatically updated by NetAct: Update SW to the BTS with SW version running on BTS before SW updat
Update SW to the BTS, unless it is automatically updated by NetAct.
1. Check the other active alarms and act accordingly._x000D_
2.
None If that does not help, block/unblock the system module._x000D_
3. FSMr2: If that does not help, replace the system module._x000D_
1. ResetIfthe
FSMr3: theSystem
faulty cell Module.
is on the baseband extension module, replace the extension module.
Check the optical connection between master and peer system modules.
2. If a reset does not resolve the fault situation, replace the System Module.
1. Wait for the startup to be completed if a synchronization master system module has been reset._x000D_
2.
PerformIf therethe is steps
1858: below
EFaultId_FaultyFcmConfigurationAl
in the listed order until the faultafter synchronization slave's recovery reset then check the RP3-01 cabl
disappears._x000D_
3.
_x000D_Check alarms in the synchronization master System Module and act accordingly._x000D_
Perform
4. Reset the
the steps below in the
synchronization listed system
master order until the fault disappears._x000D_
module.
Not
_x000D_ tracking satellites:_x000D_
Perform
1. Absolutely the steps the mostbelow in the listed
common reason order untilfault
for this the fault disappears._x000D_
indication is that the GPS antenna installation has not been done properly,
Survey
_x000D_ in progress:_x000D_
the
Perform
1. Do GPS theantenna
nothing. steps has
below a good
in the sky visibility,
listed order the
untilproblem
the
The alarm is informative only. Normally, the GPS receiver fault might be caused runs
disappears._x000D_ by installing
the survey the for
GPS twoantenna
reasons: tooa)close to the has
somebody transmit
star
No
2.
_x000D_ stored
There mightposition:_x000D_
time
Perform
1. duringthe first
steps
One ofquestionable:_x000D_
the GPS start-up._x000D_
below
settings order until
is incorrect. the
Usingfault disappears._x000D_
thethe
manager SWand of the GPS the receiver, module,
3. There
Position
2. Ifrevert might
the isautomatic be asurvey
HW fault takesin the
place GPS receiver.
every now andCheckthen, operation change that GPS if needed.
_x000D_
If
Tothere
changes, tick mark DC hasin the
Voltage
validposition
should
position storage
be
data selection,
enabled
but it isfor
not the itGPS
reportingmight
properly
be an
receiver
Antenna
in line
indication
runs
Line.
with the the
information
thesurvey
site/self sky visibility
every
estimated from
is poor
timethethe and
GPS
actual
according
receivervt
satellite
make
EEPROM
installation re-installation
invalid:_x000D_
is a poor of
onethe- the
GPSGPS antenna._x000D_
receiver turns the PPS reference OFF every now and then during the site survey. This mean
instructions
To
3. The
1. Ifrevert
theGPSGPS change, and if parameter
there
installation
receiver hasare is deviations
good
detected but with
still thethe
a malfunction actual
in theinstallation,
automatic survey
EEPROMshould
takes re-install
beplace
memoryenabledofthe
every
theGPS
for now
GPS antenna.
reporting
and then,
receiver.Note
Antenna
therethat
PerformLine.
mighteven bewhen
a (remote) the GPS
a malfunction
power an
in
reset
_x000D_
_x000D_
2.
TriggerThereSW might be afor
update HW BTSfaulttointhetherequested
GPS receiver. Check the operation and change the GPS module, if needed.
SW version.
2.
4. There might be
If the actions a malfunction
detailed in previous in the GPS
steps doreceiver.
not correct Perform a (remote)
the situation, power
there might reset
be a forHW
thefault
GPSinreceiver._x000D_
the GPS receiver. Check the
3. There might be a HW fault in the GPS receiver. Check the operation and change the GPS module, if needed.
#N/A
#N/A
Check the LTE505 related configuration. If the fault was raised at startup then correct the configuration and reset BTS. If the fau
#N/A
PHICH (Physical HARQ Indication Channel) transmission power boost can be increased by reducing the configured boosts for
#N/A
1) Check the GTP-U path supervision configuration of the eNB. _x000D_
2)
Note: Check Performthe supervised
the steps below network element
in the listedfor proper
order untiloperation._x000D_
the alarm disappears:_x000D_
3)
1. Check
Check the
the communication
connection with equipment
MME, based in between
on whether thethe eNBS1andlink the supervised
is broken network element._x000D_
accordingly._x000D_
Note: Perform the steps below in the listed order until the BTS Fault disappears:_x000D_
2.
1.CheckCheck if
the MME is
connection operational._x000D_
with adjacent
1.
3. Check
Check whether
ifif the speedthe and
transportduplex path isBTS,
setting
based on whether the X2 link is broken respectively._x000D_
alive._x000D_
of eNB S1 port is consistent with switch port which is connected directly to the eNB for
2.
2. Check
Check the adjacent
the configuration BTS is operational._x000D_
of transport addresses at MME._x000D_
_x000D_
Note:
_x000D_ Perform the steps below in the listed order until the BTS fault disappears._x000D_
If this
_x000D_
If fault
this fault happens
Block/unblock happens
BTS right after a commissioning or a configuration change,
right after a commissioning or a configuration change, verify
verify thethe following
of the adjacent data: IP address of
BTS.
1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard._x000D_
Block/unblock
_x000D_ BTS
2.
Check Loadthe theconnection
correct commissioning
with the iOMS fileortothethethird
BTS.party tool.
Note: Perform the steps below in the listed order until the BTS fault disappears.
For failure in Subscriber trace session activation/deactivation, based on the error cause provided as part of the additional info fo
1.
-Check Check the other
"Subscriber active BTS
& Equipment faults.
2. Reset and theensure System that the Trace
Module PLMNs
bycannot
feature
that have not enabled":
blocking/unblocking been listed Enable
with this
it. problem
theBTS subscriber
fault and tracethatfeature at BTS.
have been Any events
configured at BTScorresponding
for one or mo to
- "trace reference in use, trace be started": This is out of scope to be fixed at BTS and is scope of NMS(Networ
3. Update
1.Check
solution isif andto tryactivate
maximum deactivatingthe SW
number of to
all the BTS.
LNADJ
subscriber wastraces
reached.and Ifactivating
yes, check them if there
again.are _x000D_
LNADJ objects that can be manually deleted. Th
4. Check
_x000D_
-#N/A the SW files.
"max number of UE trace session reached, trace cannot be started": This problem is out of scope to be fixed at BTS and is sc
5. Replace
2.Check
subscriber FSM. supported
if maximum
traces numberatofBTS LNADJL at any was reached.
point in time)If hasyes,already
check ifbeen therereached
are LNADJL at BTS. objects
Try torelated
stop an with LNADJ
already object
active that
subscr
#N/A
#N/A
_x000D_
For
Addfailurethe LNREL in Cell/Interface
object pointing tracetosession
the correct activation/deactivation,
neighbor to allow the based on theorerror
handover enable cause
the provided
UE basedasANR. part of the additional info
-Reset
"Cell (block/unblock)
trace feature is not enabled": Enable
the BTS to recover the faulty cell. the cell trace feature at BTS. Then try to activate again the required cell/interface tr
- "trace reference in use, trace cannot be started": This problem is out of scope to be fixed at BTS and is scope of NMS(Networ
Block/unblock
solution is to tryBTS deactivating all cell and interfaces traces. Then try activating them again. _x000D_
-#N/A
"max number of cell/interface trace sessions reached, trace cannot be started": This problem is out of scope to be fixed at BTS
number of active cell and interface trace sessions put together supported at BTS at any point in time) has already been reached
#N/A
Note: Perform the steps below in the listed order until the alarm disappears._x000D_
1. Check
Note: the availability
Perform the steps of the adjacent
below in the listedBTS._x000D_
order until the alarm disappears._x000D_
2.
1. Check
the the
related adjacent
adjacentBTS._x000D_
BTS._x000D_
Note:
3. Perform and
Disconnect the steps belowthe
reconnect in adjacent
the listedBTS.
order until the alarm disappears:_x000D_
2.
1. Check
Check other faults._x000D_
availability of MME._x000D_
Note:
3. Perform
Check the the steps below
parameters related in to
thethe
listed order until
X2 interface tothe
thealarm disappears._x000D_
2.
1. Check
Check other
the faults on of
availability MME and
MME._x000D_ BTS._x000D_
4.
3. Reset
Check thethe BTS.
root cause reported in the fault. Based on the root cause, necessary actions need to be taken as mentioned below:
2. Check
Check thethe parameters related
connection with to S1 interface in the BTS and MME._x000D_
MME._x000D_
4.
3. Reset
Note: the BTS.
Perform
and belowMME.in the listed order until the alarm disappears.
1.
1. "S1 linkthe
Check failure" -reconnect
Check
availability of for
MME. any active 6202 "Transport layer connection failure in S1 interface" faults. Take necessary action
Check
2. the value of the "rimStatus" parameter in LNADJG objects to find all impacted RIM associations.
2. "Network
Check theReconfiguration
connection withInduced"
MME. - Check most recent network reconfiguration made w.r.t changes in list of PLMNs configu
3. "MME
Check
3. Configuration
the value
Disconnect and Changes"
ofreconnect
"rimStatus" - Check in
parameter most recentobjects
LNADJG configuration
to find changes made
all impacted at associations.
RIM MME(s) with which eNB is connected w.r
If only a few LNADJG objectsMME.
have "rimStatus" Unavailable, check if LNADJG identifiers (cell global id) of related GERAN cells
Note! This fault does not require any (special) actions.
If
Thismany
faultLNADJG
does notobjects
requirehave
any "rimStatus"
actions. Unavailable, check the connectivity to GSM network (MME<->SGSN<->BSC)
If many LNADJG objects have "rimStatus" Unavailable, check the connectivity to GSM network (MME<->SGSN<->BSC)
Source:
-Note!
FCM/FCT:
Perform Perform eNBbelow
the steps reset.in the listed order until the fault disappears.
- FSP: Change cell configuration to decrease call processing load.
#N/A
1. Reset the System Module.
#N/A
2. Replace the System Module.
#N/A
No actions are required
Reset the BTS when all required BTS IP settings have been set.
1) Check if the far end has BFD switched on.
2)
E1Check cabling
interfaces: and that
Check network connections
the interface typetoofthe
thefar end. interface is also configured to be a framed E1 interface. If this is not t
far-end
1. Check that the cables are connected to the correct connectors.
JT1 interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. If this is not the ca
1. Check that the cables are connected to the correct connectors.
2.
2. Check
Check that
that the
the interface
interface at the far-end interface is
is switched on.
Insert an SFP module with at
thethe far-end
correct interface
laser type (classswitched on.Gigabit Ethernet interface of the unit.
1) to the
3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.
3. Check
Use whether
the BTS there are to
Site Manager active
checkalarms
whichatinterfaces
the far end. If there
have been are, follow the
configured as instructions for handling
synchronization sources.those alarms.
Use BTS Site Manager to check which interfaces have been configured as
4.
1. To verify
Check
synchronizationthat thatthethe hardware
cables
sources. of the interface
are connected to theunit works
connectors.
Execute
2. Checkgeneralwhetherconfiguration
the interfacechecks:_x000D_
at the far end is switched on.
-3. Configuration
Check whether of CMP
there server IP address and port
farand
end.DNS server
are,IPfollow
address._x000D_
None.
For all interfaces,
-4.Configuration of do as are
routing
active
follows:
entries
alarms at
towards
the
remote
If there
peers._x000D_
To verify
1)Check that
network of the interface
connections unit
to the far works
end. correctly, connect a loop cable and check whether the alarm disappear
1. Check
2)Check
Check
1)Inspect that
Link
remotedetailsthe
OAM
peerscables
of event-
theand areandconnected
Linkcritical
intermediate
type of the OAM tostate
networkthe correct
event elements
through connectors.
information. interconnections._x000D_
2. Check
3)Check
Check
2)Check the whether
Ethernet
interface
connection
state at theof
configuration
towards
information farthe
the end
at is switched
local
Certificate on. side.
andRevocation
interface. remote Listnecessarily
server._x000D_
Replace
3. Check the
whetherfaulty SFP.
there Note that
are active only the
4)Insert
Check
3)Check acabling
DNS Link OAM
names._x000D_
and loopback.
end.If there are,
follow
1. Clean
Check
4)Check the
thetheinstructions
cables
size
Ethernet of the and onconnectors.
file
interface handling
at those alarms.
the Certificate
local and remoteList server.
side.
4. To verify
5)Insert
the OAMthe hardware
loopback.
configured of the
interface typeinterface
a
2.loop
Check cable
thatand the check
Monitor
3.
1. Checkthe that
the received
the cable
connected
Replacing faulty hardware:
4.
2.
1. Follow
To check the signal
thetransmit network and check
connect whether
a loop inany
cable andother alarms
thisoninterface.
1) Re-Plug
Check cabling. expected transport unit referenced the alarm text.
2) Check
1) Check CCM configuration at remote peer.
2. In casecabling.
there is a unit present in the slot, remove it from the slot
2)
and Check
Checkplugyouritconfiguration
back in. If the
username atunit
and remote peer.
is still
password. not recognised and the alarm
remains, replace
Provide the certificate. the faulty unit with a new one.
hardware:
1. Re-commission
Check to remove the
the BFD configuration hardware
at local end. unit referenced in the alarm text.
Try with local management or site support equipment.
NOTE: Before re-commissioning, the hardware unit must not be present in the slot.
check the connectivity to NTP server

check the NTP server configuration at BTS.
1. Check the fault name of the toggling FTM fault from the Fault name of
this fault.
2. Follow the instructions of the toggling FTM fault to clear the problem.
Check the cable connectivity.
Note! Detailed
Check the TOPinformation about the toggling frequency can be found in
configuration.
alarm history file, which can be downloaded using BTS Site Manager. The
SW upgrading:
log file is available with Snapshot."
- Upgrade the FSM SW release to the latest version that includes the support for the new external tranport device variant.
An
UnitIPvariant
Trafficreplacement:
-#N/A
Replace the unsupported device variant to another one that the currently running SW release supports.
Related Faults
3000:EFaultId_SystemModuleFailure, 3003:EFaultId_FbiaFailureAl
3070:EFaultId_ConfigurationError , 3003:EFaultId_FbiaFailureAl
19248, 3003:EFaultId_FbiaFailureAl
3000:EFaultId_SystemModuleFailure, 19268, 21234, 29615, 3003:EFaultId_FbiaFailureAl
10:EFaultId_NoConnectionToUnitAl , 16:EFaultId_SynchronizationAl, 69:EFaultId_Post_test_failedAl, 418:EFaultId_OseFatalE

1876:EFaultId_SRAMWrAl, 1875:EFaultId_SRAMRdAl,
10:EFaultId_NoConnectionToUnitAl 1876:EFaultId_SRAMWrAl,
, 16:EFaultId_SynchronizationAl, 4019:EFaultId_KeepAliveStatusErrorAl,
69:EFaultId_Post_test_failedAl, 40
69:EFaultId_Post_test_fa
214:EFaultId_FlashWrAl, 215:EFaultId_FlashRdAl, 216:EFaultId_FlashEraseAl, 217:EFaultId_FlashDrvAl, 218:EFaultId_FlashD
1839:EFaultId_LNAFailureAl, 1840:EFaultId_TuningFailureAl, 1840:EFaultId_TuningFailureAl, 1840:EFaultId_TuningFailureAl,
215:EFaultId_FlashRdAl, 216:EFaultId_FlashEraseAl,
1911:EFaultId_FrRxOutOfOrder, 217:EFaultId_FlashDrvAl,
1912:EFaultId_FrOutOfOrder, 218:EFaultId_FlashDbChksumAl,
1918:EFaultId_FrPowerOutputFault, 214:EFaultI
1920:EFaultId_FrNoFeedB
1932:EFaultId_FrNoFansDetected,
1802:EFaultId_FileRequestFlashAl, 1933:EFaultId_FrFanBroken, 1934:EFaultId_FrFanReducedSetSpeed,
1802:EFaultId_FileRequestFlashAl, 1811:EFaultId_BbBus_ConfFailedAl, 1935:EFaultId_FrFa
1811:EFaultId_Bb
1927:EFaultId_FrPowerDecreased, 1928:EFaultId_FrFpgaSwUpdateFailed, 1957:EFaultId_AntennaLineSwitchedOffAl, 102390
2017:EFaultId_Muksu_SRx10b8bAl,
4040:EFaultId_InitFaultManAl, 2019:EFaultId_Muksu_SsubMmAl,
4040:EFaultId_InitFaultManAl, 476:EFaultId_Rp3BusError,
94:EFaultId_UnknownUnitType, 6:EFaultId_SwDownloadA
95:EFaultId_NotSupportedUnit,
4025:EFaultId_MtuConfigurationFailureAl, 4077:EFaultId_FspOverheatingAl,
4044:EFaultId_IncoherencyCellConfigurationAl, 4208:EFaultId_RromIpConfigAl4092:EFaultId_MurkkuDefaultInitFailedAl,
, 103790
1816:EFaultId_Trans_Clk_MsgAl, 1898:EFaultId_PpsRefMissAl, 1899:EFaultId_2MExtRefMissAl, 4011:EFaultId_GPSSystemE 2058:E
6708:EFaultId_ExternallyTriggeredDspFatalErrAl
61605:BFD DOWN Ingress, 61606:BFD DOWN Egress, 61606:BFD DOWN Egress

19228
21229
21229
21233
1811:EFaultId_BbBus_ConfFailedAl, 1815:EFaultId_BbBus_SyncFailedAl, 2016:EFaultId_Muksu_SMTimeOffAl, 2017:EFaultId
10:EFaultId_NoConnectionToUnitAl , 1806:EFaultId_CommunicationFailureAl, 2000:EFaultId_OIC_TxAl, 2001:EFaultId_OIC_P
2008:EFaultId_OIC_CBRxFullAl, 2009:EFaultId_OIC_CBTxFullAl, 2010:EFaultId_OIC_EBFullAl,
2:EFaultId_UnitOverheatAl , 1827:EFaultId_StartTempBelowMinAl, 2007:EFaultId_OIC_DBTxFul
4071:EFaultId_SysDangerouslyOverheatAl, 4077:EFaultId_
2009:EFaultId_OIC_CBTxFullAl, 2010:EFaultId_OIC_EBFullAl, 2007:EFaultId_OIC_DBTxFullAl, 2008:EFaultId_OIC_CBRxFul
1825:EFaultId_PublicIPmissingAl, 4036:EFaultId_InvalidConfigurationFileAl, 6252:EFaultId_FailureInNetworkPlanFile
2010:EFaultId_OIC_EBFullAl, 2011:EFaultId_OIC_MCUBFullAl, 2014:EFaultId_Muksu_SFCRCompDevAl, 18648, 4039:EFault , 4038:EF
29:EFaultId_FileCorruptionAl , 30:EFaultId_SwUpdateAl , 29:EFaultId_FileCorruptionAl , 30:EFaultId_SwUpdateAl , 28:EFaultId
10:EFaultId_NoConnectionToUnitAl 217:EFaultId_FlashDrvAl,
, 1847:EFaultId_HardwareErrorAl, 218:EFaultId_FlashDbChksumAl,
1806:EFaultId_CommunicationFailureAl, 214:EFaultI
1871:EFaultId_
216:EFaultId_FlashEraseAl, 217:EFaultId_FlashDrvAl,
1873:EFaultId_UnsupportedProcedureAl 218:EFaultId_FlashDbChksumAl, 214:EFaultId_FlashWrAl,
, 1874:EFaultId_OutOfRangeAl , 1871:EFaultId_BusyAl, 215:EFaultI
1872:EFaultId_FormatErrorA
1834:EFaultId_AboveCurrentWindowAl,
4029:EFaultId_SwCorruptedPermanentAl, 1834:EFaultId_AboveCurrentWindowAl, 1869:EFaultId_MinorTMAFaultAl,
1850:EFaultId_SwCorruptedAl, 4029:EFaultId_SwCorruptedPermanentAl, 1870:EFaul
6:EFaultI
1874:EFaultId_OutOfRangeAl
10:EFaultId_NoConnectionToUnitAl , 1806:EFaultId_CommunicationFailureAl
Related Faults in issue 01
1923:EFaultId_FrUnitUnidentified

, 16:EFaultId_SynchronizationAl, 4019:EFaultId_KeepAliveStatusErrorAl,
69:EFaultId_Post_test_failedAl, 40
69:EFaultId_Post_test_fa
214:EFaultId_FlashWrAl, 215:EFaultId_FlashRdAl, 216:EFaultId_FlashEraseAl, 217:EFaultId_FlashDrvAl, 218:EFaultId_FlashD
1839:EFaultId_LNAFailureAl, 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl, 4043:EFaultId_TuningFrequencyOu
4043:EFaultId_TuningFrequencyOutOfRangeAl, 217:EFaultId_FlashDrvAl, 218:EFaultId_FlashDbChksumAl,
1901:EFaultId_FrCriticalFileNotFound, 214:EFaultI
1902:EFaultId_FrFileNotFound, 1907:E
0:EFaultId_ChangeFanAl , 1:EFaultId_FanPowerAl
1802:EFaultId_FileRequestFlashAl, , 1932:EFaultId_FrNoFansDetected,
1802:EFaultId_FileRequestFlashAl, 1933:EFaultId_FrFanBroken,
1811:EFaultId_BbBus_ConfFailedAl, 1934:EF
1811:EFaultId_Bb
1918:EFaultId_FrPowerOutputFault , 1920:EFaultId_FrNoFeedBackSignal , 1923:EFaultId_FrUnitUnidentified , 1924:EFaultId_
2017:EFaultId_Muksu_SRx10b8bAl,
4040:EFaultId_InitFaultManAl, 2019:EFaultId_Muksu_SsubMmAl,
4040:EFaultId_InitFaultManAl, 476:EFaultId_Rp3BusError,
94:EFaultId_UnknownUnitType, 6:EFaultId_SwDownloadA
95:EFaultId_NotSupportedUnit,
4025:EFaultId_MtuConfigurationFailureAl,
4008:EFaultId_PowerLevelNotSupportedAl, 4077:EFaultId_FspOverheatingAl, 4092:EFaultId_MurkkuDefaultInitFailedAl,
4000:EFaultId_IncoherencyInConfiguration, 2058:E
4044:EFaultId_IncoherencyCellConfig
1816:EFaultId_Trans_Clk_MsgAl, 1898:EFaultId_PpsRefMissAl, 1899:EFaultId_2MExtRefMissAl, 4011:EFaultId_GPSSystemE
6708:EFaultId_ExternallyTriggeredDspFatalErrAl, 12:EFaultId_TcomConfigAl
61605:BFD DOWN Ingress, 61606:BFD DOWN Egress, 61606:BFD DOWN Egress

Related Faults in release RL60
3000:EFaultId_SystemModuleFailure, 3030:EFaultId_FailureInOptical_Rp3Interface, 3100:EFaultId_AntennaLineFailure, 3511:

3030:EFaultId_FailureInOptical_Rp3Interface, 3003:EFaultId_FbiaFailureAl
3090:EFaultId_BtsInternalSwManagementProblem, 3003:EFaultId_FbiaFailureAl
3000:EFaultId_SystemModuleFailure, 3030:EFaultId_FailureInOptical_Rp3Interface, 3100:EFaultId_AntennaLineFailure, 3511:
3020:EFaultId_BaseBandBusFailure, 3003:EFaultId_FbiaFailureAl
#N/A
, 69:EFaultId_Post_test_failedAl, 4010:EFaultId_PLLStatusNotLockedAl
94:EFaultId_UnknownUnitType, , 40
214:EFaultId_FlashWrAl
216:EFaultId_FlashEraseAl, 217:EFaultId_FlashDrvAl, 218:EFaultId_FlashDbChksumAl, 214:EFaultId_FlashWrAl, 215:EFaultI
217:EFaultId_FlashDrvAl, 218:EFaultId_FlashDbChksumAl, 214:EFaultId_FlashWrAl, 215:EFaultId_FlashRdAl, 216:EFaultId_F
1815:EFaultId_BbBus_SyncFailedAl, 2016:EFaultId_Muksu_SMTimeOffAl, 2017:EFaultId_Muksu_SRx10b8bAl, 2019:EFaultId
2058:EFaultId_MuksuMsgRoutingFailedAl
1816:EFaultId_Trans_Clk_MsgAl, 1898:EFaultId_PpsRefMissAl, 1899:EFaultId_2MExtRefMissAl
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
#N/A
61605:BFD DOWN Ingress, 61606:BFD DOWN Egress

#N/A

Alarm NSN

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

Alarm NSN

Uploaded by

Copyright:

Available Formats

Changes between issues 01 and 01A Changes between releases RL60 and RL70

Antenna tilting is not possible or might function incorrectly.

A corrupted SW file in the FLASH has been detected._x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Degraded - when no other reference clock sources are available_x000D_

Degraded (RF using RP1 protocol)_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Not all fans failed: Module = Degraded, Fan group = Degraded_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD (macro)_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Status "degraded" is used for failure during BTS runtime_x000D_

alarming fan = out of order, fan group = degraded

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Degraded - when no other reference clock sources are available_x000D_

Degraded (RF using RP1 protocol)_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Not all fans failed: Module = Degraded, Fan group = Degraded_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Flexi BTS FDD, Flexi BTS TDD:_x000D_

Status "degraded" is used for failure during BTS runtime_x000D_

Working (FCM detected unsupported fsType value in TargetBD downloaded in SW update)

Out of order (MajorTMAFault)

Not all fans failed: Module = Working, Fan group = degraded_x000D_

Out of order - in any other case.

The master system module works properly.

Out of order (ALD)

If no other synchronization source is available at eNB, it runs in hold-over mode;

The BTS capacity possibly decreases.

The antenna line is not operating correctly. The cell is disabled.

If no other synchronization source is available at eNB, it runs in hold-over mode;

7652 BASE STATION NOTIFICATION 7651

7656 BASE DEGRADED

7656 BASE DEGRADED

7650 BASE STATION FAULTY

7652 BASE STATION NOTIFICATION

7653 CELL FAULTY

7650 BASE STATION FAULTY

7652 BASE STATION NOTIFICATION

7650 BASE STATION FAULTY

7650 BASE STATION FAULTY

7652 BASE STATION NOTIFICATION

7653 CELL FAULTY

7650 BASE STATION FAULTY

7653 CELL FAULTY

7650 BASE STATION FAULTY

7652 BASE STATION NOTIFICATION

7652 BASE STATION NOTIFICATION

7651 BASE STATION OPERATION DEGRADED

7651 BASE STATION OPERATION DEGRADED

7656 BASE STATION CONNECTIVITY LOST(No other S1

7652 BASE STATION NOTIFICATION (1.FSM. 2.FSP or FBB

7652 BASE STATION NOTIFICATION (Uncommissioned

7652 BASE STATION NOTIFICATION (1.FSM. 2.FSP or FBB

NORA: Blinking Red, Flexi: Stable Yellow (Fan Group Degraded)

Stable red ( 7650) , Blinking red ( 7651)

Alternating red and green (RF module working, MHA faulty)

Alternating red and green (RF working, MHA faulty)

Stable red (7650), Stable green (7652)