VNXe 3200: Unable to refresh host container VMwareESX_1 because of connection
issue with the virtual service
Hello,
I am working on a VNXe 3200, migrating some ESXi hosts from ESXi 5.5 to 6.0 via fresh install, and also migrating from vCenter 5.5 to 6.0. In this process, everything is going great, and VNXe is working just fine. But I do see a red alert message in the VNXe Dashboard that seems really confusing:
"VNXe 3200: Unable to refresh host container VMwareESX_1 because of connection issue with the virtual service"
First question is, what is a "host container"? I've never heard that terminology before.
Second question is, what is "VMwareESX_1"? That's not the name of any server here, so I'm assuming it's some sort of internal EMC code name.
Third question is, what is the "virtual service"? I don't think it is referring to vCenter, because the VNXe connection to vCenter 6.0 is working just fine under Hosts >> VMware Hosts. I see green check marks for the vCenter 6.0 server and the ESXi 6.0 servers. All initiators are logged in, all datastores are mapped properly, everything looks fine except for the big red error message above.
Could you please confirm the current software version running on VNXe3200 system? (this issue exists in software versions prior to 3.1.5 code, if the system is running older version than its susceptible to this issue).
Please try removing the hosts (from VMware > Hosts and from Host > Host), and than add by IP.
1) Host container is kind of container which consists of all ESX hosts being added to VNXe GUI.
2) "VMwareESX_1" could be the ESX host which has been upgraded to new code ie 6.0.
3) VNXe communicates with ESX host with inbuilt APIs for ESX host which we call it as "Virtual service".
In case if the alert still exists, please engage EMC support.
The VNXe 3200 is running OE v3.1.5.7213336. The upgrade from v3.1.1 to 3.1.5 was last week; the error occurred this week while on 3.1.5.
The ESXi hosts were discovered by polling the vCenter Server 6.0. The VNXe "discovered" the ESXi hosts automatically after the vCenter poll operation. Are you saying there is something wrong with this poll operation, and we should delete the hosts and re-add them manually by IP address? I'd rather not like to do this because the hosts are in production, but I can do it via Maintenance Mode if need be. At this point, all ESXi hosts (and vCenter) are on v6.0, and everything looks to be operating correctly except for this erroneous error message. Can it safely be ignored, or will problems occur in the future?
Shivanand1
70 Posts
6224
1
Posted July 19th, 2016 04:00
Hi Bill,
Could you please confirm the current software version running on VNXe3200 system? (this issue exists in software versions prior to 3.1.5 code, if the system is running older version than its susceptible to this issue).
Please try removing the hosts (from VMware > Hosts and from Host > Host), and than add by IP.
1) Host container is kind of container which consists of all ESX hosts being added to VNXe GUI.
2) "VMwareESX_1" could be the ESX host which has been upgraded to new code ie 6.0.
3) VNXe communicates with ESX host with inbuilt APIs for ESX host which we call it as "Virtual service".
In case if the alert still exists, please engage EMC support.
Regards
Shivanand