Building a VMware vSphere Virtual Lab with VMware Fusion - Part 3: Deploying vCenter Server Appliance to ESXi 6.7
This is the third part in a series of tutorials on how to build a VMware vSphere Virtual Lab on a Mac with VMware Fusion. In this tutorial, we'll deploy a vCenter Server appliance to an ESXi 6.7 host in our lab.
ESXi on its own is good for when you only have one server and a handful of VMs. But if you want to use advanced features like VMotion, Storage VMotion, vSAN and more, you’ll need to use vCenter Server to manage the hosts. The vCenter UI is a lot better than the ESXi UI and it makes managing multiple hosts much easier.
Since this is a series of tutorials, you should have read and followed the steps in Part 1 and Part 2 before continuing with this tutorial.
It’s important that all the previous steps are followed because deploying vCenter requires a DNS Resolver and we set that up at the end of Part 2.
If you’re just following this tutorial to learn how to deploy vCenter on ESXi, then make sure you have a DNS resolver on your network and the FQDN of the vCenter server appliance is resolvable.
After completing the steps in Part 1 and Part 2, you will be at a point where you have:
- Installed VMware Fusion*.
- Created two custom VMware Fusion networks.
- Created at least one ESXi VM with 10 GB of RAM and three network adapters.
- The first two network adapters will be connected to the vSphere network and the last one connected to the WAN network.
- ESXi should be installed and the management network configured with
10.1.1.11as the IP address and
10.1.1.251as the gateway and DNS resolver.
- Deployed a virtual pfSense firewall to the ESXi hosts with 10 GB of RAM.
- Configured the firewall DNS resolver so that hosts and the vCenter appliance can resolve the IP addresses of other hosts on the vSphere network.
Software required for this tutorial:
- For this tutorial, you’ll need to download the VMware vCenter Server Appliance from the VMware website. The steps in this tutorial have been tested with VMware-VCSA-all-6.7.0-14836122. You can get it by purchasing the vSphere Essentials Kit* or by downloading the free trial.
Once you’ve downloaded the VCSA, mount it by double clicking the ISO file, and we’ll begin the tutorial by deploying vCenter to the first ESXi host which has 10 GB of RAM.
Step 1: Deploy the vCenter OVA
First of all. Login to the ESXi host, click Create/Register VM, select Deploy a virtual machine from an OVF or OVA file and then click Next.
Give the virtual machine a name of vc01, then click on Click to select files or drag/drop.
Navigate to the vcsa folder on the mounted ISO, select the vCenter .ova file and click Open.
You should see the Click to select files or drag/drop text has been replaced with the name and version of the VMware vCenter Server Appliance. Click Next.
Select a datastore and click Next.
Agree to the EULA and copyright agreements by clicking the I agree button two times and then click Next.
Selct the Management network then click Next.
Fill out network configuration with the following details:
|Host Network IP Address Family||ipv4|
|Host Network Mode||static|
|Host Network IP Address||10.1.1.101|
|Host Network Prefix||24|
|Host Network Default Gateway||10.1.1.251|
|Host Network DNS Servers||10.1.1.251|
|Host Network Identity||vc01.graspingtech.com|
Assign the SSO and system password. Since this is a lab, I’ve used
Pa$$w0rd (same password as ESXi hosts) for both. Also assign vc01 for the domain name and graspingtech.com (or your domain) for the domain search path then click Next.
Review the settings are correct then click Finish to deploy the vCenter Server Appliance.
Wait for the files to be copied to the datastore.
Open the console for the vc01 machine and wait for it to boot. You will be presented with the photon-machine login prompt. Don’t login, just wait awhile for the appliance to load.
After waiting patiently, you should see the Virtual Appliance UI has loaded and contains a list of URLs to manage the appliance from.
If you navigate to the main URL for managing the vCenter appliance, it won’t work yet because we need to run the initial set up.
Step 2: Set up vCenter Server Appliance
Open the vCenter appliance set up screen by entering the FQDN of the appliance into a browser with port
5480 instead of
443. For example:
When the screen loads, click the Set up option.
Login with the password you assigned when deploying the appliance.
Click NEXT to proceed with Stage 2.
The correct network settings should already be pre-populated but you might want to change SSH access to Enabled, then click NEXT.
Assign a SSO domain name and password for the administrator account then click NEXT.
Choose wether to join the CEIP or not then click NEXT.
Verify settings are correct then click FINISH to configure the vCenter appliance.
Confirm the warning by clicking OK.
Wait for the configuration process to finish.
Now remove the configuration port number from the address and you should see the main getting started screen.
Click on LAUNCH VSPHERE CLIENT (HTML5).
Enter the username and password then click LOGIN.
We should now be logged into vCenter, and we are ready to start creating a data center, cluster and add our ESXi hosts.
After finishing this tutorial, we should now have three ESXi hosts running on
VMware Fusion* with a pfSense firewall VM and a vCenter Server Appliance running on
In the next tutorial we’ll create a datacenter object to store our hosts and clusters. We’ll create a cluster and we’ll add our hosts to vCenter without having to put them into maintenance mode.
Read Next - Part 4: Adding ESXi Hosts to a Cluster in vCenter Server
As I’m sure you’re aware, there’s only so much information that can go into a blog post, which is why you might want to check out the book titled Mastering VMware vSphere 6.7* Mastering VMware vSphere 6.7* (Marshall, Brown, Fritz, Johnson) to get a more in depth understanding of vSphere.
What the * means above
Links marked with * are affiliated and can earn us a small commission at no additional cost to you, should you click through and make a purchase. For more details, read How This Site Is Financed.