opafabricinfo(1)

💖 opafabricinfo(1) — IFSFFCLIRG (Man Page) 💖

okay bestie, welcome to the IFSFFCLIRG manual page for opafabricinfo(1), and honestly? she's that girl. she gives you the vibe check on your whole fabric, no cap.

---

✨ NAME ✨

opafabricinfo — gives you a lil summary of what's in your fabric, using the first active port on the given local host to do all the analyzing. 💅

opafabricinfo ships in two flavors, and they are not the same girl:

• Intel(R) Omni-Path Fabric Suite FastFabric Toolset — in this situation, the command can manage more than one fabric (subnet). multi-fabric main character energy 🫶
• FastFabric Tools — in this situation, the command performs analysis against the first active port on the system only. It takes no options and uses no environment variables. lowkey minimal, we respect it 🙈

opafabricinfo can be very useful as a quick assessment of the fabric state. fr fr — run it against a known good fabric to identify its components, then run it again later to see if anything has changed about the fabric configuration or state. it's giving before and after pics but for your subnet ✨

for more extensive fabric analysis, use opareport, opareports, and opatop. those tools can be found in the Intel(R) Omni-Path Fabric Suite FastFabric User Guide. like, if opafabricinfo is the cute lil recap, those three are the full dissertation 📚

---

🌸 Syntax

opafabricinfo [-t  portsfile] [-p  ports]

yes bestie, that's it. two flags. she's efficient like that. 👑

---

🎀 Options

• --help — produces full help text. the "bestie explain" button, basically.
• -t portsfile — specifies the file with list of local HFI ports used to access fabric(s) for analysis. the default is the /etc/opa/ports file. yes, that file.
• -p ports — specifies the list of local HFI ports used to access fabrics for analysis.

the default is the first active port. quick anatomy lesson, write it down 📝:

• the first HFI in the system is 1
• the first port on an HFI is 1
• uses the format hfi:port, for example:
• 0:0 — first active port in system.
• 0:y — port y within system.
• x:0 — first active port on HFI x.
• x:y — HFI x, port y.

slay. now you can point her wherever you want. 💅

---

🌈 Environment Variables

these lil guys are also used by this command, bestie, don't forget them:

• PORTS — list of ports, used in absence of -t and -p.
• PORTS_FILE — file containing list of ports, used in absence of -t and -p.

for simple fabrics, the Intel(R) Omni-Path Fabric Suite FastFabric Toolset host is connected to a single fabric. by default, the first active port on the FastFabric Toolset host is used to analyze the fabric. cute, easy, one-fabric life. 🦋

but… in more complex fabrics, the FastFabric Toolset host may be connected to more than one fabric or subnet. and in this case, you can specify the ports or HFIs to use with one of the following methods — pick your fighter:

• on the command line using the -p option.
• in a file specified using the -t option.
• through the environment variables PORTS or PORTS_FILE.
• using the ports_file configuration option in opafastfabric.conf.

⚠️ important caveat, no skipping: if the specified port does not exist or is empty, the first active port on the local system is used. and in more complex configurations, you must specify the exact ports to use for all fabrics to be analyzed. no vibes-based guessing allowed, bestie. specify. the. ports. 😤

---

🍓 Example

opafabricinfo

opafabricinfo -p '1:1 1:2 2:1 2:2'

⭐ Output example

# opafabricinfo

Fabric 0:0 Information:

SM: hds1fnb6241 hfi1_0 Guid: 0x0011750101575ffe State: Master

Number of HFIs: 8

Number of Switches: 1

Number of Links: 8

Number of HFI Links: 8              (Internal: 0 External: 8)

Number of ISLs: 0                   (Internal: 0 External: 0)

Number of Degraded Links: 0         (HFI Links: 0 ISLs: 0)

Number of Omitted Links: 0          (HFI Links: 0 ISLs: 0)

look at her go. absolutely iconic output. 👑

---

🧚 Output Definitions

so like, what does any of that actually mean? let's decode it, bestie:

• SM — each subnet manger (SM) running in the fabric is listed along with its node name, port GUID, and present SM state (Master, Standby, etc.). yes, the original says "manger". we're leaving it exactly as written. periodt. 💀
• Number of HFIs — number of unique host fabric interfaces (HFIs) in the fabric. an FI with two connected ports is counted as a single FI. so don't be out here double-counting, that's not the move.

NOTE: Fabric Interfaces include HFIs in servers as well as HFIs within I/O Modules, Native Storage, etc. she's inclusive like that 💖

• Number of Switches — number of connected switches in the fabric.
• Number of Links — number of links in the fabric. note that a large switch may have internal links. big switch, big secrets. 🤫
• Number of HFI Links — number of HFI links (Internal and External) in the fabric.
• Number of ISLs — number of Interswitch Links (Internal and External) in the fabric.
• Number of Degraded Links — number of degraded links (HSI and ISL) in the fabric. 🫠
• Number of Omitted Links — number of omitted links (HSI and ISL) in the fabric. 🫠

(and yes, those last two literally say HSI in the original and we are keeping it HSI, character for character, iykyk.)

---

and that's the whole page, bestie!! copyright vibes go out to Copyright(C) 2015-2019, Intel Corporation — thanks for the lore, Intel. 🌸 this has been your girl serving you opafabricinfo(1) from the IFSFFCLIRG man page set. go check your fabric, text me the numbers, mwah 💅💖✨