176
{ The AVF automatically restores its weight.
{ The failed master router becomes the master again.
{ The failed AVF becomes active again.
• You can associate a nonexistent track entry with a VRRP group or VF. The association takes
effect only after you create the track entry.
Associating Track with VRRP
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enter interface view.
interface
interface-type
interface-number
N/A
3. Associate Track with VRRP.
vrrp vrid
virtual-router-id
track
track-entry-number
{
forwarder-switchover
member-ip
ip-address |
priority
reduced
[ priority-reduced ] |
switchover
|
weight
reduced
[ weight-reduced ] }
By default, VRRP is not
associated with any track entries.
Associating Track with static routing
A static route is a manually configured route to route packets. For more information about static route
configuration, see Layer 3—IP Routing Configuration Guide.
A disadvantage of using static routes is that they cannot adapt to network topology changes. Link
failures or network topological changes can make the routes unreachable and cause communication
interruption.
To resolve 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.
To check the accessibility of a static route in real time, associate the Track module with the static
route.
If you specify the next hop but not the output interface when configuring a static route, you can
configure the static routing-Track-detection module collaboration. This collaboration enables you to
verify the accessibility of the static route based on the status of the track entry.
• If the track entry is in Positive state, the following conditions exist:
{ The next hop of the static route is reachable.
{ The configured static route is valid.
• If the track entry is in Negative state, the following conditions exist:
{ The next hop of the static route is not reachable.
{ The configured static route is invalid.
• If the track entry is in NotReady state, the following conditions exist:
{ The accessibility of the next hop of the static route is unknown.
{ The static route is valid.
When you associate Track with static routing, follow these restrictions and guidelines:
• You can associate a nonexistent track entry with a static route. The association takes effect only
after you create the track entry.
To Next Page
Loading...
Need help?
General
