51
Packet(s) arrived late: 0
# Display the history of DLSw tests.
[DeviceA] display nqa history admin test
NQA entry (admin admin, tag test) history record(s):
Index Response Status Time
1 19 Succeeded 2007-11-22 10:40:27.7
Configuring NQA collaboration example
Network requirements
As shown in Figure 18, configure a static route to Device C on Device A, with Device B as the next hop.
Associate the static route, track entry, and NQA test group to verify whether static route is active in real
time.
Figure 18 Network diagram for NQA collaboration configuration example
Vlan-int2
10.1.1.1/24
Vlan-int2
10.1.1.2/24
Vlan-int3
10.2.1.1/24
Device C
Vlan-int3
10.2.1.2/24
Device B
Device A
Configuration procedure
1. Assign each interface an IP address. (Omitted)
2. On Device A, configure a unicast static route and associate the static route with a track entry.
# Configure a static route, whose destination address is 10.2.1.1, and associate the static route with track
entry 1.
<DeviceA> system-view
[DeviceA] ip route-static 10.1.1.2 24 10.2.1.1 track 1
3. On Device A, create an NQA test group.
# Create an NQA test group with the administrator name being admin and operation tag being test.
[DeviceA] nqa entry admin test
# Configure the test type of the NQA test group as ICMP echo.
[DeviceA-nqa-admin-test] type icmp-echo
# Configure ICMP echo requests to use 10.2.1.1 as their destination IP address.
[DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.1.1
# Configure the device to perform tests at an interval of 100 milliseconds.
[DeviceA-nqa-admin-test-icmp-echo] frequency 100
# Create reaction entry 1. If the number of consecutive probe failures reaches 5, collaboration with other
modules is triggered.
[DeviceA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type
consecutive 5 action-type trigger-only
To Next Page
Loading...
