8-3
To do…
Use the command…
Remarks
Create a track entry, associate it
with the specified NQA reaction
entry
track track-entry-number nqa
entry admin-name
operation-tag
reaction item-number
Required
No track entry is created by
default.
You can configure a track entry before creating an NQA test group and its reaction entry. In this case,
the status of the configured track entry is
Invalid
.
Configuring Collaboration Between the Track Module and the
Application Modules
Configuring Track-Static Routing Collaboration
A static route is a manually configured route. With a static route configured, packets to the specified
destination are forwarded through the path specified by the administrator.
The disadvantage of using static routes is that they cannot adapt to network topology changes. If a
fault or a topological change occurs in the network, the routes will be unreachable and the network
breaks.
To prevent this problem, configure another route to back up the static route. When the static route is
reachable, packets are forwarded through the static route; when the static route is unreachable,
packets are forwarded through the backup route, thus avoiding network break and enhancing network
reliability.
To check the reachability of a static route in real time, establish collaboration between track and static
routing.
If you specify the next hop but not the egress interface when configuring a static route, you can
establish collaborations among the static route, the track module, and detection modules, and thus
check the reachability of the static route according to the status of the track entry.
z
If the status of the track entry 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 entry 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
—
