Sun Fire V480 Server
 
Sun Fire V490 Server
 

GCS>Sun Microsystems>Servers>Entry-Level Servers
 

NOTE: Plugging a 33MHz PCI card into a 66MHz slot (slots 0 & 1) will degrade the entire 66MHz PCI bus to 33MHz.

PCI Probe Order - Order in which Solaris[TM] builds Devices

The way the controller id's are assigned comes directly from the way the PCI buses are numbered. In V480/V490 we have two Schizos at Safari addresses 8 and 9. Each Schizo has 2 PCI buses at local Schizo addresses 600000 and 700000. This gives a total of four PCI buses with the following instances of the Schizo ("pcisch") driver in the  /etc/path_to_inst  file:

   /pci@8,600000   "A"   (66 MHz) bus on Schizo 0   ("pcisch"  instance 1)

   /pci@8,700000   "B"   (33 MHz) bus on Schizo 0   ("pcisch"  instance 0)

   /pci@9,600000   "C"   (66 MHz) bus on Schizo 1   ("pcisch"  instance 3)

   /pci@9,700000   "D"   (33 MHz) bus on Schizo 1   ("pcisch"  instance 2)

Solaris[TM] walks through the device tree looking for things that have block ("disk-type") devices (where a disk can be a HDD, a CDROM, etc., independent of the bus type - scsi/ide/fcal). When it finds a disk-type device, it knows it has found a controller too. It assigns the controller IDs in the order it finds them, so for the Sun Fire V480 and Sun Fire V490, it finds them in the order listed below.

PCI probe list (device build order):

   /pci@8,700000/<device>@2     (bus B, PCI slot 2, 33 MHz)

   /pci@8,700000/<device>@3     (bus B, PCI slot 3, 33 MHz)

   /pci@8,700000/<device>@4     (bus B, PCI slot 4, 33 MHz)

   /pci@8,700000/<device>@5     (bus B, PCI slot 5, 33  MHz)

   /pci@8,700000/ide@6               (bus B, onboard IDE, DVD-ROM)

   /pci@8,600000/<device>@1     (bus A, PCI slot 0, 66 MHz)

   /pci@8,600000/<device>@2     (bus A, PCI slot 1, 66 MHz)

   /pci@9,700000/ebus@1             (bus D, serial, pmc, rsc, etc.)

   /pci@9,700000/usb@1,3            (bus D, USB ports)

   /pci@9,700000/network@2        (bus D, ce0, net0, onboard 10/100/1000 cassini Ethernet interface)

   /pci@9,600000/network@1        (bus C, ce1, net1, onboard 10/100/1000 cassini Ethernet interface)

   /pci@9,600000/SUNW,qlc@2    (bus C, onboard FC-AL, ISP2200)  

The provided probe-order of the buses in this document should only be used as reference for assisting the field troubleshooting. We cannot guarantee what the probe-order will be from system to system. The Solaris probe is done bus-by-bus (in the above order) and assigned by specific Solaris instance at the time of installation. After initial Solaris install, it is incrementally updated as devices are added or removed, populating that information into the  /etc/path_to_inst  file. Things may be different when booting single-user off cdrom or network, since this is equivalent to a new, specific instance of Solaris, different from the disk instance normally compared to.

The order devices come up in, as well as the device path is affected by various device specifics, such as whether or not PCI bridges or multiple bridges are in between the device and the PCI bus controller. In the example below  pci@2  indicates a bridge chip on the PCI bus A with the network device sitting behind it (the output in the example is from '/etc/path_to_inst'):

   "/pci@8,600000/pci@2" 0 "pci_pci"

   "/pci@8,600000/pci@2/network@0" 0 "ce"

When there is no PCI instance in the device path (/pci@8,600000/SUNW,qlc@1) this indicates that there is no such bridge on the card, and the device is connected directly to the bus. It is common in recent designs to put multiple devices behind bridge chips:

   "/pci@8,600000/pci@1/SUNW,qlc@4" 0 "qlc"

   "/pci@8,600000/pci@1/SUNW,qlc@5" 1 "qlc"

This example shows 2 qlc devices, behind the PCI bridge  pci@1  on the dual-port Crystal+  card (X6727A) installed in slot 0 (reference the appendix: device tree).

PCI Slot Map

Two of the PCI buses are on the V480/V490 I/O board (PCI Riser). The PCI bus (A) has 2 slots, and is capable of running at either 33MHz or 66MHz. The other bus (B) has 4 slots, and runs at 33MHz. The operation on one PCI bus does not affect what happens on the other bus. These two buses come from one Schizo (Schizo 0) at Safari ID 8, so the buses are /pci@8,600000 and /pci@8,700000.

Whenever a 33MHz PCI card is present on a 66MHz PCI bus, that bus (and only that bus) will  run at 33MHz. Note that this limitation is the normal, specified behavior of the PCI bus, and is not restricted to V480/V490 or Sun systems in general.

The other two PCI buses (for a total of 4) in V480 and V490 come from the second  Schizo (Schizo 1) at Safari ID 9, so the buses are pci@9,60000 and pci@9,700000. These buses are used ONLY on the centerplane, for the on-board devices, such as Ethernet (cassini) and Fibre Channel controllers. They do not have any plug-in slots on them, and do not connect to the I/O Riser board at all.

Shown below is the PCI slot map:

Schizo 0   /pci@8,600000   PCI bus A (66 MHz/3.3V)   (plug-in, slots 0,1)

Schizo 0   /pci@8,700000   PCI bus B (33 MHz/5V)      (plug-in, slots 2,3,4,5)

Schizo 1   /pci@9,600000   PCI bus C (66 MHz/3.3V)   (on-board, no PCI slots)

Schizo 1   /pci@9,700000   PCI bus D (33 MHz/5V)      (on-board, no PCI slots)

Shown below is the translation table showing the correspondence between logical PCI devices and physical PCI slots for each bus:

NOTE: The first value in the Safari address 8 denotes Schizo 0, 9 denotes Schizo 1, the second value 6 denotes Schizo A leaf, 7 denotes Schizo B leaf

The following table gives you the relationship between the actual Schizo ASIC revision and the version reported by  /usr/platform/`uname -i`/sbin/prtdiag -v  (in the last section IO ASIC revisions):

It is important to know the Schizo revision since it is related to certain FINs and Sun Alerts. Note that the Sun Fire V480 systems are shipping with Schizo 2.2 and more recently with Schizo 2.5 (the Schizo ASICs are located on the centerplane). The Sun Fire V490 systems are shipping with Schizo 2.5 or ELE  1.1 support.  Note: ELE 1.1 is the same as Schizo 2.5 functionally, except made by a different manufacturer.

Support Matrix (supported PCI cards)

The supported PCI cards are listed (if a card is not listed on the platform page, it is not supported on that platform) in the Sun System Handbook (SSH) pages for Sun Fire V480 and Sun Fire V490

V480 Documentation, including latest product notes

V490 Documentation, including latest product notes 

Appendix: Sun Fire V480/V490 PCI device tree

    Refer to Figure 1.

NIC Configuration Matrix 

A useful configuration matrix for Storage HBAs on different
platforms:

Storage HBA Matrix

More details about the Sun Fire V480 and Sun Fire V490 PCI buses
and configuration can be found at:

Sun Fire V480 Troubleshooting page

The Sun Fire V480/V490 Just-the-Facts and a useful I/O
compatibility matrix are available after you log in at: http://sundoc.central.sun.com/Dmlogin.jsp :

Sun Fire V480 Server Just-the-Facts (JTF), SunWIN# 333632

Sun Fire V490 Server Just-the Facts (JTF), SunWIN# 417865

SSG I/O Compatibility Matrix (SPARC servers), SunWIN# 428642

This solution has no attachment