3com 5500-ei pwr Installation Instruction
1-2
Test Types Supported by remote-ping
Among the test types supported by remote-ping, only the ICMP test can be performed when XRN fabric
is enabled; all other test types cannot be performed when XRN fabric is enabled.
Table 1-1 Test types supported by remote-ping
Supported test types
Description
ICMP test
DHCP test
FTP test
HTTP test
DNS test
SNMP test
For these types of tests, you need to configure the remote-ping
client and corresponding servers.
client and corresponding servers.
Jitter test
Tcppublic test
TCP test
Tcpprivate test
Udppublic test
UDP test
Udpprivate test
z
These types of tests need the cooperation of the remote-ping
client and remote-ping server.
client and remote-ping server.
z
Do not perform a TCP, UDP or jitter test on a well-known port
(ports with a number ranging from 1 to 1023). Otherwise,
your remote-ping test may fail or the service corresponding to
the well-known port may become unavailable.
(ports with a number ranging from 1 to 1023). Otherwise,
your remote-ping test may fail or the service corresponding to
the well-known port may become unavailable.
remote-ping Test Parameters
You need to configure corresponding test parameters for each type of remote-ping test. remote-ping
test parameters can be configured on remote-ping client only. For the configurations on the remote-ping
client, refer to section
.
Table 1-2 remote-ping test parameters
Test parameter
Description
Destination address
(destination-ip)
(destination-ip)
For a TCP/UDP/jitter test, you must specify a destination IP address, and
the destination address must be the IP address of a TCP/UDP/UDP
listening service configured on the remote-ping server.
the destination address must be the IP address of a TCP/UDP/UDP
listening service configured on the remote-ping server.
Destination port
(destination-port)
(destination-port)
For a tcpprivate/udpprivate/jitter test, you must specify a destination port
number, and the destination port number must be the port number of a
TCP or UDP listening service configured on the remote-ping server.
number, and the destination port number must be the port number of a
TCP or UDP listening service configured on the remote-ping server.
Source interface
(source-interface)
(source-interface)
z
For a DHCP test, you must specify a source interface, which will be
used by the remote-ping client to send DHCP requests. If no source
interface is specified for the DHCP test, the test will not succeed.
used by the remote-ping client to send DHCP requests. If no source
interface is specified for the DHCP test, the test will not succeed.
z
After a source interface is specified, the remote-ping client uses this
source interface to send DHCP requests during the DHCP test.
source interface to send DHCP requests during the DHCP test.
z
The IP address of the specified source interface will be used as the
source IP address of DHCP requests.
source IP address of DHCP requests.
Source address
(source-ip)
(source-ip)
For remote-ping tests other than DHCP tests, you can specify a source
IP address for test packets, which will be used by the server as the
destination address of response packets.
IP address for test packets, which will be used by the server as the
destination address of response packets.
Source port
(source-port)
(source-port)
For remote-ping tests other than ICMP, DHCP and DNS, you can specify
a source port number for test packets, which will be used by the server
as the destination port number of response packets.
a source port number for test packets, which will be used by the server
as the destination port number of response packets.