HP 3500YL - Manual (Page 378)

Virtual Router Redundancy Protocol (VRRP)
Event Log Messages
Event Log Messages
Message Meaning
Failure to send out pkt for vrid
< vrid-# >, vid < vid-# >
No VR with vrid < vrid-# > found on vid
< vid-# >
Pkt recd on a non-VRRP Vlan with vid
< vid-# >
Pkt recd with version number < ver-# >,
expected < ver-# >
Vrid < vrid-# > on Vid < vid-# > has taken
backup IP ctrl
Vrid < vrid-# > on Vid < vid-# > has taken
owner IP ctrl
Vrid < vrid-# > on Vid < vid-# > lost backup
IP ctrl
Vrid < vrid-# >, Vid < vid-# > IP addr is
duplicated on the network
Vrid < vrid-# >, Vid < vid-# > recd pkt from
a duplicate master
Vrid < vrid-# >, Vid < vid-# > recd pkt with
advt int mismatch
Vrid < vrid-# >, Vid < vid-# > recd pkt with
auth type mismatch
— Continued —
A VRRP packet could not be sent out for the indicated VR on
the specific VLAN due to any system-dependent problem. If
packets could not be sent out, the expected protocol
operation may be hampered.
Indicates a VRRP packet received for a VR that does not
exist on the VLAN. This can indicate asymmetric
configuration of VRs across VRRP routers.
A VRRP packet was received on a VLAN that does not have
any VRs. This could possibly be a result of misconfiguration
of VRs on VLANs.
A VRRP packet was received with a wrong version number.
The Owner of a VR is not available and a Backup has taken
Master control of the VR.
The Owner of a VR has taken Master control of the VR, either
following a reboot or a failback from a Backup serving as
Master.
The indicated VR has been preempted by either the Owner
or a higher-priority Master.
The virtual IP address owned by the indicated VR on the
indicated VLAN is duplicated on the network.
A VRRP packet was received from a duplicate master VR by
the indicated VR on the indicated VLAN.
The indicated VR on the indicated VLAN has received a
VRRP Master message carrying a different advertisement
interval than is configured on the receiving VR and has
dropped the packet.
Indicates the VR has received a packet with the
authentication type set to 1 or 2. These are generally valid
authentication types, but are not required by RFC 3768. Thus,
the software supports only an authentication type of 0
(zero), and VRRP packets with 1 or 2 for authentication type
are dropped. Refer to “Authentication Type” under
“Operating Notes” on page 6-46.
6-48