Configuring a TCP Test

Procedure

• Configure the NQA server.
  1. Access the system view.

     system-view

  2. Configure the TCP listening address and port number.

     nqa-server tcpconnect [ vpn-instance vpn-instance-name ] ip-address port-number

• Configure the NQA client.
  1. Access the system view.

     system-view

  2. Create an NQA test instance and access the test instance view.

     nqa test-instance admin-name test-name

  3. Set the test type to TCP.

     test-type tcp

  4. Set the destination address.

     destination-address ipv4 ip-address

  5. Configure the destination port.

     destination-port port-number

  6. Optional: Configure other parameters for the TCP test.

     Item	Command	Description
     Configuring description of a test instance	description description-information	-
     Configuring a tested VPN instance	vpn-instance vpn-instance-name	-
     Setting the source IP address of test packets	source-address ipv4 ip-address	By default, no source IP address is specified for test packets. The packets use the primary IP address of the outbound interface as their source IP address. The specified source IP address must be the IP address of an Up interface on the FW. Otherwise, the test will fail.
     Setting the source port of test packets	source-port port-number	-
     Setting the payload size of test packets	datasize size	The default payload size is 20 bytes. When the value of datasize is smaller than 20, the FW still constructs the payload of a packet based on 20 bytes. When the value of datasize is larger than 20, the FW constructs the payload of a packet based on the value of datasize.
     Configuring the characters to be filled in the payload of the test packet	datafill string	By default, the FW fills in the payload using fixed fields. The string specified in the datafill command is padded cyclically from the 29th byte of the payload. That is, the datafill configuration is valid only when the value of datasize is larger than 28.
     Setting the TTL value of test packets	ttl value	The default value is 30.
     Setting the ToS value of test packets	tos value	The default value is 0.
     Configuring the interval for sending TCP SYN packets	interval { seconds interval | milliseconds interval }	By default, TCP SYN packets are sent every 4s.
     Configuring the number of probes in a single test (a probe indicates the process of establishing a TCP connection)	probe-count number	By default, one test initiates three probes.
     Setting the test interval	frequency interval	By default, no test interval is set, and the test runs only once.
     Setting the probe failure percentage	fail-percent percent	The default probe failure percentage is 100%. That is, the test is considered failed only when all probes fail.
     Setting the timeout for a single probe	timeout time	By default, the expiration time for a single probe in the TCP test is 3s.
     Setting the maximum number of historical records	records history number	By default, there are a maximum of 50 historical records.
     Configuring the maximum number of test result records	records result number	By default, a maximum of five test results are recorded.
     Setting the aging time of a test instance	agetime hh:mm:ss	The default value is 0. That is, test instances are never aged.
     Configuring the system to send test packets without querying the routing table	sendpacket passroute	By default, the FW forwards the test packets based on the route queried in the routing table.

  7. Start the NQA test.

     start

     Select one of the following start modes as required.

     • Start the NQA test immediately.

       start now [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } ]

     • Start the NQA test at a specified time point.

       start at [ yyyy/mm/dd ] hh:mm:ss [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } ]

     • Start the NQA test after the delay of a specified period.

       start delay { seconds second | hh:mm:ss } [ end { at [ yyyy/mm/dd ] hh:mm:ss | delay { seconds second | hh:mm:ss } | lifetime { seconds second | hh:mm:ss } ]