Sun Storage 3511 SATA Array
 
Sun Storage 3510 FC Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
 

Troubleshooting Sun Storage[TM] 351x Cabling.

Applies to:

Purpose

This document will assist if the following symptoms are seen with a Sun Storage 3510 or 3511 Array:

• Path degraded/offline
• Loop offline
• SCSI time-outs
• Drives  and/or Controllers  missing or failed
• No access to LUNs
• LED unlit
• Any of the following error message reports:

Path offline error messages in /var/adm/messages:

Timeouts and SCSI transport error messages in /var/adm/messages:

Loop Offline error messages in /var/adm/messages:

Error messages in the array's event log:

Troubleshooting Steps

Step 1: Confirm supported cabling configuration is used:

http://download.oracle.com/docs/cd/E19236-01/816-7300-21/appb_jbod.html#pgfId-1000275

See Sun Storage 3510 FC JBOD Array Attached to a Single HBA Port:

http://download.oracle.com/docs/cd/E19236-01/816-7300-21/appb_jbod.html#pgfId-1000285

Note: Sun Storage 3511 FC expansion trays are not supported as standalone JBODs.

http://download.oracle.com/docs/cd/E19236-01/816-7300-21/appb_jbod.html#pgfId-1000092

See Cabling to Expansion Units:

http://download.oracle.com/docs/cd/E19236-01/816-7300-21/ch04_cable.html#20126

For configurations with Oracle Cluster, follow the guidelines in Oracle Cluster documentation.

Step 2: Confirm that the appropriate  ports are in use:

Dual controller

For Sun Storage 3511 SATA arrays, channels 0 and 1 automatically configure their ports to match the transfer speed and communication method of each connection. Channels 4 and 5 only support a 2-Gbyte transfer rate. If you connect two servers to channel 0 or to channel 1, use host filtering if you want to control host access to logical drives.

Step 3: Confirm the connected SFPs are green.

• SFP link status : Solid green - Active good
• FC Connection Off - Empty or failed FC connection

Step 4: Verify the correct cable is used.  

Cable part number for 3510:

https://support.oracle.com/handbook_private/Systems/3510_R/components.html#Cables

Cable part number for 3511:

https://support.oracle.com/handbook_private/Systems/3511/components.html#Cables

Step 5: Verify channel/port connection type and speed by issuing the sccli> show channels command.

3510 example:

The speed column in the above 3510 output shows that hosts are attached  to channels 0, 1, 4 and 5 with 2-Gbyte transfer speeds. There is no host connected to channel 6 (speed=N/A).

Speed values are displayed for the primary controller only. Therefore, if a user maps one LUN to the primary controller, and another LUN to a secondary controller, only the established connection to the primary controller is displayed. As a result, if a primary ID is not mapped to a channel, and a secondary ID is mapped, "Async" displays in the Speed field.

For FC or SATA, a speed value of Async may mean no link or link down if it is on a channel with a PID.

Step 6: Confirm SFP connection by using the sccli> show bypass command to display the bypass status of all small form-factor (SFP) transceivers on a specified loop.

Loop A and Loop B refer to the redundant FC loops that each device is connected to. The SES device in the top slot of the chassis is connected to Loop A, which is the first drive channel. The bottom SES device is connected to Loop B, which is the second drive channel.

The L and the R shown above, or any channel designated as a drive channel, must not have an unused SFP installed. It will show a BYPASS status of Bypassed and ATTRIBUTES of -H.

LOOP-A refers to the controller in the top slot and LOOP-B is the controller in the bottom slot.

If a device is bypassed, the Attributes returned values include S, F, or H.

• An S means the device was bypassed due to a Sun Storage CLI command.
• An F means a drive fault caused the bypass.
• An H means the device was bypassed due to a hardware problem (no signal was present).

The following example command executed on channel 2 shows the bypass information for a Sun Storage 3511 SATA array on loop A:

The Port returned values indicate the type of device, FC or SATA, that is attached to the loop.

On a Sun Storage 3510 FC RAID IOM board, from left to right, there are six ports: channel 0, channel 1, channel 2(3) Left, channel 2(3) Right, channel 4 and channel 5. Valid values for the Sun Storage 3510 FC RAID IOM board include 0, 1, 4, 5, L and R.

On a Sun Storage 3510 FC JBOD IOM board, from left to right, there are two ports: Left and Right. Valid values for port include L and R.

On a Sun Storage 3511 SATA RAID IOM board, from left to right, there are eight ports: channel 0 left, channel 0 right, channel 1 left, channel 1 right, channel 2, channel 3, channel 4 and channel 5. Valid values for the Sun StorEdge 3511 SATA RAID IOM board include 0L, 0R, 1L, 1R, 2, 3, 4 and 5.

On a Sun Storage 3511 SATA JBOD IOM board, from left to right, there are four ports: loop A left, loop A right, loop B left and loop B right. Valid value ports for the Sun Storage 3511 SATA JBOD IOM include AL, AR, BL and BR.

More Examples:

Connection detected on Channel 0 and 1 (host ports) to a Server HBA. The second Left (L) Channel is connected to a JBOD.

With cables removed, we see connections hardware-bypassed (-H):

If the connection remains bypassed after the connection has been verified, and the cable and SFP have been swapped or replaced, contact Oracle support. More advanced diag commands can be run to test the bypass status.

The sccli> show fru ouput, event log or /var/adm/messages will not report cable or SFP failures. Additional troubleshooting may be required to identify a marginally operating or failed component or connection. See <Document 1009557.1> Troubleshooting Fibre Channel Devices from the Solaris Operating System.

Step 7: If no problems are found during the course of this document, refer back to <Document 1011431.1> Troubleshooting Sun Storage 3000 Array Series Hardware. 

This solution has no attachment