DUMP_FTS(8)

💅 DUMP_FTS — the dump_fts page, but make it make sense

okay bestie, so this is DUMP_FTS from the OpenIB Diagnostics crew. It's a man page (section 8, sysadmin business 💖) and it's about dumping InfiniBand forwarding tables. Let's get into it, no cap.

---

✨ SYNOPSIS ✨

dump_fts [options] [<startlid> [<endlid>]]

That's literally it. Options, then optionally a LID range. Slay.

---

🦋 DESCRIPTION 🦋

So dump_fts is giving very much ibroute's cooler sibling energy. The difference? ibroute does one switch. dump_fts goes and dumps tables for every single switch it finds in an ibnetdiscover scan of the subnet. Every. One. Main character behavior, honestly. 👑

And the dump file format? It's compatible with loading into OpenSM, using this syntax:

-R file -U /path/to/dump-file

So you can dump it and then feed it straight back to OpenSM. It's giving round-trip realness. 🔥

---

🎀 OPTIONS 🎀

• -a, --all — show all lids in range, even invalid entries. Yes, even the cursed ones. 🙈
• -n, --no_dests — do NOT try to resolve destinations. We're being lazy today and that's valid.
• -M, --Multicast — show multicast forwarding tables. Heads up bestie: in this case, the range parameters are specifying the mlid range. So <startlid> and <endlid> are doing double duty, iykyk.

🌸 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, range 0-65535, default 0, used for the outgoing SA/GMP MADs. And important: SMP (SMI directed-route/LID-routed) MADs always use P_Key index 0. No exceptions, periodt.

💜 Local port Selection 💜

Multiple port / Multiple CA support, okay so listen: when you don't specify an IB device or port (peep the "local umad parameters" situation below), 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).

If a port and/or CA name is specified, the libibumad library attempts to fulfill the user request, and it will fail if it is not possible. It's not gonna guess for you. 💀

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.

See how it escalates? Very demure, very mindful, very specific. ✨

🐛 Debugging flags 🐛

• -d — raise the IB debugging level. May be used several times (-ddd or -d -d -d). Stack it like a good playlist.
• -e — show send and receive errors (timeouts and others). The receipts. 🧾
• -h, --help — show the usage message.
• -v, --verbose — increase the application verbosity level. May be used several times (-vv or -v -v -v). Yap mode: unlocked.
• -V, --version — show the version info.

⭐ Configuration flags ⭐

• -t, --timeout <timeout_ms> — override the default timeout for the solicited mads.
• -y, --m_key <key> — use the specified M_key for requests. And btw: if a non-numeric value (like 'x') is specified, then a value will be prompted for. Interactive era. 🙈
• --node-name-map <node-name-map> — Specify a node name map. This file maps GUIDs to more user friendly names. See the FILES section below, bestie.
• --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 the supplied config file for details. It's the group chat settings of the diagnostic world. 💅

🧚 NODE NAME MAP FILE FORMAT 🧚

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

This functionality is provided by the opensm-libs package. See opensm(8) for the file location for your installation.

Generically:

# 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"

Look at all those friendly names. Ate. 🎀

---

👀 SEE ALSO 👀

dump_lfts(8), dump_mfts(8), ibroute(8), ibswitches(8), opensm(8)

Go read them too, they're all part of the same friend group, fr fr. 🫶

---

👑 AUTHORS 👑

Ira Weiny

<ira.weiny@intel.com>

---

okay that's the whole page, bestie. you're now certified in forwarding table dumping. go forth and dump_fts. 💖

This gem was brought to you by the OpenIB Diagnostics gang, dated 2013-03-26, and it still slays to this day. 🌸✨