HP 441877-00B User Manual
HP Network Adapter Software and Configuration Guide
Part Number 441877-00B
March 2007 (Second Edition)
© Copyright 2005-2007 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP
shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor’s standard commercial license.
Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Windows Server 2003 is a trademark of Microsoft Corporation. Intel, Pentium, and Itanium are
trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other
countries. UNIX is a registered trademark of The Open Group.
Audience assumptions
This document is for the person who installs, administers, and troubleshoots servers and storage systems.
HP assumes you are qualified in the servicing of computer equipment and trained in recognizing hazards
in products with hazardous energy levels.
Contents
Overview..................................................................................................................................... 5
Supported adapters and operating systems................................................................................................... 5
Adapter driver and software information ......................................................................................................7
PCI Hot Plug ............................................................................................................................................. 9
Duplex support........................................................................................................................................ 10
Installation ................................................................................................................................. 13
Download latest drivers, firmware, and documentation ................................................................................ 13
Windows Server 2003 and Windows Server 2003 x64 .............................................................................. 13
Windows 2000 and Windows NT............................................................................................................15
Linux...................................................................................................................................................... 20
SCO OpenServer and UnixWare.............................................................................................................. 21
Solaris ................................................................................................................................................... 23
NetWare ...............................................................................................................................................28
Firmware upgrade utility.............................................................................................................. 48
Windows utility....................................................................................................................................... 48
c-Class BladeSystem utility ........................................................................................................................ 54
Linux utility .............................................................................................................................................54
DOS utility.............................................................................................................................................. 59
Adapter configurations................................................................................................................ 62
HP NC-Series Broadcom adapters .............................................................................................................62
Keywords for Q57 NDIS2 driver .....................................................................................................62
Keywords for B06 NDIS2 driver......................................................................................................63
PXE configuration: HP NC-series Broadcom and Multifunction adapters................................................ 64
HP NC-Series Multifunction adapters.......................................................................................................... 66
Accelerated iSCSI devices .............................................................................................................. 66
iSCSI boot configuration: Multifunction adapters ............................................................................... 67
PXE configuration: HP NC-series Broadcom and Multifunction adapters................................................ 67
HP NC-Series Intel adapters...................................................................................................................... 69
Boot Agent ................................................................................................................................... 69
Keywords for N100 NDIS2 driver ................................................................................................... 81
Keywords for N1000 NDIS2 driver .................................................................................................87
PXE configuration for HP NC-Series Intel adapters.............................................................................. 89
Windows ............................................................................................................................................... 91
Modifying adapter properties using the NCU.................................................................................... 91
Modifying HP NC-Series Broadcom and Multifunction adapter properties .............................................98
Modifying HP NC-Series Intel adapter properties............................................................................. 103
Modifying NC31xx Fast Ethernet adapter properties........................................................................ 106
Modifying adapter properties in Windows NT ................................................................................ 107
Novell Netware .................................................................................................................................... 110
Advanced Server Program for NetWare......................................................................................... 110
NetWare Client 32 driver installation for HP adapters...................................................................... 120
Solaris ................................................................................................................................................. 122
Team properties........................................................................................................................ 126
Adapter teaming...................................................................................................................................126
Contents 3
Multifunction gigabit server adapter teaming ............................................................................................129
Windows 2000 and Windows NT4 teaming............................................................................................130
NetWare teaming .................................................................................................................................139
VLAN properties....................................................................................................................... 150
VLAN information.................................................................................................................................. 150
ProLiant Essentials..................................................................................................................... 151
Networking pack installation .................................................................................................................. 151
Intelligent Networking Pack-Windows Edition............................................................................................ 151
Intelligent Networking Pack-Linux Edition ..................................................................................................152
Accelerated iSCSI for stand-alone and c-Class BladeSystem Multifunction server adapters .............................. 153
Accelerated iSCSI for embedded HP Multifunction server adapters ..............................................................153
Diagnostics .............................................................................................................................. 154
PCI shared interrupts.............................................................................................................................. 154
HP NC-Series Intel adapter diagnostics .................................................................................................... 154
HP NC-Series Broadcom adapter diagnostics............................................................................................ 156
HP NC-Series Broadcom Multifunction adapter diagnostics.........................................................................167
Technical support...................................................................................................................... 172
Before you contact HP............................................................................................................................ 172
HP contact information........................................................................................................................... 172
Free automated customer support services ................................................................................................172
Acronyms and abbreviations...................................................................................................... 174
Index....................................................................................................................................... 176
Contents 4
Overview
In this section
Supported adapters and operating systems ................................................................................................. 5
Adapter driver and software information..................................................................................................... 7
PCI Hot Plug ............................................................................................................................................ 9
Duplex support....................................................................................................................................... 10
Supported adapters and operating systems
Supported adapters
The Network Configuration Utility (NCU) supports the following HP Fast Ethernet and Gigabit Server
Adapters.
Standup adapters:
• HP NC110T PCI Express Gigabit Server Adapter
• HP NC150T PCI 4-port Gigabit Combo Switch Adapter
• HP NC310F PCI-X Gigabit Server Adapter
• HP NC320T PCI Express Gigabit Server Adapter
• HP NC340T PCI-X Quad Port Gigabit Server Adapter
• HP NC360T PCI Express Dual Port Gigabit Server Adapter
• HP NC364T PCI Express Quad Port Gigabit Server Adapter
• HP NC370T PCI-X Multifunction Gigabit Server Adapter
• HP NC370F PCI-X Multifunction Gigabit Server Adapter
• HP NC373F PCI Express Multifunction Gigabit Server Adapter
• HP NC373T PCI Express Multifunction Gigabit Server Adapter
• HP NC380T PCI Express Dual Port Multifunction Gigabit Server Adapter
• HP NC1020 Cu Gigabit Server Adapter 32 PCI Single Port
• HP NC3123 Fast Ethernet Server Adapter *
• HP NC3132 Fast Ethernet Upgrade Module (Dual 10/100) for the NC3134 Server Adapter *
• HP NC3133 100FX Upgrade Module for the NC3134 Server Adapter *
• HP NC3134 Fast Ethernet Server Adapter (Dual Base 10/100) *
• HP NC3135 Fast Ethernet Upgrade Module (Dual 10/100) for the NC3134 Server Adapter *
• HP NC6132 1000 SX Gigabit Upgrade Module for the NC3134 Server Adapter*
• HP NC6133 1000 LX Gigabit Upgrade Module for the NC3134 Server Adapter *
• HP NC6134 Gigabit Server Adapter (PCI 1000 SX)
Overview 5
• HP NC6136 Gigabit Server Adapter (PCI 1000 SX)
• HP NC6170 Dual Port PCI-X Gigabit Server Adapter
• HP NC6770 PCI-X Gigabit Server Adapter
• HP NC7131 Gigabit Ethernet Server Adapter
• HP NC7132 Gigabit Ethernet Upgrade Module for the NC3134 Server Adapter *
• HP NC7170 Dual Port PCI-X Gigabit Server Adapter
• HP NC7770 PCI-X Gigabit Server Adapter
• HP NC7771 PCI-X Gigabit Server Adapter
Embedded adapters:
• HP NC320i PCI Express Gigabit Server Adapter
• HP NC324i PCI Express Dual Port Gigabit Server Adapter
• HP NC325i PCI Express Dual Port Gigabit Server Adapter
• HP NC326i PCI Express Dual Port Gigabit Server Adapter
• HP NC370i PCI-X Multifunction Gigabit Server Adapter
• HP NC371i PCI-X Multifunction Gigabit Server Adapter
• HP Embedded NC373i Multifunction Gigabit Server Adapter
• HP NC3161 Fast Ethernet Server Adapter *
• HP NC3163 Fast Ethernet Server Adapter *
• HP NC7760 PCI-X Gigabit Server Adapter
• HP NC7761 PCI-X Gigabit Server Adapter
• HP NC7780 Gigabit Server Adapter
• HP NC7781 PCI-X Gigabit Server Adapter
• HP NC7782 Dual Port PCI-X Gigabit Server Adapter
Mezzanine adapters:
• HP NC320m PCIe Gigabit Server Adapter
• HP NC325m PCI Express Quad Port 1Gb Server Adapter for c-Class BladeSystem
• HP NC326m PCI Express Dual Port 1Gb Server Adapter for c-Class BladeSystem
• HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter for c-Class BladeSystem
• HP NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter
* Not supported in Windows Server 2003 x64
Supported operating systems
These server adapters are supported on the following operating systems.
Microsoft
• Windows Server 2003 x64 Editions
• Windows Server 2003
Overview 6
• Windows® 2000 (NDIS5)
• Windows NT® 4.0 (NDIS4) (only supported on adapters that shipped before January 1, 2003)
• DOS NDIS2*
NetWare
• NetWare 6.5 Server
• NetWare 6.6 Server
• NetWare Open Enterprise Server
Linux 32
• Red Hat Enterprise Linux 5
• Red Hat Enterprise Linux 4
• Red Hat Enterprise Linux 3
• SUSE Linux Enterprise Server 10 Service
• SUSE Linux Enterprise Server 9 Service
Linux 64
• Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T
• Red Hat Enterprise Linux 4 for AMD64 and Intel EM64T
• Red Hat Enterprise Linux 3 for AMD64 and Intel EM64T
• SUSE Linux Enterprise Server 10 for AMD64 and Intel EM64T
• SUSE Linux Enterprise Server 9 for AMD64 and Intel EM64T
UNIX
• Unixware 7.x
• OpenUnix 8.x
• Open Server 5.x/6.x
Solaris
• Solaris 10
• Solaris 9
* Unattended Install Only. Also, DOS NDIS2 is not supported for NC3133 adapters.
Adapter driver and software information
To obtain driver and software information for Microsoft® Windows Server 2003 x64, Microsoft®
Windows Server 2003, Microsoft® Windows® 2000, Microsoft® Windows NT® (4.0), Novell
NetWare, SCO OpenServer, UnixWare, Linux, and Solaris:
1. Go to the HP website (http://www.hp.com).
2. Click Software & Driver Downloads from the left menu bar.
3. Type the product name in the For product box and press Enter. For example, type NC370T.
4. Select an operating system.
Overview 7
5.
Click HP ProLiant Networking Software.
6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The
SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.
7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.
Drivers
Drivers are found in the following folders:
• Microsoft® Windows Server 2003 \WIN2003
• Microsoft® Windows Server 2003 x64 \WIN2003x64
• Microsoft® Windows® 2000 \WIN2000
• Microsoft® Windows NT® 4.0 \NT4
• Novell NetWare \NETWARE\SERVER
• Linux \LINUX
• UnixWare 7.x and OpenServer 6.x \UNIX\UNIXWARE7_OPENSERVER6
• Solaris 9 and Solaris 10 \SOLARIS
• Unattended Install \DOS
Supplemental applications in \APPS
• Boot agent
• Diagnostic tests including MFDIAG.exe, N100X.exe and Q57.exe
• Online firmware upgrade utility
• Multifunction firmware upgrade utility
• c-Class BladeSystem firmware upgrade utility
• Linux firmware upgrade utility
Device-specific information
See \docs\files.txt for a descriptive list of all files in the SoftPaq.
Release notes and other documentation in \docs
• HP Accelerated iSCSI for Multifunction Network Adapters (AiSCSIUG.pdf)
• HP Network Adapter License Utility for Windows (NALICNSE.pdf)
• HP Network Adapter Scripting Utility (NICSCRPT.pdf)
• HP Network Configuration Agent (ncuasr.pdf)
• HP ProLiant Essentials Intelligent Networking Pack–Linux Edition (PEINPL.pdf)
• HP ProLiant Essentials Intelligent networking Pack–Windows Edition (PEINPW.pdf)
• HP Virus Throttle for Windows License Utility (VTLICNSE.pdf)
• HP NC510x PCIe 10 Gb Software Configuration Guide (NC510x PCIe 10 Gb Software Guide.pdf)
• Network adapter user guides (\docs\hw)
• Release notes (Relnotes.txt)
• SetLACState Utility (SetLAC.pdf)
Overview 8
Linux documentation
• Linux readme.txt file is located in the \LINUX directory
• HP iSCSI Boot User Guide for Linux in the \docs directory
PCI Hot Plug
PCI Hot Plug is an industry-standard solution that provides increased system availability and non-stop
serviceability in business-critical computing environments. PCI Hot Plug enables PCI networking adapters
to be replaced or added to a server without taking the system down. HP pioneered this technology and
has worked closely with the PCI Special Interest Group (SIG) and several key industry partners to
accelerate its adoption as an industry standard. PCI Hot Plug technology also has a broad range of
industry support from leading operating system suppliers including Microsoft® and Novell.
HP server adapters support PCI Hot Plug technology. To take advantage of this solution, you must use the
adapter in an HP or third-party system that supports PCI Hot Plug. To implement PCI Hot Plug, use the
configuration instructions that come with your system. If you use an HP system that supports PCI Hot Plug,
refer to the documentation for configuring and installing PCI Hot Plug devices in the HP SmartStart
application, which ships with HP systems.
If you use a third-party system that supports PCI Hot Plug, refer to the documentation that came with your
system or contact technical support for the vendor.
Support for enabling PCI Hot Plug
Different operating systems support PCI Hot Plug in different ways. The following list describes how
different operating systems enable PCI Hot Plug devices.
• Windows® 2000, Windows Server 2003, and Windows Server 2003 x64
o Can replace like item for like item
o Can add a new adapter to an empty slot
o Can add an option module to an existing NC3134 adapter
• Windows NT® 4.0
o Can replace like item for like item
o Cannot add a new adapter to an empty slot
• NetWare 6.x
o Can replace like item for like item
o Can remove an adapter
o Can add a new adapter to an empty slot
o Can add an option module to an existing NC3134 adapter (This feature is not supported on an
NC3134 adapter that has a persistent driver installed.)
• UnixWare 7.x and OpenServer 6.x
Requires hardware that implements PCI Hot Plug failover and a DDI 8 MDI driver that implements the
CFG_SUSPEND and CFG_RESUME subfunctions to the entry point routine. This lets the system
administrator suspend the driver, power down the slot, hot-swap or hot-replace the adapter, power
up the slot, and resume the driver, all without bringing the machine down. For further information
about PCI Hot Plug support, refer to your UNIX documentation.
• SCO OpenServer 5.x
Overview 9
No support
• Linux
No support
Upgrading the adapter with a persistent driver
To upgrade the adapter with a persistent driver:
1. Manually remove (unload) the driver.
2. Power down the slot and remove the adapter.
3. Upgrade the adapter (add the option module).
4. Reinstall the upgraded adapter.
5. Power up the slot to let NetWare automatically detect the (upgraded) adapter.
Duplex support
Duplexing is a performance option that allows you to choose how the adapter sends and receives packets
over the network. Duplex options include:
• Auto. (Auto-negotiation) The adapter negotiates with the full-duplex switch to send and receive
packets at the highest rate. The switch must support auto-negotiation. If the switch does not support
auto-negotiation, the adapter defaults to half-duplex.
NOTE: An exception is the HP NC3133 adapter, which defaults to full-duplex.
• Full-duplex. (Requires full-duplex switch) The adapter sends and receives packets simultaneously by
using a different wire to perform each function. This feature can improve adapter performance by
eliminating collisions. Set duplex mode to full-duplex ONLY if you have a hub/switch that supports
full-duplex.
• Half-duplex. The adapter performs one operation at a time (because send and receive lines are
shared); it either sends or receives.
Configuring for full-duplex
If you have an auto-negotiating switch, the adapter automatically matches the duplex setting at the switch.
If you do not have an auto-negotiating switch, you must manually configure the adapter for full-duplex
support.
Configuration is specific to the driver you are loading for your network operating system (NOS). To set up
the duplex mode, refer to the section below that corresponds to your operating system. Note that
performance may suffer if your switch is not full-duplex and you configure the adapter to full-duplex. Leave
the adapter on half-duplex if you are not sure what type of switch to which you are connected.
Windows NT® 4.0
To set the duplex options:
1. Double-click the HP Network icon in the Control Panel. Or, right-click on Network Neighborhood
and select Properties. Then select the Adapters tab. Double-click on an adapter or team to launch the
CPQNTAC utility.
2. Select an adapter from the list and click Properties.
Overview 10
3.
Set Speed/Duplex on the adapter to Auto/Auto, 10/Half, 10/Full, 100/Half, 100/Full, or
1000/Full.
4. Click OK until prompted to restart.
5. Restart Windows NT® 4.0.
Windows® 2000, Windows Server 2003, and Windows Server 2003 x64
For new installations, Windows® 2000 automatically installs the adapter drivers. Exception: For the
NC150T, NC310F, NC32xx, NC37xx, NC340x, NC1020, NC6136, NC6170, NC71xx and
NC77xx adapters, you must install the appropriate driver components located in the \WIN2000
directory in the HP SoftPaq. Complete the following steps to download the SoftPaq file.
1. Go to the HP website (http://www.hp.com).
2. Click Software & Driver Downloads from the left menu bar.
3. Type the product name in the For product box and press Enter. For example, type NC370T.
4. Select an operating system.
5. Click HP ProLiant Networking Software.
6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The
SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.
7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.
NOTE: If you need to update existing Windows® 2000 drivers, refer to the instructions in
Windows 2000 installation notes ("Windows 2000 and Windows NT" on page 15).
To set the duplex options:
1. Launch the Network Configuration Utility.
2. Select an adapter from the list in the NCU Main window and click Properties. The Adapter
Properties window appears.
3. On the Settings tab, set the Speed/Duplex Setting for the adapter to Auto/Auto, 10/Half, 10/Full,
100/Half, 100/Full, or 1000/Full.
4. Click OK twice to accept the configuration changes.
NetWare Server
To set the duplex options, use the following syntax for FORCEDUPLEX and SPEED.
NOTE: The NC340T, NC1020, NC71xx, and NC77xx adapters support full-duplex and half-
duplex. The fiber Gigabit adapters support full-duplex mode only and cannot be changed.
• Syntax: FORCEDUPLEX=n
Where n =
0–auto-negotiation (You must have an auto-negotiating switch/hub (an Nway* switch) to get full-
duplex support with the FORCEDUPLEX parameter set to 0 (auto-negotiation).
1–half-duplex
2–full-duplex
NOTE: To set the adapter to half- or full-duplex, you must set the SPEED parameter to either 10
or 100.
Default = auto-negotiate
Overview 11
Examples:
o 100 Mbps full-duplex: FORCEDUPLEX=2 SPEED=100
o 10 Mbps full-duplex: FORCEDUPLEX=2 SPEED=10
• Syntax: SPEED= n (n = 10 or 100 or 1000)
Specifies the speed the driver uses. If you do not use this parameter, the driver automatically detects
the network speed. If unable to detect the network speed, the driver defaults to 10 Mbps. If you use
this parameter, the driver operates at the specified speed instead of auto-detecting network speed.
NOTE: The NC3133 adapter supports 100 Mbps only. It does not default to 10 Mbps. You
must set the SPEED parameter to either 10 or 100 if you want to set the FORCEDUPLEX
parameter to either half or full. The SPEED parameter is for N100.LAN driver and
N1000.LAN. You cannot change the speed for the Gigabit (fiber) adapters. You can,
however, change the speed for the NC7131 and NC7132 Gigabit (copper) adapters to 10
Other NDIS 2.x-based clients
To set the duplex options in other NDIS 2.x-based clients, edit the PROTOCOL.INI file. Add the
FORCEDUPLEX and SPEED parameters to the N100 section, or the SPEEDUPLEX parameter to the N1000
section. For information on these parameters, refer to Keywords for N100 NDIS2 driver (on page 81) ,
Keywords for N1000 NDIS2 driver (on page 87), or Keywords for Q57 NDIS2 driver (on page 62).
Mbps or 100 Mbps.
Default = The adapter automatically senses speed.
Overview 12
Installation
In this section
Download latest drivers, firmware, and documentation............................................................................... 13
Windows Server 2003 and Windows Server 2003 x64 ............................................................................ 13
Windows 2000 and Windows NT........................................................................................................... 15
Linux..................................................................................................................................................... 20
SCO OpenServer and UnixWare............................................................................................................. 21
Solaris .................................................................................................................................................. 23
NetWare .............................................................................................................................................. 28
Download latest drivers, firmware, and documentation
HP updates networking software frequently to include new functionality and features. For the latest driver,
firmware, and documentation updates go to the HP website
(http://h18004.www1.hp.com/products/servers/networking/index.html
).
Windows Server 2003 and Windows Server 2003 x64
The following provides information about Windows Server 2003 and Windows Server 2003 x64 support
for HP NC-series network adapters.
Windows Server 2003
The following Windows Server 2003 network adapter drivers are used in this release:
• N100325.sys for NC31xx Fast Ethernet server adapters
• N1000325.sys for NC310xx, NC340x, NC61xx, and NC71xx server adapters
• Q57XP32.sys for NC150x, NC32xx, NC10xx, NC67xx, and NC77xx server adapters
• N1E5132.sys for NC110T, NC360x, NC364x server adapters
• BXND51X.sys for all Multifunction server adapters
• NXP2NIC.sys for NC510x 10 Gb server adapters
Components for these drivers are located in the \WIN2003 directory in the HP SoftPaq. Complete the
following steps to download the SoftPaq file.
1. Go to the HP website (http://www.hp.com).
2. Click Software & Driver Downloads from the left menu bar.
3. Type the product name in the For product box and press Enter. For example, type NC370T.
4. Select an operating system.
Installation 13
5.
Click HP ProLiant Networking Software.
6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The
SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.
7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.
Windows Server 2003 x64
IMPORTANT: NC31xx, NC6132, NC6133, and NC7132 adapters are not supported in
Windows Server 2003 x64.
The following Windows Server 2003 x64 network adapter drivers are used in this release:
• N1G5132E.sys for NC310F, NC340T, NC61xx, and NC71xx server adapters
• Q57AMD64.sys for NC150T, NC32x, NC1020, NC67xx, and NC77xx server adapters
• BXVBDA.sys for Multifunction server adapters
• N1E5132E.sys for NC110T, NC360T, NC364x server adapters
• NXP2NIC.sys for NC510x 10 Gb server adapters
Components for these drivers are located in the \WIN2003x64 directory in the HP SoftPaq. Complete
the following steps to download the SoftPaq file.
1. Go to the HP website (http://www.hp.com).
2. Click Software & Driver Downloads from the left menu bar.
3. Type the product name in the For product box and press Enter. For example, type NC370T.
4. Select an operating system.
5. Click HP ProLiant Networking Software.
6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The
SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.
7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.
Installing network drivers (new installations)
When you install the adapter in the server for the first time:
1. Connect the cable from the adapter to your network.
2. Provide power to your server.
3. Start Windows Server 2003 or Windows Server 2003 x64 .
o For the NC150T, NC310F, NC32xx, NC340x, NC37xx, NC380x, NC1020, NC6136,
NC6170, NC6770, NC71xx, and NC77xx server adapters, you must install the appropriate
driver component located in the \WIN2003 or \WIN2003x64 directory in the HP SoftPaq file.
o For all other adapters, Windows® automatically detects and installs a driver for the adapter from
its own library of drivers.
Updating network drivers
To update the network driver, follow these instructions:
Locate the driver on the CD, diskette, or directory on your hard drive where you copied it from an
updated source. See Technical Support for a list of online sources for software and driver updates.
Installation 14
Run the appropriate Driver Component Package (listed as CPxxxxxx.exe) in a directory on your hard
1.
drive. The component is a self-extracting executable with a file name based on the component
number.
2. Click the Install button to proceed with the installation.
3. After the drivers have been installed, you may delete the Component Package that you copied.
Removing the driver software
To remove the driver software:
1. Before physically removing an adapter from your system, first remove the adapter driver software.
2. Start Windows Server 2003 or Windows Server 2003 x64 and log in. You must have Network
Administrator privileges to remove the driver software.
3. Open the Control Panel and double-click the System icon. In the System Properties dialog box,
select the Hardware tab.
4. Click Device Manager. The Device Manager window appears.
5. Click the plus (+) sign to expand the Network adapters. All network adapters appear.
6. Right-click the adapter to be removed and choose Uninstall.
NOTE: Not all driver files are removed as part of this procedure. The driver and adapter can
be removed via Hot Plug, if supported.
Windows 2000 and Windows NT
The following provides information about Windows 2000 support for HP NC-series network adapters.
The following Windows 2000 network adapter drivers are used in this release:
• N100NT5.sys for NC31xx Fast Ethernet server adapters
• N1000NT5.sys for NC310x, NC340x, NC61xx, and NC71xx Gigabit Ethernet server adapters
• Q57W2K.sys for NC150x, NC32xx, NC10xx, NC67xx, and NC77xx Gigabit Ethernet server
adapters
• BXVBDX.sys for Multifunction Gigabit server adapters
• N1E5032.sys for NC360x and NC364T Gigabit Ethernet server adapters
Components for these drivers are located in the \WIN2000 directory in the HP SoftPaq file.
Installing network drivers (new installations)
When you install the adapter in the server for the first time:
1. Connect the cable from the adapter to your network.
2. Provide power to your server.
3. Start Windows Server 2003 or Windows Server 2003 x64 .
o For the NC150T, NC310F, NC32xx, NC340x, NC37xx, NC380x, NC1020, NC6136,
NC6170, NC6770, NC71xx, and NC77xx server adapters, you must install the appropriate
driver component located in the \WIN2003 or \WIN2003x64 directory in the HP SoftPaq file.
o For all other adapters, Windows® automatically detects and installs a driver for the adapter from
its own library of drivers.
Updating network drivers from disk
Installation 15
To update the network driver, follow these instructions:
Locate the driver on the CD, diskette, or directory on your hard drive where you copied it from an
updated source. See Technical Support for a list of online sources for software and driver updates.
1. Run the appropriate Driver Component Package (listed as CPxxxxxx.exe) in a directory on your hard
drive. The component is a self-extracting executable with a file name based on the component
number.
2. Click the Install button to proceed with the installation.
3. After the drivers have been installed, you may delete the Component Package that you copied.
Windows NT4 unattended install (push)
The following provides information about Windows NT support for HP NC-series network adapters.
Overview
The primary objective of the Push Installation is to get the client properly connected to the Windows NT®
server before the installation begins using the NDIS2 driver, and to keep the same client connected using
the NDIS4 driver after the Windows NT® server is installed without any end-user action.
The difficulty is that the list of supported adapters on the Windows NT® 4.0 CD-ROM is restricted and
special steps must be performed to update the installation source files and modify the scripts to automate
the process for the adapters not on the list.
Main steps of the process
1. Create a Network Installation Startup disk from the Windows NT® server and modify it for your
adapter.
2. Create a shared directory for the Windows NT® server installation files on the Windows NT®
server.
3. Modify the UNATTEND.TXT installation script to automate the procedure and add the proper
adapter installation and configuration information.
The sample UNATTEND.TXT file, provided in Item 4 of the "Samples and Templates" section,
indicates how to override default registry parameters for the adapter in the [CPQNic1ParamSection]
section. The override parameters should not be used unless the default parameters will not work
properly for a specific installation. The sample parameters are commented out.
4. Integrate the adapter driver files into the Windows NT® installation source files.
5. Perform the Unattended Installation bootup with the prepared startup disk from the client system.
Performing an unattended installation on Windows NT 4.0
1. Prepare a Windows NT® 4.0 server:
a. Create a folder on the server hard disk for the installation files (for example, NT40.INS). Make
this folder shared (for example, with shared name NT40.INS).
b. Create a user (for example, USERID with a password password) and grant read and view rights
for the NT40.INS folder.
2. Use a CD-ROM drive at the Windows NT® server and copy the i386 folder with Windows NT® 4.0
installation files to the shared folder NT40.INS on this server (for example, using NT Explorer).
3. Create or modify the installation answer file UNATTEND.TXT as required by your specific system and
desired Windows NT® configurations. UNATTEND.TXT may be read-only and may need to be
made write-able before editing (for example, attrib -r unattend.txt). Refer to the sample
UNATTEND.TXT file with comments.
4. Create the \CPQANC directory: NT40.INS\i386\DRVLIB.NIC\CPQANC.
Installation 16
Copy driver installation files: Xcopy the HP Configuration and Drivers Disk to the proper location
5.
under Adapter Device Driver folder (NT40.INS\i386\DRVLIB.NIC\CPQANC folder on the
Windows NT® server). This enables the installation program to find the same file structure as on the
Drivers disk. Be sure to use the /s /e switches on xcopy.
6. On the Windows NT® server, prepare the Microsoft® Client Installation disk using the Windows
NT® Network Client Administrator:
a. Prepare a system diskette (for example, DOS 6.22: format a: /s). Do not use the Windows NT®
system disk.
b. Copy UNATTEND.TXT from \NT40.INS\i386 to the diskette as specified in item 3 above
(preferably to the root (a:\)). The best location to put this file is in the root of your install disk, but
the only requirement is to specify the full path to this file in the AUTOEXEC.BAT for the WINNT
command.
c. Use the Windows NT® Administrative Tools (Common), start Network Client Administrator and
select Make Network Installation Startup Disk.
d. Set "Existing Path" to use the previously installed software for MS Client or, if it is the first time,
create the shared directory on the server's hard drive, using the Windows NT® 4.0 Server CDROM as a source (for example, by copying from \client on the CD-ROM to c:\client).
e. Choose Network Client v3.0 for MS-DOS and Windows.
f. Choose any of the Network Adapters from the list (for example, NE2000 compatible).
g. Set Computer name, User name, Domain and Network protocol when prompted.
h. Select OK and wait while files are copied to the disk.
i. Copy the proper ndis2 dos driver (N100.DOS, N1000.DOS, or Q57.DOS) to this disk in the
\NET directory. N100.DOS, N1000.DOS, Q57.DOS can be found in \DOS\NDIS2\ in the HP
SoftPaq file.
j. Modify A:\NET\SYSTEM.INI : netcard=N100.DOS (or N1000.DOS or Q57.DOS).
k. Modify A:\NET\PROTOCOL.INI : drivername=N100$ (or N1000$ or Q57$).
l. Add a line: CACHEFLUSH=1 just after the "drivername = N100$" line.
m. Verify or modify A:\AUTOEXEC.BAT to have the following commands:
NET USE W: \\ServerName\NT40.INS
W:\WINNT /s:W:\ /u:a:\unattend.txt
Note that W is an example for the logical drive mapped to the share on the Windows NT®
server.
n. Remove the invocation of setup.exe from A:\AUTOEXEC.BAT.
7. Insert the startup disk and boot up your DOS client. After connecting to the network. do one of the
following:
o Input USERID as a User name when prompted. Input password as a password when prompted.
o Modify the NET START line in the AUTOEXEC.BAT to NET LOGON USERID PASSWORD /YES.
Samples and templates
• PROTOCOL.INI
[network.setup]
version=0x3110
netcard=ms$ne2clone,1,MS$NE2CLONE,1
;transport=ms$ndishlp,MS$NDISHLP
Installation 17
;transport=ms$netbeui,MS$NETBEUI
;lana0=ms$ne2clone,1,ms$netbeui
;lana1=ms$ne2clone,1,ms$ndishlp
transport=tcpip,TCPIP
lana0=ms$ne2clone,1,tcpip
[ms$ne2clone]
drivername=N100$
CACHEFLUSH=1
; CACHEFLUSH line is required ONLY IF NDIS2 does not shut down
; properly
;INTERRUPT=3
;IOBASE=0x300
;SlotNumber=1
[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP
;[MS$NDISHLP]
;drivername=ndishlp$
;BINDINGS=ms$ne2clone
;[ms$netbeui]
;drivername=netbeui$
;SESSIONS=10
;NCBS=12
;BINDINGS=ms$ne2clone
;LANABASE=0
[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=255 255 0 0
IPAddress0=137 65 10 12
DisableDHCP=1
DriverName=TCPIP$
BINDINGS=ms$ne2clone
LANABASE=0
• SYSTEM.INI
[network]
filesharing=no
printsharing=no
autologon=yes
computername=COMPUTERNAME
lanroot=A:\NET
username=Administrator
workgroup=DOMAIN
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=DOMAIN
preferredredir=full
autostart=full
maxconnections=8
Installation 18
[network drivers]
netcard=N100.DOS
;transport=ndishlp.sys,*netbeui
transport=tcpdrv.dos,nemm.dos
devdir=A:\NET
LoadRMDrivers=yes
[Password Lists]
*Shares=a:\net\Share000.PWL
USERID=A:\NET\USERID.PWL
• AUTOEXEC.BAT
path=a:\net
a:\net\net start
rem a:\net\net logon userid password /yes
net use W: \\ServerName\nt40.ins
W:winnt /s:W:\ /u:a:\unattend.txt
• UNATTEND.TXT
[Unattended]
OemPreinstall = yes
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
FileSystem = LeaveAlone
ExtendOEMPartition = 0
ConfirmHardware = no
NtUpgrade = no
Win31Upgrade = no
TargetPath = winnt
OverwriteOemFilesOnUpgrade = no
OemSkipEULA = yes
[GuiUnattended]
OemSkipWelcome = 1
OEMBlankAdminPassword = 1
TimeZone = "(GMT-08:00) Pacific Time (US & Canada)"
[UserData]
FullName = "Userid"
OrgName = "Organization"
ComputerName = COMPUTER
ProductId = "xxx-xxxxxx"
[Display]
ConfigureAtLogon = 0
BitsPerPel = 8
XResolution = 640
YResolution = 480
VRefresh = 60
AutoConfirm = 1
[Network]
InstallAdapters = CPQAdapters
InstallProtocols = ProtocolsSection
Installation 19
InstallServices = ServicesSection
JoinWorkgroup = workgroup
[ProtocolsSection]
TC = TCParamSection
[TCParamSection]
DHCP = yes
[CPQAdapters]
CPQANC.1 = CPQNic1ParamSection, \i386\drvlib.nic\CPQANC
;CPQANC.2 = CPQNic2ParamSection, \i386\drvlib.nic\CPQANC
;CPQANC.3 = CPQNic3ParamSection, \i386\drvlib.nic\CPQANC
;CPQANC.4 = CPQNic4ParamSection, \i386\drvlib.nic\CPQANC
[CPQNic1ParamSection]
;NetAddress = "" ;SpeedDuplex = 0 ; 0 means autonegotiation
;MaxFrameSize = 0 ; 0 is use card default (1514)
[ServicesSection]
References
• Microsoft® Windows NT® Resource Kit—Microsoft® Press 19NT
• Microsoft® TechNet CD-ROM, April 1997
• Microsoft® support web page at http://support.microsoft.com/support Article ID : Q155197,
Linux
The following Linux drivers are available for HP adapters:
• tg3—Supports NC150x, NC320x, NC324x, NC325x, NC326x, NC1020, NC67xx, and
• e1000—Supports NC110T, NC310F, NC340x, NC360x, NC364T, NC61xx, and NC71xx server
• hp-pel—Supports ProLiant Essentials Licensing package
• hp-vt—Supports Virus Throttle for NCxxxx adapters
• iSCSI-boot—Supports the HP iSCSI boot feature that allows booting a server over iSCSI
• unm—Supports HP NC510x PCIe 10 Gigabit Adapter driver
The drivers are distributed in source RPM format and are available in the HP SoftPaq file in the \Linux
directory. Complete the following steps to download the HP SoftPaq.
1. Go to the HP website (http://www.hp.com).
Q156795
NC77xx server adapters
adapters
2. Click Software & Driver Downloads from the left menu bar.
3. Type the product name in the For product box and press Enter. For example, type NC370T.
4. Select an operating system.
5. Click HP ProLiant Networking Software.
6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The
SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number.
Installation 20
7.
Click the SoftPaq file to extract the files and then open the cmponent.htm file.
In addition, the Linux (open source) drivers can be found at the HP software and drivers website
(http://h18000.www1.hp.com/support/files/index.html
).
HP ROMPaqs for specific servers can be found at the HP support website (http://www.hp.com/support
The source RPM is suitable for use on any system that has the RPM utility installed and a properly
configured kernel source tree.
SCO OpenServer and UnixWare
SCO OpenServer 5.x, 6.x, and UnixWare 7.x drivers are provided in the following locations:
• HP SoftPaq file at the HP website (http://www.hp.com).
• HP EFS 7.64A for UnixWare 7.x and OpenServer 6.x, and HP EFS 5.64A for SCO OpenServer 5.x
at the HP website (http://www.hp.com
HP Extended Feature Supplement (EFS) is a collection of device drivers that provide maximum
performance for HP servers. The EFS also includes several utilities to monitor and increase the
performance of your HP server.
SCO OpenServer 5.x
This procedure describes the installation of the SCO OpenServer driver. This driver is released as a media
image file containing the driver package. The media image file can be copied to the target machine
directly for installation or from an installation diskette that you can create.
Creating a diskette
1. Copy the file VOL.000.000 to a Caldera system.
).
).
2. Create a diskette using: dd if =VOL.000.000 of=/dev/rfd0135ds18.
Installing the driver
To install the driver:
1. Use custom or scoadmin software to install the SCO OpenServer driver from the media image or
from the diskette created above.
2. Use netconfig to add the new network adapter.
3. Modify the hardware configuration in Advanced Options to change the Line Speed and Flow
Control if desired. The settings for these parameters are listed below:
o Line Speed
AutoNegotiate (default)
HalfDuplex10
FullDuplex10
HalfDuplex100
FullDuplex100
FullDuplex1000
o Flow Control
Off (default)
AutoNegotiate (Symmetric Pause advertised)
Installation 21
RxPause
TxPause
RxPause/TxPause
NOTE: 1000 Mbps (1 Gbps) full-duplex fixed speed is only valid for fiber connections. For
copper, twisted-pair connections, 1 Gbps can only be set through auto-negotiation with a 1
Gbps partner.
NOTE: Auto-negotiation of Flow Control is only valid when the Line Speed is set to
AutoNegotiate.
NOTE: A kernel relink and reboot is required before the new configuration will take effect.
For more detailed information and tuning parameters, at the command prompt enter:
man bcme
Jumbo Frames and other advanced parameters
Jumbo MTU sizes and other advanced, tunable parameters for the controller are located in the file
space.c in the directory /etc/conf/pack.d/bcme. A description for each parameter is contained in
space.c. Modify the desired parameter in space.c, rebuild the kernel, and reboot the system. The MTU
sizes can be individually set for each adapter in the system (Jumbo Frames is not supported on the
NC1020). All other parameters apply globally to all adapters.
UnixWare 7.x and OpenServer 6.x
The following procedure describes the installation of the UnixWare driver. The driver is released as a
PKG file.
Installing the driver locally
1. Copy the file bcme-<version>.pkg to a UnixWare 7.x system.
2. Enter the following command: pkgadd -d <path><filename> where <path> is the directory to which
the PKG file was copied.
Creating a diskette
1. Copy the file bcme-<version>.pkg to a Caldera system.
2. Create a diskette using the following command: dd if=bcme-<version>.pkg of=/dev/fd0
Installing the driver from a diskette
1. Use pkgadd -d diskette1 to install the bcme package.
2. Use netcfg or scoadmin network to add the new network adapter.
3. When prompted, select the Line Speed and then select Advanced Option for Flow Control, MAC
Address, and Jumbo MTU Size settings, if desired. The settings for these parameters are listed
below:
o Line Speed
Auto Negotiation (default)
10 Mbps half-duplex
10 Mbps full-duplex
100 Mbps half-duplex
Installation 22
100 Mbps full-duplex
1000 Mbps full-duplex
o Flow Control
Disabled (default)
Auto Negotiation (Symmetric Pause advertised)
Receive Pause
Transmit Pause
Receive & Transmit Pause
o MAC Address
No Override (default) - a user-administered MAC address entered with a colon separating each
hexadecimal byte (for example, 12:34:56:78:9a:bc).
o Jumbo MTU Size
1500–9000 (default is 1500)
For more detailed information, at the command prompt, enter:
Solaris
The following describes the Solaris driver for HP 10/100/1000 Mbps Network Server Adapters. The
driver is released in two formats:
• BRCMbcme.pkg: Datastream format
• bcmedu.img: Driver Update (DU) binary image which is used to create DU diskette.
Installing the driver
1. Change directory to where BRCMbcme.pkg resides.
2. pkgadd -d BRCMbcme.pkg
3. Execute prtconf to determine instance number of the adapter.
man bcme
NOTE: 1000 Mbps (1 Gbps) full-duplex fixed speed is only valid for fiber connections. For
copper, twisted-pair connections, 1 Gbps can only be set through auto-negotiation with a 1
Gbps partner.
NOTE: Auto-negotiation of Flow Control is only valid when the Line Speed is set to
AutoNegotiate.
4. ifconfig bcme [instance_number] plumb
5. ifconfig bcme [instance_number] ip_address netmask ....
To make these changes permanent:
1. Use your favorite text editor (for example, VI), and create a file named
hostname.bcme[instance_number] in /etc directory. Add the IP address of the interface to this file,
save and exit.
2. Add a proper subnet mask to the file /etc/netmasks.
Installation 23
In Solaris 7.0 (Intel platform), the operating system only allocates 36 pages of 4K physically contiguous
memory. The driver needs approximately 130K of physically contiguous memory per adapter. In order to
use more than one adapter, the operating system must allocate more memory. This can be done by setting
the operating system variable, "lomempages" in /etc/system.
For example, if four adapters are installed in a Solaris 7 system, physically contiguous memory is
calculated as follows:
4 adapters * 130K = 520K
130 pages of 4K is required.
Since this memory might be used by another driver in the system, 200 of 4K memory is allocated. Add
the following line in the /etc/system file:
set lomempages=200
Uninstalling the driver
To uninstall the driver:
1. ifconfig bcme [instance_number] down
2. ifconfig bcme [instance_number] unplumb
3. pkgrm BRCMbcme
Driver update (DU) diskette instruction (Intel® Platform Only)
This area contains the Solaris diskette image files, and the instructions to create diskettes from these image
files.
1. Insert a blank diskette into the diskette drive of your system, and type one of the following commands
to format it:
o If you are using DOS, type: format A:
o If you are using the Solaris operating environment, type: fdformat -Ud
2. Check to see if Volume Management is running:
a. Do one of the following:
If you are using DOS, type:
dd filename A:
If you are using the Solaris operating environment, type:
volcheck
ls -l /vol/dev/aliases/floppy0
b. If you see a message similar to this:
lrwxrwxrwx 1 root 34 Jan 21 17:28
/vol/dev/aliases/floppy0 ->
/vol/dev/rdiskette0/unnamed_floppy
Type:
dd if=bcmedu.img of=/vol/dev/aliases/floppy0
bs=36k eject floppy0
c. If you see this message:
/vol/dev/aliases/floppy0 not found
Type:
Installation 24
dd if=bcmedu.img of=/dev/rdiskette bs=36k
Installing Solaris DU dskettes
You can use Solaris DU diskettes in the following ways:
• To use new drivers to install or upgrade the Solaris operating system environment on a system with
new hardware.
• To add new drivers to support new hardware on an already installed and booted system.
Installing Solaris using DU diskettes
To install Solaris (Intel Platform Edition) using drivers on the DU diskette:
1. Insert the appropriate configuration Assistant diskette, made from the included bcmedu.img file, into
your system's disk drive. Also, insert the Solaris Installation CD-ROM or, for network installation,
verify with your system administrator that the Solaris network installation image is available on your
network.
2. Power on your system.
3. When the Configuration Assistant screen is displayed, select the F4 option (on version 2.6, it is
labeled F4_Driver Update; on Solaris 7, it is labeled F4_Add Driver). The message, "Enumerating
buses...." is displayed.
4. Remove the Configuration Assistant diskette from the disk drive and insert the first Solaris DU
diskette.
5. Select F2_Continue. The Select Solaris System Version screen is displayed.
6. Select the appropriate Solaris OS and select F2_Continue.
The Loading Driver Update Software screen is displayed, along with a progress bar that indicates
the percentage of drivers that have been extracted from the diskette. Drivers are read into memory
and survive long enough for the system to successfully boot to its installation program. When all the
new drivers on the diskette have been processed, the Continue Driver Update Installation screen is
displayed.
7. If you have additional DU diskettes to install, remove the DU diskette from the disk drive, insert the
next DU diskette.
8. Select F2_Continue.
Again, the Loading Driver Update Software screen is displayed, along with a progress bar that
shows the percentage of drivers that have been extracted from the diskette. Drivers are read into
memory and survive long enough for the system to successfully boot to its installation program.
When all the new drivers on the diskette have been processed, the Continue Driver Update
Installation screen is displayed.
9. Repeat step 7 and 8 until all desired DU diskettes are installed.
10. When all the drivers are processed, remove the DU diskette from the disk drive and reinsert the
Configuration Assistant diskette.
IMPORTANT: Do not remove the Configuration Assistant diskette from the disk drive until you
see the following message display: "If you want to bypass the device configuration and boot
screens when the system reboots, eject the Device Configuration Assistant/Boot diskette now."
11. Select F2_Continue. The Solaris Device Configuration Assistant screen is displayed.
12. Select F2_Continue. The message, "Enumerating buses...." is displayed, followed by the Scanning
Devices screen. System devices are scanned. When scanning is complete, the Identified Devices
screen is displayed.
Installation 25
13.
Select F2_Continue. The message "Loading driver...." is displayed, followed by messages about the
drivers that are required to boot your system. After a few seconds, the Boot Solaris screen is
displayed.
14. At the Boot Solaris screen, select the device controller attached to the device that contains your install
medium.
15. Select F2_Continue. Drivers display for the device controller you selected. Your system boots to run
the install program. The install program starts and your system begins booting the complete Solaris
operating system environment. Then the following messages are displayed, prompting you to insert
each of the Solaris DU diskettes required to install on your system:
Installing unbundled device driver support
Extracting driver list from tree..
<DU diskette name> driver-name...
Please insert the Driver Update diskette labeled <DU diskette name>
driver-name.
Press <ENTER> when ready.
16. Remove the Configuration Assistant diskette and reinsert the first DU diskette into the disk drive.
17. Press the Enter key. Packages, patches, or both that contain the new drivers are installed from the
diskette onto your system. Messages about each installation are displayed. If drivers on other DU
diskettes are required for your system, the following prompt is displayed.
Please insert the Driver Update diskette labeled <DU diskette name>
Press <ENTER> when ready.
Otherwise, this prompt is displayed:
If you have additional Update diskettes to install (such as video),
please insert diskette now.
Additional Update diskettes to install? (y/n) [y]
18. If drivers on other DU diskettes are required, remove the DU diskette from the diskette drive, insert
the next DU diskette you are prompted to insert. Press the Enter key. Repeat until all the drivers you
need are installed.
19. Press the Enter key.
When installation is complete, the message "Installation complete" is displayed.
20. Remove the diskette from the disk drive.
21. Reboot the system.
When the Solaris operating system is finished booting and running, the new devices whose drivers
you installed are available for use.
Adding a DU diskette to an existing Solaris system
Before adding new or updated drivers, the newly supported hardware devices should be installed and
configured according to the instructions in the corresponding Device Reference Page, if any. Refer to the
Solaris (Intel® Platform Edition) Device Configuration Guide.
When the Solaris (Intel® Platform Edition) software is already installed, the simplest way to add new or
updated drivers is to install the DU diskettes as patches on your system, as follows:
1. Become the superuser on your system.
2. Check to see if Volume Management is running on the system you are updating:
ps -ef | grep vold
For more information about managing diskette and drives, refer to the System Administration Guide.
Installation 26
If Volume Management is running, temporarily stop it by typing:
3.
# /etc/init.d/volmgt stop
4. Insert the DU diskette into the disk drive.
5. Mount the DU diskette at the /mnt mount point:
# mount -F pcfs /dev/diskette /mnt
At this point, you must mount the DU diskette in the file structure to update your system
successfully.
6. Execute the install script on the diskette, using the appropriate Solaris release directory (currently
sol_26 for Solaris 2.6, sol_27 for Solaris 7, and so on). For example:
# /mnt/DU/sol_27/i86pc/Tools/install.sh -i
The install.sh script searches for all new or updated drivers on the diskette. When a new or updated
driver is found, the following prompt is displayed:
Unconditionally installing DUs <DU driver names>
Install patch driver-name? [y]
7. If the driver is the one you want to install, at the prompt, type y for yes or press the Enter key. If the
driver is not the one you want to install, type n for no.
If you select "yes," then the install.sh script installs the driver you selected, as well as the bootmod
and bootbin patches.
8. When you have finished, and the install.sh script exits, unmount the diskette:
# cd /
# umount /mnt
9. Remove the DU diskette from the disk drive.
10. Reboot the system.
# touch /reconfigure
# reboot
11. Power down your system, add the new hardware, and power up the system.
12. When the autoboot sequence prompt is displayed, quickly press the Esc key. The autoboot sequence
is interrupted, and the Configuration Assistant screen is displayed.
13. Select F2_Continue. The message "Enumerating buses ..." is displayed, followed by the Scanning
Devices screen. System devices are scanned. When scanning is complete, the Identified Devices
screen is displayed.
14. Select F2_Continue. The message "Loading driver com.bef ..." is displayed, followed by the Boot
Solaris screen.
15. On the Boot Solaris screen, select the device controller attached to the device that contains your
install medium, in this case the main system disk. The /etc/bootrc script is displayed.
16. At the prompt, type:
b -r
Your system boots. You can now use your new hardware.
Installation 27
NetWare
A network device driver must be installed before the Gigabit Ethernet adapter can be used with your
Novell NetWare system. Before you can successfully install the adapter driver for Novell NetWare, the
adapter card must be physically installed in the server and, typically, NetWare OS software must already
be running on the server. Make sure that your server meets the hardware and operating system software
requirements.
For an adapter installation with an existing NetWare server, NetWare will automatically detect the new
adapter and attempt to load the appropriate driver. Ensure that your CD-ROM is mounted and select the
proper driver.
To enable the Gigabit Ethernet adapter to function correctly, you need to install the latest support pack
files. The latest support pack can be found at the Novell website (http://www.novell.com
Netware install program
A commonly used method to install a driver on a NetWare server is through NWCONFIG. The following
drivers are supported.
• Driver names: N1000e.LAN, N1000.LAN, and N100.LAN
• HP N1000e.LAN driver requirements
).
o Use with an HP NC110T, NC360T, and NC364T Gigabit Server Adapter
o Always install the latest Novell support pack
o Always install the latest HP NSSD
o SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)
o SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)
o SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger)
• HP N1000.LAN driver requirements
o Use with any HP NC310F, NC340T, NC61xx, and NC71xx Gigabit Server Adapter
o Always install the latest Novell support pack
o Always install the latest HP NSSD
o SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)
o SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)
o SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger)
• HP N100.LAN driver requirements
o Use with any HP NC31xx Fast Ethernet Server Adapter
o Always install the latest Novell support pack
o Always install the latest HP NSSD
o SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)
o SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)
o SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger)
Using NWCONFIG or HDETECT to install the adapter
Installation 28
NOTE: Your NetWare server software must be the latest version of the support pack before
installing the HP driver. The latest support pack is available from the Novell support site:
http://support.novell.com/misc/patlst.htm.
Before installing, use the HP SoftPaq to create a floppy disk on a different computer. Refer to
the README.TXT file located in the HP SoftPaq for details on creating a floppy disk.
Use the NetWare Install programs to install the adapter driver. See the Novell Installation Guide for
specific instructions on installing device drivers.
Packet Receive Buffers Setting is Too Low error message
When a server is first installed or has been upgraded, the number of MAXIMUM PACKET RECEIVE
BUFFERS and MINIMUM PACKET RECEIVE BUFFERS are usually too low. The adapter requires a
minimum of 64 Packet Receive Buffers per adapter port during driver initialization.
This initial load of the driver may fail because of the two above mentioned settings. The following error
message is displayed: *** Packet Receive Buffers setting is too low. ***
To correct:
1. Load MONITOR.
2. Select SERVER PARAMETERS.
3. Select COMMUNICATIONS.
4. Set MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger).
5. Set MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger).
6. Set MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger).
7. Restart NetWare to complete.
This can also be set by using the NWCONFIG and selecting the Startup.NCF file. See the Netware
Installation Guide for specific instructions.
The maximum and minimum settings of 10000 and 2000 respectively are suggested values only. You
may need to request a larger number for MAXIMUM PACKET RECEIVE BUFFERS depending on the
number of supported adapter ports in the system. This message is also displayed on the console if the
driver cannot allocate the required number of Receive Buffers during driver load.
Driver configuration parameters
Parameter Options Description
CheckSum = Default = ON
Selections are: ON, OFF, Tx,
Rx
Frame = type Valid types are:
Ethernet_802.2,
Ethernet_802.3, Ethernet_II,
Ethernet_SNAP
node = NNNNNNNNNNNN Specifies a node address in this field to
name = text
Enables or disables the transmit and receive
checksum off-loading feature. Checksum is
supported under NetWare 5.x only. If you
want to enable the CheckSum parameter, you
need to load it on the first instance.
Defines the frame type being used by this load
instance. Ethernet_802.2 and Ethernet_II are
the default values.
override the default Media Access Controller
(MAC) address (also known as the Locally
Administered Address)
Displays the name assigned to this adapter
Installation 29
Parameter Options Description
PDriver = Default = OFF
Selections are: OFF, ON
RxBuffers = Default = 200
Recommended Min = 32
Max = 512
Min = 1 when used with DOS
Client32 and when Keywrod
P3-1 or 2.
TxDescriptors = Default = 200
Recommended Min = 100
Max = 512
Min = 1 when
used with DOS
Client32 and when
Keywrod P3-1 or
2.
RxFlow = Default = OFF
Selections are: ON, OFF
TxFlow = Default = OFF
Selections are: ON, OFF
Slot = n
Speed = n
Jumbo = Set maximum physical receive
Link= Default=FORCE
RxTicks= Default = 360
packet Size = 18000 in the
STARTUP.NCF. Choices are
Jumbo = 1514–9000. This
keyword is only supported on
NetWare 6.x.
Selections are: AUTO, FORCE
Min = 0, disabled
Max = 5000000, 5 seconds
Units are in micro seconds
Allows driver to operate in persistent driver
mode. Persistent driver mode is supported
under NetWare 5.x only. Use only if adapter
is placed in a Hot Plug PCI slot and only if
required to swap with an exact board.
Pre-allocates ECB resources on the adapter for
receiving packets
Pre-allocates ECB resources on the adapter for
transmitting packets.
Allows enabling/disabling of RxFlow control.
Allows enabling/disabling of TxFlow control.
Identifies the slot number for the specific
adapter currently being configured. This
parameter is not necessary if only a single
adapter is installed.
If link negotiation has been disabled, specifies
port speed to be either Auto, 10HD or 10FD,
100HD or 100FD.
Enables/disables Jumbo Frame support. When
enabled, jumbo packets of up to 9000 bytes
are supported. Not supported on NC1020
adapters.
Only used to allow the adapter to negotiate a
specific or forced line speed with a switch that
is not forced, but instead setup for autonegotiation. It is best to allow for autonegotiation of the card and switch by not
setting this keyword or the speed keyword.
Only use this keyword if the speed keyword is
set to something other than AUTO.
Enables the use of batching receives within a
specific time period.
Installation 30
Loading...