H3C LS-3100-52P-OVS-H3 Operation Manual - page 1740
1-4
To do…
Use the command…
Remarks
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.
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
—
ip route-static dest-address { mask | mask-length}
{next-hop-address | vpn-instance d-vpn-instance-name
next-hop-address } track track-entry-number
[ preference preference-value ] [ tag tag-value ]
[ description description-text ]
Configure the
Track-Static Routing
collaboration, so as to
check the reachability
of the next hop of the
static route
ip route-static vpn-instance
s-vpn-instance-name&<1-6> dest-address { mask|
mask-length } { next-hop-address track
track-entry-number[ public ] | vpn-instance
d-vpn-instance-namenext-hop-address track
track-entry-number} [ preference preference-value ]
[ tag tag-value ] [ description description-text ]
Use either
command.
Not configured
by default.