Thursday, July 23, 2009

Instructions on booting a Sun Solaris 10 T2000 from Fabric (SAN) attached disks

Fabric (SAN) Booting a Sun Server

Server: Sun Fire T2000
HBA: Emulex (SUNW,emlxs-pci10df,fc00 LP10000-S)
SAN: Xiotech Magnitude 3D

Instructions for configuring and installing the Solaris 10 OS on a Sun
T2000 with a FC/SAN attached disk drive (ie. no local disks).

There are no directions anywhere, that I could find, that explains how
to perform this setup. Xiotech, IBM, and EMC all told me it was very
difficult to do on a Sun system. This is NOT the case, it is very
easy. It is nothing more then installing the OS.

Extra Notes
{ok} probe-scsi-all - shows drives attached to the system
{ok} show-disks - displays the disks attached to the system

We built a pretty stock jumpstart server using the JASS framework.
The following directions are all based on using jumpstart to build the

1) Configure the zone on the FC switches include the SAN and the HOST in
the zone (refer to switch documentation).

2) Configure the disks on the SAN. In our case we presented a single 45GB
disk to the system (refer to SAN documentation).

3) Boot the Sun system up into single user mode:

{ok} boot net -s

4) You are going to receive an error about the SAN disk not having a valid
lable, and a line that looks something like this:

WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,emlxs@1/fp@0,0/ssd@w212100d0b202bd41,0 (ssd2): has no label

5) Once the system is booted up, you need to label/format the disk:

# format

It will ask you to label the disk. Follow the directions.

6) Before you exit the format command make note of the full device name
for the SAN disk, it will look something like:


7) On the jumpstart server, setup a basic profile that will include
installing the OS on the SAN attached disk, something like:

root_device c2t212100D0B202BD41d0s0
filesys rootdisk.s0 10000 /
filesys rootdisk.s1 20000 /var
filesys rootdisk.s2 4000 swap
filesys rootdisk.s3 free /opt

8) Perform the Jumpstart Install:

{ok} boot net - install

8.5) You will see it selecting the SAN attached disk for the install:

- Selecting all disks
- Configuring boot device
- Using disk (c2t212100D0B202BD41d0) for "rootdisk"
- Configuring / (c2t212100D0B202BD41d0s0)
- Configuring /var (c2t212100D0B202BD41d0s1)
- Configuring swap (c2t212100D0B202BD41d0s2)
- Configuring /opt (c2t212100D0B202BD41d0s3)
- Automatically configuring disks for Solaris operating system
- Deselecting unmodified disk (c0t0d0)
- Deselecting unmodified disk (c0t1d0)

Creating and checking UFS file systems
- Creating / (c2t212100D0B202BD41d0s0)
- Creating /var (c2t212100D0B202BD41d0s1)
- Creating /opt (c2t212100D0B202BD41d0s3)

9) Once the install is completed you will see it reboot using the SAN
attached disk as the boot disk:

Rebooting with command: boot
Boot device: /pci@7c0/pci@0/pci@1/pci@0,2/SUNW,emlxs@1/fp@0,0/disk@w212100d0b202bd41,0:a File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.

1 comment:

  1. What about multipathing using MPXIO or Powerpath? This doesn't seem to take that into consideration.