beautypg.com

HP StorageWorks Scalable File Share User Manual

Page 155

background image

Verifying the system

6–25

6.

Test the PCI bandwidth to confirm whether the PCI interface is correctly detected as 64-bit/132MHz,

by entering the following command:

# /opt/gm/bin/gm_debug –L
Opening board 0, port 0
LANai is running at 224 MHz.
GM-2 DMA rate for 4096 Byte transfers (64bit / 132MHz bus)
Timing 32 segments.
bus_read (send) = 710 MBytes/s
bus_write (recv) = 1040 MBytes/s
bus_read_write (send+recv) = 849 MBytes/s

If the interface was not correctly detected during hardware initialization at boot time, consider the

possibility of a problem with the riser card or with the PCI slot. Refer to the HP ROM-based Setup

Utility User Guide for information on testing the PCI bus.

6.1.8.2.2 Testing Myrinet interconnect performance using the net_test.bash command

If you are already familiar with the

gm_allsize

tool and would prefer to use that tool to test the

performance of your Myrinet interconnect, see Section 6.1.8.2.3.

You can test the network performance of a Myrinet interconnect by running the

net_test.bash

command

between multiple HP SFS servers and clients in three modes: sequential, parallel, and incremental.

Sequential tests determine whether any of the individual links between clients and Object Storage Servers

are running slowly. Parallel tests detect problems in the network at load, and incremental tests verify the

results of the parallel tests. Run the sequential tests first, followed by the parallel tests, and finally run the

incremental tests.

To run the parallel or incremental tests, the client where you run the test must be able to connect to all of the

other clients that are to be used in testing, using either the

ssh

utility without a password or the

rsh

utility

without a password. If you are using the

rsh

utility, you must add

--remote_shell rsh

to the command

line.

Before you start to run the test scripts on the clients, ensure that the HP SFS servers are running the

appropriate network packet receivers, by entering the

net_server.bash

command on the administration

server, using the following syntax:

/usr/opt/hpls/diags/bin/net_server.bash --server "server_name1 [server_name2 ...]"
--net gm

where the

server_name

arguments are the host names of the HP SFS servers that are to be tested. The

output from the command displays the Myrinet host name of each of the specified servers. You will use these

host names as the

server_address

arguments when you run the

net_test.bash

command on the

clients.

Sequential test

To run the

net_test.bash

command to test the connections to a number of servers sequentially, enter the

command on a client node, using the following syntax. Specify the Myrinet host name of each server to be

tested:

/usr/opt/hpls/diags/bin/net_test.bash --serial --net gm --server "server_address1
[server_address2 ...]"

This command tests the network using the

gm_allsize

tool. It tests the link to each server specified on the

command line, in sequence, from the client where the command is run.

The output from the command displays the speed the link is running at, as shown in the following example:

# ./net_test.bash --serial --net gm --server "south5.my.domain.com
south6.my.domain.com south7.my.domain.com"
== Testing 3 servers in serial ==
south5.my.domain.com Throughput MBytes/sec 493.822
south6.my.domain.com Throughput MBytes/sec 494.588
south7.my.domain.com Throughput MBytes/sec 494.832
== Test Finished ==

Compare the results of these tests with the expected performance details provided in Appendix B.