HP ProLiant 2000 PCI Bus Numbering in a Microsoft Windows NT Environment
HP ProLiant 2000 Manual
View all HP ProLiant 2000 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP ProLiant 2000 manual content summary:
- HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 1
Step-By-Step Review 19 PCI Test Configurations with ProLiant Servers 19 Configuration A, ProLiant ML530 20 Configuration B, ProLiant 8000 23 Configuration C, ProLiant DL580 29 Compaq Support Software and Utilities 36 Additional Troubleshooting Tips 39 Summary 40 Appendices A-D 41 PCI Bus - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 2
Windows NT Environment 2 Notice ©2000 Compaq Computer Corporation. Compaq, the Compaq logo, NetFlex, ProLiant, and SmartStart are registered United States Patent and Trademark Office. SoftPaq is a trademark and/or service mark of Compaq Computer Corporation. Netelligent is a trademark and - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 3
SIG activities and reviews formal recommendations for changes to PCI Specification(s). Compaq is a member of the SIG Steering Committee and actively proposes and pace to meet customer's business requirements. Server technology includes equipment, such as the ProLiant 8000 with multiple PCI buses. The - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 4
buses to deliver optimized multiprocessing support to deliver increased system throughput and bus is bridged off another PCI bus (i.e., in series). Peer-to-Peer PCI Buses Primary Bus Secondary Bus architecture operating with three PCI buses on a single server is referred to as a Triple-Peer PCI Bus - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 5
a system while the system is running and replace them with equivalent PCI controllers, without removing power to the server and without reconfiguring or reloading software support. *Hot Upgrade The ability to upgrade existing PCI controllers and drivers to next generation controllers and drivers - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 6
Peer PCI Bus architecture (see Figure 3). The Compaq servers discussed in this white paper and used in the PCI architecture system designs. Refer to the "Compaq Server and Option Hardware" section of this white 32-Bit PCI Slots Server Feature Card in 32-bit PCI slot Figure 1. Dual-peer PCI - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 7
ML530 Figure 3. Triple-peer PCI bus architecture in the ProLiant 8000 PCI bridges are not limited to the computer system; controllers can include them also. Hardware manufactures such as Compaq include PCI bridges on controllers to help with signal integrity, enabling more devices to be added - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 8
BIOS supplies services to the server with the Compaq SmartStart and Support Software CD or from a diskette to update the server server configuration. The manufacturer defines the detection order for each server. Refer to "Table 11. PCI Bus Number Order of Detection Matrix" for Compaq ProLiant servers - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 9
hardware designators. Dual-Peer PCI Bus - The Compaq ProLiant ML350 server, an example of the dual-peer PCI ProLiant ML530 provides an example of highly parallel PCI architecture. This architecture uses dual memory controllers, dual-peer-PCI buses to deliver optimized multiprocessing support - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 10
6 6 6 6 7 6 13 13 14 The "Additional Troubleshooting Tips" section of this document contains a matrix titled "Table 11. PCI Bus Number Order of Detection Matrix". This matrix lists the PCI Bus detection order for several Compaq ProLiant servers. In this scenario, PCI BIOS assigns the Primary Bus as - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 11
the order of detection on the ProLiant 8000 is Primary Host-to-PCI server restarts. However, the bus number assignments in the Windows NT registry can be updated using the appropriate network configuration tool for your controllers. The Compaq TLAN Teaming and Configuration Utility supports Compaq - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 12
Compaq Network Teaming and Configuration Utility supports Compaq 10/100 and Gigabit NICs, discussed in this document. Note: When configuration changes are necessary due to server maintenance or upgrade, Compaq titled "PCI Test Configurations with ProLiant Servers" in this document. Disk Renumbering - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 13
and option hardware used to test PCI bus numbering and slot configurations for this document. Compaq Servers This white paper details the PCI bus numbering scheme of five Compaq ProLiant server models. Note: The features discussed in this section should not be considered a complete description for - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 14
PCI Bus Numbering in a Microsoft Windows NT Environment 14 ProLiant 8000 The ProLiant 8000 has 11 PCI slots: ten 64-Bit slots and one 32-Bit PCI slot (see Figure 4). Primary Bus: Slot 1 is the first PCI slot detected in this server configuration. Bus numbering starts here and continues to slots 2, - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 15
to slots 4, 5, and 6. Secondary Bus: Slots 2 and 3 comprise the Secondary Bus and complete the bus numbering in this server configuration. Figure 6. Slot view of the ProLiant ML350 ProLiant DL580 ProLiant DL580 is a triple-peer bus and is comprised of 6 PCI slots: two 64-Bit/66MHz slots, three 64 - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 16
Primary Bus. Secondary Bus: Slots 2, 3, and 4 complete bus numbering on this server configuration. Figure 8. Slot view of the ProLiant DL380 Option Hardware The following listing in Table 5 identifies the types of Compaq controllers that are categorized as either PCI bridged or non-bridged. Table - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 17
- Most Video Controllers For a complete listing of supported controllers, visit the Compaq website: • Network interface controllers, http://www.compaq.com/products/networking/nics/ • Storage controllers, http://www.compaq.com/products/servers/storage Planning a PCI System Configuration Modifying - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 18
the Compaq Support Paq part of the plan involves identifying the best method to update the original configuration. Armed with the knowledge that PCI slot number and bus number assignments are affected when controllers are added or removed will help you integrate new hardware into an existing server - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 19
to driver enhancements, the Compaq Support Paq installs several important support utilities. The Compaq Support Paq runs a detection process and identifies the software and utilities applicable to the installation. PCI Test Configurations with ProLiant Servers The following scenarios were tested - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 20
. Configuration A: Test 1 - Initial Configuration This bus number and controller discovery test was performed on a simple configuration in a dualpeer PCI ProLiant ML530 server. This configuration is described as simple because it contains one non-bridged PCI network controller and one bridged PCI - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 21
boot process, the number remains exactly the same as long as the configuration remains the same. Table 6. PCI BIOS bus detection in a ProLiant ML530-before adding a bridged controller Bus Detection Order/ Controller Discovery 1st 2nd Slot Number Primary Bus (O) Slot 1 PCI Bridge/ Controller Type - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 22
A - Test 2 - Adding a Device The example in Table 7 illustrates the PCI BIOS discovery and bus number assignment process in the same ProLiant ML530 server. However, the configuration changes slightly by adding a bridged PCI network controller on the Tertiary Bus. Table 7. PCI BIOS bus detection in - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 23
controller in slot 6 are no longer applicable and must be manually reset for this controller to function in the configuration again. Refer to the "Compaq Network and Teaming Configuration Utility" section in this document for instructions on how to reset the bindings. Comparison of Test 1 to - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 24
24 The diagrams in Figure 9 illustrate the location of the expansion slots in the rear of the ProLiant 8000. 12 34 5 6 7 8 9 10 11 Figure 9. Location of expansion slots in the ProLiant 8000 Bus number assignments for controllers with bridged devices are assigned to the device on the controller - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 25
PCI Bus Numbering in a Microsoft Windows NT Environment 25 Table 8. Test 1 - PCI BIOS bus detection in the ProLiant 8000 Bus Detection Order/ Controller Discovery Slot Number PCI Bridge/ Controller Type - Test 1 Bus Number Assignment 1st Primary Host to PCI Bus 0 Bus (O) Bridge 2nd - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 26
. Test 2 in Table 9 illustrates how bus assignments change when physical configuration changes occur in the server. IMPORTANT: The controllers that our testing added to the server configuration were selected only to illustrate how bus renumbering occurs. Several different Smart Array and network - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 27
PCI Bus Numbering in a Microsoft Windows NT Environment 27 Table 9: Test 2 - PCI BIOS bus detection in the ProLiant 8000 Bus Detection Order/ Controller Discovery Slot Number PCI Bridge/ Controller Type - Test 2 Bus Number Assignment 1st Primary Bus Host to PCI Bus 0 (O) Bridge 2nd - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 28
to bus 15. Empty slots are ignored, because they do not contain PCI devices. Comparison of Test 1 to Test 2 - Configuration B When you reboot the server and run the System Configuration utility to view the hardware configuration changes, it displays slot and bus number assignments. Test 2 data was - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 29
in a Microsoft Windows NT Environment 29 Configuration C, ProLiant DL580 Table 10 is an example of a ProLiant DL580 server set up as an original Window NT server configuration. All the controllers included in this configuration were installed in the server before Windows NT was loaded on the - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 30
A - Test 2 - Removing and Adding NICs The example in Table 11 illustrates the PCI BIOS discovery and bus number assignment process in the same ProLiant DL580 server, resulting in the reordering of bus numbers from the original configuration. When adding new network interface controllers (NIC) to - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 31
However, this loss of bindings will only be a problem until the NIC driver is installed and bound to the NIC in slot 3 unbound until it is manually reconfigured. Note that only NICs inserted between NICs affect Server In Test 2 several controllers are added to the system to provide additional support - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 32
reside. However, the SMART-2/SL Drive Array Controller is an supports the following controllers: • Compaq NC1120 Ethernet NIC • Compaq NC3120 Fast Ethernet NIC (PCI 10/100) • Compaq NC3121 Fast Ethernet NIC (PCI 10/100 WOL) • Compaq NC3122 Fast Ethernet NIC (PCI Dual 10/100) (82558 ) • Compaq - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 33
2 must be reconfigured in Windows NT after several new controllers are added to the ProLiant DL580 server. The following section illustrates how to reconfigure a controller(s). Main Window: Each Compaq Ethernet, Fast Ethernet, or Gigabit network controller that you install as standalone must have - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 34
a Controller: 1. Double click Start → Settings → Control Panel. 2. Select the Compaq Network icon to launch the Network Teaming and Configuration Utility. a. Highlight the controller that number for that driver instance. You must restart the server for the changes to take effect. 13UK-1200A-WWEN - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 35
in the server. 2. Highlight the controller that did not load and select the Remove option. Note: The Remove and Add steps are a manual process and server when the network controller configuration completes. When configuration changes are made affecting other manufacturer's controllers, the Compaq - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 36
controller prior to removing the controller. The Compaq PCI Hot Plug Utility is part of the Compaq Support Paq, which can be obtained from the Compaq SmartStart and Support Software CD and on the Compaq website at http://www.compaq.com/support/files/server/us/index.html. Once installed, the utility - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 37
to resolve problems without taking the server offline and to assist in maximizing server availability. This utility downloads as an individual Smart Component or as part of the Compaq Support Paq for Microsoft Windows NT 4.0 via the Compaq website at http://www.compaq.com/support/files/server/us - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 38
and volumes in the server. Without labels, the disk can only be identified by the drive letter. IMPORTANT: Compaq strongly recommends that you label system is brought back on line. This might not be a problem in small server configurations; however, as a network grows with more drives and volumes - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 39
Troubleshooting Tips Table 11 lists the PCI bus detection order, Primary and Secondary bus locations, and slot numbers for the several ProLiant servers Bus Slot 4 - Sec Bus ProLiant ML530 Primary Host to PCI Slot 2 - Ter Bus Slot 5 - Ter Bus ProLiant ML350 Primary Host to PCI Bridge Slot 1 - Pri - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 40
device vendor to determine if an upgraded driver will correct this problem. Summary PCI Bus numbers are determined during each and every server is booted. However, configuration mismatches are correctable using the tools that Compaq and Microsoft provide with Windows NT and several Compaq support - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 41
Bus Numbering in a Microsoft Windows NT Environment 41 Appendix A, Slot Design for Retired Compaq ProLiant Servers Retired Compaq ProLiant Servers The PCI bus numbering scheme of four retired Compaq ProLiant server models are detailed in this appendix. Note: The features discussed in this section - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 42
combined for the purpose of showing results. The most obvious difference between these two servers is that the ProLiant 7000 supports hot plug slots in the Secondary Bus (slots 7-11). A slot comparison diagram of each server follows in Figure 15: pat-10.eps EISA Slot 2 Slot 1 Primary PCI Bus Slot - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 43
PCI Bus Numbering in a Microsoft Windows NT Environment 43 Appendix B, PCI Test Configurations with Retired ProLiant Servers The following scenarios were tested in the Compaq Integration Lab. The scenarios demonstrate how the PCI BIOS assigns the bus numbers and then reassigns the bus numbers - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 44
performed on a simple configuration in a dual-peer PCI ProLiant 6500 server (see Table 13). This configuration is described as simple ry Bus Bridge (1) 5th Slot 3 Empty N/A 6th Slot 4 Netelligent Bus 1 10/100 TX 7th Slot 5 Empty N/A 8th Slot 6 Empty N/A 9th Slot 7 Empty - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 45
discovery and bus number assignment process in the same dual-peer PCI ProLiant 6500 server. However, the configuration changes slightly by adding a bridged PCI Bus Bus (1) Bridge 5th Slot 3 Empty 6th Slot 4 Netelligent 10/100 TX 7th Slot 5 Empty Slot 6 Empty 8th 9th Slot 7 Empty - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 46
controller in slot 4 are no longer applicable and must be manually reset for this controller to function in the configuration once again. Refer to the "Compaq TLAN Network Teaming and Configuration" section in this document for instructions on how to reset the bindings. Comparison of Test 1 to - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 47
The diagrams in Figure 16 illustrate the location of the expansion slots in the rear of the ProLiant 6000 and 7000 servers. Both servers share the same bus design and slot layout; however, the ProLiant 7000 server contains hot pluggable slots on the Secondary Bus as shown in Figure 16. pat-10.eps - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 48
Table 15. Test 1 - PCI BIOS bus detection in the ProLiant 6000 and 7000 servers Bus Detection Order/ Controller Discovery 1st 2nd 3rd 4th 5th 6th on these controllers. The SMART-2/SL Drive Array controller in slot 8 is assigned bus 3 and the Netelligent Dual 10/100 TX controller in slot 10 is - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 49
in the ProLiant 6000 and 7000 servers Bus Detection Order/ Controller Discovery 1st 2nd 3rd 4th Slot Number Primary Bus (0) Slot 1 (EISA) Slot 2 (EISA) Slot 3 PCI Bridge/ Controller Type - Test 2 Bus Number Assignment Host to PCI Bus bridge N/A N/A Bus 0 N/A N/A Netelligent 10/100 TX Bus - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 50
SMART-2/SL Drive Array controller in slot 8 is assigned bus 5 and the Netelligent Dual 10/100 TX controller in slot 10 is assigned bus 4. Empty slots are ignored, because they do not contain PCI devices. Comparison of Test 1 to Test 2 - Configuration B When you reboot the server - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 51
in the Smart Component called Compaq NetFlex/Netelligent Adapter Driver, which is available as an individual component and within the Compaq Support Paq on the Compaq SmartStart and Support Software CD and on the Compaq website at http://www.compaq.com/support/files/server/us/index.html. 13UK-1200A - HP ProLiant 2000 | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 52
Windows NT Environment 52 Appendix D, Order of Detection for Retired Compaq ProLiant Servers Table 18 lists the PCI bus detection order, Primary and Secondary bus locations, and slot numbers for the several retired ProLiant servers. This matrix can help you identify how the PCI BIOS assigns
Integration Note
Help us improve our technical communication. Let us know what you think
about the technical information in this document. Your feedback is valuable
and will help us structure future communications. Please send your
comments to:
December 2000
13UK-1200A-WWEN
Prepared by OS Integration
Engineering
Compaq Computer Corporation
Contents
Executive Overview
.....................
3
PCI Bus Architecture
Terminology
.................................
4
PCI Hot Plug Terminology
..........
5
PCI System Overview
..................
5
PCI Architecture and Bridged
Controllers
..................................
6
PCI BIOS
...................................
8
PCI Bus Numbering
...................
8
PCI BIOS Discovery
...................
8
Configuration Changes
............
11
Windows NT and PCI Bus
Numbering
..................................
11
PCI Bus Numbering and
Network Controllers
..................
11
Disk Renumbering
....................
12
Hardware, Software, and
Configuration Tools
...................
13
Compaq Servers and Option
Hardware
.................................
13
Planning a PCI System
Configuration
.............................
17
Before Modifying an Existing
System
.....................................
18
Planning the New
Configuration
............................
18
Step-By-Step Review
...............
19
PCI Test Configurations with
ProLiant Servers
........................
19
Configuration A, ProLiant
ML530
......................................
20
Configuration B, ProLiant
8000
.........................................
23
Configuration C, ProLiant
DL580
......................................
29
Compaq Support Software
and Utilities
..............................
36
Additional Troubleshooting
Tips
.............................................
39
Summary
....................................
40
Appendices A-D
.........................
41
PCI Bus Numbering in a
Microsoft Windows NT
Environment
Abstract:
Computing environments change rapidly to support
business requirements. Typical network PCI-based servers contain a
large number of expansion slots on multiple buses to allow for
system growth. This means that multiple network and disk
controllers of the same type may be installed in one server, with the
intent that each installed controller supports a separate unique
function. This can make it difficult to understand the physical and
logical implications of PCI bus numbering.
This document provides information to help systems engineering
professionals understand how Microsoft Windows NT handles PCI
bus numbering when controllers are physically added, moved, or
removed from a server configuration. This document also includes
ideas and suggestions that can help systems professionals avoid
network downtime due to configuration changes.
IMPORTANT:
During the development of Microsoft Windows
2000, Compaq and Microsoft worked closely together effectively
implementing Windows 2000 on Compaq hardware. Through this
partnership, device detection improved, eliminating PCI bus
numbering issues in the Windows 2000 environment. Windows 2000
checks and resets registry settings automatically, unlike its
predecessor that does not reset the registry settings after discovering
unbound devices.
The following documents were either used as references to produce
this white paper or are mentioned as recommended related reading
material:
•
PCI System Architecture, Third Edition, MindShare, Inc.
Tom
Shanley and Don Anderson, November, 1995.
•
PCI Bus Balancing and Optimization on Compaq ProLiant
Servers, March, 1998 – Doc ID ECG073/0398
.
•
Where Do I Plug the Cable?
Solving the Logical-Physical Slot
Numbering Problem, December 1996 – Doc ID 209A/1296
.
•
Deploying PCI Hot Plug on Compaq
Servers in a Microsoft
Windows NT
Environment, July 1997 - Doc ID 064A/0797
.