HP NC320T, NC340T, NC360T, NC364T, NC370T Software And Configuration 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 CD­ROM 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 auto­negotiation. It is best to allow for auto­negotiation 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

Parameter Options Description

TXPacketsPer Default = 64

Min = 0, disabled
Max = 100

NOTE: With Jumbo Frames, the first frame must be Ethernet_ii.

Enables the use of batching transmits to a
specific amount of packets.

Post installation
After NetWare 6.x has been successfully installed, set the minimum packet receive buffers parameter in

the startup.ncf file to 1500 for each adapter in the system. Set the maximum packet receive buffers to
three times the minimum packet receive buffers. Typically one MB of RAM is required per 1000 receive
buffers. For more information, refer to the "Configuring Driver Parameters" section.

In the autoexec.ncf file, delete the packet receive buffers parameter (RxBuffers=32) in the load
statement for this adapter. Deleting the receive buffers phrase from the load statement resets the receive
buffers parameter to the default value of 200 for this adapter.

NOTE: You must reboot the server for the new configuration.

Example:
The default maximum number of receive buffers for the system is 500; the default minimum is 128. Edit

the startup.ncf file to have the following entries. The actual numbers will be a function of the number of
adapters in the system.

• set maximum packet receive buffers = 30000

• set minimum packet receive buffers = 10000

• set maximum physical receive packet size = 2048

Verifying or modifying adapter properties
When an adapter configuration is saved, the NetWare install program adds load and bind statements to

the autoexec.ncf file. By accessing this file, you can verify the parameters configured for each
adapter, modify them, or enter additional parameters.

NOTE: The Novell monitor program and the CONFIG command are also useful for verifying

driver configuration. For information on how to use these programs, refer to the utilities

The parameters that can be defined in the load statements are described in NetWare server driver LOAD
line parameters for HP server adapters below. A valid autoexec.ncf file is shown below. One set of load
and bind commands is added for each frame type the adapter is configured to support.

reference in your Novell NetWare online documentation.

Valid Autoexec.ncf file

Set Time Zone = PST8PDT
set Daylight Savings Time Offset = 1
set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM)
set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM)
set Default Time Server Type = SINGLE
set Bindery Context = O=LAN

Installation 31

# WARNING!!
file server name NOVELLSERVER51
# WARNING!!
# If you change the name of this server, you must update
# all the licenses that are assigned to this server. Using
# NWAdmin, double-click on a license object and click on
# the Certificate Assignments button. If the old name of
# this server appears, you must delete it and then add the
# new server name. Do this for all license objects.

ServerID 1C8EE2C
LOAD ODINEB.NLM
LOAD TCPIP
LOAD Q57 SLOT=2 FRAME=Ethernet_802.2 NAME=Q57_1_E82
BIND IPX Q57_1_E82 NET=FAFD3D25
LOAD Q57 SLOT=2 FRAME=Ethernet_802.3 NAME=Q57_1_E83
BIND IPX Q57_1_E83 NET=5A2D8D6D
LOAD Q57 SLOT=2 FRAME=Ethernet_SNAP NAME=Q57_1_ESP
BIND IPX Q57_1_ESP NET=477A35BD
LOAD Q57 SLOT=2 FRAME=Ethernet_II NAME=Q57_1_EII
BIND IPX Q57_1_EII NET=C3C8F2E4
BIND IP Q57_1_EII ADDR=172.16.1.1 MASK=ff.ff.0.0

mount all
SEARCH ADD SYS:\JAVA\BIN
SEARCH ADD SYS:\JAVA\NWGFX

IMPORTANT: If you modify any adapter parameters, you must reboot the system before the

changes will take effect. If you make changes and do not reboot, you may experience
configuration problems.

Removing drivers from Autoexec.ncf
To remove the drivers from the Autoexec.ncf, locate the LOAD and BIND command lines associated with

the driver and remark them out by inserting the pound (#) symbol at the beginning of each command line.

Example:

# LOAD Q57 SLOT=2 FRAME=Ethernet_802.2 NAME=Q57_1_E82
# BIND IPX Q57_1_E82 NET=FAFD3D25
# LOAD Q57 SLOT=2 FRAME=Ethernet_802.3 NAME=Q57_1_E83
# BIND IPX Q57_1_E83 NET=5A2D8D6D
# LOAD Q57 SLOT=2 FRAME=Ethernet_SNAP NAME=Q57_1_ESP
# BIND IPX Q57_1_ESP NET=477A35BD
# LOAD Q57 SLOT=2 FRAME=Ethernet_II NAME=Q57_1_EII
# BIND IPX Q57_1_EII NET=C3C8F2E4
# BIND IP Q57_1_EII ADDR=172.16.1.1 MASK=ff.ff.0.0

NetWare server driver LOAD line parameters
This following lists the NetWare server driver LOAD line parameter settings for HP server adapters for

N100, N1000, and N1000e.

• FORCEDUPLEX. This keyword specifies one of the following duplex modes:

o Auto-negotiate. The adapter negotiates with the switch and hub how to send and receive packets

at either full- or half-duplex speed. If unsuccessful at negotiating the duplex, HP server adapters
default to half-duplex. 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).

Installation 32

o

Full-duplex. The adapter sends and receives packets at the same time. This improves the
performance of your adapter. Set duplex mode to full-duplex ONLY if you have a hub/switch
that supports full-duplex.

o Half-duplex. The adapter performs one operation at a time. It either transmits or receives.

NOTE: The HP NC31xx, 340T, and NC71xx Server Adapters support full-duplex and half-

duplex. The HP NC61xx fiber Gigabit Server Adapters support full-duplex mode only and
cannot be changed.

NOTE: The NC3133 default to full-duplex.

NOTE: To set the adapter to half- or full-duplex, you must set the SPEED parameter to either 10

or 100.

o Syntax: FORCEDUPLEX=n

Where n =
0—auto-negotiate
1—half-duplex
2—full-duplex

o Default = auto-negotiate
o Examples:

100 Mbps full-duplex FORCEDUPLEX=2 SPEED=100
10 Mbps full-duplex FORCEDUPLEX=2 SPEED=10

• SLOT. (Required) For PCI adapters, SLOT is derived from bus number and device location as defined

by the PCI specification. One way to determine the slot number is to load the driver from the
command line. You will be prompted with valid device number(s) for the adapter(s). Select one of
them.

o Syntax: SLOT=n

Where n = 1, 2, 3, 4,...

• SPEED. This keyword 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 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, N1000.LAN, and
N1000e.LAN drivers. You cannot change the speed for the Gigabit (fiber) adapters. You can,
however, change the speed for the NC7170, NC7131, and NC7132 Gigabit (copper)
adapters to 10 Mbps or 100 Mbps.

o Syntax: SPEED=n

Where n = 10 or 100 or 1000

o Default = The adapter automatically detects network speed.

Installation 33

• NODE. This keyword specifies a locally administered address (LAA) unique to each adapter. Use this

option to provide your own unique node address for the adapter. The node address is a 12-digit
hexadecimal number. The second digit must be one of the following digits: 2, 6, A, E.

o Syntax: NODE=xnxxxxxxxxxx

Where n = 2, 6, A, E
Where x = hexadecimal number

o Default = The adapter's assigned address

• FRAME. This keyword indicates one of four valid frame types the system is transmitting and receiving.

o Syntax: FRAME=n

Where n = Ethernet_802.2, Ethernet_802.3, Ethernet_II, Ethernet_SNAP

o Default = Ethernet_802.2

• POLL. This keyword is used to enable polling mode in the driver with interrupt backup. If polling is

enabled, interrupts will be reduced, allowing the processor to spend more time performing other
functions. In polling mode, interrupts will occur only when receive resources have been reduced to
less than half. If polling is not enabled, the driver will perform in traditional interrupt mode.

o Syntax: POLL=n
o Where n = 0 (interrupt mode), 1 (polling mode with interrupt backup)
o Default = 0 (interrupt mode)

NOTE: The POLL parameter is for the N100.LAN, N1000.LAN, and N1000e.LAN drivers.

• SPURIOUS. This keyword is used to reduce the number of spurious interrupts reported by the OS on

the driver interrupt line. This automatically loads for 10, 100, and 1000 adapters.

o Syntax: SPURIOUS=n

Where n = 0 or 1
0—Driver operates in normal mode
1—Driver operates to reduce the number of spurious interrupts

o Default = 1

NOTE: The minimum threshold for acceptable number of spurious interrupts is 200 interrupts

per second, which is the default value of the environmental variable "set display spurious
interrupt alerts threshold."

• RXCHECKSUM. This keyword is used to enable or disable the offload of Receive Packet Checksum

verification to the adapter. This automatically loads for 10/100 adapters.

o Syntax: RXCHECKSUM=n

Where n = 0 or 1
0—Does not offload Rx Checksum verification to the adapter
1—Offloads Rx Checksum verification to the adapter

o Default = 0

NetWare custom statistics
NetWare custom statistics appear when you run monitor NLM and load the LAN driver. One custom

statistic counter is the duplex mode, where 1 = half-duplex and 2 = full-duplex.

Installation 34

The following describes the adapter Status Counters and Software Counters and their acceptable ranges.
N100 custom counters

• Link Status

This counter contains the link status, as read from the PHY, or general status register of the ASIC. It is
updated once a second. A value of 0 is link up. 1 is link down.

• Duplex

This counter holds the current duplex as read directly from the PHY, or general status register of the
ASIC. A value of 0 is not supported or unknown, 1 is half-duplex, and 2 is full-duplex. Unsupported
is usually due to an unsupported chip type, or link not being present.

• Current Speed

This counter holds the current speed as read directly from the PHY, or general status register of the
ASIC. A value of 0 is not supported or not available, 10 for 10 Mbps, 100 for 100 Mbps, and
1000 for 1000 Mbps. Unsupported is usually due to an unsupported chip type, or link not being
present.

• Hardware Status

A counter of non-zero indicates failure.

• Tx Good Frames

This counter contains the number of frames that were transmitted properly on the link. It is updated
only after the actual transmission on the link is completed, and not when the frame was read from
memory as is done for the TxCB status. This value varies in accordance to the amount of frames sent,
and can reach billions very quickly.

• Tx Maximum Collisions

This counter contains the number of frames that were not transmitted because they encountered the
configured maximum number of collisions. This counter increments when the network is heavily
saturated with traffic. If this value is consistently growing, you may want to segment your network
with switches to change the collision domain, so that more time is spent sending data instead of
collisions.

• Tx Late Collisions

This counter contains the number of frames that were not transmitted because they encountered a
collision outside of the normal collision window. Normally, late collision events should occur only
rarely, if at all. A high number of late collisions is often a sign that there is some problem with the
network topology. Check the topology to be sure that all cables meet IEEE specifications (Category 5
for 100 Mbps TX), and that all distance requirements for cabling are met. Also, check to be sure that
all of the network hubs and switches are configured for the proper duplex mode.

• Tx DMA Underruns

This counter contains the number of frames that were either not transmitted or re-transmitted due to a
Tx DMA under-run. If the device is configured to retransmit on under-run, this counter may be
updated multiple times for a single frame. Under-runs occur because a lack of PCI bandwidth
resulted in the device's internal transmit FIFO running dry during the transmission of a frame. The
adaptive algorithms within the software keep this number under control. If a high number of under­runs are seen, you may want to load the driver with TxThreshold=200 on the command line.

Example:

Load N100 slot=2 Frame=Ethernet_802.2 TxThreshold=200

For additional information about the adaptive algorithm, refer to the "CurrentThreshold" section.

Installation 35

• Tx Lost Carrier Sense

This counter contains the number of frames that were transmitted by the device despite the fact that it
detected the de-assertion of Carrier Sense during the transmission.

• Tx Frames Deferred

This counter contains the number of frames that were deferred before transmission due to activity on
the link. This is a normal condition in busy conditions, and the number can grow quite large.

• Tx OK with Single Collisions

This counter contains the number of transmitted frames that encountered one, and only one, collision
before being successfully sent. This is a normal condition in busy conditions. If single collisions
accumulate quickly, you may want to consider segmenting your network more. To combat collisions,
the software can adjust the interframe gap to allow more room between frames. More room between
frames allows more frames on average. Refer to the "CurrentIFSValue" section for more details.

• Tx OK with Multiple Collisions

This counter contains the number of transmitted frames that encountered more than one collision. This
only gets incremented once, even though one frame may have had several collisions before being
successfully sent. This is a normal condition in busy conditions. If multi-collisions accumulate quickly,
you may want to consider segmenting your network more. To find the average number of multi­collisions a frame had to endure before being successful, use the following formula:

(TxTotalCollisions - TxSingle Collisions - TxMaxCollisions) / TxMultiple Collisions
If the average is close to 16 (the Ethernet max collisions before a frame will no longer be retried),

then you will need to segment your network to avoid losing frames and network efficiency to
collisions.

• Tx Total Collisions

This counter contains the total number of collisions that were encountered while attempting to
transmit. This count includes late collisions and collisions from frames that encountered
MAXCOL(16). If this counter is growing quickly, you need to segment your network more.

• Rx Good Frames

This counter contains the number of frames that were received properly from the link. It is updated
only after the actual reception from the link is completed and all the data bytes are stored in
memory.

• Rx Crc Errors

This counter contains the number of aligned frames discarded because of a CRC error. The
CRC_ERRORS counter is mutually exclusive to the ALIGNMENT_ERRORS and SHORT_FRAMES
counters. CRC errors are usually caused by late collisions where another station has sent data in the
middle of a frame. This number should be very low.

• Rx Alignment Errors

This counter contains the number of frames that are both mis-aligned (not an even length) and
contain a CRC error. The ALIGNMENT_ERRORS counter is mutually exclusive to the CRC_ERRORS
and SHORT_FRAMES counters.

• Rx No Resource Errors

This counter contains the number of good frames discarded because there were no resources
available. Frames intended for a host whose Receive Unit is in the "No Resources" state fall into this
category. The number of resource errors can be reduced by increasing the number of receive buffers

Installation 36

that software uses, or increasing the performance of the host machine's processing power (which
would allow for faster processing of the resources).

• Rx DMA Overrun Errors

This counter contains the number of frames known to be lost because the device's internal receive
FIFO overflowed. This can occur if the device is unable to get the necessary bandwidth on the system
(PCI) bus. If the overflow condition persists for more than one frame, the frames that follow the first
could also be lost. However, because there is no lost frame indicator they may not be counted. A
frame that was counted as an overrun will not be counted in other error counters (SHORT_FRAMES,
CRC_ERRORS, or ALIGNMENT_ERRORS). To combat this, a faster bus machine, or fewer devices on
the bus will be needed.

• Rx Collisions Detect Errors

This counter contains the number of frames that encountered collisions during frame reception.

• Rx Short Frame Errors

This counter contains the number of received frames that are shorter than the minimum frame length.
The SHORT_FRAMES counter is mutually exclusive to the ALIGNMENT_ERRORS and CRC_ERRORS
counters and has a higher priority (a short frame will always increment only the SHORT_FRAMES
counter).

• Flow Control TX Pause

This counter contains Xon and Xoff frames transmitted.

• Flow Control RX Pause

This counter contains Xon and Xoff frames received.

• Flow Control Unsupported

This counter contains the MAC Control frames received that are not Flow Control Pause frames.
These frames contain the predefined MAX control type value but contain an unsupported opcode.

• TCO Rx (or Tx) Frames

This counter is incremented at each received/transmitted TCO packet.

• Tx Timeouts

This is a debug timer and not currently used. It should be zero.

• Tx Dynamic Chaining Count

This is a performance evaluation counter and not currently used. It should be zero.

• Current IFS Value

This is the current Inter Frame Spacing (IFS) value that the driver is using. IFS is an Ethernet
specification term for clock time spaces between frames sent by an individual card in a burst.
Normally a card sends frames back to back with only the minimum frame spacing between each
frame. Under low load conditions, this produces maximum throughput. But under heavy load
conditions, this means less time for other stations to send safely; thus, more collisions and less
throughput.

By adaptively controlling the IFS, more stations can safely send, lowering collisions and helping to
keep throughput high. The larger this number is, the more collisions your network is experiencing.

• Current Threshold

As under-runs occur, the software can change the amount of time the hardware will wait before
starting to transfer data onto the adapter's hardware buffers. By doing so, it can slow or stop the

Installation 37

amount of under-runs. The higher this number, the more time the adapter is waiting before starting to
transmit data onto the wire. Poor bus performance, large amounts of traffic or a large number of
devices on the same bus can cause this to rise. If this number is always above 170, you may want to
consider loading the driver with the TxThreshold parameter set to a higher value, such as 200.

• RstartCnt

Re-Start Count, also known as RSC, is a support counter to see how often the restart effort occurs.
Under some high traffic, or high utilization conditions, the receiving unit does not start normally and
needs a restart. RSC has no impact on the end user. It is intended for software development use
only. It is normal for this to be non-zero.

• REC

Under some busy conditions, the receiving unit stalls and needs to be restarted. This counter tracks
the number of times it needs to be restarted. RSC is a subset of REC. Most REC events restart
normally, but the few that do not are REC events. This counter is intended for software development
use only and may be disregarded by the end user. It is normal for this to be non-zero.

• Checksum Good

This counter indicates the number of received packets that the hardware has verified, the checksum,
and if the checksum is valid.

• Checksum Bad

This counter indicates the number of received packets that the hardware has verified, the checksum,
and if the checksum is valid.

• Stalled Ints SW Resets

This counter indicates the number of times the driver issued a complete reset (to the driver and to the
adapter) as a result of a stalled interrupt situation. A stalled interrupt situation is detected by the
driver if there are no interrupts for a long time, and a SW interrupt issued by the driver fails to
arrive.

• Carrier Loss PHY Resets

This counter indicates the number of times the driver reset the PHY as a result of carrier sense loss.

N1000 and N1000e custom counters

• Duplex Mode (1=Half, 2=Full)

This counter indicates the current link duplex configuration. A value of 1 indicates the adapter is
configured to half-duplex mode. A 2 indicates full-duplex mode configuration. This counter exists in
v1.12 or higher of the NetWare server driver.

• Line Speed (Mbps)

This counter displays the current line speed in Mbps.

• Configured Duplex Mode (0=Auto, 1=Half, 2=Full)

• Configured Speed (Mbps; 0=Auto)

• PCI Mode (0=PCI, 1=PCI-x, 2=PCI-Express)

• Bus Clock Rate (Mhz) (0=Unavailable)

• Link Status (0=Up, 1=Down)

This counter describes the current link status of the adapter. A value of 0 indicates the link is up and
a value of 1 indicates that the link is down. This counter exists in v1.12 or higher of the NetWare
server driver.

Installation 38

• Link Status Change Count

This counter indicates the number of times the link status has been changed.

• Rx CRC Error Count

This counter indicates the number of receive packets with CRC errors. Packets less than 64 bytes are
not counted in this statistic.

• Alignment Errors

This counter holds the number of receive packets with alignment errors. In order for a packet to be
counted, it must pass address filtering and must be 64 bytes or greater in length. If receives are not
enabled, then this counter does not increment. This counter is valid only in MII mode during 10/100
Mbps operation.

• Rx Symbol Error Count

This counter indicates the number of symbol errors between reads. The count increases for every bad
symbol received, whether or not a packet is currently being received and whether or not the link is
up. This counter will increment along with the Rx Sequence Error Count when either the fiber cable is
disconnected or the connector is not seated completely. Also, during driver load, this counter will
increments minimally.

• Rx Error Count

This counter indicates the number of packets received in which I_RX_ER was asserted by the PHY. In
order for a packet to be counted, it must pass address filtering and must be 64 bytes or greater
(from <Destination Address> through <CRC>, inclusively) in length. If receives are not enabled, then
this counter does not increment. In TBI mode, this counter increments on the reception of /V/ codes.

• Rx Missed Packets Count

This counter indicates the number of missed packets. Packets are missed when the hardware receive
FIFO has insufficient space to store the incoming packet. This could be the result of having too few
buffers allocated or because there is insufficient bandwidth on the IO bus. These packets are also be
counted in the Total Packets Received counter as well as in Total Octets Received.

• Tx Single Collision Count

This counter indicates the number of times that a transmitted packet encountered a single collision.
This counter increments only if the device is in half-duplex mode.

• Tx Excessive Collisions Count

This counter indicates when 16 or more collisions have occurred on a packet. This counter
increments only if the device is in half-duplex mode.

• Tx Multiple Collision

This counter indicates the number of times that a transmitted packet encountered more than one
collision but less than 16. This counter increments only if the device is in half-duplex mode.

• Tx Late Collisions Count

This counter indicates collisions that occur after 512 bit (64 byte) times. This counter increments only
if the device is in half-duplex mode.

• Tx TOTAL Collision

This counter indicates the total number of collisions seen by the transmitter. This counter increments
only if the device is in half-duplex mode.

• Tx DMA Underruns

Installation 39

This counter contains the number of frames that were either not transmitted or re-transmitted due to a
Tx DMA under-run. If the device is configured to retransmit on under-run, this counter may be
updated multiple times for a single frame. Under-runs occur because a lack of PCI bandwidth
resulted in the device's internal transmit FIFO running dry during the transmission of a frame. The
adaptive algorithms within the software keep this number under control. To see how the adaptive
algorithm is doing, refer to the "Current Threshold" section.

• Tx Defer Count

This counter indicates transmit defer events. A defer event occurs when the transmitter cannot
immediately send a packet due to the medium being busy, either because another device is
transmitting or the link is not up.

• Tx with No CRS

This counter counts the number of successful packet transmissions in which the Carrier Sense input
from the PHY was not asserted within one slot time of start of transmission. The PHY should assert
Carrier Sense during every transmission. Failure to do so may indicate that the link has failed, or the
PHY has an incorrect link configuration. This counter is not valid in TBI mode, and is only valid when
the device is operating at full-duplex.

• Rx Sequence Error Count

This counter indicates receive sequence error events. This counter increments along with the Rx
Symbol Error Count when either the fiber cable is disconnected or the connector is not seated
completely.

• Rx Length Error Count

This counter indicates receive length error events. A length error occurs if an incoming packet is
undersized (less than 64 bytes) or oversized (greater than 1522).

• Rx DMA Too Early

This counter counts the total number of times that the device attempted to perform an Early DMA
operation (by speculatively requesting the host bus prior to reception of the entire packet) and ran
out of data to DMA before the device was forced to relinquish ownership of the bus. This condition is
really not an "error" condition, but is nevertheless counted for diagnostic purposes. This statistic is
valid only if Early Receives are enabled.

• XON Received Count

This counter indicates the number of XON packets received. XON packets can occur when Flow
Control is enabled and both the adapter and its link partner are configured to use it.

• XON Transmitted Count

This counter indicates the number of XON packets transmitted. XON packets can occur when Flow
Control is enabled and both the adapter and its link partner are configured to use it.

• XOFF Received Count

This counter indicates the number of XOFF packets received. XOFF packets can occur when Flow
Control is enabled and both the adapter and its link partner are configured to use it.

• XOFF Transmitted Count

This counter indicates the number of XOFF packets transmitted. XOFF packets can occur when Flow
Control is enabled and both the adapter and its link partner are configured to use it.

• Flow Control Received Unsupported Count

Installation 40

This counter indicates the number of unsupported flow control frames that are received. This counter
increments when a flow control packet is received which does not match the adapter definition of a
flow control packet. This counter is not expected to increment.

• 64 Byte Packets Received

This counter indicates the number of good packets received that are exactly 64 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• 65–127 Byte Packets Received

This counter indicates the number of good packets received that are 65–127 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• 128–255 Byte Packets Received

This counter indicates the number of good packets received that are 128–255 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• 256–511 Byte Packets Received

This counter indicates the number of good packets received that are 256–511 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• 512–1023 Byte Packets Received

This counter indicates the number of good packets received that are 512–1023 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• >1024 Byte Packets Received

This counter indicates the number of good packets received that are 1024–1522 bytes in length,
including CRC. Packets counted in the Missed Packet Count are not counted here. This counter does
not include received flow control packets.

• Good Packets Received Count (Any Length)

This counter indicates the number of good packets received of any legal length. This counter does
not include received flow control packets.

• Broadcast Packets Received Count

This counter indicates the number of good broadcast packets received.

• Multicast Packets Received Count

This counter indicates the number of good multicast packets received. This counter does not include
received flow control packets.

• Good Packets Transmitted Count (Any Length)

This counter indicates the number of good packets transmitted of any legal length. This counter does
not include received flow control packets.

• Good Octets Received Count LO

This counter, in conjunction with the Good Octets Received Count HI, makes up a 64-bit counter that
indicates the number of good octets received. This statistic reflects the lower 32 bits of the 64-bit
counter. This counter does not include received flow control packets.

Installation 41

• Good Octets Received Count HI

This counter, in conjunction with the Good Octets Received Count LO, makes up a 64-bit counter
that indicates the number of good octets received. This counter reflects the upper 32 bits of the 64-bit
counter and is incremented each time the Good Octets Received Count LO has reached it maximum
value and wraps to zero. This counter does not include received flow control packets.

• Good Octets Transmitted Count LO

This counter, in conjunction with the Good Octets Transmitted Count HI, makes up a 64-bit counter
that indicates the number of good octets transmitted. This counter reflects the lower 32 bits of the 64­bit counter. This counter does not include received flow control packets.

• Good Octets Transmitted Count HI

This counter, in conjunction with the Good Octets Transmitted Count LO, makes up a 64-bit counter
that indicates the number of good octets transmitted. This counter reflects the upper 32 bits of the 64­bit counter and is incremented each time the Good Octets Transmitted Count LO has reached it
maximum value and wraps to zero. This counter does not include received flow control packets.

• Receive No Buffers Count

This counter indicates the number of times that packets were received when there were no available
buffers in host memory to store those packets. The packet is still received if there is space in the
hardware FIFO. This counter does not include received flow control packets. Increasing Rx
Descriptors on the command line during load could result in this counter incrementing less frequently.

• Receive Undersize Count

This counter indicates the number of received packets that were less than minimum size (64 bytes)
and had a valid CRC.

• Receive Fragment Count

This counter indicates the number of received packets that were less than minimum size (64 bytes)
but had a bad CRC.

• Receive Oversize Count

This counter indicates the number of received packets that were greater than maximum size (1522
bytes) and had a valid CRC.

• Receive Jabber Count

This counter indicates the number of received packets that were greater than maximum size (1522
bytes) but had a bad CRC.

• Total Octets Received LO

This counter, in conjunction with the Total Octets Received HI, makes up a 64-bit counter that
indicates the total number of octets received. This counter reflects the lower 32 bits of the 64-bit
counter.

• Total Octets Received HI

This counter, in conjunction with the Total Octets Received LO, makes up a 64-bit counter that
indicates the total number of octets received. This counter reflects the upper 32 bits of the 64-bit
counter and is incremented each time the Total Octets Received LO has reached it maximum value
and wraps to zero.

• Total Octets Transmitted LO

Installation 42

This counter, in conjunction with the Total Octets Transmitted HI, makes up a 64-bit counter that
indicates the total number of octets transmitted. This counter reflects the lower 32 bits of the 64-bit
counter.

• Total Octets Transmitted HI

This counter, in conjunction with the Total Octets Transmitted LO, makes up a 64-bit counter that
indicates the total number of octets transmitted. This counter reflects the upper 32 bits of the 64-bit
counter and is incremented each time the Total Octets Transmitted LO has reached it maximum value
and wraps to zero.

• Total Packets Received

This counter indicates the total number of packets received. All packets are counted here, regardless
of their length, whether they are erred, or whether they are flow control packets.

• Total Packets Transmitted

This counter indicates the total number of packets transmitted. All packets transmitted will be counted
here, regardless of their length or whether they are flow control packets.

• 64 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are exactly 64 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• 65–127 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are 65–127 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• 128–255 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are 128–255 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• 256–511 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are 256–511 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• 512–1023 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are 512–1023 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• >1024 Byte Packets Transmitted

This counter indicates the number of good packets transmitted that are 1024–1522 bytes in length,
including CRC. This counter does not include transmitted flow control packets.

• Broadcast Packets Transmitted Count

This counter indicates the number of good broadcast packets transmitted.

• Multicast Packets Transmitted Count

This counter indicates the number of good multicast packets transmitted. This counter does not
include transmitted flow control packets.

• Rx Checksum Good Pkts

This counter indicates the number of receive packets with good checksums calculated. This counter
increments only when RxTcpChecksum has been enabled and packets with good checksums are
received.

• Rx Checksum Error Pkts

Installation 43

This counter indicates the number of receive packets with CRC errors. Packets less than 64 bytes are
not counted in this counter.

• Tx Threshold

This counter indicates the current value of the Early Transmit Threshold. The adapter starts
transmitting the packet when the specified number of quad-words has been DMAed in from memory.

• Current IFS Value

This counter indicates the current value of Inter Frame Spacing between back-to-back transmits.

• Jumbo Frames Received

This counter indicates the number of jumbo packets received (packets greater than 1514 in length).

• Jumbo Frames Transmitted

This counter indicates the number of jumbo packets transmitted (packets that are greater than 1514
in length).

• PCI-X mode (0=PCI, 1=PCI-X)

This counter indicates whether the adapter is in a PCI.

CPQANS custom counters

• Number of Tx ECBs Queued in Members

This counter indicates the number of packets (Event Control Blocks) that are queued in team members
for transmission.

• Number of Tx ECBs Queued in Unavailable ECBs Queue

This counter indicates the number of transmit packets (Event Control Blocks) that are currently in the
CPQANS transmit queue.

• Total Enqueued Tx Due to No Available ECBs

This counter indicates the number of transmit packets that were queued due to no available ECBs.

• Number of Probes Sent by All Team Members

This counter indicates the number of probe packets sent by all team members.

• Number of Probes Received by All Team Members

This counter indicates the number of probe packets received by all team members.

Advanced Network Services help - supported keywords

• AGG_SELECTION

o Syntax: AGG_SELECTION=[BANDWIDTH | COUNT]
o Description: Sets active aggregator selection mode by bandwidth or count

• BALANCE_INTERVAL

o Syntax: balance_interval=nnn
o Description: Changes Balance interval, nnn counts 1/18 sec

• BALANCE_SET_DEFAULT

o Syntax: balance_set_default
o Description: Restores Balance interval to factory settings

• COMMIT

o Syntax: commit [team=nnn]

Installation 44

Description: Sets a certain mode. Use after binding to base drivers with Team=nnn.

o

• DELAY

o Syntax: delay=nnn
o Description: Delays the commit in nnn seconds

• FRAME

o Syntax: frame=[ETHERNET_802.2 | ETHERNET_802.3 | ETHERNET_II | ETHERNET_SNAP]

• HELP

o Syntax: -H
o Description: Displays Help
o Example: CPQANS -H

• JOIN_INDIVIDUALS

o Syntax: join_individuals=[yes | no]
o Description: Joins all individual links to one aggregator

• LBN

o Syntax: Reset LBN=nnn
o Example: cpqans reset lbn=nnn
o Description: Resets the logical board number (LBN) of a bound adapter. Supported only after

commit command. Default value = 0

• MAX_TX_QUEUE

o Syntax: max_tx_queue=nnn
o Description: Sets the Max number of TX ECBs queued for send

• MODE

o Syntax: mode=[NFT | ALB | FEC | GEC | 802.3AD]

• NAME

o Syntax: name=[any unique name]
o Description: Sets a unique name

• PRIMARY

o Syntax: primary | secondary
o Description: Identifies the primary adapter. Supported only in BIND command

• PROBE_BURST_SIZE

o Syntax: probe_burst_size=nnn
o Description: Changes number of probes to send in a retry

• PROBE_CHECK_INTERVAL

o Syntax: probe_check_interval=nnn
o Description: Changes probes check interval

• PROBE_RECHECK_INTERVAL

o Syntax: probe_recheck_interval=nnn
o Description: Changes probe retries check interval

Installation 45

• PROBE_RETRY_COUNT

o Syntax: probe_retry_count=nnn
o Description: Changes probes retry count

• PROBE_SEND_INTERVAL

o Syntax: probe_send_interval=nnn
o Description: Changes probes send interval, nnn counts 1/18 sec

• PROBE_SET_DEFAULT

o Syntax: probe_set_default
o Description: Restores probes settings to factory settings

• PROBES

o Syntax: probes=[on | off]
o Description: Enables/disables probes

• PROBES

o Syntax: probes=[BROADCAST|MULTICAST]
o Description: Changes probes addressing

• RECOMMIT

o Syntax: recommit [team=nnn]
o Description: Resets a certain mode. Use after hot binding to base drivers with Team=nnn

• REMOVETEAM

o Syntax: removeteam [team=nnn]
o Description: Removes a team. Use after hot binding to base drivers with Team=nnn

• REMOVEVLANID

o Syntax: RemoveVlanID=nnn
o Description: Removes the selected VLAN

• RESET

o Syntax: RESET LBN=nnn
o Description: Supported only after Commit command

• SECONDARY

o Syntax: primary | secondary
o Description: Identifies the secondary adapter. Supported only in BIND command.

• SMPMODE

o Syntax: SMPMODE=[SMP | NONSMP]
o Description: Enables/disables SMP aware

• STATUS

o Syntax: status [team=nnn]
o Description: Prints CPQANS status

• TEAM

o Syntax: team=nnnn

Installation 46

Description: Identifies the team. nnnn=DecimalNumber.

o

• TX_ECBS_TO_USE

o Syntax: tx_ecbs_to_use=nnn
o Description: Sets number of TX ECBs to allocate per virtual adapter

• VLANID

o Syntax: VlanID=nnn
o Description: Sets team to VLAN mode. Creates MLID edge

Installation 47

Firmware upgrade utility

In this section

Windows utility...................................................................................................................................... 48

c-Class BladeSystem utility....................................................................................................................... 54

Linux utility ............................................................................................................................................ 54

DOS utility............................................................................................................................................. 59

Windows utility

These notes describe how to use the Gigabit Server Adapter Firmware Upgrade Utility to flash server
adapter firmware.

Flashing consists of using software to replace the current server adapter firmware on a target server with
a new firmware image. Server adapter firmware is typically flashed for the following reasons:

• To support new features

• To correct problems in a previous server adapter firmware version

Customers should upgrade their servers to the latest server adapter firmware version:

• When HP releases a new server adapter firmware version

• When installing a new server adapter

• After purchasing a new server

• When installing a SoftPaq that specifies the need for the latest version of firmware

The Gigabit Server Adapter Firmware Upgrade Utility automatically checks for driver, hardware, and
operating system dependencies, and installs only the correct server adapter firmware upgrades required
by each target server.

Supported operating systems
The upgrade utility supports the following operating systems:

• Microsoft® Windows® 2000 Server

• Microsoft® Windows® 2000 Advanced Server

• Microsoft® Windows® 2000 Data Center

• Microsoft® Windows® 2000 Terminal Server

• Microsoft® Windows 2003 Server

• Microsoft® Windows 2003 (32-bit) Enterprise Server

• Microsoft® Windows 2003 (32-bit) Data Center

• Microsoft® Windows 2003 (x64) Enterprise Server

Supported Gigabit Server Adapters
The upgrade utility provides support for the following adapters:

Firmware upgrade utility 48

Standup adapters:

• HP NC150T PCI 4-port Gigabit Combo Switch Adapter

• HP NC320T PCI Express 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 NC6770 PCI-X Gigabit Server Adapter

• HP NC7770 PCI-X Gigabit Server Adapter

• HP NC7771 PCI-X Gigabit Server Adapter

Embedded adapters:

• HP NC320i Integrated PCI Express Gigabit Server Adapter

• HP NC324i Integrated Dual Port PCI Express 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 Integrated PCI-X Multifunction Gigabit Server Adapter

• HP NC373i PCI Express Multifunction Gigabit Server Adapter

• HP NC7760 PCI-X Gigabit Server Adapter

• HP NC7761 PCI 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 PCI Express Dual Port 1Gb 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

IMPORTANT: For each server adapter in the target server, the driver for the adapter must be

installed and enabled for the server adapter to be upgraded. If the driver is unable to

communicate with the server adapter, the server adapter cannot be updated.

Firmware upgrade utility 49

IMPORTANT: Before updating NC6770 or NC7770 server adapters, move jumper J1 to the

Enable position. After updating each server adapter, move jumper J1 to the Disable position.

NOTE: NC6770, NC7770, and NC7780 server adapters require about 15 minutes each to

update both the PXE and Boot Code.

NOTE: To update the PXE code for embedded and mezzanine adapters, update the system

BIOS.

Drivers
For each server adapter in the target server, the driver for the adapter must be installed and enabled for

the server adapter to be upgraded. If the driver is unable to communicate with the server adapter, the
server adapter cannot be updated.

Installing the firmware utility
The HP Network Adapter Online Firmware Upgrade Utility is located in the \apps\fwupgrade\windows

directory obtained by extracting the HP SoftPaq file. Complete the following steps to download and
extract 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.

The upgrade utility installation is launched by clicking the Smart Component (CPXXXXXX.exe) file
(interactive mode) or by using the command line prompt. The Smart Component for the upgrade utility is
launched using the command line prompt to allow you to pass arguments to alter installation behavior.

Command line syntax
The general command line syntax for the Smart Component installation includes:

CPXXXXXX [/S[ILENT]] [/F[ORCE]] [/R[EBOOT]] [/H[ELP]] [/?]

CPXXXXXX is the command that launches the Smart Component on the target server. The six X's represent
the serialized number assigned to the component.

Command line arguments
The Smart Component recognizes the following command line arguments. Smart Components are not

case-sensitive.

NOTE: All arguments and information enclosed in brackets are optional.

Firmware upgrade utility 50

Command line

Description

argument

/S[ILENT] Supresses console messages. If this argument is omitted

from the command line, console messages are
displayed.

/F[ORCE] Specifies whether an installation will be forced,

regardless of the server adapter firmware version that is
detected on the target server. The argument changes the
Smart Component installation in the following ways:

• If the server adapter firmware on the target server is

current, the firmware reinstalls itself, and the installed
version number remains the same.

• If a newer version of the server adapter firmware is

already installed on the target server, the component
installs itself and downgrades the server adapter
firmware to the older version number.

If this argument is omitted from the command line, the
installation is not forced.

/R[EBOOT] Specifies whether the target server will reboot if the

Smart Component requests a reboot. If this argument is
omitted from the command line and the Smart
Component requests a reboot, the server must be
rebooted manually for the server adapter firmware
upgrade to take effect. The Windows server adapter

upgrade component will NOT request a reboot.
/H[ELP] Displays command line Help information.
/? Displays command line Help information. This argument

is identical to the /H[ELP] argument.

Command Line Examples
The following are examples of how to use the CPXXXXXX.exe command.

Command line

Result
input

CPXXXXXX Deploys the CPXXXXXX.EXE Smart Component on the

target server using the defaults of the component.
CPXXXXXX /F Deploys the CPXXXXXX.EXE Smart Component on the

target server, forcing the installation of the server

adapter firmware.
CPXXXXXX /S Deploys the CPXXXXXX.EXE Smart Component on the

target server using the defaults of the component. All

console messages are suppressed.
CPXXXXXX /S /F

/R

Deploys the CPXXXXXX.EXE Smart Component on the

target server, forcing the installation of the server

adapter firmware and allowing the server to reboot

automatically. All console messages are suppressed.

Common installation log file

Firmware upgrade utility 51

The upgrade installation activity (including errors) is written by the Smart Component to a common
installation log file called CPQSETUP.LOG in the \CPQSYSTEM\LOG subdirectory on the target server.
Information regarding subsequent installation activity is appended to the same log file, which provides a
chronological history of all component installation activity on the target server.

Using the NicFwUpg.exe command line interface

It is possible to launch the HP Online Firmware Upgrade Utility by clicking the executable file during
installation or by using the command line interface. The following information describes how to launch the
utility using the command line interface.

Command line syntax

The utility supports the following commands:

Command Line Input Result

nicfwupg.exe -c Displays the current firmware version of all

HP NC-Series Broadcom adapters in the
system

nicfwupg.exe -l Displays the latest version of HP NC-Series

Broadcom adapters in the system as
determined by versions shipped with the
component.

nicfwupg.exe -a Retuns the saved image version of HP NC-

Series Broadcom adapters in the system
nicfwupg.exe -s Suppresses console output
nicfwupg.exe -f Forces downgrades or restores as needed
nicfwupg.exe -p Requests a restore on all adapters
nicfwupg.exe -e [MAC Address] Requests a restore on one adapter. Supply

the MAC address for the adapter.
nicfwupg.exe -o [MAC Address] Performs an upgrade of boot code for one

adapter. Supply the MAC address for the

adapter.
nicfwupg.exe -x [MAC Address] Performs an upgrade of PXE for one

adapter. Supply the MAC address for the

adapter.
nicfwupg.exe -b [MAC Address] Performs an upgrade of CLP for one

adapter. Supply the MAC address for the

adapter.
nicfwupg.exe -i [filename] Performs an upgrade and stores the image

file to be used during a restore. Supply the

filename.

Using the nicfwup_mf.exe command line interface

It is possible to launch the HP Online Firmware Upgrade Utility for Multifunction adapters by clicking the
executable file during installation or by using the command line interface. The following information
describes how to launch the utility for Multifunction network adapters using the command line interface.

Command line syntax

The utility supports the following commands:

Firmware upgrade utility 52

Return codes

Command Line Input Result

nicfwupg_mf.exe -c Displays the current firmware version of all

HP NC-Series Broadcom adapters in the

system
nicfwupg_mf.exe -l Displays the latest version of HP NC-Series

Broadcom adapters in the system as

determined by versions shipped with the

component.
nicfwupg_mf.exe -a Retuns the saved image version of HP NC-

Series Broadcom adapters in the system
nicfwupg_mf.exe -s Suppresses console output
nicfwupg_mf.exe -f Forces downgrades or restores as needed
nicfwupg_mf.exe -p Requests a restore on all adapters
nicfwupg_mf.exe -e [MAC

Address]
nicfwupg_mf.exe -o [MAC

Address]

nicfwupg_mf.exe -x [MAC
Address]

nicfwupg_mf.exe -b [MAC
Address]

nicfwupg_mf.exe -i [filename] Performs an upgrade and stores the image

Requests a restore on one adapter. Supply

the MAC address for the adapter.

Performs an upgrade of boot code for one

adapter. Supply the MAC address for the

adapter.

Performs an upgrade of PXE for one

adapter. Supply the MAC address for the

adapter.

Performs an upgrade of CLP for one

adapter. Supply the MAC address for the

adapter.

file to be used during a restore. Supply the

filename.

When the upgrade utility has finished running, the component reports a return code to the operating
system or calling application. These return codes are processed by the %errorlevel% operating system
variable and are used to determine the status of a firmware upgrade procedure.

The following summarizes the return codes for the Smart Component installer and HP Online Firmware
Upgrade Utility commands.

Error level Meaning

0 Upgrade component failed to install
1 Upgrade component installed successfully
3 Upgrade component did not detect any supported network

adapters

4 Firmware upgrade was recommended, but the upgrade

component was instructed to not update the firmware

5 All firmware versions are current and an upgrade is not

recommended

6 At least one network adapter has firmware installed that is

newer than the available firmware.

Firmware upgrade utility 53

c-Class BladeSystem utility

The HP Gigabit Server Adapter Firmware Upgrade Utility for c-Class BladeSystem uses two separate
utilities (ccfwupg1.bat and ccfwupg2.bat) to upgrade firmware on the c-Class BladeSystem adapters.

The ccfwupg1.bat command upgrades the Boot Code and Option ROM firmware image on the following
c-Class Multifunction Gigabit Server Adapters:

• HP NC373i Multifunction Gigabit Server Adapter

• HP NC373m Multifunction Gigabit Server Adapter

The ccfwupg2.bat command upgrades the Boot Code and Option ROM firmware image on the following
c-Class Gigabit Server Adapters:

• HP NC326i PCIe Dual Port Gigabit Server Adapter

• HP NC326m PCIe Dual Port Gigabit Server Adapter

• HP NC325m PCIe Quad Port Gigabit Server Adapter

Upgrading firmware
To upgrade the boot code and Option ROM image on the adapter, complete the following:

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.

8. Copy all files and folders from the \apps\ccfwupg\ccfwupg1 directory or the

\apps\ccfwupg\ccfwupg2 directory to a bootable diskette or USB drive.

9. Boot to DOS using the diskette for your adapter.

10. Type ccfwupg1.bat or ccfwupg2.bat and press the Enter key. A confirmation message displays when

the upgrade is complete.

Linux utility

The following information describes how to use the Linux Gigabit Server Adapter Firmware Upgrade
Utility to flash server adapter firmware.

Supported operating systems
The firmware upgrade utility supports the following Linux operating systems:
Linux 32

• Red Hat Enterprise Linux 4

• Red Hat Enterprise Linux 5

• SUSE Linux Enterprise Server 10 x86

Firmware upgrade utility 54

• SUSE Linux Enterprise Server 9 x86

Linux 64

• Red Hat Enterprise Linux 4 for AMD64 and Intel EM64T

• Red Hat Enterprise Linux 5 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

For a complete listing refer to the Linux Readme file located in the HP SoftPaq file.Complete the following
steps to download and extract 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. The hpnicfwupg Linux online firmware upgrade utility is located in the apps\fwupgrade\linux folder.

Supported Gigabit Server Adapters

The upgrade utility provides support for the following adapters:
Standup adapters:

• HP NC150T PCI 4-port Gigabit Combo Switch Adapter

• HP NC320T PCI Express 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

• HP NC1020 Cu Gigabit Server Adapter 32 PCI Single Port

• HP NC6770 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 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 NC373i PCI Express Multifunction Gigabit Server Adapter

Firmware upgrade utility 55

• HP NC7760 PCI-X Gigabit Server Adapter

• HP NC7761 PCI 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 PCI Express Dual Port 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

IMPORTANT: For each server adapter in the target server, the driver for the adapter must be

installed and enabled for the server adapter to be upgraded. If the driver is unable to
communicate with the server adapter, the server adapter cannot be updated.

IMPORTANT: Before updating NC6770 or NC7770 server adapters, move jumper J1 to the

Enable position. After updating each server adapter, move jumper J1 to the Disable position.

NOTE: NC6770, NC7770, and NC7780 server adapters require about 15 minutes each to

update both the PXE and Boot Code.

NOTE: To update the PXE code for embedded and mezzanine adapters, update the system

BIOS.

Drivers
For each server adapter in the target server, the driver for the adapter must be installed and enabled for

the server adapter to be upgraded. If the driver is unable to communicate with the server adapter, the
server adapter cannot be updated.

To download the latest Linux drivers:

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. Open the Linux folder to select drivers.

Upgrading firmware

This firmware upgrade utility updates Boot code, PXE code, and CLP upgrades for c-Class BladeSystem
(NC325m, NC326m and NC373m) server adapter images. The utility is released in RPM format. The file

Firmware upgrade utility 56

names for the packages are hpnicfwupg-<version>.i386.rpm for Linux 32 and hpnicfwupg­<version>.x86_64.rpm for Linux 64. The instructions below describe the x32 version.

1. Before the RPM package is installed, check for the existence of a previous version by issuing the rpm

-q hpnicfwupg command.

2. If a previous version is found, remove it using the rpm -e hpnicfwupg command.

3. Install the RPM package using the hpnicfwupg–<version>.rpm command.

4. Launch the adapter interface by entering ifup ethx or ifconfig ethx up.

5. Launch the upgrade utility in interactive mode by entering hpnicfwupg.

6. Before the upgrade is attempted, a copy of the firmware image is saved. If the firmware upgrade

fails due to an unrecoverable error, you can restore your original firmware interactively by entering
/usr/sbin/hpnicfwupg -p.

If errors have occurred, use the hpnicfwupg utility to restore the server adapter firmware from a backup
copy.

Command line syntax
Use the following command line syntax.

To Use command

Verify previous version of hpnicfwupg
package exists

Remove an old version of hpnicfwupg
package

Install the RPM package # rpm -ivh hpnicfwupg-<version>.rpm
Launch the firmware upgrade utility # user/sbin/hpnicfwupg
Restore original firmware if errors

occur
Uninstall the RPM package # rpm -e hpnicfwupg

# rpm -q hpnicfwupg

# rpm –e hpnicfwupg

# /usr/sbin/hpnicfwupg -p

Command line arguments
The upgrade utility recognizes the following command line arguments.

Command line

Description

argument

–y Yes. Executes the utility with no user interaction. Default

action is implied for all prompts. Messages are
displayed to the screen and to the log. If –y is used with
–s, the behavior is the same as if –s had been specified.

–s Silent. Executes the utility silently with no user

interaction. Default action is implied for all prompts.
Messages are logged but are not displayed on the
screen. If the –y option is used with –s, –y is ignored.

–f Force. Forces the firmware upgrade even if the

firmware installed on the system is newer than the
firmware in the RPM. This option is only valid with –s or
–y. If neither are specified, the option is ignored.

Firmware upgrade utility 57

Command line

Description

argument

–p Previous. Interactively restores previous firmware

images that were automatically backed up prior to the
firmware update. This option is useful for recovering
from firmware upgrade failures. This option can be
used with any other option.

–h Help. Displays the usage message. If this option is used

with any other option, the other options are ignored.

–c Displays server adapters and current firmware version

without performing an updates. This option cannot be
used with any other option.

Restoring firmware image from backup
Before the server adapter firmware image on the server is updated, the current image is saved in a file

called <MAC_ADDRESS>.bc<Boot Code version>.p<PXE version>.bin. The backup file is
saved in the /var/opt/hp/nicfw_backup directory of the target server.

Use the hpnicfwupg command with the –p option to restore the original firmware image after an
upgrade or after an upgrade failure. This option can only be used interactively. The firmware backup
directory is examined for saved images and a message is displayed showing the current firmware
versions and the versions from the saved image. You will be prompted before the restore is attempted. If
more than one saved image is found for a particular server adapter, you will be prompted for each
image.

The following is a sample screen shot of a typical restore.

[root@rdple root]# /usr/sbin/hpnicfwupg -p

Found HP NC7760 Gigabit Server Adapter MAC: 000BCD5035DE
*** WARNING *** - Installed firmware is the same version as the selected
firmware.

Restore Boot Code 2.35 to 2.35 - y/n/q (n):q

Firmware upgrade cancelled by User.

Firmware upgrade log file
The firmware upgrade installation status (including errors) is written by the Linux server adapter upgrade

package to a firmware upgrade log file called nicfwupg.log in the /var/opt/hp subdirectory on
the target server. Information regarding subsequent installation activity is appended to the same log file,
providing a chronological history of all server adapter firmware upgrade activity on the target server.

Return codes
When the Linux server adapter firmware upgrade package has finished running, it reports the following

return codes to the operating system or calling application.

Error

Meaning

level

0 Hpnicfwupg installed all selected firmware successfully. For

options –c and –i , 0 means the information was displayed
correctly.

Firmware upgrade utility 58

Error
level

2 Hpnicfwupg did not attempt firmware upgrade because the

3 Hpnicfwupg attempted to upgrade firmware but one or more

Meaning

installed firmware was up-to-date, the target hardware was not
present, the command was invalid, the user responded no to all
prompts, or the user selected quit in response to a prompt. For
options –c and –i, a 2 means that the information could not be
displayed.

upgrades failed due to an unrecoverable error. This return code
is used even if some of the server adapters were upgraded
successfully.

DOS utility

These notes describe how to use the Gigabit Server Adapter Firmware Upgrade Utility to flash server
adapter firmware.

Flashing consists of using software to replace the current server adapter firmware on a target server with
a new firmware image. Server adapter firmware is typically flashed for the following reasons:

• To support new features

• To correct problems in a previous server adapter firmware version

Customers should upgrade their servers to the latest server adapter firmware version:

• When HP releases a new server adapter firmware version

• When installing a new server adapter

• After purchasing a new server

• When installing a SoftPaq that specifies the need for the latest version of firmware

The Gigabit Server Adapter Firmware Upgrade Utility automatically checks for driver, hardware, and
operating system dependencies, and installs only the correct server adapter firmware upgrades required
by each target server.

Supported Gigabit Server Adapters
The upgrade utility provides support for the following adapters:
Standup adapters:

• HP NC150T PCI 4-port Gigabit Combo Switch Adapter

• HP NC320T PCI Express Gigabit Server Adapter

• HP NC1020 Cu Gigabit Server Adapter 32 PCI Single Port

• HP NC6770 PCI-X Gigabit Server Adapter

• HP NC7770 PCI-X Gigabit Server Adapter

• HP NC7771 PCI-X Gigabit Server Adapter

Embedded adapters:

• HP NC7760 PCI-X Gigabit Server Adapter

Firmware upgrade utility 59

• HP NC7761 PCI Gigabit Server Adapter

• HP NC7780 Gigabit Server Adapter

• HP NC7781 PCI-X Gigabit Server Adapter

• HP NC7782 Dual Port PCI-X Gigabit Server Adapter

IMPORTANT: For each server adapter in the target server, the driver for the adapter must be

installed and enabled for the server adapter to be upgraded. If the driver is unable to

Drivers

communicate with the server adapter, the server adapter cannot be updated.

IMPORTANT: Before updating NC6770 or NC7770 server adapters, move jumper J1 to the

Enable position. After updating each server adapter, move jumper J1 to the Disable position.

NOTE: NC6770, NC7770, and NC7780 server adapters require about 15 minutes each to

update both the PXE and Boot Code.

NOTE: To update the PXE code for embedded adapters update the system BIOS.

For each server adapter in the target server, the driver for the adapter must be installed and enabled for
the server adapter to be upgraded. If the driver is unable to communicate with the server adapter, the
server adapter cannot be updated.

Upgrading firmware

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.

8. Click the SoftPaq file (SP31728) located in the \apps\fwupgrade\dos directory.

9. Execute the downloaded file and follow the on-screen instructions. After the files have been

unpacked, you may delete the SoftPaq file that you downloaded.

10. Copy these files to a bootable DOS diskette.

7781V235 BIN
150TV318 BIN
6770V219 BIN
7760V237 BIN
7761V318 BIN
7770V219 BIN
7771V235 BIN
7780V219 BIN
1020V318 BIN

Firmware upgrade utility 60

7782327B BIN
NICFWUPG BAT
PT5704C2 36
PXE_V322 BIN
Q57UDIAG EXE
SP29044 TXT
PXE_V778 BIN
PXE_V839 BIN
320TV355 BIN

11. Boot the system using the DOS diskette.

12. Run NICFWUPG.BAT from a command prompt.

Firmware upgrade utility 61

Adapter configurations

In this section

HP NC-Series Broadcom adapters............................................................................................................ 62

HP NC-Series Multifunction adapters ........................................................................................................ 66

HP NC-Series Intel adapters..................................................................................................................... 69

Windows .............................................................................................................................................. 91

Novell Netware ................................................................................................................................... 110

Solaris ................................................................................................................................................ 122

HP NC-Series Broadcom adapters

Keywords for Q57 NDIS2 driver

This document describes the keywords for the Q57 NDIS 2 driver version 7.65 (Q57.DOS).
The following custom keywords are used in PROTOCOL.INI:

• BUSNUM

• DEVNUM

• FUNCNUM or PORTNUM

• LineSpeed

• Duplex

• NodeAddress

• FixCheckSumOff

Descriptions

• BUSNUM and DEVNUM—These two keywords are used concurrently and have been included for

manufacturing purposes. Do not use them unless you are familiar with PCI device configuration.
These two keywords are needed if multiple NC1020, NC67xx, and/or NC77xx boards are in a
system and a specific adapter (or adapters) needs to be loaded in specific order. BUSNUM specifies
the PCI bus number, and DEVNUM specifies the device number given to the board when configured
by the PCI BIOS. The values are in decimal.

• LineSpeed—This decimal parameter, 10 or 100, specifies the speed of the network connection.

According to IEEE specifications, line speed of 1000 cannot be forced and its only achievable by
auto negotiation.

• Duplex—This string parameter, HALF or FULL, specifies duplex mode on the Ethernet controller. The

LineSpeed parameter must be set when this keyword is used. If neither the Duplex nor the LineSpeed
parameters are specified the Ethernet controller will default to autonegotiate mode.

• NodeAddress—This string parameter specifies the network address used by the Ethernet controller. If

Multicast Address or Broadcast Address was specified, the default MAC Address will be used.

Adapter configurations 62

• FixCheckSumOff—This string parameter turns off the driver work-around for the TCP/IP stack to

recognize the 1's complimented version of the checksum.

The following are examples of the use of these keywords in the protocol.ini.

[Q57]
DriverName = "Q57$"
BusNum = 3
DevNum = 14
PortNum = 2
LineSpeed = 100
Duplex = Full
NodeAddress = "001020304050"

To add more adapters (up to four), repeat the entry below, where n can be from 1 to 3.

[Q57_n]
DriverName = "Q57$"
BusNum =
DevNum =

The following examples use additional entries to load more than one adapter in the protocol.ini.

• [Q57]

DriverName = "Q57$"
BusNum = 3
DevNum = 10

• [Q57_1]

DriverName = "Q57$"
BusNum = 3
DevNum = 11

• [Q57_2]

DriverName = "Q57$"
BusNum = 3
DevNum = 12

• [Q57_3]

DriverName = "Q57$"
BusNum = 3
DevNum = 13

Keywords for B06 NDIS2 driver

This document describes the keywords for the B06 BNDIS 2 driver (bxnd20x.DOS).
The following keywords are supported through the PROTOCOL.INI file. If a keyword is not present in the

PROTOCOL.INI, the default value is chosen.

Adapter configurations 63

• DRIVERNAME

o Possible value: BXND20X$
o This field is case sensitive

• LINESPEED

o Possible values: 10, 100, or 1000
o Default: AUTONEG

• BUSNUM

o Possible values: the bus slot number the NC37xx/NC380x device is on
o Default: the bus slot number occupied by one of NC37xx/NC380x devices in the system

• DEVNUM

o Possible value: the device number the NC37xx/NC380x device is on
o Default: the device number occupied by one of NC37xx/NC380x devices in the system

• FUNCNUM

o Possible values: the function number the NC37x/NC380x device is on
o Default: the function number occupied by one of NC37x/NC380x devices in the system

• DUPLEX

o Possible values: half or full (LineSpeed is required when this keyword is used)
o Default: full

• NODEADDRESS

o Possible values: 6 hex bytes looking like "0A0B0C0D0E0F"
o Default: the MAC address for the selected NC37xx/NC380x device

Known limitations:
For Windows Server 2003 or Window Server 2003 x64 self-installation, a smartdrv driver needs to be

loaded. Otherwise, bad performance or even incorrect I/O write errors might occur.

PXE configuration: HP NC-series Broadcom and Multifunction
adapters

NOTE: PXE is not supported on the NC150T adapter.

The Pre-boot Execution Environment (PXE) of HP adapters has been upgraded to allow PXE functions to
work with the HP ProLiant servers.

The HP NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters have
PXE support. PXE is a software protocol that allows your networked computer to boot with the images
provided by remote servers across the network. PXE operates in a client/server environment. A network
consists of one or more boot servers that provide boot images to multiple computers through the network.

The PXE driver complies with the PXE-2.1 specification. The PXE driver is released with both monolithic
and split binary images. This feature provides flexibility to users in different environments in which the
motherboard may or may not have built-in base-code.

Adapter configurations 64

HP PXE implementation is supported in the following environments:

• Linux Red Hat PXE Server. HP PXE clients are able to remote-boot and utilize network resources (for

example, NFS mount) and to do Linux installation. In the case of a remote boot, the Linux universal
driver binds seamlessly with the HP UNDI (Universal Network Driver Interface) and provides a
network interface in the Linux remote-booted client environment.

• Microsoft® Windows® 2000, Windows 2003, and Windows 2003x64 Remote Installation

Services (RIS). HP PXE clients are able to install from the network.

• Intel APITEST. The HP PXE driver passes all API compliance test suites.

• DOS UNDI. Universal NDIS seamlessly binds with HP UNDI to provide NDIS2 interface to the upper-

layer protocol stack. This allows computers to connect to network resources in a DOS environment.

• 3Com® Boot Server.

Client setup
Setting up PXE client for NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server

Adapters involves enabling/disabling the PXE feature and setting up the BIOS for the boot order.
Boot method (NC32xx, NC37xx, NC380x, NC1020, NC6770, NC7770, and NC7771 only)
By default, PXE detects if the BIOS supports BBS (BIOS Boot Specification). If the BIOS supports BBS, then

PXE uses BBS as the boot method. If the BIOS does not support BBS, then PXE uses Int18h instead.
However, for some machines equipped with an old BIOS, this process may not work. In case of an old
BIOS, users must force PXE to use Int18h, Int19h, or BBS as the boot method.

To specify the boot method, press the following keys when you see the startup banner.

Broadcom Gigabit Ethernet Boot Agent

2.2.6
Copyright (c) 2000 Broadcom
Corporation
All rights reserved

• For Int18h: Press the Ctrl+F8 keys

• For Int19h: Press the Ctrl+F9 keys

• For BBS: Press the Ctrl+F10 keys

Setup BIOS
To boot from the network with PXE, make PXE the first bootable device under BIOS. This procedure

depends on server BIOS implementation. Refer to the user manual for the server for additional
information.

Server setup
Refer to the following instructions for your operating system.
Windows® 2000
The current version of Windows® 2000 does not include a network driver for the NC32xx, NC37xx,

NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters. To perform remote installation
with PXE, include a network driver for these adapters as part of the client's installation image on the
server. Refer to Microsoft® Article ID Q246184, "How to Add Third-Party OEM Network Adapters to RIS
Installations."

DOS UNDI/APITEST

Adapter configurations 65

To boot in DOS and connect to a network for the DOS environment, download the Intel® PXE PDK from
the Intel® web site. This PXE PDK comes with a TFTP/ProxyDHCP/Boot server. The PXE PDK can be
downloaded from the Intel website (http://downloadfinder.intel.com/scripts-df-

external/Support_Intel.aspx).

Red Hat Linux
Red Hat Linux 7.2 (or higher) distribution has PXE server support. It allows users to perform a complete

Linux installation over the network. Distribution also comes with boot images—boot kernel (vmlinux) and
initial ram disk (initrd). These two images can be found in the HP SoftPaq file.

• /misc/src/trees/boot/vmlinux

• /misc/src/trees/initrd-network.img

Refer to Red Hat documentation for instructions on installing PXE server on Linux.
Initrd.img, distributed with Red Hat 7.2, does not have a Linux network driver for the NC320T, NC320i,

NC324i, NC325i, NC325m, NC326i, NC326m, NC1020, NC67xx, and NC77xx Gigabit Server
Adapters.

• /images/pxeboot/vmlinux

• /images/pxeboot/initrd.img

Intel® has also created patches to the Linux PXE server code to allow clients to perform a remote boot.
You can download these patches from the Intel website (http://downloadfinder.intel.com/scripts-df-

external/Support_Intel.aspx).

A remote boot does not require a standard Linux network driver for the HP NC320T, NC320i, NC324i,
NC325i, NC325m, NC326i, NC326m, NC1020, NC67xx, and NC77xx Gigabit Server Adapters.
After the PXE client downloads the Linux kernel and initial ram disk, the Linux universal driver, that came
with the Linux distribution, will bind with the UNDI code of the PXE to form a Linux network driver.

HP NC-Series Multifunction adapters

Accelerated iSCSI devices

The iSCSI protocol transports block-level storage requests over TCP connections. Using the iSCSI protocol,
systems can connect to remote storage and use it as a physical disk (although the remote storage
provider, or "target," may actually be providing "virtual" physical disks).

HP Multifunction Gigabit Server Adapters can be enabled as virtual iSCSI host bus adapters (HBAs),
which provide the ability to run iSCSI protocol over offloaded TCP connections. By offloading the TCP
connection processing to a Multifunction Server Adapter the CPU utilization is reduced, which provides
additional processing capacity for applications.

iSCSI is enabled and network settings are configured for the iSCSI device through the Network
Configuration Utility (NCU). Configuration is limited to IP configuration (including DHCP support), user­specified MAC address, and VLAN ID (only one allowed for the iSCSI device).

Prerequisites
To use the Multifunction Server Adapter iSCSI accelerating feature, Microsoft® iSCSI Software Initiator

version 2.0 or later must be installed on your system. This software is required to configure the iSCSI
protocol, including discovery portals, iSCSI targets, authentication, and so on. The command line utility
iscsicli.exe, which is part of Microsoft iSCSI Software Initiator can also be used to configure iSCSI

Adapter configurations 66

protocol. See the Microsoft website (http://www.microsoft.com) to download the Microsoft iSCSI
Software Initiator installation wizard software and to obtain installation and usage information.

The accelerating iSCSI feature comes standard with standup HP Multifunction Server Adapters.
Accelerating iSCSI capabilities are available for embedded HP Multifunction Gigabit Server Adapters
through the purchase and installation of an HP ProLiant Essentials Accelerated iSCSI Pack license
("Accelerated iSCSI for embedded HP Multifunction server adapters" on page 153).

Configuring advanced settings parameters
If iSCSI is enabled on a Multifunction adapter port, you can adjust the SRB (iSCSI Request Block) Timeout

Delta setting and create an iSCSI VLAN for the adapter. Increasing this value may help prevent I/O
timeouts if your network is highly congested and packets are being dropped frequently.

iSCSI adapter information includes the following:

o Current MAC Address. The current MAC address for the iSCSI device.
o iSCSI Driver Name. The name of the driver for the iSCSI device
o iSCSI Driver Version. The version of the driver for the iSCSI device.
o Default Gateway. The default route for the iSCSI device.
o Subnet Mask. The subnet mask (dotted decimal) for the iSCSI device.
o iSCSI VLAN Id. The identification number (if any) for the virtual iSCSI VLAN device.
o iSCSI Packet Priority. The packet priority for the iSCSI device.
o SRB Timeout Delta. The increase to the timeout value for I/O operations.
o Page File Created. Indicates whether or not the Windows page file was created on an iSCSI

drive that is attached to the adapter. The values are Yes and No.

o DHCP (Dynamic Host Configuration Protocol). Enabled indicates that DHCP is used to acquire IP

configuration; Disabled indicates that the statically configured IP configuration is used.

o IP Address. The IPv4 address (dotted decimal) for the iSCSI device.

iSCSI boot configuration: Multifunction adapters

HP iSCSI boot is currently supported on Linux operating systems only.
The HP iSCSI boot feature allows you to boot from a remote disk (known as the iSCSI target) on a Storage

Area Network (SAN) without having to directly attach a boot disk.
Booting from a remote disk on a SAN allows you to centralize the boot process and consolidate

equipment resources. Unlike other implementations, iSCSI boot does not require a separate DHCP server
or a PXE server.

For more information about HP iSCSI Boot refer to the HP iSCSI Boot for Linux User Guide.

PXE configuration: HP NC-series Broadcom and Multifunction
adapters

NOTE: PXE is not supported on the NC150T adapter.

The Pre-boot Execution Environment (PXE) of HP adapters has been upgraded to allow PXE functions to
work with the HP ProLiant servers.

Adapter configurations 67

The HP NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters have
PXE support. PXE is a software protocol that allows your networked computer to boot with the images
provided by remote servers across the network. PXE operates in a client/server environment. A network
consists of one or more boot servers that provide boot images to multiple computers through the network.

The PXE driver complies with the PXE-2.1 specification. The PXE driver is released with both monolithic
and split binary images. This feature provides flexibility to users in different environments in which the
motherboard may or may not have built-in base-code.

HP PXE implementation is supported in the following environments:

• Linux Red Hat PXE Server. HP PXE clients are able to remote-boot and utilize network resources (for

example, NFS mount) and to do Linux installation. In the case of a remote boot, the Linux universal
driver binds seamlessly with the HP UNDI (Universal Network Driver Interface) and provides a
network interface in the Linux remote-booted client environment.

• Microsoft® Windows® 2000, Windows 2003, and Windows 2003x64 Remote Installation

Services (RIS). HP PXE clients are able to install from the network.

• Intel APITEST. The HP PXE driver passes all API compliance test suites.

• DOS UNDI. Universal NDIS seamlessly binds with HP UNDI to provide NDIS2 interface to the upper-

layer protocol stack. This allows computers to connect to network resources in a DOS environment.

• 3Com® Boot Server.

Client setup
Setting up PXE client for NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server

Adapters involves enabling/disabling the PXE feature and setting up the BIOS for the boot order.
Boot method (NC32xx, NC37xx, NC380x, NC1020, NC6770, NC7770, and NC7771 only)
By default, PXE detects if the BIOS supports BBS (BIOS Boot Specification). If the BIOS supports BBS, then

PXE uses BBS as the boot method. If the BIOS does not support BBS, then PXE uses Int18h instead.
However, for some machines equipped with an old BIOS, this process may not work. In case of an old
BIOS, users must force PXE to use Int18h, Int19h, or BBS as the boot method.

To specify the boot method, press the following keys when you see the startup banner.

Broadcom Gigabit Ethernet Boot Agent

2.2.6
Copyright (c) 2000 Broadcom
Corporation
All rights reserved

• For Int18h: Press the Ctrl+F8 keys

• For Int19h: Press the Ctrl+F9 keys

• For BBS: Press the Ctrl+F10 keys

Setup BIOS
To boot from the network with PXE, make PXE the first bootable device under BIOS. This procedure

depends on server BIOS implementation. Refer to the user manual for the server for additional
information.

Server setup
Refer to the following instructions for your operating system.
Windows® 2000

Adapter configurations 68

The current version of Windows® 2000 does not include a network driver for the NC32xx, NC37xx,
NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters. To perform remote installation
with PXE, include a network driver for these adapters as part of the client's installation image on the
server. Refer to Microsoft® Article ID Q246184, "How to Add Third-Party OEM Network Adapters to RIS
Installations."

DOS UNDI/APITEST
To boot in DOS and connect to a network for the DOS environment, download the Intel® PXE PDK from

the Intel® web site. This PXE PDK comes with a TFTP/ProxyDHCP/Boot server. The PXE PDK can be
downloaded from the Intel website (http://downloadfinder.intel.com/scripts-df-

external/Support_Intel.aspx).

Red Hat Linux
Red Hat Linux 7.2 (or higher) distribution has PXE server support. It allows users to perform a complete

Linux installation over the network. Distribution also comes with boot images—boot kernel (vmlinux) and
initial ram disk (initrd). These two images can be found in the HP SoftPaq file:

• /misc/src/trees/boot/vmlinux

• /misc/src/trees/initrd-network.img

Refer to Red Hat documentation for instructions on installing PXE server on Linux.
Initrd.img, distributed with Red Hat 7.2, does not have a Linux network driver for the NC320T, NC320i,

NC324i, NC325i, NC325m, NC326i, NC326m, NC1020, NC67xx, and NC77xx Gigabit Server
Adapters.

• /images/pxeboot/vmlinux

• /images/pxeboot/initrd.img

Intel® has also created patches to the Linux PXE server code to allow clients to perform a remote boot.
You can download these patches from the Intel website (http://downloadfinder.intel.com/scripts-df-

external/Support_Intel.aspx).

A remote boot does not require a standard Linux network driver for the HP NC320T, NC320i, NC324i,
NC325i, NC325m, NC326i, NC326m, NC1020, NC67xx, and NC77xx Gigabit Server Adapters.
After the PXE client downloads the Linux kernel and initial ram disk, the Linux universal driver, that came
with the Linux distribution, will bind with the UNDI code of the PXE to form a Linux network driver.

HP NC-Series Intel adapters

Boot Agent

The Intel® Boot Agent is a software product that allows your networked client computer to boot using a
program code image supplied by a remote server.

Implementation support for the Boot Agent includes:

• Multi-protocol boot ROM code designed for remote booting from Gigabit Ethernet Adapters

• Compliance with the Pre-boot eXecution Environment (PXE) Version 2.1 Specification

• Remote Program Load (RPL) runtime and loader software included with some versions of the Boot

Agent

Intel® Boot Agent offers:

Adapter configurations 69

• Compliance with the Wired for Management Baseline (WfM) 2.0 specification

• Compatibility with legacy boot agent environments that use BOOTP protocol

• Customization in pre-boot, Windows®, and DOS environments

Operating environment
The Boot Agent operates in a client/server environment. Often, in this environment, one or more servers

provide remote boot services to a large number of client computers through a common network. The
computer system where the Intel® Boot Agent is loaded is considered to be a client with respect to the
remote boot capability even if that system acts as a server after the system has finished booting.

Configuration options
The Intel® Boot Agent software provides configuration options that allow you to customize the behavior of

the Boot Agent software. You can configure the Boot Agent in a pre-boot environment (before the
operating system is loaded).

Configuring the Boot Agent in a pre-boot PXE or RPL environment
You can customize the behavior of the Boot Agent software through a pre-boot (operating system

independent) configuration setup program contained within the adapter's flash ROM. A single user
interface allows you to configure PXE and RPL protocols on HP Gigabit adapters. You can access this pre­boot configuration setup program each time the client computer cycles through the boot process. The boot
process is triggered whenever any of the following boot events occur:

• Power on

• Hard reset (Reset button on system, if available)

• Soft reset (Ctrl+Alt+Del)

• Operating system or application-initiated system restart

When the boot process begins, the screen clears and the computer begins its Power On Self-Test (POST)
sequence. Shortly after completion of the POST, the Boot Agent software stored in flash ROM executes.
The Boot Agent then displays an initialization message, similar to the one below, indicating that it is
active:

Initializing Intel(R) Boot Agent Version X.X.XX
PXE 2.0 Build 083 (WfM 2.0)
Press Ctrl+S to enter the Setup Menu.

This display may be hidden by the manufacturer's splash screen. Refer to your manufacturer's
documentation for details.

To customize the behavior of the Boot Agent software in a pre-boot PXE or RPL environment complete the
following steps:

1. Press the Ctrl+S keys immediately after the initialization message appears. A configuration setup

menu appears allowing you to set configuration values for the Boot Agent. The configuration setup
menu is the same for both kinds of adapters.

If you do not press the Ctrl+S keys, the Boot Agent software will proceed with the boot process
eventually bringing up the operating system. If you miss your opportunity to press the Ctrl+S keys
within the allowed number of seconds, reboot the computer to try again. If you select a Setup Menu
Wait Time setting of zero or a Show Setup Prompt setting of Disabled, you will not be prompted to
press the Ctrl+S keys even though you can still enter the configuration setup menu using this key
combination.

Adapter configurations 70

The configuration setup menu shows a list of configuration settings on the left and their
corresponding values on the right. Key descriptions near the bottom of the menu indicate how to
change values for the configuration settings. For each selected setting, a brief "mini-Help"
description of its function appears just above the key descriptions.

2. Select the setting you need to change by using the arrow keys.

3. After you have accessed the setting you want to change, press the Spacebar until the desired value

appears.

4. If you want to change additional settings, repeat steps 2 and 3.

5. After you have completed your changes, press the F4 key to update the adapter with the new values.

Any changed configuration values are applied as the boot process resumes.

Boot Agent configuration settings

Configuration

Possible values Description

settings

Network Boot
Protocol

Boot Order

Show Setup
Prompt

• PXE (Preboot

eXecution
Environment)

• RPL (Remote

Program Load)

• Use BIOS Setup

Boot Order

• Try network first,

then local drives

• Try local drives

first, then
network

• Try network only

• Try local drives

only

• Enabled

• Disabled

Controls whether the RPL or PXE boot protocol will be used. Select
PXE for use with WfM-compatible network management programs,
such as Intel® LANDesk® Management Suite, Windows 2000 RIS,
and Linux®.

Select RPL for legacy-style remote booting, as well as for Novell®
Netware® remote boot solutions.

Depending on the configuration of the Boot Agent, this parameter
may not be changeable.

Sets the boot order in which devices are selected during boot up if
the computer does not have its own control method.

If your client computer's BIOS supports the BIOS Boot Specification
(BBS), or allows PnP-compliant selection of the boot order in the
BIOS setup program, then this setting will always be Use BIOS Setup
Boot Order and cannot be changed. In this case, refer to the BIOS
setup manual specific to your client computer to set up boot options.

If your client computer does not have a BBS- or PnP-compliant BIOS,
you can select any one of the other possible values listed for this
setting except for Use BIOS Setup Boot Order.

Controls whether or not the Boot Agent displays the Ctrl+S prompt
after POST.

If you select Enabled, the Ctrl+S prompt appears after POST so that
you can press Ctrl+S within the number of seconds allowed by the
Setup Menu Wait Time setting to display the configuration setup
menu.

If you select Disabled and/or the Setup Menu Wait Time setting is
zero, the Ctrl+S setup prompt will not appear during the boot
process. However, you can display the configuration setup menu by
repeatedly pressing the Ctrl+S keys immediately after POST until the
menu appears. If the configuration setup menu does not appear
after repeatedly pressing the Ctrl+S keys, you were likely not fast
enough. In this case, reboot and try again.

Adapter configurations 71

Configuration

Possible values Description

settings

Setup Menu Wait
Time

• 0 seconds

• 2 seconds

• 3 seconds

• 5 seconds

Controls the number of seconds the Boot Agent waits for you to
press the Ctrl+S keys, so as to suspend the boot process and then
configure the way the Boot Agent operates.

If you select a Setup Menu Wait Time setting of zero and/or a Show
Setup Prompt setting of Disabled, the Ctrl+S setup prompt will not
appear during the boot process. However, you can still display the
configuration setup menu by repeatedly pressing the Ctrl+S keys
immediately after POST until the menu appears. If the configuration
setup menu does not appear after repeatedly pressing the Ctrl+S
keys, you were likely not fast enough. In this case, reboot and try
again.

If during PXE or RPL boot more than one adapter is installed in a computer and you want to boot from the
boot ROM located on a specific adapter, you can do so by removing the adapter from the BIOS Boot
Order or disabling the flash by running IBAUTIL -FlashDisable on the desired adapter.

To display diagnostics information:
Anytime the configuration setup menu is displayed, you may press the D key to display diagnostics

information in the lower half of the screen. This information can be helpful during interaction with HP
Customer Support personnel or your IT team members. After you press the D key, the information
displayed remains until you leave the configuration setup screen (either by pressing the F4 key, pressing
the Esc key, or by rebooting the computer). For more information about how to interpret the information
displayed, refer to the "Diagnostics information for pre-boot PXE or RPL environments" section.

Auxiliary DOS utilities
The IBAUtil allows you to install and configure the Boot Agent using the DOS environment. IBAUtil is a

utility program that provides an alternative means for modifying the adapter configuration settings. Use
IBAUtil to:

• Change the default settings of your HP NC310F, NC3123, NC6170, or NC7170 adapter.

• Enable/disable the Wake-on-LAN (WOL) and Intel® Boot Agent capabilities.

• Allow in-the-field upgrades to the image stored in the flash component of the adapter.

Wake-On-LAN and Intel® Boot Agent in a DOS environment
Use IBAUtil to enable or disable WOL or Boot Agent features. To obtain this utility:

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.

The IBAUtil file is located in the APPS\BOOTAGNT\N100X directory.

• Wake-On-LAN. When enabled, the adapter can react to special "wake up" packets and power up

the computer without end user intervention. However, there is a higher power draw when the system

Adapter configurations 72

is in the suspended state when this is enabled. It is strongly recommended that no more than two
adapters should have this feature enabled per computer.

• Intel Boot Agent. When enabled, the computer can initiate PXE/RPL boot if a valid flash image is

present on the adapter.

Running IBAUtil in DOS
IBAUtil (for DOS) must be run with the computer booted to DOS only. This utility cannot be run in a DOS

window in any Microsoft® Windows® product or in DOS compatibility mode in IBM OS/2.
The syntax for issuing IBAUtil command line parameters in DOS is:

IBAUTIL [-option]...

DOS command line parameters
IBAUtil accepts up to 16 simultaneous parameters and does not perform both operations if orthogonal

parameters (like the commands -FLASHENABLE -FLASHDISABLE used together) are supplied. If opposing
parameters are specified, IBAUtil exits with an error.

The parameters are grouped with their orthogonal pairs, where applicable. -HELP, -EXITCODES and ­IMAGEVERSION have special overriding characteristics. Unless noted, all other parameters may be used
in conjunction with all other parameters.

If you enter IBAUTIL without any command line options, the utility displays a listing of all of the Intel®
network adapters found in your system.

Valid parameters are listed below. All other parameters generate an error.

Parameter Description

-HELP or -? Displays command line help and exits. When -HELP is set, all other
parameters are ignored.

-EXITCODES Displays exit code help. When -EXITCODES are set, all other
parameters except -HELP are ignored.

-IMAGEVERSION or -IV Displays the PXE versions stored within the IBAUtil. When ­IMAGEVERSION is set, all other parameters except -EXITCODES
and -HELP are ignored.

Adapter Selection Options

-ALL Selects all adapters found in system, works for both EEPROM and
Flash activity.

-NIC=XX Selects a specific adapter (1–16).

-BLINK Blinks the LED on the selected adapter for 10 seconds to provide a
method for identifying an adapter.

Flash Programming Options

-AUTO or -QUIET Runs IBAUtil without asking for user intervention. It does NOT
create a backup image. This parameter must be used with -NIC or ­ALL if there is more than one adapter in the system. It runs without ­ALL or -NIC=xx if there is only one adapter in the system.

-UPGRADE or -UP Downloads the Boot Agent stored within IBAUtil to the adapters in
the system.

-FLASHENABLE or -FE Enables Boot ROM. Saves

-FLASHDISABLE or -FD Disables Boot ROM.

Adapter configurations 73

Parameter Description

-SAVE Saves existing Intel Boot Agent and EEPROM settings to a file. The
file is named based on the PCI Vendor and Device ID of the
adapter.

-RESTORE Restores previously saved Intel Boot Agent image. IBAUtil looks for
a file name based on the PCI Vendor and Device ID of the
adapter. If -RESTORE is used with -UPGRADE, an error is
generated.

Power Management Options

-WOLDISABLE or -WOLD Disables WOL bit on Fast Ethernet and disables APMPME and

-WOLENABLE or -WOLE Enables WOL bit on Fast Ethernet and enables APMPME and

-LWSENABLE OR -LWSE Enables changing the legacy OS Wakeup Support Option on

-LWSDISABLE OR -LWSD Disables changing the legacy OS Wakeup Support Option on

PXE/RPL Configuration Options

-SETUPENABLE or -STE Enables Setup Menu.

APME EEPROM bits on gigabit.

APME EEPROM bits on gigabit.

10/100 adapters.

10/100 adapters.

-SETUPDISABLE OR -STD Disables Setup Menu.

-DEFAULTCONFIG or -DEFCFG Resets configuration and control words in the EEPROM back to
default settings.

-TITLEENABLE OR -TLE Enables initial title message.

-TITLEDISABLE OR -TLD Disables initial title message.

-PROTOCOLENABLE OR -PROE Enables changing the boot protocol option.

-PROTOCOLDISABLE OR -PROD Disables changing the boot protocol option.

-ORDERENABLE OR -ORDE Enables changing the boot order option.

-ORDERDISABLE OR -ORDD Disables changing the boot order option.

-SETWAITTIME=X or -SWT=X Sets the setup delay time for the adapter to X seconds. Valid delay
times are 0, 2, 3, and 5. Only the first instance of this parameter is
valid. All other instances of the parameter generate an error.

-RPL BOOT Sets the network boot protocol to RPL if an RPL image is present in
the adapter's flash.

-PXE BOOT Sets the network boot protocol to PXE if a PXE image is present in
the adapter's flash.

DOS error codes

IBAUtil returns codes to the DOS command line when an error occurs.

• 0–Success

• 1–Operator termination

• 2–Invalid adapter

• 3–Bad command line parameter

• 4–EEPROM checksum failure

Adapter configurations 74

• 5–EEPROM read failure

• 6–EEPROM write failure

• 7–EEPROM dump failure

• 8–(Not used)

• 9–No memory

• 10–No adapters found

Examples of IBAUtil command lines
The following are examples of some typical IBAUtil command lines.

• Disables WOL on all HP network adapters:

IBAUTIL -ALL -WOLDISABLE

• Enables WOL on the second HP network adapter found in your system:

IBAUTIL -NIC=2 -WOLENABLE

• Updates the Boot Agent image on all HP network adapters:

IBAUTIL -ALL -UPGRADE

• Enables the Boot ROM on the first HP Network Adapter found in your system:

IBAUTIL -NIC=1 -FE

Boot Agent messages
The following error and information messages may be displayed during initialization. Possible causes and

how to avoid an error condition are provided where applicable.

• Flash device wrong size

This error message can occur when using IBAUtil. The full version of Boot Agent software cannot be
loaded into a flash ROM device smaller than 64 KB. If a 32 KB (or smaller) flash ROM device is
detected in the adapter, the flash update software returns this message. Assuming the device is
socketed, remove the "too small" device and install a blank 64 KB (or larger) flash ROM device.

• Invalid PMM function number

PMM is not installed or is not working correctly. Try updating the BIOS.

• PMM allocation error

PMM could not or did not allocate the requested amount of memory for driver usage.

• Press Ctrl+S to enter the Setup Menu.

Instructs you how to enter the configuration setup menu.

• PXE-E00: This system does not have enough free conventional memory. The Boot Agent cannot

continue.
System does not have enough free memory to run PXE image. The Boot Agent was unable to find

enough free base memory (below 640K) to install the PXE client software. The system cannot boot
via PXE in its current configuration. The error returns control to the BIOS and the system does not
attempt to remote boot. If this error persists, try updating your system's BIOS to the most-recent
version. Contact your system administrator or HP customer support to resolve the problem.

• PXE-E01: PCI Vendor and Device IDs do not match!

Image vendor and device ID do not match those located on the card. Be sure the correct flash image
is installed on the adapter.

• PXE-E04: Error reading PCI configuration space. The Boot Agent cannot continue.

Adapter configurations 75

PCI configuration space could not be read. Machine is probably not PCI compliant. The Boot Agent
was unable to read one or more of the adapter's PCI configuration registers. The adapter may be
misconfigured, or the wrong Boot Agent image may be installed on the adapter. The Boot Agent
returns control to the BIOS and not attempt to remote boot. Try to update the flash image. If this does
not solve the problem, contact your system administrator or HP Customer Support.

• PXE-E05: The LAN adapter's configuration is corrupted or has not been initialized. The Boot Agent

cannot continue.
The adapter's EEPROM is corrupted. The Boot Agent determined that the adapter EEPROM checksum

is incorrect. The agent will return control to the BIOS and not attempt to remote boot. Try to update
the flash image. If this does not solve the problem, contact your system administrator or HP Customer
Support.

• PXE-E06: Option ROM requires DDIM support.

The system BIOS does not support DDIM. The BIOS does not support the mapping of the PCI
expansion ROMs into upper memory as required by the PCI specification. The Boot Agent cannot
function in this system. The Boot Agent returns control to the BIOS and does not attempt to remote
boot. You may be able to resolve the problem by updating the BIOS on your system. If updating
your system's BIOS does not solve the problem, contact your system administrator or HP customer
support to resolve the problem.

• PXE-E07: PCI BIOS calls not supported.

BIOS-level PCI services not available. Machine is probably not PCI compliant.

• PXE-E09: Unexpected UNDI loader error. Status == xx

The UNDI loader returned an unknown error status. xx is the status returned.

• PXE-E20: BIOS extended memory copy error.

BIOS could not move the image into extended memory.

• PXE-E20: BIOS extended memory copy error. AH == xx

Error occurred while trying to copy the image into extended memory. xx is the BIOS failure code.

• PXE-E51: No DHCP or BOOTP offers received.

The Boot Agent did not receive any DHCP or BOOTP responses to its initial request. Be sure that
your DHCP server (and/or proxyDHCP server, if one is in use) is properly configured and has
sufficient IP addresses available for lease. If you are using BOOTP, be sure that the BOOTP service is
running and is properly configured.

• PXE-E53: No boot filename received.

The Boot Agent received a DHCP or BOOTP offer, but has not received a valid filename to
download. If you are using PXE, please check your PXE and BINL configuration. If you are using
BOOTP, be sure that the TFTP service is running and that the specific path and filename are correct.

• PXE-E61: Media test failure.

The adapter does not detect link. Be sure that the cable is good and is attached to a working hub or
switch. The link light visible from the back of the adapter should be lit.

• PXE-EC1: Base-code ROM ID structure was not found.

No base code can be located. An incorrect flash image is installed or the image has become
corrupted. Try to update the flash image.

• PXE-EC3: BC ROM ID structure is invalid.

Adapter configurations 76

Base code cannot be installed. An incorrect flash image is installed or the image has become
corrupted. Try to update the flash image.

• PXE-EC4: UNDI ROM ID structure was not found.

UNDI ROM ID structure signature is incorrect. An incorrect flash image is installed or the image has
become corrupted. Try to update the flash image.

• PXE-EC5: UNDI ROM ID structure is invalid.

The structure length is incorrect. An incorrect flash image is installed or the image has become
corrupted. Try to update the flash image.

• PXE-EC6: UNDI driver image is invalid.

The UNDI driver image signature is invalid. An incorrect flash image is installed or the image has
become corrupted. Try to update the flash image.

• PXE-EC8: !PXE structure was not found in UNDI driver code segment.

The Boot Agent cannot locate the needed !PXE structure resource. An incorrect flash image is
installed or the image has become corrupted. Try to update the flash image.

• PXE-EC9: PXENV + structure was not found in UNDI driver code segment.

The Boot Agent cannot locate the needed PXENV+ structure. An incorrect flash image is installed or
the image has become corrupted. Try to update the flash image.

• PXE-M0F: Exiting Intel Boot Agent.

Ending execution of the ROM image.

• This option has been locked and cannot be changed.

You have attempted to change a configuration setting that has been locked by your system
administrator with IBAUtil. This message can appear from the configuration setup menu when
operating in a stand-alone environment. If you think you should be able to change the configuration
setting, consult your system administrator.

• PXE-M0E: Retrying network boot; press ESC to cancel.

The Boot Agent did not successfully complete a network boot due to a network error (such as not
receiving a DHCP offer). The Boot Agent continues to attempt to boot from the network until
successful or until canceled by the user. This feature is disabled by default. For information on how to
enable this feature, contact HP Customer Support.

Troubleshooting procedures
The following list of problems and associated solutions covers a representative set of problems that you

might encounter while using the Boot Agent. If you are experiencing a problem that is not listed in this
section, contact HP Customer Support.

After booting, my computer experiences problems
After the Boot Agent product has finished its sole task (remote booting), it no longer has any effect on the

client computer operation. Thus, any issues that arise after the boot process is complete are most likely not
related to the Boot Agent product.

If you are having problems with the local (client) or network operating system, contact the operating
system manufacturer for assistance. If you are having problems with some application program, contact
the application manufacturer for assistance. If you are having problems with any of your computer's
hardware or with the BIOS, contact HP Customer Support for assistance.

Cannot change boot order

Adapter configurations 77

If you are accustomed to redefining your computer's boot order using the motherboard BIOS setup
program, the default settings of the Boot Agent setup program can override that setup. To change the
boot sequence, you must first override the Boot Agent setup program defaults. To start the Boot Agent
configuration setup program, press the Ctrl+S keys during the time the initialization message appears. A
configuration setup menu appears allowing you to set configuration values for the Boot Agent. If you do
not press the Ctrl+S keys, the Boot Agent software proceeds with the boot process, eventually bringing up
the operating system. To change your computer's boot order setting, refer to the "Configuring the Boot
Agent in a pre-boot PXE or RPL environment" section.

My computer does not complete POST
If your computer fails to boot with an adapter installed, but does boot when you remove the adapter, try

moving the adapter to another computer and using IBAUtil to disable the flash chip.
If this does not work, the problem may be occurring before the Boot Agent software even begins

operating. In this case, there may be a BIOS problem with your computer. Contact HP Customer Support
for help in correcting your problem.

Not getting a prompt to go to Boot Agent setup program
This is actually a feature of the Boot Agent product. As part of the Boot Agent's Configuration Setup

Program, two of the options, Show Setup Prompt and Setup Wait Time, allow the boot process to proceed
after POST without interruption by the Ctrl+S prompt (Press the Ctrl+S keys to enter the Setup Menu)

If the Show Setup Prompt has previously been set to Disabled and/or if the Setup Menu Wait Time option
is set to zero seconds, the prompt does not display after POST. However, even though you are not
prompted to press the Ctrl+S keys, you can still enter the configuration setup menu to customize
configuration settings as follows:

Repeatedly press the Ctrl+S keys immediately after POST until the Configuration Setup Menu appears. If
the Configuration Setup Menu does not appear after repeatedly pressing the Ctrl+S keys, you were likely
not fast enough. In this case, reboot and try again.

While in the Configuration Setup Menu, you can restore the prompt message as follows:

• If Show Setup Prompt has been set to Disabled, change it to Enabled.

• If Setup Menu Wait Time is set to zero seconds, change it to any of the wait time values that exceed

zero seconds. Refer to the list of possible Set Menu Wait Time values shown in the "Boot Agent
configuration settings" section.

There are configuration/operation problems with the boot process
If your PXE client receives a DHCP address, but then fails to boot, you know the PXE client is working

correctly. Check your network or PXE server configuration to troubleshoot the problem. Contact HP
Customer Support if you need further assistance.

Diagnostics information for pre-boot PXE or RPL environments
Anytime the Configuration Setup Menu is displayed (refer to the "Configuring the Boot Agent in a pre-

boot PXE or RPL environment" section), you may press the D key to display diagnostics information on the
screen. This information can be helpful during interaction with HP Customer Support personnel or your IT
team members. After you press the D key, the information remains displayed until you reboot your
computer.

Actual diagnostics information may vary, depending upon the adapter(s) installed in your computer.
Diagnostics information may include the following items:

• PWA Number—The Printed Wire Assembly number of the device as stored in the EEPROM

Adapter configurations 78

• MAC Address—The individual address of the device as stored in the EEPROM

• I/O—The I/O address for PCI access determined by the software. On cards without an I/O

address, all zeros are displayed

• Memory—The memory map PCI access address determined by the software

• Slot—The slot number reported by the BIOS. The number displayed is the BIOS version of the PCI

slot number. Therefore, actual positions of adapters within slots may not be displayed as expected.
Slots are not always enumerated in an obvious manner, and the diagnostics will only report what is
indicated by the BIOS.

Boot agent glossary
This glossary defines terms, abbreviations, and acronyms that apply directly to the Intel® Boot Agent.

Term / Abbreviation
/ Acronym

ACPI Advanced Configuration and Power Interface
AOL Alert on LAN
API Application Program Interface. The specific method prescribed by an OS or an

BAID BIOS Aware IPL Device. The BIOS contains all code required to IPL from the device.
BAR Base Address Register
BBS BIOS Boot Specification
BC BaseCode. The PXE BaseCode, included as a core protocol in EFI, is comprised of a

BCV Boot Connection Vector. A field in the Plug and Play (PnP) header for a device with

BEV Boot Entry Vector. A field in the Plug and Play (PnP) Header of a device with an

BINL Binary Image Negotiation Layer
BIOS Basic Input/Output System. The program a personal computer's microprocessor uses

BIS Boot Integrity Services
BOOTP Bootstrap Protocol. A legacy remote booting protocol developed originally for use

DDIM Device Driver Initialization Model
DHCP Dynamic Host Configuration Protocol. An industry standard internet protocol defined

EEPROM Electrically Erasable Programmable Read-Only Memory
ESD Electro-Static Discharge
Flash A high-density, truly non-volatile, high-performance, read-write memory solution, also

Definition

application program by which a programmer writing an application program can
make requests of the operating system or the application.

simple network stack (UDP/IP) and a few common network protocols (DHCP,
Bootserver Discovery, TFTP) that are useful for remote booting machines.

an associated option ROM.

associated option ROM. PXE is implemented as a BEV option ROM.

to get the computer system started after you turn it on. It also manages data flow
between the computer's OS and attached devices.

with UNIX. Used as Linux's server side PXE host software. Runs a Daemon once
installed.

by the IETF. DHCP was defined to dynamically provide communications-related
configuration values such as network addresses to network client computers at boot
time. DHCP is specified by IETF RFCs 1534, 2131, and 2132.

characterized by low power consumption, extreme ruggedness, and high reliability.

Adapter configurations 79

Term / Abbreviation

Definition

/ Acronym

Flb Flash Library
IA32 Shorthand for computer platforms based on Intel 32-bit architecture CPUs.
IA64 Shorthand for computer platforms based on Intel 64-bit architecture CPUs.
IAL Intel Architecture Lab
IBA Intel Boot Agent
IETF Internet Engineering Task Force. The IETF is a large open international community of

network designers, operators, vendors, and researchers concerned with the evolution
of the Internet architecture and the smooth operation of the internet. It is open to any
interested individual. For more details, refer to the Internet Engineering Task Force

website.
IPL Initial Program Load. Also known as the bootstrap or boot process.
LCM LANDesk Configuration Manager
LOM LAN On Motherboard. This is a network device that is built onto the motherboard (or

baseboard) of the machine.
MTFTP Adds multicast support to a TFTP server.
NBP Network Bootstrap Program. The first program that is downloaded into a machine

that has selected a PXE capable device for remote boot services. A typical NBP

examines the machine it is running on to try to determine if the machine is capable

of running the next layer (OS or application). If the machine is not capable of

running the next layer, control is returned to the EFI boot manager and the next boot

device is selected. If the machine is capable, the next layer is downloaded and

control can then be passed to the downloaded program. Though most NBPs are OS

loaders, NBPs can be written to be stand-alone applications such as diagnostics,

backup/restore, remote management agents, browsers, and so on.
NIC Network Interface Controller. Also referred to as adapter. Technically, a network

device that is inserted into a bus on the motherboard or into an expansion board.

For the purposes of this document, the term adapter is used in a generic sense,

meaning any device that enables a network connection (including LOMs and

network devices on external buses, such as USB 1394, and so on).
OS Operating System
PMM POST Memory Manager. A mechanism used by option ROMs to allocate RAM

memory for use during system startup.
PnP Plug and Play
POST Power On Self-Test
proxyDHCP proxyDHCP is used to ease the transition of PXE clients and servers into an existing

network infrastructure. proxyDHCP provides additional DHCP information that is

needed by PXE clients and boot servers without making changes to existing DHCP

servers.
PXE Preboot Execution Environment. PXE provides a way for a system to initiate a

network connection to various servers prior to loading an OS. This network

connection supports a number of standard IP protocols such as DHCP and TFTP, and

can be used for purposes such as software installation and system inventory

maintenance.
PXE 16 PXE Specification v2.1 or earlier. Also known as 16-bit PXE.
RFC Request For Comments. Used to denote that a new standard or modification to

standard is be introduced by IETF or other standards bodies.

Adapter configurations 80

Term / Abbreviation

Definition
/ Acronym

RIS Remote Installation Services. A Microsoft® service that uses PXE to deliver the

Network Bootstrap Program (NBP) to start the boot process. Ships with Windows®

2000 Advanced Server.
ROM Read-Only Memory. When used in this guide, ROM refers to a non-volatile memory

storage device on an adapter
RPL Remote Program Load. A bootable network device protocol, developed and used

mostly by IBM.
TCO Total Cost of Ownership. Business models often calculate the approximate total cost

of ownership for technology initiative \s through formulas that incorporate both

expenditure on hardware and software and maintenance, replacement, training,

and all aspects of business that are impacted by the core system. Remote

management tools like PXE help lower the overall cost of the ownership.
TFTP Trivial File Transfer Protocol. An industry standard internet protocol defined by the

IETF to enable the transmission of files across the internet. Trivial File Transfer

Protocol (TFTP, Revision 2) to support NBP download is specified by IETF RFC 1350.
UNDI Universal Network Driver Interface. UNDI is an architectural interface to adapters.

Traditionally adapters have had custom interfaces and custom drivers (each adapter

had a driver for each OS on each platform architecture). UNDI provides a

hardware-dependent mechanism for the PXE base code to use a adapter for network

access without controlling the adapter hardware directly. H/W UNDI is an

architectural hardware interface to an adapter; S/W UNDI is a software

implementation of the H/W UNDI.
URL Uniform Resource Locator. The address of a file (resource) accessible on the internet.
USB Universal Serial Bus. A Plug and Play (PnP) interface between a computer and add-

on devices.
WfM Wired for Management
WOL Wake on LAN

Keywords for N100 NDIS2 driver

The following how to configure the parameters for the NDIS 2 driver version 4.56 (N100 DOS).

General configuration parameters

The following configuration parameters are supported through the PROTOCOL.INI file. The "Possible
Errors" section describes the driver's behavior when error conditions are detected. If an error is fatal, the
driver will not load. In all other cases the driver will load and use the default value.

• DRIVERNAME

o Syntax: DRIVERNAME=[N100$ | N1002$ | etc]
o Example: DRIVERNAME=N100$
o Default: None. This is a required parameter.
o Normal Behavior: The driver finds its section in PROTOCOL.INI by matching its instance ID to the

value for this parameter.

o Possible Errors: The device driver uses a DOS and OS/2 function to display the name of the

driver it is expecting. This function cannot display a "$" character. For this reason, the user may

Adapter configurations 81

see a message referring to this value with the "$." The user must remember to enter the "$"
character as part of the parameter's value.

• SPEED

o Syntax: SPEED=[Auto | 10 | 100]
o Example: SPEED=10
o Default: Auto-Speed-Detect as a function of PHY detection
o Normal Behavior: If either 10 or 100 is specified, a message indicates that Auto-Speed-Detect

has been disabled and the driver sets the speed using the value specified. If the parameter is not
provided at all, or if Auto is provided, Auto-Speed-Sensing is enabled.

o Possible Errors:

If the SPEED parameter is set to an invalid value, the parameter is ignored and the default value
is used, and a message indicates a "Parameter value out of range" error.

If the FORCEDUPLEX parameter is assigned a valid non-zero value, this parameter is required.
If the duplex is forced, Auto-Speed-Sensing is disabled and the speed and full-duplex modes are

set as specified by the user. An N-Way PHY will not be able to detect speed changes in this
configuration until the driver is reloaded.

• FORCEDUPLEX

o Syntax: FORCEDUPLEX=[Auto | 1 | 2]
o Example: FORCEDUPLEX=1
o Default: Duplex mode configuration detected during PHY initialization.
o Normal Behavior: The parameter value of 1 will force the duplex mode to half-duplex. A

parameter value of 2 will force the duplex mode to full-duplex.
The SPEED parameter must be specified and must be valid if either half or full-duplex is forced.

Auto-detection by the PHY is disabled and the speed and full-duplex modes are set as specified.
The N-Way PHY will not be able to auto-detect the mode until the driver is reloaded.

o Possible Errors:

If the FORCEDUPLEX parameter is set to an invalid value, the parameter is ignored and the
default value is used, and a message indicates a "Parameter value out of range" error.

If the FORCEDUPLEX mode does not match the actual mode of the port in use, the driver will
function for certain levels of traffic and then begin to lose frames.

If the port in use is FULL duplex but it is not capable of performing an N-way auto-negotiation,
the user MUST use FORCEDUPLEX set to FULL.

• PHYADDRESS

o Syntax: PHYADDRESS=[0..32]
o Example: PHYADDRESS=1
o Default: 1, implying logical PHY 1 at address 1.
o An address of 0 implies logical PHY 0.

PHY 0 can only be at address 0.
PHY 1 can have addresses in the range 1 - 31.
PHY address 32 can be used to indicate the presence of an 82503 interface.

Adapter configurations 82

Normal Behavior: The value will be used by the PHY detection routine to locate and initialize the

o

PHY. If a PHY is not found at the address specified, the driver will load but not function properly,
because PHY detection occurs after the initial load has occurred.

o Possible Errors: If the PHYADDRESS parameter is set to an invalid value, the parameter is ignored

and the default value is used, and a message indicates a "Parameter value out of range" error.

• SLOT

o Syntax: SLOT=[0x0..0x1FFF]

Optional unless you want to specify a particular adapter or module that is not loaded by default.
(By default, the driver loads on the first adapter it finds.)

o Example: SLOT=0x1C
o Default: The driver will Auto-Configure
o Normal Behavior: The driver uses the value of the parameter to decide which adapter to control.
o Possible Errors:

If only one adapter is installed and the value does not correctly indicate the adapter slot, a
message indicates that the value does not match the actual configuration, and the driver finds the
adapter and uses it.

If more than one adapter is installed and the value does not indicate the adapter slot, a message
displays indicating possible slots to use and the driver loads on the next available slot.

• NODE

o Syntax: NODE="12 hexadecimal digits"

The value must be exactly 12 hexadecimal digits, enclosed in double quotes
The value cannot be all zeros. The value cannot have the Multicast bit set (LSB of 2nd digit = 1).

o Example: NODE="00AA00123456"
o Default: Value from EEPROM installed on adapter
o Normal Behavior: The Current Station Address in the NDIS MAC Service-Specific Characteristics

(MSSC) table is assigned the value of this parameter. The adapter hardware is programmed to
receive frames with the destination address equal to the Current Station Address in the MSSC
table. The Permanent Station Address in the MSSC table will be set to reflect the node address
read from the adapter's EEPROM.

o Possible Errors: If any of the rules described above is violated, an error message indicates the

rules for forming a proper address, and the driver treats this as a fatal error.

• CONGENB

o Syntax: CONGENB=[0 | 1]
o Example: CONGENB=1
o Default: Congestion Control is disabled.
o Normal Behavior: The absence of this parameter or the value 0 results in no Congestion Control.

The value of 1 enables the Congestion Control feature.

o Possible Errors: If the CONGENB parameter is set to an invalid value, the parameter is ignored

and the default value is used, and a message indicates a "Parameter value out of range" error.

• RXFIFO

o Syntax: RXFIFO=[0..15 | 0x0..0xF]
o Example: RXFIFO=8

Adapter configurations 83

Default: 8, corresponding to 32 bytes or 8 dwords in the receive FIFO.

o
o Normal Behavior: No message will be displayed. The driver will use the specified value to

configure.

o Possible Errors: If the RXFIFO parameter is set to an invalid value, the parameter is ignored and

the default value is used, and a message indicates a "Parameter value out of range" error.

• TXFIFO

o Syntax: TXFIFO=[0..15 | 0x0..0xF]
o Example: TXFIFO=8
o Default: 8, corresponding to 32 bytes or 8 dwords in the transmit FIFO.
o Normal Behavior: No message will be displayed. The driver will use the specified value to

configure.

o Possible Errors: If the TXFIFO parameter is set to an invalid value, the parameter is ignored and

the default value is used, and a message indicates a "Parameter value out of range" error.

• TXTHRESHOLD

o Syntax: TXTHRESHOLD=[0..254 | 0x0..0xFE]
o Example: TXTHRESHOLD=32
o Default: 32, corresponding to 32 * 8=256 bytes
o Normal Behavior: The value will be set in every transmit command. The initial value can only be

changed at load time, although the driver will increase the value if underruns are detected.
Setting a low value (less than 16) in high bus latency systems could cause excessive TX DMA
underruns, reducing throughput until the driver reacts. Setting a value of more than 200
completely eliminates the possibility of TX DMA underruns.

o Possible Errors:

If the TXTHRESHOLD parameter is set to an invalid value, the parameter is ignored and the
default value is used, and a message indicates a "Parameter value out of range" error.

• IFS

o Syntax: IFS=[0..255 | 0x0..0xFF]
o Example: IFS=16
o Default: 0 (minimum spacing between frames)
o Normal Behavior: The value will be used to configure the 82557 at initialization time. A value of

0 implies minimum IFS between 2 transmit frames. Increasing the value reduces the probability of
collisions under heavy load due to multiple clients, but will have a negative impact on transmit
throughput in a point-to-point single-client packet burst.

o Possible Errors: If the IFS parameter is set to an invalid value, the parameter is ignored and the

default value is used, and a message indicates a "Parameter value out of range" error.

• RXDMACOUNT

o Syntax: RXDMACOUNT=[0..127 | 0x0..0x7F]
o Example: RXDMACOUNT=16
o Default: 0 implying that the Rx DMA will continue until it is done. No other DMA request can

preempt it.

Adapter configurations 84

Normal Behavior: The value will be used to configure the 82557 at initialization time. Setting it

o

to a low value will force frequent internal arbitration, which will affect overall performance. The
value can be tuned to obtain optimum balance between the TX and Rx DMA machines.

o Possible Errors:

If the RXDMACOUNT parameter is set to an invalid value, the parameter is ignored and the
default value is used, and a message indicates a "Parameter value out of range" error.

• TXDMACOUNT

o Syntax: TXDMACOUNT=[0..127 | 0x0..0x7F]
o Example: TXDMACOUNT=16
o Default: 0 implying that the Tx DMA will continue until it is done. No other DMA request can

preempt it.

o Normal Behavior: The value will be used to configure the 82557 at initialization time. Setting it

to a low value will force frequent internal arbitration, which will affect overall performance. The
value can be tuned to obtain optimum balance between the Tx and Rx DMA machines.

o Possible Errors:

If the TXDMACOUNT parameter is set to an invalid value, the parameter is ignored and the
default value is used, and a message is indicates a "Parameter value out of range" error.

• TRANSMITBUFFERS

o Syntax: TRANSMITBUFFERS=[4 .. 30]
o Example: TRANSMITBUFFERS=14
o Default: 4 for DOS driver, 10 for OS/2 driver
o Normal Behavior: The driver allocates the number of buffers indicated by the parameter value.
o Possible Errors:

If the value provided is out of range, the parameter is ignored and the default value is used, and
a message indicates a "Parameter value out of range" error.

CAUTION: If the number of buffers allocated causes the driver’s size to exceed MAXIMUM,

the driver adjusts the number of buffers downward, by reducing each of the counts of
transmit/receive buffers by one until the total allocation will fit in the available memory. A
message indicates the actual number of buffers allocated. Under DOS without Window for
Workgroups (WFW), MAXIMUM is defined as 64Kb for all code and data.

Under DOS and WFW, the driver must not claim more space than its load size, but since the
driver cannot detect that it is running under WFW, a message warns the user when the size
allocated exceeds the size of the driver when loaded. Under OS/2, MAXIMUM is defined as
64Kb for all data.

• RECEIVEBUFFERS

o Syntax: RECEIVEBUFFERS=[4 .. 30]
o Example: RECEIVEBUFFERS=14
o Default: 8 for DOS driver, 10 for OS/2 driver
o Normal Behavior: The driver allocates the number of buffers indicated by the parameter value.
o Possible Errors:

If the value provided is out of range, the parameter is ignored, the default value is used, and a

message indicates a "Parameter value out of range" error.

Adapter configurations 85

CAUTION: If the number of buffers allocated causes the driver’s size to exceed MAXIMUM,

the driver adjusts the number of buffers downward, by reducing each of the counts of
transmit/receive buffers by one until the total allocation will fit in the available memory. A
message indicates the actual number of buffers allocated. Under DOS without Window for
Workgroups (WFW), MAXIMUM is defined as 64Kb for all code and data.

Under DOS and WFW, the driver must not claim more space than its load size, but since the
driver cannot detect that it is running under WFW, a message warns the user when the size
allocated exceeds the size of the driver when loaded. Under OS/2, MAXIMUM is defined as
64Kb for all data.

• MCWA

o Syntax: MCWA=[0..255 | 0x0..0xFF]
o Example: MCWA=8
o Default: 6
o Normal Behavior: This function is based on the system timer. When the counter reaches 2

seconds (in both OS/2 and DOS), the driver checks to see if the driver has received no frames
since the last time the counter ran, and the Receive Hang workaround will be executed. When
the workaround condition exists, the service routine that runs the workaround will attempt to run
the workaround every timer tick (18.3/sec in DOS, ~32/sec in OS/2). The EEPROM contains
information that will control the running of the workaround. If in the event that the EEPROM is
configured so that the workaround is not needed, the counter will not be added to the timer
chain, saving system resources.

o Possible Errors: The value is not checked in any way, only 8 bits of value are used. The counter's

effectiveness could be compromised if another executable disrupts the timer chain.

• FRAMEGAP

o Syntax: FRAMEGAP=[6..64 | 0x06..0x40]
o Example: FRAMEGAP=12
o Default: 6
o Normal Behavior: In normal circumstances, this will not be needed. If packets are being dropped

while running a T4 card, the FRAMEGAP must be increased. A value of 12 or 15 will fix the
problem in most cases. Do not use this parameter unless you are experiencing dropped packets.

o Possible Errors: If an invalid range or syntax for this parameter occurs, the default value is used.

The driver does not give any outward indication as to the state of this parameter.

• CACHEFLUSH

o Syntax: CACHEFLUSH=[0|1]
o Example: CACHEFLUSH=1
o Default: 0
o Normal Behavior: Use this parameter during a remote installation or "push-install" of Windows

NT®.

o Possible Errors: Any non-zero value sets this parameter to 1. The driver does not give any

outward indication as to the state of this parameter.

Adapter configurations 86

Keywords for N1000 NDIS2 driver

The following describes how to configure the parameters for the NDIS 2 driver version 3.62
(N1000.DOS).

Configuration
The following configuration parameters are supported through the PROTOCOL.INI file. The "Possible

Errors" section describes the driver's behavior when error conditions are detected. If an error is fatal, the
driver will not load. In all other cases the driver will load and use the default value.

• DRIVERNAME

o Syntax: DRIVERNAME=[N1000$ | N10002$ | etc]
o Example: DRIVERNAME=N1000$
o Default: None. This is a required parameter.
o Normal Behavior: The driver finds its section in PROTOCOL.INI by matching its instance ID to the

value for this parameter.

o Possible Errors: The device driver uses a DOS function to display the name of the driver it is

expecting. This function cannot display a "$" character. For this reason, the user may see a
message referring to this value without the "$." The user must remember to enter the "$"
character as part of the parameter's value.

• SPEEDDUPLEX

o Syntax: SPEEDDUPLEX = [0 | 1 | 2 | 3]
o Example: SPEEDDUPLEX = 1
o Default: Speed and Duplex mode configuration detected during PHY initialization.
o Normal Behavior: The parameter value of:

0 will force the speed to 10 Mbps and the duplex mode to half duplex.
1 will force the speed to 10 Mbps and the duplex mode to full duplex.
2 will force the speed to 100 Mbps and the duplex mode to half duplex.
3 will force the speed to 100 Mbps and the duplex mode to full duplex.

o Auto-detection by the PHY is disabled and the speed and full duplex modes are set as specified.

The PHY will not be able to auto-detect the mode until the driver is reloaded.

o Possible Errors:

If the SPEEDDUPLEX parameter is set to an invalid value, the parameter is ignored and the
default value is used, and a message indicates a "Parameter value out of range" error.

If the SPEEDDUPLEX mode does not match the actual mode of the port in use, the driver may or
may not function for certain levels of traffic and then begin to lose frames.

The SPEEDDUPLEX parameter is valid for HP NC71xx Server Adapters or Modules only and is
ignored if used with HP NC61xx Server Adapters or Modules. The HP NC71xx Server Adapters
and Modules cannot be forced to 1000 Mbps.

• SLOT

o Syntax: SLOT=[0x0..0x1FFF]

Optional unless you want to specify a particular adapter or module that is not loaded by default.

o Example: SLOT=0x1C
o Default: The driver will Auto-Configure if possible.

Adapter configurations 87

Normal Behavior: The driver uses the value of the parameter to decide which adapter to control.

o
o Possible Errors:

If only one adapter is installed and the value does not correctly indicate adapter slot, a message
indicates that the value does not match the actual configuration, and the driver finds the adapter
and uses it.

If more than one adapter is installed and the value does not indicate the adapter slot, a message
indicates that the specified slot is invalid for the driver instance. The parameter is ignored and
the default value is used.

• NODE

o Syntax: NODE = "12 hexadecimal digits"

The value must be exactly 12 hexadecimal digits, enclosed in double quotes.
The value cannot be all zeros.
The value cannot have the Multicast bit set (LSB of 2nd digit == 1).

o Example: NODE = "02AA00123456"
o Default: Value from EEPROM installed on adapter
o Normal Behavior: This value sets the adapter's Individual Address, overriding the value read

from the adapter EEPROM. The address must consist of 12 hexadecimal digits, enclosed in
double quotes. The value cannot be all zeros and cannot have the Multicast bit set. Use only the
hexadecimal digits 2, 6, A, or E as the second digit of the twelve required in the NODE
ADDRESS parameter. Use any hexadecimal digits in all other positions.

o Possible Errors: If any of the rules described above is violated, an error message indicates the

rules for forming a proper address, and the driver treats this as a fatal error.

• CACHEFLUSH

o Syntax: CACHEFLUSH= [0|1]
o Example: CACHEFLUSH=1
o Default: 0
o Normal Behavior: Use this parameter during a remote installation or "push-install" of Windows

NT®.

o Possible Errors: Any non-zero value sets this parameter to 1. The driver does not give any

outwards indication as to the state of this parameter.

Example PROTOCOL.INI file
PROTOCOL.INI section for the HP Gigabit Server Adapters and Modules:

• DRIVERNAME parameter

o Use this parameter to set 1st adapter = N1000$, 2nd adapter = N10002$, and so on
o DRIVERNAME = N1000$

• NODE parameter

o Use this to change the MAC address used by the adapter
o NODE="02AA00123456"

• SLOT parameter

o Use this to configure a particular instance of the driver designated by DRIVERNAME, to use the

adapter in a particular PCI slot. Slots should be specified in hex notation.

Adapter configurations 88

SLOT=0x7

o

• CACHEFLUSH parameter

o Set this to 1 to hook the system Disk Buffer Flush interrupt. This causes the driver to properly turn

off the adapter when the system is shut down by Windows NT® during remote installation (push­install).

o CACHEFLUSH=1
o Known Limitations: This driver does not support any application that uses protected mode, for

example, EMM386. In addition, testing has demonstrated that the GHOST software application
fails when used with this driver under Netx (VLMs are OK).

PXE configuration for HP NC-Series Intel adapters

The Pre-boot Execution Environment (PXE) of HP adapters has been upgraded to allow PXE functions to
work with the HP ProLiant servers.

The Boot Agent software provides the ability to customize its behavior through its configuration options.
Changing the Boot Agent configuration is required only the first time you add a new network adapter to a
client computer within your network. You can configure the Boot Agent within any of the following
environments:

• A pre-boot environment (before an operating system is loaded)

• A Windows® environment

• A DOS environment

Configuring the Boot Agent in a pre-boot environment
You can customize the behavior of the Boot Agent software through a pre-boot (operating system-

independent) configuration program contained within the adapter's flash ROM. You can access this pre­boot configuration setup program each time the client computer cycles through the boot process.

When you power up or perform a hard or soft system reset, the following message is displayed during the
initialization process of the Boot Agent firmware. It indicates that the boot agent is active.

Initializing Intel(R) Boot Agent Version 3.0.05
PXE 2.0 Build 078 (WFM 2.0), RPL V2.73

The following message is then displayed during the boot process to Boot Agent Services:

Intel(R) Boot Agent 3.0.05
Copyright(c) 1997-2000, Intel Corporation
Client MAC Address: 00 50 8B xx xx xx
GUID:00000000-0000-0000-000000000000
Client IP: 123.xxx.xxx.xxx MASK: 123.xxx.xxx.xxx
DHCP IP: 123.xxx.xxx.xxx
Gateway IP: 123.xxx.xxx.xxx

Changing the Boot Agent configuration settings
To access the Boot Agent Setup Menu, immediately after the initialization messages, and before any

subsequent message is displayed, quickly press Ctrl+S. This menu provides the ability to customize the
"Boot Agent Configuration Settings."

The Boot Agent setup menu displays a list of configuration settings on the left, and their corresponding
values on the right. Key functions are described near the bottom of the menu. The menu indicates how to
change the values of settings.

To access a brief Help description of a setting, select it.

Adapter configurations 89

To customize the Boot Agent configuration settings:

1. Highlight the setting you want to change using the arrow keys. Then press Enter.

2. Press the spacebar until the desired value appears.

3. If you want to change additional settings, repeat steps 1 and 2.

4. After you have completed your changes, press F4 to update the adapter with the new values.

Boot Agent configuration settings

The following table describes the Boot Agent configuration settings.

Configuration

Possible values Description

settings

Network Boot
Protocol

Boot Order

Show Setup
Prompt

• PXE (Preboot

eXecution
Environment)

• RPL (Remote

Program Load)

• Use BIOS Setup

Boot Order

• Try network first,

then local drives

• Try local drives

first, then
network

• Try network only

• Try local drives

only

• Enabled

• Disabled

Controls whether the RPL or PXE boot protocol will be used. Select
PXE for use with WfM-compatible network management programs,
such as Intel® LANDesk® Management Suite, Windows 2000 RIS,
and Linux®.

Select RPL for legacy-style remote booting, as well as for Novell®
Netware® remote boot solutions.

Depending on the configuration of the Boot Agent, this parameter
may not be changeable.

Sets the boot order in which devices are selected during boot up if
the computer does not have its own control method.

If your client computer's BIOS supports the BIOS Boot Specification
(BBS), or allows PnP-compliant selection of the boot order in the
BIOS setup program, then this setting will always be Use BIOS Setup
Boot Order and cannot be changed. In this case, refer to the BIOS
setup manual specific to your client computer to set up boot options.

If your client computer does not have a BBS- or PnP-compliant BIOS,
you can select any one of the other possible values listed for this
setting except for Use BIOS Setup Boot Order.

Controls whether or not the Boot Agent displays the Ctrl+S prompt
after POST.

If you select Enabled, the Ctrl+S prompt appears after POST so that
you can press Ctrl+S within the number of seconds allowed by the
Setup Menu Wait Time setting to display the configuration setup
menu.

If you select Disabled and/or the Setup Menu Wait Time setting is
zero, the Ctrl+S setup prompt will not appear during the boot
process. However, you can display the configuration setup menu by
repeatedly pressing the Ctrl+S keys immediately after POST until the
menu appears. If the configuration setup menu does not appear
after repeatedly pressing the Ctrl+S keys, you were likely not fast
enough. In this case, reboot and try again.

Adapter configurations 90

Configuration

Possible values Description

settings

Setup Menu Wait
Time

• 0 seconds

• 2 seconds

• 3 seconds

• 5 seconds

Controls the number of seconds the Boot Agent waits for you to
press the Ctrl+S keys, so as to suspend the boot process and then
configure the way the Boot Agent operates.

If you select a Setup Menu Wait Time setting of zero and/or a Show
Setup Prompt setting of Disabled, the Ctrl+S setup prompt will not
appear during the boot process. However, you can still display the
configuration setup menu by repeatedly pressing the Ctrl+S keys
immediately after POST until the menu appears. If the configuration
setup menu does not appear after repeatedly pressing the Ctrl+S
keys, you were likely not fast enough. In this case, reboot and try
again.

Windows

Modifying adapter properties using the NCU

This following describes the adapter properties available in the HP Network Configuration Utility (NCU).

IMPORTANT: NC31xx, NC6132, NC6133, and NC7132 adapters are not supported in

Windows Server 2003 x64.

HP 10/100 server adapters

• Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is

compatible with the link partner (examples: switch, hub).

o Default = Auto/Auto
o Range = Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full

NOTE: The NC3133 is a 100BASE-FX fiber optic upgrade module that supports 100 Mbps

only.

• Locally Administered Address. Specifies the user-defined MAC Address of the adapter, which

overrides the burned-in MAC Address. This box is disabled if the selected adapter has been teamed.

o Default = NULL
o Range = Valid unicast MAC Address

• 802.1p QoS Packet Tagging. Enables or disables IEEE 802.1p tagging to send network traffic with

different priority levels.

o Default = Disabled
o Range = Disabled; Enabled

• Adaptive Performance Tuning: NIC Bandwidth/CPU Utilization (NC31xx adapters only). Specifies the

number of frames the adapter receives before triggering an interrupt. Under normal operation, the
adapter generates an interrupt each time a frame is received. Reducing the number of interrupts
improves CPU use. Setting a low value for this parameter causes a high rate of receive interrupts
(that is, a setting of the lowest value will result in an interrupt for every frame received). A low value
increases adapter bandwidth, but may reduce CPU efficiency, slowing your computer. Setting a high
value for this parameter reduces the interrupt rate (that is, increases the number of frames the

Adapter configurations 91

adapter receives before generating an interrupt). A high value improves CPU efficiency, but may
reduce adapter bandwidth.

o Default = 1536
o Range = 0–4096 (increments of 32)

• Number of Coalesce Buffers (NC31xx adapters only). Specifies the number of memory buffers

available to the driver in case the driver runs out of available map registers. This buffer area is also
used when a packet consists of many fragments. If no coalesce buffers or map registers are
available, the driver is forced to queue the packet for later transmission. The preferred method of
transmitting data is to use map registers, because it is the most efficient method.

o Default = 8
o Range = 1–32

• Number of Receive Descriptors: Minimum/Maximum. Specifies the number of descriptors used by the

driver when copying data to the protocol memory. In high network load situations, increasing
receive descriptors can increase performance. The tradeoff is that this also increases the amount of
system memory used by the driver. If too few receive descriptors are used, performance suffers. If too
many receive descriptors are used, the driver unnecessarily consumes memory resources.

o Default = 48
o Range = 8–1024 (in increments of 8)

• Transmit Control Blocks. Specifies how many Transmit Control Blocks (TCBs) the driver allocates for

adapter use. This directly corresponds to the number of outstanding packets the driver can have in its
send queue. If too few TCBs are used, performance suffers. If too many TCBs are used, the driver
unnecessarily consumes memory resources.

o Default = 32
o Range = 1–64

• Adaptive Transmit Threshold. Determines how many bytes are in the FIFO before transmission

begins.

o Default = 200
o Range = 0–200

• Flow Control. The Flow Control property allows the user to enable or disable the receipt or

transmission of PAUSE frames. PAUSE frames enable the adapter and the switch to control the
transmit rate. The side that is receiving the PAUSE frame will momentarily stop transmitting. The
recommended selection is Off and it is the default setting. To disable Flow Control, select Off from
the Value list on the Advanced tab.

o Off. (Default) PAUSE frame receipt and transmission is disabled
o Generate. PAUSE frame transmission is enabled
o Respond. PAUSE frame receipt is enabled
o Both on. PAUSE frame receipt and transmission is enabled

HP NC110x, NC310F, NC340x, NC360x, NC364x, NC61xx, and NC71xx server adapters

• Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is

compatible with the link partner (examples: switch, hub).

o Default

1000BASE-SX or -LX Adapters: Auto/Auto
10/100/1000 Adapters: Auto/Auto

Adapter configurations 92

Range

o

1000BASE-SX or -LX Adapters: Auto/Auto
10/100/1000 Adapters: Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full; 1000/Full

NOTE: This property is disabled for the NC310F and NC61xx adapters.

• Locally Administered Address. Specifies the user-defined MAC Address of the adapter, which

overrides the burned-in MAC Address. This box is disabled if the selected adapter has been teamed.

o Default = NULL
o Range = Valid unicast MAC Address

• 802.1p QoS Packet Tagging. Enables or disables IEEE 802.1p tagging to send network traffic with

different priority levels.

o Default = Disabled
o Range = Disabled; Enabled

• Maximum Frame Size. Specifies the maximum number of bytes in a single packet. Larger frames can

increase throughput and decrease CPU use by putting more data in each packet, thereby sending
out fewer packets. This is equivalent to Jumbo Frames and must comply with switch limitations.

o Default = 1514 Bytes
o Range

NC310F and NC61xx: 1514 Bytes; 4088 Bytes; 9014 Bytes; 16128 Bytes
NC110x, NC340x, NC360x, NC364x, and NC71xx: 1514 Bytes; 4088 Bytes; 9014 Bytes

• Number of Coalesce Buffers. Specifies the number of memory buffers available to the driver in case

the driver runs out of available map registers. This buffer area is also used when a packet consists of
many fragments. If no coalesce buffers or map registers are available, the driver is forced to queue
the packet for later transmission. The preferred method of transmitting data is to use map registers,
since it is the most efficient method.

o Default

Windows® 2000: 256 (NC110x and NC364x not supported)
Windows Server 2003 and Windows Server 2003 x64: 128

o Range = 16–768 (increments of 8)

• Number of Receive Descriptors: Minimum/Maximum. Specifies the number of descriptors used by the

driver when copying data to the protocol memory. In high network load situations, increasing
receive descriptors can increase performance. The tradeoff is that this also increases the amount of
system memory used by the driver. If too few receive descriptors are used, performance suffers. If too
many receive descriptors are used, the driver unnecessarily consumes memory resources.

o Default

Windows® 2000: 256 (NC110x and NC364x not supported)
Windows Server 2003 Windows Server 2003 x64
NC110x, NC310F, NC340x, NC360x, NC364x, NC6170, and NC7170: 256
All other adapters: 160

o Range

Windows® 2000

Adapter configurations 93

NC6132, NC6133, and NC6134: 80–768 (increments of 8)
NC6136, NC7131, and NC7132: 80–256 (increments of 8)
NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32)
Windows Server 2003 Windows Server 2003 x64
NC6132, NC6133, and NC6134: 80–768 (increments of 8)
NC6136, NC7131, and NC7132: 80–256 (increments of 8)
NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32)
NC110x, NC360x, and NC364x: 80-2048 (increments of 8)

• Number of Transmit Descriptors: Minimum/Maximum. Specifies the number of descriptors to allocate

per Transmit Control Block (TCB). This value directly affects the number of map registers allocated for
the adapter (the higher the number, the more map registers are allocated).

o Default = 256
o Range

Windows® 2000
NC6132, NC6133, and NC6134: 80–768 (increments of 8)
NC6136, NC7131, and NC7132: 80–256 (increments of 8)
NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32)
Windows Server 2003
NC6132, NC6133, and NC6134: 80–768 (increments of 8)
NC6136, NC7131, and NC7132: 80–256 (increments of 8)
NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32)
NC110x, NC360x, and NC364x: 80-2048 (increments of 8)

• Rx TCP Checksum Offload. Offloads the task of computing the checksum for incoming TCP or UDP

packets, thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Tx TCP Checksum Offload. Offloads the task of computing the checksum for outgoing TCP or UDP

packets, thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Tx IP Checksum Offload. Offloads the task of computing the checksum for outgoing IP packets,

thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Rx IP Checksum Offload. (NC110x, NC310F, NC340x, NC360x, NC364x, NC6170, and

NC7170 only). Offloads the task of computing the checksum for incoming IP packets, thereby
improving performance.

o Default = Enabled
o Range = Disabled; Enabled

Adapter configurations 94

• Enable PME. (NC110T, NC310F, NC340x, NC360x, NC364T, NC6170, and NC7170 only)

Allows the use of power management and wake-up functions.

o Default = No Action
o Range = Disable; Enable; No Action; H/W Default

• Wake On. (NC110T, NC310F, NC340T, NC360x, NC364T, NC6170, and NC7170 only)

Available only when Enable PME is enabled. Allows you to choose what types of packets will cause
the adapter to wake.

o Default = Disable (NC110, NC360x, NC364x Default=OS Controlled)
o Range = Disable; Magic Packet; Direct Packet Magic and Direct Packets; OS Controlled

• Large Send Offload. Enables offloading of large TCP packets (NC110T, NC310F, NC340x,

NC360x, NC364T, NC6170, and NC7170 only). Windows 2003 and Windows 2003 x64 only.

o Default = Enabled
o Range = Disabled; Enabled

• Gigabit Master Slave Mode. (NC110x, NC360x, NC364x only) Determines IEEE 802.3ab Master-

Slave resolution during gigabit auto negotiation.

o Default = Auto Detect
o Range = Auto Detect, Force Master Mode, Force Slave Mode

• Smart Power Down. (NC110T, NC360x, and NC364T only) Minimizes power consumption by

enabling the adapter to enter a deep sleep mode under certain conditions.

o Default = H/W Default
o Range = Disable, H/W Default, Enable

• Wake on Link. (NC110T, NC360x, and NC364T only) Allows wake-up from Advanced

Configuration and Power Interface (ACPI) when link is reconnected. Windows 2003 and Windows
2003x64

o Default = Disable
o Range = Disable, Force

• Flow Control. (Windows Server 2003 only) Determines the type of flow control that is needed.

(NC110x, NC360x, NC364x only):

o Default = Both On
o Range = Off, Respond, Generate, Both On

HP NC150T, NC32x, NC37xx, NC380T, NC1020, NC67xx, and NC77xx Server Adapters

• Number of Transmit Descriptors: Minimum/Maximum. Specifies the number of descriptors to allocate

per Transmit Control Block (TCB). This value directly affects the number of map registers allocated for
the adapter (the higher the number, the more map registers are allocated).

o Default = 200
o Range = 100–600

NOTE: This property is not supported on HP Multifunction Server Adapters.

• Number of Receive Descriptors: Minimum/Maximum. Specifies the number of descriptors used by the

driver when copying data to the protocol memory. In high network load situations, increasing
receive descriptors can increase performance. The tradeoff is that this also increases the amount of

Adapter configurations 95

system memory used by the driver. If too few receive descriptors are used, performance suffers. If too
many receive descriptors are used, the driver unnecessarily consumes memory resources.

o Default = 200
o Range = 100–512

NOTE: This property is not supported on HP Multifunction Server Adapters.

• Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is

compatible with the link partner (examples: switch, hub).

o NC150T and NC67xx

Range = Auto/Auto
Default = Auto/Auto

o NC32x, NC37xx, NC380T, NC1020, and NC77xx

Range = Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full; 1000/Full
Default = Auto/Auto

• Locally Administered Address. Specifies the user-defined MAC Address of the adapter, which

overrides the burned-in MAC Address. This box is disabled if the selected adapter has been teamed.

o Default = NULL
o Range = Valid unicast MAC Address

• 802.1p QoS Packet Tagging. Enables or disables IEEE 802.1p tagging to send network traffic with

different priority levels.

o Default = Disabled
o Range = Disabled; Enabled

• Maximum Frame Size. Specifies the maximum number of bytes in a single packet. Larger frames can

increase throughput and decrease CPU use by putting more data in each packet, thereby sending
out fewer packets. This is equivalent to Jumbo Frames and must comply with switch limitations.

When TCP/IP Offload Engine (TOE) is enabled, this property cannot be set to greater than 1514
bytes. If this property is set to greater than 1514 bytes, TOE cannot be enabled.

o Default = 1514 Bytes
o Range = 1514 Bytes; 4088 Bytes; 9014 Bytes

NOTE: This property is not supported by NC150T, NC32x, NC1020, and NC7761

adapters.

• Wake Up Capabilities. Determines the type of packets that will cause the adapter to wake up the

system.

o Default = Both
o Range = None; Magic Packet; Wake Up Frame; Both

NOTE: This property is not supported on HP Multifunction Server Adapters.

• WOL Speed. (Not supported on NC150T, NC37x, NC380T, NC67xx, and NC7782 adapters)

Specifies the speed at which the adapter connects to the network during Wake-on-LAN mode.

Adapter configurations 96

Default = Auto

o
o Range = Auto, 10Mb, 100Mb

• Flow Control. Specifies the type of flow control that is needed.

o Default = Auto
o Range = Disable; Rx Pause; Tx Pause; Rx/Tx Pause; Auto

• Rx TCP Checksum Offload. Offloads the task of computing the checksum for incoming TCP or UDP

packets, thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Tx TCP Checksum Offload. Offloads the task of computing the checksum for outgoing TCP or UDP

packets, thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Tx IP Checksum Offload. Offloads the task of computing the checksum for outgoing IP packets,

thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Rx IP Checksum Offload. Offloads the task of computing the checksum for incoming IP packets,

thereby improving performance.

o Default = Enabled
o Range = Disabled; Enabled

• Ethernet@WireSpeed (NC37xx, NC380x and NC77xx only). Enables linking at 100 Mbps when

using a cable that does not support Gigabit speed.

o Default = Enabled
o Range = Disabled; Enabled

NOTE: This property is not supported by NC7761 adapters.

• Large Send Offload. Normally, the TCP segmentation is performed by the protocol stack. By

enabling the Large Send Offload parameter, the TCP segmentation can be performed by the Gigabit
Ethernet Adapter. To enable the Large Send Offload parameter, select Enable from the Value list on
the Advanced tab.

o Default = Enabled
o Range = Disabled; Enabled

• IPMI. Enables Intelligent Platform Management Interface, which provides a means for monitoring,

control, and automatic recovery of servers. IPMI can only enabled on one port at a time. IPMI cannot
be enabled on a port that has Large Send Offload enabled. (This property is only supported on the
NC320i, NC7781 and NC7782 adapters.)

Multifunction Gigabit Server Adapters only

• iSCSI properties

Adapter configurations 97

o

SRB Timeout Delta. Increases or decreases the timeout value for I/O operations through the iSCSI
HBA. Increasing this value may help prevent premature I/O timeouts if your network is highly
congested and packets are being dropped frequently. The default setting is 15 seconds. This
property only displays if iSCSI is enabled on the adapter.

o iSCSI VLAN. Allows you to create a VLAN for an iSCSI-enabled device.

• TCP/IP Offload Engine (TOE). Offloads TCP connections to the Multifunction Server Adapter.

(Microsoft Scalable Networking Pack (SNP) for Windows 2003 SP1 or later and Windows 2003
x64 SP1 or later environments only.) See the Microsoft (http://www.microsoft.com

) website to
download the latest version of the Microsoft Windows Server 2003 Scalable Networking Pack (SNP)
and the required Microsoft hotfixes in article numbers 921136, 919948, and 923187 of the
Microsoft Knowledge Base (KB).

o Default = Enabled
o Range = Disabled; Enabled

• Receive-Side Scaling (RSS). Allows the network load from a network adapter to be balanced across

multiple CPUs. (Microsoft Scalable Networking Pack (SNP) for Windows 2003 SP1 or later and
Windows 2003 x64 SP1 or later)

o Default = Enabled
o Range = Disabled; Enabled

• Optimized Interrupt Moderation. When this configuration is set to optimize, the driver automatically

and continuously determines the best Target DPC (deferred procedure call) Rate to use based on the
current network conditions. When this configuration is set to manual, the user can select a Target
DPC Rate and the driver adjusts the adapter's interrupt setting to achieve that DPC rate. Changing
this setting may improve performance for some configurations.

• Target DPC Rate. Determines the desired DPC rate. The driver adjusts the adapter's interrupt

moderation setting dynamically based on network conditions to achieve the desired DPC rate. This
configuration is valid only when "Optimized Interrupt Moderation" is set to manual.

Modifying HP NC-Series Broadcom and Multifunction adapter
properties

Although the default values should be appropriate in most cases, you may change any of the available
options to meet the requirements of your specific system. Use the following procedure to verify or change
the properties after the adapter driver is installed.

To change the adapter properties, display the Driver Properties Advanced tab as follows:

1. On the desktop, click Start then select Control Panel > System to display the System Properties

window.

2. Select the Hardware tab and click Device Manager. The Device Manager window appears.

3. Scroll down the list of hardware devices to Network Adapters and click the plus (+). This displays the

list of adapters currently configured.

4. Right-click the adapter to configure and select Properties. The Properties window appears.

5. Select the Advanced tab. The list of properties and current values for the adapter appears.

6. Select the property to modify and adjust the Value as needed.

7. Save the settings.

a. When the adapter property configuration is complete, click OK to accept the settings.

Adapter configurations 98

b.

If prompted to restart your computer, click Yes. Rebooting the system for new adapter properties
to take effect is not required; however, rebooting is recommended to re-initialize all registers.

Windows Server 2003 and Windows Server 2003 x64 adapter properties

• 802.1p QoS Packet Tagging. The 802.1p QoS parameter is a standard that enables Quality of

Service. This property is disabled by default. To change this property, select Enable or Disable.

• Checksum Offload. Normally the Checksum Offload function is computed by the protocol stack. By

selecting one of the Checksum Offload properties, the checksum can be computed by the Gigabit
Ethernet Adapter.

To enable one of the Checksum Offload properties select the property from the Value list on the
Advanced tab.

o None. Disables checksum offloading
o Rx TCP/IP Checksum. Enables receive TCP, IP, and UDP checksum offloading
o Tx TCP/IP Checksum. Enables transmit TCP, IP, and UDP checksum offloading
o Tx/Rx TCP/IP Checksum. (Default) Enables transmit and receive TCP, IP, and UDP checksum

offloading

• Ethernet@WireSpeed. This property is only available through the HP Network Configuration Utility.

The Ethernet@WireSpeed property enables a 1000Base-T Ethernet adapter to establish a link at a
lower speed when only two pairs of wires are available in the cable plant. By default, this property
is enabled. To disable the Ethernet @ WireSpeed property, select Disable from the Value list.

o Disable. Disables Ethernet@WireSpeed
o Enable. (Default) Enables Ethernet@WireSpeed

• Flow Control. The Flow Control property allows the user to enable or disable the receipt or

transmission of PAUSE frames. PAUSE frames enable the adapter and the switch to control the
transmit rate. The side that is receiving the PAUSE frame will momentarily stop transmitting. The
recommended selection is Auto and it is the default setting. To disable Flow Control, select Disable
from the Value list on the Advanced tab.

o Auto. (Default) Auto detect flow control
o Disable. PAUSE frame receipt and transmission is disabled
o Tx PAUSE. PAUSE frame transmission is enabled
o Rx PAUSE. PAUSE frame receipt is enabled
o Rx/Tx PAUSE. PAUSE frame receipt and transmission is enabled

• Large Send Offload. Normally, the TCP segmentation is performed by the protocol stack. By

enabling the Large Send Offload property, the TCP segmentation can be performed by the Gigabit
Ethernet Adapter. To enable the Large Send Offload property, select Enable from the Value drop­down menu on the Advanced tab.

o Disable. Disables large send offloading
o Enable. Enables large send offloading

• Locally Administered Address. Specifies the user-defined MAC Address of the adapter, which

overrides the burned-in MAC Address. This box is disabled if the selected adapter has been teamed.

o Default = Not Present
o Range = Value; Not Present

Adapter configurations 99

• Speed & Duplex. The Speed & Duplex property allows the user to set the connection speed to the

network and mode. The Duplex Mode allows the adapter to transmit and receive network data
simultaneously. The adapter is set to Auto (optimum connection) by default. Set the speed and mode
as described below:

o 1 Gb Full Auto. Sets the speed to 1 Gbps and mode to Full-Duplex
o 10 Mb Full. Sets the speed to 10 Mbps and mode to Full-Duplex
o 10 Mb Half. Sets the speed to 10 Mbps and mode to Half-Duplex
o 100 Mb Full. Sets the speed to 100 Mbps and mode to Full-Duplex
o 100 Mb Half. Sets the speed to 100 Mbps and mode to Half-Duplex
o Auto. (Default) Sets the speed and mode for optimum network connection (recommended)

NOTE: Auto is the recommended selection. It allows the adapter to dynamically detect the line

speed and duplex mode of the network. Whenever the network capability changes, the
adapter will automatically detect and adjust to the new line speed and duplex mode.

The Half-Duplex selection forces the adapter to connect to the network in Half-Duplex mode.
The adapter may not function if the network is not configured to operate at the same mode.

The Full-Duplex selection forces the adapter to connect to the network in Full-Duplex mode. The
adapter may not function if the network is not configured to operate at the same mode.

• Wake Up Capabilities. This property is only available through the HP Network Configuration Utility.

The Wake Up Capabilities property allows the user to set the adapter to wake up from a low power
mode when it receives a network wake up frame. Two wake up frames are possible: Magic Packet
and Wake Up Frame. By default, the adapter is set to Both. To choose the type of frame that will
cause the adapter to wake up, select the appropriate option from the Value list on the Advanced tab.

o Both. (Default) Selects both Magic Packet and Wake up Frame as wake up frames
o Magic Packet. Selects Magic Packet as the wake up frame
o None. Selects no wake up frames
o Wake Up Frame. Selects Wake up Frame as the wake up frame

• WOL Speed. This property is only available through the HP Network Configuration Utility. The WOL

Speed property allows the user to select the speed at which the adapter connects to the network
while in Wake-on-LAN mode. By default, the adapter is set to Auto.

o 10 Mb. Sets the speed to 10 Mb
o 100 Mb. Sets the speed to 100 Mb
o Auto. (Default) Sets the speed for optimum network connection

• Number of Transmit Descriptors: Minimum/Maximum. Specifies the number of descriptors to allocate

per Transmit Control Block (TCB). This value directly affects the number of map registers allocated for
the adapter (the higher the number, the more map registers are allocated).This property is only
available through the HP Network Configuration Utility.

o Default = 200
o Range = 100–600

• Number of Receive Descriptors: Minimum/Maximum. Specifies the number of descriptors used by the

driver when copying data to the protocol memory. In high network load situations, increasing
receive descriptors can increase performance. The tradeoff is that this also increases the amount of
system memory used by the driver. If too few receive descriptors are used, performance suffers. If too

Adapter configurations 100