Configuring Track-Static Routing Collaboration - 3Com MSR 50 Series Configuration Manual

n
Configuring Track-Static
Routing Collaboration
n
Configuring Collaboration Between the Track Module and Application Modules
To do...
Specify a Track object to be
monitored by VRRP
Do not perform Track object monitoring on the IP address owner.
■
When the status of the monitored Track object turns from negative to positive,
■
the corresponding router restores its priority automatically.
Refer to "VRRP Configuration" on page
■
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.
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.
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...
Enter system view system-view
Configure the ip route-static dest-address { mask | mask-length }
Track-Static Routing { gateway-address | vpn-instance
collaboration, so as d-vpn-instance-name gateway-address } track
to check the track-entry-number
reachability of the
ip route-static vpn-instance
next hop of the
s-vpn-instance-name&<1-6> dest-address { mask |
static route
mask-length } { gateway-address track
track-entry-number [ public ] | vpn-instance
d-vpn-instance-name gateway-address track
track-entry-number }
For the configuration of Track-Static Routing collaboration, the specified static
■
route can be an existent or nonexistent one. For an existent static route, the
static route and the specified Track object are associated directly; for a
nonexistent static route, the system creates the static route and then associates
it with the specified Track object.
The Track object to be associated with the static route can be a nonexistent
■
one. After you use the track command to create the Track object, the
association takes effect
If the Track module detects the next hop reachability of the static route in a
■
private network through NQA, the VPN instance number of the next hop of the
static route must be consistent with that configured for the NQA test group.
Otherwise, the reachability detection cannot function properly.
Use the command...
vrrp vrid virtual-router-id
track track-entry-number
[ reduced priority-reduced ]
1971.
2209
Remarks
Required
No Track object is specified
for VRRP by default.
Remarks
-
Required
Not configured
by default.