H3C Technologies H3C SecBlade LB Cards - Manual (Page 38)

30
If you configure the VF tracking function on an LVF to monitor its corresponding AVF on a specified router,
the LVF can take over the AVF immediately when the status of the track entry becomes negative, to ensure
uninterrupted network communications.
You can configure the VF tracking function when VRRP operates in either standard mode or load
balancing mode. However, the VF tracking function is effective only when VRRP operates in load
balancing mode.
By default, the weight of a VF is 255, and its lower limit of failure is 10.
If the weight of a VF owner is higher than or equal to the lower limit of failure, the priority of the VF owner
is always 255 and does not change with the weight value. Therefore, if an uplink fails, another VF takes
over the VF owner's work and becomes the AVF only when the weight of the VF owner decreases by a
properly specified value and becomes lower than the lower limit of failure. In other words, the weight of
the VF owner decreases by more than 245.
To configure VF tracking:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter the specified
interface view.
interface interface-type interface-number N/A
3. Configure VF tracking.
• Configure the VF tracking function to monitor a
specified track entry and specify the value by which
the weight decreases:
vrrp ipv6 vrid virtual-router-id weight track
track-entry-number [ reduced weight-reduced ]
• Configure the VF tracking function to monitor an
AVF on a specified router:
vrrp ipv6 vrid virtual-router-id track
track-entry-number forwarder-switchover
member-ip ipv6-address
Use either approach.
The VF tracking
function is not
configured by default.
Configuring VRRP packet attributes
Configuration prerequisites
Before you configure the relevant attributes of VRRP packets, create a VRRP group and configure a virtual
IPv6 address.
Configuration guidelines
• You might configure different authentication modes and authentication keys for the VRRP groups on
an interface. However, the members of the same VRRP group must use the same authentication
mode and authentication key.
• Excessive traffic might cause a backup to trigger a change of its status because the backup does not
receive any VRRP advertisements for a specified period of time. To solve this problem, prolong the
time interval to send VRRP advertisements.
• Configuring different intervals for sending VRRP advertisements on the routers in a VRRP group
might cause a backup to trigger a change of its status because the backup does not receive any
VRRP advertisements for a specified period of time. To solve this problem, configure the same
interval for sending VRRP advertisements on each router in the VRRP group.