Create a Nested ESXi 6.0 lab using VMware Fusion 8

Standard

I wanted to create this post because like me, many people just don’t have all the necessary equipment to create a full blown lab to play around and test things in. Also, I like the ability to be portable and I think its safe to say that a server isn’t the most portable thing in the world. In comes the powerful laptop. At my disposal is a Mid 2015 MacBook Pro with a 2.5 GHz Intel Core i7 with 16GB of DDR3 RAM and a 512GB SSD. I’m storing all my VMs on an external SanDisk 480GB SSD external drive. With this, combined with VMware Fusion 8, I am going to show you how to create a vSphere 6 environment. We will also create shared storage so that we can test features like HA and svMotion. Let’s get started.

The first thing we want to do is create our different networks for the different vSphere features that we want to use. We will create 5 different subnets for our network, one for each feature.

10.10.2.0 – Management Network
10.10.3.0 – iSCSI/Storage Network
10.10.4.0 – Fault Tolerance Network
10.10.5.0 – vMotion Network
10.10.6.0 – VM Network

2015-11-25_10-20-03_01

Our network settings for each of our networks should appear like this

2015-11-25_10-20-04_012015-12-02_11-54-57Once we have our networks created, we will create our two ESXi hosts. We are going to add a total of seven NICs to each of our hosts. Two for management, two for iSCSI storage, one for Fault Tolerance, one for vMotion, and one for the VM Network. Let’s get started…

First lets create a blank VM2015-12-02_11-54-58_01

Select VMware ESX > VMware ESXi 6 and click Continue

2015-12-02_11-55-16

At the Virtual Disk page click Continue

2015-12-02_11-55-16_01

Since we are trying to conserve disk space, we are going to reduce the size of the hard disk from 40GB to 3GB because ESXi is such a small install. Click Customize Settings

2015-12-02_11-55-17

Select Hard Disk

2015-12-02_11-55-17_01

Change the disk size to 3GB

2015-12-02_11-55-18

Start the VM and lets attach our ESXi 6 ISO and connect the CD/DVD Drive2015-12-09_15-09-15

Boot to the installer

2015-12-02_11-54-59_012015-12-02_11-55-00

Press Enter to continue2015-12-02_11-55-01

Press F11 to accept the EULA and continue2015-12-02_11-55-01_01

Select the disk that you want to install ESXi on…in this case we only have the one 3GB disk that we resized. Press Enter2015-12-02_11-55-02

Select your preferred language and press Enter2015-12-02_11-55-03

Create a root password . Write this password down because we are going to need it later when we start configuring the host. Press Enter.2015-12-02_11-55-042015-12-02_11-55-05

Press F11 to Install2015-12-02_11-55-05_012015-12-02_11-55-06

Our installation is complete. Press Enter to reboot the server and we will begin initial configuration.2015-12-02_11-55-07

Here we are at the final screen after the server boots up completely. Now press F2 and enter in the root password that we just created2015-12-02_11-55-082015-12-02_11-55-09

Now we are at the System Customization screen. Let’s configure the IP address and NIC that we are going to use to communicate directly with the host. Select Configure Management Network from the list2015-12-02_11-55-09_01

Select IPv4 Configuration2015-12-02_11-55-10

Here, we want to select Set static IPv4 address and network configuration and enter in our IP address. Remember, this is our management network that is on our 10.10.2.0 network. The default gateway in this case is going to be the IP address of our domain controller. We will get to the creation of our domain controller next so for now just take note of the address for the default gateway, as we will assign that same address to the DC.2015-12-02_11-55-11

After setting our IP address and pressing enter, let’s change our DNS Hostname. Do this by selecting DNS Configuration from the Configure Management Network menu. Enter in the IP address of the DC for the Primary DNS server and enter in the hostname that you want your host to be identified by.2015-12-02_11-55-12

After pressing enter and Esc to return to the main startup screen, we will receive this notice about applying our recent configuration changes. Press Y to accept these changes.2015-12-02_11-55-13

This is just a personal preference for me…but I always disable IPv6 on my hosts2015-12-02_11-55-13_01

This will require a reboot before the changes take effect2015-12-02_11-55-142015-12-02_11-55-15

While the restart of our ESXi host is taking place….let’s go and create a Windows 2012 R2 server to be used as our domain controller for our environment. We will also create another 2012 server for our vCenter. 2015-12-02_11-54-58_01

Choose Windows Server 2012. Click Continue.2015-12-02_11-54-59

Create a new virtual disk. Click Continue.2015-12-02_11-55-19_01

Before we finish up, we need to make a change to the network adapter and make it available on our 10.10.2.0 network. Click Customize Settings.2015-12-02_11-55-20

Change the network adapter to vmnet22015-12-02_11-55-20_01

Attach a Windows 2012 R2 ISO to the VM to start the install. Click Next.

2015-12-02_11-55-21

Select Windows 2012 R2 Server (Server with a GUI). Click Next2015-12-02_11-55-22

Select Custom and select the blank partition and click next to being the install2015-12-02_11-55-232015-12-02_11-55-23_01

Once the Windows install is complete, the first thing that I like to do is install VMware Tools and save the VM.

2015-12-02_11-55-242015-12-02_11-55-25

Now let’s begin making this server into a domain controller. Under Server Manager > Manage select Add Roles and Features.2015-12-02_11-55-27

Under Server Roles select Active Directory Domain Services and click Add Feature2015-12-02_11-55-28

Click Next and let the install begin2015-12-02_11-55-28_01

After the install completes, we have some post configuration to do. Click the flag marker at the top of the Server Manager panel to reveal the Promote this server to a domain controller option.2015-12-02_11-55-29

We want to select Add a new forest and name it. For my domain I selected the name lab.local but you can put whatever name you want here. Click Next and continue with the rest of the domain controller setup. I’ll assume that you know how to do the rest. Quite simply just leave everything else as default until the wizard finishes2015-12-02_11-55-30

Next, we are going to create our vCenter server. First, create another server just like the one we created for our domain controller except we need to have two processors and 8GB of RAM to meet the system requirements for vCenter to install. Also, we are going to use our vCenter server to provide shared storage to our ESXi hosts. We will go through that after we install vCenter. Mount the vCenter ISO.2015-12-10_16-56-39

Launch the installer for VMware vCenter and click Install

2015-12-02_11-55-32

2015-12-02_11-55-33

Accept the EULA and click Next2015-12-02_11-55-34

Select Embedded Deployment2015-12-02_11-55-35

Enter the FQDN or IP of the vCenter server. I added a host record in DNS for vCenter.lab.local so that I can enter the name instead of the IP address. Click Next.2015-12-02_11-57-31

Enter a SSO domain name and site name to your liking and enter a password for the SSO administrator account. Click Next.2015-12-02_12-04-34

Leave everything else as is for the rest of the install and just keep clicking Next.2015-12-02_12-04-34_01

2015-12-02_12-04-35

2015-12-02_12-04-362015-12-02_12-04-56

Click Install and get ready to hurry up and wait….and wait….annnnd…yep…wait!!!2015-12-02_12-05-15

Finally the install is complete2015-12-02_16-52-38

Now let’s being to setup our shared storage for our ESXi. As mentioned earlier, we are going to use the vCenter server to do this. On the vCenter server, go to Server Manager > Manage > Add Roles and Features. Click Next.2015-12-08_15-14-04

Click Next2015-12-08_15-14-14

Click Next2015-12-08_15-14-23

Under File and Storage Services, select iSCSI Target Server and iSCSI Target Storage Provider. Click Next2015-12-08_15-14-51

Click Next2015-12-08_15-15-15

Click Install2015-12-08_15-15-27

Click Close2015-12-08_15-16-54

Now we want to add two 200GB disks to our vCenter server to serve as shared storage.

2015-12-08_15-17-23

Once you add the two disks, they will appear in Disk Management. Bring them online, initialize them, create two new volumes and format them2015-12-08_15-18-062015-12-08_15-18-182015-12-08_15-18-272015-12-08_15-18-422015-12-08_15-18-522015-12-08_15-19-072015-12-08_15-19-252015-12-08_15-19-36

Now go under Server Manger > File and Storage Services > iSCSI. Click To create an iSCSI virtual disk, start the New iSCSI Virtual Disk Wizard2015-12-08_15-21-10

Select one of the 200GB volumes. Click Next2015-12-08_15-21-25

Create a name for the iSCSI disk. Click Next2015-12-08_15-21-40

In order to conserve space, select Dynamically expanding. This will thin provision the volume and only use the amount of physical storage as we need it. Click Next.2015-12-08_15-21-59

Now we need to create our iSCSI targets. These will be the IP addresses for the NICs used for iSCSI on our ESXi hosts. Select New iSCSI target. Click Next.2015-12-08_15-22-16

Create a name and click Next2015-12-08_15-27-50

Click Add2015-12-08_15-22-53

Change the type to IP address and enter in all of the IP addresses…you have to do them one at a time… that the ESXi hosts will be using. It will be four since we have two nics on each host that we will use for the storage network 2015-12-08_15-24-02

Click Next2015-12-08_15-29-05

Click Next2015-12-08_15-24-42

Click Assign2015-12-08_15-29-162015-12-08_15-29-28

Now we have to shutdown the vCenter VM so that we can add another NIC to it and assign it to the 10.10.3.0 network, which is our storage network2015-12-08_15-32-442015-12-08_15-33-382015-12-08_15-33-52

Also, while we are adding NICs, let’s go ahead and all all the rest of the NICs that we need to our ESXi hosts. We will have a total of seven NICs on each host. The config should be as followed:

NIC1 – vmnet2 10.10.2.0 Management
NIC2 – vmnet3 10.10.3.0 Storage
NIC3 – vmnet3 10.10.3.0 Storage
NIC4 – vmnet4 10.10.4.0 Fault Tolerance
NIC5 – vmnet5 10.10.5.0 vMotion
NIC6 – vmnet6 10.10.6.0 VM Network
NIC7 – vmnet2 10.10.2.0 Management2015-12-08_15-39-49

Back on our vCenter server, let’s configure the newly added NIC and give it an IP address on the 10.10.3.0 network

2015-12-08_16-04-172015-12-08_16-04-18

I renamed mine so that it is easily identified 2015-12-08_16-04-51

Give it an IP address
2015-12-08_16-10-58

Launch the vSphere Web Client and login as administrator@vsphere.local. We are now ready to begin adding our hosts to vCenter2015-12-08_16-48-17

First create a Datacenter by right clicking the vCenter object and selecting New Datacenter.2015-12-08_16-48-33

After creating a Datacenter, right click the Datacenter and select New Cluster. Give the cluster a name and turn on HA and DRS by checking the boxes next to the two feature.

2015-12-08_16-49-29

After we create the cluster, we will be able to right click it to add a new host2015-12-08_16-50-23

Enter in the root username and password for the ESXi host2015-12-08_16-50-54

Click Yes on the certificate security alert

2015-12-08_16-57-59

Click Next

2015-12-08_16-58-16

Assign the Evaluation License by clicking Next2015-12-08_16-58-30

Leave Lockdown mode disabled

2015-12-08_16-58-41

Click Next

2015-12-08_16-58-50

Click Finished

2015-12-08_16-59-00

Now the host will be added to the cluster. Note that you will get an error about HA not being able to be configured properly. This is because we do not have our NICs configured yet. 2015-12-08_17-01-29

Notice that we only have one NIC associated with our management network. We need to assign an additional one.2015-12-09_10-42-13

We need to go to the console of our host and login to it and add the second management adapter. Login as root and under System Configuration we will go to Configure Management Network.2015-12-09_10-43-28

Select Network Adapters. Under Network Adapters we will see vmnic6. Select that NIC to add it as part of the Management adapters. Press Enter.2015-12-09_10-44-12

Press Y to apply the changes2015-12-09_10-44-34

Going back to our web client, let’s add the second NIC to the Management network. Right click the host and select Add Networking. Select Physical Network Adapter2015-12-09_10-48-02

Click Next

2015-12-09_10-48-13

Select vmnic6

2015-12-09_10-48-26

Click Next and Finish. Now Edit the settings of the Management Network port group. Under Teaming and failover, we want to make both adapters active by selecting vmnic6 and using the arrow to move it under Active adapters. Click Ok.

2015-12-09_10-46-12

Now let’s add the rest of our NICs to our ESXi host. Right click the host and select Add Networking. Select Physical Network Adapter

2015-12-09_10-48-13

2015-12-09_10-48-39

2015-12-09_10-49-17

Let’s add our first VMkernel adapter so that we can add the shared storage to our hosts. Right click the host and select Add Networking. Select VMkernal Network Adapter.

2015-12-09_10-50-48

Click Next

2015-12-09_10-50-57

Enter a label for the port. I used ISCSI01. Click Next

2015-12-09_10-51-23

Enter a IP address on the 10.10.3.0 network

2015-12-09_10-52-42

Click Next and Finish. Now go and edit the setting of the ISCSI01 port group

2015-12-09_10-53-24

Under Teaming and failover, check the Override box. Make it so that only one of the NICs on the 10.10.3.0 is active and the other NIC on that same network is standby. Make all other nics apart of the unused adapters2015-12-09_10-54-54

Repeat the same steps again but instead, the NIC that you make active and standby, swap them around. Make vmnic2 active and vmnic1 standby.

2015-12-09_10-55-332015-12-09_10-55-522015-12-09_10-56-012015-12-09_10-57-31

Now let’s create a VMkernal adapter for our Fault Tolerance network. The steps for this are pretty much the same except we need to enable a service, Fault Tolerance logging and the IP address that we assign needs to be apart of the 10.10.4.0 network.

2015-12-09_10-58-062015-12-09_10-58-272015-12-09_10-58-37

Edit the setting of the FT port group and make only the NIC that is assigned to the 10.10.4.0 network the active adapter. Place all other adapters in the unused adapters section.

2015-12-09_10-59-09

Repeat the same steps for the vMotion network, except the enabled service will be vMotion traffic.

2015-12-09_11-00-10

Assign an IP address that is on the 10.10.5.0 network

2015-12-09_11-00-35

Click Next and Finish

2015-12-09_11-00-45

Make only the NIC assigned to the 10.10.5.0 network active. Place all other adapters as unused.

2015-12-09_11-01-50

Once we complete this step, all of our networking should be setup properly. The final networking should look like this:

2015-12-09_11-25-39

Now we need to add storage to our host. To add our storage, we need to add a Software ISCSI adapter. Do this under the Manage tab of the host. Under Storage > Storage Adapters click the green plus symbol and select software ISCSI adapter

2015-12-09_11-02-23

Click Ok

2015-12-09_11-02-32

Go to the newly created software adapter and under Targets enter the IP address that we assigned to the ISCSI NIC on our vCenter server.

2015-12-09_11-03-26

Click Ok

2015-12-09_11-03-58

Rescan Storage by right clicking the host and selecting Storage > Rescan Storage…and click Ok

2015-12-09_11-04-53

The host should not pick up the two disks that we created

2015-12-09_11-05-18

To add the storage to our host, we need to create a new datastore. Right click the host and select Storage > New Datastore

2015-12-09_11-08-06

Leave VMFS selected and click Next

2015-12-09_11-08-20

Create a name for the datastore and select the disk in the selection list below. Click Next.

2015-12-09_11-08-44

Select how much of the allocated space you want to use. We will use all 200GB in this example. Click Next

2015-12-09_11-10-23

Click Finish

2015-12-09_11-10-32

Repeat the same process to add the second 200GB datastore to our host.

Now we want to create Network Port Bindings so that we can bind the two ISCSI VMkernel port groups (ISCSI01 and ISCSI02) that we created to the software storage adapter. Under the host’s management tab, select Storage >Network Port Binding. Click the green plus symbol. In the list select ISCSI01 and ISCSI02 and click Ok.

2015-12-09_11-16-39

We should now see our Network Port Bindings are Active in the Adapter Details panel.

2015-12-09_11-17-12

We can also check to see how many paths we have available to the storage that we just connect by going under the Paths tab of Adapter Details.

2015-12-09_11-18-54

Now that we have all of our networking setup properly, we can go and reconfigure HA. Right click the host and select Reconfigure for vSphere HA

2015-12-09_11-20-00

After the election takes place, we will see that we are successfully configured for HA.

2015-12-09_11-20-51

Repeat these sames steps for the second host to add it to vCenter, setup the networking, and add shared storage to it.

So that we will be able to login to the vSphere web client using our Active Directory credentials, we need to add an Identity Source to Single Sign On. On the main home screen of the web client, click Administration from the menu on the left side of the page. Under Single Sign On select Configuration. On the SSO Configuration page select the Identity Sources tab at the top of the page. Click the green plus symbol. Select Active Directory (Integrated Windows Authentication). In the Domain name section, enter your domain name. Click Ok.12-10-2015 4-43-25 PM

Now go under Single Sign On > Users and Groups > Groups tab. Select Administrators and add your domain administrator account to it.

2015-12-09_11-24-37

All done!! Now we should have a fully functioning vSphere 6 environment to do some testing in. Keep in mind that we are running all of this on limited hardware so we won’t have top performance but if you’re just needing a lab to practice in or study for your exam…this will do the trick! 😉

 

4 thoughts on “Create a Nested ESXi 6.0 lab using VMware Fusion 8

  1. Tony

    Good Job C.Hay.. from your experiences on this subject I’m using this as a guide for my special project. Like you I’m using a Macbook Pro for portability (Mid 2012 2.6Ghz Quad i7| 16Gb Ram | 4t raid0) with the goal of using this for my CCNA recertification with the end goal of obtaining CCIE and paired with the virtualization of VMWare Fusion 8.5, ESXi 6.5, VCenter 6.5, GNS3 and Cisco vIRL I’m hoping that those sleepless moments pays off in the end. BTW if you have any performance tweak nuggets you’d like to share I’m all ears…:)..

    Like

  2. AnthonyW

    In this test lab scenario, once configured, is it possible to have a VM within the ESXi host communicate with other physical hosts on another network outside of the Fusion environment that the Mac can communicate with? For example.. The Mac is on a traditional /non-vmnet of 10.10.10.0/24 network and can already communicate with 10.10.30.0 , 10.10.40.0 networks. Once this lab environment is created, will the new VM guests on any of the ‘vmnet’ networks be able to communicate with any of the 10.10.30.0 or 10.10.40.0 networks? How could this be configured to make that work?

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s