HP Network Adapter Software and Configuration Guide Part Number 441877-00B March 2007 (Second Edition)
© Copyright 2005-2007 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software.
Contents Overview..................................................................................................................................... 5 Supported adapters and operating systems................................................................................................... 5 Adapter driver and software information ...................................................................................................... 7 PCI Hot Plug ...........................................................
Multifunction gigabit server adapter teaming ............................................................................................ 129 Windows 2000 and Windows NT4 teaming............................................................................................ 130 NetWare teaming ................................................................................................................................. 139 VLAN properties ......................................................................
Overview In this section Supported adapters and operating systems ................................................................................................. 5 Adapter driver and software information..................................................................................................... 7 PCI Hot Plug ............................................................................................................................................ 9 Duplex support.................................
• 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 Por
• 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.
5. Click HP ProLiant Networking Software. 6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number. 7. Click the SoftPaq file to extract the files and then open the cmponent.htm file.
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.
No support • Linux No support Upgrading the adapter with a persistent driver To upgrade the adapter with a persistent driver: 1. Manually remove (unload) the driver. 2. Power down the slot and remove the adapter. 3. Upgrade the adapter (add the option module). 4. Reinstall the upgraded adapter. 5. Power up the slot to let NetWare automatically detect the (upgraded) adapter.
3. Set Speed/Duplex on the adapter to Auto/Auto, 10/Half, 10/Full, 100/Half, 100/Full, or 1000/Full. 4. Click OK until prompted to restart. 5. Restart Windows NT® 4.0. Windows® 2000, Windows Server 2003, and Windows Server 2003 x64 For new installations, Windows® 2000 automatically installs the adapter drivers.
Examples: • o 100 Mbps full-duplex: FORCEDUPLEX=2 SPEED=100 o 10 Mbps full-duplex: FORCEDUPLEX=2 SPEED=10 Syntax: SPEED= n (n = 10 or 100 or 1000) Specifies the speed the driver uses. If you do not use this parameter, the driver automatically detects the network speed. If unable to detect the network speed, the driver defaults to 10 Mbps. If you use this parameter, the driver operates at the specified speed instead of auto-detecting network speed. NOTE: The NC3133 adapter supports 100 Mbps only.
Installation In this section Download latest drivers, firmware, and documentation............................................................................... 13 Windows Server 2003 and Windows Server 2003 x64 ............................................................................ 13 Windows 2000 and Windows NT........................................................................................................... 15 Linux.............................................................................
5. Click HP ProLiant Networking Software. 6. Click download and save the HP SoftPaq (sp#####.exe) file to a directory on your hard drive. The SoftPaq file is a self-extracting executable with a file name based on the SoftPaq number. 7. Click the SoftPaq file to extract the files and then open the cmponent.htm file. Windows Server 2003 x64 IMPORTANT: NC31xx, NC6132, NC6133, and NC7132 adapters are not supported in Windows Server 2003 x64.
1. Run the appropriate Driver Component Package (listed as CPxxxxxx.exe) in a directory on your hard drive. The component is a self-extracting executable with a file name based on the component number. 2. Click the Install button to proceed with the installation. 3. After the drivers have been installed, you may delete the Component Package that you copied. Removing the driver software To remove the driver software: 1.
To update the network driver, follow these instructions: Locate the driver on the CD, diskette, or directory on your hard drive where you copied it from an updated source. See Technical Support for a list of online sources for software and driver updates. 1. Run the appropriate Driver Component Package (listed as CPxxxxxx.exe) in a directory on your hard drive. The component is a self-extracting executable with a file name based on the component number. 2.
5. 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. 6. On the Windows NT® server, prepare the Microsoft® Client Installation disk using the Windows NT® Network Client Administrator: a.
;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] NB
[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.
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.
7. Click the SoftPaq file to extract the files and then open the cmponent.htm file. In addition, the Linux (open source) drivers can be found at the HP software and drivers website (http://h18000.www1.hp.com/support/files/index.html). HP ROMPaqs for specific servers can be found at the HP support website (http://www.hp.com/support). The source RPM is suitable for use on any system that has the RPM utility installed and a properly configured kernel source tree.
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.
100 Mbps full-duplex 1000 Mbps full-duplex o Flow Control Disabled (default) Auto Negotiation (Symmetric Pause advertised) Receive Pause Transmit Pause Receive & Transmit Pause o MAC Address No Override (default) - a user-administered MAC address entered with a colon separating each hexadecimal byte (for example, 12:34:56:78:9a:bc).
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.
dd if=bcmedu.img of=/dev/rdiskette bs=36k Installing Solaris DU dskettes You can use Solaris DU diskettes in the following ways: • To use new drivers to install or upgrade the Solaris operating system environment on a system with new hardware. • To add new drivers to support new hardware on an already installed and booted system. Installing Solaris using DU diskettes To install Solaris (Intel Platform Edition) using drivers on the DU diskette: 1.
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.
3. If Volume Management is running, temporarily stop it by typing: # /etc/init.d/volmgt stop 4. Insert the DU diskette into the disk drive. 5. Mount the DU diskette at the /mnt mount point: # mount -F pcfs /dev/diskette /mnt At this point, you must mount the DU diskette in the file structure to update your system successfully. 6. Execute the install script on the diskette, using the appropriate Solaris release directory (currently sol_26 for Solaris 2.6, sol_27 for Solaris 7, and so on).
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.
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.
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 Recommended Min = 32 Pre-allocates ECB resources on the adapter for receiving packets Max = 512 Min = 1 when used with DOS Client32 and when Keywrod P3-1 or 2.
Parameter Options Description TXPacketsPer Default = 64 Enables the use of batching transmits to a specific amount of packets. Min = 0, disabled Max = 100 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.
# 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.
o Full-duplex. The adapter sends and receives packets at the same time. This improves the performance of your adapter. Set duplex mode to full-duplex ONLY if you have a hub/switch that supports full-duplex. o Half-duplex. The adapter performs one operation at a time. It either transmits or receives. NOTE: The HP NC31xx, 340T, and NC71xx Server Adapters support full-duplex and halfduplex. The HP NC61xx fiber Gigabit Server Adapters support full-duplex mode only and cannot be changed.
• NODE. This keyword specifies a locally administered address (LAA) unique to each adapter. Use this option to provide your own unique node address for the adapter. The node address is a 12-digit hexadecimal number. The second digit must be one of the following digits: 2, 6, A, E. o Syntax: NODE=xnxxxxxxxxxx Where n = 2, 6, A, E Where x = hexadecimal number o • Default = The adapter's assigned address FRAME. This keyword indicates one of four valid frame types the system is transmitting and receiving.
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.
• 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.
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.
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.
• 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.
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.
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.
• 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.
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 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.
o • • DELAY o Syntax: delay=nnn o Description: Delays the commit in nnn seconds FRAME o • • • • • • • • • Syntax: frame=[ETHERNET_802.2 | ETHERNET_802.
• • • • • • • • • • • • • PROBE_RETRY_COUNT o Syntax: probe_retry_count=nnn o Description: Changes probes retry count PROBE_SEND_INTERVAL o Syntax: probe_send_interval=nnn o Description: Changes probes send interval, nnn counts 1/18 sec PROBE_SET_DEFAULT o Syntax: probe_set_default o Description: Restores probes settings to factory settings PROBES o Syntax: probes=[on | off] o Description: Enables/disables probes PROBES o Syntax: probes=[BROADCAST|MULTICAST] o Description: Ch
o • • Description: Identifies the team. nnnn=DecimalNumber. TX_ECBS_TO_USE o Syntax: tx_ecbs_to_use=nnn o Description: Sets number of TX ECBs to allocate per virtual adapter VLANID o Syntax: VlanID=nnn o Description: Sets team to VLAN mode.
Firmware upgrade utility In this section Windows utility ...................................................................................................................................... 48 c-Class BladeSystem utility ....................................................................................................................... 54 Linux utility ............................................................................................................................................
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 Gi
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.
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 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.
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 NCSeries Broadcom adapters in the system nicfwupg_mf.exe -s Suppresses console output nicfwupg_mf.exe -f Forces downgrades or restores as needed nicfwupg_mf.
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.
• SUSE Linux Enterprise Server 9 x86 Linux 64 • Red Hat Enterprise Linux 4 for AMD64 and Intel EM64T • Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T • SUSE Linux Enterprise Server 10 for AMD64 and Intel EM64T • SUSE Linux Enterprise Server 9 for AMD64 and Intel EM64T For a complete listing refer to the Linux Readme file located in the HP SoftPaq file.Complete the following steps to download and extract the SoftPaq file. 1. Go to the HP website (http://www.hp.com). 2.
• HP NC7760 PCI-X Gigabit Server Adapter • HP NC7761 PCI Gigabit Server Adapter • HP NC7780 Gigabit Server Adapter • HP NC7781 PCI-X Gigabit Server Adapter • HP NC7782 Dual Port PCI-X Gigabit Server Adapter Mezzanine Adapters: • HP NC320m PCI Express Dual Port Gigabit Server Adapter • HP NC325m PCI Express Quad Port 1Gb Server Adapter for c-Class BladeSystem • HP NC326m PCI Express Dual Port 1Gb Server Adapter for c-Class BladeSystem • HP NC373m PCI Express Dual Port Multifunction Gigabit
names for the packages are hpnicfwupg-.i386.rpm for Linux 32 and hpnicfwupg.x86_64.rpm for Linux 64. The instructions below describe the x32 version. 1. Before the RPM package is installed, check for the existence of a previous version by issuing the rpm -q hpnicfwupg command. 2. If a previous version is found, remove it using the rpm -e hpnicfwupg command. 3. Install the RPM package using the hpnicfwupg–.rpm command. 4.
Command line argument Description –p Previous. Interactively restores previous firmware images that were automatically backed up prior to the firmware update. This option is useful for recovering from firmware upgrade failures. This option can be used with any other option. –h Help. Displays the usage message. If this option is used with any other option, the other options are ignored. –c Displays server adapters and current firmware version without performing an updates.
Error level Meaning 2 Hpnicfwupg did not attempt firmware upgrade because the installed firmware was up-to-date, the target hardware was not present, the command was invalid, the user responded no to all prompts, or the user selected quit in response to a prompt. For options –c and –i, a 2 means that the information could not be displayed. 3 Hpnicfwupg attempted to upgrade firmware but one or more upgrades failed due to an unrecoverable error.
• HP NC7761 PCI Gigabit Server Adapter • HP NC7780 Gigabit Server Adapter • HP NC7781 PCI-X Gigabit Server Adapter • HP NC7782 Dual Port PCI-X Gigabit Server Adapter IMPORTANT: For each server adapter in the target server, the driver for the adapter must be installed and enabled for the server adapter to be upgraded. If the driver is unable to communicate with the server adapter, the server adapter cannot be updated.
7782327B NICFWUPG PT5704C2 PXE_V322 Q57UDIAG SP29044 PXE_V778 PXE_V839 320TV355 BIN BAT 36 BIN EXE TXT BIN BIN BIN 11. Boot the system using the DOS diskette. 12. Run NICFWUPG.BAT from a command prompt.
Adapter configurations In this section HP NC-Series Broadcom adapters............................................................................................................ 62 HP NC-Series Multifunction adapters ........................................................................................................ 66 HP NC-Series Intel adapters..................................................................................................................... 69 Windows ...............................
• FixCheckSumOff—This string parameter turns off the driver work-around for the TCP/IP stack to recognize the 1's complimented version of the checksum. The following are examples of the use of these keywords in the protocol.ini. [Q57] DriverName = "Q57$" BusNum = 3 DevNum = 14 PortNum = 2 LineSpeed = 100 Duplex = Full NodeAddress = "001020304050" To add more adapters (up to four), repeat the entry below, where n can be from 1 to 3.
• • • • • • • DRIVERNAME o Possible value: BXND20X$ o This field is case sensitive LINESPEED o Possible values: 10, 100, or 1000 o Default: AUTONEG BUSNUM o Possible values: the bus slot number the NC37xx/NC380x device is on o Default: the bus slot number occupied by one of NC37xx/NC380x devices in the system DEVNUM o Possible value: the device number the NC37xx/NC380x device is on o Default: the device number occupied by one of NC37xx/NC380x devices in the system FUNCNUM o Possible
HP PXE implementation is supported in the following environments: • Linux Red Hat PXE Server. HP PXE clients are able to remote-boot and utilize network resources (for example, NFS mount) and to do Linux installation. In the case of a remote boot, the Linux universal driver binds seamlessly with the HP UNDI (Universal Network Driver Interface) and provides a network interface in the Linux remote-booted client environment.
To boot in DOS and connect to a network for the DOS environment, download the Intel® PXE PDK from the Intel® web site. This PXE PDK comes with a TFTP/ProxyDHCP/Boot server. The PXE PDK can be downloaded from the Intel website (http://downloadfinder.intel.com/scripts-dfexternal/Support_Intel.aspx). Red Hat Linux Red Hat Linux 7.2 (or higher) distribution has PXE server support. It allows users to perform a complete Linux installation over the network.
protocol. See the Microsoft website (http://www.microsoft.com) to download the Microsoft iSCSI Software Initiator installation wizard software and to obtain installation and usage information. The accelerating iSCSI feature comes standard with standup HP Multifunction Server Adapters.
The HP NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters have PXE support. PXE is a software protocol that allows your networked computer to boot with the images provided by remote servers across the network. PXE operates in a client/server environment. A network consists of one or more boot servers that provide boot images to multiple computers through the network. The PXE driver complies with the PXE-2.1 specification.
The current version of Windows® 2000 does not include a network driver for the NC32xx, NC37xx, NC380x, NC1020, NC6770, and NC77xx Gigabit Server Adapters. To perform remote installation with PXE, include a network driver for these adapters as part of the client's installation image on the server. Refer to Microsoft® Article ID Q246184, "How to Add Third-Party OEM Network Adapters to RIS Installations.
• Compliance with the Wired for Management Baseline (WfM) 2.0 specification • Compatibility with legacy boot agent environments that use BOOTP protocol • Customization in pre-boot, Windows®, and DOS environments Operating environment The Boot Agent operates in a client/server environment. Often, in this environment, one or more servers provide remote boot services to a large number of client computers through a common network.
The configuration setup menu shows a list of configuration settings on the left and their corresponding values on the right. Key descriptions near the bottom of the menu indicate how to change values for the configuration settings. For each selected setting, a brief "mini-Help" description of its function appears just above the key descriptions. 2. Select the setting you need to change by using the arrow keys. 3.
Configuration settings Possible values Setup Menu Wait • Time 0 seconds • 2 seconds • 3 seconds • 5 seconds Description Controls the number of seconds the Boot Agent waits for you to press the Ctrl+S keys, so as to suspend the boot process and then configure the way the Boot Agent operates. If you select a Setup Menu Wait Time setting of zero and/or a Show Setup Prompt setting of Disabled, the Ctrl+S setup prompt will not appear during the boot process.
is in the suspended state when this is enabled. It is strongly recommended that no more than two adapters should have this feature enabled per computer. • Intel Boot Agent. When enabled, the computer can initiate PXE/RPL boot if a valid flash image is present on the adapter. Running IBAUtil in DOS IBAUtil (for DOS) must be run with the computer booted to DOS only. This utility cannot be run in a DOS window in any Microsoft® Windows® product or in DOS compatibility mode in IBM OS/2.
Parameter Description -SAVE Saves existing Intel Boot Agent and EEPROM settings to a file. The file is named based on the PCI Vendor and Device ID of the adapter. -RESTORE Restores previously saved Intel Boot Agent image. IBAUtil looks for a file name based on the PCI Vendor and Device ID of the adapter. If -RESTORE is used with -UPGRADE, an error is generated. Power Management Options -WOLDISABLE or -WOLD Disables WOL bit on Fast Ethernet and disables APMPME and APME EEPROM bits on gigabit.
• 5–EEPROM read failure • 6–EEPROM write failure • 7–EEPROM dump failure • 8–(Not used) • 9–No memory • 10–No adapters found Examples of IBAUtil command lines The following are examples of some typical IBAUtil command lines.
PCI configuration space could not be read. Machine is probably not PCI compliant. The Boot Agent was unable to read one or more of the adapter's PCI configuration registers. The adapter may be misconfigured, or the wrong Boot Agent image may be installed on the adapter. The Boot Agent returns control to the BIOS and not attempt to remote boot. Try to update the flash image. If this does not solve the problem, contact your system administrator or HP Customer Support.
Base code cannot be installed. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. • PXE-EC4: UNDI ROM ID structure was not found. UNDI ROM ID structure signature is incorrect. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. • PXE-EC5: UNDI ROM ID structure is invalid. The structure length is incorrect. An incorrect flash image is installed or the image has become corrupted.
If you are accustomed to redefining your computer's boot order using the motherboard BIOS setup program, the default settings of the Boot Agent setup program can override that setup. To change the boot sequence, you must first override the Boot Agent setup program defaults. To start the Boot Agent configuration setup program, press the Ctrl+S keys during the time the initialization message appears. A configuration setup menu appears allowing you to set configuration values for the Boot Agent.
• MAC Address—The individual address of the device as stored in the EEPROM • I/O—The I/O address for PCI access determined by the software. On cards without an I/O address, all zeros are displayed • Memory—The memory map PCI access address determined by the software • Slot—The slot number reported by the BIOS. The number displayed is the BIOS version of the PCI slot number. Therefore, actual positions of adapters within slots may not be displayed as expected.
Term / Abbreviation / Acronym Definition Flb Flash Library IA32 Shorthand for computer platforms based on Intel 32-bit architecture CPUs. IA64 Shorthand for computer platforms based on Intel 64-bit architecture CPUs. IAL Intel Architecture Lab IBA Intel Boot Agent IETF Internet Engineering Task Force.
Term / Abbreviation / Acronym Definition RIS Remote Installation Services. A Microsoft® service that uses PXE to deliver the Network Bootstrap Program (NBP) to start the boot process. Ships with Windows® 2000 Advanced Server. ROM Read-Only Memory. When used in this guide, ROM refers to a non-volatile memory storage device on an adapter RPL Remote Program Load. A bootable network device protocol, developed and used mostly by IBM. TCO Total Cost of Ownership.
see a message referring to this value with the "$." The user must remember to enter the "$" character as part of the parameter's value. • SPEED o Syntax: SPEED=[Auto | 10 | 100] o Example: SPEED=10 o Default: Auto-Speed-Detect as a function of PHY detection o Normal Behavior: If either 10 or 100 is specified, a message indicates that Auto-Speed-Detect has been disabled and the driver sets the speed using the value specified.
• o Normal Behavior: The value will be used by the PHY detection routine to locate and initialize the PHY. If a PHY is not found at the address specified, the driver will load but not function properly, because PHY detection occurs after the initial load has occurred. o Possible Errors: If the PHYADDRESS parameter is set to an invalid value, the parameter is ignored and the default value is used, and a message indicates a "Parameter value out of range" error. SLOT o Syntax: SLOT=[0x0..
• • o Default: 8, corresponding to 32 bytes or 8 dwords in the receive FIFO. o Normal Behavior: No message will be displayed. The driver will use the specified value to configure. o Possible Errors: If the RXFIFO parameter is set to an invalid value, the parameter is ignored and the default value is used, and a message indicates a "Parameter value out of range" error. TXFIFO o Syntax: TXFIFO=[0..15 | 0x0..
o Normal Behavior: The value will be used to configure the 82557 at initialization time. Setting it to a low value will force frequent internal arbitration, which will affect overall performance. The value can be tuned to obtain optimum balance between the TX and Rx DMA machines. o Possible Errors: If the RXDMACOUNT parameter is set to an invalid value, the parameter is ignored and the default value is used, and a message indicates a "Parameter value out of range" error.
CAUTION: If the number of buffers allocated causes the driver’s size to exceed MAXIMUM, the driver adjusts the number of buffers downward, by reducing each of the counts of transmit/receive buffers by one until the total allocation will fit in the available memory. A message indicates the actual number of buffers allocated. Under DOS without Window for Workgroups (WFW), MAXIMUM is defined as 64Kb for all code and data.
Keywords for N1000 NDIS2 driver The following describes how to configure the parameters for the NDIS 2 driver version 3.62 (N1000.DOS). Configuration The following configuration parameters are supported through the PROTOCOL.INI file. The "Possible Errors" section describes the driver's behavior when error conditions are detected. If an error is fatal, the driver will not load. In all other cases the driver will load and use the default value.
o Normal Behavior: The driver uses the value of the parameter to decide which adapter to control. o Possible Errors: If only one adapter is installed and the value does not correctly indicate adapter slot, a message indicates that the value does not match the actual configuration, and the driver finds the adapter and uses it. If more than one adapter is installed and the value does not indicate the adapter slot, a message indicates that the specified slot is invalid for the driver instance.
o • SLOT=0x7 CACHEFLUSH parameter o Set this to 1 to hook the system Disk Buffer Flush interrupt. This causes the driver to properly turn off the adapter when the system is shut down by Windows NT® during remote installation (pushinstall). o CACHEFLUSH=1 o Known Limitations: This driver does not support any application that uses protected mode, for example, EMM386. In addition, testing has demonstrated that the GHOST software application fails when used with this driver under Netx (VLMs are OK).
To customize the Boot Agent configuration settings: 1. Highlight the setting you want to change using the arrow keys. Then press Enter. 2. Press the spacebar until the desired value appears. 3. If you want to change additional settings, repeat steps 1 and 2. 4. After you have completed your changes, press F4 to update the adapter with the new values. Boot Agent configuration settings The following table describes the Boot Agent configuration settings.
Configuration settings Possible values Setup Menu Wait • Time 0 seconds • 2 seconds • 3 seconds • 5 seconds Description Controls the number of seconds the Boot Agent waits for you to press the Ctrl+S keys, so as to suspend the boot process and then configure the way the Boot Agent operates. If you select a Setup Menu Wait Time setting of zero and/or a Show Setup Prompt setting of Disabled, the Ctrl+S setup prompt will not appear during the boot process.
adapter receives before generating an interrupt). A high value improves CPU efficiency, but may reduce adapter bandwidth. • • • • • o Default = 1536 o Range = 0–4096 (increments of 32) Number of Coalesce Buffers (NC31xx adapters only). Specifies the number of memory buffers available to the driver in case the driver runs out of available map registers. This buffer area is also used when a packet consists of many fragments.
o Range 1000BASE-SX or -LX Adapters: Auto/Auto 10/100/1000 Adapters: Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full; 1000/Full NOTE: This property is disabled for the NC310F and NC61xx adapters. • • • Locally Administered Address. Specifies the user-defined MAC Address of the adapter, which overrides the burned-in MAC Address. This box is disabled if the selected adapter has been teamed. o Default = NULL o Range = Valid unicast MAC Address 802.1p QoS Packet Tagging. Enables or disables IEEE 802.
NC6132, NC6133, and NC6134: 80–768 (increments of 8) NC6136, NC7131, and NC7132: 80–256 (increments of 8) NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32) Windows Server 2003 Windows Server 2003 x64 NC6132, NC6133, and NC6134: 80–768 (increments of 8) NC6136, NC7131, and NC7132: 80–256 (increments of 8) NC310F, NC340x, NC6170, and NC7170: 80–4096 (increments of 32) NC110x, NC360x, and NC364x: 80-2048 (increments of 8) • Number of Transmit Descriptors: Minimum/Maximum.
• • • • • • • Enable PME. (NC110T, NC310F, NC340x, NC360x, NC364T, NC6170, and NC7170 only) Allows the use of power management and wake-up functions. o Default = No Action o Range = Disable; Enable; No Action; H/W Default Wake On. (NC110T, NC310F, NC340T, NC360x, NC364T, NC6170, and NC7170 only) Available only when Enable PME is enabled. Allows you to choose what types of packets will cause the adapter to wake.
system memory used by the driver. If too few receive descriptors are used, performance suffers. If too many receive descriptors are used, the driver unnecessarily consumes memory resources. o Default = 200 o Range = 100–512 NOTE: This property is not supported on HP Multifunction Server Adapters. • Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is compatible with the link partner (examples: switch, hub).
• • • • • • o Default = Auto o Range = Auto, 10Mb, 100Mb Flow Control. Specifies the type of flow control that is needed. o Default = Auto o Range = Disable; Rx Pause; Tx Pause; Rx/Tx Pause; Auto Rx TCP Checksum Offload. Offloads the task of computing the checksum for incoming TCP or UDP packets, thereby improving performance. o Default = Enabled o Range = Disabled; Enabled Tx TCP Checksum Offload.
• • o SRB Timeout Delta. Increases or decreases the timeout value for I/O operations through the iSCSI HBA. Increasing this value may help prevent premature I/O timeouts if your network is highly congested and packets are being dropped frequently. The default setting is 15 seconds. This property only displays if iSCSI is enabled on the adapter. o iSCSI VLAN. Allows you to create a VLAN for an iSCSI-enabled device. TCP/IP Offload Engine (TOE).
b. If prompted to restart your computer, click Yes. Rebooting the system for new adapter properties to take effect is not required; however, rebooting is recommended to re-initialize all registers. Windows Server 2003 and Windows Server 2003 x64 adapter properties • 802.1p QoS Packet Tagging. The 802.1p QoS parameter is a standard that enables Quality of Service. This property is disabled by default. To change this property, select Enable or Disable. • Checksum Offload.
• Speed & Duplex. The Speed & Duplex property allows the user to set the connection speed to the network and mode. The Duplex Mode allows the adapter to transmit and receive network data simultaneously. The adapter is set to Auto (optimum connection) by default. Set the speed and mode as described below: o 1 Gb Full Auto. Sets the speed to 1 Gbps and mode to Full-Duplex o 10 Mb Full. Sets the speed to 10 Mbps and mode to Full-Duplex o 10 Mb Half.
many receive descriptors are used, the driver unnecessarily consumes memory resources. This property is only available through the HP Network Configuration Utility. o Default = 200 o Range = 100–512 Multifunction Gigabit Server adapter properties • SRB Timeout Delta. Increases or decreases the timeout value for I/O operations through the iSCSI HBA. Increasing this value may help prevent premature I/O timeouts if your network is highly congested and packets are being dropped frequently.
recommended selection is Auto and it is the default setting. To disable Flow Control, select Disable from the Value list on the Advanced tab. • o Auto. (Default) Auto detect flow control o Disable. PAUSE frame receipt and transmission is disabled o Tx PAUSE. PAUSE frame transmission is enabled o Rx PAUSE. PAUSE frame receipt is enabled o Rx/Tx PAUSE. PAUSE frame receipt and transmission is enabled Speed & Duplex.
o Auto. (Default) Sets the speed for optimum network connection NOTE: This property is not supported on the NC150T and NC7782 adapters. Multifunction Gigabit Server adapter iSCSI properties • SRB Timeout Delta. Increases or decreases the timeout value for I/O operations through the iSCSI HBA. Increasing this value may help prevent premature I/O timeouts if your network is highly congested and packets are being dropped frequently. The default setting is 15 seconds.
recommended selection is Auto and it is the default setting. To disable Flow Control, select Disable from the Value list on the Advanced tab. o Auto. (Default) Auto detect flow control o Disable. PAUSE frame receipt and transmission is disabled o Tx PAUSE. PAUSE frame transmission is enabled o Rx PAUSE. PAUSE frame receipt is enabled Rx/Tx PAUSE. PAUSE frame receipt and transmission is enabled NOTE: User control of Flow Control parameter is not available for NC71xx adapters.
• • • • • • • • • Offload Receive TCP Checksum. Offloads the task of computing the checksum for incoming TCP or UDP packets, thereby improving performance. o Default = On o Range = Off; On Offload Transmit TCP Checksum. Offloads the task of computing the checksum for outgoing TCP or UDP packets, thereby improving performance. o Default = On o Range = Off; On Offload Transmit IP Checksum. This property does not apply to the NC6132, NC6133 or NC6134 adapters.
Modifying NC31xx Fast Ethernet adapter properties Although the default values should be appropriate in most cases, you may change any of the available options to meet the requirements of your specific system. Use the following procedure to verify or change the properties after the adapter driver is installed. To change the adapter properties, display the Driver Properties Advanced tab as follows: 1. On the desktop, click Start then select Control Panel > System to display the System Properties window. 2.
• Link Speed & Duplex. Allows the user to set the connection speed to the network and mode. FullDuplex Mode allows the adapter to transmit and receive network data simultaneously.
• • • • • • Adaptive Interframe Spacing. Compensates for excessive Ethernet packet collisions on the network. The default setting works best for most computers and networks by dynamically adapting to the network traffic conditions. However, in some rare cases, you may obtain better performance by manually setting the spacing value. Setting a value forces a static gap between packets. Increasing the value increases the delay between frames being transmitted.
• Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is compatible with the link partner (examples: switch, hub). o Default 1000BASE-SX or -LX Adapters: 1000/Full 10/100/100 Adapters: Auto/Auto o Range 1000BASE-SX or -LX Adapters: 1000/Full 10/100/100 Adapters: Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full; 100/Full • Maximum Frame Size. Specifies the maximum number of bytes in a single packet.
Properties for NC67xx and NC77xx Server Adapters • • Speed/Duplex Setting. Changes the current speed and duplex settings. Be sure this setting is compatible with the link partner (examples: switch, hub). o Default = Auto/Auto o Range = Auto/Auto; 10/Half; 10/Full; 100/Half; 100/Full; 1000/Full Maximum Frame Size. Specifies the maximum number of bytes in a single packet. Larger frames can increase throughput and decrease CPU use by putting more data in each packet, thereby sending out fewer packets.
1. Load the network drivers for the network adapters that will be part of the team. The frame types loaded should be the same for all adapters in the team and the same as those loaded for QASP.LAN. Do not bind protocols directly to these adapters. 2. Load ODINEB.NLM (a Novell supplied NLM) before all network drivers. Example: LOAD ODINEB.NLM LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_1_EII SLOT=1 LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_2_EII SLOT=2 3. Load QASP.LAN.
NOTE: In SLB mode, IPX traffic is load-balanced on the send side but not on the receive side. Loading frame types After one or more network adapters are bound to a virtual adapter, additional frame types can only be loaded in the virtual adapter if the corresponding frame types are also loaded in the bound adapters. For example, ETHERNET_802.2 can be loaded in QASP VSLOT 1 only if ETHERNET_802.2 is loaded for the Q57 driver in SLOT 1 and 2.
BIND QASP1 Q57_2_EII If there are multiple VLANs (each with one or more frame types) loaded on the virtual adapter, it is only necessary to bind one frame type on one VLAN on the virtual adapter to the same frame type on the physical adapter. The other VLANs will be automatically bound. 4. Bind protocols to QASP.LAN. Example: BIND IP QASP_1_V2_EII ADDR=x.x.x.x MASK=x.x.x.x This example creates a team with two adapters using VLAN ID 2.
team support hardware checksums. Be sure to load the adapter drivers with hardware checksums enabled. Default is ON. Example: A team of two adapters with hardware checksums enabled. LOAD QASP.LAN FRAME=ETHERNET_II NAME=Q57_1_EII CHECKSUM=ON VSLOT=1 LOAD ODINEB.NLM LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_1_EII CHECKSUM=ON SLOT=1 LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_2_EII CHECKSUM=ON SLOT=2 BIND QASP1 Q57_1_EII BIND QASP1 Q57_2_EII • NOSCREEN. This keyword disables the menu-driven screen when QASP.
Load QASP.LAN with the frame types and VLAN ID(s) specified. LOAD ODINEB.NLM LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V2_EII VSLOT=1 VLAN=2 LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V3_EII VSLOT=1 VLAN=3 LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V4_EII VSLOT=1 VLAN=4 Load the network drivers for the network adapters in the team with the same frame types and VLANs specified. LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_1_EII SLOT=1 VLAN=1 LOAD Q57.
LOAD QASP.LAN VSLOT=1 FRAME=Ethernet_II NAME=QASP_1_EII LOAD QASP.LAN VSLOT=1 FRAME=Ethernet_802.2 NAME=QASP_1_E82 LOAD Q57.LAN SLOT=1 speed=100fd FRAME=Ethernet_II LOAD Q57.LAN SLOT=2 speed=100fd FRAME=Ethernet_II NAME=Q57_1_EII NAME=Q57_2_EII LOAD Q57.LAN SLOT=1 speed=100fd FRAME=Ethernet_802.2 LOAD Q57.LAN SLOT=2 speed=100fd FRAME=Ethernet_802.2 NAME=Q57_1_E82 NAME=Q57_2_E82 bind qasp1 q57_1_EII bind qasp1 q57_2_EII BIND IP QASP_1_EII ADDR=192.222.20.1 MASK=255.255.255.
LOAD QASP.LAN VSLOT=4 FRAME=Ethernet_II NAME=QASP_4_EII LOAD Q57.LAN SLOT=7 speed=100fd FRAME=Ethernet_II NAME=Q57_7_EII LOAD Q57.LAN SLOT=8 speed=100fd FRAME=Ethernet_II NAME=Q57_8_EII bind qasp4 q57_7_eii bind qasp4 q57_8_eii BIND IP QASP_4_EII ADDR=192.222.23.1 MASK=255.255.255.0 • Example 6: VLAN with QASP LOAD ODINEB.NLM LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V100_EII VSLOT=1 VLAN=100 LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V200_EII VSLOT=1 VLAN=200 LOAD QASP.
LOAD BIND BIND BIND Q57.LAN FRAME=ETHERNET_II NAME=Q57_1_EII SLOT=2 QASP1 Q57_1_EII QASP1 Q57_2_EII IP QASP_1_EII ADDR=172.16.210.1 MASK=255.255.0.0 NOTE: 802.3ad mode requires the Ethernet switch to support 802.3ad with LACP (Link Aggregation Control Protocol). Configuration parameters for Q57.LAN driver Configuration parameters for Q57.LAN driver include: • TxDescriptors= o This keyword is to initialize Descriptor resources on the adapter for transmits.
• • • • • • • o This keyword is to enable the use of batching receives within a specific time period. o Min = 0, disabled o Max = 5000000, 5 seconds o Units are in micro seconds o Default = 360 TxPacketsPer= o This keyword is to enable the use of batching transmits to a specific amount of packets. o Min = 0, disabled o Max = 100 o Default = 64 CheckSum= o This keyword is to enable or disable the transmit & receive checksum off loading feature.
NOTE: If you modify any adapter parameters, you must reboot the system for the changes to take effect. If you make changes and do not reboot, you may experience configuration problems. NetWare Client 32 driver installation for HP adapters The NC10032.LAN driver is a high-performance server driver that meets the Open Data Link Interface (ODI) v1.11 C specification. It can be used on Client 32 workstations with NetWare v3.X servers and greater. Installing Client 32 on DOS 1.
o Syntax: FORCEDUPLEX=n Where n= 0–auto-negotiate 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. o Default: auto-negotiation o Examples: 100 Mbps full-duplex: FORCEDUPLEX=2 SPEED=100 10 Mbps full-duplex: FORCEDUPLEX=2 SPEED=10 • SPEED. If no speed setting is specified, the adapter auto-negotiates the speed with the hub/switch, either 10 or 100 Mbps.
FILES=100 buffers=25 LASTDRIVE=m fcbs=4,4 device=c:\6150\amsida.sys device=c:\6150\amsicd.sys /d:cpqcd001 • Example AUTOEXEC.BAT PROMPT $p$g @ECHO OFF C:\dos\mscdex.exe /d:cpqcd001 @CALL C:\nw5c32\STARTNET Solaris To customize the driver edit "/kernel/drv/bcme.conf" and update the respective parameters in this file. The parameters include the following. • ForceSpeedDuplex. Configures link (or instance) to a certain Speed and Duplex. By default, AutoNegotiate (0) is set.
4—Advertise both Rx and TX flow control being enable and negotiate with link partner. If link AutoNegotiate is not enabled, then both Tx & Rx Flow Control are disabled. Example: FlowControl=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0; • MaxJumboFrameSize. Configures the Jumbo Frame feature of a link. The valid range for this parameter is 0 to 9000. If the value configured is less than 1500, then the Jumbo Frame feature is disabled.
Example: TxCoalescingTicksDuringInt=75; • RxMaxCoalescedFramesDuringInt. Configures the number of Rx Maximum Coalesced Frames parameters during interrupt handling. This determines the upper-boundary of maximum number of Rx buffer descriptors that the device processes before it will generate an interrupt during interrupt handling. The default value is 10. Example: RxMaxCoalescedFramesDuringInt=10; • TxMaxCoalescedFramesDuringInt.
• To query current configuration of Flow Control of instance 3: ndd -set /dev/bcme Instance 3 ndd -get /dev/bcme FlowControl • To blink all LEDs for 10 seconds of adapter of instance 5: ndd -set /dev/bcme Instance 5 ndd -set /dev/bcme BlinkLeds 10 Adapter configurations 125
Team properties In this section Adapter teaming .................................................................................................................................. 126 Multifunction gigabit server adapter teaming ........................................................................................... 129 Windows 2000 and Windows NT4 teaming .......................................................................................... 130 NetWare teaming ........................................
(NFT) provides the safety of additional backup links between the server and hub/switch. Dynamic Dual Channel NFT is implemented with one channel team providing a primary adapter and another channel team providing a secondary, backup adapter(s). During normal operations, if the adapters in the primary team fail, a link to one of the adapters in the secondary, backup team automatically takes over. • 802.3ad Dynamic Dual Channel NFT and Preference Order (INP). Available in the ProLiant Essentials INP only.
SLB works only with SLB-enabled switches, such as the Catalyst 6000 series. The SLB software continuously analyzes loading on each adapter and balances network traffic across the adapters as needed. Adapter teams configured for SLB also provide the benefits of NFT. To use SLB, you must have at least two HP Fast Ethernet or Gigabit adapters installed in your server and linked to the same SLB-enabled switch.
Select or change the Transmit Balancing Method for the team. If the team type is Network Fault Tolerance Only with Preference Order or Network Fault Tolerance Only (NFT), the Transmit Balancing Algorithm list disabled and Automatic is selected. o Automatic. (Recommended) Default setting. Teaming driver selects the load balancing mechanism based on the packet type. o TCP Connection. Load balances transmit TCP packets using the TCP connection. o Destination IP Address.
• If the new team includes at least one TOE-enabled adapter and at least one non-TOE capable adapter, the team is created with TOE disabled and TOE is disabled on all of the individual teamed adapters. • If a non-TOE capable adapter is added to a TOE-enabled team, the team is changed to TOE disabled. TOE functionality for each teamed adapter is disabled.
• Any HP Software and Documentation CD Version 5.0 or earlier shipped with an HP 10/100 or Gigabit adapter The HP Primer Utility is supported on the following operating systems: • Microsoft® Windows NT® 4.0 • Microsoft® Windows® 2000 For PRIMER.EXE, refer to the HP Softpaq #10652 at the HP support website (http://h18000.www1.hp.com/support/files/index.
o HP System Partition Upgrade Utility Using HP Primer Utility from the graphical user interface To remove the Windows NT® components either before or after upgrading to Windows® 2000, follow these steps: 1. From the location where you have downloaded Primer, double-click PRIMER.EXE. 2. Click CLEANUP. The utility will now remove the previously-installed Windows NT® components. 3. Exit the Windows® 2000 Primer Utility from HP. 4. Reboot your system for the changes to take effect.
Method 2: Manual Removal 1. Dissolve all teams and controller-pairs with their respective utilities. 2. Upgrade the OS to Windows® 2000. 3. Install the new HP Network Configuration Utility (NCU) for Windows® 2000. Installing the teaming driver NOTE: Before installing the Teaming protocol (Teaming driver), you may want to back up the Windows® 2000 Registry. To install the teaming driver: 1. Go to the HP website (http://www.hp.com). 2. Click Software & Driver Downloads from the left menu bar. 3.
6. A message box appears with a warning that the protocol information for the primary adapter, such as the IP address must be configured properly. Click OK to exit this message box. 7. Restart the HP NCU and verify the adapter protocols were configured properly. Select the adapter and click Properties. Uninstalling teamed adapters If you need to completely uninstall a teamed adapter (not simply replace it), perform these steps to ensure proper operations: 1. Select the Team and click Dissolve. 2.
• Shared Access (Enable)—If selected, it allows Internet connection sharing. You can share Applications and Protocols. • Applications tab—Displays network applications to be enabled for servers sharing this connection. • Services tab—Displays services to be provided to the remote network.
WakeUp Capabilities WOL Speed • • Driver Tab o Name, Version number, Driver Details o Install o Uninstall o Update driver Resources Tab o Resource settings o Conflicting device list • Install button—Installs the selected protocol • Uninstall button—Uninstalls the selected protocol • Properties button—Accesses dialogs on the protocol for the selected device. Sharing Tab Sharing allows other servers or your local network to access external resources through this connection.
• TLB load balances IP traffic under Windows NT® and IP and IPX traffic under NetWare. • Switch-assisted Load Balancing (SLB). SLB increases a server's throughput using Fast Ethernet or Gigabit Ethernet ports. SLB load balances all traffic. Unlike TLB, SLB can be configured to increase both transmitting and receiving channels between your server and switch.
3. Select two to eight of the listed adapters by single-clicking them. Individual stand-alone adapters will remain selected as you click them. After you have selected all the desired adapters for a team, click the Team button on the upper-right of the main dialog window. IMPORTANT: If the proper Service Pack level (SP5) has not been installed on the system, a popup message displays warning you of this condition. If this message is displayed, install the correct Service Pack before proceeding. 4.
11. Click Close at the bottom of the Network Control Panel applet to finish configuration of network devices. 12. Binding analysis will be done to bind newly installed adapters and teams to all installed communication protocols. You may be prompted to enter protocol specific information (such as IP information) for newly installed adapters and teams. 13. When prompted, click Yes to reboot Windows NT® .
o Syntax: LOAD CPQANS MODE=XXX o Example: LOAD CPQANS MODE=NFT NOTE: NFT is the default mode. Issuing a "LOAD CPQANS COMMIT" command without specifying a "MODE" will result in a team configured for the Network Fault Tolerance mode. • • Adaptive Load Balancing (ALB). Creates a team of two or more adapters to increase transmission throughput while providing adapter redundancy. HP recommends that all adapters in an ALB team be the same speed (either all Gigabit or all Fast Ethernet).
• Every member of a CPQANS team must be connected to the same network segment. If you have multiple CPQANS teams, each team must be on a separate network segment. If you are connected to a VLAN-capable switch, each HP server adapter in a team must be connected to a port with the same VLAN ID number (same network segment). NOTE: VLAN is not supported on heterogeneous teaming.
Error conditions If you receive the error message "Failed to create new team," check the following: • All adapters have the same frame types. • The CPQANS team has the same frame type as the adapters. • That CPQANS is loaded once for each team. • A "BIND CPQANS " command has been issued for each adapter in the team. • All adapters in a team are connected to the same network segment. • CPQANS is not being bound to an unsupported adapter.
• • • • o Default = 3 o Minimum = 1 o Description: Changes the team's number of probes to send in case of a retry. This can also be used after the COMMIT command. load CPQANS probe_send_interval=xxx [team=nnn] o Default = 18 o Range = Relative to other parameters o Description: Changes the time interval sending of regular probes. XXX counts 1/18 second ticks. Only even numbers are supported. Odd numbers are rounded down. This can also be used after the COMMIT command.
Note that ONLY an NFT mode Team can combine an HP Gigabit server adapter (server adapters that use N1000.LAN) and an HP Fast Ethernet server adapter (use N100.LAN). (Exception: The NC71xx Gigabit over copper server adapters can be teamed with adapters of different speeds.) See Overview of NetWare teaming ("NetWare teaming" on page 139) for information about mixing adapters. Note the following: • For simplicity, in this example, only the default frame type 802.2 is used.
This example also differs from the previous example in that the Team will be in the Transmit Load Balancing (TLB) mode. This example assumes a server with two HP Fast Ethernet server adapters, one in PCI Slot 1 and the other in PCI Slot 2. Note that ONLY an NFT mode Team can combine an HP Gigabit server adapter (server adapters that use N1000.LAN) and an HP Fast Ethernet server adapter (server adapters that use N100.LAN).
you do not include "TEAM=1" CPQANS defaults to Team 1. Thus, the "TEAM" command line switch is optional for the first Team. LOAD CPQANS FRAME=ETHERNET_802.2 NAME=GIG_FT_E82 TEAM=1 MODE=NFT LOAD CPQANS FRAME=ETHERNET_II NAME=GIG_FT_EII TEAM=1 3. Load the base drivers for the first Team. LOAD N1000 SLOT=1 FRAME=ETHERNET_802.2 NAME=GIG_E82 LOAD N1000 SLOT=1 FRAME=ETHERNET_II NAME=GIG_EII LOAD N100 SLOT=2 FRAME=ETHERNET_802.2 NAME=100_E82 LOAD N100 SLOT=2 FRAME=ETHERNET_II NAME=100_EII 4.
For CPQANS.LAN to work in VLAN mode, the adapter (or adapters) needs to be connected to a "tagged" port (a "trunk port") on an IEEE 802.1Q compliant switch. This example uses 802.1Q VLAN, which is supported by all HP server adapters that support CPQANS.LAN. (Exception: The NC6134, NC6132, and NC6133 adapters do not support VLANs.) This example uses an HP Fast Ethernet server adapter and is configured for two VLANs (VLAN 5 and VLAN 6).
NOTE: VLAN is not supported on heterogeneous teaming. You can implement Teaming and VLAN at the same time. Because the script gets large quickly, this example only uses one frame type. To have both IP and IPX bound to it, the Ethernet_II frame type will be used instead of Novell's default 802.2. A homogeneous Team of two load-balanced HP Fast Ethernet server adapters configured as members of five different VLANs will be used here. 1. Load TCPIP.NLM. This can be done at any point before binding IP.
2. Load CPQANS twice for each frame type, once for each VLAN. Assign the VLANID number keyword for each instance. LOAD CPQANS FRAME=ETHERNET_802.2 NAME=E82_Vl7 TEAM=1 VLANID=7 LOAD CPQANS FRAME=ETHERNET_II NAME=EII_Vl7 TEAM=1 VLANID=7 LOAD CPQANS FRAME=ETHERNET_802.2 NAME=E82_Vl8 TEAM=1 VLANID=8 LOAD CPQANS FRAME=ETHERNET_II NAME=EII_Vl8 TEAM=1 VLANID=8 3. Load the base driver for each frame type: LOAD N100 SLOT=2 FRAME=ETHERNET_802.2 NAME=PRI_E82 LOAD N100 SLOT=2 FRAME=ETHERNET_II NAME=PRI_EII 4.
VLAN properties In this section VLAN information................................................................................................................................. 150 VLAN information A Virtual LAN (VLAN) is a collection of network nodes that share the same broadcast domain regardless of their physical location or connection point to the network.
ProLiant Essentials In this section Networking pack installation ................................................................................................................. 151 Intelligent Networking Pack-Windows Edition .......................................................................................... 151 Intelligent Networking Pack-Linux Edition.................................................................................................
bottlenecks or broken network linkages, and steer traffic to the optimum route based on network conditions. Advanced networking features include: • o Fast Path Failover—Allows a ProLiant server to use the quickest available path to the core network for all server traffic. o Active Path Failover—Allows a ProLiant server to detect blocked paths and to redirect data along an unblocked path to the core network. o Router Path Failover—Provides redundancy by grouping routers into one router group.
To enable Virus Throttle for Linux, an Intelligent Networking Pack–Linux Edition license must be installed on the system. For additional information about Virus Throttle and how to install an Intelligent Networking Pack license on your system, refer to the HP ProLiant Essentials Intelligent Networking Pack License–Linux Edition User Guide located on the HP website (http://www.hp.com).
Diagnostics In this section PCI shared interrupts............................................................................................................................. 154 HP NC-Series Intel adapter diagnostics ................................................................................................... 154 HP NC-Series Broadcom adapter diagnostics ..........................................................................................
NOTE: The DOS diagnostic utility, DIAGS.EXE, will always use auto-negotiation to determine the link type listed under the "View Adapter Configuration" section. If the network device's port to which your adapter is connected is set to auto-negotiate, then the link type will reflect an auto-negotiated value. If the network device's port has its duplex value forced to full, then the link type will show a half-duplex value. 1.
• Device Registers—Test patterns are written, read, and verified through the adapter's device registers to check proper functionality. • FIFO—This option writes test bit patterns to the adapter's FIFO buffers to check the FIFOs proper functionality. • EEPROM—This option tests both the readability of the EEPROM as well as the integrity of the data stored in the EEPROM. It reads EEPROM and calculates the checksum. This checksum is then compared to the checksum stored in the EEPROM.
Prerequisites The diagnostic utility runs under MS-DOS® v6.22 or later. It will not run from a DOS window in IBM OS/2® or any Microsoft Windows products. This utility is designed to test hardware operation and confirm the adapter's ability to communicate with another adapter in the same network, which primarily confirms cabling status. This diagostic utility is not a throughput measurement tool.
Using indirect addressing method, this test writes increment data into the MAC Hash Register table and reads back for verification. The memory read/write is done 100 times while incrementing test data. • A2. Control register test Each register specified in the configuration contents are defined as read only bit and read/write bit. The test writes zero and one into the test bits to ensure the read only bits are not changed and read/write bits are changed accordingly. • A3.
"16 00's 16 FF's" Fill the entire host DMA buffer with 16 bytes of 00's and then 16 bytes of FF's. "16 FF's 16 00's" Fill the entire host DMA buffer with 16 bytes of FF's and then 16 bytes of 00's. "32 00's 32 FF's" Fill the entire host DMA buffer with 32 bytes of 00's and then 32 bytes of FF's. "32 FF's 32 00's" Fill the entire host DMA buffer with 32 bytes of FF's and then 32 bytes of 00's. "00000000's" Fill the entire host DMA buffer with all zeros.
This is an internal loopback data transmit/receive test. It initializes MAC into internal loopback mode, and transmits 100 packets. The data should be routed back to the receive channel and is received by the receive routine, which verifies the integrity of data. One Gigabit rate is used for this test. • D2. Phy loopback test This test is the same as D1. Mac Loopback Test except the data is routed back via physical layer device. One Gigabit rate is used for this test. • D5.
o • • Example: q57diag.exe -p -npol o Selects negative link polarity in TBI test o Example: q57diag.exe -npol -q Selects quick diagnostic mode • w o Enables WOL programming in manufacture mode After a successful manufacturing testing, the program will set WOL to either enable or disable mode. Value = 0 to disable WOL and 1 to enable WOL. When -f is entered, software uses eeprom.bin's content for WOL setting. When -w is entered with -f, -w is ignored. • o Example: q57diag.
o Default Settings Enabled Tests: A1. Indirect Register Test A2. Control Register Test A3. Interrupt Test A4. Built In Self Test A5. PCI Cfg Register Test B1. Scratch Pad Test B2. BD SRAM Test B3. DMA SRAM Test B4. MBUF SRAM Test B5. MBUF SRAM via DMA Test C1. NVRAM Test C2. CPU Test C3. DMA Test C4. MII Test C5. VPD Test C6. ASF Test C7. Expansion ROM Test D1. Mac Loopback Test D2. Phy Loopback Test D4. MII Miscellaneous Test (Copper only) Disabled Tests: B6. External SRAM Test D3.
o • • -dpmi o Specifies the use of DPMI memory allocation o Uses DPMI memory allocation method to allocate memory instead of malloc() or free(). -dir o • Example: q57diag.exe -bus 5 Program tests UUTs on bus 5 Displays the version of the IPMI (Intelligent Platform Management Interface) -errctrl Specifies action on error -> a:abort, w:wait, l:loop, c:continue, s:skip • -com Enables com port value (1..
• -firmall Updates device eeprom based on ; Only MAC address will be preserved • -pxe Programs PXE firmware from file • -elog Produces a log file with only error information • -dids Shows PCI DID, VID, SDID, and SVID of present devices • • • • • • -pasf o Programs ASF firmware o is a text file that contains ASF bin file names -pxes o Sets PXE speed o Value = 0 for auto; Value = 1 for 10HD; Value = 2 for 10FD; Value = 3 for 100HD; Value = 4 for 1
o • • dflt = 1 -rstpl o = post GRC rst poll interval, dly in ms; dflt = 10 o = post GRC rst poll count; dflt = 0 (disable) -rstpld Above post reset polling counts display enable. • -addref (x) Added a ref card info of dev to refinfo.
5. Read only bit %s got changed after writing 1's at offset 0x%X 6. Read/Write bit %s did not get cleared after writing zero at offset 0x%X 7. Read/Write bit %s did not get set after writing 1's at offset 0x%X 8. BIST failed. 9. Could not generate interrupt 10. Test aborted by user 11. Tx DMA:Got 0x%08x @ 0x%08x. Expected 0x%08x 12. Rx DMA:Got 0x%08x @ 0x%08x. Expected 0x%08x 13. Tx DMA failed 14. Rx DMA failed 15. Data error, got 0x%08X at 0x%08X, expected 0x%08X 16.
41. No external memory detected 42. DMA buffer %04X is large, size must be less than %04X 43. File size %d is too big, max is %d 44. Invalid %s 45. Failed writing 0x%x to 0x%x 46. *1 47. *1 48. *1 49. *1 50. Cannot perform task while chip is not running. (need driver) 51. Cannot open register define file or content is bad 52. ASF Reset bit did not self-cleared 53. ATTN_LOC %d cannot be mapped to %cX CPU event bit %d 54. %s Register is not cleared to zero after reset 55.
The diagnostic software lets you test adapters to see if there are any problems with the adapter hardware, cabling, or network connections. HP recommends that you run diagnostics every time you install an adapter. Prerequisites The diagnostic utility runs under MS-DOS® v6.22 or later. It will not run from a DOS window in IBM OS/2® or any Microsoft Windows products.
• B3. RXP scratchpad • B4. COM scratchpad • B5. CP scratchpad • B6. MCP scratchpad • B7. TAS header buffer • B8. TAS payload buffer • B9. RBUF via GRC • B10. RBUF via indirect access • B11. RBUF Cluster list • B12. TSCH list • B13. CSCH List • B14. RV2P scratchpads • B15. TBDC memory • B16. RBDC memory • B17. CTX page table • B18. CTX memory Group C: Block tests • C1.
This test issues multiple chip resets and constant driver load/unload to check for boot ROM appropriately loads the bootcode. This test requires a proper bootcode to be programmed into the non-volatile memory. • C8. DMA engine test This tests the internal DMA engine by performing both DMA reads and writes at various location and various sizes. CRC check is performed to ensure data integrity. DMA write test also checks to ensure that the DMA writes do not corrupt the neighboring host memory.
1. If you have not already done so, download and extract the HP SoftPaq file and then run MAKEDISK.BAT to create a driver disk. 2. Boot to DOS or the EFI shell. 3. From the DOS prompt navigate to the \APPS\DIAGS\MFDIAG directory. 4. Type XDIAG and press the Enter key. The diagnostic tests run automatically. Command line options The following are the available options in xdiag. They are case sensitive.
Technical support In this section Before you contact HP........................................................................................................................... 172 HP contact information.......................................................................................................................... 172 Free automated customer support services ...............................................................................................
The following sites offer troubleshooting information, compatibility notes, and software upgrades (including Softpaqs and drivers). HP Worldwide Web Server • Navigate to a specific product, and then look for support information from the list of support resources at the HP support website (http://h18007.www1.hp.com/support/files/server).
Acronyms and abbreviations BIOS Basic Input/Output System DHCP Dynamic Host Configuration Protocol IPL initial program load iSCSI Internet Small Computer System Interface PCI peripheral component interface PDU power distribution unit PXE Preboot Execution Environment ROM read-only memory RSS Receive-Side Scaling SAN storage area network TCP/IP Transmission Control Protocol/Internet Protocol TOE TCP/IP Offload Engine Acronyms and abbreviations 174
UNDI Universal Network Driver Interface VLAN virtual local-area network Acronyms and abbreviations 175
Index A P Adapter teaming 129, 139 Advanced Server Program for NetWare 110 PCI Hot Plug 9 PCI shared interrupts 155 properties 91, 98, 106 PXE configuration HP NC-series Broadcom adapters 64, 67 HP NC-series Intel adapters 89 B Boot Agent 69 D S diagnostics 155, 157 Diver and software information 7 DXE configuration NC37xx and NC380x 67 Solaris driver information guide 23 supported operating systems 5 T F teaming adapters 126 Firmware upgrade 48 U H Unix driver software Gigabit Ethernet Adapt
