AMD in-band SSH
Intel in-band SSH
Nvidia in-band SSH
All GPU vendors in-band Auto
Metrics and attributes for out-band monitoring
Matrix of metrics and attributes for in-band monitoring
Introduction:
Entuity supports in-band and out-band monitoring of the AMD, Intel, and Nvidia GPUs in your managed servers. Based on the type of monitoring, some GPUs have specific requirements for being able to poll performance metrics. Prerequisites and configuration instructions for each GPU vendor and monitoring type follow, along with the metrics provided by each monitoring type.
Prerequisite
- If the GPUs that you want to monitor are in a Linux server, ensure that
Sudois installed on the server before attempting to monitor the GPUs.
To configure GPU monitoring:
All GPU vendors out-band:
To perform out-band monitoring of GPUs from all supported vendors, Entuity uses certain server hardware collectors along with a server hardware monitoring user account.
To configure out-band monitoring of GPUs from all supported vendors:
- Add the server to Entuity for hardware monitoring as you normally would. No further configuration is required. If the associated server hardware collector can discover GPUs in the server, the GPUs are displayed on server dashboards and dashlets in the UI.
For more information on which server hardware collectors can discover GPU information for out-band monitoring, see this article.
For more information on adding a server to your network, see this article.
AMD in-band SSH
To perform in-band monitoring of AMD GPUs through SSH, Entuity uses the amd-smi utility and a server OS monitoring user account. Keep in mind that the OS monitoring user account must have SSH access and must be able to run the amd-smi utility.
To install the amd-smi utility and configure AMD GPU in-band SSH monitoring:
- Follow the instructions in the AMD SMI documentation to install the amd-smi utility.
Note, only the amd-smi CLI is required. - If you haven't already done so, create an OS monitoring user account for the server, as described in this article.
- Ensure that the OS monitoring user account can run the amd-smi utility.
- When adding the server to Entuity, scroll to the OS Monitoring section of the Add Asset form, and do the following:
- Click the Credential field, and in the Local Credentials section of the Credential form that is displayed, enter the OS monitoring account username, password, and SSH key (if used) in the appropriate fields.
- In the GPU Connection Method dropdown field, select AMD GPU (SSH).
For more information on adding a server to your network, see this article.
Intel in-band SSH:
To perform in-band monitoring of Intel GPUs through SSH, Entuity uses the xpu-smi utility, the hl-smi utility, and a server OS monitoring user account. Keep in mind that the OS monitoring user account must have SSH access and must be able to run the xpu-smi and/or hl-smi utilities.
Note, the xpu-smi utility runs on Linux and Windows.
Installing the Intel GPU utilities:
- The xpu-smi utility is included in Intel's XPU Manager. For more information on supported operating system versions and installation instructions for XPU Manager, see the Intel XPU Manager documentation.
- The hl-smi utility is automatically installed when you set up the official Intel Gaudi Driver and Software Stack.
To configure Intel GPU in-band SSH monitoring:
- If you haven't already done so, create an OS monitoring user account for the managed server, as described in this article for Linux and this article for Windows, based on the OS of the managed server.
- Ensure that the OS monitoring user account can run the xpu-smi and hl-smi utilities.
- When adding the server to Entuity, scroll to the OS Monitoring section of the Add Asset form, and do the following:
- Click the Credential field, and in the Local Credentials section of the Credential form, enter the OS monitoring account username, password, and SSH key (if being used) in the appropriate fields.
- In the GPU Connection Method dropdown field, select Intel GPU (SSH).
For more information on adding a server to your network, see this article.
Nvidia in-band SSH:
To perform in-band monitoring of Nvidia GPUs through SSH, Entuity uses the required nvidia-smi utility (which is bundled in the Nvidia Graphics driver), the optional dcgmi utility (with the nv-hostengine service), and a server OS monitoring user account. Keep in mind that the OS monitoring user account must have SSH access and must be able to run the nvidia-smi and dcgmi utilities.
Note, the dcgmi utility is not required but is needed if you want Entuity to discover graphics/SM/tensor/DRAM activity, fabric switches, and SM occupancy for MIG instances. To list MIG instance profile names, the OS monitoring user account requires root or passwordless sudo. Without these privileges, MIG instances are still discovered in Entuity, but without profile names.
The nvidia-smi utility ships with the Nvidia official display drivers.
To install the dcgmi utility and configure Nvidia GPU in-band SSH monitoring:
- Follow the instructions in the Nvidia DCGM documentation to install the dcgmi utility.
- If you haven't already done so, create an OS monitoring user account for the managed server, as described in this article for Linux and this article for Windows, based on the OS of the managed server.
- Ensure that the OS monitoring user account can run the nvidia-smi and dcgmi utilities.
- When adding the server to Entuity, scroll to the OS Monitoring section of the Add Asset form, and do the following:
- Click the Credential field, and in the Local Credentials section of the Credential form, enter the OS monitoring account user name, password, and SSH key (if being used) in the appropriate fields.
- In the GPU Connection Method dropdown field, select NVIDA GPU (SSH).
For more information on adding a server to your network, see this article.
All GPU vendors in-band Auto:
When you first add a server to Entuity and you plan to monitor the GPUs in that server, Entuity provides the option to automatically detect the GPU vendor types and use the appropriate vendor utilities on the managed server to discover the GPUs for monitoring.
To perform this automatic in-band monitoring of GPUs through SSH, Entuity uses the required GPU vendor utilities on the server and a server OS monitoring user account. Keep in mind that the OS monitoring user account must have SSH access and must be able to run the required vendor utilities, based on the GPU vendor type.
To install the required GPU utilities and configure automatic GPU in-band monitoring:
- See the AMD, Intel, and Nvidia sections earlier in this article and follow the instructions in each section to install each of the required GPU vendor utilities on the managed server.
- If you haven't already done so, create an OS monitoring user account for the managed server, as described in this article for Linux and this article for Windows, based on the OS of the managed server.
- Ensure that the managed the OS monitoring user account can run all of the utilities.
- When adding the server to Entuity, scroll to the OS Monitoring section of the Add Asset form, and do the following:
- Click the Credential field, and in the Local Credentials section of the Credential form that is displayed, enter the OS monitoring account user name, password, and SSH key (if being used) in the appropriate fields.
- In the GPU Connection Method dropdown field, select Auto.
For more information on adding a server to your network, see this article.
Metrics and attributes for out-band monitoring
- Component Name
- Vendor
- Model
- Serial Number
- Part Number
- Component Type
- Version
- Firmware Version
- Slot
- Location
- Description
- GPU Temperature
- Memory Temperature
- Power Usage
- Operating Speed
- Bandwidth Percent
- Memory Speed
- Memory Bandwidth Percent
- Correctable Error Count
- SM Utilization Percent
- SM Activity Percent
- SM Occupancy Percent
- Tensor Core Activity Percent
- HMMA Utilization Percent
- PCIe Raw Tx Bandwidth
- PCIe Raw Rx Bandwidth
- IMMA Utilization Percent
- DMMA Utilization Percent
- Current PCIe Link Speed
- Max Supported PCIe Link Speed
- DRAM Utilization Percent
- Link Tx Throughput
- Link Rx Throughput
- Link Count
- State / State Detail
Matrix of metrics and attributes for in-band monitoring:
The following table lists the metrics available for each type of monitoring.
Note, this table lists all possible metrics. Based on the driver/utility versions and the GPU vendor type, some of the metrics shown might not be available.
| Attributes | AMD GPU in-band SSH |
Intel GPU in-band SSH |
Nvidia GPU in-band SSH |
|---|---|---|---|
| GPU Device | |||
| Component Name | ✓ | ✓ | ✓ |
| Component ID | ✓ | ✓ | ✓ |
| Accelerator ID | ✓ | ✓ | ✓ |
| UUID | ✓ | ✓ | ✓ |
| PCI Bus ID | ✓ | ✓ | ✓ |
| Serial # | ✓ | ✓ | ✓ |
| Vendor | ✓ | ✓ | ✓ |
| Part Number | ✓ | ✓ | N/A |
| Component State | ✓ | ✓ | ✓ |
| Component State Detail | ✓ | ✓ | ✓ |
| Fan Speed | ✓ | N/A | ✓ |
| VBIOS | ✓ | ✓ | ✓ |
| InfoROM | N/A | ✓ | ✓ |
| Driver Version | ✓ | ✓ | ✓ |
| Compute Capability | ✓ | ✓ | ✓ |
| MIG Mode | N/A | N/A | ✓ |
| Accelerator Utilization (%) | ✓ | ✓ | ✓ |
| Memory Utilization (%) | ✓ | ✓ | ✓ |
| Power Utilization (%) | ✓ | ✓ | ✓ |
| Accelerator Temperature | ✓ | ✓ | ✓ |
| Memory Temperature | ✓ | ✓ | ✓ |
| Memory Total | ✓ | ✓ | ✓ |
| Memory Used | ✓ | ✓ | ✓ |
| Memory Free | ✓ | ✓ | ✓ |
| Power Usage | ✓ | ✓ | ✓ |
| Maximum Power Limit | ✓ | N/A | ✓ |
| Power Limit | ✓ | ✓ | ✓ |
| Shutdown Temperature | ✓ | ✓ | ✓ |
| Slowdown Temperature | ✓ | ✓ | ✓ |
| Clock Frequencies SM | ✓ | ✓ | ✓ |
| Clock Frequencies Memory | ✓ | N/A | ✓ |
| Clock Frequencies Graphics | N/A | N/A | ✓ |
| PCIe Throughput (PCIe TX) | ✓ | ✓ | ✓ |
| PCIe Throughput (PCIe RX) | ✓ | ✓ | ✓ |
| Maximum SM Clock | ✓ | ✓ | ✓ |
| Maximum Memory Clock | ✓ | N/A | ✓ |
| Total Corrected ECC Errors | ✓ | ✓ | ✓ |
| Total Uncorrected ECC Errors | ✓ | ✓ | ✓ |
| GPU Instance | |||
| Component State | ✓ | ✓ | ✓ |
| Component State Detail | ✓ | ✓ | ✓ |
| Accelerator ID | ✓ | ✓ | ✓ |
| ID | ✓ | ✓ | ✓ |
| Entity ID | ✓ | ✓ | ✓ |
| Instance ID | ✓ | ✓ | ✓ |
| Profile | ✓ | N/A | ✓ |
| Framebuffer Memory Total | ✓ | N/A | ✓ |
| Framebuffer Memory Free | ✓ | N/A | ✓ |
| Framebuffer Memory Used | ✓ | N/A | ✓ |
| GR Engine (%) | ✓ | N/A | ✓ |
| SM Active (%) | N/A | N/A | ✓ |
| SM Occupancy (%) | N/A | N/A | ✓ |
| Tensor (%) | N/A | N/A | ✓ |
| DRAM (%) | ✓ | N/A | ✓ |
| Compute Instance | |||
| ID | N/A | N/A | ✓ |
| Instance ID | N/A | N/A | ✓ |
| Accelerator ID | N/A | N/A | ✓ |
| Profile | N/A | N/A | ✓ |
| Component State | N/A | N/A | ✓ |
| Component State Detail | N/A | N/A | ✓ |
| Entity ID | N/A | N/A | ✓ |
| Compute Instance ID | N/A | N/A | ✓ |
| GR Engine Active (%) | N/A | N/A | ✓ |
| SM Active (%) | N/A | N/A | ✓ |
| SM Occupancy (%) | N/A | N/A | ✓ |
| Tensor (%) | N/A | N/A | ✓ |
| DRAM (%) | N/A | N/A | ✓ |
| GPU Link | |||
| ID | ✓ | ✓ | ✓ |
| Component State | ✓ | ✓ | ✓ |
| Component State Detail | ✓ | ✓ | ✓ |
| Accelerator ID | ✓ | ✓ | ✓ |
| Link Count | ✓ | ✓ | ✓ |
| UUID | ✓ | ✓ | ✓ |
| Links Up | ✓ | ✓ | ✓ |
| Links Down | ✓ | ✓ | ✓ |
| Bandwidth Total | ✓ | N/A | ✓ |
| CRC Flit Errors | N/A | N/A | ✓ |
| CRC Data Errors | N/A | N/A | ✓ |
| Replay Errors | N/A | N/A | ✓ |
| Recovery Errors | N/A | N/A | ✓ |
| TX Bytes | ✓ | N/A | ✓ |
| RX Bytes | ✓ | N/A | ✓ |
| TX Rate | ✓ | ✓ | ✓ |
| RX Rate | ✓ | ✓ | ✓ |
| Fabric Switch | |||
| ID | N/A | N/A | ✓ |
| Component State | N/A | N/A | ✓ |
| Component State Details | N/A | N/A | ✓ |
| Switch ID | N/A | N/A | ✓ |
| Temperature (C) | N/A | N/A | ✓ |
| Bandwidth TX | N/A | N/A | ✓ |
| Bandwidth RX | N/A | N/A | ✓ |
Comments
0 comments
Please sign in to leave a comment.