F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices High Availability Configuration Guide-6PW100

70
• Monitor the master on a backup. If a fault occurs on the master, the backup working in switchover
mode will switch to the master immediately to maintain normal communication.
Follow these guidelines when you associate track with VRRP:
• VRRP tracking is not valid on an IP address owner. An IP address owner refers to a router when the
IP address of the virtual router is the IP address of an interface on the router in the VRRP group.
• 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,
see "Configuring VRRP."
To associate track with VRRP group:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Create a VRRP group and
configure its virtual IP
address.
vrrp vrid virtual-router-id virtual-ip
virtual-address
No VRRP group is created by
default.
4. Associate a track entry with a
VRRP group.
vrrp [ ipv6 ] vrid virtual-router-id
track track-entry-number [ reduced
priority-reduced | switchover ]
No track entry is specified for a
VRRP group by default.
Support for the ipv6 keyword
depends on the device model. For
more information, see High
Availability Command Reference.
124BAssociating 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 accessibility 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 accessibility of the static route by 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 that
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
that the configured static route is invalid.
• The Invalid state of the track entry shows that the accessibility of the next hop of the static route is
unknown, and that the static route is valid.
Follow these guidelines when you associate track with static routing: