However, I am seeing some common issues that have caused some trials to come to a halt. For the most part, these are easily addressed and prevented. I've put together a basic troubleshooting list to help make your trial or proof of concept run more smoothly. Comments welcome!
Update to 5.0.2. Once again, several bug fixes have been introduced and this release includes the fixes from 5.0.1 noted below.
Upgrading to 5.0.1 fixes several stability and performance issues 5.0.1 removes the need to run a manual repair when IP addresses change on the VMs
Shutting down/starting up. The vApp is designed to start and stop the VMs in proper sequence. It is highly recommended to shut down the ENTIRE vApp even if you only want to modify the UI VM (for example).
- Always use the vApp to start the VMs by selecting the vApp in vCenter and then clicking the "green arrow" start button as you would with a VM.
- Always use the "Power Off" button to shut down the vApp - even though it seems like that would cut power to the VMs it actually does a safe shutdown.
- Failure to do so will (eventually) cause DB corruption.
IP Pools setup. Basically, the IP Pool is used by the vApp to set up a VPN tunnel between the two VMs. Here are some things that often get overlooked or mis-configured:
- Do not enable the IP Pool, I've seen this cause issues with IP address assignment for the VMs in the vApp.
- You only need configure the subnet, mask and gateway on the IPv4 tab - an IP pool range is not required (and you won't be able to edit unless the IP pool is enabled).
- Use the DNS tab on the IP Pool properties to configure your DNS servers.
- In general do not use the "blue console" to configure networking, even though there's an option to do that. Always use the IP Pool and vApp properties to manage networking.
- Always use static IP. Even if your DHCP environment is well run, a change in IP creates havoc.
- Always change IP addresses by shutting down the vApp and editing the vApp properties.
- Verify network connectivity between the first and second VM. From the console of the UI VM, ping "secondvm-internal" and "secondvm-external" to check that all is well. If not, very likely you need to run the repair (see the section on vcops-admin command below). If a ping works, simply shut down and restart the vApp to get things working again.
- Check the /data partition on both the UI and Analytics VM using
- Add additional storage if needed by first properly shutting down the vApp (Power Off - trust me, that's the right way) and add another VMDK to the VM(s). Start the vApp and the additional disk space will be added to the /data partition automatically by the VM.
- The repair command fixes a broken vApp. That is, if your VMs are not communicating due to an IP address change (because you used DHCP for example) this command will get them talking again.
- You can use vcops-admin to restart the services on the UI VM. Sometimes this corrects issues with web pages not being accessible or other odd behavior - after you've checked storage and networking.
- Sometimes the admin password is forgotten. It happens. Use the password command.
- You can create a diagnostic bundle for VMware support from vcops-admin if you are not able to access the admin UI via web browser.
*Updated 5/22 - 5.0.1 upgrade
*Updated 7/25 - 5.0.2 upgrade and missing scroll bars
Post a Comment