Displaying And Maintaining Track Object(S); Track Configuration Examples; Vrrp-Track-Nqa Collaboration Configuration Example - HP 4800G Series Configuration Manual

Table of Contents

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 name 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.

If a static route needs route recursion, the associated Track object must monitor the next hop of the

recursive route instead of that of the static route; otherwise, a valid route may be considered

For details of static route configuration, refer to Static Routing Configuration in the IP Routing

Displaying and Maintaining Track Object(s)

Display information about the specified

Track object or all Track objects

Network requirements

Host A needs to access Host B on the Internet. The default gateway of Host A is 10.1.1.10/24.

Switch A and Switch B belong to VRRP group 1, whose virtual IP address is 10.1.1.10.

When Switch A works normally, packets from Host A to Host B are forwarded through Switch A.

When VRRP finds that there is a fault on the upper link of Switch A through NQA, packets from

Host A to Host B are forwarded through Switch B.

Use the command...

display track

{ track-entry-number | all }

Available in any view

Table of Contents