Configuration A, Proliant Ml530 - Compaq 108164-003 - ProLiant - 800 Integration Notes

PCI Bus Numbering in a Microsoft Windows NT Environment
Configuration A, ProLiant ML530 (highly parallel architecture), a two configuration scenario:
This scenario walks through a simple Windows NT configuration and shows how the bus
numbers change when you add a new controller to the server. Two tables with a side bar
description of what the PCI BIOS does during the discovery process illustrate the configurations.
Configuration B, ProLiant 8000 (triple-peer architecture), a more complex two configuration
scenario: We modified the server to include additional disk and network controllers. Two tables
with a side bar description of what the PCI BIOS does during the discovery process illustrate the
configurations.
Configuration C, ProLiant DL580 (triple-peer architecture), another more complex scenario:
This demonstrates the slot ordering difference when additional network controllers are inserted
out of order in the configuration. Two tables with a side bar description of what the PCI BIOS
does during the discovery process illustrate the configurations.

Configuration A, ProLiant ML530

All the controllers included in this configuration were installed in the server before Windows NT
was loaded on the system. Windows NT detected network controllers in the original configuration
during the installation process. However, when the configuration is modified in Test 2, PCI bus
renumbering does occur.
Configuration A: Test 1 – Initial Configuration
This bus number and controller discovery test was performed on a simple configuration in a dual-
peer PCI ProLiant ML530 server. This configuration is described as simple because it contains one
non-bridged PCI network controller and one bridged PCI network controller (see the results in
Table 6).
13UK-1200A-WWEN
20