1-4
z
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.
z
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.
z
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
invalid.
z
For details of static route configuration, refer to
Static Routing Configuration
in the
IP Routing
Volume
.
Displaying and Maintaining Track Object(s)
To do…
Use the command…
Remarks
Display information about the
specified Track object or all
Track objects
display
track
{ track-entry-number | all }
Available in any view
Track Configuration Examples
Static Routing-Track-NQA Collaboration Configuration Example
Network requirements
z
The next hop of the static route from Switch A to Switch C is Switch B.
z
Configure Static Routing-Track-NQA collaboration on Switch A to implement real-time monitoring
of the validity of the static route to Switch C.
Figure 1-2
Network diagram for Static Routing-Track-NQA collaboration configuration
Vlan-int2
10.1.1.1/24
Vlan-int2
10.1.1.2/24
Vlan-int3
10.2.1.1/24
Switch C
Vlan-int3
10.2.1.2/24
Switch B
Switch A
Configuration procedure
1) Configure the IP address of each interface as shown in
Figure 1-2
.
2) Configure a static route on Switch A and associate it with the Track object.
