VMware vSAN File Service Agent network(s) "dvportgroup-XXXXXX" not available on host

Products

• VMware vSAN

Issue/Introduction

Symptoms: 

• When enabling vSAN File Services on a Stretched vSAN cluster and choosing to use an NSX Segment split across two Distributed Virtual Switches for the File Services network, you receive errors deploying the vSAN File Services Agent VM's on one site, similar to:

Agent network(s) "dvportgroup-XXXXXX" not available on host

• You have multiple selections for the NSX Segment/subnet on different vSphere Distributed Switches in the Enable File Services Dialog due to creation of NSX sub-transport profile: 

• The Network chosen in the Enable File Services dialog is an NSX Segment defined on separate vSphere Distributed Switches(vDS) at each site using an NSX sub-transport node profile.

Environment

VMware vSphere ESXi 8.x

VMware vSphere ESXi 7.x

Cause

• The network port group or NSX Segment selected for the vSAN File Services network in the "Enable File Services" dialog must be connected to a single vDS that all hosts in the stretched cluster are attached to.

Resolution

• When enabling vSAN File Services, you must choose an NSX Segment or port group connected to a single vDS and accessible to all hosts in the vSAN cluster. Appropriate Layer 3 routing or stretched layer 2 networking must be configured, as needed to accommodate that.
• It is not supported to choose an NSX Segment for the vSAN File Services network if the segment is one of 2 NSX segments defined for the same subnet on separate vDS's for each site. This is typically done by configuring an NSX sub-transport profile for the one site (i.e. hosts at each site are thus connected to different vDS's, despite having an NSX Segment on the same subnet at both sites).  NOTE: See Sub-TNPs and Sub-clusters link below for information on how this would be created.
• Choosing an NSX segment connected to a single vDS that all hosts are attached to is fully supported.

Additional Information

• For VMware vSAN File Service Network Design Considerations, please see also:
  • Networking Considerations for vSAN File Services (TechDocs): https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/vsan-network-design/networking-considerations-for-vsan-file-service.html
  • OVERVIEW: vSAN File Service (TechDocs): https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/vsan-administration/expanding-and-managing-a-vsan-cluster/vsan-file-service.html
  • OVERVIEW: vSAN Network Design/Topologies (TechDocs): https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/8-0/vsan-network-design/understanding-vsan-network-topologies/vsan-stretched-cluster-deployments.html
  • Whitepaper: vSAN Stretched Cluster Guide: https://www.vmware.com/docs/vsan-stretched-cluster-guide
    
    
• For VMware NSX Transport Zones/Transport Profiles Information, please see also:
  • HOWTO: Create Transport Zones (supported for vSAN File Services): https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/transport-zones-and-transport-nodes/create-transport-zones.html
  • HOWTO: Transport Node Profiles (supported for vSAN File Services): https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/host-transport-nodes/preparing-esxi-hosts-as-transport-nodes/transport-node-profile.html
  • Sub-TNPs and Sub-clusters (not supported for vSAN File Services) : https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/host-transport-nodes/preparing-esxi-hosts-as-transport-nodes/sub-tnps-and-sub-clusters.html.