^(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 MLNX_OFED version, please refer to MLNX_OFED Release Notes.

From RedHat 9* and onwards, packages with SHA1 signatures are no longer supported. The CONDA package binary is signed with SHA1 signatures and thus, CONDA will not be installed with RedHat 9*.

Two options are available to overcome this.

1. Recommended Option: Run the following command to install Conda (change gpgcheck from 1 to 0): 

   cat <<EOF > /etc/yum.repos.d/conda.repo
   [conda]
   name=Conda
   baseurl=https://repo.anaconda.com/pkgs/misc/rpmrepo/conda
   enabled=1
   gpgcheck=0
   gpgkey=https://repo.anaconda.com/pkgs/misc/gpgkeys/anaconda.asc
   EOF
   
   #install conda
   yum install conda

2. Alternative Option: Run the following command to set the RedHat 9* system-wide cryptographic policy to use legacy (less-secured) policy:

   update-crypto-policies --set LEGACY

   Install Conda as instructed by the UFM installation script.
   After Conda installation, the policy can be set back to default by running the following command: 

   update-crypto-policies --set DEFAULT

For running SHARP Aggregation Manager within UFM, it is recommended to use MLNX_OFED-5.4.X version or newer.

Installation of UFM on minimal OS distribution is not supported.

UFM does not support systems in which NetworkManager service is enabled.

Before installing UFM on RedHat OS, make sure to disable the service.  

Due to a possible conflict, SM and SHARP installed by the MLNX_OFED must be uninstalled. The installation procedure will detect and print all MLNX_OFED packages that must be removed.

It is recommended to upgrade to the latest UFM version from the last 2 GA releases that came before it. Upgrading from older UFM versions may result in failures.