VI workload domain architecture VMware SDDC Manager deploys and provisions each VI workload domain and associated VMware vSphere clusters on the VxBlock System. VMware SDDC Manager manages a VI workload domain. The VI workload domain consists of one or more clusters that are derived from the VxBlock 1000 domains. Each cluster has a minimum of three hosts that use either Cisco UCS B-Series Blade Servers or Cisco UCS C-Series Rack Servers to build your clusters. Management workloads are committed to a management domain, while user workloads get deployed into separate VI workload domains. A dedicated VMware vCenter Server manages each VI workload domain. With dedicated VMware vCenter Servers for each VI workload domain, software updates can be deployed without impacting other VI workload domains. A separate VMware vCenter Server allows for additional segregation for each VI workload domain. VCF standard architecture provides scalability and allows for autonomous licensing and life cycle management. VCF separates management workloads from external workloads to provide better long-term flexibility and expansion options. You can only perform one VI workload domain operation at a time. When you create a VI workload domain, you cannot add a cluster to any other VI workload domain. VCF supports up to 14 VI workload domains on the VxBlock System. Child TopicsVI workload domain configurationsVxBlock System 1000 with VCF allows you to configure four vNICs per service profile. Cisco UCS architectureThe Cisco UCS architecture follows the same VxBlock 1000 architecture model as a non-VCF deployment. For detailed information about Cisco UCS architecture, see the VxBlock System 1000 Architecture Overview. Network standardsVCF on the VxBlock System 1000 adheres to network standards for VMware vSphere 7.0. Virtual network segmentsVirtual network segments are VMware NSX-T managed overlay backed network segments that enable the full suite of VMware NSX-T Data Center features within a VCF deployment. Default VLANsDefault VLANs are deployed on the ToR switch and VMware NSX-T instances based on the VCF topology. VLAN IDs and names are default values, but may be customized before deployment. VMware NSX-T instance deployment topologiesThere are several supported deployment topologies for VMware NSX-T instances with VCF on a VxBlock System 1000. Regardless of the topology, at least three VMware NSX-T instances are deployed on AMP Central for the VI workload domain. TEPs are provisioned on each VI workload domain host, regardless of whether virtual network segments are used. The remaining components are optional.