Poster of Linux kernelThe best gift for a Linux geek
IBTRACERT

IBTRACERT

Section: OpenIB Diagnostics (8) Updated: April 14, 2007
Local index Up

 

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) timeout_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 destination 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>


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
COMMON OPTIONS
EXAMPLES
SEE ALSO
AUTHOR

This document was created by man2html, using the manual pages.
Time: 22:01:46 GMT, April 16, 2011