Nutanix Hardware Health monitoring requirements
This topic applies only to the following products:
SolarWinds Observability Self-Hosted
SAM — VMAN
| Requirement | Details |
|---|---|
| Software |
|
| Hypervisors |
Nutanix Acropolis HyperVisor (AHV) Microsoft® Hyper-V 2008 R2 VMware vSphere® |
| Polling |
For Hyper-V and AHV, polling occurs via the Nutanix Command Line Interface (CLI). For ESXi, polling occurs via the Common Information Model (CIM). |
| Credentials |
Collect Nutanix credentials for AHV nodes, as well as Hyper-V and VMware hosts. Controller VM (CVM) credentials require privileges to connect via SSH to hosts and execute Nutanix Cluster Check (NCC) commands. SolarWinds Platform supports NCC 4.5 and later. |
| API access |
The SolarWinds Platform main polling engine or Additional Polling Engine (APE) — whichever polls the node — must have access to the Nutanix AOS API (© 2021, Nutanix, available at https://portal.nutanix.com, obtained on December 22, 2021). The SolarWinds Platform uses a combination of AOS API v1 and v2. Did you know that SAM now includes an API Poller feature? Click here for details. |
| Ports |
SSH port for Nutanix Hardware Health polling: 22 Communication port for Nutanix API: 9440 |
| Subnet |
All CVMs and hypervisor hosts must be on the same subnet. A hypervisor can be multi-homed as long as one interface is on the same subnet as the CVM. If Intelligent Platform Management (IPMI) interfaces are connected, they should be on the same subnet as CVMs and hypervisor hosts. Guest VMs can be on a different subnet. |
Nutanix port requirements
| Port | Protocol | Service/Process | Direction | Description | Encryption |
|---|---|---|---|---|---|
| 22 | SSH | SolarWinds Job Engine v2 | Outbound |
The port used for Nutanix hardware health monitoring. |
|
| 9440 | HTTPS and TCP | SolarWinds Cortex | Bidirectional | Communication between polling engines and the Nutanix AOS API. | TLS 1.2 |