Tool Used for Measuring Performance

The tool used for measuring the performance of HP-UX IPQoS is netperf. Developed by HP, this tool is distributed in source form at www.netperf.org. This site is informally maintained by Hewlett-Packard. The netperf tool has two executables: netperf and netserver. netserver can run as a child process to inetd. In that case, netserver should be added to the /etc/inetd.conf file. netserver can also run as a standalone daemon.

Two systems are required to test HP-UX IPQoS. One system runs netserver (the remote system) and the other system runs netperf (the local system). By default, netperf is installed in the /opt/netperf directory (it is possible to install it in a different directory, but changes must be made to the netperf makefiles). The remote system must have an entry for netserver in the /etc/inetd.conf file and the local system must have an entry for netperf in the /etc/services files identifying that netperf is using TCP port number 12865. After the /etc/inetd.conf file is edited, make sure to update the inetd daemon on the remote system using kill –HUP <PID#>.

netperf provides many scripts for running different tests. See the netperf manpages for a detailed description of these scripts.

The most common use of netperf is measuring bulk data transfer performance. This is also referred to as "stream" or "unidirectional stream" performance. Essentially, these tests will measure how fast one system can send data to another and/or how fast that other system can receive it.

Test Configuration

The tests were done on two systems; one running HP-UX 11i v1 and the other running HP-UX 11i v2 (update 2). The two systems, connected back to back with a crossover cable, were used for the netperf tests. HP-UX IPQoS A.01.00 was only installed on the HP-UX 11i v2 system (rp3440, 4 CPU). The other system was running HP-UX 11i v1 (rp4440, 6 CPU) without HP-UX IPQoS installed. While testing, care should be taken to make sure that other network traffic does not interfere with the traffic generated by the tests. This can be achieved by performing all the tests in a private LAN.

Tests were done on both 100BaseT and 1000BaseT interfaces with the different HP-UX IPQoS configurations occurring on the local system. As specified, the remote system was running HP-UX 11i v1 without HP-UX IPQoS installed.

On the local system (HPUX 11i v2), the tests were done twice; once with HP-UX IPQoS installed (pushed) but with no filters or policies (rules) configured. In this case HP-UX IPQoS only plays the role of “pass-through”. The second time, HP-UX IPQoS was configured with a simple filter and policy. Note: tests did not specify any bandwidth reservation since the purpose of the tests was to see the performance impact of HP-UX IPQoS on the HP-UX operating system. The simple filter and policy used for the tests was:

HP-UX IPQoS is ENABLED and FILTERING.

Name: current

Adapter: lan1 (00:0e:7f:4e:bf:88) Type: Ethernet Speed: 100 Mbps Policy: p1

DSCP: 20

Filter: f1

Transport protocol: 6 (tcp)

Priority: 0

3