<?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: Path Failed to Storrage box.... in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274333#M33938</link>
    <description>Cause and effect.&lt;BR /&gt;&lt;BR /&gt;The first message says that one of your FibreChannel connections has failed.&lt;BR /&gt;&lt;BR /&gt;The "blocked FC remote port time out" happens because whatever operation was going on the FibreChannel connection times out because the fiber loop failed.&lt;BR /&gt;&lt;BR /&gt;The messages beginning with "Error:Mpx" are coming your FC multipath software. It is reacting to the FC loop failure and reporting each and every LUN path that has become inaccessible because of the fault.&lt;BR /&gt;&lt;BR /&gt;The "Warning: /proc/ide/hd?/settings..." message is completely unrelated. It is a warning, not an error. Someone was using a program that accessed IDE HD settings using a method that will be removed in some near-future version: the warning is a friendly reminder that this program will need updating at that time.&lt;BR /&gt;&lt;BR /&gt;The "device eth0 entered/left promiscuous mode" and the corresponding audit lines would be caused by someone running tcpdump or any other tool that uses the eth0 NIC to read *all* traffic coming to the NIC. &lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Wed, 24 Sep 2008 09:52:05 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2008-09-24T09:52:05Z</dc:date>
    <item>
      <title>Path Failed to Storrage box....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274330#M33935</link>
      <description>Iam getting following error in log msgs...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;qla2xxx 0000:08:00.0: LOOP DOWN detected (4).&lt;BR /&gt; rport-3:0-0: blocked FC remote port time out: saving binding&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 257 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Killing bus 3 to Symmetrix     000190102478 port 9aA.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 275 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 274 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 272 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 263 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 273 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 258 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 259 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 260 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 261 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 264 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 262 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 265 to 000190102478 is dead.&lt;BR /&gt;Error:Mpx:Path Bus 3 Tgt 0 Lun 256 to 000190102478 is dead.&lt;BR /&gt;Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed soon!&lt;BR /&gt;device eth0 entered promiscuous mode&lt;BR /&gt;audit(1217254763.351:11): dev=eth0 prom=256 old_prom=0 auid=4294967295&lt;BR /&gt;device eth0 left promiscuous mode&lt;BR /&gt;audit(1217254763.354:12): dev=eth0 prom=0 old_prom=256 auid=4294967295&lt;BR /&gt;device eth0 entered promiscuous mode&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How can I confirm weather its a HBA problem or storrage issue??!! &lt;BR /&gt;</description>
      <pubDate>Tue, 23 Sep 2008 11:13:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274330#M33935</guid>
      <dc:creator>sreekanthtm</dc:creator>
      <dc:date>2008-09-23T11:13:35Z</dc:date>
    </item>
    <item>
      <title>Re: Path Failed to Storrage box....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274331#M33936</link>
      <description>&amp;gt;&amp;gt;&amp;gt; How can I confirm weather its a HBA problem or storrage issue??!! &lt;BR /&gt;&lt;BR /&gt;According to this message:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt; qla2xxx 0000:08:00.0: LOOP DOWN detected (4).&lt;BR /&gt;&lt;BR /&gt;This should be a problem with our HBA, your cable or your sanswitch port. You are getting LOOP DOWN messages.&lt;BR /&gt;&lt;BR /&gt;In your profile I see "I have assigned points to   42  of   105  responses".&lt;BR /&gt;&lt;BR /&gt;Please keep asigning point to the answers you get.&lt;BR /&gt;&lt;BR /&gt;Have a nice day.</description>
      <pubDate>Tue, 23 Sep 2008 12:41:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274331#M33936</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-09-23T12:41:10Z</dc:date>
    </item>
    <item>
      <title>Re: Path Failed to Storrage box....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274332#M33937</link>
      <description>ok..... But what abt the next line.&lt;BR /&gt;&lt;BR /&gt;'rport-3:0-0: blocked FC remote port time out:'&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;sreekanth</description>
      <pubDate>Wed, 24 Sep 2008 05:19:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274332#M33937</guid>
      <dc:creator>sreekanthtm</dc:creator>
      <dc:date>2008-09-24T05:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Path Failed to Storrage box....</title>
      <link>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274333#M33938</link>
      <description>Cause and effect.&lt;BR /&gt;&lt;BR /&gt;The first message says that one of your FibreChannel connections has failed.&lt;BR /&gt;&lt;BR /&gt;The "blocked FC remote port time out" happens because whatever operation was going on the FibreChannel connection times out because the fiber loop failed.&lt;BR /&gt;&lt;BR /&gt;The messages beginning with "Error:Mpx" are coming your FC multipath software. It is reacting to the FC loop failure and reporting each and every LUN path that has become inaccessible because of the fault.&lt;BR /&gt;&lt;BR /&gt;The "Warning: /proc/ide/hd?/settings..." message is completely unrelated. It is a warning, not an error. Someone was using a program that accessed IDE HD settings using a method that will be removed in some near-future version: the warning is a friendly reminder that this program will need updating at that time.&lt;BR /&gt;&lt;BR /&gt;The "device eth0 entered/left promiscuous mode" and the corresponding audit lines would be caused by someone running tcpdump or any other tool that uses the eth0 NIC to read *all* traffic coming to the NIC. &lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Wed, 24 Sep 2008 09:52:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/path-failed-to-storrage-box/m-p/4274333#M33938</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-09-24T09:52:05Z</dc:date>
    </item>
  </channel>
</rss>

