vSphere 5 AutoLab V 1.0a www.labguides.com Your lab on your laptop
10 Next we will actually change the subnet. To do this, open a terminal and do the following: cd /Library/Preferences/VMware\ Fusion Now we need
11 If you notice it uses an extension of “.vmwarevm” to allow the association with VMware Fusion and this is the only way UNF will be able to see the
12 VMware Player Setup I also don’t have a PC that could run the lab and doesn’t have Workstation installed. The Workstation VMs should be fine, but
13 The Virtual Machines The VMs in the download package are configured to be able to be powered on under VMware Workstation configured to required VM
14 Build the Lab These steps use the full set of automation to build a complete lab environment. The steps should be completed in order and each ste
15 If you watch the console of the NAS VM you may see messages about not having enough RAM for ZFS, this does not cause any issues and can be ignore
16 The VM will boot from the Windows Server 2008 R2 CDROM and use “autounattend.xml” file on the floppy disk image to automate the Windows install.
17 After the entire automated install completes the VM will reboot a final time, returning to the desktop as auto-logon is setup. At this point the
18 Power on the VC VM and allow it to boot from the CD, as with the DC VM booting from the CD will always rebuild without any prompt. After about 20
19 The basic VC build does not include a default gateway, to prevent needless VUM downloads when you rebuild repeatedly. To access the Internet fro
2 Table of Contents vSphere 5 AutoLab ...
20 Build the second server as required. Confirm that both ESX servers have the correct static IP addresses before moving to the next stage. Task 5 –
21 Lab Build Time This table gives an indication of the time to build a core vSphere lab Time Action 0:00 Power on NAS and copy in contents of Build
22 Accessing the built lab While the VMware Workstation console is perfectly functional you may wish to use guest OS native tools, like RDP. If your
23 As Built Documentation IP Addressing Main network, no VLAN Subnet 192.168.199.0 Subnet Mask 255.255.255.0 Gateway 192.168.199.2 DHCP server 192.1
24 UserIDs System UserID Password Lab.local domain Administrator VMware1! Lab.local domain vi-admin VMware1! Router administration admin VMware1! NA
25 Rebuild Process Open Source Infrastructure The NAS VM should not require rebuilding, nor should the router. If either of these machines requires
26 Veeam ONE Installation Like most management tools Veeam ONE uses a client server model. We will use a dedicated VM named V1 as the server. The en
27 5. Click through the install wizard as usual 6. Since we're evaluating we will use the free edition, Select Install Veeam ONE in a free m
28 7. The Lab build has installed all of the required Windows components for you 8. Enter the usual lab password VMware1! for the service account
29 9. To minimise the RAM footprint we will use the SQL instance on the DC, the service account has rights to create the database so simply change t
3 vSphere 5 AutoLab This lab builder kit is designed to produce a nested vSphere 5.0 or 4.1 lab environment with the minimum effort. Prebuilt shell V
30 11. Enter the lab vCenter vc.lab.local and the Veeam service account credentials, username lab\svc_veeam and password VMware1! 12. Once the
31 13. When you log back on you will find three new desktop shortcuts for the Veeam components 14. Use each shortcut to launch the components and
32 17. Veeam One Reporter, here the VMware Trends dashboard shows data immediately 18. Next setup to allow the VI-Admin user access to the Veeam p
33 20. Double click the Veeam ONE Administrators group, click the Add.. button, enter VI-Admin and click OK a couple of times, then close Computer M
34
35 After the install completes you will have a desktop shortcut for Veeam ONE Monitor, the other two components are web services. 5. On the first
36 6. Once the client connects it should show you exactly the same environment as you saw in the client on V1 7. Business View and Reporter are w
37 Veeam Backup & Replication installation Server component install on V1 1. Build the VBR VM, this follows the usual boot from CDROM with flopp
38 5. Since I’m a fan of PowerShell I included it’s snapin
39 6. Select Use existing instance of SQL Server and enter the SQL server instance on D, DC\SQLEXPRESS, leave the default database name 7. Enter t
4 Acknowledgements This project would not have come to the world without the contributions of numerous others. First of all my Wife, without whom I w
40 8. Once the installer has completed you will find a shortcut on the desktop 9. Now that the software is installed head on over to the Veeam we
41 VMware View Installation Three shell VMs are provided with the lab kit, these provide the main components of the View environment. To run these V
42 VMware vCloud Director Installation Automated build Damian Karlson’s (@sixfootdad) excellent work has brought vCloud Director to the AutoLab. Requ
43 Power down Host1 and Host2 and increase each host’s memory to 3372MB. Power them back on and allow them to reconnect to vCenter. Add the vCloud
44 Power on the vCloud VM and choose the “CentOS for vCloud” option from the PXE boot menu. An automated installation of CentOS, Oracle Express, and
45 vCenter name: vc1 Connect to vShield Manager: Host name or IP address: vshield.lab.local User name: admin Password: default Click Fini
46 Troubleshooting A few things can go wrong along the way here are some we’ve seen DC Build stalls If the NAS is not accessible from the DC then the
47 AddHosts.ps1 exits The Add Hosts script will exit immediately if either of the ESXi servers doesn’t respond to a ping and a little later if either
48
49 AutoLab Changes and Futures Changes V1.0 Addition of Veeam products Addition of VMware View 5.0 and 5.1 Addition of vCloud Director V1.5
5 Lab platform Required Hardware The core lab can run on a single PC, a dual core 64bit CPU and a minimum of 8GB RAM is required, along with around 1
6 VMware Workstation Setup The Workstation build is designed to work with a host with 8GB of RAM and VMware workstation version 8.0. The host operat
7 VMware ESXiSetup The lab runs extremely well under ESXi, in my lab it consumes a peak of 4.5GB of RAM during build and about 40GB of disk space, al
8 Once the datastore is created use the vSphere Client datastore browser and browse to \Automate\ShellVMs where you will find the remaining lab VM f
9 VMware Fusion Setup Huge thanks to James Bowling @vSential for documenting the whole Fusion setup process. The Fusion build is designed to work wi
Comments to this Manuals