Sun Fire 4810 Server
 
Sun Fire E25K Server
 
Sun Fire 3800 Server
 
Sun Fire 15K Server
 
Sun Fire 12K Server
 
Sun Fire E6900 Server
 
Sun Fire 6800 Server
 
Sun Fire 4800 Server
 
Sun Fire E20K Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-Exxk
 
_Old GCS Categories>Sun Microsystems>Servers>High-End Servers
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
 

In this Document

Goal

Solution

Sun StorEdge D1000 (also applicable to Sun StorEdge D2 array)

Sun StorEdge 3120

Sun StorEdge D240 Media Tray

Sun StorEdge S1

References

Created from <SR 3-3925000581>

Applies to:

Goal

The following High-End platforms do not have internal disks that can be used as boot device, so usually this function is accomplished by an attached SCSI JBOD (Just a Bunch Of Disks) array:

• Sun Fire[TM] 12K/15K/E20K/E25K Servers (Starcat)
• Sun Fire 3800, 4800, 4810, 6800, E4900, and E6900 Systems (Serengeti)

This Document will help to identify which SCSI JBOD array is attached to a disk-less system (usually configured as boot device) among the most commonly used ones:

• Sun StorEdge D1000 (and D2)
• Sun StorEdge 3120
• Sun StorEdge D240 Media Tray
• Sun StorEdge S1 

Solution

 Most of the simple JBOD arrays commonly used as SCSI boot device are equipped with a SAF-TE chip (SCSI Accessed Fault-tolerant Enclosure protocol chip) used to monitor some chassis environmental parameters; Solaris will manage SAF-TE devices with ses driver (SCSI Enclosure Services Driver).

SAF-TE is accessed via the SCSI data bus and inquired by Solaris with luxadm command, that will tell also the specific array type. Also the "cfgadm -alv" command ( <explorer>/sysconfig/cfgadm-alv.out ) will show the enclosure type.

Below are some examples of the SAF-TE equipped devices.

Sun StorEdge D1000 (also applicable to Sun StorEdge D2 array)

D1000 has a maximum of twelve disks on two different SCSI buses that can be accesses separately (split bus configuration) or simultaneously from the same scsi initiator (full bus configuration: this requires External SCSI Jumper Cable); each bus has its SAF-TE chip.

Disks SCSI targets are assigned by the switch on the rear of the box: they can be set to 0-5 or 8-13 on each bus.

Example of D1000 array (full bus configuration) as shown by format command:

As you can see from the above output, all disks are accessed by the same SCSI path (full bus), were both SAF-TE devices will be shown by luxadm command:

References:

D1000 Service and Administration Guide: http://docs.oracle.com/cd/E19696-01/805-2624-12/805-2624-12.pdf
Information Center: Sun Storage D1000 Array (Doc ID 1449240.2)
Sun StorEdge[TM] D1000 array cabling and address (Doc ID 1018089.1)

Sun StorEdge 3120

Sun StorEdge 3120 has a maximum of four disks on two different SCSI buses that can be accesses separately (split bus configuration) or simultaneously from the same scsi initiator (single or full bus configuration: this requires Single Bus SCSI Jumper cable); there is only one SAF-TE chip however.

Disks SCSI target IDs are set based on the switch setting on the back of array when it is powered on: can be set to 8-11 or 12-15 based on the switch position, and will remain as set in both split or full bus configuration (according to disks IDs setting, SAF-TE chip will take SCSI ID 5 or 6, respectively).

Example of two different Sun StorEdge 3120 arrays as shown by format command (in the example below, one disk is failed):

As you can see from the above output, two 3120 arrays are connected to different SCSI paths and also have different SCSI IDs assigned to disks (this is not strictly required in such a scenario as there would be no conflict even with same disks IDs, as array are accessed by different SCSI buses).

Each array's SAF-TE chip is accessed by luxadm command as shown below:

References:
Sun StorEdge 3000 Family Installation, Operation, and Service Manual for the Sun StorEdge 3120 SCSI Array: http://docs.oracle.com/cd/E19247-01/816-7956-15/816-7956-15.pdf
Information Center: Sun Storage 3120 SCSI Array (Doc ID 1449353.2)
Verifying and Troubleshooting Sun Storage 3120, 3310 and 3320 Cabling (Doc ID 1006857.1)

Sun StorEdge D240 Media Tray

Sun StorEdge D240 Media Tray has two different SCSI buses that can be accesses separately (split bus configuration) or simultaneously from the same SCSI initiator (single or full bus configuration: this requires a Short SCSI I/O cable to be connected to one "in" and one "out" port on opposite sides on the rear of the chassis, as junction for the two SCSI buses). Each SCSI bus has its own SAF-TE chip.

Each SCSI bus can host up to two devices, one located in a central bay of the D240 the chassis ("upper drive" or "lower drive"), one located into a side bay ("left drive" or "right drive"). When in split bus configuration, upper central drive shares the same bus with the right device (looking at the front of the array).

By means of a configuration switch on the back of the chassis, SCSI target IDs for the installed devices may be assigned as follows:

While central bays may host hard disk drives only, D240 side bays may host Tape drives or CD-ROM drives also; this sometimes makes the array tricky to be detected by looking at Solaris format output only; in such a scenario, cfgadm command will give better view of the devices installed in the D240 chassis; please check examples below for details.

In the first example below, two different D240 arrays are connected to the Solaris host; both arrays have only hard disk drives installed and are configured in full SCSI bus:

SAF-TE monitoring chips can be inquired by luxadm command, and this will help in revealing the array type and bus configuration:

In the second example below, a single D240 array is connected to the Solaris host; array is configured in split SCSI bus and has hard disk drives installed into central chassis bays only:

Here, both disk drives has SCSI target IDs assigned to 0 because of the split bus config; a single SAF-TE per SCSI path will confirm this:

In the third example below, cfgadm command output shows all devices installed into a D240 array configured in full bus (here, disk drives are installed in central bays only):

References:
Sun StorEdge D240 Media Tray Installation, Operation, and Service Manual: http://docs.oracle.com/cd/E19766-01/806-4211-12/806-4211-12.pdf
Information Center: Sun Storage D240 (StorEdge) Media Tray (Doc ID 1449265.2)

Below are some examples of JBOD devices that are instead not equipped with the SAF-TE chip.

Sun StorEdge S1

Sun StorEdge S1 JBOD array is equipped with a single SCSI bus that host up to three disk drives, and has no SAF-TE device available, so luxadm command does not report any output as ses driver is not used. S1 may be recognized as disk drives SCSI target IDs are usually 0, 1 and 2.
As several S1 arrays can be chained together, each S1 chassis has a SCSI-ID setting switch on the rear that allow to change the disk drives' SCSI targets IDs in order to avoid conflict on same bus (disk drives IDs will be b, b+1, b+2, where b is the base number assigned to the chassis). This is anyway an uncommon scenario, as usually a single S1 JBOD array is attached to each SCSI host adapter, and base number is 0.

In the example below, two different S1 arrays are connected to the Solaris host; both arrays have SCSI base number set to 0:

References:
Sun StorEdge S1 Array Installation and Maintenance Manual: http://docs.oracle.com/cd/E19406-01/816-0080-13/816-0080-13.pdf
Information Center: Sun Storage S1 Array (Doc ID 1449322.2)

Internal Section

References:

• Sun StorEdge[TM] D1000: How to tell if you have a D1000 attached (Doc ID 1012070.1)
• Sun Storage 3000 Arrays: Troubleshooting JBOD Failures (Doc ID 1002790.1)
• How To Remove and Replace a Sun Storage 3120 SCSI Array HDD (Doc ID 1531979.1)
• How To Replace A Failed Disk in a D240 Media Tray:ATR:1499481.1:3 (Doc ID 1499481.1)

JBOD disk troubleshooting:
General Guidance for Diagnosis (Disk Failures/Errors) and Replacing Internal Server Disks and JBOD Disks within Solaris (Doc ID 1010946.1)

References

This solution has no attachment