Home > Blogs > Support Insider > Author Archives: Rick Blythe
Rick Blythe

About Rick Blythe

Social Media Program Manager for VMware, Rick Blythe manages the Twitter handle @vmwarecares and curates the Support Insider Blog.

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 vRealize Operations Manager articles for March 2016

Top 20Here is our Top 20 vRealize Operations Manager articles list for March 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. After upgrading to vRealize Operations 6.2.0a, vCenter adapters remain in Starting state
  2. Update sequence for vSphere 6.0 and its compatible VMware products
  3. Resetting the Administrator password in VMware vRealize Operations Manager appliance
  4. Important information before upgrading to vSphere 6.0
  5. vRealize Operations Manager 6.1 and 6.2 Sizing Guidelines
  6. Restarting VMware vRealize Operations Manager 6.0.x fails with a Waiting for Analytics message in the Admin UI
  7. VMware vRealize Operations Manager 6.1.x upgrade hangs if expired projects are present
  8. VMware vRealize Operations Manager for Horizon 6.2 Broker Agent fails to pair with the Horizon adapter
  9. vRealize Operations Manager 6.x is inaccessible, status of all nodes is Waiting for Analytics to Start
  10. Cluster Status is stuck at Going Online in VMware vRealize Operations Manager 6.0.x
  11. VMware vRealize Operations Manager 6.0 displays erroneous alarm: Virtual Machine is experiencing high number of receiver packets dropped
  12. Adding additional storage to the VMware vRealize Operations Manager Analytics or UI virtual machine
  13. Configure a certificate for use with vRealize Operations Manager
  14. vRealize Operations Manager Sizing Guidelines
  15. VMware vRealize Operations Manager counters report false dropped packets on vSphere Distributed Switches with the alert: One or more ports are experiencing network contention
  16. Cannot remove a solution from VMware vRealize Operations Manager
  17. Performance issues on Domain Controller occur when running LDAP queries from VMware vRealize Operations Manager 6.1
  18. Upgrading to VMware vRealize Operations Manager 6.2.0a fails
  19. Enabling SSH access in VMware vRealize Operations Manager 6.0.x
  20. vRealize Operations Manager 6.0.1, 6.0.2, and 6.0.3 Sizing Guidelines

Top 20 vRealize Automation articles for March 2016

Top 20Here is our Top 20 vRealize Automation (vRA) articles list for March 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. Update sequence for vSphere 6.0 and its compatible VMware products
  2. Important information before upgrading to vSphere 6.0
  3. Repairing or updating the trust between all components within a VMware vRealize Automation environment
  4. Connecting to a resource using the Remote Console (VMRC) option in VMware vRealize Automation 6.2.1 fails with the error: Cannot establish a remote console connection
  5. Using JXplorer to update the LDAP string for an identity source for VMware vRealize Automation 6.0.x, 6.1.x
  6. Logging in to a tenant with verified administrator credentials or user credentials fails in VMware vRealize Automation 6.2.x
  7. Migrating to a new SSO or recovering from a reinstallation of SSO in VMware vRealize Automation
  8. Various tasks fail after upgrading or migrating to VMware vRealize Automation 6.1.x or 6.2
  9. Logging in to the VMware vRealize Automation 6.2.x Appliance Management website fails with the error: Unable to authenticate user. Please try again
  10. Certificate troubleshooting, supportability, and trust requirements for vRealize Automation 6.2/7.0
  11. Removing a virtual machine from Management in VMware vRealize Automation 7 using Cloud Client
  12. Removing a virtual machine from Management in VMware vRealize Automation or VMware vCloud Automation
  13. Deleting an endpoint in vRealize Automation fails with the error: This endpoint is being used by # compute resources and # storage paths and cannot be deleted
  14. Unable to add Active Directory users or groups to vCenter Server Appliance or vRealize Automation permissions
  15. Moving the VMware vRealize Automation 6.x SQL database to a new server
  16. Signing VMware vRealize Automation certificates using an internal Microsoft CA signing authority
  17. Network profile is not assigned to new virtual machines in VMware vRealize Automation 6.1.x and 6.2.x
  18. Setting the Kerberos token size for VMware vRealize Automation 6.x deployments
  19. Catalog items cannot be requested after upgrading to vRealize Automation 6.2
  20. Advanced Service Designer resource actions are not available for IaaS provisioned virtual machines

Top 20 vSAN articles for March 2016

Top 20Here is our Top 20 vSAN articles list for March 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. Following maintenance, hosts in a Virtual SAN cluster may erroneously report the error: Host cannot communicate with all other nodes in virtual SAN enabled cluster
  2. Avoiding a known drive failure issue when Dell PERC H730 controller is used with VMware Virtual SAN 5.5 or 6.0
  3. Certification of Dell PERC H730 and FD332-PERC Controllers with VSAN 6.2
  4. Support statement for 512e and 4K Native drives for VMware vSphere and VSAN
  5. VMware Virtual SAN 6.0 Requirements
  6. Upgrading the VMware Virtual SAN (VSAN) on-disk format version from 1 = 2
  7. Troubleshooting VSAN SSD congestion on vSphere 5.5
  8. VMware Virtual SAN 6.1 or 5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)
  9. VMware Virtual SAN 6.2 on disk upgrade fails at 10%
  10. vSphere 5.5 Virtual SAN requirements
  11. Enabling or capturing performance statistics using Virtual SAN Observer for VMware Virtual SAN
  12. Removing a VMware Virtual SAN-enabled cluster and detaching the VMware ESXi host from the cluster fails
  13. Powering on virtual machines in VMware Virtual SAN 5.5 fails with error: Failed = create swap file
  14. VSAN RVC fails = run after upgrading = vCenter Server 6.0 Update 1b
  15. VMware Virtual SAN 6.2 on disk upgrade fails at 10%
  16. Adding existing Virtual SAN hosts = a new Virtual SAN cluster after rebuilding vCenter Server
  17. VMware Virtual SAN configuration fails with the error: Found another host participating in the VSAN service which is not a member of this host”s vCenter cluster
  18. Requirements and considerations for the deployment of VMware Virtual SAN (VSAN)
  19. A VMware Virtual SAN virtual machine in a vSphere HA cluster reports as HA protected when powered off
  20. vSphere High Availability (HA) fails = restart a virtual machine when VMware Virtual SAN network is partitioned

Top 20 vCenter articles for March 2016

Top 20Here is our Top 20 vCenter articles list for March 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. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  2. Purging old data from the database used by VMware vCenter Server
  3. Upgrading to vCenter Server 6.0 best practices
  4. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  5. Unlocking and resetting the VMware vCenter Single Sign-On administrator password
  6. Consolidating snapshots in vSphere 5.x/6.0
  7. Deprecated VMFS volume warning reported by ESXi hosts
  8. Stopping, starting, or restarting VMware vCenter Server services
  9. Resetting the VMware vCenter Server and vCenter Server Appliance 6.0 Inventory Service database
  10. List of recommended topologies for VMware vSphere 6.0.x
  11. Migrating the vCenter Server database from SQL Express to full SQL Server
  12. VMware vSphere Web Client displays the error: Failed to verify the SSL certificate for one or more vCenter Server Systems
  13. Update sequence for VMware vSphere 5.5 and its compatible VMware products
  14. Update sequence for vSphere 6.0 and its compatible VMware products
  15. Linked Clone pool creation and recomposition fails with VMware Horizon View 6.1.x and older releases
  16. Unmanaged I/O workload detected on shared datastore running Storage I/O Control (SIOC) for congestion management
  17. The vpxd process becomes unresponsive after upgrading to VMware vCenter Server 5.5
  18. Installing vCenter Server 6.0 best practices
  19. 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
  20. Registering or adding a virtual machine to the inventory on vCenter Server or on an ESX/ESXi host

Top 20 NSX articles for March 2016

Top 20Here is our Top 20 NSX articles list for March 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. Update sequence for vSphere 6.0 and its compatible VMware products
  2. Downloading and enabling VMware vShield Endpoint 5.x on supported VMware vSphere platforms
  3. Virtual machine performance issues after upgrading VMware tools version to 10.0.x in NSX/ VMware vCloud Networking and Security 5.5.x
  4. Important information before upgrading to vSphere 6.0
  5. vCenter Server or Platform Services Controller certificate validation error for external VMware Solutions in vSphere 6.0
  6. Windows virtual machines using the vShield Endpoint TDI Manager or NSX Network Introspection Driver (vnetflt.sys) driver fails with a blue diagnostic screen
  7. How to license VMware NSX for vSphere 6.x
  8. Network connectivity issues after upgrading or repreparing ESXi hosts in a VMware NSX/VCNS environment
  9. NSX is unavailable from the vSphere Web Client Plug-in after taking a backup of NSX Manager with quiesced snapshot
  10. Clicking NSX Home in the vSphere Web Client reports the error: No NSX Managers available. Verify current user has role assigned on NSX Manager error
  11. Understanding and troubleshooting vShield Endpoint / Guest Introspection with VMware vCloud Networking and Security 5.x and NSX for vSphere 6.x
  12. Changing the VMware NSX for vSphere 6.x License from virtual machine to CPU
  13. In VMware NSX for vSphere 6.x, ESXi 5.5.x/6.0.x host experiences a purple diagnostic screen mentioning PFFilterPacket and VSIPDVFProcessSlowPathPackets
  14. The NSX Manager flow monitoring UI displays No Flow Records
  15. Collecting diagnostic information for the NSX Guest Introspection MUX VIB
  16. Network disruption causes a split-brain scenario on a High Availability configuration of VMware vShield Edge
  17. Net Packet Heap issue in VMware ESXi 5.5.x and 6.0.x running an NSX for vSphere Edge
  18. The netcpa agent on an ESXi host fails to communicate with NSX controller(s) in VMware NSX for vSphere 6.x
  19. In VMware NSX for vSphere 6.x, IP address assignments to VXLAN Tunnel End Point (VTEP) and NSX host preparation fails with the error: Insufficient IP addresses in IP pool
  20. Migration of Service VM (SVM) may cause ESXi host issues in VMware NSX for vSphere 6.x

Top 20 ESXi articles for March 2016

Top 20Here is our Top 20 ESXi articles list for March 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. After upgrading an ESXi host to 5.5 Update 3b and later, the host is no longer manageable by vCenter Server
  2. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing and E1000DevRx
  3. Commands to monitor snapshot deletion in VMware ESXi/ESX
  4. Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x
  5. Determining Network/Storage firmware and driver version in ESXi/ESX 4.x, ESXi 5.x, and ESXi 6.x
  6. Methods for upgrading to ESXi 5.5
  7. Methods for upgrading to VMware ESXi 6.0
  8. Recreating a missing virtual machine disk descriptor file
  9. Installing patches on an ESXi 5.x/6.x host from the command line
  10. Reverting to a previous version of ESXi
  11. Licensing VMware vCenter Site Recovery Manager
  12. Creating quiesced snapshot fails with the error: An error occurred while saving the snapshot: msg.snapshot.error-QUIESCING-ERROR
  13. Consolidating snapshots in vSphere 5.x/6.0
  14. Restarting the Management agents on an ESXi or ESX host
  15. Using esxcli in vSphere 5.5 and 6.0 to reclaim VMFS deleted blocks on thin-provisioned LUNs
  16. Identifying and addressing Non-Maskable Interrupt events on an ESX/ESXi host
  17. Downloading and installing async drivers in VMware ESXi 5.x and ESXi 6.0.x
  18. Deprecated VMFS volume warning reported by ESXi hosts
  19. Estimating the time required to consolidate snapshots during the snapshot removal for VMware ESX and VMware ESXi
  20. VMware ESXi 5.x host experiences a purple diagnostic screen mentioning E1000PollRxRing, E1000DevRx and Net_AcceptRxList

Important NSX for vSphere KB Updates – March 2016

vCloud Networking and Security will reach end of availability and end of support on September 19, 2016.

  • KB 2144733 – End of Availability and End of Support Life for VMware vCloud Networking and Security 5.5.x
  • See the fully updated vCNS to NSX Upgrade Guide
  • See also KB 2144620 – VMware vCloud Networking and Security 5.5.x upgrade to NSX for vSphere 6.2.x Best Practices
  • ​Upgrade path from vCNS 5.x: Using the NSX upgrade bundle posted on or after 31 March, 2016, you may upgrade directly from vCNS 5.1.x or vCNS 5.5.x to NSX 6.2.2 Please see the NSX 6.2.2 release notes
  • Upgrades from NSX 6.1.5 to NSX 6.2.0 are not supported. Instead, you must upgrade from NSX 6.1.5 to NSX 6.2.1 or later to avoid a regression in functionality. Refer to KB 2129200

NSX for vSphere 6.1.x will reach end of availability and end of support on October 15, 2016

  • KB 2144769End of Availability and End of Support Life for VMware NSX for vSphere 6.1.x
  • The recommended release for NSX-V is 6.2.2. Refer to KB 2144295Recommended minimum version for VMware NSX for vSphere with Guest Introspection Driver, ESXi and vCenter server.

New issues:

  • KB 2144726Service Composer fails to translate virtual machines into security-groups in VMware NSX for vSphere 6.x
  • KB 2140891Storage vMotion of Edge appliance disrupts VIX communication in VMware vCloud Networking and Security 5.5.x and NSX for vSphere 6.x
  • KB 2144476After reinstalling vCenter Server 6.0 EAM fails to push VIB’s to ESXi host with the error: Host not covered by scope anymore
  • KB 2144456Importing draft firewall rules fails after existing firewall configuration is removed by a REST API request
  • KB 2144387After upgrading to VMware NSX for vSphere 6.2.2 there is no upgrade option available for NSX Guest Introspection and NSX Data Security and the services remain at version 6.2.1
  • KB 2144420Any changes to the Primary UDLR result in the vNic_0 being shutdown on the Seconday UDLR in VMware Cross-vCenter NSX for vSphere 6.2.x
  • KB 2144236VMtools issue – Virtual machine performance issues after upgrading VMware tools version to 10.0.x in NSX/ VMware vCloud Networking and Security 5.5.x
  • KB 2144649 – IPv4 IP address do not get auto approved when SpoofGuard policy is set to Trust On First Use (TOFU) in VMware NSX for vSphere 6.2.x
  • KB 2144732 – In VMware NSX for vSphere 6.x, unpreparing Stateless ESXi host fails with the error: Agent VIB module is not installed. Cause : 15 The installation transaction failed. The transaction is not supported
  • KB 2135956 – VMware ESXi 6.0 Update 1 host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4923 – Usage error in dlmallocnow resolved in vSphere 6.0U2. See also the vSphere 6.0U2 Release Notes
  • KB 2126275Publishing Distributed Firewall (DFW) rules fails after referenced object is deleted in VMware NSX for vSphere 6.1.x and 6.2.x

Tracking the top issues:

How to Hyperlink KB articles

There are many, many, blogs, forums, videos channels out there that cover various VMware topics, and we commonly see our KB articles being linked from those sites.

We wanted to help those doing this with a couple of quick tips that will make your links easier to read and more resilient to potential changes in our CMS in the future.

When you open one of our KB articles and look at your URL bar, you’ll see a long, and parameterized URL. For example:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427

As you can see, this URL includes unnecessary parameters for sharing and just looks long and ugly. Here’s a much cleaner format to use:

https://kb.vmware.com/kb/1006427

The beginning part is always the same, just substitute the actual KB number you wish to reference at the end.  Also note that we are now using https rather than the older and less secure http protocol.

Hope this helps those of you sharing our content; you have our thanks!

Important KB updates for current NSX for vSphere users

Our NSX team would like all of our customers to know about important KB updates for current NSX for vSphere issues. Here’s what’s new and trending-

Recommended minimum version for VMware NSX for vSphere with Guest Introspection Driver, ESXi and vCenter server (KB 2144295)

  • NSX for vSphere 6.2.2​
  • NEW! See also the minimum recommended version table in the Systems Requirements section of the NSX for vSphere 6.2.2 Release Notes. 

Key issues resolved in NSX for vSphere in release 6.2.2:

  • KB 2144097After deploying a VMware NSX for vSphere 6.2.x Edge, adding a dhcp pool fails with the error: Invalid host name <name.local>
  • KB 2144457Shutting down the VMware NSX for vSphere 6.x controllers while using replication type Hybrid mode flushes out the VTEP tables on the ESXi host
  • KB 2144096VMware vCloud Networking and Security and NSX for vSphere workaround for CVE-2015-7547: glibc getaddrinfo stack-based buffer overflow
  • KB 2144018 / – In VMware NSX for vSphere 6.2.1, ESXi 5.5.x/6.0.x host experiences a purple diagnostic screen mentioning PFFilterPacket and VSIPDVFProcessSlowPathPackets
  • KB 2143397 / – In VMware NSX for vSphere 6.2.1, adding an ESXi host to the vSphere Distributed Switch fails with the error: Host <IP address> is not licensed for the VDS feature. Cannot add this host to dvSwitch
  • KB 2144314 In VMware NSX for vSphere 6.x, ESXi 5.5.x host experiences a purple diagnostic screen mentioning VdrProcessDhcpClientReq and VdrConsumeDhcp

Top troubleshooting issues:

  • KB 2144605Troubleshooting duplicate VXLAN VTEP vmk interfaces or IP addresses in VMware NSX for vSphere 6.x
  • KB 2137025IP address assignments to VXLAN Tunnel End Point (VTEP) and NSX host preparation fails with the error: Insufficient IP addresses in IP pool
  • KB 2144016In VMware NSX for vSphere 6.x, the NSX agencies on an ESXi host are uninstalled after unregistering the NSX Solution Plug-in
  • KB 2144200In VMware NSX for vSphere 6.x, installing or upgrading NSX VIBs fails with the error: ERROR: The pending transaction requires xxx MB free space, however the maximum supported size is xxx MB
  • KB 2126560 – Understanding and troubleshooting High Availability (HA) on the VMware NSX for vSphere 6.x Edge
    • ​Inline with other HA features, such as vSphere HA or MSCS, Edge HA is not designed to deliver zero downtime as the failover between appliances may require some services to be restarted.
    • ​NSX Edge HA is designed to minimize failover downtime. For example, it synchronizes the connection tracker of the statefull firewall, or the statefull information held by the load balancer. However, the time required to bring all services back up is not null. Examples of known service restart impacts include a non-zero downtime with dynamic routing when an Edge is operating as a router.
    • ​See also the 6.2.2 and 6.1.6 release notes – Fixed Issue [1573818]: [Traffic interrupted for 50 seconds after HA failover on ESG]

 

How to track the top field issues: