HP ProLiant ML330e PCI Bus Numbering in a Microsoft Windows NT Environment
HP ProLiant ML330e Manual
View all HP ProLiant ML330e manuals
Add to My Manuals
Save this manual to your list of manuals |
HP ProLiant ML330e manual content summary:
- HP ProLiant ML330e | 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 ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 3
memory Specification(s). Compaq Server technology includes equipment, such as the ProLiant 8000 with multiple PCI buses. The bus numbering when configuration computing capabilities of these servers Specification addresses server bus numbering assignments. This document discusses: • How the PCI BIOS - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 4
1 lists some memory controllers, dual-peer-PCI buses to deliver optimized multiprocessing support Specification, through which industry-standard peripheral controllers connect to computer systems. PCI BIOS functions provides a software three PCI buses on a single server is referred to as a Triple - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 5
Table 2 lists some terms related to PCI Hot Plug Terminology; however, this is not a complete list. The terms 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 6
PCI Bus architecture (see Figure 3). The Compaq servers discussed in this white paper and used system designs. Refer to the "Compaq Server and Option Hardware" section of this Memory Controller 267 MB/s OSB4 133 MB/s 2 x 64-Bit PCI Slots SuperIO Controller ISA Slot 4 x 32-Bit PCI Slots Server - HP ProLiant ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 8
(by pressing F10). The System Configuration Utility may be installed on a server with the Compaq SmartStart and Support Software CD or from a diskette to update the server configuration. PCI Bus Numbering At startup time, the PCI BIOS is aware only of the existence of PCI bus 0, the first bus - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 9
slots beginning at 2 and ending at 3. Highly Parallel PCI Bus - The Compaq 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 to deliver increased system throughput - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 10
(integrated PCI bridge) End of bus discovery Controller 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 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 11
in its registry after the 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 NetFlex-3 and Netelligent Controllers (see - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 12
Windows NT Environment 12 where as, the 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 recommends that you plan your changes carefully - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 13
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 any of the server or option hardware. Refer to the specification for each product to learn more about the complete - HP ProLiant ML330e | 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 ML330e | 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 ML330e | 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 ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 18
drives have received a signature from Windows NT. • Verify you have the necessary Windows NT CDs and the Compaq Support Paq for Microsoft Windows NT 4.0 to update drivers, if necessary. This information will be essential should you need to return to the original configuration. Planning the - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 19
. In addition 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 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 20
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 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 21
Environment 21 Note: Even though PCI bus numbers assign during every 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 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 22
NT Environment 22 Configuration 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 - HP ProLiant ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 24
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. Table 8 illustrates the relationship between slot numbers, controller installation, and PCI BIOS bus assignments in Configuration B-Test - HP ProLiant ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 26
Windows NT Environment 26 At this point, the PCI BIOS discovery process continues to the Tertiary Bus where it increments when physical configuration changes occur in the server. IMPORTANT: The controllers that our testing added to the server configuration were selected only to illustrate - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 27
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 Array Bus 14 PCI bridge is detected in slot 10. The 4250ES PCI BIOS increments the PCI number to bus 14 and assigns it to the bridge on - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 28
Fast Ethernet NIC in slot 5, a bridged device, is discovered next. The PCI BIOS assigns bus 7 to the PCI bus on the controller, the last PCI controller Test 1 to Test 2 - Configuration B When you reboot the server and run the System Configuration utility to view the hardware configuration changes, - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 29
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 Configuration Table 10. PCI BIOS bus detection in a ProLiant DL580-before removing and inserting - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 30
11 illustrates the PCI BIOS discovery and bus number assignment process in the same ProLiant DL580 server, resulting in the reordering driver must be reconfigured to accommodate the new NIC, at which time the bindings for the other NICs will be rebuilt. Table 11. PCI BIOS bus detection in a ProLiant - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 31
loss of bindings will only be a problem until the NIC driver is installed and bound to the NIC ports 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 32
boot server contains a TLAN-based network controller, you must use the Compaq TLAN Teaming and Configuration Utility referenced in Appendix C. The applet for this utility can be found in the Windows NT Control Panel with an icon labeled Compaq Network. This utility installs from the Compaq Support - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 33
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 a separate driver instance in Microsoft Windows NT. If any unbound services exist - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 34
→ Settings → Control Panel. 2. Select the Compaq Network icon to launch the Network Teaming and from the registry). The driver for this adapter will not be removed from memory until the system is the controller, but the driver is not currently loaded in memory (the driver loads the next time - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 35
are a manual process and must be performed separately. 3. Re-add the controller by selecting the controller from the Adapter List and then select server when the network controller configuration completes. When configuration changes are made affecting other manufacturer's controllers, the Compaq - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 36
halt operations on a specific 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 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 37
and as part of the Compaq Support Paq, which may be found at the following locations: • Compaq SmartStart and Support Software CD (http://www.compaq.com/support/files/server/us/smartstart.html) • Compaq Server Software Download Center website (http://www.compaq.com/support/files/server/us/index - HP ProLiant ML330e | 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 ML330e | 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. This matrix can help you identify how the PCI BIOS assigns bus numbers in these servers. The ProLiant 8000 and ProLiant ProLiant Bus ProLiant ML350 - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 40
NT does not automatically detect that bus were renumbered the server is booted. However, configuration mismatches are correctable using the tools that Compaq and Microsoft provide with Windows NT and several Compaq support software tools. This document provides the information needed to determine - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 41
a complete description for any of the server or option hardware. Refer to the specification for each product to learn more about the complete feature set. This information is available on the Compaq website at http://www.compaq.com/products/servers. The ProLiant 6500 PCI bus numbering results are - HP ProLiant ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 43
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 based on configuration - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 44
on a simple configuration in a dual-peer PCI ProLiant 6500 server (see Table 13). This configuration is described as simple because it contains only two nonbridged PCI network controllers. Table 13. PCI BIOS bus detection in a ProLiant 6500 - before adding a bridged controller Bus Detection - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 45
reside. Configuration A - Test 2 - Adding a Device The next example in Table 14 illustrates the PCI BIOS 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 disk controller on the Primary - HP ProLiant ML330e | 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 ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 48
Environment 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 Array Controller in slot 6, a bridged device, is discovered next. The PCI BIOS assigns bus 1 to the PCI bus on the bridged controller. This is - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 49
NT Environment 49 IMPORTANT: The controllers that Compaq added to the server configuration were selected only to illustrate how bus configuration changes occur in the server. Table 16. Test 2 - PCI BIOS bus detection in the ProLiant 6000 and 7000 servers Bus Detection Order/ Controller Discovery - HP ProLiant ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 50
all bus number assignments on the Secondary Bus change when the PCI BIOS discovery process continues. The Secondary Bus is assigned bus 4. The Test 1 to Test 2 - Configuration B When you reboot the server and run the System Configuration utility to view the hardware configuration changes - HP ProLiant ML330e | 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 ML330e | PCI Bus Numbering in a Microsoft Windows NT Environment - Page 52
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 bus numbers in these servers. The ProLiant 2500 servers consist
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
.