ibqueryerrors(8) [debian man page]

IBQUERYERRORS(8)						OpenIB Diagnostics						  IBQUERYERRORS(8)

NAME

       ibqueryerrors.pl - query and report non-zero IB port counters

SYNOPSIS

       ibqueryerrors.pl [-a -c -r -R -C <ca_name> -P <ca_port> -s <err1,err2,...> -S <switch_guid> -D <direct_route> -d]

DESCRIPTION

       ibqueryerrors.pl  reports  the  port  counters  of  switches.   This  is similar to ibcheckerrors with the additional ability to filter out
       selected errors, include the optional transmit and receive data counters, report actions to remedy a non-zero count, and report	full  link
       information for the link reported.

OPTIONS

       -a     Report an action to take.  Some of the counters are not errors in and of themselves.  This reports some more information on what the
	      counters mean and what actions can/should be taken if they are non-zero.

       -c     Suppress some of the common "side effect" counters.  These counters usually do not indicate an error condition and can be usually be
	      safely ignored.

       -r     Report  the port information.  This includes LID, port, external port (if applicable), link speed setting, remote GUID, remote port,
	      remote external port (if applicable), and remote node description information.

       -R     Recalculate the ibnetdiscover information, ie do not use the cached information.	This option is slower but should be  used  if  the
	      diag tools have not been used for some time or if there are other reasons to believe that the fabric has changed.

       -s <err1,err2,...>
	      Suppress the errors listed in the comma separated list provided.

       -S <switch_guid>
	      Report results only for the switch specified. (hex format)

       -D <direct_route>
	      Report results only for the switch specified by the direct route path.

       -d     Include the optional transmit and receive data counters.

       -C <ca_name>    use the specified ca_name for the search.

       -P <ca_port>    use the specified ca_port for the search.

AUTHOR

       Ira Weiny
	      <weiny2@llnl.gov>

OpenIB								   Jan 24, 2008 						  IBQUERYERRORS(8)

IBTRACERT(8)							OpenIB Diagnostics						      IBTRACERT(8)

NAME

       ibtracert- trace InfiniBand path

SYNOPSIS

       ibtracert  [-d(ebug)]  [-v(erbose)]  [-D(irect)]  [-G(uids)]  [-n(o_info)] [-m mlid] [-s smlid] [-C ca_name] [-P ca_port] [-t(imeout) time-
       out_ms] [-V(ersion)] [--node-name--map <node-name-map>] [-h(elp)] [<dest dr_path|lid|guid> [<startlid> [<endlid>]]]

DESCRIPTION

       ibtracert uses SMPs to trace the path from a source GID/LID to a destination GID/LID. Each hop along the path is displayed until the desti-
       nation is reached or a hop does not respond. By using the -m option, multicast path tracing can be performed between source and destination
       nodes.

OPTIONS

       -n, --no_info
	      simple format; don't show additional information

       -m     show the multicast trace of the specified mlid

       --node-name-map <node-name-map>
	      Specify a node name map.	The node name map file maps GUIDs to more user friendly names.	See ibnetdiscover(8)  for  node  name  map
	      file format.

COMMON OPTIONS

       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).

       -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

       -D      use directed path address arguments. The path
	       is a comma separated list of out ports.
	       Examples:
	       "0"	       # self port
	       "0,1,2,1,4"     # out via port 1, then 2, ...

       -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.

EXAMPLES

       Unicast examples

       ibtracert 4 16		   # show path between lids 4 and 16

       ibtracert -n 4 16	   # same, but using simple output format

       ibtracert -G 0x8f1040396522d 0x002c9000100d051  # use guid addresses

       Multicast example

       ibtracert -m 0xc000 4 16    # show multicast path of mlid 0xc000 between lids 4 and 16

SEE ALSO

       ibroute(8)

AUTHOR

       Hal Rosenstock
	      <halr@voltaire.com>

       Ira Weiny
	      <weiny2@llnl.gov>

OpenIB								  April 14, 2007						      IBTRACERT(8)