Documentation, Support, and Training
Understanding ILOM on the Switch
Administering ILOM (Web Interface)
Understanding Switch-Specific Commands
activate Command (switch-specific)
deactivate Command (switch-specific)
Performs a read latency diagnostic. Issued on the Linux InfiniBand host.
ib_send_lat [-p TCP_port][-d device][-i IB_port][-c RC|UC|UD][-m mtu] [-s size][-a][-l][-t depth][-g][-n iters][-I size][-C][-H][-U][-V][-e] [-F][IP_address]
where:
TCP_port is the TCP port.
device is the InfiniBand device.
IB_port is the InfiniBand port.
mtu is the size of the MTU.
size is the size of the messages.
depth is the size of the TX queue.
iters is the number of message exchanges.
IP_address is the IP address of the remote node host.
This InfiniBand software command performs a latency diagnostic between two nodes in the InfiniBand fabric. The command is dependent upon the Internet Protocol, so the InfiniBand fabric must be configured with Internet Protocol over InfiniBand (IPoIB). The command is a client-server, in that a remote node is configured as a server, while a local node performs as a client.
The command is first run locally on the server. The command is then run again locally on the client, pointing to the IP address of the server. The diagnostic checks the latency of the data transfer from the server to the client. The connection uses the Reliable Datagram transport. Optionally, you can set the connection between the nodes to use Reliable Connection, Unreliable Connection, or Unreliable Datagram transport.
Note - This command only functions if your InfiniBand fabric is configured with IPoIB.
The following table describes the options to the ib_send_lat command and their purposes:
|
The following example shows how to run a diagnostic between a local node client and a remote node server with the ib_send_lat command. First configure the remote node server:
# ib_send_lat ------------------------------------------------------------------ Send Latency Test Inline data is used up to 400 bytes message Connection type : RC local address: LID 0x01 QPN 0x9c0406 PSN 0x94e3e1 remote address: LID 0x05 QPN 0x250406 PSN 0xbecb59 Mtu : 1024 ------------------------------------------------------------------ #bytes #iterations t_min[usec] t_max[usec] t_typical[usec] 2 1000 5.98 31.40 6.14 ------------------------------------------------------------------ #
Note - The output is not displayed until the local node client issues the respective command.
Then run the command on the local node client:
# ib_send_lat 192.168.200.100 ------------------------------------------------------------------ Send Latency Test Inline data is used up to 400 bytes message Connection type : RC local address: LID 0x05 QPN 0x250406 PSN 0xbecb59 remote address: LID 0x01 QPN 0x9c0406 PSN 0x94e3e1 Mtu : 1024 ------------------------------------------------------------------ #bytes #iterations t_min[usec] t_max[usec] t_typical[usec] 2 1000 5.97 65.62 6.13 ------------------------------------------------------------------ #