Step 15 – Verifying all components
Step 14 – Installing vCenter Server
Step 13 –Configuring ESXi Server Network Settings
Step 8 – Creating Openfiler VM
Step 4 – Preparing DC
Step 2 – Creating ESXi Server VMs.
I’ve finally decided to make another instruction on how to setup virtual lab environment for vSphere 5.5. As the previous instruction was based on vSphere 5.0 and there has been few changed to the vSphere environment setup requirement and architecture, I thought another instruction may be necessary.
Tools you need
- Laptop/Desktop with minimum of 12GB RAM (16GB or more is preferable)
- VMware Workstation 10 ( Can be done with other editions but the instruction is based on 10)
- Windows 2008 x64 ISO (This will be used by vCenter Server and Domain Controller)
- Windows 2003 x32 ISO (This can be used in Lab, you use other OS you wish)
- vCenter Server 5.5 Windows Edition ISO (I am using VMware-VIMSetup-all-5.5.0-1476387-20131201.iso)
- ESXi 5.5 ISO (I am using VMware-VMvisor-Installer-5.5.0-1331820.x86_64.iso)
- Openfiler ISO (I am using openfileresa-2.99.1-x86_64-disc1.iso)
vSphere Client doesn’t show Hardware Status tab when you login to vCenter Server, it is due to vCenter Hardware Status Plugin is not running on vSphere Client. Try enabling this plugin to see if it helps.
If you get an error message like below, and you are running Windows 2003 (maybe XP, too) then your system where vSphere Client is installed is missing a update.
Obtain and install this hotfix from http://support.microsoft.com/kb/948963. Then restart the system.
After restart, you got your Hardware Status tab back, and plugins are running fine.
To restart iSCSI Target service in Openfiler, you need to have console or ssh into openfiler. When you make changes to iSCSI configuration file manually, you may need to restart the service. The Command “service iscsi-target restart”, will restart only iSCSI target service
~ $ ssh -l root 10.10.10.10 firstname.lastname@example.org's password: Last login: Tue Jul 30 12:43:42 2013 from 10.0.10.1 [root@of ~]# service iscsi-target restart Stopping iSCSI target service: ...... [ OK ] Starting iSCSI target service: [ OK ] [root@of ~]#
In the event when you restore VMs from backup or when delete Snapshot operation fails, then Snapshot List and actual Snapshot (Delta VMDK files) could become inconsistent. In this case VMs require Snapshot Consolidation, otherwise Delta-VMDK file continue growing its size without your ability to delete the snapshot as it is not listed in the Snapshot Manager.
In vSphere 5.0 above, VMs that require Snapshot Consolidation can be shown the message as you see below.