Components Bundled with UFM
|
Component |
Version |
|---|---|
|
MFT |
4.38.0-134 (integrated) |
|
SM |
5.29.1 |
|
NVIDIA® Scalable Hierarchical Aggregation and Reduction Protocol (SHARP)™ |
3.16.3 |
Supported Devices
|
Management Type |
Type |
Model |
Latest Tested Firmware / OS Version |
|---|---|---|---|
|
Externally managed |
NDR |
MQM9790 |
FW 31.2016.2054 |
|
HDR |
MQM8790 |
FW 27.2014.2428 |
|
|
EDR |
SB7790
|
FW 15.2010.4402 |
|
|
Internally managed |
XDR |
Q3200_RA
|
NVOS 25.03.1010 |
|
NDR |
MQM9700
|
MLNX-OS 3.12.6300 |
|
|
HDR |
MQ8700
|
MLNX-OS 3.12.2002 |
|
|
EDR |
SB7700
|
MLNX-OS 3.10.5002 |
System Requirements
Server Resources per Cluster Size
|
Fabric Size |
CPU Requirements |
Memory Requirements |
Disk Space Requirements |
|
|---|---|---|---|---|
|
Minimum |
Recommended |
|||
|
Up to 1000 nodes |
16-core server |
16 GB |
100 GB |
500 GB |
|
1000-5000 nodes |
32-core server |
64 GB |
250 GB |
1000 GB (1 TB) |
|
5000-10000 nodes |
64-core server |
64 GB |
1000 GB |
2000 GB (2 TB) |
|
Above 10000 nodes |
64-core server |
64 GB |
2000 GB |
4000 GB (4 TB) |
Bare Metal Deployment
|
Platform |
Type and Version |
|---|---|
|
OS (standalone and High-Availability deployments) |
64-bit OS:
|
|
CPU(a) |
x86_64 |
|
HCAs(c) |
NVIDIA ConnectX®-5, Firmware 16.35.8008 NVIDIA ConnectX®-6, Firmware 20.43.8016 NVIDIA ConnectX®-7, Firmware 28.51.1002 NVIDIA ConnectX®-8, Firmware 40.51.1002 NVIDIA BlueField-2, Firmware 24.51.1002 NVIDIA BlueField-3, Firmware 32.51.1002 |
|
DOCA Host(b) |
|
(a) CPU requirements refer to resources consumed by UFM. You can also dedicate a subset of cores on a multicore server. For example, 4 cores for UFM on a 16-core server.
(b) For supported HCAs in each DOCA Host version, see DOCA Host Release Notes.
Docker Deployment
UFM Docker Container is supported on the standard Docker environment (engine). The following operating systems were tested with Docker Container (as standalone container):
|
Component |
Type and Version |
|---|---|
|
Supported OS |
RHEL8
|
For UFM Docker Container installation in HA mode, see the Bare Metal Deployment Requirements for the list of operating systems and kernels which support HA. See Installing Docker and Podman for the installation steps.
Podman Deployment
Podman is tested on the Oracle Linux 8.10 distribution. See Installing Docker and Podman for the installation steps.
UFM GUI Client
|
Platform |
Details |
|---|---|
|
Browser |
Edge, Firefox, Chrome, Opera, Safari |
|
Memory |
Minimum: 8 GB
|
Ports Used by UFM Server
For a list of ports used by the UFM Server for internal and external communication, see Used Ports.
Pre-Installation Requirements and Notes
Before installing, make sure that:
-
UFM is not being installed on a minimal OS distribution. This is not supported.
-
The NetworkManager service is disabled. UFM does not support systems in which it is enabled, and on Red Hat OS it must be disabled before installing UFM.
-
SM and SHARP installed by MLNX_OFED are uninstalled, due to a possible conflict. The installation procedure detects and prints all MLNX_OFED packages that must be removed.
Recommendations:
-
For running SHARP Aggregation Manager within UFM, use DOCA-Host.
-
Fabric isolation: assuming the SM is connected to the production cluster, it can handle any events (IB traps) coming from the fabric that is being built; such events should not affect the routing on the production cluster. If events occurred in the production cluster, the routing could be changed. NVIDIA recommends isolating fabric sections to allow faster bring-ups, faster troubleshooting and misconfiguration avoidance that can cause routing errors. Isolation provides clearer SM and CollectX logs, avoiding warnings/errors from masking real production issues.
Installing Docker and Podman
Fixing Docker Installed via Snap (Ubuntu)
On some Ubuntu OSs, Docker is installed via SNAP, which might lead to errors when trying to use UFM Plugins. To solve this issue:
-
Remove Docker installed via SNAP:
snap remove --purge docker -
Update the local package index:
apt update -
Install native Docker:
apt install -y docker.io
Installing Podman
Since Docker and Podman are mutually exclusive, ensure that any existing Docker packages are removed before installing Podman:
yum remove $(rpm -qa | grep docker)
Install Podman and the Podman Docker-compatible CLI:
dnf install podman podman-docker
Enable and start the Podman socket to allow for socket-based communication:
systemctl enable --now podman.socket
After installing Podman, the deployment of UFM Docker Containers and UFM Plugins should function in the same way as the corresponding Docker deployments.
Software Update from Prior Versions
-
The installer detects versions previously installed on the machine and prompts you to run a clean install of the new version or to upgrade while keeping user data and configuration unchanged.
-
The upgrade from previous versions maintains the existing database and configuration, allowing a seamless upgrade process.
-
Upgrading UFM Enterprise software version is supported up to two previous GA software versions (GA -1 or -2). For example, to upgrade to UFM Enterprise v6.17.0, you can do so only from v6.16.0 or v6.15.0.
-
Before upgrading, make sure SM and SHARP installed by DOCA-Host are removed (see Pre-Installation Requirements and Notes).
Last updated: