Home > Blogs > Support Insider > Category Archives: Datacenter

Category Archives: Datacenter

Windows 2008+ incremental backups become full backups in ESXi 6.0 b3825889

vmware_tools_iconVMware is actively working to address a recently discovered issue wherein an incremental backup becomes a full backup when backing up Windows 2008 (or higher) virtual machines with VSS-based application quiesced snapshot.

This recent CBT (Changed Block Tracking) issue does not cause any data loss or data corruption.

This issue is well understood and VMware engineering is actively working on a fix.

For more details on this issue and latest status on resolution, please refer to KB article: After upgrading to ESXi 6.0 Build 3825889, incremental virtual machine backups effectively run as full backups when application consistent quiescing is enabled (2145895)

Subscribe to the rss feed for the KB article to ensure you do not miss any update by using this link.

Top 20 vCenter articles for May 2016

Top 20Here is our Top 20 vCenter articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Purging old data from the database used by VMware vCenter Server
  2. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  3. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  4. Upgrading to vCenter Server 6.0 best practices
  5. ESX/ESXi host keeps disconnecting and reconnecting when heartbeats are not received by vCenter Server
  6. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  7. Consolidating snapshots in vSphere 5.x/6.0
  8. Powering on a virtual machine fails after a storage outage with the error: could not open/create change tracking file
  9. Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
  10. VMware vSphere Web Client displays the error: Failed to verify the SSL certificate for one or more vCenter Server Systems
  11. Deprecated VMFS volume warning reported by ESXi hosts
  12. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  13. Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine
  14. vCenter Server 5.5 fails to start after reboot with the error: Unable to create SSO facade: Invalid response code: 404 Not Found
  15. Update sequence for vSphere 6.0 and its compatible VMware products
  16. Registering or adding a virtual machine to the Inventory in vCenter Server or in an ESX/ESXi host
  17. Back up and restore vCenter Server Appliance/vCenter Server 6.0 vPostgres database
  18. Updating rollup jobs after the error: Performance data is currently not available for this entity
  19. Configuring VMware vCenter Server to send alarms when virtual machines are running from snapshots
  20. Determining where growth is occurring in the VMware vCenter Server database

Top 20 ESXi articles for May 2016

Top 20Here is our Top 20 ESXi articles list for May 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. ESXi 5.5 Update 3b and later hosts are no longer manageable after upgrade
  3. Commands to monitor snapshot deletion in VMware ESXi/ESX
  4. Recreating a missing virtual machine disk descriptor file
  5. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  6. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  7. Installing patches on an ESXi 5.x/6.x host from the command line
  8. Identifying and addressing Non-Maskable Interrupt events on an ESX/ESXi host
  9. Restarting the Management agents on an ESXi or ESX host
  10. Downloading and installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  11. Enabling or disabling VAAI ATS heartbeat
  12. ESXi 5.5 or 6.0 host disconnects from vCenter Server with the syslog.log error: Unable to allocate memory
  13. Powering off a virtual machine on an ESXi host
  14. Consolidating snapshots in vSphere 5.x/6.0
  15. Powering on a virtual machine fails after a storage outage with the error: could not open/create change tracking file
  16. Snapshot consolidation in VMware ESXi 5.5.x and ESXi 6.0.x fails with the error: maximum consolidate retries was exceeded for scsix:x
  17. Reverting to a previous version of ESXi
  18. Configuring a diagnostic coredump partition on an ESXi 5.x/6.0 host
  19. Diagnosing an ESXi/ESX host that is disconnected or not responding in VMware vCenter Server
  20. Enabling or disabling simultaneous write protection provided by VMFS using the multi-writer flag

Inventory objects fail to display in the vSphere Web Client

An issue recently causing a few calls into our support lines happens after installing or upgrading to vCenter Server 6.0. The issue also impacts the vCenter appliance and is not specific to Windows. The issue occurs in the vSphere Web Client due to caching within the VMware Inventory Service.

  • When browsing inventory under Host and Clusters, some or no object are displayed
  • When using the Search function in the vSphere Web Client the object is found
  • The Issue does not occur in the vSphere Client
  • When browsing inventory under Related Objects at multiple levels you see this message:
no object found

If you suspect you have run into this head on over to KB: In the vSphere Web Client 6.0 inventory objects fail to display (2144934) for more details on what to check in your logs and what can be done about it.

 

Inventory objects

Top 20 vCenter articles for April 2016

Top 20Here is our Top 20 vCenter articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. Purging old data from the database used by VMware vCenter Server
  2. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  3. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  4. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  5. Consolidating snapshots in vSphere 5.x/6.0
  6. Deprecated VMFS volume warning reported by ESXi hosts
  7. Upgrading to vCenter Server 6.0 best practices
  8. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  9. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  10. Replacing default certificates with CA signed SSL certificates in vSphere 6.0
  11. Update sequence for VMware vSphere 5.5 and its compatible VMware products
  12. ESX/ESXi host keeps disconnecting and reconnecting when heartbeats are not received by vCenter Server
  13. VMware vSphere Web Client displays the error: Failed to verify the SSL certificate for one or more vCenter Server Systems
  14. Updating vCenter Server 5.5 to Update 3 fails with the error: Warning 32014. A utility for phone home data collector couldn’t be executed successfully
  15. Reducing the size of the vCenter Server database when the rollup scripts take a long time to run
  16. vCenter Server fails immediately after starting with the error: Fault Module: ntdll.dll
  17. Replacing a vSphere 6.0 Machine SSL certificate with a Custom Certificate Authority Signed Certificate
  18. In the vSphere Web Client 6.0 inventory objects fail to display
  19. Migrating virtual machines with Raw Device Mappings (RDMs)
  20. Cannot take a quiesced snapshot of Windows 2008 R2 virtual machine

Top 20 ESXi articles for April 2016

Top 20Here is our Top 20 ESXi articles list for April 2016. This list is ranked by the number of times a VMware Support Request was resolved by following the steps in a published Knowledge Base article.

  1. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  2. Commands to monitor snapshot deletion in VMware ESXi/ESX
  3. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  4. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  5. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  6. Powering off a virtual machine on an ESXi host
  7. Consolidating snapshots in vSphere 5.x/6.0
  8. Recreating a missing virtual machine disk descriptor file
  9. Reverting to a previous version of ESXi
  10. Installing patches on an ESXi 5.x/6.x host from the command line
  11. ESXi 6.0 Update 2 host fails with a purple diagnostic screen containing the error: Vmxnet3VMKDevRxWithLock and Vmxnet3VMKDevRx
  12. Cloning individual virtual machine disks via the ESX/ESXi host terminal
  13. Deprecated VMFS volume warning reported by ESXi hosts
  14. Restarting the Management agents on an ESXi or ESX host
  15. Enabling or disabling VAAI ATS heartbeat
  16. Downloading and installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  17. Configuring a diagnostic coredump partition on an ESXi 5.x/6.0 host
  18. Issuing a 0x85 SCSI Command from a VMware ESXi 6.0 host results in a PDL error
  19. Information about the error: state in doubt; requested fast path state update
  20. Committing snapshots when there are no snapshot entries in the Snapshot Manager

User account locked in vCenter Server Appliance

vCSAWe’ve recently noticed a number of cases where vSphere administrators become locked out of their accounts or receive reports of incorrect passwords in the vCenter Server Appliance. If you find yourself in this position, here are two articles that address these issues:

KB 2034608
When attempting to log into the VMware vSphere 5.1, 5.5, or 6.0 Web Client you observe the following symptom: “User account is locked. Please contact your administrator.” This often occurs if the wrong password was entered multiple times. Waiting the default 15 minutes lockout period will allow to attempt the login again. If after multiple attempts, you are still not successful, you may need to reset the password.

KB 2069041
When attempting to log into the vCenter Server 5.5 and 6.0 Appliance, you experience symptoms where the root account is locked out. This often occurs because the vCenter Server appliance has a default 90 password expiration policy. Steps on how to modify the password expiration policies and to unlock the password.

Top 20 ESXi articles for December 2015

  1. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  2. Licensing ESXi 5.x and vCenter Server 5.x
  3. Licensing ESXi 6.x and vCenter Server 6.x
  4. Reverting to a previous version of ESXi
  5. Commands to monitor snapshot deletion in VMware ESXi/ESX
  6. Collecting diagnostic information for VMware ESX/ESXi
  7. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  8. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  9. Installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  10. Estimating the time required to consolidate snapshots for VMware ESX and VMware ESXi
  11. How to purchase and file Pay Per Incident support for VMware products
  12. Consolidating snapshots in vSphere 5.x/6.0
  13. Uploading diagnostic information for VMware using FTP
  14. Uploading diagnostic information for VMware through the Secure FTP portal
  15. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  16. ESXi host cannot initiate vMotion or enable services and reports the error: Heap globalCartel-1 already at its maximum size.Cannot expand
  17. Making a VMware feature request
  18. Committing snapshots when there are no snapshot entries in the Snapshot Manager
  19. Using esxtop to identify storage performance issues for ESX / ESXi (multiple versions)
  20. Best practices for virtual machine snapshots in the VMware environment

What’s New in vSphere 5.5 Update 3b

noticeSSLv3 Protocol Disabled by Default

Background

Across the industry, enterprise software products and solutions are dropping use of and support for the SSLv3 protocol. The Internet Engineering Task Force (IETF) officially deprecated the SSLv3 protocol in RFC 7568 due to its obsolescence and inherent unfixability. Instead, IETF recommends the latest version of TLS.

VMware is therefore dropping support for SSLv3 on both the server side and the client side in vSphere. The release of vSphere 5.5 Update 3b from VMware disables SSLv3 by default to meet current standards and compliance.

Disabling SSLv3 by default also brings some restrictions with respect to installation, upgrading, and compatibility. This blog summarizes these limitations which are also documented in detail in the respective release notes and KB articles.

Below are some of the key aspects that you should be aware of when you upgrade to vSphere 5.5 Update 3b

  1. Upgrade sequence: As recommended in KB 2057795 you must upgrade vCenter Server to 5.5 Update 3b first and then update the hosts to ESXi 5.5 Update 3b.

Earlier releases of vCenter Server won’t be able to manage ESXi 5.5 Update 3b. As a workaround, you can re-enable SSLv3 protocol on ESXi by following the configuration described in KB 2139396. However, VMware strongly recommends against re-enabling the SSLv3 protocol.

  1. Upgrade both vCenter Server and ESXi to 5.5 Update 3b: In order to disable SSLv3 completely in your vSphere environment, we recommend that you update both vCenter Server and ESXi to vSphere 5.5 Update 3b.
  2. View Composer earlier than version 6.2 will have connection failures with ESXi 5.5 Update 3b. Refer to KB 2121021
  3. SSLv3 can be re-enabled by the configuration described in KB#2139396. Re-enablement of SSLv3 protocol has to be consistent across all ESXi and vCenter Server services and require mandatory service restart. However, VMware strongly recommends against re- enabling the SSLv3 protocol.

Note: Hostprofile will be able to capture SSLv3 protocol enablement configuration changes for all the services except Hostd service in ESXi.

Database issues when upgrading vSphere

For today’s post, we’d like to focus on issues surrounding DB validation during upgrade. Many of you are running into one of the issues when moving to vSphere 6.0

Does anything here look familiar?