IBHOSTS(8)

🌸 IBHOSTS — the OpenIB Diagnostics glow-up 🦋

okay bestie, pull up a chair because today we're talking about ibhosts, part of the OpenIB Diagnostics fam 💅 no cap, this one is a little icon.

---

✨ Name ✨

IBHOSTS — literally just show me the InfiniBand host nodes in the topology, periodt 💖

---

🎀 SYNOPSIS 🎀

ibhosts [options] [<topology-file>]

---

💜 DESCRIPTION 💜

so ibhosts is a script, right? and it does one of two things depending on the vibe:

• it either walks the IB subnet topology itself 🚶♀️✨
• or it uses an already saved topology file you hand it and just extracts the CA nodes from that 👑

like. it's giving "I already know the subnet, I just want the CAs." iconic honestly.

---

🔥 OPTIONS 🔥

• -C, --Ca <ca_name> — use the specific ca_name you picked, bestie 🫶
• -P, --Port <ca_port> — use the specific ca_port you picked ✨
• -t, --timeout <timeout_ms> — override the default timeout for the solicited mads ⏰
• -y, --m_key <key> — use this M_key for requests. and listen — if you give it something non-numeric (like 'x'), it's gonna prompt you for a value instead 👀
• -h, --help — show the usage message, the classic 💅
• --config, -z <config_file> — specify an alternate config file. Default: /etc/infiniband-diags/ibdiag.conf 📁

---

🌈 Local port Selection 🌈

okay this part is so real. Multiple port / Multiple CA support: when you don't specify an IB device or port (peep the "local umad parameters" below, iykyk), the libibumad library picks the port for you using these criteria:

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

and then: if you do specify a port and/or a CA name, libibumad will try its hardest to fulfill your request — but it will fail if it's not possible 😭 no soft landings.

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.

---

🦋 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 the supplied config file for details 📖✨

---

🌸 NODE NAME MAP FILE FORMAT 🌸

The node name map is used to specify user friendly names for nodes in the output 🥰 GUIDs are what perform the lookup.

This functionality is provided by the opensm-libs package. See opensm(8) for where the file lives on your installation 👑

Generically, it looks like this:

# comment
<guid> "<name>"

Example:

# IB1
# Line cards
0x0008f104003f125c "IB1 (Rack 11 slot 1   ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f125d "IB1 (Rack 11 slot 1   ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10d2 "IB1 (Rack 11 slot 2   ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10d3 "IB1 (Rack 11 slot 2   ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10bf "IB1 (Rack 11 slot 12  ) ISR9288/ISR9096 Voltaire sLB-24D"

# Spines
0x0008f10400400e2d "IB1 (Rack 11 spine 1   ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e2e "IB1 (Rack 11 spine 1   ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e2f "IB1 (Rack 11 spine 1   ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e31 "IB1 (Rack 11 spine 2   ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e32 "IB1 (Rack 11 spine 2   ) ISR9288 Voltaire sFB-12D"

# GUID   Node Name
0x0008f10400411a08 "SW1  (Rack  3) ISR9024 Voltaire 9024D"
0x0008f10400411a28 "SW2  (Rack  3) ISR9024 Voltaire 9024D"
0x0008f10400411a34 "SW3  (Rack  3) ISR9024 Voltaire 9024D"
0x0008f104004119d0 "SW4  (Rack  3) ISR9024 Voltaire 9024D"

---

👀 SEE ALSO 👀

ibnetdiscover(8)

---

🧚 DEPENDENCIES 🧚

ibnetdiscover, ibnetdiscover format 🌈

---

👑 AUTHOR 👑

Hal Rosenstock < <halr@voltaire.com> >

---

and that's the whole page bestie, slay 💅✨ this one's dated 2016-12-20 and it's part of OpenIB Diagnostics — mkay love u bye 🫶💖