Archive for the ‘Nested Lab’ Category

Nested Lab – Domain Controller / Control Center VM

March 25, 2015 2 comments

This VM is there as a Windows Domain Controller, but also hosts DNS and DHCP services.

I have also installed Update Manager to this VM.

As a VM its is configured as follows:


The networking settings in the guest are configured as below:


I have configured Routing and Remote Access as follows:


DNS is configured as below:


And DHCP as follows:


As far as installing Update Manager (vSphere 6 version), I will cover this in a later post.

Categories: Nested Lab Tags:

Nested Lab – VMware Workstation Network Settings

March 25, 2015 Leave a comment

I have used VMware Workstation 11 for my nested lab, but older versions (9&10) should be ok.

The networking settings are configured as below:


I use host-only connections for the Management, vMotion and Production networks, and have a NAT connection for internet access (via the DomainController / ControlCenter vm).

Categories: Nested Lab Tags:

“Not enough Physical Memory” error – VMware Workstation problem on Windows 8.1

March 25, 2015 Leave a comment

When I first started virtualising vSphere 6, I had issues with VMware Workstation starting VMs.

I kept getting message “not enough physical memory is available”, when powering on VMs, despite having 16Gb and only attempting to start 1 VM with 1Gb RAM.

To fix this issue, edit c:\ProgramData\VMware\VMwareWorkstation\config.ini and add the line:

vmmon.disableHostParameters = “TRUE”

Then reboot.

Categories: Nested Lab, vSphere Tags:

vSphere 6 – My nested lab experiences

March 17, 2015 Leave a comment

So vSphere 6 is finally generally available, and I have been getting my nested build up to date, and thought I would share some of my experiences.

More to follow….

Categories: Nested Lab Tags:

Tricking ESXi into seeing an SSD device

January 30, 2013 3 comments

Sometimes supported SSD drives do not appear in the vSphere Client or Web Client as an SSD, but instead as unknown or Non-SSD.

It is possible to use storage claim rules to alter this behaviour, to be able to use the ESXi host cache feature in ESXi 5.0 and above.

To start with, it is important to identify the device that is being reported incorrectly.


As you can see from the vSphere Client above, the datastore created as SharedSSD is reported as Non-SSD.

We need to identify the device that this datastore has been created on, one possible way would be to go into the properties of the datastore, and then enter the manage paths screen as shown below.


Notice that the SATP (Storage Array Type Plugin) used for this device is VMW_SATP_DEFUALT_AA, we will need this with the device id.

We can then right click on the path and copy the name to the clipboard. In this case that would contain all the detail after Name: in the lower window. The only detail required is in this case the iSCSI t10 number.

(Although in this example we have already created a datastore on the device, it would be possible to configure a device that does not currently have a datastore as SSD except we would need to identify the device via the storage adapter.)

Once we have the device id, and SATP we can than use the esxcli command line tool (found in the ESXi shell, and vCli and vMa) to configure a claim rule.

The first setup is to create the claim rule with the required optional parameter to enable SSD.


The next step is to ensure that the claim rule has been added.


Notice that the claim rule previously entered is displayed as a result of the command.

Now we need to reclaim all claim rules to ensure that SSD is now enabled for this device.


Notice that in this case it was unable to unclaim the path. This can happen sometimes, and is easily fixed with a reboot of the host.

Alternatively, unclaim the device:

esxcli storage core claiming unclaim -t device -d t10.945445000000000023030000000000000000000000000000

Then load, and run the claim rule:

esxcli storage core claimrule load
esxcli storage core claimrule run

If you do not get the unable to reclaim message detailed above, you can now confirm hat the rule has been applied and that the device is now seen as SSD.


As you can see in the above, the value for Is SSD: is true.

You should now see the datastore listed as SSD in the client.


It is also possible to use this method to allow the use of SSD for host caching when using a nested setup for testing.

Nested Home Lab – Setting up Shared Storage on SuSE (SLES11)

June 14, 2012 Leave a comment

Over the years teaching vSphere, several peers, colleagues and students have asked me how I setup shared storage in my nested test environment.  Being a Novell instructor teaching SuSE Linux. for me this was the obvious choice.  However, most of my colleagues and students are not familiar with Linux, so I have decided to put together a procedure detailing the steps necessary to configure your own shared storage.

You will need:
VMware Workstation 8 / Player 4

SuSE Linux Enterprise Server 11

Due to the length of the instructions (plus loads of screen grabs), I decided to make a PDF available , Enjoy!


Categories: Nested Lab, Storage, vSphere

How to create a Nested vSphere 5 Lab

June 14, 2012 Leave a comment

Many of my students ask me how to create a nested vSphere lab environment for testing/learning purposes.

I was going to document what I had done, then found a REALLY useful blog site by Sammy Bogaert, which has the details.

So check out “Building the Ultimate vSphere Lab” on Sammy’s blog site at

Categories: Nested Lab, vSphere