<?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>Lun on The IT Hollow</title>
    <link>https://theithollow.com/tags/lun/</link>
    <description>Recent content in Lun 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/lun/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>VMware Path Masking</title>
      <link>https://theithollow.com/2012/10/30/vmware-path-masking/</link>
      <pubDate>Tue, 30 Oct 2012 13:15:34 +0000</pubDate>
      <guid>https://theithollow.com/2012/10/30/vmware-path-masking/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://shanksnet.files.wordpress.com/2012/10/images.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;http://shanksnet.files.wordpress.com/2012/10/images.jpg&#34;&gt;&lt;/a&gt;  I&amp;rsquo;ve written posts in the past regarding &lt;a href=&#34;https://theithollow.com/2012/03/12/lun-masking-vs-zoning/&#34; title=&#34;Lun Masking vs Zoning&#34;&gt;LUN masking&lt;/a&gt; on a storage array, but it is possible to mask a path directly from your vSphere environment.  I feel that if at all possible the masking should be handled at array level because the array is closest to the disk.  Let&amp;rsquo;s face it, if vSphere shouldn&amp;rsquo;t see a LUN for one reason or another, then why is the array presenting it in the first place?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lun Masking vs Zoning</title>
      <link>https://theithollow.com/2012/03/12/lun-masking-vs-zoning/</link>
      <pubDate>Tue, 13 Mar 2012 01:27:47 +0000</pubDate>
      <guid>https://theithollow.com/2012/03/12/lun-masking-vs-zoning/</guid>
      <description>&lt;p&gt;Zoning and Lun Masking are often confused for each other, probably because both of them are used to restrict access to storage.  They should both be used to secure the storage network and reduce unnecessary traffic.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Zoning&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;If you want to specify only certain hosts from accessing a storage device then you would want to setup zoning.  For instance, in the example below, you can see that the two servers on the right can access three of the four storage devices, whereas the two on the left can only access two of the SANs.  This configuration is done on the Fibre Channel switch.  iSCSI, NFS, and FCoE can also be segmented, but they would use typical TCPIP segmentation methods like setting up a VLAN.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
