Sun Storage 3511 SATA Array
 
Sun Storage 3310 Array
 
Sun Storage 3510 FC Array
 
Sun Storage 3320 SCSI Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: SE31xx_33xx_35xx
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
 

Applies to:

Goal

The purpose of this document is to help verifying configuration parameter settings.

It would be needed in those situations where:

• Array is experiencing poor performances
• Array cannot be accessed
• SCSI I/O timeouts
• Random global spare assignments
• Cannot access the array via ethernet (out of band)
• Network protocols failing

Solution

A.  Verify communication parameters

1-Verify that the baud rate is set to 38400

 2-Please keep the IP address on a private network for security reasons

 3-Avoid enabling unneeded protocols, for security reasons

B.   Verify drive parameters

Ensure the following values are set:

• scsi-io-timeout= 30s
• queue-depth= 32 (this may be set to 8 for upgraded 3511)
• auto-global-spare =disabled
• smart=detect-clone-replace
• Leaving the cylinder, head, and sector settings at Variable ensures that all three values are calculated automatically. If you choose a specific value for one of these settings and leave the other two set to Variable, the firmware calculates the other two settings. If you set two, the firmware automatically calculates the third.  For Solaris based hosts you can choose - 64 heads and either the < 65536 cylinder setting or the Variable cylinder setting to cover all logical drives over 253 GByte and under the maximum limit. The controller automatically adjusts the sector count.

'polling-interval' is used to determine the interval at which the controller polls each drive to determine if it is alive, regardless of whether or not there is any host I/O. This value must be enabled for SMART to be functional. The default value is 30 seconds.

In 4.x firmware, newly replaced drives in the 3510 and 3511 are automatically re-scanned by the controller.
For the 3310 and 3320 with either 3.2x or 4.x firmware,  newly replaced drives must be manually re-scanned to be recognized by the controller.

C.   Verify host parameters

Ensure values are set according to instructions in sections Host-Side and Drive-Side:

Fibre-connection-mode is set to 'Loop' for direct attached storage.
If Fibre-connection-mode is set to P2P (point-to-point),  indicating SAN attached, ensure that only a PID or SID value is configured per channel (see example below).

D.   Verify cache settings

Ensure cache settings match recommended values:

E.   Verify peripheral device type

In the firmware user interface, select
View and edit Configuration parameters > Host-side Parameters > Peripheral Device Type Parameters > Peripheral Device Type.

F.   Verify the auto-write-through trigger values

G.   Verify the unique identifier

Wrong values could lead to network connection failures and the World Wide Name will be incorrect which will cause problems accessing the
array. (usually experienced after controller or chassis replacement)

The Unique Identifier is based on the chassis serial number.

The UID shoul d be preserved

In a dual controller array, the replacement controller will obtain a copy controller Unique Identifier.

In a single controller array, the replacement controller will have the same UID value it had previous to being replaced.

For details refer to the appropriate Controller Module Replacement Guide, found on the Oracle Disk Storage Systems Documentation page.

When replacing a controller or chassis(midplane) follow the Replacement guideline steps carefully. Record the unique identifier value before attempting replacement.

When replacing a controller if the value is not set to the recorded  value, the unique identifier will need to be set to 0 (to automatically read the chassis serial number from the midplane).

When replacing a chassis/midplane, the unique identifier will need to be set to the hex value for the original serial number of the chassis.

A nonzero value should be specified only if the chassis has been replaced, but the original chassis serial number must be retained.

H.   If the above steps did not help, refer to <Document 1005313.1> Sun Storage 3000 Arrays: Troubleshooting Configuration Problems.

For information about Media Scan:

http://pts-storage.us.oracle.com/products/SE33xx/toi/scan.html

For additional information about SMART:

http://pts-storage.us.oracle.com/products/SE33xx/toi/smart.html

For additional information about the Controller Unique ID:

http://pts-storage.us.oracle.com/products/SE33xx/toi/other.html

3510, 3511, 3310, 3320, 351x, 33x0, Fibre, SCSI Parameters, Defaults, cache, SES, port, loop, P2P, point-to-point, RS232, IP, telnet, write-back, peripheral, baud, normalized
Previously Published As
89051

This solution has no attachment