Table 5. VLANs and IP subnets for a sample deployment
Workload Domain
Cluster
VLAN Function
VLAN ID
Subnet
Gateway
Management
Cluster-01
Management
1611
172.16.11.0/24
172.16.11.253
vMotion
1612
172.16.12.0/24
172.16.12.253
vSAN
1613
172.16.13.0/24
172.16.13.253
VXLAN (NSX VTEP) 1614
172.16.14.0/24
172.16.14.253
vRealize Suite
(optional)
1616
172.16.16.0/24
172.16.16.253
Uplink 1
2711
172.27.11.0/24
172.27.11.253
Uplink 2
2712
172.27.12.0/24
172.27.12.253
NOTE:
Cloud Foundation deploys vRealize Suite products to a dedicated VLAN-backed vSphere Distributed Port Group. The IP
subnet must be routable to the Cloud Foundation management network and the firewall. Also, the networks should be disabled or
configured as prescribed in the Cloud Foundation documentation.
Host names and IP addresses
Before deploying a Cloud Foundation, or creating or expanding a workload domain, you must define the hostnames and IP addresses for
various system components.
Most of the defined hostnames and IP addresses need to exist in DNS and be resolvable, through forward and reverse lookups.
The required hostnames and IP addresses are categorized as follows:
•
External services—services that are external to the Cloud Foundation solution and are required for proper operation.
•
Virtual infrastructure layer—components that provide for the basic foundation of the Cloud Foundation solution.
•
Operations management layer—components used for day-to-day management of the environment, for example, vRealize Operations.
•
Cloud management layer—services that use the infrastructure layer resources, for example, vRealize Automation.
Host names and IP addresses for external services
External services such as Active Directory (AD) and NTP must be accessible and resolvable by IP Address and Fully Qualified Domain Name
(FQDN). Acquire the hostnames and IP addresses for AD and NTP before deploying Cloud Foundation.
Allocate hostnames and IP addresses to the following components:
•
NTP
•
AD
•
DNS
•
Certificate Authority (CA)
The following table provides sample information for the external services. This example uses a DNS domain called
rainpole.local
for
illustration purposes. Modify the sample information to conform to the configuration of your site.
Cloud Foundation and SDDC design considerations
35
Summary of Contents for PowerEdge MX7000
Page 1: ...Dell EMC VMware Cloud Foundation for PowerEdge MX7000 Deployment Guide ...
Page 8: ...Figure 1 Cloud Foundation deployment workflow 8 Overview ...
Page 27: ...Figure 19 Dual PowerEdge MX7000 enclosure configuration Physical layout 27 ...
Page 29: ...Figure 20 MX9002m Management module cabling Physical layout 29 ...
Page 30: ...Figure 21 Connectivity between FSE modules and FEM modules 30 Physical layout ...
Page 31: ...Figure 22 Uplinks to customer network environment Physical layout 31 ...
Page 42: ...Figure 25 MX9002m Management Module cabling 42 Networking requirements ...
Page 43: ...Figure 26 Connectivity between FSE modules and FEM modules Networking requirements 43 ...
Page 44: ...Figure 27 Uplinks to customer network environment 44 Networking requirements ...