vSAN Configuration Behavior in Stretched Clusters with vSphere Configuration Profiles (VCP)

Products

• VMware vCenter Server

Issue/Introduction

When managing a vSAN stretched cluster using vSphere Configuration Profiles (VCP) in vCenter Server 9.1, users may observe that all vSAN-related settings appear as "Not Configured" within the profile, despite the overall desired state reporting the cluster as "Compliant."

Environment

• Product: VMware vCenter Server 9.1
• Component: vSphere Configuration Profiles (VCP)
• Configuration: vSAN Stretched Clusters

Cause

This behavior is expected in vSphere 9.1. Engineering has confirmed that vSAN stretched clusters are not currently integrated with VCP; only single-site vSAN configurations are supported. For stretched cluster topologies, VCP employs a "no-op" (no operation) approach. As a result, the profile will not present any vSAN-specific configurations, nor will it monitor or report non-compliance for vSAN stretched cluster settings.

Resolution

No action is required to resolve this status. This is the intended behavior for vSAN stretched clusters when managed by vSphere Configuration Profiles in version 9.1.

• The "Compliant" status of the desired state reflects the configuration of other managed components within the profile.
• vSAN stretched cluster configurations must be managed independently of vSphere Configuration Profiles, as they fall outside the current scope of VCP integration.

Additional Information

• vSphere Configuration Profiles (VCP) provide desired state management for supported topologies.
• Administrators should continue to manage vSAN stretched cluster configurations via standard vSAN management workflows.
• Future product updates may expand support for additional vSAN topologies within VCP.