Infrastructure Subnet

As I discussed in the previous post, I am going to separate my environment into 3 different class B subnets so that I have some logical separation between the various aspects of this environment. My first class B subnet is going to be for the infrastructure/physical VMware Cloud Foundation architecture.

I decided to build a physical and nested VCF architecture because in the physical side I can test out a true deployment on a single host and use this deployment as my test bed for my own training and hands-on experience with it. I don’t want to muddy up my VCF deployment when assisting customers so I will also deploy nested VCF environments that can be spun up on the fly as needed and rebuilt quickly using Powershell scripts and PowerCLI module.

So back to my infrastructure subnet, I know that with VCF we will at least need 5 subnets just to deploy this but my experience with the product also tells me that I will end up needing more than just that so the list below will explain the segments I am creating and reasoning behind them

/28 Out of Band ManagementThis will be for the iLO, iDRAC and NAS Management
/27 vSphere/ESXi ManagementESXi Physical Host Management Segment
/27 vMotionDHCP Pool for Physical Host vMotion Segment
/27 vSANDHCP Pool for Physical Host vSAN Segment
/27 iSCSIDHCP Pool for iSCSI connections to QNAP volume
/27 ProvisioningDHCP Pool for Physical Host Provisioning Network Segment. Provisioning is used for cold migrations, cloning and snapshots
/29 Domain ServerThis will be used for LDAP,DNS,ADFS and Certificate Authority
/29 Lab ServersThis will be used for IPAM, Ubuntu desktop, VCF offline depot, SFTP backup server and others
/28 Wired DHCPDHCP Pool for management computers using the lab network
/28 Wireless DHCPDHCP Pool for wireless management connections
/28 TemplatesDHCP Pool for Virtual machine template creation
/25 VM ManagementThis will be used for virtual machine management for VCF (vCenter,NSX,Fleet,Ops, etc..)

Yes this a good amount of subnets to create but these are what I determined are needed based on my experience with other labs and wanting to ensure I have logical separation for all the various pieces I am going to be deploying.

Check out my next posts where I will go into details on the networking and nested subnets.