Sun StorEdge 3310/3320/3510/3511: Running sccli command may result in SCSI timeouts
Last updated on APRIL 24, 2018
Applies to:Sun Storage 3310 Array - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage 3320 SCSI Array - Version Not Applicable and later
This phenomenon appears on systems connected with Sun Storage A1000, A3000 and A3500 arrays, as well as Sun Storage 3000 arrays (3310, 3320, 3510, 3511).
Managing Sun Storage 3000 arrays requires the sccli utility. Click here to download the sccli utility using <Patch 10310598>.
SCSI timeouts have been reported by the LUNs of Sun Storage A1000, A3000 and A3500 arrays in the following circumstances:
- SCCLI is invoked on the host to manage the Sun Storage 3000 arrays.
- Sun Storage A1000, A3000 and A3500 arrays are connected on the same host.
- One of the following is true:
- /usr/bin/osa/bin/parityck is being run for the LUNs or is being run from the GUI of Raid Manager software (rm6), which manages Sun Storage A1000, A3000 and A3500 arrays.
- /usr/bin/osa/bin/parityck is being run at the same time from both hosts to the same LUNs, where the configuration includes multi-host connections.
- There is a heavy I/O load on the LUNs. Note: This problem happens only if you invoke sccli without any options.
The following are examples of error messages generated when invoking SCCLI on a system where parityck is running for LUN 0:
Example 1: These messages are generated if the Sun Storage A1000, A3000 and A3500 array is connected on a SBUS system with ISP1000U host bus adapter, which uses isp HBA driver.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms