Skip to main content

VMware vSphere 6.5 common Issues



                                  Purple Screen of Death (PSOD) Issues

 PSOD is an actual purple diagnostic screen that is displayed on the console of your ESXi host. A PSOD will happen when the VMkernel on that host experiences a critical error or becomes inoperable. Your virtual machines will cease to run when this happens.
To diagnose the PSOD, use the vmkernel.log and/or the backtrace of the diagnostic screen by console access to the host.

Issue – PSOD: GP Exception 13 in multiple VMM world at VmAnon_AllocVmmPages.
Occurs on destination hosts when vMotioning a virtual machine that contains custom VMX settings.
Resolved in ESXi 6.50a. If you are unable to upgrade, manually change Numa.FollowCoresPerSocket to 1 on the ESXi 6.5 hosts.
Issue – PSOD: World nnnn tried to re-acquire lock.
Occurs on HPE Proliant servers running 6.5 due to an issue in the hp-ilo kernel module charOpen process. The specific driver affected is 65.10.0.1-24.
Resolved by upgrading the hp-ilo driver to version 650.10.0.2 or later

Upgrade Issues

Issue – Windows vCenter Server 6.5 fails with an exception: Failed to configure identity manager.
Occurs due to a conflicting OpenSSL installation on the same Windows machine. Checking the vmware-sts-idmd.log will show error relating to unable to load library ‘ssleay32.dll’
Resolved by removing any additional OpenSSL installations or applications that bundle OpenSSL. It is always best practice to install vCenter on its own machine. However, if you need to install additional applications, add them after vCenter install.
Issue – vCenter 6.5 upgrade fails with an error stating, VMware VirtualCenter failed firstboot. An error occurred while invoking external command : ‘Command: [‘/usr/sbin/vpxd’, ‘-L’] Stderr:
Occurs due to a duplicate entry for a dvSwitch or dvPortGroup. VPXD.log will show a record of Duplicate entry found for child: dvSwitch in folder:
Resolved by renaming objects (dvSwitch or Portgroup) with unique names.
Issue – vCenter Server Appliance 6.5 upgrade fails with an error stating, internal error occurs during execution of upgrade process.
Typically occurs when eth0 network adapter is not found on the VCSA. If the vCenter Server had previously been restored from backup, had the adapter changed or MAC address altered, the network adapter will no longer be eth0. It would have been renamed to eth1 or 2, etc. Bootstrap.log will show an entry for Eth0: error fetching interface information: Device not found.
Resolved by removing invalid entries or renaming 70-persisten-net.rules file.

Issue – Windows vCenter Server 6.5 services fails to start prompting a logon failure: the user has not been granted the requested logon type at this computer.
Occurs when VMware Service Lifecycle Manager service fails to start. Event Viewer log displays an entry stating, logon failure: the user has not been granted the requested logon type at this computer.
Resolved by adding vCenter accounts to the Log on as a batch job policy of effective GPO.
Issue – Unable to deploy OVF/OVA using vCenter Server Appliance 6.5 web client. Error states, this version of vCenter Server does not support Deploy OVF Template using this version of vSphere Web Client. To Deploy OVF Template, login with version 6.5.0.0 of vSphere Web Client
Occurs due to an inconsistency in the SSO token issuer certificate on systems upgraded from vSphere 5.1 or earlier
Resolved in VMware vCenter Server Appliance 6.5b. If you are unable to upgrade, deploy the OVF with OVF Tool.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Dell EMC VxRail – VMware Virtual SAN Stretched Cluster

Logical Diagram of VMware vSAN Stretched Cluster Physical Diagram of VMware vSAN Stretched Cluster Last week I deployed a test environment of VMware vSAN Stretched Cluster which is running on Dell EMC VxRail Appliance. In this post we will describe how to setup VMware vSAN Stretched Cluster on Dell EMC VxRail Appliance. Above figure is the high level of physical system diagram. In site A/B there are six VxRail Appliances and two 10GB Network Switch which are interconnected by two 10GB links, and each VxRail Appliance has one 10GB uplink connects to each Network Switch. In site C, there are one vSAN Witness host and one 10GB Network Switch. For the details of configuration of each hardware equipment in this environment, you can reference the followings. Site A (Preferred Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and 3 x SAS HDD, 2 x 10GB SFP+ ports 1 x 10GB Network switch Site B (Secondary Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and...
1 comment
Read more

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...
1 comment
Read more

UEFI Secure Boot with ESXi 6.5

UEFI Secure Boot: UEFI, or Unified Extensible Firmware Interface, is a replacement for the traditional BIOS firmware. In UEFI, Secure Boot is a “protocol” of the UEFI firmware. UEFI Secure boot ensures that the boot loaders are not compromised by validating their digital signature against a digital certificate in the firmware. UEFI can store whitelisted digital certificates in a signature database (DB). There is also a blacklist of forbidden certificates (DBX), a Key Exchange Keys (KEK) database and a platform key. These digital certificates are used by the UEFI firmware to validate the boot loader.  Boot loaders are typically cryptographically signed and their digital signature chains to the certificate in the firmware.The default digital certificate in almost every implementation of UEFI firmware is a x509 Microsoft UEFI Public CA cert. Most of the UEFI implementations also allows the installation of additional certificate in the UEFI firmware and UE...
Post a Comment
Read more