Received this alert in vCenter and the kb aritcle https://kb.vmware.com/s/article/83627 says that it is related to the error conditions between vmnic and the physical port. Can someone help me to identify which port has issues for me to debug further. I see this alert in two of the seven esxi hosts.
Hi. Can it be that the ESXi hosts are freshly installed? Some ESXi hosts also showed me this message shortly after the installation. After the traffic was higher, the message disappeared
These are updated couple of months before. The article says that the error can appear even if it is found before the upgrade. Not sure how to check the current counters or reset the counters to see if it happens again.
What's the hardware of the server. You might have to look into the server manager ( IDRAC for DELL or iLO for HPE) of the servers for more CRC errors.
Identifiying which interface is having a drop packet on an esxi, ideal option is to run esxtop
@sabarirjpm , In the vSphere client, if you select the host in question and go to Monitor > vSAN > Performance > Physical Adapters > Select vmnic used (and/or other one) it will show you any pNIC errors for the time period in question - unfortunately the graphs can only show 24hrs worth of data at a time so it would be worthwhile validating the timestamp of when the alarm/alert was triggered and check the 24hrs prior to that.
error is reported on ESX 7.0.2 and higher. To troubleshoot it you need to check ESX NIC counters.
Run following script then review output:
I'd say check NIC counters first. Then compare results with kb#83627
Also, confirm if this is Intel card (x710 or x810) or other vendor
Total receive errors: 236952
Two days ago HP published this:
Looks like most of times FW upgrade is going to fix problem on Qlogic part.
Also, AFAIK next 7.0.3 update, should fix most of pNIC error warnings
We had this on fujitsu servers.
I had to update the fw of my network cards and install the appropriate driver that was supported for this fw in the compatibility list.
I had this on vSphere 7.0.2,
>>>I had this on vSphere 7.0.2<<<
This is because VMware introduced that alarm in vSphere 7.0.2. It is possible that lot of environments had that issue for years, and upgrade to 7.0.2 uncover that problem.