Remote-Ping Configuration Example 517
TCP Connect Time: 73 HTTP Operation Min Time: 27
TCP Connect Min Time: 5 HTTP Operation Max Time: 80
TCP Connect Max Time: 20
TCP Connect Timeout Times: 0
[4210-Remote-Ping-administrator-http] display Remote-Ping history administrator h
ttp
Remote-Ping entry(admin administrator, tag http) history record:
Index Response Status LastRC Time
1 13 1 0 2000-04-02 15:15:52.5
2 9 1 0 2000-04-02 15:15:52.5
3 3 1 0 2000-04-02 15:15:52.5
4 3 1 0 2000-04-02 15:15:52.5
5 3 1 0 2000-04-02 15:15:52.5
6 2 1 0 2000-04-02 15:15:52.4
7 3 1 0 2000-04-02 15:15:52.4
8 3 1 0 2000-04-02 15:15:52.4
9 2 1 0 2000-04-02 15:15:52.4
10 2 1 0 2000-04-02 15:15:52.4
For detailed output description, see the corresponding command manual.
n
For an HTTP test, if configuring the destination address as the host name, you
must configure the IP address of the DNS server to resolve the host name into an
IP address, which is the destination IP address of this HTTP test.
Jitter Test Network requirements
Both the Remote-Ping client and the Remote-Ping server are Switch 4210s.
Perform a Remote-Ping jitter test between the two switches to test the delay jitter
of the UDP packets exchanged between this end (Remote-Ping client) and the
specified destination end (Remote-Ping server).
Network diagram
Figure 184 Network diagram for the Jitter test
Configuration procedure
■ Configure Remote-Ping Server (Switch B):
# Enable the Remote-Ping server and configure the IP address and port to listen
on.
<4210> system-view
[4210] Remote-Ping-server enable
[4210] Remote-Ping-server udpecho 10.2.2.2 9000
■ Configure Remote-Ping Client (Switch A):
# Enable the Remote-Ping client.
<4210> system-view
[4210] Remote-Ping-agent enable
# Create a Remote-Ping test group, setting the administrator name to
"administrator" and test tag to "Jitter".
[4210] Remote-Ping administrator Jitter
Switch A
Switch B
HWPing Client
IP network
10.1.1.1/8 10.2.2.2/8
HWPing Server
To Next Page
Loading...
