Sun Fire T1000 Server
 
Sun Fire T2000 Server
 
Sun SPARC Enterprise T5120 Server
 
Sun Ultra 25 Workstation
 
Sun SPARC Enterprise T5220 Server
 
Sun SPARC Enterprise T5240 Server
 
Sun SPARC Enterprise T5140 Server
 

PLA-Support>Sun Systems>SPARC>Usx/Blade/Netra>SN-SPARC: USx
 
.Old GCS Categories>Sun Microsystems>Servers>Blade Servers
 
.Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
 
.Old GCS Categories>Sun Microsystems>Desktops>Workstations
 
.Old GCS Categories>Sun Microsystems>Servers>CMT Servers
 

This document provides basic information of the LSI-H/W-RAID functionality on the Sun Fire[TM] Mid-range- and Work group servers Sun Fire[TM] T1000, T2000, netra T2000, T5120, T5220,  T5140, T5240, V215, V245, V445, V440, Netra 440, Workstations Ultra[TM] 25 and Ultra 45 and Sun Blade[TM] T6300, T6320, T6340

Hardware

LSI 1030 is on-board for V440/Netra 440 - even though some PCI HBAs use the same chip, RAID functionality is only supported with the on-board controller for V440/Netra 440
LSI SAS1064 is a HBA built into all current machines with up to 4 SAS disks
LSI SAS1068 controller is mounted on PCI-X slot on V445 for up to 8 disks
LSI SAS1068E is part of each T6300/T6320 blade module and T5120/5220

Device paths

You can determine the type and/or path of the HBA via different methods:

From Solaris:

# iostat -En

e.g.
c1t0d0 LSILOGIC Product: 1030
c0t0d0 LSILOGIC Product: Logical Volume Revision: 3000

# cfgadm -alv

e.g. c1t0d0 LSILOGIC 1030 /devices/pci@1f,700000/scsi@2:scsi::dsk/c1t0d0

# prtdiag -v

e.g. scsi-pci1000,30 LSI,1030 /pci@1f,700000/scsi@2
e.g. scsi-pci1000,50 LSI,1064 /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1

# prtconf -vp

e.g.
LSI1030 FCode Driver: 1.8 03/04/17 scsi: '/pci@1f,700000/scsi@2'firmware-version: '1.03.11.01'
LSI,1064 firmware-version:'1.08.04.00' mpt-version:'1.05'version: '1.00.40'

# prtpicl -v

e.g.
LSI1030 FCode Driver: 1.8 03/04/17 devfs-path /pci@1f,700000/scsi@2
LSI,1064 mpt-version 1.05 firmware-version 1.8.4.0
devfs-path /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1

From explorer:

The above information is also available in explorer output in addition we have the scsi-inquiries in ./disks/diskinfo

e.g.
c1t0d0 LSILOGIC 1030-IM -IM 1000 LSIINTERNAL
c0t0d0 LSILOGIC Logical Volume 3000 LSIInternal

From the OBP:

Use probe-scsi-all or devalias or show-disks to get the right controller path

e.g. ok probe-scsi-all

/pci@7c0/pci@0/pci@2/scsi@0
MPT Version 1.05, Firmware Version 1.18.00.00
Target 0
Unit 0 Disk SEAGATE ST914602SSUN146G0400 286739329 Blocks, 146 GB
SASAddress 5000c50000b84465 PhyNum 0

e.g. ok show-disks

a) /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk
b) /pci@1e,600000/pci@0/pci@1/pci@0/ide@1f/cdrom
c) /pci@1e,600000/pci@0/pci@1/pci@0/ide@1f/disk
q) NO SELECTION
Enter Selection, q to quit: q

choose the right path:

e.g.
ok cd /pci@1e,600000/pci@0/pci@2/scsi@0
ok .properties
...
firmware-version 1.08.04.00
mpt-version 1.05

The current paths to LSI-controllers are:

Ultra25
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1

Ultra45
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1

V440
/pci@1f,700000/scsi@2

V215
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1

V245
/pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1

V445
/pci@1f,700000/pci@0/pci@2/pci@0/pci@8/LSILogic,sas@1

V445 with 501-7244 SAS controller
/pci@1e,600000/pci@0/pci@2/scsi@0

T1000
/pci@7c0/pci@0/pci@8/scsi@2

T2000
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
- for initial T2000 systems using factory installed PCI-X card (370-7696)
/pci@780/pci@0/pci@9/scsi@0 for later T2000 with on-board chip

T6300
/pci@7c0/pci@0/pci@2/scsi@0

T6320
/pci@0/pci@0/pci@2/LSILogic,sas@0

T5120
/pci@0/pci@0/pci@2/scsi@0

T5220
/pci@0/pci@0/pci@2/scsi@0

T5140/T5240
/pci@400/pci@0/pci@8/scsi@0

T6340
/pci@500/pci@0/pci@9/LSILogic,sas@0

The kernel driver module for all those LSI-controller is "mpt".

Special Information

• The only tool to manage the LSI HBA on Solaris is "raidctl"

• The only supported "normal" way to create a RAID-Volume is usage of "raidctl" after boot net -s or boot cdrom -s

• Always use "Auto configure" in format type menue. Otherwise you could loose an amount of the maximum volume capacity by wrong logical geometry and type

• LSI1030 HBA supports only 1 RAID volume (IM, Integrated Mirror) on V440
  H/W mirroring can be initiated after installation of data onto physical disk.
  Backwards, breaking the mirror will give two disks with valid data on each.

• LSI SAS1064/1068 HBA supports up to 2 RAID volumes of same RAID-level for machines with more than two harddisks.
  Just one RAID is supported on two-disk machines T1000, V215, Ultra25.

• Having more than the supported volumes or ghost volumes configured, can cause panic on boot. You must remove ghost volumes via OBP command "show-volumes" and "delete-volume".

• When a board that houses the RAID-controller is replaced, the new chip has the existing Raidset not enabled. Because of that boot off the Raid is not possible.
  OBP nor OS detect the underlaying physical disks.
  Trying to delete the Raid volume via OBP "delete-volume", would release physical disks, but destroy data on former Raid-disks.
  The reason for this is the different disk format when disks are part of a RAID.
  You must enable the volumes, recognized on original disks, via OBP command "activate-volume".

• Disk format of directly accessible disk and disks behind a RAID-volume are only identical on V440 machines with older controller chips. On this machine you can delete volume and use data on underlaying disks. Vice versa, you can install data on physical disks and create the H/W mirror without loosing data.

NOTE: There are no sense data logged on RAID-controller to determine a disk, that is already "leaky", but not yet FAILED by LSI chip firmware.
There is no other way than reading "raidctl" output or looking for scsi errors or warnings on mpt driver

Firmware and Patches

Remember to install the right and best OBP version, because OBP contains the proper driver to communicate with FCode on HBA.

Current firmware/FCode:

lsi1030-fw-1.03.11.01
sas1064: version 1.00.39: mpt-version 1.05: firmware-version 1.8.4.0
sas1068: version 1.00.39: mpt-version 1.05: firmware-version 1.8.4.0
sas1068: on T63xx and T5xxx MPT Version 1.05, Firmware Version 1.22.00.00

Above codes can be reached either by factory default implementation, proper OBP-upgrade or by use of following patches

lsi1030-fw-1.03.11.01
patch 115662-01
Hardware/Firmware: LSI1030 U320 SCSI controller

sas1064 on T1000
123456-01
Hardware/PROM Sun Fire T1000 1064 Firmware update V1.10.00.00IR

sas1064 on T2000 with PCI-X Plugin cards FCode_1_00_40.ROM
122165-02
Hardware/1064_FCode Sun Fire T2000 1064 FCode update

sas1068 on V445
123485-01
Hardware/PROM Sun Fire V445 1068X update 1.0.39

In general HBA fcodes are part of obp code on machines with on-board HBAs.
Every OBP- or FCode upgrade requires a power-cyle, not just a reboot.

Required Solaris patches:

Solaris 8:


SunOS 5.8: mpt driver patch

Solaris 9:

<SUNPATCH: 116532-03>
SunOS 5.9: mpt Patch

Solaris 10:

<SUNPATCH: 143128-04> (or later) SunOS 5.10: MPT driver patch
Please note the Required Patches for 143128-xx listed in the Patch Description

In general mpt driver is part of kernel patches of Sol9 and Sol10; kernel patching is required.

Reference

This Technical Instruction is platform comprehensive and supplements the following documents:

<Document: 1006930.1> RAID on the Sun Fire [TM] V215/245 Servers

<Document: 1009346.1> Hardware RAID usage on the Sun Fire[TM] T2000

<Document: 1018063.1> Deleting mirrored volume on a Sun Fire[TM] V440 if OS is not yet installed

<Document: 1009932.1> SunFire[TM] systems using on-board LSI SAS controller incur disk geometry re-mapping issues when existing OS on a regular SAS/SATA disk is HW RAIDed

<Document: 1018181.1> How to delete a RAID volume on a Sun Fire[TM] V215/V245 at the OBP level

References

This solution has no attachment