1-4z For the configuration of Track-Static Routing collaboration, the specified static route can be anexistent or nonexistent one. For an existent static route, the static route and the specified Trackobject are associated directly; for a nonexistent static route, the system creates the static route andthen 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 thetrack 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 therecursive route instead of that of the static route; otherwise, a valid route may be consideredinvalid.z For details of static route configuration, refer to Static Routing Configuration in the IP RoutingVolume.Displaying and Maintaining Track Object(s)To do… Use the command… RemarksDisplay information about thespecified Track object or allTrack objectsdisplay track{ track-entry-number | all } Available in any viewTrack Configuration ExamplesStatic Routing-Track-NQA Collaboration Configuration ExampleNetwork requirementsz 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 monitoringof the validity of the static route to Switch C.Figure 1-2 Network diagram for Static Routing-Track-NQA collaboration configurationVlan-int210.1.1.1/24Vlan-int210.1.1.2/24Vlan-int310.2.1.1/24Switch CVlan-int310.2.1.2/24Switch BSwitch A
