<?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: EVA 4000 random Drive/Mirror Port Errors in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330188#M29634</link>
    <description>Hi, we have EVA6000 and have the same problem. But the problem is isolated only in encloser 3. &lt;BR /&gt;This problem started since we upgraded our EVA, and filled all the bays with disk drives. The failed disks are random but only within the bay3. &lt;BR /&gt;I also see the events EIP17, EIP05 and EIP13.&lt;BR /&gt;&lt;BR /&gt;I think that we must replace the encloser. I don't think that there is other solution.&lt;BR /&gt;I dont think that this is a firmware bug. It happens with old and the new disk drives.</description>
    <pubDate>Mon, 29 Jun 2009 06:02:33 GMT</pubDate>
    <dc:creator>Cvetan Grigorov</dc:creator>
    <dc:date>2009-06-29T06:02:33Z</dc:date>
    <item>
      <title>EVA 4000 random Drive/Mirror Port Errors</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330185#M29631</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;On one of my EVA4000 boxes i suddenly recieve random event 060b4709's scattered over various enclosures disks. The warning shows up on a daily bases. Anyone have any idea what they mean exactly.&lt;BR /&gt;&lt;BR /&gt;--- The actual event:&lt;BR /&gt;&lt;BR /&gt;everity: Warning -- not failed but attention recommended or required. A non-data exchange sent to a physical disk drive has timed out.&lt;BR /&gt;&lt;BR /&gt;Error reading extended event description from c:\hsvmafiles\napp\eventout.txt&lt;BR /&gt;&lt;BR /&gt;EIP09 - Fibre Channel Services Physical Disk Drive/Mirror Port Error&lt;BR /&gt;An error was encountered while attempting to access a physical disk drive or the mirror port.&lt;BR /&gt;&lt;BR /&gt;Event Log Packet Event Specific Information&lt;BR /&gt;&lt;BR /&gt;   flags (Flags)&lt;BR /&gt;      Flag field bits: 01000011&lt;BR /&gt;&lt;BR /&gt;      Time has been set on this HSV200 controller: TRUE&lt;BR /&gt;      Time has been synchronized with all HSV200 controllers in the Storage System: TRUE&lt;BR /&gt;      Event sequence number reset occurred: FALSE&lt;BR /&gt;      Event reported out of sequence due to Final Event Block reconciliation or lost host event: FALSE&lt;BR /&gt;      Event requeued following restart or resynchronization: FALSE&lt;BR /&gt;      Event reported using LAB code: FALSE&lt;BR /&gt;      Event reported by primary HSV200 controller (Note: Not valid until Storage System primary HSV200 controller is elected): TRUE&lt;BR /&gt;      Single power supply HSV200 controller: FALSE&lt;BR /&gt;&lt;BR /&gt;   revision - Structure revision number: 2  [0x02]&lt;BR /&gt;   count - Event specific information size in bytes: 172  [0xac]&lt;BR /&gt;   sequence_number - Sequence number assigned to the event: 37566  [0x92be]&lt;BR /&gt;   sw_version - HSV200 controller software version number string: 5020&lt;BR /&gt;   baselevel_id - HSV200 controller baselevel build string: CR0920&lt;BR /&gt;   ctrlr_model_id - HSV200 controller model string: HSV200&lt;BR /&gt;   reporting_ctrlr - Storage System Management Interface Handle of HSV200 controller that reported the event: Noid: 0   IdType: 7   IdLength: 8   UUID: 5005-08b4-0010-4d03-0000-0000-0000-0000&lt;BR /&gt;   report_time - Time event was reported: Date: 30-Dec-2008  Time: 03:52:14:850&lt;BR /&gt;   report_location - Location of event report call: 1177492  [0x11f794]&lt;BR /&gt;&lt;BR /&gt;   header (Header Information)&lt;BR /&gt;&lt;BR /&gt;      ** NOTE: The following is part of a UNION with more than one interpretation.&lt;BR /&gt;         You will need to determine which union value is relevant.&lt;BR /&gt;&lt;BR /&gt;      ** START UNION: ( u - Event Code Union ) **&lt;BR /&gt;&lt;BR /&gt;      ec (Event Code)&lt;BR /&gt;         eiptype - Event Information Packet Type Code: 9  [0x09]&lt;BR /&gt;         cac - Corrective Action Code: 71  [0x47]&lt;BR /&gt;            Corrective Action: Dropped frames are potential indications of an impending Fibre Channel port or physical disk drive failure when they occur excessively. If frame drop becomes excessive, the indicated Fibre Channel port or the indicated physical disk drive will be placed in the inoperative state. This is a preemptive action warning, no immediate action is necessary. &lt;BR /&gt;         evnum - Event Number: 11  [0x0b]&lt;BR /&gt;         scid - HSV200 Controller Software Component Identification: 6  [0x06]&lt;BR /&gt;&lt;BR /&gt;      ** UNION OR: ( u - Event Code Union ) **&lt;BR /&gt;      value - Event Code Value: 101402377  [0x060b4709]&lt;BR /&gt;      ** END UNION: ( u - Event Code Union ) **&lt;BR /&gt;      revision - Packet revision number: 4  [0x04]&lt;BR /&gt;      type - Packet type: 9  [0x09]&lt;BR /&gt;      count - Number of bytes in packet: 108  [0x6c]&lt;BR /&gt;&lt;BR /&gt;   device - UUID of physical disk drive associated with the event: 2000-0000-8776-a962-0000-0000-0000-0000&lt;BR /&gt;   cerp_id - HSV200 controller enclosure rear panel Fibre Channel port attached to the physical disk drive or mirror port: DP-1A&lt;BR /&gt;   exch_type - Frame exchange type: 2  [0x02]&lt;BR /&gt;   port - HSV200 controller internal Fibre Channel port number attached to the physical disk drive or mirror port: 0  [0x00]&lt;BR /&gt;   dencl_num - Enclosure where the physical disk drive is located: 3  [0x03]&lt;BR /&gt;   al_pa - AL_PA of the physical disk drive or mirror port: 89  [0x59]&lt;BR /&gt;   rack_num - Rack where physical disk drive is located: 0  [0x00]&lt;BR /&gt;   bay - Enclosure bay where the physical disk drive is located: 9  [0x09]&lt;BR /&gt;   fed_class - Fibre Channel Exchange Descriptor class: 33554476  [0x0200002c]&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Dec 2008 14:28:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330185#M29631</guid>
      <dc:creator>J.Kool_1</dc:creator>
      <dc:date>2008-12-30T14:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4000 random Drive/Mirror Port Errors</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330186#M29632</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;THE MIRROR PORT&lt;BR /&gt;if it is random daily on the various enclosures/disks, then it could be the problem of the mirror port itself. &lt;BR /&gt;The failing element could be either the controllerÂ´s &lt;BR /&gt;a) chip&lt;BR /&gt;b) mirror port SFP&lt;BR /&gt;c) cable (copper)&lt;BR /&gt;EVA4000 has 4 mirror ports&lt;BR /&gt;There are the followin LED indications of the mirror port health:&lt;BR /&gt;GREEN - normal operation&lt;BR /&gt;AMBER - no signal detected or the controller port failure&lt;BR /&gt;OFF   - no GBIC/SFP detected&lt;BR /&gt;&lt;BR /&gt;NOTE&lt;BR /&gt;The firmware cannot determine the root cause of the failure. It can determine only that it was unable to properly communicate with the other mirror port. The problem may be in the transmission or the receiving function of either controller. The controller firmware retries the failed mirror port once per second. The port LED of a failed mirror port will return to green very quickly after the action that resolved the failure.&lt;BR /&gt;&lt;BR /&gt;THE PHYSICAL DISK&lt;BR /&gt;if it is always the same enclosure/bay/disk, then it could be the problem of the physical disk&lt;BR /&gt;&lt;BR /&gt;The actual event comes from the &lt;BR /&gt;1. DISK BACK END PORT DP-1A &lt;BR /&gt;cerp_id - HSV200 controller enclosure rear panel Fibre Channel port attached to the physical disk drive or mirror port: DP-1A&lt;BR /&gt;exch_type - Frame exchange type: 2 [0x02]&lt;BR /&gt;port - HSV200 controller internal Fibre Channel port number attached to the physical disk drive or mirror port: 0 [0x00]&lt;BR /&gt;&lt;BR /&gt;2. ENCLOSURE 3&lt;BR /&gt;dencl_num - Enclosure where the physical disk drive is located: 3 [0x03]&lt;BR /&gt;&lt;BR /&gt;3. AL_PA 89&lt;BR /&gt;al_pa - AL_PA of the physical disk drive or mirror port: 89 [0x59]&lt;BR /&gt;&lt;BR /&gt;4. RACK NUMBER 0&lt;BR /&gt;rack_num - Rack where physical disk drive is located: 0 [0x00]&lt;BR /&gt;&lt;BR /&gt;5. DISK BAY 9&lt;BR /&gt;bay - Enclosure bay where the physical disk drive is located: 9 [0x09]&lt;BR /&gt;fed_class - Fibre Channel Exchange Descriptor class: 33554476 [0x0200002c] &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Dec 2008 15:47:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330186#M29632</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-12-30T15:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4000 random Drive/Mirror Port Errors</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330187#M29633</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have been experiencing the same entries in our EVA event logs for some time. After having HP Support investigate the issue it was determined that it is a known bug with specific types of fibre drive firmware which will be installed in your EVA. HP confirmed to us however that these errors are benign and do not pose a risk to our data.  We had more of a problem trying to get that officially confirmed in writing however ;-)&lt;BR /&gt;&lt;BR /&gt;For your own peace of mind,  I would recommend you collect all the EVA controller event logs and open a new case with HP for them to investigate. Until they get back to you with more information I wouldn't worry too much about these entries.</description>
      <pubDate>Tue, 30 Dec 2008 16:09:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330187#M29633</guid>
      <dc:creator>Schwarzie</dc:creator>
      <dc:date>2008-12-30T16:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4000 random Drive/Mirror Port Errors</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330188#M29634</link>
      <description>Hi, we have EVA6000 and have the same problem. But the problem is isolated only in encloser 3. &lt;BR /&gt;This problem started since we upgraded our EVA, and filled all the bays with disk drives. The failed disks are random but only within the bay3. &lt;BR /&gt;I also see the events EIP17, EIP05 and EIP13.&lt;BR /&gt;&lt;BR /&gt;I think that we must replace the encloser. I don't think that there is other solution.&lt;BR /&gt;I dont think that this is a firmware bug. It happens with old and the new disk drives.</description>
      <pubDate>Mon, 29 Jun 2009 06:02:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330188#M29634</guid>
      <dc:creator>Cvetan Grigorov</dc:creator>
      <dc:date>2009-06-29T06:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: EVA 4000 random Drive/Mirror Port Errors</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330189#M29635</link>
      <description>One of the new disks may be causing problems on the loop and interrupting the coomunication to the other disks.&lt;BR /&gt;&lt;BR /&gt;You need to contact HP and get someone with experience to analyze the logs, to see which disks show "missing data" or "dropped frames" and if they are all on the same loop.</description>
      <pubDate>Mon, 29 Jun 2009 08:26:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-4000-random-drive-mirror-port-errors/m-p/4330189#M29635</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2009-06-29T08:26:10Z</dc:date>
    </item>
  </channel>
</rss>

