R3166-R3206-HP High-End Firewalls High Availability Configuration Guide-6PW101

47
To do… Use the command… Remarks
Associate a track entry
with a virtual forwarder
vrrp vrid virtual-router-id
weight track
track-entry-number [ reduced
weight-reduced ]
Required
No track entry is specified for a virtual forwarder by
default.
This command is supported when VRRP works in
both the standard protocol mode and load
balancing mode. However, this function takes effect
only when VRRP works in the load balancing mode.
NOTE:
• Do not perform track entry monitoring on the IP address owner.
• When the status of the track entry changes from Negative to Positive or Invalid, the associated router o
r
VF restores its priority automatically.
• You can associate a nonexistent track entry with a VRRP group or VF. The association takes effect only
after you use the track command to create the track entry.
• For more information about VRRP configuration, see the chapter ”VRRP configuration.”
Associating track with static routing
A static route is a manually configured route. With a static route configured, packets to the specified
destination are forwarded through the path specified by the administrator.
The disadvantage of using static routes is that they cannot adapt to network topology changes. Faults or
topological changes in the network can make the routes unreachable, causing network breaks.
To prevent this problem, configure another route to back up the static route. When the static route is
reachable, packets are forwarded through the static route; when the static route is unreachable, packets
are forwarded through the backup route, avoiding network breaks and enhancing network reliability.
To check the reachability of a static route in real time, establish association between the track and the
static route.
If you specify the next hop but not the egress interface when configuring a static route, you can establish
collaborations among the static route, the track module, and detection modules. This enables you to
check the reachability of the static route according to the status of the track entry.
• The Positive state of the track entry shows that the next hop of the static route is reachable, and the
configured static route is valid.
• The Negative state of the track entry shows that the next hop of the static route is not reachable, and
the configured static route is invalid.
• The Invalid state of the track entry shows that the reachability of the next hop of the static route is
unknown, and the static route is valid.