1-4
To do…
Use the command…
Remarks
Enter interface view
interface interface-type
interface-number
—
Create a VRRP group and
configure its virtual IP address
vrrp vrid virtual-router-id
virtual-ip
virtual-address
Required
No VRRP group is created by
default.
Specify a Track object to be
monitored by VRRP
vrrp vrid
virtual-router-id
track
track-entry-number
[
reduced
priority-reduced
|
switchover
]
Required
No Track object is specified for
VRRP by default
Specify a Track object to be
monitored by a virtual
forwarder
vrrp vrid
virtual-router-id
weight
track
track-entry-number
[
reduced
weight-reduced
]
Required
No Track object is specified for
a virtual forwarder by default.
z
Do not perform Track object monitoring on the IP address owner.
z
When the status of the monitored Track object turns from Negative to Positive, the corresponding
router restores its priority automatically.
z
The monitored Track object can be nonexistent, so that you can first specify the Track object to be
monitored using the
vrrp vrid track
command, and then create the Track object using the
track
command.
z
Refer to
VRRP Configuration
in the
System Volume
for details of VRRP.
Configuring Track-Static Routing Collaboration
You can check the validity of a static route in real time by establishing collaboration between Track and
static routing.
If you specify the next hop but not the egress interface when configuring a static route, you can
associate the static route with a Track object and thus check the validity of the static route according to
the status of the Track object.
z
If the status of the Track object is
Positive
, then the next hop of the static route is reachable, and
the configured static route is valid.
z
If the status of the Track object is
Negative
, then the next hop of the static route is unreachable,
and the configured static route is invalid.
Follow these steps to configure the Track-Static Routing collaboration:
To do…
Use the command…
Remarks
Enter system view
system-view
—
