Plan fabric operations alongside an externally managed InfiniBand switch
QM9790 and UFM family-level operations; no implied UFM license bundle or unverified exact appliance mapping.
Plan fabric operations alongside an externally managed InfiniBand switch
NVIDIA’s QM97XX manual describes QM9790 as externally managed and distinguishes it from the internally managed QM9700/QM9701. That matters when planning how a fabric will be brought up, monitored and maintained. The switch’s data-plane port count does not answer the management question.
The manual describes UFM’s role in fabric operations. Separately, the UFM Cyber-AI appliance overview describes telemetry analysis and anomaly-detection functions. Treat those as software and appliance design choices requiring their own configuration and entitlement checks, rather than assuming they are included with every switch.
A public NVIDIA Developer Forums question illustrates a real operational detail: an operator asked how to find the uptime of an unmanaged QM9790. A reply suggested mlxuptime using the switch LID and checking OpenSM discovery/removal logs. This is one observed question, not evidence of a most-asked issue or a measured customer outcome.
For selection, record who operates the subnet manager, how telemetry is collected, what versioned tools are available, and which support path owns troubleshooting. Those decisions make the hardware specification more useful without inventing performance improvements.
Scope: QM9790 and UFM family-level operations; no implied UFM license bundle or unverified exact appliance mapping.