Alcatel-Lucent 5620 Troubleshooting Manual page 136

3 — Troubleshooting using network alarms
Alarm
Name: VirtualNeighborDown
Type: VirtualNeighborDown (22)
Probable cause: VirtualNeighborDown (105)
(12 of 12)
Alarm
Name: DataMtReused
Type: dataMtReusedAlarm (37)
Probable cause: DataMtReused (258)
Name: GroupInSSMRange
Type: configurationAlarm (11)
Probable cause: STARGGroupInSSMRange
(147)
Name: InvalidJoinPrune
Type: communicationsAlarm (4)
Probable cause: InvalidJoinPruneReceived
(145)
Name: InvalidRegister
Type: communicationsAlarm (4)
Probable cause:
InvalidJoinRegisterReceived (146)
Name: invalidRPLoopbackInterfaceConfig
Type: configurationAlarm (11)
Probable cause: invalidRPLoopbackIfConfig
(201)
Name: McacPolicyDropped
Type: communicationsAlarm (4)
Probable cause: pimGroupOnSapDropped
(266)
Name: mismatchAnyCastRPTypes
Type: configurationAlarm (11)
Probable cause: mismatchAnyCastRPTypes
(202)
Name: missingStaticRPConfigurations
Type: configurationAlarm (11)
Probable cause:
missingStaticRPConfigurations (200)
(1 of 2)
3-94
Attributes
Severity: Warning
Object Type (class): ShamLink,
VirtualLink
Domain: ospf
Implicitly cleared (self-clearing): Yes
Table 3-48 Domain: pim
Attributes
Severity: Warning
Object Type (class): DataMtInterface
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Site
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Site
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Site
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
VirtualAnyCastRP
Domain: pim
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Interface
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): AnyCastRP
Domain: pim
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
VirtualAnyCastRP
Domain: pim
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when a neighbor
virtual link is operationally down.
Additional information
The alarm is raised when a data MDT
is reused.
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.
The alarm is raised when the RP
address in a Join Prune message is
not the RP for the group specified in
the message.
The alarm is raised when the RP
address in a Register message is not
the RP for the group specified in the
message.
The alarm is raised when an RP
loopback interface configuration is
invalid.
The alarm is raised when a PIM group
is dropped because a multicast CAC
policy is applied.
The alarm is raised when there is an
anycast RP type mismatch.
The alarm is raised when a static RP
configuration is missing.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4