Before you get started with virtualization in your environment there are a few things you will need to have in place.
First and foremost you will need a working network in place to provide the various components of you vSphere solution connectivity to one another. A working DNS solution must be in place, in most cases this is provided by the Domain Controllers in a Windows Active Directory environment. DNS and AD will support both name resolution of your hosts as well as Single Sign-On (SSO) used by vCenter.
In addition to DNS, NTP is very important, especially if you plan to introduce solutions such as vRealize Automation. Even if virtual machines are just a few minutes off, products may not work properly.
Here are the components in a typical setup:
Once the above items are in place, you can now create DNS records for each of your ESXi hosts. With DNS records created, you can breeze through the installation and configuration of ESXi via the Direct Console User Interface (DCUI). Additionally, kickstart files can be used to configure your ESXi hosts during installation by pressing “shift-O” during startup to access to the boot options or by using Auto Deploy. If you do opt for Auto Deploy, consider a management cluster built on ESXi hosts installed to local disk or SD/USB drives. In this cluster you would run your critical services such as AD, DHCP, DNS, and vCenter so that during an outage you have the ability to recover core services that do not rely on the very services you are trying to restore. Once the management cluster is restored, Auto Deploy can service. Rob Nelson covers Auto Deploy nicely on a #vBrownBag over at professionalvmware.com.
Other components you need to also consider installing during production builds include a centralized syslog server (vCenter provides one for free, or Log Insight which is an enterprise grade solution. You can also use syslog-ng, Graylog, Splunk, or Nagios Log Monitor. Other tools that ship with vCenter include the dump collector, VMware Update Manager, the VMware Support Assistant and some type of monitoring solution such as Nagios, Realize Operations (vR Ops) or Hyperic. With a working environment ready, you can move on to installing your first ESXi host.
Of course this is a basic list, even the 5 bullet points I listed could consume months of learning if you’re not familiar with VLANs, or for planning IP schemas. If you’ve read though this list and not overwhelmed, you shouldn’t have a problem virtualizing if you have not already.
In my last video, we walked through how to install VMware Tools for CentOS 6.x. Now we are going to prepare the virtual machine for cloning. This requires we remove a specific file; /etc/udev/rules.d/70-persistent-net.rules. This file contains the MAC address for the virtual machine. Once removed, the file will be created during the initial boot with the matching MAC address for the cloned virtual machine.
This is a video demonstration on installing VMware Tools in CentOS 6.x. The assumptions for this walk through are you have access to VMware Workstation or the vSphere Client to initiate the VMware Tools installation and at least 1 E1000 network card to provide internet access. VMware Tools is needed for VMXNET3, so you will at least initially need an E1000 to provide network access for Perl, or local Perl installers to run the installer.
Posted in Tech Tagged with: Home, install vmware tools linux, Linux, network, Shared, Technology, Training, vcenter, Vendors, Virtualization, VMware, vmware tools, vmware tools install, vmware vsphere, vmware workstation, vSphere, workstation
I was going to do a post on NFS versus iSCSI, to be honest that is such old hat in my opinion it doesn’t really matter. Whether you use iSCSI or NFS is up to you, your application and business requirements along with any constraints in your infrastructure that may force you to lean one way or another. Since I am an NFS networking ninja, clearly I am going to go the NFS route. Let’s get started on setting up NFS, if you are not already log into your Synology DSM.
Next I need to connect to my NFS share from the ESXi hosts. Typically I’d have NFS on its on VLAN, but sans a switch in my home lab to VLANs it will be riding with all my other network traffic.
The datastore should now be available on both hosts (Click on the host >> related objects >> datastores) as seen below. Repeat for the gold datastore.
Now that the datastores are created, I am going to create an “ISO” folder on the silver datastore to hold my linux ISOs and build virtual machines in vCenter.
Posted in Tech Tagged with: datastore, ESXI, Home, home lab, lab, Lab Series, NAS, nested esxi, network, NFS, nfs datastore, Shared, Storage, Synology, synology nfs datastore vmware, Synology Setup Series, Technology, Training, vcenter, vcsa, Vendors, Virtualization, VMware, vpshere, vSphere, web client
So you’ve got vCenter up and running and hosts added, it’s time to enable the cool things vCenter can do – namely vMotion, HA and DRS. I’ve gone back and forth on how I wanted to present vMotion and networking in the home lab. On one hand many existing deployments are likely running 1Gbps, though newer ones are likely to start with 10Gbps as prices have dropped. After a quick Twitter chat I decided to move forward as I would if I had 10Gbps networking and not have separate physical interfaces in my host for different traffic types.
When we setup our ESXi templates there was only a single NIC, let’s add a 2nd NIC to the VM’s. For purposes of this labs (and maybe I’m still old like this) I will keep my management network on a standard switch and my VM network and vMotion traffic on a distributed switch.
Once the ESXi virtual machine has been restarted, you should see two interfaces in the vSphere Web Client. Repeat for your 2nd host.
In the vSphere Web Client, click on the network tab in the navigator so we can create the VDS.
Your hosts will be added to the VDS and vMotion will be enabled on the newly created VMkernel adapter. To test, I have created an empty virtual machine on vxprt-esxi02 in the silver datastore, I am going to vMotion and Storage vMotion that virtual machine to vxprt-esxi01. Here you can see the screenshot
You can see the progress of the vMotion in the Running Tasks window. After a few minutes you should now see your virtual machine on vxprt-esxi01
Posted in Tech Tagged with: create vds, distributed switch, ESXI, HOL, Home, home lab, Lab Series, migrate virtual machine, nested esxi, network, port group, Shared, Storage, Technology, Training, vcenter, vcsa, vDS, Vendors, virtual machine, Virtualization, VM, vmk, vmkernel, vmotion, vmotion vm, VMware, vSphere, web client