Sun Fire[TM] 12K, 15K, E20K, and E25K: Determining slot numbers from I/O device paths

Asset ID:	1-71-1001879.1
Update Date:	2011-04-19
Keywords:

Solution Type Technical Instruction Sure

Solution 1001879.1 : Sun Fire[TM] 12K, 15K, E20K, and E25K: Determining slot numbers from I/O device paths

Applies to:

Sun Fire 12K Server
Sun Fire 15K Server
Sun Fire E20K Server
Sun Fire E25K Server
All Platforms

Goal

This document describes how to decode a Solaris[TM] Operating System device path to a physical location or slot, in an I/O board on a Sun Fire[TM] 12K/15K/E20K/E25K platform.

Solution

Here is an example of an I/O device path as reported by Solaris OS:

/pci@5c,700000/pci@1/SUNW, isptwo@4/sd@5,0
/\ /\ /\
Agent ID Offset Slot

The "5c" represents an Agent ID. Agent IDs will always end in a "c" or a "d".A "c" represents IOC 0, while "d" represents IOC 1.
700000 represents the Offset. Each IOC supports two PCI buses, an 'A' and a 'B' bus. Bus A is represented by an Offset of 600000, while Bus B is represented by an Offset of 700000.
"pci@1" represents the Slot Number. The slot number on a SF15K will always be pci@1.

So, to map the Solaris device path to a physical location, take the following steps:

Determine the Agent ID, and map that ID to a Expander and IOC. Here is the Agent ID Table. Using this table, we can determine from the Agent ID which expander and which IOC the device is located on. In the table below, the Agent ID is outside of the parenthesis (also known as the hexadecimal number), while the number in the parenthesis is the decimal IOC number:

Expander Number	IOC 0	IOC 1
0	1c (28)	1d (29)
1	3c (60)	3d (61)
2	5c (92)	5d (93)
3	7c (124)	7d (125)
4	9c (156)	9d (157)
5	bc (188)	bd (189)
6	dc (220)	dd (221)
7	fc (252)	fd (253)
8	11c (284)	11d (285)
9	13c (316)	13d (317)
10	15c (348)	15d (349)
11	17c (380)	17d (381)
12	19c (412)	19d (413)
13	1bc (444)	1bd (445)
14	1dc (476)	1dd (477)
15	1fc (508)	1fd (509)
16	21c (540)	21d (541)
17	23c (572)	23d (573)

Use the "Offset" in addition to the IOC determined in step 1 to map the device path to a specific slot number/location. Using the table below, the offset can be matched to the specific slot:

Slot

IOC

Offset

0

0

600000

1

0

700000

2

1

600000

3

1

700000
Put steps 1 and 2 together and identify the slot location: Step 1 produces a Expander number and IOC number, while Step 2 produces the physical slot location, based on the Offset number and IOC from step 1.

Below is a diagram of the I/O board, labeling the IO slots:

           ____________
          |     |     |
          |     |     |
          | slot|slot |   <--- This is IOC Bus "B".
          |   3 |  1  |
          |     |     |
          |     |     |
          |-----|-----|
          |     |     |
          |     |     |
          | slot|slot |   <--- This is IOC Bus "A".
          |   2 |  0  |
          |     |     |
          |_____|_____|

Example:

/pci@11d,600000/pci@1/SUNW...

11d is the Agent ID. Using the table in step 1, 11d maps to Expander 8, IOC 1.

In step 2, the offset is 600000. Using the step 2 table, an offset of 600000 with an IOC of 1 maps to slot 2.

Finally, referencing the slot diagrams, this device path equates to a card located on EXB 8, slot 2, the bottom left IO slot on the board.

Warning: the hsPCI+ IO-board has an extra PCI bridge-chip to get to slot1.
See Document 1006575.1 for details on what this means for your device path.

References:
Document 1017493.1 Sun Fire[TM] 12K/15K/E20K/E25K: Cheat Sheet: hsPCI and hsPCI+ Cartridge Locations
Document 1006575.1 After upgrading hsPCI to hsPCI+ domain fails to boot

Product
Sun Fire 15K Server
Sun Fire 12K Server
Sun Fire E25K Server
Sun Fire E20K Server

Internal section

See the Systems TSC Starcat Product Pages for additional information.

Keywords: hsPCI, hsPCI+, upgrade, starcat, IO, I/O, IO Board, device path, decode, device decode, slot, IO slot, I/O slot

Previously Published As 54540

Attachments

This solution has no attachment