TN Alarm Description

14/08/2015
AlarmDescriptions
OPERATINGINSTRUCTIONS 5/1543HRA90120V13UenJ
AlarmDescriptions
MINILINKTNETSI
Contents
1
Introduction
SafetyInformation
Preparations
3.1
AdditionalPreparations
Overview
4.1
Consequences
4.2
AlarmAnalysis
4.3
CorrectiveActions
4.4
AlarmClearance
Alarms
5.1
AIS(Minor)
5.2
AIS(Critical)
5.3
AISonProtectionLine
5.4
AMS15MinThresholdCrossing
5.5
AMS24hThresholdCrossing
5.6
ATPCCapability
5.7
ATPCCapability(FarEnd)
5.8
AuditlogFTPTransferFailed
5.9
B1BBE15MinThresholdCrossing
5.10
B1BBE24hThresholdCrossing
5.11
B1ES15MinThresholdCrossing
5.12
B1ES24hThresholdCrossing
5.13
B1SES15MinThresholdCrossing
5.14
B1SES24hThresholdCrossing
5.15
B1UnavailablePeriod
5.16
BBE15MinThresholdCrossing
5.17
BBE24hThresholdCrossing
5.18
BER(Major)
5.19
BER(Critical)
5.20
BIDMissing
5.21
Blocked(FarEnd)
5.22
BRPressed
5.23
CarrierRecoveryLoss(Major)
5.24
CarrierRecoveryLoss(Critical)
5.25
ClockLossOfReference
5.26
CLOS
5.27
ConfigurationAborted
5.28
ConfigurationFailure(FarEnd)
http://localhost:43190/ETSI/MLTN/5_1543HRA90120V13Uen.J.html#CHAPTER4.1
1/219
14/08/2015
AlarmDescriptions
5.29
ControlSystemFailure(Minor)
5.30
ControlSystemFailure(Major)
5.31
CTRLOR
5.32
DefaultConfigurationNotAccepted
5.33
DefXconCCM
5.34
DEG(Minor)
5.35
DEG(Major)
5.36
DEGFCS
5.37
DegradedService:HDLCorIMGroup
5.38
DegradedService:IMGroup
5.39
DegradedService:LAG
5.40
DEGTHEC
5.41
DmodClock(Major)
5.42
DmodClock(Critical)
5.43
EarlyWarning
5.44
EmergencyUnlockResetKeyRequired(Warning)
5.45
EmergencyUnlockResetKeyRequired(Major)
5.46
EOSMISSING
5.47
EOSMULTIPLE
5.48
EquipmentErrororNoHoldoverCapableBoardProvider
5.49
ES15MinThresholdCrossing
5.50
ES24hThresholdCrossing
5.51
EthernetDown(Critical)
5.52
EXC
5.53
ExcessiveTemperature
5.54
EXM
5.55
FailedLogonAttempt
5.56
FAL<Number>LicenseMissing<KeyProductName>(Major)
5.57
FAL<Number>LicenseMissing<KeyProductName>(Critical)
5.58
FileIntegrityViolation(Warning)
5.59
FileIntegrityViolation(Minor)
5.60
FileIntegrityViolation(Major)
5.61
FileIntegrityViolation(Critical)
5.62
FOPR
5.63
FreeRunningModeEntered
5.64
GIDERR
5.65
GroupTimingMismatch
5.66
HardwareError:FAU
5.67
HardwareError:PluginUnit(Minor)
5.68
HardwareError:PluginUnit(Major)
5.69
HardwareError:PluginUnit(Critical)
5.70
HardwareError:RAU
5.71
HardwareError:SFP(Critical)
5.72
HCC
5.73
HighBER(Major)
5.74
HighBER(Critical)
5.75
HighDMRTTDelay
5.76
HighDMVariationRTTDelay
2/219
14/08/2015
AlarmDescriptions
5.77
HighTemperature:NPU
5.78
HighTemperature:PluginUnit
5.79
HitlessPhase
5.80
HoldoverModeEntered
5.81
ICC
5.82
IEEE1588IncompatibleHardware
5.83
IFLOSR2L(Major)
5.84
IFLOSR2L(Critical)
5.85
InRepair
5.86
IncompatibleUnits:PluginUnit
5.87
IncompatibleUnits:RAU
5.88
InsufficientLinks
5.89
InsufficientLinks(FarEnd)
5.90
InsufficientResources(Major)
5.91
InsufficientResources(Critical)
5.92
Interface/PortStatusNotUp
5.93
InterMMUChannelFailure
5.94
InternalLossofPackets
5.95
JitterBufferOverrun
5.96
L2LoopDetected
5.97
L2ExternalLoopDetected
5.98
LateArrivingFrames
5.99
LCASCRC
5.100
LFD
5.101
LicenseHandlingIsinanUnlockedPeriod(Minor)
5.102
LicenseHandlingIsinanUnlockedPeriod(Major)
5.103
LinkDown
5.104
LinkFault
5.105
LinkOAMLoopback
5.106
LOA
5.107
LockingStateLastingLongerthan30Minutes
5.108
LOF(Critical)
5.109
LOF:RS(Critical)
5.110
LOFL2R(Major)
5.111
LOFL2R(Critical)
5.112
LOFR2L(Major)
5.113
LOFR2L(Critical)
5.114
LOM
5.115
LOMF(Major)
5.116
LOMF(Critical)
5.117
LOP(Major)
5.118
LOP(Critical)
5.119
LOS(Critical)
5.120
LOS:RAUIF(Major)
5.121
LOS:RAUIF(Critical)
5.122
LOSL2R(Major)
5.123
LOSL2R(Critical)
5.124
LossofCellDelineation:ATM
3/219
14/08/2015
AlarmDescriptions
5.125
LossofCellDelineation:IMALink
5.126
LossofContinuity
5.127
LossofDelaySynchronization
5.128
LossofGrandmasterTraceability
5.129
LossofIMAFrame
5.130
LossofKeepAlive
5.131
LossofMasterClockProtection
5.132
LossofNetworkReferenceRedundancy
5.133
LostCCMs
5.134
LowBER
5.135
LowInputVoltage
5.136
LossofFrames
5.137
LowerLayerDown
5.138
MaintenanceUnlockResetKeyRequired(Warning)
5.139
MaintenanceUnlockResetKeyRequired(Major)
5.140
MalformedFrames
5.141
Mismerge(IncorrectMAIDinCCM)
5.142
ModIndex
5.143
ModeMismatch:MS
5.144
ModeMismatch:MSP
5.145
NoHoldoverProtection
5.146
NoTraffic:LAG
5.147
NoTrafficPossible
5.148
NodeInstallation
5.149
NONLCAS
5.150
NPUInstallation
5.151
OAMLocalErroredFrame<window>,<threshold>,<value>
5.152
OAMLocalErroredFramePeriod<window>,<threshold>,<value>
5.153
OAMLocalErroredSecsSummary<window>,<threshold>,<value>
5.154
OAMLocalErroredSymbolPeriod<window>,<threshold>,<value>
5.155
OAMRemoteErroredFrame<window>,<threshold>,<value>
5.156
OAMRemoteErroredFramePeriod<window>,<threshold>,<value>
5.157
OAMRemoteErroredSecsSummary<window>,<threshold>,<value>
5.158
OAMRemoteErroredSymbolPeriod<window>,<threshold>,<value>
5.159
OSPFLSADatabaseOverload
5.160
PFM
5.161
PhaseFreeRunningModeEntered
5.162
PhaseHoldoverModeEntered
5.163
PLCR
5.164
PLCT
5.165
PLM(Major)
5.166
PLM(Critical)
5.167
PowerFailure(LowerInput)
5.168
PPPDown
5.169
ProtectedLineInterface:EquipmentAlarm(Minor)
5.170
ProtectedLineInterface:EquipmentAlarm(Critical)
5.171
ProtectedLineInterface:CommunicationAlarm(Minor)
5.172
ProtectedLineInterface:CommunicationAlarm(Critical)
4/219
14/08/2015
AlarmDescriptions
5.173
ProtectedPort
5.174
PTM
5.175
RadioFrame(Major)
5.176
RadioFrame(Critical)
5.177
RadioID(Major)
5.178
RadioID(Critical)
5.179
RAI
5.180
RAUPowerSupplyChanged
5.181
RCC(Major)
5.182
RCC(Critical)
5.183
RDI(Minor)
5.184
RDI(Major)
5.185
RDIBitSetinCCM
5.186
ReceivedInvalidCCM
5.187
RemoteFailureIndication
5.188
RemoteLossofFrames
5.189
RemoteTxSwitchOver
5.190
ReservedPosition
5.191
RFInputLevel(Critical)
5.192
RFInputLevelDiv(Minor)
5.193
RFInputLevelDiv(Major)
5.194
RFInputLevelMain(Minor)
5.195
RFInputLevelMain(Major)
5.196
RFInputThreshold
5.197
RFInputThresholdProtection
5.198
RFOutputLevel(Major)
5.199
RFOutputLevel(Critical)
5.200
RFOutputLevelATPC
5.201
RLIMEOversubscription
5.202
RLIMEResourceGroup1Oversubscription
5.203
RLIMEDegradedService
5.204
RLIMENoTraffic
5.205
RLIMEReassemblyFailure
5.206
RunningConfigurationNotAccepted
5.207
RxAFC
5.208
RXFrequency(Major)
5.209
RXFrequency(Critical)
5.210
RxIFInput
5.211
RxLinkMisconnected
5.212
RxUnusable(FarEnd)
5.213
SDCDADECalibrationMismatchorNotCalibrated
5.214
SDCDivHardwareError
5.215
SDCMainHardwareError
5.216
SES15MinThresholdCrossing
5.217
SES24hThresholdCrossing
5.218
SFPLOS(Major)
5.219
SFPLOS(Critical)
5.220
SFPTemperatureHigh/Low(Critical)
5/219
14/08/2015
AlarmDescriptions
5.221
SFPTemperatureHigh/Low(Warning)
5.222
SFPVoltageHigh/Low(Critical)
5.223
SFPVoltageHigh/Low(Warning)
5.224
SFPTXBiasHigh/Low(Critical)
5.225
SFPTXBiasHigh/Low(Warning)
5.226
SFPTXPowerHigh/Low(Critical)
5.227
SFPTXPowerHigh/Low(Warning)
5.228
SFPRXPowerHigh/Low(Critical)
5.229
SFPRXPowerHigh/Low(Warning)
5.230
SQM
5.231
SQMULTIPLE
5.232
SQNC
5.233
SQNONCONT
5.234
SQOR
5.235
SquelchThresholdReached
5.236
StartingUp(FarEnd)
5.237
SyncProblem
5.238
TIM(Major)
5.239
TIM(Critical)
5.240
TIMLineSide
5.241
TIMRadioSide
5.242
TLCR
5.243
TLCT
5.244
TrafficSystemFailure(Major)
5.245
TrafficSystemFailure(Critical)
5.246
TULOM
5.247
TXFrequency(Major)
5.248
TXFrequency(Critical)
5.249
TxIFInput(Major)
5.250
TxIFInput(Critical)
5.251
TxLinkMisconnected
5.252
TXSwitchOver
5.253
TxUnusable(FarEnd)
5.254
UnabletoProtect:NPU
5.255
UnabletoProtect:E1(Minor)
5.256
UnabletoProtect:E1(Critical)
5.257
UnabletoProtect:LPS(Major)
5.258
UnabletoProtect:LPS(Critical)
5.259
UnabletoProtect:MSP(Minor)
5.260
UnabletoProtect:MSP(Critical)
5.261
UnabletoProtect:RLIME
5.262
UnabletoProtect:SWITCH(Major)
5.263
UnabletoProtect:SWITCH(Critical)
5.264
UnabletoProtectFailureonActivePort:LAN
5.265
UnabletoProtectFailureonBothPorts:LAN
5.266
UnabletoProtectFailureonPassivePort:LAN
5.267
UnabletoProtectManualMode:LAN
5.268
UnabletoProtectPortNotConnectedtoSwitch:LAN
6/219
14/08/2015
AlarmDescriptions
5.269
UnavailablePeriod
5.270
UnavailableState
5.271
UnavailableStateFarEnd
5.272
Unequipped(Major)
5.273
Unequipped(Critical)
5.274
UnexpectedMDLevelinCCM
5.275
UnexpectedMEPCondition
5.276
UnexpectedPeriodinCCM
5.277
UnitInaccessible:PluginUnit
5.278
UnitInaccessible:RMM
5.279
UnitRemoved(Minor)
5.280
UnitRemoved(Critical)
5.281
UnsupportedCapabilityProfile
5.282
UnsupportedUnitType
5.283
UPM
5.284
UserInput
5.285
WrongNPSoftware
5.286
WrongNPUSoftware
5.287
WrongPosition
5.288
WrongSoftware:PluginUnit
5.289
WSTLOSL2R(Major)
5.290
WSTLOSL2R(Critical)
5.291
WSTLOSR2L(Major)
5.292
WSTLOSR2L(Critical)
5.293
XPICCableDisconnected
5.294
XPICLOS
ReferenceList
Abstract
ThisdocumentdescribesthealarmshandledintheMINILINKTNintermsofdefinition,causesand
suggestedrecoveryactiontobetakeninordertoremovethealarmcauses.
1Introduction
ThisdocumentdescribesthealarmsforMINILINKTN.Italsoproposesactionstobetakenupon
receptionofanalarm.
WhenMINILINKTNisusedinHighDensityMicrowaveExpansion(HDME)withMINILINKPT,the
alarmsoriginatingfromMINILINKPTaremappedtoMINILINKTNalarms.Thisdocumentdoesnot
describethemappedalarmsinHDME.IfanalarmwithProbableCauseequalto
"RemoteAlarmInterface"israised,refertoMINILINKPTCPIforthedescriptionofthealarm.For
moreinformationonthemappingmechanism,seeFaultManagementOperations,Reference[3].
2SafetyInformation
Makesurethattheinformationinthefollowingdocumentshasbeenunderstoodbythepersons
performingtheprocedures:
7/219
14/08/2015
AlarmDescriptions
PersonalHealthandSafetyInformation,Reference[8]
SystemSafetyInformation,Reference[21]
SupplementarySafetyInformationforMINILINK,Reference[20]
3Preparations
Thissectionpresentsthepreparationsneededforasuccessfulcompletionoftheproceduresinthis
instruction.
3.1AdditionalPreparations
Considerthefollowingadditionalpreparations:
Readthroughallapplicablesectionsandmakesurereferenceddocumentsareavailable.
MakesureyouhaveaccesstotheNetworkElement(NE)usingMINILINKCraft.Formore
information,seeAccessingaNetworkElement,Reference[1].
4Overview
Eachalarmsectionbeginswithashortdescriptionofthealarm.Thefollowinginformationisalso
includedasreportedintheNotificationListinMINILINKCraft:
SpecificProblem Thenameofthealarm.
Source
AlarmType
Severity
Thesourceofthealarm.
Thealarmtype.ThealarmtypesarespecifiedinFaultManagementOperations,
Reference[3].
Theseverityofthealarm,forexample,CriticalorMinor.Allseveritiesare
describedinFaultManagementOperations,Reference[3].
ProbableCause Theprobablecauseofthealarm.
Thenameofeachalarmsectioncancontainfourparts:SpecificProblem,Source,AlarmType,and
Severity.Onlythepartsthatarenecessarytospecifyauniquealarmareincludedineachheading.
Forexample,thenameofthealarmHardwareError,withsourceequaltopluginunitandseverity
equaltocritical,isnamed"HardwareError:PluginUnit(Critical)".
Optionally,thelistwithinformationfromtheNotificationListinMINILINKCraftisfollowedby
subsectionsthatdescribethealarminmoredetail,seebelow.
4.1Consequences
Sectionthatdescribeswhatelseoccursasaresultofthisalarm,informsifaswitchoccurs,andif
thereareanymaskedalarms.
4.2AlarmAnalysis
Sectiondescribinghowtofindtherootcauseofthealarm.
4.3CorrectiveActions
Sectionthatdescribeswhichactionscanbetakentorecoverthesystem.
8/219
14/08/2015
AlarmDescriptions
4.4AlarmClearance
Sectionthatdescribeshowthealarmiscleared,automaticallyorasaresultofcorrectiveaction.
5Alarms
Thissectiondescribesallalarmslistedalphabetically.
5.1AIS(Minor)
AlarmIndicationSignal(AIS)
TheAISindicatesatransmissioninterruptioninthepathtothereceiver,thatis,thereisaproblem
withtheincomingtrafficsignal.ThisalarmindicatesthatthefaultoriginatesoutsidethereceivingNE.
SpecificProblem AIS
Source
E1
E2/E3
MS/RS
VC12
VC4
AlarmType
CommunicationAlarm
Severity
Minor
ProbableCause AlarmIndicationSignal
5.1.1Consequences
Serviceunavailable.
5.1.2AlarmAnalysis
TheAIScanbeusedforfaultlocalizationpurposesandtodeliverinformationofdefectsorfaults
acrosslayers.
Thepossibleproblemswiththetrafficsignalarethefollowing:
Thetrafficsignalbecomescorrupt.
Thetrafficsignalislost.
ThiscanoccurbetweendifferentNEs,forexample,betweentwoLTUs,butalsowithintheNE,for
example,betweenVC4andVC12inanLTU.TheAISisgeneratedinbothcases.
Tomaintaintransmissioncontinuity,theNEreplacesthemissingorcorruptinputsignalwith
continuousbinaryones,thatistheAIS,andthissignalissenttothenextNE.
5.1.3CorrectiveActions
9/219
14/08/2015
AlarmDescriptions
Figure1WorkflowforAISAlarmCorrectiveActions
Dothefollowing:
1. Checkthattheconfigurationiscorrectonthefarend.Takecorrectiveactionsasneeded.
2. Checkthelinestatusonthenearendandthefarend.Takecorrectiveactionsasneeded.
3. Checkthealarmconditionsonthenearendandthefarend.Takecorrectiveactionsasneeded.
4. Checkthestatusoftheradiolinkbetweenthenearendandthefarend.Takecorrectiveactions
asneeded.
5. Repeatthestepsaboveforallsectionsbetweenintermediateelementsonthepath.
10/219
14/08/2015
AlarmDescriptions
5.1.4AlarmClearance
TheAISisclearedwhentheNEthatistransmittingtheAISreceivesavalidtrafficsignal.
5.2AIS(Critical)
SpecificProblem AIS
Source
FramedE1
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause AlarmIndicationSignal
5.2.1Consequences
Serviceunavailable.
5.2.2AlarmAnalysis
acrosslayers.
11/219
14/08/2015
AlarmDescriptions
Dothefollowing:
asneeded.
12/219
14/08/2015
AlarmDescriptions
5.2.4AlarmClearance
5.3AISonProtectionLine
SpecificProblem AIS
Source
E1
AlarmType
CommunicationAlarm
Severity
Minor
ProbableCause Indeterminate
5.3.1Consequences
Serviceunavailable.
5.3.2AlarmAnalysis
acrosslayers.
13/219
14/08/2015
AlarmDescriptions
Dothefollowing:
asneeded.
14/219
14/08/2015
AlarmDescriptions
5.3.4AlarmClearance
5.4AMS15MinThresholdCrossing
AdaptiveModulationSeconds(AMS)
Theterminalusestheminimummodulationlongertimethantheconfigured15minutethreshold.The
thresholdiscrossedduringthecurrent15minuteinterval.
ApplicableforRAUIF(1+0).
ApplicableforSWITCH(1+1).
SpecificProblem AMS15mthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
QualityOfServiceAlarm
Severity
Minor
ProbableCause ThresholdCrossed
5.4.1Consequences
Decreasedtrafficcapacityforalongertimethanexpected.
Theproblemcanbetemporary,butifthealarmcontinuesoverconsecutive15minintervals,trythe
followingactions:
1. VerifytheRadioFrequency(RF)inputpowerlevel:itmustbeatleast5dBabovethe106Bit
ErrorRatio(BER)thresholdforthecurrentconfigurationduringgoodweatherconditions.See
linkbudgetcalculationforthecorrectlevel.
2. Checktheantennaalignment,seeInstallingOutdoorEquipment,Reference[5].
3. Checkifobstaclesareplacedintheradiopathbetweenthetwohops'antennas(atclearsky
conditions).
4. VerifythattheRadioNetworkPlanningiscorrect.
5.4.3AlarmClearance
Thealarmisclearedwhenthetimespentintheminimummodulationattheendoftheintervalisless
thantheAMS15minresetthreshold.
5.5AMS24hThresholdCrossing
AdaptiveModulationSeconds(AMS)
Theterminalusestheminimummodulationlongertimethantheconfigured24hourthreshold.
15/219
14/08/2015
AlarmDescriptions
SpecificProblem AMS24hthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
Severity
Minor
5.5.1Consequences
Decreasedtrafficcapacityforalongertimethanexpected.
Trythefollowingactions:
ErrorRatio(BER)thresholdforthecurrentconfigurationduringgoodweatherconditions.See
linkbudgetcalculationforthecorrectlevel.
conditions).
4. VerifythattheRadioNetworkPlanningiscorrect.
5.5.3AlarmClearance
Thealarmisnotclearedautomatically.Toclearitdoawarmrestart,seeTroubleshooting,Reference
[22].
5.6ATPCCapability
AutomaticTransmitPowerControl(ATPC)
TheterminalisconfiguredforATPC,buttheRAUdoesnotsupportATPC.Thisalarmisactivatedonly
ifATPCisturnedon(anydirection).
SpecificProblem ATPCCapability
Source
RAU
AlarmType
EquipmentAlarm
Severity
Major
ProbableCause ReplacebleUnitTypeMismatch
5.6.1Consequences
ItisnotpossibletouseATPCfunctionality.
16/219
14/08/2015
AlarmDescriptions
ReplacetheRAUtoonewithATPCsupport,seeReplacingaRadioUnit,Reference[16].
5.6.3AlarmClearance
ThealarmisclearedwhenATPCisdisabledoriftheRAUisreplacedtoaRAUwithATPCsupport.
5.7ATPCCapability(FarEnd)
TheterminalonthefarendisconfiguredforATPC,butatleastoneofthepluginunitsdoesnot
supportATPC.
SpecificProblem ATPCCapability(FarEnd)
Source
AllMMUs
AlarmType
EquipmentAlarm
Severity
Major
5.7.1Consequences
ItisnotpossibletoenableATPCfunctionality.
ReplacefarendterminaltoonewithATPCsupport,seetherelevantReplacingdocument.
5.7.3AlarmClearance
ThealarmisclearedwhenATPCisdisabledorifthefarendterminalisreplacedtoonewithATPC
support.
5.8AuditlogFTPTransferFailed
ThealarmisraisedifthetransferoftheauditlogtotheactiveFTPserverfails.
SpecificProblem FTPtransferoftheauditlogfilefailed
Source
NE
AlarmType
EquipmentAlarm
Severity
Warning
ProbableCause ConnectionEstablishmentError
5.8.1Consequences
TheauditlogisnotuploadedtotheactiveFTPserver.
ManuallyretrievetheauditlogandchecktheFTPserverconfiguration.
5.8.3AlarmClearance
17/219
14/08/2015
AlarmDescriptions
Thealarmisautomaticallyclearedthenexttimetheauditlogissuccessfullytransferredtotheactive
FTPserver.ThealarmcanalsobeclearedbydisablingthealarminMINILINKCraft.
5.9B1BBE15MinThresholdCrossing
BackgroundBlockError(BBE)
TheSynchronousDigitalHierarchy(SDH)BBEcounterthreshold,setfor15mintimewindows,is
crossedthelast15minutes.TheBBErepresentsthenumberofSynchronousTransportModulelevel1
(STM1)framescontainingatleastoneerror,andiscomputedbytheMMUwhentheoperatorenables
G.826performancemonitoring.ThealarmisraisedwhentheBBEcountervaluecrossestheBBE
thresholdsetbytheoperator.ThisvalueisconfiguredwithintheG.826performance15minutes
monitoringoptions.
SpecificProblem B1BBE15minthresholdcrossing
Source
RADIORS
AlarmType
Severity
Major
5.9.1Consequences
Degradedtraffic.
followingactions:
conditions).
2. Verifythatthereceivedsignalpowerisasexpected(byperformingalinkbudgetcalculation).
3. Checkthatnointerferencesignalispresent.
4. ReplacetheMMU,seeReplacinganMMU,Reference[13]orReplacinganMMU2CS,Reference
[14].
5. ReplacetheRAU,seeReplacingaRadioUnit,Reference[16].
5.9.3AlarmClearance
Thealarmisclearedatthenext15minutesintervalwheretheBBEcounterthresholdnolongeris
crossed.
5.10B1BBE24hThresholdCrossing
TheSynchronousDigitalHierarchy(SDH)BBEcounterthreshold,setfor24htimewindows,is
crossedthelast24hours.TheBBErepresentsthenumberofSynchronousTransportModulelevel1
(STM1)framescontainingatleastoneerror,andiscomputedbytheMMUwhentheoperatorenables
G.826performancemonitoring.ThealarmisraisedwhentheBBEcountervaluecrossestheBBE
thresholdsetbytheoperator.ThisvalueisconfiguredwithintheG.826performance24hours
monitoringoptions.
18/219
14/08/2015
AlarmDescriptions
SpecificProblem B1BBE24hthresholdcrossing
Source
RADIORS
AlarmType
Severity
Major
5.10.1Consequences
Degradedtraffic.
Theproblemcanbetemporary,butifthealarmcontinuesoverconsecutive24hintervals,trythe
followingactions:
conditions).
2. Verifythatthereceivedsignalpowerisasexpected(bypreformingalinkbudgetcalculation).
[14].
5.10.3AlarmClearance
Thealarmisclearedatthenext24hoursintervalwheretheBBEcounterthresholdnolongeris
crossed.
5.11B1ES15MinThresholdCrossing
ErroredSeconds(ES)
TheSynchronousDigitalHierarchy(SDH)EScounterthreshold,setfor15mintimewindows,is
crossedthelast15minutes.TheESrepresentsasecondinwhichoneormoreSynchronousTransport
Modulelevel1(STM1)framescontainatleastoneerror,andiscomputedbytheMMUwhenthe
operatorenablesG.826performancemonitoring.ThealarmisraisedwhentheEScountervalue
crossestheESthresholdsetbytheoperator.ThisvalueisconfiguredwithintheG.826performance
15minutesmonitoringoptions.
SpecificProblem B1ES15minthresholdcrossing
Source
RADIORS
AlarmType
Severity
Minor
5.11.1Consequences
Thisalarmindicatesdegradedtraffic.Iftheproblemcontinues,itcanleadtoB1SES15minthreshold
crossing,seeSection5.13.
19/219
14/08/2015
AlarmDescriptions
followingactions:
conditions).
[14].
Thealarmisclearedatthenext15minutesintervalwheretheEScounterthresholdnolongeris
crossed.
5.12B1ES24hThresholdCrossing
ErroredSeconds(ES)
TheSynchronousDigitalHierarchy(SDH)EScounterthreshold,setfor24htimewindows,iscrossed.
TheESrepresentsasecondinwhichoneormoreSynchronousTransportModulelevel1(STM1)
framescontainatleastoneerror,andiscomputedbytheTRUwhentheoperatorenablesG.826
performancemonitoring.ThealarmisraisedwhentheEScountervaluecrossestheESthresholdset
bytheoperator.ThisvalueisconfiguredwithintheG.826performance24hoursmonitoringoptions.
SpecificProblem B1ES24hthresholdcrossing
Source
RADIORS
AlarmType
Severity
Minor
5.12.1Consequences
Thisalarmindicatesdegradedtraffic.Iftheproblemcontinues,itcanleadtoB1SES24hthreshold
followingactions:
conditions).
[14].
20/219
14/08/2015
AlarmDescriptions
Thealarmisclearedatthenext24hourintervalwheretheEScounterthresholdnolongeriscrossed.
5.13B1SES15MinThresholdCrossing
SeverelyErroredSeconds(SES)
TheSynchronousDigitalHierarchy(SDH)SEScounterthreshold,setfor15mintimewindows,is
crossed.TheSESrepresentsasecondinwhichmorethan30%oftheSynchronousTransportModule
level1(STM1)framescontainatleastoneerror,andiscomputedbytheMMUwhentheoperator
enablesG.826performancemonitoring.ThealarmisraisedwhentheSEScountervaluecrossesthe
SESthresholdsetbytheoperator.ThisvalueisconfiguredwithintheG.826performance15minutes
monitoringoptions.
SpecificProblem B1SES15minthresholdcrossing
Source
RADIORS
AlarmType
Severity
Major
5.13.1Consequences
Degradedtraffic.
conditions).
[14].
Thealarmisclearedatthenext15minutesintervalwheretheSEScounterthresholdnolongeris
crossed.
5.14B1SES24hThresholdCrossing
TheSynchronousDigitalHierarchy(SDH)SEScounterthreshold,setfor24htimewindows,is
crossed.TheSESrepresentsasecondinwhichmorethan30%oftheSynchronousTransportModule
level1(STM1)framescontainatleastoneerror,andiscomputedbytheMMUwhentheoperator
enablesG.826performancemonitoring.ThealarmisraisedwhentheSEScountervaluecrossesthe
SESthresholdsetbytheoperator.ThisvalueisconfiguredwithintheG.826performance24hours
monitoringoptions.
21/219
14/08/2015
AlarmDescriptions
SpecificProblem B1SES24hthresholdcrossing
Source
RADIORS
AlarmType
Severity
Major
5.14.1Consequences
Degradedtraffic.
conditions).
[14].
Thealarmisclearedatthenext24hourintervalwheretheSEScounterthresholdnolongeris
crossed.
5.15B1UnavailablePeriod
TheSynchronousDigitalHierarchy(SDH)UnavailablePeriodcounterthresholdiscrossed.Thehopis
inunavailabilitystatus,since10consecutiveSeverelyErroredSeconds(SES)aredetected.
SpecificProblem B1UnavailablePeriod
Source
RADIORS
AlarmType
Severity
Major
ProbableCause PerformanceDegraded
5.15.1Consequences
TrafficLoss.
Performthefollowingactions:
1. Checkifobstaclesareplacedintheradiopathbetweenthetwohopsantennas(atclearsky
conditions).
22/219
14/08/2015
AlarmDescriptions
[14].
Thealarmisclearedwhenthehopexitsfromtheunavailabilitystatus.Thisoccurswhen10
consecutivenonSESaredetected.
5.16BBE15MinThresholdCrossing
BBEthresholdcrossingfor15mincompositeperformancemonitoring.Thealarmisraisedwhenthe
BBEcountervaluecrossestheBBEthresholdsetbytheoperator.
SpecificProblem BBE15minthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
Severity
Major
5.16.1Consequences
Degradedtraffic.
followingactions:
conditions).
[14].
Thealarmisclearedatthenext15minutesintervalwheretheBBEcounterthresholdnolongeris
crossed.
23/219
14/08/2015
AlarmDescriptions
5.17BBE24hThresholdCrossing
BBEthresholdcrossingfor24hourcompositeperformancemonitoring.Thealarmisraisedwhenthe
BBEcountervaluecrossestheBBEthresholdsetbytheoperator.
SpecificProblem BBE24hthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
Severity
Major
5.17.1Consequences
Degradedtraffic.
followingactions:
conditions).
[14].
Thealarmisclearedatthenext24hoursintervalwheretheBBEcounterthresholdnolongeris
crossed.
5.18BER(Major)
BitErrorRatio(BER)
TheBERcalculatedbytheForwardErrorCorrection(FEC)forthereceivedsignalexceedstheBER
alarmthreshold.TheincomingsignalissocorruptthattheFECisunabletocorrecttheincoming
traffic.
SpecificProblem BER
24/219
14/08/2015
AlarmDescriptions
Source
RAUIF
AlarmType
Communication
Severity
Major
ProbableCause DegradedSignal
5.18.1Consequences
RadioProtectionSwitchselectstheotherdemodulationpathifitssignalqualityisbetter.
Note: MakesurethattheSwitchModeissettoManualonboththenearendandthefarend
terminalbeforetroubleshooting.Performalltheactionsontheactiveunit.SetSwitchMode
toAutooncethetroubleshootingiscompleted.
Dothefollowing:
1. VerifythattheRFinputpoweronthereceivingRAUisatleast5dBabovethethresholdforBER
106forthecurrentconfiguration.Seelinkbudgetcalculationforthecorrectlevel.
IftheRFinputpowerisnotatleast5dBabovethethreshold,gotoStep2.
IftheRFinputpowerisatleast5dBabovethethreshold,gotoStep12.
2. PerformanRFlooptestonthenearendRAU.TurnofftheRAUtransmitteronthefarend
duringthetest.
IftheRFinputpowerisnotabout50dBm(10dB)duringthetest,replacetheRAUon
thenearend.DescribethefaultontheBlueTagandsendittotheRepairCentertogether
withthefaultyRAU.
Iftheinputpowerisabout50dBm(10dB)duringthetest,gotoStep3.
3. Checkfadingconditionsandweathercircumstances.
Iflinkperformanceisnotaffectedbypropagationissues,gotoStep4.
Iflinkperformanceisaffectedbypropagationissues,consultthetransmissiondesign
departmentonhowtoaddressthelinkbudget.
4. Checkthealarmsandstatusofthefarendterminal.
Iftherearenoalarmsraisedonthefarendterminal,gotoStep5.
Iftherearealarmsraisedonthefarendterminal,findtherootcausesofthesealarms
first,andtakecorrectiveactionsaccordingtothealarmdescription.IftheBERalarmis
stillraisedonthenearendterminalafterclearingthealarmsonthefarendterminal,go
toStep5.
5. Verifythatthenearendterminalconfigurationmatchesthefarendterminalconfiguration.
Iftheconfigurationisnotcorrect,reconfigurethenearendterminalandthefarend
terminalaccordingtotheSiteInstallationDocumentation(SID).
Iftheconfigurationiscorrect,gotoStep6.
6. PerformanRFlooptestonthefarendRAU.TurnofftheRAUtransmitteronthenearend
duringthetest.
thefarend.DescribethefaultontheBlueTagandsendittotheRepairCentertogether
withthefaultyRAU.
IftheRFinputpowerisabout50dBm(10dB)duringthetest,gotoStep7.
25/219
14/08/2015
AlarmDescriptions
7. Checkforpossibleobstaclesinterferingwiththelineofsightandcheckthattheantennasare
mountedatthecorrectheightaccordingtothelinkbudgetplanning.
Ifthereareobstaclesortheantennasarenotmountedatthecorrectheight,consultthe
networkdesigndepartmenttoreviewthelinkbudgetplanning.
Iftherearenoobstaclesinthelineofsightandtheantennasaremountedatthecorrect
height,gotoStep8.
8. Makesuretheantennasarealignedcorrectlyonthenearendandthefarendtomeetthelink
budgettarget.
Iftheantennasarenotalignedcorrectly,takecorrectiveactions.
Iftheantennasarealignedcorrectly,gotoStep9.
9. VerifythattheRAUsarecorrectlymountedontheantennas,thatanyflexiblewaveguidesare
notdamaged,andthatcorrectpolarizationissetonbothsidesofthehop.
Ifyoufindanyproblem,takecorrectiveactions.
Ifyoudonotfindanyproblems,gotoStep10.
10. Replacetheantennaonthenearend.
IftheBERalarmisnotclearedafterthereplacement,reinstalltheinitialantennaandgo
toStep11.
IftheBERalarmisclearedafterthereplacement,describethefaultontheBlueTagand
sendittotheRepairCentertogetherwiththefaultyantenna.
11. Replacetheantennaonthefarend.DescribethefaultontheBlueTagandsendittotheRepair
Centertogetherwiththefaultyantenna.
13. PerformacoldrestartoftheMMUandtheRAUonthenearend.RestartMINILINKCraft.
Caution!
Acoldrestartwilldisturbthetraffic.
IftheBERalarmisnotclearedaftertherestart,gotoStep14.
IftheBERalarmisclearedaftertherestart,monitorthehopforfurtherBERalarms.If
thealarmisraisedagainwhiletheRFinputlevelishigherthanthethresholdlevelfor
BER106forthecurrentconfiguration,gotoStep14.
14. PerformanIFlooptestonthenearendMMU.
IftheBERalarmisnotclearedduringthetest,replacetheMMUonthenearend.
DescribethefaultontheBlueTagandsendittotheRepairCentertogetherwiththefaulty
MMU.
IftheBERalarmisclearedduringthetest,gotoStep15.
duringthetest.
IftheBERalarmisnotclearedduringthetest,gotoStep23.
26/219
14/08/2015
AlarmDescriptions
toStep17.
17. PerformanRXlooptestonthefarend.
IftheBERalarmiscleared,reviewthequalityoftheincomingtrafficonthefarendMMU
lineside.
18. Performaninterferencetest,seeVerifyinganInstallation,Reference[24].
Ifthereisnointerferenceduringthetest,gotoStep19.
Ifthereisanyinterferenceduringthetest,consultthetransmissiondesigndepartmentto
reviewnetworkplanningandlinkbudget.
19. ReplacetheMMUonthefarend.
IftheBERalarmisnotclearedonthenearendafterthereplacement,reusetheinitial
MMUonthefarend,andgotoStep20.
IftheBERalarmisclearedonthenearendafterthereplacement,describethefaulton
theBlueTagandsendittotheRepairCentertogetherwiththefaultyMMU.
20. ReplacetheRAUonthefarend.
RAUonthefarend,andgotoStep21.
theBlueTagandsendittotheRepairCentertogetherwiththefaultyRAU.
21. ChecktheradiocableforinterferenceontheIFsignalbetweentheMMUandtheRAUonthe
farendterminalwithaSiteMasteroraSpectrumAnalyzer.Makesurethatthereisno
interferenceinthefrequencyrangeof0400MHz.
Ifthereisnointerference,gotoStep22.
Ifthereisanyinterference,checkthecablesfordamagesandreplacethecablesif
needed.Monitortheinterferingsourceandremoveitifpossible,orreroutetheIFcables
nottobedisturbedbytheinterferingsource.
22. ReplacetheradiocablesandtheconnectorsbetweentheMMUandtheRAUonthefarend
terminal.
23. ReplacetheRAUonthenearend.
RAU,andgotoStep24.
nearendterminalwithaSiteMasteroraSpectrumAnalyzer.Makesurethatthereisno
terminal.
FormoreinformationonhowtoreplacetheRAU,seeReplacingaRadioUnit,Reference[16].
27/219
14/08/2015
AlarmDescriptions
Formoreinformationonantennaalignmentandantennainstallation,seeInstallingOutdoor
Equipment,Reference[5].
FormoreinformationonhowtoreplacetheMMU,seeReplacinganMMU,Reference[13].
ThealarmisclearedwhentheBERestimationisbelowtheBERalarmthreshold.
5.19BER(Critical)
BitErrorRatio(BER)
TheBERcalculatedbytheForwardErrorCorrection(FEC)forthereceivedsignalexceedstheBER
alarmthreshold.TheincomingsignalissocorruptthattheFECisunabletocorrecttheincoming
traffic.
SpecificProblem BER
Source
RAUIF
AlarmType
Communication
Severity
Critical
5.19.1Consequences
Degradationofsignalquality.OnlyforPlesiochronousDigitalHierarchy(PDH).
Dothefollowing:
duringthetest.
withthefaultyRAU.
Iftheinputpowerisabout50dBm(10dB)duringthetest,gotoStep3.
28/219
14/08/2015
AlarmDescriptions
toStep5.
duringthetest.
withthefaultyRAU.
mountedatthecorrectheightaccordingtothelinkbudgetplanning.
height,gotoStep8.
budgettarget.
toStep11.
Caution!
29/219
14/08/2015
AlarmDescriptions
MMU.
duringthetest.
toStep17.
lineside.
terminal.
30/219
14/08/2015
AlarmDescriptions
RAU,andgotoStep24.
terminal.
ThealarmisclearedwhentheBERestimationisbelowtheBERalarmthreshold.
5.20BIDMissing
TheAMMbackplaneID(serialnumber)cannotberead.
Source
AMMbackplaneorpluginunit
AlarmType
EquipmentAlarm
Severity
Warning
ProbableCause Corrupt/brokenAMMbackplaneorpluginunit
Figure4ExampleoftheBIDMissingAlarminMINILINKCraft
31/219
14/08/2015
AlarmDescriptions
5.20.1Consequences
Noimpactontraffic.
ReplaceorchecktheapplicableHW.
ThealarmisclearedwhenthecorruptorbrokenHWhasbeenreplaced.
5.21Blocked(FarEnd)
ThefarendInverseMultiplexeroverATM(IMA)grouphasbeenblocked(inhibitedbythe
ManagementSystem).
SpecificProblem Blocked(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause RemoteAlarmInterface
5.21.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbetransmittedoverthespecificIMAgroupbefore
boththenearendandfarendgroupsbecomeoperational.
Unblockthefarendgroup.
ThealarmisclearedwhenfarendIMAgrouphasbeenunblocked.
5.22BRPressed
BoardRemoval(BR)buttonispressed,whichisarequesttotakethepluginunitoutofservice.The
pluginunitcanthenberemoved.TheBRbuttonmustalwaysbepressedbeforeremovingaplugin
unit,otherwise,theNEmightshowunstablebehavior.
SpecificProblem BRPressed
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
ProbableCause ReplacableUnitProblem
5.22.1Consequences
TheBR(yellow)LEDisON.ThepluginunitgetsoperationalstatusOutofServiceandalltraffic
32/219
14/08/2015
AlarmDescriptions
relatedalarmsforthispluginunitaredisabled.ForinformationonthelocationoftheBRbuttonand
BRLED,seeLEDDescriptions,Reference[6].
Ifthepluginunitisremovedpermanently,followtheinstructionsinRemovingaPlugInUnit,
Reference[10].
Ifthepluginunitisreplacedbyanotherunitwiththesamefunction,followtheinstructionsinthe
relevantReplacingdocument.
Thealarmisclearedwhenthepluginunitisremoved.ThealarmisalsoclearediftheBRbuttonis
pressedonceagain.
5.23CarrierRecoveryLoss(Major)
TheSynchronousDigitalHierarchy(SDH)carriersignalcannotberecoveredatthedemodulator.The
140MHzspectrumcomingfromthereceivingRAUistoolowortoocorruptedtolockthecarrier.Itis
generallycausedbydeepfading.
Thealarmcanalsobecausedbythefollowingevents:
TransmissionproblemonthehopothersideTx.
Deepfadingontheradiopath.
SpecificProblem CarrierRecoveryLoss
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause ReceiverFailure
5.23.1Consequences
ThesystemswitchesonthestandbyfaultlessMMU.
1. Verifythatthetransmitteronhopothersideiscorrectlyworking.
2. VerifythefrequencysettingsontheTxandRx.
ErrorRatio(BER)thresholdforthecurrentconfiguration.Seelinkbudgetcalculationforthe
correctlevel.
4. IncreasetheRFinputpowerlevel(ifpossible)byactingonthefarendoutputpower.
6. Verifythelinkbudgetcalculation.
7. CheckforpresenceofRFinterferers.
8. CheckforpresenceofIntermediateFrequency(IF)interferers(andeventuallytheRFcoaxial
33/219
14/08/2015
AlarmDescriptions
cableshielding).
9. Evaluatethepresenceofselective(multipath)fading.
10. PerformanIFloopontheMMU,seeFaultManagementOperations,Reference[3].Ifthealarm
isstillpresentthenreplacetheactiveMMU,seeReplacinganMMU,Reference[13]orReplacing
anMMU2CS,Reference[14].
11. PerformanRFloopontheRAU,seeFaultManagementOperations,Reference[3].Ifthealarm
isstillpresentthenreplacetheactiveRAU,seeReplacingaRadioUnit,Reference[16].
12. Executetroubleshootingasstep10and11onthefarendandactconsequently.
Thealarmisclearedwhenagoodqualitysignalisreceived.
5.24CarrierRecoveryLoss(Critical)
TheSynchronousDigitalHierarchy(SDH)carriersignalcannotberecoveredatthedemodulator.The
140MHzspectrumcomingfromthereceivingRAUistoolowortoocorruptedtolockthecarrier.Itis
generallycausedbydeepfading.
Thealarmcanalsobecausedbythefollowingevents:
TransmissionproblemonthehopothersideTx
Deepfadingontheradiopath
SpecificProblem CarrierRecoveryLoss
Source
RAUIF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.24.1Consequences
TrafficislostonthelinesideandanAlarmIndicationSignal(AIS)issent.
1. Verifythatthetransmitteronhopothersideiscorrectlyworking.
2. VerifythefrequencysettingsontheTxandRx.
correctlevel.
cableshielding).
34/219
14/08/2015
AlarmDescriptions
isstillpresentthenreplacetheactiveMMU,seeReplacinganMMU,Reference[13]orReplacing
anMMU2CS,Reference[14].
Thealarmisclearedwhenagoodqualitysignalisreceived.
5.25ClockLossOfReference
ThealarmisraisedwithLTU155whenthefollowingconditionsoccuratthesametime:
NetworkSynchronizationfunctionisdisabled.
LTU155isconfiguredtouseRxsignalasclocksource.
ThereisnovalidincomingSTM1signaltotheLTU155.
SpecificProblem ClockLossOfReference
Source
MS/RS
AlarmType
EquipmentAlarm
Severity
Minor
5.25.1Consequences
NoclocksourceavailablefortheLTU155.
EnableNetworkSynchronizationfunctionorprovidevalidSTM1signalfortheLTU155.
ThealarmisclearedwhenNetworkSynchronizationfunctionisenabledorthereisvalidincoming
STM1signaltotheLTU155.
5.26CLOS
ClientSignalLoss(CLOS)
Aclientmanagementframe(PTI=001b)signalingLossofClientSignal(LCS)(UPI=00000001b)is
received.
SpecificProblem CLOS
Source
GFP
AlarmType
CommunicationAlarm
Severity
Critical
35/219
14/08/2015
AlarmDescriptions
ProbableCause LossOfSignal
5.26.1Consequences
Interfacedown.
RemovefailureintheFarEnd.
Thealarmisclearedwhencommunicationisrecovered.
5.27ConfigurationAborted
ThefarendtriestouseInverseMultiplexeroverATM(IMA)configurationparametersnotcompatible
withthenearendconfiguration.
SpecificProblem ConfigurationAborted
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause ConfigurationOrCustomizationError
5.27.1Consequences
CheckthefarendIMAconfiguration:M(IMAFrameSize)=128,SymmetricConfigurationand
Operation.
Thealarmisclearedwhenthefarendconfigurationisacceptedbythenearend.
5.28ConfigurationFailure(FarEnd)
ThefarenddoesnotaccepttheconfigurationparametersofthenearendInverseMultiplexerover
ATM(IMA)deviceandreportsunacceptableconfigurationparameters.
SpecificProblem ConfigurationFailure(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Major
36/219
14/08/2015
AlarmDescriptions
5.28.1Consequences
CheckthefarendIMAconfiguration:M(IMAFrameSize)=128,SymmetricConfigurationand
Operation.
Thealarmisclearedwhenthenearendconfigurationisacceptedbythefarend.
5.29ControlSystemFailure(Minor)
SpecificProblem ControlFailure
Source
NE
SAU
AlarmType
EquipmentAlarm
Severity
Minor
ProbableCause CommunicationsSubsystemFailure
5.30ControlSystemFailure(Major)
Amalfunctionrelatedtomanagement,theNPUorthecontrolbusfails.
SpecificProblem ControlFailure
Source
NE
AlarmType
EquipmentAlarm
Severity
Major
5.30.1Consequences
Themanagementfunctionalityisreducedorunavailable.
Trythefollowing:
AccesstheNElocally,seeAccessingaNetworkElement,Reference[1].
1. CheckthesiteLANportconfiguration.
2. Checkthealarmlist.
ReplacetheNPUifitisdamaged,seeReplacinganNPU,Reference[15].
37/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhenthemanagementfunctionalityisworkingagain.
5.31CTRLOR
UndefinedcontrolwordononeormoreVirtualContainers(VCs).
SpecificProblem CTRLOR
Source
VCG/LCASNonStandardAlarms
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause CommunicationsProtocolError
5.32DefaultConfigurationNotAccepted
TheMMU/RAU/SFPcouldnotacceptthedefaultconfiguration.Thiscanbecausedbyanerrorinthe
configurationfileorbyahardwareerror.Theservice(yellow)LEDflashesduringthisalarm.
SpecificProblem Defaultconfigurationnotaccepted
Source
AllMMUs
AllRAUs
AllSFPs
AlarmType
EquipmentAlarm
Severity
Major
ProbableCause ReplaceableUnitTypeMismatch
5.32.1Consequences
Failuretomanagethepluginunitortheentirenode.
Thealarmisclearedwhentheconfigurationfileisaccepted.
5.33DefXconCCM
TheMaintenanceEndPoint(MEP)hasreceivedatleastoneContinuityCheckMessage(CCM)from
eitheranotherMaintenanceAssociation(MA)IDoralowerMaintenanceDomain(MD)level,theCCM
intervalofwhichhasnotyettimedout.
Note: ThisalarmisonlyavailablewhenusingtheIEEE802.1agstandardforConnectivityFault
Management(CFM).
SpecificProblem DefXconCCM
Source
LANwithMEP
WANwithMEP
LAGwithMEP
38/219
14/08/2015
AlarmDescriptions
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause PathTraceMismatch
Nocorrectiveactionisrequired.
5.34DEG(Minor)
DegradedSignal(DEG)
Probablecause:incomingsignalofthislayerviolatesthesignaldegradationthreshold.
SpecificProblem DEG
Source
AU4
MS
TU3
TU12
VC3
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Minor
5.34.1Consequences
Servicedegraded.
Checklinkconnectionofthislayer.
5.35DEG(Major)
DegradedSignal(DEG)
Theincomingsignalviolatesthedegradeddefectthresholdforaperiodlongerthanthedefined
monitoringperiod.
SpecificProblem DEG
Source
MS/RS
VC12
VC4
39/219
14/08/2015
AlarmDescriptions
AlarmType
Severity
Major
5.35.1Consequences
Theserviceisdegraded.
Checkandcorrectthelinkconnectionofthefaultylayer.
Thealarmisclearedwhentheincomingsignalisbelowthedegradeddefectthreshold.
5.36DEGFCS
DegradedFrameCheckSequence(DEGFCS)
AnexcessivenumberofframeswithFCSerrorisreceived.Thethresholdforthisalarmis
configurable.
SpecificProblem DEGFCS
Source
GFP
AlarmType
Severity
Critical
5.36.1Consequences
Interfacedown.
1. ChecktheBitErrorRatio(BER),seeTroubleshooting,Reference[22].
2. Checkthesource.
Alessthan1/10thresholdnumberofframeswithFCSerrorisreceived.Thethresholdforthisalarm
isconfigurable.
5.37DegradedService:HDLCorIMGroup
Oneorseveral(butnotall)InverseMultiplexer(IM)interfacesaredown,leadingtodecreasedspeed
onthebridgeconnection.
SpecificProblem Degradedservice
Source
HDLC
40/219
14/08/2015
AlarmDescriptions
IMGroup
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause Unavailable
1. ChecktheBitErrorRatio(BER).
2. Checkthesource.
5.38DegradedService:IMGroup
ThedefinedthresholdfordiscardedframesontheInverseMultiplexer(IM)grouplayerisexceeded.
SpecificProblem Degradedservice
Source
IMGroup
AlarmType
Severity
Major
5.39DegradedService:LAG
Foroneormoreportsbutnotalltheportsallocatedtothelinkaggregationgroup,thelinkisdown.
SpecificProblem DegradedService
Source
LAG
AlarmType
CommunicationAlarm
Severity
Major
Note: WhenExtendedBufferisenabled,thisalarmissuppressed.
5.40DEGTHEC
DegradedtHEC.AnexcessivenumberofframeswithtHECerrorisreceived.Thethresholdforthis
alarmisconfigurable.
SpecificProblem DEGTHEC
Source
GFP
AlarmType
Severity
Critical
41/219
14/08/2015
AlarmDescriptions
5.40.1Consequences
Interfacedown.
2. Checkthesource.
Alessthan1/10thresholdnumberofframeswithtHECerrorisreceived.Thethresholdforthisalarm
isconfigurable.
5.41DmodClock(Major)
TheinternaldatarateoftheMMUdoesnotcorrespondtothereceiveddatarate.Thisfaultcausesbit
slipinthecompositebitstream.
Probablecausesforthefault:faultyMMUorfading.
SpecificProblem DmodClock
Source
RAUIF
AlarmType
EquipmentAlarm
Severity
Major
ProbableCause TimingProblem
5.41.1Consequences
ThisconditioncanleadtoUnabletoProtectorhitlessswitchingnotworking,ifaswitchneedstobe
donelater.
Iftheproblemiscausedbyfadingwhenspacediversityisused,thesystemisprobablyableto
correctitselfandnoactionisnecessary.Otherwise,trythefollowing:
Makeamanualswitch.
Testtheradiohop.
ThealarmisclearedwhentheinternaldatarateoftheMMUmatchesthereceiveddatarate.
5.42DmodClock(Critical)
TheInternaldatarateoftheMMUdoesnotcorrespondtothereceiveddatarate.Thisfaultcausesbit
slipinthecompositebitstream.
Probablecausesforthefault:faultyMMUorfading.
42/219
14/08/2015
AlarmDescriptions
SpecificProblem DmodClock
Source
RAUIF
AlarmType
EquipmentAlarm
Severity
Critical
ProbableCause TimingProblem
5.42.1Consequences
TrafficLoss.
Testtheradiohop.
ThealarmisclearedwhentheinternaldatarateoftheMMUmatchesthereceiveddatarate.
5.43EarlyWarning
Thethresholdforearlywarningispassed.Probablecausesarethefollowing:
Fading(flatorselective).
Badantennaalignment.
Linkbudgetcalculationnotcorrect.
PresenceofInterferers.
SpecificProblem EarlyWarning
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Minor
5.43.1Consequences
Degradationofthesignalquality.
Note: Ifthealarmoccursina1+1protectedterminal,makesurethattheSwitchModeissetto
Manualonboththenearendandthefarendterminalbeforetroubleshooting.Takeall
actionsontheactiveunit.SetSwitchModetoAutooncethetroubleshootingiscompleted.
1. VerifythattheRFinputpoweronthereceivingRAUisatleast10dBabovethethresholdfor
BER106forthecurrentconfiguration.Seelinkbudgetcalculationforthecorrectlevel.
43/219
14/08/2015
AlarmDescriptions
duringthetest.
withthefaultyRAU.
toStep5.
duringthetest.
withthefaultyRAU.
mountedatthecorrectheightaccordingtothelinkbudget.
height,gotoStep8.
budgettarget.
IftheBERalarmisnotclearedafterthereplacement,reinstalltheinitialantenna,andgo
toStep11.
44/219
14/08/2015
AlarmDescriptions
Caution!
MMU.
duringthetest.
toStep17.
lineside.
45/219
14/08/2015
AlarmDescriptions
terminal.
RAU,andgotoStep24.
terminal.
ThealarmisclearedwhentheBERestimationisbelowthethreshold.
5.44EmergencyUnlockResetKeyRequired(Warning)
ThenumberofavailableEmergencyUnlocktokensdecreasedtoone,becausetheuserentered
EmergencyUnlockperiod.WhenenteringEmergencyUnlockperiodagain,thetokensrunoutandthe
severityofthisalarmischangedtoMajor.
SpecificProblem EmergencyUnlockResetKeyRequired
Source
LicenseHandler
AlarmType
OperationalViolation
Severity
Warning
46/219
14/08/2015
AlarmDescriptions
InstallEmergencyUnlockRefilllicenses,seeInstallingandManagingLicenses,Reference[4].
ThealarmisclearedassoonastheuserinstallsatleastoneEmergencyRefilllicense.
5.45EmergencyUnlockResetKeyRequired(Major)
NoEmergencyUnlocktokensavailable,becausetheuserenteredEmergencyUnlockperiodseveral
times.WhenanEmergencyUnlockRefilllicenseisinstalled,theseverityofthisalarmischangedto
Warning.
SpecificProblem EmergencyUnlockResetKeyRequired
Source
LicenseHandler
AlarmType
Severity
Major
InstallEmergencyUnlockRefilllicenses,seeInstallingandManagingLicenses,Reference[4].
ThealarmisclearedassoonastheuserinstallsatleastoneEmergencyRefilllicense.
5.46EOSMISSING
EndOfSequence(EOS)
NoneoftheVirtualContainers(VCs)belongingtotheVirtualConcatenationGroups(VCGs)received
EOS.
SpecificProblem EOSMISSING
Source
AlarmType
CommunicationAlarm
Severity
Minor
5.47EOSMULTIPLE
EndOfSequence(EOS)
MorethanoneVirtualContainer(VC)belongingtotheVirtualConcatenationGroup(VCG)received
EOS.
SpecificProblem EOSMULTIPLE
Source
AlarmType
CommunicationAlarm
47/219
14/08/2015
AlarmDescriptions
Severity
Minor
5.48EquipmentErrororNoHoldoverCapableBoardProvider
SpecificProblem Equipmenterrorornoholdovercapableboardprovider
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause ClockSynchronisationProblem
5.49ES15MinThresholdCrossing
ErroredSeconds(ES)
ThePlesiochronousDigitalHierarchy(PDH)EScounterthreshold,setfor15mintimewindow,is
crossedthelast15minutes.AnErroredSecondisaonesecondperiodwithoneormoreerrored
blocks,oratleastonedefect.
SpecificProblem ES15minthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
Severity
Minor
5.49.1Consequences
Thisalarmindicatesdegradedtraffic.Iftheproblemcontinues,itcanleadtoSES15minthreshold
followingactions:
conditions).
[14].
48/219
14/08/2015
AlarmDescriptions
Thealarmisclearedatthenext15minutesintervalwheretheEScounterthresholdnolongeris
crossed.
5.50ES24hThresholdCrossing
ErroredSeconds(ES)
ThePlesiochronousDigitalHierarchy(PDH)EScounterthreshold,setfor24htimewindow,iscrossed
thelast24hours.AnErroredSecondisaonesecondperiodwithoneormoreerroredblocks,orat
leastonedefect.
SpecificProblem ES24hthresholdcrossing
Source
RAUIF(1+0)
SWITCH
AlarmType
Severity
Minor
5.50.1Consequences
Thisalarmindicatesdegradedtraffic.Iftheproblemcontinues,itcanleadtoSES24hthreshold
followingactions:
conditions).
[14].
Thealarmisclearedatthenext24hoursintervalwheretheEScounterthresholdnolongeris
crossed.
5.51EthernetDown(Critical)
ProblemhasbeendetectedontheL1causedbyEthernetcarriernotdetected.Thisalarmcanbe
causedbyanEthernetcableproblem,configurationerrororpowerdownontheconnecteddevice.
49/219
14/08/2015
AlarmDescriptions
SpecificProblem Ethernetdown
Source
Bridge
EthernetBridge
LAN
AlarmType
CommunicationAlarm
Severity
Critical
5.51.1Consequences
NoCarrierDetectedontheEthernetPort.NoEthernetconnection.
50/219
14/08/2015
AlarmDescriptions
Figure5WorkflowforEthernetDownAlarmCorrectiveActions
Trythefollowing:
1. MakesurethattheadministrativestatusissettoUpontheappropriateportfortheETUorthe
NPU.
2. Onsiteaction:CheckthattheEthernetcableconnectedtotheappropriateportisnotdamaged.
3. Onsiteaction:PerformacoldrestartoftheETUortheNPU.
4. Onsiteaction:ReplacetheETUortheNPU.DescribethefaultontheBlueTagandsenditto
theRepairCentertogetherwiththefaultyETUorNPU.
FormoreinformationonhowtoreplacetheETU,seeReplacinganLTU,ETU,orSAU3,Reference
[12].
51/219
14/08/2015
AlarmDescriptions
FormoreinformationonhowtoreplacetheNPU,seeReplacinganNPU,Reference[15].
ThealarmisclearedwhenacarrierisdetectedontheEthernetport.
5.52EXC
IncaseofPoissondistributionoferrorsassumed,theBitErrorRatio(BER)exceedsthethresholdfor
excessiveerrors.
SpecificProblem EXC
Source
AU4
MS
TU3
TU12
VC3
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause ExcessiveBitErrorRate
5.52.1Consequences
Serviceunavailable.
Thisisatransmissionerror.Thealarmceasesifthealarmconditionceases.Thatis,checkthecause
forthissituationonthelink.
5.53ExcessiveTemperature
Theunitreachesanexcessivetemperature.
Thiscanbecausedbyfanfailure,toohighambienttemperature,componentfailure,orairflow
blocking.
SpecificProblem ExcessiveTemperature
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
ProbableCause HighTemperature
5.53.1Consequences
52/219
14/08/2015
AlarmDescriptions
Bothcontrolandtrafficfunctionsareshutdown(operationalstatusOutofService)toreduce
dissipatedpowertoaminimum.Thisisdonetoavoidpermanentdamage.
Trythefollowing:
Checkthatthefanisworkingproperly,seeLEDDescriptions,,Reference[6].
Checktheambienttemperatureandtakemeasuresifitistoohigh.
Checkforcomponentfailurealarmsandtakecareofanyproblems.
Makesurethattheairflowisnotblocked.
Thealarmisclearedwhenthetemperaturegoesbelowthehightemperaturethresholdfortheplugin
unit.
5.54EXM
ExtendedHeaderIdentifierMismatch(EXM)
TheExtendedHeaderIdentifier(EXI)fieldinareceivedframedoesnotmatchtheconfiguredvalue.
SpecificProblem EXM
Source
GFP
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause PayloadTypeMismatch
5.55FailedLogonAttempt
Thealarmisraisediftherearethreeconsecutivefailedlogonattempts.
SpecificProblem Securityissueonlogon
Source
NE
AlarmType
CommunicationAlarm
Severity
Warning
ProbableCause ConnectionEstablishmentError
5.55.1Consequences
Thealarmcanbeanindicationofapotentialsecuritythreat.
Ifnecessary,disablelocalaccesstotheNE.
ThealarmisclearedeithermanuallyinMINILINKCraftorautomaticallyafterawarmorcoldrestart.
53/219
14/08/2015
AlarmDescriptions
5.56FAL<Number>LicenseMissing<KeyProductName>(Major)
Alicenseforalicensecontrolledfeature,withthespecifiedproductnumber,ismissing.TheNEisin
anunlockedperiodorthelicensecontrolledfeatureisnotlocked.
SpecificProblem FAL<Number>LicenseMissing<KeyProductName>
Source
NE
AlarmType
Severity
Major
ProbableCause DenialOfService
5.56.1Consequences
AwarningisissuedontheLicensespageinMINILINKCraft.
Installthecorrespondinglicenseforthelicensecontrolledfeaturebyfollowingtheinstructionsin
InstallingandManagingLicenses,Reference[4].
Thealarmisclearedassoonasthecorrespondinglicenseisinstalled.
5.57FAL<Number>LicenseMissing<KeyProductName>(Critical)
Alicenseforalicensecontrolledfeature,withthespecifiedproductnumber,ismissing.TheNEisin
lockedperiodandthelicensecontrolledfeatureislocked.
SpecificProblem FAL<Number>LicenseMissing<KeyProductName>
Source
NE
AlarmType
Severity
Critical
ProbableCause DenialOfService
5.57.1Consequences
AnerrorisissuedontheLicensespageinMINILINKCraft.
Installthecorrespondinglicenseforthelicensecontrolledfeaturebyfollowingtheinstructionsin
InstallingandManagingLicenses,Reference[4].
Thealarmisclearedassoonasthecorrespondinglicenseisinstalledorwhenenteringanunlocked
period.
Enteringanunlockedperiodispossibleinoneofthefollowingways:
Usertriggeredunlock.
54/219
14/08/2015
AlarmDescriptions
UpgradingfromanunlockedmodeSWreleasetoalockedmodeSWrelease,thatis,upgrading
fromreleasesbeforeMINILINKTN5.3toMINILINKTN5.3orlaterrelease.
UpgradingfromalockedmodeSWreleasetoanewmainlockedmodeSWrelease.
5.58FileIntegrityViolation(Warning)
ThealarmisraisediftheinternalfilesoftheNEaremodified.
Formoreinformationaboutthealarmcauseandtheappliedseverity,seetheFileIntegrityViolation
report.
SpecificProblem FileIntegrityViolation
Source
NE
AlarmType
EnvironmentalAlarm
Severity
Warning
ProbableCause FileError
ThealarmisclearedandthefileintegritymonitoringfunctionisalsodisabledwhentheFile
IntegrityViolationisnotselectedontheSecurityAlarmHandlingpageinMINILINKCraftor
whentheCLIcommandsetfileintegrityalarmoffisused.
5.59FileIntegrityViolation(Minor)
report.
Source
NE
AlarmType
EnvironmentalAlarm
Severity
Minor
5.60FileIntegrityViolation(Major)
report.
Source
NE
55/219
14/08/2015
AlarmDescriptions
AlarmType
EnvironmentalAlarm
Severity
Major
5.61FileIntegrityViolation(Critical)
report.
Source
NE
AlarmType
EnvironmentalAlarm
Severity
Critical
5.62FOPR
FailureonProtocolReceive(FOPR)
OneormoreLinkCapacityAdjustmentScheme(LCAS)controlpacketswithCRC(CyclicRedundancy
Check)errorisreceivedonanyoftheVirtualContainers(VCs)belongingtotheVirtualConcatenation
Group(VCG).
SpecificProblem FOPR
Source
VCG/LCASStandardAlarms
AlarmType
CommunicationAlarm
Severity
Minor
2. Checkthesource.
56/219
14/08/2015
AlarmDescriptions
5.63FreeRunningModeEntered
Thenetworksynchronizationfunctionentersthefreerunningstatus.
SpecificProblem Freerunningmodeentered
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause LossOfSynchronisation
5.63.1Consequences
ThesynchronizationoutputsignalissquelchedortheappropriateSynchronizationStatusMessage
(SSM)valueispropagatedoninterfacessupportingSSM.
Noactionrequired.
Thealarmisclearedwhenthenetworksynchronizationfunctionenterslockedstatus.
5.64GIDERR
GroupIDError(GIDERR)
Activechannels(VCs)inaVirtualConcatenationGroup(VCG)haveadifferentGroupID.
SpecificProblem GIDERR
Source
AlarmType
CommunicationAlarm
Severity
Minor
Checkthesource.
5.65GroupTimingMismatch
Thefarendtransmitclockisdifferentfromthenearendtransmitclockmode.SincetheAAU
supportsonlytheCommonTransmitClock(CTC)itislikelythatthefarendtransmitclockhasbeen
settotheITC.
SpecificProblem GroupTimingMismatch
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Critical
57/219
14/08/2015
AlarmDescriptions
5.65.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbetransmittedoverthespecificInverseMultiplexer
overATM(IMA)groupbeforeboththenearendandfarendgroupsbecomeoperational.
5.65.2AlarmAnalysis
ThefarendtransmitclockcouldbesetinITCmodeinsteadofCTC,whichistheonlymodesupported
bytheAAU.
CheckifthefarendtransmitclockissettoCTC.
Thealarmisclearedwhenboththenearendandfarendareconfiguredwiththesametransmitclock
mode(CTC).
5.66HardwareError:FAU
FanUnit(FAU)
Amalfunctionrelatedtohardware.
SpecificProblem HardwareError
Source
FAU
AlarmType
EquipmentAlarm
Severity
Critical
ProbableCause CoolingFanFailure
5.66.1Consequences
AhardwareerrorontheFAUmayadditionallyresultinmalfunctionduetoHighTemperature(see
Section5.77)orExcessiveTemperature(seeSection5.53)inotherunitsintheNE.
58/219
14/08/2015
AlarmDescriptions
Figure6WorkflowforHardwareError:FAUAlarmCorrectiveActions
Note: Toclearthealarm,performallthecorrectiveactionsbelowonsite.
Dothefollowing:
1. VerifythattheFAUiscorrectlymountedintheAMM.
2. IftheFAUisfedwithaseparatepowersupplycable,verifythatthecableiscorrectlyconnected
andthatitsuppliesthecorrectpoweraccordingtoFAUrequirement.
3. ReplacetheFAU,seeReplacingaFanUnit,Reference[11].
59/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhenaworkingFAUisinstalled.
5.67HardwareError:PluginUnit(Minor)
Acontrolsystemfailurerelatedtohardwareerror.
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Minor
ProbableCause ReplaceableUnitProblem
5.67.1Consequences
NotpossibletomanagethePluginUnit(PIU).
Figure7WorkflowforHardwareError:PluginUnitAlarmCorrectiveActions
60/219
14/08/2015
AlarmDescriptions
Trythefollowing:
1. PerformacoldrestartofthePIU.
Caution!
Onsiteaction:IfHardwareErroralarmisnotcleared,replacethePIU.Describethefault
ontheBlueTagandsendittotheRepairCentertogetherwiththefaultyPIU.
Onsiteaction:IfHardwareErroralarmiscleared,monitorthePIUforfurtherHardware
Erroralarms.Ifthealarmisraisedagain,replacethePIU.DescribethefaultontheBlue
TagandsendittotheRepairCentertogetherwiththefaultyPIU.
FormoreinformationonhowtoreplacethefaultyPIU,seeapplicableCPIunderHWManagement
folder.
ThealarmisclearedwhenitispossibletomanagethePIU.
5.68HardwareError:PluginUnit(Major)
Atrafficorpowersystemfailurerelatedtohardwareerror.
Applicableforthestandbyterminalina1+1configuration.
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Major
5.68.1Consequences
ThePluginUnit(PIU)isnotworking.
61/219
14/08/2015
AlarmDescriptions
Trythefollowing:
Caution!
folder.
5.69HardwareError:PluginUnit(Critical)
Atrafficorpowersystemfailurerelatedtohardwareerror.
62/219
14/08/2015
AlarmDescriptions
Applicablefor1+0configurationandfortheactiveterminalina1+1configuration.
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
5.69.1Consequences
ThePluginUnit(PIU)isnotworking.
Trythefollowing:
63/219
14/08/2015
AlarmDescriptions
Caution!
folder.
5.70HardwareError:RAU
TheRAUhasahardwareerror.
Source
RAU
AlarmType
EquipmentAlarm
Severity
Critical
5.70.1Consequences
TrafficLoss.
64/219
14/08/2015
AlarmDescriptions
Figure10WorkflowforHardwareError:RAUAlarmCorrectiveActions
Dothefollowing:
1. PerformacoldrestartoftheRAUandrestartMINILINKCraft.
Caution!
Onsiteaction:IftheHardwareErroralarmisnotclearedaftertherestart,replacethe
RAU.DescribethefaultontheBlueTagandsendittotheRepairCentertogetherwiththe
faultyRAU.
Onsiteaction:IftheHardwareErroralarmiscleared,monitortheRAUforfurther
HardwareErroralarms.Ifthealarmisraisedagain,replacetheRAU.Describethefault
ontheBlueTagandsendittotheRepairCentertogetherwiththefaultyRAU.
5.71HardwareError:SFP(Critical)
TheSFPmodulehasahardwareerrorandmustbereplaced.Applicablefor1+0configurationandfor
65/219
14/08/2015
AlarmDescriptions
theactiveterminalina1+1configuration.
SpecificProblem HardwareErrorat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.71.1Consequences
TrafficLoss.
Figure11WorkflowforHardwareError:SFPAlarmCorrectiveActions
Note: Toclearthealarm,performthecorrectiveactionbelowonsite.
ReplacetheSFPmodule,seeReplacinganSFP,Reference[18].
5.72HCC
HopCommunicationChannel(HCC)
CommunicationislostontheHCC,betweentheMMUandthefarendMMU.
SpecificProblem HCC
Source
AllMMUs
AlarmType
CommunicationAlarm
Severity
Major
66/219
14/08/2015
AlarmDescriptions
5.72.1Consequences
ItisnotpossibletoaccesstheFarEnd.
Figure12WorkflowforHCCAlarmCorrectiveActions,Part1
67/219
14/08/2015
AlarmDescriptions
68/219
14/08/2015
AlarmDescriptions
69/219
14/08/2015
AlarmDescriptions
Performthefollowingsteps:
1. MakesurethattheconfigurationofthenearendandthefarendisaccordingtotheSite
InstallationDocumentation(SID).
IftheconfigurationofthenearendandthefarendisaccordingtotheSID,gotoStep2.
IftheconfigurationofthenearendandthefarendisnotaccordingtotheSID,take
correctiveactions.IftheHCCalarmisnotclearedafterthecorrection,gotoStep2.
2. ChecktheRFinputlevel.
IftheRFinputlevelisaccordingtothelinkbudget,goStep3.
IftheRFinputlevelisnotaccordingtothelinkbudget,gotoStep4.
70/219
14/08/2015
AlarmDescriptions
IftheRFinputlevelisabove30dBm,consultnetworkdesigndepartmenttoaddress
upfading.
3. PerformacoldrestartoftheMMUandrestartMINILINKCraft.
Caution!
IftheHCCalarmisclearedaftertherestart,monitorthehopforfurtherHCCalarms.If
theHCCalarmreoccurs,gotoStep13.
IftheHCCalarmisnotclearedaftertherestart,gotoStep13.
4. MakesurethattheRFoutputlevelofthenearendandthefarendisaccordingtothelink
budgetplanning.
IftheRFoutputlevelofthenearendandthefarendisaccordingtothelinkbudget
planning,gotoStep5.
IftheRFoutputlevelofthenearendandthefarendisnotaccordingtothelinkbudget
planning,consultthetransmissiondesigndepartmentforcorrectiveactions.
5. CheckiftheRFinputlevelisbelowthethresholdlevelforBER106forthecurrent
configuration.
IftheRFinputlevelisbelowthethresholdlevelforBER106forthecurrentconfiguration,
gotoStep6.
IftheRFinputlevelisnotbelowthethresholdlevelforBER106forthecurrent
configuration,gotoStep13.
6. Onsiteaction:PerformanRFlooptestonthenearendRAU.TurnofftheRAUtransmitteron
thefarendduringthetest.
IftheRFinputpowerisabout50dBm(10dB)onthenearendRAUduringthetest,go
toStep7.
IftheRFinputpowerisnotabout50dBm(10dB)onthenearendRAUduringthe
test,replacetheRAUonthenearend.DescribethefaultontheBlueTagandsenditto
theRepairCentertogetherwiththefaultyRAU.
Note: HCCalarmswillbeautomaticallymaskedduringanRFlooptest,thatis,HCCalarm
disappearsduringthelooptest.TheRFlooptestcannotbeusedtodefinethefaulty
unit.TheRFlooptestonlyshowsiftheRFinputleveliscorrect.
7. CheckifRFOutputLevelalarmisactiveonthefarendRAU.
Onsiteaction:IftheRFOutputLevelalarmisactive,replacetheRAUonthefarend.
RAU.
IftheRFOutputLevelalarmisnotactive,gotoStep8.
8. Onsiteaction:Checkfadingconditionsandweathercircumstances.
9. Onsiteaction:Checkforpossibleobstaclesinterferingwiththelineofsight.
Ifthereareobstacles,consultthetransmissiondesigndepartment.
71/219
14/08/2015
AlarmDescriptions
Iftherearenoobstacles,gotoStep10.
10. Onsiteaction:Makesuretheantennasarealignedcorrectlyonthenearendandthefarendto
meetthelinkbudgettarget.
11. CheckthestatusoftheRFinputlevel,thatcanbestableorcanvaryovertimeindicating
multipathfading.Ifyouareunsure,monitortheRFinputlevelfor24hourstofindcyclic
variations.
IftheRFinputlevelisstable,gotoStep12.
IftheRFinputleveldecreaseisintermittentorperiodic,consultthetransmissiondesign
departmenttoanalyzethepossiblemultipathfading.
12. Onsiteaction:PerformanRFlooptestonthefarendRAU.TurnofftheRAUtransmitteronthe
nearendduringthetest.
IftheRFinputpowerisabout50dBm(10dB)onthefarendRAUduringthetest,go
toStep17.
IftheRFinputpowerisnotabout50dBm(10dB)onthefarendRAUduringthetest,
replacetheRAUonthefarend.DescribethefaultontheBlueTagandsendittothe
RepairCentertogetherwiththefaultyRAU.
Note: HCCalarmswillbeautomaticallymaskedduringanRFlooptest,thatis,HCCalarm
disappearsduringthelooptest.TheRFlooptestcannotbeusedtodefinethefaulty
unit.TheRFlooptestonlyshowsiftheRFinputleveliscorrect.
13. Onsiteaction:Performaninterferencetest,seeVerifyinganInstallation,Reference[24].
RecordthehighestreceivedRFinputlevelwhilescanningthewholebandwidthandcompareit
totheacceptableinterferencevalues.
IfthereceivedRFinputlevelexceedsthedefinedvalue,consultthetransmissiondesign
department.
IfthereceivedRFinputleveldoesnotexceedthedefinedvalue,gotoStep14.
14. Onsiteaction:ReplacetheMMUonthenearend.
IftheHCCalarmisclearedafterthereplacement,describethefaultontheBlueTagand
sendittotheRepairCentertogetherwiththefaultyMMU.
IftheHCCalarmisnotclearedafterthereplacement,reusetheinitialMMU,andgoto
Step15.
15. Onsiteaction:ReplacetheMMUonthefarend.
IftheHCCalarmisnotclearedafterthereplacement,reusetheinitialMMU,andgoto
Step16.
16. Onsiteaction:ReplacetheRAUonthenearend.
sendittotheRepairCentertogetherwiththefaultyRAU.
IftheHCCalarmisnotclearedafterthereplacement,reusetheinitialRAU,andgoto
Step17.
17. Onsiteaction:ReplacetheRAUonthefarend.
sendittotheRepairCentertogetherwiththefaultyRAU.
72/219
14/08/2015
AlarmDescriptions
IftheHCCalarmisnotclearedafterthereplacement,reusetheinitialRAU,andgoto
Step18.
18. Onsiteaction:Makesurethatthepolarizationonthenearendandthefarendissetaccording
tothelinkbudgetplanning.
Ifthepolarizationonthenearendandthefarendiscorrectlyset,gotoStep19.
Ifthepolarizationonthenearendandthefarendisnotcorrectlyset,takecorrective
actions.
19. Onsiteaction:Replacetheantennaonthenearend.
IftheHCCalarmisnotclearedafterthereplacement,reinstalltheinitialantenna,andgo
toStep20.
20. Onsiteaction:Replacetheantennaonthefarend.DescribethefaultontheBlueTagandsend
ittotheRepairCentertogetherwiththefaultyantenna.
ThealarmisclearedwhenaccesstotheFarEndisrecovered.
5.73HighBER(Major)
BitErrorRatio(BER)
ThethresholdforSynchronousDigitalHierarchy(SDH)HighBERispassed(BERthresholdlevel).
Probablecausesarethefollowing:
Fading(flatorselective)
Badantennaalignment
Linkbudgetcalculationnotcorrect
PresenceofInterferers
SpecificProblem HighBER
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.73.1Consequences
TheRadioProtectionSwitchselectstheotherdemodulationpathifitssignalqualityisbetter.
Note: MakesurethattheSwitchModeissettoManualonboththenearendandthefarend
73/219
14/08/2015
AlarmDescriptions
terminalbeforetroubleshooting.Performalltheactionsontheactiveunit.SetSwitchMode
toAutooncethetroubleshootingiscompleted.
duringthetest.
withthefaultyRAU.
toStep5.
duringthetest.
withthefaultyRAU.
height,gotoStep8.
budgettarget.
74/219
14/08/2015
AlarmDescriptions
toStep11.
Caution!
MMU.
duringthetest.
toStep17.
lineside.
75/219
14/08/2015
AlarmDescriptions
terminal.
RAU,andgotoStep24.
terminal.
5.74HighBER(Critical)
BitErrorRatio(BER)
76/219
14/08/2015
AlarmDescriptions
ThethresholdforSynchronousDigitalHierarchy(SDH)HighBERispassed(BERthresholdlevel).
Probablecausesforthisare:
Badantennaalignment
PresenceofInterferers
SpecificProblem HighBER
Source
RAUIF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.74.1Consequences
Degradationofthequalityofthetrafficsignallineside.
duringthetest.
withthefaultyRAU.
toStep5.
duringthetest.
77/219
14/08/2015
AlarmDescriptions
withthefaultyRAU.
height,gotoStep8.
budgettarget.
toStep11.
Caution!
MMU.
duringthetest.
78/219
14/08/2015
AlarmDescriptions
toStep17.
lineside.
terminal.
RAU,andgotoStep24.
79/219
14/08/2015
AlarmDescriptions
terminal.
5.75HighDMRTTDelay
TheDelayMeasurement(DM)RoundTripTime(RTT)DelayattheNthpercentileisabovethe
configuredthreshold,whereNcanbeconfiguredbetween1and100(defaultvalueis95).
SpecificProblem HighDMRTTdelay
Source
SessionwithMEP
AlarmType
Severity
Major
5.76HighDMVariationRTTDelay
TheDelayMeasurementVariation(DMV)RoundTripTime(RTT)DelayvariationattheNthpercentile
isabovetheconfiguredthreshold,whereNcanbeconfiguredbetween1and100(defaultvalueis95).
SpecificProblem HighDMVariationRTTdelay
Source
SessionwithMEP
AlarmType
Severity
Major
5.77HighTemperature:NPU
Theunitreachesanabnormaltemperature.
blocking.
80/219
14/08/2015
AlarmDescriptions
SpecificProblem HighTemperature
Source
NPU
AlarmType
EquipmentAlarm
Severity
Critical
5.77.1Consequences
Thecontrolsystemfunctionsareshutdown(operationalstatusReducedService).Thisgivesa
gracefuldegradationthroughcontrolledprotectionswitchina1+1.Alarmsaresentina1+0,butthe
trafficisstillactive.
Trythefollowing:
Checkthatthefanisworkingproperly,seeLEDDescriptions,Reference[6].
Thealarmisclearedwhenthetemperatureisstablefor60secondsbelowthehightemperature
thresholdforthepluginunit.
5.78HighTemperature:PluginUnit
Theunithasreachedanabnormaltemperature.
blocking.
SpecificProblem HighTemperature
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Minor
5.78.1Consequences
Thecontrolsystemfunctionsareshutdown(operationalstatusReducedService).Thisgivesa
gracefuldegradationthroughcontrolledprotectionswitchina1+1.Alarmsaresentina1+0,butthe
trafficisstillactive.
Trythefollowing:
Checkthatthefanisworkingproperly,seeLEDDescriptions,Reference[6].
81/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhenthetemperatureisstablefor60secondsbelowthehightemperature
thresholdforthepluginunit.
5.79HitlessPhase
FailureofsynchronizingofthereceivedtrafficinthetwoMMUswithadurationlongerthanthetime
givenbyFadeNotificationTimer.
SpecificProblem HitlessPhase
Source
SWITCH
AlarmType
EquipmentAlarm
Severity
Warning
ProbableCause ProtectionPathFailure
5.80HoldoverModeEntered
ThenodeentersHoldovermodeduetolossofnetworksynchronizationreference.
SpecificProblem Holdovermodeentered
Source
NE
AlarmType
CommunicationAlarm
Severity
Major
5.80.1Consequences
WhenthenodeisinHoldovermodeithasnonetworksynchronizationreferenceavailable.
SynchronizationoutputsignalsaresquelchedortheappropriateSynchronizationStatusMessage
Ifthenodeisinholdovermodeforanextensivetime,checkthereasonwhythenetwork
synchronizationisnotavailable.Ifrequired,reconfigurethenodetouseanothersynchronization
reference.
Thealarmisclearedwhenthenetworksynchronizationfunctionenterslockedstatus.
5.81ICC
InternalCommunicationChannel(ICC)
CommunicationislostontheICC,betweentwoMMUsinthesameterminal.
82/219
14/08/2015
AlarmDescriptions
Possiblecause:thesoftwareorhardwareoftheMMUsisnotcompatible.
SpecificProblem ICC
Source
MMU2B/C/E/F
AlarmType
CommunicationAlarm
Severity
Major
5.81.1Consequences
UnabletoProtect.
Trythefollowing:
1. CheckthesoftwareandhardwareoftheMMUs.
2. UpgradesoftwareorreplaceoneMMUtoachievecompatibility.
5.82IEEE1588IncompatibleHardware
ThealarmisraisediftheNEhasIEEE1588configuration,buttheRstateoftheNPUisnotcompatible
withIEEE1588.
SpecificProblem IEEE1588IncompatibleHardware
Source
NE
AlarmType
EquipmentAlarm
Severity
Critical
5.82.1Consequences
TheNEdisablesitsIEEE1588frequencyandphasesynchronizationfunction.
ReplacetheNPUwithanNPUthatsupportsIEEE1588.Formoreinformation,seeReplacinganNPU,
Reference[15].
Formoreinformationonfeatureandequipmentcompatibility,seetheCompatibilitydocumentinthe
PlanningfolderoftheMINILINKTNCPIlibrary.
ThealarmisclearedwhentheNPUisreplacedwithanNPUthatsupportsIEEE1588orwhenthe
IEEE1588configurationisremoved.
5.83IFLOSR2L(Major)
83/219
14/08/2015
AlarmDescriptions
ThefailureiscausedbylossofthereceivingIntermediateFrequency(IF)signalfromtheRAUtothe
MMU(onlyforMMU2E/FandMMU3B).
Thealarmcanbecausedbythefollowingevents:
LossofsignalfromtheRAUtotheMMU.
AhardwareMMUfailureintheMMUIFblockorthedemodulatoritself.
SpecificProblem IFLOSR2L
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.83.1Consequences
Lossofreceivedsignal:hitlessswitchonthefaultlessRx.
84/219
14/08/2015
AlarmDescriptions
Figure16WorkflowforIFLOSR2LAlarmCorrectiveActions
1. PerformanIFlooptestontheMMU,seeFaultManagementOperations,Reference[3].
Onsiteaction:IftheIFLOSR2Lalarmisnotclearedduringthetest,replacetheMMU.
MMU.
IftheIFLOSR2Lalarmisclearedduringthetest,gotoStep2.
2. Onsiteaction:ReplacetheRAU.
IftheIFLOSR2Lalarmisnotcleared,reusetheinitialRAU.GotoStep3.
IftheIFLOSR2Lalarmiscleared,describethefaultontheBlueTagandsendittothe
85/219
14/08/2015
AlarmDescriptions
3. Onsiteaction:CheckandreplacetheradiocablingbetweentheRAUandtheMMU.
ThealarmisclearedwhentheMMUdemodulatorreceivesavalidsignal.
5.84IFLOSR2L(Critical)
ThefailureiscausedbylossofthereceivingIntermediateFrequency(IF)signalfromtheRAUtothe
MMU(onlyforMMU2E/FandMMU3B).
SpecificProblem IFLOSR2L
Source
RAUIF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.84.1Consequences
Lossofreceivedsignal:trafficislostonthelineside.
86/219
14/08/2015
AlarmDescriptions
Figure17WorkflowforIFLOSR2LAlarmCorrectiveActions
Onsiteaction:IftheIFLOSR2Lalarmisnotclearedduringthetest,replacetheMMU.
MMU.
IftheIFLOSR2Lalarmisclearedduringthetest,gotoStep2.
IftheIFLOSR2Lalarmisnotcleared,reusetheinitialRAU.GotoStep3.
IftheIFLOSR2Lalarmiscleared,describethefaultontheBlueTagandsendittothe
87/219
14/08/2015
AlarmDescriptions
5.85InRepair
Thealarmisraisedifaconfiguredunitisremovedfromtheslot.
SpecificProblem InRepair(OnlyapplicableifsourceisPluginunitorRAU)
InRepairat<BoardType>(OnlyapplicableifsourceisSFP)
Source
PluginUnit
SFP
RAU
AlarmType
EquipmentAlarm
Severity
Critical
5.85.1Consequences
Theunitisnotoperating.
Insertaunit.
Thealarmisclearedwhenaunitisinsertedintheslot.
5.86IncompatibleUnits:PluginUnit
SpecificProblem IncompatibleUnits
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
5.87IncompatibleUnits:RAU
TheRAUinuseisincompatiblewiththeconnectedMMU.
88/219
14/08/2015
AlarmDescriptions
SpecificProblem IncompatibleUnits
Source
RAU
AlarmType
EquipmentAlarm
Severity
Major
5.87.1Consequences
Itisnotpossibletoconfiguretheradioterminal.
ReplacetheRAUwithoneofcompatibletype,seeReplacingaRadioUnit,Reference[16].
ThealarmisclearedwhentheRAUisreplacedwithoneofcompatibletype.
5.88InsufficientLinks
Thenearenddoesnothaveenoughactivelinksinneitherthetransmitnorthereceivedirections(less
thanPTxtransmitorPRxreceivelinksareactive).
SpecificProblem Insufficientlinks
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Critical
5.88.1Consequences
5.88.2AlarmAnalysis
Thenearenddoesnothaveenoughactivelinksinbothdirections.Thiscanbecausedbyoneormore
faultsaffectingthelinksofthegroupsorbecausenotenoughlinkshavebeenconfiguredinthegroup.
CheckifanyalarmisreportedontheIMAlinksofthespecificgroup.IfnoalarmsaffecttheIMA
links,addoneormorelinkstothegrouptoreachtherequiredminimumnumberoflinks.
Thealarmisclearedwhenthenearendterminalhastherequirednumberofactivelinks.
5.89InsufficientLinks(FarEnd)
Thefarenddoesnothaveenoughactivelinksinthetransmitand/orreceivedirectionsandreports
89/219
14/08/2015
AlarmDescriptions
thatlessthanPTxtransmitorPRxreceivelinksareactive.
SpecificProblem Insufficientlinks(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Critical
5.89.1Consequences
5.89.2AlarmAnalysis
Thefarenddoesnothaveenoughactivelinksinbothdirections.Thiscanbecausedbyoneormore
faultsaffectingthelinksofthegroupsorbecausenotenoughlinkshavebeenconfiguredinthegroup.
CheckifanyalarmisreportedontheIMAlinksofthespecificgroup.IfnoalarmsaffecttheIMA
links,addoneormorelinkstothegrouptoreachtherequiredminimumnumberoflinks.
NofaultsaffectIMAlinksofthespecificgroupifitholdstherequiredminimumofactivelinks.
5.90InsufficientResources(Major)
TheRAUdoesnotsupportthecurrentconfiguration.
SpecificProblem Insufficientresources
Source
RAU
AlarmType
EquipmentAlarm
Severity
Major
5.90.1Consequences
Thetransmitterisactiveorcanbeactivated,buttheradiolinkcanhavedegradedperformance.
Tryoneofthefollowing:
SelectaframeformatsupportedbythecurrentRAU.Onewaytodothisistoselectaframe
formatwherethemodulationhaslowerconstellationorderinthesamechannelspacing,for
example,changefrom512QAMto256QAMwithchannelspacing28MHz.
ReplacetheRAUwithanewRAUsupportingthecurrentframeformat,thatis,aRAUthathasa
betterphasenoisegrade.Formoreinformation,seeReplacingaRadioUnit,Reference[16].
90/219
14/08/2015
AlarmDescriptions
Thealarmisclearedineitherofthefollowingcases:
TheframeformatischangedtoonethatissupportedbythecurrentRAU.
TheRAUisreplacedwithonethatsupportsthecurrentframeformat.
5.91InsufficientResources(Critical)
TheNEdoesnothavetheresourcestohandlethisPluginUnit.
SpecificProblem Insufficientresources
Source
PlugInUnit
RAU
SFP
AlarmType
EquipmentAlarm
Severity
Critical
IfthesourceofthealarmisaRAU,tryoneofthefollowing:
ReplacetheRAUwithonethatdoesnotrequiremorethan37Wofinputpower,seeReplacinga
RadioUnit,Reference[16].
ReplacetheMMUwithonethatsupportsmorethan37Wofoutputpower,seeReplacingan
MMU,Reference[13].
IfthesourceofthealarmisaRAU,thealarmisclearedineitherofthefollowingcases:
TheRAUisreplacedwithonethatdoesnotrequiremorethan37Wofinputpower.
TheMMUisreplacedwithonethatsupportsmorethan37Wofoutputpower.
5.92Interface/PortStatusNotUp
OneormoreremoteMaintenanceEndPoints(MEPs)reportthatInterfaceStatusTypeLengthValue
(TLV)isnotisUp(interfacestatusUp),oroneormoreremoteMEPsreportthatPortStatusTLVisnot
psUp(portstatusUp).
Management(CFM).
SpecificProblem Interface/PortstatusnotUp
Source
LANwithMEP
WANwithMEP
LAGwithMEP
91/219
14/08/2015
AlarmDescriptions
AlarmType
CommunicationAlarm
Severity
Warning
5.93InterMMUChannelFailure
HighlevelfaultoninterMMU2E/FcommunicationofRegeneratorSection(RS).Onlyvalidwhen
protected.
SpecificProblem InterMMUChannelFailure
Source
MMU2E/F
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause LossOfFrame
5.94InternalLossofPackets
Thealarmisraisedwhenmorepacketsthanthegiventhresholdarelostontheinterconnection
betweentwoprotectedEthernetbridges(NPUs).
SpecificProblem InternalLossofPackets
Source
NPU
AlarmType
CommunicationAlarm
Severity
Warning
5.94.1Consequences
TrafficislostbetweenthetwoNPUs.ProbablecausesoftrafficlossbetweenthetwoNPUsareoneof
thefollowing:
OversubscriptionofthefrontportsoftheNPUwiththepassiveEthernetswitchfrontbythe
portsoftheNPUwiththeactiveEthernetswitch.
TheconnectionbetweenthetwoNPUsislost,inwhichcaseaprotectionswitchtakesplace.
Dependingonthecauseoftrafficloss,performoneofthefollowingcorrectiveactions:
Incaseofoversubscriptionofthefrontports,checkthetrafficflowsbetweentheportsofthe
NPUs.
IncaseofconnectionproblemsbetweenthetwoNPUs,replacetheNPUinthesecondaryslot.If
theproblemstillremains,replacetheNPUintheprimaryslotwhilethetrafficisontheNPUin
thesecondaryslot.
92/219
14/08/2015
AlarmDescriptions
Formoreinformationabouttheprimaryandthesecondaryslot,seeRecommendationsfor
PositioningofPlugInUnits,Reference[9].
Makesurethebackplaneofthesubrackisnotdamaged.
ThealarmisclearedwhenthepacketlossontheinterconnectionbetweenthetwoEthernetbridges
(NPUs)isbelowthegiventhreshold.
5.95JitterBufferOverrun
Thealarmisraisedifthepercentageofframes,causingJitterBufferOverrun,staysaboveadefined
thresholdfor2.5seconds.
SpecificProblem JitterBufferOverrun
Source
CES
AlarmType
Severity
Major
5.95.1Consequences
Framesaredroppedincaseofjitterbufferoverrun.Droppedframesarereplacedwithfillerdata
(0xFF).
Improvethejitterperformanceofthenetworkorreconfiguretheparametersforthejitterbufferto
matchthenetworkperformance.
ThealarmisclearedwhennocasesofJitterBufferOverrunaredetectedfor10seconds.
5.96L2LoopDetected
Layer2Ethernetloopsaredetectedbysendingtestframestomulticastorbroadcastaddressesinthe
network.
ThealarmisraisedwhentheNEreceivesatestframesentbyitself.
SpecificProblem L2LoopDetected
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
5.96.1Consequences
RiskoftrafficcongestionintheLayer2domain.
93/219
14/08/2015
AlarmDescriptions
EliminatetheLayer2loopbymodifyingexistingLayer2connections.
ThealarmisclearedwhentheNEdoesnotdetecttestframessentbyitselfforaperiodconfiguredby
theuser.Thisthresholdperiodissetwhenenablingtheloopdetection,itsdefaultvalueis60seconds.
5.97L2ExternalLoopDetected
Layer2Ethernetloopsaredetectedbysendingtestframestomulticastorbroadcastaddressesinthe
network.
ThealarmisraisedwhentheNEreceivesatestframesentbyitself,onthesenderport.TheNEis
notpartofthedetectedLayer2loop,butitisconnectedtotheLayer2domainwheretheLayer2
loopoccurred.
SpecificProblem L2ExternalLoopDetected
Source
NE
AlarmType
CommunicationAlarm
Severity
Major
5.97.1Consequences
RiskoftrafficcongestionintheLayer2domain.
EliminatetheLayer2loopbymodifyingexistingLayer2connections.
ThealarmisclearedwhentheNEdoesnotdetecttestframessentbyitselfforaperiodconfiguredby
theuser.Thisthresholdperiodissetwhenenablingtheloopdetection,itsdefaultvalueis60seconds.
5.98LateArrivingFrames
Thealarmisraisedifthepercentageofframes,arrivingtoolatetobehandled,exceedsadefined
thresholdfor2.5seconds.
SpecificProblem LateArrivingFrames
Source
CES
AlarmType
QualityofServiceAlarm
Severity
Major
5.98.1Consequences
Framesthatarrivelatearedroppedandreplacedbyfillerdata(0xFF).
94/219
14/08/2015
AlarmDescriptions
Checkandimprovethenetworkperformance.
Thealarmisclearedwhenthepercentageofframes,arrivingtoolatetobehandled,staysbelowa
definedthresholdfor10seconds.
5.99LCASCRC
LinkCapacityAdjustmentSchemeCyclicRedundancyCheck(LCASCRC)
OneormoreLCAScontrolpacketswithCyclicRedundancyCheck(CRC)errorisreceivedonanyof
theVirtualContainers(VCs)belongingtotheVirtualConcatenationGroup(VCG).
SpecificProblem LCASCR
Source
AlarmType
CommunicationAlarm
Severity
Minor
2. Checkthesource.
5.100LFD
LossofFrameDelineation(LFD)
TheGenericFramingProcedure(GFP)delineationstatemachinehaslefttheSYNCstate.
SpecificProblem LFD
Source
GFP
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause FramingError
5.100.1Consequences
Interfacedown.
2. Checkthesource.
95/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhenthetrafficrecoversandtheGFPdelineationstatemachinechangesto
SYNCstate.Communicationrecovers.
5.101LicenseHandlingIsinanUnlockedPeriod(Minor)
TheNEisinanunlockedperiod,buttherearenolicenseviolations.
Thisalarmisraisedwhentheunlockedperiodisenteredandrepeatedwhenhalfofthetimeis
consumed.Afterhalfofthetime,thealarmisrepeatedevery8hoursperiodically.
Ifanylicensecontrolledfeatureisconfiguredbutnorelatedlicenseisinstalled,theseverityofthis
alarmischangedtoMajor.Formoreinformation,seeSection5.102.
SpecificProblem Licensehandlingisinanunlockedperiod,therearenolicenseviolations.
Source
LicenseHandler
AlarmType
Severity
Minor
Thealarmisclearedassoonastheuserexitstheunlockedperiodortheunlockedperiodexpires.
5.102LicenseHandlingIsinanUnlockedPeriod(Major)
TheNEisinanunlockedperiodandtherearelicenseviolations.Therearefeaturesusedwhich
requirelicensesandtherequiredlicenseshavenotbeeninstalledyet.
Thisalarmisraisedwhentheunlockedperiodisenteredandrepeatedwhenhalfofthetimeis
consumed.Afterhalfofthetime,thealarmisrepeatedevery8hoursperiodically.
Iftherequiredlicensesareinstalledornoneofthelicensecontrolledfeaturesisconfigured,the
severityofthisalarmischangedtoMinor.Formoreinformation,seeSection5.101.
SpecificProblem Licensehandlingisinanunlockedperiod,therearelicenseviolations.
Source
LicenseHandler
AlarmType
Severity
Major
Installtherequiredlicenses,seeInstallingandManagingLicenses,Reference[4].
Thealarmisclearedassoonastheuserexitstheunlockedperiodortheunlockedperiodexpires.
5.103LinkDown
96/219
14/08/2015
AlarmDescriptions
ProblemhasbeendetectedontheL1causedbyEthernetcarriernotdetected.Thisalarmcanbe
causedbyanEthernetcableproblem,configurationerrororpowerdownontheconnecteddevice.
SpecificProblem LinkDown
Source
SITELAN
AlarmType
CommunicationAlarm
Severity
Minor
5.103.1Consequences
NoCarrierDetectedontheEthernetPort.NoEthernetconnection.
97/219
14/08/2015
AlarmDescriptions
Figure18WorkflowforLinkDownAlarmCorrectiveActions
Trythefollowing:
1. MakesurethattheadministrativestatusissettoUpontheappropriateportfortheNPU.
2. Onsiteaction:CheckthattheEthernetcableconnectedtotheappropriateportisnotdamaged.
3. Onsiteaction:PerformacoldrestartoftheNPU.
4. Onsiteaction:ReplacetheNPU.DescribethefaultontheBlueTagandsendittotheRepair
CentertogetherwiththefaultyNPU.
FormoreinformationonhowtoreplacetheNPU,seeReplacinganNPU,Reference[15].
98/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhenacarrierisdetectedontheEthernetport.
5.104LinkFault
ThisalarmisraisedwhenaLinkOAMdetectsalinkfaultataninterface.
ThealarmcanalsobecausedbyaLinkFaultmessagereceivedfromanotherlinkOAMenabled
entity.Inthiscase,thealarmremainsactiveevenifthelinkisOKinbothdirections.
SpecificProblem Linkfault
Source
LAN
AlarmType
CommunicationAlarm
Severity
Critical
5.104.1Consequences
NoCarrierDetectedinTxdirectionontheEthernetPort.
Trythefollowing:
1. DisconnecttheEthernetcable.
2. ChecktheEthernetcablefordamagesandreplaceitifnecessary.
3. ReconnecttheEthernetcable.
4. CheckthesiteLANportconfiguration.
Thealarmisclearedwhenthefollowingistrue:
NoLinkFaultmessagereceivedfromanotherlinkOAMenabledentity.
TheEthernetcableisdisconnectedandreconnected.
AcarrierisdetectedontheEthernetport.
5.105LinkOAMLoopback
ALinkOAMloopbackcanbesetatinterfacebyremoteLinkOAMandtheinterfaceisnotableto
transmitusertraffic.Thisalarmisraisedwheneversuchloopbackissetataninterfacebyremote
LinkOAM.
SpecificProblem OAMloopbacksetbyremote
Source
LAN
AlarmType
CommunicationAlarm
Severity
Critical
99/219
14/08/2015
AlarmDescriptions
5.105.1Consequences
EgresstrafficdiscardedandingresstrafficloopbacktotheremotepeerontheEthernetPort.
TrytoremovetheLinkOAMlooponthepeerlinkOAMentity.IfLinkOAMfunctionalityisnotneeded,
itcanbedisabled.
ThealarmisclearedwhenlinkOAMloopbackisremovedorLinkOAMsessionisterminated.
5.106LOA
LossofAlignment(LOA)
LOAforchannelswithtraffic.
Thedifferentialdelayforatleastonechannelcannotbealigned.
SpecificProblem LOA
Source
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause FramingError
5.107LockingStateLastingLongerthan30Minutes
Thealarmisraisedifthenodeinvalidatesasynchronizationreferenceduetoinstabilityofthe
synchronizationreference.
SpecificProblem SynchronizationReferenceFailed
Source
NE
AlarmType
CommunicationAlarm
Severity
Major
5.107.1Consequences
Whenasynchronizationreferencebecomesunavailable,thenodeselectsanothersynchronization
reference.Ifthereisnosynchronizationreferenceavailablethatcanbeused,thenodeenters
Holdovermode.
Thenodecannotenterlockedstatusbecauseofinstablenetworksynchronizationreference.Checkthe
stabilityofthesynchronizationreference.
Thealarmisclearedwhenthenetworksynchronizationreferenceisavailableagain.
100/219
14/08/2015
AlarmDescriptions
5.108LOF(Critical)
LossofFrameAlignment(LOF)
Probablecausesforthisareasfollows:
Fiberbroken.
Fiberpowermismatch.
Theconnectrateofthedevicemismatch.
SpecificProblem LOF
Source
E2/E3
FramedE1
MS
AlarmType
CommunicationAlarm
Severity
Critical
5.108.1Consequences
Trafficblock.
Checkfiberconnectionorfarenddevice.
Thealarmisclearedwhenthecommunicationrecovers.
5.109LOF:RS(Critical)
LossOfFrameAlignment(LOF)
TheFrameAlignmentSignal(FAS)isnotfound.
SpecificProblem LOF
Source
RS
AlarmType
CommunicationAlarm
Severity
Critical
5.109.1Consequences
Serviceunavailable.
101/219
14/08/2015
AlarmDescriptions
Ceasetheparticulartransmissionerror.
5.110LOFL2R(Major)
TheinputtrafficontheLineinterfaceiscorrupted.Thereisalossofframeonthereceivingline(only
forMMU2E/F).
SpecificProblem LOFL2R
Source
LINERS(1+1EEP/ELP)
AlarmType
CommunicationAlarm
Severity
Major
5.110.1Consequences
AnAISispropagatedtotheradioside.Thesystemswitchestothefaultlessinterface.
1. CheckthecableandconnectorLinesideontheMMU.
2. Ifpossible,performaloopontheexternalequipmentfeedingtheLineinterfaceoftheMMU,see
FaultManagementOperations,Reference[3].Ifnoalarmisdetectedontheexternalequipment
thenreplacetheMMU,seeReplacinganMMU,Reference[13].
3. ReplacetheMMU,seeReplacinganMMU,Reference[13].
Thealarmisclearedwhentheframealignmentontheincomingsignalispossibleagain.
5.111LOFL2R(Critical)
TheinputtrafficontheLineinterfaceiscorrupted.Thereisalossofframeonthereceivingline(only
forMMU2E/F).
SpecificProblem LOFL2R
Source
LINERS(1+0,1+1SI)
AlarmType
CommunicationAlarm
Severity
Critical
5.111.1Consequences
AnAlarmIndicationSignal(AIS)ispropagatedtotheradioside.Asaconsequencetrafficisloston
theradioside.
102/219
14/08/2015
AlarmDescriptions
1. CheckthecableandconnectorLinesideontheMMU.
2. Ifpossible,performaloopontheexternalequipmentfeedingtheLineinterfaceoftheMMU,see
FaultManagementOperations,Reference[3].Ifnoalarmisdetectedontheexternalequipment
thenreplacetheMMU,seeReplacinganMMU,Reference[13].
3. ReplacetheMMU,seeReplacinganMMU,Reference[13].
Thealarmisclearedwhentheframealignmentontheincomingsignalispossibleagain.
5.112LOFR2L(Major)
LossOfFrame(LOF)
LOFonthetransmittingline(onlyforMMU2E/F).Probablecausesarethefollowing:
Badantennaalignment
Presenceofinterferers
SpecificProblem LOFR2L
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.112.1Consequences
AnAlarmIndicationSignal(AIS)ispropagatedtothelineside.TheRadioProtectionSwitchchooses
theotherMMUifitssignalqualityisbetter.
correctlevel.
cableshielding).
isstillpresentthenreplacetheactiveMMU,seeReplacinganMMU,Reference[13].
103/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhentheframealignmentontheincomingradiosignalispossibleagain.
5.113LOFR2L(Critical)
LossOfFrame(LOF)
LOFonthetransmittingline(onlyforMMU2E/F).Probablecausesforthisare:
Presenceofinterferers.
SpecificProblem LOFR2L
Source
RAUIF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.113.1Consequences
AnAlarmIndicationSignal(AIS)ispropagatedtothelineside.Asaconsequencethetrafficisloston
thelineside.
correctlevel.
cableshielding).
isstillpresentthenreplacetheactiveMMU,seeReplacinganMMU,Reference[13].
104/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhentheframealignmentontheincomingradiosignalispossibleagain.
5.114LOM
LossofMultiframe(LOM)
The2stagemultiframealignmentusedforvirtualconcatenationislost.
SpecificProblem LOM
Source
VC12
VC3
VC4
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause LossOfMultiFrame
2. Checkthesource.
5.115LOMF(Major)
LossofMultiframe(LOMF)
SpecificProblem LOMF
Source
VC4
AlarmType
CommunicationAlarm
Severity
Major
5.116LOMF(Critical)
LossofMultiframe(LOMF)
SpecificProblem LOMF
Source
FramedE1
AlarmType
CommunicationAlarm
Severity
Critical
105/219
14/08/2015
AlarmDescriptions
5.117LOP(Major)
LossofPointer(LOP)
Theincomingsignaliscorruptedsothepointercannotbelocatedinthesignal.
SpecificProblem LOP
Source
AU4
TU3
TU12
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause LossOfPointer
5.117.1Consequences
Theserviceisunavailable.
Thealarmisclearedwhentheincomingsignalisnotcorruptedanymoreandthepointercanbe
locatedintheincomingsignal.
5.118LOP(Critical)
LossofPointer(LOP)
Theincomingsignaliscorrupted,sothepointercannotbelocatedinthesignal.
SpecificProblem LOP
Source
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause LossOfPointer
5.118.1Consequences
106/219
14/08/2015
AlarmDescriptions
Thealarmisclearedthentheincomingsignalisnotcorruptedanymore,andthepointercanbe
locatedintheincomingsignal.
5.119LOS(Critical)
LossofSignal(LOS)
LOSisdetectedontheincomingtrafficonthelineinterface.
SpecificProblem LOS
Source
E1
MS/RS
AlarmType
CommunicationAlarm
Severity
Critical
5.119.1Consequences
107/219
14/08/2015
AlarmDescriptions
Figure19WorkflowforLOSAlarmCorrectiveActions
Dothefollowing:
1. PerformalocallooponthecorrespondinginterfaceofthenearendPluginUnit(PIU).
Onsiteaction:IftheLOSalarmisnotcleared,replacethePIUonthenearend.Describe
thefaultontheBlueTagandsendittotheRepairCentertogetherwiththefaultyPIU.
IftheLOSalarmiscleared,gotoStep2.
2. PerformalineloopontheinterfaceofthefarendPIU.
IftheLOSalarmisnotcleared,gotoStep3.
Onsiteaction:IftheLOSalarmiscleared,replacethePIUonthefarend.Describethe
faultontheBlueTagandsendittotheRepairCentertogetherwiththefaultyPIU.
108/219
14/08/2015
AlarmDescriptions
3. Onsiteaction:CheckandreplacethetransmissionmediabetweenthenearendPIUandthe
farendPIUasneeded.
folder.
Thealarmisclearedwhentrafficisdetectedintheincomingsignal.
5.120LOS:RAUIF(Major)
LossofSignal(LOS)
ThefailureiscausedbylossofreceivedIntermediateFrequency(IF)signalfromtheRAUtothe
MMU.
SpecificProblem LOS
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.120.1Consequences
109/219
14/08/2015
AlarmDescriptions
Figure20WorkflowforLOS:RAUIFAlarmCorrectiveActions
Dothefollowing:
Onsiteaction:IftheLOS:RAUIFalarmisnotclearedduringthetest,replacetheMMU.
MMU.
IftheLOS:RAUIFalarmisclearedduringthetest,gotoStep2.
IftheLOS:RAUIFalarmisnotcleared,reusetheinitialRAU.GotoStep3.
IftheLOS:RAUIFalarmiscleared,describethefaultontheBlueTagandsendittothe
110/219
14/08/2015
AlarmDescriptions
5.121LOS:RAUIF(Critical)
LossofSignal(LOS)
ThefailureiscausedbylossofreceivedIntermediateFrequency(IF)signalfromtheRAUtothe
MMU.
SpecificProblem LOS
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Critical
5.121.1Consequences
111/219
14/08/2015
AlarmDescriptions
Figure21WorkflowforLOS:RAUIFAlarmCorrectiveActions
Dothefollowing:
Onsiteaction:IftheLOS:RAUIFalarmisnotclearedduringthetest,replacetheMMU.
MMU.
IftheLOS:RAUIFalarmisclearedduringthetest,gotoStep2.
IftheLOS:RAUIFalarmisnotcleared,reusetheinitialRAU.GotoStep3.
IftheLOS:RAUIFalarmiscleared,describethefaultontheBlueTagandsendittothe
112/219
14/08/2015
AlarmDescriptions
5.122LOSL2R(Major)
Lossofreceivedsignalatthelineinterface(onlyforMMU2E/FandMMU3B).
Applicableforthestandbyinterfacein1+1EnhancedEquipmentProtection(EEP)/EquipmentandLine
Protection(ELP).
SpecificProblem LOSL2R
Source
LINERS(1+1EEP/ELP)
AlarmType
CommunicationAlarm
Severity
Major
5.122.1Consequences
Theprotectionislost.
113/219
14/08/2015
AlarmDescriptions
Figure22WorkflowforLOSL2R(Major)AlarmCorrectiveActions
Dothefollowing:
1. PerformalocallooponthelineinterfaceofthenearendMMU.
Onsiteaction:IftheLOSL2Ralarmisnotcleared,replacetheMMUonthenearend.
MMU.
IftheLOSL2Ralarmiscleared,gotoStep2.
2. PerformalineloopontheactiveinterfaceofthefarendPIU.
IftheLOSL2Ralarmisnotcleared,gotoStep3.
Onsiteaction:IftheLOSL2Ralarmiscleared,replacetheactivePIUonthefarend.
114/219
14/08/2015
AlarmDescriptions
PIU.
3. Onsiteaction:CheckandreplacethetransmissionmediabetweenthenearendMMUandthe
farendPIUasneeded.
folder.
Thealarmisclearedwhenavalidsignalisdetectedinthelineinterface.
5.123LOSL2R(Critical)
Lossofreceivedsignalatthelineinterface(onlyforMMU2E/FandMMU3B).
Applicablefor1+0,1+1SingleInterface(SI),andtheactiveinterfacein1+1EnhancedEquipment
Protection(EEP)/EquipmentandLineProtection(ELP).
SpecificProblem LOSL2R
Source
LINERS(1+0,1+1SI)
AlarmType
CommunicationAlarm
Severity
Critical
5.123.1Consequences
Lossofreceivedsignal:trafficislostontheradioside.
115/219
14/08/2015
AlarmDescriptions
Figure23WorkflowforLOSL2R(Critical)AlarmCorrectiveActions
Dothefollowing:
1. PerformalocallooponthelineinterfaceofthenearendMMU.
Onsiteaction:IftheLOSL2Ralarmisnotcleared,replacetheMMUonthenearend.
MMU.
IftheLOSL2Ralarmiscleared,gotoStep2.
2. PerformalineloopontheinterfaceofthefarendPIU.
IftheLOSL2Ralarmisnotcleared,gotoStep3.
Onsiteaction:IftheLOSL2Ralarmiscleared,replacethePIUonthefarend.Describe
116/219
14/08/2015
AlarmDescriptions
farendPIUasneeded.
folder.
Thealarmisclearedwhenavalidsignalisdetectedinthelineinterface.
5.124LossofCellDelineation:ATM
AsynchronousTransferMode(ATM)CellscannotbeextractedfromtheE1LinkconfiguredasaG.804
ATMinterface.
SpecificProblem LossofCellDelineation
Source
ATM
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause TransmissionError
5.124.1Consequences
ThereisnoATMtrafficintheRxdirectionofthespecificATMInterface.
5.124.2AlarmAnalysis
ThenetworkequipmentconnectedtoE1isnotconfiguredforATMserviceorphysicalfailureattheE1
interface(LossOfSignal(LOS)/LossOfFrame(LOF)/AlarmIndicationSignal(AIS)).
ChecktheconfigurationofthenetworkequipmentinterfaceconnectedtothespecificE1interface.
ThealarmisclearedwhenthetransmissionconvergenceisabletodelineateandextractATMcells
fromthespecificlink.
5.125LossofCellDelineation:IMALink
AsynchronousTransferMode(ATM)CellscannotbeextractedfromtheE1Linkconfiguredasan
InverseMultiplexeroverATM(IMA)Link.
SpecificProblem LossofCellDelineation
Source
IMALink
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause TransmissionError
117/219
14/08/2015
AlarmDescriptions
5.125.1Consequences
NoATMtrafficcanbereceivedfromthespecificIMALink.RelatedIMAgroupscanalsobeaffectedby
thefault:incasetheIMAgroupgoesbelowthe"minimumnumberof(active)links"noATMtraffic
canflowatallthroughthegroup.InthiscasetheoperationalstatusofrelatedATMIMA(IMAgroup)
andATMgoestodown.IftheIMAgroupstillhaveaminimumnumberoflinksitcanstillreceivethe
guaranteedbandwidthoftraffic.
ThenetworkequipmentconnectedtoE1isnotconfiguredforATMserviceorphysicalfailureattheE1
interface(LossOfSignal(LOS)/LossOfFrame(LOF)/AlarmIndicationSignal(AIS)).
Checktheconfigurationofthenetworkequipmentinterfaceconnectedtothespecificlink.
ThealarmisclearedwhenthetransmissionconvergenceisabletodelineateandextractATMcells
fromthespecificlink.
5.126LossofContinuity
AMaintenanceEndPoint(MEP)doesnotreceiveContinuityCheckMessage(CCM)framesfromapeer
MEPduringanintervalequalto3.5timestheCCMtransmissionperiodconfiguredattheMEP.
Note: ThisalarmisonlyavailablewhenusingtheITUTY.1731standardforConnectivityFault
Management(CFM).
SpecificProblem LossOfContinuity
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Major
5.127LossofDelaySynchronization
Thelinkhasadelayhigherthanthetolerablelinkdifferentialdelay(25msec)withrespecttothe
otherlinksinthegroup.
SpecificProblem LossofDelaySynchronization
Source
IMALink
AlarmType
CommunicationAlarm
118/219
14/08/2015
Severity
AlarmDescriptions
Critical
5.127.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbereceivedfromthespecificInverseMultiplexer
overATM(IMA)Link.RelatedIMAgroupscanalsobeaffectedbythefault:incasetheIMAgroup
goesbelowthe"minimumnumberof(active)links"noATMtrafficcanflowatallthroughthegroup.
InthiscasetheoperationalstatusofrelatedATMIMA(IMAgroup)andATMgoestodown.IftheIMA
groupstillhaveaminimumnumberoflinksitcanstillreceivetheguaranteedbandwidthoftraffic.
Linksbelongingtothegrouphavedifferentpathsinthenetworkcausinganexcessivedifferential
delayamongthelinks.
Trytoreducedifferentialdelaysbyusingotherlinks.
Thealarmisclearedwhenthedifferentialdelayofthelinksinksbelowthelimitthreshold(25msec).
5.128LossofGrandmasterTraceability
TheNEhaslostfrequency(G.8265.1mode)orphase(IEEE1588v2mode)traceabilitytothe
Grandmaster.
SpecificProblem LossofGrandmasterTraceability
Source
NE
AlarmType
CommunicationAlarm
Severity
Major
5.128.1Consequences
The1588v2functionentersintoHoldoverorFreeRunningMode,andcannotbeusedasaNetsynch
reference.
ChecktheavailabilityofMasterClocksandconfigureanotherMasterifneeded.
ThealarmisclearedwhenGrandmastertraceabilityisrecovered.
5.129LossofIMAFrame
PersistenceofaLIFdefectatthenearend(morethan2.5+/0.5sec).InverseMultiplexeroverATM
(IMA)devicecannotfindIMAICPCellsdelimitingIMAFrames.
119/219
14/08/2015
AlarmDescriptions
SpecificProblem LossofIMAFrame
Source
IMALink
AlarmType
CommunicationAlarm
Severity
Critical
5.129.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbereceivedfromthespecificIMALink.RelatedIMA
groupscanalsobeaffectedbythefault:incasetheIMAgroupgoesbelowthe"minimumnumberof
(active)links"noATMtrafficcanflowatallthroughthegroup.Inthiscasetheoperationalstatusof
relatedATMIMA(IMAgroup)andATMgoestodown.IftheIMAgroupstillhaveaminimumnumber
oflinksitcanstillreceivetheguaranteedbandwidthoftraffic.
ThefarendlinkisnotconfiguredasanIMALink.
Checkthefarendlinkconfiguration.
ThealarmisclearedwhentheIMAdevicecanreceiveICPcellsfromthefarendlink.
5.130LossofKeepAlive
Lossofkeepaliveframesisdetected.
SpecificProblem Lossofkeepalive
Source
IMGroup
AlarmType
CommunicationAlarm
Severity
Critical
5.131LossofMasterClockProtection
TheNEhaslosttheconnectivitytotheredundant(backup)MasterClock.
SpecificProblem LossofMasterClockProtection
Source
NE
AlarmType
CommunicationAlarm
Severity
Warning
5.131.1Consequences
GrandmastertraceabilityisstillkeptbutthePTPconnectivityisnolongerprotected.
120/219
14/08/2015
AlarmDescriptions
ChecktheavailabilityofMasterClocksandconfigureanotherMasterifneeded.
ThealarmisclearedwhenconnectivitytoabackupMasterisrecovered.
5.132LossofNetworkReferenceRedundancy
Thenodelostitsredundant(backup)networksynchronizationreference.
SpecificProblem Lossofnetworkreferenceredundancy
Source
NE
AlarmType
CommunicationAlarm
Severity
Warning
5.132.1Consequences
Whenthenodeonlyhasonenetworksynchronizationreferenceavailableitisconsideredvulnerable
andifthelastsynchronizationreferenceislostitputsthenodeinholdover.
Thealarmisclearedwhenaredundantnetworksynchronizationreferenceisavailableagain.
5.133LostCCMs
TheMaintenanceEndPoint(MEP)doesnotreceivevalidContinuityCheckMessage(CCM)framesfrom
atleastoneoftheremoteMEPs.
Management(CFM).
SpecificProblem LostCCMs
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Major
121/219
14/08/2015
AlarmDescriptions
5.134LowBER
BitErrorRatio(BER)
ThethresholdforSynchronousDigitalHierarchy(SDH)LowBERispassed(MMU2E/FandMMU3B
only).
Possiblecausesarethefollowing:
Presenceofinterferers.
SpecificProblem LowBER
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.134.1Consequences
Degradationofthequalityofthetrafficsignallineside.
Note: Ifthealarmoccursina1+1protectedterminal,makesurethattheSwitchModeissetto
Manualonboththenearendandthefarendterminalbeforetroubleshooting.Performallthe
actionsontheactiveunit.SetSwitchModetoAutooncethetroubleshootingiscompleted.
duringthetest.
withthefaultyRAU.
122/219
14/08/2015
AlarmDescriptions
Iftherearenoalarmsraisedonthefarendterminal,gotoStep5inSection5.74.2.
toStep5.
duringthetest.
withthefaultyRAU.
height,gotoStep8.
budgettarget.
IftheBERalarmisnotclearedafterthereplacement,reinstalltheinitialantenna,andgo
toStep11.
Caution!
123/219
14/08/2015
AlarmDescriptions
MMU.
duringthetest.
toStep17.
lineside.
terminal.
124/219
14/08/2015
AlarmDescriptions
RAU,andgotoStep24.
terminal.
5.135LowInputVoltage
Theinputvoltageislow.Ifitdropsfurther,oneormorepluginunitscanstopworking.
SpecificProblem LowInputVoltage
Source
NE
AlarmType
EnvironmentalAlarm
Severity
Major
ProbableCause PowerProblem
5.136LossofFrames
ThealarmisraisediftheframeLossRatiostaysaboveadefinedthresholdfor2.5seconds.
SpecificProblem LossofFrames
Source
CES
AlarmType
QualityofServiceAlarm
Severity
Critical
5.136.1Consequences
AnAlarmIndicationSignal(AIS)isgenerated.
125/219
14/08/2015
AlarmDescriptions
Checkandimprovethenetworkperformance.
ThealarmisclearedwhentheFrameLossRatiostaysbelowadefinedthresholdfor10seconds.
5.137LowerLayerDown
Nothroughputontheinterface.AllInverseMultiplexer(IM)interfacesaredown.ForTDMLink,Lower
LayerDown(LLD)isreportedforBER>103.ForPacketLink,LLDisreportedforBER>105.
SpecificProblem LowerLayerDown
Source
IMGroup
AlarmType
CommunicationAlarm
Severity
Critical
5.138MaintenanceUnlockResetKeyRequired(Warning)
ThenumberofavailableMaintenanceUnlocktokensdecreasedtoone,becausetheuserentered
MaintenanceUnlockperiod.WhenenteringMaintenanceUnlockperiodagain,thetokensrunoutand
theseverityofthisalarmischangedtoMajor.
SpecificProblem MaintenanceUnlockResetKeyRequired
Source
LicenseHandler
AlarmType
Severity
Warning
InstallMaintenanceUnlockRefilllicenses,seeInstallingandManagingLicenses,Reference[4].
ThealarmisclearedassoonastheuserinstallsatleastoneMaintenanceRefilllicense.
5.139MaintenanceUnlockResetKeyRequired(Major)
NoMaintenanceUnlocktokensavailable,becausetheuserenteredMaintenanceUnlockperiodseveral
times.WhenaMaintenanceUnlockRefilllicenseisinstalled,theseverityofthisalarmischangedto
Warning.
SpecificProblem MaintenanceUnlockResetKeyRequired
Source
LicenseHandler
AlarmType
Severity
Major
126/219
14/08/2015
AlarmDescriptions
InstallMaintenanceUnlockRefilllicenses,seeInstallingandManagingLicenses,Reference[4].
ThealarmisclearedassoonastheuserinstallsatleastoneMaintenanceRefilllicense.
5.140MalformedFrames
Thealarmisraisedifthepercentageofmalformedframesstaysaboveadefinedthresholdfor2.5
seconds.
SpecificProblem MalformedFrames
Source
CES
AlarmType
CommunicationAlarm
Severity
Major
5.140.1Consequences
Malformedframesarereplacedwithfillerdata(0xFF).
Checkthatthenetworkiscorrectlyconfiguredandthattherearenosecuritythreatsinthenetwork.
Thealarmisclearedwhenthepercentageofmalformedframesstaysbelowadefinedthresholdfor
10seconds.
5.141Mismerge(IncorrectMAIDinCCM)
AMaintenanceEndPoint(MEP)hasreceivedaContinuityCheckMessage(CCM)framewithcorrect
MaintenanceDomain(MD)level,butwithincorrectMaintenanceAssociation(MA)ID.
Management(CFM).
SpecificProblem Mismerge(incorrectMAIDinCCM)
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Major
127/219
14/08/2015
AlarmDescriptions
5.142ModIndex
ThemodulationindexoftheMMU,controlledbythefarendMMU,isoutoftheallowedrange.
SpecificProblem ModIndex
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.143ModeMismatch:MS
MultiplexSectionProtection(MSP)modemismatch.
FarendconfiguredasMSP1:nandthereceivedK2bytedoesnotindicate1+1.
SpecificProblem ModeMismatchK2.Indicatesfaultyconfigurationinthefarendunit.
Source
MultiplexSection(MS)
AlarmType
EquipmentAlarm
Severity
Minor
Checkandcorrectconfigurationmismatch.
ThealarmisclearedwhentheK2byteindicates1+1.
5.144ModeMismatch:MSP
MultiplexSectionProtection(MSP)modemismatch.
FarendconfiguredasMSP1:nandthereceivedK2bytedoesnotindicate1+1.
SpecificProblem ModeMismatch
Source
MSP
AlarmType
CommunicationAlarm
Severity
Minor
128/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhentheK2byteindicates1+1.
5.145NoHoldoverProtection
SpecificProblem Noholdoverprotection
Source
NE
AlarmType
CommunicationAlarm
Severity
Minor
5.146NoTraffic:LAG
Foralltheportsallocatedtothelinkaggregationgroup,thelinkisdown.
SpecificProblem NoTraffic
Source
LAG
AlarmType
CommunicationAlarm
Severity
Critical
5.147NoTrafficPossible
Nothroughputontheinterface.AllInverseMultiplexer(IM)interfacesareDown.
SpecificProblem NoTrafficPossible
Source
HDLC
AlarmType
CommunicationAlarm
Severity
Critical
5.148NodeInstallation
TheNEisinNodeInstallationmode.EntertheURLhttp://10.0.0.1toreachtheinstallationwizard.
SpecificProblem NodeInstallation
Source
NE
AlarmType
EquipmentAlarm
Severity
Minor
5.149NONLCAS
AsinkoperatinginLinkCapacityAdjustmentScheme(LCAS)modedetectedaNONLCASsource.
129/219
14/08/2015
AlarmDescriptions
SpecificProblem NONLCAS
Source
AlarmType
CommunicationAlarm
Severity
Warning
Checkthesource.
5.150NPUInstallation
TheNEisinNPUInstallationmode.EntertheURLhttp://10.0.0.1toreachtheinstallationwizard.
SpecificProblem NPUInstallation
Source
NE
AlarmType
EquipmentAlarm
Severity
Major
5.151OAMLocalErroredFrame<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesexceedsthethresholdduringthedefinedperiod
oftime.
Therearetwovariantsofthisalarm:OAMLocalErroredFrameandOAMRemoteErroredFrame.If
LinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,Araisesalocalalarm
andsendsanindicationabouttrafficdisturbanceusingtheLinkOAMprotocoltoB.Bthenraisesa
remotealarm.
SpecificProblem OAMLocalErroredFrame<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
5.152OAMLocalErroredFramePeriod<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesexceedsthethresholdpercentageduringthe
definednumberofframes.
Therearetwovariantsofthisalarm:OAMLocalErroredFramePeriodandOAMRemoteErrored
FramePeriod.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,A
raisesalocalalarmandsendsanindicationabouttrafficdisturbanceusingtheLinkOAMprotocolto
B.Bthenraisesaremotealarm.
SpecificProblem OAMLocalErroredFramePeriod<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
130/219
14/08/2015
Severity
AlarmDescriptions
Major
5.153OAMLocalErroredSecsSummary<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesecondsexceedsthethresholdduringthedefined
periodoftime.Anerroredframesecondisaonesecondintervalduringwhichatleastoneframe
errorisdetected.
Therearetwovariantsofthisalarm:OAMLocalErroredFrameSecsSummaryandOAMRemote
ErroredFrameSecsSummary.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLink
OAMentityB,AraisesalocalalarmandsendsanindicationabouttrafficdisturbanceusingtheLink
OAMprotocoltoB.Bthenraisesaremotealarm.
SpecificProblem OAMLocalErroredFrameSecsSummary<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
5.154OAMLocalErroredSymbolPeriod<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredsymbolsexceedsthethresholdpercentageduring1
second.
Therearetwovariantsofthisalarm:OAMLocalErroredSymbolPeriodandOAMRemoteErrored
SymbolPeriod.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,A
SpecificProblem OAMLocalErroredSymbolPeriod<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
5.155OAMRemoteErroredFrame<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesexceedsthethresholdduringthedefinedperiod
oftime.
Therearetwovariantsofthisalarm:OAMLocalErroredFrameandOAMRemoteErroredFrame.If
LinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,Araisesalocalalarm
andsendsanindicationabouttrafficdisturbanceusingtheLinkOAMprotocoltoB.Bthenraisesa
remotealarm.
SpecificProblem OAMRemoteErroredFrame<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
131/219
14/08/2015
AlarmDescriptions
5.156OAMRemoteErroredFramePeriod<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesexceedsthethresholdpercentageduringthe
definednumberofframes.
Therearetwovariantsofthisalarm:OAMLocalErroredFramePeriodandOAMRemoteErrored
FramePeriod.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,A
SpecificProblem OAMRemoteErroredFramePeriod<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
5.157OAMRemoteErroredSecsSummary<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredframesecondsexceedsthethresholdduringthedefined
periodoftime.Anerroredframesecondisaonesecondintervalduringwhichatleastoneframe
errorisdetected.
Therearetwovariantsofthisalarm:OAMLocalErroredFrameSecsSummaryandOAMRemote
ErroredFrameSecsSummary.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLink
OAMentityB,AraisesalocalalarmandsendsanindicationabouttrafficdisturbanceusingtheLink
OAMprotocoltoB.Bthenraisesaremotealarm.
SpecificProblem OAMRemoteErroredFrameSecsSummary<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
5.158OAMRemoteErroredSymbolPeriod<window>,<threshold>,<value>
Thealarmisraisedifthenumberoferroredsymbolsexceedsthethresholdpercentageduring1
second.
Therearetwovariantsofthisalarm:OAMLocalErroredSymbolPeriodandOAMRemoteErrored
SymbolPeriod.IfLinkOAMentityAhasproblemsreceivingtrafficfrompeerLinkOAMentityB,A
SpecificProblem OAMRemoteErroredSymbolPeriod<window>,<threshold>,<value>
Source
LAN
AlarmType
CommunicationAlarm
Severity
Major
132/219
14/08/2015
AlarmDescriptions
5.159OSPFLSADatabaseOverload
TheOpenShortestPathFirst(OSPF)routingdatabaseisfullduetotoomanyroutersinthenetwork.
SpecificProblem OSPFLSAdatabaseoverload
Source
NE
AlarmType
CommunicationAlarm
Severity
Minor
ProbableCause StorageCapacityProblems
5.160PFM
PayloadFCSIdentifierMismatch(PFM)
ThePayloadFCSIdentifier(PFI)fieldinthereceivedframedoesnotmatchtheconfiguredvalue.
SpecificProblem PFM
Source
GFP
AlarmType
CommunicationAlarm
Severity
Major
RepairtheVirtualContainer(VC)trail.
TheAlarmisclearedwhenthePFIfieldinthereceivedframematchestheconfiguredvalue.
5.161PhaseFreeRunningModeEntered
TheNEhaslosttraceabilitytotheGrandmasterandrunsinPhaseFreeRunningMode.
SpecificProblem PhaseFreeRunningModeEntered
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
5.161.1Consequences
Localclockaccuracyisoutsideoftheholdoverspecification.TheclockcannotbeusedasaMasterany
more.
133/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhenthe1588v2synchronizationfunctionenterslockedstatus.
5.162PhaseHoldoverModeEntered
TheNEhaslosttraceabilitytotheGrandmasterandrunsinPhaseHoldoverMode.
SpecificProblem PhaseHoldoverModeEntered
Source
NE
AlarmType
CommunicationAlarm
Severity
Major
5.162.1Consequences
LocalclockaccuracyisstillwithintheholdoverspecificationanditcanbeusedasaMasterfora
limitedperiod.
CheckthereasonwhyGrandmastertraceabilityislost.
ThealarmisclearedwhentheGrandmastertraceabilityisrecoveredorwhenthenodeentersinto
FreeRunningModeaftertheholdoverdurationexpires.
5.163PLCR
PartialLossofCapacityReceived(PLCR)
SomeoftheVirtualContainers(VCs)belongingtoaVirtualConcatenationGroup(VCG)are
temporarilyremovedinthereceivedirection.
SpecificProblem PLCR
Source
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause BandwithReduced
TheAlarmisclearedwhenthetemporarilyremovedVCsarerestored.
5.164PLCT
134/219
14/08/2015
AlarmDescriptions
PartialLossofCapacityTransmit(PLCT)
SomeoftheVirtualContainers(VCs)belongingtoaVirtualConcatenationGroup(VCG)are
temporarilyremovedinthetransmitdirection.
SpecificProblem PLCT
Source
AlarmType
CommunicationAlarm
Severity
Major
TheAlarmisclearedwhenthetemporarilyremovedVCsarerestored.
5.165PLM(Major)
PayloadMismatch(PLM)
ThedetectionofPLMisbasedonacomparisonbetweentheexpectedTrailSignalLabel(TSL),
representingtheselected/activatedadaptionfunction,andtheacceptedTSL.
SpecificProblem PLM
Source
VC3
VC4
VC412
AlarmType
CommunicationAlarm
Severity
Major
5.165.1Consequences
Serviceunavailable.
Ceasetheparticulartransmissionerror.
Checksource.
5.166PLM(Critical)
PayloadMismatch(PLM)
Nonconsistentconfiguration,sothereceivedC2byteisnotequaltotheexpectedC2byte.
135/219
14/08/2015
AlarmDescriptions
SpecificProblem PLM
Source
VC12
VC4
AlarmType
CommunicationAlarm
Severity
Critical
ProbableCause SignalLabelMismatch
5.166.1Consequences
Thealarmisclearedwhentheconfigurationmismatchisresolved.
5.167PowerFailure(LowerInput)
SpecificProblem PowerFailure(lowerinput)
Source
NE
AlarmType
EquipmentAlarm
Severity
Major
5.168PPPDown
FailureintheDataCommunicationNetwork(DCN)communication.
Note: ValidforbothIPv4andIPv6.
SpecificProblem PPPdown
Source
PPP
AlarmType
CommunicationAlarm
Severity
Minor
5.169ProtectedLineInterface:EquipmentAlarm(Minor)
ThealarmisraisedifoneoftheApplicationPluginUnits(APU)inanMSPconfigurationisfaulty.
SpecificProblem UnabletoProtect
Source
MSP
136/219
14/08/2015
AlarmDescriptions
AlarmType
EquipmentAlarm
Severity
Minor
5.169.1Consequences
OnlyoneofthetwoAPUsintheMSPconfigurationisoperatingcorrectly.Ifthereisafailureinthe
secondAPU,thereisacompletelossoftraffic.
Checkandifnecessary,replacethefaultyAPU.
ThealarmisclearedwhenbothAPUsareoperatingcorrectly.
5.170ProtectedLineInterface:EquipmentAlarm(Critical)
ThealarmisraisedifbothAPUs(ApplicationPluginUnits)inanMSPconfigurationarefaulty.
Source
MSP
AlarmType
EquipmentAlarm
Severity
Critical
5.170.1Consequences
BothAPUsintheMSPconfigurationarefaulty.Thereisacompletelossoftraffic.
Checkandifnecessary,replacetheAPUs.
ThealarmisclearedwhenbothAPUsareoperatingcorrectly.
5.171ProtectedLineInterface:CommunicationAlarm(Minor)
ThealarmisraisedifaSignalFail(SF)isdetectedinoneoftheSTM1linesinanMSPconfiguration.
Source
MSP
AlarmType
CommunicationAlarm
Severity
Minor
137/219
14/08/2015
AlarmDescriptions
5.171.1Consequences
OnlyoneofthetwoSTM1linesintheMSPconfigurationisoperatingcorrectly.IfthesecondSTM1
linefails,thereisacompletelossoftraffic.
CheckthefaultySTM1line.
ThealarmisclearedwhenbothSTM1linesareoperatingcorrectly.
5.172ProtectedLineInterface:CommunicationAlarm(Critical)
ThealarmisraisedifbothSTM1linesinanMSPconfigurationfails.
Source
MSP
AlarmType
CommunicationAlarm
Severity
Critical
5.172.1Consequences
AfailinbothSTM1linesresultsincompletelossoftraffic.
CheckthefaultySTM1lines.
ThealarmisclearedwhenbothSTM1linesareoperatingcorrectly.
5.173ProtectedPort
ThisalarmisonlyapplicableforLTU2155.ThealarmisraisedwhenbothportsinanSFPport
protectionpairaredetectedasfaulty.
SpecificProblem ProtectedPort
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.173.1Consequences
Trafficloss.
138/219
14/08/2015
AlarmDescriptions
IfoneoftheSFPsappearstobeworkingstill,thefollowingapplies:Ifautomaticswitchingis
activated,whichisthedefaultbehavior,nocorrectiveactionisneeded.Otherwiseperformamanual
switch,seeCLIUserGuide,Reference[2].
IfnoneoftheSFPsappearstobeworking,trythefollowing:
Danger!
Neverlookdirectlyintotheendofafiberopticcable,orotherlasersource.Equipmentthat
transmitslaserlightcancausepermanenteyedamage.Switchoffthelaserbeforestartingworkon
laserequipment.
1. VerifythatbothSFPsarestillinplace.
2. IftheSFPLOSalarmortheRDIalarmisactive,trythefollowing:
VerifythattheYcableusedforSFPportprotectionisOK.
VerifythatthelineisOK.
Correctanyrelevantproblemsatthefarend.
Afteranautomaticswitch,theNEmonitorstheactiveport.Iftheactiveportbecomesfreeoffaults
within30minutes,thealarmiscleared.Otherwise,anewswitchingandrecoveryprocedureis
started.
Afteramanualswitch,theNEmonitorstheactiveportandclearsthealarmiftheactiveportis
detectedasfreeoffaults.Otherwise,anewmanualswitchisrequired,seeCLIUserGuide,Reference
[2].
5.174PTM
PayloadTypeIdentifierMismatch(PTM)
ThePayloadTypeIdentifier(PTI)fieldinthereceivedframeisdifferentfrom000b(clientdata
frame),or100bdoesnotmatchoneoftheconfiguredvalues.
SpecificProblem PTM
Source
GFP
AlarmType
CommunicationAlarm
Severity
Major
1. Checkthelocalconfiguration.
2. Checktheremoteconfiguration.
5.175RadioFrame(Major)
Thereceiverfailedtosynchronizetheframeofthereceivedcompositebitstreamduetosignal
139/219
14/08/2015
AlarmDescriptions
failure.
SpecificProblem RadioFrame
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.176RadioFrame(Critical)
Thereceiverfailedtosynchronizetheframeofthereceivedcompositebitstreamduetosignal
failure.
SpecificProblem RadioFrame
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Critical
5.177RadioID(Major)
ThereceivedtrafficcomesfromaterminalwithanIDnotmatchingtheFarEndID.Possiblecauses
arethefollowing:
WrongRadioIDissetineithernearendorfarendterminal.
Theantennaalignmentisincorrectandthenearendradioreceivesasignalfromanotherradio
onthesamefrequency.
SpecificProblem RadioID
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.177.1Consequences
1. CheckRadioIDonbothnearendandfarendterminal.
2. IfRadioIDiscorrectonbothnearendandfarend,checkantennaalignment.
140/219
14/08/2015
AlarmDescriptions
3. Performaninterferencecheckbymeasuringinputreceivelevelwhenfarendtransmitteris
turnedoff.
ThealarmisclearedwhencorrectRadioIDisset,orifRemoteIDcheckisdisabled.
5.178RadioID(Critical)
ThereceivedtrafficcomesfromaterminalwithanIDnotmatchingtheFarEndID.Possiblecauses
arethefollowing:
WrongRadioIDissetineithernearendorfarendterminal.
Theantennaalignmentisincorrectandthenearendradioreceivesasignalfromanotherradio.
SpecificProblem RadioID
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Critical
5.178.1Consequences
Noconnectionwithfarendandtrafficloss.
1. CheckRadioIDonbothnearendandfarendterminal.
2. IfRadioIDiscorrectonbothnearendandfarend,checkantennaalignment.
3. Performaninterferencecheckbymeasuringinputreceivelevelwhenfarendtransmitteris
turnedoff.
ThealarmisclearedwhencorrectRadioIDisset,orifRemoteIDcheckisdisabled.
5.179RAI
RemoteAlarmIndication(RAI)
SpecificProblem RAI
Source
E2/E3
FramedE1
AlarmType
CommunicationAlarm
Severity
Minor
141/219
14/08/2015
AlarmDescriptions
ProbableCause RemoteAlarmIndication
5.180RAUPowerSupplyChanged
MINILINKTNcanfeedtheRAUwithapowersupplyofeither+57VDCor48VDC.Theuseof48V
DCcansupportahigherpowerconsumptionoftheRAU,buttherearecertainprerequisites.
ThealarmindicatesthattheselectedRAUpowersupplyisnotavailableduetooneofthefollowing
reasons:
DCBypasscannotbeenabledbecausetheprerequisitesontheNEpowersupplyarenotfulfilled.
ThereisincompatibilitybetweentheselectedRAUpowersupplysettingandtheinstalled
MMU/RAU.
SpecificProblem RAUpowersupplychanged
Source
MMU
AlarmType
EquipmentAlarm
Severity
Minor
5.180.1Consequences
AswitchofRAUpowersupplymayresultinRAUsthatarenotsupportedbythenewpowersupply
rangemaybeturnedoff.Theswitchcanalsoresultinchangesinthepowerconsumption.
VerifythatthecorrectprerequisitesarefulfilledfortherequiredpowersupplyandthattheNEis
correctlyconfigured.Formoreinformationontheprerequisites,seeTroubleshooting,Reference[22].
ThealarmisclearedwhenallcircumstancesthatpreventstheNEfromusingtheselectedpower
supplyisremoved.
5.181RCC(Major)
RadioCommunicationChannel(RCC)
CommunicationislostontheRCC,betweentheMMUandtheRAU.
SpecificProblem RCC
Source
AllMMUs
RAU
AlarmType
CommunicationAlarm
Severity
Major
142/219
14/08/2015
AlarmDescriptions
5.181.1Consequences
CommunicationbetweenthestandbyMMUandtheRAUislost,resultinginthetransmitterontheRAU
beingswitchedoff.
Figure24WorkflowforRCCAlarmCorrectiveActions
TochecktheconnectionbetweentheMMUandtheRAU,dothefollowing:
1. ChecktheIFcablewithaSiteMaster(4.5MHzto350MHz).
143/219
14/08/2015
AlarmDescriptions
2. Checktheindoorradioconnectorforshortcircuitandbadorintermittentconnections.
3. Checktheradiointerfacepanelconnectionandthestationradiocable.
4. Checkthattheoutdoorradioconnectorsealingiscorrect,thatis,thereisnowaterleakagein
thecable.
5. CheckthatthesealingoftheIFcablegroundingiscorrect,thatis,thereisnowaterleakagein
thecable.
Ifnoneoftheabovestepsclearthealarm,hardwarereplacementisrequired.
Toreplacethefaultyhardware,dothefollowing:
6. ReplacetheMMU.
IftheRCCalarmiscleared,describethefaultontheBlueTagandsendittotheRepair
CentertogetherwiththefaultyMMU.
IftheRCCalarmisnotcleared,reusetheinitialMMUandgotoStep7.
7. ReplacetheRAU.DescribethefaultontheBlueTagandsendittotheRepairCentertogether
withthefaultyRAU.
ThealarmisclearedwhentheRCCcommunicationisrestored.
5.182RCC(Critical)
RadioCommunicationChannel(RCC)
CommunicationislostontheRCC,betweentheMMUandtheRAU.
SpecificProblem RCC
Source
AllMMUs
RAU
AlarmType
CommunicationAlarm
Severity
Critical
5.182.1Consequences
CommunicationbetweentheMMUandtheRAUislost,resultinginthetransmitterontheRAUbeing
switchedoff.
144/219
14/08/2015
AlarmDescriptions
Figure25WorkflowforRCCAlarmCorrectiveActions
TochecktheconnectionbetweentheMMUandtheRAU,dothefollowing:
1. ChecktheIFcablewithaSiteMaster(4.5MHzto350MHz).
2. Checktheindoorradioconnectorforshortcircuitandbadorintermittentconnections.
3. Checktheradiointerfacepanelconnectionandthestationradiocable.
4. Checkthattheoutdoorradioconnectorsealingiscorrect,thatis,thereisnowaterleakagein
thecable.
5. CheckthatthesealingoftheIFcablegroundingiscorrect,thatis,thereisnowaterleakagein
thecable.
145/219
14/08/2015
AlarmDescriptions
Ifnoneoftheabovestepsclearthealarm,hardwarereplacementisrequired.
Toreplacethefaultyhardware,dothefollowing:
6. ReplacetheMMU.
IftheRCCalarmiscleared,describethefaultontheBlueTagandsendittotheRepair
CentertogetherwiththefaultyMMU.
IftheRCCalarmisnotcleared,reusetheinitialMMUandgotoStep7.
7. ReplacetheRAU.DescribethefaultontheBlueTagandsendittotheRepairCentertogether
withthefaultyRAU.
ThealarmisclearedwhentheRCCcommunicationisrestored.
5.183RDI(Minor)
RemoteDefectIndication(RDI)
TheRDIalarmindicatesthatthetrafficsignaltransmittedfromthenearendlineinterfaceisreceived
witherrorsonthefarendlineinterface.
SpecificProblem RDI
Source
MS/RS
VC12
VC4
AlarmType
CommunicationAlarm
Severity
Minor
ProbableCause FarEndReceiverFailure
5.183.1Consequences
Theserviceisunavailableatfarend.
146/219
14/08/2015
AlarmDescriptions
Figure26WorkflowforRDIAlarmCorrectiveActions,Part1
147/219
14/08/2015
AlarmDescriptions
1. Checkifanyalarmisraisedonthefarendreceivinginterface.
Ifthereisnoalarmraisedonthefarend,gotoStep2.
Ifthereareoneormorealarmsraisedonthefarend,reviewthealarmsandtake
correctiveactionsaccordingtotheiralarmdescription.Forbasicandgeneralfaultfinding
instructionsofRDI,gotoStep3
2. PerformacoldrestartofthePlugInUnit(PIU)thathasreceivedtheRDIalarm,andrestart
MINILINKCraft.
Caution!
148/219
14/08/2015
AlarmDescriptions
Onsiteaction:IftheRDIalarmisnotclearedaftertherestart,replacethePIUonthe
nearend.DescribethefaultontheBlueTagandsendittotheRepairCentertogether
withthefaultyPIU.
Onsiteaction:IftheRDIalarmiscleared,monitorthehopforfurtheralarms.Iffurther
alarmsareraisedwithoutanyalarmsoccurringonthefarendinterface,replacethePIU
onthenearend.DescribethefaultontheBlueTagandsendittotheRepairCenter
togetherwiththefaultyPIU.
3. Makesurethattheconfigurationiscorrectlysetuponthenearendandthefarendandis
accordingtotheSiteInstallationDocumentation(SID).
Iftheconfigurationofthenearendandthefarendisnotcorrectlysetupandisnot
accordingtotheSID,takecorrectiveactions.IftheRDIalarmisnotclearedafterthe
correction,gotoStep4.
Iftheconfigurationofthenearendandthefarendiscorrectlysetupandisaccordingto
theSID,gotoStep4.
4. Performalinelooptestonthefarendinterface.
Onsiteaction:Ifthealarmisnotclearedonthefarendduringthetest,replacethePIU
onthefarend.DescribethefaultontheBlueTagandsendittotheRepairCenter
Ifthealarmisclearedonthefarendduringthetest,gotoStep5.
5. Performalinelooptestonthenearendinterface.
Ifthealarmisnotclearedonthefarendduringthetest,gotoStep6.
Onsiteaction:Ifthealarmisclearedonthefarendduringthetest,replacethePIUon
withthefaultyPIU.
6. Onsiteaction:Checkthetransmissionandthecablesbetweenthetransmittingandreceiving
interfacesforfaults.
folder.
Thealarmisclearedwhenthefarendinterfacereceivesavalidtrafficsignal.
5.184RDI(Major)
RemoteDefectIndication(RDI)
TheRDIalarmindicatesthatthetrafficsignaltransmittedfromthenearendlineinterfaceisreceived
witherrorsonthefarendlineinterface.
SpecificProblem RDI
Source
AU4
MS
TU3
TU12
VC3
149/219
14/08/2015
AlarmDescriptions
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Major
5.184.1Consequences
Serviceunavailableatfarend.
150/219
14/08/2015
AlarmDescriptions
1. Checkifanyalarmisraisedonthefarendreceivinginterface.
Ifthereisnoalarmraisedonthefarend,gotoStep2.
Ifthereareoneormorealarmsraisedonthefarend,reviewthealarmsandtake
correctiveactionsaccordingtotheiralarmdescription.Forbasicandgeneralfaultfinding
instructionsofRDI,gotoStep3.
2. PerformacoldrestartofthePlugInUnit(PIU)thathasreceivedtheRDIalarm,andrestart
MINILINKCraft.
Caution!
151/219
14/08/2015
AlarmDescriptions
Onsiteaction:IftheRDIalarmisnotclearedaftertherestart,replacethePIUonthe
withthefaultyPIU.
Onsiteaction:IftheRDIalarmiscleared,monitorthehopforfurtheralarms.Iffurther
alarmsareraisedwithoutanyalarmsoccurringonthefarendinterface,replacethePIU
onthenearend.DescribethefaultontheBlueTagandsendittotheRepairCenter
3. Makesurethattheconfigurationiscorrectlysetuponthenearendandthefarend,andis
accordingtotheSiteInstallationDocumentation(SID).
Iftheconfigurationofthenearendandthefarendisnotcorrectlysetupandisnot
accordingtotheSID,takecorrectiveactions.IftheRDIalarmisnotclearedafterthe
correction,gotoStep4.
Iftheconfigurationofthenearendandthefarendiscorrectlysetupandisaccordingto
theSID,gotoStep4.
4. Performalinelooptestonthefarendinterface.
Onsiteaction:Ifthealarmisnotclearedonthefarendduringthetest,replacethePIU
onthefarend.DescribethefaultontheBlueTagandsendittotheRepairCenter
Ifthealarmisclearedonthefarendduringthetest,gotoStep5.
5. Performalinelooptestonthenearendinterface,thathastheRDIalarmraised.
Ifthealarmisnotclearedonthefarendduringthetest,gotoStep6.
Onsiteaction:Ifthealarmisclearedonthefarendduringthetest,replacethePIUon
withthefaultyPIU.
6. Onsiteaction:Checkthetransmissionandthecablesbetweenthetransmittingandreceiving
interfacesforfaults.
folder.
Thealarmisclearedwhenthefarendinterfacereceivesavalidtrafficsignal.
5.185RDIBitSetinCCM
AMaintenanceEndPoint(MEP)hasreceivedaContinuityCheckMessage(CCM)framewiththe
RemoteDefectIndication(RDI)fieldset.
Note: ThisalarmisavailablewithboththeIEEE802.1agandtheITUTY.1731standardsfor
ConnectivityFaultManagement(CFM).
SpecificProblem RDIbitsetinCCM
Source
LANwithMEP
WANwithMEP
LAGwithMEP
152/219
14/08/2015
AlarmDescriptions
AlarmType
CommunicationAlarm
Severity
Warning
5.186ReceivedInvalidCCM
TheMaintenanceEndPoint(MEP)hasreceivedatleastoneinvalidContinuityCheckMessage(CCM),
theCCMintervalofwhichhasnotyettimedout.
Management(CFM).
SpecificProblem ReceivedInvalidCCM
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Major
5.187RemoteFailureIndication
PersistenceofanRDIIMAdefectatthenearend(morethan2.5+/0.5sec).AnRxfailureis
detectedonthecorrespondinginterfaceatthenearendIMAunit.
SpecificProblem RemoteFailureIndication
Source
IMALink
AlarmType
CommunicationAlarm
Severity
Critical
5.187.1Consequences
Sincethefarenddetectsafailureatthecorrespondinginterface,thelinkisnotactiveanymore.
RelatedIMAgroupscanalsobeaffectedbythefault:incasetheIMAgroupgoesbelowthe"minimum
numberof(active)links"noAsynchronousTransferMode(ATM)trafficcanflowatallthroughthe
group.InthiscasetheoperationalstatusofrelatedATMIMA(IMAgroup)andATMgoestodown.If
theIMAgroupstillhaveaminimumnumberoflinksitcanstilltransmittheguaranteedbandwidthof
traffic.
153/219
14/08/2015
AlarmDescriptions
Thefarendlinkshouldexperienceanyfaultfromphysical(LossOfSignal(LOS)/LossOfFrame
(LOF)/AlarmIndicationSignal(AIS))orTC(LCD)layer.
Checkthatthecorrespondingnearendlinkisproperlyconnectedandconfigured.
Thealarmisclearedwhenthefarendnolongerdetectsanylinkfailure.
5.188RemoteLossofFrames
ThealarmisraisedifaframereceivedatthenearendhastheRbitsetinthecontrolword.Aframe
thatisreceivedwiththeRbitsetinthecontrolwordindicatesfailureoftheconnectioninthe
oppositedirection.
SpecificProblem RemoteLossofFrames
Source
CES
AlarmType
CommunicationAlarm
Severity
Minor
ProbableCause RemoteAlarmIndication
5.188.1Consequences
AremotelossofframesalarmisreportedinMINILINKCraft.Ifstructureawaremodeisconfigured,
aRemoteDefectIndication(RDI)alarmisgenerated.
Checkthenetworkperformanceinthenearendtofarenddirection.Thealarmindicatesthatthereis
aproblemwithnetworktrafficfromthenearendtothefarend.
ThealarmisclearedwhenaframereceivedatthenearenddoesnothavetheRbitsetinthecontrol
word.
5.189RemoteTxSwitchOver
Thisalarmisraisedwhenanactiveradioswitchoverisorderedfromthefarendside.Itisonlyvalid
inHotStandby(HSB).
Bydefault,raisingofthisalarmisdisabled.ItcanbeenabledinMINILINKCraft,seeMINILINK
CraftUserInterfaceDescriptions,Reference[7],butitisonlyrecommendedtoenableitinhopsthat
havehighfademarginsandlowprobabilityfordeepflatormultipathfading.
SpecificProblem RemoteTxSwitchOver
Source
SWITCH
AlarmType
EquipmentAlarm
154/219
14/08/2015
Severity
AlarmDescriptions
Major
5.189.1Consequences
Theprotectionswitchingfunctionislockeduntilthealarmisresetmanually.Eveniftheinitialfault
thattriggeredtheswitchoveriscorrected,theswitchingfunctiondoesnotworkandthehoponly
functionsas1+0untilthealarmisresetmanually.
TheremoteTXswitchoverfunctioninHSBisusedforprotectionofradioequipmentaftertheoutput
RFpowerdetectorthisincludesbranching,flexiblewaveguide,powersplitter,andantenna.Faultsin
thisequipmentcanbecaused,forexample,byhighwindloadorfadingconditions(bothrainand
multipath).Thiskindofequipmentfaultisnotpossibletodetectatthenearendside.Ifsuchafault
occursontheactiveTXpath,thefarendsidelosesinputsignalonbothreceivers.Itislikelythat
eithertheRadioFramealarmortheRFInputLevelalarmisraised.After4seconds,acommandis
senttothenearendsidetoswitchactiveTXandaftercompletiontheconnectionisupagain.
BecausearemoteTXswitchoverclearsanyalarmsraisedbytheinitialfault,theRemoteTXSwitch
Overalarmmustberaisedtopreventaswitchoverbacktothefaultypath.Forthisreason,the
RemoteTXSwitchOveralarmmustberesetmanuallyiffullequipmentprotectioninHSBiswanted.
Correcttheinitialfaultthattriggeredtheswitchover,formoreinformationseeTroubleshooting,
Reference[22].
Thealarmisnotclearedautomatically.ItmustberesetmanuallyinMINILINKCraftontheSWITCH
AlarmsandStatuspagefortheapplicableMMU.Thereasonforthisisthatthefaultthattriggeredthe
remoteTXswitchovermustbeunderstoodandcorrectedbeforearemoteTXswitchovercantake
placeagain.AlwaysresettheRemoteTXSwitchOveralarmbeforetakingahopintoserviceas
installationworkandtestingcanalsotriggerthefunction.
5.190ReservedPosition
Thealarmisraisediftheunitinacertainpositionisofadifferenttypethanthetypeofunitthe
positionisreservedfor.
SpecificProblem ReservedPosition(OnlyapplicableifsourceisPluginUnitorRAU
Source
ReservedPositionat<BoardType>(OnlyapplicableifsourceisSFP)
PluginUnit
RAU
SFP
AlarmType
EquipmentAlarm
Severity
Critical
155/219
14/08/2015
AlarmDescriptions
5.190.1Consequences
Theunitisnotoperatingcorrectly.
Cleartheslotreservationorinstallacorrectunit.
Thealarmisclearedwhentheslotreservationisclearedoracorrectunitisinstalled.
5.191RFInputLevel(Critical)
ThereceivedRadioFrequency(RF)inputsignalleveldropsbelowthethresholdforthereceiver.
ApplicableforRF(1+0).
SpecificProblem RFInputLevel
Source
RF
AlarmType
CommunicationAlarm
Severity
Critical
156/219
14/08/2015
AlarmDescriptions
Figure30WorkflowforRFInputLevelAlarmCorrectiveActions,Part1
157/219
14/08/2015
AlarmDescriptions
158/219
14/08/2015
AlarmDescriptions
1. MakesurethattheconfigurationofthenearendandthefarendisaccordingtotheSite
InstallationDocumentation(SID).
IftheconfigurationofthenearendandthefarendisnotaccordingtotheSID,take
correctiveactions.IftheRFInputLevelalarmisnotclearedafterthecorrection,goto
Step2.
IftheconfigurationofthenearendandthefarendisaccordingtotheSID,gotoStep2.
2. CheckiftheRFinputlevelisbelowthethresholdlevelforBER106forthecurrent
159/219
14/08/2015
AlarmDescriptions
configuration.
IftheRFinputlevelisnotbelowthethresholdlevelforBER106forthecurrent
configuration,gotostepStep3.
IftheRFinputlevelisbelowthethresholdlevelforBER106forthecurrentconfiguration,
gotoStep4.
Caution!
Onsiteaction:IftheRFInputLevelalarmisnotclearedaftertherestart,replacethe
RAUonthenearend.DescribethefaultontheBlueTagandsendittotheRepairCenter
togetherwiththefaultyRAU.
Onsiteaction:IftheRFInputLevelalarmiscleared,monitorthehopforfurtherRFInput
Levelalarms.IfthealarmisraisedagainwhileRFinputlevelishigherthanthethreshold
levelforBER106forthecurrentconfiguration,replacetheRAUonthenearend.
RAU.
4. Onsiteaction:PerformanRFlooptestonthenearendRAU.TurnofftheRAUtransmitteron
thefarendduringthetest.
withthefaultyRAU.
5. CheckiftheRFOutputLevelalarmisactiveonthefarendRAU.
IftheRFOutputLevelalarmisnotactive,gotoStep6.
Onsiteaction:IftheRFOutputLevelalarmisactive,replacetheRAUonthefarend.
RAU.
6. CheckiftheRFoutputlevelonthefarendisaccordingtothelinkbudget.
IftheRFoutputlevelisnotaccordingtothelinkbudget,verifythecorrectvaluetobe
usedwithtransmissiondesigndepartmentandchangethevalue.
IftheRFoutputlevelisaccordingtothelinkbudget,gotoStep7.
7. Onsiteaction:PerformanRFlooptestonthefarendRAU.TurnofftheRAUtransmitteronthe
nearendduringthetest.
IftheRFinputpowerisnotabout50dBm(10dB)onthefarendRAUduringthetest,
replacetheRAUonthefarend.DescribethefaultontheBlueTagandsendittothe
IftheRFinputpowerisabout50dBm(10dB)onthefarendRAUduringthetest,go
toStep8.
8. Onsiteaction:Checkfadingconditionsandweathercircumstances.
9. Onsiteaction:Checkforpossibleobstaclesinterferingwiththelineofsight.
Iftherearenoobstacles,gotoStep10.
160/219
14/08/2015
AlarmDescriptions
Ifthereareobstacles,consultthetransmissiondesigndepartment.
10. Onsiteaction:Makesurethattheantennasarealignedcorrectlyonthenearendandthefar
endtomeetthelinkbudgettarget.
11. Onsiteaction:CheckthestatusoftheRFinputlevel,thatcanbestableorcanvaryovertime
indicatingmultipathfading.Ifyouareunsure,monitortheRFinputlevelfor24hourstofind
cyclicvariations.
IftheRFinputlevelisstable,gotoStep12.
IftheRFinputleveldecreaseisintermittentorperiodic,consultthetransmissiondesign
departmenttoanalyzethepossiblereflectionsandrefractions.
12. Onsiteaction:Makesurethatthepolarizationonthenearendandthefarendissetaccording
tothelinkbudgetplanning.
Ifthepolarizationonthenearendandthefarendisnotcorrectlyset,takecorrective
actions.
Ifthepolarizationonthenearendandthefarendiscorrectlyset,gotoStep13.
13. Onsiteaction:Replacetheantennaonthenearend.
IftheRFInputLevelalarmisnotclearedafterthereplacement,reinstalltheinitial
antenna,andgotoStep14.
IftheRFInputLevelalarmisclearedafterthereplacement,describethefaultontheBlue
TagandsendittotheRepairCentertogetherwiththefaultyantenna.
14. Onsiteaction:Replacetheantennaonthefarend.DescribethefaultontheBlueTagandsend
ittotheRepairCentertogetherwiththefaultyantenna.
ThealarmisclearedwhenthereceivedRFinputsignalisabovethethresholdforthereceiver.
5.192RFInputLevelDiv(Minor)
ThereceivedRadioFrequency(RF)inputsignalleveldropsbelowthethresholdfortheRxdiversity
channeloftheTRXSpaceDiversityCombiner(SDC).RFInputLevelandSDCDivHardwareError
alarmsmaskRFInputLevelDivalarmbecauseofhigherseverityinthereceiversection.
Applicablefor1+1SpaceDiversityconfiguration.
SpecificProblem RFInputLevelDiv
Source
TRXSDC
AlarmType
CommunicationAlarm
Severity
Minor
CheckthatthecableiscorrectlyconnectedbetweentheTRXSDCunitandtheRFbranchingfilter.If
161/219
14/08/2015
AlarmDescriptions
thecableisbroken,replacethecable.
ThealarmisclearedwhenthecableiscorrectlyconnectedbetweentheTRXSDCunitandtheRF
branchingfilter.
5.193RFInputLevelDiv(Major)
ThereceivedRadioFrequency(RF)inputsignalleveldropsbelowthethresholdfortheRxdiversity
channeloftheTRXSpaceDiversityCombiner(SDC).RFInputLevelandSDCDivHardwareError
alarmsmaskRFInputLevelDivalarmbecauseofhigherseverityinthereceiversection.
SpecificProblem RFInputLevelDiv
Source
TRXSDC
AlarmType
CommunicationAlarm
Severity
Major
branchingfilter.
5.194RFInputLevelMain(Minor)
ThereceivedRadioFrequency(RF)inputsignalleveldropsbelowthethresholdfortheRxmain
channeloftheTRXSpaceDiversityCombiner(SDC).RFInputLevelandSDCMainHardwareError
alarmsmaskRFInputLevelMainalarmbecauseofhigherseverityinthereceiversection.
SpecificProblem RFInputLevelMain
Source
TRXSDC
AlarmType
CommunicationAlarm
Severity
Minor
162/219
14/08/2015
AlarmDescriptions
branchingfilter.
5.195RFInputLevelMain(Major)
ThereceivedRadioFrequency(RF)inputsignalleveldropsbelowthethresholdfortheRxmain
channeloftheTRXSpaceDiversityCombiner(SDC).RFInputLevelandSDCMainHardwareError
alarmsmaskRFInputLevelMainalarmbecauseofhigherseverityinthereceiversection.
SpecificProblem RFInputLevelMain
Source
TRXSDC
AlarmType
CommunicationAlarm
Severity
Major
branchingfilter.
5.196RFInputThreshold
TheRadioFrequency(RF)inputleveldropsbelowtheRFInputAlarmThreshold.
SpecificProblem RFInputThreshold
Source
RF
SWITCH
AlarmType
CommunicationAlarm
Severity
Warning
5.197RFInputThresholdProtection
TheRadioFrequency(RF)inputlevelofbothreceiversinaprotectedterminaldropsbelowtheir
respectiveRFInputAlarmThreshold.
SpecificProblem RFInputThresholdProtection
Source
SWITCH
AlarmType
CommunicationAlarm
Severity
Warning
163/219
14/08/2015
AlarmDescriptions
5.198RFOutputLevel(Major)
TheRFOutputLevelalarmistriggeredifthetransmitterisunabletoachievetheconfiguredRFoutput
power.ApplicableforRAURF(1+1workingstandby)standbytransmitter.
SpecificProblem RFOutputLevel
Source
RF
AlarmType
CommunicationAlarm
Severity
Major
ProbableCause TransmitterFailure
Figure33WorkflowforRFOutputLevel(Major)AlarmCorrectiveActions
164/219
14/08/2015
AlarmDescriptions
Dothefollowing:
1. PerformanRFlooptestonthenearendRAU.TurnoffbothfarendRAUtransmittersduringthe
test.
Onsiteaction:Iftheinputpowerisnotabout50dBm(10dB),replacetheRAUwith
thealarmraisedonthenearend.DescribethefaultontheBlueTagandsendittothe
Iftheinputpowerisabout50dBm(10dB),gotoStep2.
Caution!
Onsiteaction:IftheRFOutputLevelalarmisnotclearedaftertherestart,replacethe
Onsiteaction:IftheRFOutputLevelalarmiscleared,monitorthehopforfurtherRF
OutputLevelalarms.Ifthealarmisraisedagain,replacetheRAUonthenearend.
RAU.
ThealarmisclearedwhenthetransmitterisabletoachievetheconfiguredRFoutputpower.
5.199RFOutputLevel(Critical)
TheRFOutputLevelalarmistriggeredifthetransmitterisunabletoachievetheconfiguredRFoutput
power.ApplicableforRAURF(1+0)andRAURF(1+1)activetransmitter.
SpecificProblem RFOutputLevel
Source
RF
AlarmType
CommunicationAlarm
Severity
Critical
165/219
14/08/2015
AlarmDescriptions
Figure34WorkflowforRFOutputLevel(Critical)AlarmCorrectiveActions
Dothefollowing:
1. PerformanRFlooptestonthenearendRAU.TurnoffbothfarendRAUtransmittersduringthe
test.
Onsiteaction:Iftheinputpowerisnotabout50dBm(10dB),replacetheRAUonthe
withthefaultyRAU.
Iftheinputpowerisabout50dBm(10dB),gotoStep2.
Caution!
166/219
14/08/2015
AlarmDescriptions
Onsiteaction:IftheRFOutputLevelalarmisnotclearedaftertherestart,replacethe
Onsiteaction:IftheRFOutputLevelalarmiscleared,monitorthehopforfurtherRF
OutputLevelalarms.Ifthealarmisraisedagain,replacetheRAUonthenearend.
RAU.
ThealarmisclearedwhenthetransmitterisabletoachievetheconfiguredRFoutputpower.
5.200RFOutputLevelATPC
ThisalarmindicatesthattheATPCFallbackfunctionalityisactivated.Thetransmitteroutputpoweris
continuouslyatMaximumATPCOutputPowertoolong.Thiscanoccurduetothefollowingreasons:
MaximumATPCOutputPowerissettoolow.
Thehopattenuationincreases(steadystate).
ThetransmitterPowerAmplifierisdeteriorating.
TheLowNoiseAmplifierinRxisdeteriorating.
SpecificProblem RFOutputLevelATPC
Source
RF
AlarmType
CommunicationAlarm
Severity
Major
5.200.1Consequences
Thehopmightbedownoritcanhavelowavailability.
Trythefollowing:
1. IncreasetheMaximumATPCOutputPower.
conditions).
3. IftheRAUisfaulty,replaceit,seeReplacingaRadioUnit,Reference[16].
TorestorenormalATPCfunctionagain:
1. DisableATPC(thatissetOutputPowerModetoRTPC).
2. EnableATPCagain.
167/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhennormalATPCfunctionisrestored.
5.201RLIMEOversubscription
ThetotalcapacityofthepacketlinksintheRLIMEgroupexceedsthemaximumcapacityoftheRL
IMEgroup.ThiscanoccurduringRLIMEconfigurationorradiolinkconfiguration.Itcanalsooccurif
theAdaptiveModulationfeatureincreasesthelinkcapacity.
SpecificProblem RLIMEOversubscription
Source
RLIME
AlarmType
CommunicationAlarm
Severity
Critical
5.201.1Consequences
Trafficcanbelost.
ReducethenumberofpacketlinksintheRLIMEgrouporreducethecapacityofthepacketlinksin
theRLIMEgroup.
ThealarmisclearedwhenthetotalcapacityofthepacketlinksconfiguredfortheRLIMEgroupisno
longerhigherthanthemaximumcapacityoftheRLIMEgroup.
5.202RLIMEResourceGroup1Oversubscription
TheRLIMEresourcegroupusesmorecapacitythanthemaximumcapacityallowed.
SpecificProblem RLIMEResourceGroup1Oversubscription
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
5.202.1Consequences
Lossoftraffic.
DecreasethecapacityusedbytheRLIMEmembersoftheresourcegroup.
ThealarmisclearedwhentheRLIMEmembersoftheresourcegroupnolongeruseacapacitythatis
higherthanthemaximumcapacityallowed.
168/219
14/08/2015
AlarmDescriptions
5.203RLIMEDegradedService
SpecificProblem DegradedService
Source
RLIME
AlarmType
CommunicationAlarm
Severity
Major
5.204RLIMENoTraffic
SpecificProblem NoTraffic
Source
RLIME
AlarmType
CommunicationAlarm
Severity
Critical
5.205RLIMEReassemblyFailure
SpecificProblem Reassemblyfailure
Source
RLIME
AlarmType
Severity
Major
5.206RunningConfigurationNotAccepted
TheMMU/RAU/SFPcouldnotaccepttherunningconfigurationtheserviceLEDisflashing.Theunit
couldalsobesubjecttoasoftwareupgrade.
SpecificProblem Runningconfigurationnotaccepted
Source
AllMMUs
AllRAUs
AllSFPs
AlarmType
EquipmentAlarm
Severity
Major
Theproblemcanoccuriftheinsertedboardisusinganincompatiblesoftwareversion.Seethe
compatibilitydocumentinthePlanningfolderoftheCPILibraryforinstructionsonhowtoverifyand
alignpluginunitandsoftwarecompatibility.
IfthealarmoccurseventhoughthesoftwareversioninstalledontheNEiscompatiblewiththeplug
169/219
14/08/2015
AlarmDescriptions
inunitsaveconfiguration,removetheboard,makeclearreservation,andinsertboardagain.
Downloadconfigurationfile.
5.207RxAFC
ThefrequencyofthereceivedsignalisoutsidetherangeoftheAutomaticFrequencyControl(AFC)in
theRAUreceiver.TheMMUhasdetectedadeviationbetweentheactualreceivedsecondintermediate
frequencyandthetheoreticalfrequency.Thetheoreticalfrequencyrequiresafrequencychangeasit
isattheboundaryoftheallowedrange.
SpecificProblem RxAFC
Source
RF
AlarmType
CommunicationAlarm
Severity
Major
170/219
14/08/2015
AlarmDescriptions
Figure35WorkflowforRxAFCAlarmCorrectiveActions
1. MakesurethattheRxfrequencyonthenearendcorrespondstotheTxfrequencyonthefar
end.
2. Onsiteaction:Performaninterferencetest,seeVerifyinganInstallation,Reference[24].
Note: Anundesiredsignalinthereceivercancauseinterferenceinmicrowavesystems.Asa
result,theAFCcannotmonitortheactuallyreceivedfrequencysignal.
3. Onsiteaction:PerformacoldrestartoftheRAUandrestartMINILINKCraft.
Caution!
171/219
14/08/2015
AlarmDescriptions
IftheRxAFCalarmisnotclearedaftertherestart,replacetheRAU.Describethefaulton
IftheRxAFCalarmiscleared,monitorthehopforfurtherRxAFCalarms.Ifthealarmis
raisedagain,replacetheRAU.DescribethefaultontheBlueTagandsendittotheRepair
CentertogetherwiththefaultyRAU.
ThealarmisclearedwhentheincomingRFsignaliswithintherangeofthereceiver.
5.208RXFrequency(Major)
Thereceiverfrequencysynthesizerloopisunlocked.MainreasonforanRXFrequencyalarmisa
hardwarefaultintheRAU.
SpecificProblem RXFrequency
Source
RF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.208.1Consequences
Thereceivingpathisswitched.
172/219
14/08/2015
AlarmDescriptions
Figure36WorkflowforRXFrequencyAlarmCorrectiveActions
Dothefollowing:
Caution!
Onsiteaction:IftheRXFrequencyalarmisnotclearedaftertherestart,replacethe
faultyRAU.
Onsiteaction:IftheRXFrequencyalarmiscleared,monitorthehopforfurtherRX
Frequencyalarms.Ifthealarmisraisedagain,replacetheRAU.Describethefaultonthe
BlueTagandsendittotheRepairCentertogetherwiththefaultyRAU.
5.209RXFrequency(Critical)
Thereceiverfrequencysynthesizerloopisunlocked.MainreasonforanRXFrequencyalarmisa
173/219
14/08/2015
AlarmDescriptions
SpecificProblem RXFrequency
Source
RF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.209.1Consequences
Degradationintrafficcapacity,ortrafficiscompletelylost.
Figure37WorkflowforRXFrequencyAlarmCorrectiveActions
Dothefollowing:
174/219
14/08/2015
AlarmDescriptions
Caution!
Onsiteaction:IftheRXFrequencyalarmisnotclearedaftertherestart,replacethe
faultyRAU.
Onsiteaction:IftheRXFrequencyalarmiscleared,monitorthehopforfurtherRX
5.210RxIFInput
FailureonthereceiverIntermediateFrequency(IF)signalfromtheRAUtotheMMU.
SpecificProblem RxIFInput
Source
RAUIF
AlarmType
CommunicationAlarm
Severity
Major
5.211RxLinkMisconnected
RxlinkisnotconnectedtothesamefarendInverseMultiplexeroverATM(IMA)unitastheotherRx
linksinthegroup.
SpecificProblem RxLinkMisconnected
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Critical
5.211.1Consequences
WrongconnectionoftheRxIMAlink.
ConnecttheRxIMAlinktothesamefarendIMAunitastheotherRxlinksinthegroup.
175/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhentheRxIMAlinkiscorrectlyconnectedtothefarendIMAunit.
5.212RxUnusable(FarEnd)
ThealarmisreportedwhenthefarendInverseMultiplexeroverATM(IMA)unitdeterminesthatits
Rxlinkcannotbeusedforreceptioninthegroup.
SpecificProblem RxUnusable(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Major
5.212.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbetransmittedoverthespecificIMALink.Related
IMAgroupscanalsobeaffectedbythefault:incasetheIMAgroupgoesbelowthe"minimumnumber
of(active)links"noATMtrafficcanflowatallthroughthegroup.Inthiscasetheoperationalstatus
ofrelatedATMIMA(IMAgroup)andATMgoestodown.IftheIMAgroupstillhaveaminimum
numberoflinksitcanstilltransmittheguaranteedbandwidthoftraffic.
AfaultinthefarendlinkorprotocolisdetectedbytheIMAunitatRxdirection.
CheckthestatusofthefarendRxlink.
ThealarmisclearedwhenthefarendRxlinkfailureisdeletedorthecauseatthecorresponding
nearendlink.
5.213SDCDADECalibrationMismatchorNotCalibrated
Thealarmisraisedinthefollowingcases:
SpaceDiversityCombiner(SDC)DelayAntennaDelayEqualization(DADE)calibrationisnot
performed.
TRXSDCisreplaced,butnonewDADEcalibrationisperformed.
SpecificProblem SDCDADECalibrationMismatchorNotCalibrated
Source
TRXSDC
AlarmType
EquipmentAlarm
Severity
Major
5.213.1Consequences
176/219
14/08/2015
AlarmDescriptions
TheSDCfunctioncannotbeused.Thepathselectionisnotallowedanditisnotpossibletousethe
combiningfunctionuntilvalidDADEcalibrationisperformed.
AfterSDCisenabled,thedefaultsettingforpathselectoristhemainchannel.WithoutDADE
calibration,SDCcombinermodecannotbeactivated.ThemainchannelworkswithoutDADE
calibration.WhenSDCisenabled,DADEcalibrationmustbeperformed.
TheproblemisthattheDADEcalibrationisnotperformedafterTRXSDCinstallationorwhenthereis
aTRXSDCreplacement.
PerformDADEcalibration.
ThealarmisclearedwhenDADEcalibrationisperformed.
5.214SDCDivHardwareError
ThealarmisraisedwhenthereisahardwareerrorontheRxdiversitychanneloftheTRXSpace
DiversityCombiner(SDC).
SpecificProblem SDCDivHardwareError
Source
TRXSDC
AlarmType
EquipmentAlarm
Severity
Major
5.214.1Consequences
For1+0SpaceDiversityconfiguration,theSDCfunctionisoutofworkbecausethereceiverforthe
diversitychannelisfaulty.Thesystemstillworksasasinglereceiver,withoutaffectingthetraffic.
For1+1SpaceDiversityconfiguration,anRxdiversityswitchisperformedtotheMMUandTRXSDC
withnofaults.TheSDCisavailablewithfullfunctionality.
SDCDiversityHardwareErrorindicatesthattheSDCfunctionisnotavailablebecauseofafailure
insidetheRxdiversityreceiver.TheRxmainreceiverstillworks,sonotrafficisaffected.
In1+1SpaceDiversityconfiguration,SDCMainHardwareErrorandSDCDivHardwareErroralarms
areusedasatriggerforRadioProtectionSwitch(RPS),thatis,Rxdiversityswitch.Theswitchis
performedtousethesignalcomingfromthecompanionMMUconnectedtotheTRXhavingfullSDC
functionality.Theswitchdoesnotaffectthetrafficandtheprotectionisanequipmentandradio
protection.
ReplacethefaultyTRXSDC,seeReplacingaTRX,Reference[19].
177/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhenthefaultyTRXSDCisreplaced.
5.215SDCMainHardwareError
ThealarmisraisedwhenthereisahardwareerrorontheRxmainchanneloftheTRXSpace
DiversityCombiner(SDC).
SpecificProblem SDCMainHardwareError
Source
TRXSDC
AlarmType
EquipmentAlarm
Severity
Major
5.215.1Consequences
For1+0SpaceDiversityconfiguration,theSDCfunctionisoutofworkbecausethereceiverforthe
mainchannelisfaulty.Thesystemstillworksasasinglereceiver,withoutaffectingthetraffic.
For1+1SpaceDiversityconfiguration,anRxdiversityswitchisperformedtotheMMUandTRXSDC
withnofaults.TheSDCisavailablewithfullfunctionality.
SDCMainHardwareErrorindicatesthattheSDCfunctionisnotavailablebecauseofafailureinside
theRxmainreceiver.TheRxdiversityreceiverstillworks,sonotrafficisaffected.
In1+1SpaceDiversityconfiguration,SDCMainHardwareErrorandSDCDivHardwareErroralarms
areusedasatriggerforRadioProtectionSwitch(RPS),thatis,Rxdiversityswitch.Theswitchis
performedtousethesignalcomingfromthecompanionMMUconnectedtotheTRXhavingfullSDC
functionality.Theswitchdoesnotaffectthetrafficandtheprotectionisanequipmentandradio
protection.
ReplacethefaultyTRXSDC,seeReplacingaTRX,Reference[19].
ThealarmisclearedwhenthefaultyTRXSDCisreplaced.
5.216SES15MinThresholdCrossing
SESthresholdcrossingfor15minutescompositeperformancemonitoring.
SpecificProblem SES15minthresholdcrossing
Source
RAUIF
178/219
14/08/2015
AlarmDescriptions
SWITCH
AlarmType
Severity
Major
5.217SES24hThresholdCrossing
SESthresholdcrossingfor24hourscompositeperformancemonitoring.
SpecificProblem SES24hthresholdcrossing
Source
RAUIF
SWITCH
AlarmType
Severity
Major
5.218SFPLOS(Major)
SFPreportslossofsignal.
Applicableforthestandbyinterfaceina1+1configuration.
SpecificProblem SFPLOS
Source
LINERS(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.218.1Consequences
179/219
14/08/2015
AlarmDescriptions
Figure38WorkflowforSFPLOSAlarmCorrectiveActions
Dothefollowing:
1. PerformalineloopontheinterfaceofthefarendPluginUnit(PIU).
IftheSFPLOSalarmisnotcleared,gotoStep2.
Onsiteaction:IftheSFPLOSalarmiscleared,replacethePIUonthefarend.Describe
2. Onsiteaction:ReplacetheSFP.
IftheSFPLOSalarmisnotcleared,reusetheinitialSFP.GotoStep3.
IftheSFPLOSalarmiscleared,describethefaultontheBlueTagandsendittothe
RepairCentertogetherwiththefaultySFP.
180/219
14/08/2015
AlarmDescriptions
farendPIU.
FormoreinformationonhowtoreplacetheSFP,seeReplacinganSFP,Reference[18].
folder.
ThealarmisclearedwhenavalidsignalisdetectedintheSFP.
5.219SFPLOS(Critical)
SFPreportslossofsignal.
Applicablefor1+0configurationorfortheactiveinterfaceina1+1configuration.
SpecificProblem SFPLOS
Source
LINERS(1+0andactiveSI)
AlarmType
CommunicationAlarm
Severity
Critical
5.219.1Consequences
Lossofreceivedsignal:trafficislostonthePluginUnit(PIU)side.
181/219
14/08/2015
AlarmDescriptions
Figure39WorkflowforSFPLOSAlarmCorrectiveActions
Dothefollowing:
1. PerformalineloopontheinterfaceofthefarendPluginUnit(PIU).
IftheSFPLOSalarmisnotcleared,gotoStep2.
Onsiteaction:IftheSFPLOSalarmiscleared,replacethePIUonthefarend.Describe
2. Onsiteaction:ReplacetheSFP.
IftheSFPLOSalarmisnotcleared,reusetheinitialSFP.GotoStep3.
IftheSFPLOSalarmiscleared,describethefaultontheBlueTagandsendittothe
RepairCentertogetherwiththefaultySFP.
182/219
14/08/2015
AlarmDescriptions
farendPIU.
FormoreinformationonhowtoreplacetheSFP,seeReplacinganSFP,Reference[18].
folder.
ThealarmisclearedwhenavalidsignalisdetectedintheSFP.
5.220SFPTemperatureHigh/Low(Critical)
ThealarmisraisedifthemeasuredtemperatureintheSFPexceedstheupperexcessivethreshold
valueorfallsbelowthelowerexcessivethresholdvalue.
SpecificProblem SFPtemperaturehigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.220.1Consequences
TheSFPisnotoperatingcorrectly.
Makesurethattheenvironmentalconditionsareaccordingtorecommendations.ReplacetheSFP.
ThealarmisclearedwhenthemeasuredtemperatureintheSFPisbelowtheupperexcessive
thresholdvalueandabovethelowerexcessivethresholdvalue.
5.221SFPTemperatureHigh/Low(Warning)
ThealarmisraisedifthemeasuredtemperatureintheSFPexceedstheupperwarningthreshold
valueorfallsbelowthelowerwarningthresholdvalue.
SpecificProblem SFPtemperaturehigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Warning
5.221.1Consequences
183/219
14/08/2015
AlarmDescriptions
Makesurethattheenvironmentalconditionsareaccordingtorecommendations.ReplacetheSFP.
ThealarmisclearedwhenthemeasuredtemperatureintheSFPisbelowtheupperwarningthreshold
valueandabovethelowerwarningthresholdvalue.
5.222SFPVoltageHigh/Low(Critical)
ThealarmisraisedifthemeasuredsupplyvoltageintheSFPexceedstheupperexcessivethreshold
SpecificProblem SFPvoltagehigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.222.1Consequences
ReplacetheSFP.
Thealarmisclearedwhenthemeasuredsupplyvoltageisbelowtheupperexcessivethresholdvalue
andabovethelowerexcessivethresholdvalue.
5.223SFPVoltageHigh/Low(Warning)
ThealarmisraisedifthemeasuredsupplyvoltageintheSFPexceedstheupperwarningthreshold
valueorfallsbelowthelowerwarningthresholdvalue.
SpecificProblem SFPvoltagehigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Warning
5.223.1Consequences
ReplacetheSFP.
184/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhenthemeasuredsupplyvoltageisbelowtheupperwarningthresholdvalue
andabovethelowerwarningthresholdvalue.
5.224SFPTXBiasHigh/Low(Critical)
ThealarmisraisedifthemeasuredTXlaserbiascurrentexceedstheupperexcessivethresholdvalue
orfallsbelowthelowerexcessivethresholdvalue.
SpecificProblem SFPTXbiashigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.224.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredTXlaserbiascurrentisbelowtheupperexcessivethreshold
valueandabovethelowerexcessivethresholdvalue.
5.225SFPTXBiasHigh/Low(Warning)
ThealarmisraisedifthemeasuredTXlaserbiascurrentexceedstheupperwarningthresholdvalue
orfallsbelowthelowerwarningthresholdvalue.
SpecificProblem SFPTXbiashigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Warning
5.225.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredTXlaserbiascurrentisbelowtheupperwarningthreshold
185/219
14/08/2015
AlarmDescriptions
5.226SFPTXPowerHigh/Low(Critical)
ThealarmisraisedifthemeasuredcoupledSFPTXpowerexceedstheupperexcessivethreshold
SpecificProblem SFPTXpowerhigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.226.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredcoupledSFPTXpowerisbelowtheupperexcessive
5.227SFPTXPowerHigh/Low(Warning)
ThealarmisraisedifthemeasuredcoupledSFPTXpowerexceedstheupperwarningthresholdvalue
SpecificProblem SFPTXpowerhigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Warning
5.227.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredcoupledSFPTXpowerisbelowtheupperwarningthreshold
186/219
14/08/2015
AlarmDescriptions
5.228SFPRXPowerHigh/Low(Critical)
ThealarmisraisedifthemeasuredcoupledSFPRXpowerexceedstheupperexcessivethreshold
SpecificProblem SFPRXpowerhigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.228.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredcoupledSFPRXpowerisbelowtheupperexcessive
5.229SFPRXPowerHigh/Low(Warning)
ThealarmisraisedifthemeasuredcoupledSFPRXpowerexceedstheupperwarningthresholdvalue
SpecificProblem SFPRXpowerhigh/lowat<BoardType>
Source
SFP
AlarmType
EquipmentAlarm
Severity
Warning
5.229.1Consequences
ReplacetheSFP.
ThealarmisclearedwhenthemeasuredcoupledSFPRXpowerisbelowtheupperwarningthreshold
5.230SQM
SequenceIndicatorMismatch(SQM)
187/219
14/08/2015
AlarmDescriptions
Thereceivedsequencenumberdoesnotmatchtheconfiguredsequencenumber.Itcanbecausedby
SynchronousDigitalHierarchy(SDH)crossconnectionmisconfiguration.
SpecificProblem SQM
Source
VC12
VC3
VC4
AlarmType
CommunicationAlarm
Severity
Critical
5.230.1Consequences
Interfacedown.
1. ChecktheSDHcrossconnectionconfiguration.
2. Checkthelocalconfiguration.
Thealarmisclearedwhenthereceivedsequencenumbermatchestheconfiguredsequencenumber.
Communicationrecovers.
5.231SQMULTIPLE
Multiplesequencenumbersreceived.Therearetwoormoreequalsequencenumbersindifferent
VirtualContainers(VCs).
SpecificProblem SQMULTIPLE
Source
AlarmType
CommunicationAlarm
Severity
Major
188/219
14/08/2015
AlarmDescriptions
5.232SQNC
ThereceivedsequencenumbersforthisVirtualConcatenationGroup(VCG)arenotconsistent(outof
rangeornoncontinuous).
SpecificProblem SQNC
Source
AlarmType
CommunicationAlarm
Severity
Major
5.233SQNONCONT
Noncontinuoussequencenumbersreceived(perVirtualConcatenationGroup(VCG)).
SpecificProblem SQNONCONT
Source
AlarmType
CommunicationAlarm
Severity
Major
5.234SQOR
Sequencenumberoutofrangereceived(perVirtualConcatenationGroup(VCG)).
SpecificProblem SQOR
Source
AlarmType
CommunicationAlarm
Severity
Major
189/219
14/08/2015
AlarmDescriptions
5.235SquelchThresholdReached
ThequalitylevelofthesynchronizationreferencereachestheSquelchqualitylevel.
SpecificProblem Squelchthresholdreached
Source
NE
AlarmType
CommunicationAlarm
Severity
Critical
5.235.1Consequences
ThesynchronizationoutputsignalissquelchedortheappropriateSynchronizationStatusMessage
Noactionrequired.
ThealarmisclearedwhenthesynchronizationreferencereachesaqualitylevelabovetheSquelch
qualitylevel.
5.236StartingUp(FarEnd)
ThefarendInverseMultiplexeroverATM(IMA)unitisstartingup(restarting).
SpecificProblem Startingup(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Warning
5.236.1Consequences
NoATMtrafficcanbetransmittedoverthespecificIMAgroupbeforeboththenearendandfarend
groupsbecomeoperational.
ThefarendIMAgroupisrestarted.
WaituntiltheIMAgroupbecomesoperational.
190/219
14/08/2015
AlarmDescriptions
UsuallythisisatemporaryalarmwhichiscanceledassoonastheIMAgroupbecomesoperational
again,oritpresentsanotherspecificfailurecondition(forinstance"Insufficientlinks").
5.237SyncProblem
Thisalarmisraisedwhenoneofthreeothersynchronizationalarmsisraised.
Forseveritywarning,seeLossofnetworkreferenceredundancy(Section5.132).
Forseveritymajor,seeHoldovermodeentered(Section5.80).
Forseveritycritical,seeFreerunningmodeentered(Section5.63).
5.238TIM(Major)
TraceIdentifiedMismatch(TIM)
ThedetectionofTIMisbasedonacomparisonbetweentheacceptedTrailTraceIdentifier(TTI)and
theexpectedTTI,configuredthroughtheNetworkManagementSystem(NMS).IfTIMdetectionis
disabledattheNMS,TIMisconsidered"false".
SpecificProblem TIM
Source
AU4
RS
TU3
TU12
VC3
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Major
5.238.1Consequences
Traffictowardsthenodeislost.Trafficfromthenodeisnotaffected.
CheckconfigurationofTxTTIatsource.
CheckconfigurationofexpectedTTIatsink.
Checkcrossconnections.
5.239TIM(Critical)
TraceIdentifierMismatch(TIM)
ConfigurationmismatchbetweentheexpectedTrailTraceidentifier(TTI)andthereceivedTTI.
191/219
14/08/2015
AlarmDescriptions
SpecificProblem TIM
Source
MS/RS
VC12
VC4
AlarmType
CommunicationAlarm
Severity
Critical
5.239.1Consequences
Traffictowardsthenodecanbelost.Trafficfromthenodeisnotaffected.
CheckconfigurationofTTIinsourcesinkandcrossconnections.
ThealarmisclearedwhenthereceivedTTIisequaltotheexpectedTTI.
5.240TIMLineSide
TIMattheLineside.
SpecificProblem TIMLineSide
Source
LINERS
AlarmType
CommunicationAlarm
Severity
Major
5.241TIMRadioSide
TIMattheRadioside.
SpecificProblem TIMRadioSide
Source
RADIORS
AlarmType
CommunicationAlarm
Severity
Major
5.242TLCR
TotalLossofCapacityReceive(TLCR)
192/219
14/08/2015
AlarmDescriptions
LinkCapacityAdjustmentScheme(LCAS)deletesallmembers.
SpecificProblem TLCR
Source
AlarmType
CommunicationAlarm
Severity
Critical
5.242.1Consequences
Interfacedown.
1. RepairtheVirtualContainer(VC)trail.
2. ChecktheMultiplexSection(MS),RegeneratorSection(RS),andL1.
5.243TLCT
TotalLossofCapacityTransmit(TLCT)
ProbablecauseisLinkCapacityAdjustmentScheme(LCAS)deletesallmembers.
SpecificProblem TLCT
Source
AlarmType
CommunicationAlarm
Severity
Critical
5.243.1Consequences
Interfacedown.
1. RepairtheVirtualContainer(VC)trail.
2. ChecktheMultiplexSection(MS),RegeneratorSection(RS),andL1.
193/219
14/08/2015
AlarmDescriptions
5.244TrafficSystemFailure(Major)
SpecificProblem TrafficSystemFailure
Source
NE
AlarmType
EquipmentAlarm
Severity
Major
5.245TrafficSystemFailure(Critical)
SpecificProblem TrafficSystemFailure
Source
NE
AlarmType
EquipmentAlarm
Severity
Critical
5.246TULOM
TributaryUnitLossofMultiframe(TULOM)
SpecificProblem TULOM
Source
VC4
AlarmType
CommunicationAlarm
Severity
Critical
5.247TXFrequency(Major)
Thereceiverfrequencysynthesizerloopisunlocked.MainreasonforaTXFrequencyalarmisa
SpecificProblem TXFrequency
Source
RF
AlarmType
CommunicationAlarm
Severity
Major
5.247.1Consequences
Inhotstandbyconfiguration,theactivetransmitterisswitchedoffandthestandbytransmitteris
automaticallyswitchedon.
194/219
14/08/2015
AlarmDescriptions
Figure40WorkflowforTXFrequencyAlarmCorrectiveActions
Dothefollowing:
Caution!
Onsiteaction:IftheTXFrequencyalarmisnotclearedaftertherestart,replacethe
faultyRAU.
Onsiteaction:IftheTXFrequencyalarmiscleared,monitorthehopforfurtherTX
5.248TXFrequency(Critical)
Thereceiverfrequencysynthesizerloopisunlocked.MainreasonforaTXFrequencyalarmisa
195/219
14/08/2015
AlarmDescriptions
SpecificProblem TXFrequency
Source
RF
AlarmType
CommunicationAlarm
Severity
Critical
5.248.1Consequences
Thetransmitterisswitchedoffthatresultsintrafficloss.
Figure41WorkflowforTXFrequencyAlarmCorrectiveActions
Dothefollowing:
196/219
14/08/2015
AlarmDescriptions
Caution!
Onsiteaction:IftheTXFrequencyalarmisnotclearedaftertherestart,replacethe
faultyRAU.
Onsiteaction:IftheTXFrequencyalarmiscleared,monitorthehopforfurtherTX
5.249TxIFInput(Major)
FailureonthereceivedIntermediateFrequency(IF)signalfromtheMMUtotheRAU.
SpecificProblem TxIFInput
Source
RAUIF
AlarmType
Communication
Severity
Major
5.250TxIFInput(Critical)
FailureonthereceivedIntermediateFrequency(IF)signalfromtheMMUtotheRAU.
SpecificProblem TxIFInput
Source
RAUIF
AlarmType
Communication
Severity
Critical
5.251TxLinkMisconnected
TheTxlinkisnotconnectedtothesamefarendInverseMultiplexeroverATM(IMA)unitasthe
othersTxlinksinthegroup.
SpecificProblem TxLinkMisconnected
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Critical
197/219
14/08/2015
AlarmDescriptions
5.251.1Consequences
NoAsynchronousTransferMode(ATM)trafficcanbetransmittedoverthespecificIMALink.Related
IMAgroupscanalsobeaffectedbythefault:incasetheIMAgroupgoesbelowthe"minimumnumber
of(active)links"noATMtrafficcanflowatallthroughthegroup.Inthiscasetheoperationalstatus
ofrelatedATMIMA(IMAgroup)andATMgoestodown.IftheIMAgroupstillhaveaminimum
numberoflinksitcanstilltransmittheguaranteedbandwidthoftraffic.
WrongconnectionofTxIMAlink.
ConnecttheTxIMAlinktothesamefarendIMAunitastheotherTxlinksinthegroup.
ThealarmisclearedwhentheTxIMAlinkiscorrectlyconnectedtothefarendIMAunit.
5.252TXSwitchOver
Thisalarmisraisedwhenanactiveradioswitchoverisorderedbythenearendside.Itisonlyvalid
inHotStandby(HSB).
Bydefault,thefunctionalitytoorderanactiveradioswitchoveronthefarendsideisdisabled.Itcan
beenabledinMINILINKCraft,seeMINILINKCraftUserInterfaceDescriptions,Reference[7],butit
isonlyrecommendedtoenableitinhopsthathavehighfademarginsandlowprobabilityfordeep
flatormultipathfading.
SpecificProblem TXSwitchOver
Source
SWITCH
AlarmType
EquipmentAlarm
Severity
Major
5.252.1Consequences
Theprotectionswitchingfunctionislockeduntilthealarmisresetmanually.Eveniftheinitialfault
thattriggeredtheswitchoveriscorrected,theswitchingfunctiondoesnotworkandthehoponly
functionsas1+0untilthealarmisresetmanually.
TheTXswitchoveroccurswhentheoutputpoweroftheactiveradioislostinHSB.TheRFOutput
Levelalarmisraised.Theprotectionfunctionswitchesofftheoutputpoweronthisradioandswitches
ontheoutputpoweronthepassiveradio.TheRFOutputLevelalarmonthefaultyradioisthen
deactivated.
BecauseaTXswitchoverclearsanyalarmsraisedbytheinitialfault,theTXSwitchOveralarmmust
beraisedtopreventaswitchoverbacktothefaultypath.Forthisreason,theTXSwitchOveralarm
mustberesetmanuallyiffullequipmentprotectioninHSBiswanted.
198/219
14/08/2015
AlarmDescriptions
ReplacetheRAU,seeReplacingaRadioUnit,Reference[16].
Thealarmisnotclearedautomatically.ItmustberesetmanuallyinMINILINKCraftontheSWITCH
AlarmsandStatuspagefortheapplicableMMU.Thereasonforthisisthatthefaultthattriggeredthe
remoteTXswitchovermustbeunderstoodandcorrectedbeforearemoteTXswitchovercantake
placeagain.AlwaysresettheTXSwitchOveralarmbeforetakingahopintoserviceasinstallation
workandtestingcanalsotriggerthefunction.
5.253TxUnusable(FarEnd)
ThealarmisreportedwhenthefarendInverseMultiplexeroverATM(IMA)unitdeterminesthatits
Txlinkcannotbeusedfortransmissioninthegroup.
SpecificProblem TxUnusable(FarEnd)
Source
IMAGroup
AlarmType
CommunicationAlarm
Severity
Major
5.253.1Consequences
AfaultinthefarendlinkorprotocolisdetectedbytheIMAunitatTxdirection.
CheckthestatusofthefarendTxlink.
ThealarmisclearedwhenthefarendTxlinkfailureisremoved.
5.254UnabletoProtect:NPU
Thealarmisraisedwhenaprotectionswitchisperformedbecauseofoneofthefollowing:
BRbuttonispressedontheNPUinthesecondaryslot.
TheNPUinthesecondaryslotisremovedwithoutpressingtheBRbutton.
FailureoftheNPUinthesecondaryslot.
FormoreinformationabouttheprimaryandthesecondaryslotintheAMM,seeRecommendationsfor
PositioningofPlugInUnits,Reference[9].
199/219
14/08/2015
AlarmDescriptions
Source
NPU
AlarmType
EquipmentAlarm
Severity
Major
ProbableCause
ReplaceableUnitProblem
ReplaceableUnitMissing
5.254.1Consequences
TheEthernetswitchisnotprotected.IftheNPUintheprimaryslotthathastheactiveEthernetswitch
fails,trafficislost.
RepairorreplacethefaultyNPU.
ThisalarmisclearedwhentheNPUinthesecondaryslotisfunctioningcorrectly.
NotethattheNPUintheprimaryslotstillcanhavetheactiveEthernetswitchafterreplacementof
theotherNPU.Tohaveaprotectedsetupperformoneofthefollowing:
Iftherevertiveswitchismanual,settheactiveswitchtotheNPUinthesecondaryslot.
Iftherevertiveswitchisautomatic,waitfortheWaitToRestoreTime.
5.255UnabletoProtect:E1(Minor)
Source
E1
AlarmType
CommunicationAlarm
Severity
Minor
5.256UnabletoProtect:E1(Critical)
Theprotectionfails.Bothinterfacesfailorthetrafficislockedtoafailinginterface.
Source
E1
AlarmType
CommunicationAlarm
Severity
Critical
5.257UnabletoProtect:LPS(Major)
Thesystemisnolongerabletoprovideprotectionofthelineside.LossOfSignal(LOS)orLossOf
Frame(LOF)ononepath.
200/219
14/08/2015
AlarmDescriptions
Source
LPS
AlarmType
Communication
Severity
Major
5.258UnabletoProtect:LPS(Critical)
Thesystemisnolongerabletoprovideprotectionofthelineside.
Source
LPS
AlarmType
Communication
Severity
Critical
5.259UnabletoProtect:MSP(Minor)
Theprotectionfails.FailureononeofthetwolinesinvolvedinaMultiplexSectionProtection(MSP)
configuration.
Thelinehasafaultcondition(LossOfSignal(LOS)).
OneLTU155boardisfaulty(Equipmentfault).
OneLTU155boardisinrepair(notpresent).
MSPisconfiguredononlyoneofthetwoSynchronousTransportModulelevel1(STM1)boards.
Manualswitchmodeisconfigured(trafficislockedtooneofthetwolines).
Source
MSP
AlarmType
Severity
Minor
5.259.1Consequences
OnlyoneofthetwoSTM1linesintheMSPconfigurationisoperative.Failureofthislinealsoleadsto
completelossoftraffic.
Checktheabovementionedprobablecauses.
ThealarmisclearedwhentheSTM1linesareoperative.
201/219
14/08/2015
AlarmDescriptions
5.260UnabletoProtect:MSP(Critical)
Theprotectionfails.FailureonbothlinesinvolvedinaMultiplexSectionProtection(MSP)
configuration.
Bothlineshasafaultcondition(LossOfSignal(LOS)).
BothLTU155boardsarefaulty(Equipmentfault).
BothLTU155boardsareinrepair(notpresent).
Manualswitchmodeisconfigured(trafficislockedtooneofthetwolines)andthislineis
faulty.
Source
MSP
AlarmType
Severity
Critical
5.260.1Consequences
BothSynchronousTransportModulelevel1(STM1)linesintheMSPconfigurationarefaulty.The
resultiscompletelossoftraffic.
Checktheabovementionedprobablecauses.
ThealarmiscompletelyclearedwhenbothSTM1linesareoperative.Ifoneofthetwolinesbecomes
operative,thealarmchangesseverityfromCriticaltoMinor.
5.261UnabletoProtect:RLIME
ThealarmisraisedwhenanUnabletoProtectalarmisactiveonaradiolinkthatisassignedtothe
RLIMEgroup.
Source
RLIME
AlarmType
EquipmentAlarm
Severity
Warning
CheckandcleartheUnabletoProtectalarmsoftheradiolinksthatareassignedtotheRLIMEgroup.
202/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhennoUnabletoProtectalarmsareactiveontheradiolinksthatareassigned
totheRLIMEgroup.
5.262UnabletoProtect:SWITCH(Major)
Thesystemisnolongerabletoprovideprotectionoftheradioside.Probablecausesforthisareas
follows:
ATxalarmoracommonalarmononepath.
AnRxalarmononepathandthedurationislongerthan200s(defaultvalue).
Source
SWITCH
AlarmType
EquipmentAlarm
Severity
Major
5.263UnabletoProtect:SWITCH(Critical)
Thesystemisnolongerabletoprovideprotectionoftheradiosidebecausetherearealarmsonboth
paths.
Source
SWITCH
AlarmType
EquipmentAlarm
Severity
Critical
5.264UnabletoProtectFailureonActivePort:LAN
ThisalarmisonlyapplicableforETU2BandETU3.Thealarmisraisediftheactiveportinan
Ethernetportprotectiongroupdoesnotoperatewithfullfunctionality.
Thereasonsofthefailureontheactiveportcanbethefollowing:
TheoperationalstatusisDownfortheLANinterface.
TheoperationalstatusisOutofServicefortheactiveSFP.
TheoperationalstatusisOutofServicefortheactiveETU.
Note: OnlyapplicableifEthernetportprotectionisconfiguredondifferentETUs.
SpecificProblem UnabletoProtectFailureonActivePort
Source
LAN
AlarmType
EquipmentAlarm
Severity
Minor
203/219
14/08/2015
AlarmDescriptions
5.264.1Consequences
TheNEperformsaportprotectionswitch.OnlyoneofthetwoEthernetportsintheportprotection
groupisoperative.Failureofthisportleadstocompletelossoftraffic.
Tocorrectthefailureontheactiveport,dothefollowing:
1. CheckthattheadministrativestatusissettoUpfortheLANinterface.
2. CheckthattheLANconnectioniscorrectlyconfiguredwiththefarend.
3. CheckthattheadministrativestatusissettoInServicefortheSFPandtheETU.
4. CheckthattheSFPandtheETUarepluggedcorrectly.
5. ReplacethefaultySFP.Formoreinformation,seeReplacinganSFP,Reference[18].
6. ReplacethefaultyETU.Formoreinformation,seeReplacinganLTU,ETU,orSAU3,Reference
[12].
Danger!
laserequipment.
Forfaultsdetectedontheactiveport,aswitchisperformed,andtheformeractiveportbecomes
passive.Aftertheswitch,theNEmonitorsthestatusofthenewpassiveport.Thealarmisclearedif
thenewpassiveportisdetectedasfreeoffaults.
5.265UnabletoProtectFailureonBothPorts:LAN
ThisalarmisonlyapplicableforETU2BandETU3.Thealarmisraisedifboththeactiveportandthe
passiveportinanEthernetportprotectiongroupdonotoperatewithfullfunctionality.
Thereasonsofthefailurecanbethefollowing:
TheoperationalstatusisOutofServicefortheETUthathasboththeactiveandthepassive
port.
Note: IfEthernetportprotectionisconfiguredondifferentETUs,theoperationalstatuscan
beOutofServiceforboththeactiveandthepassiveETU.
TheoperationalstatusisOutofServicefortheactiveSFPandthepassiveSFP.
SpecificProblem UnabletoProtectFailureonBothPorts
Source
LAN
AlarmType
EquipmentAlarm
Severity
Critical
5.265.1Consequences
204/219
14/08/2015
AlarmDescriptions
BothEthernetportsintheportprotectiongrouparenotoperative.Thisleadstocompletelossof
traffic.
Tocorrectthefailureonbothports,dothefollowing:
1. CheckthattheadministrativestatusissettoUpfortheLANinterface.
2. CheckthattheLANconnectioniscorrectlyconfiguredwiththefarend.
[12].
Danger!
laserequipment.
Fortheactiveport,aswitchisperformed.Aftertheswitch,theNEmonitorsthestatusoftheactive
port.Iftheneededrecoverystepsaretakenontheactiveportwithin30minutes,thealarmis
cleared.Otherwise,after30minutes,anewswitchisperformed,andtheNEchecksthestatusofthe
portsagain.Ifoneofthetwoportsisdetectedasfreeoffaults,thealarmiscleared.
5.266UnabletoProtectFailureonPassivePort:LAN
ThisalarmisonlyapplicableforETU2BandETU3.Thealarmisraisedifthepassiveportinan
Ethernetportprotectiongroupdoesnotoperatewithfullfunctionality.
Thereasonsofthefailureonthepassiveportcanbethefollowing:
TheoperationalstatusisOutofServiceforthepassiveSFP.
TheoperationalstatusisOutofServiceforthepassiveETU.
Note: OnlyapplicableifEthernetportprotectionisconfiguredondifferentETUs.
SpecificProblem UnabletoProtectFailureonPassivePort
Source
LAN
AlarmType
EquipmentAlarm
Severity
Minor
5.266.1Consequences
Theactiveportisnotprotectedanymore.OnlyoneofthetwoEthernetportsintheportprotection
groupisoperative.Failureoftheactiveportleadstocompletelossoftraffic.
205/219
14/08/2015
AlarmDescriptions
Tocorrectthefailureonthepassiveport,dothefollowing:
[12].
Danger!
laserequipment.
Thealarmisclearedifthepassiveportisdetectedasfreeoffaults.
5.267UnabletoProtectManualMode:LAN
ThisalarmisonlyapplicableforETU2BandETU3.ThealarmisraisediftheEthernetportprotection
switchmodeissettomanual.
SpecificProblem UnabletoProtectManualMode
Source
LAN
AlarmType
EquipmentAlarm
Severity
Minor
5.267.1Consequences
Theactiveportisnotprotected.EveniftheNEdetectsaproblemontheactiveport,theNEdoesnot
performaswitchtothepassiveportautomatically.
SetEthernetportprotectionswitchmodetoautomatic.
ThealarmisclearediftheEthernetportprotectionswitchmodeissettoautomatic.
5.268UnabletoProtectPortNotConnectedtoSwitch:LAN
ThisalarmisonlyapplicableforETU2BandETU3.ThealarmisraisediftheEthernetportprotection
hasbeencreated,butithasnotbeenconnectedtoaswitchport.
SpecificProblem UnabletoProtectPortNotConnectedtoSwitch
Source
LAN
206/219
14/08/2015
AlarmDescriptions
AlarmType
EquipmentAlarm
Severity
Warning
5.268.1Consequences
TheconfigurationoftheEthernetportprotectionisnotcomplete.
ConnecttheprimaryLANinterface,whichistheactiveport,tooneoftheavailableswitchports.
ThealarmisclearediftheprimaryLANinterfaceisconnectedtoaswitchport.
5.269UnavailablePeriod
ThePlesiochronousDigitalHierarchy(PDH)UnavailablePeriodcounterthresholdiscrossed,dueto
possibleradiopropagationproblem.
SpecificProblem UnavailablePeriod
Source
RAUIF
SWITCH
AlarmType
Severity
Major
5.270UnavailableState
UnavailableStateisactivatedaftertenconsecutiveSeverelyErroredSeconds(SES).
SpecificProblem UnavailableState
Source
AU4
E1
E2/E3
FramedE1
MS/RS
MSP
TU3
TU12
VC3
207/219
14/08/2015
AlarmDescriptions
VC4
VC12
AlarmType
Severity
Critical
5.270.1Consequences
Serviceunavailable.
EliminatedefectsthatcauseSESorUnavailableSeconds(UAS).
ThealarmisclearedaftertenconsecutivenonSES.
5.271UnavailableStateFarEnd
Atthefarend,UnavailableStateisactivatedaftertenconsecutiveSeverelyErroredSeconds(SES).
SpecificProblem UnavailableStateFarEnd
Source
AU4
MS/RS
MSP
TU3
TU12
VC3
VC4
VC12
AlarmType
Severity
Critical
5.271.1Consequences
Serviceunavailableatfarend.
EliminatedefectsthatcauseSESorUnavailableSeconds(UAS).
5.272Unequipped(Major)
208/219
14/08/2015
AlarmDescriptions
Theinterfacehasnocontent,sincetheunitisnotconfigured.
SpecificProblem Unequipped
Source
AU4
TU3
TU12
VC3
VC4
VC12
AlarmType
CommunicationAlarm
Severity
Major
5.272.1Consequences
Checkcrossconnectionofthealarmedpath.
Thealarmisclearedwhenthecrossconnectionisestablished.
5.273Unequipped(Critical)
Nonconsistentconfiguration,theunequippeddefectisdetectedintheC2byte.
SpecificProblem Unequipped
Source
VC12
VC4
AlarmType
CommunicationAlarm
Severity
Critical
5.273.1Consequences
Checkandcorrectconfiguration.
209/219
14/08/2015
AlarmDescriptions
Thealarmisclearedwhentheconfigurationiscorrected.
5.274UnexpectedMDLevelinCCM
AMaintenanceEndPoint(MEP)hasreceivedaContinuityCheckMessage(CCM)framewithincorrect
MaintenanceDomain(MD)level.
Management(CFM).
SpecificProblem UnexpectedMDLevelinCCM
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Warning
5.275UnexpectedMEPCondition
MaintenanceDomain(MD)levelandcorrectMaintenanceAssociation(MA)ID,butwithunexpected
MEPID.
Management(CFM).
SpecificProblem UnexpectedMEPCondition
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Major
5.276UnexpectedPeriodinCCM
210/219
14/08/2015
AlarmDescriptions
MaintenanceDomain(MD)level,correctMaintenanceAssociation(MA)ID,andcorrectMEPID,but
withaperiodfieldvaluedifferentfromitsownCCMtransmissionperiod.
Management(CFM).
SpecificProblem UnexpectedPeriodinCCM
Source
LANwithMEP
WANwithMEP
LAGwithMEP
AlarmType
CommunicationAlarm
Severity
Warning
ProbableCause ResponseTimeExcessive
5.277UnitInaccessible:PluginUnit
Theunitisnotaccessible.
SpecificProblem UnitInaccessible
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Minor
5.278UnitInaccessible:RMM
TheRMMisnotaccessiblebecauseofafaultorbecausenoRMMispresent.
SpecificProblem UnitInaccessible
Source
RMM
AlarmType
EquipmentAlarm
Severity
Major
5.278.1Consequences
Enteringanunlockedperiod,duringwhichalllicensecontrolledfeaturesthatareconnectedtothe
licensesintheNEarepossibletouse.
CheckiftheRMMisinsertedcorrectlyorreplacetheRMM,seeReplacinganRMM,Reference[17].
211/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhenaccesstotheRMMisrestored.
5.279UnitRemoved(Minor)
EitherontheactivesideoronthepassivesideoftheEthernetportprotection,theSFPortheETUhas
beenremoved.
SpecificProblem UnitRemoved
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Minor
5.279.1Consequences
MissingSFPorETUfortheEthernetportprotectiongroup.
InsertthemissingSFPorETUtotheNE.
5.280UnitRemoved(Critical)
Theunitisremoved.
SpecificProblem UnitRemoved
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
5.281UnsupportedCapabilityProfile
ThealarmisraisediftheloadmoduleofETU2BorETU3doesnotsupporttheconfiguredcapability
profile.
SpecificProblem UnsupportedCapabilityProfile
Source
ETU2B
ETU3
AlarmType
EquipmentAlarm
Severity
Minor
ProbableCause SoftwareEnvironmentProblem
5.281.1Consequences
212/219
14/08/2015
AlarmDescriptions
TheNErunswithreducedcapabilities,thatis,theconfiguredcapabilityisdisabledonthepluginunit.
ChangethecapabilityprofiletoasupportedoneorupgradetheloadmoduleofETU2BorETU3.For
moreinformation,seeUpgradingorDowngradingaSWLoadModule,Reference[23].
FormoreinformationonfeatureandsoftwarecompatibilityregardingETUcapabilityprofiles,seethe
CompatibilitydocumentinthePlanningfolderoftheMINILINKTNCPIlibrary.
Thealarmisclearedwhenthecapabilityprofileischangedtoasupportedoneortheloadmoduleof
ETU2BorETU3isupgraded.
5.282UnsupportedUnitType
Thealarmisraisediftheunittypeisnotsupportedbythesoftware.
SpecificProblem UnsupportedUnitType(OnlyapplicableifsourceisPluginUnitorRAU)
UnsupportedUnitTypeat<BoardType>(OnlyapplicableifsourceisSFP)
Source
PluginUnit
RAU
SFP
AlarmType
EquipmentAlarm
Severity
Critical
5.282.1Consequences
Theunitisnotoperating.
Removeand,ifapplicable,replacetheunit.
Thealarmisclearedwhentheunsupportedunitisremoved.
5.283UPM
UserPayloadIdentifierMismatch(UPM)
TheUserPayloadIdentifier(UPI)fieldinthereceivedGenericFramingProcedure(GFP)framedoes
notmatchtheconfiguredvalue.
SpecificProblem UPM
Source
GFP
213/219
14/08/2015
AlarmDescriptions
AlarmType
CommunicationAlarm
Severity
Major
5.283.1Consequences
Theserviceisnottrustedandmaybeunavailable.
Correcttheuserpayloadinformationandcheckconfigurationinbothendsofthepath.
ThealarmisclearedwhentheUPIfieldinthereceivedGFPframematchestheconfiguredvalue.
5.284UserInput
TheSpecificProblemandSeverityaredefinedontheUserInputConfigurationpage,see
Reference[7].
SpecificProblem Userinput
Source
UserInput
AlarmType
EnvironmentalAlarm
Severity
UserDefined
ProbableCause
5.285WrongNPSoftware
TherunningNPUSWdoesnotsupporttheRMMduetoincompatibility.
SpecificProblem WrongNPSoftware
Source
RMM
AlarmType
EquipmentAlarm
Severity
Minor
ProbableCause ReplacableUnitProblem
5.285.1Consequences
TheRMMisnotaccessiblebytheSWduetoincompatibility.
PerformaSWupgradeontheNPU.
AlarmisautomaticallyclearedwhentheRMMiscompatiblewiththeNPUSW.
214/219
14/08/2015
AlarmDescriptions
5.286WrongNPUSoftware
Theunitneedsalater(updated)NPUsoftwarerelease.
SpecificProblem WrongNPUSoftware
Source
Pluginunit
AlarmType
EquipmentAlarm
Severity
Critical
5.287WrongPosition
TheunitisinthewrongpositionintheAMM.
SpecificProblem WrongPosition
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
5.288WrongSoftware:PluginUnit
ThesoftwarerevisionontheunitisnotalignedwiththeSoftwareBaseline(SBL).
SpecificProblem WrongSoftware
Source
PluginUnit
AlarmType
EquipmentAlarm
Severity
Critical
5.289WSTLOSL2R(Major)
TrafficfailureinthetransmittingdirectionoftheWaysideChannel(onlyforMMU2E/F).
SpecificProblem WSTLOSL2R
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.290WSTLOSL2R(Critical)
TrafficfailureinthetransmittingdirectionoftheWaysideChannel(onlyforMMU2E/F).
SpecificProblem WSTLOSL2R
Source
RAUIF(1+0)
215/219
14/08/2015
AlarmDescriptions
AlarmType
CommunicationAlarm
Severity
Critical
5.291WSTLOSR2L(Major)
TheWaysideChannelReceiverononeoftheMMU2E/Fina1+1protectionconfigurationdetectsloss
ofinputsignal.
SpecificProblem WSTLOSR2L
Source
RAUIF(1+1)
AlarmType
CommunicationAlarm
Severity
Major
5.291.1Consequences
ProtectionlostontheWaysideChannelonMMU2E/F.
ThealarmisclearedwhenaninputsignalisreceivedontheWaysideChannelonMMU2E/F.
5.292WSTLOSR2L(Critical)
TheWaysideChannelReceiverontheMMU2E/Fdetectslossofinputsignal.
SpecificProblem WSTLOSR2L
Source
RAUIF(1+0)
AlarmType
CommunicationAlarm
Severity
Critical
5.292.1Consequences
TrafficislostontheWaysideChannelonMMU2E/F.
ThealarmisclearedwhenaninputsignalisreceivedontheWaysideChannelonMMU2E/F.
5.293XPICCableDisconnected
LossoftheCrossPolarizationInterferenceCanceller(XPIC)basebandcrosssignaldueto
disconnectedorbrokenXPICcrosscablebetweentwoMMU2F/H/K,MMU3A/BmodemsinXPIC
mode.
SpecificProblem XPICCableDisconnected
Source
216/219
14/08/2015
AlarmDescriptions
MMU2F
MMU2H
MMU2K
MMU3A
MMU3B
AlarmType
EquipmentAlarm
Severity
Major
ProbableCause ReplaceableUnitMissing
5.293.1Consequences
Degradedreceivingthresholds,performance(BER)orlossoftraffic.
ConnecttheXPICcrosscableorreplacethefaultyone.
ThealarmisclearedwhenanonfaultyXPICcrosscableiscorrectlyconnectedbetweenthetwo
MMU2F/H/K,MMU3A/BmodemsinXPICmode.
5.294XPICLOS
ThealarmisraisedwhentheCrossPolarizationInterferenceCanceller(XPIC)basebandcrosssignal
betweentwoMMU2F/H/K,MMU3A/BmodemsinXPICmodeislost,withtheXPICcrosscable
correctlyconnected.LossoftheXPICbasebandcrosssignalduetoMMU2F/H/K,MMU3A/Binternal
hardwareorsoftwarefault.NotduetodisconnectedXPICcrosscable.
SpecificProblem XPICLOS
Source
MMU2F
MMU2H
MMU2K
MMU3A
MMU3B
AlarmType
CommunicationAlarm
Severity
Major
5.294.1Consequences
Degradedreceivingthresholds,performance(BER)orlossoftraffic.
217/219
14/08/2015
AlarmDescriptions
Figure42WorkflowforXPICLOSAlarmCorrectiveActions
Dothefollowing:
1. CheckifRxIFInputalarmorRCCalarmisalsoraised.
IfRxIFInputalarmorRCCalarmisraised,findtherootcausesofthesealarmsfirst,and
takecorrectiveactionsaccordingtotheiralarmdescription.
IfRxIFInputalarmorRCCalarmisnotraised,gotoStep2.
2. Onsiteaction:ReplaceoneoftheMMUsintheXPICpair.
IftheXPICLOSalarmisnotcleared,reusetheinitialMMUandgotoStep3.
IftheXPICLOSalarmiscleared,describethefaultontheBlueTagandsendittothe
RepairCentertogetherwiththefaultyMMU.
3. Onsiteaction:ReplacetheotherMMUintheXPICpair.DescribethefaultontheBlueTagand
218/219
14/08/2015
AlarmDescriptions
ThealarmisclearedwhentheXPICbasebandcrosssignalispresentagain.
ReferenceList
[1]AccessingaNetworkElement,3/1543HRA90120
[2]CLIUserGuide,2/1553HRA90120
[3]FaultManagementOperations,4/1543HRA90120
[4]InstallingandManagingLicenses,9/1543HRA90120
[5]InstallingOutdoorEquipment,1/1531HRA90103/1
[6]LEDDescriptions,24/1543HRA90120
[7]MINILINKCraftUserInterfaceDescriptions,7/1551HRA90120
[8]PersonalHealthandSafetyInformation,124462885
[9]RecommendationsforPositioningofPlugInUnits,15/1551HRA90120
[10]RemovingaPlugInUnit,20/1543HRA90120
[11]ReplacingaFanUnit,42/1543HRA90120
[12]ReplacinganLTU,ETU,orSAU3,39/1543HRA90120
[13]ReplacinganMMU,37/1543HRA90120
[14]ReplacinganMMU2CS,38/1543HRA90120
[15]ReplacinganNPU,35/1543HRA90120
[16]ReplacingaRadioUnit,41/1543HRA90120
[17]ReplacinganRMM,36/1543HRA90120
[18]ReplacinganSFP,55/1543HRA90120
[19]ReplacingaTRX,1/1543HRA90120
[20]SupplementarySafetyInformationforMINILINK,12446HSD10116/1
[21]SystemSafetyInformation,124462886
[22]Troubleshooting,5/15443HRA90120
[23]UpgradingorDowngradingaSWLoadModule,13/1543HRA90120
[24]VerifyinganInstallation,1/1532HRA90120
Copyright
EricssonAB20122014.Allrightsreserved.Nopartofthisdocumentmaybereproducedinanyform
withoutthewrittenpermissionofthecopyrightowner.
Disclaimer
Thecontentsofthisdocumentaresubjecttorevisionwithoutnoticeduetocontinuedprogressin
methodology,designandmanufacturing.Ericssonshallhavenoliabilityforanyerrorordamageofanykind
resultingfromtheuseofthisdocument.
AlarmDescriptionsMINILINKTNETSI
219/219

TN Alarm Description

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TN Alarm Description

Încărcat de

Drepturi de autor:

Formate disponibile

14/08/2015

S-ar putea să vă placă și