{"id":1882,"date":"2024-01-06T15:22:55","date_gmt":"2024-01-06T20:22:55","guid":{"rendered":"https:\/\/ithinkvirtual.com\/?p=1882"},"modified":"2024-01-06T15:23:00","modified_gmt":"2024-01-06T20:23:00","slug":"nested-vsphere-home-lab-part-3-vsphere-8-x-lab-deployment","status":"publish","type":"post","link":"https:\/\/ithinkvirtual.com\/2024\/01\/06\/nested-vsphere-home-lab-part-3-vsphere-8-x-lab-deployment\/","title":{"rendered":"Nested vSphere Home Lab \u2013 Part 3 \u2013 vSphere 8.x Lab Deployment"},"content":{"rendered":"\n
Welcome back! In my previous<\/a> post, I covered the deployment and configuration of an Active Directory and Microsoft Certificate Authority server(s) for the nested lab environment.<\/p>\n\n\n\n Next, I will cover the steps used to deploy the nested lab via William Lam’s Automated Nested Lab Deployment script<\/a>.\u00a0 This script makes it easy to deploy a set of vSphere Hypervisor (ESXi) VMs, along with a VMware vCenter Server Appliance virtual machine to manage the nested lab environment.<\/p>\n\n\n\n I will not go into detail here on how to use William’s script, as he’s done a fine job documenting the process on both his blog<\/a> and GitHub<\/a> pages.\u00a0 However, what I will cover are the tweaks I’ve made to deploy and configure the lab environment to my needs for this series.\u00a0 So let’s get to it!<\/p>\n\n\n\n <\/a><\/p>\n\n\n\n As I’ve stated in an earlier post, I am deploying this nested lab on a Dell PowerEdge R720 server. I swapped out the original dual CPUs in favor of dual Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz CPUs so that I could leverage my 768GB of available RAM that I was able to score fairly cheap on eBay.<\/p>\n\n\n\n I also swapped out the RAID controller for an H710p which I also scored for cheap on eBay, so that the server would recognize the local disks with ESXi 8.0.<\/p>\n\n\n\n For shared storage, I have some SSDs configured as an NFS datastore from my Synology RS3618xs. I also have configured some local direct-attached storage (DAS) where I’ll be deploying the nested lab to; a 1TB Timetec SSD housed in a CDROM\/SATA to M.2 adapter, as well as a 2TB Samsung 970 Evo Plus M.2 in a PCI-E adapter. This is where the router and domain controller VMs reside. The latter is reserved for future use with nested VMware Cloud Foundation via the Holodeck Toolkit!<\/p>\n\n\n\n After obtaining and modifying the deployment script to point to the required binaries and networking set to the nested trunked portgroup, I ran the deployment and was provided with deployed and configured vCenter Server Appliance and a number of ESXi host VMs. I then modified the script again, this time changing the ESXi VM hostnames and IP addresses so that I can deploy a second cluster of hosts for the lab environment. I also modified the following and redeployed the script:<\/p>\n\n\n\nPhysical Hardware<\/h3>\n\n\n\n
vSphere Lab Deployment<\/h3>\n\n\n\n
Prerequisites<\/h4>\n\n\n\n
\n
Tweaks & Configuration<\/h4>\n\n\n\n
Note: Modifying the following is not normally recommended. Do this at your own risk.<\/pre>\n\n\n\n