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

93
Step Command Remarks
4. Associate Track with
VRRP VF.
• Associate a track entry with the VRRP
VF:
vrrp [ ipv6 ] vrid virtual-router-id
weight track track-entry-number
[ reduced weight-reduced ]
• Configure the LVF to monitor the AVF
status through the track entry:
vrrp [ ipv6 ] vrid virtual-router-id
track track-entry-number
forwarder-switchover member-ip
ip-address
Use at least one command.
By default, no track entry is
specified for a VF.
This command is configurable
when VRRP is operating in
standard mode or load balancing
mode. However, this function takes
effect only when VRRP is operating
in load balancing mode.
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 accessibility of a static route in real time, establish association between 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:
• You can associate a nonexistent track entry with a static route. The association takes effect only after
you use the track command to create the track entry.
• If the Track module detects the next hop accessibility of the static route in a private network through
NQA, the VPN instance name of the next hop of the static route must be consistent with that
configured for the NQA test group. Otherwise, accessibility detection cannot function properly.
• If a static route needs route recursion, the associated track entry must monitor the next hop of the
recursive route instead of that of the static route. Otherwise, a valid route may be considered invalid.
For more information about static route configuration, see Network Management Configuration
Guide.
To associate Track with static routing: