October 25, 2001
Creating the Drivers Diskettes
Selecting the Manual Installation Method
Special Instructions for Installing Windows 2000 on HP NetServer LH 6000 or LT 6000r Systems
Special Instructions for Installing Windows 2000 on an HP NetServer LP 1000r or LP 2000r
Hardware Status Check
Initialize Hard Drives
Configure Server IP Address
Attach Clients to Network
Domain Controller Setup
Adding Terminal Server Services
Installing Citrix MetaFrame for Microsoft Windows 2000
Installing Windows 2000 DataCenter from the HP-Provided CD-ROM
Tip #1. Upgrading from NT 4.0 to Windows 2000
Tip #2. HP NetRaid-1 Partition >8GB Not supported
Tip #3. NetServer LH Pro, LD Pro and LH II with DAC present hangs during high work load
Tip #4. Windows 2000 Installation halts about three minutes after starting to boot from CD-ROM
Tip #5. LX Pro, LX, LXe, LH Pro, LD Pro & LH II hang when booting from the Windows 2000 CD
Tip #6. Avoid using IRQ 9 on NetServer LH 4
Tip #7. Using the Windows 2000 integrated backup utility with NetServer E60 and E 50 bundled tape drives
Tip #8. Hewlett Packard NetRaid D4992A and D4943A Should be used in PCI bus zero
Tip #9. Configure the Parallel (LPT) Port for ECP Mode
Tip #10. Event Viewer Error 3013 On NT Clients
Tip #11. Mirror Drive Issue
Tip #12. Upgrading Windows 2000 from Uniprocessor HAL to Multiprocessor HAL
Tip #13. Installing the NetRAID-4M, 2M, or 1M Driver After Windows 2000 is Installed
Tip #14. Windows 2000 Driver Signatures
Tip #15. Upgrading D5013B NIC Drivers for Windows 2000
Tip #16. Installation Fails to Boot after First Reboot
Tip #17. Installing Citrix on HP NetServer LT 6000
Tip #18. Windows 2000 Recovery Options
Tip #19. Installing the HP NetRaid-4M Drivers when Upgrading to Windows 2000
Tip #20. Page Address Extension /PAE not added by Windows 2000 DataCenter installer
Tip #21. Hibernate Tab Not Available in Windows 2000 DataCenter
Tip #22. Windows 2000 DataCenter WINMSD.EXE utility reports wrong BIOS version
This document was created by Hewlett-Packard for the purpose of helping you install Microsoft Windows 2000 on your HP NetServer based on procedures tested by HP. The objective of this document is to provide the information needed to achieve the following tasks.
Before you start installing or upgrading to Windows 2000 check the following documents and make sure you develop an action plan to complete the installation. Use the following informational resources to help you.
Complete the following table before you begin the installation process. You will need this information in order to answer questions that you will be asked during the installation process.
Partition Table: ______________________(List target partitions)
User Name: _________________________
Organization: ________________________
Licensing: ___________________________
Computer Name: ______________________
Admin Password: _____________________
Date Time Zone: ______________________
Workgroup or Domain Name: ______________
Registration Key: ____________________________
There are several ways of installing Windows 2000. The most popular methods are listed below. Select a method and go to the appropriate section of this guide to begin. Depending upon your system and its configuration, it may also be necessary to create a drivers diskette.
HP recommends that you follow this method to install Windows 2000. This is the easiest method because it requires less user intervention. Following are the steps to complete the installation of Windows 2000 using the HP Navigator CD.
Before you begin, use one of the following two methods that can be used to create the drivers diskette. One method is to create the drivers diskette using a system booted from the Navigator CD. The other method is to create the drivers diskette using a system that is running Windows NT, Windows 2000, or Windows 95/98.
NOTE: The system’s monitor must be set for at least 800 x 600 resolution.
Before using this method of installation, decide whether you want to install Windows 2000 using Setup Diskettes, or by booting directly from the Windows 2000 CD.
If you opt for starting the Windows 2000 installation from Setup Diskettes, do the following:
The Windows 2000 installation process automatically sets "write combine" on which causes the HP NetServer LH 6000 and LT 6000r to hang under various conditions. If you are installing Windows 2000 on an LH 6000 or LT 6000r, carefully perform the following special instructions for installing Windows 2000 on an LH 6000 or LT 6000r.
NOTE: There are no embedded 53C1010 Ultra 3 SCSI boot device drivers included on the Windows 2000 CD-ROM
Before you begin the installation of Windows 2000 on an LP 1000r or LP 2000r, create the "Windows 2000 Drivers Diskette for the embedded 53C1010 Ultra 3 SCSI." (Created from HP Navigator CD-ROM) See the instructions for creating drivers diskettes earlier in this document.
After the installation of Windows 2000, the Windows 2000 Device Manager will detect SDR GEM318 SCSI Processor Device as Other Device because Windows 2000 does not have the SAF-TE.INF file.
To solve this issue, perform the following steps:
Install Windows 2000 using the procedure given below.
NOTE: An intermittent, but critical cache manager timeout issue in Windows 2000 Server and Windows 2000 Advanced Server has been identified. To avoid potential data loss in certain situations, it is strongly recommended that you install a Microsoft fix after you install Windows 2000 Server or Windows 2000 Advanced Server.
To obtain this fix refer to Microsoft knowledgebase article Q252332 at http://support.microsoft.com/directory. Refer to the Microsoft website for any updates.
NOTE: If you experience any hang or issue during this time, consult the Tips/Tricks section of this document for help.
NOTE: If the boot device driver is not included on the Windows 2000 CD-ROM, for example the "HP NetRAID-4M", then do the following steps after pressing F6
a) Press S to select additional hardware.
b) Select Other and press Enter.
c) When prompted to insert driver diskette, please insert the target adapter driver’s diskette created with the HP Navigator CD-ROM. Press Enter to continue.
d) Select the target device driver from the list provided on the display. For example, if you have the "HP NetRAID-4M", select "Hewlett Packard NetRAID-4M RAID CONTROLLER".
if you have the "HP NetRAID-1M/2M", select "Hewlett Packard NetRAID-1M/2M RAID CONTROLLER".
Please repeat the above step for the "HP NetRAID-2M and 1M"
e) If you have no other drivers that you need to install, press Enter to continue with the installation.
NOTE: If you see a dialog box titled "Digital Signature Not Found".
Please click "Yes" to continue the installation and read Tip #14 in the troubleshooting section of this guide.
NOTE: For Windows 2000 DataCenter, you must enter either the domain or workgroup name before you can proceed to the next step.
NOTE: There may be a period of time with no apparent activity after it displays a message that reads "OS Loader Version 5.0". Be patient.
In this section you will run the "Device Manager" tool to identify any issues with the installed devices or resource conflicts.
NOTE: Hewlett Packard and Microsoft have identified some devices that under normal conditions can produce (!) or (?) marks. Please see table 5 in the Appendix A of this document for an interpretation.
To start the disk administrator use the following procedure.
NOTE: There are two types of hard drive configuration: Dynamic and Basic. You can select the appropriate type by right clicking on the drive icon on the screen. Dynamic drives are used to create volumes which can contain more than one physical hard drive. Basic drives are used to create primary or local partitioned drives.
During the installation process the system was configured to use DHCP. Also, when no DHCP server is found on the network the system will auto-configure a random IP address to start functioning. It is important that you configure the proper IP address to be able to communicate with the clients.
Configuring IP Address Steps.
Follow normal procedure to patch the clients to the proper hub with the server.
The Windows 2000 reference guide calls this process "Promoting the server to a domain controller".
The objective of this section is to assist customers with manual installation of "Citrix MetaFrame for Windows 2000 Terminal Service" on a Hewlett-Packard NetServer system.
NOTE: You Need to install Windows 2000 Terminal Service before you install Citrix MetaFrame Windows 2000 Servers.
Citrix 1.8 MetaFrame for Windows 2000 CD-ROM. Windows 2000 installed with Terminal Service.
The objective of this section is to assist customers with a manual installation of "Citrix MetaFrame XP for Windows 2000 Terminal Service" on an HP NetServer system.
NOTE: You Need to install Windows 2000 Terminal Service before you install Citrix MetaFrame XP.
NOTE: when you install MetaFrame XP using the MetaFrame XP Setup option the Citrix Management console is automatically install by default.
The following are the procedures for installing Microsoft Windows 2000 DataCenter Server from the HP-provided CD-ROM. For more information, please view the Windows 2000 DataCenter Readme file.
This section provides information about known issues, solutions and workaround.
It is possible to upgrade from any edition of NT 4.0 including Terminal Server to Windows 2000. Please refer to the readme.doc on the Windows 2000 CD and the Windows 2000 Setup Guide for information on how to perform the upgrades.
Issue: You cannot install Windows 2000 on a system using an HP NetRaid-1 as the boot device and a logical drive > 8GB.
Workaround: the HP NetRAID-1 adapter has an 8 GB limit for the boot partition. If you are going to boot from devices connected to a NetRAID-1 controller, be sure that you don't set the boot partition any larger than 8 GB during the Windows 2000 installation procedure.
When using adapters behind the PCI bridge, HP recommends that the EISA configuration setting "PCI Bridge Timers" be changed using the following steps.
Issue: When installing Windows 2000 on any X86 system with more than one hard drive it is possible to experience the following error:
Setup has encountered an error and cannot continue. Contact technical support for assistance. The following status codes will assist them in diagnosing the problem. (0x4, 0x1, 0x0, 0x0)
The cause of this problem is that the NTLOADER is encountering a duplicate hard drive signature. This signature is calculated by the NTLOADER code after reading a specific sector offset from the hard drive. For more information please refer to Microsoft document ID: Q226361.
The following list provides some of the things that can cause hard drive to have duplicate signatures:
At this time, Microsoft has no fix for this problem
Workaround: HP recommends that you use the following workaround for this problem.
Issue: If the system contains an Adaptec SCSI controller, depending upon how the controller is configured, the system can hang if you attempt to boot from the Windows 2000 CD. The hang is usually encountered within 30 seconds after the start of the boot process. The message that is displayed on the screen is "Set up is inspecting your computer’s hardware configuration …".
NOTE: The boot order is: slot 1, slot 2, slot 3, slot 4, embedded SCSI A, embedded SCSI B, slot 5 and slot 6.
Workaround:
Issue: If you configure any adapter to use IRQ9 on a NetServer LH 4, Windows 2000 will not configure the adapter. The device manager will report an error code 12, meaning no resources available. Also, if the boot drive is on a SCSI adapter with IRQ9 the system will fail to boot with a STOP 7B(0xF401b848, 0xC0000034, 0x0, 0x0).
Workaround: HP recommends that you use one of the following workarounds for this problem.
The following steps explain how to make this change.
The backup utility in w2k has a "Backup Destination" pull down menu with the following choices:
File
minQIC
Travan
The T20 tape drive shipped with the NetServer E 60 requires that you set this option to minQIC when using 20GB cartridge. If you plan to use an 8GB cartridge (read-only mode supported) then change this setting to Travan.
The T4 tape drive shipped with the NetServer E 50 requires that you set this option to Travan. The T4 tape drive only supports 8GB cartridges.
It you don't set this option properly the backup utility will report that either the tape drive is broken or the media is full.
For performance reasons it is recommended to install the HP NetRAID-1 (D4992A) or HP NetRAID (D4943A) in a PCI bus that is part of bus zero. Please note that this recommendation is only for these two part numbers.
HP recommends that you configure the LPT port for ECP mode. Otherwise the device manager may not show this port on the list. This configuration change is made by using the following procedure:
NOTE: Depending on your NetServer model the above steps may not read exactly the same. Please locate the I/O device Configuration section on the screen and make the change.
Issue: An intermittent, but critical cache manager timeout issue in Windows 2000 Server and Windows 2000 Advanced Server has been found when doing a large volume of network file transfers to a server. This condition causes a reasonable amount of disk I/O stress which may potentially cause data loss in certain situations. This condition can be identified by the following error appearing on the Client/Workstation Event Log:
Error 3013: The redirector has timed out to servername
Solution: It is strongly recommended that you install a Microsoft fix after you install Windows 2000 Server or Windows 2000 Advanced Server. To obtain this fix refer to Microsoft knowledgebase article Q252332 at http://support.microsoft.com/directory. Refer to the Microsoft website for any updates. This fix will be released on SP1.
Issue: Windows 2000 running with Software Mirrored system drive will not allow you to reconfigure a drive after you break the mirror. For example, you cannot delete the system volume.
After breaking the mirror of the system disk the Disk Management cannot delete the volume of the system disk. For example, add mirror for the system disk with an allocated hard disk drive (for example: Disk 0 contains Windows 2000 is mirror with Disk 1 that is unallocated). Next, break the mirror then try to delete the volume of Disk 1, but the Disk Management cannot delete the volume of Disk 1. Instead the disk Management only allows you to format Disk 1. Furthermore, the Disk Management will not allow you to mirror the system disk (Disk 0) with any other hard disk.
Workaround: In order for the Mirror feature to work again and to delete the system volume of Disk 1. Please do the following:
NOTE: After the OS boots up "Disk Management" will show Disk 1 is now "UNALLOCATED". This means the system volume of Disk 1 is successfully mounted, and now the Mirror feature will work. But, now Disk Management will show there is one drive "MISSING". In order to fix the drive "MISSING" problem the OS has to be reinstalled.
Solution: Apply Windows 2000 SP1 when available.
Issue: If you have a uni-processor system running Windows 2000 and a second processor is added, the plug and play feature in Windows 2000 will not auto-detect the second processor.
Solution: Use the following procedure to configure Windows 2000 to use the second processor .
NOTE: Please consult the "HP NetRAID-4M" installation guide for instructions on doing the physical installation of the adapter.
Please use steps #1 to 4 above for installing the "NetRAID-2M" or "NetRAID-1M"
Windows 2000 checks for digital signatures on driver files to help maintain system integrity. During the installation or update of a driver, if there is no matching signature file Windows 2000 displays a "Digital Signature not Found" box.
To expedite release of new products, drivers may be shipped by HP without signature files. All Windows 2000 drivers provided by Hewlett-Packard are submitted to Microsoft for certification testing . Upon completion of testing, Microsoft produces signature files. HP then posts the revised driver package at www.hp.com.
If a signature warning is displayed during installation of a driver, you may override the warning. We recommend that you check the HP Website for the latest driver package. If available, install the new driver.
You can elect to have Windows 2000 ignore signatures. Right-click My Computer; select Properties, Hardware, then Driver Signing. This is helpful if you are setting up multiple systems.
Digital signatures are a powerful way to ensure system integrity as you add drivers -- whether provided by Hewlett-Packard or others -- to your system.
Windows 2000 installation automatically detects the HP D5013 NIC and installs the driver bundled with the Windows 2000 CD-ROM. The following procedure will help you upgrade the driver using the "Drivers Diskette" created with the "Hewlett Packard Naviagator CD-ROM". ( See Manual Installation section of this document for instructions on how to create the drivers diskette. )
To update the driver for the adapter:
Issue: Windows 2000 installation fails to boot after the first reboot. with an error indicating that something is wrong with the disk subsystem. This problem is usually because the BIOS does not support Int13 extensions to handle drives > 8G.
Workaround: Create a partition of 2G or so to install Windows 2000.
Solution: Check http://www.hp.com to see if a new BIOS is available for the system or component providing the boot functionality.
NOTE: The NetServer LXr Pro 8 will experience this issue. Hewlett Packard did not roll the BIOS for this system. It is recommended that you implement the workaround listed above.
The following procedure was created by Citrix after using our installation guide and testing with the LT6000.
This application note describes how to install Citrix MetaFrame 1.8 and Microsoft Windows 2000 Advanced Server on an HP NetServer LT 6000 server.
If you do not have the HP Navigator CD-ROM you can download the necessary file from their website: http://www.hp.com/country/us/eng/supportservices.htm
In the event that the current installation of Windows 2000 fails to boot (this might happen after installing a new driver, component, software, etc), Windows 2000 provides the following recovery options to help you gain access to your windows 2000 installation to replace damaged files and services for troubleshooting purpose.
It is recommended that you install the Recovery Console as listed on this document to enhance the system configuration.
Activated by pressing F8 during the system process of Windows 2000 and selecting "Last Known Good Configuration" from the menu.
This boot mode is used in the case that the system fails to boot after installing a new software or driver. The system will use the previous registry setting to initialize and boot the system.
Activated by pressing F8 during the system boot. It provides minimal configuration with required drivers and services. The safe mode boot provides three options:
There is a Safe-Mode boot loophole. Since NTLDR loads "Boot Load" drivers, these drivers bypass the IO Manager’s safe Mode check.
Recovery Console can be used when safe boot fails. You can enter RC in two ways booting from Windows 2000 CD-ROM or by installing the recovery console boot on your system.
It is recommended to install the recovery console (RC) immediately after installing Windows 2000.
If you have a need of booting the Windows 2000 recovery console but this feature is not installed on the system, use the following procedure to boot the RC from the Windows 2000 CD-ROM.
NOTE: The file access security can prevent you from getting to files.
Refer to the HP NetRaid-4M "User’s Guide" for information on how to installing the drivers when upgrading to Windows 2000 for a HP NetRaid-4M adapter.
If your system has more than 4G of RAM edit boot.ini file to add /PAE switch at the end of the operating system string, i.e. the operating system string that declares Microsoft Windows 2000 DataCenter Server.
For example:
multi(0)disk(0)rdisk(0)partition(3)\WINNT="Microsoft Windows 2000 Professional" /fastdetect C:\="Microsoft Windows" /PAE
The hibernate tab is not available on systems with one of the following conditions:
Microsoft indicated that this is how the product was designed.
The Microsoft utility WINMSD.EXE reports the Phoenix core version number 6. The Hewlett Packard version number 8 is not reported. To obtain the proper BIOS version you need to either use the LXr 8500 LCD display or power cycle the server and view the BIOS banner displayed during the Power-On Self Test.
Question: What NetServer BIOS version do I need to run Windows 2000?
Answer: Table 6, provided in Aappendix A of this document provides a list of NetServer and BIOS versions used to test with Windows 2000. HP recommends that you use the version provided in this table or a later release.
Question: What HP Disk Array BIOS/Firmware version do I need to run Windows 2000?
Answer: Table 7, provided in Aappendix A of this document provides a list of Disk Array BIOS/Firmware versions used to test with Windows 2000. HP recommends that you use the version indicated in this table or a later release.
Question: What ACPI features are supported for each NetServer running Windows 2000?
Answer: Table 8, provided in Appendix A of this document provides a list of all ACPI features tested for each NetServer running Windows 2000.
Question: Where do I get the driver's required to run Windows 2000?
Answer: The initial release of Windows 2000 includes all the drivers required to install Windows 2000 on the NetServer's and DAC's listed in table 6 & 7 of Appendix A. Except the NetRaid-4M adapter.
Future driver updates or new adapter driver's will be provided on the Hewlett Packard Navigator CD, or check http://www.hp.com.
If you have a HP Fiber Channel adapter, you will need to install the drivers provided on the HP Fiber Channel Adapter drivers diskette. You can use the HP Navigator CD to create the drivers diskette.
Question: Can I configure the HP NetRaid 3Si or LH 3 / LH 4 integrated DAC in I2O mode to run Windows 2000?
Answer: No, the first release of Microsoft Windows 2000 does not support I2O. Some magazine publication may list this technology as a new feature but it is not currently supported.
Question: How do I configure the HP D5013 Network Interface Card for NIC teaming?
Answer: NIC teaming is not supported with the D5013 Driver bundled with Windows 2000 CD-ROM. You can identify this driver by looking at "Device Manager", driver date is 10/26/1999 and driver version is 4.1.6.67.0. Hewlett Packard is working on a future driver, which will support this feature.
Question: Can I upgrade my NetServer running Windows NT 4.0 to Windows 2000?
Answer: Yes, Hewlett Packard tested with upgrade configurations. However, it is unpredictable if any application on your system will work after the upgrade.
Question: Where can I get more information on Windows 2000?
Answer: You may also use the following resources:
www.hp.com
Windows 2000 online help.
Question: How do I enable Windows 2000 to use more than 4G RAM?
Answer: You need to install Windows 2000 Advanced Server or Data Center Edition. Next, edit boot.ini and add /pae option.
The following is an example boot.ini with this change implemented. Remember to make a backup copy and remove the SHR attribute before editing this file.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect /pae
NOTE: The last line listed above should not wrap around when edited with the system ASCII editor.
Question: What is the max number of CPU’s supported by each version of Windows NT?
Answer: Please check with the Microsoft web site for latest update. During beta test the following information was provided:
Windows 2000 Server, Max = 2-Way SMP.
Windows 2000 Adv. Server, Max = 4-Way SMP.
Windows 2000 Adv. Server, Upgrade from NT 4.0 Enterprise Edition, Max = 8-Way SMP.
Windows 2000 Data Center, Max = 16-Way SMP.
This section provides additional information to help add new components, troubleshoot, etc.
List of NetServer platforms supported by the method called "Automatic - Boot from Hewlett-Packard Navigator CD-ROM" (see "Table #6" for a list of Windows 2000 tested and supported systems).
Model |
HP Auto-Install Support |
CD Boot Supported? |
Win 2000 Supported? |
Also see Tip # |
E30 |
No |
Yes |
No |
|
E40 |
No |
Yes |
No |
|
E45 |
No |
Yes |
No |
|
E50 |
No |
Yes |
Yes |
7,9 |
E60 |
Yes |
Yes |
Yes |
7,9 |
E200 |
Yes |
Yes |
No |
|
E800 |
Yes |
Yes |
Yes |
|
LC |
No |
No |
No |
|
LC Plus |
No |
Yes |
No |
|
LCII |
No |
Yes |
Yes |
2,8,9 |
LC3 |
Yes |
Yes |
Yes |
2,8,9 |
LC2000 |
Yes |
Yes |
Yes |
2,8,9 |
LD |
No |
Yes |
No |
|
LD Pro |
Yes |
Yes |
Yes |
2,3,8,9 |
LF |
No |
Yes |
No |
|
LH |
No |
Yes |
No |
|
LH Pro |
Yes |
Yes |
Yes |
2,3,8,9 |
LHII |
Yes |
Yes |
Yes |
2,3,8,9 |
LH3 |
Yes |
Yes |
Yes |
2,8,9 |
LH4 |
Yes |
Yes |
Yes |
2,6,8,9 |
LH3000 |
Yes |
Yes |
Yes |
2,8,9 |
LH6000 |
Yes |
Yes |
Yes |
2,8,9 |
LT6000r |
Yes |
Yes |
Yes |
2,8,9 |
LM(All) |
No |
No |
No |
|
LS(All) |
No |
Yes |
No |
|
LX |
Yes |
Yes |
Yes |
2,5,8,9 |
LXr Pro8 |
No |
Yes |
Yes |
2,8,9 |
LPr |
Yes |
Yes |
Yes |
2,8,9 |
LP1000r |
Yes |
Yes |
Yes |
13 |
LP2000r |
Yes |
Yes |
Yes |
13 |
LXr8000 |
Yes |
Yes |
Yes |
2,8,9 |
LXr8500 |
Yes |
Yes |
Yes |
2,8,9 |
List of embedded SCSI chip set for each NetServer (see "Table #6" for a list of Windows 2000 tested and supported systems).
Model |
SCSI Adapter |
Ultra SCSI/ |
E30 |
Adaptec 29xx |
No/A |
E40 |
Adaptec 29xx |
No/A |
E45 |
Adaptec 29xx |
No/A |
E50 |
Adaptec 29xx |
No/A |
E60 |
Adaptec 7895 |
(Wide)/A,B |
E800 |
Symbios 896 |
Ultra2/ A,B |
LC |
Adaptec 7770 |
No/A |
LC Plus |
Adaptec 78xx |
Yes/A |
LCII |
Adaptec 78xx |
Yes/A |
LC3 |
Adaptec 78xx |
Yes/A,B |
LC2000 |
Symbios 897 |
Ultra2/A,B |
LD |
Adaptec 78xx |
No/A,B |
LD Pro |
Adaptec 78xx |
No/A,B |
LF |
Adaptec 7770 |
No/A |
LH |
Adaptec 78xx |
No/A |
LH Pro |
Adaptec 78xx |
Yes/A,B |
LHII |
Symbios 895 |
Ultra2/A,B |
LH3 |
Symbios 895 |
Ultra2/A,B |
LH4 |
Symbios 895 |
Ultra2/A,B |
LH3000 |
Symbios 895/ Adaptec 7880 |
Ultra2/A,B |
LH6000 |
Symbios 896/ Adaptec 7880 |
Ultra2/A,B |
LT6000r |
Symbios 896/ Adaptec 7880 |
Ultra2/A,B |
LM (All) |
Adaptec 7770 |
No/A,B |
LS (All) |
Adaptec 78xx |
No/A,B |
LX |
Adaptec 78xx |
No/A,B |
LXr Pro8 |
Symbios 975 |
Yes/A(6) |
LPr |
Symbios 895 |
Yes/A,B |
LP1000r |
Symbios 53C1010-33 |
Ultra 3/ A,B |
LP2000r |
Symbios 53C1010-33 |
Ultra 3/ A,B |
LXr 8000 |
Symbios 896 |
Ultra2/A,B |
LXr 8500 |
Symbios 896 |
Ultra2/A,B |
List of embedded Video Product Name and Driver Name for each NetServer (see "Table #6" for a list of Windows 2000 tested and supported systems).
Model |
Video Adapter |
E30 |
S3 Trio 64 |
E40 |
CL 5446 1M |
E45 |
CL 5446 1M |
E50 |
CL 5446 1M |
E60 |
ATIRage IIC 4M AGP |
E800 |
ATIRage XL 8M PCI |
LC |
Trident 9000I 512K* |
LC Plus |
Trident 9000I 512K* |
LCII |
CL 5446 1M |
LC3 |
CL 5446 1M |
LC2000 |
ATIRage IIC 2M |
LD |
Trident 9000I 512K* |
LD Pro |
Trident 9000I 512K* |
LF |
Trident 9000I 512K* |
LH |
Trident 9000I 512K* |
LH Pro |
Trident 9000I 512K* |
LHII |
Trident 9000I 512K* |
LH3 |
CL 5446 1M |
LH4 |
CL 5446 1M |
LH3000 |
ATIRage IIC 2M |
LH6000 |
ATIRage IIC 2M |
LT6000r |
ATIRage IIC 2M |
LM (All) |
WD 512K* |
LS (All) |
CL 5436 512K* |
LX |
CL5436 512K* |
LXr Pro8 |
S3 Virge |
LPr |
CL 5446 1M |
LP1000r |
AITRage XL PCI 4MB |
LP2000r |
AITRage XL PCI 4MB |
LXr8000 |
CL 5446 1M |
LXr8500 |
CL 5446 1M |
* The driver is not provided by Hewlett-Packard. Users should use the driver bundled with Windows NT CD-ROM.
Note: Video adapters with 1M can be upgraded to 2M.
This table provides a list of CD-ROM type for each NetServer (see "Table #6" for a list of tested and supported system under Windows 2000).
Model |
CD-ROM Type |
E30 |
IDE |
E40 |
IDE |
E45 |
IDE |
E50 |
IDE |
E60 |
IDE |
E800 |
IDE |
LC |
SCSI |
LC Plus |
SCSI |
LCII |
IDE |
LC3 |
IDE |
LC2000 |
IDE |
LD |
SCSI |
LD Pro |
SCSI |
LF |
SCSI |
LH |
SCSI |
LH Pro |
SCSI |
LHII |
SCSI |
LH3 |
IDE |
LH4 |
IDE |
LH3000 |
IDE |
LH6000 |
IDE |
LT6000r |
IDE |
LM (All) |
SCSI |
LS (All) |
SCSI |
LX |
SCSI |
LXr Pro8 |
IDE |
LPr |
IDE |
LP1000r |
IDE |
LP2000r |
IDE |
LXr8000 |
IDE |
LXr8500 |
IDE |
This table provides a list of device manager events that are approved by Microsoft as acceptable.
Model |
ACPI Event |
Integrated RAID on NetServer |
Device manager reports a (?) other devices, PCI memory controller. This error condition in only present when the integrated RAID is disabled. |
NetServer LH3, LH4 |
(!) Intel 82371 AB/EB PCI to USB Universal Controller. (USB chipset is present but no connector available on the system.) |
NetServer LC 2000, LH6000, LT6000r. HP D5989A or D5989B, RS12 Storage Cabinet |
Device manager shows one of the following messages under (?) Other devices.
Action to fix this error: Load the HP Navigator CD-ROM, go to the library diskette section and create the INF driver diskette for the Storage cabinet. Follow the instructions on the readme.txt file on the diskette. |
NetServer LH, LH Pro, LD, LD Pro |
(!) Trident video controller. (No Driver available. Need to replace integrated video with a supported video controller.) |
This table provides a list of NetServers tested with Windows 2000.
Model |
WHQL MID |
CPU (Range) |
Max RAM |
Video |
HP NIC |
ACPI |
BIOS/ Date |
E50 |
TBD |
Uni- Pentium II (300-330) |
384M |
CL 5446 |
D5013 |
No |
4.05.08 PM 7/2/99 |
E60 |
16993 |
Dual Pentium III (450-550) |
512M |
ATIRage IIC AGP |
D5013 |
Yes |
4.06.21 PN 9/16/99 |
E800 |
TBD |
Dual Pentium III (667-800) |
2G |
ATIRage XL PCI |
D5013 |
yes |
TBD |
LCII |
20008 |
Dual Pentium II (266-333) |
512M |
CL 5446 |
D5013 |
No |
4.06.26 PK 8/3/99 |
LC3 |
19399 |
Dual Pentium II (400-550) |
1G |
CL 5446 |
D5013 |
No |
4.06.31 PQ 8/6/99 |
LD Pro |
TBD |
Dual Pentium Pro (200) |
512M |
Trident 9000i |
D5013 |
No |
4.05.16 6/10/98 |
LH Pro |
TBD |
Dual Pentium Pro (200) |
512M |
Trident 9000i |
D5013 |
No |
4.05.16 6/10/98 |
LHII |
20007 |
Dual Pentium II (266-333) |
512M |
Trident 9000i |
D5013 |
No |
4.05.20 PF 7/21/99 |
LH3 |
19400 |
Dual Pentium III (400-600) |
1G |
CL 5446 |
D5013 |
No |
4.06.36 PL 8/6/99 |
LH4 |
16859 |
Quad Xeon (400-550) |
4G |
CL 5446 |
D5013 |
Yes |
4.06.27 PS 9/7/99 |
LPr |
19401 |
Dual Pentium III (450-600) |
1G |
CL 5446 |
D5013 |
Yes |
4.06.20 PR 9/7/99 |
LP1000r |
TBD |
Dual Pentium III (867-1000) |
4G |
ATIRage XL PCI |
D5013 |
Yes |
TBD |
LP2000r |
TBD |
Dual Pentium III (867-1000) |
4G |
ATIRage XL PCI |
D5013 |
Yes |
TBD |
LX Pro |
20006 |
Quad Pentium Pro (166-200) |
4G |
CL 5436 |
D5013 |
No |
1.00.11.CD0L 10/29/97 |
Lxe Pro |
20006 |
Quad Pentium Pro (166-200) |
4G |
CL 5436 |
D5013 |
No |
1.00.11.CD0L 10/29/97 |
LXr Pro |
20006 |
Quad Pentium Pro (166-200) |
4G |
CL 5436 |
D5013 |
No |
1.00.11.CD0L 10/29/97 |
LXr Pro8 |
20011 |
Eight Pentium Pro (200) |
4G |
CL 5436 |
D5013 |
No |
2.00PB4.0Rel6.20 4/14/98 |
LXr8000 |
18111 |
Quad Xeon (400-550) |
8G |
CL 5446 |
D5013 |
Yes |
Rel. 12 8/23/99 |
LXr8500* |
19643 |
Eight Xeon (400-550) |
32G |
CL 5446 |
D5013 |
Yes |
Rel. 6 10/6/99 |
LH3000 |
N/A |
Dual Pentium III (600-667) |
4G |
ATIRage IIC PCI |
D5013 |
Yes |
4.06.14 PT 11/17/99 |
LH6000 |
N/A |
6-way Pentium III (550) |
4G |
ATIRage IIC PCI |
D5013 |
Yes |
4.06.14B |
LT6000r |
N/A |
6-way Pentium III (550) |
4G |
ATIRage IIC PCI |
D5013 |
Yes |
4.06.14B |
LC2000 |
N/A |
Dual Pentium III (533-733) |
4G |
ATIRage IIC PCI |
D5013 |
Yes |
4.06.12 PV 10/28/99 |
* This system supports Windows 2000 Datacenter.
This table provides a list of Disk Array Adapters tested with Windows 2000.
Adapter |
P/N |
BIOS |
Firmware |
Win2K Support |
Max Boot Drive Size* |
NetRaid 1Si |
D2140A |
B.02.01 |
F.02.02 |
Yes |
|
NetRaid 3Si |
D5955A |
B.02.01 |
C.02.02 |
Yes |
|
NetRaid 1 |
D4992A |
A.04.03 |
A.04.03 |
Yes (1) |
8G |
NeRaid |
D4943A |
A.04.03 |
A.04.03 |
Yes(1) |
8G |
LH3 Integrated |
N/A |
B.02.01 |
D.03.02 |
Yes |
8G |
LH4 Integrated |
N/A |
B.02.01 |
D.03.02 |
Yes |
|
NetRaid-4M |
See Table 7C |
||||
NetRaid-2M |
See Table 7D |
||||
NetRaid-1M |
See Table 7D |
||||
Mylex DAC |
N/A |
N/A |
N/A |
No |
N/A |
* There is no size limitation for non-boot drives.
(1) Must install adapter in BUS 0.
This table indicates Windows 2000 support for HP NetRAID disk array controllers, including, where appropriate, the recommended slot in which to install the adapter.
Model |
NetRAID-1 |
NetRAID |
NetRAID-3Si |
NetRAID-1Si |
LH 6000 |
No |
No |
Yes |
Yes |
LT 6000 |
No |
No |
Yes |
Yes |
LC 2000 |
No |
No |
Yes |
Yes |
LH 3000 |
No |
No |
Yes |
Yes |
LXr8000 |
Yes |
No |
Yes |
Yes |
LXr Pro8 |
Yes |
Yes |
Yes |
Yes |
LH4 |
Yes(1) |
No |
Yes |
Yes |
LH3 |
Yes(1) |
Yes(1) |
Yes |
Yes |
LPr |
Yes(3) |
Yes(3) |
Yes |
Yes |
LP 1000r |
No |
No |
No |
Yes |
LP 2000r |
No |
No |
No |
Yes |
LC3 |
Yes(4) |
Yes(4) |
Yes |
Yes |
E800 |
No |
No |
Yes |
Yes |
E60 |
No |
No |
Yes |
Yes |
E50 |
Yes |
Yes |
Yes |
Yes |
1 = slots 7,8 only
2 = Available Q299
3 = slots 1,2 only
4 = slots 5,6 only
List of NetServers that support the NeRAID-4M adapter with Windows 2000.
Model |
Min BIOS |
Max NetRAID-4M Supported |
Slotting preferences |
LPr |
4.06.32 PR |
1 |
Slot 1 (the top slot) because 2-3 do not get a PCI reset during a warm reboot. |
LP2000r |
TBD |
1 |
|
LH4 |
4.06.32 PS |
3 |
Slots 7-8 because 7-8 are 64 bit slots and 1-6 are 32 bit slots. |
LXr8000 |
Prod 12 |
4 |
Slots 7-10 because 7-10 are 64 bit slots, 1-6 are 32 bit slots, and 1-2 are typically used for the NIC and RMC. |
LXr8500 |
Prod 7 |
8 |
Slots 3-10 because 1-2 are typically used for the NIC and RMC. |
LC2000 |
4.06.23 PV |
2 |
Slots 5-6 because 5-6 are 64 bit slots, 1-4 are 32 bit slots, and 3-4 have insufficient air flow. |
LH3000 |
4.06.24 PT |
4 |
Slots 1-6 because 1-6 are 64 bit slots and 7-8 are 32 bit slots. |
LH6000 |
4.06.26 |
7 |
Slots 1-8 ok |
LT6000 |
4.06.26 |
2 |
Slots 2-6 ok. Slot 1 (the bottom slot) uses a special tray that is mechanically incompatible with the NetRAID-4M. |
List of NetServers that support the NeRAID-2M and 1M with Windows 2000.
Net-Server |
Min BIOS |
Max NetRAID-2M Supported |
Max NetRAID-1M Supported |
Slotting preferences |
LP 1000r |
TBD |
1 |
1 |
Slot 1 OK |
LP 2000r |
TBD |
1 |
2 |
Slot 1-3 OK |
LH3000 |
4.06.24 PT |
4 |
4 |
1M not supported on slot 4. |
LH6000 |
4.06.26 |
4 |
4 |
1M not supported on slot 4. |
LH3 |
4.06.36 PL 8/6/99 |
4 |
4 |
All slots |
LH4 |
4.06.27 PS 9/7/99 |
4 |
4 |
All slots |
This appendix describes how to perform a TopTool Agent install and/or an Instant TopTools install on a single server. This install process is similar to the TopTools install options available when installing an operating system using HP Navigator Installation Assistant program.
The first step to installing TopTools is to identify which TopTools product would be right for your server needs. If you install TopTool agents you will need TopTools Device Manager, Instant TopTools or an equivalent management program to retrieve and interpret information from the agents. Loading Instant TopTools on a system with agents will increase its management capabilities. Once you decide to install one or both TopTool products, then check to make sure your system is prepared for the TopTools installation. This document will guide you through the installation of SNMP services, TopTool Agents and Instant TopTools.
NOTE: If using DHCP the following page will shows "Obtain an IP address automatically" selected and the rest of the page is grayed out.
Insert the HP Netserver Navigator CD-ROM into your Windows NT system's CD-ROM drive and choose "Run" from the File menu in Program Manager, or the Start menu in Windows, and enter the following:
For TopTool Agents enter:
x
:\hpapps\iaa\language\nt\setupFor Instant TopTools enter:
x
:\hpapps\ia_itt\language\nt\setupWhere x: is the CD-ROM drive containing the HP NetServer Navigator CD-ROM and language is an abbreviation for your local language (US=English, FR=French, GE=German, IT=Italian, SP=Spanish, JP=Japanese).
Follow the instructions on the screen to setup the TopTools Agents and/or the Instant TopTools product.
Microsoft World Wide Web access: http://www.microsoft.com
HP World Wide Web access: http://www.hp.com
HP NetServer Online Documentation CD (included with your system): includes all NetServer documentation online