collaboration with other modules is triggered. The implementation of collaboration is shown in
Figure 1-1 Implementation of collaboration
The collaboration here involves three parts: the application modules, the Track module, and the
The detection modules monitor the link status, network performance and so on, and inform the
Track module of the detection result.
Upon receiving the detection result, the Track module changes the status of the Track object
accordingly and informs the application modules. The Track module works between the application
modules and the detection modules and is mainly used to obscure the difference of various
detection modules to provide a unified interface for application modules.
The application modules then deal with the changes accordingly based on the status of the Track
object, and thus collaboration is implemented.
Take static routing as an example. You have configured a static route with the next hop 192.168.0.88. If
192.168.0.88 is reachable, the static route is valid; if 192.168.0.88 is unreachable, the static route is
invalid. With the collaboration between NQA, Track module and application modules, real time
monitoring of reachability of the static route can be implemented:
Monitor reachability of the destination 192.168.0.88 through NQA.
If 192.168.0.88 is detected to be unreachable, NQA will inform the static routing module through
The static routing module then can know that the static route is invalid.
At present, VRRP is not supported.
For the detailed description of the Track module, see Track Configuration in the High Availability
Supporting delivery of traps
You can set whether to send traps to the network management server when an NQA test is performed.
When a probe fails or a test is completed, the network management server can be notified, and the
network administrator can know the network running status and performance in time through the traps