A water-utility team must validate InfiniBand inventory against the live fabric map. Which tools should they use?
Select an answer to reveal the explanation.
Short Explanation
Need a live IB street map for the water utility? Use ibnodes and iblinkinfo — they list InfiniBand nodes and how the links actually stitch together, not how someone hoped they would.
Full Explanation
A water-utility team validating InfiniBand inventory against the live fabric map needs tools that query the InfiniBand subnet itself. ibnodes discovers InfiniBand node membership visible to the subnet, while iblinkinfo reports how those nodes interconnect—link endpoints, widths, and related topology detail—so inventory records can be checked against what the municipal fabric actually presents. Together they provide an authoritative InfiniBand street map for civic asset validation. SNMP polling of Spectrum switches for Ethernet interface counters only captures Ethernet interface counters on Spectrum devices and misses HCA/switch membership on the IB side of a hybrid AI factory. Kubernetes Network Operator events for GPU node provisioning status reflect cluster provisioning state and overlay networking, not the InfiniBand subnet’s node and link database. NVUE configuration snapshots for Spectrum Ethernet policy validation describe intended Spectrum Ethernet configuration, not live InfiniBand topology. Exam caveat: ibnodes and iblinkinfo depend on SM reachability and correct local IB stack state; if the host cannot talk to the fabric, fix local HCA/port issues first, then re-run discovery. Operational check: run ibnodes and iblinkinfo from a trusted water-utility management host, export or compare the discovered node and link list to the inventory CMDB, and flag mismatches (missing GUIDs, unexpected neighbors, downed links) before declaring the fabric map validated.