<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Esxi on The IT Hollow</title>
    <link>https://theithollow.com/tags/esxi/</link>
    <description>Recent content in Esxi on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 24 Sep 2013 13:30:39 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/esxi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Windows Server 2012 as a Storage Device for vSphere Home Lab</title>
      <link>https://theithollow.com/2013/09/24/windows-server-2012-as-a-storage-device-for-vsphere-home-lab/</link>
      <pubDate>Tue, 24 Sep 2013 13:30:39 +0000</pubDate>
      <guid>https://theithollow.com/2013/09/24/windows-server-2012-as-a-storage-device-for-vsphere-home-lab/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;ve got a some hardware lying around for your lab, Windows Server 2012 may be a great solution for a home storage device.  You can now do both block (iSCSI) and NAS (NFS) on the same server, as well as having an OS to install some management apps on it.  In my lab, I use this management server to run Veeam for my backups, PRTG network monitor for bandwidth tracking, as well as using this server for both iSCSI targets and NFS mounts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Software iSCSI load balancing in ESXi 5</title>
      <link>https://theithollow.com/2012/12/03/software-iscsi-load-balancing-in-esxi-5/</link>
      <pubDate>Mon, 03 Dec 2012 14:14:56 +0000</pubDate>
      <guid>https://theithollow.com/2012/12/03/software-iscsi-load-balancing-in-esxi-5/</guid>
      <description>&lt;p&gt;When you team NICs together in ESXi 5 you can pick from a variety of load balancing techniques to determine how traffic should flow over the adapters.  You might think that setting up software iSCSI initiators in ESXi would be done in a similar manner.  Add a VMkernel to a vSwitch, add a couple of adapters and set a teamingfailover policy.  It turns out that this is not the case.  You could setup a software iSCSI initiator this way, but it won&amp;rsquo;t provide you the teaming or failover you&amp;rsquo;ve intended.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Upgrading ESXi hosts using VMware Update Manager</title>
      <link>https://theithollow.com/2012/05/29/upgrading-esxi-hosts-using-vmware-update-manager/</link>
      <pubDate>Tue, 29 May 2012 19:42:54 +0000</pubDate>
      <guid>https://theithollow.com/2012/05/29/upgrading-esxi-hosts-using-vmware-update-manager/</guid>
      <description>&lt;p&gt;Unlike many operating systems, VMware ESXi gives you a nice tool to upgrade their hypervisor to the latest version.  VMware Update Manager gives you the ability to grab the latest build and apply it to your existing ESXi hosts.&lt;/p&gt;
&lt;p&gt;I should mention that VMware Update Manager is not the only solution to upgrade your ESXi hosts.  Hosts can also be upgraded manually by booting the host to the latest build and performing an upgrade, or by utilizing the new autodeploy features in vSphere 5.  VMware Update Manager is a simple tool that can automate the installs on several hosts in sequence and is available with all editions of vSphere 5.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware Network Traffic Routing</title>
      <link>https://theithollow.com/2012/03/16/vmware-network-traffic-routing/</link>
      <pubDate>Fri, 16 Mar 2012 13:00:27 +0000</pubDate>
      <guid>https://theithollow.com/2012/03/16/vmware-network-traffic-routing/</guid>
      <description>&lt;p&gt;VMware has lots of ways to setup networking on their ESXi hosts.  In order to set this up in the best way for your needs, it&amp;rsquo;s important to understand how the traffic will be routed between VMs, virtual switches, physical switches and physical network adapters.&lt;/p&gt;
&lt;p&gt;Before looking at an example, we should review some networking 101.  Machines on the same vlan on the same switch can communicate with one another (assuming there is no firewall type devices in the way).  Machines on different vlans on the same switch cannot communicate unless the traffic passes through a router.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
