The command is executed in VRID instance context
Forcing the backup VR to take ownership of the VR
instance
Failback is disabled on the owner VR; it can be executed only on the backup VR. Failback can occur only on a VR
on which
failover
or
failover with-monitoring
has been executed.
Syntax:
failback
This command takes effect only if the backup VR instance has a higher priority than the current owner, which is
normal VRRP router behavior. The command is executed in VRID instance context.
Configuring the Authentication Data Field
The
null-auth-compatiblity
command is used to allow inter-operation with other switches that expect
authentication data fields in VRRPv3 packets for IPv6. It is configured in the VR context. This command allows
compatibility with some Comware switches.
Syntax:
[no] null-auth-compatibility
When this command is enabled, authentication data is appended at the end of an IPv6 VRRP packet that is being
sent. The authentication data consists of 8 bytes of zeros.
Configuring the Authentication Data Field
switch(vlan-2-vrid-1)# null-auth-compatibility
Pinging the virtual IP of a backup router
Enabling the response to a ping request
The backup router can be enabled to respond to pings using the following command. For more information, see
Pinging the virtual IP of a backup router
on page 346.
Syntax:
[no] router vrrp virtual-ip-ping
Enables or disables the response to a ping request for the switch. When enabled, all VRs that are not owners and
are not explicitly disabled (see
virtual-ip-ping enabled
command) respond to ping requests sent to the
VIP when the backup VR is acting as master.
Default: Response to virtual IP ping is disabled.
Enabling the response to ping requests
router1# config
router1(config)# ip routing
router1Router1(config)# router vrrp
router1(config)# router vrrp virtual-ip-ping
322
Aruba 3810 / 5400R Multicast and Routing Guide for ArubaOS-
Switch 16.08
