Configuring The Udp Jitter Operation - H3C SR6600-X Configuration Manual

Step
2. Create an NQA operation
and enter NQA operation
view.
3. Specify the HTTP type and
enter its view.
4. Specify the URL of the
destination HTTP server.
5. Specify an HTTP login
username.
6. Specify an HTTP login
password.
7. (Optional.) Specify the source
IP address of request packets.
8. Specify the HTTP operation
type.
9. Specify the HTTP version.
10. (Optional.) Enter raw request
view.
11. (Optional.) Specify the
content of a GET request for
the HTTP operation.
12. Save the input and exit to
HTTP operation view.

Configuring the UDP jitter operation

CAUTION:
To ensure successful UDP jitter operations and avoid affecting existing services, do not perform the
operations on well-known ports from 1 to 1023.
Jitter means inter-packet delay variance. A UDP jitter operation measures unidirectional and
bidirectional jitters. You can verify whether the network can carry jitter-sensitive services such as real-time
voice and video services through the UDP jitter operation.
The UDP jitter operation works as follows:
1. The NQA client sends UDP packets to the destination port at a regular interval.
Command
nqa entry admin-name
operation-tag
type http
url url
username username
password { cipher |
simple } password
source ip ip-address
operation { get | post |
raw }
version { v1.0 | v1.1 }
raw-request
Enter or paste the content.
quit
16
Remarks
By default, no NQA operation is created.
N/A
By default, no URL is specified for the
destination HTTP server.
Enter the URL in one of the following
formats:
•
http://host/resource.
•
http://host:port/resource.
By default, no HTTP login username is
specified.
By default, no HTTP login password is
specified.
By default, no source IP address is
specified.
The source IP address must be the IP
address of a local interface, and the
interface must be up. Otherwise, no
request packets can be sent out.
By default, the HTTP operation type is get,
which means obtaining data from the HTTP
server.
By default, HTTP 1.0 is used.
Every time you enter raw request view, the
previously configured content of the HTTP
request is removed.
By default, no contents are specified.
This step is required for the raw operation.
N/A