1IBDMCHK(1)                   IB DATA MODEL PACKAGE                  IBDMCHK(1)
2
3
4

NAME

6       IBDM - Network Checker and Attributes Analyzer
7

SYNOPSYS

9       ibdmchk has two operation modes: design and verification.
10
11       DESIGN:
12
13       ibdmchk [-v][-h][-u][-r <roots file>] -t <topology file> -n <SM Node>
14         -p <SM Port> [-e] [-l <lmc>]
15
16       VERIFICATION:
17
18       ibdmchk [-v][-h][-r <roots file>] [-s <subnet file>] [-f <fdb file>]
19         [-m <mcfdbs file> [-l <lmc>] [-u] [-M] [-a]
20         [-c <path sl file>] [-d <sl2vl tables file>]
21

DESIGN MODE DESCRIPTION

23       The Design mode is intended to be used before the cluster is built. It
24       provides basic checks of the specified network as described by a topol‐
25       ogy file. After simulating the SM LID assignment and routing algorithms
26       it provides reports of the (H)CA to (H)CA paths depth histogram and
27       credit deadlock potential in the resulting routing scheme.
28

ARGUMENTS:

30-t⎪--topo <topo file>
31The topology file specifying the network. See man ibdm-topology-file
32
33-n⎪--node <SM Node>
34The name of the Subnet Manager node (syntax: <Topo-File-System>/U1)
35
36-p⎪--port <SM Port>
37The port number by which the SM nodes is attached to the fabric.
38

OPTIONS

40-v⎪--verbose
41Verbsoe mode
42
43-h⎪--help
44Provides this help message
45
46-l⎪--lmc <lmc>
47LMC value > 0 means assigning 2^lmc lids to each port.
48
49-e⎪--enh
50Use enhanced routing algorithm when LMC > 0 and report the resulting paths
51correlation (using same system/node) histogram
52
53-r⎪--roots <roots file> A file with all the roots node names (one on each
54line).
55

VERIFICATION MODE DESCRIPTION

57       After the cluster is built and OpenSM is run (using flag -D 0x43) it
58       reports the subnet and FDB tables into the files osm-subnet.lst,
59       osm.fdbs and osm.fdbs in /var/log/ (or subnet.lst, osm.fdbs and
60       osm.mcfdbs into /tmp in older OpenSM versions). ibdiagnet is also pro‐
61       ducing the same files in its output directory.  Based on these files
62       the utility checks all CA to CA connectivity. Further analysis for
63       credit deadlock potential is performed and reported.  In case of an LMC
64       > 0 it reports histograms for how many systems and nodes are common
65       between the different paths for the same port pairs.
66

ARGUMENTS

68-l⎪--lmc <lmc>
69The LMC value used while running OpenSM. Mandatory if not the default 0.
70

OPTIONS

72-v⎪--verbose
73Verbsoe mode
74
75-h⎪--help
76Provides this help message
77
78-s⎪--subnet <file>
79OpenSM subnet.lst file (default is /var/log/osm-subnet.lst or /tmp/subnet.lst)
80
81-f⎪--fdb <file>
82OpenSM dump of Ucast LFDB. Use -D 0x41 to generate it (default is
83/var/log/osm.fdbs or /tmp/osm.fdbs).
84
85-m⎪--mcfdb <file>
86OpenSM dump of Multicast LFDB. Use -D 0x41 to generate it (default is
87/var/log/osm.mcfdbs or /tmp/osm.mcfdbs).
88
89-c⎪--psl <file>
90Source Guid to DLID -> Path SL mapping.  Each line holds: src_node_guid dlid
91sl.  Used by the credit loop check to accuartly model SL/VL based routing.
92
93-d⎪--slvl <file>
94SL2VL mapping of all switces.  Each line holds: swguid iport oport
950x(sl0)(sl1) 0x(sl2)(sl3)...  Used by the credit loop check to accuartly model
96SL/VL based routing.
97
98-r⎪--roots <roots file>
99A file holding all root nodes guids (one per line).
100
101-u⎪--updn
102Use Up/Down based credit loop check algorithm instead of the generic one.
103
104-M⎪--MFT
105Include multicast routing in credit loops analysis.
106
107-a⎪--all
108Verify not only CA-CA paths but also SW-SW, CA-SW and SW-CA.  Both check for
109FDB path connectivity and also for credit loops.
110

AUTHOR

112       Eitan Zahavi, Mellanox Technologies LTD, eitan@mellanox.co.il
113
114
115
116IBDM 1.0                          2009-03-17                        IBDMCHK(1)
Impressum