Nvidia Support

The ONNX-Cuda runtime is available on both x86_64 machines (for eg. machines with Nvidia RTX 4090, A100, etc.) and AARCH64 machine (for eg. Jetson Orin AGX, Jetson Xavier NX, etc.).

Operating conditions

For the AI Manager to work on the machine with Nvidia GPUs, the machine needs to have CUDA properly installed, in which case these conditions needs to be met:

On X86_64

1. This file /proc/driver/nvidia/version needs to be available.

2. This file /usr/local/cuda/version.json needs to be available and contain the install CUDA version. An example of the file should like this:

   {
      "cuda" : {
         "name" : "CUDA SDK",
         "version" : "12.2.20230823"
      },
      ...
   }

3. The nvidia-smi command should be installed and has to be compatible with the installed Nvidia drivers.

On AARCH64

• A compatible JetPack version needs to be installed. You can verify that by running this command:

  dpkg-query --showformat='${Version}' --show nvidia-l4t-core

The command returns the version of the installed NVIDIA JetPack SDK.

Installing the runtime manually

Before trying to install the runtime, make sure that the Nvidia GPU and CUDA version are supported by reviewing this table, and that they correctly installed by checking the conditions above.

First setup to setup the runtime manually is to download the correct runtime library for the relevant machine using one of the links below:

For X86_64

• CUDA 11

• CUDA 12

For AARCH64

• Jetpack 4.6

• Jetpack 5.x

• Jetpack 6.0

When the download is complete, unpack the archive in this directory using this command:

tar -xf <archive-path> -C /opt/networkoptix-metavms/mediaserver/bin/plugins/nxai_plugin/nxai_manager/bin

then, create a file named installed_runtime.txt in the same directory and set its content as ONNX-CUDA using this command:

echo "ONNX-CUDA" > /opt/networkoptix-metavms/mediaserver/bin/plugins/nxai_plugin/nxai_manager/bin/installed_runtime.txt

After that, for changes to take effect, restart the Nx server using this command:

sudo systemctl restart networkoptix-metavms-mediaserver.service

Troubleshooting

For systems using NVIDIA's JetPack SDK, especially recent installations, the networkoptix-metavms user might not automatically be added to the render group. This group membership is essential for the Network Optix AI Manager plugin to fully utilize NVIDIA GPUs for hardware acceleration. While this process will be automated in a future Nx Server release, for now, you can manually add the user to the render group by following these steps:

1. Check if the 'render' Group Exists

First, verify whether the render group exists on your system:

getent group render

• Expected Output

  If the render group exists, you will see output similar to:

  render:x:104:username

  This indicates that the group exists and lists the users currently in the group.

• No Output

  If there's no output, the render group does not exist on your system. In this case, there's no need to continue with the next steps. Y

2. Add 'networkoptix-metavms' to the 'render' Group

• Run the following command to add the user to the render group:

  sudo usermod -aG render networkoptix-metavms

  Explanation of the Command:

  • sudo runs the command with administrative privileges.

  • usermod is used to modify user accounts.

  • -aG appends the user to the specified group(s) without removing them from others.

  • render is the group you're adding the user to.

  • networkoptix-metavms is the username for the Network Optix VMS user.

3. Verify the Group Membership

Confirm that the networkoptix-metavms user has been added to the render group:

groups networkoptix-metavms

• Expected Output

  The command will list all groups the user is a part of. You should see render included in the list.

4. Restart the Network Optix Service

For the changes to take effect, restart the Network Optix media server service:

sudo systemctl restart networkoptix-mediaserver.service

• This command restarts the service, allowing it to recognize the updated group permissions.

If the AI Manager doesn't work even when the conditions above are met, please refer to our general troubleshooting section.