vCloud Director Troubleshooting.
What is in this post ?
Troubleshooting , resolving vCloud director issues are complex and tricky, there are no straight forward method to resolve those issues (For Ex:Go ahead just “Restart the service”, “Reboot the server” won’t work with vCloud director) . It needs more patience and calm approach. To understand the behavior, it is important to understand all the components / services in the vCloud. I tried explaining my way of approach, below are the topics I covered which I feel it is essential to read.
vCD & its components
You must understand what is vCloud director, what it can do, how it can be used to implement IaaS (Infrastructure as a Service) , there are numerous blog-post and references explaining what is vCloud director (vCD), some of them which I think it is important to read are listed below.
vCloud Training :
vCD Cell Architecture:
Internal Components of vCD:
vCloud Cell is a Supported Linux Server with vCloud director software installed.
Transfer Service is involved when a user in vCloud director uploads a OVF / Media to their allocated resources
Console Proxy is proxy service for VMRC- Virtual Machine Remote Console, this component re-directs the VMRC from the ESXi host to vCloud director UI.
VC Proxy / Cell Listener service is agent which sends / receives updates from the vCenter server, like power on/off VM, Create VM…Etc…
Active MQ – Message Bus is communication bus between multiple vCloud cells, it is for synchronization.
vCD log components:
|cell.log||Start up log.|
|vcloud-container-debug.log||Debugging log messages from the cell|
|vcloud-container-info.log||Warnings or errors in the cell|
|vmware-vcd-watchdog.log||Log of the Watchdog service – which restarts the vCD service if it hangs or stops|
- vCenter services
- VMware SSO services (Including all dependent services) (Applies on vCenter 5.1 and above)
- VMware vSphere Profile-Driven storage Service (Applies on vCenter 5.1 and above)
- vShield Manager
- vCloud services (vmware-vcd)
vCD Troubleshooting Checklist:
These are the common items must take into consideration before we begin troubleshooting
- vCenter and its DB
- vCloud and its DB
- vShield Manager
- Time Sync – Check if the time is synchronized of all vCD components
- Name Resolution – Check if the vCD components are resolved by its FQDN
- Valid SSL certificate on all vCD components
- Connectivity between all vCD components
- Perform Ping, telnet, netcat test to validate
- Synchronization – Check if the synchronization of all vCD components
- In vCloud director –> System tab –> vSphere resources –> vCenter, see if there is tick mark in the Status bar
- In vCloud director –> System tab –> Cloud Resources –> Cells, check if the vCenter proxy is running
- In vShield manager –> Configuration — >vCenter, Check the last inventory sync, it should contain the latest time stamp
- Service Start-up Issue
- VMRC Issues
- Ovf Upload issue
- Networking issues ..ahem
- Resource allocation issues
- Multi Cell and Load balancer
- Guest Customization
- Connectivity issues
3 thoughts on “vCloud Director Troubleshooting.”
Great post! I’m happy to find this your page. The internal connectivity and its relationship among vShield manager & vCD&vCenter servers also should be referred on this page isn’t it ? I really would like to know that..especially the internal provisioning procedure of Edge Gateway. Without those information, we cannot correspond to a trouble around vCloud network.
You are right, you need to understand the flow / concept to troubelshoot vCD networking issues, I am working on it and I will publish it at earliest.
Comments are closed.