HP StorageWorks Scalable File Share - Manual (Page 152)

Verifying, diagnosing, and maintaining the system 6–22
The output from the command displays the speed the link is running at, as shown in the following example:
# ./net_test.bash --serial --net tcp --server "10.128.0.1 10.128.0.2"
== Testing 2 servers in serial ==
10.128.0.1 Throughput MBytes/sec 91.40
10.128.0.2 Throughput MBytes/sec 91.73
== Test Finished ==
Compare the results of this test with the expected performance details provided in Appendix B. Note that if
you are performing the sequential test on a dual Gigabit Ethernet where client nodes have only a single link,
the maximum throughput that will be seen from such a test is that of a single Gigabit Ethernet link, as each
server link is tested sequentially, not each individual server.
Parallel test
To run the
net_test.bash
command to test connections between a number of servers and a number of
clients in parallel, enter the command on one of the client nodes using the following syntax. Specify the
TCP/IP address of each server and the host name of each client to be tested:
NOTE: To ensure that an accurate test is performed where a dual Gigabit Ethernet interconnect is used,
order the client nodes so that they are matched with a server IP address that they can communicate with.
Where there is only a single Gigabit Ethernet link on the client nodes, this means that each client must be
matched to a server address on the same subnet as itself. Where there is a dual Gigabit Ethernet link on
the client nodes, it is possible to specify each client twice, once for each link to a server on a different
subnet.
To ensure that an accurate test is performed where a bonded Gigabit Ethernet interconnect is used, the
ratio of clients to servers must be an even number. (If the number of clients is not an even multiple of the
number of servers, there will be an imbalance in the system, and this will skew the results.) The likelihood
of imbalance in the system decreases as the ratio of clients to servers increases. As a general rule, it is best
to test with four or more clients per server.
/usr/opt/hpls/diags/bin/net_test.bash --parallel --net tcp --server "server_address1
[server_address2 ...]" --client "client_name1 [client_name2 ...]"
The command uses the
netperf
tool to determine the speed each link is running at. The speed of each
link and the aggregate speed are displayed in the output, as shown in the following example:
# ./net_test.bash --parallel --net tcp --server "10.128.0.1 10.128.0.2" --client
"blue0 blue1"
== Testing 2 servers in parallel ==
10.128.0.1 Throughput MBytes/sec 90.21
10.128.0.2 Throughput MBytes/sec 91.61
Total throughput: 181.82
== Test Finished ==
Compare the results of these tests with the expected performance details provided in Appendix B.
Incremental test
When you run the
net_test.bash
command in incremental mode, the command tests first with a single
HP SFS server, then with two, then three, and so on until all servers have been tested in parallel. The
incremental test verifies whether the Gigabit Ethernet network connecting each of the HP SFS servers to each
client used in the test is performing at the expected speed, and if there is any degradation under load.
To test connections between a number of servers and a number of clients incrementally, enter the
net_test.bash
command on one of the client nodes using the following syntax. Specify the TCP/IP
address of each server and the host name of each client to be tested: