Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-77-1000281.1
Update Date:2012-01-31
Keywords:

Solution Type  Sun Alert Sure

Solution  1000281.1 :   Sun StorEdge 3510 JBOD or 3511 RAID Connected With LP10000 HBA May Experience I/O Interruption  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3511 SATA Array
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun Alert
  •  
  • .Old GCS Categories>Sun Microsystems>Sun Alert>Release Phase>Resolved
  •  

PreviouslyPublishedAs
200396


Product
Sun StorageTek 3511 SATA Array JBOD
Sun StorageTek LP10000 Host Bus Adapter
Sun StorageTek 3510 FC Array JBOD

Bug Id
SUNBUG: 6313136

Date of Workaround Release
20-JUL-2006

Date of Resolved Release
28-Mar-2008

1. Impact

When a Sun StorEdge 3510 JBOD or 3511 RAID array (with firmware 3.2x or later) is connected using a series LP10000 Host Bus Adapter (HBA), the array may experience periodic I/O interruption indicated by excessive filesystem activity. If misdiagnosed, this condition could lead to unnecessary hardware replacement.


2. Contributing Factors

This issue can occur on the following platforms:

  • Sun StorEdge 3510 JBOD or 3511 RAID array with firmware 3.2x or later
when connected to the system with Series LP 10000 Host Bus Adapter (HBA)

Notes:

1. The 3510 RAID array is NOT subject to this issue.

2. This issue will only occur with the LP 10000 HBA in a direct attach (point to point) connection with the 3510 JBOD or 3511 RAID array. I/O interruption will be isolated to ports 0 and 1 on the array.

3. The issue is due to an incompatibility between the LP 10000 and the Port Bypass Circuitry (PBC) used on channels 0/1 of the 3510 JBOD or 3511 RAID array.

To determine the firmware version on the 3511, the following command can be run:

sccli> show inquiry
Vendor: SUN
Product: StorEdge 3511
Revision: 423A

3. Symptoms

Output from iostat(1M) will appear similar to the following; on some devices showing 100% busy on the file system:

    dd if=/dev/zero of=/dev/rdsk/c9t40d0s0 bs=1048576
          extended device statistics
    r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
    0.5 0.0 1.5 0.0 0.0 0.0 0.0 5.1 0 0 d3
    0.5 0.0 1.5 0.0 0.0 0.0 0.0 5.1 0 0 d13
    0.5 0.0 1.5 0.0 0.0 0.0 0.0 5.0 0 0 c1t0d0
    12.0 126.0 128.0 643.5 0.0 0.1 0.0 0.5 0 6 c2t0d1
    4.5 126.0 44.0 643.5 0.0 0.1 0.0 0.5 0 5 c3t0d0
    5.0 2.0 40.0 20.0 0.0 0.0 0.0 4.5 0 3 c4t0d0
    3.0 2.0 24.0 40.0 0.0 0.0 0.0 2.1 0 1 c4t1d0
    0.0 3.5 0.0 3.0 0.0 0.0 0.0 2.5 0 0 c4t1d1
    7.5 5.5 60.0 52.0 0.0 0.1 0.0 8.4 0 6 c8t0d0
    604.0 7.0 4831.8 23.7 0.0 1.5 0.0 2.4 2 90 c8t1d0
    0.0 4.0 0.0 38.2 0.0 0.0 0.0 6.5 0 1 c8t0d1
    126.0 12.0 1008.0 148.0 0.0 1.0 0.0 6.9 0 49 c8t1d1
    13.0 0.0 104.0 0.0 0.0 0.1 0.0 7.0 0 9 c8t0d2
    51.0 11.0 408.0 44.0 0.0 0.5 0.0 7.9 0 38 c8t1d2
    0.0 4.0 0.0 20.7 0.0 0.0 0.0 0.4 0 0 c2t0d3
    1.0 1.0 8.0 6.0 0.0 0.0 0.0 11.2 0 2 c8t0d3
    3.0 0.5 24.0 4.0 0.0 0.0 0.0 6.3 0 2 c8t0d4
    0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0 100 c9t40d0 <---
          extended device statistics
    r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
    2.0 0.0 13.5 0.0 0.0 0.0 0.0 3.1 0 1 d3
    0.5 25.5 4.0 29.2 0.2 0.8 8.4 31.4 22 23 d7
    1.0 0.0 8.0 0.0 0.0 0.0 0.0 0.3 0 0 d13
    0.5 26.5 4.0 29.7 0.0 0.2 0.0 8.9 0 9 d17
    1.0 0.0 5.5 0.0 0.0 0.0 0.0 5.8 0 1 d23
    0.0 25.5 0.0 29.2 0.0 0.8 0.0 31.5 0 22 d27
    1.5 26.5 12.0 29.7 0.0 0.2 0.0 8.6 0 9 c1t0d0
    1.0 40.0 5.5 36.5 0.0 1.2 0.0 28.1 0 27 c1t1d0
    5.5 108.5 60.0 615.5 0.0 0.1 0.0 0.9 0 5 c2t0d1
    1.5 111.0 16.0 614.2 0.0 0.1 0.0 1.1 0 4 c3t0d0
    12.0 2.5 96.5 20.0 0.0 0.0 0.0 3.2 0 5 c4t0d0
    21.0 1.5 152.5 4.0 0.0 0.1 0.0 3.5 0 8 c4t1d0
    22.5 0.0 180.0 0.0 0.0 0.1 0.0 6.5 0 15 c8t0d0
    412.0 5.0 3295.8 84.0 0.0 0.9 0.0 2.1 1 82 c8t1d0
    36.0 0.0 288.0 0.0 0.0 0.2 0.0 4.3 0 15 c8t0d1
    193.5 20.5 1547.9 208.0 0.0 2.0 0.0 9.5 1 86 c8t1d1
    3.0 0.0 24.0 0.0 0.0 0.0 0.0 9.7 0 3 c8t0d2
    53.0 14.0 424.0 112.0 0.0 0.8 0.0 11.3 0 56 c8t1d2
    2.0 0.0 16.0 0.0 0.0 0.0 0.0 10.9 0 2 c2t0d3
    14.0 3.0 96.5 22.0 0.0 0.1 0.0 8.3 0 14 c8t0d3
    14.0 2.0 96.5 16.0 0.0 0.1 0.0 7.3 0 12 c8t0d4
    0.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0 100 c9t40d0 <---
    ...

4. Workaround

To work around the described issue:

A) Do not use the LP 1000 HBA for 3510 JBOD or 3511 RAID array configurations.

B) Use a fabric switch, No direct connection (HBA-Array).


5. Resolution

There are no further updates planned for this Sun Alert document. If you need additional assistance regarding this issue, please contact Oracle Support  Services.


Modification History
28-Mar-2008: Resolved
22-Nov-2006: Updated Contributing Factors section
31-Jan-2012: Updated for clarifications in Impact, Contributing Factors and Workaround sections


Emulex single and dual FC HBAs are referenced as LP 10000 series HBAs.
Additional information is available on the Emulex website at:

http://www.emulex.com/ts/downloads/lp10000/lp10000.html

Internal Contributor/submitter
[email protected]
Internal Eng Business Unit Group
NWS (Network Storage)
Internal Services Knowledge Engineer
[email protected]
Internal Escalation ID
1-12980335, 1-13890753, 1-15909132, 1-15991090, 1-16242155
Internal Sun Alert Kasp Legacy ID:102223
Responsible Manager: [email protected]

References

SUNBUG: 6313136

Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback