<?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: MSA1000 and MPIO supported configurations in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576971#M13405</link>
    <description>It is mentioned in the Release Notes for Secure Path Workgroup Edition 4.0B (AA-RL4TN-TE - July 2003):&lt;BR /&gt;""You must make sure that the active HBA in each node is located in the PCI slot that is activated earlier during server boot than the slot containing the passive HBA. After the active and passive HBAs have been configured in the nodes, the boot order of each HBA can be visually confirmed using the following procedure:&lt;BR /&gt;&lt;BR /&gt;1. Located the ports on the two interconnect switches that are connected to the active and passive HBAs in one of the nodes.&lt;BR /&gt;2. Shut down and power off the node.&lt;BR /&gt;3. Power up the node.&lt;BR /&gt;4. Watch the port LEDs on the interconnect switch to determine which port is&lt;BR /&gt;activated first.&lt;BR /&gt;5. If this test indicates that the port on the interconnect switch that connects to the active controller is activated last, switch the cable positions and repeat the test to confirm that the configuration has been corrected.&lt;BR /&gt;6. If this test confirms that the configuration is correct for this node, repeat this test for the other node(s) in the cluster.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;Note: If the active HBA is not correctly configured in the node, the node failover does not occur. If an active node has already failed and failover did not occur to the passive node, the passive node must be shut down and power cycled before the MSA1000 is recognized.&lt;BR /&gt;------""</description>
    <pubDate>Thu, 14 Jul 2005 01:13:14 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-07-14T01:13:14Z</dc:date>
    <item>
      <title>MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576964#M13398</link>
      <description>We have 5 Windows servers connected to an MSA1000, 4 of them have a dual-path connection with MPIO. The last server has only a single path connection so we didn't install the MPIO software on it. I'd like to know if this is a supported configuration.&lt;BR /&gt;On the "hp StorageWorks SAN Design reference guide" I found that a similar configuration is supported with Secure Path but MPIO isn't mentioned.</description>
      <pubDate>Wed, 06 Jul 2005 06:50:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576964#M13398</guid>
      <dc:creator>Alberto Lambertini</dc:creator>
      <dc:date>2005-07-06T06:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576965#M13399</link>
      <description>Hi Alberto&lt;BR /&gt;&lt;BR /&gt;Yes, it is supported configuration, since MPIO is required for multiple paths to SAN&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Mahesh</description>
      <pubDate>Wed, 06 Jul 2005 08:27:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576965#M13399</guid>
      <dc:creator>Mahesh Kumar Malik</dc:creator>
      <dc:date>2005-07-06T08:27:54Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576966#M13400</link>
      <description>hi &lt;BR /&gt;&lt;BR /&gt;one thing to remember is that if one of your multi path servers has a failed fibre link and the standby controller becomes active your single HBA server will lose its connection, also as failback is not automatic on MPIO version 1.1 basic you with have to do a manual failback to bring controller A back on line.&lt;BR /&gt;&lt;BR /&gt;good luck&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Jul 2005 08:37:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576966#M13400</guid>
      <dc:creator>andy steven</dc:creator>
      <dc:date>2005-07-06T08:37:10Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576967#M13401</link>
      <description>Yes Andy, I know this limitation of basic MPIO. I posted this thread because yesterday we had a problem: we did maintenance on two of the multi-path servers, this required rebooting them. First we rebooted a Win2000 server and after 30 minutes we rebooted a Win2003 server. Today I noticed that during this 30 minutes the single-path server lost connectivity to the MSA1000 because a failover was generated after the first reboot and a failback after the second. I did a more in depth analysis and I found that:&lt;BR /&gt;- the first server has the HBA in the lower PCI slot number connected to the MSA standby controller (left)&lt;BR /&gt;- the second server has the HBA in the lower PCI slot number connected to the MSA active controller (right).&lt;BR /&gt;So I have this opinion: when a multi-path server reboots it tries to establish connection to the MSA by its first HBA (the lower PCI slot) starting a failover if the HBA is actually connected to the standby controller. I'm going to verify my opinion with a test ...</description>
      <pubDate>Wed, 06 Jul 2005 09:28:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576967#M13401</guid>
      <dc:creator>Alberto Lambertini</dc:creator>
      <dc:date>2005-07-06T09:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576968#M13402</link>
      <description>&lt;BR /&gt;Hi, Alberto, it is supported, but as you previosly experienced it's not a good idea to do it that way... The things you'ved seen during the maintenance is a normal behavior...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Jul 2005 09:47:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576968#M13402</guid>
      <dc:creator>Tv_3</dc:creator>
      <dc:date>2005-07-06T09:47:55Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576969#M13403</link>
      <description>Hi Tv, do you know any HP or Microsoft document that describe this behaviour ?</description>
      <pubDate>Wed, 06 Jul 2005 09:59:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576969#M13403</guid>
      <dc:creator>Alberto Lambertini</dc:creator>
      <dc:date>2005-07-06T09:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576970#M13404</link>
      <description>unfortunaly no...</description>
      <pubDate>Thu, 14 Jul 2005 00:48:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576970#M13404</guid>
      <dc:creator>Tv_3</dc:creator>
      <dc:date>2005-07-14T00:48:11Z</dc:date>
    </item>
    <item>
      <title>Re: MSA1000 and MPIO supported configurations</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576971#M13405</link>
      <description>It is mentioned in the Release Notes for Secure Path Workgroup Edition 4.0B (AA-RL4TN-TE - July 2003):&lt;BR /&gt;""You must make sure that the active HBA in each node is located in the PCI slot that is activated earlier during server boot than the slot containing the passive HBA. After the active and passive HBAs have been configured in the nodes, the boot order of each HBA can be visually confirmed using the following procedure:&lt;BR /&gt;&lt;BR /&gt;1. Located the ports on the two interconnect switches that are connected to the active and passive HBAs in one of the nodes.&lt;BR /&gt;2. Shut down and power off the node.&lt;BR /&gt;3. Power up the node.&lt;BR /&gt;4. Watch the port LEDs on the interconnect switch to determine which port is&lt;BR /&gt;activated first.&lt;BR /&gt;5. If this test indicates that the port on the interconnect switch that connects to the active controller is activated last, switch the cable positions and repeat the test to confirm that the configuration has been corrected.&lt;BR /&gt;6. If this test confirms that the configuration is correct for this node, repeat this test for the other node(s) in the cluster.&lt;BR /&gt;&lt;BR /&gt;-----&lt;BR /&gt;Note: If the active HBA is not correctly configured in the node, the node failover does not occur. If an active node has already failed and failover did not occur to the passive node, the passive node must be shut down and power cycled before the MSA1000 is recognized.&lt;BR /&gt;------""</description>
      <pubDate>Thu, 14 Jul 2005 01:13:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/msa1000-and-mpio-supported-configurations/m-p/3576971#M13405</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-07-14T01:13:14Z</dc:date>
    </item>
  </channel>
</rss>

