<?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 MSA500 G2 MPIO path failures in Server Clustering</title>
    <link>https://community.hpe.com/t5/server-clustering/msa500-g2-mpio-path-failures/m-p/4404390#M311</link>
    <description>We have 2 Proliant DL380G5 servers connected to an MSA500G2 server using the high availability option kit with a 4 port I/O module.  When trying to add the second node to the cluster we are getting MPIO path verification failure.  Does anyone know how to fix this problem.  I am running MPIO version 2.0D.  All firmware and bios and support packs are up to date.  Could someone send me an email.  Please email response to David.J.hull@siemens.com  Thank you</description>
    <pubDate>Mon, 20 Apr 2009 22:36:22 GMT</pubDate>
    <dc:creator>Coralee</dc:creator>
    <dc:date>2009-04-20T22:36:22Z</dc:date>
    <item>
      <title>MSA500 G2 MPIO path failures</title>
      <link>https://community.hpe.com/t5/server-clustering/msa500-g2-mpio-path-failures/m-p/4404390#M311</link>
      <description>We have 2 Proliant DL380G5 servers connected to an MSA500G2 server using the high availability option kit with a 4 port I/O module.  When trying to add the second node to the cluster we are getting MPIO path verification failure.  Does anyone know how to fix this problem.  I am running MPIO version 2.0D.  All firmware and bios and support packs are up to date.  Could someone send me an email.  Please email response to David.J.hull@siemens.com  Thank you</description>
      <pubDate>Mon, 20 Apr 2009 22:36:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/msa500-g2-mpio-path-failures/m-p/4404390#M311</guid>
      <dc:creator>Coralee</dc:creator>
      <dc:date>2009-04-20T22:36:22Z</dc:date>
    </item>
  </channel>
</rss>

