MPR 9500 Unspecified Alarm List

Alarm Reference > Alarm Reference
39 — Unspecified NE alarms
Note - This chapter lists alarms that have no NE type specified. The alarms listed in this chapter may apply to
one or more NE types, however, this information is not specified in the 5620 SAM alarm schema. Associating
alarms with specific NE types is an ongoing Alcatel-Lucent effort.
Table 39-1 AARadiusAcctPlcyFailure

Alarm Attributes Applicable major
releases
Name: AARadiusAcctPlcyFailure (3948) Severity: major Unspecified

Type: AARadiusAcctPlcyFailureAlarm Implicitly cleared: false
(120) Default probable cause:
Package: aapolicy aARadiusAcctPlcyFailure (1527)
Raised on class:
aapolicy.AARadiusAccountingPolicy
Description: The alarm is raised when a RADIUS accounting request was not successfully sent to any of the
RADIUS servers specified in the AA RADIUS accounting policy. The effect is accounting data for current
subscribers will not be exported externally. Based on the noted reason, if necessary take action to ensure that
the next RADIUS accounting will be successfully sent.
Remedial action: The AA RADIUS Accounting Server(s) which are configured in the AA RADIUS Accounting
Policy are unreachable. This may occur in a number of different scenarios. The server(s) may have become
unresponsive - please refer to the AA RADIUS Accounting Server documentation for assistance. The network
connectivity to the server(s) may have been lost - please investigate why the underlying transport network is
unreliable.
Table 39-2 AARadiusAcctServerStateChanged

releases
Name: Severity: info Unspecified

AARadiusAcctServerStateChanged Implicitly cleared: true
(3949)
Default probable cause:
Type: aARadiusAcctServerStateChanged (1528)
AARadiusAcctServerStateChangedAlarm
(121)
Package: aapolicy
Raised on class:
aapolicy.AARadiusAccountingServer
Description: The notification alarm is raised when the operational status of an AA RADIUS Accounting Policy
Server has transitioned from ’In Service’ to ’Out of Service’ or ’Unknown’ and cleared when operational status
transitioned to ’In Service’.
Raising condition: ((’Operational State’ EQUAL ’Out Of Service’) AND (’isLocal’ EQUAL ’true’))
Clearing condition: (’Operational State’ EQUAL ’In Service’)
Remedial action: Informational - This is a notification alarm to indicate that AA RADIUS Accounting Server
which is configured in the AA RADIUS Accounting Policy is changing operational state.
Table 39-3 AarpStateChanged

releases
Name: AarpStateChanged Severity: info Unspecified

(3705) Implicitly cleared: false
Type: AarpStateChanged Default probable cause: AarpStateChanged
(108) (1445)
Package: aapolicy
Raised on class: aapolicy.Aarp
Description: The alarm is raised when the 5620 SAM detects that an AARP state is changed.
Remedial action: The application assurance redundancy protocol state is changed between standalone,
remote, master or backup.
Table 39-4 AAUrlFilterStateChanged

releases
Name: AAUrlFilterStateChanged Severity: info Unspecified

(4972) Implicitly cleared: true
Type: processingErrorAlarm (81) Default probable cause:
Package: aapolicy aAUrlFilterStateChanged (2029)
Raised on class:
aapolicy.AAUrlFilter
Description: The notification alarm is raised when the operational status has transitioned from ’In Service’ to
’Out of Service’ and cleared when operational status transitioned from ’Out of Service’ to ’In Service’.
Raising condition: ((’Operational State’ EQUAL ’Down’) AND (’isLocal’ EQUAL ’true’))
Clearing condition: (’Operational State’ EQUAL ’Up’)
Remedial action: Informational - This is a notification alarm to indicate that AA URL Filter which is configured
in the AA URL Filter Policy is changing operational state.
Table 39-5 ABSAlarm

releases
Name: ABSAlarm (5187) Severity: major Unspecified

Type: equipmentAlarm (3) Implicitly cleared: true
Package: isa Default probable cause:
Raised on class: resourceLimitReached (131)
isa.MgGroupMember
Description: The ABSAlarm is raised when a set of the internal parameters for ICC call latency and memory
utilization reach the high threshold (activated) and cleared when it drop back and keep staying below the low
threshold for at least some time period (de-activated)
Remedial action: Diagnose why high memory utilization and/or control signaling overload happen.
Table 39-6 AddressAttachFailed (rtr)

releases
Name: AddressAttachFailed Severity: warning Unspecified

Type: processingErrorAlarm (81) Default probable cause: addressAttachFailed
Package: rtr (2530)
Raised on class:
rtr.NetworkInterface
Description: The alarm is raised when an IP address could not be attached to an interface.
Remedial action: An IP address could not be attached to an interface. A possible cause is that a duplicate
address is detected.
Table 39-7 AddressAttachFailed (service)
releases
Name: AddressAttachFailed (8134) Severity: warning Unspecified

Type: processingErrorAlarm (81) Implicitly cleared: false
Package: service Default probable cause:
Raised on class: addressAttachFailed (2530)
service.L3AccessInterface
Description: The alarm is raised when an IP address could not be attached to an interface.
Remedial action: An IP address could not be attached to an interface. A possible cause is that a duplicate
address is detected.
Table 39-8 AddressMisconfiguration

releases
Name: Severity: major Unspecified

AddressMisconfiguration Implicitly cleared: true
(591)
Type: configurationAlarm EpipeBackboneMacAddressMismatch (444)
(11) Applicable probable causes:
Package: service EpipeBackboneMacAddressMismatch
Raised on class: BVplsSourceMacAddressDuplicate
service.Service
Description: The alarm is raised when B-VPLS site addresses are misconfigured. The
EpipeBackboneMacAddressMismatch probable cause indicates that the backbone destination MAC address
does not match the backbone source MAC address of the site on the destination NE. The
BVplsSourceMacAddressDuplicate probable cause indicates that there are duplicate backbone source MAC
addresses.
Remedial action: Reconfigure the backbone MAC address so that the destination MAC address match the
destination site for an EPIPE, or the source MAC address is not duplicate to the other source MAC address for
a B-VPLS.
Table 39-9 AdvNotActivated

releases
Name: AdvNotActivated Severity: warning Unspecified

Type: configurationAlarm Default probable cause:
(11) advertisementNotActivated (517)
Package: vrrp
Raised on class:
vrrp.InstanceV6
Description: The alarm is raised when the parent interface of an IPv6 VR instance is not configured to send
router advertisements, or when router advertisement is not configured to use the virtual MAC address.
Remedial action: Activate the Advertisement for the interface for the VRRP so that it sends Advertisement
and Use Virtual MAC Address.
Table 39-10 Ais

Alarm Attributes Applicable major releases
Name: Ais (736) Severity: variable Unspecified

Type: communicationsAlarm (4) Implicitly cleared: true
Package: equipment Default probable cause: ais (513)
Raised on class: equipment.Port
Description: The alarm is raised when an NE reports an AIS condition on the Tx or Rx circuit of a PDH
tributary.
Remedial action: Please refer 9500 Node Maintenance manual for remedial action information.
Table 39-11 AisRx

Name: AisRx (1157) Severity: variable Unspecified

Package: equipment Default probable cause: aisRx (860)
Raised on class: equipment.Equipment
Description: The alarm is raised when there is a receiver alarm indication signal.
Table 39-12 AisTx

Name: AisTx (1158) Severity: variable Unspecified

Package: equipment Default probable cause: aisTx (861)
Description: The alarm is raised when there is a transmission alarm indication signal.
Table 39-13 AllBgpPeerConnectionsDown

releases

AllBgpPeerConnectionsDown Implicitly cleared: true
(5417)
Type: topologyAlarm (34) CPAAPeerConnectionDown (2124)
Package: topology
Raised on class: topology.Cpaa
Description: The alarm is raised when all CPAA’s BGP peers went down.
Remedial action: 1) All BGP peer connections are down for the active CPAA. Please check the connections.
2) If the standby CPAA is functional as per your requirements, switch-over might resolve the issue.
Table 39-14 AllTimingReferencesNotQualified

releases

AllTimingReferencesNotQualified Implicitly cleared: true
(549)
Type: communicationsAlarm (4) allTimingReferencesNotQualified (419)
Package: sonet
Raised on class: sonet.SiteSync
Description: The alarm is raised when no timing references on an NE are in the Qualified state.
Raising condition: ((’Qualified For Use’ NOT EQUAL ’Qualified’) AND (’Qualified For Use’ NOT EQUAL
’Qualified’) AND (’Qualified For Use’ NOT EQUAL ’Qualified’) AND (’Qualified For Use’ NOT EQUAL
’Qualified’))
Clearing condition: ((’Qualified For Use’ EQUAL ’Qualified’) OR (’Qualified For Use’ EQUAL ’Qualified’) OR
(’Qualified For Use’ EQUAL ’Qualified’) OR (’Qualified For Use’ EQUAL ’Qualified’))
Remedial action: Make sure that all the Timing References are qualified.
Table 39-15 apsCfgRaiseAlarm

releases
Name: apsCfgRaiseAlarm (772) Severity: major Unspecified

Type: configurationAlarm (11) Implicitly cleared: true
Package: ethernettunnel Default probable cause:
Raised on class: configurationMismatch (548)
ethernettunnel.EthernetTunnelEndpoint
Description: The alarm is raised when the 5620 SAM detects a mismatch between the working and protection
Ethernet tunnel group configurations.
Remedial action: Fix the mismatch between the working and protection Ethernet tunnel configurations.
Table 39-16 apsNoRspRaiseAlarm

releases
Name: apsNoRspRaiseAlarm (773) Severity: major Unspecified

Raised on class: incompleteProtectionSwitching (549)
Description: The alarm is raised when an Ethernet tunnel group protection switch is incomplete, as indicated
by a comparison of the transmitted ’Requested Signal’ values and the received ’Bridged Signal’ in the APS
protocol.
Remedial action: Fix the mismatch between the working and protection Ethernet tunnel configurations.
Table 39-17 apsPrvsnAlarm

releases
Name: apsPrvsnAlarm (1196) Severity: major Unspecified

Package: ethring Default probable cause: provisioningMismatch
Raised on class: (470)
ethring.Element
Description: The alarm is raised when a mismatch is detected on Ethernet Ring provisioning. The mismatch
occurs when the RPL Owner Node receives one or more No Request R-APS message(s) with an RPL blocked
status flag set (NR, RB) and a different Node ID.
Remedial action: Probably more than one Ring Protection Link owners configured in the Ring, make sure
which one should be RPL owner and delete others.
Table 39-18 apsPrvsnRaiseAlarm
releases
Name: apsPrvsnRaiseAlarm (774) Severity: major Unspecified

Raised on class: provisioningMismatch (470)
Description: The alarm is raised when an Ethernet tunnel group provisioning mismatch is detected at the ETH
layer. The mismatch is detected through a comparison of the transmitted and received APS protocol A, B and
D bits.
Remedial action: Check the configuration of the two ends of the tunnel are compatible/same for the protocol.
Table 39-19 AsymmetricalConfig (bundle)

releases
Name: AsymmetricalConfig (295) Severity: major Unspecified

Package: bundle Default probable cause:
Raised on class: asymmetricalConfig (226)
bundle.MultiChassisApsInterface
Description: The alarm is raised when the bundles in an APS group do not have matching configurations.
Raising condition: (’Asymmetrical Config Detected’ EQUAL ’true’)
Clearing condition: (’Asymmetrical Config Detected’ EQUAL ’false’)
Remedial action: Check configurations on both members to see anything not matched.
Table 39-20 AtcaAlarmCard_e1InfraAlarm

releases
Name: AtcaAlarmCard_e1InfraAlarm Severity: info Unspecified

Type: communicationsAlarm (4) Default probable cause:
Package: femto remoteAlarmInterface (615)
Raised on class:
femto.SCATCAAlarmCard
Description: This Alarm is raised when there is a failure and the infrastructure alarms :E1_A, E1_B, E1_C,
E1_D get raised.
Remedial action: TBD

releases

Raised on class:
Description: This Alarm is raised when there is a failure and the infrastructure alarms : E2_A, E2_B, E2_C,
E2_D get raised.

releases

Raised on class:
E3_D get raised.
Table 39-23 AtcaAlarmCard_e4InfraAlram

releases
Name: AtcaAlarmCard_e4InfraAlram Severity: info Unspecified

Raised on class:
E4_D get raised.
Table 39-24 AtcaAlarmCard_pdu

releases
Name: AtcaAlarmCard_pdu (5708) Severity: info Unspecified

Package: femto Default probable cause:
Raised on class: equipmentMalfunction (698)
Description: This Alarm is raised when there is failure in the PDU presence.
Table 39-25 AtcaAlarmCard_pduBreakerPwr

releases
Name: AtcaAlarmCard_pduBreakerPwr Severity: major Unspecified

(5709)
Implicitly cleared: true
Type: environmentalAlarm (2)
Default probable cause: powerProblem
Package: femto (911)
Raised on class:
Description: This Alarm is raised when there is failure in AT1 PDU Breaker A, AT1 PDU Breaker B.
Table 39-26 AtcaAlarmCard_pduFeedPwr

releases
Name: AtcaAlarmCard_pduFeedPwr Severity: critical Unspecified

Type: environmentalAlarm (2) Default probable cause: powerProblem
Raised on class:
Description: This Alarm is raised when there is failure in the AT1 PDU Feed A, AT1 PDU Feed B.
Table 39-27 AtcaAlarmCard_powerFailure

releases
Name: AtcaAlarmCard_powerFailure Severity: info Unspecified

Type: environmentalAlarm (2) Default probable cause: powerProblem
Raised on class:
Description: This Alarm is raised when the Loop Voltage failure, VoltageFailure48V_A and
VoltageFailure48V_B. happens
Table 39-28 AtcaAlarmCard_telcoAlarmInput

releases

AtcaAlarmCard_telcoAlarmInput Implicitly cleared: true
(5712)
Type: equipmentAlarm (3) equipmentMalfunction (698)
Package: femto
Raised on class:
Description: This Alarm is raised when the System manager does the minor Reset, major Reset and Alarm
cutoff.
Table 39-29 AtcaFanTray_fanAgingDown1

releases

AtcaFanTray_fanAgingDown1 Implicitly cleared: true
(5713)
Type: equipmentAlarm (3) replaceableUnitProblem (643)
Package: femto
Raised on class:
femto.SCATCAFanTray
Description: This Alarm is raised when the Down fan tray reaches the Aging1

releases

(5714)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5715)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5716)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5717)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5718)
Package: femto
Raised on class:
femto.SCATCAFanTray
Table 39-35 AtcaFanTray_fanAgingRear1

releases

AtcaFanTray_fanAgingRear1 Implicitly cleared: true
(5719)
Package: femto
Raised on class:
femto.SCATCAFanTray
Description: This Alarm is raised when the Rear fan tray reaches the Aging1

releases

(5720)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5721)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5722)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases

(5723)
Package: femto
Raised on class:
femto.SCATCAFanTray

releases
(5724)
Package: femto
Raised on class:
femto.SCATCAFanTray
Table 39-41 AtcaFanTray_fanAgingUp1

releases
Name: AtcaFanTray_fanAgingUp1 Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause:
Package: femto replaceableUnitProblem (643)
Raised on class:
femto.SCATCAFanTray
Description: This Alarm is raised when the Upper fan tray reaches the Aging1

releases

Raised on class:
femto.SCATCAFanTray

releases

Raised on class:
femto.SCATCAFanTray

releases

Raised on class:
femto.SCATCAFanTray

releases

Raised on class:
femto.SCATCAFanTray

releases

Raised on class:
femto.SCATCAFanTray
Table 39-47 AtcaShelf_alarmCardAbsence

releases

AtcaShelf_alarmCardAbsence Implicitly cleared: true
(5755)
Type: equipmentAlarm (3) probCauseUnknown (2442)
Package: femto
Raised on class:
femto.SCATCAShelf
Description: This Alarm is raised when there is failure in the Alarm card presence.

Table 39-48 AtcaShelfManager_boardFilterAbsence
releases
Name: Severity: minor Unspecified

AtcaShelfManager_boardFilterAbsence Implicitly cleared: true
(5731)
Package: femto
Raised on class:
femto.SCATCAShelfManager
Description: This Alarm is raised when the Board filter or the Front side filter or grid is not present.
Table 39-49 AtcaShelfManager_cpldSensor

releases

AtcaShelfManager_cpldSensor Implicitly cleared: true
(5732)
Package: femto
Raised on class:
Description: This Alarm is raised when there is change in the shelf manager redundancy status.
Table 39-50 AtcaShelfManager_fanTrayLowAbsence

releases

AtcaShelfManager_fanTrayLowAbsence Implicitly cleared: true
(5733)
Package: femto
Raised on class:
Description: This Alarm is raised when the Lower fan tray is not present.
Table 39-51 AtcaShelfManager_fanTrayRearAbsence

releases

AtcaShelfManager_fanTrayRearAbsence Implicitly cleared: true
(5734)
Package: femto
Raised on class:
Description: This Alarm is raised when the Rear fan tray is not present.
Table 39-52 AtcaShelfManager_fanTraysFRUcriticalFailure

releases
Name: Severity: critical Unspecified

AtcaShelfManager_fanTraysFRUcriticalFailure Implicitly cleared: true
(5736)
Package: femto
Raised on class: femto.SCATCAShelfManager
Description: This Alarm is raised when failure occurs in the Fan Trays FRUs.
Table 39-53 AtcaShelfManager_fanTrayUpAbsence

releases

AtcaShelfManager_fanTrayUpAbsence Implicitly cleared: true
(5735)
Package: femto
Raised on class:
Description: This Alarm is raised when the Up fan tray is not present.
Table 39-54 AtcaShelfManager_i2cLocalBus

releases

AtcaShelfManager_i2cLocalBus Implicitly cleared: true
(5737)
Package: femto
Raised on class:
Description: This Alarm is raised when failure happens to the I2C Local Bus.
Table 39-55 AtcaShelfManager_i2cMasterResourceHighLimit

releases

AtcaShelfManager_i2cMasterResourceHighLimit Implicitly cleared: true
(5738)
Package: femto
Description: This Alarm is raised when the I2C Master Resource reaches the critical limit.
Table 39-56 AtcaShelfManager_i2cMasterResourceMidLimit

releases

AtcaShelfManager_i2cMasterResourceMidLimit Implicitly cleared: true
(5739)
Package: femto
Description: This Alarm is raised when the I2C of the Master Resource reaches the major limit
Table 39-57 AtcaShelfManager_ipmbLinkDown

releases

AtcaShelfManager_ipmbLinkDown Implicitly cleared: true
(5740)
Package: femto
Raised on class:
Description: This Alarm is raised when failure happens to the IPMB-0 link
Table 39-58 AtcaShelfManager_lm75TempDownHighLimit

releases

AtcaShelfManager_lm75TempDownHighLimit Implicitly cleared: true
(5741)
Type: environmentalAlarm (2) lowTemperature (674)
Package: femto
Description: This Alarm is raised when the temperature of the bottom of the NBSHMC board reaches the
lower critical limit.
Table 39-59 AtcaShelfManager_lm75TempDownMidLimit

releases

AtcaShelfManager_lm75TempDownMidLimit Implicitly cleared: true
(5742)
Type: environmentalAlarm (2) Default probable cause:
Package: femto lowTemperatureMidLimit (2443)
Raised on class:
Description: This Alarm is raised when the temperature of the bottom of the NBSHMC board reaches the
lower major limit.
Table 39-60 AtcaShelfManager_lm75TempUpHighLimit

releases

AtcaShelfManager_lm75TempUpHighLimit Implicitly cleared: true
(5743)
Type: environmentalAlarm (2) highTemperature (667)
Package: femto
Raised on class:
Description: This Alarm is raised when the temperature of the top of the NBSHMC board reaches the upper
critical limit.
Table 39-61 AtcaShelfManager_lm75TempUpMidLimit

releases

AtcaShelfManager_lm75TempUpMidLimit Implicitly cleared: true
(5744)
Type: environmentalAlarm (2) highTemperature (667)
Package: femto
Raised on class:
Description: This Alarm is raised when the temperature of the top of the NBSHMC board reaches the upper
major limit.
Table 39-62 AtcaShelfManager_pwrRedDegraded

releases

AtcaShelfManager_pwrRedDegraded Implicitly cleared: true
(5745)
Package: femto
Raised on class:
Description: Power supple redundancy degraded assert. Redundancy still exists, but at a less than full level.
For example, a system has four fans, and can tolerate the failure of two of them, and presently one has failed

Table 39-63 AtcaShelfManager_pwrRedLost
releases

AtcaShelfManager_pwrRedLost Implicitly cleared: true
(5746)
Package: femto
Raised on class:
Description: This Alarm is raised when the Power supply redundancy lost or Entered any non-redundant
state, including Non-redundant: Insufficient Resources
Table 39-64 AtcaShelfManager_pwrRedRegained

releases

AtcaShelfManager_pwrRedRegained Implicitly cleared: true
(5747)
Package: femto
Raised on class:
Description: This Alarm is raised when the full power supply redundancy has been regained
Table 39-65 AtcaShelfManager_rebootReason

releases

AtcaShelfManager_rebootReason Implicitly cleared: false
(5748)
Package: femto
Raised on class:
Description: This Alarm is raised when the Shelf Manager has been Rebooted
Table 39-66 AtcaShelfManager_rtmFilterAbsence

releases

AtcaShelfManager_rtmFilterAbsence Implicitly cleared: true
(5749)
Package: femto
Raised on class:
Description: This Alarm is raised when the RTM filter or the Back side filter or grid is not present.
Table 39-67 AtcaShelfManager_shelfFRUcriticalFailure

releases

AtcaShelfManager_shelfFRUcriticalFailure Implicitly cleared: true
(5750)
Package: femto
Raised on class:
Description: This Alarm is raised when critical failure happens to the Shelf FRUs in EEPROMs.
Table 39-68 AtcaShelfManager_shelfFRUminorFailure

releases

AtcaShelfManager_shelfFRUminorFailure Implicitly cleared: true
(5751)
Package: femto
Raised on class:
Description: This Alarm is raised when minor failure happens to the Shelf FRUs in EEPROMs.
Table 39-69 AtcaShelfManager_shelfManagerConnectionFailure

releases

AtcaShelfManager_shelfManagerConnectionFailure Implicitly cleared: true
(5752)
Type: communicationsAlarm (4) unspecifiedReason (802)
Package: femto
Description: This Alarm is raised when the Shelf Oam is unable to communicate with shelf manager
Table 39-70 AtcaShelfManager_shelfManagerInNonRedundantState

Alarm Attributes Applicable
major releases

AtcaShelfManager_shelfManagerInNonRedundantState Implicitly cleared: true
(5753)
Package: femto
Description: This Alarm is raised when the Peer Shelf Manager is not available
Table 39-71 AtcaShelfManager_shelfManagerUnAvailable

releases

AtcaShelfManager_shelfManagerUnAvailable Implicitly cleared: true
(5754)
Package: femto
Raised on class:
Description: This Alarm is raised when the Shelf Manager Card is not available
Table 39-72 AtcaSwitchBaseEthernetIntf_malbanBaseEthernetPortFailure

major
releases

AtcaSwitchBaseEthernetIntf_malbanBaseEthernetPortFailure Implicitly cleared: false
(5756)
Package: femto
Raised on class: femto.SCATCASwitchBaseEthernetIntf
Description: This Alarm is raised when the Malban Card Base Ethernet port has failed
Table 39-73 AtcaSwitchCPU_malban10CPUFailure

releases

AtcaSwitchCPU_malban10CPUFailure Implicitly cleared: false
(5757)
Type: equipmentAlarm (3) processorProblem (633)
Package: femto
Raised on class:
femto.SCATCASwitchCPU
Description: This Alarm is raised when software critical error occurs on the payload. Usually followed by a
board reboot or reset. It is asserted upon fault detection by the payload software and de-asserted on startup.
Table 39-74 AtcaSwitchFabricEthernetIntf_malbanFabricEthernetPortFailure

major
releases

AtcaSwitchFabricEthernetIntf_malbanFabricEthernetPortFailure Implicitly cleared: false
(5758)
Type: equipmentAlarm (3) equipmentMalfunction
Raised on class: femto.SCATCASwitchFabricEthernetIntf
Description: This Alarm is raised when the Malban Card Fabric Ethernet port has failed
Table 39-75 AtcaSwitchSlot_malbanConnectionFailure

releases

AtcaSwitchSlot_malbanConnectionFailure Implicitly cleared: true
(5759)
Package: femto
Raised on class: femto.SCATCASwitchSlot
Description: This Alarm is raised when the Shelf Oam is unable to communicate with Malban
Table 39-76 AtcaSwitchSlot_malbanInNonRedundantState

releases

AtcaSwitchSlot_malbanInNonRedundantState Implicitly cleared: true
(5760)
Package: femto
Description: This Alarm is raised when the Peer Malban is not available
Table 39-77 AtcaSwitchSlot_malbanIpmbLinkDown

releases

AtcaSwitchSlot_malbanIpmbLinkDown Implicitly cleared: true
(5761)
Package: femto
Raised on class:
femto.SCATCASwitchSlot
Description: This Alarm is raised when failure happens to the IPMB-0 link

Table 39-78 AtcaSwitchSlot_malbanUnAvailable
releases

AtcaSwitchSlot_malbanUnAvailable Implicitly cleared: true
(5762)
Package: femto
Raised on class:
Description: This Alarm is raised when the Malban Card is not available
Table 39-79 AtcaSwitchSlot_malbanVlanCreationFailure

releases

AtcaSwitchSlot_malbanVlanCreationFailure Implicitly cleared: true
(5763)
Package: femto
Description: This Alarm is raised when the vlan creation failed in Malban
Table 39-80 AtcaSwitchSlot_ncpuFatalError

releases

AtcaSwitchSlot_ncpuFatalError Implicitly cleared: false
(5764)
Package: femto
Raised on class:
Description: This Alarm is raised when a software critical error occurs on the payload.
Table 39-81 ATPCHighPowerTimeout

releases
Name: ATPCHighPowerTimeout Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: ATPCLoopProblem
Package: mwa (1903)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects a ATPC High Power Timeout
Remedial action: Please refer to either 9500 or 7705 Node Maintenance manual for remedial action
information.
Table 39-82 AtpcLoopProblem

releases
Name: AtpcLoopProblem (1142) Severity: variable Unspecified

Package: radioequipment Default probable cause:
Raised on class: atpcLoopProblem (848)
radioequipment.RadioPortSpecifics
Description: The alarm is raised when a local transmitter was operating continuously at full power for 5-
minutes, and the transmitter power is reduced to its minimum power setting.
Table 39-83 ATPCTimeout

releases
Name: ATPCTimeout (3939) Severity: variable Unspecified

Package: radioequipment Default probable cause: atpcTimeout
Description: The alarm is raised when a the ATPC timeout defect raise.
Remedial action: The alarm is raised when a the ATPC timeout defect raise.
Table 39-84 AuthFailure

releases
Name: AuthFailure (281) Severity: major Unspecified

Type: authenticationAlarm (14) Implicitly cleared: false
Package: vrrp Default probable cause: authFailure
vrrp.AbstractInstance
Description: The alarm is raised when authentication fails. The alarm information includes the source IP
address.
Remedial action: Reconfigure the authentication key so that the keys are the same for the peer VRRP
instances.
Table 39-85 AuthKeyConflict (ldp)

releases
Name: AuthKeyConflict (5188) Severity: warning Unspecified

Type: processingErrorAlarm Implicitly cleared: true
(81) Default probable cause: AuthKeyConflict
Package: ldp (2103)
Raised on class: ldp.Peer
Description: The alarm is raised when both Authentication Key and LDP Peer Keychain are configured. LDP
Peer Keychain will be used.
Remedial action: Authentication Key and LDP Peer Keychain are both configured. LDP Peer Keychain will be
used. The alarm is cleared when only one is configured.
Table 39-86 AuxiliaryAlarm

releases
Name: AuxiliaryAlarm (1159) Severity: variable Unspecified

Type: dryContactAlarm (47) Implicitly cleared: false
Package: equipment Default probable cause:
Raised on class: auxliaryAlarmTriggered (862)
equipment.AuxAlarmDefinition
Description: The alarm is raised when an NE reports that a configured auxiliary alarm condition has been
triggered.
Remedial action: Informational - no corrective action required.
Table 39-87 AuxiliaryDatabaseProxyStateChangeDetected

releases
Name: Severity: warning Unspecified

AuxiliaryDatabaseProxyStateChangeDetected Implicitly cleared: false
(5170)
Type: databaseAlarm (29) systemFailed (144)
Package: db
Raised on class: db.AuxiliaryDatabase
Description: This informative alarm is raised when the state of the auxiliary database proxy has changed at
least once since the last check interval.
Remedial action: Informational - no corrective action required. The state (up/down) of the auxiliary database
proxy has changed at least once since the last check interval. The alarm must be manually cleared.
Table 39-88 AuxiliaryDatabaseProxyUnreachable

releases

AuxiliaryDatabaseProxyUnreachable Implicitly cleared: true
(5171)
Type: communicationsAlarm (4) systemFailed (144)
Package: db
Description: This informative alarm is raised when a 5620 SAM server cannot communicate with an auxiliary
database proxy. The alarm clears when communication is restored.
Raising condition: (’Database Proxy Status’ EQUAL ’Down’)
Clearing condition: (’Database Proxy Status’ EQUAL ’Up’)
Remedial action: The 5620 SAM server cannot communicate with an auxiliary database proxy. Check the
status of the auxiliary database proxy and the communication link between SAM server and auxiliary database
node.
Table 39-89 AuxiliaryDatabaseStateChangeDetected

releases

AuxiliaryDatabaseStateChangeDetected Implicitly cleared: false
(5172)
Type: databaseAlarm (29) systemFailed (144)
Package: db
Description: This informative alarm is raised when the state of the auxiliary database has changed at least
once since the last check interval.
Remedial action: Informational - no corrective action required. The state (up/down) of the auxiliary database
has changed at least once since the last check interval. The alarm must be manually cleared.
Table 39-90 AuxiliaryDatabaseStatus

releases
Name: AuxiliaryDatabaseStatus Severity: critical Unspecified

Type: communicationsAlarm (4) Default probable cause: systemFailed
Package: db (144)
Raised on class:
db.AuxiliaryDatabase
Description: This informative alarm is raised when a 5620 SAM server cannot communicate with an auxiliary
database server. The alarm clears when communication is restored.
Raising condition: (’Database Status’ EQUAL ’Down’)
Clearing condition: (’Database Status’ EQUAL ’Up’)
Remedial action: The 5620 SAM server cannot communicate with an auxiliary database. Check the status of
the auxiliary database and the communication link between SAM server and auxiliary database node.
Table 39-91 BackgroundDiagnosticFault

releases
Name: BackgroundDiagnosticFault Severity: minor Unspecified

Package: equipment backgroundDiagnosticFault (353)
Raised on class:
equipment.ReplaceableUnit
Description: The alarm is raised when an NE detects a failure in a background diagnostic test suite.
Remedial action: Informational - if the condition persists then the element indicated in the alarm should be
replaced.
Table 39-92 backupScriptInUse

releases
Name: backupScriptInUse (274) Severity: major Unspecified

Package: subscrident Default probable cause: backupInUse
subscrident.Policy
Description: The alarm is raised when the primary subscriber identification script is operationally down, but
one of the other scripts is operationally up.
Raising condition: ((’isLocal’ EQUAL ’true’) AND (’Primary Script Operational State’ NOT EQUAL ’Up’) AND
((’Secondary Script Operational State’ EQUAL ’Up’) OR (’Tertiary Script Operational State’ EQUAL ’Up’)))
Clearing condition: ((’isLocal’ EQUAL ’true’) AND ((’Primary Script Operational State’ EQUAL ’Up’) OR
((’Secondary Script Operational State’ NOT EQUAL ’Up’) AND (’Tertiary Script Operational State’ NOT EQUAL
’Up’))))
Remedial action: If the DHCP ACK Python script processing behaviour is desired, please make sure that
primary, secondary and tertiary scripts are installed and operationally up.
Table 39-93 BandwidthOverFlow

releases
Name: BandwidthOverFlow (1143) Severity: variable Unspecified

Raised on class: bandwidthOverFlow (849)
Description: The alarm is raised when a MPT is on-line and the cross-connections occupation overcomes the
MPT net capacity bandwidth.
Table 39-94 BatteryFail (equipment)

releases
Name: BatteryFail (616) Severity: variable Unspecified

Package: equipment Default probable cause: batteryFail
equipment.Equipment
Description: The alarm is raised when the battery fails or is missing.
Remedial action: The battery on the CPM should be replaced or re-installed.
Table 39-95 BatteryFail (mpr)

releases
Name: BatteryFail (616) Severity: variable Unspecified

Package: mpr Default probable cause: batteryFail
mpr.SubRackElements
Description: The alarm is raised when the battery fails or is missing.
Remedial action: The battery on the subrack element should be replaced or re-installed.
Table 39-96 BfdSessionDown (rtr)

releases
Name: BfdSessionDown (439) Severity: warning Unspecified

Type: bfdSessionAlarm (46) Implicitly cleared: true
Package: rtr Default probable cause: bfdSessionDown
Description: The alarm is raised when a BFD session is operationally down.
Remedial action: This alarm is raised when a BFD session on a network interface goes down. The situation
may occur if the underlying physical interface is down either because of administrative disabling or a fault on
the far end port or due to a cable connection or cable failure. This alarm will also be raised if the underlying
transport network fails or is unreliable. Resolving the underlying instability in the transport network will correct
this problem.
Table 39-97 BfdSessionDown (service)

releases

Package: service Default probable cause: bfdSessionDown
Remedial action: This alarm is raised when a BFD session on a L3 access interface goes down. The situation
this problem.
Table 39-98 BfdSessionDown (vprn)

releases

Package: vprn Default probable cause: bfdSessionDown
vprn.NetworkInterface
Description: The alarm is raised when a BFD session is operationally Down.
Remedial action: This alarm is raised when a BFD session on a VPRN network interface goes down. The
situation may occur if the underlying physical interface is down either because of administrative disabling or a
fault on the far end port or due to a cable connection or cable failure. This alarm will also be raised if the
underlying transport network fails or is unreliable. Resolving the underlying instability in the transport network
will correct this problem.
Table 39-99 BfdSessionFlapped (rtr)

releases
Name: BfdSessionFlapped Severity: warning Unspecified

Type: bfdSessionAlarm (46) Default probable cause: bfdSessionFlapped
Package: rtr (1491)
Raised on class:
Description: The alarm is raised when a BFD session transitions from Up to Down and back to Up within the
BFD operational state transition interval.
Remedial action: The BFD session on a network interface has transitioned from Up to Down and back to Up
within the configured BFD Flapping Interval.
Table 39-100 BfdSessionFlapped (service)

releases
Name: BfdSessionFlapped (3900) Severity: warning Unspecified

Raised on class: bfdSessionFlapped (1491)
Remedial action: The BFD session on a L3 access interface has transitioned from Up to Down and back to
Up within the configured BFD Flapping Interval.
Table 39-101 BfdSessionFlapped (vprn)

releases
Name: BfdSessionFlapped (3900) Severity: warning Unspecified

Package: vprn Default probable cause: bfdSessionFlapped
Remedial action: The BFD session on a VPRN network interface has transitioned from Up to Down and back
to Up within the configured BFD Flapping Interval.
Table 39-102 BfdSessionMissing (rtr)

releases
Name: BfdSessionMissing (438) Severity: warning Unspecified

Package: rtr Default probable cause: bfdSessionMissing
Description: The alarm is raised when a previously present BFD session is absent.
Remedial action: This alarm is raised when a previously present BFD session on a network interface is
absent. The situation may occur if the underlying physical interface is down either because of administrative
disabling or a fault on the near end port or due to a cable connection or cable failure. This alarm will also be
raised if the underlying transport network fails or is unreliable. Resolving the underlying instability in the
transport network will correct this problem.
Table 39-103 BfdSessionMissing (service)

releases

Raised on class: bfdSessionMissing (345)
Remedial action: This alarm is raised when a previously present BFD session on a L3 access interface is
Table 39-104 BfdSessionMissing (vprn)

releases

Package: vprn Default probable cause: bfdSessionMissing
Remedial action: This alarm is raised when a previously present BFD session on a VPRN network interface is
Table 39-105 BgpAdVplsIdDiscoveryError

releases

BgpAdVplsIdDiscoveryError (572) Implicitly cleared: true
Type: serviceAlarm (16) Default probable cause:
Package: vpls bgpAdVplsIdInconsistent (439)
Raised on class: vpls.AbstractSite
Description: The alarm is raised when the VPLS ID of a discovered VPLS instance is ambiguous.
Remedial action: Check that all VPLS IDs are properly configured for all VPLS instances.
Table 39-106 BgpAdVplsIdMisconfiguration

releases

BgpAdVplsIdMisconfiguration Implicitly cleared: true
(570)
Type: configurationAlarm (11) bgpAdVplsIdInconsistent (439)
Package: vpls
Raised on class: vpls.AbstractVpls
Description: The alarm is raised when the VPLS ID of a site does not match the VPLS ID of the other sites in
the service.
Remedial action: All VPLS IDs of sites in a service must be the same.
Table 39-107 BgpAsPathLenPerMonPrefThresholdReached

releases

BgpAsPathLenPerMonPrefThresholdReached Implicitly cleared: true
(795)
Type: topologyAlarm (34) asPathTooLong (562)
Package: topology
Description: The alarm is raised when the AS path length for a monitored BGP route reaches or exceeds the
maximum threshold value.
Remedial action: User configured alarm for monitoring purpose. Alarm text provides information about the
affected prefix. User can look at the records for BGP prefix monitoring or BGP events history for debugging
purpose.
Table 39-108 BgpEventUnreachable

releases
Name: BgpEventUnreachable Severity: major Unspecified

Type: topologyAlarm (34) Default probable cause: prefixUnreachable
Package: topology (827)
Description: The alarm is raised when Unreachable BGP Event is detected.
Remedial action: Alarm text provides information about the affected prefix. User can look at the BGP events
history for debugging purpose.
Table 39-109 BgpFlowspecNlriProblem

releases
Name: BgpFlowspecNlriProblem Severity: major Unspecified

Type: ProtocolAlarm (1) Default probable cause: NlriProblem
Package: rtr (1156)
Raised on class:
rtr.RoutingInstanceSite
Description: The alarm is raised when the filter module receives a BGP FlowSpec NLRI that cannot be
treated.
Remedial action: Information - if the the problem persists please contact Alcatel-Lucent support for
assistance.
Table 39-110 BgpMonitorPrefixFlapRateThresholdReached

releases

BgpMonitorPrefixFlapRateThresholdReached Implicitly cleared: true
(432)
Type: topologyAlarm (34) unstablePrefix (410)
Package: topology
Description: The alarm is raised when a BGP monitor prefix flap rate exceeds the maximum flap rate
threshold value.
purpose.
Table 39-111 BgpMonPrefixUnreachable

releases
Name: BgpMonPrefixUnreachable Severity: major Unspecified

Type: topologyAlarm (34) Default probable cause: prefixUnreachable
Description: The alarm is raised when no route for the monitored prefix is detected.
purpose.
Table 39-112 BgpMonPrefRedundancyLossThresholdReached

releases

BgpMonPrefRedundancyLossThresholdReached Implicitly cleared: true
(796)
Type: topologyAlarm (34) lowNumberofNHops (563)
Package: topology
Description: The alarm is raised when the number of next hops for a monitored BGP route reaches or falls
below the minimum threshold value.
purpose.
Table 39-113 BgpPktRateThresholdReached

releases

BgpPktRateThresholdReached (431) Implicitly cleared: true
Type: topologyAlarm (34) Default probable cause:
Package: topology unstableBgpSpeaker (409)
Description: The alarm is raised when a BGP packet rate exceeds the maximum threshold value.
Remedial action: User configured alarm for monitoring purpose. BGP events history can be used for
debugging purpose.
Table 39-114 BgpProfilePrefixUnreachable

releases
Name: BgpProfilePrefixUnreachable Severity: variable Unspecified

Package: topology BGPProfilePrefixUnreachable (2544)
Raised on class:
topology.AbstractBgpRouteProfile
Description: The alarm is raised when the prefix on BGP profile is unreachable.
Remedial action: BGP Profile matched with BGP prefix unreachable event.
Table 39-115 BgpRouteChangeThresholdPerNHopReached

releases

BgpRouteChangeThresholdPerNHopReached Implicitly cleared: true
(601)
Type: topologyAlarm (34) unstableBgpSpeaker (409)
Package: topology
Description: The alarm is raised when the number of BGP route changes for a next hop reaches the
maximum threshold value for a next hop.
debugging purpose.
Table 39-116 BgpRouteChangeThresholdPerRTargetReached

releases

BgpRouteChangeThresholdPerRTargetReached Implicitly cleared: true
(600)
Type: topologyAlarm (34) unstableVpnSite (413)
Package: topology
Description: The alarm is raised when the number of BGP route changes for a route target reaches the
maximum threshold value for route targets.
debugging purpose.
Table 39-117 BgpRouteCountThresholdReached

releases

BgpRouteCountThresholdReached Implicitly cleared: true
(428)
Type: topologyAlarm (34) tooManyBgpRouteForNextHop (408)
Package: topology
Description: The alarm is raised when the BGP route count for a next hop exceeds the maximum threshold
value for next hops.
debugging purpose.
Table 39-118 BgpRouteFlapRateThresholdReached

releases

BgpRouteFlapRateThresholdReached Implicitly cleared: true
(430)
Type: topologyAlarm (34) unstableBgpSpeaker (409)
Package: topology
Description: The alarm is raised when the BGP route flap rate exceeds the maximum threshold value.
debugging purpose.
Table 39-119 BgpRouteHighWatermarkPerRTargetReached

major releases

BgpRouteHighWatermarkPerRTargetReached Implicitly cleared: true
(433)
Type: topologyAlarm (34) tooManyBgpRouteForGivenRouteTarget
Description: The alarm is raised when there are too many BGP routes for a route target.
debugging purpose.
Table 39-120 BgpRouteLowWatermarkPerRTargetReached

major releases

BgpRouteLowWatermarkPerRTargetReached Implicitly cleared: true
(434)
Type: topologyAlarm (34) tooLittleBgpRouteForGivenRouteTarget
Description: The alarm is raised when there are too few BGP routes for a route target.
debugging purpose.
Table 39-121 BgpRouteRateThresholdPerRTargetReached

releases

BgpRouteRateThresholdPerRTargetReached Implicitly cleared: true
(435)
Type: topologyAlarm (34) unstableVpnSite (413)
Package: topology
Description: The alarm is raised when the BGP route rate for a target reaches the maximum threshold value
for route targets.
debugging purpose.
Table 39-122 BgpRouteRateThresholdReached

releases

BgpRouteRateThresholdReached Implicitly cleared: true
(429)
Type: topologyAlarm (34) tooManyBgpRouteForNextHop (408)
Package: topology
Description: The alarm is raised when the BGP route rate for a next hop exceeds the maximum threshold
value for next hops.
debugging purpose.
Table 39-123 BidirectionalTPLspDestinationMisconfiguration

major releases

BidirectionalTPLspDestinationMisconfiguration Implicitly cleared: true
(5117)
Type: configurationAlarm (11) DestinationParametersMismatch (2053)
Package: mplstp
Raised on class: mplstp.GlobalTPLsp
Description: The alarm is raised when the Destination Global ID, Destination Node ID, or Destination Tunnel
Number is not consistent with the configuration of the opposite TP-LSP in a Bidirectional TP-LSP.
Remedial action: This alarm is generated when a TP-LSP that belongs to a Bidirectional TP-LSP has any of
its Destination Global ID, Destination Node ID, or Destination Tunnel Number misconfigured. Review the
configuration both TP-LSPs in the Bidirectional TP-LSP and ensure that the Destination Global ID, Destination
Node ID, and Destination Tunnel Number are configured properly.
Table 39-124 BidirectionalTPLspPathLspNumberMisconfiguration

major releases

BidirectionalTPLspPathLspNumberMisconfiguration Implicitly cleared: true
(5118)
Type: configurationAlarm (11) LSPNumberMismatch (2054)
Package: mplstp
Raised on class: mplstp.GlobalTPLspPath
Description: The alarm is raised when the LSP Path Number is not consistent with the LSP Path Number for
LER A and LER B.
Remedial action: This alarm is generated when the LSP Path Number for the Bidirectional TP-LSP Path does
not match LER A and/or LER B. Review the configuration of LSP Path Number LER A and LER B and ensure
both are set to the same value as the Bidirectional TP-LSP Path’s LSP Path Number.
Table 39-125 BidirIpPathMonitorPathsDiverge
releases
Name: BidirIpPathMonitorPathsDiverge Severity: minor Unspecified

Package: monpath ipPathsDiverge (449)
Raised on class:
monpath.BidirMonitoredIpPath
Description: The alarm is raised when the 5650 CPAM detects that the IP paths of a bidirectional IP path
monitor diverge. The alarm clears when the paths converge. This may occur when an IP path monitor cannot
be set up after the number of attempts specified by the cpamManagedRoute problematicThresholdAlarmAfter
value in the nms-server.xml file. The alarm is raised if the cpamManagedRoute problematicRetryStrategy value
in nms-server.xml is set to countdown. The default problematicRetryStrategy value of reactive prevents the
alarm from being raised.
Remedial action: Informational - Paths in both direction can be highlighted on the CPAM map to identify the
divergence point.
Table 39-126 BidirLspMonitorPathsDiverge

releases
Name: BidirLspMonitorPathsDiverge Severity: minor Unspecified

Package: monpath LspPathsDiverge (917)
Raised on class:
monpath.BidirMonitoredLspPath
Description: The alarm is raised when the LSP’s active path’s hops do not match in the forward and reverse
direction.
Remedial action: Informational - Paths in both direction can be highlighted on the CPAM map to identify the
divergence point.
Table 39-127 BladeHardware_lm75localTempCriticalAssLMert

releases

BladeHardware_lm75localTempCriticalAssLMert Implicitly cleared: true
(5870)
Package: femto
Raised on class: femto.BladeHardware
Description: LM 75 local temperature critical assert
Table 39-128 BladeHardware_lm75localTempCriticalDeassLMert

releases

BladeHardware_lm75localTempCriticalDeassLMert Implicitly cleared: true
(5872)
Package: femto equipmentMalfunction (698)
Raised on class: femto.BladeHardware
Description: LM 75 local temperature critical deassert
Table 39-129 BootEnvironmentSyncFailed

releases
Name: BootEnvironmentSyncFailed Severity: critical Unspecified

Package: sw bootEnvironmentSyncFailed (87)
Raised on class:
sw.SoftwareUpgradeManager
Description: The alarm is raised when the synchronization of one or more system initialization files between
the active and standby CPM cards fails, or when one or both of the CSM compact flash devices do not have
enough space when the ’admin redundancy synchronize boot-env’ command is executed, or when the node is
rebooted.
Remedial action: The operator should make sure that the Boot Environment files on the CSM cards are in
Sync with each other or there is enough space available on the compact flash.
Table 39-130 BootLoaderFirmwareMismatchAlarm

releases

BootLoaderFirmwareMismatchAlarm Implicitly cleared: false
(617)
Type: firmwareAlarm (26) bootLoaderVersionMismatch (118)
Package: equipment
Raised on class:
equipment.ControlProcessor
Description: The alarm is raised when there is a mismatch between the firmware version and the software
image on an NE. The alarm information includes the discovered and expected version identifiers.
Remedial action: Either the firmware or the device SW must be upgraded to compatible versions. The image
(firmware or device SW) which is the oldest should be upgraded. Firmware must be upgraded using the NE’s
CLI. 5620 SAM can be used to upgrade the SW image on the device.
Table 39-131 BrokenLoop

releases
Name: BrokenLoop (469) Severity: major Unspecified

Raised on class: stackNotInLoop (355)
equipment.StackConfiguration
Description: The alarm is raised when the loop-detection stack detects a loop condition, or when the stack
contains an unexpected element.
Remedial action: Login to switch console, check and correct configuration and reload stack.
Table 39-132 BSRSubscriberTraceConfig_subscriberTraceRecordingSessionFailure
major
releases

BSRSubscriberTraceConfig_subscriberTraceRecordingSessionFailure Implicitly cleared: true
(5801)
Default probable
Type: processingErrorAlarm (81) cause:
Package: femto unspecifiedReason
Raised on class: femto.FemtoSubscriberTraceConfig (802)
Description: Failure to start a trace recording session due to any problem.
Table 39-133 BSRSubscriberTraceConfig_subscriberTraceUploadFailure

major
releases

BSRSubscriberTraceConfig_subscriberTraceUploadFailure Implicitly cleared: true
(5802)
Type: communicationsAlarm (4) responseTimeExcessive
Raised on class: femto.FemtoSubscriberTraceConfig
Description: Failure to transferring SubscriberTrace files even after retries.
Table 39-134 BWUtilizationExceeded

releases
Name: BWUtilizationExceeded (811) Severity: major Unspecified

Type: thresholdCrossed (6) Implicitly cleared: true
Package: netw Default probable cause:
Raised on class: thresholdCrossed (12)
netw.AbstractPhysicalLink
Description: The alarm is raised when the per-CoS or overall bandwidth utilization exceeds the configured
threshold.
Remedial action: Informational - if the alarm persists or is occurring frequently then investigation is required to
understand how this Physical Link became overbooked
Table 39-135 CableLOS (equipment)

releases
Name: CableLOS (678) Severity: variable Unspecified

Package: equipment Default probable cause: cableLOS
equipment.Equipment
Description: The alarm is raised when an MSS detects a cable LOS event.
Remedial action: The alarm is raised when an MSS detects a cable LOS event.
Table 39-136 CableLOS (radioequipment)

releases
Name: CableLOS (678) Severity: variable Unspecified

Package: radioequipment Default probable cause: cableLOS
Description: The alarm is raised when an MSS detects a cable LOS event.
Remedial action: The alarm is raised when an MSS detects a cable LOS event. Please refer 9500 Node
Maintenance manual for remedial action information.
Table 39-137 CallTraceAlreadyActive

releases
Name: CallTraceAlreadyActive Severity: warning Unspecified

Type: callTraceSessionAlarm Default probable cause:
(90) callTraceManuallyActivated (906)
Package: lte
Raised on class: lte.CTg
Description: The alarm is raised when a Call Trace Session is already active when the scheduled task starts.
The scheduled task will not deactivate it. The Call Trace Session must be manually deactivated. The alarm is
cleared when the Call Trace session is deactivated successfully.
Remedial action: The existing Call Trace Session must be manually deactivated. The alarm is cleared when
the Call Trace session is deactivated successfully.
Table 39-138 CallTraceScheduledTaskExecutionError

releases

CallTraceScheduledTaskExecutionError Implicitly cleared: false
(1280)
Type: callTraceSessionAlarm (90) callTraceConfigurationError (907)
Package: lte Applicable probable causes:
Raised on class: lte.CTg callTraceConfigurationError
eventBasedTraceEnabled
debugTraceActive
Description: The alarm is raised when the execution of a Call Trace scheduled task has a failure activating or
deactivating this Call Trace session.
Remedial action: Check the call trace session.
Table 39-139 CAProfileStateChange

releases
Name: CAProfileStateChange (3910) Severity: major Unspecified

Package: sitesec
Raised on class: Default probable cause:
sitesec.CertificateAuthProfile caProfileStateDown (1497)
Description: The alarm is raised when Certificate Authority profile changes state to ’down’ due to
tmnxSecNotifFailureReason.
Remedial action: The Certificate Authority profile changes state to ’down’. Depending on the reason specified,
corrective action should be taken
Table 39-140 CardCPUAboveThreshold

releases

CardCPUAboveThreshold Implicitly cleared: false
(618)
Type: configurationAlarm CardCPUUtilizationCrossedAboveThreshold (458)
(11)
Package: equipment
Raised on class:
equipment.CardSlot
Description: The alarm is raised when the card CPU usage exceeds the threshold value.
Remedial action: Informational - The CPU of the card indicated in the alarm is overloaded. If the condition
persists then processing load should be transferred from this card to other cards which are more lightly loaded.
If the problem persists then please contact Alcatel-Lucent support for assistance.
Table 39-141 CardMemoryAboveThreshold

releases

CardMemoryAboveThreshold Implicitly cleared: false
(619)
Type: configurationAlarm (11) CardMemoryUtilizationCrossedAboveThreshold (459)
Package: equipment
Raised on class:
equipment.CardSlot
Description: The alarm is raised when the card memory usage exceeds the threshold value.
Remedial action: Informational - The memory of the card indicated in the alarm is over utilized. If the condition
persists then processing load should be transferred from this card to other cards which are more lightly loaded
in order to reduce memory consumption. If the problem persists then please contact Alcatel-Lucent support for
assistance.
Table 39-142 CardRxAboveThreshold

releases

CardRxAboveThreshold Implicitly cleared: true
(620)
Type: configurationAlarm CardRxUtilizationCrossedAboveThreshold (460)
(11)
Package: equipment
Raised on class:
equipment.CardSlot
Description: The alarm is raised when the card Rx exceeds the threshold value.
Remedial action: The utilization of the card is higher than normal. If the problem persists please contact
Alcatel-Lucent support for assistance.
Table 39-143 CardRxTxAboveThreshold

releases

CardRxTxAboveThreshold Implicitly cleared: true
(621)
Type: configurationAlarm CardRxTxUtilizationCrossedAboveThreshold (461)
(11)
Package: equipment
Raised on class:
equipment.CardSlot
Description: The alarm is raised when the card Tx exceeds the threshold value.
Remedial action: The utilization of the card is higher than normal. If the problem persists please contact
Table 39-144 CardUnseated

releases
Name: CardUnseated (1161) Severity: major Unspecified

Package: equipment Default probable cause: CardUnseated
equipment.CardSlot
Description: The alarm is raised when a card is removed.
Table 39-145 CeAddressIncompatible

releases
Name: CeAddressIncompatible Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause:
Package: ipipe ceAddressIncompatible (190)
Raised on class: ipipe.Ipipe
Description: The alarm is raised when two SAPs in an Ipipe have the same CE IP address, or when the CE IP
address is not the same as the CE IP address of the peer SDP binding.
Raising condition: (’ceAddressIncompatible’ EQUAL ’true’)
Clearing condition: (’ceAddressIncompatible’ EQUAL ’false’)
Remedial action: Modify the CE Address so that it’s not same address as other SAPs and it matches the
address of the peer SDP binding.
Table 39-146 CheckpointLimitAt75Percent

releases
Name: CheckpointLimitAt75Percent Severity: warning Unspecified
Package: topology tooManyCheckpoints (337)
Raised on class:
topology.TopologyManager
Description: The alarm is raised when the number of check points reaches 75 percent of the maximum
allowed value.
Remedial action: Informational - deprecated 9.0
Table 39-147 CheckpointLimitReachedOrExceeded

releases

CheckpointLimitReachedOrExceeded Implicitly cleared: false
(426)
Type: configurationAlarm (11) tooManyCheckpointObjects (837)
Package: topology
Raised on class:
topology.TopologyManager
Description: The alarm is raised when the number of check points objects reaches or exceeds the maximum
allowed value.
Remedial action: Maximum number of Checkpoint objects reached, the IGP history cleanup task begins and
removes older objects. To keep history increase maximumNumberOfCheckpointObjects in nms-server,xml.
Table 39-148 ChildTemplateInvalid

releases
Name: ChildTemplateInvalid (193) Severity: major Unspecified

Package: template Default probable cause:
Raised on class: referencedObjectInvalid (152)
template.TemplateBinding
Description: The alarm is raised when a child template in a template binding is invalid. The alarm is
deprecated in the 5620 SAM, Release 6.0 and later.
Raising condition: (’childTemplateInvalidReference’ EQUAL ’true’)
Clearing condition: (’childTemplateInvalidReference’ EQUAL ’false’)
Table 39-149 CliLoginMaxAttempts

releases
Name: CliLoginMaxAttempts Severity: warning Unspecified

Type: communicationsAlarm (4) Default probable cause: cliLoginMaxAttempts
Package: netw (1439)
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the number of CLI login failures due to an incorrect user name or
password using TELNET session exceeds the configured value.
Remedial action: Informational
Table 39-150 ClockFailure

Name: ClockFailure (1162) Severity: variable Unspecified

Package: equipment Default probable cause: clockFailure (865)
Description: The alarm is raised when an MPT radio clock failure occurs.
Table 39-151 CModeRxQueryMismatch

releases

CModeRxQueryMismatch Implicitly cleared: false
(160)
Type: configurationAlarm InvalidCompatibilityModeofQueryReceieved (130)
(11)
Package: igmp
Raised on class:
igmp.Interface
Description: The alarm is raised when an IGMP interface receives an IGMP query of a higher version than the
version configured on the interface, for example, when the interface is configured for IGMPv1 and it receives
an IGMPv2 or IGMPv3 query. The interface does not process the received IGMP message.
Table 39-152 CommonLOS

releases
Name: CommonLOS (3621) Severity: variable Unspecified

Package: equipment Default probable cause: commonLOS
equipment.Port
Description: The alarm is raised when a radio interface CLA detects a loss of signal.
Table 39-153 CommunityMisconfiguration

releases

CommunityMisconfiguration Implicitly cleared: true
(442)
Type: serviceAlarm (16) CommunityMisconfiguration (347)
Package: vprn
Raised on class:
vprn.AbstractSite
Description: The alarm is raised when the 5620 SAM detects a community misconfiguration on a service site.
Remedial action: Configure the SNMP community String on the VPRN service site
Table 39-154 ConfigFileSyncFailed

releases
Name: ConfigFileSyncFailed (102) Severity: critical Unspecified

Package: sw Default probable cause:
Raised on class: configFileSyncFailed (88)
sw.SoftwareUpgradeManager
Description: The alarm is raised when the configuration file synchronization between the active and standby
CPM cards fails.
Remedial action: Please log into the NE in question via CLI and execute a manual synchronization. If the
problem persists please contact Alcatel-Lucent support for assistance.
Table 39-155 ConfigNotCompatible

releases
Name: ConfigNotCompatible Severity: critical Unspecified

Package: equipment DaughterCardConfigNotCompatible (301)
Raised on class:
equipment.PhysicalPort
Description: The alarm is raised when an MDA configuration is incompatible with the MDA.
Remedial action: A configuration error has occurred which must be corrected. The MDA type configured for
the slot identified in the alarm must match the installed MDA type.
Table 39-156 Connected2GUEsExceeded

releases
Name: Connected2GUEsExceeded Severity: info Unspecified

Package: ltemme ThresholdExceeded (2052)
Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of Connected 2G UEs exceeds the threshold that has been
set by the operator.
Raising condition: ((’2G Connected UEs Threshold’ NOT EQUAL ’0L’) AND (’2G Connected UEs’ > ’2G
Connected UEs Threshold’))

releases
Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of Connected 3G UEs exceeds the threshold that has been
Raising condition: ((’3G Connected UEs Threshold’ NOT EQUAL ’0L’) AND (’3G Idle UEs’ > ’3G Connected
UEs Threshold’))

releases

Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of 4G Connected UEs exceeds the threshold that has been
Raising condition: ((’4G Connected UEs Threshold’ NOT EQUAL ’0L’) AND (’4G Connected UEs’ > ’4G
Connected UEs Threshold’))
Table 39-159 ContainingEquipmentMissing

releases

ContainingEquipmentMissing Implicitly cleared: true
(463)
Type: equipmentAlarm (3) containingEquipmentMissing (327)
Package: equipment
Description: The alarm is raised when the compositeEquipmentState attribute has a value of
containingEquipmentMissing.
Clearing condition: ((’Status’ NOT EQUAL ’Parent Removed’) OR (’isTerminatable’ NOT EQUAL ’true’) OR
(’Equipped’ EQUAL ’false’))
Remedial action: Informational - an card has been removed from the system.
Table 39-160 CorporateAndSecuredCompositeServicesAreNotConnected

major
releases

CorporateAndSecuredCompositeServicesAreNotConnected Implicitly cleared: false
(828)
Package: ipsec CompositeServiceMisconfiguration
(591)
Raised on class: ipsec.IPSecSecuredVpn
Description: The alarm is raised when the corporate and secured services used by an IPsec VPN do not have a
connector between them.
Raising condition: (’corporateToSecureServiceConnector’ EQUAL ’Not Connected’)
Clearing condition: ((’corporateToSecureServiceConnector’ EQUAL ’Connected’) OR

(’corporateToSecureServiceConnector’ EQUAL ’None’))
Remedial action: Create a connector to connect the Corporate service and Secured service.
Table 39-161 CorporateAndSecuredCompositeServicesMistmatch

major
releases

CorporateAndSecuredCompositeServicesMistmatch Implicitly cleared: false
(829)
Type: serviceAlarm (16) CompositeServiceMisconfiguration
Package: ipsec (591)
Raised on class: ipsec.IPSecSecuredVpn
Description: The alarm is raised when the corporate and secured services used by an IPsec VPN are in
different composite services.
Table 39-162 CorruptedBgpUpdate

releases
Name: CorruptedBgpUpdate (3328) Severity: major Unspecified

Type: topologyAlarm (34) Implicitly cleared: false
Package: topology Default probable cause:
Raised on class: CorruptedBgpUpdateDetected (1164)
topology.BgpAutonomousSystem
Description: The alarm is raised when a BGP-bad-update-packet-received message is sent from the CPAA
against a BGP AS. The alarm is not auto-cleared by CPAM.
Remedial action: A peer is sending a corrupted BGP update. The information regarding the update can be
viewed in the BGP corrupted update record. Action should be taken to fix the offending BGP speaker.
Table 39-163 CouplingEthernetLinkDown

releases
Name: CouplingEthernetLinkDown Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: LossOfSignal
Package: mwa (541)
Raised on class: mwa.PortTermination
Description: The alarm is raised when a MPT detects a coupling Ethernet Link Down
information.
Table 39-164 CouplingLossOfRadioFrame
releases
Name: CouplingLossOfRadioFrame Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: LossOfFrame
Package: mwa (1904)
Description: The alarm is raised when a MPT detects a Loss of Radio Frame from Coupling Path
information.
Table 39-165 CouplingPortSFPCardFailure

releases
Name: Severity: variable Unspecified

CouplingPortSFPCardFailure Implicitly cleared: true
(4821)
Type: equipmentAlarm (3) ReplaceableUnitProblem (1905)
Package: mwa
Raised on class:
mwa.PortTermination
Description: This alarm is raised when coupling port SFP Card failure is detected.
information.
Table 39-166 CouplingPortSFPMissing

releases
Name: CouplingPortSFPMissing Severity: variable Unspecified

Package: mwa ReplaceableUnitMissing (1906)
Raised on class:
mwa.PortTermination
Description: This alarm is raised when coupling port SFP is missing.
information.
Table 39-167 CpaaAreaUnreachableThroughISIS

releases

CpaaAreaUnreachableThroughISIS Implicitly cleared: true
(5418)
Type: topologyAlarm (34) CPAALinksToAreaDown (2125)
Package: topology
Description: The alarm is raised when all links from CPAA to an area are down.
Remedial action: 1) The active CPAA cannot reach certain CPAA instance through the ISIS protocol. Please
check the links to the unreachable CPAA instance. 2) If the standby CPAA is functional as per your
requirements, switch-over might resolve the issue.
Table 39-168 CpaaAreaUnreachableThroughOSPF

releases

CpaaAreaUnreachableThroughOSPF Implicitly cleared: true
(5419)
Package: topology
Description: The alarm is raised when all links from CPAA to OSPF area are down.
Remedial action: 1) The active CPAA cannot reach certain area through the OSPF protocol. Please check the
links to the unreachable area. 2) If the standby CPAA is functional as per your requirements, switch-over might
resolve the issue.
Table 39-169 CpaaAreaUnreachableThroughOSPFv3

releases

CpaaAreaUnreachableThroughOSPFv3 Implicitly cleared: true
(5420)
Package: topology
Description: The alarm is raised when all links from CPAA to OSPFv3 area are down.
Remedial action: 1) The active CPAA cannot reach certain area through the OSPFv3 protocol. Please check
the links to the unreachable area. 2) If the standby CPAA is functional as per your requirements, switch-over
might resolve the issue.
Table 39-170 CpamTimedLicenseExpiryNotice

releases

CpamTimedLicenseExpiryNotice Implicitly cleared: false
(692)
Type: cpamLicensingAlarm (39) timedcpamLicenseExpiryNotice (293)
Package: security
Raised on class:
security.CpamLicense
Description: The alarm is raised when the 5650 CPAM license timer expires. The alarm information includes
the license expiry date.
Remedial action: Informational - the CPAM license key is about to expire. Please contact Alcatel-Lucent Sales
to request either an extension for the license or a permanent license key.
Table 39-171 CpeUnreachable

releases
Name: CpeUnreachable (525) Severity: major Unspecified

Type: communicationsAlarm Implicitly cleared: true
(4) Default probable cause: CpeUnreachable
Package: rtr (334)
Raised on class:
rtr.StaticRoute
Description: The alarm is raised when the CPE associated with a static route is unreachable.
Remedial action: Please check that the static route is correct or exists for the CPE.
Table 39-172 CPMPChipMemoryEvent

releases
Name: CPMPChipMemoryEvent Severity: warning Unspecified

Type: hardwareAnomaly (55) Default probable cause:
Package: equipment memoryParityError (451)
Raised on class:
equipment.ProcessorCard
Description: The alarm is raised when a PChip detects a memory error. The alarm is raised against a 7450
ESS, 7710 SR, 7950 SR, or 7750 SR. The alarm is raised against a Release 11.0 NE at R4 or later.
Remedial action: A fault has been detected in the hardware if the problem persists please contact Alcatel-
Lucent support for assistance.
Table 39-173 CPUInfo_thermakTripAssert

releases
Name: CPUInfo_thermakTripAssert Severity: minor Unspecified

Package: femto processorProblem (633)
Raised on class:
femto.FGWCPUInfo
Description: Thermal trip assert
Table 39-174 CreditControlInsertedFltrEntryDropped

releases

CreditControlInsertedFltrEntryDropped Implicitly cleared: false
(1150)
Type: configurationAlarm (11) FilterEntryDropped (856)
Package: aclfilter
Raised on class: aclfilter.FilterDefinition
Description: The alarm is raised when a request to insert a filter entry is not successful for a credit control
application.
Remedial action: A Configuration error has occurred. The request to insert a filter entry was not successful for
Credit Control application. Check the configuration filter entry.
Table 39-175 CreditControlInsertSpaceThresholdAlarm
releases

CreditControlInsertSpaceThresholdAlarm Implicitly cleared: true
(1149)
Type: configurationAlarm (11) UtilizationExceedConfiguredLimit (855)
Package: aclfilter
Raised on class: aclfilter.FilterDefinition
Description: The alarm is raised when the utilization of a filter entry range that is reserved for filter entry
insertion increases to the configured maximum value for a credit control application insert range.
Remedial action: The filter entry range reserved for filter entry insertion has increased to the configured high
watermark for Credit Control application. Make an adjusted to the high watermark or to the filter.
Table 39-176 CrossConnectionFail

releases
Name: CrossConnectionFail (679) Severity: variable Unspecified

Raised on class: crossConnectionFail (494)
Description: The alarm is raised when an MSS TDM cross-connection fails.
Table 39-177 CTAuxMisalignementWhileEnbAutoAllocationDisabled

major releases

CTAuxMisalignementWhileEnbAutoAllocationDisabled Implicitly cleared: true
(5423)
Type: communicationsAlarm (4) eNBsAuxIPMisalignment (2126)
Package: lte
Raised on class: lte.CallTraceSessionManager
Description: The alarm is raised if automatic AUX allocation is disabled and if there is a discrepancy between
the eNB configurations and the AUX assigned to the eNB in SAM. If the automatic AUX allocation is enabled,
SAM will automatically set the eNB IP addresses linked to the trace management on the assigned AUX in
SAM.
Remedial action: Manually launch the allocation of the eNBs to the active CT AUX server.
Table 39-178 DatabaseServerErrors

releases
Name: DatabaseServerErrors Severity: critical Unspecified

Type: databaseAlarm (29) Default probable cause: DatabaseErrors
Package: db (2090)
Raised on class:
db.DatabaseManager
Description: The alarm is raised when when a critical Oracle error occurs.
Remedial action: The probable cause of this alarm is the database server detected a critical error. The
EmsDbServerHealth.log and oracle trace files will provide more information.
Table 39-179 DataChannelLoopback

releases
Name: DataChannelLoopback (3945) Severity: warning Unspecified

Package: tdmequipment Default probable cause:
Raised on class: dataChannelLoopback (1526)
tdmequipment.DataChannelSpecifics
Description: The alarm is raised when an NE reports that a data channel has a loopback alarm condition.
Remedial action: Informational only.
Table 39-180 DataMtReused

releases
Name: DataMtReused (361) Severity: warning Unspecified

Type: dataMtReusedAlarm (37) Implicitly cleared: false
Package: pim Default probable cause: DataMtReused
pim.DataMtInterface
Description: The alarm is raised when a data MDT is reused.
Remedial action: A configuration error has occurred that must be corrected. Please check MVPN Selective
Tunnel Data MT Interface configuration so that no duplicate C (S,G) is mapped to a data MDT.
Table 39-181 DaughterCardConfigNotCompatible

releases

DaughterCardConfigNotCompatible Implicitly cleared: false
(404)
Type: equipmentAlarm (3) DaughterCardConfigNotCompatible (301)
Package: equipment
Raised on class:
equipment.DaughterCardSlot
Description: The alarm is raised when a supported MDA is inserted into a compatible IOM slot, but the
configuration on the MDA ports is not compatible with the MDA.
Remedial action: A configuration error has occurred which must be corrected. The configuration of one or
more ports must be changed to match the ports on the MDA.
Table 39-182 DDosCardFpEventOverflow

releases
Name: DDosCardFpEventOverflow Severity: warning Unspecified
Type: Default probable cause: eventOverflow
securityServiceOrMechanismViolation (1684)
(92)
Package: equipment
Raised on class: equipment.Card
Description: The alarm is raised when a flood of distributed CPU FP protection events occur on a particular
card and some of the events are lost due to event throttling mechanism.
Remedial action: Please reduce the number of distributed DoS FP protection policers configured.
Table 39-183 DDosCardSapEventOverflow

releases
Name: DDosCardSapEventOverflow Severity: warning Unspecified

(92)
Package: equipment
Description: The alarm is raised when a flood of distributed CPU protection SAP events occur on a particular
card and some of the events are lost due to event throttling mechanism.
Remedial action: Please reduce the number of distributed DoS SAP protection policers configured.
Table 39-184 DDosCardVrtrIfEventOverflow

releases
Name: DDosCardVrtrIfEventOverflow Severity: warning Unspecified

(92)
Package: equipment
Description: The alarm is raised when a flood of distributed CPU protection network-interface events occur on
a particular card and some of the events are lost due to event throttling mechanism.
Remedial action: Please reduce the number of distributed DoS Network Interface protection policers
configured.
Table 39-185 DDosFpDynamicPoolUsageHigh

releases

DDosFpDynamicPoolUsageHigh Implicitly cleared: true
(4463)
Type: resourceLimitReached (131)
securityServiceOrMechanismViolation
(92)
Package: equipment
Raised on class:
equipment.ForwardingPlane
Description: The alarm is raised when the dynamic enforcement policer pool usage on the forwarding plane is
nearly exhausted.
Remedial action: Please adjust the dynamic enforcement policer pool usage.
Table 39-186 Degrade

Name: Degrade (622) Severity: variable Unspecified

Package: equipment Default probable cause: degrade (462)
Description: The alarm is raised when a degraded signal is detected.
Remedial action: The signal being received on the indicated port is of poor quality. Check to ensure that the
physical link is not damaged and that the link is properly connected/seated to the port.
Table 39-187 DemFail (equipment)

releases
Name: DemFail (680) Severity: variable Unspecified

Package: equipment Default probable cause: demFail
equipment.Equipment
Description: The alarm is raised when an MSS demodulation function fails.
Table 39-188 DemFail (radioequipment)

releases
Name: DemFail (680) Severity: variable Unspecified

Package: radioequipment Default probable cause: demFail
Description: The alarm is raised when an MSS demodulation function fails.
Table 39-189 DemodulatorUnlocked

releases
Name: DemodulatorUnlocked Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: DemodulationFailure
Package: mwa (1907)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects demodulation failure.

information.
Table 39-190 DemXpicLOS (equipment)

Name: DemXpicLOS (3622) Severity: variable Unspecified

Package: equipment Default probable cause: demXpicLos (1411)
Raised on class:
equipment.Port
Description: The alarm is raised when a loss of signal occurs during XPIC demodulation.
Remedial action: The alarm is raised when a loss of signal occurs on XPIC demodulation
Table 39-191 DemXpicLOS (mpr)

releases
Name: DemXpicLOS (3622) Severity: variable Unspecified

Package: mpr Default probable cause: demXpicLos
mpr.SubRackElements
Description: The alarm is raised when a loss of signal occurs during XPIC demodulation.
Remedial action: The alarm is raised when a loss of signal occurs on XPIC demodulation
Table 39-192 DependentObjectDeleted

releases
Name: DependentObjectDeleted Severity: major Unspecified

Package: template referencedObjectGone (151)
Raised on class:
template.Template
Description: The alarm is raised when an object referenced by a template cannot be found. The alarm is
Raising condition: (’Invalid References (Reset on Save)’ EQUAL ’true’)
Clearing condition: (’Invalid References (Reset on Save)’ EQUAL ’false’)
Table 39-193 DeployProfileFailed

releases
Name: DeployProfileFailed (610) Severity: major Unspecified

Type: configurationAlarm (11) Implicitly cleared: false
Package: autoconfig Default probable cause:
Raised on class: DeployProfileFailed (453)
autoconfig.AutoProvisioning
Description: The alarm is raised when the deployment of a script to a 7705 SAR fails.
Remedial action: Informational - Please revisit target node configuration.
Table 39-194 Deregistered4GUEsExceeded

releases

Deregistered4GUEsExceeded Implicitly cleared: false
(5044)
Type: communicationsAlarm (4) ThresholdExceeded (2052)
Package: ltemme
Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of 4G Deregistered UEs exceeds the threshold that has
been set by the operator.
Raising condition: ((’4G Deregistered UEs Threshold’ NOT EQUAL ’0L’) AND (’4G Deregistered UEs’ > ’4G
Deregistered UEs Threshold’))
Table 39-195 DfPeerDown

Name: DfPeerDown (3304) Severity: major Unspecified

Type: EpcLIAlarm (102) Implicitly cleared: true
Package: lteli Default probable cause: DfPeerDown (1151)
Raised on class: lteli.DFPeer
Description: The alarm is raised on a Delivery Function that is operationally down.
Raising condition: ((’isLocal’ EQUAL ’true’) AND (’Operational State’ NOT EQUAL ’In Service’))
Clearing condition: NOT (((’isLocal’ EQUAL ’true’) AND (’Operational State’ NOT EQUAL ’In Service’)))
Remedial action: A TCP connection failure associated with a Delivery Function has occurred. The underlying
transport network is unreliable. Please correct the issue within the transport network.
Table 39-196 DHCPPFoLeaseUpdateFailedAddressConflict

major
releases

DHCPPFoLeaseUpdateFailedAddressConflict Implicitly cleared: false
(5159)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedAddressConflict
Package: dhcp (2079)
Raised on class: dhcp.LocalDhcpPoolFailover
Description: This alarm is raised when a address conflict lease update received from the failover peer cannot
be processed successfully. This DHCP pool instance has already leased another address to this host.
Remedial action: This alarm indicates that the Local DHCP Pool Failover lease update has failed. Packets
received from the failover peer cannot be processed. This DHCP pool instance has already leased another
address to this host. Please ensure all configurations are correct.
Table 39-197 DHCPPFoLeaseUpdateFailedfoShutdown
major releases

DHCPPFoLeaseUpdateFailedfoShutdown Implicitly cleared: false
(5167)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedfoShutdown
Raised on class:
dhcp.LocalDhcpPoolFailover
Description: This alarm is raised when a shutdown lease update received from the failover peer cannot be
processed successfully. The failover state of this DHCP Pool instance is ’shutdown’.
received from the failover peer cannot be processed. The failover state of this DHCP Pool instance is
’shutdown’. Please ensure all configurations are correct.
Table 39-198 DHCPPFoLeaseUpdateFailedHostConflict

major releases

DHCPPFoLeaseUpdateFailedHostConflict Implicitly cleared: false
(5160)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedHostConflict
Raised on class:
Description: This alarm is raised when a host conflict lease update received from the failover peer cannot be
processed successfully. This DHCP pool instance has already leased this address to another host.
received from the failover peer cannot be processed. This DHCP pool instance has already leased this
address to another host. Please ensure all configurations are correct.
Table 39-199 DHCPPFoLeaseUpdateFailedLeaseExpired

major releases

DHCPPFoLeaseUpdateFailedLeaseExpired Implicitly cleared: false
(5161)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedLeaseExpired
Raised on class:
Description: This alarm is raised when a lease expired lease update received from the failover peer cannot be
processed successfully. The lease received from the peer has expired.
received from the failover peer cannot be processed. The lease received from the peer has expired. Please
ensure all configurations are correct.
Table 39-200 DHCPPFoLeaseUpdateFailedMaxLeaseReached

major
releases
DHCPPFoLeaseUpdateFailedMaxLeaseReached Implicitly cleared: false
(5162)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedMaxLeaseReached
Description: This alarm is raised when a maximum reached lease update received from the failover peer cannot be
processed successfully. The maximum number of leases is already reached.
Remedial action: This alarm indicates that the Local DHCP Pool Failover lease update has failed. Packets received
from the failover peer cannot be processed. The maximum number of leases is already reached. Please ensure all
configurations are correct.
Table 39-201 DHCPPFoLeaseUpdateFailedPeerConflict

major releases

DHCPPFoLeaseUpdateFailedPeerConflict Implicitly cleared: false
(5163)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedPeerConflict
Raised on class:
Description: This alarm is raised when a peer conflict lease update received from the failover peer cannot be
processed successfully. The failover peer has leased an address within a subnet range of which the failover
control is set to ’local’ on this local DHCP pool instance.
received from the failover peer cannot be processed. The failover peer has leased an address within a subnet
range of which the failover control is set to ’local’ on this local DHCP pool instance. Please ensure all
configuration is correct.
Table 39-202 DHCPPFoLeaseUpdateFailedPersistenceCongested

major
releases

DHCPPFoLeaseUpdateFailedPersistenceCongested Implicitly cleared: false
(5164)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedPersistenceCongested
Description: This alarm is raised when a persistence congested lease update received from the failover peer cannot be
processed successfully. The lease received from the peer can not be persistently stored because the persistence subsystem
is in overload.
Remedial action: This alarm indicates that the Local DHCP Pool Failover lease update has failed. Packets received from
the failover peer cannot be processed. The lease received from the peer can not be persistently stored because the
persistence subsystem is in overload. Please ensure all configuration is correct.
Table 39-203 DHCPPFoLeaseUpdateFailedRangeNotFound

major
releases

DHCPPFoLeaseUpdateFailedRangeNotFound Implicitly cleared: false
(5165)
Type: configurationAlarm (11)
DHCPPFoLeaseUpdateFailedRangeNotFound
Description: This alarm is raised when a range not found lease update received from the failover peer cannot
be processed successfully. No valid include range for this lease could be found.
received from the failover peer cannot be processed. No valid include range for this lease could be found.
Please ensure all configurations are correct.
Table 39-204 DHCPPFoLeaseUpdateFailedSubnetNotFound

major
releases

DHCPPFoLeaseUpdateFailedSubnetNotFound Implicitly cleared: false
(5166)
Type: configurationAlarm (11) DHCPPFoLeaseUpdateFailedSubnetNotFound
Description: This alarm is raised when a subnet not found lease update received from the failover peer cannot
be processed successfully. No valid subnet for this lease could be found.
received from the failover peer cannot be processed. No valid subnet for this lease could be found. Please
ensure all configurations are correct.
Table 39-205 DHCPSFoLeaseUpdateFailedAddressConflict

major
releases

DHCPSFoLeaseUpdateFailedAddressConflict Implicitly cleared: false
(4977)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedAddressConflict
Raised on class:
dhcp.LocalDhcpServerFailover
Description: This alarm is raised when a address conflict lease update received from the failover peer cannot
be processed successfully. This DHCP server instance has already leased another address to this host.
Remedial action: This alarm indicates the Local DHCP Server Failover lease update has failed. Packet
received from the failover peer, cannot be processed successfully. This DHCP server instance has already
leased another address to this host. Please ensure all configuration is correct.
Table 39-206 DHCPSFoLeaseUpdateFailedfoShutdown

major releases

DHCPSFoLeaseUpdateFailedfoShutdown Implicitly cleared: false
(4985)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedfoShutdown
Raised on class:
Description: This alarm is raised when a shutdown lease update received from the failover peer cannot be
processed successfully. The failover state of this DHCP Server instance is ’shutdown’.
received from the failover peer, cannot be processed successfully. The failover state of this DHCP Server
instance is ’shutdown’. Please ensure all configuration is correct.
Table 39-207 DHCPSFoLeaseUpdateFailedHostConflict

major releases

DHCPSFoLeaseUpdateFailedHostConflict Implicitly cleared: false
(4978)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedHostConflict
Raised on class:
Description: This alarm is raised when a host conflict lease update received from the failover peer cannot be
processed successfully. This DHCP server instance has already leased this address to another host.
received from the failover peer, cannot be processed successfully. This DHCP server instance has already
leased this address to another host. Please ensure all configuration is correct.
Table 39-208 DHCPSFoLeaseUpdateFailedLeaseExpired

major releases

DHCPSFoLeaseUpdateFailedLeaseExpired Implicitly cleared: false
(4979)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedLeaseExpired
Raised on class:
Description: This alarm is raised when a lease expired lease update received from the failover peer cannot be
processed successfully. The lease received from the peer has expired.
received from the failover peer, cannot be processed successfully. The lease received from the peer has
expired. Please ensure all configuration is correct.
Table 39-209 DHCPSFoLeaseUpdateFailedMaxLeaseReached

major
releases

DHCPSFoLeaseUpdateFailedMaxLeaseReached Implicitly cleared: false
(4980)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedMaxLeaseReached
Raised on class: dhcp.LocalDhcpServerFailover
Description: This alarm is raised when a maximum reached lease update received from the failover peer cannot be
processed successfully. The maximum number of leases is already reached.
Remedial action: This alarm indicates the Local DHCP Server Failover lease update has failed. Packet received
from the failover peer, cannot be processed successfully. The maximum number of leases is already reached. Please
ensure all configuration is correct.
Table 39-210 DHCPSFoLeaseUpdateFailedPeerConflict
major releases

DHCPSFoLeaseUpdateFailedPeerConflict Implicitly cleared: false
(4981)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedPeerConflict
Raised on class:
Description: This alarm is raised when a peer conflict lease update received from the failover peer cannot be
processed successfully. The failover peer has leased an address within a subnet range of which the failover
control is set to ’local’ on this local DHCP server instance.
received from the failover peer, cannot be processed successfully. The failover peer has leased an address
within a subnet range of which the failover control is set to ’local’ on this local DHCP server instance. Please
Table 39-211 DHCPSFoLeaseUpdateFailedPersistenceCongested

major
releases

DHCPSFoLeaseUpdateFailedPersistenceCongested Implicitly cleared: false
(4982)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedPersistenceCongested
Raised on class: dhcp.LocalDhcpServerFailover
Description: This alarm is raised when a persistence congested lease update received from the failover peer cannot be
processed successfully. The lease received from the peer can not be persistently stored because the persistence subsystem
is in overload.
Remedial action: This alarm indicates the Local DHCP Server Failover lease update has failed. Packet received from the
failover peer, cannot be processed successfully. The lease received from the peer can not be persistently stored because
the persistence subsystem is in overload. Please ensure all configuration is correct.
Table 39-212 DHCPSFoLeaseUpdateFailedRangeNotFound

major
releases

DHCPSFoLeaseUpdateFailedRangeNotFound Implicitly cleared: false
(4983)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedRangeNotFound
Raised on class:
Description: This alarm is raised when a range not found lease update received from the failover peer cannot
be processed successfully. No valid include range for this lease could be found.
received from the failover peer, cannot be processed successfully. No valid include range for this lease could be
found. Please ensure all configuration is correct.
Table 39-213 DHCPSFoLeaseUpdateFailedSubnetNotFound

major
releases

DHCPSFoLeaseUpdateFailedSubnetNotFound Implicitly cleared: false
(4984)
Type: configurationAlarm (11) DHCPSFoLeaseUpdateFailedSubnetNotFound
Raised on class:
Description: This alarm is raised when a subnet not found lease update received from the failover peer cannot
be processed successfully. No valid subnet for this lease could be found.
Remedial action: This alarm indicates the Local DHCP Server Failover lease update has failed. Packet received
from the failover peer, cannot be processed successfully. No valid subnet for this lease could be found. Please
Table 39-214 DiamAppMessageDropped

releases

DiamAppMessageDropped Implicitly cleared: false
(5175)
Type: processingErrorAlarm (81) diamAppMessageDropped (2091)
Package: diameter
Raised on class:
diameter.DiameterPeer
Description: The alarm is raised when the Diameter protocol has dropped a message
Remedial action: The recovery action depends on the exact cause of the failure. See the Additional Text field
in the Alarm Info form for a specific cause for the failure.
Table 39-215 DiamAppSessionFailure

releases
Name: DiamAppSessionFailure (5410) Severity: minor Unspecified

Package: ressubscr Default probable cause:
Raised on class: diamAppSessionFailure (2118)
ressubscr.ResidentialSubscriberInstance
Description: The alarm is raised when the Diameter protocol has a session failure.
Remedial action: The recovery action depends on the exact cause of the failure. See the Additional Text field
in the Alarm Info form for a specific cause for the failure.
Table 39-216 DiskCapacityProblem

releases
Name: DiskCapacityProblem (144) Severity: variable Unspecified

Type: storageAlarm (25) Implicitly cleared: false
Raised on class: diskCapacityProblem (115)
equipment.FlashMemory
Description: The alarm is raised when a compact flash capacity threshold value on an NE is reached or
exceeded. The alarm condition is detected during resynchronization or when a tnmxEqFlashDiskFull trap is
received. The threshold value is not configurable. The severity of the alarm depends on the percentage of disk
capacity used, as listed below: - 75 percent, Minor - 90 percent, Major - 100 percent, Critical
Remedial action: The usage of the compact flash device must be analysed and old or redundant files must be
removed. This operation must be executed using the CLI interface on the NE.
Table 39-217 DryContactAlarm

releases
Name: DryContactAlarm (460) Severity: variable Unspecified

Type: dryContactAlarm (47) Implicitly cleared: false
Raised on class: dryContactExternalAlarmRaised (351)
equipment.DryContact
Description: The alarm is raised when a device detects a dry contact alarm condition.
Remedial action: The remedial action for this alarm depends on the condition that the dry contact alarm is
configured.
Table 39-218 DS1E1Loopback

releases
Name: DS1E1Loopback (409) Severity: warning Unspecified

Raised on class: ds1e1Loopback (305)
tdmequipment.DS1E1ChannelSpecifics
Description: The alarm is raised when an NE reports that a specific DS1 or E1 channel has a loopback alarm
condition.
Table 39-219 DS3E3Loopback

releases
Name: DS3E3Loopback (408) Severity: warning Unspecified

Raised on class: ds3e3Loopback (304)
tdmequipment.DS3E3ChannelSpecifics
Description: The alarm is raised when an NE reports that a specific DS3 or E3 channel has a loopback alarm
condition.
Table 39-220 DscPlatformLicenseKeyExpiredAlarm

releases

DscPlatformLicenseKeyExpiredAlarm Implicitly cleared: false
(1133)
Type: EpcAlarm (59)
Package: lte Default probable cause:
Raised on class: DscPlatformLicenseKeyExpired (841)
lte.DynamicServicesControllerInstance
Description: The alarm is raised when the DSC platform license key is expired.
Remedial action: Contact Alcatel-Lucent support to obtain new DSC license key
Table 39-221 DscPlatformLicenseKeyExpiringAlarm

releases

DscPlatformLicenseKeyExpiringAlarm Implicitly cleared: false
(1134)
Type: EpcAlarm (59) DscPlatformLicenseKeyExpiring (842)
Package: lte
Raised on class:
Description: The alarm is raised when the DSC platform license key is expiring.
Table 39-222 DscPlatformLicenseKeyHighWaterAlarm

major
releases

DscPlatformLicenseKeyHighWaterAlarm Implicitly cleared: false
(1135)
Type: EpcAlarm (59) DscPlatformLicenseKeyHighWaterMarkCrossed
Package: lte (843)
Raised on class:
Description: The alarm is raised when the 5780 DSC license key crosses the high watermark for a specified
threshold.
Table 39-223 DscPlatformLicenseKeyLowWaterAlarm

major releases

DscPlatformLicenseKeyLowWaterAlarm Implicitly cleared: false
(1136)
Type: EpcAlarm (59) DscPlatformLicenseKeyLowWaterMarkCrossed
Package: lte (844)
Raised on class:
Description: The alarm is raised when the 5780 DSC license key crosses the low watermark for a specified
threshold.
Table 39-224 DscPlatformLicenseKeyThresholdReachedAlarm

major
releases

DscPlatformLicenseKeyThresholdReachedAlarm Implicitly cleared: true
(1137)
Type: EpcAlarm (59) DscPlatformLicenseKeyThresholdReached
Package: lte (845)
Raised on class:
Description: The alarm is raised when the 5780 DSC license key reaches a specified threshold.
Remedial action: NContact Alcatel-Lucent support to obtain new DSC license key
Table 39-225 DualEndedLossNotSupported

releases

DualEndedLossNotSupported Implicitly cleared: true
(1194)
Type: oamAlarm (18) dualEndedLossNotSupported (895)
Package: ethernetoam
Raised on class:
ethernetoam.MaintAssociation
Description: The alarm is raised when a MEP that does not support Y1731 Dual Ended Loss test is
participating in a CFM Continuity Check test that has Y1731 Dual Ended Loss test enabled.
Remedial action: Informational - The alarm is raised when at least one MEP that does not support Y1731
Dual Ended Loss test is participating in a CFM Continuity Check test that has Y1731 Dual Ended Loss test
enabled.
Table 39-226 DualEndedLossThresholdAlarm

releases

DualEndedLossThresholdAlarm Implicitly cleared: true
(1195)
Type: oamAlarm (18) dualEndedLossThresholdExceeded (896)
Raised on class:
ethernetoam.Mep
Description: The alarm is raised when a MEP reports that either the Local or Remote loss ratio has exceeded
the configured threshold for the specified remote MEP.
Remedial action: Informational - The alarm is raised when a MEP reports that either the Local or Remote loss
ratio has exceeded the configured threshold for the specified remote MEP.
Table 39-227 DualMaster

Name: DualMaster (420) Severity: major Unspecified

Package: srrp Default probable cause: dualMaster (313)
Raised on class: srrp.Instance
Description: The alarm is raised when the local and remote SRRP instances are in the master state.
Remedial action: Shut down one of the peer SRRP instances, modify the priority to a larger value (lower
priority) and then turn it up.
Table 39-228 duplicateAdminGroupName

releases
Name: duplicateAdminGroupName Severity: warning Unspecified

Package: svt duplicateNameExists (1953)
Raised on class:
svt.TunnelAdminGroup
Description: The alarm is raised when two or more global Admin Groups share the same group name.
Remedial action: Either change the admin group name to a different value, or delete this one and recreate it
with a new name.
Table 39-229 DuplicateIpAddress

releases
Name: DuplicateIpAddress (5129) Severity: warning Unspecified

Package: rtr Default probable cause:
Raised on class: duplicateIpAddress (2059)
rtr.VirtualRouterIpAddress
Description: The alarm is raised when a duplicate routing instance IP Address is found on two or more
different NEs.
Remedial action: Verify to ensure the duplicate routing instance IP Address is not for dual homing or network
redundancy configuration. Navigate to the Virtual Router Duplicate IP Addresses listing: (Tools -> Network
Resources -> Virtual Router Duplicate IP Addresses), for more information on the duplicate IP address.
Table 39-230 DuplicateRole

releases
Name: DuplicateRole (470) Severity: major Unspecified

Raised on class: twoElementsWithSameRole (356)
Description: The alarm is raised when a slot has the same primary or secondary role as another slot in the
stack. The slot subsequently enters pass-through mode.
Remedial action: Login to switch console, check and correct configuration and reload stack.
Table 39-231 DuplicateRouteDistinguisher

releases

DuplicateRouteDistinguisher Implicitly cleared: true
(4996)
Package: l3fwd duplicateRouteDistinguisher (2050)
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised if a duplicate Route Distinguisher is configured on two different NE’s on
different VPRN Service.
Remedial action: The Route Distinguisher has been configured on another L3 VPRN Site. Please check the
value of Route Distinguisher under Routing tab of VPRN Routing Instance.
Table 39-232 DuplicateSlot

releases
Name: DuplicateSlot (468) Severity: major Unspecified

Raised on class: duplicateSlotNINumber (354)
Description: The alarm is raised when a slot has the same slot number as another stack element. The slot
must relinquish its operational status because it has a higher election key, based on the up time, slot number,
and MAC address. Both slots subsequently enter pass-through mode.
Remedial action: Login to switch console, correct the slot number and reload stack.
Table 39-233 DuplicateVrfPolicy

releases
Name: DuplicateVrfPolicy (229) Severity: warning Unspecified

Package: l3fwd Default probable cause:
Raised on classes: duplicateVrfPolicyExists (177)
l3fwd.ServiceSiteImportPolicy
l3fwd.ServiceSiteExportPolicy
Description: The alarm is raised when the 5620 SAM detects a duplicate VRF policy in a VPRN. The alarm
information includes the VRF policy ID and type, and information about the service site. Note: starting from
SAM 12.0 R1, SAM no longer raise this alarm since it is not much useful but has performance issue.
Remedial action: A configuration error has been made which must be corrected. The duplicate VRF policy
must be deleted. Note: starting from SAM 12.0 R1, SAM no longer raises this alarm.
Table 39-234 DuplicateVrfTarget

releases
Name: DuplicateVrfTarget Severity: warning Unspecified

Package: l3fwd duplicateVrfTargetExists (178)
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the 5620 SAM detects a duplicate VRF target in a VPRN. The alarm
information includes the VRF policy ID and type, and information about the service site.
Remedial action: A configuration error has been made which must be corrected. The duplicate VRF target
must be deleted.
Table 39-235 DyingGasp (equipment)
releases
Name: DyingGasp (1164) Severity: major Unspecified

Type: communicationsAlarm (4) Implicitly cleared: false
Package: equipment Default probable cause: dyingGaspSignal
equipment.CardSlot
Description: The alarm is raised when a Dying Gasp trap is received to indicate a power failure.
Remedial action: This alarm is raised by the node just before going down, this might be due to the fact that
the power supply connected to the node is down or failed. Please make sure the power supply to the specific
node is proper.
Table 39-236 DyingGasp (netw)

releases
Name: DyingGasp (1164) Severity: major Unspecified

Package: netw Default probable cause: dyingGasp
netw.NetworkElement
Description: The alarm is raised when a 7210 SAS node has loss of power.
Remedial action: This alarm is raised by the node just before going down, this might be due to the fact that
the power supply connected to the node is down or failed. Please make sure the power supply to the specific
node is proper.
Table 39-237 DyingGaspSignal

releases
Name: DyingGaspSignal (623) Severity: major Unspecified

Package: equipment Default probable cause: dyingGaspSignal
Description: The alarm is raised when a Dying Gasp signal is received from a remote 7210 SAS to indicate a
power loss.
Clearing condition: (’state’ EQUAL ’Link Up’)
Remedial action: This alarm is raised by the node to indicate that one of the neighbouring node which is
directly connected to the specific port of this node has signaled that it’s going down. This might be due to the
fact that the power supply connected to the remote node is down or failed, please make sure the power supply
to that specific remote node through the specific port (as found in the additional text field) is proper.
Table 39-238 DynSvcIdRangeConflict

releases
Name: DynSvcIdRangeConflict Severity: warning Unspecified

Type: DynSvcIdRangeConflict Default probable cause:
(126) DynSvcIdRangeConflict (1584)
Package: dynsvc
Raised on class:
dynsvc.DynSvcNeConfig
Description: The alarm is raised when the configured Dynamic Service ID Range has conflicts with one or
more Range Policies.
Remedial action: A possible conflict currently exists between the Dynamic Service ID Range specified for this
NE and one or more Range Policy entries. To clear the alarm, one of the two must change. This alarm may be
benign if the the conflicting Range Policy and Dynamic Service ID Range were intended.
Table 39-239 DynSvcSapFailure

releases
Name: DynSvcSapFailure (4421) Severity: warning Unspecified

Type: DynSvcSapFailure (127) Implicitly cleared: false
Package: dynsvc Default probable cause: DynSvcSapFailure
dynsvc.DynSvcNeConfig
Description: The DynSvcSapFailure alarm is raised when a Dynamic Services service SAP creation,
modification or removal failed. If the SAP does not exist at the time of this notification, the value ’invalid portid’
is put in the alarms sapPortId.’
Remedial action: Ensure that the RADIUS server and python script specified by the Dynamic Service Policy is
functioning correctly.
Table 39-240 EarlyWarning (mwa)

releases
Name: EarlyWarning (681) Severity: variable Unspecified

Package: mwa Default probable cause: EarlyWarning
mwa.PortTermination
Description: The alarm is raised when a MPT detects an early warning event.
information.
Table 39-241 EarlyWarning (radioequipment)

releases
Name: EarlyWarning (681) Severity: variable Unspecified

Raised on class: earlyWarning (496)
Description: The alarm is raised when an MSS detects an early warning event.
Table 39-242 EcIdRxTxOrMacModified

releases
Name: EcIdRxTxOrMacModified Severity: minor Unspecified

Package: mpr ecIdRxTxOrMacModified (568)
Raised on class: mpr.MprVll
Description: The alarm is raised when something other than the 5620 SAM deletes a service cross-connect
and creates a new service cross-connect whose MAC address, EC ID Rx, or EC ID Tx value does not match
the value in the original service.
Table 39-243 EMSystemTimeOut

releases
Name: EMSystemTimeOut Severity: warning Unspecified

Type: communicationsAlarm Default probable cause: excessiveResponseTime
(4) (1141)
Package: hip
Raised on class:
hip.EMSystem
Description: The alarm is raised when the time out is raised (the SAM to EMS request take too long time)
Remedial action: NA#Remedial actions for modelRelease: LR_13_03, supported release: , version: 2.03
Table 39-244 EncapsulationTypeIncompatible

releases

EncapsulationTypeIncompatible Implicitly cleared: false
(250)
Type: configurationAlarm (11) sapEncapsulationTypeIncompatible (189)
Package: vll
Raised on class: vll.Vll
Description: The alarm is raised when the encapsulation types of two SAPs in the same Ipipe are
mismatched.
Raising condition: (’encapsulationTypeIncompatible’ EQUAL ’true’)
Clearing condition: (’encapsulationTypeIncompatible’ EQUAL ’false’)
Remedial action: Ensure that the encapsulation type of any two SAPs in I-Pipe service are not mismatched.
Table 39-245 EndpointActiveObjectChanged

releases

EndpointActiveObjectChanged Implicitly cleared: false
(437)
Type: redundancyAlarm (52) ServiceEndpointSwitchover (1442)
Package: service Applicable probable causes:
Raised on class: service.Endpoint ServiceEndpointSwitchover
ForceSwitchover
Description: The alarm is raised when an automatic or manual endpoint switchover occurs.
Table 39-246 EndpointMacLimitReached

releases
Name: EndpointMacLimitReached Severity: warning Unspecified

Type: resourceAlarm (28) Default probable cause:
Package: vpls resourceLimitReached (131)
Raised on class: vpls.Endpoint
Description: The alarm is raised when the 5620 SAM receives the svcEndpointMacLimitAlarmRaised trap
from an NE, which indicates that the number of MAC addresses stored in the FDB for the endpoint exceeds
the high watermark for the site FIB. The number of MAC addresses includes the static MAC addresses on the
endpoint and the learned MAC addresses in the spoke SDPs that are associated with the endpoint. The alarm
clears when the 5620 SAM receives the svcEndpointMacLimitAlarmCleared trap from the NE.
Remedial action: Increase the high water mark for the site FIB to allow more entries to be added.
Table 39-247 EPSAbnormalState

releases
Name: EPSAbnormalState (3932) Severity: variable Unspecified

Type: epsAbnormalConditionAlarm Implicitly cleared: true
(113) Default probable cause: EPSProblem
Package: mpr (1515)
Raised on class: mpr.MPRProtection
Description: The alarm is raised when abnormal state resulted due to force switch/lockout operation in EPS
mode.
Remedial action: This alarm is raised when forced-switch/lockout command in EPS mode which led to an
abnormal condition.
Table 39-248 EPSPathDrillDownFailed

releases
Name: EPSPathDrillDownFailed Severity: major Unspecified

Type: EpcAlarm (59) Default probable cause:
Package: lte EPSPathDrillDownFailed (604)
Raised on class: lte.EPSPath
Description: The alarm is raised when the drilldown of an EPS path fails.
Raising condition: (’State’ EQUAL ’Failed’)
Clearing condition: (’State’ NOT EQUAL ’Failed’)
Remedial action: A configuration error has been made which must be corrected. The configured drill down
hint does not match the underlying transport connectivity.
Table 39-249 EPSPathReferencedObjectDeleted

releases

EPSPathReferencedObjectDeleted Implicitly cleared: true
(848)
Type: EpcAlarm (59) EPSPathReferencedObjectDeleted (605)
Package: lte
Raised on class:
lte.EPSPathComponent
Description: The alarm is raised when a referenced object is deleted.
Raising condition: (’componentPointer’ EQUAL ’\"\"’)
Clearing condition: (’componentPointer’ NOT EQUAL ’\"\"’)
Table 39-250 EthernetPortCrcFailure

releases
Name: EthernetPortCrcFailure (3629) Severity: major Unspecified

Package: ethernetequipment Default probable cause:
Raised on class: ethernetPortCrcFailure (1414)
ethernetequipment.EthernetPortSpecifics
Description: The alarm is raised when an Ethernet port CRC alarm condition is detected (Signal Degradation
Threshold or Signal Failure Threshold exceeded).
Remedial action: One of the following conditions exists on the referenced physical interface which must be
corrected. A cable/fiber fault exists which must be corrected - check to ensure that the cable is not faulty and is
properly connected. The port is faulty - run diagnostics on the port to determine the nature of the fault. If the
problem cannot be resolved swap the card containing the port with a card which is known be functional.
Table 39-251 EthernetPortInternalAlarm

releases
Name: EthernetPortInternalAlarm (3630) Severity: major Unspecified

Raised on class: ethernetPortInternalAlarm (1415)
ethernetequipment.EthernetPortSpecifics
Description: The alarm is raised when an Ethernet port experiences excessive internal MAC tx errors. It is
generated only when downOnInternalError is enabled on the port.
Remedial action: This alarm indicates that the port (card) in question is likely faulty. Please replace the card
with a card known to be functional.
Table 39-252 EthernetTunnelDown

releases
Name: EthernetTunnelDown (771) Severity: major Unspecified

Raised on class: ethernetTunnelDown (547)
ethernettunnel.EthernetTunnel
Description: The alarm is raised when the aggregated Ethernet tunnel Operational State is Down.
Raising condition: ((’aggrEndPtOperationalState’ EQUAL ’Down’))
Clearing condition: ((’aggrEndPtOperationalState’ NOT EQUAL ’Down’))
Remedial action: Fix the error indicated in the alarm, e.g. port down, MEP down...
Table 39-253 ExcessiveEnvironmentTemparature (equipment)

releases

ExcessiveEnvironmentTemparature Implicitly cleared: true
(1118)
Type: equipmentAlarm (3) excessiveEnvironmentTemp (830)
Package: equipment
Description: The alarm is raised when MPT is overheated.
Table 39-254 ExcessiveEnvironmentTemparature (mpr)

releases

ExcessiveEnvironmentTemparature Implicitly cleared: true
(1118)
Type: communicationsAlarm (4) excessiveEnvironmentTemp (830)
Package: mpr
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when MPT is overheated.
Table 39-255 ExportPolicyNotFound

releases
Name: ExportPolicyNotFound (231) Severity: major Unspecified

Raised on class: exportPolicyDoesNotExist (179)
l3fwd.ServiceSiteExportPolicy
Description: The alarm is raised when a VRF export policy for a VPRN cannot be found. The alarm
information includes the policy ID. Note: starting from SAM 12.0 R1, SAM no longer raise this alarm since it is
not much useful but has performance issue.
Remedial action: A configuration error has occurred which must be corrected. The VRP export policy must be
created and distributed to the NE reporting the problem. Note: starting from SAM 12.0 R1, SAM no longer
raises this alarm.
Table 39-256 FanCommunicationProblem

releases

FanCommunicationProblem Implicitly cleared: true
(5424)
Type: communicationsAlarm (4) fanCommunicationProblem (2127)
Package: mpr
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when a communication problem with fan is detected.
Remedial action: The alarm is raised when FAN communication Problem is detected on the subrack. Refer
9500 Node Maintenance manual for remedial action information
Table 39-257 FanRPMAlarm

Name: FanRPMAlarm (1126) Severity: variable Unspecified

Type: equipmentAlarm (3) Implicitly cleared: false
Package: equipment Default probable cause: fanFailure (116)
Raised on class: equipment.Fan
Description: The alarm is raised when a fan alarm usage state is other than Normal.
Remedial action: The NE has detected internal temperatures which are abnormally high. This could be
caused by a failed fan unit or one or more dirty fan filters. Replacing the failed unit or filters should resolve the
problem. Alternately the environment that the NE is operating in may not be within specifications found in the
NE user guides.
Table 39-258 FIBHighOccupancy

releases
Name: FIBHighOccupancy (752) Severity: warning Unspecified

Type: resourceAlarm (28) Implicitly cleared: true
Package: equipment Default probable cause: FIBHighOccupancy
equipment.BaseCard
Description: The alarm is raised when the FIB occupancy on an IOM card changes from normal to high.
Table 39-259 FibOutOfSynch

releases
Name: FibOutOfSynch (625) Severity: critical Unspecified

Package: equipment Default probable cause: fibUpdateFailed
equipment.DaughterCard
Description: The alarm is raised when the FIB on an MDA is out of synchronization.
Table 39-260 FileTransferFailure

releases
Name: FileTransferFailure (8152) Severity: major Unspecified

Package: netw Default probable cause: fileTransferFailure
netw.NetworkElement
Description: The alarm is raised when SAM cannot transfer a file from a Network Element due to one or more
of the following causes: unreachable NE, remote file not found, authentication failure, file transfer interrupted,
or lack of available local storage space.
Remedial action: Investigation is required to resolve the following possible scenarios: SAM server has
connectivity issue with NE; insufficient disk space on the SAM server to accommodate the file transfer being
attempted; loss of connectivity to the NE during transfer; the FTP daemon on the NE may have stopped; FTP
security credential issues.
Table 39-261 FilterApplyPathProblem

releases
Name: FilterApplyPathProblem (4904) Severity: minor Unspecified

Package: filterprefixlist Default probable cause:
Raised on class: tFilterApplyPathProblem (1960)
filterprefixlist.PrefixListApplyPathMember
Description: The alarm is raised when a problem is encountered for a configured IP PrefixList apply-path rule.
Remedial action: Clear the alarm and verify the prefix-list configurations which might have reached the
maximum limit. Try reducing the prefix-list/ apply-path members.
Table 39-262 FilterEmbeddingOperStateChange

releases

FilterEmbeddingOperStateChange Implicitly cleared: false
(4973)
Type: configurationAlarm (11) tFilterEmbeddingOperStateChange (2030)
Package: aclfilter
Raised on class:
aclfilter.FilterEmbeddedRefTable
Description: The alarm is raised when the embedding oper state change is other than in-service.
Remedial action: The alarm is raised when the embedded filter operstate is other than inService. Remove
and reapply the embedding to make operstate as inService.
Table 39-263 FirmwareDownloadOnGoing (equipment)

releases

FirmwareDownloadOnGoing Implicitly cleared: true
(626)
Type: equipmentAlarm (3) firmwareDownloadOnGoing (465)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when a firmware download is in progress.
Remedial action: Informational - Firmware for the equipment is downloading.
Table 39-264 FirmwareDownloadOnGoing (mpr)

releases

FirmwareDownloadOnGoing Implicitly cleared: true
(626)
Type: equipmentAlarm (3) firmwareDownloadOnGoing (465)
Package: mpr
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when a firmware download is in progress.
Remedial action: Informational - Firmware for the equipment is downloading.
Table 39-265 FirmwareMismatchAlarm

releases
Name: FirmwareMismatchAlarm Severity: critical Unspecified

Type: firmwareAlarm (26) Default probable cause:
Package: equipment bootRomVersionMismatch (119)
Raised on class: Applicable probable causes:
equipment.Card bootRomVersionMismatch
fpgaVersionMismatch
Description: The alarm is raised when a device detects a mismatch between the firmware version and the
device software image. The alarm information includes the expected firmware version.
Remedial action: Either the firmware or the device SW must be upgraded to compatible versions. The image
(firmware or device SW) which is the oldest should be upgraded. Firmware must be upgraded using the NE’s
CLI. 5620 SAM can be used to upgrade the SW image on the device.
Table 39-266 FirmwareUpgradeAlarm

releases
Name: FirmwareUpgradeAlarm Severity: info Unspecified

Type: firmwareAlarm (26) Default probable cause: firmwareUpgraded
Package: equipment (169)
Description: The alarm is raised when a device automatically upgrades the firmware of a hot-inserted IOM or
CPM.
Table 39-267 FlowRouteInvalid

releases
Name: FlowRouteInvalid Severity: minor Unspecified

Type: ProtocolAlarm (1) Default probable cause: flowRouteInvalid
Package: bgp (1126)
Raised on class: bgp.Peer
Description: The alarm is raised when the received BGP flow route is invalid. The BGP peer dose not create
ip filter entry for the received flow route.
Remedial action: The NE has received an invalid flow route from a 3rd party appliance which is monitoring the
network for suspect traffic. This could be the result of corruption or a SW error on the 3rd party appliance.
Please refer to the documentation supplied with appliance for assistance.
Table 39-268 FlowspecUnsupportdComAction

releases

FlowspecUnsupportdComAction Implicitly cleared: false
(2933)
Type: ProtocolAlarm (1) unsupportdComAction (1127)
Package: bgp
Raised on class: bgp.Site
Description: The alarm is raised when the best route for a FlowSpec NLRI is received from a remote BGP
peer with an extended community action that is unsupported.
Table 39-269 ForceQTagForwardingMisconfiguration (epipe)

releases

ForceQTagForwardingMisconfiguration Implicitly cleared: true
(813)
Type: configurationAlarm (11) forceQTagForwardingInconsistent (576)
Package: epipe
Raised on class: epipe.Epipe
Description: The alarm is raised when two I-sites in a service use different Force Q Tag Forwarding values.
Raising condition: (’operationalFlags’anyBit’Force Q Tag Forwarding Inconsistent’)
Clearing condition: NOT ((’operationalFlags’anyBit’Force Q Tag Forwarding Inconsistent’))
Remedial action: Check configuration so that I-sites in the service use same Force Q-Tag Forwarding values.
Table 39-270 ForceQTagForwardingMisconfiguration (vpls)

releases

ForceQTagForwardingMisconfiguration Implicitly cleared: true
(813)
Type: configurationAlarm (11) forceQTagForwardingInconsistent (576)
Package: vpls
Description: The alarm is raised when two I-sites in a service use different Force Q Tag Forwarding values.
Raising condition: (’operationalFlags’anyBit’Force Q Tag Forwarding Inconsistent’)

Clearing condition: NOT ((’operationalFlags’anyBit’Force Q Tag Forwarding Inconsistent’))
Remedial action: Check configuration so that I-sites in the service use same Force Q-Tag Forwarding values.
Table 39-271 GenericInterfaceLinkDown

releases
Name: GenericInterfaceLinkDown Severity: major Unspecified

Package: genericne inoperableEquipment (8)
Raised on class:
genericne.GenericNeInterface
Description: The alarm is raised when the 5620 SAM detects a communication link failure on a GNE interface.
The alarm clears when the link returns to service.
Raising condition: (’Operational State’ EQUAL ’Down’)
Clearing condition: (’Operational State’ EQUAL ’Up’)
Remedial action: The Operational State of the generic NE interface is down. The physical port (near end or
far end) may have failed - this can be remedied by replacing the interface card in question. The physical links
may have been turned down administratively - re-enable the links. A cable failure or disconnect may have
occurred - please ensure that the cables are properly connected to the physical port and and that the cable has
not been damaged.
Table 39-272 GlobalAppProfileCreated

releases
Name: GlobalAppProfileCreated Severity: warning Unspecified

Type: ConfigurationAlarm (15) Default probable cause:
Package: aapolicy globalAppProfileMissing (1125)
Raised on class:
aapolicy.ApplicationProfile
Description: The alarm is raised when a global application profile to which a global transit IP policy is
referenced does not exist. The alarm notifies the user that a global application profile has been created.
Remedial action: Informational. A global Application Profile has been created; this object is referenced by a
Transit IP Policy or Transit Prefix Policy.
Table 39-273 globalLicenseViolation

releases
Name: globalLicenseViolation (2909) Severity: critical Unspecified

Package: ranlicense Default probable cause:
Raised on class: atLeastOneLicenseInViolation (1115)
ranlicense.RANLicenseManager
Description: The alarm is raised when at least one RAN license is in violation.
Remedial action: Provide a new LKDI license file with a further expiration date and/or more tokens.
Table 39-274 GneCommunicationAlarm

releases
Name: GneCommunicationAlarm Severity: variable Unspecified

Type: CommunicationAlarm (64) Default probable cause: User_Defined
Package: netw (558)
Raised on class:
netw.NetworkElement
Description: This user-definable alarm is raised against a generic NE when the 5620 SAM receives a trap
from the generic NE that is mapped to the alarm in a generic NE alarm catalogue. The alarm mapping defines
the Probable cause, Severity, and Implicitly cleared values, and optionally contains an extension that is
appended to the Name value.
Remedial action: This alarm is mapped from a GNE trap. Remedial action depends on the specific equipment
and trap definition.
Table 39-275 GneEnvironmentalAlarm

releases
Name: GneEnvironmentalAlarm Severity: variable Unspecified

Type: EnvironmentalAlarm (65) Default probable cause: User_Defined
Package: netw (558)
Raised on class:
netw.NetworkElement
Table 39-276 GneEquipmentAlarm

releases
Name: GneEquipmentAlarm (785) Severity: variable Unspecified

Type: EquipmentAlarm (66) Implicitly cleared: false
Package: netw Default probable cause: User_Defined
netw.NetworkElement
Table 39-277 GneMTIEAlarm (genericne)

releases
Name: GneMTIEAlarm (3633) Severity: variable Unspecified

Package: genericne Default probable cause: User_Defined
(558)
Raised on class:
genericne.GenericNeInterface
Table 39-278 GneMTIEAlarm (netw)

releases
Name: GneMTIEAlarm (3633) Severity: variable Unspecified

netw.NetworkElement
Table 39-279 GneProcessingErrorAlarm

releases
Name: GneProcessingErrorAlarm Severity: variable Unspecified

Type: ProcessingErrorAlarm (67) Default probable cause: User_Defined
Package: netw (558)
Raised on class:
netw.NetworkElement
Table 39-280 GneQualityOfServiceAlarm

releases
Name: GneQualityOfServiceAlarm Severity: variable Unspecified

Type: QualityOfServiceAlarm (68) Default probable cause: User_Defined
Package: netw (558)
Raised on class:
netw.NetworkElement
Table 39-281 GneServiceAlarm

releases
Name: GneServiceAlarm (788) Severity: variable Unspecified

Type: ServiceAlarm (69) Implicitly cleared: false
netw.NetworkElement
Table 39-282 GneSystemAlarm

releases
Name: GneSystemAlarm (789) Severity: variable Unspecified

Type: SystemAlarm (70) Implicitly cleared: false
netw.NetworkElement
Table 39-283 GneTransportAlarm

releases
Name: GneTransportAlarm (790) Severity: variable Unspecified

Type: TransportAlarm (71) Implicitly cleared: false
netw.NetworkElement
Table 39-284 GponPortInBandAlarm

major releases
Name: GponPortInBandAlarm Severity: major Unspecified

Type: Default probable cause:
gponInBandSignallingAlarm InBandSignallingNotEstablishedBetweenSARAndONT
(106) (1435)
Package: equipment
Raised on class:
equipment.GponPortSpecifics
Description: The alarm is raised when in-band signaling between the ONT and SAR for GPON statistics
collection is not established after 30 seconds of GPON port uptime.
Remedial action: Informational - Reachability between SAR and ONT devices has to be checked.
Table 39-285 GponPortInBandAlarmClear

major releases
Name: Severity: cleared Unspecified

GponPortInBandAlarmClear Implicitly cleared: true
(3698)
Type: InBandSignallingEstablishedBetweenSARAndONT
gponInBandSignallingAlarm (1436)
(106)
Package: equipment
Raised on class:
equipment.GponPortSpecifics
Description: The alarm is raised when in-band signaling between the ONT and SAR for GPON statistics
collection is established.
Table 39-286 GroupInSSMRange

releases
Name: GroupInSSMRange Severity: warning Unspecified

(11) STARGGroupInSSMRange (147)
Package: pim
Raised on class: pim.Site
Description: The alarm is raised when an NE receives a PIM register, PIM (*,G) assert, PIM (*,G) join/prune,
or an IGMP local membership message for a group defined in the SSM address range.
Remedial action: Informational - no corrective action required
Table 39-287 GwAcrFailuresAlarmMajor

releases
Name: GwAcrFailuresAlarmMajor Severity: major Unspecified

Package: lte connectionDown (2)
Raised on class: lte.AgwRfPeer
Description: A tmnxMobGwAcrFailuresAlarmMajor is generated when 2 ACR transmission failures occur in a

10 second interval or 5 ACR transmission failures occur in a 60 second interval to the peer.
Remedial action: Informational - a threshold for Anonymous Communication Rejection transmission failures
has been exceeded. If the condition persists please contact Alcatel-Lucent support for assistance.
Table 39-288 GwCdfDownAlarm

releases
Name: GwCdfDownAlarm (2956) Severity: minor Unspecified

Package: lte Default probable cause: connectionDown
lte.RfReferencePoint
Description: A tmnxMobGwCdfDownAlarm notification is generated when both the primary and the secondary
Charging Data Functions (CDFs) are down for active Rf diameter sessions
Remedial action: The Charging Data Functions (primary and secondary) are down for a Rf reference point.
The CDF function appears down for one of the following reasons: the underlying IP or physical interface is
down, the far end diameter peer is down or the underlying transport between this NE and the peer NE is down.
To resolve the issue ensure that the IP/physical interface is up, check that the far end diameter peer is
operational and check that the underlying transport network is up.
Table 39-289 GwCfCapacityAlarmMajor

releases
Name: GwCfCapacityAlarmMajor Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: resourceFull
Package: lte (53)
Raised on class:
lte.AGWReferencePoint
Description: A tmnxMobGwCfCapacityAlarmMajor notification is generated when compact flash capacity

reaches 95% limit.
Remedial action: The compact flash device of the MGW is approaching capacity. The contents of the device
must be analysed to identify redundant content which can be deleted.
Table 39-290 GwCfCapacityAlarmMinor

releases
Name: GwCfCapacityAlarmMinor Severity: minor Unspecified

Package: lte (53)
Raised on class:
lte.AGWReferencePoint
Description: A tmnxMobGwCfCapacityAlarmMinor notification is generated when compact flash capacity

reaches 85% limit
Remedial action: The compact flash device of the MGW is approaching capacity. The contents of the device
must be analysed to identify redundant content which can be deleted.
Table 39-291 GwDdnThrottlingStart

releases
Name: GwDdnThrottlingStart (4630) Severity: warning Unspecified

Raised on class: downLinkThrottling (1897)
lte.SigAGWGTPPMIPPeer
Description: A GwDdnThrottlingStart notification is generated when the serving gateway (SGW) starts
throttling the Downlink Data Notification (DDN) for the low priority traffic towards a peer node (SGSN/MME).
Remedial action: The serving gateway (SGW) starts throttling the Downlink Data Notification (DDN) for the
low priority traffic towards a peer node (SGSN/MME). When the throttling duration is passed, the SGW will stop
throttling the DDN.
Table 39-292 GwDdnThrottlingStop

releases
Name: GwDdnThrottlingStop (4631) Severity: warning Unspecified

Raised on class: downLinkThrottling (1897)
lte.SigAGWGTPPMIPPeer
Description: A GwDdnThrottlingStop notification is generated when the serving gateway (SGW) stops
throttling the Downlink Data Notification (DDN) for the low priority traffic towards a peer node (SGSN/MME).
Remedial action: The serving gateway (SGW) stops throttling the Downlink Data Notification (DDN) for the
low priority traffic towards a peer node (SGSN/MME). When another throttling instruction is received from a
peer node, the SGW will start throttling the DDN.
Table 39-293 GwGtpPriSrvGrpStateChange

releases

GwGtpPriSrvGrpStateChange Implicitly cleared: true
(3635)
Type: EpcAlarm (59) GwGtpPriSrvGrpDown (1419)
Package: lte
Raised on class: lte.EPCGateway
Description: An alarm is raised when there has been a change in GPRS Tunneling Protocol (GTP) Prime
Server state for all mobile system groups.
Remedial action: If a GTP Prime server group state is down, CDR packets will be written to CDR files until at
least one server becomes available.
Table 39-294 GwPoolCapacityAlarmMajor

releases
Name: GwPoolCapacityAlarmMajor Severity: major Unspecified

Type: EpcAlarm (59) Default probable cause: Threshold
Package: lte (2104)
Raised on class: lte.IpPool
Description: A tmnxMobGwPoolCapacityAlarmMajor notification is generated when either the IPv4 or IPv6

address pool usage reaches 95% of the pool size.
Remedial action: The IPv4 or IPv6 address pool usage reached 95% of the pool size. Need to look at
increasing the address pool size.
Table 39-295 GwPoolCapacityAlarmMinor

releases
Name: GwPoolCapacityAlarmMinor Severity: minor Unspecified

Type: EpcAlarm (59) Default probable cause: Threshold
Package: lte (2104)
Raised on class: lte.IpPool
Description: A tmnxMobGwPoolCapacityAlarmMinor notification is generated when either the IPv4 or IPv6

address pool usage reaches 85% of the pool size.
Remedial action: Informational: The IPv4 or IPv6 address pool usage reached 85% of the pool size. Need to
closely monitor the usage.
Table 39-296 GwRadGroupFail

releases
Name: GwRadGroupFail (3636) Severity: major Unspecified

Type: EpcAlarm (59) Implicitly cleared: false
Package: lte Default probable cause: EPSGroupDown
lte.EPCGateway
Description: A tmnxMobGwRadGrpFailAlarm notification is generated when all the radius servers have failed
in the radius server group.
Remedial action: The Radius server(s) which are configured in the Radius Server are unreachable. This
problem may occur in a number of different scenarios. The server(s) may have become unresponsive - please
refer to the Radius server documentation for assistance. The network connectivity to the server(s) may have
been lost - please investigate why the underlying transport network is unreliable.
Table 39-297 GwRadPeerFail

releases
Name: GwRadPeerFail (3682) Severity: major Unspecified

Type: EpcAlarm (59) Implicitly cleared: false
Package: lteradius Default probable cause: EPSPeerDown
lteradius.PdnRadiusPeer
Description: The alarm is raised when the 5620 SAM receives a tmnxMobGwRadPeerFailAlarm notification in
response to a RADIUS server failure.
Remedial action: A Radius peer is operationally down for one of the following reasons: the underlying IP or
physical interface is down, the far end peer is down or the underlying transport between this NE and the peer
NE is down. To resolve the issue ensure that the IP/physical interface is up, check that the far end peer is
operational and check that the underlying transport network is up.
Table 39-298 HardwareBootFailure

releases

HardwareBootFailure
Type: softwareAlarm (19) Default probable cause:
softwareBootProblemDueToHardwareIssues (92)
Package: sw
Raised on class:
sw.CardSoftware
Description: The alarm is raised when an NE fails to boot because of a hardware problem.
Remedial action: Please contact Alcatel-Lucent support for assistance.
Table 39-299 HardwareRedundancyAlarm

releases
Name: HardwareRedundancyAlarm Severity: major Unspecified

Package: equipment primaryCpmFailure (121)
Raised on class:
equipment.ControlProcessor
Description: The alarm is raised when the primary CPM fails.
Remedial action: The CPM card in the chassis may have suffered a failure. Remove and reset the card in
question. If this does not resolve the problem replace the card.
Table 39-300 HashLabelMismatch (svt)

releases
Name: HashLabelMismatch Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: hashLabelMismatch
Package: svt (826)
Raised on class:
svt.SdpBinding
Description: The alarm is raised when an SDP binding hash label is enabled and the return SDP binding hash
label is disabled. If this misconfiguration causes the mismatch of the operational hash label on both sides, the
receiving site will drop the data packets as a result. This alarm is cleared when the hash label is either enabled
or disabled on both sides.
Remedial action: The hash label must be enabled or disabled on both ends of the SDP
Table 39-301 HashLabelMismatch (vprn)

releases
Name: HashLabelMismatch Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: hashLabelMismatch
Package: vprn (826)
Raised on class: vprn.Vprn
Description: The alarm is raised when the hash label is enabled on a VPRN site and disabled on another site
in the service.
Remedial action: A configuration error has occurred which must be corrected. The hash label must be
enabled or disabled on both ends of the SDP
Table 39-302 HashLabelSignalCapabilityMismatch
releases

HashLabelSignalCapabilityMismatch Implicitly cleared: true
(3327)
Type: configurationAlarm (11) hashLabelSignalCapabilityMismatch (1163)
Package: svt
Raised on class: svt.SdpBinding
Description: The alarm is raised when an SDP binding hash label signal capability is enabled and the return
SDP binding hash label signal capability is disabled or not supported. If this misconfiguration causes the
mismatch of the operational hash label on both sides, the receiving site will drop the data packets as a result.
This alarm is cleared when the hash label signal capability is either enabled or disabled on both sides.
Remedial action: The hash label signal capability must be enabled or disabled on both ends of the SDP
Table 39-303 hdmAlarmListenerFailure

releases

hdmAlarmListenerFailure Implicitly cleared: true
(6305)
Type: communicationsAlarm communicationsSubsystemFailure (915)
(4)
Package: femto
Raised on class:
femto.HDMCluster
Description: This alarm indicates a communication issue with hdmAlarmListenerFailure Listener of HDM.
Table 39-304 hdmDashboardAlarmListenerFailure

releases

hdmDashboardAlarmListenerFailure Implicitly cleared: true
(6306)
Type: communicationsAlarm (4) communicationsSubsystemFailure (915)
Package: femto
Raised on class: femto.HDMCluster
Description: This alarm indicates a communication issue with hdmDashboardAlarmListenerFailure Listener of

HDM.
Table 39-305 hdmRegistrationListenerFailure

releases

hdmRegistrationListenerFailure Implicitly cleared: true
(6308)
Package: femto
Raised on class:
femto.HDMCluster
Description: This alarm indicates a communication issue with hdmRegistrationListenerFailure Listener of
HDM.
Table 39-306 hdmReRegistrationListenerFailure

releases

hdmReRegistrationListenerFailure Implicitly cleared: true
(6307)
Package: femto
Raised on class: femto.HDMCluster
Description: This alarm indicates a communication issue with hdmReRegistrationListenerFailure Listener of

HDM.
Table 39-307 hdmResynchroListenerFailure

releases

hdmResynchroListenerFailure Implicitly cleared: true
(6309)
Package: femto
Raised on class:
femto.HDMCluster
Description: This alarm indicates a communication issue with hdmResynchroListenerFailure Listener of HDM.
Table 39-308 hdmWebservicesFailure

releases

hdmWebservicesFailure Implicitly cleared: true
(6310)
Type: communicationsAlarm communicationsSubsystemFailure (915)
(4)
Package: femto
Raised on class:
femto.HDMCluster
Description: This alarm indicates a communication issue with hdmWebservicesFailure Listener of HDM.
Table 39-309 HighBER (mwa)

releases
Name: HighBER (682) Severity: variable Unspecified
Package: mwa Default probable cause: HighBER
mwa.PortTermination
Description: The alarm is raised when a MPT detects a high BER.
information.
Table 39-310 HighBER (radioequipment)

releases
Name: HighBER (682) Severity: variable Unspecified

Package: radioequipment Default probable cause: highBER
Description: The alarm is raised when an MSS detects a high BER.
Remedial action: The alarm is raised when an MSS detects a high BER.
Table 39-311 HighLevelRoutesReached

releases
Name: HighLevelRoutesReached Severity: minor Unspecified

Type: ProtocolAlarm (1) Default probable cause:
Package: l3fwd HighLevelRoutesReached (897)
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the number of routes in a VPRN exceeds the high threshold value. The
high threshold value is a percentage of the maximum number of routes specified in the VPRN configuration.
The percentage is derived by adding 100 to the threshold value in the VPRN configuration and dividing the
result by 2. The alarm information includes the number of routes and this calculated high threshold value.
Remedial action: Informational. The threshold configured should be revisited to ensure that it is not set to low
given the number of routes that are being received. If the threshold is set close to the maximum number of
routes supported by the NE then it is probable that there is an issue with another NE or VRF instance in the
network. If the problem persists please contact Alcatel-Lucent support for assistance.
Table 39-312 HistCorrDbSizeThresholdExceeded

releases

HistCorrDbSizeThresholdExceeded Implicitly cleared: true
(5169)
Type: configurationAlarm (11) HistCorrEventDBSizeIsNotSufficient (2089)
Package: histcorr
Raised on class:
histcorr.HistCorrPartitionManager
Description: The alarm is raised when the actual DB size consumed by Correlation Events exceeds the
threshold.
Remedial action: Correlation Events DB storage reached threshold or exceeded, increase "Max DB Size" in
Correlation Partition Manager GUI.
Table 39-313 HoldTimeInconsistent

releases
Name: HoldTimeInconsistent Severity: major Unspecified

Type: ProtocolAlarm (1) Default probable cause: holdTimeInconsistent
Package: bgp (575)
Description: The alarm is raised when a BGP site tries to establish a peering using a hold time that is less
than the configured strict hold time. The peering is rejected as a result.
Remedial action: A configuration error has occurred which must be corrected. The hold time must be set to a
value greater than the strict hold time.
Table 39-314 HostConnectivityLostRateExceeded

releases
Name: HostConnectivityLostRateExceeded Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: hostDown
Package: ressubscr (208)
Raised on class: ressubscr.ShcvSite Applicable probable causes:
hostDown
trapDropped
Description: The alarm is raised when the trapDroppedRaisesAlarm parameter is enabled and the maximum
allowed number of SHCV host connectivity loss events on a SAP is exceeded. The SHCV action in response
to the alarm is specified by the maxHostLostConnectivityRate parameter. If the specified action is to remove
the host information, the host information is removed and the connectivity of the host is not subsequently
verified.
Remedial action: This may be a transient error condition in the network or possible congestion or could be a
sign that the SHCV ping interval is too short. Verify the status of the network for those subscribers and the
service SHCV configuration.
Table 39-315 HostSharedFilterHighWatermarkAlarm

releases

HostSharedFilterHighWatermarkAlarm Implicitly cleared: true
(4974)
Type: configurationAlarm (11) HostSharedFilterHighWatermarkAlarm (2031)
Package: aclfilter
Raised on class:
aclfilter.FilterDefinition
Description: The alarm is raised when the number of dynamically allocated Host Shared Filters based on the
indicated filter reaches or exceeds the configured high watermark. This alarm is cleared when the number of
dynamically allocated Host Shared Filters drops to or below the configured low watermark of the indicated filter.
Remedial action: Please check the watermark configurations on the indicated filter and make an adjustment
accordingly.
Table 39-316 HouseKeeping (equipment)

releases
Name: HouseKeeping (1165) Severity: variable Unspecified

Package: equipment Default probable cause: houseKeeping
equipment.Equipment
Description: The alarm is raised when a HouseKeeping trap is received.
Table 39-317 HouseKeeping (mpr)

releases
Name: HouseKeeping (1165) Severity: minor Unspecified

Package: mpr Default probable cause: HouseKeeping
mpr.AbstractMprAux
Description: Defect detected by an house-keeping interface on AUX card.
Table 39-318 Idle2GUEsExceeded

releases
Name: Idle2GUEsExceeded Severity: info Unspecified

Type: communicationsAlarm (4) Default probable cause: ThresholdExceeded
Package: ltemme (2052)
Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of Idle 2G UEs exceeds the threshold that has been set by
the operator.
Raising condition: ((’2G Idle UEs Threshold’ NOT EQUAL ’0L’) AND (’2G Idle UEs’ > ’2G Idle UEs
Threshold’))

releases

Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of Idle 3G UEs exceeds the threshold that has been set by
the operator.
Threshold’))

releases

Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of 4G Idle UEs exceeds the threshold that has been set by
the operator.
Threshold’))
Table 39-321 IgmpGrpIfSapMaxGroupsLimitExceeded

major releases

IgmpGrpIfSapMaxGroupsLimitExceeded Implicitly cleared: false
(3979)
Type: configurationAlarm (11) IgmpGrpIfSapMaxGroupsLimitExceeded
Package: igmp (1556)
Raised on class:
igmp.GroupInterfaceSap
Description: This alarm is raised when an IGMP host subscribes to a new multicast group that cannot be
installed because the maximum number of active groups on the IGMP group interface SAP has already been
reached.
Remedial action: Increase the value of the ’maxGroups’ attribute in the parent IGMP group interface so that
the number of active IGMP groups stays under the configured threshold.
Table 39-322 IgmpGrpIfSapMaxGrpSrcLimExcd

releases

IgmpGrpIfSapMaxGrpSrcLimExcd Implicitly cleared: false
(4622)
Type: configurationAlarm (11) IgmpGrpIfSapMaxGrpSrcLimExcd (1890)
Package: igmp
Raised on class:
Description: This alarm is raised when an attempt is made to configure a group source for a group when the
number of group sources is equal to vRtrIgmpGrpIfSapMaxGrpSources, the maximum number of group
sources per group supported on the SAP.
Remedial action: Increase the value of the ’maxGrpSources’ attribute in the parent IGMP group interface so
that the number of active IGMP Group sources stays under the configured threshold.
Table 39-323 IgmpGrpIfSapMaxSourcesLimitExceeded

major releases

IgmpGrpIfSapMaxSourcesLimitExceeded Implicitly cleared: false
(3980)
Type: configurationAlarm (11) IgmpGrpIfSapMaxSourcesLimitExceeded
Package: igmp (1557)
Raised on class:
Description: This alarm is raised when an IGMP host subscribes to a multicast group with a source that
cannot be installed because the maximum number of active sources on the IGMP group interface SAP has
already been reached.
Remedial action: Increase the value of the ’maxSources’ attribute in the parent IGMP group interface so that
the number of active IGMP sources stays under the configured threshold.
Table 39-324 IgmpHostMaxGrpSrcsLimitExcd

releases

IgmpHostMaxGrpSrcsLimitExcd Implicitly cleared: false
(4623)
Type: configurationAlarm (11) IgmpHostMaxGrpSrcsLimitExcd (1891)
Package: igmp
Raised on class:
igmp.GrpInterface
Description: This alarm is raised when an attempt is made to configure a source for a group when the number
of group sources is equal to vRtrIgmpHostMaxGrpSources, the maximum number of group sources per group
supported on the host.
Remedial action: Increase the value of the ’maxGrpSources’ attribute in the parent IGMP group interface so
that the number of active IGMP Group sources stays under the configured threshold.
Table 39-325 IgmpSnpgGrpDroppedLimitExceeded (svt)

releases

IgmpSnpgGrpDroppedLimitExceeded Implicitly cleared: false
(392)
Type: SdpBindingAlarm (30) igmpSnpgGrpMaxNbrGrpsReached (292)
Package: svt
Raised on class:
svt.SdpBindingIgmpSnpgCfg
Description: The alarm is raised when an IGMP group is removed from an SDP binding because the number
of allowed IGMP groups specified by sdpBndIgmpSnpgCfgMaxNbrGrps is reached.
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP groups on the
SDP.
Table 39-326 IgmpSnpgGrpDroppedLimitExceeded (vpls)

releases

IgmpSnpgGrpDroppedLimitExceeded Implicitly cleared: false
(392)
Type: AccessInterfaceAlarm (32) igmpSnpgGrpMaxNbrGrpsReached (292)
Package: vpls
Raised on class:
vpls.L2AccessInterfaceIgmpSnpgCfg
Description: The alarm is raised when an IGMP group is removed from a SAP because the number of allowed
IGMP groups specified by sapIgmpSnpgCfgMaxNbrGrps is reached.
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP groups on the
SAP.
Table 39-327 IgmpSnpgGrpSrcLimitExceed

releases

IgmpSnpgGrpSrcLimitExceed Implicitly cleared: false
(4894)
Type: SdpBindingAlarm (30) IgmpSnpgGrpSrcLimitExceed (1952)
Package: svt
Raised on class:
Description: The alarm is raised when an IGMP group or source is dropped on a given SDP Bind because a
user configurable upper limit given by sdpBndIgmpSnpgCfgMaxNbrGrpSrcs is reached
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP group sources
on the SDP.
Table 39-328 IgmpSnpgGrpSrcLimitExceeded

releases

IgmpSnpgGrpSrcLimitExceeded Implicitly cleared: false
(4897)
Type: AccessInterfaceAlarm (32) igmpSnpgGrpMaxNbrGrpSrcsReached (1954)
Package: vpls
Raised on class:
Description: The alarm is raised when an IGMP group or source is dropped on a given SAP because a user
configurable upper limit given by sapIgmpSnpgCfgMaxNbrGrpSrcs is reached
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP Group sources
on the SAP.
Table 39-329 IgmpSnpgSrcDroppedLimitExceeded (svt)

releases

IgmpSnpgSrcDroppedLimitExceeded Implicitly cleared: false
(735)
Type: SdpBindingAlarm (30) igmpSnpgGrpMaxNbrSrcsReached (512)
Package: svt
Raised on class:
Description: The alarm is raised when an IGMP source is removed from an SDP binding because the number
of allowed IGMP sources specified by sdpBndIgmpSnpgCfgMaxNbrSrcs is reached.
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP sources on the
SDP.
Table 39-330 IgmpSnpgSrcDroppedLimitExceeded (vpls)

releases

IgmpSnpgSrcDroppedLimitExceeded Implicitly cleared: false
(735)
Type: AccessInterfaceAlarm (32) igmpSnpgGrpMaxNbrSrcsReached (512)
Package: vpls
Raised on class:
Description: The alarm is raised when an IGMP source is removed from a SAP because the number of
allowed IGMP sources specified by sapIgmpSnpgCfgMaxNbrGrps is reached.
Remedial action: This can be remedied by increasing the maximum number of allowed IGMP sources on the
SAP.
Table 39-331 IgpPrefixUnreachable

releases
Name: IgpPrefixUnreachable (5428) Severity: critical Unspecified

Type: virtualSwitchAlarm (136) Implicitly cleared: true
Package: dctr Default probable cause: IgpPrefixDown
dctr.AbstractVirtualSwitchGlobal
Description: The alarm is raised when the IGP Prefix is unreachable i.e. all the advertising routers are down.
Remedial action: This alarm can be cleared when the IGP Prefix for the Virtual Switch is reachable.
Table 39-332 IK4003104 - BB SLICE1 FAILURE DUE TO LOSS OF HS DATA LINK

releases
Name: IK4003104 (7963) Severity: major Unspecified

Type: equipmentAlarm (3) Specific problem: BB SLICE1 FAILURE DUE TO LOSS
Package: lte OF HS DATA LINK (1871)
Raised on class: Implicitly cleared: true
lte.BBCardSpecifics Default probable cause: equipmentMalfunction (698)
Description: This alarm indicates a failure of the BB to CB link, which leads to BB slice 1 failure.
Impact: LTE service is not possible on this BB’s slice 1.
Remedial action: Reset BB, reset CB, replace BB or CB if problem persists.

releases

Description: This alarm indicates a failure of the BB to CB link, which leads to BB slice 2 failure.

releases

Description: This alarm indicates a failure of the BB to CB link, which leads to BB Slice 3 failure
Table 39-335 IK4003107 - BB TEMPERATURE SENSOR FAILURE

releases

Type: equipmentAlarm (3) Specific problem: BB TEMPERATURE SENSOR
Package: lte FAILURE (1874)
Description: This alarm indicates a temperature sensor failure.
Impact: Temperature read from BB is not precise anymore and fan control cannot work normally. eNB may be
in condition of over temperature
Remedial action: Reset the BB in low traffic hours,if problem persists then replace the BB
Table 39-336 IK4004198 - GNSS FIRMWARE UPGRADE MISMATCH

releases
Name: IK4004198 (7967) Severity: critical Unspecified

Type: equipmentAlarm (3) Specific problem: GNSS FIRMWARE UPGRADE
Package: lte MISMATCH (1875)
lte.CBCardSpecifics Default probable cause: versionMismatch (405)
Description: The GNSS firmware is incompatible with the GNSS receiver component.
Impact: GNSS receiver cannot be programmed. Therefore satellite based synchronization cannot be
supported.
Remedial action: Check the GNSS type and ensure firmware to be downloaded is compatible with GNSS
component vendor and part..
Table 39-337 IK4004199 - GNSS FIRMWARE UPGRADE FAILURE
releases

Type: equipmentAlarm (3) Specific problem: GNSS FIRMWARE UPGRADE
lte.CBCardSpecifics Default probable cause: versionMismatch (405)
Description: The GNSS firmware fails to be successfully loaded to the GNSS receiver component
Impact: GNSS receiver cannot be programmed. Therefore satellite based synchronization cannot be
supported.
Remedial action: Check the GNSS type and ensure firmware to be downloaded is compatible with GNSS
component..
Table 39-338 IK4004200 - CB INIT GPS SELF SURVEY INPROGRESS

releases
Name: IK4004200 (7969) Severity: variable Unspecified

Type: equipmentAlarm (3) Specific problem: CB INIT GPS SELF SURVEY
Package: lte INPROGRESS (198)
lte.CBCardSpecifics Default probable cause: unknown (1097)
Description: This event indicates that the eNB has started a high accuracy GPS survey for OTDOA, which
normally takes 10 hours to complete.
Impact: No impact on eNodeB.
Remedial action: No action is required.
Table 39-339 IK4004201 - CB INIT GPS SELF SURVEY FAILURE

releases
Name: IK4004201 (7970) Severity: warning Unspecified

Type: equipmentAlarm (3) Specific problem: CB INIT GPS SELF SURVEY
lte.CBCardSpecifics Default probable cause: equipmentMalfunction
(698)
Description: This alarm indicates a high accuracy GPS survey has not been successfully completed after 24
hours.
Impact: Quality of GPS timing source is too low to support OTDOA geolocation.
Remedial action: Check GPS performance. Ensure good GPS receiver and GPS antenna is installed per
Alcatel-Lucent guidelines and located to have a full sky visibility with no local interference or multipath, then
power cycle the controller to restart survey. If GPS reception can’t be improved then disable OTDOA
(isGeoLocPhaseSyncAllowed="False), which will clear the alarm."
Table 39-340 IK4007209 - MME M3 SETUP FAILURE

releases

Type: qualityOfServiceAlarm Specific problem: MME M3 SETUP FAILURE
(82) (1878)
Package: lte Implicitly cleared: true
Raised on class: lte.Mce Default probable cause: unknown (1097)
Description: This alarm indicates that all the attempts initiated by the MCE to set up the M3 AP with a peer
MME have failed. The failure can be due to a MME reject (oam intervention or unknown cause) or it can be
due to a timer expiration on the MCE side because the MME has not answered on time.
Impact: The M3MmeAccess Operational state and Availability Status are set to {Disabled, Failed}. So the peer
MME concerned by the M3 setup failure can’t convey the signaling for eMBMS.
Remedial action: Correct the issue on the MME; when the issue is solved, lock then unlock the
M3MmeAccess.
Table 39-341 IK4007210 - MME M3 RESET ALL FAILURE

releases

Type: qualityOfServiceAlarm Specific problem: MME M3 RESET ALL FAILURE
(82) (1879)
Raised on class: lte.Mce Default probable cause: unknown (1097)
Description: This alarm indicates that all attempts to perform the MCE initiated M3 Reset/All have failed due
to no response of the MME.
Impact: The M3MmeAccess Operational state and Availability Status are set to {Disabled, Failed}. So the peer
MME concerned by the M3 setup failure can’t convey the signaling for eMBMS.
Remedial action: Correct the issue on the MME; when the issue is solved, lock then unlock the
M3MmeAccess.
Table 39-342 IK4007212 - ABS DUTY CYCLE IMPACT ON DL PRB CONSUMPTION

releases
Name: IK4007212 Severity: variable Unspecified

(7973) Specific problem: ABS DUTY CYCLE IMPACT ON DL PRB
Type: CONSUMPTION (1880)
qualityOfServiceAlarm Implicitly cleared: true
(82) Default probable cause: unknown (1097)
Package: lte
Raised on class:
lte.ENBEquipment
Description: This event indicates that an on-line change of the ABS duty cycle leads to increase the downlink
percentage of the PRB consumption beyond a configurable threshold called
eIcicDlAlarmOnAbsDutyCycleThresholdOnPrb in the object called eIcicAbsGenerationConf.
Impact: Increase of the downlink percentage on the PRB consumption
Table 39-343 IK4007214 - END OF INTERRAT CDMA HRPD ANR ACTIVE PHASE
releases

(7974) Specific problem: END OF INTERRAT CDMA HRPD ANR
ACTIVE PHASE (1881)
Type: Implicitly cleared: true
processingErrorAlarm Default probable cause: unknown (1097)
(81)
Package: lte
Raised on class:
lte.Cell
Description: This event indicates the end of the inter-RAT CDMA HRPD ANR active phase.
Table 39-344 IK4007215 - END OF INTERRAT CDMA 1xRTT ANR ACTIVE PHASE
releases

(7975) Specific problem: END OF INTERRAT CDMA 1xRTT ANR
Type: ACTIVE PHASE (1882)
processingErrorAlarm Implicitly cleared: true
Package: lte
Raised on class:
lte.Cell
Description: This event indicates the end of the inter-RAT CDMA 1xRTT ANR active phase.
Table 39-345 IK4007216 - CDMA HRPD NEIGHBOR RELATION MIB INSTANCE CANNOT BE REMOVED BY ANR
major
releases
Name: IK4007216 Severity: major Unspecified

(7976) Specific problem: CDMA HRPD NEIGHBOR RELATION MIB
Type: INSTANCE CANNOT BE REMOVED BY ANR (1883)
(81) Default probable cause: configurationOrCustomizationError (902)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates the HRPD neighbor relation MIB instance is not removed because the
removal is not allowed.
Impact: Mobility to this HRPD neighbor will be impacted.
Remedial action: Remove the existing HRPD neighbor relation so that it can be created by ANR under the
correct frequency.
Table 39-346 IK4007217 - CDMA 1xRTT NEIGHBOR RELATION MIB INSTANCE CANNOT BE REMOVED BY ANR
major
releases

(7977) Specific problem: CDMA 1xRTT NEIGHBOR RELATION MIB
INSTANCE CANNOT BE REMOVED BY ANR (1884)
processingErrorAlarm Default probable cause: configurationOrCustomizationError (902)
(81)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates the 1xRTT neighbor relation MIB instance is not removed because the
Impact: Mobility to this 1xRTT neighbor will be impacted.
Remedial action: Remove the existing 1xRTT neighbor relation so that it can be created by ANR under the
correct frequency.
Table 39-347 IK4007218 - HRPD NEIGHBOR RELATION REPLACEMENT

releases

(7978) Specific problem: HRPD NEIGHBOR RELATION
Type: REPLACEMENT (1885)
Package: lte
Raised on class: lte.Cell
Description: This event indicates that a HRPD Neighbor Relation has been replaced with another higher
priority neighbor.
Impact: Neighbor Relation replaced
Table 39-348 IK4007219 - 1xRTT NEIGHBOR RELATION REPLACEMENT

releases

(7979) Specific problem: 1xRTT NEIGHBOR RELATION
Type: REPLACEMENT (1886)
Package: lte
Description: This event indicates that a 1xRTT Neighbor Relation has been replaced with another higher
priority neighbor.
Impact: Neighbor Relation replaced
Table 39-349 IK4007220 - PCI CONFUSION CDMA NEIGHB CELLS

releases

(7980) Specific problem: PCI CONFUSION CDMA NEIGHB
Type: CELLS (1887)
operationalViolation (93) Implicitly cleared: true
Package: lte
Raised on class: lte.Cell Default probable cause:
configurationOrCustomizationError (902)
Description: This alarm indicates this cell is a victim of a CDMA PCI (pnOffset) confusion, it has neighbor cells
in a particular CDMA neighboring frequency that have the same PCI. A manual intervention is needed to solve
the problem. This issue may affect mobility procedures from LTE to CDMA.
Impact: Mobility procedure triggered in the eNB towards CDMA may be directed to a wrong neighboring cell.
Remedial action: The maintenance action is to change the PCI value of one of the neighbor CDMA cells to
resolve the conflict.
Table 39-350 IK4007221 - UTRAN NEIGHBOR RELATION MIB INSTANCE CANNOT BE REMOVED BY ANR
major
releases

Type: processingErrorAlarm (81) Specific problem: UTRAN NEIGHBOR RELATION MIB
Package: lte INSTANCE CANNOT BE REMOVED BY ANR (585)
lte.UtraFddNeighboringCellRelation Default probable cause:
Description: This alarm indicates the UTRAN neighbor relation MIB instance is not removed because the
Impact: Mobility to this Neighbor will be impacted.
Remedial action: Remove the existing UTRAN neighbor relation so that it can be created by ANR under the
correct frequency.
Table 39-351 IK4007222 - PCI OUT OF PCI ALLOWED LIST DETECTED UNDER RESOLUTION
releases
Name: IK4007222 Severity: warning Unspecified

(7982) Specific problem: PCI OUT OF PCI ALLOWED LIST DETECTED
Type: UNDER RESOLUTION (1888)
operationalViolation Implicitly cleared: true
(93) Default probable cause: configurationOrCustomizationError (902)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates a PCI out of the related pciAllowedList provided by the operator. The
eNodeB attempts for a resolution.
Impact: The impact is that the PCI used is not in the list provided by the operator, so may use a value reserved
for other topic.
Remedial action: This is due to an operator action. AutoPCI will solve the issue by changing the PCI. So
check that pciAllowedList is the one that you really need.
Table 39-352 IK4009210 - HW SW CAPABILITY CHECK RADIOCACENB FAILURE

releases
Name: IK4009210 (4689) Severity: minor Unspecified

Type: equipmentAlarm (3) Specific problem: HW SW CAPABILITY CHECK
Package: lte RADIOCACENB FAILURE (1889)
Raised on class: Default probable cause: equipmentMalfunction (698)
lte.CBCardSpecifics
Description: There is a mismatch between MIM configuration data RadioCacEnb and HW reported
capabilities detected.
Impact: The RadioCacEnb algorithm is limited to HW capabilities.
Remedial action: The operator has to check the MIM configuration of RadioCacEnb object and the installed
Controller Type. The MIM configuration must be aligned to the capability of the HW.
Table 39-353 IK4009211 - BB TO BB LOSS OF USER PLANE INTERBOARD CONNECTIVITY FOR LEGACY ENB
major
releases

(7983) Specific problem: BB TO BB LOSS OF USER PLANE
Type: INTERBOARD CONNECTIVITY FOR LEGACY ENB (1890)
equipmentAlarm (3) Implicitly cleared: true
Package: lte Default probable cause: unknown (1097)
Raised on class:
lte.BBCardSpecifics
Description: This alarm indicates a loss of User Plane inter-board connectivity between this BB board and the
peer BB board(s) indicated in the additional info.
Impact: Telecom: No impact on non-CA calls, Carrier Aggregation calls are no longer possible between this
board and the peer board indicated in the additional info.
Remedial action: Reset the board where the alarm is raised, If it does not clear the alarm, perform an eNodeB
reset; If it fails to recover, replace the board.
Table 39-354 IK4009212 - BB TO BB LOSS OF USER PLANE INTERBOARD CONNECTIVITY

major releases

(7984) Specific problem: BB TO BB LOSS OF USER PLANE
Type: equipmentAlarm INTERBOARD CONNECTIVITY (1891)
Raised on class:
lte.BBCardSpecifics
Impact: Telecom: No impact on non-CA calls, Carrier Aggregation calls are no longer possible between this
board and the peer board indicated in the additional info.
Table 39-355 IK4009213 - BB TO CB LOSS OF USER PLANE INTERBOARD CONNECTIVITY

major releases
Name: IK4009213 Severity: critical Unspecified

(7985) Specific problem: BB TO CB LOSS OF USER PLANE
Type: equipmentAlarm INTERBOARD CONNECTIVITY (1892)
Raised on class:
lte.BBCardSpecifics
CB board indicated in the additional info.
Impact: Telecom: The user plane GTP traffic for calls is interrupted.
Table 39-356 IK4009214 - CB LOSS OF USER PLANE INTERBOARD CONNECTIVITY

releases

Type: equipmentAlarm Specific problem: CB LOSS OF USER PLANE
(3) INTERBOARD CONNECTIVITY (1893)
Raised on class: Default probable cause: unknown (1097)
lte.CBCardSpecifics
Description: This alarm indicates a loss of User Plane inter-board connectivity between this CB board and the
Impact: Telecom: The user plane GTP traffic for calls is interrupted.
Remedial action: Reset the eNodeB, If it fails to recover, replace the board.
Table 39-357 IK4009215 - RFM TEMPORARY UNAVAILABLE

releases

Type: Specific problem: RFM TEMPORARY
processingErrorAlarm (81) UNAVAILABLE (1894)
Raised on class: lte.RFM Default probable cause: equipmentMalfunction
(698)
Description: This alarm indicates that the RFM cant execute the request because it is temporary unavailable.
The request will be repeated.
Impact: Telecom: Possible loss of telecom resources. OAM: No impact on OAM service.
Remedial action: No action is required
Table 39-358 IK4009216 - RFM UNAVAILABLE

releases

Type: processingErrorAlarm Specific problem: RFM UNAVAILABLE (1895)
Package: lte Default probable cause: equipmentMalfunction
Raised on class: lte.RFM (698)
Description: This alarm indicates the scenario failure due to no-response from the module.
Impact: Telecom: The telecom resources processed by the module are lost as the module is out of service.
OAM: No impact on OAM service.
Remedial action: Reset the module. If the alarm persist replace the module.
Table 39-359 IK4009217 - RFM PROCESSING ERROR

releases

Type: processingErrorAlarm Specific problem: RFM PROCESSING ERROR
(81) (1896)
(698)
Description: This alarm indicates the scenario failure due to RFM failure of processing.
Remedial action: Reset the module. If the alarm persist replace the module.
Table 39-360 IK4009218 - RFM NOT OPERATIONAL

releases

Type: processingErrorAlarm Specific problem: RFM NOT OPERATIONAL
(81) (1897)
(698)
Description: This alarm indicates that the RFM has been detected as not operational. In most situations a
second alarm related to this object should be already raised and an equipment reset already triggered.
Remedial action: If the eNodeB recovery action does not fix the alarm then reset the module. If the alarm
persists replace the module.
Table 39-361 IK4012078 - SCB INIT GPS SELF SURVEY FAILURE

releases

(7991) Specific problem: SCB INIT GPS SELF SURVEY
Type: equipmentAlarm FAILURE (1898)
Package: lte Default probable cause: equipmentMalfunction (698)
Raised on class:
lte.MODULE
Description: This alarm indicates that high accuracy GPS self survey for OTDOA sync has not been
successfully completed after 24 hours.
Impact: Synchronization accuracy too low to support OTDOA.
Remedial action: Check GPS performance. Ensure good GPS receiver and GPS antenna is installed per
Alcatel-Lucent guidelines and located to have a full sky visibility with no local interference or multipath, then
power cycle the controller to restart survey. If GPS reception can’t be improved then disable OTDOA sync
(isGeoLocPhaseSyncAllowed="False), which will clear the alarm."
Table 39-362 IK4012079 - SCB INIT GPS SELF SURVEY INPROGRESS

releases

(7992) Specific problem: SCB INIT GPS SELF SURVEY
Type: equipmentAlarm INPROGRESS (880)
Package: lte Default probable cause: equipmentMalfunction (698)
Raised on class:
lte.MODULE
Description: This event indicates that the eNB has started a high accuracy GPS survey for OTDOA, which
normally takes 10 hours to complete.
Table 39-363 IK4022001 - ERRONEOUS BACKHAUL ETHERNET PORT NAME

releases

(7993) Specific problem: ERRONEOUS BACKHAUL ETHERNET
Type: equipmentAlarm PORT NAME (1899)
Package: lte Default probable cause: configurationOrCustomizationError
lte.EthernetPort
Description: The backhaul port name defined in the configuration, received from the EMS by the eNB doesn’t
match with the identity of the ethernet backhaul port used by the eNB to connect to the EMS.
Impact: The eNB shall not apply the transport configuration if this configuration involves more than one
ethernet port and as long as the cabling doesn’t match the configuration. Else the risk will be to not be able to
reach anymore the eNB from the EMS
Remedial action: EthernetPort.ethernetPortName[0] value shall be modified in the EMS configuration.
Table 39-364 IK4022002 - BAD ETHERNET PORT POLICING CONFIGURATION

releases

(7994) Specific problem: BAD ETHERNET PORT POLICING
Type: CONFIGURATION (1900)
(82) Default probable cause: configurationOrCustomizationError
Package: lte (902)
Raised on class:
lte.EthernetPort
Description: This alarm indicates that the policing ingress CIR exceeds the Ethernet port speed, when
policing is requested on the Ethernet port.
Impact: The policing function has no effect.
Remedial action: Review the Ethernet port policing configuration and change if necessary.
Table 39-365 IK4022003 - ETHERNET PORT NOT OPERATIONAL
releases

Type: equipmentAlarm (3) Specific problem: ETHERNET PORT NOT
Package: lte OPERATIONAL (1901)
lte.EthernetPort Default probable cause:
Description: This alarm indicates that a feature involving the use of this Ethernet Port has been activated and
the Ethernet Port is not operational.
Impact: The feature that needs the use of the Ethernet Port cannot be activated.
Remedial action: The cabling shall be checked as well as the EMS configuration in order cabling and EMS
configuration match.
Table 39-366 IK4022004 - ETHERNET PORT OPERATIONAL

releases
Name: IK4022004 (7996) Severity: variable Unspecified

Type: equipmentAlarm (3) Specific problem: ETHERNET PORT
Package: lte OPERATIONAL (1902)
lte.EthernetPort Default probable cause: unknown (1097)
Description: This event indicates that a feature involving the use of this Ethernet Port has been activated and
the Ethernet Port is operational.
Impact: Traffic can flow through the Ethernet backhaul port.
Table 39-367 IK4022005 - ETHERNET PORT FAILURE

releases

Type: equipmentAlarm (3) Specific problem: ETHERNET PORT FAILURE
Package: lte (777)
lte.EthernetPort Default probable cause: inputOutputDeviceError
(703)
Description: This alarm indicates that the eNB failed to send/receive traffic through an Ethernet port.
Impact: No more traffic can go through the Ethernet port
Remedial action: The eNB Ethernet port equipement shall be checked and the eNB controller board or the
SFP will be replaced if necessary.
Table 39-368 IK4022006 - BAD ETHERNET PORT SHAPING CONFIGURATION

releases

(7998)
Specific problem: BAD ETHERNET PORT SHAPING
Type:
CONFIGURATION (1903)
qualityOfServiceAlarm
(902)
Raised on class:
lte.EthernetPort
Description: This alarm indicates that either the sum of the egress CIR per VLAN exceeds the Ethernet port
speed when shaping per VLAN is requested on this Ethernet port, either the egress CIR exceeds the Ethernet
port speed when shaping per port is requested on this Ethernet port.
Impact: The shaping function has no effect.
Remedial action: Review the Ethernet port shaping configuration and change if necessary.
Table 39-369 IK4305187 - TERTIARY CPRI PORT CONFIGURATION MISMATCH

releases
Name: IK4305187 Severity: minor Unspecified

(7999) Specific problem: TERTIARY CPRI PORT
Type: CONFIGURATION MISMATCH (1904)
Package: lte (902)
Raised on class:
lte.RRH
Description: This alarm indicates the misalignment between the tertiary CPRI port position in MIM
configuration and the detected tertiary CPRI port position, or the tertiary CPRI port is configured but the RRH
cant support 3 ports at all.
Impact: Telecom: the assigned cell is not operational. OAM: No impact on OAM service.
Remedial action: Verify and correct the configuration data or Verify and correct the hardware configuration, or
verify if RRH support 3 CPRI ports.
Table 39-370 IK4305188 - CELL OR SECTOR CONFIGURATION MISMATCH VERSUS HARDWARE

major releases

(8000) Specific problem: CELL OR SECTOR CONFIGURATION
Type: MISMATCH VERSUS HARDWARE (1905)
Package: lte (902)
Raised on class:
lte.Cell
Description: This alarm indicates inconsistency in the cell or corresponding sector configuration versus the
RRH hardware capacity
Impact: Telecom: the cell is not operational. OAM: No impact on OAM service.
Remedial action: Verify and correct the configuration data or Verify and correct the hardware configuration
Table 39-371 IK4305189 - LTE NEIGHBOR RELATION MIB INSTANCE CANNOT BE REMOVED BY ANR
major releases

(8001)
Specific problem: LTE NEIGHBOR RELATION MIB INSTANCE
Type:
CANNOT BE REMOVED BY ANR (603)
processingErrorAlarm
Package: lte Default probable cause: configurationOrCustomizationError (902)
Raised on class:
lte.Cell
Description: This alarm indicates the LTE neighbor relation MIB instance is not removed because the removal
is not allowed.
Impact: Mobility to this Neighbor will be impacted.
Remedial action: Remove the existing LTE neighbor relation so that it can be created by ANR under the
correct frequency.
Table 39-372 IK4305190 - LICENSE REQUIRED TO SUPPORT THE CONFIGURED LTECELL

releases

IK4305190 Specific problem: LICENSE REQUIRED TO SUPPORT THE
(8002) CONFIGURED LTECELL (1906)
equipmentAlarm Default probable cause: configurationOrCustomizationError (902)
(3)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates that the cell cannot be enabled due to licensing restriction
Impact: Telecom: The cell is not operational. OAM: No impact on OAM service.
Remedial action: The operator shall purchase the corresponding license.
Table 39-373 IK4305191 - 4TX CELL CONFIGURATION FAILURE

releases

Type: Specific problem: 4TX CELL CONFIGURATION
processingErrorAlarm (81) FAILURE (1907)
Raised on class: lte.Cell Default probable cause:
Description: This alarm indicates a cell is configured with 4 DL antennas, whereas the feature allowing 4 Tx
antennas is disabled (is4TxAntennasEnabled="false)."
Impact: Telecom: The telecom service on the cell is disabled. OAM: No impact on OAM service.
Remedial action: Verify the DL antennas setting for this cell in MIM and verify the is4TxAntennasEnabled flag
in MIM.
Table 39-374 IK4305192 - CONFIGURATION DATA REJECTED

releases

Type: Specific problem: CONFIGURATION DATA
processingErrorAlarm (81) REJECTED (1908)
Raised on class: lte.RFM Default probable cause: equipmentMalfunction (698)
Description: This alarm indicates inconsistency in the RFM configuration data.
Impact: Telecom: Possible loss of telecom resources. OAM: No impact on OAM service.
Remedial action: Verify and correct the configuration data. Identify from additional info the impacted
parameter.
Table 39-375 IK4306108 - FEATURE TRI-CARRIER NOT SUPPORTED

releases

(8005) Specific problem: FEATURE TRI-CARRIER NOT
Type: SUPPORTED (1909)
lte.Cell
Description: This alarm indicates that the cell configuration with Tri-carrier is not supported by the equipped
modem type.
Impact: Telecom traffic is not enabled for the cell.
Remedial action: Verify and correct the configuration data.
Table 39-376 IK4306109 - CB TWAMP EXCESS CONTROL SESSION REQUEST

releases

Type: equipmentAlarm (3) Specific problem: CB TWAMP EXCESS CONTROL
Package: lte SESSION REQUEST (1910)
lte.CBCardSpecifics Default probable cause:
Description: This alarm indicates 5 TWAMP Control sessions have been requested in a VLAN. 4 is the
maximum supported number.
Impact: TWAMP Control sessions above the number supported are ignored.
Remedial action: Check TWAMP client configuration to ensure it matches maximum requirements of the base
station server.
Table 39-377 IK4306110 - CB TWAMP TEST SESSION FAILURE

releases

Type: equipmentAlarm (3) Specific problem: CB TWAMP TEST SESSION
lte.CBCardSpecifics Default probable cause: informationMissing (792)
Description: A TWAMP session in the VLAN has failed based on lack of incoming Test packets for a period of
time configured by SERVWAIT/REFWAIT timers.
Impact: TWAMP session with loss of packets is terminated.
Remedial action: Check TWAMP client and the backhaul link between TWAMP client and base station for any
backhaul connectivity failure.
Table 39-378 IK4306111 - CB TWAMP MODE MISMATCH

releases

Type: equipmentAlarm (3) Specific problem: CB TWAMP MODE MISMATCH
Package: lte (1912)
Description: The server has a TWAMP Control session Request with an unacceptable Mode value. Only
’Unauthenticated’ is acceptable.
Impact: TWAMP Control sessions will be supported only when mode is Unauthenticated.
Remedial action: Check TWAMP client configuration to ensure it matches the acceptable ’mode’ value for
Unauthentication.
Table 39-379 IK4306112 - SCB TWAMP EXCESS TEST SESSION REQUEST

releases

(8009) Specific problem: SCB TWAMP EXCESS TEST SESSION
Type: equipmentAlarm REQUEST (1913)
lte.MODULE
Description: This alarm indicates 6 TWAMP test-sessions have been requested in a TWAMP Control-session
in a VLAN. 5 is the maximum supported number.
Impact: TWAMP test sessions above the number supported are ignored.
station server.
Table 39-380 IK4306113 - SCB TWAMP EXCESS CONTROL SESSION REQUEST

releases

(8010) Specific problem: SCB TWAMP EXCESS CONTROL
Type: SESSION REQUEST (1914)
lte.MODULE
Description: This alarm indicates 5 TWAMP Control sessions have been requested in a VLAN. 4 is the
maximum supported number.
Impact: TWAMP Control sessions above the number supported are ignored.
station server.
Table 39-381 IK4306114 - SCB TWAMP TEST SESSION FAILURE

releases

(8011) Specific problem: SCB TWAMP TEST SESSION
Type: equipmentAlarm FAILURE (1915)
Package: lte Default probable cause: informationMissing (792)
Raised on class:
lte.MODULE
Description: A TWAMP session in the VLAN has failed based on lack of incoming Test packets for a period of
time configured by SERVWAIT/REFWAIT timers.
Impact: TWAMP session with loss of packets is terminated.
Remedial action: Check TWAMP client and the backhaul link between TWAMP client and base station for any
backhaul connectivity failure.
Table 39-382 IK4306115 - SCB TWAMP MODE MISMATCH

releases

(8012) Specific problem: SCB TWAMP MODE MISMATCH
Type: equipmentAlarm (1916)
Raised on class: configurationOrCustomizationError (902)
lte.MODULE
Description: The server has a TWAMP Control session Request with an unacceptable Mode value. Only
’Unauthenticated’ is acceptable.
Impact: TWAMP Control sessions will be supported only when mode is Unauthenticated.
Remedial action: Check TWAMP client configuration to ensure it matches the acceptable ’mode’ value for
Unauthentication.
Table 39-383 IK4306116 - SIM HEALTH CHECK PHASE 1 - TX PWR FAILED

releases

(8013) Specific problem: SIM HEALTH CHECK PHASE 1 - TX
Type: PWR FAILED (1917)
(81) Default probable cause: softwareProgramError (720)
Package: lte
Description: This alarm indicates that the System Integrity Monitor, monitoring the health of the eNodeB cell,
has detected an active antenna transmit path (Cell, RFM id, antenna port #) with zero power continually for the
Phase 1 detection period.
Impact: Telecom: The alarm is notice that the cell is degraded. OAM: no impact..
Remedial action: No action is required. If the degradation persists, SIM may escalate to Local Recovery
Action on the implicated cell.
Table 39-384 IK4306117 - SIM HEALTH CHECK PHASE 1 - LOW RRC SUCCESS RATE
releases

(8014) Specific problem: SIM HEALTH CHECK PHASE 1 - LOW
Type: RRC SUCCESS RATE (1918)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates that the System Integrity Monitor, monitoring the health of the eNodeB, has
detected a degradation in the RRC Success Rate on the cell. This is the SIM Phase 1 detection.
Impact: Telecom: The alarm is notice that the RRC Success Rate is degraded. OAM: no impact.
Remedial action: No action is required. If the degradation persists, SIM may escalate to Local Recovery
Action.
Table 39-385 IK4306118 - SIM HEALTH CHECK PHASE 2 - LOW RRC SUCCESS RATE
releases

(8015) Specific problem: SIM HEALTH CHECK PHASE 2 - LOW
Type: RRC SUCCESS RATE (1919)
Package: lte
Raised on class:
lte.Cell
detected that the RRC Success Rate degradation has persisted beyond the configurable limit. This is the SIM
Phase 2 detection.
Impact: Telecom: The alarm is notice that the RRC Success Rate is degraded. OAM: no impact.
Remedial action: No action is required. If SIM escalation to Local Recovery Action is allowed, SIM will
automatically trigger Local Recovery Action to try to restore service on this cell.
Table 39-386 IK4306119 - SIM HEALTH CHECK - MAXIMUM NUMBER OF LRA REACHED
releases

(8016) Specific problem: SIM HEALTH CHECK - MAXIMUM NUMBER
Type: OF LRA REACHED (1920)
Package: lte
Raised on class:
lte.Cell
Description: The OAM System Integrity Monitor has run a SIM Health Check on the cell and has detected a
degradation that has escalated to the point of Phase 2 recovery. But, since SIM has already taken the
configurable maximum number of SIM triggered Phase 2 recovery actions on this cell in a 24 hour period, SIM
is prevented from taking recovery on this detection. Investigation is required to determine the cause for the
frequent degradations.
Impact: Telecom: The cell is degraded according to the health check that is failing. OAM: no impact.
Table 39-387 IK4306120 - UNEXPECTED RFME MODULE RESET

releases

(8017) Specific problem: UNEXPECTED RFME MODULE
Type: equipmentAlarm RESET (1921)
Raised on class:
lte.RFME
Description: This event indicates that the ENB suffered from an unexpected, unplanned failure on the RFME.
Specific details are in the Additional Text.
Impact: Depending on the nature of the failure, some Telecom or OAM functionalities may not be available
during recovery. On successful reset, the Telecom and OAM functionalities are available.
Table 39-388 IK4306121 - SIM HEALTH CHECK PHASE 2 - TX PWR FAILED

releases

(8018) Specific problem: SIM HEALTH CHECK PHASE 2 - TX
Type: PWR FAILED (1922)
Package: lte
detected an active antenna transmit path (Cell, RFM id, antenna port #) with zero power continually for the
Phase 2 detection period.
Impact: Telecom: The alarm is notice that the cell is degraded. OAM: no impact.
Remedial action: No action is required. If SIM escalation to Local Recovery Action is allowed, SIM will
automatically trigger Local Recovery Action to try to restore service on this cell.
Table 39-389 IK4306122 - SMART COLLECTION SERVICE ACTION PLAN COMPLETE

releases

(8019) Specific problem: SMART COLLECTION SERVICE ACTION
Type: PLAN COMPLETE (1923)
(81) Default probable cause: unspecifiedReason (802)
Package: lte
Raised on class:
lte.ENBEquipment
Description: This event indicates that the Smart Collection Service initiated a smart data collection and has
either 1) created a Local File, 2) streamed DDT to the DTC, and/or 3) used On Demand File Collection to push
the ODFC archive to the Snapshots and Postmortem Collector entity (SPC). This was triggered by a fault event
or state change. Specific details about the triggering event and the files that were collected are in the
Additional Text.
Impact: Telecom: no impact. OAM: no impact.
Table 39-390 IK4306123 - HANDOVER OPTIMIZATION ADJUSTMENT STARTED

releases

(8020) Specific problem: HANDOVER OPTIMIZATION
Type: ADJUSTMENT STARTED (1924)
(82) Default probable cause: unspecifiedReason (802)
Package: lte
Raised on class:
lte.Cell
Description: This alarm indicates the SON process that adjusts intra-frequency handover parameters has
started adjusting handover parameters.
Impact: MRO adjustment has begun and tuning of handover parameters is in progress for handover
optimization.
Remedial action: None.
Table 39-391 IK4306124 - CB TWAMP EXCESS TEST SESSION REQUEST

releases

Type: equipmentAlarm (3) Specific problem: CB TWAMP EXCESS TEST
Package: lte SESSION REQUEST (1925)
Description: This alarm indicates 6 TWAMP test-sessions have been requested in a TWAMP Control-session
in a VLAN. 5 is the maximum supported number.
Impact: TWAMP test sessions above the number supported are ignored.
station server.
Table 39-392 IK4306126 - RFM CONFIGURATION FAILURE

releases

Type: processingErrorAlarm Specific problem: RFM CONFIGURATION
(81) FAILURE (1926)
(698)
Description: This alarm indicates the failure to configure the RFM.
Remedial action: Reset the module. If the alarm persists, replace the module.
Table 39-393 IK4901006 - UNSUPPORTED DELEGATION BY OTHER CONTROLLER
releases

(2766) Specific problem: UNSUPPORTED DELEGATION BY OTHER
Type: CONTROLLER (1347)
equipmentAlarm Implicitly cleared: true
Package: lte (902)
Raised on class:
lte.RFM
Description: The primary controller for this RE (CDMA, WCDMA or GSM) has delegated a management
function such as ’Software Management’ to the LTE controller. This function is not supported by this LTE
release.
Impact: The delegated management function (e.g. software management) is not currently available.
Remedial action: Reconfigure the RE on the primary controller (CDMA, WCDMA or GSM) to no longer
delegate the unsupported management function to LTE.
Table 39-394 ImportPolicyNotFound

releases
Name: ImportPolicyNotFound (232) Severity: major Unspecified

Raised on class: importPolicyDoesNotExist (180)
l3fwd.ServiceSiteImportPolicy
Description: The alarm is raised when a VRF import policy for a VPRN cannot be found. The alarm
Remedial action: A configuration error has occurred which must be corrected. The VRP import policy must be
created and distributed to the NE reporting the problem. Note: starting from SAM 12.0 R1, SAM no longer
raises this alarm.
Table 39-395 IncompatibleCapacity

releases
Name: IncompatibleCapacity Severity: variable Unspecified

Package: equipment incompatibleCapacity (868)
Raised on class:
equipment.Equipment
Description: The alarm is raised when there is a radio capacity incompatibility.
Table 39-396 IncompatibleChannelSpacing (equipment)

releases

IncompatibleChannelSpacing
incompatibleChannelSpacing (869)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when there is a channel spacing incompatibility.
Table 39-397 IncompatibleChannelSpacing (radioequipment)

releases
Name: IncompatibleChannelSpacing Severity: variable Unspecified

Package: radioequipment incompatibleChannelSpacing (869)
Raised on class:
Description: The alarm is raised when a incompatibility of channel spacing value defect raise.
Remedial action: The alarm is raised when a incompatibility of channel spacing value defect raise.
Table 39-398 IncompatibleFrequency (mwa)

releases
Name: IncompatibleFrequency Severity: variable Unspecified

Package: mwa IncompatibleFrequency (1910)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a provisioned MPT frequency is incompatible with the MPT hardware.
information.
Table 39-399 IncompatibleFrequency (radioequipment)

releases
Name: IncompatibleFrequency (683) Severity: variable Unspecified

Raised on class: incompatibleFrequency (498)
Description: The alarm is raised when a provisioned MSS frequency is incompatible with the MSS hardware.
Table 39-400 IncompatibleModulation

releases
Name: IncompatibleModulation (4417) Severity: variable Unspecified
Raised on class: incompatibleModulation (850)
Description: The alarm is raised when an incompatibility of the modulation value defect raise.
Remedial action: The alarm is raised when an incompatibility of the modulation value defect raise.
Table 39-401 IncompatibleModulationParam (mwa)

releases

IncompatibleModulationParam Implicitly cleared: true
(1144)
Type: communicationsAlarm (4) IncompatibleModulationParam (1911)
Package: mwa
Raised on class:
mwa.PortTermination
Description: The alarm is raised when the provisioned modulation parameters are incompatible with the MPT
hardware.
information.
Table 39-402 IncompatibleModulationParam (radioequipment)

releases
Name: IncompatibleModulationParam Severity: variable Unspecified

Package: radioequipment incompatibleModulation (850)
Raised on class:
Description: The alarm is raised when the configured modulation parameters are not supported by MPT (or)
when XPIC is configured on an MPT that does not allow XPIC capability.
Table 39-403 IncompatiblePower

releases
Name: IncompatiblePower (3940) Severity: variable Unspecified

Raised on class: incompatiblePower (1522)
Description: The alarm is raised when a incompatibility of the power value defect raise.
Remedial action: The alarm is raised when a incompatibility of the power value defect raise.
Table 39-404 IncompatibleProtection (equipment)
releases
Name: IncompatibleProtection Severity: variable Unspecified

Type: equipmentAlarm (3) Default probable cause: incompatibleProtection
Raised on class:
equipment.Port
Description: The alarm is raised in case of hardware incompatibility for 1+1 radio configuration i.e. MPT-HCv2
without RPS or XPIC equipped.
Table 39-405 IncompatibleProtection (mwa)

releases
Name: IncompatibleProtection Severity: variable Unspecified

Package: mwa IncompatibleProtection (1912)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a incompatible protection scheme is selected.
information.
Table 39-406 IncompatiblePTX

releases
Name: IncompatiblePTX (684) Severity: variable Unspecified

Raised on class: incompatiblePTX (499)
Description: The alarm is raised when the provisioned MSS transmit power is incompatible with the MSS
hardware.
Table 39-407 IncompatibleShifter (mwa)

releases
Name: IncompatibleShifter (685) Severity: variable Unspecified

Package: mwa Default probable cause: Incompatibleshifter
mwa.PortTermination
Description: The alarm is raised when the provisioned MPT shifter parameters are incompatible with the MPT
hardware.
information.
Table 39-408 IncompatibleShifter (radioequipment)

releases
Name: IncompatibleShifter (685) Severity: variable Unspecified

Raised on class: incompatibleShifter (500)
Description: The alarm is raised when the provisioned MSS shifter parameters are incompatible with the MSS
hardware.
Table 39-409 IncompatibleTxPower

releases
Name: IncompatibleTxPower Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: IncompatibleTxPower
Package: mwa (1914)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when the provisioned MPT transmit power is incompatible with the MPT
hardware.
information.
Table 39-410 IncompleteConfig (bundle)

releases
Name: IncompleteConfig (294) Severity: major Unspecified

Package: bundle Default probable cause:
Raised on class: incompleteConfig (225)
bundle.MultiChassisApsInterface
Description: The alarm is raised when there are not exactly two APS bundles in an APS group.
Raising condition: ((’Number of members’ NOT EQUAL ’2’))
Clearing condition: ((’Number of members’ EQUAL ’2’))
Remedial action: Configure the missing peered object.
Table 39-411 IncompleteConfig (lag)

releases
Name: IncompleteConfig (294) Severity: major Unspecified

Package: lag
Raised on class: Default probable cause: incompleteConfig
lag.MultiChassisLag (225)
Description: The alarm is raised when an MC LAG has fewer than two members.
Raising condition: (’numberOfMembers’ NOT EQUAL ’2’)
Clearing condition: (’numberOfMembers’ EQUAL ’2’)
Remedial action: Configure the missing peered object.
Table 39-412 IncompleteConfig (rmon)

releases
Name: IncompleteConfig Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: incompleteConfig
Package: rmon (225)
Raised on classes:
rmon.Event
rmon.Alarm
Description: The alarm is raised when an object is created with default values but not yet made active.
Raising condition: (’Status’ EQUAL ’Under Creation’)
Clearing condition: (’Status’ NOT EQUAL ’Under Creation’)
Remedial action: The object is created with default values but not yet made active. Please activate.
Table 39-413 InconsistenciesOnNode

releases
Name: InconsistenciesOnNode Severity: warning Unspecified

Type: integrityViolation (85) Default probable cause:
Package: netw inconsistenciesOnNode (813)
Raised on class:
netw.NetworkElement
Description: The alarm is raised when a device detects one or more configuration inconsistencies. On a 9500
MPR, this can be caused by cross-connect creation failure during service creation.
Remedial action: Please click on the clear inconsistencies button from the NE properties GUI form to clear the
inconsistencies.
Table 39-414 InstanceIdMismatch

releases
Name: InstanceIdMismatch Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: instanceIdMismatch
Package: srrp (309)
Description: The alarm is raised when a local SRRP SAP is backed up by a different SRRP instance on a
remote peer.
Remedial action: Reconfigure the instance so that the peer SRRP instances have the same ID.
Table 39-415 InSufficientBandwidth

releases
Name: InSufficientBandwidth Severity: major Unspecified

Package: mpr inSufficientBandwidth (521)
Raised on class:
mpr.VlanPathInstance
Description: The alarm is raised when there is insufficient bandwidth on a radio link between hops in a
service.
Remedial action: Information - Service cannot be deployed because insufficient bandwidth on the port. Use a
different port or ensure the required bandwidth.
Table 39-416 InterfaceDbDescriptAuthFailure

releases

InterfaceDbDescriptAuthFailure (46) Implicitly cleared: false
Type: authenticationAlarm (14) Default probable cause:
Package: ospf authTypeMismatch (45)
Raised on class: ospf.Interface Applicable probable causes:
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a dbDescript packet on a non-virtual interface from an
NE whose authentication key or authentication type conflicts with the local NE authentication key or
authentication type.
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a non-
virtual interface from the network whose authentication key or authentication type conflicts with the local NE’s
configuration.
Table 39-417 InterfaceDbDescriptConfig

releases
Name: InterfaceDbDescriptConfig Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: badVersion
Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
helloIntervalMismatch
deadIntervalMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a dbDescript packet on a non-virtual interface from an
NE whose configuration parameters conflict with the local NE configuration parameters.
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a non-
virtual interface from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-418 InterfaceHelloAuthFailure

releases
Name: InterfaceHelloAuthFailure Severity: warning Unspecified

Type: authenticationAlarm (14) Default probable cause: authTypeMismatch
Package: ospf (45)
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a hello packet on a non-virtual interface from an NE
whose authentication key or authentication type conflicts with the local NE authentication key or authentication
type.
Remedial action: Informational - The alarm signifies that a hello packet has been received on a non-virtual
interface from the network whose authentication key or authentication type conflicts with the local NE’s
configuration.
Table 39-419 InterfaceHelloConfig

Name: InterfaceHelloConfig (39) Severity: warning Unspecified

Package: ospf Default probable cause: badVersion (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a hello packet on a non-virtual interface from an NE
whose configuration parameters conflict with the local NE configuration parameters.
Remedial action: Informational - The alarm signifies that a hello packet has been received on a non-virtual
interface from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-420 InterfaceLsAckAuthFailure

releases
Name: InterfaceLsAckAuthFailure Severity: warning Unspecified

Package: ospf (45)
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsAck packet on a non-virtual interface from an NE
type.
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a non-virtual
configuration.
Table 39-421 InterfaceLsAckConfig

Name: InterfaceLsAckConfig (43) Severity: warning Unspecified

badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsAck packet on a non-virtual interface from an NE
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a non-virtual
Table 39-422 InterfaceLsReqAuthFailure

releases
Name: InterfaceLsReqAuthFailure Severity: warning Unspecified

Package: ospf (45)
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsReq packet on a non-virtual interface from an NE
type.
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a non-virtual
configuration.
Table 39-423 InterfaceLsReqConfig

Name: InterfaceLsReqConfig (41) Severity: warning Unspecified
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsReq packet on a non-virtual interface from an NE
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a non-virtual
Table 39-424 InterfaceLsUpdateAuthFailure

releases

InterfaceLsUpdateAuthFailure (48) Implicitly cleared: false
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsUpdate packet on a non-virtual interface from an
NE whose authentication key or authentication type conflicts with the local NE authentication key or
authentication type.
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a non-
virtual interface from the network whose authentication key or authentication type conflicts with the local NE’s
configuration.
Table 39-425 InterfaceLsUpdateConfig

releases
Name: InterfaceLsUpdateConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsUpdate packet on a non-virtual interface from an
NE whose configuration parameters conflict with the local NE configuration parameters.
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a non-
virtual interface from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-426 InterfaceNullPacketAuthFailure

releases

InterfaceNullPacketAuthFailure (50) Implicitly cleared: false
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a null packet on a non-virtual interface from an NE
type.
Remedial action: Informational - The alarm signifies that a null packet has been received on a non-virtual
configuration.
Table 39-427 InterfaceNullPacketConfig

releases
Name: InterfaceNullPacketConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifTypeMismatch
nullRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a null packet on a non-virtual interface from an NE
Remedial action: Informational - The alarm signifies that a null packet has been received on a non-virtual
Table 39-428 InterfaceRxBadPacket

Name: InterfaceRxBadPacket (51) Severity: warning Unspecified

Package: ospf Default probable cause: hello (47)
hello
dbDescript
lsReq
lsUpdate
lsAck
nullPacket
Description: The alarm is raised when an NE cannot parse an OSPF packet that it receives on a non-virtual
interface.
Remedial action: Informational - an NE cannot parse an OSPF packet that it receives on a non-virtual
interface.
Table 39-429 InternalCommunicationProblem (equipment)

releases

InternalCommunicationProblem Implicitly cleared: true
(627)
Type: equipmentAlarm (3) internalCommunicationProblem (466)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when an ODU is unresponsive.
Table 39-430 InternalCommunicationProblem (mpr)

releases

InternalCommunicationProblem Implicitly cleared: true
(627)
Type: equipmentAlarm (3) internalCommunicationProblem (466)
Package: mpr
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when an MPTHLv2 is unresponsive.
Remedial action: The alarm is raised when there is a loss of communication with MPT. Please refer 9500
Node Maintenance manual for remedial action information.
Table 39-431 InterRedundantMPTCommunicationFailure

releases

InterRedundantMPTCommunicationFailure Implicitly cleared: true
(4826)
Type: communicationsAlarm (4) InternalCommunicationProblem (1915)
Package: mwa
Description: The alarm is raised when a MPT detects a Inter Redundant MPTs Communication Failure
information.
Table 39-432 InterXPolarizedMPTCommunicationFailure

releases

InterXPolarizedMPTCommunicationFailure Implicitly cleared: true
(4827)
Type: communicationsAlarm (4) InternalCommunicationProblem (1915)
Package: mwa
Description: The alarm is raised when a MPT detects a Inter X-Polarized MPTs Communication Failure
information.
Table 39-433 InvalidBOFAddress

releases
Name: InvalidBOFAddress (1141) Severity: warning Unspecified

Package: netw Default probable cause: invalidBOF
netw.NodeDiscoveryControl
Description: The alarm is raised during a network topology rescan in which the 5620 SAM does not find a
previously configured NE BOF address, and the Management IP Selection of the NE is set to one of the
following: - Out Of Band Preferred - In Band Preferred
Remedial action: A configuration error has been made which must be corrected. The BOF address must be
configured on the NE.
Table 39-434 InvalidJoinPrune

releases
Name: InvalidJoinPrune Severity: warning Unspecified

Type: Default probable cause: InvalidJoinPruneReceived
communicationsAlarm (4) (145)
Package: pim
Description: The alarm is raised when the RP address in a Join Prune message is not the RP for the group
specified in the message.
Remedial action: Informational - please make sure the RP address in a Join Prune message is the RP for the
group specified
Table 39-435 InvalidRegister

releases
Name: InvalidRegister Severity: warning Unspecified
communicationsAlarm (4) InvalidJoinRegisterReceived (146)
Package: pim
Description: The alarm is raised when the RP address in a Register message is not the RP for the group
specified in the message.
Remedial action: Informational - please make sure the RP address in a Register message is the RP for the
group specified
Table 39-436 invalidRPLoopbackInterfaceConfig

releases

invalidRPLoopbackInterfaceConfig Implicitly cleared: true
(269)
Type: configurationAlarm (11) invalidRPLoopbackIfConfig (201)
Package: pim
Raised on class:
pim.VirtualAnyCastRP
Description: The alarm is raised when an RP loopback interface configuration is invalid.
Remedial action: A configuration error has occurred that must be corrected. Please check the global Virtual
Anycast RP configuration and its operational status flag so that the loopback is properly configured, PIM is
enabled on the loopback interface.
Table 39-437 IpAddressManaged

releases
Name: IpAddressManaged Severity: info Unspecified

Type: IpAddressManaged (124) Default probable cause: IpAddressManaged
Package: ptp (1571)
Raised on class:
ptp.SourceEntryPoint
Description: The alarm is raised when unmanaged IP address becomes managed virtual router IP address.
Remedial action: The source entry point unmanaged IP address becomes managed virtual router IP address.
Please re-configure source entry point.
Table 39-438 IpAddressOverlap

releases
Name: IpAddressOverlap (3318) Severity: warning Unspecified

Package: rtr Default probable cause: IpAddressOverlap
rtr.VirtualRouterIpAddress
Description: The alarm is raised when the IP addresses configured on different VPRN sites within service
overlap.
Remedial action: Please check the IP Addresses configured on different VPRN sites have no overlap.
Table 39-439 IPListMismatch
releases
Name: IPListMismatch (282) Severity: warning Unspecified

Package: vrrp Default probable cause:
Raised on class: nonMatchingBackupAddressList (214)
Description: The alarm is raised when the IP address list in an advertisement message from the current
master does not match the configured IP address list.
Remedial action: Check the configured IP addresses, make sure they match the advertised IP addresses
from the master VRRP instance.
Table 39-440 IpPathDown

releases
Name: IpPathDown (1916) Severity: major Unspecified

Type: topologyAlarm (34) Implicitly cleared: true
Package: monpath Default probable cause: ipPathDown
monpath.MonitoredIpPath
Description: This alarm is raised when the re-calculation by the CPAA shows that no IP Path is available.
Remedial action: Informational - The IP path record provides an Error code which provides a clue on why the
path is down.
Table 39-441 IpPathMonitorFailedRetryThresholdCrossed

releases

IpPathMonitorFailedRetryThresholdCrossed Implicitly cleared: true
(400)
Type: topologyAlarm (34) ipPathCouldNotBeDetermined (299)
Package: monpath
Raised on class: monpath.MonitoredIpPath
Description: The alarm is raised when the 5650 CPAM cannot set up an IP path monitor after the number of
attempts specified by the cpamManagedRoute problematicThresholdAlarmAfter value in the nms-server.xml
file. The alarm is raised if the cpamManagedRoute problematicRetryStrategy value in nms-server.xml is set to
countdown. The default problematicRetryStrategy value of reactive prevents the alarm from being raised.
Remedial action: Informational - The Retry strategy can be modified in nms-server.xml. This alarm is not
raised for the default retry strategy, reactive.
Table 39-442 IpPathMonitorRetryAttemptsExhausted

releases

IpPathMonitorRetryAttemptsExhausted Implicitly cleared: false
(401)
Type: topologyAlarm (34) ipPathCouldNotBeDetermined (299)
Package: monpath
Raised on class:
Description: The alarm is raised when the 5650 CPAM stops trying to set up an IP path monitor after the
number of attempts specified by the cpamManagedRoute problematicDeadAfter value in the nms-server.xml
countdown. The default problematicRetryStrategy value of reactive prevents the alarm from being raised.
Table 39-443 IpPathMulticastWarning

releases
Name: IpPathMulticastWarning Severity: major Unspecified

Package: monpath IpPathSegmentNotMulticastEnabled (919)
Raised on class:
Description: If IP Path is enabled for monitoring Multicast, the alarm is raised when at least one IP Path
segment is not Multicast enabled. The alarm is cleared when all the segments are Multicast enabled.
Remedial action: Informational - The segments without PIM interface enabled can be obtained from path
record. PIM should be enabled on these interfaces in order for alarm to be cleared.
Table 39-444 IPsecInterfaceBfdSessionDown

releases
Name: IPsecInterfaceBfdSessionDown Severity: warning Unspecified

Type: bfdSessionAlarm (46) Default probable cause:
Package: service bfdSessionDown (346)
Raised on class: service.IPsecInterface
Remedial action: This alarm is raised when a BFD session on an IPsec interface goes down. The situation
this problem.
Table 39-445 IPsecInterfaceBfdSessionFlapped

releases

IPsecInterfaceBfdSessionFlapped Implicitly cleared: true
(3905)
Type: bfdSessionAlarm (46) bfdSessionFlapped (1491)
Package: service
Remedial action: The BFD session on an IPsec interface has transitioned from Up to Down and back to Up
within the configured BFD Flapping Interval.
Table 39-446 IPsecInterfaceBfdSessionMissing
releases

IPsecInterfaceBfdSessionMissing Implicitly cleared: true
(3325)
Type: bfdSessionAlarm (46) bfdSessionMissing (345)
Package: service
Remedial action: This alarm is raised when a previously present BFD session on an IPsec interface is absent.
The situation may occur if the underlying physical interface is down either because of administrative disabling
or a fault on the near end port or due to a cable connection or cable failure. This alarm will also be raised if the
underlying transport network fails or is unreliable. Resolving the underlying instability in the transport network
will correct this problem.
Table 39-447 IPSecRUSAFailToAddRoute

releases
Name: IPSecRUSAFailToAddRoute Severity: warning Unspecified

Package: ipsec IPSecRUSAFailToAddRoute (2101)
Raised on class:
ipsec.IPSecSecuredVpnManager
Description: The trap tIPsecRUSAFailToAddRoute is sent when adding route to tIPsecRUSARemAddr for the
remote-user tunnel fails with reason indicated by tIPsecNotifReason.
Remedial action: Informational - Please see reason for failure.
Table 39-448 IPsecRUTnlFailToCreate

releases
Name: IPsecRUTnlFailToCreate Severity: warning Unspecified

Package: ipsec IPsecRUTnlFailToCreate (2102)
Raised on class:
ipsec.IPSecGateway
Description: This alarm is sent when creation of a remote-user tunnel fails with reason indicated by
notifReason.
Remedial action: Informational - Please see reason for failure.
Table 39-449 IsaAaGrpBitRate

releases
Name: IsaAaGrpBitRate Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpBitRate
Package: isa (1143)
Raised on class: isa.AaGroup
Description: The alarm is raised when the current bit rate on the MDA in the ISA-AA group is greater than or
equal to tmnxBsxBitRateHighWatermark, and the prior bit rate is less than the threshold.
Remedial action: The current bit rate on the MDA in the ISA-AA group is greater than or equal to the
configured Bit Rate High Watermark. The threshold configured should be revisited to ensure that it is not set
too low. To disable the notification, set the Packet Rate High Watermark to maximum.
Table 39-450 IsaAaGrpCapCostThres

releases
Name: IsaAaGrpCapCostThres Severity: warning Unspecified

Package: isa IsaAaGrpCapCostThres (595)
Raised on class:
isa.AaGroupMember
Description: The alarm is raised when the capacity cost for an MDA in an ISA-AA group reaches the
configured threshold.
Remedial action: The capacity cost high threshold for the MDA in the ISA-AA group has been reached.
Table 39-451 IsaAaGrpFailure

Name: IsaAaGrpFailure Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpFailure (434)
Package: isa
Raised on class:
isa.AaGroup
Description: The alarm is raised when an ISA-AA Group has no configured primary MDA or the number of
active MDAs is not equal to the number of configured primary MDAs.
Remedial action: There is a failure on the ISA-AA group. Ensure that ISA-AA group has a primary MDA group
member configured, and that the number of active MDAs is equal to the number of configured primary MDAs.
Table 39-452 IsaAaGrpFlowFull

releases
Name: IsaAaGrpFlowFull Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpFlowFull
Package: isa (436)
Description: The alarm is raised when an ISA-AA group uses a greater number of flow records than the value
specified by tmnxBsxFlowFullHighWatermark.
Remedial action: The number of flow records that the ISA-AA group is using is greater than or equal to the
configured Flow Full High Watermark. The threshold configured should be revisited to ensure that it is not set
too low.
Table 39-453 IsaAaGrpFlowSetup

releases
Name: IsaAaGrpFlowSetup Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpFlowSetup
Package: isa (1144)
Description: The alarm is raised when the current flow setup rate on the MDA in the ISA-AA group is greater
than or equal to tmnxBsxFlowSetupHighWatermark, and the prior bit rate is less than the threshold.
Remedial action: The current flow setup rate on the MDA in the ISA-AA group is greater than or equal to the
configured Flow Setup High Watermark. The threshold configured should be revisited to ensure that it is not set
too low. To disable the notification, set the Flow Setup High Watermark to maximum.
Table 39-454 IsaAaGrpFmSbWaSBufOvld

releases

IsaAaGrpFmSbWaSBufOvld Implicitly cleared: true
(2950)
Type: equipmentAlarm (3) IsaAaGrpFmSbWaSBufOvld (1145)
Package: isa
Raised on class:
isa.AaGroupMember
Description: The alarm is raised when the current weighted average shared buffer for an ISA in the from
subscriber direction is greater than or equal to a high water mark in a normal, non-overloaded, state.
Remedial action: The ISA-AA Egress From-Subscriber buffer pool has entered an overload state as
determined by the configured Buffer Utilization High Watermark. The threshold configured should be revisited
to ensure it is not set too low. To disable the notification, set the Buffer Utilization High Watermark to the
maximum.
Table 39-455 IsaAaGrpNonRedundant

releases
Name: IsaAaGrpNonRedundant Severity: warning Unspecified

Package: isa isaAaGrpNonRedundant (435)
Description: The alarm is raised when an ISA-AA Group has a configured backup MDA but there is no
standby MDA available.
Remedial action: The ISA-AA Group has a configured backup MDA but there is no standby MDA available.
Check that the configured standby MDA is active and operationally up. There may be a fault with the ISA
Application Assurance MDA.
Table 39-456 IsaAaGrpOvrldCutthru

releases
Name: IsaAaGrpOvrldCutthru Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: IsaAaGrpOvrldCutthru
Package: isa (1146)
Raised on class:
isa.AaGroupMember
Description: The alarm is raised when cut through processing starts on an ISA MDA.
Remedial action: Overload Cut-Through is enabled on the ISA-AA Group. All traffic is cut-through and the
ISA-AA MDA is overloaded. Disable Overload Cut-Through if this is not required.
Table 39-457 IsaAaGrpPacketRate

releases
Name: IsaAaGrpPacketRate Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpPacketRate
Package: isa (1147)
Description: The alarm is raised when the current packet rate on the MDA in the ISA-AA group is greater than
or equal to tmnxBsxPacketRateHighWatermark, and the prior rate is less than this threshold.
Remedial action: The current packet rate on the MDA in the ISA-AA group is greater than or equal to the
configured Packet Rate High Watermark. The threshold configured should be revisited to ensure that it is not
set too low. To disable the notification, set the Packet Rate High Watermark to maximum.
Table 39-458 IsaAaGrpSwitchover

releases
Name: IsaAaGrpSwitchover Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: isaAaGrpSwitchover
Package: isa (437)
Description: The alarm is raised when an ISA-AA group experiences an activity switch from one ISA-AA to
another.
Remedial action: The ISA-AA Group has performed an activity switch from one ISA-AA MDA to another.
Table 39-459 IsaAaGrpToSbWaSBufOvld

releases

IsaAaGrpToSbWaSBufOvld Implicitly cleared: true
(2953)
Type: equipmentAlarm (3) IsaAaGrpToSbWaSBufOvld (1148)
Package: isa
Raised on class:
isa.AaGroupMember
Description: The alarm is raised when the current weighted average shared buffer use for an ISA in the To
subscriber direction, is greater than or equal to a high water mark, after being in a normal or non-overloaded
state.
Remedial action: The ISA-AA Egress To-Subscriber buffer pool has entered an overload state as determined
by the configured Buffer Utilization High Watermark. The threshold configured should be revisited to ensure it
is not set too low. To disable the notification, set the Buffer Utilization High Watermark to the maximum.
Table 39-460 IsidMisconfiguration (epipe)

releases
Name: IsidMisconfiguration Severity: warning Unspecified
Type: configurationAlarm (11) Default probable cause: isidInconsistent
Package: epipe (446)
Raised on class: epipe.Epipe
Description: The alarm is raised when Epipe service sites that are bound to a PBB backbone use different
ISID values.
Raising condition: (’operationalFlags’anyBit’ISID Inconsistent’)
Clearing condition: NOT ((’operationalFlags’anyBit’ISID Inconsistent’))
Remedial action: All service sites must use consistent I-SID values for a PBB backbone.
Table 39-461 IsidMisconfiguration (vpls)

releases
Name: IsidMisconfiguration (592) Severity: warning Unspecified

Package: vpls Default probable cause: isidInconsistent
vpls.AbstractVpls
Description: The alarm is raised when service sites use inconsistent I-SID values for a PBB backbone. The
alarm is raised against a VPLS or M-VPLS service.
Raising condition: (’operationalFlags’anyBit’ISID Inconsistent’)
Clearing condition: NOT ((’operationalFlags’anyBit’ISID Inconsistent’))
Remedial action: All service sites must use consistent I-SID values for a PBB backbone.
Table 39-462 IsisAreaMismatch

releases
Name: IsisAreaMismatch Severity: warning Unspecified

Type: configurationAlarm Default probable cause: areaTypeMisconfigured
(11) (34)
Package: isis
Raised on class: isis.Site
Description: The alarm is raised when IS-IS receives a Hello PDU from an IS with which it does not share an
area address.
Remedial action: Check whether NET address is configured and the AREA ID between two adjacencies are
not the same.
Table 39-463 IsisAuthFailure

Name: IsisAuthFailure (155) Severity: ng Unspecified

Type: authenticationAlarm (14) Implicitly cleared: false
Package: isis Default probable cause: authFailure (46)
Description: The alarm is raised when IS-IS receives a PDU that contains incorrect authentication information.
Remedial action: The authentication information on the ISIS Site needs to be changed to match its
neighbours.
Table 39-464 IsisAuthTypeFailure

Name: IsisAuthTypeFailure (154) Severity: warning Unspecified

Type: authenticationAlarm (14) Implicitly cleared: true
Package: isis Default probable cause: authFailure (46)
Description: The alarm is raised when IS-IS receives a PDU that contains the wrong authentication type.
Remedial action: The authentication information on the ISIS Site needs to be changed to match its
neighbours.
Table 39-465 IsisExportLimitDropped

releases
Name: IsisExportLimitDropped Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: exportLimitDropped
Package: isis (598)
Description: The alarm is raised when the number of routes exported from the route table to an IS-IS level
drops below the Export Limit value for the level.
Remedial action: Informational.
Table 39-466 IsisExportLimitReached

releases
Name: IsisExportLimitReached Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: exportLimitReached
Package: isis (599)
Description: The alarm is raised when the number of routes exported from the route table to an IS-IS level is
equal to the Export Limit value for the level.
Remedial action: Informational - the number of routes exported from the route table to an IS-IS level is equal
to the Export Limit value for the level
Table 39-467 IsisExportLimitWarning

releases
Name: IsisExportLimitWarning Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: exportLimitWarning
Package: isis (600)
Description: The alarm is raised when the number of routes exported from the route table to an IS-IS level is
equal to the Export Limit percentage specified by the Export Limit Log Percent value.
Remedial action: Informational - the number of routes exported from the route table to an IS-IS level is equal
to the Export Limit percentage specified by the Export Limit Log Percent value.
Table 39-468 IsisLspRateThresholdExceeded

releases

IsisLspRateThresholdExceeded (376) Implicitly cleared: true
Package: topology unstableIGPNetwork (241)
Description: The alarm is raised when the IS-IS LSP rate exceeds the maximum allowed value because of an
unstable IGP network.
Remedial action: User configured alarm for monitoring purpose. IGP historical map can be used for
debugging purpose.
Table 39-469 IsisLspThresholdExceeded

releases
Name: IsisLspThresholdExceeded Severity: major Unspecified

Type: topologyAlarm (34) Default probable cause: largeIGPNetwork
Description: The alarm is raised when the number of IS-IS LSPs exceeds the maximum allowed value
because of a large IGP network.
debugging purpose.
Table 39-470 IsisManualAddressDrops

Name: IsisManualAddressDrops (157) Severity: warning Unspecified

Package: isis Default probable cause: noError (44)
Description: The alarm is raised when a manual area address assigned to an IS is ignored during a route
computation.
Table 39-471 IsisReachabilityThresholdExceeded

releases

IsisReachabilityThresholdExceeded Implicitly cleared: true
(377)
Type: topologyAlarm (34) manyExternalLSAsFloodingIntoIGP (271)
Package: topology
Description: The alarm is raised when the IS-IS reachability value exceeds the maximum allowed value
because too many external LSAs are flooding the IGP.
Remedial action: User configured alarm for monitoring purpose. The advertised routes can be viewed using
CPAM IGP prefix list.
Table 39-472 IsisRejectedAdjacency

releases
Name: IsisRejectedAdjacency Severity: minor Unspecified

Type: adjacencyAlarm (31) Default probable cause: interfaceMismatch
Package: isis (170)
Raised on class: isis.Interface
Description: The alarm is raised when the 5620 SAM receives a vRtrIsisRejectedAdjacency trap, which
indicates that an adjacency cannot be established in response to a Hello PDU from an IS because of a lack of
resources.
Remedial action: Informational, might have exceeded the maximum number of adjacencies allowed.
Table 39-473 IuCS_aspInactive

releases
Name: IuCS_aspInactive Severity: critical Unspecified

communicationsAlarm (4) communicationsProtocolError (901)
Package: femto
Raised on class:
femto.IuCS
Description: Notification to inform the application that the FGW’s IPSP instance has become inactive
Table 39-474 IuPS_aspInactive

releases
Name: IuPS_aspInactive Severity: critical Unspecified

communicationsAlarm (4) communicationsProtocolError (901)
Package: femto
Raised on class:
femto.IuPS
Description: Notification to inform the application that the FGW’s IPSP instance has become inactive
Table 39-475 L2AccessInterfaceChange

releases
Name: L2AccessInterfaceChange Severity: info Unspecified
Type: communicationsAlarm (4) Default probable cause: SAPChanged
Package: mpr (1516)
Raised on class:
Description: The alarm is raised when the SAP is changed in Service for 9500.
Remedial action: Informational - if SAP is changed this alarm is raised.
Table 39-476 L2tpLnsSePppSessionFailure

releases

L2tpLnsSePppSessionFailure Implicitly cleared: false
(3901)
Type: processingErrorAlarm (81) l2tpLnsSePppSessionFailed (1492)
Package: rtr
Raised on class:
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot create a new L2TP session.
Remedial action: The alarm is raised when an NE notifies the 5620 SAM that it cannot create a new L2TP
session. Verify the configuration to have LNS group assigned to the group tunnel profile or tunnel profile.
Additionally, verify the length of the auto-generated subscriber identification.
Table 39-477 L2tpTunnelBlacklisted

releases
Name: L2tpTunnelBlacklisted Severity: variable Unspecified

Type: processingErrorAlarm Default probable cause:
(81) tmnxL2tpTunnelBlacklisted (1893)
Package: l2tp
Raised on class:
l2tp.TunnelStatus
Description: This alarm is raised when a L2TP tunnel is added to the tunnel-selection-blacklist. It is
automatically cleared when the tunnel is removed from the list.
Remedial action: In most cases the problem is a configuration mismatch between LAC and LNS, or a problem
on LNS. Please refer to the additional text and enable the debug log on event lac-session-setup to figure out
the root cause.
Table 39-478 LacpExpired

releases
Name: LacpExpired (3981) Severity: minor Unspecified

Package: lag Default probable cause:
Raised on class: LagSubgroupMemberStateChange (1558)
lag.PortTermination
Description: The alarm is raised when Lacp expired on subgroup lag member due to state change.
Remedial action: The reasons for LACP Expired alarm may vary. The following possible causes of this alarm
should be investigated. The partner lag member oper state may have changed or LACP Transmit Standby may
have been disabled - this can be remedied by enabling the LACP Transmit Standby on Lag. The partner lag
member 802.3ah oper state may have changed - ensure that 802.3ah state is same on both ends. The partner
lag member dot1ag state may have changed - ensure that dot1ag state is same on both ends.
Table 39-479 LagDot1agStateChanged

releases
Name: LagDot1agStateChanged Severity: minor Unspecified

Type: equipmentAlarm (3) Default probable cause: Dot1agStateChange
Package: lag (1559)
Raised on class:
lag.PortTermination
Description: The alarm is raised when the subgroup lag member dot1ag state has changed.
Remedial action: The lag member dot1ag state may have changed - please ensure that dot1ag state is same
on both ends.
Table 39-480 LagEfmOamStateChanged

releases
Name: LagEfmOamStateChanged Severity: minor Unspecified

Package: lag EfmOamStateChange (1560)
Raised on class:
lag.PortTermination
Description: The alarm is raised when the subgroup lag member efmOam state has changed.
Remedial action: The lag member 802.3ah oper state may have changed - please ensure that 802.3ah state
is same on both ends.
Table 39-481 LagPartnerOperStateChanged

releases

LagPartnerOperStateChanged Implicitly cleared: true
(3984)
Type: equipmentAlarm (3) PartnerOperStateChange (1561)
Package: lag
Raised on class:
lag.PortTermination
Description: The alarm is raised when the subgroup lag member partner oper state has changed.
Remedial action: The lag member oper state may have changed or LACP Transmit Standby may have been
disabled - this can be remedied by enabling the LACP Transmit Standby on Lag.
Table 39-482 LanFailure

releases
Name: LanFailure (628) Severity: variable Unspecified

Package: equipment
Raised on class: Default probable cause: lanFailure
equipment.Equipment (467)
Description: The alarm is raised when a LAN failure is detected.
Table 39-483 LastHopIncorrectLabelAction

releases

LastHopIncorrectLabelAction Implicitly cleared: true
(352)
Type: configurationAlarm (11) LabelActionIsNotPopOnLastHop (254)
Package: mpls
Raised on class: mpls.StaticLsp
Description: The alarm is raised when the label action specified for the last hop in a static LSP is not a pop
action.
Remedial action: Ensure the last hop configured with a pop label action, if the last hop node is managed by
SAM.
Table 39-484 LastHopNotMatchingDestination

releases

LastHopNotMatchingDestination Implicitly cleared: true
(351)
Type: configurationAlarm (11) LastHopNotMatchingDestination (253)
Package: mpls
Description: The alarm is raised when the last hop in a static LSP is not the destination.
Remedial action: Ensure the last hop configured in the static LSP match the destination of the LSP, if the last
hop node is managed by SAM.
Table 39-485 LCD

releases
Name: LCD (803) Severity: major Unspecified

(4) Default probable cause: lossOfCellDelineation
Package: mpr (569)
Raised on class:
mpr.IMALink
Description: The alarm is raised when a Loss of Cell Delineation signal is detected on an ASAP MDA.
Table 39-486 LdpInterfaceDown

Name: LdpInterfaceDown (21) Severity: critical Unspecified

Type: ProtocolAlarm (1) Implicitly cleared: false
Package: ldp Default probable cause: protocolDown (1)
Raised on class: ldp.Interface
Description: The alarm is raised when an LDP interface is operationally down.
Remedial action: Check operational state down reason and state qualifier, then update accordingly.
Table 39-487 LegalReq_legalReqFileDeliveryFailureclearance

releases

LegalReq_legalReqFileDeliveryFailureclearance Implicitly cleared: true
(6091)
Type: processingErrorAlarm (81) fileError (700)
Package: femto
Raised on class: femto.LegalReq
Description: This alarm is generated when the FGW succeeds in sending a previously failed legal req file.
Table 39-488 Licensed3RouterLimitExceeded

releases

Licensed3RouterLimitExceeded Implicitly cleared: true
(694)
Type: cpamLicensingAlarm (39) cpamLicensedLimitExceeded (285)
Package: security
Raised on class:
Description: The alarm is raised when the number of third-party routers in the 5650 CPAM network reaches
100 percent of the license capacity.
Raising condition: (’isLicensed3RouterLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensed3RouterLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Third Party Router licenses purchased and available on the
CPAM server is insufficient as compared to the number of third party routers under management in the
network. Please contact Alcatel-Lucent Sales to purchase additional licenses.
Table 39-489 Licensed3RouterLimitNearing

releases

Licensed3RouterLimitNearing Implicitly cleared: true
(695)
Type: cpamLicensingAlarm (39) cpamLicensedLimitNearing (283)
Package: security
Raised on class:
75 to 90 percent of the license capacity.
Table 39-490 Licensed3RouterLimitNearlyExceeded

releases

Licensed3RouterLimitNearlyExceeded Implicitly cleared: true
(696)
Type: cpamLicensingAlarm (39) cpamLicensedLimitNearlyExceeded (284)
Package: security
Raised on class:
90 to 100 percent of the license capacity.
Table 39-491 LicensedBgpRouteProfileLimitExceeded

releases

LicensedBgpRouteProfileLimitExceeded Implicitly cleared: true
(5132)
Package: security
Raised on class: security.CpamLicense
Description: The alarm is raised when the number of BGP Route Profiles in the 5650 CPAM reaches 100
percent of the license capacity.
Raising condition: (’isLicensedBgpProfileLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedBgpProfileLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Bgp Route Profile Module licenses purchased and available
on the CPAM server is insufficient as compared to the number of Bgp Route Profiles in the network. Please
contact Alcatel-Lucent Sales to purchase additional licenses.
Table 39-492 LicensedBgpRouteProfileLimitNearing

releases

LicensedBgpRouteProfileLimitNearing Implicitly cleared: true
(5133)
Package: security
Description: The alarm is raised when the number of BGP Route Profiles in the 5650 CPAM reaches 75 to 90
Remedial action: Informational - The number of Bgp Route Profile Module licenses purchased and available
on the CPAM server is insufficient as compared to the number of Bgp Route Profiles in the network. Please
Table 39-493 LicensedBgpRouteProfileLimitNearlyExceeded

major releases

LicensedBgpRouteProfileLimitNearlyExceeded Implicitly cleared: true
(5134)
Type: cpamLicensingAlarm (39) cpamLicensedLimitNearlyExceeded
Package: security (284)
Description: The alarm is raised when the number of BGP Route Profiles in the 5650 CPAM reaches 90 to
100 percent of the license capacity.
Remedial action: Informational - The number of Bgp Route Profiles Module licenses purchased and available
on the CPAM server is insufficient as compared to the number of BGP Route Profiles in the network. Please
Table 39-494 LicensedBigRouterLimitExceeded

releases

LicensedBigRouterLimitExceeded Implicitly cleared: true
(709)
Package: security
Raised on class:
Description: The alarm is raised when the number of Alcatel-Lucent large routers in the network reaches 100
percent of the 5650 CPAM license capacity.
Raising condition: (’isLicensedBigRouterLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedBigRouterLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Big Router licenses purchased and available on the CPAM
server is insufficient as compared to the number of big routers under management in the network. Please
Table 39-495 LicensedBigRouterLimitNearing

releases

LicensedBigRouterLimitNearing Implicitly cleared: true
(710)
Package: security
Raised on class:
Description: The alarm is raised when the number of Alcatel-Lucent large routers in the network reaches 75 to
90 percent of the 5650 CPAM license capacity.
Table 39-496 LicensedBigRouterLimitNearlyExceeded
releases

LicensedBigRouterLimitNearlyExceeded Implicitly cleared: true
(711)
Package: security
Description: The alarm is raised when the number of Alcatel-Lucent large routers in the network reaches 90 to
100 percent of the 5650 CPAM license capacity.
Table 39-497 LicensedImpactAnalysisRouterLimitExceeded

releases

LicensedImpactAnalysisRouterLimitExceeded Implicitly cleared: true
(712)
Package: security
Raised on class:
security.CpamLicenseScenario
Description: The alarm is raised when the number of routers in a simulation scenario reaches 100 percent of
the license capacity.
Raising condition: (’isLicensedRouterLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedRouterLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of licenses purchased and available on the CPAM server for
routers in a simulation scenario is insufficient as compared to the number of routers in a simulation scenario.
Please contact Alcatel-Lucent Sales to purchase additional licenses.
Table 39-498 LicensedImpactAnalysisRouterLimitNearing

releases

LicensedImpactAnalysisRouterLimitNearing Implicitly cleared: true
(713)
Package: security
Raised on class:
security.CpamLicenseScenario
Description: The alarm is raised when the number of routers in a simulation scenario reaches 75 to 90
Table 39-499 LicensedImpactAnalysisRouterLimitNearlyExceeded

major
releases

LicensedImpactAnalysisRouterLimitNearlyExceeded Implicitly cleared: true
(714)
Type: cpamLicensingAlarm (39) cpamLicensedLimitNearlyExceeded
Raised on class: security.CpamLicenseScenario
Description: The alarm is raised when the number of routers in a simulation scenario reaches 90 to 100
Table 39-500 LicensedIpPathLimitExceeded

releases

LicensedIpPathLimitExceeded Implicitly cleared: true
(715)
Package: security
Raised on class:
Description: The alarm is raised when the number of IP path monitors in the 5650 CPAM reaches 100 percent
of the license capacity.
Raising condition: (’isLicensedIpPathLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedIpPathLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Path Computation Module licenses purchased and available
on the CPAM server is insufficient as compared to the number of PCA paths in the network. Please contact
Alcatel-Lucent Sales to purchase additional licenses.
Table 39-501 LicensedIpPathLimitNearing

releases

LicensedIpPathLimitNearing Implicitly cleared: true
(716)
Package: security
Raised on class:
Description: The alarm is raised when the number of IP path monitors in the 5650 CPAM reaches 75 to 90
Table 39-502 LicensedIpPathLimitNearlyExceeded

releases
LicensedIpPathLimitNearlyExceeded Implicitly cleared: true
(717)
Package: security
Raised on class:
Description: The alarm is raised when the number of IP path monitors in the 5650 CPAM reaches 90 to 100
Table 39-503 LicensedMcRouterLimitExceeded

releases

LicensedMcRouterLimitExceeded Implicitly cleared: true
(718)
Package: security
Raised on class:
Description: The alarm is raised when the number of multicast routers in the 5650 CPAM reaches 100 percent
of the license capacity.
Raising condition: (’isLicensedMcRouterLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedMcRouterLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Multicast Router licenses purchased and available on the
CPAM server is insufficient as compared to the number of multicast routers under management in the network.
Table 39-504 LicensedMcRouterLimitNearing

releases

LicensedMcRouterLimitNearing Implicitly cleared: true
(719)
Package: security
Raised on class:
Description: The alarm is raised when the number of multicast routers in the 5650 CPAM reaches 75 to 90
Table 39-505 LicensedMcRouterLimitNearlyExceeded

releases
LicensedMcRouterLimitNearlyExceeded Implicitly cleared: true
(720)
Package: security
Description: The alarm is raised when the number of multicast routers in the 5650 CPAM reaches 90 to 100
Table 39-506 LicensedSmallRouterLimitExceeded

releases

LicensedSmallRouterLimitExceeded Implicitly cleared: true
(727)
Package: security
Raised on class:
Description: The alarm is raised when the number of Alcatel-Lucent small routers in the network reaches 100
percent of the 5650 CPAM license capacity.
Raising condition: (’isLicensedSmallRouterLimitExceeded’ EQUAL ’true’)
Clearing condition: (’isLicensedSmallRouterLimitExceeded’ NOT EQUAL ’true’)
Remedial action: Informational - The number of Small Router licenses purchased and available on the CPAM
server is insufficient as compared to the number of small routers under management in the network. Please
Table 39-507 LicensedSmallRouterLimitNearing

releases

LicensedSmallRouterLimitNearing Implicitly cleared: true
(728)
Package: security
Raised on class:
to 90 percent of the 5650 CPAM license capacity.
Table 39-508 LicensedSmallRouterLimitNearlyExceeded

major releases

LicensedSmallRouterLimitNearlyExceeded Implicitly cleared: true
(729)
Type: cpamLicensingAlarm (39) Default probable cause:
Package: security cpamLicensedLimitNearlyExceeded (284)
to 100 percent of the 5650 CPAM license capacity.
Table 39-509 licenseExpiration

releases
Name: licenseExpiration (2911) Severity: variable Unspecified

Package: ranlicense Default probable cause: licenseExpired
ranlicense.RANLicense
Description: The alarm is raised when a RAN license expires.
Remedial action: Provide a new LKDI license file with a further expiration date.
Table 39-510 LicenseMisMatch

releases
Name: LicenseMisMatch (693) Severity: critical Unspecified

Type: cpamLicensingAlarm (39) Implicitly cleared: false
Package: security Default probable cause:
Raised on class: cpamLicenseMisMatch (507)
Description: The alarm is raised when the primary 5650 CPAM server license does not match the standby
5650 CPAM server license.
Remedial action: Informational - Please ensure that the same license key is installed on both the active and
standby SAM/CPAM servers
Table 39-511 liDestinationChangeReject

releases

liDestinationChangeReject Implicitly cleared: false
(551)
Type: ConfigurationAlarm (15) tMirrorDestinationChangeReject (421)
Package: mirrorli
Raised on class:
mirrorli.LIMirrorSiteCfg
Description: The alarm is raised when an operator tries to modify a mirror destination that is in use by an LI
mirror.
Table 39-512 liDestinationEnabled

releases
Name: liDestinationEnabled Severity: warning Unspecified

Package: mirrorli tMirrorDestinationEnabled (420)
Raised on class:
Description: The alarm is raised when a mirror destination Operational State changes from Down to Up.
Table 39-513 LIF

releases
Name: LIF (804) Severity: major Unspecified

(4) Default probable cause: lossOfIMAFrame
Package: mpr (570)
Raised on class: mpr.IMALink
Description: The alarm is raised when a Loss of IMA Frame signal is detected on an ASAP MDA.
Table 39-514 liFilterAssignToItfWarn

releases
Name: liFilterAssignToItfWarn Severity: warning Unspecified

Package: mirrorli tMirrorFilterAssignToItfWarn (426)
Raised on class:
Description: The alarm is raised when an operator tries to assign a filter that is in use by LI to an interface.
Table 39-515 liFilterAssignToSapWarn

releases
Name: liFilterAssignToSapWarn Severity: warning Unspecified

Package: mirrorli tMirrorFilterAssignToSapWarn (424)
Raised on class:
Description: The alarm is raised when an operator tries to assign a filter that is in use by LI to a SAP.
Table 39-516 liFilterAssignToSdpWarn

releases
Name: liFilterAssignToSdpWarn Severity: warning Unspecified

Package: mirrorli tMirrorFilterAssignToSdpWarn (425)
Raised on class:
Description: The alarm is raised when an operator tries to assign a filter that is in use by LI to an SDP.
Table 39-517 LinkAggMemberMisconfigured

releases

LinkAggMemberMisconfigured Implicitly cleared: true
(652)
Type: lnkaggAlarm (56) lagMemberMisconfigured (483)
Package: lag
Raised on class: lag.Interface
Description: The alarm is raised when one or more misconfigured LAG members are detected, for example,
when some LAG members are in access mode and some are in network mode.
Remedial action: A configuration error has occurred which must be corrected. The configuration of the LAG
port member should be checked and the configuration error corrected,
Table 39-518 LinkAggModeMisconfigured

releases

LinkAggModeMisconfigured (653) Implicitly cleared: true
Type: lnkaggAlarm (56) Default probable cause:
Package: lag lagModeMisconfigured (484)
Description: The alarm is raised when the LAG mode differs from the mode of one or more LAG members, for
example, when the LAG mode is access and the LAG members are in network mode.
Remedial action: A configuration error has occurred which must be corrected. The configuration of the LAG
port member should be checked and the configuration error corrected,
Table 39-519 LinkAggPortJoin

Name: LinkAggPortJoin (654) Severity: info Unspecified

Type: lnkaggAlarm (56) Implicitly cleared: false
Package: lag Default probable cause: lagPortJoin (485)
Description: The alarm is raised when a LAG port joins a LAG by entering the attached state.

Table 39-520 LinkAggPortLeave
Name: LinkAggPortLeave (655) Severity: info Unspecified

Type: lnkaggAlarm (56) Implicitly cleared: false
Package: lag Default probable cause: lagPortLeave (486)
Description: The alarm is raised when a LAG port leaves a LAG by exiting the attached state.
Table 39-521 LinkAggPortRemove

releases
Name: LinkAggPortRemove Severity: warning Unspecified

Type: lnkaggAlarm (56) Default probable cause: lagPortRemove
Package: lag (487)
Description: The alarm is raised when a LAG port is removed from a LAG because of an invalid configuration.
Remedial action: A configuration error has occurred which must be corrected. Please check the configuration
of the port in question.
Table 39-522 LinkDown (optical)

releases
Name: LinkDown (12) Severity: critical Unspecified

(4) Default probable cause: OperationalStateDown
Package: optical (1963)
Raised on class:
optical.OpticalLink
Description: The alarm is raised when any of the Optical Link end point is operationally down.
Remedial action: Informational - If the alarm persists or is occurring frequently then investigation is required
by looking at the active alarms on the Link End points to understand why the underlying transport network is
unreliable.
Table 39-523 LinkIdentifierMismatch (mwa)

releases
Name: LinkIdentifierMismatch Severity: variable Unspecified

Package: mwa LinkIdentifierMismatch (1916)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects a link identifier mismatch.
information.
Table 39-524 LinkIdentifierMismatch (radioequipment)
releases
Name: LinkIdentifierMismatch (686) Severity: variable Unspecified

Raised on class: linkIdentifierMismatch (501)
Description: The alarm is raised when an MSS detects a link identifier mismatch.
Table 39-525 linkLoss

releases
Name: linkLoss (6389) Severity: critical Unspecified

Package: femto communicationsSubsystemFailure (915)
Raised on class:
femto.FemtoNetwork
Description: This alarm indicates that there was a loss of communication link with FileServer.
Table 39-526 liSourceDisabled

releases
Name: liSourceDisabled (563) Severity: warning Unspecified

Type: ConfigurationAlarm (15) Implicitly cleared: false
Package: mirrorli Default probable cause:
Raised on class: tMirrorSourceDisabled (433)
mirrorli.LISourceCfg
Description: The alarm is raised when an LI mirror source Operational State changes from Up to Down.
Table 39-527 liSourceEnabled

releases
Name: liSourceEnabled (562) Severity: warning Unspecified

Package: mirrorli Default probable cause: tMirrorSourceEnabled
mirrorli.LISourceCfg
Description: The alarm is raised when an LI mirror source Operational State changes from Down to Up.

Table 39-528 liSourceFilterAssignReject
releases

liSourceFilterAssignReject Implicitly cleared: false
(557)
Type: ConfigurationAlarm (15) tMirrorSourceFilterAssignReject (427)
Package: mirrorli
Raised on class:
mirrorli.LIMgmtSite
Description: The alarm is raised when an operator tries to modify a filter that is in use by LI.
Table 39-529 liSourceFilterAssignWarn

releases

liSourceFilterAssignWarn (559) Implicitly cleared: false
Package: mirrorli tMirrorSourceFilterAssignWarn (429)
Raised on class:
mirrorli.LIMgmtSite
Description: The alarm is raised when an operator assigns a mirror filter that is in use by LI and the
assignment may be overruled.
Table 39-530 liSourceFilterChanged

releases
Name: liSourceFilterChanged Severity: warning Unspecified

Package: mirrorli tMirrorSourceLiFilterChanged (1152)
Raised on class:
mirrorli.LIMgmtSite
Description: The alarm is raised when a parameter of a filter which is referenced by Lawful Intercept (LI), or a
parameter of one of its entry is changed. This notification may be triggered only if the LI filter lock is overruled,
and one of the following actions occurs: -a filter referenced by LI has been deleted. -one of the parameters
(default-action, scope) of a filter which is referenced by LI has been changed. -a filter which is referenced by LI
is overwritten. -a new entry is created for a filter which is referenced by LI. -an entry of a filter which is
referenced by LI is activated. -an entry is removed from a filter which is referenced by LI. -an entry of a filter
which is referenced by LI is renumbered. -oneof the parameters of an entry in a filter which is referenced by LI
is changed.
Table 39-531 liSourceFilterOverruled

releases
Name: liSourceFilterOverruled Severity: warning Unspecified

Package: mirrorli tMirrorSourceFilterOverruled (428)
Raised on class:
mirrorli.LIMgmtSite
Description: The alarm is raised when the assignment of a mirror filter is overruled by another filter
assignment.
Table 39-532 liSourceIP6FltrChangeReject

releases

liSourceIP6FltrChangeReject Implicitly cleared: false
(4377)
Type: ConfigurationAlarm (15) tMirrorSourceIP6FltrChangeReject (1562)
Package: mirrorli
Raised on class:
Description: The alarm is raised when an operator tries to modify an IPv6 filter or an IPv6 filter entry that is in
use by LI.
Table 39-533 liSourceIPFltrChangeReject

releases

liSourceIPFltrChangeReject Implicitly cleared: false
(552)
Type: ConfigurationAlarm (15) tMirrorSourceIPFltrChangeReject (422)
Package: mirrorli
Raised on class:
Description: The alarm is raised when an operator tries to modify an IP filter or an IP filter entry that is in use
by LI.
Table 39-534 liSourceMacFltrChangeReject

releases

liSourceMacFltrChangeReject Implicitly cleared: false
(553)
Type: ConfigurationAlarm (15) tMirrorSourceMacFltrChangeReject (423)
Package: mirrorli
Raised on class:
Description: The alarm is raised when an operator tries to modify a MAC filter or a MAC filter entry that is in
use by LI.
Table 39-535 liSourceSapChange

releases
Name: liSourceSapChange (560) Severity: warning Unspecified

Package: mirrorli Default probable cause:
Raised on class: tMirrorSourceSapChange (430)
mirrorli.LISourceInterface
Description: The alarm is raised when a SAP that is associated with LI is modified or deleted.
Table 39-536 liSourceSubscriberChange

releases
Name: liSourceSubscriberChange Severity: warning Unspecified

Package: mirrorli tMirrorSourceSubChange (431)
Raised on class:
mirrorli.LISourceSubscriberHost
Description: The alarm is raised when a subscriber that is associated with LI is modified or deleted.
Table 39-537 LocalRadioTxMuteAbnormalState

releases

LocalRadioTxMuteAbnormalState Implicitly cleared: true
(3941)
Type: localRadioTxMuteABNAlarm LocalRadioTxMuteABNProblem (1523)
(117)
Package: radioequipment
Raised on class:
Description: The alarm is raised when abnormal state resulted due to local radio Tx is muted manually.
Remedial action: The alarm is raised when abnormal state resulted due to local radio Tx is muted manually.
Table 39-538 LODS

releases
Name: LODS (805) Severity: major Unspecified

communicationsAlarm (4) Default probable cause:
Package: mpr lossOfDelaySynchronization (571)
Raised on class:
mpr.IMALink
Description: The alarm is raised when a Loss of Delay Synchronization signal is detected on an ASAP MDA.
Table 39-539 LoopbackActivateAbnormalState (equipment)
releases

LoopbackActivateAbnormalState Implicitly cleared: true
(3942)
Type: loopbackActivateABNAlarm LoopbackActivateABNProblem (1524)
(118)
Package: equipment
Description: The alarm is raised when abnormal state resulted due to loopback activated.
Remedial action: The alarm is raised when abnormal state resulted due to manual loopback activation by
user.
Table 39-540 LoopbackActivateAbnormalState (radioequipment)

releases

LoopbackActivateAbnormalState Implicitly cleared: true
(3942)
Type: loopbackActivateABNAlarm LoopbackActivateABNProblem (1524)
(118)
Package: radioequipment
Raised on class:
Description: The alarm is raised when abnormal state resulted due to loopback activated.
Remedial action: The alarm is raised when abnormal state resulted due to manual loopback activation by
user.
Table 39-541 LoopProblem

releases
Name: LoopProblem (1145) Severity: variable Unspecified

Raised on class: loopProblem (851)
Description: The alarm is raised when there is a loss of communication command path between far end
transmitter and local receiver .
Table 39-542 LossOfAlignment

releases
Name: LossOfAlignment (629) Severity: variable Unspecified

Package: equipment Default probable cause: lossOfAlignment
equipment.Equipment
Description: The alarm is raised when a Loss of Alignment signal is detected.

Table 39-543 LossOfCESoEthFrames

releases
Name: LossOfCESoEthFrames Severity: variable Unspecified

Package: equipment lossOfCESoEthFrames (870)
Description: The alarm is raised when an Ethernet frame loss is detected on a CES.
Remedial action: The alarm is raised when a loss occurs on CES over Ethernet Frames.
Table 39-544 LossOfESMC

releases
Name: LossOfESMC (2939) Severity: variable Unspecified

Package: equipment Default probable cause: lossOfESMC
equipment.Equipment
Description: The alarm is raised when a loss of ESMC signal failure is detected.
Table 39-545 LossOfFrame (equipment)

Name: LossOfFrame (630) Severity: variable Unspecified

Package: equipment Default probable cause: lossOfFrame (97)
Description: The alarm is raised when an LOF is detected on a port.
Table 39-546 LossOfPointer

Name: LossOfPointer (3623) Severity: variable Unspecified

Package: equipment Default probable cause: lossOfPointer
equipment.Port
Description: The alarm is raised when a loss of pointer occurs

Table 39-547 LossOfProtection (equipment)

releases
Name: LossOfProtection (1169) Severity: variable Unspecified

(4) Default probable cause: lossOfProtection
Raised on class:
equipment.Port
Description: The alarm is raised when an MPT radio protection loss occurs.
Remedial action: The alarm is raised when a protection loss occurs on MPT Radio.
Table 39-548 LossOfProtection (mpr)

releases
Name: LossOfProtection (1169) Severity: variable Unspecified

Package: mpr Default probable cause: lossOfProtection
Description: The alarm is raised when a Loss of Protection occurs
Table 39-549 LossOfRadioFrame

releases
Name: LossOfRadioFrame (4828) Severity: variable Unspecified

Package: mwa Default probable cause: LossOfFrame
mwa.PortTermination
Description: The alarm is raised when a MPT detects a Loss of Radio Frame from Radio Path
information.
Table 39-550 LossOfRadioFramesAlignment

releases
Name: LossOfRadioFramesAlignment Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: LossOfAlignment
Package: mwa (1917)
Description: The alarm is raised when a MPT detects a Loss of Radio Frames Alignment
information.
Table 39-551 LossOfSignal (equipment)

Name: LossOfSignal (631) Severity: variable Unspecified

Package: equipment Default probable cause: lossOfSignal (99)
Description: The alarm is raised when a Loss of Signal is detected on a port.
Table 39-552 LowSwitchFabricCap

releases
Name: LowSwitchFabricCap Severity: major Unspecified

Package: equipment LowSwitchFabricCapacity (2094)
Raised on class:
equipment.Card
Description: The alarm is raised when the total switch fabric capacity becomes less than the line card
capacity due to link failures. At least one of the taps on the Card is below 100% capacity.
Remedial action: 1. Make sure that the hardware switching fabric capacity is more than the line card capacity.
2. Please reboot the card and check if it resolves the problem. If problem persists after reboot, please contact
Table 39-553 LpsLearnMac

releases
Name: LpsLearnMac (519) Severity: warning Unspecified

Type: learnedPortSecurityAlarm Implicitly cleared: true
Package: lps portLearnedBridgedMAC (394)
Raised on class:
lps.LearnedPortSecurity
Description: The alarm is raised when an LPS port learns a bridged MAC address.
Table 39-554 LpsPortUpAfterLearningWindowExpired

releases

LpsPortUpAfterLearningWindowExpired Implicitly cleared: true
(517)
Type: learnedPortSecurityAlarm (51) portUpAfterLearningWindowExpired (392)
Package: lps
Raised on class: lps.LPSConfiguration
Description: The alarm is raised either when an LPS port is enabled after the learning window expires and
MAC address learning on the port is disabled, or when the learning window expires with slice and port values
of 0.
Table 39-555 LsdbOverflow

Name: LsdbOverflow (53) Severity: major Unspecified

Package: ospf Default probable cause: resourceFull (53)
Raised on class: ospf.Site
Description: The alarm is raised when the number of received external LSAs exceeds the configured number
allowed. By default, there is no limit. The alarm information includes the configured LSDB limit and one of the
following LSDB overflow states: - 0, which means no overflow - 1, which means nearing limit - 2, which means
limit exceeded
Remedial action: Informational - the number of received external LSAs exceeds the configured number
allowed. The alarm will also be raised when external LSAs is nearing limit.
Table 39-556 LudbDhcpHostGroupIfTooLong

releases

LudbDhcpHostGroupIfTooLong Implicitly cleared: false
(4627)
Type: ludbDhcpHostGroupIfTooLong (1895)
LudbDhcpHostGroupIfTooLongAlarm
(129)
Package: localuserdb
Raised on class:
localuserdb.DhcpHost
Description: The alarm is raised when the default MSAP group interface name of a DHCP Host, concatenated
with the port ID is longer than 32 characters.
Remedial action: The string configured in DHCP Host as default MSAP Group Interface Name concatenated
with the port-id is longer than 32 characters. It is an invalid configuration since it exceeds the length allowed for
a Group Interface Name. (Please) Reconfigure the MSAP Group Interface Name or refer to the Local User
Database documentation for assistance.
Table 39-557 LudbPppHostGroupIfTooLong

releases

LudbPppHostGroupIfTooLong Implicitly cleared: false
(4628)
Type: ludbPppHostGroupIfTooLong (1896)
LudbPppHostGroupIfTooLongAlarm
(130)
Package: localuserdb
Raised on class:
localuserdb.PppHost
Description: The alarm is raised when the default MSAP group interface name of a PPP host, concatenated
with the port ID is longer than 32 characters.
Remedial action: The string configured in PPP Host as default MSAP Group Interface Name concatenated
with the port-id is longer than 32 characters. It is an invalid configuration since it exceeds the length allowed for
a Group Interface Name. (Please) Reconfigure the MSAP Group Interface Name or refer to the Local User
Database documentation for assistance.
Table 39-558 MacAccountingLimitReached (rtr)

releases

MacAccountingLimitReached Implicitly cleared: true
(4907)
Type: macAccountingAlarm (132) macAccountingLimitReached (1964)
Package: rtr
Raised on class:
Description: The alarm is raised when the system detects that the MAC accounting table is full.
Remedial action: This alarm can be cleared when the used MAC entries are deleted by disabling MAC
accounting on a particular interface or through manual intervention with a user command such as clear router
interface mac.
Table 39-559 MacAccountingLimitReached (service)

releases

MacAccountingLimitReached Implicitly cleared: true
(4907)
Type: macAccountingAlarm (132) macAccountingLimitReached (1964)
Package: service
Raised on class:
Description: The alarm is raised when the system detects that the MAC accounting table is full.
Remedial action: This alarm can be cleared when the used MAC entries are deleted by disabling MAC
accounting on a particular interface or through manual intervention with a user command such as clear router
interface mac.
Table 39-560 MacPinningViolation

releases
Name: MacPinningViolation Severity: warning Unspecified

Type: serviceAlarm (16) Default probable cause: macAddressPinned
Package: vpls (348)
Raised on class:
vpls.AbstractSite
Description: The alarm is raised when an attempt is made to assign a pinned MAC address to another L2
access interface or spoke SDP binding in an M-VPLS or VPLS.
Remedial action: Use a MAC address that is not already pinned.
Table 39-561 ManagedRouteAddFailed

releases
ManagedRouteAddFailed Implicitly cleared: false
(5130)
Type: processingErrorAlarm tmnxVRtrManagedRouteAddFailed (2060)
(81)
Package: rtr
Raised on class:
Description: The alarm is raised when a managed route could not be installed.
Remedial action: Check the additional text of the alarm for more details.
Table 39-562 ManagedRouteFailedRetryThresholdCrossed

major releases

ManagedRouteFailedRetryThresholdCrossed Implicitly cleared: true
(397)
Type: topologyAlarm (34) managedRouteCouldNotBeSetup (298)
Package: topology
Raised on class: topology.RouteManager
Description: The alarm is raised when the 5650 CPAM cannot set up a managed route after the number of
attempts specified by the cpamManagedRoute problematicThresholdAlarmAfter value in the nms-server.xml
countdown. The alarm is not raised if the problematicRetryStrategy value is set to the default of reactive.
Table 39-563 ManagedRouteRetryAttemptsExhausted

releases

ManagedRouteRetryAttemptsExhausted Implicitly cleared: false
(398)
Type: topologyAlarm (34) managedRouteCouldNotBeSetup (298)
Package: topology
Raised on class:
topology.RouteManager
Description: The alarm is raised when the 5650 CPAM stops trying to set up a managed route after the
number of attempts specified by the cpamManagedRoute problematicDeadAfter value in the nms-server.xml
countdown. The alarm is not raised if the problematicRetryStrategy value is set to the default value of reactive.
Table 39-564 ManagementVlanConflict

releases
Name: ManagementVlanConflict Severity: warning Unspecified

Package: vlan topologyMisconfigured (81)
Raised on class: vlan.Vlan
Description: The alarm is raised when a management VLAN ID is in use by another service type.
Raising condition: (’managementVlanConflict’ EQUAL ’true’)
Clearing condition: (’managementVlanConflict’ EQUAL ’false’)
Remedial action: Ensure that the VLAN ID of this Management Service is not used on any other type of VLAN
Service.
Table 39-565 ManualCpaaSwitchover

releases
Name: ManualCpaaSwitchover Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: CPAASwitchover
Description: The alarm is raised when an operator has manually initiated a switchover. This alarm is not self
clearing. Another switchover will not be permitted for 10 mins.
Remedial action: Manual Switchover has been executed.
Table 39-566 MaxFecLimitReached

releases
Name: MaxFecLimitReached Severity: major Unspecified

Type: processingErrorAlarm Default probable cause: MaxFecLimitReached
(81) (2448)
Package: ldp
Description: The alarm is raised when the number of FECs accepted from the peer has reached the value
specified by fecLimit. The alarm is cleared when a new MaxFecThresholdChange notification is received.
Remedial action: Number of FECs accepted from the peer has reached the value specified by FEC Limit.
Appropriate configuration changes in local or peer LSR will be required.
Table 39-567 MaxFecThresholdChange

releases
Name: MaxFecThresholdChange Severity: warning Unspecified

Package: ldp MaxFecThresholdChange (2449)
Description: The alarm is raised when the number of FECs accepted from the peer has exceeded the
threshold percent of the value specified by fecLimit. The alarm is cleared when the number of FECs received
drops below the threshold percent of the value specified by fecLimit.
Remedial action: Number of FECs accepted from the peer has exceeded or dropped below the threshold
percent of the value specified by FEC Limit. Appropriate configuration changes in local or peer LSR will be
required.
Table 39-568 MaxNumExportRoutesReached

releases

MaxNumExportRoutesReached Implicitly cleared: true
(1116)
Type: ProtocolAlarm (1) MaxNumExportRoutesReached (828)
Package: vprn
Raised on class: vprn.AbstractSite
Description: The alarm is raised when the number of routes exported from a route table to a VRF reaches the
configured maximum.
Table 39-569 MaxNumIpv6RoutesReached

releases

MaxNumIpv6RoutesReached Implicitly cleared: true
(505)
Type: ProtocolAlarm (1) MaxNumIpv6RouteReached (389)
Package: l3fwd
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the number of IPv6 routes in a VPRN exceeds the configured
maximum.
Remedial action: The number of IPv6 routes has exceeded the configured maximum for the VPRN - the route
table must be examined to ensure that all of the routes in the table are valid and not the result of a
misconfiguration in the VPRN service. If all of the routes appear to be valid then the value used as the
maximum value should be revisited.
Table 39-570 MaxNumMcastRoutes

releases

MaxNumMcastRoutes (206) Implicitly cleared: true
Package: l3fwd MaxNumMcastRoutesReached (160)
Raised on class: l3fwd.Site
Description: The alarm is raised when the number of multicast routes in a VPRN exceeds the configured
maximum.
Remedial action: Informational. The number of multicast routes in a VPRN exceeds the configured maximum.
The value used as the threshold value should be revisited.
Table 39-571 MaxNumRoutesReached

releases
Name: MaxNumRoutesReached Severity: major Unspecified

Package: l3fwd MaxNumRoutesReached (898)
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the number of routes in a VPRN reaches the maximum number of
routes specified in the VPRN configuration. The alarm information includes the number of routes, the specified
maximum, and the route type, which is either IPv4 or IPv6.
Table 39-572 MaxNumV6ExportRoutesReached

releases

MaxNumV6ExportRoutesReached Implicitly cleared: true
(4398)
Type: ProtocolAlarm (1) MaxNumV6ExportRoutesReached (1575)
Package: vprn
Raised on class: vprn.AbstractSite
Description: The alarm is raised when the number of IPv6 routes exported from a route table to a VRF
reaches the configured maximum.
Table 39-573 MaxPdnConnections

releases
Name: MaxPdnConnections Severity: major Unspecified

Type: EpcAlarm (59) Default probable cause: thresholdCrossed
Package: lte (12)
Raised on class: lte.PdnApn
Description: The alarm is generated when the maximum number of Packet Data Network (PDN) connections
for this Access Point Name (APN) on the gateway is reached.
Remedial action: Maximum number of PDN connections for this APN on the gateway is reached.To accept
new PDN connections, system has to wait until the number of PDN connections goes below the value of
PdnApnMaxPdnConnections.
Table 39-574 McacPolicyDropped (igmp)

releases
Name: McacPolicyDropped Severity: major Unspecified

Type: communicationsAlarm Default probable cause:
(4) igmpGroupOnSapDropped (246)
Package: igmp
Raised on class:
igmp.Interface
Description: The alarm is raised when an IGMP group is dropped because a multicast CAC policy is applied.
Table 39-575 McacPolicyDropped (pim)

releases
Name: McacPolicyDropped Severity: major Unspecified

Type: communicationsAlarm Default probable cause:
(4) pimGroupOnSapDropped (266)
Package: pim
Raised on class:
pim.Interface
Description: The alarm is raised when a PIM group is dropped because a multicast CAC policy is applied.
Table 39-576 McacPolicyDropped (svt)

releases
Name: McacPolicyDropped (341) Severity: major Unspecified

Package: svt Default probable cause:
Raised on class: igmpGroupOnSdpBindDropped (265)
Description: The alarm is raised when an IGMP group is dropped because a multicast CAC policy is applied
to an SDP binding.
Table 39-577 McacPolicyDropped (vpls)

releases
Name: McacPolicyDropped (341) Severity: major Unspecified

Package: vpls Default probable cause:
Raised on class: igmpGroupOnSapDropped (246)
Description: The alarm is raised when an IGMP group is removed from a SAP because a multicast CAC
policy is applied.
Table 39-578 McastRoutesMidLevelThresholdReached

releases

McastRoutesMidLevelThresholdReached Implicitly cleared: false
(207)
Type: ProtocolAlarm (1) MidLevelThresholdReached (161)
Package: l3fwd
Raised on class: l3fwd.Site
Description: The alarm is raised when the number of multicast routes in a VPRN exceeds the configured
threshold value. The alarm information includes the number of multicast routes and the threshold value.
Remedial action: the number of multicast routes in a VPRN exceeds the configured threshold value. The
value used as the threshold value should be revisited.
Table 39-579 McIPsecTunnelGroupSyncTagMisconfigured

major releases

McIPsecTunnelGroupSyncTagMisconfigured Implicitly cleared: true
(4817)
Type: redundancyAlarm (52) ipsecGroupSyncTagMisconfigure (1902)
Package: multichassis
Raised on class:
multichassis.MultiChassisIPSecGroup
Description: The alarm is raised when a peer of MC IPsec tunnel groups has unconfigured or mismatched
synchronization tag.
Raising condition: ((’Synchronization Tag’ NOT EQUAL ’Synchronization Tag’) OR ((’Synchronization Tag’
EQUAL ’\"\"’) OR (’Synchronization Tag’ EQUAL ’\"\"’)))
Clearing condition: ((’Synchronization Tag’ EQUAL ’Synchronization Tag’) AND ((’Synchronization Tag’ NOT
EQUAL ’\"\"’) AND (’Synchronization Tag’ NOT EQUAL ’\"\"’)))
Remedial action: Check if the synchronization tag has been configured for the MC IPsec tunnel group peer
and they matches.
Table 39-580 McLagSourceBMacLsbMisconfigured (lag)

releases

McLagSourceBMacLsbMisconfigured Implicitly cleared: true
(776)
Type: configurationAlarm (11) McLagSourceBMacLsbMisconfigured (551)
Package: lag
Raised on class: lag.MultiChassisLag
Description: The alarm is raised when the 5620 SAM detects a mismatch in the last 16 bits of the source
backbone MAC address on the peer device. This mismatch prevents PBB access dual homing from operating.
Raising condition: (’srcBMacLSBMisconfigured’ EQUAL ’true’)
Clearing condition: (’srcBMacLSBMisconfigured’ EQUAL ’false’)
Remedial action: Check the MAC Address LSB is correct for source backbone address.
Table 39-581 McLagSourceBMacLsbMisconfigured (multichassis)

releases

McLagSourceBMacLsbMisconfigured Implicitly cleared: true
(776)
Type: configurationAlarm (11) McLagSourceBMacLsbMisconfigured (551)
Package: multichassis
Raised on class:
multichassis.MultiChassisLag
Description: The alarm is raised when the 5620 SAM detects a mismatch in the last 16 bits of the source
backbone MAC address on the peer device. This mismatch prevents PBB access dual homing from operating.
Raising condition: (’srcBMacLSBMisconfigured’ EQUAL ’true’)
Clearing condition: (’srcBMacLSBMisconfigured’ EQUAL ’false’)
Remedial action: Check the MAC Address LSB is correct for source backbone address.
Table 39-582 McMobileGeoRedChgInfo

releases
Name: McMobileGeoRedChgInfo (4380) Severity: warning Unspecified

Package: multichassis Default probable cause:
Raised on class: equipmentAlarm (1565)
multichassis.MultiChassisPeerMobileGateway
Description: The alarm is raised when the mobile-gateway or the CPM has changed its geo-redundancy state
or the peer’s connection status has changed.
Remedial action: Check what caused this state change. Bring the peer and/or peer-link up and ensure that
the chassis and CPM geo-redundancy states are ’hot’.
Table 39-583 McMobileIssuStateChange

releases
Name: McMobileIssuStateChange (5119) Severity: warning Unspecified

Type: integrityViolation (85) Implicitly cleared: true
Raised on class: mismatchPeerSets (199)
multichassis.MultiChassisPeerMobileSpecifics
Description: The alarm is raised when ISSU state between the mobile-gateways participating in the geo-
redundancy changes
Remedial action: Check what caused this change in ISSU state and correct the issue for geo-redundancy to
work.
Table 39-584 McOmcrClientNumEntriesHigh

releases
Name: McOmcrClientNumEntriesHigh Severity: minor Unspecified

Package: multichassis McOmcrClientNumEntriesHigh (2458)
Raised on class:
multichassis.PeerSynchronizationProtocol
Description: The alarm is raised when the system is configured as an OMCR warm standby system, and the
total number of entries in the MCS database for a particular application becomes high. When the 80% and
90% threshold is crossed, there is no effect. When the 100% threshold is exceeded, the peer indicated by the
values of tmnxMcPeerIpType and tmnxMcPeerIpAddr is shut down automatically by this system.
Remedial action: Reconfigure the oversubscribed multi chassis redundancy set up to reduce the number of
entries protected by this system.
Table 39-585 McPathBlackHole
releases
Name: McPathBlackHole (2940) Severity: critical Unspecified

Description: The alarm is raised when a multicast (S,G) specification enters a black-hole state.
Remedial action: The alarm is raised when a source, group (S,G) goes into a black-hole state. The situation
may occur when a certain source, group(S,G) has a bandwidth higher than it’s configured maximum and no
path/plane that can accommodate for the bandwidth of the new stream. This can be remedied by increasing
the path limit(iom2 and older) or plane limit (iom3 and newer) at the Daughter Card tab or by modifying Ingress
Multicast Path Management policy which assigned to the card.
Table 39-586 McPathsBlackHole

releases
Name: McPathsBlackHole (4903) Severity: critical Unspecified

Type: resourceAlarm (28) Implicitly cleared: false
Description: The alarm is raised when one or more multicast (S,G) specifications enters a black-hole state.
Remedial action: The alarm is raised when one or more source, group (S,G) goes into a black-hole state. The
situation may occur when a certain source, group (S,G) has a bandwidth higher than it’s configured maximum
and no path/plane that can accommodate for the bandwidth of the new stream. This can be remedied by
increasing the path limit(iom2 and older) or plane limit (iom3 and newer) at the Daughter Card tab or by
modifying Ingress Multicast Path Management policy which assigned to the card.
Table 39-587 MD5AuthFailure

releases
Name: MD5AuthFailure (2934) Severity: major Unspecified

Type: communicationsAlarm Implicitly cleared: false
(4) Default probable cause: md5AuthFailure
Package: bgp (1128)
Raised on class: bgp.Md5Key
Description: The alarm is raised when an incoming packet is dropped because of BGP MD5 key
authentication failure.
Remedial action: A configuration error has been made which must be corrected. The MD5 authentication key
configured is incorrect.
Table 39-588 MFibTableSizeLimitReached

releases

MFibTableSizeLimitReached (190) Implicitly cleared: true
Package: vpls resourceLimitReached (131)
Raised on classes:
vpls.AbstractTlsSite
vpls.AbstractBSite
Description: The alarm is raised when the 5620 SAM receives a svcTlsMfibTableFullAlarmRaised trap for a
VPLS site. The alarm clears when the 5620 SAM receives a svcTlsMfibTableFullAlarmCleared trap for the site.
understand why
Table 39-589 MGMCSwitchOverStatusNotify

major releases
Name: MGMCSwitchOverStatusNotify (4814) Severity: info Unspecified

Raised on class: configurationOrCustomizationError (902)
multichassis.MultiChassisPeerMobileGateway
Description: The alarm is raised when the status of switchover enforced on the mobile-gateway in geo-
redundancy changes
Remedial action: Check switchover failure reason and correct the issue in order to perform switchover.
Table 39-590 MgwPeerConnectionStateAlarm

releases

MgwPeerConnectionStateAlarm Implicitly cleared: false
(4399)
Type: MgwPeerConnectionStateAlarm (1576)
connectionStateChangeAlarm
(125)
Package: wlangw
Raised on class: wlangw.MgwPeer
Description: This alarm is raised when the state of a connection with a Mobile Gateway has changed.
[CAUSE] The state of a connection with a Mobile Gateway has changed to Fault. [EFFECT] The effect
depends on the new state. [RECOVERY] No recovery is required on this system.
Remedial action: Fault occurred on the connection with Mobile Gateway. Check the physical connection and
interfaces between Mobile Gateway and WLAN Gateway.
Table 39-591 MgwPeerGtpMismatchAlarm

releases

MgwPeerGtpMismatchAlarm Implicitly cleared: false
(5144)
Type: configurationAlarm (11) MgwPeerGtpMismatchAlarm (2067)
Package: wlangw
Raised on class:
wlangw.MgwPeer
Description: This alarm is raised when the Negotiated QoS profile RADIUS attribute contains a release
indicator either for GGSN or PGW that does not correspond to the interface type actually used in GTP. e.g. the
release indicator is for GGSN and the interface type used in GTP is S2a/S2b while it should be Gn.
Remedial action: The RADIUS Server configuration should be corrected to match the MgwPeer interface type
actually used in GTP.
Table 39-592 MicroBFDSessionDown
releases

MicroBFDSessionDown Implicitly cleared: true
(4997)
Type: lnkaggAlarm (56) LagMemberMicroBfdSessionStateChanged (2051)
Package: lag
Raised on class:
lag.Interface
Description: The alarm is raised when there is a change in the state of the micro-BFD session of a link (port)
of the LAG. When the state is ’idle’, ’failed’, ’waitingFwd’, ’up’, then the port is forwarding traffic. When the state
is ’waiting’, ’down’, then the port is not forwarding traffic.
Remedial action: Micro BFD Session state of one of the LAG links is changed. Please check the LAG’s BFD
configuration or the configuration of the LAG and the Ports in it.
Table 39-593 MidLevelIPv6RoutesReached

releases

MidLevelIPv6RoutesReached Implicitly cleared: false
(506)
Type: ProtocolAlarm (1) MidLevelIPv6RoutesReached (390)
Package: l3fwd
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the number of IPv6 routes in a VPRN exceeds the configured threshold
value. The alarm information includes the number of IPv6 routes and the threshold value.
Remedial action: The number of IPv6 routes has exceeded the configured maximum for the VPRN - the route
table must be examined to ensure that all of the routes in the table are valid and not the result of a
misconfiguration in the VPRN service. If all of the routes appear to be valid then the value used as the
threshold value should be revisited.
Table 39-594 MidLevelRoutesReached

releases
Name: MidLevelRoutesReached Severity: minor Unspecified

Package: l3fwd MidLevelRoutesReached (899)
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the number of routes in a VPRN exceeds the threshold specified in the
VPRN configuration. The threshold value is a percentage of the maximum number of routes specified in the
VPRN configuration. The alarm information includes the number of routes and the threshold value.
Table 39-595 MirrorDestinationMisconfigured

releases

MirrorDestinationMisconfigured Implicitly cleared: true
(209)
Type: configurationAlarm (11) mirrorDestinationMisconfigured (162)
Package: mirror
Raised on class: mirror.Mirror
Description: The alarm is raised when more than two destination Sites are configured for a service mirror.
Raising condition: (’destinationMisconfigured’ EQUAL ’true’)
Clearing condition: (’destinationMisconfigured’ EQUAL ’false’)
Remedial action: Delete destination site so that there are two or less destination sites in one Mirror service.
Table 39-596 MirrorEncapsulationTypeInconsistent

releases

MirrorEncapsulationTypeInconsistent Implicitly cleared: true
(217)
Type: configurationAlarm (11) mirrorEncapsulationTypeInconsistent (171)
Package: mirror
Description: The alarm is raised when the encapsulation types of the mirror sites differ.
Raising condition: (’encapsulationTypeInconsistent’ EQUAL ’true’)
Clearing condition: (’encapsulationTypeInconsistent’ EQUAL ’false’)
Remedial action: Reconfigure the ’Encapsulation Type’ for the sites (delete and re-add the sites if not
configurable) so that the ’Encapsulation Type’ are the same in one Mirror service.
Table 39-597 MisconfiguredInflow

releases
Name: MisconfiguredInflow (1067) Severity: major Unspecified

Package: mpr Default probable cause: misconfiguredInflow
Description: The alarm is raised when the ports in a service use different inflow clock sources.
Remedial action: Configured inflow is not in sync with the configuration on the NE. Please check for
Mismatch.
Table 39-598 mismatchAnyCastRPTypes

releases

mismatchAnyCastRPTypes (270) Implicitly cleared: false
Package: pim mismatchAnyCastRPTypes (202)
Raised on class: pim.AnyCastRP
Description: The alarm is raised when there is an anycast RP type mismatch.
Remedial action: A configuration error has occurred that must be corrected. Please check to make sure the
global Virtual Anycast RP service type and this PIM Anycast RP service type are consistent.
Table 39-599 mismatchBackupAddress

releases
Name: mismatchBackupAddress Severity: minor Unspecified

Package: vrrp mismatchBackupAddress (212)
Raised on class:
vrrp.VRInstance
Description: The alarm is raised when two VR instances in a VR have different backup addresses.
Remedial action: Reconfigure the backup addresses for the peer VRRP instances so that they are the same.
Table 39-600 mismatchSubnets

releases
Name: mismatchSubnets (280) Severity: major Unspecified

Package: vrrp Default probable cause: mismatchSubnets
vrrp.VRInstance
Description: The alarm is raised when two VR Instances in a VR have backup addresses that are in different
subnets.
Remedial action: Reconfigure the ip addresses for the peer VRRP instances so that they are in the same
subnets.
Table 39-601 mismatchVrrpTypes

releases
Name: mismatchVrrpTypes Severity: minor Unspecified

Type: configurationAlarm (11) Default probable cause: mismatchVrrpTypes
Package: vrrp (211)
Raised on class:
vrrp.VRInstance
Description: The alarm is raised when two VR instances in a VR are of different types, for example, when one
VR instance type is Network and the other is IES.
Raising condition: ((’VRRP Type’ NOT EQUAL ’VRRP Type’))
Clearing condition: ((’VRRP Type’ EQUAL ’VRRP Type’))
Remedial action: Reconfigure the VRRP instance peers so that they are from the same type of interfaces
(Network, IES or VPRN).
Table 39-602 MissingFallingEvent

releases
Name: MissingFallingEvent Severity: major Unspecified

Package: rmon (225)
Raised on class: rmon.Alarm
Description: The alarm is raised when the 5620 SAM cannot find the falling event object that is named in an
RMON policy alarm definition.
Raising condition: (’Missing Falling Event’ EQUAL ’true’)
Clearing condition: (’Missing Falling Event’ EQUAL ’false’)
Remedial action: Cannot find the falling event object that is named in an RMON policy alarm definition.
Please create the required event.
Table 39-603 MissingHopConfiguration

releases
Name: MissingHopConfiguration Severity: warning Unspecified

Package: mpls MissingHopConfiguration (252)
Description: The alarm is raised when a static LSP is created without hops.
Remedial action: Need to configure static hops to the destination.
Table 39-604 MissingRisingEvent

releases
Name: MissingRisingEvent Severity: major Unspecified

Package: rmon (225)
Raised on class: rmon.Alarm
Description: The alarm is raised when the 5620 SAM cannot find the rising event object that is named in an
RMON policy alarm definition.
Raising condition: (’Missing Rising Event’ EQUAL ’true’)
Clearing condition: (’Missing Rising Event’ EQUAL ’false’)
Remedial action: Cannot find the rising event object that is named in an RMON policy alarm definition. Please
create the required event.
Table 39-605 missingStaticRPConfigurations

releases

missingStaticRPConfigurations Implicitly cleared: true
(268)
Type: configurationAlarm (11) missingStaticRPConfigurations (200)
Package: pim
Raised on class:
Description: The alarm is raised when a static RP configuration is missing.
Anycast RP configuration and its operational status flag so that the Static RP and Group Range(s) are all
configured.
Table 39-606 MissSpokeConfiguration

releases
Name: MissSpokeConfiguration Severity: warning Unspecified

Package: vpls missSpokeConfiguration (172)
Raised on class:
vpls.AbstractVpls
Description: The alarm is raised when the 5620 SAM detects a spoke SDP binding between two sites in one
M-VPLS or VPLS. The alarm is not raised by the 5620 SAM, Release 4.0 or later.
Raising condition: (’missSpokeConfiguration’ EQUAL ’true’)
Clearing condition: (’missSpokeConfiguration’ EQUAL ’false’)
Remedial action: Deprecated since Rel.4.0
Table 39-607 MldGrpIfSapCModeRxQueryMism

releases

MldGrpIfSapCModeRxQueryMism Implicitly cleared: false
(5390)
Type: configurationAlarm (11) InvalidCompatibilityModeofQueryReceived (2106)
Package: mld
Raised on class:
mld.GrpInterfaceSap
Description: The alarm is raised when there is a mismatch between the compatible mode of the MLD SAP
and the version of the received query. It is generated when the SAP is in MLDv1 compatible mode but it
receives an MLDv2. It will include information on the configured version of the compatibility mode of the SAP,
and the version of the received query.
Remedial action: Change the MLD Version attribute on the MLD Group Interface to match the MLD host
version.
Table 39-608 MldGrpIfSapMaxGroupsLimitExceeded

releases

MldGrpIfSapMaxGroupsLimitExceeded Implicitly cleared: false
(5391)
Type: configurationAlarm (11) MldGrpIfSapMaxGroupsLimitExceeded (2107)
Package: mld
Raised on class: mld.GrpInterfaceSap
Description: ’This alarm is raised when an attempt is made to configure a group when the number of groups
configured on the SAP, is equal to the ’Maximum Number of Groups’ supported on the SAP.’
Remedial action: Increase the value of the ’Maximum Number of Groups’ attribute in the parent MLD group
interface so that the number of active MLD groups stays under the configured threshold.
Table 39-609 MldGrpIfSapMaxGrpSrcLimExcd

releases

MldGrpIfSapMaxGrpSrcLimExcd Implicitly cleared: false
(5392)
Type: configurationAlarm (11) MldGrpIfSapMaxGrpSrcLimExcd (2108)
Package: mld
Raised on class:
mld.GrpInterfaceSap
Description: This alarm is raised when an attempt is made to configure a group source for a group when the
number of group sources is equal to the ’Maximum Number of Group Sources’ per group supported on the
SAP.
Remedial action: Increase the value of the ’Maximum Number Of Group Sources’ attribute in the parent MLD
group interface so that the number of active MLD Group sources stays under the configured threshold.
Table 39-610 MldGrpIfSapMaxSourcesLimitExceeded

major releases

MldGrpIfSapMaxSourcesLimitExceeded Implicitly cleared: false
(5393)
Type: configurationAlarm (11) MldGrpIfSapMaxSourcesLimitExceeded
Package: mld (2109)
Raised on class: mld.GrpInterfaceSap
Description: ’This alarm is raised when an attempt is made to configure a source for a group when the
number of sources for this group is equal to the ’Maximum Number of Sources’ per group supported on the
SAP.’
Remedial action: Increase the value of the ’Maximum Number Of Sources’ attribute in the parent MLD group
interface so that the number of active MLD sources stays under the configured threshold.
Table 39-611 MldGrpIfSapRxQueryVerMism

releases

MldGrpIfSapRxQueryVerMism Implicitly cleared: false
(5394)
Type: configurationAlarm (11) InvalidVersionofQueryMessageReceived (129)
Package: mld
Raised on class:
mld.GrpInterfaceSap
Description: The alarm is raised when the MLD host SAP is configured as MLDv2 but receives an MLDv1
Query. It will include information on the configured version of the SAP, and the version of the received query.
version.
Table 39-612 MldHostCModeRxQueryMismatch

releases

MldHostCModeRxQueryMismatch Implicitly cleared: false
(8051)
Type: configurationAlarm (11) InvalidCompatibilityModeOfQueryReceived (2452)
Package: mld
Raised on class: mld.Site
Description: The alarm is raised when there is a mismatch between the compatible mode of the MLD Host
and the version of the received query, i.e. the Host is in MLDv1 compatible mode but it receives a MLDv2
Query.
version.
Table 39-613 MldHostInstantiationFail

releases
Name: MldHostInstantiationFail Severity: warning Unspecified

Package: mld MldHostInstantiationFailed (2453)
Raised on class:
mld.GrpInterface
Description: This alarm is generated when a host is eligible for running MLD, but MLD cannot be started on
the host.
Remedial action: A host is eligible for running MLD, but MLD cannot be started on the given host.
Table 39-614 MldHostMaxGroupsLimitExceeded

releases

MldHostMaxGroupsLimitExceeded Implicitly cleared: false
(8053)
Type: configurationAlarm (11) MldHostMaxGroupsLimitExceeded (2454)
Package: mld
Raised on class: mld.GrpInterface
Description: This alarm is generated when an attempt is made to configure a group when the number of
groups configured on the PIM interface is equal to the maximum number of groups supported on the host.
Remedial action: Increase the value of the ’Maximum Number of Groups’ attribute in the MLD group interface
so that the number of active MLD groups stays under the configured threshold.
Table 39-615 MldHostMaxGrpSrcsLimitExceeded

releases

MldHostMaxGrpSrcsLimitExceeded Implicitly cleared: false
(8054)
Type: configurationAlarm (11) MldHostMaxGrpSrcsLimitExceeded (2455)
Package: mld
Description: The alarm is generated when an attempt is made to configure a source for a group when the
number of group sources is equal to the maximum number of group sources per group supported on the host.
Remedial action: Increase the value of the ’Maximum Number Of Group Sources’ attribute in the MLD group
interface so that the number of active MLD Group sources stays under the configured threshold.
Table 39-616 MldHostMaxSrcsLimitExceeded

releases

MldHostMaxSrcsLimitExceeded Implicitly cleared: false
(8055)
Type: configurationAlarm (11) MldHostMaxSrcsLimitExceeded (2456)
Package: mld
Description: The alarm is generated when an attempt is made to configure a source for a group when the
number of sources for this group is equal to the maximum number of sources per group supported on the host.
Remedial action: Increase the value of the ’Maximum Number Of Sources’ attribute in the MLD group
interface so that the number of active MLD sources stays under the configured threshold.
Table 39-617 MldHostRxQueryVerMismatch

releases

MldHostRxQueryVerMismatch Implicitly cleared: false
(8056)
Type: configurationAlarm (11) InvalidVersionOfQueryMessageReceived (2457)
Package: mld
Raised on class: mld.Site
Description: The alarm is raised when the MLD host is configured as MLDv2 but receives an MLDv1 Query. It
will include information on the configured version of MLD Host, and the version of the received query.
version.
Table 39-618 MldSnpgGrpDroppedLimitExceeded

releases

MldSnpgGrpDroppedLimitExceeded Implicitly cleared: false
(537)
Type: AccessInterfaceAlarm (32) mldSnpgGrpMaxNbrGrpsReached (406)
Package: vpls
Raised on class:
vpls.L2AccessInterfaceMldSnpgCfg
Description: The alarm is raised when a SAP drops an MLD group because the configurable maximum
number of MLD groups on the SAP is reached.
Remedial action: Increasing the maximum number of MLD Groups to prevent groups from being dropped.
Table 39-619 MlpppBundleInterleavingDisabled

releases
MlpppBundleInterleavingDisabled Implicitly cleared: true
(4383)
Type: other (123) mlpppBundleInterleavingDisabled (1567)
Package: netw
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the ’Link Fragmentation and LFI’ bit is set but LFI isn’t active for
MLPPP Bundle. It is cleared for other cases. If LFI is not desired, disable it in the L2TP MLPPP configuration of
the related routing instance. Or, ensure that the MLPPP bundle only contains a single link.
Remedial action: If LFI is not desired, disable it in the L2TP MLPPP configuration of the related routing
instance. Or, ensure that the MLPPP bundle only contains a single link.
Table 39-620 MobGwSysGrpWriteCdrToCfAlarm

releases

MobGwSysGrpWriteCdrToCfAlarm Implicitly cleared: true
(3634)
Type: MgGroupAlarm (75) MobGwSysGrpWriteCdrToCfStop (1418)
Package: isa
Raised on class: isa.MgIsaGroup
Description: The alarm is raised when the SGW or PGW writes Charging Data Record (CDR) packets to the
local compact flash for the mobile system group.
Remedial action: Retrieve Charging Data Record (CDR) files from compact flash.
Table 39-621 ModFail

releases
Name: ModFail (1171) Severity: variable Unspecified

Package: equipment Default probable cause: modFail
equipment.Equipment
Description: The alarm is raised when a modulation failure is detected.
Table 39-622 ModLOS

releases
Name: ModLOS (1172) Severity: variable Unspecified

Package: equipment Default probable cause: modLOS
equipment.Equipment
Description: The alarm is raised when a modulation loss of signal is detected.
Table 39-623 ModuleOutOfMemory

releases
Name: ModuleOutOfMemory (180) Severity: critical Unspecified

Package: netw Default probable cause: outOfMemory
netw.NetworkElement
Description: The alarm is raised when the available NE memory is insufficient for allocation to a task.
Remedial action: Informational - If the alarm persists please contact Alcatel-Lucent support for assistance
Table 39-624 MonitoredObjectsCrossThreshold

releases

MonitoredObjectsCrossThreshold Implicitly cleared: true
(8146)
Type: processingErrorAlarm (81) MonitoredObjectsCrossThreshold (2542)
Package: sup
Raised on class:
sup.SupervisionManager
Description: This alarm is raised when total monitored objects count cross certain threshold. It is in warning
when the total count exceeds 90% of the limit, and in critical when the total count reaches the limit. It is
automatically cleared when the total count is back under the limit and threshold.
Remedial action: Please remove unnecessary supervision groups or change the inclusion filters of
supervision groups to reduce monitored objects.
Table 39-625 MplsResignalTimerExpired

releases
Name: MplsResignalTimerExpired Severity: info Unspecified

Package: mpls resignalTimerExpired (833)
Raised on class: mpls.Site
Description: The alarm is raised when an MPLS instance resignal timer expires.
Table 39-626 MprVllDown

releases
Name: MprVllDown (1139) Severity: major Unspecified

Type: serviceDown (88) Implicitly cleared: true
Package: mpr Default probable cause: vlanPathInstanceDown
mpr.MprVll
Description: The alarm is raised when the Operational State of a VLAN path instance is Down.It could be
caused by one of the following conditions: - The radio link is down. - A cross connect is deleted. - The
Operational State of one or more ports in the cross connect is Down.
Remedial action: Components of the VLL service , site , ports and or links may be down. Please check the
components for root cause.
Table 39-627 MPTCardFailure
releases
Name: MPTCardFailure (4830) Severity: variable Unspecified

Package: mwa Default probable cause:
Raised on class: ReplaceableUnitProblem (1905)
mwa.PortTermination
Description: This alarm is raised when MPT card failure is detected.
information.
Table 39-628 MPTPlugInCardFailure

releases
Name: MPTPlugInCardFailure Severity: variable Unspecified

Package: mwa ReplaceableUnitProblem (1905)
Raised on class:
mwa.PortTermination
Description: This alarm is raised when RPS/XPIC Plug-in card failure is detected.
information.
Table 39-629 MPTPowerSupplyFailure

releases
Name: MPTPowerSupplyFailure Severity: variable Unspecified

Type: equipmentAlarm (3) Default probable cause: powerSupplyFailure
Description: The alarm is raised when an MPT radio power source has a power supply failure.
Table 39-630 msapCreationFailure

releases
Name: msapCreationFailure (740) Severity: warning Unspecified

Package: vpls Default probable cause: creationFailure
vpls.L2AccessInterface Applicable probable causes:
creationFailure
radiusAuthFailed
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot create an MSAP.
Remedial action: This warning is raised when the NE fails to create an MSAP. Please review the alarm’s
additional text to obtain information about the error condition. Possible problems can be mis-configuration of
the capture SAP, authentication failures, a missing target service or interface, illegal trigger packets and more.
Table 39-631 MsdpActSrcLimExcd

releases

MsdpActSrcLimExcd (380) Implicitly cleared: false
communicationsAlarm (4) MsdpActiveSourcesLimitExceeded (279)
Package: msdp
Raised on class: msdp.Site
Description: The alarm is raised when an MSDP site receives a number of source active messages that
exceeds the configured maximum.
Remedial action: Increase the configurable maximum number of source active messages if possible.
Table 39-632 MsdpGroupSrcActMsgsExcd

releases

MsdpGroupSrcActMsgsExcd Implicitly cleared: false
(378)
Type: communicationsAlarm MsdpGroupActiveSourcesLimitExceeded (277)
(4)
Package: msdp
Raised on class:
msdp.PeerGroup
Description: The alarm is raised when an MSDP group receives a number of source active messages that
Table 39-633 MsdpPeerActSrcLimExcd

releases

MsdpPeerActSrcLimExcd Implicitly cleared: false
(379)
Type: communicationsAlarm MsdpPeerActiveSourcesLimitExceeded (278)
(4)
Package: msdp
Raised on classes:
msdp.GroupPeer
msdp.Peer
Description: The alarm is raised when an MSDP peer receives a number of source active messages that
Table 39-634 MsdpRPFFailure

releases
Name: MsdpRPFFailure (354) Severity: warning Unspecified

Type: communicationsAlarm Implicitly cleared: false
(4) Default probable cause: MsdpRPFFailure
Package: msdp (275)
Raised on class: msdp.Site
Description: The alarm is raised when an MSDP site experiences an RPF failure.
Table 39-635 MsdpSourceSrcActMsgsExcd

releases

MsdpSourceSrcActMsgsExcd Implicitly cleared: false
(381)
Type: communicationsAlarm MsdpSourceActiveSourcesLimitExceeded (280)
(4)
Package: msdp
Raised on class: msdp.Source
Description: The alarm is raised when an MSDP source receives a number of source active messages that
Table 39-636 MsPwFecMisConfig

releases
Name: MsPwFecMisConfig Severity: major Unspecified

Type: serviceAlarm (16) Default probable cause: msPwFecMisConfig
Package: svt (1430)
Raised on class:
svt.SpokeSdpFec
Description: The alarm is raised when a misconfiguration is discovered between two signaling multi-segment
pseudowires. For example, configuring both multi-segment pseudowires as master would cause this
notification.
Clearing condition: (’Administrative State’ EQUAL ’Up’)
Remedial action: Configure multi-segment pseudo-wires such that both are not configured to be master.
Table 39-637 MultiChassisStpBlockingStatus

major releases

MultiChassisStpBlockingStatus Implicitly cleared: false
(4902)
Type: communicationsAlarm (4) PrimarybridgeSTPPriorityishigherthansecondrybridge
Package: aosredundancy (1959)
Raised on class:
aosredundancy.AOSMultiChassis
Description: Primary bridge STP Priority is higher than secondary bridge

Remedial action: This Alarm can be cleared by setting primary bridge STP Priority lower then secondary
bridge stp priority
Table 39-638 MultipleOwners

releases
Name: MultipleOwners (283) Severity: major Unspecified

Package: vrrp Default probable cause:
Raised on class: multipleOwnersConfigured (215)
Description: The alarm is raised when an owner VR instance detects another instance that advertises itself as
an owner.
Remedial action: Shut down one of the peer VRRP instances and change the owner to false and then turn it
up.
Table 39-639 multipleRPLOwner

Name: multipleRPLOwner (2946) Severity: major Unspecified

Package: ethring Default probable cause: multiplerpl (1135)
Raised on class: ethring.Element
Description: The alarm is raised on RPL elements configured as RPL owners, when there are multiple RPL
owners detected in the ring topology.
Remedial action: A configuration error has been made which must be corrected. The duplicate RPL owners
must be deleted.
Table 39-640 MVPNDuplicateVrfPolicy

releases
Name: MVPNDuplicateVrfPolicy (649) Severity: warning Unspecified

Raised on classes: duplicateVrfPolicyExists (177)
l3fwd.ServiceSiteMVPNImportPolicy
l3fwd.ServiceSiteMVPNExportPolicy
Description: The alarm is raised when the 5620 SAM detects a duplicate VRF policy in a multicast VPRN. The
alarm information includes the VRF policy ID and type, and information about the service site. Note: starting
from SAM 12.0 R1, SAM no longer raise this alarm since it is not much useful but has performance issue.
Remedial action: A configuration error has occurred which must be corrected. The duplicate VRF policy must
be removed. Note: starting from SAM 12.0 R1, SAM no longer raises this alarm.
Table 39-641 MVPNExportPolicyNotFound

releases
Name: MVPNExportPolicyNotFound Severity: major Unspecified

Package: l3fwd exportPolicyDoesNotExist (179)
Raised on class:
l3fwd.ServiceSiteMVPNExportPolicy
Description: The alarm is raised when a VRF export policy for a multicast VPRN cannot be found. The alarm
Remedial action: A configuration error has occurred which must be corrected. A VRF export policy with the
appropriate ID must be configured. Note: starting from SAM 12.0 R1, SAM no longer raises this alarm.
Table 39-642 MVPNImportPolicyNotFound

releases
Name: MVPNImportPolicyNotFound Severity: major Unspecified

Package: l3fwd importPolicyDoesNotExist (180)
Raised on class:
l3fwd.ServiceSiteMVPNImportPolicy
Description: The alarm is raised when a VRF import policy for a multicast VPRN cannot be found. The alarm
Remedial action: A configuration error has occurred which must be corrected. A VRF import policy with the
appropriate ID must be configured. Note: starting from SAM 12.0 R1, SAM no longer raises this alarm.
Table 39-643 MwLinkEPSActivityChange

releases
Name: MwLinkEPSActivityChange Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: EPSActivityChange
Package: mwa (2002)
Raised on class: mwa.MwLink
Description: This alarm is raised when a microwave link changes activity for EPS.
information.
Table 39-644 MwLinkMaintenanceChange

releases

MwLinkMaintenanceChange Implicitly cleared: false
(4946)
Type: communicationsAlarm (4) MaintenanceCommandChange (2003)
Package: mwa
Description: This alarm is raised when a microwave link maintenance command changes.
information.
Table 39-645 MwLinkPeerChange

releases
Name: MwLinkPeerChange Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: PeerChange
Package: mwa (1918)
Description: This alarm is raised when a microwave link discovered peer changes.
information.
Table 39-646 MwLinkRPSActivityChange

releases
Name: MwLinkRPSActivityChange Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: RPSActivityChange
Package: mwa (2004)
Description: This alarm is raised when a microwave link changes activity for RPS.
information.
Table 39-647 MwLinkTPSActivityChange

releases
Name: MwLinkTPSActivityChange Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: TPSActivityChange
Package: mwa (2005)
Description: This alarm is raised when a microwave link changes activity for TPS.
information.
Table 39-648 NatIsaMemberSessionUsageHi

releases
Name: NatIsaMemberSessionUsageHi Severity: major Unspecified

Package: nat (53)
Raised on class: nat.IsaMember
Description: The alarm is raised when the session usage of an ISA-NAT group member reaches the high
watermark. The alarm clears when the session usage reaches the low watermark.
Remedial action: Review the watermarks configuration to make sure it matches the capacity of your network.
If required, deploy extra equipment to deal with the demand.
Table 39-649 NatIsaMemberSessionUsageHigh
releases
Name: NatIsaMemberSessionUsageHigh Severity: major Unspecified

Package: nat resourceFull (53)
Raised on class: nat.IsaMda
Description: Deprecated in 10.0, Use {NatIsaMemberSessionUsageHi on nat.IsaMember} instead. The alarm

is raised when the session usage of an ISA-NAT group member reaches the high watermark. The alarm clears
when the session usage reaches the low watermark.
Table 39-650 NatL2AwSubIcmpPortUsageHigh

releases
Name: NatL2AwSubIcmpPortUsageHigh Severity: warning Unspecified

Package: ressubscr resourceFull (53)
Raised on class:
Description: The alarm is raised when the ICMP port usage of an L2-aware NAT subscriber reaches the high
or low watermark.
Remedial action: Review the watermarks configuration to make sure it matches the capacity of the network. If
required, deploy extra equipment to deal with the demand.
Table 39-651 NatL2AwSubSessionUsageHigh

releases
Name: NatL2AwSubSessionUsageHigh (1087) Severity: warning Unspecified

Raised on class: resourceFull (53)
Description: The alarm is raised when the session usage of an L2-aware NAT subscriber reaches the high or
low watermark.
Table 39-652 NatL2AwSubTcpPortUsageHigh

releases
Name: NatL2AwSubTcpPortUsageHigh (1088) Severity: warning Unspecified

Description: The alarm is raised when the TCP port usage of an L2-aware NAT subscriber reaches the high or
low watermark.
Table 39-653 NatL2AwSubUdpPortUsageHigh

releases
Name: NatL2AwSubUdpPortUsageHigh (1089) Severity: warning Unspecified

Description: The alarm is raised when the UDP port usage of an L2-aware NAT subscriber reaches the high
or low watermark.
Table 39-654 NatPlL2AwBlockUsageHigh

releases
Name: NatPlL2AwBlockUsageHigh Severity: warning Unspecified

Package: nat (53)
Raised on class: nat.NatPool
Description: The alarm is raised when the block usage of an L2-aware NAT address pool reaches the high
watermark. The alarm clears when the block usage reaches the low watermark.
Remedial action: This alarm indicates the block usage of a L2-aware NAT address pool reaches its threshold
on a particular member MDA of its ISA group. Please ensure the address pool block usage configuration
adequate for the system requirement. This alarm will be cleared automatically once the block usage is below
the watermark.
Table 39-655 NatPlLsnMemberBlockUsageHigh

releases
Name: NatPlLsnMemberBlockUsageHigh Severity: warning Unspecified

Package: nat resourceFull (53)
Raised on class: nat.NatPool
Description: The alarm is raised when the block usage of a large-scale NAT address pool reaches the high
watermark. The alarm clears when the block usage reaches the low watermark.
Remedial action: This alarm indicates the block usage of a Large Scale NAT address pool reaches its
threshold on a particular member MDA of its ISA group. Please ensure the address pool block usage
configuration adequate for the system requirement. This alarm will be cleared automatically once the block
usage is below the watermark.
Table 39-656 NeighborLoss (pim)

releases
Name: NeighborLoss (188) Severity: warning Unspecified
(4) Default probable cause: NeighborConnectionLost
Package: pim (148)
Raised on class:
pim.Interface
Description: The alarm is raised when the connection to a neighbor is lost.
Remedial action: Informational - please check the connection to the neighbor is fine, e.g the peer is not in
shutdown state. The alarm will be cleared when the neighbor is discovered up.
Table 39-657 NeighborLoss (vpls)

releases
Name: NeighborLoss (188) Severity: warning Unspecified

Package: vpls Default probable cause:
Raised on class: NeighborConnectionLost (148)
vpls.InterfacePimSnooping
Description: The alarm is raised when the 5620 SAM detects a loss of connection to a PIM neighbor.
Remedial action: There is a lost connection to the PIM Neighbor. Check the PIM Neighbor to ensure it is still
operational and that underlying transport of the SAP or SDP is operationally up.
Table 39-658 netconfEventReplayFailure

releases

netconfEventReplayFailure Implicitly cleared: false
(5389)
Type: communicationsAlarm (4) MmeInternalProcessingError (1421)
Package: ltemme
Raised on class:
ltemme.MmeInstance
Description: Replay of the NETCONF notification event buffer has failed and 5620 SAM is no longer
attempting to replay old events. Any Performance Measurement Statistics files that 5620 SAM was trying to
replay must be manually retrieved from the 9471 WMM. The additionalText field of the alarm displays the
timestamp of the last successful NETCONF notification that 5620 SAM has processed after server startup. If
the additionalText field is empty, we have not processed any NETCONF notifications since the 5620 SAM
started and any missing files need to be manually retrieved from the 9471 WMM. New NETCONF event
notifications are still processed as normal.
Remedial action: Replay of the NETCONF notification event buffer has failed and 5620 SAM is no longer
attempting to replay old events. Any Performance Measurement Statistics files that 5620 SAM was trying to
replay must be manually retrieved from the 9471 WMM. The additionalText field of the alarm displays the
timestamp of the last successful NETCONF notification that 5620 SAM has processed after server startup. If
the additionalText field is empty, we have not processed any NETCONF notifications since the 5620 SAM
started and any missing files need to be manually retrieved from the 9471 WMM. New NETCONF event
notifications are still processed as normal.
Table 39-659 NetConfEventSubscriptionProblem

releases

NetConfEventSubscriptionProblem Implicitly cleared: true
(4864)
Type: communicationsAlarm (4) NetConfEventSubscriptionFailed (1932)
Package: netw
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the 5620 SAM is unable to subscribe for Netconf event notification from
a network element. For a WMM: if this problem persists it may result in a loss of PM file collection.
Remedial action: Informational -if the alarm persists or is occurring frequently then investigation is required to
understand why the Netconf event subscription configuration is failing.
Table 39-660 NetworkElementChassisTypeMismatch

major releases

NetworkElementChassisTypeMismatch Implicitly cleared: true
(1946)
Type: communicationsAlarm (4) mismatchOfNetworkElementChassisType
Package: netw (934)
Raised on class: netw.DiscoveredNode
Description: The alarm is raised when the chassis type of the shadow network element does not match with
the chassis type of the discovered NE.
Remedial action: A configuration error has been made which must be corrected. The pre-provisioned NE
chassis type defined must match the chassis type of the node being discovered.
Table 39-661 NetworkElementTypeMismatch

releases

NetworkElementTypeMismatch Implicitly cleared: true
(1947)
Type: communicationsAlarm (4) mismatchOfNetworkElementType (935)
Package: netw
Raised on class:
netw.DiscoveredNode
Description: The alarm is raised when the type of the shadow network element does not match with the type
of the discovered NE.
Remedial action: A configuration error has been made which must be corrected. The pre-provisioned NE type
defined must match the type of the node being discovered.
Table 39-662 NetworkElementVersionMismatch

releases

NetworkElementVersionMismatch Implicitly cleared: true
(1948)
Type: communicationsAlarm (4) mismatchOfNetworkElementVersion (936)
Package: netw
Raised on class:
netw.DiscoveredNode
Description: The alarm is raised when the version of the shadow network element does not match with the
version of the discovered NE.
Remedial action: A configuration error has been made which must be corrected. The pre-provisioned NE
version defined must match the version of the node being discovered.
Table 39-663 NodeDatabaseCorruptionDetected
releases

NodeDatabaseCorruptionDetected Implicitly cleared: true
(1961)
Type: communicationsAlarm (4) nodeDatabaseCorrupted (948)
Package: netw
Raised on class:
netw.NetworkElement
Description: This alarm is raised when an error in the node causes the node to lose its configuration and
come up in an inconsistent/incomplete state. To overcome this it might be necessary to reconfigure the node.
Remedial action: The node configuration is inconsistent. You may have to do a Reconfigure. However if it’s a
first discovery, you have to delete the node, then create a pre-provisioned NE instance, create a new discovery
rule with a self-configuration policy and discover the node.
Table 39-664 NodeSoftwareMisalignmentDetected

releases

NodeSoftwareMisalignmentDetected Implicitly cleared: true
(4906)
Type: communicationsAlarm (4) nodeSoftwareMisalignment (1962)
Package: netw
Raised on class:
netw.NetworkElement
Description: The alarm is raised when a software misalignment has been detected on the node and comes
back up with an unexpected software version (software change triggered by external tool) To correct this
situation it is necessary to download and activate on the node the software referenced by SAM and then
reconfigure the node with the 5620 SAM’s current configuration.
Remedial action: the NE software is misaligned. Perform a Download and Activate Software operation with
the software version known by SAM which is the reference.
Table 39-665 noFunctioningScript

releases
Name: noFunctioningScript Severity: critical Unspecified

Type: configurationAlarm (11) Default probable cause: primaryBackupDown
Package: subscrident (207)
Raised on class:
subscrident.Policy
Description: The alarm is raised when all subscriber identification scripts are operationally down.
Raising condition: ((’isLocal’ EQUAL ’true’) AND (’Primary Script Operational State’ NOT EQUAL ’Up’) AND
(’Secondary Script Operational State’ NOT EQUAL ’Up’) AND (’Tertiary Script Operational State’ NOT EQUAL
’Up’))
Clearing condition: ((’isLocal’ EQUAL ’true’) AND ((’Primary Script Operational State’ EQUAL ’Up’) OR
(’Secondary Script Operational State’ EQUAL ’Up’) OR (’Tertiary Script Operational State’ EQUAL ’Up’)))
Table 39-666 NoRPLOwner
Name: NoRPLOwner (3700) Severity: major Unspecified

Package: ethring Default probable cause: norpltype (1438)
Raised on class:
ethring.RadioRing
Description: The alarm is raised when there is No RPL Owner selected on a Radio Ring.
Remedial action: Operator has to configure at least one of the Elements belonging to a Radio Ring as RPL
Owner.
Table 39-667 NotEnoughContiguousBlocks

releases

NotEnoughContiguousBlocks Implicitly cleared: false
(4987)
Type: configurationAlarm (11) notEnoughContiguousBlocks (2042)
Package: dhcp
Raised on class:
dhcp.LocalDhcp6Server
Description: The alarm is raised when a lease cannot be created because not enough contiguous blocks are
found for the requested delegated prefix size.
Remedial action: This alarm is raised when a lease cannot be created because not enough contiguous blocks
are found for the requested delegated prefix size. Please adjust the associated pools.
Table 39-668 NTPNoServersAvail

releases
Name: NTPNoServersAvail Severity: major Unspecified

Type: communicationsAlarm Default probable cause: NTPNoServersAvail
(4) (1942)
Package: ntp
Raised on class: ntp.NTP
Description: The alarm is generated when no NTP Servers are available.
Remedial action: Please check if the configured servers are physically reachable (IP ping) from the node (Or)
check if the configured servers are enabled as NTP Server (NTP Server attribute on General Tab) and their
Operational state is Up (Or) check if the authentication keys are correctly defined on the client and the NTP
server node.
Table 39-669 NTPServerChange

releases
Name: NTPServerChange Severity: info Unspecified

Type: communicationsAlarm Default probable cause: NTPServerChange
(4) (1944)
Package: ntp
Raised on class: ntp.NTP
Description: The alarm generated when more than one NTP servers are configured in a system and a
different NTP server is selected because the operational status of the earlier NTP server has changed.
Remedial action: This is informational alarm to indicate that the current clock source has changed for the
node. Alarm needs to be manually cleared.
Table 39-670 OCHTrailDown

releases
Name: OCHTrailDown (3891) Severity: critical Unspecified

Raised on class:
optical.OCHTrail
Description: The alarm is raised when the termination point(s) of the OCH trail are operationally down.
by looking at the active alarms on the hops to understand why the underlying transport network is unreliable.
Table 39-671 OCHTrailMisConfigured

releases

OCHTrailMisConfigured Implicitly cleared: false
(5125)
Type: communicationsAlarm OchCrossConnectionTrailNameMisMatch (1391)
(4)
Package: optical
Raised on class:
optical.OCHTrail
Description: The alarm is raised when all the OCh cross connections (XCs) of an OCh trail do not have the
same trail name. In order for the auto wavekey processing to work properly, the XC name should be the same
on all NEs of the OCh trail.
Remedial action: Recreate the OCH Cross Connects with same OCH Trail name else Wave Tracker does not
work properly.
Table 39-672 ODUTrailDown

releases
Name: ODUTrailDown (3892) Severity: critical Unspecified

Raised on class:
optical.ODUTrail
Description: The alarm is raised when the termination point(s) of the ODU trail are operationally down.
Table 39-673 ODUTrailMisConfigured

releases

ODUTrailMisConfigured Implicitly cleared: false
(3893)
(4)
Package: optical
Raised on class:
optical.ODUTrail
Description: The alarm is raised when all the OCh cross connections (XCs) of an OCh trail do not have the
on all NEs of the OCh trail.
Remedial action: Recreate the OCH Cross Connects with same OCH Trail name else Wave Tracker does not
work properly.
Table 39-674 OlcStateChangeAlarm

releases
Name: OlcStateChangeAlarm (3740) Severity: info Unspecified

Package: generic Default probable cause: unknown
generic.GenericObject
Description: The alarm is raised to notify the user, when an OLC State change takes place at the specified
revert time.
Remedial action: Informational - This is a notification alarm to indicate that the object will revert it’s OLC state.
Table 39-675 OMSTrailDown

releases
Name: OMSTrailDown (8082) Severity: critical Unspecified

Raised on class:
optical.OMSTrail
Description: The alarm is raised when termination point(s) of the OMS trail are operationally down.
Table 39-676 OperDownInvalidMac

releases
Name: OperDownInvalidMac Severity: minor Unspecified

Type: configurationAlarm (11) Default probable cause: invalidMacAddress
Package: srrp (2540)
Description: This Alarm is generated when the operational virtual MAC of an SRRP instance conflicts with the
MAC of the parent interface.
Remedial action: The alarm is generated when the operational virtual MAC of an SRRP instance conflicts with
the MAC of the parent interface. The SRRP virtual router instance is not allowed to become operationally ’up’.
Table 39-677 OperDownInvalidMacClear

releases

OperDownInvalidMacClear Implicitly cleared: true
(8145)
Type: configurationAlarm (11) invalidMacAddressCleared (2541)
Package: srrp
Description: The Alarm is generated when a previously occurring OperDownInvalidMac notification has been
cleared. Operational virtual MAC of an IPv4 SRRP instance does not have any conflict with the MAC of the
parent interface.
Remedial action: The alarm is generated when a previously occurring OperDownInvalidMac notification has
been cleared. Operational virtual MAC of an IPv4 SRRP instance does not have any conflict with the MAC of
the parent interface.
Table 39-678 OpticalAmplifierLossOfInputOpticalPower

releases

OpticalAmplifierLossOfInputOpticalPower Implicitly cleared: true
(1185)
Type: communicationsAlarm (4) AmplifierLossOfInputOpticalPower (886)
Package: ethernetequipment
Raised on class:
ethernetequipment.WaveLengthTracker
Description: The alarm is raised when a device reports an Amplifier Loss of input optical power on an optical
amplifier interface.
Remedial action: Ensure that the input optical power at the face plate is greater than the minimum required
Table 39-679 OpticalAmplifierLossOfOutputPower

releases

OpticalAmplifierLossOfOutputPower Implicitly cleared: true
(1186)
Type: communicationsAlarm (4) AmplifierLossOfOutputPower (887)
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Loss of output power on an optical
amplifier interface.
Remedial action: If the alarm is persistent: 1. clear the mda, 2. clear card 3. replace the card
Table 39-680 OPticalAmplifierModuleCaseTemperatureHigh

major releases
OPticalAmplifierModuleCaseTemperatureHigh Implicitly cleared: true
(1180)
Type: communicationsAlarm (4) AmplifierModuleCaseTemperatureHigh
Package: ethernetequipment (881)
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Module Case Temperature High on an
optical amplifier interface.
Remedial action: Decrease the ambient temperature
Table 39-681 OPticalAmplifierModuleCaseTemperatureLow

major releases

OPticalAmplifierModuleCaseTemperatureLow Implicitly cleared: true
(1181)
Type: communicationsAlarm (4) AmplifierModuleCaseTemperatureLow
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Module Case Temperature Low on an
optical amplifier interface.
Remedial action: Increase the ambient temperature
Table 39-682 OpticalAmplifierModuleCommunicationFailure

major releases

OpticalAmplifierModuleCommunicationFailure Implicitly cleared: true
(1187)
Type: communicationsAlarm (4) AmplifierModuleCommunicationFailure
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Module Communication Failure on a
tunable dispersion compensation module’s interface.
Table 39-683 OpticalAmplifierPumpCurrent

releases
Name: OpticalAmplifierPumpCurrent Severity: major Unspecified

Package: ethernetequipment AmplifierPumpcurrent (889)
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Pump over current on an optical amplifier
interface.
Table 39-684 OPticalAmplifierPumpTemperature
releases

OPticalAmplifierPumpTemperature Implicitly cleared: true
(1182)
Type: communicationsAlarm (4) AmplifierPumpTemperature (883)
Raised on class:
Description: The alarm is raised when a device reports an Amplifier Pump Temperature on an optical amplifier
interface.
Table 39-685 OpticalTdcmEEPROMinvalid

releases
Name: OpticalTdcmEEPROMinvalid (1189) Severity: major Unspecified

Raised on class: TdcmEEPROMinvalid (890)
Description: The alarm is raised when a device reports a Tdcm EEPROM invalid on a tunable dispersion
compensation module’s interface.
Remedial action: Replace the card
Table 39-686 OpticalTdcmModuleCommunicationFailure

major releases

OpticalTdcmModuleCommunicationFailure Implicitly cleared: true
(1190)
Type: communicationsAlarm (4) TdcmModuleCommunicationFailure (891)
Raised on class:
Description: The alarm is raised when a device reports a Tdcm Module Communication Failure on a tunable
dispersion compensation module’s interface.
Table 39-687 OPticalTdcmModuleTemperatureHigh

releases

OPticalTdcmModuleTemperatureHigh Implicitly cleared: true
(1183)
Type: communicationsAlarm (4) TdcmModuleTemperatureHigh (884)
Raised on class:
Description: The alarm is raised when a device reports a Tdcm Module Temperature High on a tunable
Table 39-688 OPticalTdcmModuleTemperatureLow

releases

OPticalTdcmModuleTemperatureLow Implicitly cleared: true
(1184)
Type: communicationsAlarm (4) TdcmModuleTemperatureLow (885)
Raised on class:
Description: The alarm is raised when a device reports a Tdcm Module Temperature Low on a tunable
Remedial action: Increase the ambient temperature
Table 39-689 OpticalTdcmNotReady

releases
Name: OpticalTdcmNotReady (1191) Severity: major Unspecified

Raised on class: TdcmNotReady (892)
Description: The alarm is raised when a device reports a Tdcm Not Ready on a tunable dispersion
compensation module’s interface.
Remedial action: This is a transient condition that should clear under normal operation but if it causes the link
to fail and persists: 1. clear the mda, 2. clear card 3. replace the card
Table 39-690 OpticalTdcmThermalControlTemperatureLimit

major releases

OpticalTdcmThermalControlTemperatureLimit Implicitly cleared: true
(1192)
Type: communicationsAlarm (4) TdcmThermalControlTemperatureLimit
Raised on class:
Description: The alarm is raised when a device reports a Tdcm Thermal Control Temperature Limit on a
tunable dispersion compensation module’s interface.
Remedial action: If this alarm persists: 1. clear the mda, 2. clear card 3. replace the card
Table 39-691 OpticalTdcmThermalControlUnlocked

releases
OpticalTdcmThermalControlUnlocked Implicitly cleared: true
(1193)
Type: communicationsAlarm (4) TdcmThermalControlUnlocked (894)
Raised on class:
Description: The alarm is raised when a device reports a Tdcm Thermal Control Unlocked on a tunable
Remedial action: This is a transient condition that should clear under normal operation but if it causes the link
to fail and persists: 1. clear the mda, 2. clear card 3. replace the card
Table 39-692 OspfExportLimitDropped

releases
Name: OspfExportLimitDropped Severity: warning Unspecified

Package: ospf (598)
Description: The alarm is raised when the total number of exported routes to the OSPF level, drops below the
configured limit.
Remedial action: Informational - the total number of exported routes from the route table to this OSPF level
drops below the configured export limit.
Table 39-693 OspfExportLimitReached

releases
Name: OspfExportLimitReached Severity: warning Unspecified

Package: ospf (599)
Description: The alarm is raised when the total number of routes to the OSPF level is equal to the configured
limit for exported routes.
Remedial action: Informational - the total number of routes for the level is equal to the configured limit for
exported routes
Table 39-694 OspfExportLimitWarning

releases
Name: OspfExportLimitWarning Severity: warning Unspecified

Package: ospf (600)
Description: The alarm is raised when the total number of exported routes to the OSPF level is equal to the
configured percentage, vRtrIsisExportLimitLogPercent of the export limit.
Remedial action: Informational - the total number of exported routes or the level is equal to the configured
Export Limit Log Percent
Table 39-695 OspfExternalLsaThresholdExceeded
releases

OspfExternalLsaThresholdExceeded Implicitly cleared: true
(372)
Type: topologyAlarm (34) manyExternalLSAsFloodingIntoIGP (271)
Package: topology
Description: The alarm is raised when the number of OSPF external LSAs exceeds the maximum threshold
because a large number of external LSAs flooding into the IGP.
Remedial action: User configured alarm for monitoring purpose. The advertised external routes can be
viewed using CPAM IGP prefix list.
Table 39-696 OspfIfTxRetransmit

Name: OspfIfTxRetransmit (662) Severity: warning Unspecified

hello
dbDescript
lsReq
lsUpdate
lsAck
nullPacket
Description: The alarm is raised when an NE retransmits an OSPF packet. The alarm information includes the
NE ID of the OSPF neighbor. The alarm is not raised against a Release 4.0 or later NE.
Remedial action: Informational - an NE retransmits an OSPF packet. The alarm information includes the NE
ID of the OSPF neighbor. The alarm is not raised against a Release 4.0 or later NE.
Table 39-697 OspfInternalLsaRateThresholdExceededPerArea

releases

OspfInternalLsaRateThresholdExceededPerArea Implicitly cleared: true
(310)
Type: topologyAlarm (34) unstableIGPNetwork (241)
Package: topology
Raised on class: topology.Area
Description: The alarm is raised when the OSPF internal LSA rate for an area exceeds the maximum allowed
value because of an unstable IGP network.
debugging purpose.
Table 39-698 OspfInternalLsaThresholdExceededPerArea

releases

OspfInternalLsaThresholdExceededPerArea Implicitly cleared: true
(309)
Type: topologyAlarm (34)
largeIgpNetwork (240)
Package: topology
Raised on class: topology.Area
Description: The alarm is raised when the number of OSPF internal LSAs for an area exceeds the maximum
allowed value because of a large IGP network.
debugging purpose.
Table 39-699 OspfLsaRateThresholdExceededPerRouter

releases

OspfLsaRateThresholdExceededPerRouter Implicitly cleared: true
(308)
Type: topologyAlarm (34) unstableLinksOnRouter (239)
Package: topology
Raised on class: topology.Router
Description: The alarm is raised when the OSPF LSA rate for an NE exceeds the maximum allowed value
because of an unstable NE link.
debugging purpose.
Table 39-700 OspfLsaThresholdExceededPerRouter

releases

OspfLsaThresholdExceededPerRouter Implicitly cleared: true
(374)
Type: topologyAlarm (34) routerAdvertisingManyLSAs (273)
Package: topology
Raised on class: topology.Router
Description: The alarm is raised when the number of OSPF LSAs for an NE exceeds the maximum allowed
value because the NE advertises too many LSAs.
debugging purpose.
Table 39-701 OTSTrailDown

releases
Name: OTSTrailDown (8084) Severity: critical Unspecified

Raised on class:
optical.OTSTrail
Description: The alarm is raised when the termination point(s) of the OTS trail are operationally down.
Table 39-702 OTUAlarmIndicationSignal
releases
Name: OTUAlarmIndicationSignal Severity: major Unspecified

Package: ethernetequipment AlarmIndicationSignal (531)
Raised on class:
ethernetequipment.OtuInterface
Description: The alarm is raised when a device reports an AIS on an OTU-enabled interface.
Table 39-703 OTUBackwardDefectIndication

releases
Name: OTUBackwardDefectIndication Severity: major Unspecified

Package: ethernetequipment BackwardDefectIndication (532)
Raised on class:
Description: The alarm is raised when a device reports a BDI on an OTU-enabled interface.
Table 39-704 OTUBackwardIncomingAlignmentError

releases

OTUBackwardIncomingAlignmentError Implicitly cleared: true
(815)
Type: communicationsAlarm (4) BackwardIncomingAlignmentError (578)
Raised on class:
Description: The alarm is raised when a device reports an ODU alarm indication signal on an OTU-enabled
interface.
Table 39-705 OTUBitErrorRateSignalDegradation

releases

OTUBitErrorRateSignalDegradation Implicitly cleared: true
(757)
Type: communicationsAlarm (4)
BitErrorRateSignalDegradation (533)
Raised on class:
Description: The alarm is raised when a device reports a BER-SD on an OTU-enabled interface.
Table 39-706 OTUBitErrorRateSignalFail

releases
Name: OTUBitErrorRateSignalFail Severity: critical Unspecified

Package: ethernetequipment BitErrorRateSignalFail (534)
Raised on class:
Description: The alarm is raised when a device reports a BER-SF on an OTU-enabled interface.
Table 39-707 OTUFECRxTxModeMismatch

releases
Name: OTUFECRxTxModeMismatch Severity: critical Unspecified

Package: ethernetequipment FECRxTxModeMismatch (535)
Raised on class:
Description: The alarm is raised when a device reports a FEC Rx/Tx mode mismatch on an OTU-enabled
interface.
Table 39-708 OTUFECSignalDegradation

releases
Name: OTUFECSignalDegradation Severity: major Unspecified

Package: ethernetequipment FECSignalDegradation (536)
Raised on class:
Description: The alarm is raised when a device reports a FEC-SD on an OTU-enabled interface.
Table 39-709 OTUFECSignalFailure

releases
Name: OTUFECSignalFailure (761) Severity: major Unspecified

Raised on class: FECSignalFailure (537)
Description: The alarm is raised when a device reports a FEC-SF on an OTU-enabled interface.
Table 39-710 OTUIncomingAlignmentError

releases
Name: OTUIncomingAlignmentError Severity: major Unspecified

Package: ethernetequipment IncomingAlignmentError (579)
Raised on class:
Description: The alarm is raised when a device reports an ODU open connection indication on an OTU-
enabled interface.
Table 39-711 OTULossOfClock

releases
Name: OTULossOfClock (762) Severity: critical Unspecified

Package: ethernetequipment Default probable cause: LossOfClock
Description: The alarm is raised when a device reports an LOC on an OTU-enabled interface.
Table 39-712 OTULossOfFraming

releases
Name: OTULossOfFraming (763) Severity: critical Unspecified
Raised on class: LossOfFraming (539)
Description: The alarm is raised when a device reports an LOF on an OTU-enabled interface.
Table 39-713 OTULossOfMultiFrame

releases
Name: OTULossOfMultiFrame (764) Severity: major Unspecified

Raised on class: LossOfMultiFrame (540)
Description: The alarm is raised when a device reports an LOM on an OTU-enabled interface.
Table 39-714 OTULossOfSignal

releases
Name: OTULossOfSignal (765) Severity: critical Unspecified

Raised on class: LossOfSignal (541)
Description: The alarm is raised when a device reports an LOS on an OTU-enabled interface.
Table 39-715 OTUODUAlarmIndicationSignal

releases

OTUODUAlarmIndicationSignal (766) Implicitly cleared: true
Package: ethernetequipment ODUAlarmIndicationSignal (542)
Raised on class:
Description: The alarm is raised when a device reports an ODU AIS on an OTU-enabled interface.
Table 39-716 OTUODULocked

releases
Name: OTUODULocked (767) Severity: critical Unspecified

Package: ethernetequipment Default probable cause: ODULocked
Description: The alarm is raised when a device reports an ODU locked on an OTU-enabled interface.
Table 39-717 OTUODUOpenConnectionIndication

releases

OTUODUOpenConnectionIndication Implicitly cleared: true
(768)
Type: communicationsAlarm (4) ODUOpenConnectionIndication (544)
Raised on class:
Description: The alarm is raised when a device reports an ODU-OCI on an OTU-enabled interface.
Table 39-718 OTUOPUPSIPayloadTypeMismatch

releases

OTUOPUPSIPayloadTypeMismatch Implicitly cleared: true
(817)
Type: communicationsAlarm (4) OPUPSIPayloadTypeMismatch (580)
Raised on class:
Description: The alarm is raised when a device reports a PM backward defect indication on an OTU-enabled
interface.
Table 39-719 OTUOPUPSITraceMismatch

releases
Name: OTUOPUPSITraceMismatch Severity: major Unspecified

Package: ethernetequipment OPUPSITraceMismatch (581)
Raised on class:
Description: The alarm is raised when a device reports an ODU locked indication on an OTU-enabled
interface.
Table 39-720 OTUPMBackwardDefectIndication

releases

OTUPMBackwardDefectIndication Implicitly cleared: true
(769)
Type: communicationsAlarm (4) PMBackwardDefectIndication (545)
Raised on class:
Description: The alarm is raised when a device reports a PM BDI on an OTU-enabled interface.
Table 39-721 OTUPMTraceIDMismatch

releases
Name: OTUPMTraceIDMismatch (819) Severity: major Unspecified

Raised on class: PMTraceIDMismatch (582)
Description: The alarm is raised when a device reports an ODU open connection indication on an OTU-
enabled interface.
Table 39-722 OTUTraceIdMismatch

releases
Name: OTUTraceIdMismatch (820) Severity: major Unspecified

TraceIdMismatch (583)
Raised on class:
Description: The alarm is raised when a device reports a trace ID mismatch on an OTU-enabled interface.
Table 39-723 OTUTrailDown

releases
Name: OTUTrailDown (5126) Severity: critical Unspecified

Raised on class:
optical.OTUTrail
Description: The alarm is raised when the termination point(s) of the OTU trail are operationally down.
Table 39-724 OTUTrailMisConfigured

releases

OTUTrailMisConfigured Implicitly cleared: false
(5127)
(4)
Package: optical
Raised on class:
optical.OTUTrail
Description: The alarm is raised when all the OCh cross connections (XCs) of an OTU trail do not have the
on all NEs of the OTU trail.
Remedial action: Recreate the OCH Cross Connects with same Trail name else Wave Tracker does not work
properly.
Table 39-725 OTUUncorrectableFECErrors

releases
Name: OTUUncorrectableFECErrors Severity: major Unspecified

Package: ethernetequipment UncorrectableFECErrors (546)
Raised on class:
Description: The alarm is raised when a device reports one or more uncorrectable FEC errors on an OTU-
enabled interface.
Table 39-726 OutOfSlots

releases
Name: OutOfSlots (462) Severity: major Unspecified

Package: equipment Default probable cause: noAvailableSlotNumbers
equipment.Shelf
Description: The alarm is raised when a stack element enters pass-through mode because there is no slot
number for the element.
Remedial action: Login to switch console, correct the slot number and reload stack.
Table 39-727 ParentTemplateInvalid

releases
Name: ParentTemplateInvalid (194) Severity: major Unspecified

Package: template Default probable cause:
Raised on class: referencedObjectInvalid (152)
template.TemplateBinding
Description: The alarm is raised when a parent template in a template binding is invalid. The alarm is
Raising condition: (’parentTemplateInvalidReference’ EQUAL ’true’)
Clearing condition: (’parentTemplateInvalidReference’ EQUAL ’false’)
Table 39-728 PathReoptimized

Name: PathReoptimized (28) Severity: warning Unspecified

Type: pathAlarm (12) Implicitly cleared: false
Package: mpls Default probable cause: pathReoptimized (21)
Raised on class: mpls.Tunnel
Description: The alarm is raised when an MPLS path generates an mplsTunnelReoptimized trap.
Table 39-729 PathRerouted

Name: PathRerouted (29) Severity: warning Unspecified

Type: pathAlarm (12) Implicitly cleared: false
Package: mpls Default probable cause: pathRerouted (22)
Raised on class: mpls.Tunnel
Description: The alarm is raised when an MPLS path generates an mplsTunnelRerouted trap.
Table 39-730 PbbSiteMisconfiguration

releases
Name: PbbSiteMisconfiguration Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: includeBothBAndISite
Package: vpls (440)
Raised on class:
vpls.AbstractVpls
Description: The alarm is raised when a VPLS contains a B-Site and an I-Site.
Raising condition: ((’Include B-Site(s)’ EQUAL ’true’) AND (’Include I-Site(s)’ EQUAL ’true’))
Clearing condition: ((’Include B-Site(s)’ NOT EQUAL ’true’) OR (’Include I-Site(s)’ NOT EQUAL ’true’))
Remedial action: A configuration error has occurred which needs to be corrected. The service can have only
an I-site or a B-site but not both.
Table 39-731 PChipCAMEvent

Name: PChipCAMEvent (814) Severity: warning Unspecified

Type: hardwareAnomaly (55) Implicitly cleared: true
Package: equipment Default probable cause: camError (577)
Description: The alarm is raised when an IOM or CPM experiences a P-chip CAM error.
Remedial action: Informational - if the condition persists then the card indicated in the alarm should be
replaced.
Table 39-732 PChipError

releases
Name: PChipError (593) Severity: minor Unspecified

Package: equipment Default probable cause: pChipError
equipment.BaseCard
Description: The alarm is raised when persistent FCS errors are detected on the specified complex in the
specified direction.
Remedial action: A fault has been detected in the hardware. If the problem persists please contact Alcatel-
Table 39-733 PChipMemoryEvent

releases
Name: PChipMemoryEvent (608) Severity: warning Unspecified

Package: equipment Default probable cause: memoryParityError
equipment.BaseCard
Description: The alarm is raised when a P chip detects a memory parity error. The alarm is raised against a
7450 ESS, 7710 SR, or 7750 SR. The alarm is raised against a Release 6.0 NE at R10 or later and a Release
6.1 NE at R5 or later.
Table 39-734 peerSetConfigurationIssue

releases
Name: peerSetConfigurationIssue Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: mismatchPeerSets
Package: pim (199)
Raised on class:
Description: The alarm is raised when a peer set is misconfigured.
Anycast RP configuration and its operational status flag so that the Inconsistent Peer Sets and Only one peer
bits are reset.
Table 39-735 PeerUnreachable

Name: PeerUnreachable (842) Severity: variable Unspecified

Type: ProtocolAlarm (1) Implicitly cleared: true
Package: l2tp Default probable cause: protocolDown (1)
Raised on class: l2tp.Peer
Description: The alarm is raised when an L2TP peer becomes unreachable.
Remedial action: This alarm is raised when L2TP peer is unreachable. Please verify the L2TP tunnel profile
configuration to ensure that the peer is properly configured. Also verify that the peer is actually reachable from
this network element. This alarm is cleared automatically when L2TP Peer becomes reachable.
Table 39-736 PersistenceRestoreProblem

releases

PersistenceRestoreProblem Implicitly cleared: false
(5141)
Type: processingErrorAlarm (81) persistenceRestoreProblem (2064)
Package: sw
Raised on class:
sw.NodePersistence
Description: The alarm is raised when an error is detected while processing a persistence record.
Remedial action: Check the node persistence configuration.
Table 39-737 PersistencyFileSysThresRaised

releases

PersistencyFileSysThresRaised Implicitly cleared: true
(5142)
Type: equipmentAlarm (3) persistencyFileSysThresRaised (2065)
Package: sw
Raised on class:
sw.NodePersistence
Description: The alarm is raised when the filesystem reaches 90 percent usage.
Remedial action: Delete unnecessary files on the compact flash disk. This operation must be executed using
CLI interface on the NE.
Table 39-738 PhysicalLinkDown

releases
Name: PhysicalLinkDown Severity: major Unspecified

Type: communicationsAlarm Default probable cause: PhysicalLinkDown
(4) (846)
Package: mpr
Raised on class: mpr.VlanPath
Description: The alarm is raised when the physical link between two hops of a VLAN path is down.
Remedial action: Check if the port that is used in the physical link is operationally up.
Table 39-739 PkiCertVerificationFailed

releases
Name: PkiCertVerificationFailed Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: pkiCertInvalid
Package: ipsec (1478)
Raised on class:
ipsec.IPSecBaseEntity
Description: The alarm is raised when an attempt to verify the certificate fails.
Remedial action: An attempt to verify the certificate fails. Please make sure the certificate specified exists
under the node cf3:system-pki and is a valid certificate
Table 39-740 PkiFileReadFailed (ipsec)

releases
Name: PkiFileReadFailed (3744) Severity: major Unspecified

Package: ipsec Default probable cause:
Raised on class: pkiFileReadCorrupted (1479)
ipsec.IPSecBaseEntity
Description: The alarm is raised when an attempt to read the file fails.
Remedial action: An attempt to read the PKI file fails. Please make sure the path specified is correct and the
file exists under the node cf3:system-pki
Table 39-741 PkiFileReadFailed (sitesec)
releases
Name: PkiFileReadFailed (3744) Severity: major Unspecified

Package: sitesec Default probable cause:
Raised on class: pkiFileReadCorrupted (1479)
sitesec.CertificateAuthProfile
Description: The alarm is raised when an attempt to read the file fails.
Remedial action: An attempt to read the PKI file fails. Please make sure the path specified is correct and the
file exists under the node cf3:system-pki
Table 39-742 PlcyAcctStatsEventOvrflw

releases

PlcyAcctStatsEventOvrflw Implicitly cleared: true
(5640)
Type: equipmentAlarm (3) PlcyAcctStatsPoolInUseExcAndLow (2415)
Package: equipment
Raised on class:
equipment.Card
Description: The alarm is raised because of resource usage fluctuation that happens when the number of in-
use stats resource usage exceeds 95 percent and deprecates below 85 percent of the specified stats pool limit
more than 200 times.
Remedial action: Notifications will resume once the resource usage fluctuation is in control i.e when the
occurrence of tmnxPlcyAcctStatsPoolExcResource and tmnxPlcyAcctStatsPoolLowResource is less than 200.
Table 39-743 PMFileRecovery

releases
Name: PMFileRecovery (4867) Severity: major Unspecified

Package: netw Default probable cause: netconfDown
netw.NetworkElement
Description: The alarm is raised when a 5620 SAM main server loses connectivity to an NE and as a result
retrieves PM files that were not previously collected.
Table 39-744 PoolMinFreeExc

releases
Name: PoolMinFreeExc Severity: warning Unspecified

Package: dhcp actualFreeAddrBelowPoolMin (1434)
Raised on class:
dhcp.AddressPool
Description: The alarm is raised when the actual number of free addresses in a pool falls below the desired
minimum number specified in the address pool configuration.
Remedial action: The alarm is raised when the actual number of free addresses in a pool falls below the
desired minimum number specified in the address pool configuration.
Table 39-745 PortsSeggregated

releases
Name: PortsSeggregated (746) Severity: major Unspecified

Package: mpr Default probable cause: portsSeggregated
Description: The alarm is raised when the two ports that are to be part of a service cross-connect are
segregated.
Remedial action: Segregated ports are being used in service. Remove the port from Segregation or use a
port that is not involved in Segregation.
Table 39-746 PowerModule_voltageALocalFailure

releases

PowerModule_voltageALocalFailure Implicitly cleared: true
(6171)
Type: environmentalAlarm (2) powerProblem (911)
Package: femto
Raised on class:
femto.SCATCAPowerModule
Description: This Alarm is raised when the 48V Voltage Failure happens in the power supply A of the local
Shelf.
Table 39-747 PowerModule_voltageARemoteFailure

releases

PowerModule_voltageARemoteFailure Implicitly cleared: true
(6172)
Package: femto
Raised on class:
Description: This Alarm is raised when the 48V Voltage Failure happens in the power supply A of the remote
Shelf.
Table 39-748 PowerModule_voltageBLocalFailure

releases
PowerModule_voltageBLocalFailure Implicitly cleared: true
(6173)
Package: femto
Raised on class:
Description: This Alarm is raised when the 48V Voltage Failure happens in the power supply B of the local
Shelf.
Table 39-749 PowerModule_voltageBRemoteFailure

releases

PowerModule_voltageBRemoteFailure Implicitly cleared: true
(6174)
Package: femto
Raised on class:
Description: This Alarm is raised when the 48V Voltage Failure happens in the power supply B of the remote
Shelf.
Table 39-750 PowerSupplyACRectifierFailure

releases

PowerSupplyACRectifierFailure Implicitly cleared: true
(5181)
Type: equipmentAlarm (3) PowerSupplACRectifierFailedorMissing (2097)
Package: equipment
Raised on class:
equipment.PowerSupplyTray
Description: This alarm is generated if any one of the AC rectifiers for a given power supply is in a failed state
or is missing. When the alarm is raised during device discovery, one or both AC Rectifiers of the Power Supply
Tray may be not equipped. When the alarm is raised while the device is in the managed state, one or both AC
Rectifiers of the Power Supply Tray might be removed or they have a fault condition. The alarm clears when
the status changes to OK.
Remedial action: Ensure that the NE is properly connected to power. There is an increased risk of the power
supply failing, causing insufficient power to the system. Please bring the AC rectifiers back online by equipping
them properly. If the problem persists please contact Alcatel-Lucent support for assistance.
Table 39-751 PowerSupplyVoltageAlarm

releases
Name: PowerSupplyVoltageAlarm Severity: variable Unspecified

Package: equipment powerSupplyFailure (117)
Raised on class:
equipment.PowerSupply
Description: The alarm is raised when the power supply voltage alarm state changes to a value other than
Normal.
Remedial action: Check the status of the site power supply.
Table 39-752 PPPFail

Name: PPPFail (632) Severity: variable Unspecified

Package: equipment Default probable cause: pppFail
equipment.Equipment
Description: The alarm is raised when a PPP IP Fail condition is detected.
Table 39-753 PppNcpFailure

releases
Name: PppNcpFailure (3689) Severity: major Unspecified

Raised on class: sapAtmPppNcpFailure (1428)
service.ServiceAccessPoint
Description: The alarm is raised when there is an NCP phase setup problem.
Remedial action: This alarm indicates the NCP phase setup failed, thus IP protocol can not be configured for
the user that attempted to set up the PPP session. Please verify NCP setup configuration.
Table 39-754 PPPoASessionFailure

releases
Name: PPPoASessionFailure Severity: major Unspecified

Package: service sapAtmPppSessionFailure (1427)
Raised on class:
service.AccessInterface
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot create a PPPoA Session.
Remedial action: This alarm indicates the problem encountered by NE while trying to create a new PPPoA
session. Please review the alarm’s additional text to obtain information about the error condition. Possible
problems include authentication failures, LCP or IPCP layer problems during the session establishment, or
possible mis-configuration on the service interface or PPP policy.
Table 39-755 PPPoESessionFailure

releases
Name: PPPoESessionFailure (2915) Severity: major Unspecified

pppoeSessionFailed (1119)
Raised on class:
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot create a PPPoE Session.
Remedial action: This alarm indicates the problem encountered by NE while trying to create a new PPPoE
session. Please review the alarm’s additional text to obtain information about the error condition. Possible
problems include authentication failures, LCP or IPCP layer problems during the session establishment, or
possible mis-configuration on the service interface or PPP policy.
Table 39-756 PrefixLimitExceeded

releases
Name: PrefixLimitExceeded Severity: critical Unspecified

Type: ProtocolAlarm (1) Default probable cause: prefixLimitExceeded
Package: bgp (4)
Description: The alarm is raised when a BGP instance learns the maximum number of peer routes.
given the number of peer routes that are being received. If the threshold is set close to the maximum number
of routes supported by the NE then it is probable that there is an issue with another NE in the network. If the
Table 39-757 PrefixLimitNearing

Name: PrefixLimitNearing (3) Severity: major Unspecified

Type: ProtocolAlarm (1) Implicitly cleared: false
Package: bgp Default probable cause: prefixLimitNearing (3)
Description: The alarm is raised when a BGP instance exceeds the threshold percentage of the configured
maximum.
given the number of peer routes that are being received. If the threshold is set close to the maximum number
of routes supported by the NE then it is probable that there is an issue with another NE in the network. If the
Table 39-758 PrimaryVirtualSwitchControllerFailed

releases

PrimaryVirtualSwitchControllerFailed Implicitly cleared: true
(5429)
Type: virtualSwitchAlarm (136) PrimaryControllerFailOver (2130)
Package: dctr
Raised on class: dctr.VirtualSwitch
Description: The alarm is raised when communication between the virtual switch to the primary controller has
failed.
Remedial action: This alarm can be cleared when primary virtual switch is operationally up.
Table 39-759 ProbeFailedAlarm (atm)

releases
Name: ProbeFailedAlarm (3707) Severity: major Unspecified

Type: oamAlarm (18) Implicitly cleared: true
Package: atm Default probable cause: networkDegradation
atm.PvcConnection
Description: The alarm is raised when an OAM test on the object reports a probe failure.
understand why the underlying transport network is un-reliable.
Table 39-760 ProbeFailedAlarm (bgp)

releases
Name: ProbeFailedAlarm Severity: major Unspecified

Type: oamAlarm (18) Default probable cause: networkDegradation
Package: bgp (204)
Table 39-761 ProbeFailedAlarm (ethernetoam)

releases

Package: ethernetoam Default probable cause:
Raised on class: networkDegradation (204)
Description: The alarm is raised when an OAMtest on the object reports a probe failure.
Table 39-762 ProbeFailedAlarm (ldp)

releases

Package: ldp (204)
Raised on class: ldp.Site
Table 39-763 ProbeFailedAlarm (lte)
releases

Package: lte (204)
Description: The alarm is raised when ProbeFailedAlarm is raised for any test on this object.
Table 39-764 ProbeFailedAlarm (lteservice)

releases

Package: lteservice Default probable cause:
lteservice.MobileService
understand why the underlying transport network is unreliable.
Table 39-765 ProbeFailedAlarm (mirror)

releases

Package: mirror (204)
Table 39-766 ProbeFailedAlarm (monpath)

releases

Package: monpath Default probable cause:
Table 39-767 ProbeFailedAlarm (mpls)
releases

Package: mpls (204)
Raised on class: mpls.Lsp
Table 39-768 ProbeFailedAlarm (mplstp)

releases

Package: mplstp (204)
Raised on class:
mplstp.TPLsp
Table 39-769 ProbeFailedAlarm (netw)

releases

Package: netw Default probable cause: networkDegradation
netw.NetworkElement
Table 39-770 ProbeFailedAlarm (pim)

releases

Package: pim (204)
Table 39-771 ProbeFailedAlarm (rtr)

releases

Package: rtr (204)
Raised on class:
rtr.VirtualRouter
Table 39-772 ProbeFailedAlarm (service)

releases

service.SpokeConnector
Table 39-773 ProbeFailedAlarm (svt)

releases

Package: svt (204)
Raised on class: svt.Tunnel
Table 39-774 ProbeFailedAlarm (vll)

releases

Package: vll (204)
Table 39-775 ProbeFailedAlarm (vpls)

releases

Package: vpls (204)
Raised on class:
vpls.AbstractVpls
Table 39-776 ProbeFailedAlarm (vprn)

releases

Package: vprn (204)
Table 39-777 ProbeFailedAlarm2 (ethernetoam)

releases
Name: ProbeFailedAlarm2 Severity: major Unspecified

Package: ethernetoam (204)
Raised on class:
ethernetoam.Mep
Table 39-778 ProbeFailedAlarm2 (lte)

releases

Package: lte (204)
Raised on class: lte.EPSPeer
Table 39-779 ProbeFailedAlarm2 (mpls)

releases
Name: ProbeFailedAlarm2 (3738) Severity: major Unspecified

Package: mpls Default probable cause:
mpls.P2MPDynamicLsp
Table 39-780 ProbeFailedAlarm2 (rtr)

releases

rtr.LDPTunnelInterface
Table 39-781 ProbeFailedAlarm2 (service)

releases

Package: service (204)
Raised on class: service.Site
Table 39-782 ProbeFailedAlarm2 (svt)

releases

Type: oamAlarm (18)
Package: svt Default probable cause: networkDegradation
svt.SdpBinding
Table 39-783 ProbeFailedAlarm3 (mpls)

releases

Package: mpls (204)
Raised on class: mpls.LspPath
Table 39-784 ProbeFailedAlarm3 (service)

releases

service.CompositeService
Table 39-785 ProbeFailureAlarm

releases
Name: ProbeFailureAlarm Severity: major Unspecified

Package: sas (204)
Raised on class: sas.Test
Description: This alarm is raised when a probe failure trap is received from the node.
Remedial action: Fix network connections issues.
Table 39-786 ProvisioningMismatch

releases
Name: ProvisioningMismatch Severity: variable Unspecified

(634)
Type: equipmentAlarm (3)
Package: equipment provisioningMismatch (470)
Raised on class:
equipment.Equipment
Description: The alarm is raised when a license mismatch is detected for provisioned equipment.
Table 39-787 PTPCardNotSupportedAlarm

releases

PTPCardNotSupportedAlarm Implicitly cleared: true
(3603)
Type: equipmentAlarm (3) PTPCardNotSupported (1392)
Package: ptp
Raised on class:
ptp.IEEEPTPClock
Description: The alarm is raised when the Precision Timing Protocol (PTP) is enabled on a card that does not
support clock recovery.
Remedial action: Please enable PTP on CPM which supports OCX0 oscillator type
Table 39-788 PTPClockRecoveryStateAlarm

releases

PTPClockRecoveryStateAlarm Implicitly cleared: false
(3605)
Type: communicationsAlarm (4) PTPClockRecoveryStateChange (1394)
Package: ptp
Raised on class:
ptp.IEEEPTPClock
Description: The alarm is raised when the aluPtpClockRecoveryState changes for an IEEE 1588 Precision
Timing Protocol (PTP) clock.
Table 39-789 PTPMasterChangeAlarm

releases
Name: PTPMasterChangeAlarm Severity: info Unspecified

Type: communicationsAlarm (4) Default probable cause: PTPMasterChange
Package: ptp (1395)
Raised on class:
ptp.IEEEPTPClock
Description: The alarm is raised when there is a change in the synchronization source for a Precision Timing
Protocol (PTP) clock.

Table 39-790 PTPOutOfResourcesAlarm
releases
Name: PTPOutOfResourcesAlarm Severity: minor Unspecified

Package: ptp PTPOutOfResources (1396)
Raised on class:
ptp.IEEEPTPClock
Description: The alarm is raised when the Precision Timing Protocol (PTP) process on the card is out of
resources. This may occur in either of two situations: 1. The number of PTP peers exceeds the system limit. 2.
The total unicast packet rate negotiated with all PTP peers reaches the maximum packet rate supported by the
system.
Table 39-791 PTPPortDSPortStateAlarm

releases
Name: PTPPortDSPortStateAlarm Severity: info Unspecified

Package: ptp PTPPortDSPortState (1399)
Raised on class: ptp.IEEEPTPPort
Description: The alarm is raised when the aluPtpPortDSPortState changes for an IEEE 1588 Precision Timing
Protocol (PTP) port.
Table 39-792 PTPQualityLevelChangedAlarm

releases

PTPQualityLevelChangedAlarm Implicitly cleared: false
(3612)
Type: communicationsAlarm (4) PTPQualityLevelChanged (1401)
Package: sonet
Description: The alarm is raised when there is a change of the received quality level on the Precision Timing
Protocol (PTP).
Table 39-793 QChipBufferMemoryEvent

releases
Name: QChipBufferMemoryEvent Severity: minor Unspecified

Type: hardwareAnomaly (55) Default probable cause: bufMemoryError
Description: The alarm is raised when a Q-chip experiences an occurrence of a buffer memory error on IOM
or CPM.
Table 39-794 QChipIfCellEvent

Name: QChipIfCellEvent (4991) Severity: minor Unspecified

Package: equipment Default probable cause: ifCellError (2045)
Description: The alarm is raised when an inter-chip interface (XPL2 bundle) experiences internal datapath cell
errors on IOM or CPM.
Table 39-795 QChipIfDownEvent

Name: QChipIfDownEvent Severity: minor Unspecified

Type: hardwareAnomaly (55) Default probable cause: ifDownError
Raised on class:
equipment.Card
Description: The alarm is raised when an inter-chip interface (XPL2 bundle) experiences an internal datapath
problem on IOM or CPM.
Table 39-796 QChipIntMemoryEvent

releases
Name: QChipIntMemoryEvent Severity: minor Unspecified

Type: hardwareAnomaly (55) Default probable cause: intMemoryError
Description: The alarm is raised when a Q-chip experiences an occurrence of an internal memory error on
IOM or CPM.
Table 39-797 QChipResetProtImpact

releases
Name: QChipResetProtImpact Severity: minor Unspecified

Package: equipment qChipResetProtocolTimeout (2418)
Raised on class:
equipment.Card
Description: The alarm is raised when a slot experienced a data path failure due to Qchip reset on IOM/CPM
which caused a timeout on short BFD or ETH-CFM protocol timers.
Remedial action: Informational.The alarm is raised when a slot experienced a data path failure due to Qchip
reset on IOM/CPM which caused a timeout on short BFD or ETH-OAM protocol timers. Services-related data
associated with the impacted protocol may be lost.
Table 39-798 QChipStatsMemoryEvent

releases
Name: QChipStatsMemoryEvent Severity: minor Unspecified

Type: hardwareAnomaly (55) Default probable cause: statsMemoryError
Description: The alarm is raised when a Q-chip experiences an occurrence of a statistics memory error on
IOM or CPM.
Table 39-799 QueryVerMismatch

releases

QueryVerMismatch (159) Implicitly cleared: false
(11) InvalidVersionofQueryMessageReceived (129)
Package: igmp
Raised on class:
igmp.Interface
Description: The alarm is raised when an interface configured for IGMPv3 receives a query message for an
earlier IGMP version. The interface subsequently enters an IGMP mode that is compatible with the earlier
version. The alarm information includes the IGMP version on the interface and the IGMP version of the
received query.
Table 39-800 RadAcctOnOngoing

major
releases
Name: RadAcctOnOngoing Severity: minor Unspecified

radiusAccountingPolicyAlarm TooManyUnacknowledgedRadiusAccountingOnMessages
(38) (2025)
Package: aaa Applicable probable causes:
Raised on class: TooManyUnacknowledgedRadiusAccountingOnMessages
aaa.RadiusServerPolicy MisconfiguredPolicy
RadiusServerUnreachable
MissingClientInformation
Description: The alarm is raised each time when the RADIUS client has sent 10 RADIUS Accounting-On
messages without receiving any acknowledgement from the RADIUS server.
Remedial action: Ensure that: 1.The RADIUS server is up and running. 2.The RADIUS server policy
configuration is correct. Please note that this system will keep on retrying indefinitely until it receives an
acknowledgement from the RADIUS server.
Table 39-801 RadioHop15TCA

releases
Name: RadioHop15TCA (4835) Severity: variable Unspecified

Package: mwa Default probable cause: ThresholdCrossed
mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio hop 15 minutes TCA
information.
Table 39-802 RadioHop15UAT

releases
Name: RadioHop15UAT (4836) Severity: variable Unspecified

Package: mwa Default probable cause: UnavailableTime
mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio hop 15 minutes UAT
information.
Table 39-803 RadioHop24TCA

releases
Name: RadioHop24TCA (4837) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio hop 24 Hours TCA
information.
Table 39-804 RadioHop24UAT

releases
Name: RadioHop24UAT (4838) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio hop 24 Hours UAT
information.
Table 39-805 RadioLink15TCA

releases
Name: RadioLink15TCA (4839) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio Link 15 minutes TCA
information.
Table 39-806 RadioLink15UAT

releases
Name: RadioLink15UAT (4840) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio Link 15 minutes UAT
information.
Table 39-807 RadioLink24TCA

releases
Name: RadioLink24TCA (4841) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio Link 24 Hours TCA
information.
Table 39-808 RadioLink24UAT

releases
Name: RadioLink24UAT (4842) Severity: variable Unspecified

mwa.PortTermination
Description: The alarm is raised when a MPT detects a threshold crossing - Radio Link 24 Hours UAT
information.
Table 39-809 RadioLinkAMAbnormalState

releases
Name: RadioLinkAMAbnormalState Severity: inate Unspecified

Type: radiolinkAMABNAlarm (119) Default probable cause:
Package: radioequipment RadiolinkAMABNProblem (1525)
Raised on class:
Description: The alarm is raised when abnormal state resulted due to Radio link AM mode.
Remedial action: The alarm is raised when abnormal state resulted due to Radio link AM mode.
Table 39-810 RadioLinkDown

Name: RadioLinkDown (747) Severity: major Unspecified

(4) Default probable cause: radioLinkDown
Package: mpr (523)
Raised on class: mpr.VlanPath
Description: The alarm is raised when the radio link between two hops of a VLAN path is down.
Remedial action: Check if the port that is used in the Radio link is operationally up.
Table 39-811 RadioLoopProblemCh1

releases
Name: RadioLoopProblemCh1 Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: LoopProblem
Package: mwa (1922)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects a ATPC/ACM Loop problem - CH1 Radio Loop Problem
information.
Table 39-812 RadioLoopProblemChx

releases
Name: RadioLoopProblemChx Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: LoopProblem
Package: mwa (1922)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects a ATPC/ACM Loop problem - CHX Radio Loop Problem
information.
Table 39-813 RadioRdi

Name: RadioRdi (4846) Severity: major Unspecified

Package: mwa Default probable cause: Rdi (1888)
Description: The alarm is raised when a microwave radio device receives a remote defect indication from the
far end microwave radio.
information.
Table 39-814 RadioSwPackageMissing

releases
Name: RadioSwPackageMissing Severity: warning Unspecified

Type: integrityViolation (85) Default probable cause: SwPackageMissing
Package: mwa (1925)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a valid microwave radio software package is not present at startup.
information.
Table 39-815 RadiusAcctPlcyFailure

releases
Name: RadiusAcctPlcyFailure Severity: major Unspecified

radiusAccountingPolicyAlarm radiusAccountingRequestFailure (260)
(38)
Package: radiusaccounting
Raised on class:
radiusaccounting.Policy
Description: The alarm is raised when a RADIUS accounting request is not successfully sent to any of the
RADIUS servers specified in the RADIUS accounting policy.
Remedial action: The Radius server(s) which are configured in the accounting policy are unreachable. This
may occur in a number of different scenarios. The server(s) may have become unresponsive - please refer to
the Radius server documentation for assistance. The network connectivity to the server(s) may have been lost
- please investigate why the underlying transport network is unreliable.
Table 39-816 RadiusInsertedFltrEntryDropped

releases

RadiusInsertedFltrEntryDropped Implicitly cleared: false
(1152)
Type: configurationAlarm (11) FilterEntryDropped (856)
Package: aclfilter
Raised on class:
Description: The alarm is raised when a request to insert a filter entry is not successful for a RADIUS
application.
Remedial action: A Configuration error has occurred. The request to insert a filter entry was not successful for
Radius application. Check the configuration filter entry.
Table 39-817 RadiusInsertSpaceThresholdAlarm

releases

RadiusInsertSpaceThresholdAlarm Implicitly cleared: true
(1151)
Type: configurationAlarm (11) UtilizationExceedConfiguredLimit (855)
Package: aclfilter
Raised on class:
Description: The alarm is raised when the utilization of a filter entry range that is reserved for filter entry
insertion increases to the configured maximum value for a RADIUS application insert range.
Remedial action: The filter entry range reserved for filter entry insertion has increased to the configured high
watermark for Radius application. Make an adjusted to the watermarks or to the filter.
Table 39-818 radiusServerOverloaded

releases

radiusServerOverloaded Implicitly cleared: true
(3913)
Type: communicationsAlarm radiusServerRequestLimitReached (1499)
(4)
Package: subscrauth
Raised on class:
subscrauth.RadiusEntry
Description: The alarm is raised when the RADIUS server is overloaded.
Raising condition: ((’Operational State’ EQUAL ’Over Loaded’))
Clearing condition: ((’Operational State’ NOT EQUAL ’Over Loaded’))
Remedial action: Verify the RADIUS server is properly configured to process pending authentication requests
at the desired rate and ensure that this rate matches the authentication request limit defined for this RADIUS
server on the network element.
Table 39-819 RadRouteDownloadFailed

releases
Name: RadRouteDownloadFailed Severity: warning Unspecified
Package: aaa networkDegradation (204)
Raised on class:
aaa.RouteDownloadPolicy
Description: The alarm is raised when a RADIUS route-download process fails.
Remedial action: Ensure that: 1.The routes defined in the RADIUS Server have a valid syntax. 2.The number
of downloaded routes is less than the maximum. 3.There are no issues affecting the node’s ability to populate
the routes into the routing table.
Table 39-820 RDI (mpr)

releases
Name: RDI (806) Severity: minor Unspecified

(4) Default probable cause: remoteDefectIndication
Package: mpr (572)
Raised on class:
mpr.IMALink
Description: The alarm is raised when a Remote Defect Indication signal is detected on an ASAP MDA.
Table 39-821 RDICh1

releases
Name: RDICh1 (4833) Severity: variable Unspecified

Raised on class: RemoteDefectIndication (1919)
mwa.PortTermination
Description: The alarm is raised when a MPT receives a remote MPT CH1 remote defect indication
information.
Table 39-822 RDIChx

releases
Name: RDIChx (4834) Severity: variable Unspecified

Raised on class: RemoteDefectIndication (1919)
mwa.PortTermination
Description: The alarm is raised when a MPT receives a remote MPT CHX remote defect indication
information.
Table 39-823 ReceivedHigherBridgePriority

releases

ReceivedHigherBridgePriority Implicitly cleared: false
(504)
Type: SdpBindingAlarm (30) customerDeviceMisconfigured (332)
Package: l2fwd
Raised on class: l2fwd.CircuitStp
Description: The alarm is raised when a customer NE is configured with a bridge priority of zero. The SDP
binding that connects to the customer device is subsequently blocked.
Remedial action: Remove the customer’s device or reconfigure the customer’s bridge priority with value
greater than zero.
Table 39-824 RedundancySwitchover

releases
Name: RedundancySwitchover Severity: warning Unspecified

Type: equipmentAlarm (3) Default probable cause: CPMSwitchover
Raised on class:
netw.NetworkElement
Description: The alarm is raised when a 5620 SAM main server receives a CPMSwitchover trap from an NE,
which indicates that the standby CPM detects an active CPM failure and is preparing to take over as the new
active CPM.
Table 39-825 RedundantIfMismatch

releases
Name: RedundantIfMismatch Severity: major Unspecified

Package: srrp redundantIfNotProperlyPaired (312)
Raised on class:
srrp.Instance
Description: The alarm is raised when the local and remote redundant interfaces are not correctly paired.
Remedial action: Reconfigure the redundant interfaces for the peer SRRP instances so that they match each
other.
Table 39-826 RedundantRadioLink

releases
Name: RedundantRadioLink Severity: minor Unspecified

Package: netw redundantRadioLinkConfigured (819)
Raised on class:
netw.RadioPhysicalLink
Description: The alarm is raised when a radio link is discovered between two nodes when there is already a
physical link(s) between the same nodes.
Remedial action: Informational-this alarm indicates that there is another radio link between the nodes
involved.
Table 39-827 ReferenceOneLossOfSignal

releases

ReferenceOneLossOfSignal Implicitly cleared: true
(1953)
Type: communicationsAlarm (4) ReferenceOneLossOfSignal (941)
Package: sonet
Description: The alarm is raised when the Timing Reference One on an NE is not qualified due to Loss of
Signal.
Raising condition: ((’Not Qualified Due To’anyBit’LOS’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’LOS’)))
Remedial action: Make sure that peer connected to Reference One is properly configured.
Table 39-828 ReferenceOneOutOfFrequency

releases

ReferenceOneOutOfFrequency Implicitly cleared: true
(1954)
Type: communicationsAlarm (4) ReferenceOneOutOfFrequency (942)
Package: sonet
Description: The alarm is raised when the Timing Reference One on an NE is not qualified due to Out of
frequency.
Raising condition: ((’Not Qualified Due To’anyBit’OOF’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’OOF’)))
Remedial action: Check the communication path is up between the local PTP slave clock and its selected
master
Table 39-829 ReferenceOneOutOfPollInRange

releases

ReferenceOneOutOfPollInRange Implicitly cleared: true
(1955)
Type: communicationsAlarm (4) ReferenceOneOutOfPollInRange (943)
Package: sonet
Description: The alarm is raised when the Timing Reference One on an NE is not qualified due to Out of poll
in range.
Raising condition: ((’Not Qualified Due To’anyBit’OOPIR’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’OOPIR’)))

Remedial action: Check the timing reference is configured correctly. Check the SONET port is configured
correctly and that the physical layer cabling is operating correctly. Call customer support if necessary.
Table 39-830 ReferenceTwoLossOfSignal

releases

ReferenceTwoLossOfSignal Implicitly cleared: true
(1956)
Type: communicationsAlarm (4) ReferenceTwoLossOfSignal (944)
Package: sonet
Description: The alarm is raised when the Timing Reference Two on an NE is not qualified due to Loss of
Signal.
Raising condition: ((’Not Qualified Due To’anyBit’LOS’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’LOS’)))
Remedial action: Make sure that peer connected to Reference Two is properly configured.
Table 39-831 ReferenceTwoOutOfFrequency

releases

ReferenceTwoOutOfFrequency Implicitly cleared: true
(1957)
Type: communicationsAlarm (4) ReferenceTwoOutOfFrequency (945)
Package: sonet
Description: The alarm is raised when the Timing Reference Two on an NE is not qualified due to Out of
frequency.
Raising condition: ((’Not Qualified Due To’anyBit’OOF’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’OOF’)))
Remedial action: Make sure that frequency configured for Reference Two is correct.
Table 39-832 ReferenceTwoOutOfPollInRange

releases

ReferenceTwoOutOfPollInRange Implicitly cleared: true
(1958)
Type: communicationsAlarm (4) ReferenceTwoOutOfPollInRange (946)
Package: sonet
Description: The alarm is raised when the Timing Reference Two on an NE is not qualified due to Out of poll
in range.
Raising condition: ((’Not Qualified Due To’anyBit’OOPIR’))
Clearing condition: NOT (((’Not Qualified Due To’anyBit’OOPIR’)))

Remedial action: Check the timing reference is configured correctly. Check the SONET port is configured
correctly and that the physical layer cabling is operating correctly. Call customer support if necessary.
Table 39-833 Registered4GUEsExceeded

releases
Name: Registered4GUEsExceeded Severity: info Unspecified

Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of 4G Registered UEs exceeds the threshold that has been
Raising condition: ((’4G Registered UEs Threshold’ NOT EQUAL ’0L’) AND (’4G Registered UEs’ > ’4G
Registered UEs Threshold’))
Table 39-834 RegisteredIdle4GUEsExceeded

releases

RegisteredIdle4GUEsExceeded Implicitly cleared: false
(5049)
Package: ltemme
Raised on class:
ltemme.MmeInstance
Description: The alarm is raised when the number of 4G Registered Idle UEs exceeds the threshold that has
been set by the operator.
Raising condition: ((’4G Registered Idle UEs Threshold’ NOT EQUAL ’0L’) AND (’4G Registered Idle UEs’ >
’4G Registered Idle UEs Threshold’))
Table 39-835 RemoteDefectIndication

releases
Name: RemoteDefectIndication Severity: variable Unspecified

Package: equipment remoteDefectIndication (572)
Description: The alarm is raised when a RDI occurs.
Table 39-836 RemoteNEFailure

releases
Name: RemoteNEFailure (1173) Severity: variable Unspecified

Package: equipment Default probable cause: remoteNEFailure
equipment.Equipment
Description: The alarm is raised when a remote NE failure is detected.
Table 39-837 ReplaceableUnitMissing

releases
Name: ReplaceableUnitMissing Severity: variable Unspecified

Type: equipmentAlarm (3) Default probable cause: cardMissing
Raised on class:
equipment.Equipment
Description: The alarm is raised when a device detects that a provisioned card is not physically present.
Table 39-838 ReplaceableUnitProblem (equipment)

releases
Name: ReplaceableUnitProblem (636) Severity: variable Unspecified

Package: equipment Default probable cause: cardFail
equipment.Equipment
Description: The alarm is raised when a card fails.
Table 39-839 ReplaceableUnitProblem (mpr)

releases
Name: ReplaceableUnitProblem (636) Severity: variable Unspecified

Package: mpr Default probable cause: cardFail
mpr.SubRackElements
Description: The alarm is raised when a card fails.
Table 39-840 ReplaceableUnitTypeMismatch (equipment)

releases
ReplaceableUnitTypeMismatch (637) Implicitly cleared: true
Package: equipment equipmentMismatch (473)
Raised on class:
equipment.Equipment
Description: The alarm is raised when there is a mismatch between the installed card type and the expected
card type.
Remedial action: A configuration error has occurred which must be corrected. The card type configured for
the slot identified in the alarm must match the installed card type.
Table 39-841 ReplaceableUnitTypeMismatch (mpr)

releases

ReplaceableUnitTypeMismatch (637) Implicitly cleared: true
Package: mpr equipmentMismatch (473)
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when there is a mismatch between the installed equipment type and the
expected equipment type.
Remedial action: A configuration error has occurred which must be corrected. The card type configured for
the slot identified in the alarm must match the installed card type.
Table 39-842 ReplicationLmtExceeded

releases
Name: ReplicationLmtExceeded Severity: info Unspecified

Package: equipment resourceLimitReached (131)
Raised on class:
equipment.BaseCard
Description: The alarm is raised when an IOM fails to program an OIF for an (S,G) record because the
replication limit for that (S,G) on that IOM has been reached. The replication limit per (S,G) entry on an IOM is
currently 127.
Table 39-843 ReservedRouteTargetMismatch

releases

ReservedRouteTargetMismatch Implicitly cleared: true
(6446)
Type: configurationAlarm (11) reservedRouteTargetChanged (2446)
Package: l3fwd
Raised on class: l3fwd.ServiceSite
Description: The alarm is raised when the 5620 SAM detects a pre-assigned route target on this VPRN has
been modified. The alarm information includes the source, i.e., import or export, and the conflict reserved
VPRN RT entry distinguished name.
Remedial action: A configuration error has occurred which should be corrected. This VPRN’s route target has
been modified from its pre-reserved value defined in the Reserved VPRN Route Target Table.
Table 39-844 ResiliencySapDeleted

releases
Name: ResiliencySapDeleted (688) Severity: major Unspecified

Type: resiliencyAlarm (58) Implicitly cleared: true
Package: resiliency Default probable cause:
Raised on class: resiliencySapDeleted (503)
resiliency.HsdpaResiliency
Description: The alarm is raised when a SAP that is used for resiliency is deleted.
Table 39-845 ResiliencyServiceSwitch

releases
Name: ResiliencyServiceSwitch Severity: major Unspecified

Type: resiliencyAlarm (58) Default probable cause:
Package: resiliency secondaryServiceSiteActive (504)
Raised on class:
Description: The alarm is raised when a secondary service becomes active.
Table 39-846 ResiliencySiteDeleted

releases
Name: ResiliencySiteDeleted Severity: major Unspecified

Type: resiliencyAlarm (58) Default probable cause:
Package: resiliency secondaryServiceSiteDeleted (505)
Raised on class:
Description: The alarm is raised when a secondary service site is deleted.
Table 39-847 restoreFailureAlarm

releases
Name: restoreFailureAlarm (535) Severity: major Unspecified

Type: softwareAlarm (19) Implicitly cleared: false
Raised on class: restoreFailureAlarm (404)
sw.SoftwareControlModule
Description: The alarm is raised when the software restore process on an NE fails.
Remedial action: The SW image on the NE may have been inadvertently corrupted. Download a new copy of
the SW image to the NE. If the problem persists contact Alcatel-Lucent support for assistance.
Table 39-848 RetimingBufferOverFlow

releases
Name: RetimingBufferOverFlow Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: bufferOverFlow
Description: The alarm is raised when an retiming buffer overflow occurs.
Table 39-849 RevertiveMisMatch

releases
Name: RevertiveMisMatch Severity: warning Unspecified

Type: pathAlarm (12) Default probable cause: RevertiveMisMatch
Raised on class:
mplstp.PathMep
Description: This alarm is generated when an MPLS-TP LSP revertive mode mismatch is detected on the
protection MEP. The revertive mode must match on the local node and the far-end node.
Remedial action: This alarm is generated when an MPLS-TP LSP revertive mode mismatch is detected on
the protection MEP. The revertive mode must match on the local node and the far-end node.
Table 39-850 RFSwitchFail (equipment)

releases
Name: RFSwitchFail (5425) Severity: variable Unspecified

Package: equipment Default probable cause: rFSwitchFail
equipment.Equipment
Description: The alarm is raised when a RF switch failure is detected.
Remedial action: The alarm is raised when RF switch failure is detected. Refer 9500 Node Maintenance
manual for remedial action information
Table 39-851 RFSwitchFail (mpr)

releases
Name: RFSwitchFail (5425) Severity: variable Unspecified

Package: mpr Default probable cause: rFSwitchFail
mpr.SubRackElements
Description: The alarm is raised when a RF switch failure is detected.
Remedial action: The alarm is raised when RF switch failure is detected. Refer 9500 Node Maintenance
manual for remedial action information
Table 39-852 RingAuditProblem

releases
Name: RingAuditProblem Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: invalidConfiguation
Package: ethring (2049)
Raised on class: ethring.Ring
Description: The alarm is raised when the Ring Audit has detected a problem.
Remedial action: A configuration error has been made which must be corrected. Please see the additional
test for more details.
Table 39-853 RipAuthenticationFailure

Name: RipAuthenticationFailure Severity: warning Unspecified

Type: authenticationAlarm (14) Default probable cause: authFailure
Package: rip (46)
Raised on class: rip.Interface
Description: The alarm is raised when a peer authentication failure occurs. The alarm information includes the
peer address.
Remedial action: Informational - please check that RIP neighbor is sending the RIPv2 packet with the
matching authentication key with this router.
Table 39-854 RipAuthenticationMismatch

releases
Name: RipAuthenticationMismatch Severity: warning Unspecified

Package: rip (45)
Raised on class: rip.Interface
Description: The alarm is raised when a peer authentication mismatch occurs. The alarm indicates the peer
address.
Remedial action: Informational - please check that RIP neighbor is sending the RIPv2 packet with the
matching authentication type with this router.
Table 39-855 RipExportLimitDropped

releases
Name: RipExportLimitDropped Severity: warning Unspecified

Package: rip (598)
Raised on class: rip.Site
Description: The alarm is raised when the total number of exported routes from the route table to this RIP
level drops below the configured export limit
Table 39-856 RipExportLimitReached

releases
Name: RipExportLimitReached Severity: warning Unspecified

Package: rip (599)
Description: The alarm is raised when the total number of routes for the level is equal to the configured limit
for exported routes
Remedial action: Informational - Additional routes would not be exported into RIP from the route table.
Table 39-857 RipExportLimitWarning

releases
Name: RipExportLimitWarning Severity: warning Unspecified

Package: rip (600)
Description: The alarm is raised when the number of exported routes for the RIP level equals the percentage
of the export limit configured in the Export Limit Log Percent parameter.
Remedial action: Informational - Additional routes will continue to be exported into RIP from the route table till
the export limit is reached.
Table 39-858 ripRouteMaxLimitReached

releases
Name: ripRouteMaxLimitReached Severity: warning Unspecified

Package: rip maxRouteReached (825)
Description: The alarm is raised when the number of RIP routes learned by an NE exceeds the maximum
specified in the RIP configuration of the NE.
Table 39-859 RootDirMaxFilesReached

releases
Name: RootDirMaxFilesReached Severity: variable Unspecified

Type: storageAlarm (25) Default probable cause:
Package: equipment rootDirMaxFilesReached (1437)
Raised on class:
equipment.FlashMemory
Description: The alarm is raised when the number of files in the root directory reaches the maximum.
Remedial action: This alarm has been raised due the fact that the number of files in the root directory of the
compact flash has gone beyond the pre-defined limit. To rectify this issue please remove unused files from the
root directory.
Table 39-860 RouterLimitExceedDueToMultiAdditions

major releases

RouterLimitExceedDueToMultiAdditions Implicitly cleared: true
(602)
Type: cpamLicensingAlarm (39) cpamRouterLimitExceedDueToMultiAdditions
Description: The alarm is raised when the 5650 CPAM cannot discover one or more routers because the
license capacity is reached.
Raising condition: (’License violation due to multiple routers addition’ EQUAL ’true’)
Clearing condition: (’License violation due to multiple routers addition’ EQUAL ’false’)
Remedial action: Informational - The number of router (Big/Small/Multicast/Third Party) licenses purchased
and available on the CPAM server is insufficient as compared to the number of big/small/multicast/third party
routers under management in the network. Please contact Alcatel-Lucent Sales to purchase additional
licenses.
Table 39-861 RouteTargetConflict

releases
Name: RouteTargetConflict Severity: warning Unspecified

(11) routeTargetConflictWithOtherService (2447)
Package: l3fwd
Raised on class:
l3fwd.ServiceSite
Description: The alarm is raised when the 5620 SAM detects a conflict between the configured route target on
VPRN and the Reserved VPRN Table. The alarm information includes the source, i.e., import or export, and
the conflict reserved VPRN RT entry distinguished name.
Remedial action: A configuration error has occurred which should be corrected. The configured VPRN route
target has a conflict with the Reserved VPRN Route Target Table. This route target has been been reserved by
another service.
Table 39-862 RouteTargetMisConfigured

releases
Name: RouteTargetMisConfigured Severity: warning Unspecified

Package: service routeTargetMisConfigured (2535)
Raised on class:
service.SvcResourceReservation
Description: This alarm is raised when the configured route targets associated with this Reserved Route
Target entry has been misconfigured; i.e. the route target RT1 or RT2 is not configured when they are needed
for associated VPRN service site creation. The affected route target’s relative distinguished name is included in
the alarm.
Remedial action: A configuration error has occurred which should be corrected. This Reserved VPRN Route
Target Table does not have all the configured route targets that are needed for the associated VPRN. This
alarm needs to be explicitly cleared.
Table 39-863 RPSAbnormalState

releases
Name: RPSAbnormalState (3934) Severity: variable Unspecified

Type: rpsAbnormalConditionAlarm Implicitly cleared: true
(114) Default probable cause: RPSProblem
Package: mpr (1517)
Description: The alarm is raised when abnormal state resulted due to force switch/lockout operation in RPS
mode.
Remedial action: This alarm is raised when forced-switch/lockout command in RPS mode which led to an
abnormal condition.
Table 39-864 RPSPathFail

releases
Name: RPSPathFail (8133) Severity: variable Unspecified

Raised on class: receiverProtectionFail (824)
Description: The alarm is raised when a receiver protection switchover fails.
Table 39-865 RTM_rtmMP3_3V

releases
Name: RTM_rtmMP3_3V (6191) Severity: major Unspecified

Package: femto Default probable cause: equipmentMalfunction
femto.SCATCARTM
Description: This Alarm is raised when failure happens to RTM 3.3V monitoring from the carrier.
Table 39-866 RTM_rtmPower12V

releases
Name: RTM_rtmPower12V Severity: major Unspecified
Type: equipmentAlarm (3) Default probable cause: equipmentMalfunction
Raised on class:
femto.SCATCARTM
Description: This Alarm is raised when failure happens to RTM 12V monitoring from the carrier.
Table 39-867 RTM_rtmPowerCurrent

releases
Name: RTM_rtmPowerCurrent Severity: major Unspecified

Package: femto equipmentMalfunction (698)
Raised on class:
femto.SCATCARTM
Description: This Alarm is raised when failure happens to RTM current monitoring from the carrier.
Table 39-868 RTM_rtmPowerPGD

releases
Name: RTM_rtmPowerPGD Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: equipmentMalfunction
Raised on class:
femto.SCATCARTM
Description: This Alarm is raised when failure happens to Power supply status,from the RTM point of view.
Table 39-869 RxFail

releases
Name: RxFail (687) Severity: variable Unspecified

Package: radioequipment Default probable cause: rxFail
Description: The alarm is raised when an MSS detects a receive failure.
Table 39-870 SapDHCPLeaseEntriesExceeded

releases

SapDHCPLeaseEntriesExceeded Implicitly cleared: false
(386)
Type: communicationsAlarm (4) sapDHCPLeaseEntriesExceeded (290)
Package: service
Raised on class:
Description: The alarm is raised when the number of DHCP lease-state entries on a SAP reaches the
configured maximum value. This value is defined by sapTlsDhcpLeasePopulate for a TLS VLAN service, and
by vRtrIfDHCPLeasePopulate for an IES or VPRN service.
Remedial action: The Number of DHCP lease-state entries (e.g. subscribers) on the affected interface has
crossed the leasePopulate threshold defined in the DHCP Relay configuration of that interface. Please review
the DHCP leasePopulate configuration and adjust the number of allowed leases to meet the network
requirements. Alternately, the DHCP leases can be spread out across extra interfaces.
Table 39-871 sapDHCPLseStatePopulateErr

releases

sapDHCPLseStatePopulateErr Implicitly cleared: false
(3908)
Type: processingErrorAlarm (81) sapDHCPLseStatePopulateError (1495)
Package: service
Raised on class:
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot update the DHCP Lease
State table upon reception of a DHCP ACK message.
Remedial action: The alarm is raised when an NE notifies the 5620 SAM that it cannot update the DHCP
Lease State table upon reception of a DHCP ACK message. Verify the local DHCP server configuration or the
DHCP relay configuration. Additionally, verify the length of the auto-generated subscriber identification.
Table 39-872 sapDHCPProxyServerError

releases

sapDHCPProxyServerError (387) Implicitly cleared: false
Package: service UnableProxyDHCPRequest (291)
Raised on class:
Description: The alarm is raised when the 5620 SAM is unable to proxy a DHCP request.
Remedial action: Please verify your DHCP relay configuration. The local proxy server will not become
operational without the emulated-server address being specified. Also ensure the Proxy server state is enabled
on this SAP.
Table 39-873 SapMismatch

releases
Name: SapMismatch (417) Severity: major Unspecified

Type: configurationAlarm Implicitly cleared: false
(11) Default probable cause: remoteSapMismatch
Package: srrp (310)
Raised on class:
srrp.Instance
Description: The alarm is raised when the SRRP SAPs on the local interface do not match the SRRP SAPs
on the remote interface.
Remedial action: Reconfigure the Service Access Interfaces for the Group Interface so that they connecting
to each other for the peer SRRPs.
Table 39-874 sapReceivedProtSrcMac

releases
Name: sapReceivedProtSrcMac Severity: minor Unspecified

Type: accessInterfaceAlarm (40) Default probable cause:
Package: l2fwd ProtectedSourceMacLearned (294)
Raised on class:
l2fwd.AccessInterfaceFib
Description: The alarm is raised when a restricted SAP receives a re-learn request for a protected MAC
address.
Table 39-875 SapStaticHostDynamicMacConflict

releases

SapStaticHostDynamicMacConflict Implicitly cleared: false
(313)
Type: configurationAlarm (11) LearnedDynamicMacAlreadyLearned (243)
Package: antispoof
Raised on class:
antispoof.AntiSpoofingStaticHosts
Description: The alarm is raised when an NE tries to learn a dynamic MAC address from an IP-only static
host.
Remedial action: Informational - The NE has detected an existing FIB entry with the same MAC address,
created for another static host. Clearing the FIB entries could fix it.
Table 39-876 SapTagMismatch

releases
Name: SapTagMismatch Severity: major Unspecified

Type: configurationAlarm Default probable cause: remoteSyncTagMismatch
(11) (311)
Package: srrp
Raised on class:
srrp.Instance
Description: The alarm is raised when the tag of a local SAP does not match the tag of a remote SAP.
Remedial action: Reconfigure the SAPs for the peer SRRP instances so that their tags match each other.
Table 39-877 SapVlanSubTypeConflict

releases
Name: SapVlanSubTypeConflict Severity: warning Unspecified

Package: vlan topologyMisconfigured (81)
Raised on class: vlan.Site
Description: The alarm is raised when a SAP resynchronization indicates that the VLAN subtype of the SAP is
different from the site subtype. The alarm information includes the ID of the associated port.
Remedial action: Ensure that the VLAN Subtype of the SAP matches the VLAN Subtype of the Site.
Table 39-878 SasAccountingAlarm

releases
Name: SasAccountingAlarm Severity: minor Unspecified

Type: oamAlarm (18) Default probable cause: noAccountingPolicy
Package: sas (506)
Raised on class: sas.TestSuite
Description: The alarm is raised when the 5620 SAM cannot find an SAA Accounting Policy.
Remedial action: A configuration error has been made which must be corrected. An SAA Accounting policy is
required but has not been configured - please perform the required configuration.
Table 39-879 SasPmBinAlarmLimitReached

releases

SasPmBinAlarmLimitReached Implicitly cleared: false
(5413)
Type: configurationAlarm (11) tooManyAlarmsRaisedByBinStats (2121)
Package: server
Raised on class:
server.SamServer
Description: The alarm is raised when PM Bin Statistics has exceeded the limit of alarms for an interval.
Remedial action: Informational - the maximum number of bin threshold alarms that can be raised in the reset
interval has been reached. After the Bin alarm reset interval has passed, alarms can be raised again for the
next interval until the number of alarms reaches the limit again.
Table 39-880 SasPmBinStatThresholdExceeded

releases

SasPmBinStatThresholdExceeded Implicitly cleared: false
(5412)
Type: misConfiguration (53) SasPmBinStatThresholdExceeded (2120)
Package: sas
Raised on class: sas.TestManager
Description: The alarm is raised if sas pm bin stats count exceeds threshold limit. This Alarm has to be
cleared Manually.
Remedial action: The alarm is raised if sas pm bin stats count exceeds Threshold Limit.This Alarm has to be
cleared Manually.
Table 39-881 SasResultCollectionThresholdExceeded

major releases

SasResultCollectionThresholdExceeded Implicitly cleared: false
(5158)
Type: misConfiguration (53) sasResultCollectionThresholdExceeded
Package: sas (2078)
Description: The alarm is raised if test result count exceeds maximum allowed Limit.
Remedial action: collection Rate Greater Than expected.
Table 39-882 SasResyncWorkerQueueOverflow

releases

SasResyncWorkerQueueOverflow Implicitly cleared: false
(8137)
Type: misConfiguration (53) tooManySasResyncTasks (2533)
Package: sas
Description: The alarm is raised when incoming OAM traps can not be handled because the number of tasks
that await processing on the SasResyncWorkerPool queue by the 5620 SAM surpasses the servers capacity
to process them. The trap tasks mainly include incoming test results and threshold crossing events.
Remedial action: Consider stopping some SNMP based tests or using accounting-file based tests instead.
The alarm has to be cleared manually.
Table 39-883 SasThresholdExceededAlarm

releases

SasThresholdExceededAlarm (272) Implicitly cleared: true
Type: oamAlarm (18) Default probable cause:
Package: sas networkDegradation (204)
Description: The alarm is raised when a rising or falling threshold is crossed by a jitter, latency, or loss value.
The alarm is raised only against a scheduled test. The alarm information includes the threshold type, the
threshold setting, and the current rising or falling value.
Table 39-884 SasTooManyTestsOnNodeAlarm

releases

SasTooManyTestsOnNodeAlarm Implicitly cleared: true
(287)
Type: oamAlarm (18) tooManyTestsDeployedOnNode (220)
Package: sas
Raised on class: sas.NeAgent
Description: The alarm is raised when an NE reaches 60 percent of the allowed number of created or
simultaneously executed OAM tests. An attempt to create or execute an NE schedulable test on an NE fails
when the number of tests reaches 95 percent of the NE capacity. The alarm information includes the following:
- the NE ID - the number of deployed tests on the NE - the allowed number of deployed tests on the NE
Remedial action: Informational - 5620 SAM is close to or at the maximum number of OAM tests it can
support.
Table 39-885 ScriptAlarm

releases
Name: ScriptAlarm (5131) Severity: variable Unspecified

Type: serverAlarm (94) Implicitly cleared: false
Package: script Default probable cause: ScriptAlarm
script.AbstractScript
Description: This alarm was raised from within a SAM user script when certain conditions were met, as
implemented by the script author. See the alarm’s ’Additional Text’ for any informative details the script author
may have supplied.
Remedial action: This is an alarm generated from within a SAM user script, and therefore the remedial action
will vary. See the alarm’s "Additional Text" for any remedial action the script author may have supplied.
Table 39-886 scriptBackupLost

releases
Name: scriptBackupLost (273) Severity: warning Unspecified

Package: subscrident Default probable cause: backupDown
subscrident.Policy
Description: The alarm is raised when the primary subscriber identification script URL is operationally up, but
a lower-priority script or URL is operationally down.
Raising condition: ((’isLocal’ EQUAL ’true’) AND (’Primary Script Operational State’ EQUAL ’Up’) AND
((’Secondary Script Operational State’ NOT EQUAL ’Up’) OR (’Tertiary Script Operational State’ NOT EQUAL
’Up’)))
Clearing condition: ((’isLocal’ EQUAL ’true’) AND ((’Primary Script Operational State’ NOT EQUAL ’Up’) OR
((’Secondary Script Operational State’ EQUAL ’Up’) AND (’Tertiary Script Operational State’ EQUAL ’Up’))))
Table 39-887 SdpBindingMisconfigured

releases

SdpBindingMisconfigured Implicitly cleared: true
(293)
Type: SdpBindingAlarm (30) returnSdpBindingTypeMismatch (224)
Package: svt
Raised on class:
svt.SdpBinding
Description: The alarm is raised when the return SDP binding type does not match the originating SDP
binding type, for example, when the return SDP binding is spoke and the originating SDP binding is mesh.
Remedial action: A configuration error has occurred which must be corrected. The configuration on the
endpoints of the SDP does not match causing the SDP to be down. Correct the configuration error and the
SDP will come up.
Table 39-888 sdpBindReceivedProtSrcMac

releases

sdpBindReceivedProtSrcMac Implicitly cleared: false
(3746)
Type: SdpBindingAlarm (30) ProtectedSourceMacLearned (294)
Package: l2fwd
Raised on class:
l2fwd.AbstractCircuitFib
Description: The alarm is raised when a restricted SDP receives a re-learn request for a protected MAC
address.
Table 39-889 SdpMldSnpgGrpDroppedLimitExceeded

releases

SdpMldSnpgGrpDroppedLimitExceeded Implicitly cleared: false
(738)
Type: SdpBindingAlarm (30) igmpSnpgGrpMaxNbrGrpsReached (292)
Package: vpls
Raised on class:
vpls.SdpBindingMldSnpgCfg
Description: The alarm is raised when an SDP binding drops an MLD group because the configurable
maximum number of MLD groups on the SDP binding is reached.
Remedial action: Increase the maximum number of MLD groups for the SDP binding.
Table 39-890 sdpPbbActvPwWithNonActvCtrlPwChg

releases

sdpPbbActvPwWithNonActvCtrlPwChg Implicitly cleared: true
(5416)
Type: processingErrorAlarm (81) sdpPbbActvPwWithNonActvCtrlPwChg (2123)
Package: svt
Description: The alarm is raised when last pseudo-wire (PW) goes standby or down and when first PW
becomes active on the Backbone Edge Bridge (BEB) where control PW is standby or down on that SDP.
Remedial action: sdpPbbActvPwWithNonActvCtrlPwChg event with sdpPbbActvPwWithNonActvCtrlPw set to

’false’ indicate clearing of sdpPbbActvPwWithNonActvCtrlPwChg with sdpPbbActvPwWithNonActvCtrlPw set
to ’true’.
Table 39-891 SecondaryBatteryFail (equipment)
releases
Name: SecondaryBatteryFail Severity: variable Unspecified

Type: equipmentAlarm (3) Default probable cause: secondaryBatteryFail
Raised on class:
equipment.Equipment
Description: The alarm is raised when a secondary battery failure is detected.
Remedial action: The battery on the CPM should be replaced or re-installed.
Table 39-892 SecondaryBatteryFail (mpr)

releases
Name: SecondaryBatteryFail Severity: variable Unspecified

Type: equipmentAlarm (3) Default probable cause: secondaryBatteryFail
Package: mpr (1412)
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when a secondary battery failure is detected.
Remedial action: The battery on the subrack element(MPT) should be replaced or re-installed.
Table 39-893 SectionTraceMismatch

releases
Name: SectionTraceMismatch Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: sectionTraceMismatch
Description: The alarm is raised when a trace mismatch is detected on a SONET section.
Table 39-894 SerialChannelLoopback

releases
Name: SerialChannelLoopback (807) Severity: warning Unspecified

Raised on class: serialChannelLoopback (573)
tdmequipment.SerialChannelSpecifics
Description: The alarm is raised when an NE reports that a serial channel has a loopback alarm condition.

Table 39-895 ServerDeclineStaticAddr
releases
Name: ServerDeclineStaticAddr Severity: warning Unspecified

Package: dhcp DhcpClientHasStaticIpAddress (1530)
Raised on class:
dhcp.AbstractDhcpServer
Description: The tmnxDhcpSvrDeclineStaticAddr notification is generated when a DHCP decline message is

received from a DHCP client that has a static IP address assigned.
Remedial action: DHCP client has a static IP address. Make sure that the DHCP client has a dynamic IP
address
Table 39-896 ServerHardware_dnsServerDown

releases
Name: ServerHardware_dnsServerDown Severity: major Unspecified

Type: processingErrorAlarm (81) Default probable cause: outOfService
Raised on class: femto.ServerHardware
Description: This fault is generated when the DNS server within FGW hardware is out of service.
Table 39-897 ServerHardware_sntpServerDown

releases
Name: ServerHardware_sntpServerDown Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: outOfService
Raised on class: femto.ServerHardware
Description: This fault is generated when the ToD server within FGW hardware is out of service
Table 39-898 ServerLeaseDefaultTimers

releases
Name: ServerLeaseDefaultTimers Severity: warning Unspecified

Package: dhcp LeaseTimerInconsistent (1129)
Raised on class:
Description: The alarm is raised when the system has reverted to default lease timer values for a particular
DHCP client because the configuration of the lease timers was inconsistent.
Remedial action: This warning is generated when configuration of the lease timers of a particular DHCP client
is inconsistent; the system has reverted to default lease timer values. The lease renew time T1 and lease
rebind time T2 have been reverted to the default value of 1/2 and 2/3 of the lease time. Please check the lease
timers configuration on the local DHCP server to ensure the timers are compatible.
Table 39-899 ServerMaxLeasesReached

releases

ServerMaxLeasesReached Implicitly cleared: false
(3316)
Type: configurationAlarm (11) DhcpSvrMaxLeasesReached (1155)
Package: netw
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the maximum number of leases allocated by local DHCP server is
reached.
Remedial action: Informational - this alarm indicates that the maximum number of leases allocated by a local
DHCP server was reached. The address ranges for existing address pools should be extended or a new
address pool should be configured for the local DHCP server.
Table 39-900 ServerMsgTooLong

releases
Name: ServerMsgTooLong (2938) Severity: warning Unspecified

Package: dhcp Default probable cause:
Raised on class: DhcpSvrMsgTooLong (1130)
Description: The alarm is raised when a DHCP message is generated but the message size exceeds either
the maximum DHCP message size, or the size provided by the client in the option maximum DHCP message
size.
Remedial action: Review the access network DHCP configuration to ensure all parties send DHCP packets
with appropriate message size.
Table 39-901 ServerUserDatabaseUnknown

releases

ServerUserDatabaseUnknown Implicitly cleared: false
(3952)
Type: configurationAlarm (11) CannotFindUserDatabase (1531)
Package: dhcp
Raised on class:
Description: The tmnxDhcpSvrUserDbUnknown notification is generated when the local DHCP server
instance drops a DHCP message because a local user database with the name specified for this server
instance could not be found.
Remedial action: Please specify a valid local user database for this server instance.
Table 39-902 ServiceMisConfigured

releases
Name: ServiceMisConfigured (8140) Severity: warning Unspecified
Raised on class: serviceMisConfigured (2536)
Description: This alarm is raised when the VPRN service associated with a route target reservation entry has
been modified, i.e., the service name is changed, or the service is deleted, or there is duplicate VPRN service
with the same service and customer name detected. The associated service manager ID is attached with the
alarm.
Remedial action: A configuration error has occurred which should be corrected. The VPRN service
associated with this Route Target Reservation entry has been modified, or there is duplicate VPRN service with
the same service name detected.
Table 39-903 SflowCpEntrySampling

releases

SflowCpEntrySampling Implicitly cleared: true
(8142)
Type: communicationsAlarm SflowCpSamplingInterruptedorStarted (2538)
(4)
Package: sflow
Raised on class:
sflow.Receiver
Description: The alarm is raised when the sampling of an sFlow counter poller is interrupted or started.
Remedial action: Counter sampling may not be available. Make sure counter poller is reachable from NE and
no counter poller sequence reset happened.
Table 39-904 SflowPacketTransmisionFailure

releases

SflowPacketTransmisionFailure Implicitly cleared: true
(8143)
Type: communicationsAlarm (4) SflowPacketTxFailure (2539)
Package: sflow
Raised on class: sflow.Receiver
Description: The alarm is raised when an sFlow packet fails to transmit from an active sFlow receiver.
Remedial action: Packet transmission failed.Flow data may be lost. Please check the Receiver configurations
and make sure it is up and running.
Table 39-905 SGLimitExceeded

releases

SGLimitExceeded (456) Implicitly cleared: false
Type: resourceAlarm Default probable cause:
(28) pimSnpgSGGroupMaxSupportedLimitExceeded (350)
Package: equipment
Raised on class:
equipment.Card
Description: The alarm is raised when the number of PIM snooping source group records on a card exceeds
the maximum.
Remedial action: Informational - The alarm is raised when the number of PIM snooping source group records
on a card exceeds the maximum. To rectify this issue please increase the max number of groups for the pim
snooping associated with the card. The maximum number allowed is 16,000 (S,G) entries.
Table 39-906 ShamLinkDbDescriptAuthFailure

releases

ShamLinkDbDescriptAuthFailure (663) Implicitly cleared: false
Raised on class: ospf.ShamLink Applicable probable causes:
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a dbDescript packet on a sham link from an NE whose
authentication key or authentication type conflicts with the local NE authentication key or authentication type.
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a sham
link from the network whose authentication key or authentication type conflicts with the local NE’s
configuration.
Table 39-907 ShamLinkDbDescriptConfig

releases
Name: ShamLinkDbDescriptConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a dbDescript packet on a sham link from an NE whose
configuration parameters conflict with the local NE configuration parameters.
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a sham
link from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-908 ShamLinkHelloAuthFailure

releases
Name: ShamLinkHelloAuthFailure Severity: warning Unspecified

Package: ospf (45)
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a hello packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a hello packet has been received on a sham link
from the network whose authentication key or authentication type conflicts with the local NE’s configuration.
Table 39-909 ShamLinkHelloConfig

Name: ShamLinkHelloConfig (667) Severity: warning Unspecified

badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a hello packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a hello packet has been received on a sham link
from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-910 ShamLinkLsAckAuthFailure

releases
Name: ShamLinkLsAckAuthFailure Severity: warning Unspecified

authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsAck packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a sham link
Table 39-911 ShamLinkLsAckConfig

Name: ShamLinkLsAckConfig Severity: warning Unspecified

Type: configurationAlarm (11) Default probable cause: badVersion (35)
Package: ospf Applicable probable causes:
Raised on class: ospf.ShamLink badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsAck packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a sham link
Table 39-912 ShamLinkLsReqAuthFailure

releases
Name: ShamLinkLsReqAuthFailure Severity: warning Unspecified

authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsReq packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a sham link
Table 39-913 ShamLinkLsReqConfig

Name: ShamLinkLsReqConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsReq packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a sham link
Table 39-914 ShamLinkLsUpdateAuthFailure
releases

ShamLinkLsUpdateAuthFailure (672) Implicitly cleared: false
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsUpdate packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a sham link
Table 39-915 ShamLinkLsUpdateConfig

releases
Name: ShamLinkLsUpdateConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsUpdate packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a sham link
Table 39-916 ShamLinkNullPacketAuthFailure

releases

ShamLinkNullPacketAuthFailure (674) Implicitly cleared: false
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a null packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a null packet has been received on a sham link from
the network whose authentication key or authentication type conflicts with the local NE’s configuration.
Table 39-917 ShamLinkNullPacketConfig
releases
Name: ShamLinkNullPacketConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a null packet on a sham link from an NE whose
Remedial action: Informational - The alarm signifies that a null packet has been received on a sham link from
the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-918 ShamLinkRxBadPacket

Name: ShamLinkRxBadPacket (676) Severity: warning Unspecified

hello
dbDescript
lsReq
lsUpdate
lsAck
nullPacket
Description: The alarm is raised when an NE cannot parse an OSPF packet that it receives on a sham link.
Remedial action: Informational - an NE cannot parse an OSPF packet that it receives on a sham link.
Table 39-919 ShelfCPUAboveThreshold

releases

ShelfCPUAboveThreshold Implicitly cleared: false
(638)
Type: configurationAlarm (11) ShelfCPUUtilizationCrossedAboveThreshold (474)
Package: equipment
Raised on class:
equipment.HealthMonitoring
Description: The alarm is raised when shelf CPU usage exceeds the threshold value.
Remedial action: Informational - Please contact Alcatel-Lucent support for assistance.

Table 39-920 ShelfMemoryAboveThreshold
releases

ShelfMemoryAboveThreshold Implicitly cleared: false
(639)
Type: configurationAlarm (11) ShelfMemoryUtilizationCrossedAboveThreshold (475)
Package: equipment
Raised on class:
Description: The alarm is raised when shelf memory usage exceeds the threshold value.
Table 39-921 ShelfRxAboveThreshold

releases
Name: ShelfRxAboveThreshold Severity: major Unspecified

Package: equipment ShelfRxUtilizationCrossedAboveThreshold (476)
Raised on class:
Description: The alarm is raised when shelf Rx exceeds the threshold value.
Table 39-922 ShelfRxTxAboveThreshold

releases

ShelfRxTxAboveThreshold Implicitly cleared: false
(641)
Type: configurationAlarm (11) ShelfRxTxUtilizationCrossedAboveThreshold (477)
Package: equipment
Raised on class:
Description: The alarm is raised when shelf Tx exceeds the threshold value.
Table 39-923 ShelfTemperatureAboveThreshold

major releases

ShelfTemperatureAboveThreshold Implicitly cleared: false
(642)
Type: configurationAlarm (11) ShelfTemperatureUtilizationCrossedAboveThreshold
Raised on class:
Description: The alarm is raised when shelf temperature exceeds the threshold value.
Remedial action: The NE has detected internal temperatures which are abnormally high. This could be
caused by a failed fan unit or one or more dirty fan filters. Replacing the failed unit or filters should resolve the
problem. Alternately the environment that the NE is operating in may not be within specifications found in the
NE user guides.
Table 39-924 SignalLabelMismatch

releases
Name: SignalLabelMismatch Severity: variable Unspecified

Type: communicationsAlarm (4) Default probable cause: signalLabelMismatch
Raised on class:
equipment.Port
Description: The alarm is raised when a signal label mismatch is detected.
Table 39-925 SiteBgpAdVplsIdMisconfiguration

releases

SiteBgpAdVplsIdMisconfiguration Implicitly cleared: true
(739)
Type: configurationAlarm (11) bgpAdVplsIdInconsistent (439)
Package: vpls
Raised on class: vpls.BgpAdSite
Description: The alarm is raised when the configured VPLS ID on a BGP AD object differs from the VPLS ID
configured for the VPLS site.
Remedial action: The VPLS ID on a BGP AD object must match the VPLS ID configured for the VPLS site.
Table 39-926 SiteSyncDeploymentFailure

releases
Name: SiteSyncDeploymentFailure Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: siteSyncFailure
Package: sonet (441)
Description: The alarm is raised when the 5620 SAM tries to deploy a value for an object when a transaction
that involves the object is in progress from a different context.
Remedial action: Another transaction is updating the object, Please try after some time.
Table 39-927 SnmpTrapDropped

releases
Name: SnmpTrapDropped (179) Severity: warning Unspecified

Package: netw Default probable cause:
Raised on class: snmpDaemonOverloaded (141)
netw.NetworkElement
Description: The alarm is raised when the 5620 SAM receives a tmnxTrapDropped notification from an NE to
indicate that the NE has dropped a trap. As a result, the 5620 SAM resynchronizes the table associated with
the dropped trap.
Table 39-928 SoftwareBootFailure

releases
Name: SoftwareBootFailure Severity: major Unspecified

Type: softwareAlarm (19) Default probable cause: softwareBootProblem
Package: sw (91)
Raised on class:
sw.CardSoftware
Description: The alarm is raised when an NE fails to boot because of a software problem.
Remedial action: Please contact Alcatel-Lucent support for assistance.
Table 39-929 SoftwareDownloading

releases
Name: SoftwareDownloading Severity: warning Unspecified

Type: softwareAlarm (19) Default probable cause: softwareDownloading
Package: sw (93)
Raised on class:
sw.CardSoftware
Description: The alarm is raised when an NE begins to download software to a IOM or CPM card.
Table 39-930 SoftwareFailureAlarm

releases
Name: SoftwareFailureAlarm (149) Severity: critical Unspecified

Type: softwareAlarm (19) Implicitly cleared: true
Package: equipment Default probable cause: loadFailed
equipment.ReplaceableUnit
Description: The alarm is raised when the CPM fails to load the software from the specified location. The
alarm information includes the software location.
Remedial action: The CPM card did not find the SW in the expected location. Reinstall the SW using 5620
SAM.
Table 39-931 SoftwareInitialized

releases
Name: SoftwareInitialized (111) Severity: warning Unspecified
Package: sw Default probable cause: softwareInitialized
sw.CardSoftware
Description: The alarm is raised when software initialization on an IOM or CPM card completes.
Table 39-932 SoftwareInitializing

releases
Name: SoftwareInitializing (110) Severity: warning Unspecified

Package: sw Default probable cause: softwareInitializing
sw.CardSoftware
Description: The alarm is raised when software initialization on an IOM or CPM card begins.
Table 39-933 SoftwareUpgradeDownloadFailed

releases
Name: SoftwareUpgradeDownloadFailed Severity: warning Unspecified

Type: communicationsAlarm (4) Default probable cause: linkFailure
Package: lte (740)
Raised on class: lte.ENBEquipment
Description: This alarm is raised when the transfer of software scheduled by a Self Config policy fails due to
communication problem (communication timeout, cable disconnected). It is automatically cleared before
starting a new upgrade scheduled by a Self Config policy.
Remedial action: Check what happened during the File Transfer. Possible issues: Loss of NE Connectivity,
FTP daemon down, FTP credential issues
Table 39-934 SoftwareUpgradeOperationNotAttempted

releases

SoftwareUpgradeOperationNotAttempted Implicitly cleared: true
(1963)
Type: communicationsAlarm (4) bsCommunicationOffline (904)
Package: lte
Description: This alarm is raised when the BS Communication State goes ’offline’. While BS communication
state is ’offline’ none of the Software Upgrade Operations can be attempted
Clearing condition: ((’bsCommunicationState’ EQUAL ’omcManaged’))
Remedial action: Release NEM sessions

Table 39-935 SonetSDHLoopback
releases
Name: SonetSDHLoopback (407) Severity: warning Unspecified

Package: sonetequipment Default probable cause:
Raised on class: sonetSDHLoopback (303)
sonetequipment.SonetPortSpecifics
Description: The alarm is raised when a loopback test is provisioned on a SONET/SDH port.
Remedial action: Remove the loopback test from the SONET/SDH port.
Table 39-936 SONEventsProcessingDelayed

releases

SONEventsProcessingDelayed Implicitly cleared: true
(3874)
Type: integrityViolation (85) UnableToAcquireLock (949)
Package: lte
Description: This alarm is raised when a SON events cannot be handled (CM session is running). It is
automatically cleared.
Remedial action: Informational only - self-correcting condition.
Table 39-937 sourceSapChange

releases
Name: sourceSapChange (4813) Severity: warning Unspecified

Package: mirror Default probable cause:
Raised on class: tMirrorSourceSapChange (430)
mirror.SourceInterface
Description: The alarm is raised when a SAP that is associated with this mirror source is modified or deleted.
Table 39-938 SpbNbrMultAdjExists

Name: SpbNbrMultAdjExists (4394) Severity: major Unspecified

Package: spb Default probable cause: multiAdj (1573)
Raised on class: spb.Site
Description: The alarm is sent when IS-IS SPB instance detects a neighbor to which it already has a direct
adjacency on another interface.
Remedial action: Check number of links to neighbor to make sure there is only one SPB link.
Table 39-939 SpbRejectedAdjacency

releases
Name: SpbRejectedAdjacency Severity: minor Unspecified

Type: adjacencyAlarm (31) Default probable cause: interfaceMismatch
Package: spb (170)
Raised on class:
spb.AbstractInterface
Description: The alarm is raised when the 5620 SAM receives a vRtrIsisRejectedAdjacency trap, which
indicates that an adjacency cannot be established in response to a Hello PDU from an IS because of a lack of
resources.
Remedial action: Informational, might have exceeded the maximum number of adjacencies allowed.
Table 39-940 SSHLoginMaxAttempts

releases
Name: SSHLoginMaxAttempts Severity: warning Unspecified

Type: communicationsAlarm (4) Default probable cause: sshLoginMaxAttempts
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the number of CLI login failures due incorrect user name or password
using SSH session exceeds the configured value.
Table 39-941 StandbyVersionMismatch (equipment)

releases
Name: StandbyVersionMismatch Severity: variable Unspecified

Package: equipment standbyVersionMismatch (875)
Raised on class:
equipment.Equipment
Description: The alarm is raised when a standby device software version mismatch is detected.
Table 39-942 StandbyVersionMismatch (mpr)

releases
Name: StandbyVersionMismatch Severity: variable Unspecified

Package: mpr standbyVersionMismatch (875)
Raised on class:
mpr.SubRackElements
Description: The alarm is raised when a standby device software version mismatch is detected.
Remedial action: This alarm is raised when standby Software version on the MPT does not match the
software version on the core. Please refer 9500 Node Maintenance manual for remedial action information.
Table 39-943 StatsPollerProblem

releases
Name: StatsPollerProblem (5404) Severity: major Unspecified

Package: netw Default probable cause: resyncFailed
netw.NetworkElement
Description: The alarm is raised when the 5620 SAM is unable to poll a network stats object, for example,
because of intermittent or no IP connectivity to an NE, incorrect SNMP security parameters, or disabled SNMP
on the NE.
understand a) why the underlying transport network is unreliable or b) why the NE is too busy to respond to
5620 SAM or c) has SNMP been disabled on the NE. Once the issue has been resolved SAM will
automatically re-attempt.
Table 39-944 STMSystemMultiAuxAvailable

releases

STMSystemMultiAuxAvailable Implicitly cleared: false
(527)
Type: misConfiguration (53) multiAuxiliaryServersAvailable (399)
Package: sas
Raised on class:
sas.TestManager
Description: The alarm is raised when the 5620 SAM detects multiple available auxiliary servers for test
execution.
Remedial action: Reserved for future use
Table 39-945 STMSystemNotAvailable

releases

STMSystemNotAvailable (526) Implicitly cleared: false
Package: sas noAuxiliaryServersAvailable (256)
Raised on class:
sas.TestManager
Description: The alarm is raised when the 5620 SAM detects no available auxiliary servers for test execution.
Remedial action: Reserved for future use
Table 39-946 STMTestIdRangeMistmatch

releases
Name: STMTestIdRangeMistmatch Severity: major Unspecified

Type: oamAlarm (18)
Package: sas Default probable cause:
Raised on class: sas.TestManager testIdRangeMismatch (560)
Description: The alarm is raised when the 5620 SAM detects an STM test ID range mismatch between the
primary and standby main servers.
Remedial action: The configuration on the primary and standby servers must be aligned to resolve this
problem. Please contact Alcatel-Lucent support for assistance.
Table 39-947 STMTestsOutsideRange

releases
Name: STMTestsOutsideRange Severity: major Unspecified

Type: oamAlarm (18) Default probable cause: testsOutsideRange
Package: sas (561)
Raised on class:
sas.TestManager
Description: The alarm is raised when the 5620 SAM detects one or more STM Tests that have IDs outside
the specified range.
Remedial action: A configuration error has been made which must be corrected. The testId in a STM test
definition must be within the testId range specified within the nms-server.xml file
Table 39-948 subHostInconsistentAtmTdOvr

releases
Name: subHostInconsistentAtmTdOvr Severity: minor Unspecified

Package: ressubscr tmnxSubHostInconsistentAtmTdOvr (1424)
Raised on class:
Description: The alarm is raised when an AAA server (e.g. a RADIUS server) specifies an ATM Traffic
Descriptor override for a subscriber host while it has already specified another one for another host on the
same ATM Virtual Circuit.
Remedial action: Modify the AAA configuration so that all subscriber hosts sharing the same ATM Virtual
circuit use the same ATM Traffic Descriptor Override VSA. If different overrides are required, then the
subscribers must be in different ATM Virtual Circuits.
Table 39-949 SubnetBindingFailed

releases
Name: SubnetBindingFailed Severity: major Unspecified

(81) tmnxDhcpSvrSubnetBindingFailed (2043)
Package: dhcp
Raised on class:
dhcp.AddressPool
Description: This alarm is raised when a DHCP server instance cannot offer an IP address to a host, because
a subnet binding with its access node (service) is required but not available anymore in the pool.
Remedial action: The configuration of the Local DHCP Server IP Address Pool and/or the access node
(service) must be changed in order to make more subnets available.
Table 39-950 SubnetFailCtrlError
releases

SubnetFailCtrlError Implicitly cleared: false
(5156)
Type: configurationAlarm leaseWithInconsistentFailoverConfiguration (2075)
(11)
Package: dhcp
Raised on class:
dhcp.Subnet
Description: The alarm is raised each time a lease is created in a subnet with an inconsistent failover
configuration
Remedial action: A subnet lease has an inconsistent failover configuration, where the failover control type is
not identical for all subnet ranges while the pool subnet binding key is not equal to ’none’. Please restore
consistency of the failover control configuration for all subnet ranges in this subnet.
Table 39-951 SubnetMinFreeExc

releases
Name: SubnetMinFreeExc Severity: warning Unspecified

(11) actualFreeAddrBelowSubnetMin (391)
Package: dhcp
Raised on class:
dhcp.Subnet
Description: The alarm is raised when the actual number of free addresses in a subnet falls below the desired
minimum number specified in the subnet configuration
Remedial action: Please ensure that an adequate free address threshold is configured or create a new subnet
to meet the system requirements. This warning is raised on IPv4 DHCP servers only.
Table 39-952 SubnetMismatch

releases
Name: SubnetMismatch Severity: major Unspecified

Type: configurationAlarm Default probable cause: ipAddressListMismatch
(11) (308)
Package: srrp
Raised on class:
srrp.Instance
Description: The alarm is raised when the IP address list received from the master does not match the local
IP address list.
Remedial action: Check the IP address of the Subscriber interface and make sure the address for the peer
SRRP instances are in the same subnet.
Table 39-953 SubRackBatteryFail

Name: SubRackBatteryFail (5426) Severity: variable Unspecified
Package: mpr Default probable cause: batteryFail (457)
Raised on class: mpr.SubRack
Description: The alarm is raised when the battery fails or is missing on SubRack.
Remedial action: The battery on the subrack should be replaced or re-installed.
Table 39-954 SubRackSecondaryBatteryFail

releases

SubRackSecondaryBatteryFail Implicitly cleared: true
(5427)
Type: equipmentAlarm (3) secondaryBatteryFail (1412)
Package: mpr
Raised on class: mpr.SubRack
Description: The alarm is raised when a secondary battery failure is detected on SubRack.
Remedial action: The battery on the subrack should be replaced or re-installed.
Table 39-955 SubscrAuthPolicyMisconfigured (rtr)

releases

SubscrAuthPolicyMisconfigured Implicitly cleared: true
(271)
Type: ConfigurationAlarm (15) SubscrAuthPolicyNotFound (203)
Package: rtr
Raised on class:
rtr.VirtualInterfaceConfiguration
Description: The alarm is raised when a subscriber authentication policy for DHCP relay is misconfigured.
Remedial action: This alarm is raised on L2 and L3 access interfaces when the authentication policy specified
for DHCP Relay does not exist. Please make sure to select an authentication policy that exists or to configure
a new authentication policy with that name.
Table 39-956 SubscrAuthPolicyMisconfigured (vpls)

releases

SubscrAuthPolicyMisconfigured Implicitly cleared: true
(271)
Type: ConfigurationAlarm (15) SubscrAuthPolicyNotFound (203)
Package: vpls
Raised on class:
vpls.L2AccessItfDhcpRelayCfg
Description: The alarm is raised when a subscriber authentication policy for DHCP relay is misconfigured.
Remedial action: Check the local and global configuration for the subscriber authentication policy for DHCP
relay.
Table 39-957 SubscriberMisConfigured

releases
Name: SubscriberMisConfigured Severity: warning Unspecified

Package: service subscriberMisConfigured (2537)
Raised on class:
Description: This alarm is raised when the customer associated with a route target reservation entry has been
modified, i.e., the customer name can be changed, or the customer is deleted.
Remedial action: A configuration error has occurred which should be corrected. This customer associated
with the Reserved VPRN Route Target Table has been modified.
Table 39-958 SubSlaacOverride

releases
Name: SubSlaacOverride (5414) Severity: major Unspecified

Type: processingErrorAlarm (81) Implicitly cleared: true
Raised on class: subSlaacAddressOverlap (2122)
Description: The alarm is raised when an NE notifies the 5620 SAM that an IPv6 client requests a DHCPv6
non-temporary address (IA_NA) which overrides an existing SLAAC prefix that is assigned to a host. This
configuration causes the SLAAC host to be removed from the system.
Remedial action: Provide a non-overlapping IPv6 Address for the SLAAC host.
Table 39-959 SubSlaacSetupFailure

releases
Name: SubSlaacSetupFailure Severity: major Unspecified

Package: service SubSlaacSetupFailure (1494)
Raised on class:
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot create or update a SLAAC
host in the tmnxSubSlaacTable.
Remedial action: The alarm is raised when an NE notifies SAM that it cannot create or update a SLAAC host
in the tmnxSubSlaacTable. Verify the service configuration.
Table 39-960 SubVirtualSubnetHostsDeleted

releases
Name: SubVirtualSubnetHostsDeleted Severity: warning Unspecified

Package: ressubscr subVirtualSubnetHostsDeleted (2119)
Raised on class:
Description: This alarm is raised when the NE deletes all existing hosts for a subscriber associated with a
virtual subnet because a new default router and/or subnet were assigned. This is the consequence of a
configuration change on the server that assigns the subnet.
Remedial action: The hosts must transmit DHCP requests if they require a connection.
Table 39-961 svcArpHostPopulateErr

releases
Name: svcArpHostPopulateErr Severity: major Unspecified

Package: service svcArpHostPopulateError (1496)
Raised on class:
Description: The alarm is raised when an NE notifies the 5620 SAM that it cannot update the ARP Host table
upon reception of an ARP message.
Remedial action: The alarm is raised when an NE notifies the 5620 SAM that it cannot update the ARP Host
table upon reception of an ARP message. Verify the service configuration. Additionally, verify the length of the
auto-generated subscriber identification.
Table 39-962 svcFdbMimDestTableFull

releases
Name: svcFdbMimDestTableFull Severity: warning Unspecified

Package: netw resourceLimitReached (131)
Raised on class:
netw.NetworkElement
Description: The alarm is raised when the number of backbone MAC address indices on an NE reaches the
maximum allowed value. The alarm clears when the number of backbone MAC address indices on the NE falls
below 95 percent of the maximum allowed value.
Table 39-963 SWIncompatibility

releases
Name: SWIncompatibility (471) Severity: major Unspecified

Raised on class: elementNotCompatibleWithExistingStack (357)
Description: The alarm is raised when a slot is not compatible with the current stack. The slot subsequently
enters pass-through mode.
Remedial action: Login to switch console, and install same software load on primary and secondary slot and
synchronize them and reload switch.
Table 39-964 SychronizationLossOfSignal

releases
Name: SychronizationLossOfSignal Severity: major Unspecified

(799)
Default probable cause: lossOfSignal
Raised on class: equipment.Shelf
Description: The alarm is raised when an SLOS signal is detected on a PDH tributary.
Table 39-965 SyncCertFailed

releases
Name: SyncCertFailed (3912) Severity: major Unspecified

Package: sitesec Default probable cause:
Raised on class: SyncCertFailed (1498)
sitesec.SiteSystemSecurityPublicKey
Description: The alarm is raised when the synchronization of certificate files between the primary and
secondary CPMs is stopped due to errors.
Remedial action: The synchronization of certificate files between the primary and secondary CPMs is stopped
due to errors. Depending on the reason specified, corrective action should be taken
Table 39-966 synchroFailureAlarm

releases
Name: synchroFailureAlarm (534) Severity: major Unspecified

Type: softwareAlarm (19) Implicitly cleared: false
Raised on class: synchroFailureAlarm (403)
sw.SoftwareControlModule
Description: The alarm is raised when the flash card synchronization on an NE fails.
Remedial action: The SW image on the NE may have been inadvertently corrupted. Download a new copy of
the SW image to the NE. If the problem persists contact Alcatel-Lucent support for assistance.
Table 39-967 SynchronizationSignalFailure

releases

SynchronizationSignalFailure Implicitly cleared: true
(2944)
Type: communicationsAlarm (4) synchronizationSignalFailure (1134)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when a synchronization signal failure is detected.
Table 39-968 SystemModeChange

releases
Name: SystemModeChange (1923) Severity: major Unspecified

Package: optical Default probable cause:
Raised on class: systemModeChange (923)
optical.OpticalNeProperties
Description: The alarm is raised when an NE undergoes a system mode change, for example, from SONET
to SDH mode. The alarm information includes the Site ID, old system mode value and new system mode
value.
Remedial action: Informational.The alarm is raised when an NE undergoes a system mode change, for ex.
from SONET to SDH mode.
Table 39-969 TChipMemoryError

releases
Name: TChipMemoryError Severity: minor Unspecified

Package: equipment tchipMemoryParityError (2099)
Raised on class:
equipment.BaseCard
Description: This Alarm is raised when a T-chip experiences an occurrence of an internal memory parity error.
Remedial action: A fault has been detected in the hardware. If the problem persists please contact Alcatel-
Table 39-970 TemporaryCommunicationFailure

releases

TemporaryCommunicationFailure Implicitly cleared: true
(800)
Type: equipmentAlarm (3) temporaryCommunicationProblem (566)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when a temporary communication failure is detected.
Remedial action: 5620 SAM has temporarily lost contact with an NE. This may have been caused by the NE
restarting, the NE being taken off-line via operator intervention or by a loss of connectivity to the NE. If the NE
restarted then there will be an alarm indicating th
Table 39-971 TestFailedAlarm (atm)

releases
Name: TestFailedAlarm (3708) Severity: major Unspecified

Package: atm Default probable cause: networkDegradation
atm.PvcConnection
Description: The alarm is raised when an OAM test on the object fails.
Table 39-972 TestFailedAlarm (bgp)

releases
Name: TestFailedAlarm Severity: major Unspecified

Package: bgp (204)
Table 39-973 TestFailedAlarm (ethernetoam)

releases

Package: ethernetoam Default probable cause:
Table 39-974 TestFailedAlarm (ldp)

releases

Package: ldp (204)
Table 39-975 TestFailedAlarm (lte)

releases

Package: lte (204)
Raised on class:
lte.EPSPath
Description: The alarm is raised when TestFailedAlarm is raised for any test on this object.
Table 39-976 TestFailedAlarm (lteservice)

releases

Package: lteservice Default probable cause:
Table 39-977 TestFailedAlarm (mirror)

releases

Package: mirror (204)
Raised on class:
mirror.Mirror
Table 39-978 TestFailedAlarm (monpath)

releases

Package: monpath Default probable cause:
Table 39-979 TestFailedAlarm (mpls)

releases

Package: mpls (204)
Table 39-980 TestFailedAlarm (mplstp)

releases

Raised on class:
mplstp.TPLsp
Table 39-981 TestFailedAlarm (netw)

releases

Package: netw Default probable cause: networkDegradation
netw.NetworkElement
Table 39-982 TestFailedAlarm (pim)

releases

Package: pim (204)
Table 39-983 TestFailedAlarm (rtr)

releases

Package: rtr Default probable cause: networkDegradation
rtr.VirtualRouter
Table 39-984 TestFailedAlarm (service)

releases

Table 39-985 TestFailedAlarm (svt)

releases

Package: svt (204)
Table 39-986 TestFailedAlarm (vll)

releases

Package: vll (204)
Table 39-987 TestFailedAlarm (vpls)

releases
Package: vpls Default probable cause: networkDegradation
vpls.AbstractVpls
Table 39-988 TestFailedAlarm (vprn)

releases

Package: vprn (204)
Table 39-989 TestFailedAlarm2 (ethernetoam)

releases
Name: TestFailedAlarm2 (3739) Severity: major Unspecified

Package: ethernetoam Default probable cause: networkDegradation
ethernetoam.Mep
Table 39-990 TestFailedAlarm2 (lte)

releases
Name: TestFailedAlarm2 Severity: major Unspecified

Package: lte (204)
Table 39-991 TestFailedAlarm2 (mpls)

releases
Package: mpls Default probable cause:
mpls.P2MPDynamicLsp
Table 39-992 TestFailedAlarm2 (rtr)

releases

Table 39-993 TestFailedAlarm2 (service)

releases

Table 39-994 TestFailedAlarm2 (svt)

releases

Package: svt (204)
Raised on class:
svt.SdpBinding
Table 39-995 TestFailedAlarm3 (mpls)

releases

Package: mpls (204)
Raised on class:
mpls.LspPath
Table 39-996 TestFailedAlarm3 (service)

releases

Table 39-997 TestFailureAlarm

releases
Name: TestFailureAlarm Severity: major Unspecified

Package: sas (204)
Description: This alarm is raised when a test failure trap is received from the node.
Remedial action: Fix network connections issues.
Table 39-998 TestThresholdExceededAlarm (atm)

releases
Name: TestThresholdExceededAlarm Severity: major Unspecified

Package: atm networkDegradation (204)
Raised on class: atm.PvcConnection
Description: The alarm is raised when SasThresholdExceededAlarm is raised for any test on this object.
Table 39-999 TestThresholdExceededAlarm (bgp)
releases

Package: bgp networkDegradation (204)
Table 39-1000 TestThresholdExceededAlarm (ethernetoam)

releases

Package: ethernetoam networkDegradation (204)
Raised on class:
Table 39-1001 TestThresholdExceededAlarm (ldp)

releases

Package: ldp networkDegradation (204)
Table 39-1002 TestThresholdExceededAlarm (lte)

releases

Package: lte networkDegradation (204)
Table 39-1003 TestThresholdExceededAlarm (lteservice)
releases

Package: lteservice networkDegradation (204)
Raised on class:
Table 39-1004 TestThresholdExceededAlarm (mirror)

releases

Package: mirror networkDegradation (204)
Table 39-1005 TestThresholdExceededAlarm (monpath)

releases

Package: monpath networkDegradation (204)
Raised on class:
Table 39-1006 TestThresholdExceededAlarm (mpls)

releases

Package: mpls networkDegradation (204)
Table 39-1007 TestThresholdExceededAlarm (mplstp)

releases

Package: mplstp networkDegradation (204)
Raised on class: mplstp.TPLsp
Table 39-1008 TestThresholdExceededAlarm (netw)

releases

Package: netw networkDegradation (204)
Raised on class:
netw.NetworkElement
Table 39-1009 TestThresholdExceededAlarm (pim)

releases

Package: pim networkDegradation (204)
Table 39-1010 TestThresholdExceededAlarm (rtr)

releases

Package: rtr networkDegradation (204)
Raised on class: rtr.VirtualRouter
Description: The alarm is raised when an OAM test on the object reports that the test threshold has been
exceeded.
Table 39-1011 TestThresholdExceededAlarm (service)

releases

Package: service networkDegradation (204)
Raised on class:
Table 39-1012 TestThresholdExceededAlarm (svt)

releases

Package: svt networkDegradation (204)
Table 39-1013 TestThresholdExceededAlarm (vlan)

releases

Package: vlan networkDegradation (204)
Table 39-1014 TestThresholdExceededAlarm (vll)

releases

Type: oamAlarm (18)
Package: vll Default probable cause:
Raised on class: vll.Vll networkDegradation (204)
Table 39-1015 TestThresholdExceededAlarm (vpls)

releases

Package: vpls networkDegradation (204)
Table 39-1016 TestThresholdExceededAlarm (vprn)

releases

Package: vprn networkDegradation (204)
Table 39-1017 TestThresholdExceededAlarm2 (ethernetoam)

releases

TestThresholdExceededAlarm2 Implicitly cleared: true
(1918)
Type: oamAlarm (18) networkDegradation (204)
Raised on class: ethernetoam.Mep
exceeded.
Table 39-1018 TestThresholdExceededAlarm2 (lte)

releases
(1918)
Package: lte
Table 39-1019 TestThresholdExceededAlarm2 (mpls)

releases

(1918)
Package: mpls
Raised on class:
mpls.P2MPDynamicLsp
exceeded.
Table 39-1020 TestThresholdExceededAlarm2 (rtr)

releases

(1918)
Package: rtr
Raised on class:
Table 39-1021 TestThresholdExceededAlarm2 (service)

releases

(1918)
Package: service
Table 39-1022 TestThresholdExceededAlarm2 (svt)
releases

(1918)
Package: svt
Raised on class: svt.SdpBinding
exceeded.
Table 39-1023 TestThresholdExceededAlarm3 (mpls)

releases

(1919)
Package: mpls
Raised on class: mpls.LspPath
Description: The alarm is raised when an OAM test on the object reports that a test threshold is exceeded.
Table 39-1024 TestThresholdExceededAlarm3 (service)

releases

(1919)
Package: service
Raised on class:
Table 39-1025 ThresholdCrossingAlarmCard

releases
Name: ThresholdCrossingAlarmCard Severity: warning Unspecified

Type: thresholdCrossed (6) Default probable cause:
Package: equipment thresholdCrossed (12)
Raised on class: equipment.BaseCard
Description: The alarm is raised when a card value crosses a TCA threshold.
Remedial action: A condition set when a counter exceeds a user-selected high or low threshold. A TCA does
not generate an alarm but is available on demand through the CIT.Please refer 1830 PSS TroubleShooting
guide for more details.
Table 39-1026 ThresholdCrossingAlarmOduk

releases
Name: ThresholdCrossingAlarmOduk Severity: warning Unspecified

Package: oth thresholdCrossed (12)
Raised on class: oth.Oduk
Description: The alarm is raised when a ODUk value crosses a TCA threshold.
Table 39-1027 ThresholdCrossingAlarmOtuk

releases
Name: ThresholdCrossingAlarmOtuk Severity: warning Unspecified

Package: oth thresholdCrossed (12)
Raised on class: oth.Otuk
Description: The alarm is raised when a OTUk value crosses a TCA threshold.
Table 39-1028 ThresholdCrossingAlarmPort

releases
Name: ThresholdCrossingAlarmPort Severity: warning Unspecified

Package: equipment thresholdCrossed (12)
Raised on class:
Description: The alarm is raised when a port value crosses a TCA threshold.
Table 39-1029 ThresholdCrossingMDAResvCBSAlarm

releases

ThresholdCrossingMDAResvCBSAlarm
thresholdCrossed (12)
Package: equipment
Raised on class: equipment.DaughterCard
Description: The alarm is raised when the reserved CBS of an MDA crosses a threshold.
Remedial action: This alarm is raised when the traffic rates being received on an MDA are exceeding the
amount of buffer allocated for the MDA in the committed burst size configuration parameter. In all probability
the QoS being delivered by the MDA is degraded. Steps must be taken to shed traffic from the ports/links
associated with the MDA.
Table 39-1030 ThresholdCrossingPortResvCBSAlarm

releases

ThresholdCrossingPortResvCBSAlarm Implicitly cleared: true
(3627)
Type: thresholdCrossed (6) thresholdCrossed (12)
Package: equipment
Raised on class: equipment.PhysicalPort
Description: The alarm is raised when the reserved CBS of a port crosses a threshold.
Remedial action: This alarm is raised when the traffic rates being received on a port are exceeding the
amount of buffer allocated for the port in the committed burst size configuration parameter. In all probability the
QoS being delivered by the port is degraded. Steps must be taken to shed traffic from the port in question..
Table 39-1031 TimeRefDisqualified

releases
Name: TimeRefDisqualified Severity: info Unspecified

Type: communicationsAlarm Default probable cause: TimeRefDisqualified
(4) (2474)
Package: netw
Raised on class: netw.Time
Description: The alarm is raised when a system time input reference is disqualified.
Remedial action: Informational- no corrective action required.
Table 39-1032 TimeRefSelect

releases
Name: TimeRefSelect (8073) Severity: info Unspecified

Package: netw Default probable cause: TimeRefSelect
netw.TimeSource
Description: The alarm is raised when a system time input reference is selected.
Table 39-1033 TimingHoldover

releases
Name: TimingHoldover (734) Severity: major Unspecified

Package: sonet Default probable cause: timingHoldover
sonet.SiteSync
Description: The alarm is raised when the timing of an NE is in the Holdover state.
Raising condition: ((’Status’ EQUAL ’Master Holdover’))
Clearing condition: ((’Status’ NOT EQUAL ’Master Holdover’))
Table 39-1034 TimingReferenceOneNotQualified

releases

TimingReferenceOneNotQualified Implicitly cleared: true
(545)
Type: communicationsAlarm (4) timingReferenceNotQualified (418)
Package: sonet
Description: The alarm is raised when Timing Reference One on an NE is not in the Qualified state.
Raising condition: ((’Qualified For Use’ EQUAL ’Not Qualified’) AND (’Administrative State’ NOT EQUAL
’Down’))
Clearing condition: ((’Qualified For Use’ NOT EQUAL ’Not Qualified’) OR (’Administrative State’ EQUAL
’Down’))
Remedial action: Make sure that Timing Reference One is qualified.
Table 39-1035 TimingReferenceTwoNotQualified

releases

TimingReferenceTwoNotQualified Implicitly cleared: true
(546)
Type: communicationsAlarm (4) timingReferenceNotQualified (418)
Package: sonet
Description: The alarm is raised when Timing Reference Two on an NE is not in the Qualified state.
Raising condition: ((’Qualified For Use’ EQUAL ’Not Qualified’) AND (’Administrative State’ NOT EQUAL
’Down’))
Clearing condition: ((’Qualified For Use’ NOT EQUAL ’Not Qualified’) OR (’Administrative State’ EQUAL
’Down’))
Remedial action: Make sure that Timing Reference Two is qualified.
Table 39-1036 TMNLossofSignal

Name: TMNLossofSignal (1920) Severity: variable Unspecified
Package: mpr Default probable cause: tmnLOS (920)
Raised on class: mpr.MprTMN
Description: The alarm is raised when a Loss of Signal occurs on the TMN Interface.
Table 39-1037 tmnxMcSyncClientAlarm

major releases
Name: tmnxMcSyncClientAlarm (423) Severity: warning Unspecified

Raised on class: locallyDeletedEntryInMCSyncDatabase
multichassis.PeerSynchronizationProtocol (407)
Description: The alarm is raised when a MC synchronization database entry is deleted locally.
Table 39-1038 TooManyCpaaPerIsisArea

releases

TooManyCpaaPerIsisArea (385) Implicitly cleared: true
Package: topology tooManyCpaaPeIsisArea (930)
Description: The alarm is raised when there are too many 7701 CPAAs for an ISIS L1 area.
Remedial action: Check the configuration of CPAA and make sure there is at most one CPAA configured for
an ISIS area within an administrative domain.
Table 39-1039 TopologyIsisSystemError

releases
Name: TopologyIsisSystemError Severity: major Unspecified

Package: topology isisSystemNotAdvertisingTeRouterId (272)
Raised on class:
topology.AutonomousSystem
Description: The alarm is raised when an IS-IS topology system error is detected.
Remedial action: Alarm contains the systemId of the router which is not advertising ISIS TE RouterId. User
should either configure the ISIS TE routerId on the node or configure a routerId for that system in "ISIS System
ID Mapping" menu. Configuring the routerId in systemID mapping will not clear the alarm.
Table 39-1040 TopologyMisconfigured

releases
Name: TopologyMisconfigured Severity: critical Unspecified

Type: configurationAlarm (11) Default probable cause: topologyMisconfigured
Raised on class:
service.Service
Description: This alarm is raised when service sites are not fully connected.
Raising condition: (’topologyMisconfigured’ EQUAL ’true’)
Clearing condition: (’topologyMisconfigured’ EQUAL ’false’)
Remedial action: Connect the service sites with SDP Bindings, Vlan Uplinks, or PBB tunnels.
Table 39-1041 TPSAbnormalState

releases
Name: TPSAbnormalState (3935) Severity: variable Unspecified

Type: tpsAbnormalConditionAlarm Implicitly cleared: true
(115) Default probable cause: TPSProblem
Package: mpr (1518)
Description: The alarm is raised when abnormal state resulted due to force switch/lockout operation in TPS
mode.
Remedial action: This alarm is raised when forced-switch/lockout command in TPS mode which led to an
abnormal condition.
Table 39-1042 TrailDegrade

releases
Name: TrailDegrade (8101) Severity: major Unspecified

(4) Default probable cause: ProtectionDegrade
Raised on class: optical.Trail
Description: The alarm is raised when either Trail Path of Protected Trail is Operationally down.
by looking at the active alarms on APS Group’s work and protect TPs to understand why trail protection is
degraded.
Table 39-1043 TrailPathDown

releases
Name: TrailPathDown (5128) Severity: critical Unspecified

Raised on class:
optical.TrailPath
Description: The alarm is raised when the termination point(s) of the trail path are operationally down.
Table 39-1044 TrailSignalFail

releases
Name: TrailSignalFail (798) Severity: major Unspecified

Package: bundle Default probable cause: trailSignalFailure
bundle.Interface
Description: The alarm is raised when a a local or remote failure in an IMA group generates a Trail Signal Fail
message.
Table 39-1045 TransportServerFailure

releases
Name: TransportServerFailure Severity: critical Unspecified

Package: optical UnderlyingServerDown (2502)
Raised on class:
optical.TransportService
Description: The alarm is raised when any of the server trails in the service is operationally down
by looking at the active alarms on Server Trails to understand why transport service protection is unreliable.
Table 39-1046 TransportServiceDegrade

releases
Name: TransportServiceDegrade Severity: major Unspecified

Type: communicationsAlarm (4) Default probable cause: ProtectionDegrade
Raised on class:
Description: The alarm is raised when either work or protect path of Protected Transport Service is
operationally down
by looking at the active alarms on APS Group’s work and protect TPs to understand why transport service
protection is degraded.
Table 39-1047 TransportServiceDown

releases
Name: TransportServiceDown Severity: critical Unspecified

Package: optical Default probable cause:
Raised on class: OperationalStateDown (1963)
Description: The alarm is raised when: 1. The termination point(s) or VTS XC’s of the service path(s) are
operationally down. 2. There are missing VTS XCs in any of the service path(s) of this transport service.
Table 39-1048 TransportServicePathDown

releases
Name: TransportServicePathDown Severity: critical Unspecified

Package: optical OperationalStateDown (1963)
Raised on class:
optical.ServicePath
Description: The alarm is raised when the termination point(s) of the service path are operationally down.
Table 39-1049 TunnelOverbooked

releases
Name: TunnelOverbooked Severity: warning Unspecified

Type: resourceAlarm (28) Default probable cause: tunnelOverbooked
Package: svt (442)
Description: The alarm is raised when the allocated SDP binding bandwidth specified by
sdpBookedBandwidth exceeds the sdpMaxBookableBandwidth value.
Clearing condition: (’SDP Available Bandwidth’ NOT EQUAL ’0’)
Remedial action: Please set the maximum bookable bandwidth parameter to a more appropriate value or
offload traffic from the SDP in question to another SDP.
Table 39-1050 TunnelSelBlacklistFull

releases
Name: TunnelSelBlacklistFull Severity: major Unspecified

(81) tmnxL2tpTunnelSelBlacklistFull (1894)
Package: l2tp
Raised on class: l2tp.Site
Description: This alarm is raised when the number of tunnels and peers in the tunnel-selection-blacklist
reaches the limit configured on the L2TP Site, and is cleared when the limit is no longer reached.
Remedial action: Either increase Max List Length in Tunnel Selection Blacklist configuration or fix blacklisted
tunnels or peers.
Table 39-1051 TwampReflectorAlarm
releases

TwampReflectorAlarm (8138) Implicitly cleared: true
Package: sas missingTwlReflectorConfiguration (2534)
Raised on class:
sas.TWLSession
Description: This alarm is raised when a Twamp-Light Session is configured without a matching Reflector
Prefix.
Remedial action: This alarm is raised when a Twamp-Light Session is configured without a matching
Reflector Prefix.
Table 39-1052 TwampSrvInactivityTimeout

releases

TwampSrvInactivityTimeout Implicitly cleared: true
(3319)
Type: communicationsAlarm (4) TWAMPServerInactivityTimeout (1158)
Package: sas
Raised on class: sas.TwampSrv
Description: The alarm is raised when a TWAMP control connection is disconnected by the TWAMP server
due to the connection being inactive for a period exceeding the server’s inactivity timeout, which generates a
TWAMP Server InactivityTimeout notification.
Remedial action: Verify the value of the inactivity-timeout parameter and modify it according to the operational
needs.
Table 39-1053 TwampSrvMaxConnsExceeded

releases

TwampSrvMaxConnsExceeded Implicitly cleared: true
(3320)
Type: communicationsAlarm (4) TWAMPServerMaxConnsExceeded (1159)
Package: sas
Description: The alarm is raised when the maximum number of concurrent TWAMP control connections for
the server has been reached. [EFFECT] The TWAMP client cannot request test runs on the rejected
connection. [RECOVERY] Configure the system-level maximum number of concurrent TWAMP control
connections to a larger value, or disconnect any TWAMP control connection.’
Remedial action: Verify the value of the max-conn-server parameter and modify it according to the operational
needs.
Table 39-1054 TwampSrvMaxSessExceeded

releases

TwampSrvMaxSessExceeded Implicitly cleared: true
(3321)
Package: sas TWAMPServerMaxSessExceeded (1160)
Description: The alarm is raised when the maximum number of concurrent TWAMP sessions for the server
has been reached. [EFFECT] The TWAMP client cannot request test runs on the rejected session.
[RECOVERY] Configure the system-level maximum number of concurrent TWAMP sessions to a larger value,
or disconnect any TWAMP session.’
Remedial action: Verify the max-sess-server parameter and modify it according to the operational needs.
Table 39-1055 TwampSrvPfxMaxConnsExceeded

releases

TwampSrvPfxMaxConnsExceeded Implicitly cleared: true
(3322)
Type: communicationsAlarm (4) TWAMPServerPrefixxMaxConnsExceeded (1161)
Package: sas
Description: The alarm is raised when the maximum number of concurrent TWAMP control connections for a
TWAMP client prefix has been reached. [EFFECT] The TWAMP client cannot request test runs on the rejected
connection. [RECOVERY] Configure the prefix’s maximum number of concurrent TWAMP control connections
to a larger value, or disconnect a TWAMP control connection which uses the prefix.
Remedial action: Verify the max-conn-prefix parameter and modify it according to the operational needs.
Table 39-1056 TwampSrvPfxMaxSessExceeded

releases

TwampSrvPfxMaxSessExceeded Implicitly cleared: true
(3323)
Type: communicationsAlarm (4) TWAMPServerPrefixMaxSessExceeded (1162)
Package: sas
Description: The alarm is raised when the maximum number of concurrent TWAMP sessions for a TWAMP
client prefix has been reached. [EFFECT] The TWAMP client cannot request test runs on the rejected session.
[RECOVERY] Configure the prefix’s maximum number of concurrent TWAMP sessions to a larger value, or
disconnect a TWAMP session which uses the prefix.’
Remedial action: Verify the max sess-prefix parameter and modify it according to the operational needs.
Table 39-1057 TxFail

Name: TxFail (1175) Severity: variable Unspecified

Package: equipment Default probable cause: txFail (876)
Description: The alarm is raised when a transmission failure is detected.
Table 39-1058 TxFailure
Name: TxFailure (3931) Severity: major Unspecified

Package: equipment Default probable cause: txFail (876)
Description: The alarm is raised when a txFail (a fail of the Tx subfunction) defect raise.
Remedial action: The alarm is raised when a txFail (a fail of the Tx subfunction) defect raise.
Table 39-1059 TxRetransmit

Name: TxRetransmit (266) Severity: warning Unspecified

Raised on classes: Applicable probable causes:
ospf.ShamLink hello
ospf.VirtualLink dbDescript
lsReq
lsUpdate
lsAck
nullPacket
Description: The alarm is raised when an NE retransmits an OSPF packet on a non-virtual interface. The
alarm information includes the NE ID of the OSPF neighbor.
Remedial action: Informational - an NE retransmits an OSPF packet on a non-virtual interface. The alarm
information includes the NE ID of the OSPF neighbor.
Table 39-1060 TypeMismatch

releases
Name: TypeMismatch (96) Severity: critical Unspecified

Type: configurationAlarm Implicitly cleared: true
Package: service serviceSiteTypeMisconfigured (82)
Raised on class:
service.Service
Description: The alarm is raised when a VLAN type for a Site doesn’t match what has been configured on the
Service.
Raising condition: (’serviceTypeInconsistent’ EQUAL ’true’)
Clearing condition: (’serviceTypeInconsistent’ EQUAL ’false’)
Remedial action: Configure the VLAN subtype on the site same as the service VLAN subtype.
Table 39-1061 UDPPortAssignmentProblem

releases

UDPPortAssignmentProblem Implicitly cleared: true
(8026)
Type: processingErrorAlarm (81) configurationOrCustomizationError (902)
Package: lte
Raised on class:
lte.CallTraceSessionManager
Description: This alarm is raised when a NE’s TCE UDP port cannot be updated.
Remedial action: Ensure the NE is managed, reachable and that no configuration operation is in progress on
that NE and relaunch the operation.
Table 39-1062 UnavailableTime

releases
Name: UnavailableTime (644) Severity: variable Unspecified

(4) Default probable cause: unavailableTime
Raised on class:
equipment.Port
Description: The alarm is raised when a port experiences 10 consecutive SES.
Table 39-1063 UnconfiguredEquipmentPresent

releases

UnconfiguredEquipmentPresent Implicitly cleared: true
(645)
Type: equipmentAlarm (3) unconfiguredEquipmentPresent (481)
Package: equipment
Raised on class:
equipment.Equipment
Description: The alarm is raised when unconfigured equipment is detected.
Remedial action: A configuration error has occurred which must be corrected. The card slot has not been
configured
Table 39-1064 UndefinedSchedulerReference

releases

UndefinedSchedulerReference Implicitly cleared: true
(118)
Type: configurationAlarm (11) undefinedSchedulerReference (101)
Package: vs
Raised on class:
vs.ServiceTypeDefinition
Description: The alarm is raised when a queue specified in the access ingress or access egress policy of an
L2 access interface is not referenced by the scheduler policy for the interface.
Raising condition: ((’numberReferences’ > ’0’) AND (’numberOfDefinitions’ EQUAL ’0’))
Clearing condition: ((’numberReferences’ EQUAL ’0’) OR (’numberOfDefinitions’ > ’0’))

Remedial action: A queue specified in the access ingress/egress policy used by an L2 access interface is not
referencing a scheduler policy. Ensure all required queues created in the access ingress/egress policy is
referencing a scheduler.
Table 39-1065 UnderlyingResourceDegrade

releases

UnderlyingResourceDegrade Implicitly cleared: true
(1176)
Type: communicationsAlarm (4) underlyingResourceDegrade (877)
Package: equipment
Description: The alarm is raised when degradation of an underlying radio interface resource is detected.
Table 39-1066 UnderlyingResourceUnavailable

releases

UnderlyingResourceUnavailable Implicitly cleared: true
(1131)
Type: communicationsAlarm (4) underlyingResourceUnavailable (724)
Package: equipment
Description: The alarm is raised when an underlying resource is unavailable on an E1, radio, or Ethernet
interface.
Table 39-1067 UnderlyingResourceUnavailableService

major releases

UnderlyingResourceUnavailableService Implicitly cleared: true
(1177)
Type: communicationsAlarm (4) underlyingResourceUnavailableService (878)
Package: equipment
Description: The alarm is raised when an underlying E1, radio, or Ethernet interface resource service is
unavailable.
Table 39-1068 UnmanagedMplsTpSDPTunnelSite

releases

UnmanagedMplsTpSDPTunnelSite Implicitly cleared: true
(8147)
Type: configurationAlarm (11) unmanagedMplsTpSDPTunnelSite (2543)
Package: svt
Description: The alarm is raised when the MPLS-TP SDP Tunnel has configured with a non-managed site.
Remedial action: Investigation is required to resolve the following possible scenarios: The far-end site at the
MPLS-TP SDP Tunnel is non-managed Site. Please start to manage the NE with SAM or change the far-end
site id to a correct MPLS-TP site at MPLS-TP SDP Tunnel form.
Table 39-1069 UnresolvedVirtualPortConfiguration

releases

UnresolvedVirtualPortConfiguration Implicitly cleared: true
(4908)
Type: virtualPortAlarm (133) UnableToResolveNetworkConfiguration (1965)
Package: dctr
Raised on class:
dctr.AbstractVirtualPort
Description: The alarm is raised when VSD was not able to resolve network configuration for this virtual port.
The virtual port will not be assigned an ip address and there is no service associated with it.
Raising condition: ((’Active’ EQUAL ’true’) AND (’Resolved State’ EQUAL ’false’))
Clearing condition: ((’Active’ EQUAL ’false’) OR (’Resolved State’ EQUAL ’true’))
Remedial action: This alarm can be cleared when VSD is able to resolve the network configuration of the
virtual port. This notification reports that VSD cannot assign service objects to this virtual port. This could be
one or more of the domain, zone, subnet, user, or permission are missing, mismatched or not properly
configured in VSD. Please make sure the settings in VSD are correct for this virtual port.
Table 39-1070 UpgradeApplicationLockNotObtained

releases

UpgradeApplicationLockNotObtained Implicitly cleared: true
(1964)
Type: integrityViolation (85) UnableToAcquireLock (949)
Package: lte
Description: This alarm is raised when the Software Upgrade Application is unable to acquire lock to start the
operation. Retry the Software Upgrade Operation once the lock is released by the other application.
Remedial action: Retry the Software Management Operation once the lock is released by the other
application.
Table 39-1071 VersionMismatch (equipment)

releases
Name: VersionMismatch (646) Severity: variable Unspecified

Package: equipment Default probable cause: versionMismatch
equipment.Equipment
Description: The alarm is raised when an ODU software version mismatch is detected.
Table 39-1072 VersionMismatch (mpr)

releases
Name: VersionMismatch (646) Severity: variable Unspecified

Package: mpr Default probable cause: versionMismatch
mpr.SubRackElements
Description: The alarm is raised when an ODU software version mismatch is detected.
Remedial action: This alarm is raised when the software version on the MPT does not match the software
version on the core. Please refer 9500 Node Maintenance manual for remedial action information.
Table 39-1073 VirtualLinkDbDescriptAuthFailure

releases

VirtualLinkDbDescriptAuthFailure (61) Implicitly cleared: false
Raised on class: ospf.VirtualLink Applicable probable causes:
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a dbDescript packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a virtual
link from the network whose authentication key or authentication type conflicts with the local NE’s
configuration.
Table 39-1074 VirtualLinkDbDescriptConfig

releases
Name: VirtualLinkDbDescriptConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a dbDescript packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a dbDescript packet has been received on a virtual
link from the network whose configuration parameters conflict with the local NE’s configurations.
Table 39-1075 VirtualLinkHelloAuthFailure

releases
Name: VirtualLinkHelloAuthFailure Severity: warning Unspecified

Package: ospf (45)
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a hello packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a hello packet has been received on a virtual link
Table 39-1076 VirtualLinkHelloConfig

Name: VirtualLinkHelloConfig (54) Severity: warning Unspecified

badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a hello packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a hello packet has been received on a virtual link
Table 39-1077 VirtualLinkLsAckAuthFailure

releases
Name: VirtualLinkLsAckAuthFailure Severity: warning Unspecified

authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsAck packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a virtual link
Table 39-1078 VirtualLinkLsAckConfig

Name: VirtualLinkLsAckConfig (58) Severity: warning Unspecified

badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsAck packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a lsAck packet has been received on a virtual link
Table 39-1079 VirtualLinkLsReqAuthFailure

releases
Name: VirtualLinkLsReqAuthFailure Severity: warning Unspecified

authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives an lsReq packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a virtual link
Table 39-1080 VirtualLinkLsReqConfig

Name: VirtualLinkLsReqConfig (56) Severity: warning Unspecified

badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Remedial action: Informational - The alarm signifies that a lsReq packet has been received on a virtual link
Table 39-1081 VirtualLinkLsUpdateAuthFailure

releases

VirtualLinkLsUpdateAuthFailure (63) Implicitly cleared: false
authTypeMismatch
authFailure
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a virtual link
Table 39-1082 VirtualLinkLsUpdateConfig

releases
Name: VirtualLinkLsUpdateConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives an lsUpdate packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a lsUpdate packet has been received on a virtual link
Table 39-1083 VirtualLinkNullPacketAuthFailure

releases

VirtualLinkNullPacketAuthFailure (65)
Implicitly cleared: false
Type: authenticationAlarm (14)
Raised on class: ospf.VirtualLink
Applicable probable causes:
authTypeMismatch
authFailure
Description: The alarm is raised when an NE receives a null packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a null packet has been received on a virtual link
which authentication key or authentication type conflicts with the local NE’s configuration.
Table 39-1084 VirtualLinkNullPacketConfig

releases
Name: VirtualLinkNullPacketConfig Severity: warning Unspecified

Package: ospf (35)
badVersion
areaMismatch
unknownNbmaNbr
unknownVirtualNbr
netMaskMismatch
optionMismatch
mtuMismatch
noError
duplicateRouterId
ifAdminDown
ifPassive
Description: The alarm is raised when an NE receives a null packet on a virtual link from an NE whose
Remedial action: Informational - The alarm signifies that a null packet has been received on a virtual link
which configuration parameters conflict with the local NE’s configurations.
Table 39-1085 VirtualLinkRxBadPacket

Name: VirtualLinkRxBadPacket (66) Severity: warning Unspecified

hello
dbDescript
lsReq
lsUpdate
lsAck
nullPacket
Description: The alarm is raised when an NE cannot parse an OSPF packet that it receives on a virtual
interface.
Remedial action: Informational - an NE cannot parse an OSPF packet that it receives on a virtual interface.
Table 39-1086 VirtualMachineDown

releases

VirtualMachineDown Implicitly cleared: true
(4909)
Type: vmAlarm (134) VirtualMachineShutDownOrDeletedOrCrashed (1966)
Package: dctr
Raised on class:
dctr.VirtualMachine
Description: The alarm is raised when VM is shutdown.
Remedial action: This alarm can be cleared when virtual machine is up.
Table 39-1087 VirtualMachineSuspended

releases

VirtualMachineSuspended Implicitly cleared: true
(4911)
Type: vmAlarm (134) UserInitiatatedOrRequiredResourceIdBeingBlocked
Package: dctr (1968)
Raised on class:
dctr.VirtualMachine
Description: The alarm is raised when VM state changes to Paused on this object.
Raising condition: ((’Virtual Machine State’ EQUAL ’Paused’))
Clearing condition: ((’Virtual Machine State’ NOT EQUAL ’Paused’))
Remedial action: This alarm can be cleared when the virtual machine is resumed.
Table 39-1088 VirtualPortDown

releases
Name: VirtualPortDown (5434) Severity: info Unspecified

Type: virtualPortAlarm (133) Implicitly cleared: true
Package: dctr Default probable cause:
Raised on class: VirtualPortDownOrDeleted (2135)
dctr.AbstractVirtualPort
Description: The alarm is raised when VP is shutdown.
Remedial action: This alarm can be cleared when virtual port is up.
Table 39-1089 VirtualRouterDown

releases
Name: VirtualRouterDown (277) Severity: major Unspecified

Package: vrrp Default probable cause: virtualRouterDown
vrrp.VrrpVirtualRouter
Description: The alarm is raised when the aggregated Operational State of a VR is Down.
Raising condition: ((’Aggregated Operational State’ EQUAL ’Down’))

Clearing condition: ((’Aggregated Operational State’ NOT EQUAL ’Down’))
Remedial action: Check the configuration of both VRRP instances for the VRRP virtual router.
Table 39-1090 VirtualSwitchControllerDown

releases

VirtualSwitchControllerDown Implicitly cleared: true
(4912)
Type: virtualSwitchControllerAlarm ControllerNotOperationallyUp (1969)
(135)
Package: dctr
Raised on class:
dctr.VirtualSwitchController
Description: The alarm is raised when Virtual Switch Controller is not operationally up.
Raising condition: ((’Operational State’ EQUAL ’Down’))
Clearing condition: ((’Operational State’ EQUAL ’Up’))
Remedial action: This alarm can be cleared when virtual switch controller is operationally up.
Table 39-1091 VirtualSwitchDown

major releases
Name: VirtualSwitchDown Severity: major Unspecified

Type: virtualSwitchAlarm (136) Default probable cause:
Package: dctr ControllerDownOrPhysicalPortDownOrInterfaceDown
Description: The alarm is raised when Openflow session to the virtual switch is lost.
Remedial action: This alarm can be cleared when virtual switch is operationally up.
Table 39-1092 VirtualSwitchIpAddressDuplicated

releases

VirtualSwitchIpAddressDuplicated Implicitly cleared: false
(5435)
Type: virtualSwitchAlarm (136) VirtualSwitchIpAddressMisConfiguration (2136)
Package: dctr
Raised on class:
Description: The alarm is raised when more than one virtual switches in the same domain have the same ip
address. Virtual switches that are not belong or have not been associated to any domain are considered to be
in ’undefined’ domain.
Remedial action: This might have caused by a network configuration. Please check the status of the Admin
Domain and/or the Virtual Switch ip address and controller state. Please make sure the CPAA is managed,
Admin Domain is operational, then unmanage the node with duplicate virtual switch ip address and remanage
it again. This alarm must be cleared manually.
Table 39-1093 VirtVpnBGPPrefixConflict
releases

VirtVpnBGPPrefixConflict Implicitly cleared: true
(5431)
Type: virtualPortAlarm DuplicateVswNextHop_VmExistsOnTwoLocations (2132)
(133)
Package: dctr
Raised on class:
dctr.VirtualPort
Description: The alarm is raised when routes or service context could be stuck in compute or the network.
Remedial action: Routes or service context could be stuck in compute or the network. Reapply compute or
network policies to reset the network attachment.
Table 39-1094 VirtVpnBGPPrefixUnreachable

releases

VirtVpnBGPPrefixUnreachable Implicitly cleared: true
(5432)
Type: virtualPortAlarm (133) VportCannotBeReachedFromBgpVpn (2133)
Package: dctr
Raised on class: dctr.VirtualPort
Description: The alarm is raised when there is no route for the VPN regardless of routing on the virtual port.
Remedial action: There is no route for the VPN regardless of routing on the virtual port. This may be an
RR/VSC policy issue or internal VSD policy issue; e.g. no route assigned.
Table 39-1095 VirtVpnBGPPrefixWithdrawnNotReceived

major releases

VirtVpnBGPPrefixWithdrawnNotReceived Implicitly cleared: true
(5433)
Type: virtualPortAlarm (133) VportAddressMismatchWithBgpRoute
Package: dctr (2134)
Raised on class: dctr.VirtualPort
Description: The alarm is raised when there is no route on virtual port whereas BGP RIB has a route or routes
which do not match.
Remedial action: There is no route on virtual port whereas BGP RIB has a route or routes which do not
match. Check compute and Nuage virtualization policies.
Table 39-1096 VlanPathModified (mpr)

releases
Name: VlanPathModified Severity: minor Unspecified

Type: communicationsAlarm Default probable cause: PathChanged
(4) (1519)
Package: mpr
Raised on class: mpr.MprVll
Remedial action: Informational - If VLAN Path changed.alarmRemedialAction.mpr.
Table 39-1097 VlanPathModified (vlan)

releases
Name: VlanPathModified Severity: minor Unspecified

Type: communicationsAlarm Default probable cause: PathChanged
(4) (1519)
Package: vlan
Remedial action: Informational - if the VLAN Path Changed.
Table 39-1098 VlanSubTypeConflict

releases
Name: VlanSubTypeConflict Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: topologyMisconfigured
Package: vlan (81)
Description: The alarm is raised when more than one type of VLAN service has the same VLAN ID. The
alarm is raised against a service.
Raising condition: (’vlanSubTypeConflict’ EQUAL ’true’)
Clearing condition: (’vlanSubTypeConflict’ EQUAL ’false’)
Remedial action: Ensure that the VLAN Subtype of the Site matches the VLAN Subtype of the Service.
Table 39-1099 VLanUplinkDown

releases
Name: VLanUplinkDown (1146) Severity: major Unspecified

Type: VLanUplinkAlarm (89) Implicitly cleared: true
Package: service Default probable cause: VLanUplinkDown
service.VlanUplink
Description: The alarm is raised when a VLAN uplink is operationally down.
Raising condition: ((’Aggregation Operational State’ EQUAL ’Partially Down’) OR (’Aggregation Operational
State’ EQUAL ’Down’))
Clearing condition: ((’Aggregation Operational State’ NOT EQUAL ’Partially Down’) AND (’Aggregation
Operational State’ NOT EQUAL ’Down’))
Remedial action: Check the underlying physical link for the SAPs.
Table 39-1100 VLanUplinkNotCreated
releases
Name: VLanUplinkNotCreated Severity: major Unspecified

Type: VLanUplinkAlarm (89) Default probable cause:
Package: service VLanUplinkNotCreated (853)
Raised on class: service.Service
Description: The alarm is raised when an expected VLAN uplink does not exist.
Remedial action: Make sure the two participating ports which hold the uplink SAPs of the service are
physically connected and operationally up. And make sure a physical link is created and is operationally up
either by enabling LLDP or manually creating a physical link between those ports.If the physical link already
exists and operationally up, make sure the uplink SAPs has been created with matching encapsulation values,
in case the uplink SAPs has already been created with different encapsulation values, please delete those
uplink SAPs and create the uplink SAPs with same encapsulation values.
Table 39-1101 VoiceChannelLoopback

releases
Name: VoiceChannelLoopback (1148) Severity: warning Unspecified

Raised on class: voiceChannelLoopback (854)
tdmequipment.VoiceChannelSpecifics
Description: The alarm is raised when an NE reports that a voice channel has a loopback alarm condition.
Table 39-1102 vPortHostMatchFailure

releases
Name: vPortHostMatchFailure Severity: major Unspecified

Package: equipment tPortEgrVPortHostMatchFailure (1413)
Raised on class:
equipment.Port
Description: The alarm is raised when a host match lookup fails to resolve the egress virtual port.
Remedial action: This alarm is raised when the subscriber host with an intermediate destination ID that does
not match the host-match destination set under the V-port. Modify the intermediate destination ID of the
subscriber host to match the host-match defined in the v-port; Or modify the host-match destination ID to
match the intermediate destination ID of the subscriber host.
Table 39-1103 VprnTypeMismatched

releases
Name: VprnTypeMismatched Severity: major Unspecified

Type: configurationAlarm (11) Default probable cause: vprnTypeMismatched
Package: vprn (2545)
Description: The alarm is raised when the newly created VPRN Site has a VPRN type that is of a different
topology from existing VPRN Sites of the service, i.e, mesh vs hub/spoke, or vice versa.
Remedial action: A configuration error has occurred which should be corrected. The VPRN type of the
created site is of a different topology type from the existing VPRN Sites of the service, i.e., mesh and
hub/spoke sites shall not be mixed in the same service. The service shall be deleted and re-created with
consistent type.
Table 39-1104 VSiteServiceImpacted

releases
Name: VSiteServiceImpacted Severity: info Unspecified

Package: dctr VirtualPortReachability (2131)
Raised on class:
dctr.AbstractVirtualSite
Description: The alarm is raised on the VSite object when there is an alarm on VPort that affects service.
Remedial action: One or more virtual ports are down or have BGP reachability problem such as stuck or
unreachable prefix. This alarm can be cleared when the corresponding alarms on virtual ports are cleared.
Table 39-1105 VwmShelfCardRemoved

releases
Name: VwmShelfCardRemoved Severity: major Unspecified

Package: equipment VwmShelfCardRemoved (2438)
Raised on class:
equipment.VWMCardSlot
Description: The alarm is raised when a vwm card is removed.
Remedial action: Informational - a vwm shelf card has been removed from the NE
Table 39-1106 VwmShelfMismatch

releases
Name: VwmShelfMismatch Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: VwmShelfMismatch
Raised on class:
equipment.VwmShelf
Description: The alarm is raised when the configured vwm shelf id is different than the equipped vwm shelf.
Remedial action: This alarm is raised when the detected VWM shelf id does not match the provisioned id.
Please follow the below steps to clear this alarm: a. Check the id on the rotary dial on the VWM SHelf. b. Use
any of the following commands to clear the alarm. c. To change the VWM shelf id("config system vwm-shelf
<shelf-id> . d. To delete an existing shelf("config system no vwm-shelf <shelf-id>").
Table 39-1107 VwmShelfRemoved

releases
Name: VwmShelfRemoved Severity: major Unspecified

Type: equipmentAlarm (3) Default probable cause: VwmShelfRemoved
Raised on class:
equipment.VwmShelf
Description: The alarm is raised when a vwm shelf is removed.
Remedial action: Informational - a vwm shelf has been removed from the NE
Table 39-1108 WlanGwTuQosProblem

releases
Name: WlanGwTuQosProblem Severity: minor Unspecified

Type: resourceAlarm (28) Default probable cause: resourceFull
Package: wlangw (53)
Raised on class: wlangw.IsaMember
Description: The alarm is raised when a resource issue occurs while creating a WLAN Gateway tunnel QoS
infrastructure instance.
Remedial action: This may be a temporary phenomenon. If it persists, the QoS configuration or the scaling
may have to be modified to ensure enough resources are available for the UE QoS.
Table 39-1109 WMMPMFileNotificationMissing

releases

WMMPMFileNotificationMissing Implicitly cleared: false
(5387)
Type: communicationsAlarm (4) PMFileNotificationMissing (2105)
Package: ltemme
Raised on class:
ltemme.MmeInstance
Description: This alarm is raised when a PM File notification is expected from the node, but has not been
received after a certain period of time.
Remedial action: SAM has not received a PM File notification from the node, and may have missed retrieving
PM Files. Ensure that the node has PMEnabled and PMFileEvent values set to true. Ensure a PM job is active
with an intended schedule. If the problem persists please contact Alcatel-Lucent support for assistance. This
alarm notification can be turned off under the General tab in the MME Instance.
Table 39-1110 WMMUEOccupiedSlotsExceeded

releases

WMMUEOccupiedSlotsExceeded Implicitly cleared: false
(5050)
Package: ltemme
Raised on class: ltemme.MmeInstance
Description: The alarm is raised when the number of WMM UE Occupied Slots exceeds the threshold that
has been set by the operator.
Raising condition: ((’WMM UE Occupied Slots Threshold’ NOT EQUAL ’0L’) AND (’WMM UE Occupied Slots’
> ’WMM UE Occupied Slots Threshold’))
Table 39-1111 WppHostAuthenticationFailed

releases

WppHostAuthenticationFailed Implicitly cleared: false
(3916)
Type: processingErrorAlarm (81) portalWppHostAuthenticationFailure (1501)
Package: wpp
Raised on class: wpp.Portal
Description: The alarm is raised when a WPP host cannot be authenticated.
Remedial action: The recovery action will depend on the exact failure cause as given by the failureReason.
Table 39-1112 WppPortalUnreachable

releases
Name: WppPortalUnreachable Severity: minor Unspecified

Type: ProtocolAlarm (1) Default probable cause: protocolDown
Package: wpp (1)
Raised on class: wpp.Portal
Description: This alarm is raised when WPP protocol messages are sent out after a node is restarted but no
route to the web portal is available. This notification is sent every minute while the portal remains unreachable
up to a certain time. After that, all WPP messages to that portal are dropped.
Remedial action: Initially no recovery is required as it is expected that the WPP portal can be unreachable for
some time after a node restart. When the problem remains, the operator should check the routing table.
Table 39-1113 XPICCableLoss

releases
Name: XPICCableLoss (4851) Severity: variable Unspecified

Package: mwa DemodulatorXPICLossOfSignal (1928)
Raised on class:
mwa.PortTermination
Description: The alarm is raised when a MPT detects a XPIC plug-in cable loss
information.

MPR 9500 Unspecified Alarm List

Uploaded by

Copyright:

Available Formats

MPR 9500 Unspecified Alarm List

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MPR 9500 Unspecified Alarm List

Uploaded by

Copyright:

Available Formats

Alarm Reference > Alarm Reference

Table 39-1 AARadiusAcctPlcyFailure

Name: AARadiusAcctPlcyFailure (3948) Severity: major Unspecified

Table 39-2 AARadiusAcctServerStateChanged

Name: Severity: info Unspecified

Clearing condition: (’Operational State’ EQUAL ’In Service’)

Table 39-3 AarpStateChanged

Name: AarpStateChanged Severity: info Unspecified

Table 39-4 AAUrlFilterStateChanged

Name: AAUrlFilterStateChanged Severity: info Unspecified

Clearing condition: (’Operational State’ EQUAL ’Up’)

Table 39-5 ABSAlarm

Name: ABSAlarm (5187) Severity: major Unspecified

Table 39-6 AddressAttachFailed (rtr)

Name: AddressAttachFailed Severity: warning Unspecified

Name: AddressAttachFailed (8134) Severity: warning Unspecified

Table 39-8 AddressMisconfiguration

Name: Severity: major Unspecified

Table 39-9 AdvNotActivated

Name: AdvNotActivated Severity: warning Unspecified

Table 39-10 Ais

Name: Ais (736) Severity: variable Unspecified

Table 39-11 AisRx

Name: AisRx (1157) Severity: variable Unspecified

Table 39-12 AisTx

Name: AisTx (1158) Severity: variable Unspecified

Table 39-13 AllBgpPeerConnectionsDown

Name: Severity: major Unspecified

Table 39-14 AllTimingReferencesNotQualified

Name: Severity: major Unspecified

Table 39-15 apsCfgRaiseAlarm

Name: apsCfgRaiseAlarm (772) Severity: major Unspecified

Table 39-16 apsNoRspRaiseAlarm

Name: apsNoRspRaiseAlarm (773) Severity: major Unspecified

Table 39-17 apsPrvsnAlarm

Name: apsPrvsnAlarm (1196) Severity: major Unspecified

Name: apsPrvsnRaiseAlarm (774) Severity: major Unspecified

Table 39-19 AsymmetricalConfig (bundle)

Name: AsymmetricalConfig (295) Severity: major Unspecified

Raising condition: (’Asymmetrical Config Detected’ EQUAL ’true’)

Clearing condition: (’Asymmetrical Config Detected’ EQUAL ’false’)

Table 39-20 AtcaAlarmCard_e1InfraAlarm

Name: AtcaAlarmCard_e1InfraAlarm Severity: info Unspecified

Remedial action: TBD

Table 39-21 AtcaAlarmCard_e2InfraAlarm

Name: AtcaAlarmCard_e2InfraAlarm Severity: info Unspecified

Remedial action: TBD

Table 39-22 AtcaAlarmCard_e3InfraAlarm

Name: AtcaAlarmCard_e3InfraAlarm Severity: info Unspecified

Remedial action: TBD

Table 39-23 AtcaAlarmCard_e4InfraAlram

Name: AtcaAlarmCard_e4InfraAlram Severity: info Unspecified

Remedial action: TBD

Table 39-24 AtcaAlarmCard_pdu

Name: AtcaAlarmCard_pdu (5708) Severity: info Unspecified

Remedial action: TBD

Table 39-25 AtcaAlarmCard_pduBreakerPwr

Name: AtcaAlarmCard_pduBreakerPwr Severity: major Unspecified

Remedial action: TBD