Since VSAN is not yet integrated with the vSphere Configuration Profile (VCP), after enabling vSAN on a VCP enabled cluster, VCP check compliance will report certain drifts in the desired configuration.
Drifts under 'network' settings:
These are the services that are currently supported and can be enabled on the vmknics. Among them, vsan, vsanExternal and witness services can show up as drifts as part of vSAN cluster workflows:
faultToleranceLogging
management
vsphereProvisioning
vsphereReplication
vsphereReplicationNfc
vmotion
vsan
witness
vsphereBackupNfc
precisionTimeProtocol
nvmeTcp
nvmeRdma
vsanExternal
The following drifts might be seen under 'network_vss' settings:
/<>/esx/network_vss/switches/<vSwitchId>/port_groups/<port_group_id>/policy
The forged_transmits and allow_promiscuous configs under 'policy' are enabled as part of the vSAN File Services enablement process and are flagged as drifts as it is not configured through VCP.
VMware vSphere 8.0U3 and 9.0
The VSAN cluster workflows use host-level imperative API to configure certain settings on the hosts. However, in a VCP enabled cluster the source of truth for all the host settings is the cluster desired configuration. As a result, such settings changed by VSAN workflows are flagged as drifts w.r.t cluster desired configuration.
Follow the steps mentioned below to absorb all of the reported drifts into the desired configuration: