![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 2254509.1 : Fujitsu SPARC M12-1 / M12-2 / M12-2S Device Paths
In this Document
Applies to:Fujitsu SPARC M12-2 - Version All Versions to All Versions [Release All Releases]Fujitsu SPARC M12-2S - Version All Versions to All Versions [Release All Releases] Fujitsu SPARC M12-1 - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. GoalThe goal of this document is to describe the Device Paths for the servers in the M12 family SolutionM12-1Device Device Path 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 SAS /pci@8100/pci@4/pci@0/pci@0/scsi@0 Internal HDD#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p0 Internal HDD#1 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p1 Internal HDD#2 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p2 Internal HDD#3 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p3 Internal HDD#4 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p4 Internal HDD#5 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p5 Internal HDD#6 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p6 Internal HDD#7 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p7 External SAS /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p5xx Internal USB ports (rear: USB 3.0) /pci@8100/pci@4/pci@0/pci@8/usb@0/hub@1/****@1 (rear: USB 2.0/1.1) /pci@8100/pci@4/pci@0/pci@8/usb@0/hub@5/****@1 (front USB 2.0/1.1) /pci@8100/pci@4/pci@0/pci@8/usb@0/****@6 Remote storage /pci@8100/pci@4/pci@0/pci@8/usb@0/storage@7 PCI#0 /pci@8100/pci@4/pci@0/pci@9/****@0 PCI expansion units under PCI#0 PCI#1 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@0/****@0 PCI#2 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@1/****@0 PCI#3 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@8/****@0 PCI#4 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@0/****@0 PCI#5 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/****@0 PCI#6 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@10/****@0 PCI#7 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@11/****@0 PCI#8 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@0/****@0 PCI#9 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@1/****@0 PCI#10 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@10/****@0 PCI#11 /pci@8100/pci@4/pci@0/pci@9/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@11/****@0 Internal LAN#2 /pci@8200/pci@4/pci@0/pci@0/network@0 Internal LAN#3 /pci@8200/pci@4/pci@0/pci@0/network@0,1 PCI#1 /pci@8200/pci@4/pci@0/pci@8/****@0 PCI#1 PCIexpansion units under PCI#1 PCI#1 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@0/****@0 PCI#2 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@1/****@0 PCI#3 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@8/****@0 PCI#4 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@0/****@0 PCI#5 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/****@0 PCI#6 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@10/****@0 PCI#7 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@11/****@0 PCI#8 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@0/****@0 PCI#9 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@1/****@0 PCI#10 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@10/****@0 PCI#11 /pci@8200/pci@4/pci@0/pci@8/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@11/****@0 PCI#2 /pci@8300/pci@4/pci@0/pci@1/****@0 PCI expansion units under PCI#2 PCI#1 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@0/****@0 PCI#2 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@1/****@0 PCI#3 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@8/****@0 PCI#4 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@0/****@0 PCI#5 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@1/****@0 PCI#6 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@10/****@0 PCI#7 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@10/pci@0/pci@11/****@0 PCI#8 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@0/****@0 PCI#9 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@1/****@0 PCI#10 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@10/****@0 PCI#11 /pci@8300/pci@4/pci@0/pci@1/pci@0/pci@0/pci@0/pci@1/pci@0/pci@11/pci@0/pci@11/****@0
M12-2The M12-2 comes in two configurations: o 1 CPU configuration The Device Paths are different for the 2 configurations Device Paths for 1 CPU configuration on a M12-2Device Device Path
Internal LAN#0 /pci@8000/pci@4/pci@0/pci@0/network@0 Internal LAN#1 /pci@8000/pci@4/pci@0/pci@0/network@0,1 PCI#8 /pci@8000/pci@4/pci@0/pci@1/****@0 PCI#3 /pci@8000/pci@4/pci@0/pci@10/****@0 PCI#2 /pci@8000/pci@4/pci@0/pci@11/****@0 Internal SAS#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0 Internal HDD#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p0 Internal HDD#1 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p1 Internal HDD#2 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p2 Internal HDD#3 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p3 External SAS /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p5xx Internal USB ports (rear:USB3.0) /pci@8100/pci@4/pci@0/pci@1/usb@0/hub@1/****@1 (rear:USB2.0/1.1) /pci@8100/pci@4/pci@0/pci@1/usb@0/hub@5/****@1 (front:USB3.0/2.0/1.1) (*1) /pci@8100/pci@4/pci@0/pci@1/usb@0/****@6 Remote storage /pci@8100/pci@4/pci@0/pci@1/usb@0/storage@7 PCI#1 /pci@8100/pci@4/pci@0/pci@10/****@0 PCI#0 /pci@8100/pci@4/pci@0/pci@11/****@0 Internal LAN#2 /pci@8200/pci@4/pci@0/pci@0/network@0 Internal LAN#3 /pci@8200/pci@4/pci@0/pci@0/network@0,1 PCI#6 /pci@8200/pci@4/pci@0/pci@1/****@0 PCI#7 /pci@8200/pci@4/pci@0/pci@8/****@0 PCI#10 /pci@8200/pci@4/pci@0/pci@9/****@0 Internal SAS#1 /pci@8300/pci@4/pci@0/pci@0/scsi@0 Internal HDD#4 /pci@8300/pci@4/pci@0/pci@0/scsi@0/disk@p4 Internal HDD#5 /pci@8300/pci@4/pci@0/pci@0/scsi@0/disk@p5 Internal HDD#6 /pci@8300/pci@4/pci@0/pci@0/scsi@0/disk@p6 Internal HDD#7 /pci@8300/pci@4/pci@0/pci@0/scsi@0/disk@p7 PCI#4 /pci@8300/pci@4/pci@0/pci@1/****@0 PCI#5 /pci@8300/pci@4/pci@0/pci@8/****@0 PCI#9 /pci@8300/pci@4/pci@0/pci@9/****@0 * Disk paths can be different with HW RAID. See: Fujitsu M10/M12 Introduction to HW Raid (Doc ID 1623067.1)
Device Paths for 2 CPUs configuration on a M12-2
Device Device Path
Internal LAN#0 /pci@8000/pci@4/pci@0/pci@0/network@0
Internal LAN#1 /pci@8000/pci@4/pci@0/pci@0/network@0,1
PCI#2 /pci@8000/pci@4/pci@0/pci@11/****@0
Internal SAS#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p0
Internal HDD#1 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p1
Internal HDD#2 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p2
Internal HDD#3 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p3
External SAS /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p5xx
Internal USB port
(rear:USB3.0) /pci@8100/pci@4/pci@0/pci@1/usb@0/hub@1/****@1
(rear:USB2.0/1.1) /pci@8100/pci@4/pci@0/pci@1/usb@0/hub@5/****@1
(front:3.0/2.0/1.1) (*1) /pci@8100/pci@4/pci@0/pci@1/usb@0/****@6
Remote storage /pci@8100/pci@4/pci@0/pci@1/usb@0/storage@7
PCI#0 /pci@8100/pci@4/pci@0/pci@11/****@0
PCI#7 /pci@8200/pci@4/pci@0/pci@8/****@0
PCI#10 /pci@8200/pci@4/pci@0/pci@9/****@0
PCI#5 /pci@8300/pci@4/pci@0/pci@8/****@0
PCI#9 /pci@8300/pci@4/pci@0/pci@9/****@0
Internal LAN#2 /pci@8400/pci@4/pci@0/pci@0/network@0
Internal LAN#3 /pci@8400/pci@4/pci@0/pci@0/network@0,1
PCI#6 /pci@8400/pci@4/pci@0/pci@1/****@0
Internal SAS#1 /pci@8500/pci@4/pci@0/pci@0/scsi@0
Internal HDD#4 /pci@8500/pci@4/pci@0/pci@0/scsi@0/disk@p4
Internal HDD#5 /pci@8500/pci@4/pci@0/pci@0/scsi@0/disk@p5
Internal HDD#6 /pci@8500/pci@4/pci@0/pci@0/scsi@0/disk@p6
Internal HDD#7 /pci@8500/pci@4/pci@0/pci@0/scsi@0/disk@p7
PCI#4 /pci@8500/pci@4/pci@0/pci@1/****@0
PCI#8 /pci@8600/pci@4/pci@0/pci@1/****@0
PCI#3 /pci@8600/pci@4/pci@0/pci@10/****@0
PCI#1 /pci@8700/pci@4/pci@0/pci@10/****@0
* Disk paths can be different with HW RAID. See: Fujitsu M10/M12 Introduction to HW Raid (Doc ID 1623067.1) M12-2SThe M12-2S comes in two configurations: o 1 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 For example consider the Device Paths for HDD#0 for LSB00 and LSB01 in a 2 CPUs configuration: LSB00 path to HDD#0 /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p0 thus the only thing different between the two paths is the 8100 signifying LSB00 and 8900 signifying LSB01. The Device Paths shown will be for a generic M12-2S with the critical differentiator for the paths shown as <Inst #> Device Paths for 1 CPUs configuration on a M12-2SDevice Device Path Internal LAN#0 /pci@<Inst 0>/pci@4/pci@0/pci@0/network@0 Internal LAN#1 /pci@<Inst 0>/pci@4/pci@0/pci@0/network@0,1 PCI#3 /pci@<Inst 0>/pci@4/pci@0/pci@10/****@0 PCI#2 /pci@<Inst 0>/pci@4/pci@0/pci@11/****@0 Internal SAS#0 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0 Internal HDD#0 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p0 Internal HDD#1 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p1 Internal HDD#2 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p2 Internal HDD#3 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p3 External SAS /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p5xx Internal USB port (rear:USB3.0) /pci@<Inst 2>/pci@4/pci@0/pci@1/usb@0/hub@1/****@1 (rear:USB2.0/1.1) /pci@<Inst 2>/pci@4/pci@0/pci@1/usb@0/hub@5/****@1 (front:USB3.0/2.0/1.1) (*1) /pci@<Inst 2>/pci@4/pci@0/pci@1/usb@0/****@6 Remote storage /pci@<Inst 1>/pci@4/pci@0/pci@1/usb@0/storage@7 PCI#1 /pci@<Inst 1>/pci@4/pci@0/pci@10/****@0 PCI#0 /pci@<Inst 1>/pci@4/pci@0/pci@11/****@0 Internal LAN#2 /pci@<Inst 2>/pci@4/pci@0/pci@0/network@0 Internal LAN#3 /pci@<Inst 2>/pci@4/pci@0/pci@0/network@0,1 PCI#6 /pci@<Inst 2>/pci@4/pci@0/pci@1/****@0 PCI#7 /pci@<Inst 2>/pci@4/pci@0/pci@8/****@0 Internal SAS#1 /pci@<Inst 3>/pci@4/pci@0/pci@0/scsi@0 Internal HDD#4 /pci@<Inst 3>/pci@4/pci@0/pci@0/scsi@0/disk@p4 Internal HDD#5 /pci@<Inst 3>/pci@4/pci@0/pci@0/scsi@0/disk@p5 Internal HDD#6 /pci@<Inst 3>/pci@4/pci@0/pci@0/scsi@0/disk@p6 Internal HDD#7 /pci@<Inst 3>/pci@4/pci@0/pci@0/scsi@0/disk@p7 PCI#4 /pci@<Inst 3>/pci@4/pci@0/pci@1/****@0 PCI#5 /pci@<Inst 3>/pci@4/pci@0/pci@8/****@0 * Disk paths can be different with HW RAID. See: Fujitsu M10/M12 Introduction to HW Raid (Doc ID 1623067.1)
Examples of Device Paths for 1 CPU configuration on a M12-2S LSB00 - LSB15Consider the path /pci@a800/pci@4/pci@0/pci@0/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 indicate this is Internal LAN#1 on LSB05
Consider the path /pci@cb00/pci@4/pci@0/pci@0/scsi@0/disk@p5 The c800 corresponds to LSB09 and looking at the table this corresponds to Inst 3. Looking at the Device Paths above then this would indicate this is HDD#5 on LSB09
Consider the path /pci@f200/pci@4/pci@0/pci@8/network@0,1 The f200 corresponds to LSB14 and looking at the table this corresponds to Inst 2. Looking at the Device Paths above then this would indicate this is a network card in PCI 7 in LSB14 Device Paths for 2 CPUs configuration on a M12-2SDevice Device Path
Internal LAN#0 /pci@<Inst 0>/pci@4/pci@0/pci@0/network@0
Internal LAN#1 /pci@<Inst 0>/pci@4/pci@0/pci@0/network@0,1
PCI#2 /pci@<Inst 0>/pci@4/pci@0/pci@11/****@0
Internal SAS#0 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0
Internal HDD#0 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p0 *
Internal HDD#1 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p1 *
Internal HDD#2 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p2 *
Internal HDD#3 /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p3 *
External SAS /pci@<Inst 1>/pci@4/pci@0/pci@0/scsi@0/disk@p5xx
Internal USB port
(rear:USB3.0) /pci@<Inst 1>/pci@4/pci@0/pci@1/usb@0/hub@1/****@1
(rear:USB2.0/1.1) /pci@<Inst 1>/pci@4/pci@0/pci@1/usb@0/hub@5/****@1
(front:USB3.0/2.0/1.1) (*1) /pci@<Inst 1>/pci@4/pci@0/pci@1/usb@0/****@6
Remote storage /pci@<Inst 1>/pci@4/pci@0/pci@1/usb@0/storage@7
PCI#0 /pci@<Inst 1>/pci@4/pci@0/pci@11/****@0
PCI#7 /pci@<Inst 2>/pci@4/pci@0/pci@8/****@0
PCI#5 /pci@<Inst 3>/pci@4/pci@0/pci@8/****@0
Internal LAN#2 /pci@<Inst 4>/pci@4/pci@0/pci@0/network@0
Internal LAN#3 /pci@<Inst 4>/pci@4/pci@0/pci@0/network@0,1
PCI#6 /pci@<Inst 4>/pci@4/pci@0/pci@1/****@0
Internal SAS#1 /pci@<Inst 5/pci@4/pci@0/pci@0/scsi@0
Internal HDD#4 /pci@<Inst 5/pci@4/pci@0/pci@0/scsi@0/disk@p4 *
Internal HDD#5 /pci@<Inst 5/pci@4/pci@0/pci@0/scsi@0/disk@p5 *
Internal HDD#6 /pci@<Inst 5/pci@4/pci@0/pci@0/scsi@0/disk@p6 *
Internal HDD#7 /pci@<Inst 5/pci@4/pci@0/pci@0/scsi@0/disk@p7 *
PCI#4 /pci@<Inst 5/pci@4/pci@0/pci@1/****@0
PCI#3 /pci@<Inst 6>/pci@4/pci@0/pci@10/****@0
PCI#1 /pci@<Inst 7>/pci@4/pci@0/pci@10/****@0
* Disk paths can be different with HW RAID. See: Fujitsu M10/M12 Introduction to HW Raid (Doc ID 1623067.1)
Examples of Device Paths for 2 CPUs configuration on a M12-2S LSB00 - LSB15Consider the path /pci@dc00/pci@4/pci@0/pci@0/network@0,1 The dc00 corresponds to LSB11 and looking at the table this corresponds to Inst 4. Looking at the Device Paths above then this would indicate this is Internal LAN#3 on LSB11
Consider the path /pci@cd00/pci@4/pci@0/pci@0/scsi@0/disk@p6 The cd00 corresponds to LSB09 and looking at the table this corresponds to Inst 5. Looking at the Device Paths above then this would indicate this is HDD#6 on LSB09
Consider the path /pci@da00/pci@4/pci@0/pci@8/network@0,1 The da00 corresponds to LSB11 and looking at the table this corresponds to Inst 2. Looking at the Device Paths above then this would indicate this is a network card in PCI 7 in LSB11
OBP, format and prtdiag examples{0} ok show-nets 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 2 CPUs and the BB that is LSB07 contains 1 CPUs. Format output Searching for disks...done AVAILABLE DISK SELECTIONS: Note the paths under Solaris 11 don't look like the c0t0d0 designation in Solaris 10. The disks shown are HDD#0 and HDD#1 from LSB00 and HDD#5 and HDD#6 from LSB010 Determining the path to a disk at the OBP requires the output of show-disks and probe-scsi-all {0} ok show-disks 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@d500/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@8100/pci@4/pci@0/pci@1/pci@0/usb@4,1/storage@1 Unit 0 Removable Disk Staples 1.22 /pci@8100/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@d100. In the middle of the output is the beginning of the LSB00 information, identified by /pci@8100. 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@d500/pci@4/pci@0/pci@0/scsi@0/disk@p5,0 HDD#6 in LSB10 path to disk: /pci@d500/pci@4/pci@0/pci@0/scsi@0/disk@p6,0 HDD#0 in LSB00 path to disk: /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p0,0 HDD#1 in LSB00 path to disk: /pci@8100/pci@4/pci@0/pci@0/scsi@0/disk@p1,0 Determining the M12-2S 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 Max Speed Cur Speed Status Type Path /Width /Width ------------------------------------------------------------------------------------------- /BB0/CMUL/NET0 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@8000/pci@4/pci@0/pci@0/network@0 /BB0/CMUL/NET1 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@8000/pci@4/pci@0/pci@0/network@0,1 /BB0/CMUL/SASHBA0 PCIE scsi-pciex1000,87 LSI,2308_2 5.0GT/x8 5.0GT/x8 /pci@8100/pci@4/pci@0/pci@0/scsi@0 /BB0/CMUL/USB PCIE usb-pciexclass,0c0330 5.0GT/x1 5.0GT/x1 /pci@8100/pci@4/pci@0/pci@1/usb@0 /BB0/CMUL/NET2 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@8400/pci@4/pci@0/pci@0/network@0 /BB0/CMUL/NET3 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@8400/pci@4/pci@0/pci@0/network@0,1 /BB0/CMUL/SASHBA1 PCIE scsi-pciex1000,87 LSI,2308_2 5.0GT/x8 5.0GT/x8 /pci@8500/pci@4/pci@0/pci@0/scsi@0 /BB2/CMUL/NET0 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@d000/pci@4/pci@0/pci@0/network@0 /BB2/CMUL/NET1 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@d000/pci@4/pci@0/pci@0/network@0,1 /BB2/CMUL/SASHBA0 PCIE scsi-pciex1000,87 LSI,2308_2 5.0GT/x8 5.0GT/x8 /pci@d100/pci@4/pci@0/pci@0/scsi@0 /BB2/CMUL/USB PCIE usb-pciexclass,0c0330 5.0GT/x1 5.0GT/x1 /pci@d100/pci@4/pci@0/pci@1/usb@0 /BB2/CMUL/NET2 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@d400/pci@4/pci@0/pci@0/network@0 /BB2/CMUL/NET3 PCIE network-pciex8086,1528 5.0GT/x8 5.0GT/x8 /pci@d400/pci@4/pci@0/pci@0/network@0,1 /BB2/CMUL/SASHBA1 PCIE scsi-pciex1000,87 LSI,2308_2 5.0GT/x8 5.0GT/x8 /pci@d500/pci@4/pci@0/pci@0/scsi@0 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@8000/pci@4/pci@0/pci@0/network@0 /pci@d000/pci@4/pci@0/pci@0/network@0
The paths map to LSB00 which prtdiag shows is BB0 and LSB10 which prtdiag shows is BB2 The showboards output from the snapshot shows the mapping of BBs to LSBs for all ppars (domains) XSCF> showboards -a
PSB PPAR-ID(LSB) Assignment Pwr Conn Conf Test Fault ---- ------------ ----------- ---- ---- ---- ------- -------- 00-0 01(00) Assigned y y y Passed Normal 01-0 00(01) Assigned y y y Passed Normal 02-0 01(10) Assigned y y y Passed Normal 03-0 00(02) Assigned y y y Passed Normal 04-0 00(03) Assigned y y y Passed Normal 05-0 00(04) 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 --------------------------------------------- 01-0 01 /pci@8800/pci@4/pci@0/pci@0/network@0 03-0 02 /pci@9000/pci@4/pci@0/pci@0/network@0 04-0 03 /pci@9800/pci@4/pci@0/pci@0/network@0 05-0 04 /pci@a000/pci@4/pci@0/pci@0/network@0 00-0 01 /pci@8000/pci@4/pci@0/pci@0/network@0 02-0 10 /pci@d000/pci@4/pci@0/pci@0/network@0
06-0 02 /pci@9000/pci@4/pci@0/pci@0/network@0
07-0 03 /pci@9800/pci@4/pci@0/pci@0/network@0 During a solaris 11 install the disk list will look like this:
scsi 558.9 06CC_HDD01 TOSHIBA showhardconf shows: BB#00 Status:Normal; Role:Slave; Ver:2041h; Serial:2081238007; BB#01 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237012; BB#02 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237015; BB#03 Status:Normal; Role:Slave; Ver:2041h; Serial:2081237006; 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 References<NOTE:1623067.1> - Fujitsu M10 / M12 Introduction to HW RaidAttachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|