IBDMCHK(1)

📦
version 1.5.7+0.2.gbd7e502 · 5 versions
, in ubuntu noble, ubuntu questing

💖 IBDMCHK(1) — bestie, let's get into ibdmchk 💖

Hiii okay so this is the manual page for IBDMCHK(1), from the IB DATA MODEL PACKAGE, and the official NAME on the birth certificate is:

IBDM - Network Checker and Attributes Analyzer

So it checks your network and analyzes attributes. Double threat. Main character energy, no cap. 🌈✨

✨ SYNOPSYS ✨

okay so ibdmchk has two operation modes: design and verification. two moods, both iconic. 💅

DESIGN:

ibdmchk [-v][-h][-u][-r <roots file>] -t <topology file> -n <SM Node>
  -p <SM Port> [-e] [-l <lmc>]

VERIFICATION:

ibdmchk [-v][-h][-r <roots file>] [-s <subnet file>] [-f <fdb file>]
  [-m <mcfdbs file> [-l <lmc>] [-u] [-M] [-a]
  [-c <path sl file>] [-d <sl2vl tables file>]

🎀 DESIGN MODE DESCRIPTION 🎀

The Design mode is literally meant to be used before the cluster is even built — like picking the fit before the party, bestie. 🦋

It gives you basic checks of the network you specified, as described by a topology file. Then, after simulating the SM LID assignment and routing algorithms, it hands you reports of:

  • the (H)CA to (H)CA paths depth histogram 📊
  • the credit deadlock potential in the resulting routing scheme 💀
Not me simulating your whole fabric before it exists. Obsessed.

🔍 ARGUMENTS:

  • -t, --topo <topo file> — the topology file that specifies the network. See man ibdm-topology-file for the deets. 🗺️
  • -n, --node <SM Node> — the name of the Subnet Manager node (syntax: <Topo-File-System>/U1). 👑
  • -p, --port <SM Port> — the port number by which the SM node is attached to the fabric. 🔌

⚙️ OPTIONS ⚙️

  • -v, --verbose — verbose mode. all the tea, none of the chill 🍵
  • -h, --help — provides this help message. say it back 🫶
  • -l, --lmc <lmc> — an LMC value > 0 means assigning 2^lmc lids to each port. ✨
  • -e, --enh — use the enhanced routing algorithm when LMC > 0, and report the resulting paths correlation (using same system/node) histogram. 💫
  • -r, --roots <roots file> — a file with all the roots node names (one on each line). 🌱

🔎 VERIFICATION MODE DESCRIPTION 🔎

So after the cluster is built and OpenSM has been run (using flag -D 0x43), it reports the subnet and FDB tables into the files osm-subnet.lst, osm.fdbs and osm.fdbs in /var/log/ — or, on older OpenSM versions, subnet.lst, osm.fdbs and osm.mcfdbs into /var/cache/ibutils. 🗂️

ibdiagnet is also producing the same files in its output directory. 🧚

Based on these files, the utility checks all CA to CA connectivity. Further analysis for credit deadlock potential is performed and reported. And in case of an LMC > 0, it reports histograms for how many systems and nodes are common between the different paths for the same port pairs. 📈

🔍 ARGUMENTS

  • -l, --lmc <lmc> — the LMC value used while running OpenSM. Mandatory if it's not the default 0. don't skip it, bestie, it's not optional-optional 🙈

⚙️ OPTIONS ⚙️

  • -v, --verbose — verbose mode. louder, more tea 🍵
  • -h, --help — provides this help message. iconic behavior 💅
  • -s, --subnet <file> — OpenSM subnet.lst file (default is /var/log/osm-subnet.lst or /var/cache/ibutils/subnet.lst). 🗂️
  • -f, --fdb <file> — OpenSM dump of Ucast LFDB. Use -D 0x41 to generate it (default is /var/log/osm.fdbs or /var/cache/ibutils/osm.fdbs). 📄
  • -m, --mcfdb <file> — OpenSM dump of Multicast LFDB. Use -D 0x41 to generate it (default is /var/log/osm.mcfdbs or /var/cache/ibutils/osm.mcfdbs). 📬
  • -c, --psl <file> — Source Guid to DLID -> Path SL mapping. Each line holds: src_node_guid dlid sl. Used by the credit loop check to accurately model SL/VL based routing. 🧵
  • -d, --slvl <file> — SL2VL mapping of all switches. Each line holds: swguid iport oport 0x(sl0)(sl1) 0x(sl2)(sl3)... Used by the credit loop check to accurately model SL/VL based routing. 🧶
  • -r, --roots <roots file> — a file holding all root nodes guids (one per line). 🌱
  • -u, --updn — use the Up/Down based credit loop check algorithm instead of the generic one. ⬆️⬇️
  • -M, --MFT — include multicast routing in the credit loops analysis. 📡
  • -a, --all — verify not only CA-CA paths but also SW-SW, CA-SW and SW-CA. Both check for FDB path connectivity and for credit loops. the full sweep, periodt 🔥

👑 AUTHOR 👑

Eitan Zahavi, Mellanox Technologies LTD, eitan@mellanox.co.il 💌

okay that's the whole page, bestie, you ate it. 🫶

and for the cute sign-off: this was IBDM 1.0, dated 2024-04-22 — write it in your notes, it's giving vintage and it's giving accurate. 🎀🦋💖

📦 where this page comes from