HP Hewlett Packard Network Card 441877 00B User Manual

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

•

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

•

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:

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Overview

Click HP ProLiant Networking Software.

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.

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

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

Can replace like item for like item

Can add a new adapter to an empty slot

Can add an option module to an existing NC3134 adapter

•

Windows NT® 4.0

Can replace like item for like item

Cannot add a new adapter to an empty slot

NetWare 6.x

Can replace like item for like item

Can remove an adapter

Can add a new adapter to an empty slot

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

No support

•

Linux

No support

Upgrading the adapter with a persistent driver

To upgrade the adapter with a persistent driver:

Manually remove (unload) the driver.

Power down the slot and remove the adapter.

Upgrade the adapter (add the option module).

Reinstall the upgraded adapter.

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:

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.

Select an adapter from the list and click Properties.

Overview 10

Set Speed/Duplex on the adapter to Auto/Auto, 10/Half, 10/Full, 100/Half, 100/Full, or

1000/Full.

Click OK until prompted to restart.

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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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.

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:

Launch the Network Configuration Utility.

Select an adapter from the list in the NCU Main window and click Properties. The Adapter

Properties window appears.

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.

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:

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

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

Mbps or 100 Mbps.

Default = The adapter automatically senses speed.

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 ).

Overview 12

Installation

In this section

Download latest drivers, firmware, and documentatio n ............................................................................... 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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Installation 13

Click HP ProLiant Networking Software.

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.

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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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.

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:

Connect the cable from the adapter to your network.

Provide power to your server.

Start Windows Server 2003 or Windows Server 2003 x64 .

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.

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

drive. The component is a self-extracting executable with a file name based on the component

number.

Click the Install button to proceed with the installation.

After the drivers have been installed, you may delete the Component Package that you copied.

Removing the driver software

To remove the driver software:

Before physically removing an adapter from your system, first remove the adapter driver software.

Start Windows Server 2003 or Windows Server 2003 x64 and log in. You must have Network

Administrator privileges to remove the driver software.

Open the Control Panel and double-click the System icon. In the System Properties dialog box,

select the Hardware tab.

Click Device Manager. The Device Manager window appears.

Click the plus (+) sign to expand the Network adapters. All network adapters appear.

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:

Connect the cable from the adapter to your network.

Provide power to your server.

Start Windows Server 2003 or Windows Server 2003 x64 .

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.

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.

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.

Click the Install button to proceed with the installation.

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

Create a Network Installation Startup disk from the Windows NT® server and modify it for your

adapter.

Create a shared directory for the Windows NT® server installation files on the Windows NT®

server.

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.

Integrate the adapter driver files into the Windows NT® installation source files.

Perform the Unattended Installation bootup with the prepared startup disk from the client system.

Performing an unattended installation on Windows NT 4.0

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.

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).

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.

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

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.

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.

Insert the startup disk and boot up your DOS client. After connecting to the network. do one of the

following:

Input USERID as a User name when prompted. Input password as a password when prompted.

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,

Q156795

Linux

The following Linux drivers are available for HP adapters:

•

tg3—Supports NC150x, NC320x, NC324x, NC325x, NC326x, NC1020, NC67xx, and

NC77xx server adapters

•

e1000—Supports NC110T, NC310F, NC340x, NC360x, NC364T, NC61xx, and NC71xx server

adapters

•

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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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

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

Copy the file VOL.000.000 to a Caldera system.

Create a diskette using: dd if =VOL.000.000 of=/dev/rfd0135ds18.

Installing the driver

To install the driver:

Use custom or scoadmin software to install the SCO OpenServer driver from the media image or

from the diskette created above.

Use netconfig to add the new network adapter.

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:

Line Speed

AutoNegotiate (default)

HalfDuplex10

FullDuplex10

HalfDuplex100

FullDuplex100

FullDuplex1000

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

Copy the file bcme-<version>.pkg to a UnixWare 7.x system.

Enter the following command: pkgadd -d <path><filename> where <path> is the directory to which

the PKG file was copied.

Creating a diskette

Copy the file bcme-<version>.pkg to a Caldera system.

Create a diskette using the following command: dd if=bcme-<version>.pkg of=/dev/fd0

Installing the driver from a diskette

Use pkgadd -d diskette1 to install the bcme package.

Use netcfg or scoadmin network to add the new network adapter.

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:

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

Flow Control

Disabled (default)

Auto Negotiation (Symmetric Pause advertised)

Receive Pause

Transmit Pause

Receive & Transmit Pause

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).

Jumbo MTU Size

1500–9000 (default is 1500)

For more detailed information, at the command prompt, enter:

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.

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

Change directory to where BRCMbcme.pkg resides.

pkgadd -d BRCMbcme.pkg

Execute prtconf to determine instance number of the adapter.

ifconfig bcme [instance_number] plumb

ifconfig bcme [instance_number] ip_address netmask ....

To make these changes permanent:

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.

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:

ifconfig bcme [instance_number] down

ifconfig bcme [instance_number] unplumb

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.

Insert a blank diskette into the diskette drive of your system, and type one of the following commands

to format it:

If you are using DOS, type: format A:

If you are using the Solaris operating environment, type: fdformat -Ud

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:

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.

Power on your system.

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.

Remove the Configuration Assistant diskette from the disk drive and insert the first Solaris DU

diskette.

Select F2_Continue. The Select Solaris System Version screen is displayed.

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.

If you have additional DU diskettes to install, remove the DU diskette from the disk drive, insert the

next DU diskette.

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.

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:

Become the superuser on your system.

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:

# /etc/init.d/volmgt stop

Insert the DU diskette into the disk drive.

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.

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]

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.

When you have finished, and the install.sh script exits, unmount the diskette:

# cd /

# umount /mnt

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

Use with an HP NC110T, NC360T, and NC364T Gigabit Server Adapter

Always install the latest Novell support pack

Always install the latest HP NSSD

SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)

SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)

SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger)

•

HP N1000.LAN driver requirements

Use with any HP NC310F, NC340T, NC61xx, and NC71xx Gigabit Server Adapter

Always install the latest Novell support pack

Always install the latest HP NSSD

SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)

SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)

SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger)

HP N100.LAN driver requirements

Use with any HP NC31xx Fast Ethernet Server Adapter

Always install the latest Novell support pack

Always install the latest HP NSSD

SET MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)

SET MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger)

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:

Load MONITOR.

Select SERVER PARAMETERS.

Select COMMUNICATIONS.

Set MAXIMUM PACKET RECEIVE BUFFERS = 10000 (or larger).

Set MINIMUM PACKET RECEIVE BUFFERS = 2000 (or larger).

Set MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2048 (or larger).

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

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.

Selections are: ON, OFF, Tx,

Frame = type

node =

Valid types are:

Ethernet_802.2,

Ethernet_802.3, Ethernet_II,

Ethernet_SNAP

Defines the frame type being used by this load

instance. Ethernet_802.2 and Ethernet_II are

the default values.

NNNNNNNNNNNN

Specifies a node address in this field to

override the default Media Access Controller

(MAC) address (also known as the Locally

Administered Address)

name = text

Displays the name assigned to this adapter

Installation 29

Parameter

Options

Description

PDriver =

Default = OFF

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.

Selections are: OFF, ON

RxBuffers =

Default = 200

Pre-allocates ECB resources on the adapter for

receiving packets

Recommended Min = 32

Max = 512

Min = 1 when used with DOS

Client32 and when Keywrod

P3-1 or 2.

TxDescriptors =

Default = 200

Pre-allocates ECB resources on the adapter for

transmitting packets.

Recommended Min = 100

Max = 512

Min = 1 when

used with DOS

Client32 and when

Keywrod P3-1 or

RxFlow =

TxFlow =

Slot = n

Default = OFF

Allows enabling/disabling of RxFlow control.

Allows enabling/disabling of TxFlow control.

Selections are: ON, OFF

Default = OFF

Selections are: ON, OFF

Identifies the slot number for the specific

adapter currently being configured. This

parameter is not necessary if only a single

adapter is installed.

Speed = n

Jumbo =

If link negotiation has been disabled, specifies

port speed to be either Auto, 10HD or 10FD,

100HD or 100FD.

Set maximum physical receive Enables/disables Jumbo Frame support. When

packet Size = 18000 in the

STARTUP.NCF. Choices are

Jumbo = 1514–9000. This

keyword is only supported on

NetWare 6.x.

enabled, jumbo packets of up to 9000 bytes

are supported. Not supported on NC1020

adapters.

Link=

Default=FORCE

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.

Selections are: AUTO, FORCE

RxTicks=

Default = 360

Enables the use of batching receives within a

specific time period.

Min = 0, disabled

Max = 5000000, 5 seconds

Units are in micro seconds

Installation 30

Parameter

Options

Description

TXPacketsPer

Default = 64

Min = 0, disabled

Max = 100

Enables the use of batching transmits to a

specific amount of packets.

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

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

reference in your Novell NetWare online documentation.

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.

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:

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

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.

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.

Syntax: FORCEDUPLEX=n

Where n =

0—auto-negotiate

1—half-duplex

2—full-duplex

Default = auto-negotiate

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.

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.

Syntax: SPEED=n

Where n = 10 or 100 or 1000

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.

Syntax: NODE=xnxxxxxxxxxx

Where n = 2, 6, A, E

Where x = hexadecimal number

Default = The adapter's assigned address

•

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

Syntax: FRAME=n

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

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.

Syntax: POLL=n

Where n = 0 (interrupt mode), 1 (polling mode with interrupt backup)

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.

Syntax: SPURIOUS=n

Where n = 0 or 1

0—Driver operates in normal mode

1—Driver operates to reduce the number of spurious interrupts

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.

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

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

Syntax: AGG_SELECTION=[BANDWIDTH | COUNT]

Description: Sets active aggregator selection mode by bandwidth or count

BALANCE_INTERVAL

Syntax: balance_interval=nnn

Description: Changes Balance interval, nnn counts 1/18 sec

BALANCE_SET_DEFAULT

Syntax: balance_set_default

Description: Restores Balance interval to factory settings

COMMIT

Syntax: commit [team=nnn]

Installation 44

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

•

DELAY

Syntax: delay=nnn

Description: Delays the commit in nnn seconds

•

FRAME

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

HELP

Syntax: -H

Description: Displays Help

Example: CPQANS -H

•

JOIN_INDIVIDUALS

Syntax: join_individuals=[yes | no]

Description: Joins all individual links to one aggregator

LBN

Syntax: Reset LBN=nnn

Example: cpqans reset lbn=nnn

Description: Resets the logical board number (LBN) of a bound adapter. Supported only after

commit command. Default value = 0

•

MAX_TX_QUEUE

Syntax: max_tx_queue=nnn

Description: Sets the Max number of TX ECBs queued for send

•

MODE

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

NAME

Syntax: name=[any unique name]

Description: Sets a unique name

•

PRIMARY

Syntax: primary | secondary

Description: Identifies the primary adapter. Supported only in BIND command

PROBE_BURST_SIZE

Syntax: probe_burst_size=nnn

Description: Changes number of probes to send in a retry

PROBE_CHECK_INTERVAL

Syntax: probe_check_interval=nnn

Description: Changes probes check interval

PROBE_RECHECK_INTERVAL

Syntax: probe_recheck_interval=nnn

Description: Changes probe retries check interval

Installation 45

•

PROBE_RETRY_COUNT

Syntax: probe_retry_count=nnn

Description: Changes probes retry count

PROBE_SEND_INTERVAL

Syntax: probe_send_interval=nnn

Description: Changes probes send interval, nnn counts 1/18 sec

PROBE_SET_DEFAULT

Syntax: probe_set_default

Description: Restores probes settings to factory settings

PROBES

Syntax: probes=[on | off]

Description: Enables/disables probes

PROBES

Syntax: probes=[BROADCAST|MULTICAST]

Description: Changes probes addressing

RECOMMIT

Syntax: recommit [team=nnn]

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

REMOVETEAM

Syntax: removeteam [team=nnn]

Description: Removes a team. Use after hot binding to base drivers with Team=nnn

REMOVEVLANID

Syntax: RemoveVlanID=nnn

Description: Removes the selected VLAN

RESET

Syntax: RESET LBN=nnn

Description: Supported only after Commit command

SECONDARY

Syntax: primary | secondary

Description: Identifies the secondary adapter. Supported only in BIND command.

SMPMODE

Syntax: SMPMODE=[SMP | NONSMP]

Description: Enables/disables SMP aware

STATUS

Syntax: status [team=nnn]

Description: Prints CPQANS status

TEAM

Syntax: team=nnnn

Installation 46

Description: Identifies the team. nnnn=DecimalNumber.

•

TX_ECBS_TO_USE

Syntax: tx_ecbs_to_use=nnn

Description: Sets number of TX ECBs to allocate per virtual adapter

VLANID

Syntax: VlanID=nnn

Description: Sets team to VLAN mode. Creates MLID edge

Installation 47

Firmware upgrade utility

In this section

Windows utilit y...................................................................................................................................... 48

c-Class BladeSystem utilit y....................................................................................................................... 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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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.

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

argument

Description

/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

input

Result

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

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

nicfwupg.exe -f

nicfwupg.exe -p

Suppresses console output

Forces downgrades or restores as needed

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

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

nicfwupg_mf.exe -f

nicfwupg_mf.exe -p

Suppresses console output

Forces downgrades or restores as needed

Requests a restore on all adapters

nicfwupg_mf.exe -e [MAC

Address]

Requests a restore on one adapter. Supply

the MAC address for the adapter.

nicfwupg_mf.exe -o [MAC

Address]

Performs an upgrade of boot code for one

adapter. Supply the MAC address for the

adapter.

nicfwupg_mf.exe -x [MAC

Address]

Performs an upgrade of PXE for one

adapter. Supply the MAC address for the

adapter.

nicfwupg_mf.exe -b [MAC

Address]

Performs an upgrade of CLP for one

adapter. Supply the MAC address for the

adapter.

nicfwupg_mf.exe -i [filename]

Performs an upgrade and stores the image

file to be used during a restore. Supply the

filename.

Return codes

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

Upgrade component failed to install

Upgrade component installed successfully

Upgrade component did not detect any supported network

adapters

Firmware upgrade was recommended, but the upgrade

component was instructed to not update the firmware

All firmware versions are current and an upgrade is not

recommended

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:

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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.

Click the SoftPaq file to extract the files and then open the cmponent.htm file.

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

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

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.

Go to the HP website (http://www.hp.com ).

Click Software & Driver Downloads from the left menu bar.

Type the product name in the For product box and press Enter. For example, type NC370T.

Select an operating system.

Click HP ProLiant Networking Software.

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.

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