Solaris

hi all:
I have a sun blade-1000 for labs only, with 73G hd loaded, which boot block installed on slice 0. I'm confused by setting "boot-device" value in obp, which my question as follow:

in ok mode, I got device alias like this:
disk0: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@2,0

as I know the the disk0(fc disk) with wwn got form "cfgadm -al":
c1::2112345c5032da08 .... (for example.)

so I can replace the default boot device with:
boot /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w2112345c5032da08,0
(same as followed :a)
or just said;
boot disk0

with "prtconf -v" got the device path of HD is:
dev_path=/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100000c5032da08,0:a
or "format":
/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2112345c5032da08,0

but such boot device caused fail to boot up:
boot /pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2112345c5032da08,0
(same as followed :a)
...
Can't locate boot device

seem like only ".../disk@w211..." work but ".../ssd@w211..." don't work. can any one tell the difference? and where the value ".../disk@" came from?

I'm pretty new to solaris, so any help is great, thank in advance.

disk is the hardware device. ssd is the driver name for solaris . this can not be seen from obp, only from solaris.

thank, I guess that I probably understand the difference now, but still wondering about why use "disk"? is it from "show-disks" responds ?
{0} ok show-disks
a) /pci@8,600000/SUNW,qlc@4/fp@0,0/disk
...
thank

'disk' is the generic name used by the OBP to identify a disk target. Basically it just means that this is a block device that the OBP recognises as having a generic "disk" interface, it can be any type of disk, including a LUN made up of many one or many disks on external storage that makes up.

In order to allow it to be "sas" of "ssd" or "dad" or any of the other types of disk a lot more and less generic code would be required in the PROM. Disk is simply the most logical choice for the generic name for anything which looks like a disk. It is not because of / a result of show-disks they both use the same underlying code to find/map the device, they are simply using the same information so one will match the other.

hi all, I got the answer now. thank.