During the deployment of the vcOPs vApp for a customer I ran into a new error – well, new for me. While the vApp (v5.8.1) deployed and booted fine, as I was registering it with the vCenter (v 5.1) as part of the initial configuration I got the following error: Unable to get vCenter server certification chain. Off we go to Google… Here’s a quick summary of things to check:
- Confirm name resolution is working, username/passwords are right, etc.
- Assuming Windows, RDP to vCenter with the user you’re attempting to use or try access via your favorite vSphere management tool
- Hop on the console of the UI VM and ping the vCenter by IP and DNS name (username: root initial password: vmware)
- Check that your vCenter certificate hasn’t expired. It’s the rui.crt file in c:\ProgramData\VMware\VMware VirtualCenter\SSL. This article has good info on locating and renewing your certificate, should that be your problem.
- In the end, my fix came by importing the certificate file to the UI VM manually as outlined in this VMware KB article.
- Full disclosure, the symptoms in the above article didn’t match my problem exactly and I don’t like just trying random fixes. However, when I found this Blog Post, in Spanish, with my exact error recommending a similar .cert import process I threw caution to the wind. The exact steps from the Spanish blog didn’t quite work, which could be a result of my inability to read Spanish and/or Google Translate not being perfect, but the VMware KB article was spot on.
After importing the certificate manually and restarting services, all was well and I was able to complete the configuration of vcOPs. By the way, did you know that since vSphere 5.1, all licensed versions of vSphere now include the Foundation edition of vcOPs? More than 5 hosts in your environment and you’ve got enough scale to warrant leveraging this tool. For a limited time, VMware is letting Lewan perform a free vSphere Optimization Check including a 60 day trial of the Standard Edition, complete with the capacity management features, dynamic thresholds, and root cause analysis. Give us a call today to test drive Operations Management!
A new patch release notification from VMware was received today, it’s copied below.
We are pleased to inform you that new VMware ESX/ESXi Patches are available as of May 3, 2012.
These patches address several critical security issues. Detailed information regarding resolved and known issues and enhancements can be found in these Knowledge Base articles:
3.5 EP2 Patch Release Notes:
4.0 EP7 Patch Release Notes:
4.1 EP2-1 Patch Release Notes:
5.0 EP3 Patch Release Notes:
VMware ESX/ESXi Patches are available for download at http://www.vmware.com/patch/download/.
VMware vSphere Product Release Team
Chethan Kumar has recently updated the Performance Troubleshooting for vSphere 4.1 guide. This is a great asset I use regularly for any client or partner that asks about vSphere performance – especially those working with Tier 1 applications. It is very educational and addresses the most common scenarios clients experience.
“The hugely popular Performance Troubleshooting for VMware vSphere 4 guide is now updated for vSphere 4.1 . This document provides step-by-step approach for troubleshooting most common performance problems in vSphere-based virtual environments. The steps discussed in the document use performance data and charts readily available in the vSphere Client and esxtop to aid the troubleshooting flows. Each performance troubleshooting flow has two parts:
1. How to identify the problem using specific performance counters.
2. Possible causes of the problem and solutions to solve it.”
It is located here: http://communities.vmware.com/docs/DOC-14905
Here’s a great post over at www.vladan.fr (who’s a well known VMware blogger and vExpert) on some of the KB articles he’s found regarding best practices on installing vSphere 4.1 and vCenter 4.1.
Preparing the vCenter Server Installation Worksheet – Download and fill out the vCenter Server Installation Worksheet.
MicrosoftSQL Server 2005 Express is intended for use with small deployments of up to 5 hosts and/or 50 virtual machines.
Memory – 3GB RAM. RAM requirements may be higher if your database runs on the same machine. VMware VirtualCenter Management WebServices requires 128Mb to 1.5GB of memory which is allocated at startup.Disk storage – 2GB. Disk requirements may be higher if your database runs on the same machine.
- vCenter Server 4.1 requires a 64 bit DSN and MUST NOT be a Domain controller. vSphere Compatibility Matrix.
- The computer name – no more than 15 characters.
- have reliable DNS and Time services.
Recommended, but not mandatory:
- separate database for vCenter Server and vCenter Update Manager
vCenter server needs all this (will be installed as part of vCenter Installation):
Apache Tomcat (64 bit)
Java Runtime Environment JRE (64 bit)
Active Directory Application Management (ADAM)
Visual C++ 2005 Runtime Redistributable
.NET 3.0 SP1 or above (optional based on DB selection)
If the machine on which you are installing vCenter Server has a previous version of vCenter installed (if it’s on 64 bit hardware), you might want to upgrade instead of performing a fresh installation of vCenter Server.
Best practices for the ESX installations:
Check on the HCL (hardware compatibility list) page…. – I blogged about that earlier too ….
- System compatibility
- I/O compatibility (Network and HBA cards)
- Storage compatibility
- Backup software compatibility
32bits installation are no longer supported. VMware ESX 4.1 only installs and runs on servers with 64 bit x86 CPUs.
- Check the Enable Intel VT in the BIOS.
- If you are installing to the local disks and you have a SAN with Fiber Channel connected to the ESX host, make sure and detach the fiber before continuing with the installation. (Do not disable HBA cards in the BIOS)
- minimum size of the vmdk where the /, swap, and all the optional partitions are stored should be set for 8GB.
- Make a separate partition for /var/log.
Source: Installing ESX 4.1 and vCenter Server 4.1 best practices
Running on vSphere 4.1, I installed a VM with Fedora 12 on it (Kernel version: 184.108.40.206-168.fc12.x86_64) and when I tried to install VMware Tools, I kept getting an error at the step that said:
“What is the location of the directory of C header files that match your running kernel?”
There are countless posts around the internet with people looking for help with this.
I searched and searched online but could not find a solution that worked for me, until I came across this site, which I followed and it worked perfectly!
The steps are copied below for reference (from the above site).
- Download Fedora 12.
- Install the OS.
- Boot up the virtual machine.
- Open up the Terminal.
- Run “su” and type your root password to gain administrative control.
- Run “yum update” to update all the packages to the newest version.
- Open up the Terminal.
- Run “yum install kernel-devel kernel-headers gcc mkinitrd”
- Click the menu option in your VMware application to install VMware tools. This should put a compressed folder on the desktop.
- Expand the zip file and using the terminal, navigate into the newly created directory.
- As the root user, type “./vmware-install.pl”
- When it asks you questions and prompts you for a response, just hit enter. Everything should be properly configured at this point.
- Reboot when the script finishes. That’s it!