- vCenter Setup – VMware Workstation Home Lab Setup Part 11
- Importing VCSA via PowerCLI – VMware Workstation Home Lab Setup Part 10
- VMware Workstation Home Lab Setup Part 9 – Importing VCSA via vSphere Client
- VMware Workstation Home Lab Setup Part 8 – Add “Datastores” to virtual ESXi hosts
- VMware Workstation Home Lab Setup Part 7 – Management Tools
- VMware Workstation Home Lab Setup Part 6 – Cloning ESXi
- VMware Workstation Home Lab Setup Part 5 – ESXi Template
- VMware Workstation Home Lab Setup Part 4 – Domain Controller setup
- VMware Workstation Home Lab Setup Part 3 – Domain Controller
- VMware Workstation Home Lab Setup Part 2 – Attack of the Clones
The home lab is getting close! With the vCenter Server Appliance deployed and basic configuration done, its time to get vCenter setup – AD permissions, Data Center, Cluster and adding hosts to the cluster. While there are only 2 hosts so far in the home lab, its still good to get an idea of all of the functions / features so here we go.
vCenter can be a bit of a memory hog, and given our limited resources I really don’t want to force my home lab box into memory crunching. With 32GB of RAM in the host, 2x ESXi virtual machines each with 4GB of RAM and 1x Domain Controller with 2GB of RAM I am using roughly 19% of my total physical memory available (according to Windows) – that is pretty efficent given that I have assigned about 32% of the total system memory to virtual machines alone, never mind Windows 8.1 running, my anti-virus, etc… etc… However when I boot the VCSA which has 8GB assigned, my utilization jumps to almost 50% and I have a lot more virtual machines to deploy! After finishing the VCSA setup wizard I shut the virtual machine off, edited the VM settings to only assign 4GB of RAM – thanks again to William Lam for the research on that. Now power back on the VCSA, in my environment I went from 50% down to 33% – a nice savings for sure.
So, time to log in and get vCenter setup, navigate to https://192.168.6.6:9443 assuming you are using the same IP scheme as me.
A quick aside, you may be wondering why I am using IP’s instead of FQDN’s – my host OS, where I am doing all my work from is not using my lab DC for DNS, thus I have no way to resolve the names without editing my host file. If you want to access vCenter by name, simply add an entry to your host file or point your DNS to the IP of your domain controller.
When the vSphere Web Client login page comes up, log in as firstname.lastname@example.org with the password you set during the VCSA configuration wizard. Once logged in, the first thing you want to probably do is get rid of that pesky welcome screen, however if you are new to the vSphere Web Client take some time to check it out before disabling it and check out my other tips on the vSphere Web Client. So here we go…
vCenter Setup: Permissions
- Once logged into the vSphere Web Client click on Administration >> Configuration
- If your domain is not listed, click on the green + icon
- Select the first radio button under Identity Source Type: Active Directory (Integrated Windows Authentication)
- Ensure use machine account is selected and click the OK button
- Select your domain and click the the CD looking icon with the blue arrow, this will set your domain as the default so you can log in as adusername instead of email@example.com
- Click on Users and Groups, change the Domain pull down menu to your domain; ensure you can see users in your Active Directory and do not receive any error messages
- Click on the home link >> vCenter >> vCenter Servers; click on your vCenter server – in my case vxprt-vc01
- Click on the manage tab >> permissions
- Click on the green + icon, then click the Add button
- Ensure the domain pull down is your Active Directory Domain
- In my AD I have created a group called vcAdmins and an administrative user for myself; jfadmin which is a member of the vcAdmins group. In the search box type vcAdmins or which ever group name you wish to assign full administrative privileges to.
- Highlight the group, click the Add button then click OK
- In the Assigned Role pane select Administrator
- Click the OK button and ensure the group was added
- Log out of vCenter and log back in with a user account that is part of the vcAdmins group
- Once signed back in, click on vCenter and confirm you can see the vCenter server in inventory
vCenter Setup: Create Datacenter
Now that we are logged into vCenter with an administrative user, it’s time to setup our datacenter. Now a data center is really just a construct/container in vCenter. If I wanted I could create multiple data centers inside vCenter even if all of the compute resources were in the same physical location, even in the same rack, even sharing the same network. What I would not be able to do as of vSphere 5.5 is vMotion or “live migrate” virtual machines from one data center to another. In my lab I will be creating a single data center.
- Click on Hosts and Clusters
- Ensure you are on the summary tab and see vCenter in the Navigation pane
- Right click on your vCenter and select New Datacenter…
- As you can see from the wizard, there isn’t a lot we can do in terms of settings at the data center level, name your datacenter, I prefer short names so I am going with dc01; click the OK button
A quick aside here; keep in mind when naming components in vCenter that down the road you may need to integrate other products. For example in the past I have seen problems when trying to use Vagrant to bring up virtual machines in vSphere because of spaces in the names datacenters or clusters. Keep your naming simple but identifiable. I also prefer all lower case for my naming scheme.
vCenter Setup: Create Cluster
With the datacenter created, we can now create our clusters. Clusters play a big role in vSphere so while they are simple to create, managing the settings at the cluster level are vital to understand. We’ll get into that in a future post but just know a cluster is where your add resources such as compute/servers and configure VSAN, EVC, HA and DRS, assuming you have the appropriate licensing.
- Right click on your newly created datacenter and select new cluster
- You can see that there are quite a few options here for the cluster, we won’t enable them all now but have a peak through and see what is available
- Name your new cluster, again I prefer simple so cl01 will be my cluster name; click the OK button
With different physical hosts, EVC is one item you may have enabled right away. EVC “standardizes” on a processor feature set so that virtual machines can move between different physical hosts with different processors, assuming those processors can share a common processor feature set. You cannot mix Intel and AMD processors. In this home lab build with all virtual ESXi hosts, our hosts processors will all be identical.
vCenter Setup: Add hosts to cluster
Now with our cluster build, we can now add the two virtual ESXi hosts we created in workstation earlier. There will be warnings/errors after adding the hosts, don’t worry those are expected and we’ll take care of them!
- Right click on the cluster you just created and select Add hosts…
- Type the hostname of one the ESXi hosts you created in DNS, in my case vxprt-esxi01 and vxprt-esxi02, click next
- Type the username (root) and password you set during setup, click next
- When prompted to accept the certificate, click yes
- Review the information and click next
- On the license screen you can use the trial license or if you have license keys, enter the key here and click next
- Click next on the lockdown mode screen without selecting the Enable lockdown mode checkbox (lockdown mode disables access to the DCUI)
- Click finish, the host will be added to the cluster
- Repeat for the remaining virtual ESXi hosts you created
If you added local storage to your first ESXi hosts like we did in a previous posts you should see that host added with no warnings. The 2nd ESXi hosts has no storage available for logs because it was only setup with a 1GB drive for the OS.
You now have the basics of a working vCenter setup, up next is some of the more advanced features like vMotion and HA!