Remote-Ping Configuration - 3Com 4210 PWR Configuration Manual

498 C 45: R
HAPTER EMOTE
Remote-Ping
Configuration
Configuration on a
Remote-Ping Server
-P C
ING ONFIGURATION
Table 369 Remote-Ping test parameters
Test parameter
FTP operation type (ftp-operation)
FTP login username and password (username
and password)
File name for FTP operation (filename)
Number of jitter test packets to be sent per
probe (jitter-packetnum)
Interval to send jitter test packets
(jitter-interval)
Trap
The TCP/UDP/jitter tests need the cooperation of Remote-Ping client and
Remote-Ping Server, Other types of tests need to configure Remote-Ping client and
corresponding different servers.
You can enable both the Remote-Ping client and Remote-Ping server functions on
a Switch 4210, that is, the switch can serve as a Remote-Ping client and server
simultaneously.
Description
This parameter is used to set the type of FTP
interaction operation between Remote-Ping
client and FTP server.
The two parameters are used to set the
username and password to be used for FTP
operation.
Name of a file to be transferred between
Remote-Ping client and FTP server
Jitter test is used to collect statistics
■
about delay jitter in UDP packet
transmission
In a jitter probe, the Remote-Ping client
■
sends a series of packets to the
Remote-Ping server at regular intervals
(you can set the interval). Once receiving
such a packet, the Remote-Ping server
marks it with a timestamp, and then
sends it back to the Remote-Ping client.
Upon receiving a packet returned, the
Remote-Ping client computes the delay
jitter time. The Remote-Ping client
collects delay jitter statistics on all the
packets returned in the test. So, the
more packets a jitter probe sends, the
more accurate the jitter statistics is, but
the longer time the jitter test costs.
Each jitter probe will send multiple UDP test
packets at regular intervals (you can set the
interval). The smaller the interval is, the
faster the test is. But a too small interval
may somewhat impact your network.
A Remote-Ping test will generate a Trap
■
message no matter whether the test
successes or not. You can use the Trap
switch to enable or disable the output of
trap messages.
You can set the number of consecutive
■
failed Remote-Ping tests before Trap
output. You can also set the number of
consecutive failed Remote-Ping probes
before Trap output.