<?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: MPIO with ISCSI in ESX 4 in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/MPIO-with-ISCSI-in-ESX-4/m-p/10388#M1022</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I might be totally off base here...but do you have iSCSI access lists setup on the NetApp side to keep invalid/unreachable interfaces from getting advertised to the ESX host?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Sep 2009 02:44:45 GMT</pubDate>
    <dc:creator>amiller_1</dc:creator>
    <dc:date>2009-09-28T02:44:45Z</dc:date>
    <item>
      <title>MPIO with ISCSI in ESX 4</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/MPIO-with-ISCSI-in-ESX-4/m-p/10383#M1021</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Configuring ISCSI MPIO in ESX 4 as documented in TR 3749.&amp;nbsp; I have 2 VMkernels on a virtual switch and have selected only one active adapter on each VMkernel (other unused).&amp;nbsp; Have also bound ISCSI to each vmkernel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm actually seeing three paths (and three corresponding ISCSI sessions in Data ONTAP) and am trying to figure out what the 3rd path is.&amp;nbsp; It shows up with the same remote endpoint just with a different port...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Paths as defined in ESX are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mhba33:C0:T0:L0&lt;/P&gt;&lt;P&gt;mhba33:C2:T0:L0&lt;/P&gt;&lt;P&gt;mhba33:C3:T0:L0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sessions from ONTAP show the following (names/IPs changed to protect the innocent).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session 791&lt;BR /&gt;&amp;nbsp; Initiator Information&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Initiator Name: iqn.1998-01.com.vmware:vmware-7b671060&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ISID: 00:02:3d:00:00:03&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Connection Information&lt;BR /&gt;&amp;nbsp; Connection 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remote Endpoint: 192.168.5.250:60953&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Endpoint: 192.168.5.56:3260&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Interface: e0c&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; TCP recv window size: 131400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session 792&lt;BR /&gt;&amp;nbsp; Initiator Information&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Initiator Name: iqn.1998-01.com.vmware:vmware-7b671060&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ISID: 00:02:3d:00:00:04&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Connection Information&lt;BR /&gt;&amp;nbsp; Connection 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remote Endpoint: 192.168.5.25:58415&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Endpoint: 192.168.5.56:3260&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Interface: e0c&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; TCP recv window size: 131400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session 793&lt;BR /&gt;&amp;nbsp; Initiator Information&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Initiator Name: iqn.1998-01.com.vmware:vmware-7b671060&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ISID: 00:02:3d:00:00:01&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; Connection Information&lt;BR /&gt;&amp;nbsp; Connection 0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remote Endpoint: 192.168.5.250:59964&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Endpoint: 192.168.5.56:3260&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Local Interface: e0c&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; TCP recv window size: 131400&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:23:32 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/MPIO-with-ISCSI-in-ESX-4/m-p/10383#M1021</guid>
      <dc:creator>weller</dc:creator>
      <dc:date>2025-06-05T07:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: MPIO with ISCSI in ESX 4</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/MPIO-with-ISCSI-in-ESX-4/m-p/10388#M1022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I might be totally off base here...but do you have iSCSI access lists setup on the NetApp side to keep invalid/unreachable interfaces from getting advertised to the ESX host?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Sep 2009 02:44:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/MPIO-with-ISCSI-in-ESX-4/m-p/10388#M1022</guid>
      <dc:creator>amiller_1</dc:creator>
      <dc:date>2009-09-28T02:44:45Z</dc:date>
    </item>
  </channel>
</rss>

