Accessing The Onboard Administrator; Accessing The Oa Through The Network; Access The Oa Web-Based Administration Interface - HP IBRIX X9720 System Administrator Manual

The exds_netperf utility measures streaming performance in two modes:
Serial—Streaming I/O is done to each network interface in turn. The host where
exds_netperf is run is the client that is being tested.
Parallel—Streaming I/O is done on all network interfaces at the same time. This test uses
several clients.
The serial test measures point-to-point performance. The parallel test measures more components
of the network infrastructure and could uncover problems not visible with the serial test. Keep in
mind that overall throughput of the parallel test is probably limited by client's network interface.
The test is run as follows:
Copy the contents of /opt/hp/mxso/diags/netperf-2.1.p13 to an x86_64 client host.
Copy the test scripts to one client from which you will be running the test. The scripts required
are exds_netperf, diags_lib.bash, and nodes_lib.bash from the /opt/hp/mxso/
diags/bin directory.
Run exds_netserver -s <server_list> to start a receiver for the test on each X9720
Network Storage System server blade, as shown in the following example:
exds_netserver -s glory[1-8]
Read the README.txt file to build for instructions on building exds_netperf and build
and install exds_netperf. Install on every client you plan to use for the test.
On the client host, run exds_netperf in serial mode against each X9720 Network Storage
System server in turn. For example, if there are two servers whose eth2 addresses are
16.123.123.1 and 16.123.123.2, use the following command:
# exds_netperf --serial --server "16.123.123.1 16.123.123.2"
On a client host, run exds_netperf in parallel mode, as shown in the following example.
In this example, hosts blue and red are the tested clients (exds_netperf itself could be one
of these hosts or on a third host):
# exds_netperf --parallell \
Normally, the IP addresses you use are the IP addresses of the host interfaces (eth2, eth3, and so
on).

Accessing the Onboard Administrator

Accessing the OA through the network

The OA has a CLI that can be accessed using ssh. The address of the OA is automatically placed
in /etc/hosts. The name is <systemname>-mp. For example, to connect to the OA on a system
called glory, use the following command:
# ssh exds@glory-mp

Access the OA Web-based administration interface

The OA also has a Web-based administration interface. Because the OA's IP address is on the
management network, you cannot access it directly from outside the system. You can use ssh
tunneling to access the OA. For example, using a public domain tool such as putty, you can
configure a local port (for example, 8888) to forward to <systemname>-mp:443 on the remote
server. For example, if the system is called glory, you configure the remote destination as
glory-mp:443. Then log into glory from your desktop. On your desktop, point your browser at
https://localhost:8888. This will connect you to the OA.
142 Troubleshooting
--server "16.123.123.1,16.123.123.2" \
--clients "red,blue"