1 person found this helpful
I have the same error. To resolve that you must do:
1) enter maintenance mode
2) move esxi from cluster to datacenter
3) disconnect esxi
4) remove esxi from inventory
5) add esxi host do datacenter
6) move esxi to cluster.
That helped my.
Even i am getting the same error message after upgrading ESXi hosts from 5.5 to 6.5
Tried below KB article:
But after adding removing host and adding it back from DC to cluster makes the error message appearing again.
I believe this issue can be related to the usage of distributed switches associated to the hosts, as I have seen it on systems that are not using any configured storage providers.
The hint here is the VMware KB 2150311 article fix procedure last step being:
- Reconfigure vDS for the host.
I had exactly this very same Warning associated to some of my v6.5 hosts after a vDS reconfiguration (changed from 4 to 7 uplinks).
I'm not using any storage providers configured in vCenter.
The problem was only apparent after a total vCenter and hosts shutdown, followed by a power on.
By applying tyhe VMware KB 2150311 procedure the issue was fixed in two of the six hosts.
However the issue remains on the other 4 hosts.
Nope, the issue keeps popping up randomly every time the hosts are rebooted.
For instance, powering on the 6 hosts at the same time.
I wonder if this is really what it means, a storage issue?
I'm using this lab environment to test this issue, and when the 6 hosts are powered on at the same time, I get this issue on a few hosts.
The storage is a iSCSI target on a Windows server.
On the other side, I have the same setup running without this issue, where the only difference I see is the VMware vCenter/ESXi software version.
I never saw this issue on the 6.5 GA version.
This time I am using a more recent s/w version: ESXi 6.5.0-5310538 and vCenter 6.5.0-5318154.
I found out that the issue is not showing up if we start the ESXi hosts AFTER having the vCenter server up and running.
Meaning you need a management cluster to run the vCenter appliance in first place, and only then start your hosts in another production clusters.
As I mentioned before, I never saw this issue when using the previous versions of vSphere 6.5.
In may case this issue is probably related to this very specific s/w release versions:
ESXi 6.5.0-5310538 and vCenter 6.5.0-5318154.
Yeah, i am running on all the hosts with ESXi 6.5.0-5310538 in particular vCenter(Version 6.5.0 Build 5705665), where i am encountering this error message.
But same version of hosts running in another vCenter are not producing this error message.
Raised a case with VMware and awaiting for response
I have the same problem with the following version.
vCenter 6.5 u1 5973321
esxi 6.5 u1 5969303
I hope that a solution is found soon.
I too have this issue after upgrade from 6.5 to 6.5u1
I'm running 2 ESXI in one EVC cluster :
vm01 - Dell T430, dual Intel Xeon CPU E5-2650 v4, 192GB RAM - Perc H730P internal - iSCSI to QNAP server
vm02 - Dell T430, dual Intel Xeon CPU E5-2620 v3, 192GB RAM - Perc H730P internal - iSCSI to QNAP server
EVC using Intel "Sandy Bridge"
All BIOS and firmware on highest level.
Both ESXI on version 6.5.0 Update 1 (Build 5969303)
vCenter server 6.5.0 build 6671409
My EVC cluster :
vm01 server - OK, vMotion storage possible
vm02 server - status (not responding)- Cannot synchronize host vm02.... - Host connection and power state.
I tried remove server from cluster, remove from inventory, add host to datacenter, move host to cluster : after few seconds server show the error
'registration/unregistration of third-party io filter storage providers fails on a host'
For the time being, I can't migrate anything on vm02.
No error in vm02 log - but an-managable in vCenter.
Anyone have a hint ?? (VMWare were to no assistance)
Hello, what's the impact on a vsan cluster with this error?
Registration/unregistration of third-party IO filter storage provider fails on a host.
We tried to upgrade the vcenter to 6.5 u1 and it failed (we had wrong permissions for the service users), so we had to restore the database and rollback the vm.
I didn't have any downtime but that error appeared, and I just noticed it today.
That KB says it doen's apply to 6.x but I just wanted to be shure because I have to do the update again.
When I go and check the storage providers on our hosts everything seems OK.
2 people found this helpful
I had the same problem but then I found that port 9080 was being blocked by our firewalls.
Once I enabled this port I had to remove and add the host as per KB 2150311.
Port 9080 is the port used by the I/O Filter Service.
Thank you kyle901. Our issue was caused by the firewall blocking TCP/9080 FROM vCenter TO the ESXi hosts. Once the port was open, the error message eventually disappeared. We could see traffic on TCP/9080 with two hours interval.
I/O Filter Service
Used by the I/O Filters storage feature
Hi kyle901 & stiftelsen,
I have the same problem in vSAN cluster.
How do I check if port 9080 is blocked?
I ran the following commands on the ESXi:
nc -z 10.76.4.209 9080
Connection to 10.76.4.209 9080 port [tcp/*] succeeded!
esxcli network ip connection list | grep 9080
tcp 0 0 :::9080 :::0 LISTEN 67874 newreno ioFilterVPServer
Is this mean the port is enabled?
That helped for me. Port 9080 wasn't opened from the vCenter to the hosts.
Looks like this requirement for port 9080 being open from vCenter server towards all hosts in the environment is new feature with 6.5. I had missed that when I started upgrading my environments.
You saved my time with your post, thanks for that!
I come across this often. 90% of the time I forgot to mount a Datastore to all hosts in a cluster.