High pNIC error rate detected

Question

High pNIC error rate detected

Sai Sankar Gochhayat 0 Microsoft Employee

User's image

AVS VM creation is failing with -
{

  "errorCode": "DeployError", 

  "errorResponse": "{\n\"message\": \"Error in getting VM powered on: No host is compatible with the virtual machine.\"\n}", 

  "errorMetadata": { 

  "errorCategory": "", 

  "errorAdditionalInfos": null 

  } 

  } 

  { 

      ErrorCode: "DeployError", 

      ErrorResponse: <*sdkerror.Error | 0x23451f6070a0>{ 

          Message: "Error in getting VM powered on: No host is compatible with the virtual machine.", 

      }, 

      ErrorMetadata: { 

          ErrorCategory: "", 

          ErrorAdditionalInfos: nil, 

      }, 

  }   
`vSphere HA host monitoring is disabled. No virtual machine failover will occur until Host Monitoring is re-enabled for cluster Cluster-1 in SDDC-Datacenter`

0 comments

1 answer

Your answer

Answer 1

Hello @Sai Sankar Gochhayat

The “High pNIC error rate detected” alarm is actually a documented Azure VMware Solution known issue. Microsoft states that AVS hosts using Mellanox NICs can report high pNIC errors due to buffer overflows, and the alert itself should generally be treated as informational because Microsoft manages the underlying infrastructure.

You can use Reset to Green to clear that particular alarm.

However, I would treat the VM deployment failure separately. The error:

Error in getting VM powered on: No host is compatible with the virtual machine

combined with the message that vSphere HA Host Monitoring is disabled deserves further investigation. The pNIC warning alone shouldn't normally make the AVS cluster unable to place or power on a VM.

I would check:

Cluster > Monitor > vSphere HA and confirm which hosts are currently eligible/connected.
Check whether any hosts are in maintenance, disconnected, or otherwise unavailable.
Review the VM's Tasks and Events for the detailed compatibility/placement failure.
Check Azure Resource Health for ongoing host remediation or replacement events. AVS continuously monitors hosts and automatically initiates remediation when it detects host degradation or failure.

If all hosts unexpectedly show as incompatible or HA Host Monitoring cannot be restored, I recommend opening an Azure Support request. Host health/remediation and the AVS underlay are Microsoft-managed, so Microsoft can verify the backend host state.

Sharing you this references:

Microsoft Learn: Azure VMware Solution known issues | https://learn.microsoft.com/en-us/azure/azure-vmware/azure-vmware-solution-known-issues?

Microsoft Learn: Azure VMware Solution Resource Health | https://learn.microsoft.com/en-us/azure/azure-vmware/resource-health-for-azure-vmware-solution-overview?

So, I wouldn't try to remediate the physical NIC alarm yourself. The more important issue to investigate is why vSphere currently considers no host compatible with the VM.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.