Fujitsu M10-1, M10-4 and M10-4s Device Paths

Asset ID:	1-71-1543194.1
Update Date:	2018-04-05
Keywords:

Solution Type Technical Instruction Sure

Solution 1543194.1 : Fujitsu M10-1, M10-4 and M10-4s Device Paths

Applies to:

Fujitsu M10-1 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4 - Version All Versions to All Versions [Release All Releases]
Fujitsu M10-4S - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

The goal of this document is to describe the Device Paths for the servers in the M10 family

Solution

M10-1

The M10-1 comes in one configuration. The Device Paths for the M10-1 are as follows:

Device Device Path
Internal SAS /pci@8000/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2   /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
Internal HDD#4 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
Internal LAN#0    /pci@8000/pci@4/pci@0/pci@1/network@0
Internal LAN#1    /pci@8000/pci@4/pci@0/pci@1/network@0,1
Internal LAN#2    /pci@8100/pci@4/pci@0/pci@0/network@0
Internal LAN#3    /pci@8100/pci@4/pci@0/pci@0/network@0,1
Internal USB ports
rear: USB1.1 /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4/****@1
front: USB1.1 /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4/****@2
rear: USB2.0 /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/****@1
front USB2.0 /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/****@2
PCI#0 /pci@8000/pci@4/pci@0/pci@8/****@0
PCI#1 /pci@8100/pci@4/pci@0/pci@1/****@0
PCI#2 /pci@8100/pci@4/pci@0/pci@9/****@0

* Disk paths can be different with HW RAID. See:

Fujitsu M10-1, M10-4 and M10-4s Introduction to HW Raid (Doc ID 1623067.1)

M10-4

The M10-4 comes in two configurations:

o 2 CPUs configuration
o 4 CPUs configuration.

The Device Paths are different for the 2 configurations

Device Paths for 2 CPUs configuration on a M10-4

Device Device Path
Internal SAS /pci@8000/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
Internal HDD#4 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
Internal LAN#0 /pci@8000/pci@4/pci@0/pci@9/network@0
Internal LAN#1 /pci@8000/pci@4/pci@0/pci@9/network@0,1
Internal LAN#2 /pci@8000/pci@4/pci@0/pci@a/network@0
Internal LAN#3 /pci@8000/pci@4/pci@0/pci@a/network@0,1
Internal USB ports
rear: USB1.1 /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4/****@1
rear: USB2.0 /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/****@1
front: USB1.1/2.0) /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/hub@2/****@1
PCI#0 /pci@8100/pci@4/pci@0/pci@0/****@0
PCI#1 /pci@8100/pci@4/pci@0/pci@8/****@0
PCI#2 /pci@8100/pci@4/pci@0/pci@9/****@0
PCI#3 /pci@8200/pci@4/pci@0/pci@0/****@0
PCI#4 /pci@8200/pci@4/pci@0/pci@8/****@0
PCI#5 /pci@8200/pci@4/pci@0/pci@9/****@0
PCI#6 /pci@8200/pci@4/pci@0/pci@11/****@0
PCI#7 /pci@8300/pci@4/pci@0/pci@0/****@0
PCI#8 /pci@8300/pci@4/pci@0/pci@8/****@0
PCI#9 /pci@8300/pci@4/pci@0/pci@9/****@0
PCI#10 /pci@8300/pci@4/pci@0/pci@11/****@0

* Disk paths can be different with HW RAID. See:

Fujitsu M10-1, M10-4 and M10-4s Introduction to HW Raid (Doc ID 1623067.1)

Device Paths for 4 CPUs configuration on a M10-4

Device Device Path
Internal SAS /pci@8000/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0   /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2   /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
Internal HDD#4    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7    /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
Internal LAN#0    /pci@8000/pci@4/pci@0/pci@9/network@0
Internal LAN#1    /pci@8000/pci@4/pci@0/pci@9/network@0,1
Internal LAN#2    /pci@8400/pci@4/pci@0/pci@a/network@0
Internal LAN#3    /pci@8400/pci@4/pci@0/pci@a/network@0,1
Internal USB ports
rear: USB1.1 /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4/****@1
rear: USB2.0 /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/****@1
front: USB1.1/2.0) /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/hub@2/****@1
PCI#0 /pci@8100/pci@4/pci@0/pci@0/****@0
PCI#1 /pci@8500/pci@4/pci@0/pci@8/****@0
PCI#2 /pci@8500/pci@4/pci@0/pci@9/****@0
PCI#3 /pci@8200/pci@4/pci@0/pci@0/****@0
PCI#4 /pci@8200/pci@4/pci@0/pci@8/****@0
PCI#5 /pci@8600/pci@4/pci@0/pci@9/****@0
PCI#6 /pci@8600/pci@4/pci@0/pci@11/****@0
PCI#7 /pci@8300/pci@4/pci@0/pci@0/****@0
PCI#8 /pci@8300/pci@4/pci@0/pci@8/****@0
PCI#9 /pci@8700/pci@4/pci@0/pci@9/****@0
PCI#10      /pci@8700/pci@4/pci@0/pci@11/****@0

* Disk paths can be different with HW RAID. See:

Fujitsu M10-1, M10-4 and M10-4s Introduction to HW Raid (Doc ID 1623067.1)

M10-4S

The M10-4S comes in two configurations:

o 2 CPUs configuration
o 4 CPUs configuration.

The Device Paths are different for the 2 configurations

Not only do the Device Paths differ between the 2 configurations they also differ depending on the LSB#. So
the paths for LSB00 are similar to those of say LSB01. The critical differentiator is the beginning of the Device Path.

For example consider the Device Paths for HDD#0 for LSB00 and LSB01 in a 4 CPUs configuration:

LSB00 path to HDD#0 /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0
LSB01 path to HDD#0 /pci@8800/pci@4/pci@0/pci@0/scsi@0/disk@p0

thus the only thing different between the two paths is the 8000 signifing LSB00 and 8800 signifing LSB01.

The Device Paths shown will be for a generic M10-4S with the critical differentiator for the paths shown as <Inst #>
in both a 2 and 4 CPUs configuration. After the paths will be a table showing the corresponding <Inst #> numbers
for the paths in column 1 and then LSB00 - LSB15 in the following columns. Then it is just a matter of using the column 1
<Inst #> number and matching the rest of the path to determine the Device. There will be a few examples after the Tables
to help make this clear.

Device Paths for 2 CPUs configuration on a M10-4s

Device Device Path
Internal SAS /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
Internal HDD#4 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
Internal LAN#0 /pci@<Inst 0>/pci@4/pci@0/pci@9/network@0
Internal LAN#1 /pci@<Inst 0>/pci@4/pci@0/pci@9/network@0,1
Internal LAN#2 /pci@<Inst 0>/pci@4/pci@0/pci@a/network@0
Internal LAN#3 /pci@<Inst 0>/pci@4/pci@0/pci@a/network@0,1
Internal USB ports
rear: USB1.1 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4/****@1
rear: USB2.0 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4,1/****@1
front: USB1.1/2.0 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4,1/hub@2/****@1
PCI#0 /pci@<Inst 2>/pci@4/pci@0/pci@0/****@0
PCI#1   /pci@<Inst 2>/pci@4/pci@0/pci@8/****@0
PCI#2    /pci@<Inst 2>/pci@4/pci@0/pci@9/****@0
PCI#3   /pci@<Inst 4>/pci@4/pci@0/pci@0/****@0
PCI#4   /pci@<Inst 4>/pci@4/pci@0/pci@8/****@0
PCI#5   /pci@<Inst 4>/pci@4/pci@0/pci@9/****@0
PCI#6   /pci@<Inst 4>/pci@4/pci@0/pci@11/****@0
PCI#7   /pci@<Inst 6>/pci@4/pci@0/pci@0/****@0

* Disk paths can be different with HW RAID. See:

Fujitsu M10-1, M10-4 and M10-4s Introduction to HW Raid (Doc ID 1623067.1)

Inst #	LSB00	LSB01	LSB02	LSB03	LSB04	LSB05	LSB06	LSB07	LSB08
0	8000	8800	9000	9800	a000	a800	b000	b800	c000
2	8100	8900	9100	9900	a100	a900	b100	b900	c100
4	8200	8a00	9200	9a00	a200	aa00	b200	ba00	c200
6	8300	8b00	9300	9b00	a300	ab00	b300	bb00	c300

Inst #	LSB09	LSB10	LSB11	LSB12	LSB13	LSB14	LSB15
0	c800	d000	d800	e000	e800	f000	f800
2	c900	d100	d900	e100	e900	f100	f900
4	ca00	d200	da00	e200	ea00	f200	fa00
6	cb00	d300	db00	e300	eb00	f300	fb00

Examples of Device Paths for 2 CPUs configuration on a M10-4s LSB00 - LSB15

Consider the path /pci@a800/pci@4/pci@0/pci@a/network@0,1

The a800 corresponds to LSB05 and looking at the table this corresponds to Inst 0. Looking at the Device Paths above then this would indicates this is Internal LAN#3 on LSB05

Consider the path /pci@c800/pci@4/pci@0/pci@0/scsi@0/disk@p5

The c800 corresponds to LSB09 and looking at the table this corresponds to Inst 0. Looking at the Device Paths above then this would indicates this is HDD#5 on LSB09

Consider the path /pci@f100/pci@4/pci@0/pci@8/network@0,1

The f100 corresponds to LSB14 and looking at the table this corresponds to Inst 2. Looking at the Device Paths above then this would indicates this is a network card in PCI 1 in LSB14

Device Paths for 4 CPUs configuration on a M10-4s

Device Device Path
Internal SAS /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
Internal HDD#4 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7 /pci@<Inst 0>/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
Internal LAN#0   /pci@<Inst 0>/pci@4/pci@0/pci@9/network@0
Internal LAN#1   /pci@<Inst 0>/pci@4/pci@0/pci@9/network@0,1
Internal LAN#2   /pci@<Inst 1>/pci@4/pci@0/pci@a/network@0
Internal LAN#3   /pci@<Inst 1>/pci@4/pci@0/pci@a/network@0,1
Internal USB ports
rear: USB1.1 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4/****@1
rear: USB2.0 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4,1/****@1
front: USB1.1/2.0 /pci@<Inst 0>/pci@4/pci@0/pci@1/pci@0/usb@4,1/hub@2/****@1
PCI#0      /pci@<Inst 2>/pci@4/pci@0/pci@0/****@0
PCI#1    /pci@<Inst 3>/pci@4/pci@0/pci@8/****@0
PCI#2 /pci@<Inst 3>/pci@4/pci@0/pci@9/****@0
PCI#3 /pci@<Inst 4>/pci@4/pci@0/pci@0/****@0
PCI#4 /pci@<Inst 4>/pci@4/pci@0/pci@8/****@0
PCI#5 /pci@<Inst 5>/pci@4/pci@0/pci@9/****@0
PCI#6 /pci@<Inst 5>/pci@4/pci@0/pci@11/****@0
PCI#7 /pci@<Inst 6>/pci@4/pci@0/pci@0/****@0

* Disk paths can be different with HW RAID. See:

Fujitsu M10-1, M10-4 and M10-4s Introduction to HW Raid (Doc ID 1623067.1)

Inst #	LSB00	LSB01	LSB02	LSB03	LSB04	LSB05	LSB06	LSB07	LSB08
0	8000	8800	9000	9800	a000	a800	b000	b800	c000
1	8400	8c00	9400	9c00	a400	ac00	b400	bc00	c400
2	8100	8900	9100	9900	a100	a900	b100	b900	c100
3	8500	8d00	9500	9d00	a500	ad00	b500	bd00	c500
4	8200	8a00	9200	9a00	a200	aa00	b200	ba00	c200
5	8600	8e00	9600	9e00	a600	ae00	b600	be00	c600
6	8300	8b00	9300	9b00	a300	ab00	b300	bb00	c300

Inst #	LSB09	LSB10	LSB11	LSB12	LSB13	LSB14	LSB15
0	c800	d000	d800	e000	e800	f000	f800
1	cc00	d400	dc00	e400	ec00	f400	fc00
2	c900	d100	d900	e100	e900	f100	f900
3	cd00	d500	dd00	e500	ed00	f500	fd00
4	ca00	d200	da00	e200	ea00	f200	fa00
5	ce00	d600	de00	e600	ee00	f600	fe00
6	cb00	d300	db00	e300	eb00	f300	fb00

Examples of Device Paths for 4 CPUs configuration on a M10-4s LSB00 - LSB15

Consider the path /pci@dc00/pci@4/pci@0/pci@a/network@0,1

The dc00 corresponds to LSB11 and looking at the table this corresponds to Inst 1. Looking at the Device Paths above then this would indicates this is Internal LAN#3 on LSB11

Consider the path /pci@c800/pci@4/pci@0/pci@0/scsi@0/disk@p6

The c800 corresponds to LSB09 and looking at the table this corresponds to Inst 0. Looking at the Device Paths above then this would indicates this is HDD#6 on LSB09

Consider the path /pci@db00/pci@4/pci@0/pci@0/network@0,1

The db00 corresponds to LSB11 and looking at the table this corresponds to Inst 6. Looking at the Device Paths above then this would indicates this is a network card in PCI 7 in LSB11

OBP, format and prtdiag examples

{0} ok show-nets
a) /pci@b800/pci@4/pci@0/pci@a/network@0,1
b) /pci@b800/pci@4/pci@0/pci@a/network@0
c) /pci@b800/pci@4/pci@0/pci@9/network@0,1
d) /pci@b800/pci@4/pci@0/pci@9/network@0
e) /pci@8400/pci@4/pci@0/pci@a/network@0,1
f) /pci@8400/pci@4/pci@0/pci@a/network@0
g) /pci@8000/pci@4/pci@0/pci@9/network@0,1
h) /pci@8000/pci@4/pci@0/pci@9/network@0

This 2 LSB configuration shows the Internal Networks for LSB00 (e-h) and LSB07 (a - d). Note that LSB00 is shown at the bottom of the list. Also note that the BB that is LSB00 contains 4 CPUs and the BB that is LSB07 contains 2 CPUs.

Format output

Searching for disks...done

AVAILABLE DISK SELECTIONS:
0. c4t500003942828B15Ad0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>
/pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500003942828b15a,0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d4cff/04CM_HDD00/disk
1. c4t5000039408321952d0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>
/pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w5000039408321952,0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d4cff/04CM_HDD01/disk
2. c2t500003942823FB3Ad0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>
/pci@d000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500003942823fb3a,0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d247f/01XZ_HDD05/disk
3. c2t500003940832182Ed0 <TOSHIBA-MBF2600RC-3706 cyl 64986 alt 2 hd 27 sec 668>
/pci@d000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500003940832182e,0
/dev/chassis/FUJITSU-BBEXP.500000e0e06d247f/01XZ_HDD06/disk

Note the paths under Solaris 11 don't look like the c0t0d0 designation in Solaris 10. The disk shown are HDD#0 and HDD#1 from LSB00 and HDD#5 and HDD#6 from LSB010

from prtdiag

================================ IO Devices ================================

Slot + Bus Name + Model Speed

Status Type Path

----------------------------------------------------------------------------

/BB5/CMUL/SASHBA PCIE scsi-pciex1000,87 LSI,2308_2 5.0GTx8

/pci@8000/pci@4/pci@0/pci@0/scsi@0

/BB5/CMUL/NET0 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8000/pci@4/pci@0/pci@9/network@0

/BB5/CMUL/NET1 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8000/pci@4/pci@0/pci@9/network@0,1

/BB5/CMUL/NET2 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8400/pci@4/pci@0/pci@a/network@0

/BB5/CMUL/NET3 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8400/pci@4/pci@0/pci@a/network@0,1

/BB8/CMUL/SASHBA PCIE scsi-pciex1000,87 LSI,2308_2 5.0GTx8

/pci@8800/pci@4/pci@0/pci@0/scsi@0

/BB8/CMUL/NET0 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8800/pci@4/pci@0/pci@9/network@0

/BB8/CMUL/NET1 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8800/pci@4/pci@0/pci@9/network@0,1

/BB8/PCI3 PCIE network-pciex8086,105e SUNW,pcie-northstar2.5GTx4

/pci@8a00/pci@4/pci@0/pci@0/network@0

/BB8/PCI3 PCIE network-pciex8086,105e SUNW,pcie-northstar2.5GTx4

/pci@8a00/pci@4/pci@0/pci@0/network@0,1

/BB8/CMUL/NET2 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8c00/pci@4/pci@0/pci@a/network@0

/BB8/CMUL/NET3 PCIE network-pciex8086,10c9 2.5GTx2

/pci@8c00/pci@4/pci@0/pci@a/network@0,1

MB PCIX usb-pciclass,0c0310 --

/pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4

MB PCIX usb-pciclass,0c0320 --

/pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1

MB PCIX usb-pciclass,0c0310 --

/pci@8800/pci@4/pci@0/pci@1/pci@0/usb@4

MB PCIX usb-pciclass,0c0320 --

/pci@8800/pci@4/pci@0/pci@1/pci@0/usb@4,1

This shows the 4 Internal Networks for LSB00 and LSB01, the SCSI controlers, the USB ports and a 2 port network card in LSB01 PCI slot 3.
Also note that prtdiag is a good source when trying to map the LSB# to the physical BB#. In this example LSB00 is physical BB#5 and LSB01
is BB#8

Determining the path to a disk at the OBP requires the output of show-disks and probe-scsi-all

{0} ok show-disks
a) /pci@d000/pci@4/pci@0/pci@0/scsi@0/disk
b) /pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/storage@1/disk
c) /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk
d) /iscsi-hba/disk
q) NO SELECTION
Enter Selection, q to quit:

the show-disks output shows the beginning of the disk path for the disks in LSB00 (menu choice c) and LSB10 (menu choice a)

{0} ok probe-scsi-all
/pci@d000/pci@4/pci@0/pci@0/scsi@0

FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00

Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 500003942823fb38 SASAddress 500003942823fb3a PhyNum 5
Target b
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 500003940832182c SASAddress 500003940832182e PhyNum 6
Target c
Unit 0 Encl Serv device FUJITSU BBEXP 0d32
SASAddress 500000e0e06d247d PhyNum 14

/pci@8000/pci@4/pci@0/pci@1/pci@0/usb@4,1/storage@1
Unit 0 Removable Disk Staples 1.22

/pci@8000/pci@4/pci@0/pci@0/scsi@0

FCode Version 1.00.56, MPT Version 2.00, Firmware Version 13.00.66.00

Target a
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 500003942828b158 SASAddress 500003942828b15a PhyNum 0
Target b
Unit 0 Disk TOSHIBA MBF2600RC 3706 1172123568 Blocks, 600 GB
SASDeviceName 5000039408321950 SASAddress 5000039408321952 PhyNum 1
Target c
Unit 0 Encl Serv device FUJITSU BBEXP 0d32

The probe-scsi-all shows which disks are physically installed. The beginning of the output shows the information for LSB10 which can be identified by /pci@d000. In the middle of the output is the beginning of the LSB00 information, identified by /pci@8000. The first device for LSB00 is a USB device. The easiest way to identify the disks is by the 600 GB. Looking at the disk size it is easy to see that there are 4 disks. Use the information just under the 600GB line to make the disk paths.

The format of the path is <beginning of path>@p<PhyNum>,0

HDD#5 in LSB10 path to disk: /pci@d000/pci@4/pci@0/pci@0/scsi@0/disk@p5,0
HDD#6 in LSB10 path to disk: /pci@d000/pci@4/pci@0/pci@0/scsi@0/disk@p6,0
HDD#0 in LSB00 path to disk: /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0
HDD#1 in LSB00 path to disk: /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p1,0

Determining the M10-4s BB for a given LSB from an explorer or snapshot.

Knowing the path to a given hardware component is usually not enough. For purposes of physically connecting networks, booting off a network port or doing hardware replacement, you need to know both the path and the BB associated with it. The path has to by mapped to a physical BB.

From the explorer this is simply a matter of looking at the prtdiag to determine the mapping:

================================ IO Devices ================================

Slot + Bus Name + Model Speed

Status Type Path

----------------------------------------------------------------------------

/BB6/CMUL/SASHBA PCIE scsi-pciex1000,87 LSI,2308_2 5.0GTx8

/pci@9000/pci@4/pci@0/pci@0/scsi@0

/BB6/CMUL/NET0 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9000/pci@4/pci@0/pci@9/network@0

/BB6/CMUL/NET1 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9000/pci@4/pci@0/pci@9/network@0,1

/BB6/CMUL/NET2 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9400/pci@4/pci@0/pci@a/network@0

/BB6/CMUL/NET3 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9400/pci@4/pci@0/pci@a/network@0,1

/BB7/CMUL/SASHBA PCIE scsi-pciex1000,87 LSI,2308_2 5.0GTx8

/pci@9800/pci@4/pci@0/pci@0/scsi@0

/BB7/CMUL/NET0 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9800/pci@4/pci@0/pci@9/network@0

/BB7/CMUL/NET1 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9800/pci@4/pci@0/pci@9/network@0,1

/BB7/PCI3 PCIE network-pciex8086,105e SUNW,pcie-northstar2.5GTx4

/pci@9a00/pci@4/pci@0/pci@0/network@0

/BB7/PCI3 PCIE network-pciex8086,105e SUNW,pcie-northstar2.5GTx4

/pci@9a00/pci@4/pci@0/pci@0/network@0,1

/BB7/CMUL/NET2 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9c00/pci@4/pci@0/pci@a/network@0

/BB7/CMUL/NET3 PCIE network-pciex8086,10c9 2.5GTx2

/pci@9c00/pci@4/pci@0/pci@a/network@0,1

MB PCIX usb-pciclass,0c0310 --

/pci@9000/pci@4/pci@0/pci@1/pci@0/usb@4

MB PCIX usb-pciclass,0c0320 --

/pci@9000/pci@4/pci@0/pci@1/pci@0/usb@4,1

MB PCIX usb-pciclass,0c0310 --

/pci@9800/pci@4/pci@0/pci@1/pci@0/usb@4

MB PCIX usb-pciclass,0c0320 --

/pci@9800/pci@4/pci@0/pci@1/pci@0/usb@4,1

The fist step is to determine the LSB #s that are used. prtdiag will always show the 4 network ports for a given BB.

For this example there are 2 sets of 4 network ports or 2 LSBs

Using the above table and the following 2 paths to NET0 (LAN 0):

        /pci@9000/pci@4/pci@0/pci@9/network@0
        /pci@9800/pci@4/pci@0/pci@9/network@0

The paths map to LSB02 which prtdiag shows is BB6 and LSB03 which prtdiag shows is BB7

The   showboards   output from the snapshot shows the mapping of BBs to LSBs for all ppar s (domains)

XSCF> showboards -a
PSB PPAR-ID(LSB) Assignment Pwr Conn Conf Test    Fault
---- ------------ ----------- ---- ---- ---- ------- --------
00-0 00(00)       Assigned    y    y    y    Passed Normal
01-0 00(01)       Assigned    y    y    y    Passed Normal
02-0 01(01)       Assigned    y    y    y    Passed Normal
03-0 01(02)       Assigned    y    y    y    Passed Normal
04-0 01(03)       Assigned    y    y    y    Passed Normal
05-0 00(02)       Assigned    y    y    y    Passed Normal
06-0 02(02)       Assigned    y    y    y    Passed Normal
07-0 02(03)       Assigned    y    y    y    Passed Norma

The PSB is the BB so in this example the mapping is for BB00 - BB07
The are 3 ppar s (domains) 0 1 and 2
The LSB numbers only have to be unique to the ppar

So the mapping we have is:

BB    LSB    Path to LAN 0
---------------------------------------------
00-0   00          /pci@8000/pci@4/pci@0/pci@9/network@0
01-0   01          /pci@8800/pci@4/pci@0/pci@9/network@0
05-0 02          /pci@9000/pci@4/pci@0/pci@9/network@0

02-0   01        /pci@8800/pci@4/pci@0/pci@9/network@0
03-0   02          /pci@9000/pci@4/pci@0/pci@9/network@0
04-0   03          /pci@9800/pci@4/pci@0/pci@9/network@0

06-0 02 /pci@9000/pci@4/pci@0/pci@9/network@0
07-0 03 /pci@9800/pci@4/pci@0/pci@9/network@0

Matching Solaris Install Disk Names to Actual BB Location

During a solaris 11 install the disk list will look like this:

scsi 558.9 06CC_HDD01 TOSHIBA
scsi 558.9 06CD_HDD00 TOSHIBA
scsi 558.9 06CD_HDD01 TOSHIBA
scsi 558.9 02DE_HDD00 TOSHIBA
scsi 558.9 02DE_HDD01 TOSHIBA
scsi 558.9 06CC_HDD00 TOSHIBA
scsi 558.9 06C9_HDD00 TOSHIBA
scsi 558.9 06C9_HDD01 TOSHIBA

showhardconf shows:

BB#00 Status:Normal; Role:Slave; Ver:2041h; Serial:2081238007;
CMUL Status:Normal; Ver:0101h; Serial:PP123602DE ;

BB#01 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237012;
CMUL Status:Normal; Ver:0101h; Serial:PP123406C9 ;

BB#02 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237015;
CMUL Status:Normal; Ver:0101h; Serial:PP123406CD ;

BB#03 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237006;
CMUL Status:Normal; Ver:0101h; Serial:PP123406CC ;

The abbreviated XSCF> showhardconf shows that the Bold numbers on the front of the disk names come from the end of the CMUL Serial Number so

02DE is BB#00
06C9   is BB#01
06CD   is BB#02
06CC   is BB#03

References

<NOTE:1623067.1> - Fujitsu M10 / M12 Introduction to HW Raid

Attachments

This solution has no attachment