When
configuring HWPing, go to these sections for information you are interested in:
l
HWPing Overview
l
HWPing Configuration
l
HWPing Configuration Examples
HWPing (pronounced Hua’Wei Ping) is a
network diagnostic tool. It is used to test the performance of various
protocols running in networks. HWPing provides more functions than the ping
command.
l
The ping command can only use the ICMP
protocol to test the round trip time (RTT) between this end and a specified
destination end for the user to judge whether the destination end is reachable.
l
Besides the above function of the ping
command, HWPing can also provide other functions, such as testing the status (open/close)
of a DHCP/FTP/HTTP/SNMP server and the response time of various services.
You need to configure HWPing client and
sometimes the corresponding HWPing servers as well to perform various HWPing
tests.
All HWPing tests are initiated by HWPing
client and you can view the test results on HWPing client only.
When performing a HWPing test, you need to
configure a HWPing test group on the HWPing client. A HWPing test group is a
set of HWPing test parameters. A test group contains several test parameters
and is uniquely identified by an administrator name and a test tag.
After creating a HWPing test group and
configuring the test parameters, you can then perform a HWPing test by the test-enable
command.
l
Being different from the ping command,
HWPing does not display the RTT or timeout status of each packet on the Console
terminal in real time. To view the statistic results of your HWPing test
operation, you need to execute the display hwping command.
l
HWPing also allows you to set parameters for
HWPing test groups, start HWPing tests and view statistical test results
through a network management device.
Figure 1-1 HWPing
illustration
Among the test types supported by HWPing,
only the ICMP test can be performed when IRF fabric is enabled; all other test
types cannot be performed when IRF fabric is enabled.
Table 1-1 Test types supported by HWPing
|
Supported test types
|
Description
|
|
ICMP test
|
For these types of tests, you need to
configure HWPing client and corresponding servers.
|
|
DHCP test
|
|
FTP test
|
|
HTTP test
|
|
DNS test
|
|
SNMP test
|
|
Jitter test
|
l
These types of tests need the cooperation of
the HWPing client and HWPing server.
l
Do not perform a TCP, UDP or jitter test on a
well-known port (ports with a number ranging from 1 to 1023) or on a port
with a port number greater than 50000. Otherwise, your HWPing test may fail
or the service corresponding to the well-known port may become unavailable.
|
|
TCP test
|
Tcppublic test
|
|
Tcpprivate test
|
|
UDP test
|
Udppublic test
|
|
Udpprivate test
|
You need to configure corresponding test
parameters for each type of HWPing test. HWPing test parameters can be
configured on HWPing client only. For the configurations on HWPing client,
refer to section HWPing Client
Configuration.
Table 1-2
HWPing test parameters
|
Test parameter
|
Description
|
|
Destination address (destination-ip)
|
For 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 HWPing server.
|
|
Destination port (destination-port)
|
For 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
HWPing server.
|
|
Source interface (source-interface)
|
l
For DHCP test, you must specify a source
interface, which will be used by HWPing client to send DHCP requests. If no
source interface is specified for a DHCP test, the test will not succeed.
l After a source interface is specified, HWPing client uses this
source interface to send DHCP requests during a DHCP test.
l
The IP address of the specified source
interface will be used as the source IP address of DHCP requests.
|
|
Source address (source-ip)
|
For HWPing tests other than DHCP test,
you can specify a source IP address for test packets, which will be used by
the server as the destination address of response packets.
|
|
Source port (source-port)
|
For HWPing 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.
|
|
Test type (test-type)
|
l
You can use HWPing to test a variety of
protocols, see Table 1-1 for details.
l
To perform a type of test, you must first create
a test group of this type. One test group can be of only one HWPing test
type.
l
If you modify the test type of a test group
using the test-type command, the parameter settings, test results, and
history records of the original test type will be all cleared.
|
|
Number of probes per test (count)
|
l
For tests except jitter test, only one test packet
is sent in a probe. In a jitter test, you can use the jitter-packetnum command
to set the number of packets to be sent in a probe.
|
|
Packet size (datasize)
|
l
For ICMP/UDP/jitter test, you can configure
the size of test packets.
l
For ICMP test, the ICMP packet size refers to
the length of ECHO-REQUEST packets (excluding IP and ICMP headers)
|
|
Maximum number of history records that
can be saved (history-records)
|
This parameter is used to specify the
maximum number of history records that can be saved in a test group. When the
number of saved history records exceeds the maximum number, HWPing discards
some earliest records.
|
|
Automatic test interval (frequency)
|
This parameter is used to set the
interval at which the HWPing client periodically performs the same test
automatically.
|
|
Probe timeout time (timeout)
|
l The probe timeout timer is started after the HWPing client sends out
a test packet.
l
This parameter is in seconds.
|
|
Type of service (tos)
|
Type of service is the value of the ToS
field in IP header in the test packets.
|
|
dns
|
This parameter is used to specify a DNS
domain name in a HWPing DNS test group.
|
|
dns-server
|
This parameter is used to set the DNS
server IP address in a HWPing DNS test group.
|
|
HTTP operation type (http-operation)
|
This parameter is used to set the type of
HTTP interaction operation between HWPing client and HTTP server.
|
|
HTTP operation string and version (http-string)
|
This parameter is used to set the HTTP
operation string and version in an HTTP test.
|
|
FTP operation type (ftp-operation)
|
This parameter is used to set the type of
FTP interaction operation between HWPing client and FTP server.
|
|
FTP login username and password (username
and password)
|
The two parameters are used to set the
username and password to be used for FTP operation.
|
|
File name for FTP operation (filename)
|
Name of a file to be transferred between
HWPing client and FTP server
|
|
Number of jitter test packets to be sent
per probe (jitter-packetnum)
|
l
Jitter test is used to collect statistics
about delay jitter in UDP packet transmission
l
In a jitter probe, the HWPing client sends a
series of packets to the HWPing server at regular intervals (you can set the
interval). Once receiving such a packet, the HWPing server marks it with a
timestamp, and then sends it back to the HWPing client. Upon receiving a
packet returned, the HWPing client computes the delay jitter time. The HWPing
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.
|
|
Interval to send jitter test packets (jitter-interval)
|
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.
|
|
Trap
|
l
A HWPing 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.
l
You can set the number of consecutive failed
HWPing tests before Trap output. You can also set the number of consecutive
failed HWPing probes before Trap output.
|
1.2 HWPing Configuration
The TCP/UDP/jitter tests need the
cooperation of HWPing client and HWPing server. Other types of tests need to
configure HWPing client and corresponding different servers.
You can enable both the HWPing client and
HWPing server functions on an H3C S5600 Ethernet switch, that is, the switch
can serve as a HWPing client and server simultaneously.
The following table describes the
configuration on HWPing server, which is the same for HWPing test types that
need to configure HWPing server.
Follow these steps
to perform HWPing server configurations:
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
—
|
|
Enable the HWPing server function
|
hwping-server enable
|
Required
Disabled by default.
|
|
Configure a UDP listening service
|
hwping-server udpecho ip-address port-num
|
Required for UDP and jitter tests
By default, no UDP listening service is
configured.
|
|
Configure a TCP listening service
|
hwping-server tcpconnect ip-address port-num
|
Required for TCP tests
By default, no TCP listening service is
configured.
|
Note that:
l
The HWPing server function is needed only for
jitter, TCP, and UDP tests.
l
You can configure multiple TCP/UDP listening
services on one HWPing server, with each listening service corresponding to a specific
destination IP address and port number.
After HWPing client is enabled, you can
create multiple test groups for different tests, without the need to enable
HWPing client repeatedly for each test group.
Different types of HWPing tests are
somewhat different in parameters and parameter ranges. The following text
describes the configuration on HWPing client for different test types.
Among the test
types supported by HWPing, only the ICMP test can be performed when IRF fabric
is enabled; all other test types cannot be performed when IRF fabric is enabled.
With IRF fabric enabled, you are allowed to configure HWPing tests and use the display
commands to check your configurations, but for non ICMP tests, the HWPing tests
you configured cannot be executed until fabric is disabled.
1)
Configuring ICMP test on HWPing client
Follow these steps
to configure ICMP test on HWPing client:
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
—
|
|
Enable the HWPing client function
|
hwping-agent enable
|
Required
By default, the HWPing client function is
disabled.
|
|
Create a HWPing test group and enter its
view
|
hwping administrator-name
operation-tag
|
Required
By default, no test group is configured.
|
|
Configure the test type
|
test-type icmp
|
Optional
By default, the test type is ICMP.
|
|
Configure the destination IP address
|
destination-ip ip-address
|
Required
By default, no destination address is
configured.
|
|
Configure the source IP address
|
source-ip ip-address
|
Optional
By default, no source IP address is
configured.
|
|
Configure the number of probes per test
|
count times
|
Optional
By default, each test makes one probe.
|
|
Configure the packet size
|
datasize size
|
Optional
By default, the packet size is 56 bytes.
|
|
Configure the maximum number of history
records that can be saved
|
history-records number
|
Optional
By default, the maximum number is 50.
|
|
Configure the automatic test interval
|
frequency interval
|
Optional
By default, the automatic test interval
is zero seconds, indicating no automatic test will be made.
|
|
Configure the probe timeout time
|
timeout time
|
Optional
By default, a probe times out in three
seconds.
|
|
Configure the type of service (ToS)
|
tos
value
|
Optional
By default, the service type is zero.
|
|
Start the test
|
test-enable
|
Required
|
|
Display test results
|
display hwping results [ admin-name operation-tag ]
|
Required
Available in any view.
|
2)
Configuring DHCP test on HWPing client
Follow these steps to configure DHCP test
on HWPing client:
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
—
|
|
Enable the HWPing client function
|
hwping-agent enable
|
Required
By default, the HWPing client function is
disabled.
|
|
Create a HWPing test group and enter its
view
|
hwping administrator-name
operation-tag
|
Required
By default, no test group is configured.
|
|
Configure the test type
|
test-type dhcp
|
Required
By default, the test type is ICMP.
|
|
Configure the source interface
|
source-interface interface-type interface-number
|
Required
You can only configure a VLAN interface
as the source interface.
By default, no source interface is
configured.
|
|
Configure the number of probes per test
|
count times
|
Optional
By default, each test makes one probe.
|
|
Configure the maximum number of history
records that can be saved
|
history-records number
|
Optional
By default, the maximum number is 50.
|
|
Configure the probe timeout time
|
timeout time
|
Optional
By default, a probe times out in three
seconds.
|
|
Start the test
|
test-enable
|
Required
|
|
Display test results
|
display hwping results [ admin-name operation-tag ]
|
Required
You can execute the command in any view.
|
3)
Configuring FTP test on HWPing client
Follow these steps to configure FTP test on
HWPing client:
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
—
|
|
Enable the HWPing client function
|
hwping-agent enable
|
Required
By default, the HWPing client function is
disabled.
|
|
Create a HWPing test group and enter its
view
|
hwping administrator-name
operation-tag
|
Required
By default, no test group is configured.
|
|
Configure the test type
|
test-type ftp
|
Required
By default, the test type is ICMP.
|
|
Configure the destination IP address
|
destination-ip ip-address
|
Required
By default, no destination address is
configured.
|
|
Configure the source IP address
|
source-ip ip-address
|
Required
By default, no source IP address is
configured.
|
|
Configure the source port
|
source-port port-number
|
Optional
By default, no source port is configured.
|
|
Configure the number of probes per test
|
count times
|
Optional
By default, each test makes one probe.
|
|
Configure the maximum number of history
records that can be saved
|
history-records number
|
Optional
By default, the maximum number is 50.
|
|
Configure the automatic test interval
|
frequency interval
|
Optional
By default, the automatic test interval
is zero seconds, indicating no automatic test will be made.
|
|
Configure the probe timeout time
|
timeout time
|
Optional
By default, a probe times out in three
seconds.
|
|
Configure the type of service
|
tos
value
|
Optional
By default, the service type is zero.
|
|
Configure the type of FTP operation
|
ftp-operation { get | put }
|
Optional
By default, the type of FTP operation is get,
that is, the FTP operation will get a file from the FTP server.
|
|
Configure an FTP login username
|
username name
|
Required
By default, neither username nor password
is configured.
|
|
Configure an FTP login password
|
password password
|
|
Configure a file name for the FTP
operation
|
filename file-name
|
Required
By default, no file name is configured
for the FTP operation
|
|
Start the test
|
test-enable
|
Required
|
|
Display test results
|
display hwping results [ admin-name operation-tag ]
|
Required
You can execute the command in any view.
|
4)
Configuring HTTP test on HWPing client
Follow these steps to configure HTTP test
on HWPing client:
|
To do…
|
Use the command…
|
Remarks
|
|
Enter system view
|
system-view
|
—
|
|
Enable the HWPing client function
|
hwping-agent enable
|
Required
By default, the HWPing client function is
disabled.
|
|
Create a HWPing test group and enter its
view
|
hwping administrator-name
operation-tag
|
Required
By default, no test group is configured.
|
|
Configure the test type
|
test-type http
|
Required
By default, the test type is ICMP.
|
|
Configure the destination IP address
|
destination-ip ip-address
|
Required
You can configure an IP address or a host
name.
By default, no destination address is
configured.
|
|
Configure dns-server
|
dns-server
ip-address
|
Required when you use the destination-ip
command to configure the destination address as the host name.
By defaul |
