I had queried the list regarding the PCI bus probe order on the DS20 :
Dr. Tom Blinn came through once again with :
The order in which PCI option slots are probed on the DS20 is as
follows:
(Modified from Dr. Blinn's original in order to reflect the
 physical layout of the slots on the mainboard)
        PCI Hose 0  Slot 0 (J35 - IDSEL 7) Priority 4
        PCI Hose 0  Slot 1 (J40 - IDSEL 8) Priority 5
        PCI Hose 0  Slot 2 (J41 - IDSEL 9) Priority 6 (Lowest)
        PCI Hose 1  Slot 0 (J42 - IDSEL 7) Priority 1 (Highest)
        PCI Hose 1  Slot 1 (J44 - IDSEL 8) Priority 2
        PCI Hose 1  Slot 2 (J46 - IDSEL 9) Priority 3
What this means is that when populating the DS20 with SCSI controllers, the
drives attached to the controller in J42 will
have the lowest rz id's, J44 will be the next highest and so on.
If you add a new controller to the system at a higher priority
than the existing controllers, all disks on controllers at lower
priority will change rz id's. This can be especially troublesome
when the boot disk or disks under LSM control change id's.
There are several methods of solving the problem. Careful attention to bus
priority when adding new controllers will avoid many problems. There are
times, though, when the new configuration results in priority changes no
matter what order the controllers are installed in. In this case, the
options are :
        1. Swap SCSI cables if controller types are compatible
        2. Modify the kernel configuration file to preserve the
             scsiN naming of the original controller entries.
        3. Fix the disk names in the OS configuration and LSM data
                fstab, rc.config, swapdefault, fdmns domain links
                LSM sysconfigtab rootvol/swapvol, if used
                Change LSM disk name references.
The instructions for changing LSM disk name references are found in the
Trucluster Software Installation Guide, chapter 3, section 3.7.3,
"Changing References to Renumbered Devices in System Files".
http://www.unix.digital.com/faqs/publications/cluster_doc/cluster_15/TCR_INS
T/CHPFLLNS.HTM#sect-full-change-file-refs
An example of modifying the kernel file :
Original configuration :
bus             ata0       at pci0      slot  105
controller      scsi1      at ata0      slot  0
bus             pci2000    at pci0      slot  7
bus             itpsa0     at pci2000   slot  0 vector    itpsaintr
controller      scsi2      at itpsa0    slot  0
bus             itpsa1     at pci2000   slot  1 vector    itpsaintr
controller      scsi3      at itpsa1    slot  0
Configuration after adding new SCSI adapter at highest priority :
bus             ata0       at pci0      slot  105
controller      scsi1      at ata0      slot  0
bus             ata1       at pci0      slot  205
controller      scsi2      at ata1      slot  0
bus             pci2000    at pci0      slot  7
bus             itpsa0     at pci2000   slot  0 vector    itpsaintr
controller      scsi3      at itpsa0    slot  0
bus             itpsa1     at pci2000   slot  1 vector    itpsaintr
controller      scsi4      at itpsa1    slot  0
Fixed configuration :
bus             ata0       at pci0      slot  105
controller      scsi1      at ata0      slot  0
bus             ata1       at pci0      slot  205
controller      scsi4      at ata1      slot  0
bus             pci2000    at pci0      slot  7
bus             itpsa0     at pci2000   slot  0 vector    itpsaintr
controller      scsi2      at itpsa0    slot  0
bus             itpsa1     at pci2000   slot  1 vector    itpsaintr
controller      scsi3      at itpsa1    slot  0
Alan Davis
Tru64 Unix Consultant
Received on Tue Mar 02 1999 - 20:41:40 NZDT