5.1

vSphere 5.0 and 5.1 End of Support 2016-08-24

vsphere-5Today, 5 years after the release vSphere 5.0 and vSphere 5.1, end of support for both products has been reached and enters the technical guidance phase starts.

If not are not aware of the EOS, I encourage you to use my VMware Product End Of Support Countdown to keep an eye on EOS dates (It also supports ics based calendar reminders).

Currently, the only fully supported versions are

  • vSphere 5.5
  • vSphere 6.0

Read More »vSphere 5.0 and 5.1 End of Support 2016-08-24

vSphere 5.0 & 5.1 End of Support soon - Upgrade your ESXi Hosts

hcl-60You might be aware that General Support for VMware vSphere 5.0 and 5.1 ends in about 4 weeks at August 24th. If not, I encourage you to use my VMware Product End Of Support Countdown to keep an eye on EOS dates (It also supports ics based calendar reminders).

If you are not running on ESXi 5.5 or ESXi 6.0, it is time to upgrade now. Prior to upgrade, please check VMware Compatibility Guide (HCL) to verify that your server is supported for the targeted vSphere release.

Read More »vSphere 5.0 & 5.1 End of Support soon - Upgrade your ESXi Hosts

vCenter Server 5.0/5.1 Update - CVE-2014-6593 (SKIP-TLS)

vcenter-server-logoVMware has published an update for vCenter Server 5.0 and 5.1 where CVE-2014-6593 (SKIP-TLS) has been fixed.

It was discovered that the SSL/TLS implementation in the JSSE component in OpenJDK failed to properly check whether the ChangeCipherSpec was received during the SSL/TLS connection handshake. A man-in-the-middle attacker could possibly use this flaw to force a connection to be established without encryption being enabled. The update has been already fixed in newer versions of vCenter Server (6.0a, 5.5 Update 2e). More information are available in VMSA-2015-0003.Read More »vCenter Server 5.0/5.1 Update - CVE-2014-6593 (SKIP-TLS)

VMware ESXi 5.x E1000 PSOD Issue

Even though the bug has been fixed I still see it to come up. ESXi 5.x has two issues that might cause the ESXi host to fail with a purple diagnostic screen. Both PSOD look very similiar:

KB2059053:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+ 0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a

KB2079094:

#PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing@vmkernel#nover+0xeb7
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx@vmkernel#nover+0x18a
[...]
0xnnnnnnnn:[0xnnnnnnnn]Net_AcceptRxList@vmkernel#nover+0x157

Read More »VMware ESXi 5.x E1000 PSOD Issue

Upgrade vCenter 5.1 to 5.5 error: "The existing ssl certificate is invalid"

The upgrade from vCenter Server 5.1 to vCenter Server 5.5 (5.5.0 and 5.5.0a) fails during the SSO installation with the following error message:

The existing ssl certificate is invalid

After verifying the certificate i could confirm that it is valid and not expired. After troubleshooting the update log I figured out that the problem was caused by a wrong registry entry. The old 5.1 installation was using an IP address instead of the vCenters FQDN.

Read More »Upgrade vCenter 5.1 to 5.5 error: "The existing ssl certificate is invalid"

Warning 25000 at vCenter 5.5 Update - How to handle?

When you are updating VMware vCenter Server 5.1 to version 5.5 you always get that "Warning 25000" message. This post shows how to check that the certificate is valid, and how to replace a expired certificate

Warning 25000. Please verify that the SSL certificate for your vCenter Single Sign-On 5.1 SSL is not expired. If it did expire, please replace it with a valid certificate before upgrading to vCenter Single Sign-On 5.5.

Read More »Warning 25000 at vCenter 5.5 Update - How to handle?

VMware VDP Required Permissions

In some environments you might have to reduce the permissions given to the vSphere Data Protection (VDP) Backup User to as few as possible. The documentation provided by VMware is a little bit ambiguous on that topic. The permissions given in that post are at least required for the following purposes:

  • VDP backup user (The user that the appliances uses to talk to the vCenter Server)
  • Configure and Add Backup/Restore Jobs
  • See the vSphere Data Protection button in the vSphere Web Client

Read More »VMware VDP Required Permissions