ibsysstat(8)

💖 ibsysstat — system status on an InfiniBand address 💖

okay bestie, grab a snack because ibsysstat is literally the group chat of InfiniBand tools — it slides into another IB node's DMs, checks that the vibe (aka connectivity) is still there, and comes back with the tea. This is page 8 of the Open IB Diagnostics manual, and yeah, it's giving absolute icon behavior. 👑

---

✨ SYNOPSIS ✨

ibsysstat [options] <dest lid | guid> [<op>]

---

🌸 DESCRIPTION 🌸

So here's the deal, fr fr: ibsysstat uses vendor mads to validate connectivity between IB nodes, and to obtain other information about the IB node. That's the whole personality. It's basically a "u up?" text but for fabric nodes. 💌

And the way it works? ibsysstat runs as client/server, bestie. Default is to run as client — so if u don't say anything, you're the one knocking on the door, not the one answering it. Periodt.

---

🎀 OPTIONS 🎀

Current supported operations 🦋

These are the ops u can pass as that [<op>] at the end of the synopsis. Pick ur fighter:

• ping — verify connectivity to server (this is the default, the main character, the one that runs if u say nothing)
• host — obtain host information from server 🖥️
• cpu — obtain cpu information from server 🧠

Flags 💅

• -o, --oui — use specified OUI number to multiplex vendor mads
• -S, --Server — start in server mode. Heads up bestie: it does not return. Like, it commits. It's a lifestyle. Don't expect it to come back to u. 😭

Addressing Flags 🌈

• -G, --Guid — the address specified is a Port GUID
• -L, --Lid — the address specified is a LID
• -s, --sm_port <smlid> — use smlid as the target lid for SA queries.

Port Selection flags 👑

• -C, --Ca <ca_name> — use the specified ca_name.
• -P, --Port <ca_port> — use the specified ca_port.
• -Y, --pkey-idx <idx> — P_Key table index (0-65535, default 0) used for the outgoing SA/GMP MADs. and here's the lil plot twist — SMP (SMI directed-route/LID-routed) MADs always use P_Key index 0. no exceptions, not even for u. 💀

Local port Selection 🧚

Multiple port / Multiple CA support, aka: when no IB device or port is specified (peep the "local umad parameters" below), the libibumad library selects the port to use by the following criteria:

1. the first port that is ACTIVE.
2. if not found, the first port that is UP (physical link up).

And if a port and/or CA name is specified, the libibumad library attempts to fulfill the user request, and will fail if it is not possible. no vibes-based rescuing, it just says no. 🙈

For example:

ibaddr                 # use the first port (criteria #1 above)
ibaddr -C mthca1       # pick the best port from "mthca1" only.
ibaddr -P 2            # use the second (active/up) port from the first available IB device.
ibaddr -C mthca0 -P 2  # use the specified port only.

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, --help — show the usage message
• -v, --verbose — increase the application verbosity level. May be used several times (-vv or -v -v -v)
• -V, --version — show the version info.

Configuration flags ⭐

• -t, --timeout <timeout_ms> — override the default timeout for the solicited mads.
• --config, -z <config_file> — Specify alternate config file. Default: /etc/infiniband-diags/ibdiag.conf

---

📁 FILES 📁

CONFIG FILE 💜

/etc/infiniband-diags/ibdiag.conf

A global config file is provided to set some of the common options for all tools. See supplied config file for details.

---

🫶 AUTHOR 🫶

Hal Rosenstock < <halr@voltaire.com> >

---

okay that's the whole page, bestie, u ate that. this was the ibsysstat(8) page from Open IB Diagnostics, dated 2017-08-21 — the og drop, still iconic, still slaying. go ping something. 💖✨🎀