In a very low threshold of occurrences, we have seen when rebooting Virtual Center when the vRanger Pro DPP services are running the Virtual Center Server Service will not start.
Does this affect Virtual Center 4.0?
No, from our testing Virtual Center 4.0 does not prematurely start accepting API connections before its ready and stop its self from fully starting. The current version of vRanger Pro 4.0 was used in this testing and no product updates are needed as Virtual center 4.0 is not showing the same behavior as Virtual Center 2.5x.
When Virtual Center 2.5x is rebooted, vRanger Pro DPP tries to reconnect to the Virtual Center service over the VMware provided API’s. Once Virtual Center is restarted it will start accepting its API calls over TCP and we are able to connect to the Virtual Center service at that time even though all VC services may not be fully loaded. On the first available acceptance of inbound API requests, Virtual Center is not ready for them because of this problem and this prevents the rest of the Virtual Center internal services from starting fully and from normal Virtual Center operations to occur.
This causes the issue where if the Virtual Center is rebooted, while the vRanger Pro DPP service is running Virtual Center does not fully start. The resolution here is to reboot Virtual Center while vRanger Pro DPP services are temporarily stopped until a patch is releases from Vizioncore to work around the Virtual Center issue. Once Virtual Center is running again you can restart the vRanger Pro DPP services. This is a temporary workaround until Vizioncore releases a patch or Vmware fixes Virtual Center API Call acceptance.
What is VMware or Vizioncore doing to resolve this issue?
During the initial starting phase of Virtual Center, Virtual Center is accepting API connections before all services are fully loaded which is inducing a false positive of complete readiness and will cause Virtual Center to hang-up on itself. To combat this Vizioncore has added in additional API checks into vRanger Pro DPP to ensure that Virtual Center is fully ready for its VMware provided API’s. If not, vRanger Pro will wait, disconnect and reconnect to Virtual Center and try again until Virtual Center is fully started and is not providing a false positive about its readiness to serve VMware provided API’s, this will remove the issue with vRanger 4.0 and Virtual Center 2.5x.
If you feel, you’re affected by this anomaly please do the following.
1.Stop all vRanger Pro services
2.Start VC service
3.Restart vRanger Pro services
KB Article: 00000296
Updated: Jul 30, 2009
vRanger Pro DPP
Expires on: 365 days from publish date