Sun Fire[TM] V1280, E2900, Netra[TM] 1280, and 1290: PCI I/O probe order

Asset ID:	1-71-1010550.1
Update Date:	2017-02-02
Keywords:

Solution Type Technical Instruction Sure

Solution 1010550.1 : Sun Fire[TM] V1280, E2900, Netra[TM] 1280, and 1290: PCI I/O probe order

Applies to:

Sun Netra 1280 Server - Version Not Applicable and later
Sun Fire V1280 Server - Version Not Applicable and later
Sun Fire E2900 Server - Version Not Applicable and later
Sun Netra 1290 Server - Version Not Applicable and later
All Platforms

Goal

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.

This document lists the I/O probe order for Sun Fire[TM] V1280, E2900, Netra[TM] 1280, and 1290.

Solution

The list below shows the probe order for Sun Fire 1280 servers:

PCI slot 0	pci@18,700000 Device 1
PCI slot 1	pci@18,700000 Device 2
INT IDE	pci@18,700000 Device 3
PCI slot 5	pci@18,600000 Device 1
INT SCSI	pci@18,600000 Device 2
PCI slot 2	pci@19,700000 Device 1
PCI slot 3	pci@19,700000 Device 2
PCI slot 4	pci@19,700000 Device 3
INT GBE (NET0)	pci@19,600000 Device 1
INT GBE (NET1)	pci@19,600000 Device 2

Physical Device Mapping for Sun Fire V1280/E2900 PCI+/PCI-X 6-Slot I/O Boards : refer to Document 1007870.1

The list below shows the probe order for Netra[TM] 1290 servers (additional reference see Document 1005907.1) for IB_SSC Assembly PCI+/PCI-X Device Mapping :
I/O Assembly Name : IB6

Device Path	Physical Slot Number	I/O Controller Number	Bus
/ssm@0,0/pci@18,700000/*@1	0	0	B
/ssm@0,0/pci@18,700000/*@2	1	0	B
/ssm@0,0/pci@18,700000/*@3	X	0	B
/ssm@0,0/pci@18,600000/*@1	5	0	A
/ssm@0,0/pci@18,600000/*@2	W	0	A
/ssm@0,0/pci@19,700000/*@1	2	1	B
/ssm@0,0/pci@19,700000/*@2	3	1	B
/ssm@0,0/pci@19,700000/*@3	4	1	B
/ssm@0,0/pci@19,600000/*@1	Y	1	A
/ssm@0,0/pci@19,600000/*@2	Z	1	A

where:

W is the onboard LSI1010R SCSI controller
X is the onboard CMD646U2 EIDE controller
Y is the onboard Gigaswift Ethernet controller 0
Z is the onboard Gigaswift Ethernet controller 1
* is dependent upon the type of PCI card installed in the slot.

Note the following:

600000 is the bus offset and indicates bus A, which operates at 66 MHz.
700000 is the bus offset and indicates bus B, which operates at 33 MHz for PCI+ and at 33/66MHz for PCI-X.
*@3 is the device number. In this example @3 means it is the third device on the bus.

This can be an issue if systems are rebuilt/reloaded, and the I/O configuration differs from the initial build, as the device instance numbers will change as a result of the probe order.

For Example:

The systems come preloaded with Solaris[TM] Operating System(OS), so the onboard devices will be numbered as follows:

INT IDE -> c0
INT SCSI -> c1
NET0 -> ce0
NET1 -> ce1

If a SCSI PCI card is installed in slot 0 or 1, and the system is reloaded/rebuilt, then the onboard IDE and SCSI will become c1 and c2 respectively, and the PCI card will be c0.

If a SCSI PCI card is installed in slot 5, and the system is reloaded/rebuilt, then the onboard IDE will remain as c0, and the PCI card will become c1, making the onboard SCSI c2.

Similarly, if a Cassini based network card is installed in ANY PCI slot, and the system is reloaded/rebuilt, then the onboard NET0 & NET1
ports will no longer be ce0 & ce1, but will get renumbered, depending on the number of other ports that will now be probed first.

NOTE: This ONLY applies if Solaris OS is reloaded, or the system is installed using JumpStart[TM] software, that is, Solaris OS is re-installed.

If PCI cards are added to an existing configuration, and the normal methods of creating device entries are used(devfsadm, boot -r, etc), then the original device numbering will be retained.

Attachments

This solution has no attachment