The destination-port command configures the destination port number for an NQA test.
The undo destination-port command restores the default setting.
A port number larger than 10000 is recommended for a jitter test instance. A small port number may be conflict with the default port number of a protocol, causing a test failure.
Parameter | Description | Value |
---|---|---|
port-number | Specifies the destination port number. | The value is integer that ranges from 1 to 65535. The configured port cannot be a well-known port or used by other modules. |
Usage Scenario
NQA detects service features by creating test instances. In NQA, two test ends are called an NQA client and an NQA server. An NQA test is initiated by the NQA client. After test instances are configured with commands on the client, NQA places different types of test instances into various test queues. After the test starts, a response packet is returned. Carriers can then know the operating status about protocols by analyzing the received response packet.
For a test instance, the port for accessing the server is specified using the destination port number configured with the destination-port command on the client.
For example, to detect whether the TCP service runs normally on the peer device using a TCP test instance, perform the following configurations:
On the server: Configure the TCP server used for NQA tests, including the supported client IP address and the TCP port number opened to the client.
Precautions
In the case of a TCP test instance and a UDP test instance, the configured destination port number must be the same as the opened port number on the server.
This command applies to only the FTP, HTTP, TCP, Trace, UDP, and UDP Jitter test instances.
You cannot change the destination port number of the test that is being performed.