Alcatel-Lucent 5620 Troubleshooting Manual page 93

Alarm
Name: ThresholdCrossingAlarmDbl
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
(2 of 2)
Alarm
Name: GenericInterfaceLinkDown
Type: equipmentAlarm (3)
Probable cause: inoperableEquipment (8)
Alarm
Name: IGHMisconfigured
Type: ighAlarm (74)
Probable cause: IGHProtocolMismatch (590)
Alarm
Name: CModeRxQueryMismatch
Type: configurationAlarm (11)
Probable cause:
InvalidCompatibilityModeofQueryReceieved
(130)
Name: IgmpDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
(1 of 2)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Warning
Object Type (class): GenericObject
Domain: generic
Implicitly cleared (self-clearing): Yes
Table 3-20 Domain: genericne
Attributes
Severity: Major
Object Type (class):
GenericNeInterface
Domain: genericne
Implicitly cleared (self-clearing): Yes
Table 3-21 Domain: igh
Attributes
Severity: Major
Object Type (class):
InterfaceGroupHandler
Domain: igh
Implicitly cleared (self-clearing): Yes
Table 3-22 Domain: igmp
Attributes
Severity: Major
Object Type (class): Interface
Domain: igmp
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class): Site
Domain: igmp
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when a value
crosses a configured rising or falling
threshold. The alarm information
includes the current threshold value,
the default threshold value, and the
threshold name.
Additional information
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.
Additional information
The alarm is raised when the IGH is
administratively up but none of the
IGH protocols is operationally up.
Additional information
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.
The alarm is raised when an IGMP
site has an Operational State other
than Up, and the Administrative
State is Up.
3-51