VMware Inc.

08/30/2023 | News release | Distributed by Public on 08/30/2023 16:00

Top 10 Most Popular Knowledge Articles for SRM, vSan, and Core Storage for August 2023

Get answers and solutions instantly by using VMware's Knowledge Base (KB) articles to solve known issues. Whether you're looking to improve your productivity, troubleshoot common issues, or simply learn something new, these most used and most viewed knowledge articles are a great place to start.

Here are the top 5 most viewed KB articles for SRM, vSan, and Core Storage:

  1. What You Can (and Cannot) Change in a vSAN ESA ReadyNode™ (90343)

Discover the vSAN Express Storage Architecture (vSAN ESA) introduced in vSAN 8.0, offering an alternative to vSAN Original Storage Architecture (vSAN OSA). Learn about vSAN ESA ReadyNodes - pre-configured, tested, and certified x86 servers from leading vendors. Explore FAQs addressing hardware requirements, storage devices, networking, and more, with guidance on vSAN ESA profiles and allowable changes.

  1. ESXi 7.0 Update 3 host fails with a backtrace NMI IPI: Panic requested by another PCPU. (86100)

This KB dicusss how after upgrading to ESXi 7.0.3 Build: 18644231, thin provisioned virtual disks (VMDKs) on VMFS6 datastores might trigger multiple hosts in an HA cluster to fail with a purple diagnostic screen. The issue is traced back to a maximum UNMAP granularity change introduced in VMFS, affecting Thin Provisioned VMDKs. Find out the cause, impact, resolution, and workaround options to prevent this issue.

  1. Urgent Patch (8.0U1c) Available to Prevent Inaccessible Data Risk for VMs on vSAN ESA (Version 8.0, 8.0 P01, 8.0 U1, 8.0U1a (EP1)) (93657)

This KB addresses a rare issue affecting VMs running on vSAN ESA versions 8.0, 8.0 P01, 8.0 U1, and 8.0U1a (EP1) that have snapshots. The issue results in inaccessible data and is characterized by VMs being unable to power on, unresponsive hosts, and potential PSOD occurrences. The article recommends upgrading to vSAN ESA version 8.0U1c to mitigate this risk. The issue is more likely with high-frequency snapshot activities, and adjusting snapshot schedules can temporarily reduce risk. The KB outlines specific steps for upgrading and configuration adjustments to prevent the problem, as well as offering manual download instructions for the patch.

  1. Object health issue 'Reduced availability with no rebuild' (83173)

This KB addresses an issue occurring when converting a regular vSAN cluster to a stretched cluster on vCenter/ESXi versions up to 7.0U3c. After conversion, some objects exhibit red health status with the problem 'Reduced availability with no rebuild'. The root cause is traced to a CLOM bug that misplaces components during configuration conversion, leading to data availability problems. The issue is resolved in VMware ESXi 7.0 Update 3c. Workarounds include reverting to a regular vSAN cluster before conversion and performing specific host maintenance steps during the conversion process to ensure object health.

  1. RHEL High Availability Cluster on VMware vSphere 7.x, 8.0: Guidelines for supported configurations (85598)

This KB offers guidance for setting up RHEL High Availability Clusters with shared disks on vSphere 7.0 Update 3 and later. It covers compatibility, storage configuration, virtual SCSI settings, fencing agents, vWDT usage, and supported vSphere features like vMotion and HA. The article emphasizes proper cluster setup, network requirements, and limitations, including avoiding certain VM hardware changes and unsupported features. It's a comprehensive resource for ensuring a stable RHEL High Availability Cluster in the vSphere environment.

Here are the top 5 most linked KB articles for SRM, vSan, and Core Storage:

  1. Site Recovery Manager (SRM) Storage Replication Adapter (SRA) Issues (88434)

This KB addresses storage problems encountered with VMware's Site Recovery Manager (SRM), specifically concerning Array Based Replication (ABR). It explains SRM's role in orchestrating replication and offers guidance on resolving issues such as incomplete replication, failed Promote/Demote processes, and more. The article emphasizes contacting both the storage vendor and VMware Support for assistance. It provides steps to rescan arrays and devices, highlights compatibility resources, and outlines API workflows between SRM and ABR. The KB serves as a troubleshooting reference for resolving SRM-related storage challenges.

  1. SRM or VR is unable to connect to vCenter after PSC is converged to Embedded PSC or vCenter SSL changed (85970)

This KB deals with errors during SRM (Site Recovery Manager) convergence after the External Platform Services Controller (PSC) deprecation. It covers issues like 'null' UI display, service crashes, and modification errors. The article outlines steps to update PSC URLs, SSL checks, and DB modifications, emphasizing restarting services and reconfiguring. It's a resource for addressing challenges post PSC convergence, impacting SRM and VR (vSphere Replication) operations.

  1. How to handle inconsistent cluster power status in vSAN shutdown workflow (87350)

This article addresses vSAN cluster power status problems occurring after shutdown operations through the vCenter UI. The recommended resolution is to upgrade vCenter and ESXi to version 7.0U3d or higher. Workarounds involve manual adjustments to the cluster power status using commands or the vSAN Managed Object Browser (MOB). These workarounds are applicable based on the specific scenario encountered.

  1. ESXI Host reports PSOD due to async qedi driver in use (91503)

This article addresses random host crashes (PSOD) caused by packet corruption due to misconfigured software iSCSI using QLogic QL41xx or QL45xx CNAs. Misusing iSCSI NICs as normal NICs can result in PSOD, impacting VMs and services abruptly. To resolve, validate NIC configuration (esxcfg-scsidevs -a) and use proper NICs for iSCSI or switch to hardware iSCSI.

  1. Inaccessible objects in vSAN when all components show as Active (90851)

This article addresses the issue where vCenter displays inaccessible objects with a health status of "inaccessible - Object is initializing or creating (APD)." Running esxcli vsan debug object list -all shows such objects. The cause is the advanced setting /VSAN/DOMPauseAllCCPs set to 1 on certain hosts in the cluster, leading to objects going into the APD state. This setting is used for cluster reboot/shutdown.

Our curated solutions are available 24/7 through VMware KB Articles. Make sure to also check our other resources:

  • Knowledge Base : So many articles. So many topics. Find what you need.
  • Product Documentation : Explore a full range of technical documentation including manuals, release notes, and more.
  • Tech Zone : Go from zero to hero with the latest VMware technical resources.
  • Technical Papers : Access content written by VMware technical experts.
  • VMware Blogs : Benefit from the experience of industry professionals from around the VMware community.