The SPARC T4-1 server has two SAS2 RAID controllers on the motherboard. Each controller is connected to four slots on the disk backplane. The following table shows the PhyNum-to-disk slot mapping for the eight-slot SPARC T4-1 backplane.
Table 4 SAS2 Controller Port Mapping for the SPARC T4-1 Disk Backplane
This table shows that ports 0-3 of controller 0 are connected to backplane slots 0-3 and ports 0-3 of controller 1 are connected to slots 4-7.
The following example is based on a SPARC T4-1 server with eight hard drives. These hard drives are deployed as six individual storage devices and a virtual drive. The virtual drive consists of two hard drives configured as a RAID volume. Controllers 0 and 1 are attached to these storage devices in the following manner:
Controller 0 is attached to Targets 9 and b (two individual storage devices).
Controller 0 is also attached to Target 523 (a RAID volume).
Controller 1 is attached to Targets 9, b, c, and d (four individual storage devices).
Controller 1 is also attached to Target a (a DVD unit).
Note - For SPARC T4-1 servers, the second field of the device path specifies the controllers: /pci@400/pci@1 = controller 0 and /pci@400/pci@2 = controller 1.
ok probe-scsi-all /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 /pci@400/pci@2/pci@0/pci@4/scsi@0 <---- SAS controller 1 FCode Version 1.00.56, MPT Version 2.00, Firmware Version 9.00.00.00 Target 9 Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c5001d33fba7 SASAddress 5000c5001d33fba5 PhyNum 0 Target a Unit 0 Removable Read Only device TEAC DV-W28SS-R 1.0C SATA device PhyNum 6 Target b Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00a76e380 SASAddress 5000cca00a76e381 PhyNum 1 Target c Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000cca00a76ddcc SASAddress 5000cca00a76ddcd PhyNum 2 Target d Unit 0 Disk HITACHI H106060SDSUN600G A2B0 1172123568 Blocks, 600 GB SASDeviceName 5000cca01201e544 SASAddress 5000cca01201e545 PhyNum 3 /pci@400/pci@1/pci@0/pci@4/scsi@0 <---- SAS controller 0 FCode Version 1.00.56, MPT Version 2.00, Firmware Version 9.00.00.00 Target 9 Unit 0 Disk HITACHI H103030SCSUN300G A2A8 585937500 Blocks, 300 GB SASDeviceName 5000cca00a75dcac SASAddress 5000cca00a75dcad PhyNum 0 Target a Unit 0 Disk SEAGATE ST930003SSUN300G 0B70 585937500 Blocks, 300 GB SASDeviceName 5000c5001d33eb5f SASAddress 5000c5001d33eb5d PhyNum 1 Target 523 Volume 0 Unit 0 Disk LSI Logical Volume 3000 583983104 Blocks, 298 GB VolumeDeviceName 3ce534e42c02a3c0 VolumeWWID 0ce534e42c02a3c0 ok
In this example, the controller ports are attached to the hard drives and the DVD in the following manner:
Note - Target values are not static. The same storage device can appear in two consecutive probe-scsi-all listings with different Target values.
The default boot device has the following values:
Controller = 0
Target = 9
PhyNum = 0
SASDeviceName = 5000cca00a75dcac
SASAddress = 5000cca00a75dcad
If you want to specify another drive to be the boot device, find its PhyNum value in the output and use the SASDeviceName assigned to that device. For example, if you want to use the hard drive in disk slot 5, it has the following values:
Controller = 1
Target = b
PhyNum = 1
SASDeviceName = 5000cca00a76e380
SASAddress = 5000cca00a76e381