1-2
Supporting the collaboration function
Collaboration is implemented by establishing collaboration entries to monitor the detection results of the
current test group. If the number of consecutive probe failures reaches a certain limit, NQA’s
collaboration with other modules is triggered. The implementation of collaboration is shown in
Figure
1-1
.
Figure 1-1
Implementation of collaboration
The collaboration here involves three parts: the application modules, the Track module, and the
detection modules.
z
The detection modules monitor the link status, network performance and so on, and inform the
Track module of the detection result.
z
Upon receiving the detection result, the Track module changes the status of the track entry
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.
z
The application modules then deal with the changes accordingly based on the status of the track
entry, 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:
1) Monitor reachability of the destination 192.168.0.88 through NQA.
2) If 192.168.0.88 is detected to be unreachable, NQA will inform the static routing module through
Track module.
3) The static routing module then can know that the static route is invalid.
For the detailed description of the Track module, refer to
Track Configuration
in the
High Availability
Volume
.
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
sent.
Содержание S7902E
Страница 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1 ...
Страница 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist ...
Страница 494: ...ii Displaying and Maintaining Tunneling Configuration 1 45 Troubleshooting Tunneling Configuration 1 45 ...
Страница 598: ...ii ...
Страница 1757: ...4 9 ...
Страница 1770: ...6 4 ...
Страница 2017: ...2 11 Figure 2 3 SFTP client interface ...
Страница 2062: ...i Table of Contents 1 URPF Configuration 1 1 URPF Overview 1 1 What is URPF 1 1 How URPF Works 1 1 Configuring URPF 1 2 ...
Страница 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002 ...
Страница 2442: ...2 4 Set the interval for sending Syslog or trap messages to 20 seconds Device mac address information interval 20 ...