Example for Configuring an NQA TCP Test to Measure the Response Time on an IP Network
This section provides an example for configuring an NQA TCP test to measure the response time on an IP network.
Networking Requirements
On the network shown in Figure 4-7, the headquarters and a subsidiary of a company often need to use TCP to exchange files with each other. The time taken to respond to a TCP transmission request must be less than 800 ms. The NQA TCP test can be configured to measure the TCP response time between DeviceA and DeviceD that are connected to the IP backbone network.
Configuration Roadmap
The configuration roadmap is as follows:
Configure DeviceD as the NQA client and DeviceA as the NQA server, and create a TCP test instance.
Configure the test instance to start at 10:00 o'clock every day and start the test instance.
Data Preparation
To complete the configuration, you need the following data:
IP addresses of DeviceA and DeviceD that are connected to the IP backbone network
Number of the port used to monitor TCP services
Procedure
- Configure the NQA server DeviceA.
<DeviceA> system-view [~DeviceA] nqa-server tcpconnect 10.1.1.1 4000 [*DeviceA] commit
- Configure the NQA client DeviceD. Create a TCP test instance. Set the destination IP address to
the IP address of DeviceA.
<DeviceD> system-view [~DeviceD] nqa test-instance admin tcp [*DeviceD-nqa-admin-tcp] test-type tcp [*DeviceD-nqa-admin-tcp] destination-address ipv4 10.1.1.1 [*DeviceD-nqa-admin-tcp] destination-port 4000
- Start the test instance immediately.
[*DeviceD-nqa-admin-tcp] start now [*DeviceD-nqa-admin-tcp] commit
- Verify the test result. Run the display nqa results
test-instance admin tcp command on DeviceD. The command output shows that the TCP response time is less than
800 ms.
[~DeviceD-nqa-admin-tcp] display nqa results test-instance admin tcp NQA entry(admin, tcp) :testflag is active ,testtype is tcp 1 . Test 1 result The test is finished Send operation times: 3 Receive response times: 3 Completion:success RTD OverThresholds number:0 Attempts number:1 Drop operation number:0 Disconnect operation number:0 Operation timeout number:0 System busy operation number:0 Connection fail number:0 Operation sequence errors number:0 RTT Stats errors number:0 Destination ip address:10.1.1.1 Min/Max/Average Completion Time: 600/610/603 Sum/Square-Sum Completion Time: 1810/1092100 Last Good Probe Time: 2011-01-16 02:59:41.6 Lost packet ratio: 0 %
- Configure the test instance to start at 10:00 o'clock every
day.
[*DeviceD-nqa-admin-tcp] stop [*DeviceD-nqa-admin-tcp] start daily 10:00:00 to 10:30:00 [*DeviceD-nqa-admin-tcp] commit
Configuration Files
DeviceA configuration file
# sysname DeviceA # nqa-server tcpconnect 10.1.1.1 4000 # isis 1 network-entity 00.0000.0000.0001.00 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.1.1.1 255.255.255.0 isis enable 1 # return
DeviceD configuration file
# sysname DeviceD # isis 1 network-entity 00.0000.0000.0001.00 # interface GigabitEthernet0/1/0 undo shutdown ip address 10.2.2.1 255.255.255.0 isis enable 1 # nqa test-instance admin tcp test-type tcp destination-address ipv4 10.1.1.1 destination-port 4000 start daily 10:00:00 to 10:30:00 # return
