vSphere with Tanzu LAB Environment Installation Step-by-Step (Included vCenter, vSAN, NSX, Supervisor Cluster and pfSense)-3
vCenter installation and configuration on Physical Infrastructure
We mount the vCenter ISO that we downloaded on the Physical Infrastructure terminal.
On the Physical Infrastructure, we select the vCenter OVA file and deploy it.
We continue by ignoring the certificate warning.
You can specify the vCenter size based on your resources. I’m using the Small vCenter Large Storage.
Don’t forget to select Thin Provision for vCenter!
Because the installation is on the Physical Infrastructure, we choose ACME-MANAGEMENT as the Port Group.
We enter the following parameters in order according to our own LAB environment.
We don’t upgrade so we leave it blank!
We enter the domain information.
We review all the parameters and start the import process.
NOTE: If there is an incorrect parameter, vCenter may not work properly. In such a case, delete the vCenter Appliance and import it again!
After vCenter OVA Import is completed, we Power-on. The initial configuration is going to be completed for 4–5 minutes, then you are going to continue the installation with Stage-2 on the VAMI interface.
We go to Stage-2 by choosing Setup.
We enter NTP information for vCenter and activate the SSH service.
We enter SSO access information.
NOTE: If you set up a Multi-Site structure, you select the Join an existing SSO domain parameter for the second vCenter. Thus, the second vCenter is going to be Join into the first vCenter PSC and Linked Mode are going to be established in between.
(Multiple vCenter are going to be managed on single GUI)
Review everything again, if you are sure that it is correct, start the final configuration with Finish.
After the installation is complete, you can now access the vCenter interface via the link.
Creation of vCenter Cluster on Nested Infrastructure and adding of ESXi Nodes
We are creating a new Datacenter.
We create a new cluster. We are not doing anything for DRS, HA and vSAN right now!
We are adding the ESXi Nodes we have setup for Nested Infrastructure.
VDS and Port Group configuration on Nested Infrastructure
We create MANAGEMENT and TRUNK Virtual Distributed Switches.
We created two Virtual Distributed Switches required for Nested Infrastructure.
For VDS, which is TRUNK, we set the MTU value to 9000. vSAN, vMotion and NSX-T VMkernel networks will passthrough this VDS!
We create Port Group for Management Network under MANAGEMENT VDS.
We add ESXi Nodes to MANAGEMENT VDS with Add and Manage Hosts.
We reserved the first two Virtual NIC for MANAGEMENT VDS. We Assign vmnic0 and vmnic1.
We assign Host Management VMkernel Adapter on MANAGEMENT VDS.
We do the same settings for TRUNK VDS.
We reserved the last two Virtual NIC for TRUNK VDS. We Assign vmnic2 and vmnic3.
We don’t Assign Host Management VMkernel Adapter for TRUNK VDS. (Pass this part for TRUNK VDS)
We do a general check, if our definitions are correct, we start creating our Port Groups on TRUNK VDS.
We are creating a Port Group for vMotion.
We choose TRUNK as the VLAN type.
We add vMotion VMkernel Adapter on vMotion Port Group.
We attach all ESXi Nodes.
We choose vMotion as Available Services.
We enter IP addresses from the ACME-vMotion-vLAN network.
If everything is correct, we save our settings.
We are creating a Port Group for vSAN.
We choose TRUNK as the VLAN type.
We choose vSAN as Available Services.
We enter IP addresses from the ACME-vSAN-vLAN network.
If everything is correct, we save our settings.
We do a general check for VMkernel Adapters.
We have completed your general configuration for vCenter.
Part 4.
- vSAN Cluster configuration on Nested Infrastructure
