<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NetApp - FC Alias &amp;amp; VMWare in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16387#M1652</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OnCommand Insight Assure/Plan/Perform (formerly SANscreen) can pull in your Cisco configs, NetApp and VMware configs, and show all the interrelationships, along with covering a lot more use cases. Meaning, for a given ESX host, it will show you what NetApp ports it is zoned to, what paths to LUNs exist, etc. For a storage array, the ports microview will show the "friendly" name for ports, as well as having the WWPN/WWNN for each. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Dec 2011 13:36:57 GMT</pubDate>
    <dc:creator>ostiguy</dc:creator>
    <dc:date>2011-12-19T13:36:57Z</dc:date>
    <item>
      <title>NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16382#M1651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;I have recently started working with my NetApp SAN and VMWare 4 U3 environment. One thing I have found frustrating whilst troubleshooting is the use of WWNN/WWPN between the various components i.e. ESX hosts, FC Switch, HP virtual connect, NetApp filer. Particularly when looking at the MPIO paths on the ESX hosts it is not intuitive which head/port on a clustered filer you are looking at. Is there any way of giving these WWNN/WWPN an alias at the ESX host? I can do this on my Core Cisco MDS switch using the fcalias command which is designed for this exact purpose. It would make troubleshooting dead paths etc. so much easier! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance. &lt;SPAN __jive_emoticon_name="laugh" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/laugh.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:39:23 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16382#M1651</guid>
      <dc:creator>darraghos</dc:creator>
      <dc:date>2025-06-05T06:39:23Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16387#M1652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;OnCommand Insight Assure/Plan/Perform (formerly SANscreen) can pull in your Cisco configs, NetApp and VMware configs, and show all the interrelationships, along with covering a lot more use cases. Meaning, for a given ESX host, it will show you what NetApp ports it is zoned to, what paths to LUNs exist, etc. For a storage array, the ports microview will show the "friendly" name for ports, as well as having the WWPN/WWNN for each. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Dec 2011 13:36:57 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16387#M1652</guid>
      <dc:creator>ostiguy</dc:creator>
      <dc:date>2011-12-19T13:36:57Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16394#M1653</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply,&lt;/P&gt;&lt;P&gt;I was wondering though if there was any way to do this natively i.e. have the aliases appear in the vi client?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Dec 2011 13:52:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16394#M1653</guid>
      <dc:creator>darraghos</dc:creator>
      <dc:date>2011-12-19T13:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16398#M1654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set FC aliases on NetApp, but I don't think this is doable on ESX host&amp;nbsp; (&lt;A href="http://www.vmware.com/pdf/vsphere4/r41/vsp_41_san_cfg.pdf" title="http://www.vmware.com/pdf/vsphere4/r41/vsp_41_san_cfg.pdf" target="_blank"&gt;http://www.vmware.com/pdf/vsphere4/r41/vsp_41_san_cfg.pdf&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Dec 2011 14:57:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16398#M1654</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2011-12-19T14:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16403#M1655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the replies guys. I'll look at this software but was hoping there was something that could be done at the ESX side as I used other vendors SANs also such a HP EVA. I wish there was an industry standard for SAN topolgy discovery and aliasing. It would make life so much easier!&lt;/P&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="cry" __jive_macro_name="emoticon" class="jive_macro jive_macro_emoticon jive_emote" src="https://community.netapp.com/5.0.1/images/emoticons/cry.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 12:08:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16403#M1655</guid>
      <dc:creator>darraghos</dc:creator>
      <dc:date>2011-12-20T12:08:29Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16406#M1656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To make things a *bit* easier, different vendors use different prefixes, so quite often it is not that hard to identify which WWN belongs to which array.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As far as I can tell NetApp ones should look this:&lt;/P&gt;&lt;P&gt;50:0a:09:8x:xx:xx:xx:xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 17:52:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16406#M1656</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2011-12-20T17:52:46Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16413#M1657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been in that boat too.&amp;nbsp; If you have vCenter which I'm sure you do, take a look at the Virtual Storage Console.&amp;nbsp; This may help resolve any problems that you may be looking at that stuff for in the first place.&amp;nbsp; Also, if you can install OnCommand Data Fabric Manager that will help keep LUNs, controllers, ESX, VMs.... all of it straight &lt;EM&gt;except &lt;/EM&gt;your WWWNs.&amp;nbsp; Sorry, I can't offer anything better than that.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Dec 2011 19:04:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16413#M1657</guid>
      <dc:creator>dgshuenetapp</dc:creator>
      <dc:date>2011-12-20T19:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16418#M1658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Radek,&lt;/P&gt;&lt;P&gt;You are right of course. In my enviroment though I may have a single ESX hosts connected to 4 different heads and 8 different cards. Would be great if you could enter WWNN/PN aliases into a config file and have a tab in vCenter that converts the data seen on the HBA link to the aliases, Would be great for logical diagrams etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Dec 2011 11:25:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16418#M1658</guid>
      <dc:creator>darraghos</dc:creator>
      <dc:date>2011-12-21T11:25:22Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp - FC Alias &amp; VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16422#M1659</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Daniel,&lt;/P&gt;&lt;P&gt;I hadn't even looked at Data Fabric Manager. Will do now. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Dec 2011 11:04:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/NetApp-FC-Alias-amp-VMWare/m-p/16422#M1659</guid>
      <dc:creator>darraghos</dc:creator>
      <dc:date>2011-12-23T11:04:29Z</dc:date>
    </item>
  </channel>
</rss>

