| SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers Administration Guide
|
|
Mapping Device Path Names
|
This appendix
describes how to map device path names to physical system devices in
SPARC Enterprise M3000/M4000/M5000/M8000/M9000 servers from Oracle and
Fujitsu. It contains these sections:
Device Mapping and Logical System Board Numbers
The physical address represents a
physical
characteristic that is unique to the device. Examples of physical
addresses include the bus address and the slot number. The slot number
indicates where the device is installed.
The
logical system board (LSB) number affects both the processor numbering and the
I/O device paths in the server. Physical resources are assigned to LSBs in the specified domain using the
setdcl command. It is the LSB numbers that the Oracle Solaris OS uses.
CPU Mapping
Each LSB on a midrange or high-end server has a bank of 32
processor
numbers assigned to it. For entry-level servers, the bank holds eight
processors. The SPARC64 VI processor has two cores, each with two
threads (also known as
virtual processors). The SPARC64 VII+ and SPARC64 VII processor has two cores or four cores, each with two threads.
An LSB on a
midrange or high-end server has up to four processors (when a Uni-XSB is
assigned to the LSB); therefore, the LSB needs 32 processor IDs. An LSB
on an entry-level server, which supports only a single processor,
requires only eight processor IDs.
TABLE A-1 shows the relationship between LSB numbers and starting processor (
proc) numbers, in hexadecimal/decimal format. The Oracle Solaris
prtdiag(IM)
command provides the LSB numbers and CPU chip numbers in decimal format for components that are part of the domain.
TABLE A-1 LSB Numbers and Starting Processor Numbers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Midrange and High-End Servers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CPU Numbering Examples
This section contains examples of CPU numbering, using the output of the
showboards(8)
command on the Service Processor, and the output of the
prtdiag(1M)
command on the domain.
XSCF> showboards -a
XSB DID(LSB) Assignment Pwr Conn Conf Test Fault
---- -------- ----------- ---- ---- ---- ------- --------
00-0 00(00) Assigned y y y Passed Normal
00-1 00(01) Assigned y y y Passed Normal
00-2 00(04) Assigned y y y Passed Normal
00-3 00(05) Assigned y n n Passed Normal
01-0 01(00) Assigned y y y Passed Normal
01-1 01(09) Assigned y y y Passed Normal
01-2 01(06) Assigned y n n Passed Normal
01-3 01(07) Assigned y n n Passed Normal
|
domain_0# prtdiag -v
...
==================================== CPUs ====================================
CPU CPU Run L2$ CPU CPU
LSB Chip ID MHz MB Impl. Mask
--- ---- -------------------- ---- --- ----- ----
00 0 0, 1, 2, 3 2150 4.0 6 129
01 1 40, 41, 42, 43 2150 4.0 6 129
04 2 144, 145, 146, 147 2150 4.0 6 129
05 3 184, 185, 186, 187 2150 4.0 6 129
==============================================================================
|
domain_1# prtdiag -v
...
==================================== CPUs ====================================
CPU CPU Run L2$ CPU CPU
LSB Chip ID MHz MB Impl. Mask
--- ---- -------------------- ---- --- ----- ----
00 0 0, 1, 2, 3 2150 4.0 6 129
09 1 296, 297, 298, 299 2150 4.0 6 129
06 2 208, 209, 210, 211 2150 4.0 6 129
07 3 248, 249, 250, 251 2150 4.0 6 129
==============================================================================
|
I/O Device Mapping
I/O device paths are dictated by which LSB the I/O
unit is assigned to.
Entry-level servers have one I/O controller. The XSB is assigned four PCIe slots.
Midrange servers have only one I/O controller on the I/O unit (IOU). For an
XSB in Uni-XSB mode, all I/O is on XSB#
xx-0. For an XSB in Quad-XSB mode, internal resources, the PCI-X slot, and two PCIe slots are on XSB#
xx-0, and two PCIe slots are on XSB#
xx-1.
High-end servers have two I/O controllers; therefore, each XSB can have two
PCIe slots assigned to it.
TABLE A-2 shows the LSB numbers and the corresponding device path values that are used in I/O device mapping on the server.
TABLE A-2 LSB Numbers and Device Path Values
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I/O Device Mapping on Entry-Level Servers
TABLE A-3 shows the device mapping on an entry-level server.
TABLE A-3 I/O Device Mapping on an Entry-level Server
|
|
Host Bus Adapter Slot Type
|
OpenBoot PROM Device Path
|
|
|
|
/pci@0,600000/pci@0/pci@8
|
|
|
|
/pci@1,700000/pci@0/pci@0
|
|
|
|
/pci@1,700000/pci@0/pci@8
|
|
|
|
/pci@1,700000/pci@0/pci@9
|
Internal Devices on Entry-Level Servers With SPARC64 VII+ Processors
The entry-level server has a single system board, at location XSB 00-0. Internal devices and device paths are shown in
TABLE A-4.
TABLE A-4 Internal Devices and Device Paths on an Entry-level Server with SPARC64 VII+ Processors
Accessible Internal Devices
|
|
OpenBoot PROM Device Path
|
|
|
|
/pci@0,600000/pci@0/pci@1/network@0
|
|
|
|
/pci@0,600000/pci@0/pci@1/network@0,1
|
|
|
|
/pci@0,600000/pci@0/pci@2/network@0
|
|
|
|
/pci@0,600000/pci@0/pci@2/network@0,1
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@0
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@1
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@2
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@3
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@4
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/ xx@5,z, where xx is the disk when connecting to a disk, or a tape when connecting to a tape drive unit.
|
Internal Devices on Entry-Level Servers Without SPARC64 VII+ Processors
The entry-level server has a single system board, at location XSB 00-0. Internal devices and device paths are shown in
TABLE A-5
TABLE A-5 Internal Devices and Device Paths on an Entry-level Server without SPARC64 VII+ Processors
Accessible Internal Devices
|
|
OpenBoot PROM Device Path
|
|
|
|
/pci@0,600000/pci@0/pci@1/pci@0/network@4
|
|
|
|
/pci@0,600000/pci@0/pci@1/pci@0/network@4,1
|
|
|
|
/pci@0,600000/pci@0/pci@2/pci@0/network@4
|
|
|
|
/pci@0,600000/pci@0/pci@2/pci@0/network@4,1
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@0
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@1
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@2
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@3
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/disk@4
|
|
|
|
/pci@0,600000/pci@0/pci@0/scsi@0/ xx@5,z, where xx is the disk when connecting to a disk, or a tape when connecting to a tape drive unit.
|
I/O Device Mapping on Midrange Servers
TABLE A-6 shows the device mapping on a midrange server. In the device path,
x is LSB-dependent, and is assigned a value as shown in
TABLE A-2.
TABLE A-6 I/O Device Mapping on a Midrange Server
|
|
Host Bus Adapter Slot Type
|
OpenBoot PROM Device Path
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0,1
|
|
|
|
/pci@ x0,600000/pci@0/pci@9
|
|
|
|
|
|
|
|
|
|
|
|
|
Internal Devices on Midrange Servers
The internal
midrange server devices, which are located at the XSB location 00-0 or
01-0 (regardless of Uni-XSB or Quad-XSB mode), are shown in
TABLE A-7 and
TABLE A-8. In the device path,
x is LSB-dependent, and is assigned a value as shown in
TABLE A-2.
TABLE A-7 Internal Devices and Device Paths on the Midrange Servers, IOU#0
XSB 00-0/IOU 0 Accessible Internal Devices (M4000/M5000)
|
|
OpenBoot PROM Device Path
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/network@2
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/network@2,1
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/disk@1
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/disk@3
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/tape@2
|
TABLE A-8 Internal Devices and Device Paths on the M5000 (but not M4000) Server, IOU#1
XSB 01-0/IOU 1 Accessible Internal Device (M5000)
|
|
OpenBoot PROM Device Path
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/network@2
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/network@2,1
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0
|
|
|
|
/pci@ x0,600000/pci@0/pci@8/pci@0/scsi@1/disk@1
|
I/O Device Mapping on High-End Servers
TABLE A-9 shows the device mapping on a high-end server. In the PCIe device path,
x is LSB-dependent, and is assigned a value as shown in
TABLE A-2.
xx is the XSB number and is in the range from 00-15.
TABLE A-9 I/O Device Mapping on a High-end Server
|
|
|
|
OpenBoot PROM PCIe Device Path
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Internal Devices on High-End Servers
The IOUA is a
PCIe Host Bus Adapter that provides access to internal devices when
installed at specific locations. The IOUA contains two 1Gb Ethernet
ports on the card (“on-board”). When the IOUA is installed at specific
locations, it also provides access to storage located on the IOU, as
well as platform CD-RW/DVD-RW drive or tape drive resources at the
locations shown in
TABLE A-10. In the PCIe device path,
x is LSB-dependent, and is assigned a value as shown in
TABLE A-2.
xx is the XSB number and is in the range from 00-15.
nn
is the number associated with the PSB to which the CD-RW/DVD-RW drive
or tape drive is attached, as further explained in the table footnote.
TABLE A-10 Internal Devices and Device Paths on a High-end Server
|
|
|
|
OpenBoot PROM PCIe Device Path
|
OpenBoot PROM IOUA HBA On-board, IOU, and Platform Accessible Devices
|
|
|
|
|
|
.../pci@0,1/network@1 (IOUA HBA On-board BGE Port 0)
.../pci@0,1/network@1,1 (IOUA HBA On-board BGE Port 1)
.../pci@0/scsi@1/disk@0 (IOU HD0; SCSI Target 0)
.../pci@0/scsi@1/disk@1 (IOU HD1; SCSI Target 1)
.../pci@0/scsi@1/disk@4 (Platform CD-RW/DVD-RW at cfgdevice port
.../pci@0/scsi@1/tape@5 (Platform tape at cfgdevice port nn-0;
|
|
|
|
|
|
|
|
|
|
|
|
.../pci@0,1/network@1 (IOUA HBA On-board BGE Port 0)
.../pci@0,1/network@1,1 (IOUA HBA On-board BGE Port 1)
.../pci@0/scsi@1/disk@4 (Platform CD-RW/DVD-RW at cfgdevice port
.../pci@0/scsi@1/tape@5 (Platform tape at cfgdevice port nn-2;
|
|
|
|
|
|
|
|
|
|
|
|
.../pci@0,1/network@1 (IOUA HBA On-board BGE Port 0)
.../pci@0,1/network@1,1 (IOUA HBA On-board BGE Port 1)
.../pci@0/scsi@1/disk@0 (IOU HD2; SCSI Target 0)
.../pci@0/scsi@1/disk@1 (IOU HD3; SCSI Target 1)
.../pci@0/scsi@1/disk@4 (Platform CD-RW/DVD-RW at cfgdevice port
.../pci@0/scsi@1/tape@5 (Platform tape at cfgdevice port nn-4;
|
|
|
|
|
|
|
|
|
|
|
|
.../pci@0,1/network@1 (IOUA HBA On-board BGE Port 0)
.../pci@0,1/network@1,1 (IOUA HBA On-board BGE Port 1)
.../pci@0/scsi@1/disk@4 (Platform CD-RW/DVD-RW at cfgdevice port
.../pci@0/scsi@1/tape@5 (Platform tape at cfgdevice port nn-6;
|
|
|
|
|
|
|
Sample cfgadm Output
- Sample output for the command cfgadm -s “select=class(pci)” on an unpopulated server. As you connect devices, the cfgadm output will change to reflect the device type and connection status on your server.
- The device
matrix for midrange and for high-end servers, when the IOU is configured
as part of a domain. I/O portions of the IOU resources may be in
different domains.
Entry-Level Server
The
entry-level server does not support PCI hotplug. Therefore, the concepts
of attachment points and classes do not apply, and executing the
command
cfgadm -s "select=class(pci)"
either would produce an error or display nothing.
Midrange Servers
M4000 Server sample output:
# cfgadm -s "select=class(pci)"
Ap_Id Type Receptacle Occupant Condition
iou#0-pci#0 unknown empty unconfigured unknown
iou#0-pci#1 unknown empty unconfigured unknown
iou#0-pci#2 unknown empty unconfigured unknown
iou#0-pci#3 unknown empty unconfigured unknown
iou#0-pci#4 unknown empty unconfigured unknown
|
M5000 Server sample output:
# cfgadm -s "select=class(pci)"
Ap_Id Type Receptacle Occupant Condition
iou#0-pci#0 unknown empty unconfigured unknown
iou#0-pci#1 unknown empty unconfigured unknown
iou#0-pci#2 unknown empty unconfigured unknown
iou#0-pci#3 unknown empty unconfigured unknown
iou#0-pci#4 unknown empty unconfigured unknown
iou#1-pci#0 unknown empty unconfigured unknown
iou#1-pci#1 unknown empty unconfigured unknown
iou#1-pci#2 unknown empty unconfigured unknown
iou#1-pci#3 unknown empty unconfigured unknown
iou#1-pci#4 unknown empty unconfigured unknown
|
TABLE A-11 cfgadm Device Matrix for Midrange Servers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
High-End Servers
M8000 Server sample output:
# cfgadm -s "select=class(pci)"
Ap_Id Type Receptacle Occupant Condition
iou#1-pci#0 unknown empty unconfigured unknown
iou#1-pci#1 unknown empty unconfigured unknown
iou#1-pci#4 unknown empty unconfigured unknown
iou#1-pci#5 unknown empty unconfigured unknown
iou#1-pci#6 unknown empty unconfigured unknown
iou#1-pci#7 unknown empty unconfigured unknown
|
M9000 Server sample output:
# cfgadm -s "select=class(pci)"
Ap_Id Type Receptacle Occupant Condition
iou#0-pci#0 unknown empty unconfigured unknown
iou#0-pci#1 unknown empty unconfigured unknown
iou#0-pci#2 unknown empty unconfigured unknown
iou#0-pci#3 unknown empty unconfigured unknown
iou#0-pci#4 unknown empty unconfigured unknown
iou#0-pci#5 unknown empty unconfigured unknown
iou#0-pci#6 unknown empty unconfigured unknown
iou#0-pci#7 unknown empty unconfigured unknown
iou#3-pci#0 unknown empty unconfigured unknown
iou#3-pci#1 unknown empty unconfigured unknown
iou#3-pci#2 unknown empty unconfigured unknown
iou#3-pci#3 unknown empty unconfigured unknown
|
TABLE A-12 cfgadm Device Matrix for High-End Servers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
