Provided by: infiniband-diags_1.4.4-20090314-1_amd64
ibping - ping an InfiniBand address
ibping [-d(ebug)] [-e(rr_show)] [-v(erbose)] [-G(uid)] [-C ca_name] [-P ca_port] [-s smlid] [-t(imeout) timeout_ms] [-V(ersion)] [-c ping_count] [-f(lood)] [-o oui] [-S(erver)] [-h(elp)] <dest lid | guid>
ibping uses vendor mads to validate connectivity between IB nodes. On exit, (IP) ping like output is show. ibping is run as client/server. Default is to run as client. Note also that a default ping server is implemented within the kernel.
-c stop after count packets -f, --flood flood destination: send packets back to back without delay -o, --oui use specified OUI number to multiplex vendor mads -S, --Server start in server mode (do not return)
Most OpenIB diagnostics take the following common flags. The exact list of supported flags per utility can be found in the usage message and can be shown using the util_name -h syntax. # Debugging flags -d raise the IB debugging level. May be used several times (-ddd or -d -d -d). -e show send and receive errors (timeouts and others) -h show the usage message -v increase the application verbosity level. May be used several times (-vv or -v -v -v) -V show the version info. # Addressing flags -G use GUID address argument. In most cases, it is the Port GUID. Example: "0x08f1040023" -s <smlid> use 'smlid' as the target lid for SM/SA queries. # Other common flags: -C <ca_name> use the specified ca_name. -P <ca_port> use the specified ca_port. -t <timeout_ms> override the default timeout for the solicited mads. Multiple CA/Multiple Port Support When no IB device or port is specified, the port to use is selected by the following criteria: 1. the first port that is ACTIVE. 2. if not found, the first port that is UP (physical link up). If a port and/or CA name is specified, the user request is attempted to be fulfilled, and will fail if it is not possible.
Hal Rosenstock <firstname.lastname@example.org>