Alcatel-Lucent 5620 - Page 179

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-137
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-83 Domain: vrrp
Alarm Attributes Additional information
Name: AdvNotActivated
Type: configurationAlarm (11)
Probable cause: advertisementNotActivated
(517)
Severity: Warning
Object Type (class): InstanceV6
Domain: vrrp
Implicitly cleared (self-clearing): Yes
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.
Name: AuthFailure
Type: authenticationAlarm (14)
Probable cause: authFailure (46)
Severity: Major
Object Type (class):
AbstractInstance
Domain: vrrp
Implicitly cleared (self-clearing): No
The alarm is raised when
authentication fails. The alarm
information includes the source IP
address.
Name: InstanceDown
Type: configurationAlarm (11)
Probable cause: instanceDown (216)
Severity: Major
Object Type (class):
AbstractInstance
Domain: vrrp
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects that a VRRP
instance is operationally down.
Name: IPListMismatch
Type: configurationAlarm (11)
Probable cause:
nonMatchingBackupAddressList (214)
Severity: Warning
Object Type (class):
AbstractInstance
Domain: vrrp
Implicitly cleared (self-clearing): Yes
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.
Name: mismatchBackupAddress
Type: configurationAlarm (11)
Probable cause: mismatchBackupAddress
(212)
Severity: Minor
Object Type (class): VRInstance
Domain: vrrp
Implicitly cleared (self-clearing): No
The alarm is raised when two VR
instances in a VR have different
backup addresses.
Name: mismatchSubnets
Type: configurationAlarm (11)
Probable cause: mismatchSubnets (213)
Severity: Major
Object Type (class): VRInstance
Domain: vrrp
Implicitly cleared (self-clearing): Yes
The alarm is raised when two VR
Instances in a VR have backup
addresses that are in different
subnets.
Name: mismatchVrrpTypes
Type: configurationAlarm (11)
Probable cause: mismatchVrrpTypes (211)
Severity: Minor
Object Type (class): VRInstance
Domain: vrrp
Implicitly cleared (self-clearing): Yes
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.
Name: MultipleOwners
Type: configurationAlarm (11)
Probable cause: multipleOwnersConfigured
(215)
Severity: Major
Object Type (class):
AbstractInstance
Domain: vrrp
Implicitly cleared (self-clearing): No
The alarm is raised when an owner
VR instance detects another instance
that advertises itself as an owner.
Name: VirtualRouterDown
Type: configurationAlarm (11)
Probable cause: virtualRouterDown (210)
Severity: Major
Object Type (class):
VrrpVirtualRouter
Domain: vrrp
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
aggregated Operational State of a VR
is Down.
Aug 2010
AAAD
8.0 R4