<?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: iscsi mutipathing in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277735#M52965</link>
    <description>Hi, &lt;BR /&gt;&lt;BR /&gt;in case some one stumbles along this thread ..the solution is in red hat knowledge base article :34404 , also the sam e is mentioned in equallogic iscsi configuration guide &lt;BR /&gt;=====cut and paste====&lt;BR /&gt;Configuring Mulitpath Connections:&lt;BR /&gt;To create the multiple logins needed for Linux dev-mapper to work you need to create an â  interfaceâ   file for each GbE interface you wish to use to connect to the array.&lt;BR /&gt;Use the following commands to create the interface files for MPIO.&lt;BR /&gt;(Select the appropriate Ethernet interfaces youâ  re using.)&lt;BR /&gt;#iscsiadm -m iface -I eth0 -o new&lt;BR /&gt;New interface eth0 added&lt;BR /&gt;Repeat for the other interface, i.e. eth1&lt;BR /&gt;#iscsiadm â  m iface â  I eth1 â  o new&lt;BR /&gt;New interface eth1 added&lt;BR /&gt;Now update the interface name for each port:&lt;BR /&gt;#iscsiadm â  m iface â  I eth0 - -op=update â  n iface.net_ifacename â  v eth0&lt;BR /&gt;eth0 updated&lt;BR /&gt;#iscsiadm â  m iface â  I eth1 - -op=update â  n iface.net_ifacename â  v eth1&lt;BR /&gt;eth1 updated&lt;BR /&gt;Hereâ  s an example of what the /var/lib/iscsi/ifaces/eth0 looks like:&lt;BR /&gt;iface.iscsi_ifacename = eth0&lt;BR /&gt;iface.net_ifacename = eth0&lt;BR /&gt;iface.hwaddress = default&lt;BR /&gt;iface.transport_name = tcp&lt;BR /&gt;If you have already discovered your volumes, you now need to re-discover the target(s).&lt;BR /&gt;#iscsiadm â  m discovery â  t st â  p &lt;GROUP ip="" addr=""&gt;:3260&lt;BR /&gt;172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;You should see an entry for each interface you specified.&lt;BR /&gt;You now need to log into the volume.&lt;BR /&gt;#iscsiadm â  m node â  l â  T iqn.2001-05.com.equallogic:0-8a0906-8951f2302-815273634274741f-rhel5-test â  p 172.23.10.240:3260&lt;BR /&gt;#iscsiadm â  m session&lt;BR /&gt;tcp: [3] 172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;tcp: [4] 172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;This shows that both adapters have connected to the array.&lt;BR /&gt;Verify that the multipathing is correctly configured.&lt;BR /&gt;#multipath â  v2&lt;BR /&gt;#multipath â  ll&lt;BR /&gt;dw-test-vol (36090a02830f251891f74744263735281) dm-1 EQLOGIC,100E-00&lt;BR /&gt;[size=100G][features=1 queue_if_no_path][hwhandler=0]&lt;BR /&gt;\_ round-robin 0 [prio=0][active]&lt;BR /&gt;\_ 9:0:0:0 sdd 8:48 [active][ready]&lt;BR /&gt;\_ 8:0:0:0 sde 8:64 [active][ready]&lt;BR /&gt;dw-svr-vol (36090a01840b31c74e173a4873200a02f) dm-0 EQLOGIC,100E-00&lt;BR /&gt;[size=10G][features=0][hwhandler=0]&lt;BR /&gt;\_ round-robin 0 [prio=0][enabled]&lt;BR /&gt;\_ 6:0:0:0 sdb 8:16 [active][ready]&lt;BR /&gt;\_ 7:0:0:0 sdc 8:32 [active][ready]&lt;BR /&gt;In this example you see that there are two paths to each volume. They are set one on top of the other. If they are separated, then MPIO is not working correctly. Try restarting the multipath service and check again. If not, review your multipath configuration file for any errors.&lt;BR /&gt;#service multipathd restart&lt;BR /&gt;Other resources for configuring MPIO can be found at:&lt;BR /&gt;&lt;A href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/DM_Multipath/mpio_configfile.html" target="_blank"&gt;http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/DM_Multipath/mpio_configfile.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://kbase.redhat.com/faq/docs/DOC-3353" target="_blank"&gt;http://kbase.redhat.com/faq/docs/DOC-3353&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;closing the thread&lt;BR /&gt;Regards,&lt;/GROUP&gt;</description>
    <pubDate>Sun, 27 Mar 2011 10:37:59 GMT</pubDate>
    <dc:creator>DeafFrog</dc:creator>
    <dc:date>2011-03-27T10:37:59Z</dc:date>
    <item>
      <title>iscsi mutipathing</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277734#M52964</link>
      <description>Dear Gurus , &lt;BR /&gt;&lt;BR /&gt;We have 2 10G card , in each of the 2 M160 dell blades,running Redhat el 5.5 .&lt;BR /&gt;all 4 iscis hba's have been assigned IP and granted access to iscsi target which &lt;BR /&gt;resides in a equallogic iscsi san ,mutilpath -l does shows only one entry.&lt;BR /&gt;how to set the mutipath properly.&lt;BR /&gt;&lt;BR /&gt;Regards,  &lt;BR /&gt;</description>
      <pubDate>Fri, 25 Mar 2011 12:25:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277734#M52964</guid>
      <dc:creator>DeafFrog</dc:creator>
      <dc:date>2011-03-25T12:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: iscsi mutipathing</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277735#M52965</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;in case some one stumbles along this thread ..the solution is in red hat knowledge base article :34404 , also the sam e is mentioned in equallogic iscsi configuration guide &lt;BR /&gt;=====cut and paste====&lt;BR /&gt;Configuring Mulitpath Connections:&lt;BR /&gt;To create the multiple logins needed for Linux dev-mapper to work you need to create an â  interfaceâ   file for each GbE interface you wish to use to connect to the array.&lt;BR /&gt;Use the following commands to create the interface files for MPIO.&lt;BR /&gt;(Select the appropriate Ethernet interfaces youâ  re using.)&lt;BR /&gt;#iscsiadm -m iface -I eth0 -o new&lt;BR /&gt;New interface eth0 added&lt;BR /&gt;Repeat for the other interface, i.e. eth1&lt;BR /&gt;#iscsiadm â  m iface â  I eth1 â  o new&lt;BR /&gt;New interface eth1 added&lt;BR /&gt;Now update the interface name for each port:&lt;BR /&gt;#iscsiadm â  m iface â  I eth0 - -op=update â  n iface.net_ifacename â  v eth0&lt;BR /&gt;eth0 updated&lt;BR /&gt;#iscsiadm â  m iface â  I eth1 - -op=update â  n iface.net_ifacename â  v eth1&lt;BR /&gt;eth1 updated&lt;BR /&gt;Hereâ  s an example of what the /var/lib/iscsi/ifaces/eth0 looks like:&lt;BR /&gt;iface.iscsi_ifacename = eth0&lt;BR /&gt;iface.net_ifacename = eth0&lt;BR /&gt;iface.hwaddress = default&lt;BR /&gt;iface.transport_name = tcp&lt;BR /&gt;If you have already discovered your volumes, you now need to re-discover the target(s).&lt;BR /&gt;#iscsiadm â  m discovery â  t st â  p &lt;GROUP ip="" addr=""&gt;:3260&lt;BR /&gt;172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;You should see an entry for each interface you specified.&lt;BR /&gt;You now need to log into the volume.&lt;BR /&gt;#iscsiadm â  m node â  l â  T iqn.2001-05.com.equallogic:0-8a0906-8951f2302-815273634274741f-rhel5-test â  p 172.23.10.240:3260&lt;BR /&gt;#iscsiadm â  m session&lt;BR /&gt;tcp: [3] 172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;tcp: [4] 172.23.10.240:3260,1 iqn.2001-05.com.equallogic: 0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test&lt;BR /&gt;This shows that both adapters have connected to the array.&lt;BR /&gt;Verify that the multipathing is correctly configured.&lt;BR /&gt;#multipath â  v2&lt;BR /&gt;#multipath â  ll&lt;BR /&gt;dw-test-vol (36090a02830f251891f74744263735281) dm-1 EQLOGIC,100E-00&lt;BR /&gt;[size=100G][features=1 queue_if_no_path][hwhandler=0]&lt;BR /&gt;\_ round-robin 0 [prio=0][active]&lt;BR /&gt;\_ 9:0:0:0 sdd 8:48 [active][ready]&lt;BR /&gt;\_ 8:0:0:0 sde 8:64 [active][ready]&lt;BR /&gt;dw-svr-vol (36090a01840b31c74e173a4873200a02f) dm-0 EQLOGIC,100E-00&lt;BR /&gt;[size=10G][features=0][hwhandler=0]&lt;BR /&gt;\_ round-robin 0 [prio=0][enabled]&lt;BR /&gt;\_ 6:0:0:0 sdb 8:16 [active][ready]&lt;BR /&gt;\_ 7:0:0:0 sdc 8:32 [active][ready]&lt;BR /&gt;In this example you see that there are two paths to each volume. They are set one on top of the other. If they are separated, then MPIO is not working correctly. Try restarting the multipath service and check again. If not, review your multipath configuration file for any errors.&lt;BR /&gt;#service multipathd restart&lt;BR /&gt;Other resources for configuring MPIO can be found at:&lt;BR /&gt;&lt;A href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/DM_Multipath/mpio_configfile.html" target="_blank"&gt;http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/DM_Multipath/mpio_configfile.html&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://kbase.redhat.com/faq/docs/DOC-3353" target="_blank"&gt;http://kbase.redhat.com/faq/docs/DOC-3353&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;closing the thread&lt;BR /&gt;Regards,&lt;/GROUP&gt;</description>
      <pubDate>Sun, 27 Mar 2011 10:37:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277735#M52965</guid>
      <dc:creator>DeafFrog</dc:creator>
      <dc:date>2011-03-27T10:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: iscsi mutipathing</title>
      <link>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277736#M52966</link>
      <description>Hi , solution as above.&lt;BR /&gt;&lt;BR /&gt;Reards , &lt;BR /&gt;Rahul.</description>
      <pubDate>Sun, 27 Mar 2011 10:39:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/iscsi-mutipathing/m-p/5277736#M52966</guid>
      <dc:creator>DeafFrog</dc:creator>
      <dc:date>2011-03-27T10:39:36Z</dc:date>
    </item>
  </channel>
</rss>

