VCF on VxRail: vDS Upgrade Behavior in VCF on VxRail Environments
Summary: This article explains the different upgrade behaviors for various types of vSphere Distributed Switches (vDS) during VMware Cloud Foundation (VCF) on VxRail upgrade processes.
Instructions
Issue Description
Customers have reported confusion about whether their vSphere Distributed Switches (vDS) is automatically upgraded during VCF or VxRail upgrade processes. The behavior differs depending on how the vDS was created and which management component is responsible for it.
Different vDS creation methods result in different management ownership and upgrade behaviors:
- vDS created by VxRail Manager during initial deployment
- NSX vDS created during initial deployment of VCF on the VxRail system, also treated as Customized vDS for a VxRail cluster
- Customer-created vDS after VCF/VxRail initiation
Explanation
vDS in VMware Cloud Foundation (VCF) Upgrades
Customized vDS: vDS created by customers after the initial VCF deployment, and NSX vDS Customized vDS are NOT automatically upgraded during VCF upgrades.
Customer Responsibility: Customers must manually manage the upgrade of these vDS configurations. For detailed VCF upgrade planning, see the VMware Cloud Foundation Lifecycle Management documentation below.
vDS in VxRail Upgrades
VxRail Manager-managed vDS: vDS created during the VxRail Manager build process.
VxRail Manager-managed vDS is automatically upgraded during VxRail upgrade processes. These vDS configurations are managed by VxRail Lifecycle Manager (LCM) and are in the automated upgrade workflow.
Customer Responsibility: No customer action required for vDS created by VxRail Manager
Reference VMware Cloud Foundation Upgrade Planning Documentation VMware Cloud Foundation 5.2.x Upgrade Overview