Sun SPARC Enterprise M9000-64 Server
 
Sun SPARC Enterprise M9000-32 Server
 
Sun SPARC Enterprise M8000 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Mx000
 
_Old GCS Categories>Sun Microsystems>Servers>OPL Servers
 

Applies to:

Goal

Description
The intent of this document is to provide the reader with an overview of how the Sun SPARC Enterprise(R) M8000 and M9000 device paths are arranged.

Solution

Steps to Follow
There are two important factors that impact how the Sun SPARC Enterprise M8000 and Sun SPARC Enterprise M9000-32 and Sun SPARC Enterprise M9000-64 device paths are arranged: the I/O architecture and the assignmentof the Logical System Board (LSB).

When allocating resources to a domain through the Domain Control List (DCL), the OPL equivalent of an access control list, these resources are also assigned to a Logical System Board (LSB).  More information on LSB's can be found in Technical Instruction Document: 1011446.1 Sun SPARC Enterprise Mx000 Servers: Logical System Board (LSB).   

In addition, the Sun SPARC  Enterprise M8000 and M9000 provides an optional  IOUA  PCIe HBA which when installed into PCIe slots 0, 2, 4, or 6 provides access to two onboard 10/100/1000 HDX/FDX ethernet ports as well as connections to additional internal devices, such as the hard disks located on the IOU, and the platform's DVD/CDROM and DAT devices, depending on where the IOUA is installed.  Note that access to the IOU's hard disks and platform DVD and DAT is only possible through an IOUA PCIe HBA.  Also, installing the IOUA in slots 1, 3, 5, and 7 is not supported.

The following is a graphical representation of the Sun SPARC  Enterprise M8000 and M9000 IOU device path layout, which also shows the additional devices accessible when installing the optional IOUA (where the IOUA connected devices are shown in italics):

|----- /pci@[LSB1]0,600000 (PCIe Slot 0)

     |-- .../pci@0,1 (IOUA base network device path)

          |-- .../network@1 (IOUA onboard network port)

          |-- .../network@1,1 (IOUA onboard network port)

     |-- .../pci@0/scsi@1 (IOUA base SCSI device path)

          |-- .../disk@0 (IOU HD0)

          |-- .../disk@1 (IOU HD1)

          |-- .../disk@4 (Plat. DVD/CDROM -  cfgdevice port PSB-0)

          |-- .../tape@5 (Plat. DAT  -  cfgdevice port PSB-0)

|----- /pci@[LSB1]1,700000 (PCIe Slot 1)

|----- /pci@[LSB2]2,600000 (PCIe Slot 2)

     |-- .../pci@0,1 (IOUA base network device path)

          |-- .../network@1 (IOUA onboard network port)

          |-- .../network@1,1 (IOUA onboard network port)

     |-- .../pci@0/scsi@1 (IOUA base SCSI device path)

          |-- .../disk@4 (Plat. DVD/CDROM - cfgdevice port PSB-2)

          |-- .../tape@5 (Plat. DAT - cfgdevice port PSB-2)

|----- /pci@[LSB2]3,700000 (PCIe Slot 3)

 |----- /pci@[LSB3]4,600000 (PCIe Slot 4)

     |-- .../pci@0,1 (IOUA base network device path)

          |-- .../network@1 (IOUA onboard network port)

          |-- .../network@1,1 (IOUA onboard network port)

     |-- .../pci@0/scsi@1 (IOUA base SCSI device path)

          |-- .../disk@0 (IOU HD2)

          |-- .../disk@1 (IOU HD3)

          |-- .../disk@4 (Plat. DVD/CDROM - cfgdevice port PSB-4)

          |-- .../tape@5 (Plat. DAT -  cfgdevice port PSB-4)

|----- /pci@[LSB3]5,700000 (PCIe Slot 5)

|----- /pci@[LSB4]6,600000 (PCIe Slot 6)

     |-- .../pci@0,1 (IOUA base network device path)

          |-- .../network@1 (IOUA onboard network port)

          |-- .../network@1,1 (IOUA onboard network port)

     |-- .../pci@0/scsi@1 (IOUA base SCSI device path)

          |-- .../disk@4 (Plat. DVD/CDROM -  cfgdevice port PSB-6)

          |-- .../tape@5 (Plat. DAT -  cfgdevice port PSB-6)

|----- /pci@[LSB4]7,700000 (PCIe Slot 7)

Note:  When the Physical System Board (PSB) is in UniMode, [LSB1] through [LSB4] will all have the same value.  When in QuadMode, [LSB1] through [LSB4] will not be the same value when the resources are in the same domain.  It is possible however that when in QuadMode, there could be the equivalent values for [LSB1] through [LSB4] when the resources are in different domains.

In addition, on the Sun SPARC  Enterprise M8000 and Sun SPARC  Enterprise M9000-32 since there is only one DVD/CDROM as well as only one DAT in the system, these resources are allocated to a Physical System Board (PSB) at a particular location (called a  port ) using the XSCF  cfgdevice  command.  Note that the Sun SPARC  Enterprise M9000-64 actually contains up to two DVD/CDROM devices and two DAT drives.  In this case the DVD/CDROM and the DAT must be assigned to a PSB and port that physically resides in the same chassis as the DVD/CDROM and DAT devices.  However once they are assigned to a PSB and port on the same chassis, they can be used by the entire domain that contains the PSB and port where the DVD/CDROM and DAT have been assigned, even if that domain contains XSB resources than spans both base cabinets.

The following table represents the same device path information shown above presented in a table format:

Note:  Devices shown in italics are devices that are accessed through the IOUA PCIe HBA.

Lastly, a significant piece of  understanding the complete device path is knowing which LSB the XSB resource has been assigned.  Assigning a XSB resource to a specific DCL has the following impact on device path numbering (ie.  [LSB1] ,   [LSB2] ,  [LSB3] , and  [LSB4]):

A quick method to look up the location of a PCI device is to cross reference the device path to the output of "fmtopo -V".

Device path information for the  Sun SPARC  Enterprise M4000 and M5000 are contained in Technical Instruction Document: 1002807.1 Sun SPARC Enterprise M4000 & M5000 Server Device Paths.      Device path information for the External I/O Expansion Unit are contained in Technical Instruction Document: 1005332.1Sun SPARC External I/O Expansion Unit Device Paths.

Actual device paths may be seen using some of the following methods:

    OBP:   show-devs  command

    Solaris:  /etc/path_to_inst  file

    Solaris:   prtpicl  command

    Solaris:   prtdiag -v  command

This solution has no attachment