<?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: LIP reset / LOOP down in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958139#M24322</link>
    <description>Yes, Redhat have fixed this in an update 5.&lt;BR /&gt;&lt;A href="http://kbase.redhat.com/faq/FAQ_85_9610" target="_blank"&gt;http://kbase.redhat.com/faq/FAQ_85_9610&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope it helps&lt;BR /&gt;&lt;BR /&gt;Phil</description>
    <pubDate>Wed, 06 Feb 2008 15:28:10 GMT</pubDate>
    <dc:creator>Philip Dunn_1</dc:creator>
    <dc:date>2008-02-06T15:28:10Z</dc:date>
    <item>
      <title>LIP reset / LOOP down</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958137#M24320</link>
      <description>Hi to all,&lt;BR /&gt;Wonder if anyone with some SAN experience can help?&lt;BR /&gt;We have some boot-from-SAN bl35p blades (running redhat 4u4) in an enclosure. Recently several of the blades have started behaving quite strange, giving read-only errors when writing to filesystems, LIP reset and LOOP down errors in syslog (see below) and in worst cases loosing published disks completely.&lt;BR /&gt;Has anyone ever come across anything like this before and could point me in the right direction of things to check in order to resolve this issue?&lt;BR /&gt;&lt;BR /&gt;Many Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Phil&lt;BR /&gt;&lt;BR /&gt;&lt;HOSTNAME&gt;# touch test&lt;BR /&gt;touch: cannot touch `test': Read-only file system&lt;BR /&gt;&lt;BR /&gt;sample of /var/log/messages:&lt;BR /&gt;Mar  8 13:54:36 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.0: LIP occured (b5b5).&lt;BR /&gt;Mar  8 13:54:39 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.0: LIP reset occured (b5f5).&lt;BR /&gt;Mar  8 13:54:40 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.0: LOOP DOWN detected (2).&lt;BR /&gt;Mar  8 13:54:44 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.1: LIP reset occured (f700).&lt;BR /&gt;Mar  8 13:54:44 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.0: LIP occured (f8f7).&lt;BR /&gt;Mar  8 13:54:44 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.1: LIP occured (f700).&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.0: LOOP UP detected (2 Gbps).&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: qla2300 0000:04:01.1: LOOP UP detected (2 Gbps).&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: scsi(0) :Loop id 0x0082 is an EVA_XL (AA) device&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; last message repeated 2 times&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: scsi(0) :Loop id 0x0083 is an EVA_XL (AA) device&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; last message repeated 2 times&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: scsi(1) :Loop id 0x0081 is an EVA_XL (AA) device&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; last message repeated 2 times&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; kernel: scsi(1) :Loop id 0x0082 is an EVA_XL (AA) device&lt;BR /&gt;Mar  8 13:54:46 &lt;HOSTNAME&gt; last message repeated 2 times&lt;BR /&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;&lt;/HOSTNAME&gt;</description>
      <pubDate>Thu, 08 Mar 2007 09:51:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958137#M24320</guid>
      <dc:creator>Philip Dunn_1</dc:creator>
      <dc:date>2007-03-08T09:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: LIP reset / LOOP down</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958138#M24321</link>
      <description>I'm having the same problem. Please post an update if you have solved this.</description>
      <pubDate>Wed, 06 Feb 2008 14:49:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958138#M24321</guid>
      <dc:creator>Brian Mousseau</dc:creator>
      <dc:date>2008-02-06T14:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: LIP reset / LOOP down</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958139#M24322</link>
      <description>Yes, Redhat have fixed this in an update 5.&lt;BR /&gt;&lt;A href="http://kbase.redhat.com/faq/FAQ_85_9610" target="_blank"&gt;http://kbase.redhat.com/faq/FAQ_85_9610&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope it helps&lt;BR /&gt;&lt;BR /&gt;Phil</description>
      <pubDate>Wed, 06 Feb 2008 15:28:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958139#M24322</guid>
      <dc:creator>Philip Dunn_1</dc:creator>
      <dc:date>2008-02-06T15:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: LIP reset / LOOP down</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958140#M24323</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;AFAIK is this a normal behaviour. I also seen this with Windows hosts, they report also errors to the event log. Two BL30/35 blades in a sleeve are bulding a FC-AL. This loop is connected to the fabric (fabric loop). This is needed because only 8 ports for outgoing fc-connects are available with a p-Class enclosure. But you can use it with up to 16 blades (BL30/35). While booting one blade in the sleeve, a LIP will be generated. This is noticed by the other blade. You can see this in you logs or eventlog.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Thu, 07 Feb 2008 12:20:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/lip-reset-loop-down/m-p/3958140#M24323</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2008-02-07T12:20:38Z</dc:date>
    </item>
  </channel>
</rss>

