<?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 MSA1500 - Failed redundancy path in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/msa1500-failed-redundancy-path/m-p/6245479#M27534</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Javier was helping a customer:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A MSA1500 has one of the controllers showing warning message from ACU “Failed redundancy path”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MSA fw: v7.00&lt;/P&gt;
&lt;P&gt;ACU v8.50&lt;/P&gt;
&lt;P&gt;ADU doesn’t show any error&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I’ve found an issue with the zoning and cabling. In a windows cluster (2 node), both HBA’s from each node are connected to the same switch (server1:HBA1a, HBA1b =&amp;gt; SWITCH1, server2:HBA2a, HBA2b =&amp;gt; SWITCH2).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I’ve asked to the customer to solve the cabling and zoning issues and do a complete shutdown/startup of MSA and servers but I’m not sure if message from controller will be solved.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If warning continues being, any idea about the source of the warning?, any tip or experience about this message)?.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Uwe:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check also the “show tech_support” output on both controllers CLI (you need a special cable, was delivered with the MSA).&lt;/P&gt;
&lt;P&gt;Look for “Current Redundancy Mode” etc. of both controllers.&lt;/P&gt;
&lt;P&gt;Check if both controller own a few LUNs: “show preferred_path”&lt;/P&gt;
&lt;P&gt;Record a “show eventlog” on both controllers before the customer reboots the MSA.&lt;/P&gt;
&lt;P&gt;What are the LED codes of both controller? &amp;nbsp;Heartbeat LEDs are blinking? What is listed on the display? Scroll up and down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I remember correctly then the error could also be a communication problem between both MSA controllers (e.g. one controller has a problem).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Reply from Javier:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To close this thread, the issue was due to an incorrect HBA cabling.&lt;/P&gt;
&lt;P&gt;The customer had installed/configured servers and MSA in headquarters before move to the remote site. During pass to production in remote site, the customer plugged the HBA cables wrongly, non-crossing one of the HBA cables to switch in both servers, so the SAN zones had missed a path.&lt;/P&gt;
&lt;P&gt;After solve the cabling issue the “Failed redundancy path” message gone definitely without any other action.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Comments?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Oct 2013 14:25:11 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2013-10-23T14:25:11Z</dc:date>
    <item>
      <title>MSA1500 - Failed redundancy path</title>
      <link>https://community.hpe.com/t5/bladesystem-general/msa1500-failed-redundancy-path/m-p/6245479#M27534</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Javier was helping a customer:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A MSA1500 has one of the controllers showing warning message from ACU “Failed redundancy path”.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MSA fw: v7.00&lt;/P&gt;
&lt;P&gt;ACU v8.50&lt;/P&gt;
&lt;P&gt;ADU doesn’t show any error&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I’ve found an issue with the zoning and cabling. In a windows cluster (2 node), both HBA’s from each node are connected to the same switch (server1:HBA1a, HBA1b =&amp;gt; SWITCH1, server2:HBA2a, HBA2b =&amp;gt; SWITCH2).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I’ve asked to the customer to solve the cabling and zoning issues and do a complete shutdown/startup of MSA and servers but I’m not sure if message from controller will be solved.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If warning continues being, any idea about the source of the warning?, any tip or experience about this message)?.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Uwe:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check also the “show tech_support” output on both controllers CLI (you need a special cable, was delivered with the MSA).&lt;/P&gt;
&lt;P&gt;Look for “Current Redundancy Mode” etc. of both controllers.&lt;/P&gt;
&lt;P&gt;Check if both controller own a few LUNs: “show preferred_path”&lt;/P&gt;
&lt;P&gt;Record a “show eventlog” on both controllers before the customer reboots the MSA.&lt;/P&gt;
&lt;P&gt;What are the LED codes of both controller? &amp;nbsp;Heartbeat LEDs are blinking? What is listed on the display? Scroll up and down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I remember correctly then the error could also be a communication problem between both MSA controllers (e.g. one controller has a problem).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Reply from Javier:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To close this thread, the issue was due to an incorrect HBA cabling.&lt;/P&gt;
&lt;P&gt;The customer had installed/configured servers and MSA in headquarters before move to the remote site. During pass to production in remote site, the customer plugged the HBA cables wrongly, non-crossing one of the HBA cables to switch in both servers, so the SAN zones had missed a path.&lt;/P&gt;
&lt;P&gt;After solve the cabling issue the “Failed redundancy path” message gone definitely without any other action.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Comments?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2013 14:25:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/msa1500-failed-redundancy-path/m-p/6245479#M27534</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2013-10-23T14:25:11Z</dc:date>
    </item>
  </channel>
</rss>

