Ethernet Support GuideHP-UX 11i v3

AbstractThis document contains specific information that is intended for users of HP products.

HP Part Number: 5900-2305Published: October, 2012Edition: 3

© Copyright 2012 Hewlett-Packard Development Company, L.P.

Legal Notices

The information in this document is subject to change without notice.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, CommercialComputer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government undervendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP productsand services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed asconstituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Acknowledgments

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group.

Revision history

This table indicates the part and edition numbers, and the publication date, of each revision of the document. For changes made to the currentedition of this document, see Section 5.2 (page 58).

Publication dateEdition numberDocument manufacturing part number

October 2012Edition 35900–2305

April 2012Edition 25900-2304

November 2009Edition 15969-7066

Contents1 Overview..................................................................................................5

1.1 Fast Ethernet and cards........................................................................................................51.2 Gigabit Ethernet and cards ..................................................................................................61.3 10 Gigabit Ethernet and cards..............................................................................................71.4 HP-UX drivers support a wide variety of cards.........................................................................81.5 Features offered by HP-UX drivers and associated cards............................................................9

2 Installing HP-UX driver software and verifying connectivity..............................152.1 Determining whether the latest version of the LAN driver is installed.........................................152.2 Getting and installing the latest software..............................................................................152.3 Verifying the Ethernet LAN installation.................................................................................16

3 Setting and displaying driver Ethernet parameters.........................................213.1 Tools for configuring Ethernet parameters.............................................................................213.2 Driver Ethernet parameters, configuration files, and startup scripts...........................................213.3 Displaying Ethernet parameters...........................................................................................233.4 Displaying and setting the Ethernet MAC address.................................................................243.5 Displaying and setting parameters for link speed, duplexity, and autonegotiation......................253.6 Displaying and setting the receive and transmit flow control parameters...................................27

3.6.1 Flow control parameters..............................................................................................273.6.2 Displaying current flow control settings.........................................................................283.6.3 Setting the flow control parameter...............................................................................29

3.7 Displaying and setting maximum transmission unit (MTU) parameter and Jumbo Frames.............293.7.1 Before enabling Jumbo Frames.....................................................................................303.7.2 Displaying current MTU/Jumbo Frame settings...............................................................303.7.3 Setting MTU/Jumbo Frames........................................................................................313.7.4 Verifying the MTU size change....................................................................................31

3.8 Displaying and setting the multiple queue parameter.............................................................313.9 Displaying and setting the Checksum Offload (CKO) parameter..............................................323.10 Displaying and setting the TCP segmentation offload (TSO)/Virtual MTU parameter.................343.11 Displaying and setting the TCP segment reassembly parameter...............................................353.12 Other parameters............................................................................................................363.13 Unsupported parameters of iether driver on HP-UX 11i..........................................................38

4 Troubleshooting........................................................................................394.1 Troubleshooting overview...................................................................................................394.2 Basic troubleshooting tips..................................................................................................394.3 Diagnostic flowcharts........................................................................................................40

4.3.1 Flowchart 1: Cable and LED test..................................................................................404.3.1.1 Flowchart 1 procedures.......................................................................................41

4.3.2 Flowchart 2: Link-level test...........................................................................................424.3.2.1 Flowchart 2 procedures.......................................................................................43

4.3.3 Flowchart 3: Network-level tests...................................................................................434.3.3.1 Flowchart 3 procedures.......................................................................................43

4.3.4 Flowchart 4: ARP test.................................................................................................444.3.4.1 Flowchart 4 procedures......................................................................................44

4.3.5 Flowchart 5: ping test................................................................................................444.3.5.1 Flowchart 5 procedures.......................................................................................45

4.3.6 Flowchart 5 ping test (continued) ................................................................................464.3.6.1 Flowchart 5 (continued) procedures......................................................................46

4.3.7 Flowchart 6: Transport-level test...................................................................................474.3.7.1 Flowchart 6 procedures.......................................................................................47

4.3.8 Flowchart 7: Bridge/gateway loopback test .................................................................48

Contents 3

4.3.8.1 Flowchart 7 procedures......................................................................................484.3.9 Flowchart 8: Configuration tests..................................................................................49

4.3.9.1 Flowchart 8 procedure........................................................................................494.3.10 Flowchart 9: ioscan and nwmgr tests..........................................................................49

4.3.10.1 Flowchart 9 procedures.....................................................................................504.3.11 Flowchart 10: netfmt and nwmgr -r -c lanppa tests.........................................................51

4.3.11.1 Flowchart 10 procedures.....................................................................................524.3.12 Flowchart 11: ifconfig test...........................................................................................53

4.3.12.1 Flowchart 11 procedures....................................................................................534.3.13 Network-level test for Jumbo Frames............................................................................54

4.3.13.1 Test procedure..................................................................................................544.4 Ethernet-specific information...............................................................................................54

4.4.1 Error messages..........................................................................................................544.4.2 Logging messages....................................................................................................54

4.5 Contacting HP for problem support.....................................................................................555 Support and other resources......................................................................56

5.1 Contacting HP .................................................................................................................565.1.1 Contacting Your HP representative: what to provide for technical support...........................565.1.2 HP contact information................................................................................................57

5.2 New and changed information in this edition ......................................................................585.3 Related information...........................................................................................................58

5.3.1 Documentation..........................................................................................................585.3.2 HP-UX manual reference pages (manpages)..................................................................585.3.3 Webpages with related information.............................................................................59

5.4 Typographic conventions....................................................................................................596 Documentation feedback...........................................................................61A Cabling requirements...............................................................................62

A.1 Connectors......................................................................................................................62A.2 Cabling..........................................................................................................................62

A.2.1 Back-to-back connection.............................................................................................62B Card statistics..........................................................................................63

B.1 nwmgr display..................................................................................................................63B.1.1 RFC 1213 MIB II..........................................................................................................64B.1.2 RFC 1284 Ethernet-like interface statistics.......................................................................65

B.2 Card statistics...................................................................................................................66B.2.1 Explanation of card statistics.......................................................................................67

Glossary....................................................................................................68Index.........................................................................................................74

4 Contents

1 OverviewThis manual provides an overview of HP Gigabit and 10-Gigabit Ethernet network interface cards(NICs) for HP-UX 11i v3 and describes how to install, configure, administer, and troubleshootthem.The information in this manual is intended for network managers who administer Ethernet networks.It is assumed that the reader is experienced with the basics of local and wide area networkingand has a knowledge of HP-UX operating system concepts, commands, and configuration.This chapter provides an overview of Ethernet technology and its features.

1.1 Fast Ethernet and cardsFast Ethernet is the Ethernet networking technology that carries traffic at the nominal rate of 100megabits per second (Mbit/s), which is ten times that of the original Ethernet speed of 10 Mbit/s.Fast Ethernet was introduced in 1995 and remained the fastest version of Ethernet for approximatelythree years until it was superseded by Gigabit Ethernet. Fast Ethernet is based on IEEE 802.3standards and uses the standard CSMA/CD (carrier sense multiple access with collision detection)to avoid collisions among devices sharing the network.Fast Ethernet is sometimes referred to as 100Base-T, representing any of several standards fortwisted pair cables. Fast Ethernet is also referred to as 100Base-X, where “X” is the placeholderfor the variants of the physical medium, such as TX (copper) and FX (optical fiber). In either case,the “100” represents the transmission speed, while “Base” refers to baseband signalling, whichmeans only Ethernet signals are carried on the medium. Fast Ethernet runs on unshielded twistedpair (UTP) and fiber optic cable. The most commonly-supported Fast Ethernet variant is 100Base-TX,which carries data at 100 Mbit/s over two-pair category 5 (Cat 5) or better cables. Each networksegment can have a maximum distance of 100 meters (328 ft). In its typical configuration,100Base-TX uses one pair of twisted wires in each direction, providing 100 Mbit/s of throughputin each direction (full-duplex).HP offers a suite of 10/100Base-T Ethernet LAN network interface cards (NICs) — NICs are alsoreferred to in this document as cards or adapters — for every networking requirement. From thebasic single-port 10/100 Ethernet NIC to the 4-port 10/100 NIC to the 2-port 100Base-T and2-port SCSI Combo adapter, HP provides a standards-based networking solution for every need.All of the Ethernet/Fast Ethernet NICs are tuned for high performance and high availability on theHP-UX servers. For more information about NICs, see Section 1.4 (page 8).The HP Ethernet/Fast Ethernet LAN adapters fully support the IEEE 802.3 and 802.3u standards.These scalable network links allow customers to move large amounts of data quickly while leveragingtheir existing investments in Ethernet technology. Based on the same Ethernet standards alreadywidely deployed in the marketplace, the HP LAN adapters protect customers’ investments byallowing them to migrate from 10 to 100 Mbit/s quickly and easily, with fast deployment andminimal training. Use of the HP Ethernet adapters not only enables customers to implementstreamlined high-speed networking projects but, with the multi-ported cards, also preserves valuableI/O slots in their enterprise servers.In addition, most HP Ethernet/Fast Ethernet cards support HP-UX VLANs (Virtual LANs). Thissoftware-based solution offers IT Managers a powerful tool that simplifies the tasks of building,managing, and securing complex network infrastructures. Physical LANs can be segmented intosmaller logical or “virtual” LANs, allowing broadcast traffic to be reduced, thereby improvingoverall network performance. HP-UX VLAN is compliant with host-based IEEE 802.1Q VLANtagging, IEEE 802.1p (later incorporated in IEEE 802.1D) priority encoding, and IP Type of Service(ToS)—802.1p priority conversion.For more information about HP-UX VLAN functionality, see the following website:http://www.hp.com/go/vlan

1.1 Fast Ethernet and cards 5

Some of the other major features that might be provided by these cards are listed in Section 1.5(page 9).HP-UX provides software drivers that manage the 100Base-T Ethernet cards or interfaces. Forexample, the btlan driver manages both 100Base-T and 100Base-FX interfaces. For moreinformation about this driver and managing it, see the nwmgr_btlan(1m) manpage and “Settingand displaying driver Ethernet parameters” (page 21).For more detailed information on the currently supported Fast Ethernet cards, drivers, and theplatforms that support them, see the HP-UX Ethernet Card Support Matrix document at the followingBusiness Support Center website:www.hp.com/go/hpux-iocards-11iv3-docs

NOTE: The btlan driver is not mentioned by name in the HP-UX Ethernet Card Support Matrixdocument. The driver does not come with a separate software bundle as do most other driversmentioned there but instead is automatically installed with the HP-UX kernel.

1.2 Gigabit Ethernet and cardsGigabit Ethernet (GbE) is an Ethernet networking solution that supplanted most Fast Ethernet inwired local area networks because of its higher performance. Gigabit Ethernet delivers Ethernetframes at a rate of a gigabit per second (Gb/s), as defined by the IEEE 802.3-2008 standard.Gigabit Ethernet is a generic reference to 1000Base Ethernet, which provides a transmission speedof 1000 Mbit/s for baseband signalling. Gigabit Ethernet includes the following basic standards:

• 1000Base-T IEEE 802.3ab — Gigabit Ethernet over copper cables using four pairs of category5 or better twisted pair to achieve the gigabit data rate. Generally this standard supports amaximum length of 100 meters. 1000Base-T brings high bandwidth with 10, 100, and 1000Mbit/s speeds, which makes more network bandwidth available for applications. 1000Base-Tcan be used in data centers for server switching, for uplinks from desktop computer switches,or directly to the desktop for broadband applications. A big advantage of 1000base-T is thatexisting copper cabling can be used instead of having to rewire with optical fiber.

• 1000Base-SX IEEE 802.3z — Gigabit Ethernet over shortwave laser multi-mode fiber opticcable, generally for a maximum length of 550 meters. This standard is popular for intra-buildinglinks in large office buildings, co-location facilities and carrier neutral internet exchanges.

The demand for higher-speed network connections is growing at a tremendous rate to keep pacewith the speed requirements of current applications and systems. Data centers process terabytesof data daily. Processing, sharing, and distributing this data requires faster and faster networks.Intelligent cards take on more of the network processing from the server. They have become criticallyimportant in helping servers cope with the onslaught of traffic running at Gigabit/s speeds.The HP Gigabit Ethernet intelligent cards are designed to maximize host CPU efficiency by takingon more of the network processing from the server. These cards include features provided by FastEthernet 10/100Base-T cards and more. They not only perform functions such as TCP/IP checksum,interrupt coalescing, and byte swapping, but also enable the reduction of host data copy operations.Bulk data transfers can be optimized by using Jumbo Frames — the large 9000-byte maximumtransfer unit (MTU) improves system efficiency.The Gigabit LAN cards are also supported with HP Auto Port Aggregation (APA) software. Up to4 Gigabit Ethernet links can be logically aggregated to form a single, extremely high-bandwidthchannel with one IP address, automatic link failover, and load balancing.HP Gigabit Ethernet cards support HP-UX VLANs, as discussed in Section 1.1 (page 5).The 1000Base-T cards are tri-speed cards that support autonegotiation and autosensing. Theyoperate in full-duplex mode at 10, 100 and 1000 Mbit/s or in half-duplex mode at 10 and 100Mbit/s.

6 Overview

1000Base-SX cards support full-duplex point-to-point or back-to-back operations only (usingswitch-to-card or card-to-card connections). The cards do not support half-duplex and do not speednegotiate (1000 Mbit/s operation only) but do perform autonegotiation for other link parameters.Mezzanine cards and combination (combo) cards are available for some HP servers. The mezzaninecards provide two or more Gigabit Ethernet ports on a single card. The cards are designed forapplications that require additional Gigabit Ethernet ports than those provided on the server. Theyare ideal for virtualization, security, server consolidation, network segmentation, and otherBladeSystem applications requiring additional network port density. Likewise, the combo cardsprovide multiple-function ports with both Ethernet and Fibre Channel connectivity. HP-UX allowsyou to configure the card as several devices, each with different connection functionality.Some of the other major features that might be provided by Gigabit Ethernet cards are listed inSection 1.5 (page 9).HP-UX provides drivers that manage Gigabit Ethernet cards and interfaces. The drivers are shippedwith software bundles. Each driver may support several cards. Table 1 (page 7) lists the HP-UXGigabit drivers, their associated bundle names, and the manpage where you can obtain moreinformation. Some information about managing drivers is also included in “Setting and displayingdriver Ethernet parameters” (page 21).

Table 1 HP-UX Gigabit drivers

ManpageBundleDriver

nwmgr_gelan(1m)GigEther-00gelan

nwmgr_igelan(1m)GigEther-01igelan

nwmgr_iether(1m)IEther-00iether

For more detailed information on the currently supported Gigabit Ethernet cards, drivers, and theplatforms that support them, see the HP-UX Ethernet Card Support Matrix document at the followingBusiness Support Center website:www.hp.com/go/hpux-iocards-11iv3-docsTo see what has changed from one release to the next, see the appropriate release notes for thedriver. The release notes are also located at the previously-mentioned website.

1.3 10 Gigabit Ethernet and cards10 Gigabit Ethernet (also referred to as 10GbE) is a telecommunication technology standardizedin IEEE 802.3a that offers data speeds up to 10 Gb/s — ten times faster than Gigabit Ethernet.Built on the Ethernet technology used in most of today's local area networks (LANs), 10 GigabitEthernet offers more bandwidth for moving data on backbone connections between networks whilealso providing a consistent technology end-to-end.10 Gigabit Ethernet can be used to interconnect LANs, wide area networks (WANs), andmetropolitan area networks (MANs). 10 Gigabit Ethernet uses only full-duplex point-to-pointtransmission over optical fiber, which makes possible a considerable distance range. On multi-modefiber, 10 Gigabit Ethernet can support distances up to 300 meters; on single-mode fiber, it cansupport distances up to 40 kilometers. Gigabit Ethernet networks can feed into a 10 GigabitEthernet network.10GbE network interface cards plug into ordinary computer servers using the PCIe (PCI Express)and PCI-X (PCI-eXtended) bus technology and connect to the LAN with a choice of physical (PHY)modules. HP-UX supports a wide variety of cards, as described in Section 1.4 (page 8). Thesecards offer features provided by Fast Ethernet and Gigabit Ethernet cards, as described in previoussections.Some of the other major features that might be provided by 10 Gigabit Ethernet cards are listedin Section 1.5 (page 9).

1.3 10 Gigabit Ethernet and cards 7

HP-UX provides several drivers that manage 10 Gigabit Ethernet cards and interfaces. The driversare shipped with software bundles. Each driver may support several cards. Table 2 (page 8) liststhe HP-UX 10 Gigabit drivers, their associated bundle names, and the manpage where you canobtain more information. Some information about managing drivers is also included in “Settingand displaying driver Ethernet parameters” (page 21).

Table 2 HP-UX 10 Gigabit drivers

ManpageBundleDriver

nwmgr_ixgbe(1m)10GigEthr-00ixgbe

nwmgr_icxgbe(1m)10GigEthr-01icxgbe

nwmgr_iexgbe(1m)10GigEthr-02iexgbe

nwmgr_iocxgbe(1m)10GigEthr-03iocxgbe

For more detailed information on the currently supported 10 Gigabit Ethernet cards, drivers, andthe platforms that support them, see the HP-UX Ethernet Card Support Matrix document at thefollowing Business Support Center website:www.hp.com/go/hpux-iocards-11iv3-docsTo see what has changed from one release to the next, see the appropriate release notes for thedriver. The release notes are also located at the previously-mentioned website.

1.4 HP-UX drivers support a wide variety of cardsHP-UX drivers support a wide variety of network cards and devices for a variety of platforms. Thesecards support conventional Peripheral Component Interconnect (PCI) as well as PCI-X (PCI-eXtended)and PCIe (PCI Express) computer I/O bus standards (technologies for attaching hardware devicesto a computer).Basic types of network devices supported by HP-UX drivers include:

• LAN on motherboard (LOM)A LOM is a chip or chipset capable of network connections that has been embedded directlyon the motherboard of a server. For example, server blades include LOMs that are dual-port1 or 10 Gigabit Ethernet interfaces.

• Mezzanine cardA mezzanine card, also known as a daughterboard or daughtercard, plugs directly into themotherboard or another plug-in card to extend functionality. It usually fits on top of and parallelto the board or card it plugs into.

• Standup cardA standup card plugs into a PCI slot (PCIe or PCI-X). It may be a single-ported, dual-ported,or quad-ported card, providing one, two, or four connections to the network.

• Combination (combo) cardA 10Gbe/Fibre Channel combo card is a PCIe device that can provide both Ethernet andFibre Channel connectivity, or a PCI-X device that provides both Ethernet and SCSI connectivity.For example, for some combo cards, HP-UX can configure the card as four separate devices— a dual port FC device and a dual port LAN device. The FC devices are connected to anFC fabric through two FC fiber connections on the card. The LAN devices are connected toa 10 Gigabit LAN through two NIC fiber connections on the card. The FC and LAN devicesdo not share bandwidth on a common connection to the fabric or network.

For each of these types of cards, the network device may be dual-ported, providing two connectionsto the network.

8 Overview

The network device may be a converged network adapter (CNA), also called a converged networkinterface controller (C-NIC). This is a computer input/output device that combines the functionalityof a host bus adapter (HBA) with a network interface card (NIC). In other words it “converges”access to, respectively, a storage area network and a local area network. Such devices can beconfigured by HP-UX as a number of LAN devices, depending on the system configuration. Forexample, the 10GigEthr-03 iocxgbe driver can support the CNA. Typically, CNA devices aredual-ported, with each port representing a single wired connection to the network — one for theHBA — Fibre Channel over Ethernet (FCoE) — and one for the LAN. HP-UX can configure adual-ported CNA with as many as eight PCIe functions, each function being a single FCoE or LANdevice. Up to four functions are allowed per port; two of those functions can be FCoE devices (oneper port), the remainder are LAN devices.

• In a Blade Virtual Connect environment, the CNA is configured in the HP Virtual ConnectFlex-10 mode which logically converges up to four NICs over each of two 10 Gigabit serverconnections. The NICs share the total bandwidth of the 10 Gigabit network connection.Bandwidth limits can be dynamically configured on each NIC, on the fly. One of theseindividual devices on each port can be an FCoE device.Several HP 10Gigabit Ethernet drivers support the HP Virtual Connect Flex-10 interface onblade platforms. By allowing you to logically divide each network port into multiple devices,the Flex-10 technology reduces management requirements, the number of NICs and interconnectmodules needed, and power and operational costs. Before HP Virtual Connect was introduced,only two interconnect choices were available for connecting server blades to a network —pass-thru devices and switches. Pass-thru devices are simple but require too many cumbersomecables and create complexity. Blade switches reduce the number of cables but add moremanagement responsibilities for LAN and SAN administrators. In both cases, multiple peopleare needed to perform very simple server tasks. Only HP offers the third choice — HP VirtualConnect. For more information about HP Virtual Connect, see the following website:http://h18004.www1.hp.com/products/blades/virtualconnect/index.html

• In other environments, the CNA is configured as two individual devices per port, one FCoEand one LAN device, depending on the hardware configuration, with both sharing thebandwidth of the network connection.

A CNA device can be integrated into the highly-scalable HP FlexFabric data center architectureof an HP Converged Infrastructure. (Virtual Connect FlexFabric broadens Virtual Connect Flex-10technology to provide solutions for converging different network protocols.) The HP FlexFabricopen architecture uses industry standards to simplify server and storage network connections whileproviding seamless interoperability with existing core data center networks. For more informationabout HP FlexFabric, see the HP FlexFabric website:www.hp.com/go/flexfabricThe network device may be part of a combo card, where multiple ports provide NIC functionalityin addition to SCSI or FC functionality.In a server blade environment, depending on the interconnect module installed, the network devicemay be a multi-function device. Depending on the interconnect module, the system profile, and thedevice, the network device appears as multiple functions, some of these functions are NIC andsome are Fiber Channel over Ethernet (FCoE) — each function appearing and treated as a separatedevice. Although not required, HP recommends listing at least two functions of each port in theprofile.

1.5 Features offered by HP-UX drivers and associated cardsTable 3 (page 10) describes some of the main features supported by HP-UX drivers and associatedcards.

1.5 Features offered by HP-UX drivers and associated cards 9

Table 3 Description of features

DescriptionFeature

Allows use of flow control negotiation and the sending and receiving of pause frames. Forinformation about configuring flow control, see Section 3.6 (page 27).

Receive and transmitflow control

The CKO option enables the network adapter to compute the TCP checksum on transmit andreceive, saving the host from having to compute the checksum. This feature reduces CPU

Transmit and receiveChecksum Offload(CKO) overhead. Some driver interfaces have an attribute that allows you to enable or disable receive

and send CKO; see Section 3.9 (page 32). The feature is valid with IPv4 only.

The TSO option breaks down large groups of data sent over the network into smaller segments.(Also called large segment offload, LSO.) This feature reduces CPU overhead. Some driver

Transmit TCPsegmentation offload(TSO) interfaces have an attribute that allows you to enable or disable receive and send CKO and

transmit TSO; see Section 3.10 (page 34). The feature is valid with IPv4 only.

The reverse of segmentation. Segmented units of data are reassembled into a stream of datain its original form. (Also called large receive offload, LRO.) Some driver interfaces have an

TCP segmentreassembly in driver

attribute that allows you to turn TCP segment reassembly on or off. For more information, seeSection 3.11 (page 35).

HP Flex-10 allows each 10 Gigabit Ethernet adapter port to be divided into up to fourindividual FlexNICs with bandwidth allocation in 100 Mb/s increments (to the maximum of

Flex-10 bandwidthallocation

10 Gb/s per adapter port). Each FlexNIC is an abstraction of a portion of the Virtual Connectconnection, represented to the O/S as a standard NIC — each FlexNIC has a unique MACaddress and supports key benefits of integrated switching, including port aggregation, failover,and VLAN tagging. For more information about HP Virtual Connect, see http://h18004.www1.hp.com/products/blades/virtualconnect/index.html.

Network traffic streams are distributed into queues that can be associated with specificprocessor cores. This distributes the workload and prevents data traffic processing from

Multiple receive queues

overwhelming a single core, for example. The packet queues can be accessed by driverthreads running on different processor cores, such that multiple cores can process networkpackets in parallel. Some driver interfaces have an attribute that allows you to configuremultiple queues. For more information, see Section 3.8 (page 31).

See description of multiple receive queues. For more information, see Section 3.8 (page 31).Multiple transmitqueues

Also known as packet steering on the receive side, when multiple receive queues are supportedby the driver and NIC, the NIC steers inbound packets to different queues so that the network

Receive Side Scaling(RSS) with TCP

load is shared across multiple CPUs to avoid a single-processor bottleneck. RSS enablespacket receive-processing to scale with the number of available processors.

UDP 4-tuple uniquely describes a User Datagram Protocol socket pair. TCP 4-tuple uniquelydescribes a Transmission Control Protocol socket pair. The 4-tuple is a set of source and

UDP 4-tuple, TCP4-tuple

destination IP addresses and port numbers (local and remote socket addresses) that are usedfor calculations. In contrast, a 2-tuple only has source and destination IP addresses.

Large 9000–byte maximum transmission unit (MTU) for improved efficiency and performancefor bulk data transfers. Some driver interfaces have an attribute that allows you to configureJumbo Frames; see Section 3.7 (page 29).

Jumbo Frames

In multicast mode one or more multicast group addresses are programmed into the networkcard through the driver; the card receives and processes all multicast packets corresponding

Multicast andPromiscuous mode

to the programmed addresses. In contract, promiscuous mode allows all packets to be receivedand processed, regardless of type or addressee.

Internet protocol version 6, a version of IP currently used to direct almost all Internet traffic.Intended to succeed IPv4.

IPv6

The IEEE standard supports VLANs on an Ethernet network, defining a system of VLAN taggingand stripping of tags for Ethernet frames, and the accompanying procedures used by bridges

IEEE802.1Q VLANtagging and strippingin h/w and switches in handling such frames. For more information about HP-UX VLAN functionality,

see http://www.hp.com/go/vlan.

Provides a flexible mechanism for managing CPU interrupt assignments by moving externalI/O device interrupts from one CPU to another to prevent performance degradation that wouldoccur if, for example, two heavily loaded I/O cards mapped interrupts to the same CPU.

Interrupt migration

10 Overview

Table 3 Description of features (continued)

DescriptionFeature

To avoid flooding the host system with too many interrupts, packets are collected so one singleinterrupt is generated for multiple packets. Some driver interfaces have attributes that allow

Interrupt coalescing

you to configure the minimum time between interrupts. For 10Gigabit Ethernet drivers, seethe nwmgr_driver(1m) manpage, where driver is the name of the driver.

SmartLink feature enables effective, reliable link redundancy, load sharing, and fastconvergence for switches and Virtual Connect networks.

Link handling

HP-UX dynamically loadable kernel module. Defined as such a module, a new driver can beinstalled without having to reboot the system. Improves system availability by allowing devicedrivers to be configured into the kernel while the system is running.

DLKM

Link aggregation or trunking feature that provides the ability to logically group two or morephysical network ports into a single “Fat Pipe” or “trunk”. Network traffic is load balanced

HP Auto PortAggregation (APA)

across all the links in the aggregation, allowing for large bandwidth logical links into theserver. The links are highly available and completely transparent to the client and serverapplications. For more information, see the HP-UX APA documentation at www.hp.com/go/hpux-APA-docs, and the nwmgr_apa(1m) manpage.

HP APA allows you to combine physical link ports into one failover group formed by LANMonitor. The failover group is used for an alternative when a particular link fails.

HP APA failover(LAN_MONITOR mode)

Accelerated Virtual Input/Output. An I/O protocol that improves virtual I/O performance fornetwork and storage devices used within the Integrity Virtual Machines environment. The

HPVM AVIO

protocol also enables support for a greater number of virtual I/O devices per guest. For moreinformation, see http://www.hp.com/go/hpux-hpvm-docs.

The networking feature that allows virtual machines to directly control I/O devices, minimizingdevice emulation overhead that would be incurred with AVIO.

HPVM Direct InputOutput (DIO)

HP-UX cluster solution that keeps critical application services continually up and running.Services are maintained on multiple servers in the cluster and can be moved between servers

HP Serviceguard

automatically, such as in response to a failure, or by command, such as when a NetworkAdministrator needs to bring a server down to install a new LAN adapter. For more information,see http://www.hp.com/go/serviceguard and http://www.hp.com/go/hpux-SG-docs.

Online Addition, Replacement, and Deletion (OL*) of network cards. Server does not needto be powered off to replace a network card. For more information, see the Interface Card

PCI OLRAD

OL* Support Guide at http://www.hp.com/go/hpux-core-docs (select HP-UX 11i v3) andthe olrad(1m) manpage.Fiber-optic based (Base-SX) and copper-based (Base-T) cards are not considered to be likecards for OL*; that is, you cannot replace a Base-SX card with a Base-T card, and vice versa.

If PCI error occurs, allows HP-UX system to avoid a Machine Check Abort (MCA) or a HighPriority Machine Check (HPMC). Without the PCI Error Handling feature installed, PCI slots

PCI Error handling/recovery1

are set in hardfail mode. If a PCI error occurs when a slot is in hardfail mode, an MCA orHPMC will occur, then the system will crash. When the PCI Error Handling feature is installed,the PCI slots containing I/O cards that support PCI Error Handling will be set in softfail mode.If a PCI error occurs when a slot is in softfail mode, the slot will be isolated from further I/O,the corresponding device driver will report the error, and the driver will be suspended. Theolrad command and the Attention Button can be used to online recover, restoring the slot,card, and driver to a usable state. PCI Error handling and recovery requires installation ofthe PCIErrorHandling-00 bundle.

HP-UX Virtual Partitions (vPars) software partitioning that divides an individual hard partitionor server into several smaller virtual servers, each with their own operating system, resources,

vPars V6

and applications. Any application or operating system-related failures can only impact orbring down the vPar in which it is executing, without affecting other virtual partitions executingon the same system. For more information, see www.hp.com/go/vpars and www.hp.com/go/hpux-vpars-docs.

Collects information about Ethernet links on your system. Can be accessed throughWBEM-based clients. For more information, see http://www.hp.com/go/hpux-networking-docs(click HP-UX 11i WBEM Software).

HP-UX LAN provider

1.5 Features offered by HP-UX drivers and associated cards 11

Table 3 Description of features (continued)

DescriptionFeature

Directs the data link service (DLS) provider to return 64-bit statistics.MIB (SNMP) and driverstatistics

A tool for capturing network events or packets. Logging captures network activities such asstate changes, errors, and connection establishment. Tracing captures, or takes a snapshot

nettl tracing/logging

of, inbound and outbound packets going through the network, as well as loopback or headerinformation. For more information, see the nettl(1m) manpage.

1 Requires installation of PCIErrorHandling-00 bundle.

Table 4 (page 12) indicates the driver support for each feature.

Table 4 Feature support per driver

10 Gigabit EthernetGigabit EthernetFastEthernet

iocxgbe10GigEthr-03

iexgbe10GigEthr-02

icxgbe10GigEthr-01

ixgbe10GigEthr-00

igelanGigEther-01

gelanGigEther-00

ietherIEther-00

btlanFeature

YesYes1YesYesYesYesYesNoReceive flowcontrol

YesYesYesYesNoNoNoNoTransmit flowcontrol

YesYesYes3Yes2YesYesYesNoReceive CKO

YesYesYes3Yes2YesYesYesNoTransmit CKO

YesYesYesYesYesNoYesNoTransmit TSO

YesYesYesYesNoNoNoNoTCP segmentreassembly indriver (LRO)

YesYesNoNoNoN/ANoN/AFlex-10bandwidthallocation

NoNoYesYesNoNoNoNoMultipletransmitqueues

Yes4YesYesYesNoNoNoNoMultiplereceivequeues

Yes6Yes6Yes6Yes 5NoNoNoNoReceive SideScaling (RSS)withTCP/UDP

YesYes8YesYesYesYesYesNoJumboFrames7

YesYesYesYesYesYesYesYesMulticast andPromiscuousmode

YesYesYesYesYesYesYesYesIPv6

YesYesYesYesYes9Yes9Yes9Yes9IEEE802.1QVLANtagging andstripping inh/w

12 Overview

Table 4 Feature support per driver (continued)

10 Gigabit EthernetGigabit EthernetFastEthernet

iocxgbe10GigEthr-03

iexgbe10GigEthr-02

icxgbe10GigEthr-01

ixgbe10GigEthr-00

igelanGigEther-01

gelanGigEther-00

ietherIEther-00

btlanFeature

YesYesYesYesYesYesYesYesInterruptmigration

YesYesYesYesYesYesYes10NoInterruptcoalescing

YesYesNoNoYesNoYesNoLink handling

YesYesYesYesYesYesYesYesDLKM

Yes12Yes12Yes12Yes12, 13YesYesYesYesHP APAaggregatemode11

YesYesYesYesYesYesYesYesHP APAfailover(LAN_MONITORmode)

YesYesYesYesYesNoYesNoHPVM AVIO

YesYesNoNoNoNoNoNoHPVM DIO

YesYesYesYesYesYesYesYesHPServiceguard

Yes14YesYesYesYesYesYesYesPCI OLRAD

YesYesYesYesYesYesYesYesPCI Errorhandling/recovery15

YesYesYesYesNoNoYesNovPars V6

YesYesYesYesYesYesYesYesHP-UX LANprovider

YesYesYesYesYesYesYesYes16MIB (SNMP)and driverstatistics

YesYesYesYesYesYesYesYesnettltracing/logging

1 Not supported with Flex-10 interfaces. With non-Flex-10 interfaces, must be disabled if Jumbo Frames are used.2 Supports UDP multifragment CKO.3 Supports TCP/UDP IPv4 multifragment CKO on some cards.4 On first function of each port.5 The AD385A card supports Destination Port-based Steering (DPS) by default; the card supports configuration of TCP

4-tuple, UDP 4-tuple. The AB287A card supports TCP 4-tuple, UDP 2-tuple.6 TCP 4-tuple; UDP 2-tuple (IPv4 only).7 Supported only on 1000 Mbit/s or faster interfaces; the link partner must also support Jumbo Frames.8 For iexgbe, several restrictions exist (see Section 3.7 (page 29)).9 Does not support stripping.10 Not supported on PCIe cards.11 Not supported on server blade downlinks with Virtual Connect interconnects. Virtual Connect does not support aggregates

(trunks), LACP, or otherwise on the downlinks side.12 Only LACP mode is supported with APA aggregation over 10GbE links.

1.5 Features offered by HP-UX drivers and associated cards 13

13 Not supported with the AB287A card.14 On Superdome 2 only, with up-to-date firmware.15 Require installation of PCIErrorHandling-00 bundle.16 32-bit Extended MIB statistics.

14 Overview

2 Installing HP-UX driver software and verifying connectivityThis chapter describes how to obtain and install the latest software for an Ethernet card and howto verify connectivity.

2.1 Determining whether the latest version of the LAN driver is installedTo determine whether you have the latest version of the LAN card driver on your server, followthese steps:1. Determine the latest available driver for your version of HP-UX by checking the driver’s history

support matrix; for example, the HP-UX Gigabit Ethernet Driver IEther-00 Release History.2. To determine the driver version that is installed in your server’s kernel, run the following

command:what /stand/vmunix /stand/current/mod/* | grep drivername

where drivername is one of the following:

• btlan

• gelan

• iether

• igelan

• icxgbe

• iexgbe

• ixgbe

• iocxgbe

The server displays the LAN driver version. For example:iether_ilan Version: 2 Jan 18 2008iether Revision: B.11.31.0709 Jan 18 2008

2.2 Getting and installing the latest softwareTable 5 (page 15) lists the HP-UX software bundles and the associated drivers that are built intothe HP-UX OE.

Table 5 HP-UX software bundles and associated drivers

DriverSoftware Bundle

ietherIEther-00

gelanGigEther-00

igelanGigEther-01

ixgbe10GigEthr-00

icxgbe10GigEthr-01

iexgbe10GigEthr-02

iocxgbe10GigEthr-03

If your LAN card is a built-in card or was factory installed, the software bundle required for theEthernet card is already loaded onto your system’s hard drive.

2.1 Determining whether the latest version of the LAN driver is installed 15

If you are adding in a LAN card yourself and just want to make sure you have the latest LAN driver,you can get the software driver as follows:• You can get the software bundle containing the Gigabit Ethernet driver from the latest quarterly

release software media. You do not necessarily have to load the entire operating environment(OE). You can either load the entire HP-UX 11i v3 OE from the distribution media and youwill automatically get the correct LAN software bundles, or you can just select and load thesoftware bundle such as GigEther-01 required for the card. To see which LAN driver supportsyour LAN card, see the latest HP-UX Ethernet Card Support Matrix at:http://www.hp.com/go/hpux-iocards-11iv3-docs

• You can also get the latest LAN driver version online as follows:Go to: http://www.hp.com/1.

2. Locate and click the Support & Drivers link on the main page.3. Click the Drivers & Software tab.4. Enter the product order number or name in the search box, and click Search.

Make sure you have the latest Ethernet patches and updates for your driver. Search the driverrelease notes for the latest patch and dependency requirements. Install all driver software anddependency patches.

NOTE: Patches are available from the Software Depot website:https://h20392.www2.hp.com/portal/swdepot/index.do

Once you have the correct driver and the latest patches installed, configure the LAN card’s IPaddress and subnet mask, and set up your LAN card according to the instructions for configuringand verifying Ethernet in the HP-UX System Administrator's Guide: Configuration Management,available at the following location:www.hp.com/go/hpux-systemadmin-docsEach driver has a set of configurable parameters that allow you to set the MAC address and tocontrol such features as duplexity, autonegotiation, flow control, maximum transmission unit size(enabling or disabling Jumbo Frames), TCP segmentation offload, TCP segment reassembly, andmore. For more information, see “Setting and displaying driver Ethernet parameters” (page 21).

2.3 Verifying the Ethernet LAN installationTo verify the Ethernet LAN installation, follow these steps:

• Verify that the LAN card’s Link LED is steadily on (this means the card and driver are installedsuccessfully and the card is connected to a network).

• Issue the nwmgr, ioscan, and lanscan commands to obtain information about the device,such as the MAC address, link state, and the PPA number used to identify the device orfunction.

nwmgr command: MAC addressIn the following nwmgr command example, all the network interfaces in the system aredisplayed. The MAC address is displayed in the third column (identified here as “StationAddress”). For example, the MAC address for interface lan8 — in this instance, the first portof the iocxgbe driver's adapter — is 0x984BE12F3598 (in the example, the line showingthis information is highlighted in bold typeface).

NOTE: “Interface” refers to LAN devices, where a LAN device might be a port (in anon-Flex-10 environment), a function (in a Flex-10 environment), or a pseudo-device such asthe LAN9xx devices, which are APA devices, or LAN5xxx devices, which are VLAN devices(not listed in this nwmgr output example).

16 Installing HP-UX driver software and verifying connectivity

SRVR06 /> nwmgrName/ Interface Station Sub- Interface RelatedClassInstance State Address system Type Interface============== ========= ============== ======== ============== =========lan2 UP 0x001F29F2908C igelan 1000Mbpslan4 DOWN 0x00215AB004BC iexgbe 10GBASE-KRlan5 DOWN 0x00215AB004BE iexgbe 10GBASE-KRlan0 UP 0x001F29F29092 igelan 1000Mbpslan1 UP 0x001F29F29093 igelan 1000Mbpslan6 UP 0x001B78290818 iether 1000Mb/slan7 UP 0x001B78290819 iether 1000Mb/slan3 UP 0x001F29F2908D igelan 1000Mbpslan900 DOWN 0x000000000000 hp_apa hp_apalan901 DOWN 0x000000000000 hp_apa hp_apalan902 DOWN 0x000000000000 hp_apa hp_apalan903 DOWN 0x000000000000 hp_apa hp_apalan904 DOWN 0x000000000000 hp_apa hp_apalan8 UP 0x984BE12F3598 iocxgbe 10GBASE-KRlan9 UP 0x984BE12F359C iocxgbe 10GBASE-KRlan10 UP 0x984BE12F3599 iocxgbe 10GBASE-KRlan11 UP 0x984BE12F359D iocxgbe 10GBASE-KRlan12 UP 0x984BE12F359A iocxgbe 10GBASE-KRlan13 UP 0x984BE12F359E iocxgbe 10GBASE-KRlan14 UP 0x984BE12F359B iocxgbe 10GBASE-KRlan15 UP 0x984BE12F359F iocxgbe 10GBASE-KR

The MAC address is a unique 48-bit identifier used when configuring the system. The MACaddress labelled on each card refers to LAN port A or 1 (on a multi-port card). Add 1 (hex)to obtain the MAC address for each additional port.Multi-function devices include a unique MAC address for each function configured by HP-UX.For information about how MAC addresses are assigned for cards, see the appropriate cardinstallation guide at the following website:www.hp.com/go/hpux-iocards-11iv3-docsFor information about how MAC addresses are assigned in a blade enclosure, see the HPVirtual Connect for c-Class BladeSystem Setup and Installation Guide at the following location:http://www.hp.com/go/bladesystem/documentation (select the Installation tab)

lanscan command: PPA number, H/W pathThe lanscan command displays the hardware path and the PPA number, in addition to theMAC address (station address). In the following example taken from the same system as thepreceding nwmgr command example, the line highlighted in bold shows the hardware path0/4/0/0/0/0, the MAC address 0x984BE12F3598, the interface lan8 and snap8, andthe PPA number 8.

SRVR06 /> lanscanHardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#0/2/2/0 0x001F29F2908C 2 UP lan2 snap2 1 ETHER Yes 1190/3/0/0/0/0 0x00215AB004BC 4 UP lan4 snap4 2 ETHER Yes 1190/3/0/0/0/1 0x00215AB004BE 5 UP lan5 snap5 3 ETHER Yes 1190/1/1/0 0x001F29F29092 0 UP lan0 snap0 10 ETHER Yes 1190/1/1/1 0x001F29F29093 1 UP lan1 snap1 11 ETHER Yes 1190/5/0/0/0/0 0x001B78290818 6 UP lan6 snap6 14 ETHER Yes 1190/5/0/0/0/1 0x001B78290819 7 UP lan7 snap7 15 ETHER Yes 1190/2/2/1 0x001F29F2908D 3 UP lan3 snap3 16 ETHER Yes 119LinkAgg0 0x000000000000 900 DOWN lan900 snap900 18 ETHER Yes 119LinkAgg1 0x000000000000 901 DOWN lan901 snap901 19 ETHER Yes 119LinkAgg2 0x000000000000 902 DOWN lan902 snap902 20 ETHER Yes 119LinkAgg3 0x000000000000 903 DOWN lan903 snap903 21 ETHER Yes 119LinkAgg4 0x000000000000 904 DOWN lan904 snap904 22 ETHER Yes 1190/4/0/0/0/0 0x984BE12F3598 8 UP lan8 snap8 148 ETHER Yes 1190/4/0/0/0/1 0x984BE12F359C 9 UP lan9 snap9 149 ETHER Yes 1190/4/0/0/0/2 0x984BE12F3599 10 UP lan10 snap10 150 ETHER Yes 119

2.3 Verifying the Ethernet LAN installation 17

0/4/0/0/0/3 0x984BE12F359D 11 UP lan11 snap11 151 ETHER Yes 1190/4/0/0/0/4 0x984BE12F359A 12 UP lan12 snap12 152 ETHER Yes 1190/4/0/0/0/5 0x984BE12F359E 13 UP lan13 snap13 153 ETHER Yes 1190/4/0/0/0/6 0x984BE12F359B 14 UP lan14 snap14 154 ETHER Yes 1190/4/0/0/0/7 0x984BE12F359F 15 UP lan15 snap15 155 ETHER Yes 119

The PPA number is the unique number assigned to each physical device. As shown in thislanscan display, a single hardware device may have multiple namePPA identifiers, wherethe name indicates the encapsulation method, and multiple encapsulation methods could besupported by the device. In this example, each device supports Ethernet encapsulation, asdesignated by the name lan, and Subnetwork Access Protocol (SNAP) encapsulation,designated by snap.

ioscan command: device descriptionThe ioscan command displays the hardware path and device description of all reportablehardware found on the system. In the following abbreviated example, the lan8 interface(which you can identify by the hardware path 0/4/0/0/0/0 that was revealed in thepreceding lanscan example) is shown to be for an NC552m dual-port 10 Gigabit Ethernetadapter.

TBLA06 /> ioscanH/W Path Class Description===========================================================...0/4 ba Local Bus Adapter0/4/0/0 ba PCItoPCI Bridge0/4/0/0/0 slot PCI Slot0/4/0/0/0/0 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/1 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/2 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/3 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/4 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/5 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/6 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter0/4/0/0/0/7 lan HP NC552m 2p 10GbE BL-c Mezzanine Adapter...

• To verify link-level connectivity with a remote system, enter, where destination_MAC is theremote system's MAC address and ppa is the PPA number of the remote system device:nwmgr --diag -A dest=destination_MAC -c lanppa

NOTE: when you use nwmgr --diag to check connectivity, ensure that the remote systemis on the same subnet and is an HP-UX-based system.

• To verify IP-level connectivity with a remote system, enter:ping Remote_IP_Address

andnetstat -in

When you use netstat -in, the displayed values Ipkts and Opkts should beincrementing.

• Installation is complete when you have successfully run nwmgr --diag -Adest=destination_MAC-c lanppa, ping, and netstat.To set up communication between the local IP network and remote IP networks, configure agateway using the route option under the SMH Network Services Configuration screen, oruse the route command to put the new route into effect on the system as follows:/usr/sbin/route add default router_ip_address 1

• Optionally, if you want to verify that the system recognizes the LAN driver for each installedcard, enter:

18 Installing HP-UX driver software and verifying connectivity

ioscan —fknC lan

The following is an example of ioscan output for each port of an AT111A CNA card:ioscan -kfnC lanClass I H/W Path Driver S/W State H/W Type Description==========================================================================lan 6 40/0/0/2/0/0/0 iocxgbe CLAIMED INTERFACE HP AT111-60001 10Gb PCIe 2-port FlexFabric (NIC) Adapterlan 7 40/0/0/2/0/0/1 iocxgbe CLAIMED INTERFACE HP AT111-60001 10Gb PCIe 2-port FlexFabric (NIC) Adapter

The third column represents the hardware path of the slot in which the adapter is installed.This path will be different for each installed adapter port. The path that has “0” as the lastdigit indicates the first port on the card (on the AT11A, the first port is labelled as port 1; onsome cards, such as the AT094A, the first port is labeled as LAN-A).In this example, an iocxgbe driver is installed on both ports. In a multiport card, all portsshould display as CLAIMED. To determine whether the latest version of a driver is installed,see the instructions in Section 2.1 (page 15).For a card installed in a server blade enclosure with a Flex-10 interconnect module, the ioscan-fknC lan output might be similar to the following example. In this example, an NC532mdual-port card is installed in Mezzanine Slot #1 of a BL860c “B” model system. The NC532mI/O paths are shown in the lines highlighted in bold. These lines display data for the card’seight physical functions (FlexNICs), where each of the card’s two ports has four physicalfunctions. (The first four lines of this display show the LOM ports of a BL860c server blade.)Class I H/W Path Driver S/W State H/W Type Description=====================================================================lan 0 0/1/1/0 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-inlan 1 0/1/1/1 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-inlan 2 0/2/2/0 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-inlan 3 0/2/2/1 igelan CLAIMED INTERFACE HP PCI-X 1000Mbps Dual-port Built-inlan 4 0/3/0/0/0/0 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 5 0/3/0/0/0/1 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 10 0/3/0/0/0/2 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 11 0/3/0/0/0/3 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 12 0/3/0/0/0/4 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 13 0/3/0/0/0/5 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 14 0/3/0/0/0/6 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 15 0/3/0/0/0/7 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapter

NOTE: In this example, the server profile was not configured to define multiple functions forthe mezzanine card. If two or more functions are listed in the server profile, then the card isconfigured in HP Virtual Connect Flex-10 mode; the ioscan display would show the text“FLEX-10” appended to the description for each function, as in the following example:lan 4 0/3/0/0/0/0 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapter

FLEX-10

Although not required, HP recommends listing at least two functions of each port in the serverprofile.

For a card installed in a server blade enclosure with a non-Flex-10 interconnect module orswitch, the output might be similar to the following, where an NC532m adapter is installedin Mezzanine Slot #1 in the second blade of a BL870c i2 or a BL890c i2 model system. TheNC532m I/O paths are shown in the lines highlighted in bold.Class I H/W Path Driver S/W State H/W Type Description========================================================================lan 0 1/0/0/3/0/0/0 iexgbe CLAIMED INTERFACE HP PCIe 2-p 10GbE Built-inlan 1 1/0/0/3/0/0/1 iexgbe CLAIMED INTERFACE HP PCIe 2-p 10GbE Built-inlan 2 1/0/0/4/0/0/0 iexgbe CLAIMED INTERFACE HP PCIe 2-p 10GbE Built-inlan 3 1/0/0/4/0/0/1 iexgbe CLAIMED INTERFACE HP PCIe 2-p 10GbE Built-inlan 34 1/0/0/5/0/0/0 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapterlan 35 1/0/0/5/0/0/1 iexgbe CLAIMED INTERFACE HP 454521-001 PCIe 2-p 10GbE Mezzanine Adapter

• Observe whether the ioscan output reports the following:lan 0/3/0/0/0/0 UNCLAIMED UNKNOWN ...

2.3 Verifying the Ethernet LAN installation 19

If this is reported, HP-UX detected the adapter but the driver is not recognized.

• If the correct driver is installed and the adapter is not listed in the ioscan output, contact HPfor assistance.

20 Installing HP-UX driver software and verifying connectivity

3 Setting and displaying driver Ethernet parametersThis chapter explains how to set Ethernet parameter values for drivers and how to display thecurrent values.

3.1 Tools for configuring Ethernet parametersOn HP-UX 11i v3, you can configure the cards using any of the following tools:• The ncweb graphical user interface for configuring the networking portion of the System

Management Homepage (SMH). On HP-UX 11i v3, SMH replaces the SAM tool. For furtherdetails on using SMH, see the HP-UX System Administrator’s Guide: Configuration Managementavailable at the following location:www.hp.com/go/hpux-systemadmin-docsFor more information about ncweb, see the ncweb(1m) manpage.

• nwmgr, a command to enter on the HP-UX command-line to administer all HP-UX LANparameters.For information, enter man nwmgr at the HP-UX command prompt. You can modify LANparameters and obtain information about features supported by a specific driver by referringto the nwmgr_driver(1m) manpage, where driver is the name of the driver (for example,nwmgr_iexgbe(1m)).To see the list of drivers (subsystems) supported by nwmgr on your HP-UX system, enter:nwmgr -h -S all

You can use the nwmgr command on LAN interfaces to:

◦ Display information of an interface

◦ Modify settings of an interface

◦ Reset the interface or its statistics

◦ Diagnose link connectivity

◦ Create and set configuration information for a component simultaneously

◦ Delete or erase components

3.2 Driver Ethernet parameters, configuration files, and startup scripts

Ethernet parametersEach driver interface has several attributes or parameters. Some are configurable while others areread-only. In general, each parameter can have a value in the running system (the parameter'scurrent value), another value in the driver's configuration file that stores data across boots andDLKM loads (the parameter's saved or persistent configuration value), and an HP-supplied value(the parameter's default value) that is applied by the driver after boot before the saved value isapplied.

Setting Ethernet parameters on the running system (using nwmgr command)When using the nwmgr command, you must set the parameter specific to a port or function,specifying the lanppa option, where ppa is the port or function number. For example, to set thespeed and duplexity for port 2 to 100 Mbit/s half-duplex, use this command:# nwmgr -s -A speed=100HD -c lan2

3.1 Tools for configuring Ethernet parameters 21

The ppa is obtained from the output of the lanscan command (for an example, see Section 2.3(page 16)).To set the parameter for multiple ports or functions, enter the nwmgr command multiple times,specifying a unique PPA each time.Parameter values that are set with the nwmgr command take effect immediately. They do not persistacross reboots unless the --sa option is specified with the command.

Setting Ethernet parameters in a configuration file — changes take effect atnext startupIn the driver's configuration file, you set the parameter value for a specific port by appending theport number in brackets to the parameter name, in the following format:parameter-name[ppa]

For example, to turn off transmit flow control on port 2 of an iocxgbe driver, specify theHP_IOCXGBE_TX_FLOW_CONTROL parameter as follows:HP_IOCXGBE_TX_FLOW_CONTROL[2]=OFF

The configuration file allows you to apply the value to all ports or functions on the device by omittingthe “[ppa]” string.Changes to the configuration file parameter values take effect the next reboot or when running thedriver's startup script. The configuration file defines and saves parameter values so that they persistacross reboots.

Using startup scripts to test configuration file settings and apply them to therunning systemThe startup script applies the configured values to the kernel during run time. The startup script isexecuted automatically after each reboot. You can also run a startup script manually by providingthe argument start, as in the following command example for an iexgbe driver's startup script:/sbin/rc2.d/S307hpiexgbe start

This startup feature allows you to experiment with the current values. When a desired configurationis achieved, you can then preserve it for posterity. HP recommends setting tested values permanentlyto persist across reboots.

Names and locations of driver configuration files and startup scriptsTable 6 (page 22) lists each driver's configuration file and startup script along with their locationon the system. Edit configuration files using an editor such as vi.

Table 6 Driver configuration files

Startup scriptConfiguration fileDriver

/sbin/rc2.d/S333hpbtlan/etc/rc.config.d/hpbtlanconfbtlan

/sbin/rc2.d/S308hpiether/etc/rc.config.d/hpietherconfiether

/sbin/rc2.d/S308hpgelan/etc/rc.config.d/hpgelanconfgelan

/sbin/rc2.d/S305hpigelan/etc/rc.config.d/hpigelanconfigelan

/sbin/rc2.d/S308hpixgbe/etc/rc.config.d/hpixgbeconfixgbe

/sbin/rc2.d/S308hpicxgbe/etc/rc.config.d/hpicxgbeconficxgbe

/sbin/rc2.d/S308hpiexgbe/etc/rc.config.d/hpiexgbeconfiexgbe

/sbin/rc2.d/S310hpiocxgbe/etc/rc.config.d/hpiocxgbeconfiocxgbe

22 Setting and displaying driver Ethernet parameters

3.3 Displaying Ethernet parametersYou can use the nwmgr command to display Ethernet parameter settings. By default, the informationis displayed in human-readable form. You can also display the information in script-friendly parsableform by specifying the - -sc or - -script option. Output examples in this document showthe human-readable form.To display the default configuration for all parameters of a specific device port:1. Remove the device configuration file.2. Reboot the system.3. Use the following command to display the default settings for the port or function identified

by PPA (for example, for port 1, specify lan1):nwmgr -g -A all -c lanPPA

Use the following options to display parameter options:-g (or --get) Displays the system configuration information, component parameter

(attribute) information, and subsystem-specific information such asstatistics. (In nwmgr terminology, a subsystem is an interface driver,such as iexgbe or gelan.) You can use this option to display thecurrent (runtime), saved (across reboots), and default configuration.

-c (or --class) An option to limits the scope of the display to a specific class orobject, such as to a specific port (for example, -c lan2).

-A (or --attribute Displays the parameter or attribute associated with the specifiedtarget. For example, -A all displays information about allparameters, while -A speed displays information specifically aboutthe speed parameter.

3.3 Displaying Ethernet parameters 23

Example 1 Displaying the setting of all parameters for a specific device port

Use the following nwmgr command to display all Ethernet parameters for a specific device portor function, where ppa is the port or function number.nwmgr -g -A all -c lanppa

The following is an example of output from the command (for port 2, specified as lan2)lan2 current values: Link State = Up Speed = 1000 Mbps Full Duplex MTU = 1500 MAC Address = 0xb499ba6499ac Transmit Flow Control = On Receive Flow Control = On Transmit Checksum Offload = On Receive Checksum Offload = On Virtual MTU = 32160 TCP Segmentation Offload is now enabled. TX Interrupt Timer = 48 RX Interrupt Timer = 24 Number of Queues = 8 TCP Packet Reassembly in Driver = On

Example 2 Displaying the setting of a specific parameter on a device port

Use the following command to display information about a specific parameter (parameter) fora specific Ethernet device port or function (lanppa).nwmgr -g -A parameter -c lanppalan0 current values: Transmit Flow Control = On

For example, to display the speed setting for port lan2, specify the following command:nwmgr -g -A speed -c lanppa

Sample output:lan2 current values: Speed = 1000 Mbps Full Duplex

3.4 Displaying and setting the Ethernet MAC addressEthernet devices are factory-programmed with a unique Ethernet Station Address. This cannot bemodified. By default, this address is used as the MAC address assigned to the device, but you canchange the address by using the nwmgr or ncweb command.The default value is ON.

NOTE: Multi-function devices include a unique MAC address for each function configured byHP-UX.For information about how MAC addresses are assigned for cards, see the appropriate cardinstallation guide at the following website:

www.hp.com/go/hpux-iocards-11iv3-docsFor information about how MAC addresses are assigned in a blade enclosure, see the HP VirtualConnect for c-Class BladeSystem Setup and Installation Guide at the following location:http://www.hp.com/go/bladesystem/documentation (select the Installation tab)

24 Setting and displaying driver Ethernet parameters

Example 3 Displaying a device's MAC address

To display the MAC address setting, enter the following command, where ppa is the PPA numberof the device:nwmgr -g -A mac -c lanppa

The following is an example of the output:MAC address = 0x002634738529

Example 4 Setting a device's MAC address

HP recommends setting the MAC address permanently to persist across reboots. To do so, enterthe following nwmgr command with the --sa option, where MAC is the MAC address and ppaidentifies the device PPA number:nwmgr --sa -A mac=MAC -c lanppa

For example, the following command sets the MAC address of the device with PPA 1 (lan1) to0x002634738528:nwmgr --sa -A mac=0x002634738528 -c lan1

3.5 Displaying and setting parameters for link speed, duplexity, andautonegotiation

Gigabit 1000Base-T cardsGigabit Ethernet copper-based LAN cards (1000Base-T) cards operate at 10 or 100 Mbit/s ineither full- or half-duplex modes, and at 1000 Mbit/s only in full-duplex mode. Set the 1000Base-Tcard (drivers iether, gelan, and igelan) speed, duplex, and autonegotiation to be equivalentto that of the link partner. With autonegotiation off, you can force the speed to 10 or 100 Mbit/s,with full or half duplex. With igelan and iether cards, you can force the speed to 1000 Mbit/sif autonegotiation and full-duplex are enabled. With gelan cards, you cannot force the speed to1000 Mbit/s; you must enable autonegotiation and connect the card to a link partner that iscapable of running at 1000 Mbit/s and is itself set to autonegotiate. Half duplex mode is notsupported at 1000 Mbit/s. Table 7 (page 25) describes valid configurations for your card andon your switch or link partner.

Table 7 HP-UX 1000Base-T supported configurations and parameter settings

Resulting speedLink partnerCorresponding HP-UXparameter value

HP-UX 1000Base-T port

Highest common speed (HP-UX supports10/100/1000)

AutonegotiateAUTO_ONAutonegotiate

10 Mbit/s half duplex10 half-duplex (forexample, a 10Base-Thub)

10HD10 half-duplex

10 Mbit/s full duplex10 full-duplex10FD10 full-duplex

100 Mbit/s half duplex100 half-duplex100HD100 half-duplex

100 Mbit/s full duplex100 full-duplex100FD100 full-duplex

1000 Mbit/s full duplex1000 full-duplex1000FD1000 full-duplex

Table 8 (page 26) lists the configuration file and nwmgr parameters available to set speed, duplex,and autonegotiation states for Gigabit Ethernet cards. Valid speeds are indicated by digits, duplexityby either hd or fd, and autonegotiation as either auto_on or auto_off.

3.5 Displaying and setting parameters for link speed, duplexity, and autonegotiation 25

Table 8 1000Base-T parameters and valid values

DefaultValid valuesnwmgr parameterConfiguration fileparameter

Driver

auto_on10hd 10fd 100hd 100fdauto_on

speedHP_GELAN_SPEEDgelan

auto_on10hd 10fd 100hd 100fd1000fd auto_on

speedHP_IGELAN_SPEEDigelan

auto_on10hd 10fd 100hd 100fd1000fd auto_on

speedHP_IETHER_SPEEDiether

NOTE: Speeds below 1000 Mbit/s are allowed only if the MTU size is 1500 bytes or less (JumboFrames disabled, as described in Section 3.7 (page 29)).The 1000 Mbit/s FD speed is not supported with gelan devices.For more detail about configuration rules and exceptions, see your driver's nwmgr_driver(1m)manpage.

Gigabit 1000Base-SX cardsFor 1000Base-SX cards, the speed is fixed at 1000 Mbit/s in full-duplex mode. The only adjustablesetting is for autonegotiation. As shown in Table 9 (page 26), there is a specific configuration fileparameter for setting autonegotiation. The nwmgr command uses the speed parameter to setautonegotiation.

Table 9 1000Base-SX parameters and valid values

Defaultnwmgr parameter and validvalues

Configuration file parameter andvalid values

Driver

1000 Mbit/s,Full Duplex,

speedHP_GELAN_AUTONEGgelan

auto_off1 or ONAutonegotiationenabled

auto_on0 or OFF

auto_onspeedHP_IGELAN_AUTONEGigelan

auto_off1 or ONauto_on0 or OFF

auto_onspeedHP_IETHER_AUTONEGiether

auto_off1 or ONauto_on0 or OFF

10 Gigabit cardsAll 10 Gigabit Ethernet LAN cards operate at 10 Gbit/s in full-duplex mode. The speed is notsettable. Some 10 Gigabit Ethernet LAN cards support 1000Base-SX in addition to 10 Gbase-SX.To obtain the 1000 Mbit/s speed, the 1000Base-SX cards need to be connected to an InterconnectGigabit pass-thru module, for example.

26 Setting and displaying driver Ethernet parameters

Example 5 Displaying current speed and duplex setting

To display the current speed and duplex setting, use the following nwmgr command, where ppaidentifies the device by its PPA number.nwmgr -g -A speed -c lanppa

Sample output (port 2):lan2 current values: Speed = 1000 Mbps Full Duplex

Example 6 Setting the speed and duplex

HP recommends setting the speed and duplex options permanently so that they are saved acrossreboots; where possible, enable autonegotiation. To do so, edit the driver's configuration file toset the HP_driver_SPEED parameter, where driver is the name of the driver. For example, toset port 2 on the igelan driver to autonegotiation, specify the following in the /etc/rc.config.d/hpigelanconf configuration file:HP_IGELAN_SPEED[2]=AUTO_ON

To set all ports on an igelan device to autonegotiate and operate at 100 Mbits/s full-duplexmode, specify the following:HP_IGELAN_SPEED=100FD AUTO_ON

To set the speed, duplex, autonegotation immediately and permanently, use the nwmgr commandfor each port, specifying the --sa option, as in the following example:nwmgr --sa -A speed=100fd auto_on -c lanppa

3.6 Displaying and setting the receive and transmit flow control parametersMost drivers support receive and transmit flow control. Flow control allows NICs to use data flownegotiation and the sending and receiving of pause frames. When the NIC is overwhelmed bydata (such as when the NIC has too few buffers available to handle full-speed reception), it sendsa pause frame to the transmitting end to delay transmission until more data can be handled. If theNIC has no available buffers, it will discard frames and update counters. When receive flow controlparameter is enabled, the card receives and manages pause frames sent by the link partner. Fordrivers that support transmit flow control, when the transmit flow control parameter is enabled, thecard transmits and manages pause frames transmitted to the link partner. When flow control isdisabled, the card will silently discard these pause frames.

3.6.1 Flow control parametersAll drivers support receive flow control except btlan. Several drivers do not support transmit flowcontrol. Flow control parameter names, default values, and support varies from driver to driver.Table 10 (page 28) lists for each driver the configuration file parameter, nwmgr parameter, anddefaults for receive and transmit flow control. Possible values for each parameter are ON or OFF.

NOTE: The btlan driver does not support flow control in either direction.

3.6 Displaying and setting the receive and transmit flow control parameters 27

Table 10 Configuration file and nwmgr flow control parameters

Transmit flow control parameterReceive flow control parameter

Driver

Configuration fileConfiguration filenwmgrnwmgrDefaultDefault

Not supportediether HP_IETHER_FLOW_CONTROLrx_fctlON

Not supportedgelan HP_GELAN_FLOW_CONTROLrx_fctlON

Not supportedigelan HP_IGELAN_FLOW_CONTROLrx_fctlON

ixgbe HP_IXGBE_TX_FLOW_CONTROLHP_IXGBE_RX_FLOW_CONTROLtx_fctlrx_fctlONON1

icxgbe HP_ICXGBE_TX_FLOW_CONTROLHP_ICXGBE_RX_FLOW_CONTROLtx_fctlrx_fctlONON2

iexgbe HP_IEXGBE_TX_FLOW_CONTROLHP_IEXGBE_RX_FLOW_CONTROLtx_fctlrx_fctlONON with non-Flex-10; OFF with Flex-1043

iocxgbe HP_IOCXGBE_TX_FLOW_CONTROLHP_IOCXGBE_RX_FLOW_CONTROLtx_fctlrx_fctlONON

1 When configured, the driver automatically generates a pause frame when the amount of data in the receive queueexceeds the flow control threshold, which is defined by the configuration file HP_IXGBE_FLOW_CONTROL_THRESHparameter or the nwmgr command fctrl_thresh parameter. The threshold value is expressed as a percentage ofthe receive buffer size on the adapter. Values are 1 to 100.

2 When configured, the driver automatically generates a pause frame when the amount of data in the receive queueexceeds the flow control threshold, which is defined by the configuration file HP_ICXGBE_FLOW_CONTROL_WMARKSparameter or the nwmgr command fctrl_wmarks parameter. The threshold value is expressed as a percentage ofthe receive buffer size on the adapter. Values are 10 to 90.

3 For current versions of this driver, the receive flow control default is off in Flex-10 environments; in non-Flex-10 environments,receive flow control is turned off if Jumbo Frames are being used (MTU size greater than 1500). For more information,see the latest release of the 10GigEthr-02 (iexgbe) B.11.31 Release Notes.

4 In Flex-10 environments, the transmit flow control can be set to ON only. Prior to release B.11.31.1205 of 10GigEthr-02(iexgbe), the default value for all environments is OFF. For more information, see the appropriate version of the10GigEthr-02 (iexgbe) B.11.31 Release Notes.

3.6.2 Displaying current flow control settingsThe following examples show how to display current receive and transmit control settings.

28 Setting and displaying driver Ethernet parameters

Example 7 Displaying current receive flow control settings

To display the current receive flow control setting, use the following command, where ppa identifiesthe device by its PPA number. Sample output is shown.nwmg -g -A rx_fctrl -c lanppalan0 current values: Receive Flow Control = On

Example 8 Displaying current transmit flow control settings

To display the current transmit flow control setting, use the following command, where ppa identifiesthe device by its PPA number. Sample output is shown.nwmgr -g -A tx_fctrl -c lanppalan0 current values: Transmit Flow Control = On

3.6.3 Setting the flow control parameterThe following examples show how to set receive and transmit flow control.

NOTE: Certain versions of the 10GigEthr-02 (iexgbe) product and supported hardware imposelimitations on flow control and the use of Jumbo Frames. For details about flow control and JumboFrame support for your version of 10GigEthr-02, refer to the release notes for that version.

Example 9 Setting receive flow control

HP recommends setting receive flow control permanently to persist across reboots. To turn receiveflow control on or off permanently, edit the driver's configuration file to set the parameter value toON or OFF. For the name of the receive flow control parameter supported by your device, refer toTable 10 (page 28). For example, to set receive flow control for all ports on the iexgbe deviceto ON, specify the following:HP_IEXGBE_RX_FLOW_CONTROL=ON

Alternatively, use the nwmgr command to set receive flow control immediately and permanently,specifying the --sa option in the following format where ppa identifies the device PPA number:nwmgr --sa -A rx_fctrl= {on|off} -c lanppa

Example 10 Setting transmit flow control

HP recommends setting transmit flow control permanently to persist across reboots. To do so, editthe driver's configuration file to set the parameter value to ON or OFF. For the name of the transmitflow control parameter supported by your driver, refer to Table 10 (page 28).Alternatively, use the nwmgr command to set receive flow control immediately and permanently,specifying the --sa option in the following format, where ppa identifies the device PPA number:nwmgr --sa -A tx_fctrl= {on|off} -c lanppa

3.7 Displaying and setting maximum transmission unit (MTU) parameterand Jumbo Frames

Jumbo Frames are large, 9000-byte data frames that can provide more efficient andhigher-performance transmission. You enable Jumbo Frames by setting the maximum transmissionunit (MTU) size to 9000 bytes. Jumbo Frames are supported only when the link speed is configuredto 1000 Mbit/s or greater. For Gigabit and 10 Gigabit Ethernet, the acceptable MTU settingsdepend on which driver and which HP-UX release you are using. For a summary of the allowableMTU sizes for each Ethernet driver and release, see Table 11 (page 30).

3.7 Displaying and setting maximum transmission unit (MTU) parameter and Jumbo Frames 29

Table 11 Allowable MTU sizes for each HP-UX 11i v3 driver

Allowable MTU SizesDriver/bundle name

257 through 1500btlan (includedwith HP-UXinstallations)

257 through 1500, and 9000iether /IEther-00

1024 through 1500, and 9000gelan /GigEther-00

257 through 1500, and 9000igelan/GigEther-01

257 through 1500, and 9000ixgbe/10GigEthr-00

257 through 1500, and 9000icxgbe/10Gigethr-01

257 through 1500, and 9000iexgbe/10GigEthr-02

257 through 1500, and 9000iocxgbe/10GigEthr-03

3.7.1 Before enabling Jumbo FramesBefore Jumbo Frames are used between end stations, ensure the following with the nwmgr command:

• The end stations have the same maximum transmission unit (MTU) setting (this discussionassumes that the end stations do not have any routers or layer 3 switches between them)

• Intermediate stations such as switch ports in your LAN have an MTU equal to or greater thanthe end station’s MTU

NOTE: Certain versions of the 10GigEthr-02 (iexgbe) product and supported hardware imposelimitations on flow control and the use of Jumbo Frames. As of version B.11.31.1209, receive flowcontrol must be disabled when Jumbo Frames are used.For details about Jumbo Frame support for your version of 10GigEthr-02, refer to the release notesfor that version.The btlan driver does not support Jumbo Frames.

3.7.2 Displaying current MTU/Jumbo Frame settingsThe following example shows how to display the current setting for a device's MTU size.

30 Setting and displaying driver Ethernet parameters

Example 11 Displaying the current MTU size

Use the following nwmgr command, where ppa identifies the device by the PPA number:$nwmgr -g -A mtu -c lanppa

Sample output (port 2):lan2 current values: MTU = 1500

3.7.3 Setting MTU/Jumbo Frames

Example 12 Setting the MTU size

HP recommends setting the MTU size permanently to persist across reboots. To do so, edit thedriver's configuration file to set the HP_driver_MTU parameter, where driver is the name ofthe driver. For example, to set the MTU size for all ports on the icxgbe driver to 9000 (enablingJumbo Frames), specify the following in the /etc/rc.config.d/hpicxgbeconf configurationfile:HP_ICXGBE_MTU=9000

Alternatively, to set the parameter immediately and permanently, use the nwmgr command foreach port, specifying the --sa option, as in the following example:nwmgr --sa -A mtu=9000 -c lanppa

3.7.4 Verifying the MTU size changeVerify any MTU changes by using the netstat -rn command. If the MTU size has not changedas expected, enter the following commands:$ifconfig lanppa unplumb$ifconfig lanppa ip_address netmask netmask up

To check the current Ethernet frame size for your device, use the nwmgr command, as explainedin Section 3.7.2 (page 30).

3.8 Displaying and setting the multiple queue parameterMultiple queues allow network traffic streams to be distributed into queues associated with specificprocessor cores. This distributes the workload and prevents data traffic processing fromoverwhelming a single core. With some exceptions, you can set both multiple receive queues andmultiple transmit queues. Multiple queues are only supported by 10GbE drivers. All 10GbE driverssupport multiple receive queues; not all 10GbE drivers support multiple transmit queues. For moresupport information, see Table 4 (page 12).

3.8 Displaying and setting the multiple queue parameter 31

Example 13 Displaying current multiple queue parameter values

To determine the number of queues currently set for a specific device, enter the following command:nwmgr -g -A drv_mq -c lanppa

Example 14 Setting multiple queues

HP recommends setting multiple queue options permanently so they are saved across reboots.Edit the driver's configuration file to set the appropriate parameter value to the number of queuesto be used by the driver. The configuration file parameter name is HP_driver_MQ, such asHP_IEXGBE_MQ or HP_IOCXGBE_MQ.For example, in the icxgbe driver configuration file /etc/rc.config.d/hpicxgbeconf, setthe HP_ICXGBE_MQ parameter value to the number of queues to be used by the driver, such asin the following example:HP_ICXGBE_MQ=3

For drivers that support both multiple receive and transmit queues, the parameter sets the samenumber of queues for both receive and transmit.The maximum limits for transmit and receive queues vary from driver to driver. For all drivers thatsupport multiple queues, the default setting for the number of queues is 1 (meaning, multiple queuesis not enabled). For details about multiple queue parameter settings, refer to the appropriatenwmgr_driver(1m) manpage.Alternatively, you can use the nwmgr command with the --sa option to immediately andpermanently set the number of queues. The nwmgr multiple queues parameter is drv_mq. Use thecommand in the following format:nwmgr --sa -A drv_mq=number-of-queues -c lanppa

3.9 Displaying and setting the Checksum Offload (CKO) parameterThe Checksum Offload (CKO) enables the network adapter to compute the TCP checksum. Savingthe host from having to compute the checksum, this feature reduces CPU overhead. Most HP Ethernetdrivers allow you to set hardware TCP/UDP (IPv4) Checksum Offload (CKO) receive and transmitto OFF or ON. The ixgbe and icxgbe drivers also allow you to set multifragment checksumoffload.

32 Setting and displaying driver Ethernet parameters

Example 15 Displaying current CKO parameter values

To determine the current CKO settings, enter the nwmgr command in the following format:nwmgr -g -A all -c lanppa

Sample output (port 2):lan2 current values: Transmit Checksum Offload = On

Example 16 Setting CKO parameter values

The names of the configuration file parameters that set receive and transmit CKO vary from driverto driver. Table 12 (page 33) lists the configuration file CKO parameter name for each driver thatsupports the feature.

Table 12 Configuration file parameter name for setting TCP segment reassembly (supported driversonly)

CKO parameter nameDriver

gelan HP_GELAN_RECV_CKOHP_GELAN_SEND_CKO

igelan HP_IGELAN_RECV_CKOHP_IGELAN_SEND_CKO

iether HP_IETHER_RECV_CKOHP_IETHER_SEND_CKO

ixgbe HP_IXGBE_RX_CHECKSUM_OFFLOADHP_IXGBE_TX_CHECKSUM_OFFLOAD

icxgbe HP_ICXGBE_CKO_IPV4_RXHP_ICXGBE_CKO_IPV4_TX

iexgbe HP_IEXGBE_RX_CHECKSUM_OFFLOADHP_IEXGBE_TX_CHECKSUM_OFFLOAD

iocxgbe HP_IOCXGBE_RX_CHECKSUM_OFFLOADHP_IOCXGBE_TX_CHECKSUM_OFFLOAD

For example, to enable receive and transmit CKO for the iether driver, edit the configurationfile /etc/rc.config.d/hpietherconf to specify the parameters as follows:HP_IETHER_SEND_CKO=ONHP_IETHER_RECV_CKO=ON

Alternatively, use the nwmgr command with the --sa option to set CKO values across reboots.The parameters to set CKO are the same for all drivers: rx_cko for receive CKO and tx_ckofor transmit CKO. For example, use these commands to turn on receive and send CKO for thedevice and port identified by ppa:nwmgr --sa -A tx_cko=on -c lanppanwmgr -s -A rx_cko=on -c lanppa

For details about CKO parameter options, refer to the appropriate nwmgr_driver(1m) manpage.

3.9 Displaying and setting the Checksum Offload (CKO) parameter 33

Example 17 Setting UDP multifragment CKO for ixgbe drivers

The ixgbe driver supports UDP IPv4 multifragment checksum offload. The configuration parameterfor setting multifragment checksum offload is HP_IXGBE_UDP_MF_CHECKSUM_OFFLOAD. Thenwmgr parameter is udpmf_cko. To enable or disable the feature, set the parameter to ON orOFF. The receive and transmit CKO parameters must both be enabled.

Example 18 Setting TCP/UDP multifragment CKO for icxgbe drivers

The icxgbe driver supports TCP/UDP IPv4 multifragment checksum offload. You can set this featureindividually for receive and transmit. The icxgbe configuration file parameters areHP_ICXGBE_CKO_IPV4_MF_RX and HP_ICXGBE_CKO_IPV4_MF_TX. The nwmgr parametersfor receive and transmit multifragment CKO are rxmf_cko and txmf_cko, respectively. You canenable or disable the feature by setting parameters to ON or OFF. The corresponding receive andtransmit CKO parameters must also be enabled.

3.10 Displaying and setting the TCP segmentation offload (TSO)/VirtualMTU parameter

Transmit TCP segmentation offload (TSO) is a mechanism by which the host stack offloads certainportions of outbound TCP packet processing to the NIC, thereby reducing host CPU utilization.This functionality can significantly reduce the load on the host for certain applications that primarilytransmit large amounts of data from the system. Examples include web serving and file transferapplications. All HP drivers discussed in this document support TSO except btlan and gelan.How TSO WorksThe reduction in CPU utilization is achieved primarily by allowing the host to transmit large frames(frames larger than the link's MTU) to the NIC. The NIC subsequently segments the frames intosmaller, MTU-sized frames, before transmitting them on the wire. Thus instead of processing manysmall MTU-sized frames during transmit, the host sends fewer of the larger VMTU (Virtual MTU)sized frames, thereby increasing the efficiency of the data transfer in the host. The VMTU is typicallymuch larger than the link MTU; for example, on a typical Ethernet card, the link MTU is 1500 byteswhile a VMTU could be as large as 32 Kbytes.

NOTE: TSO is settable for TCP/IP IPv4 only. Not all applications benefit from the TSO mechanism.Only data intensive applications that transmit large data buffers using TCP over IPv4 are improved.Other types of applications will not significantly benefit from the TSO mechanism. Performanceimprovements vary depending upon the platform used.

34 Setting and displaying driver Ethernet parameters

Example 19 Displaying the current TSO setting

Use the nwmgr command in the following format to display the TSO capability of the link. Anoutput example follows.# nwmgr -g -A vmtu -c lanppaDriver/Hardware supports TCP Segmentation Offload. Current VMTU = 32160

Example 20 Setting the TSO capability for a link

TSO is enabled or disabled for a link by defining a VMTU parameter in the device configurationfile or by using the nwmgr command to modify the VMTU parameter.The configuration file parameter is in the format HP_driver_VMTU, such as HP_ICXGBE_VMTU.The nwmgr TSO parameter is vmtu. To enable TSO, set the VMTU parameter value to 32160. Todisable TSO, set the parameter to 0.

NOTE: Transmit CKO must be enabled (for information about setting CKO, see Section 3.9(page 32)).For the iether and igelan drivers, TSO is disabled by default. For the 10Gigabit drivers, TSOis enabled by default.

To set the parameter value to persist across reboots (recommended), edit the driver's configurationfile to specify the HP_driver_VMTU parameter value. For example, to enable TSO for all portson an iocxgbe driver device, specify the parameter as follows:HP_IOCXGBE_VMTU=32160

To use the nwmgr command to enable TSO immediately and permanently, use the --sa optionas in the following example:#nwmgr --sa -A vmtu=new_vmtu_value -c lanppa

Changes to the Output of Current CommandsIf you are using NetTL or tcpdump to trace outbound packets, you may see these differences:tracing outbound packets in the host will display large packets being transmitted on the link, whiletracing the packets on the wire or at the receiving end will display only packets that are less thanor equal to the link MTU size.

TSO Interaction with Other SoftwareTSO is supported on virtual LANs (VLANs). It is supported for all MTU values (that is, TSO issupported with Jumbo frames) and speed settings on the link. Both Ethernet and SNAP encapsulationsare supported.TSO is supported on link aggregations starting with the September 2004 version of the HP AutoPort Aggregation (APA) product. For further details, see the latest release notes for the HP APAproduct at the following location:http://www.hp.com/go/hpux-APA-docs

3.11 Displaying and setting the TCP segment reassembly parameterTCP segment reassembly (also known as TCP packet reassembly and Large Receive Offload)combines TCP segments of data and passes the large, combined packet to the upper layers of thenetwork stack in the receive path. This can lower CPU utilization. This feature is supported by10GbE drivers only.

3.11 Displaying and setting the TCP segment reassembly parameter 35

Example 21 Displaying current TCP segment reassembly parameter values

To determine the current TCP segment reassembly settings, enter the following command:nwmgr -g -A drv_pr -c lanppa

Example 22 Setting TCP segment reassembly

To set the TCP segment reassembly option permanently so that it is saved across reboots, edit thedriver's configuration file to set the appropriate parameter value to ON or OFF.The name of the configuration file parameter that sets TCP segment reassembly varies from driverto driver. (The nwmgr parameter is drv_pr for all supporting drivers. ) Table 13 (page 36) liststhe configuration file parameter name for each driver that supports the feature.

Table 13 Configuration file parameter name for setting TCP segment reassembly (supported driversonly)

Parameter nameDriver

HP_IXGBE_DRV_PRixgbe

HP_ICXGBE_LROicxgbe

HP_IEXGBE_SW_LROiexgbe

HP_IOCXGBE_DRV_PRiocxgbe

For example, to enable TCP segment reassembly for the iocxgbe driver, edit the configurationfile /etc/rc.config.d/hpiocxgbeconf to specify the parameter as follows:HP_IOCXGBE_DRV_PR=ON parameter.Alternatively, you can also use the nwmgr command with the --sa option to immediately andpermanently set TCP segment reassembly. Set the parameter drv_pr to ON or OFF. Specify thecommand in the following format:nwmgr --sa -A drv_pr={on|off} -c lanppa

TCP segment reassembly is not supported by the Gigabit drivers. For most drivers that support TCPsegment reassembly, the default is OFF. The default for the iocxgbe driver is ON. The default forthe iexgbe driver is ON as of B.11.31.1109; the default for earlier versions is OFF.

NOTE: To turn on TCP segment reassembly, the CKO receive (rx_cko, HP_driver_RECV_CKO)parameter must be set to ON, and Jumbo Frames must be disabled.

For details about TCP segment reassembly parameter settings, refer to the appropriatenwmgr_driver(1m) manpage.

3.12 Other parametersA variety of other parameters are available, many of which are device-specific. Table 14 (page 36)briefly describes some of these parameters. For details about these and other parameters, refer tothe appropriate nwmgr_driver(1m) manpage.

Table 14 Some other parameters that might be settable and are device-specific

Supporting driversDescriptionParameter

ixgbe (AD385 cards only)Enables or disables 4-tuple hash-basedsteering.

4-tuple

ixgbeFrame count for Interrupt coalescing,specified individually for receive andtransmit.

Coalescing frame count

36 Setting and displaying driver Ethernet parameters

Table 14 Some other parameters that might be settable and are device-specific (continued)

Supporting driversDescriptionParameter

ixgbe, icxgbeLink-utilization range limit for interruptcoalescing. 1

Coalescing range limit

ixgbe, icxgbe, iexgbe, iocxgbe,iether3,gelan, igelan4

Time interval between interrupts; themaximum time for the NIC to coalescebefore it raises an interrupt. For

Coalescing interrupt timer

Gigabit drivers, the parameter isknown as maximum receive coalesceticks or maximum send coalesce ticks.1, 2

iether, gelan, igelan, ixgbe,iexgbe,iocxgbe

Specifies the Ethernet MAC addressof the remote interface; only valid fordiagnose operation (nwmgr --diag).

Destination MAC address

ixgbeA feature that allows packets to besteered to different queues based on

Destination Port-based Steering (DPS)

the destination port number of thepacket. This feature can improveperformance with some workloads.

ixgbeEnable/disable round robin mode ofqueue assignment for DestinationPort-based Steering.

DPS PQM Round Robin

ixgbeEnable/disable periodic invalidationof Port-to-queue mapping table entriesfor Destination Port-based Steering.

DPS PQM Periodic Invalidation

ixgbeTimer value after which theport-to-queue mapping table entrieswill be invalidated.

DPS PQM Invalidation Timer

iether, gelan, igelanModifies the inbound packet ratethreshold below which the driver

Diagnostics threshold

internal diagnostic for hardware faultdetection will be enabled; for somedrivers, the threshold below whichCKO diagnostics are run. Thediagnostics will be activated when thepacket rate on the interface dropsbelow this threshold.

ietherModifies interrupt spacing. Can be setto enable automatic dynamic tuningin the driver.

Interrupt Throttle Mode (ITR mode)

iether3, gelan, igelanModifies the number of receive bufferdescriptors to send at one time; the

Maximum receive buffers

maximum number of receivedescriptors for the NIC to coalescebefore it raises an interrupt.

iether3,gelan, igelanModifies the number of receive bufferdescriptors to receive at one time.

Maximum send buffers

iether, gelan, igelan,ixgbe,iexgbe,iocxgbe

Specifies the packet size of each testframe; only valid for diagnoseoperation (nwmgr --diag).

Packet size

iether, gelan, igelan,iexgbe,iocxgbe

Station address of interface;configured through lanadmin.

Station address

ietherLimits the transmit buffer size.Transmit buffer size limit

3.12 Other parameters 37

1 The ixgbe and iocxgbe set the parameter individually for transmit and receive; the icxgbe sets a parameter thatapplies to both.

2 The iether, gelan, igelan, iexgbe, and iocxgbe drivers set interrupt timers individually for transmit and receive.3 Restrictions and recommendations concerning modification of this parameter exist for cards using the iether driver;

see Section 3.13 (page 38).4 The igelan driver only supports a timer for receive.

3.13 Unsupported parameters of iether driver on HP-UX 11iFor PCI and PCI-X LAN cards that use the iether driver, HP does not recommend changing thedefault values of the following four tunables. It has been found that certain combinations of thesetunables (other than the default settings) could result in card hangs.• send_max_bufs

• recv_max_bufs

• send_coal_ticks

• recv_coal_ticks

These tunables are not supported with PCI-E cards that use the iether driver.

38 Setting and displaying driver Ethernet parameters

4 TroubleshootingThis chapter provides flowcharts that will help diagnose Ethernet hardware and software problems.

4.1 Troubleshooting overviewAs with any troubleshooting process, a systematic approach is helpful. The following table andsubsequent flowcharts provide a logical sequence of steps to follow when troubleshooting.Using the diagnostic flowcharts:1. Identify whether the problem is with Ethernet or any of the connections to the switch, or if the

problem is in some other part of the network.2. Verify your assumptions.3. If the problem is limited to Ethernet software or hardware, use the diagnostic flowcharts in this

chapter to help identify and fix the problem. In addition, see the hardware troubleshootingsuggestions in Section 4.2 (page 39).

NOTE: To help ensure operation without degraded performance, ensure that both link partnersare set to autonegotiate; alternatively, if using manual settings, ensure that each side is set to thesame speed and duplexity.

If you cannot solve the problem on your own, call your HP representative. To help you communicatethe nature of the problem effectively, use the guidelines in Section 5.1.1 (page 56). The Ethernetproducts use diagnostic tools compatible with the HP LAN Link product.

4.2 Basic troubleshooting tipsThe following list provides some tips on troubleshooting common hardware problems. Refer to thisinformation when you are trying to identify Ethernet hardware problems.

• Check the network cables. Make sure the network cable connections are secure and that thecables are not damaged. If you find any connections that are loose, or cables that aredamaged, fix the problem and then see if your computer can communicate on the network.

• Check to be sure that configuration settings are correct. If you suspect that a card is faulty,do the following:

◦ Use a different cable

◦ Move the suspected card to another slot

◦ Check to be sure that your system has the correct driver version

◦ If the driver is the correct version, try re-installing it

◦ Reboot the system

• Verify that the device at the other end of the connecting cable is an Ethernet device, and thatit is receiving power.

• Check to be sure that the connecting cable is of the correct category and length.

• Check the Link LED on the LAN card bulkhead. If the Link LED is ON and there still is a fault,enter the dmesg command at the HP-UX command prompt and view the output on your screento see if any error messages exist.

4.1 Troubleshooting overview 39

Other possible causes of a fault condition could be:

• A defective cable

• A cable not connected to an active hub or switch

• A defective card

4.3 Diagnostic flowchartsTable 15 summarizes the types of network tests recommended in the diagnostic flowcharts.

Table 15 Diagnostic flowcharts

PurposeType of testChart

Checks that hardware, cables, and connectors between your system andcard are operational.

Cable and LED test1

Checks communication between link levels on source and target host usingnwmgr.

Link-level test2

Groups the ARP and ping tests at the network level (for the details of thesetests, see Figure 4 and Figure 5).

Network-level tests3

Verifies that an entry exists for the remote host in your system's ARP cache.ARP test4

Checks communication between network layers on the source and targethost.

ping test5

Checks communication between transport layers on source and target hostusing telnet and ftp sessions.

Transport-level test6

Checks general network connections through a gateway.Bridge/gateway loopbacktest

7

Verifies configuration of network interface on a host using ioscan, nwmgr,netfmt, nwmgr --diag, and ifconfig.

Configuration tests8

Verifies configuration of network interface on a host.ioscan and nwmgr tests9

Verifies configuration of network interface on a host.netfmt and nwmgr -r-c lanppa tests

10

Verifies configuration of network interface on a host.ifconfig test11

4.3.1 Flowchart 1: Cable and LED testUse the process in this flowchart to ensure that the hardware, cables and connectors between yoursystem and card are operational.

40 Troubleshooting

Figure 1 Flowchart 1: Cable and LED test

Cableand LED

test

Check cardinstallation, reset

and/or reseat card.

Doesdmesg/syslog show

error message?

YES

NOLink-level test

YES

NO

Link LED = OFFor

All speed LEDs = ON?

NO

All speed LEDs = OFFor

Link LED = Flashing?

Check for incorrect/faulty networkcable or connector. Ensure that settings

for switch and card are the same.

YES

Configurationtests

4.3.1.1 Flowchart 1 procedures

• Check the dmesg/syslog output and look for error messages pertaining to the driver. Also,check the nettl log messages. If there are errors, check the card installation and reset orreseat the card. The following log files are created by NetTL:

◦ nettl.LOG000

◦ nettl.LOG001

• Verify the status of the card’s LEDs. If the Link LED = OFF, check the card installation and resetand/or reseat the card. If a card’s LEDs are now displayed correctly, continue to the link-leveltest (“Flowchart 2: Link-level test” (page 42)).

• If Link LED = Flashing, check for an incorrect or faulty network cable or connector. Ensure thatyour switch is capable of the appropriate speed operation. Ensure that the switch (or immediatelink partner) and card are set to the same autonegotiation settings. Then, perform the

4.3 Diagnostic flowcharts 41

configuration tests (“Flowchart 8: Configuration tests” (page 49)). Otherwise, if the Link LEDis on, continue to the link-level test (“Flowchart 2: Link-level test” (page 42)).

NOTE: For details about LED behavior, see the installation guide for the I/O card.

4.3.2 Flowchart 2: Link-level testUse the process in this flowchart to check communications between link levels on the source andtarget host by using the following command:nwmgr --diag -A dest=destination_MAC-c lanppa

Figure 2 Flowchart 2: Link-level test

Link-leveltest

Enternwmgr --diag

toremote host.

Check remoteMAC address again or choose a different

remote host andre-enter nwmgr --diag

command.

Correct the linkaddress parameter.

nwmgr--diag

successful?

“Addresshas bad

format” or“Not an individualaddress”

errormessage?

nwmgr--diag

successful?

Network-leveltests

Configurationtests

Repeatlink-level

test

Network-leveltests

NO

NO

NO

YES

YES

YES

42 Troubleshooting

4.3.2.1 Flowchart 2 procedures

• Enter nwmgr --diag -A dest=destination_MAC-c lanppa using the remote host’sMAC address. If the nwmgr --diag result is successful, perform the network-level tests(“Flowchart 3: Network-level tests” (page 43)). Otherwise, note the error that was returned.

• If loopback failed and the error message returned was “Address has bad format” or “Not anindividual address”, correct the link level address with the proper station address format andvalue, and then repeat the link-level test.

• Otherwise, loopback failed because the remote host did not respond. Check the remote host’sMAC address or choose another remote host, and re-enter nwmgr --diag -Adest=destination_MAC-c lanppa. If nwmgr --diag is now successful, perform thenetwork-level tests (“Flowchart 3: Network-level tests” (page 43)). You may also want to callthe node manager of the remote host that did not respond (if this was the case). If nwmgr--diag fails, perform the configuration tests (“Flowchart 8: Configuration tests” (page 49)).

• Note that nwmgr --diag cannot be used to test connectivity between end stations if thosestations are separated by a gateway or router. To test connectivity between stations underthese circumstances, run the nwmgr --diag test between the router or gateway and eachof the end stations independently, then verify network level connectivity by using ping betweenthe end stations. If the end stations cannot communicate with each other, but they can eachcommunicate with the router or gateway, then verify the routing tables in the router or gateway.

4.3.3 Flowchart 3: Network-level testsUse the process in this flowchart to validate arp entries and remote host availability. This processalso uses ping to check communication between network layers on the source and target host(see Figure 4 and Figure 5).

Figure 3 Flowchart 3: Network-level tests

ARP test

Network-leveltests

pingtest

4.3.3.1 Flowchart 3 procedures

• Use the ARP test to validate arp entries and remote host availability (see Figure 4).

• Use the ping test to check communication between network layers on source and target host(see Figure 5)

4.3 Diagnostic flowcharts 43

4.3.4 Flowchart 4: ARP testUse the process in this flowchart to validate arp entries and remote host availability.

Figure 4 Flowchart 4: ARP test

NO

NO

Use ARP tocorrect and

complete theentry.

Enter ping remote-host2000 -n 1 command.

Bring upremote host.

ARPtest

Is remotehost entry

in ARPcache?

Remotehostup?

Is theARP entry

correct andcomplete?

Repeatpingtest

NO

YES

YES

YES

4.3.4.1 Flowchart 4 procedures

• Enter ping to the remote host’s IP address so that an ARP entry is added. Whether or notping is successful, proceed to the next step.

• Use arp to verify that an entry exists for the remote host in your system's ARP cache, byentering the arp hostname command.

• If there is no ARP entry for the remote host, check whether the remote host is up. If not, bringup the remote host and continue to the ping test (Figure 5).

• If the ARP entry is correct or complete, continue to the ping test. Otherwise, use arp to enterthe correct station address of the remote system and continue to the ping test (Figure 5).

4.3.5 Flowchart 5: ping testUse the process in Flowchart 5 to check communication between network layers on the source andtarget host.

44 Troubleshooting

Figure 5 Flowchart 5: ping test

pingtest

continuedin Figure

6

Successful?YES

NO

NO

NO

Enternetstat -in.

Are MTUs same onlocal and remote

hosts?

Set MTUs the sameon local and remote hosts

by enteringnwmgr -s -A mtu=size

-c lanppa.

Transport-leveltest

Is speedappropriate?

YES

YES

YES

NOUsingJumbo

Frames?

Enter pingremote-host 2000 command.

Set desired speed onlocal and remote hosts

by enteringnwmgr -s -A speed=value

-c lanppa command.

Validate network,remote host and

configurationsettings.

Repeatpingtest

Repeatpingtest

4.3.5.1 Flowchart 5 procedures

• Enter ping to the remote host. If ping is successful, perform the transport-level test (“Flowchart6: Transport-level test” (page 47)). For more information about this command, see the ping(1m)manpage.

• If ping is not successful, enter netstat -in to verify MTU size. Ensure that the MTU sizeis the same on both the local and remote hosts (9000 for Jumbo Frames and 1500 for standardframes) by entering nwmgr -s -A mtu=mtusize -c lanppa and repeat the ping test.Jumbo Frames are not supported in Fast Ethernet.

• If ping is still not successful and you are either (1) not using Jumbo Frames or (2) using JumboFrames with the correct speed setting, continue to the next flowchart (“Flowchart 5 ping test(continued) ” (page 46)) to validate the network, remote host, and configuration settings.

• If the link speed is not appropriate, set it with nwmgr -s -A speed=speed _value -clanppa and repeat the ping test.

4.3 Diagnostic flowcharts 45

4.3.6 Flowchart 5 ping test (continued)

Figure 6 Flowchart 5: ping test (continued)

YES

NO

YES

YES

NO

YES

NO

pingnot

successful

Networkunreachable

error?

Noresponse

from ping?

UsingJumbo

Frames?

Do switchesin the path

support JumboFrames?

NO

NO

YES

Unknownhost

error?

Correct BIND, YP,or/etc/hosts

configuration.

Reconfigurenetwork.

YES

NO

Noroute-to-host

error?

Call HP

Add routetable entry.

Repeatpingtest

Configurationtests

Cable andLED test

Repeat ping test

4.3.6.1 Flowchart 5 (continued) proceduresThe procedures in this part of the Flowchart are:

• If there is a network unreachable error, perform the configuration tests (“Flowchart 8:Configuration tests” (page 49)).

• If there is no response from ping, and you are using Jumbo Frames, verify that the switchesin the path support Jumbo Frames, making sure the path MTU is the same (9000 maximum)from the source host to the destination host. Otherwise, reconfigure the network path andrepeat the ping test. If you are not using Jumbo Frames, or the switches and path MTU arecorrectly set for Jumbo Frames (9000 bytes), perform the cable and LED test (“Flowchart 1:Cable and LED test” (page 40)).

• If you receive an unknown host error, add the missing host name and repeat the ping test.

• If you receive “error=SendTo: No route to host,” use routeto add a route table entry for themissing host and repeat the ping test. Otherwise, call your HP representative.

46 Troubleshooting

4.3.7 Flowchart 6: Transport-level testUse the process in this flowchart to check communications between transport layers on the sourceand target host.

Figure 7 Flowchart 6: Transport-level test

YES

Configure TCP.

Enter telnet toremote host.

Enter ftp toremote host.

Transport-leveltest

telnetsuccesful?

YESftpsuccessful?

NOIs TCP

configuredon local and

remotehosts?

NONetworkcongested?

NO

NO

YES

YES

Call HP

Stop

Call HP

Call HP

Repeattransport-level

test

4.3.7.1 Flowchart 6 procedures

• Enter telnet to a remote host. If the process is successful, stop.

• If the process is not successful, try to establish an ftp link to a remote host. Unlike telnet,ftp does not use a pseudoterminal (pty) driver on your system. This will determine if pty isthe cause of the telnet failure. If ftp is successful, call your HP representative to determinewhy you have a problem with pty.

• If ftp fails, check whether TCP is configured on both hosts by verifying the /etc/protocolsfile. Both telnet and ftp work at the transport layer and require TCP. If TCP is not configured,configure it now and repeat the transport-level test.

• If TCP is installed on both hosts, telnet to another host and use netstat to check for lostpackets. If the network is congested, you may need to reconfigure the network. If networkcongestion is not the cause of the problem, more detailed network diagnostics are required.In either case, call your HP representative for assistance.

4.3 Diagnostic flowcharts 47

4.3.8 Flowchart 7: Bridge/gateway loopback testUse the process in this flowchart to check the general network connections through a gateway .

Figure 8 Flowchart 7: Bridge/gateway loopback test

YES

Enter ping from aknown good host through

a gateway to anotherknown good host.

Examine gateway.

Configure interface up.

See non-HPdocumentation or if HP,

enter ifconfig on gateway.

Check route tableon problem hostand all hosts in

path and correctif necessary.

Bridge/gateway

test

Succesful?

YESNetworkinterface

up?

NO

NO

NO

Configuration tests

Repeatbridge/gateway

test

Network-leveltests

4.3.8.1 Flowchart 7 procedures

• Enter ping from a known good host through a gateway to another known good host. Thiswill test connectivity through the bridge/gateway level. If successful, run netstat -r andexamine the route table on the problem host and all hosts in the path. If necessary, correctthe routing table and perform the network-level tests (“Flowchart 3: Network-level tests”(page 43)).

• If ping fails, examine the gateway to see if it is an HP or non-HP product. If non-HP, seenetworking documentation for that product. If HP, enter ifconfig for all interfaces on gateway

48 Troubleshooting

or host (for more details on ifconfig, see configuration tests, “Flowchart 8: Configurationtests” (page 49)).

• If ifconfig does not show the UP parameter as output for the gateway, enter netstat -ito check the status of network interfaces. An asterisk (*) indicates that the interface is down.If the network interface is down, configure the interface up and repeat the bridge/gatewaytest. If all interfaces are up, perform the configuration tests (“Flowchart 8: Configuration tests”(page 49)) and test all interfaces on the gateway.

4.3.9 Flowchart 8: Configuration testsUse the process in this flowchart to verify configuration of a network interface on a host.

Figure 9 Flowchart 8: Configuration tests

netfmt andnwmgr -r -c lanppa

test

ioscan and nwmgr test

Configurationtests

ifconfigtest

4.3.9.1 Flowchart 8 procedureThis procedure verifies the configuration of a network interface on a host by using ioscan, nwmgr,netfmt, nwmgr -r -c lanppa, and ifconfig commands.

4.3.10 Flowchart 9: ioscan and nwmgr testsUse the process in this flowchart to verify the configuration of a network interface on a host.

4.3 Diagnostic flowcharts 49

Figure 10 Flowchart 9: ioscan and nwmgr tests

NO

NO

netfmt(logging)

andnwmgr -r

test

Call HP

IInstall driver usingswinstall and use kernelconfiguration commands

as needed.

Check cardinstallation, reset

and/or reseat card.

Repeatioscannwmgr

test

Cable andLED test

ioscanand

nwmgrtest

Is the cardclaimed by the

system, asshown byenteringioscan?

NO

NO

Repeatioscan

andnwmgr

test

Doesnwmgr showhardware UP

for yourinterface?

Doeswhat /stand/vmunix

/stand/current/mod/*display theLAN driver?

Doesdmesg/syslog

show errormessages

for theLAN driver?

YES

YES

YES

YES

4.3.10.1 Flowchart 9 procedures

• Use the ioscan command as follows:ioscan -kfd drivername

Verify that the output from ioscan shows that the card is “CLAIMED” by the system.

• If the card is claimed, enter the nwmgr command and check whether the hardware statedisplay shows UP. If so, perform the cable and LED test (“Flowchart 1: Cable and LED test”(page 40)). If not, continue to the logging function of the netfmt and nwmgr -r test(“Flowchart 10: netfmt and nwmgr -r -c lanppa tests” (page 51)).

• If the card is not claimed, enter the following command:what /stand/vmunix /stand/current/mod/* | grep drivername

In this command, drivername is the name of the driver that operates the card. Verify thatthe version is the same as the version documented in the driver release notes. Use the nameof the running kernel image file in place of /stand/vmunix, as appropriate.

50 Troubleshooting

• If the driver is displayed, check whether the dmesg/syslog output shows error messagespertaining to any of the following LAN drivers:

◦ btlan

◦ gelan

◦ iether

◦ igelan

◦ icxgbe

◦ iexgbe

◦ ixgbe

◦ iocxgbe

Also, check nettl log messages. If there are errors, check the card installation and reset orreseat the card, and repeat this test. Otherwise, call your HP representative for assistance.Note that NetTL creates the following log files:

◦ nettl.LOG000

◦ nettl.LOG001

• If the driver is not displayed, install it using swinstall and use the appropriate kernelconfiguration commands.

4.3.11 Flowchart 10: netfmt and nwmgr -r -c lanppa testsUse the process in this flowchart to verify the configuration of the network interface on a host.

4.3 Diagnostic flowcharts 51

Figure 11 Flowchart 10: netfmt and nwmgr -r -c lanppa tests

netfmt(logging)

andnwmgr -r

test

Resetcard once

more; if stillnot successful,

call HP.

Enter netfmt.Check causesand actions in

log output.

ifconfig testProblemsolved?

YES

Reset card.

Link-level testResetsuccessful?

NO

NO

NO

YES

4.3.11.1 Flowchart 10 procedures

• Enter netfmt and view the error and disaster log messages. For example, enter:netfmt -vf /var/adm/nettl.LOG000

To help find proper logs, use the time stamp. Ensure you are looking at Ethernet information.Note that the names of the NetTL log files are:

◦ nettl.LOG000

◦ nettl.LOG001

• If the problem is solved, continue to the ifconfig test (“Flowchart 11: ifconfig test” (page 53)).

• If the problem persists, run nwmgr -r -c lanppa to reset the card.

• If the reset is successful, perform the link-level test (“Flowchart 2: Link-level test” (page 42)).Otherwise, reset the card once more; if it is still not successful, call your HP representative forassistance.

52 Troubleshooting

4.3.12 Flowchart 11: ifconfig testUse the process in this flowchart to verify configuration of the network interface on a host.

Figure 12 Flowchart 11: ifconfig test

Enterifconfig interface

IP address netmasknetmask up command.Enter ifconfig interface

command.

Add network configfor card to

/etc/rc.config.d/netconf.

Correct problemaccording to

message received.

Correct ifconfigflag settings.

Repeat ifconfigtest

ifconfigsuccessful

?

ifconfig entry in/etc/rc.config.d/netconf

?

YES

NO Areflags

correct?

NO

NOYES

YES YES

Any errormessagesreturned?

YESNO

ifconfigTest

Call HP

Network-leveltests

4.3.12.1 Flowchart 11 procedures

• To ensure that the interface is enabled, enter ifconfig on the interface you want to configure.For example:ifconfig lan1 192.6.1.17 netmask 255.255.255.0 up

Next, to test and verify that the flag setting is UP and the correct IP address is displayed, enterifconfig interface. For example:ifconfig lan1<UP,BROADCAST,RUNNING,MULTICAST,CKO>

• If the IP and flags are correct, verify there is an entry for the card interface in /etc/rc.config.d/netconf. If so, perform the network-level tests (“Flowchart 3: Network-leveltests” (page 43)). Otherwise, add the correct interface parameters to

4.3 Diagnostic flowcharts 53

/etc/rc.config.d/netconf file and reboot. If the flags are incorrect, correct themwith ifconfig and repeat this test. Otherwise, if ifconfig is not successful and errormessages appear, correct them accordingly and repeat this test.

• If you cannot correct the errors, call your HP representative for assistance.

4.3.13 Network-level test for Jumbo FramesJumbo Frames only apply to Gigabit or 10 Gigabit Ethernet. If you are using Fast Ethernet cards,you may ignore this section.

4.3.13.1 Test procedureWithin a LAN (that is, not across a router), MTUs of all the end stations must be set equal to eachother, and greater than or equal to 1500. You can verify this using the nwmgr [-g] -A mtu-c lanppa administrative command on HP-UX systems. The MTU for bridges and layer 2 switchesin the LAN must be set to the MTU value of the end stations, or to a greater value. To test for JumboFrames, follow these steps:1. Ensure that the MTU of all end stations is greater than, or equal to, 1500.2. Check the IP level connectivity by using the ping command (ping(1m)) with a message size

greater than 1480. For example:ping 192.6.20.2 2000

3. If there is a response to the ping command, Jumbo Frames is configured correctly.

4.4 Ethernet-specific informationThis section provides references to information and useful tools for installing, configuring, andmaintaining Ethernet products.

4.4.1 Error messagesMany drivers come with an online message catalog that is used to report networking problems.You must use the nettl logging and tracing utility to display the probable cause and action fora message.

4.4.2 Logging messagesEthernet uses the nettl logging and tracing facility supplied with HP-UX. (For more information,refer to the nettl(1m) manpage.) You may access the logging and tracing utility using either thegraphical user interface (GUI) version or the command-line interface. The names of the log filesproduced by NetTL are:• nettl.LOG000

• nettl.LOG001

Features of the GUI version, which are now a part of your HP system, include:

• An interface that guides you through logging and tracing tasks

• An interface that allows you to create and format reports

• The capability to collect logging and tracing subsystem-specific information

• Report screens that are updated instantaneously with current logging and tracing informationby the subsystem

• Context-sensitive online helpTo access the GUI version of the logging and tracing utility, enter:$ nettladm

54 Troubleshooting

For information on using the GUI version, see the nettladm(1m) manpage . For information onusing the command-line interface, see the nettl(1m) manpage.Listed below are some example commands using the command-line interface.

• To examine the log file with cause and action descriptions, enter:$ netfmt -v -f /var/adm/nettl.LOG000 | more

The -v option enables the reporting of available cause and action descriptions for each logmessage. A sample log message using the -v option follows:***********Gigabit Ethernet LAN Networking*********** Timestamp : Mon Dec 3 PDT 2007 18:37:16.175754 Process ID : [ICS] Subsystem:GELAN User ID ( UID ) : -1 Log Class:DISASTER Device ID : 3 Path ID: 0 Connection ID : 0 Log Instance: 0

• To examine just the log messages in the log file, enter:$ netfmt -f /var/adm/nettl.LOG000

• To check network logging and tracing status, enter:$ nettl -status

• To start Ethernet tracing on the file /tmp/tracefile.TRC000, enter:$nettl -traceon all -entity iether -file /tmp/tracefile

or$nettl -traceon all -entity igelan -file /tmp/tracefile

or$ nettl -traceon all -entity gelan -file /tmp/tracefile

NOTE: The nettl command adds the .TRC000 postfix for you.

• To stop Ethernet tracing, enter:$ nettl -traceoff -entity iether

or$ nettl -traceoff -entity igelan

or$ nettl -traceoff -entity gelan

• To format the Ethernet trace file into the file /tmp/traceout, enter:$ netfmt -f /tmp/tracefile.TRC000 > /tmp/traceout

For more information on how to create a filter for trace formatting, see the netfmt(1m) manpage.

4.5 Contacting HP for problem supportFor information about contacting HP for technical support, see “Support and other resources”(page 56). In particular, for a list of information that you can provide your HP representative whenseeking technical support, see Section 5.1.1 (page 56).

4.5 Contacting HP for problem support 55

5 Support and other resourcesThis chapter explains how to contact HP to obtain support or provide feedback, and lists a varietyof resources. In addition, it provides a table describing conventions used in this document. Tocontact HP to provide documentation feedback, see Chapter 6 (page 61).

5.1 Contacting HPThis section describes how to contact HP for product support.

5.1.1 Contacting Your HP representative: what to provide for technical supportIf you have no service contract with HP, you may use the following procedure, but you will bebilled accordingly for time and materials.If you have a service contract with HP, document the problem as a Service Request (SR) and forwardit to your HP representative. Include the following information where applicable:

• A characterization of the problem. Describe the events leading up to and including the problem.Attempt to describe the source and symptoms of the problem.Your characterization should include: HP-UX commands; communication subsystem commands;job streams; result codes and messages; and data that can reproduce the problem. You shouldalso provide a network map with the host name, IP address and station address of each systemconnected with the HP system.Illustrate as clearly as possible the context of any message(s). Prepare copies of informationdisplayed at the system console and user terminal.

• The installed versions of the LAN drivers. To determine the driver version that is installed inyour server’s kernel, run the following command:what /stand/vmunix /stand/current/mod/* | grep drivername

where drivername is one of the following:

◦ btlan

◦ gelan

◦ iether

◦ igelan

◦ icxgbe

◦ iexgbe

◦ ixgbe

◦ iocxgbe

You can also run the swlist command and look for the LAN drivers listed above.

• The version of your HP-UX kernel. To determine the version of your kernel, enter the followingcommand:uname -r

• Prepare copies of the /etc/hosts, /etc/rc.config.d/hpietherconf (orhpigelanconf or hpgelanconf) and /etc/rc.config.d/netconf files.

• Run the dmesg command and record messages about the status of the card.

• Run the nwmgr -v command and record the output.

56 Support and other resources

• Run nwmgr -g to display all statistics on the interface and record the output.

• Record the troubleshooting flowchart number where you are unable to resolve the problem.

• Record all error messages and numbers that appear at the user terminal and the system console.

• Save all network log files:/var/adm/nettl.LOG000 and nettl.LOG001 (for HP-UX 11i and later)Make sure that the ERROR and DISASTER log classes are enabled when the log files arecollected.Prepare the formatted output and a copy of the log file for your HP representative to furtheranalyze.

• Prepare a listing of the HP-UX I/O configuration you are using for your HP representative tofurther analyze. Use theioscan(1m) command to help collect this information.

• Try to determine the general area within the software where you think the problem exists. Seethe appropriate reference manual and follow the guidelines on gathering information for thatproduct.

• Document your interim, or workaround, solution. The cause of the problem can sometimes befound by comparing the circumstances in which it occurs with the circumstances in which itdoes not occur.

• Create copies of any Internet or Ethernet link trace files that were active when the problemoccurred for your HP representative to further analyze.

• In the event of a system failure, a full memory dump must be taken. Use the HP-UX utility savea core dump. Send the output to your HP representative.

• Run the nwmgr -g command to collect card configuration and statistics. Examples:nwmgr -g -A all -c lanppa

nwmgr -g --st mib,subsys -c lanppa

nwmgr -g --st extmib -c lanppa

In these examples, ppa is the physical point of attachment of the card.

5.1.2 HP contact informationFor the name of the nearest HP authorized reseller:

• See the Contact HP worldwide (in English) webpage:http://www8.hp.com/us/en/hp-information/summary/ww-contact-us.html

For HP technical support:

• In the United States, see the Contact HP United States webpage:http://www8.hp.com/us/en/contact-hp/contact.html

• To contact HP by phone:

Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7days a week. For continuous quality improvement, calls may be recorded or monitored.

◦

◦ If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For moreinformation about Care Packs, refer to the HP website:http://www8.hp.com/us/en/services/it-services.html

◦ In other locations, see the Contact HP worldwide (in English) webpage:http://welcome.hp.com/country/us/en/wwcontact.html

5.1 Contacting HP 57

5.2 New and changed information in this editionThe information in this edition has been updated significantly to include:• More detailed information about Fast Ethernet and Gigabit Ethernet

• Information about 10 Gigabit Ethernet

• Information about HP-UX drivers and supported cards including supported features

• More extensive and accurate instructions for verifying the Ethernet LAN installation

• More information about displaying and setting HP-UX driver Ethernet parameters

• Update of flowchart graphics

5.3 Related information

5.3.1 DocumentationYou can find documentation for the products discussed in this guide at the following locations:

• Documentation for HP 10 Gigabit Ethernet cards can be found at:http://www.hp.com/go/10-gigabit-ethernet-docs

• Documentation for HP Gigabit Ethernet and 100Base-T cards can be found at:http://www.hp.com/go/gigabit-ethernet-100bt-cards-docs

• General index for HP-UX I/O products documentation:www.hp.com/go/hpux-iocards-docs

• HP-UX 11i v3 documentation:http://www.hp.com/go/hpux-core-docs (select HP-UX 11i v3)

• You can find other documentation from the Manuals page of the HP Business Support Centerwebsite:http://www.hp.com/support/manuals

5.3.2 HP-UX manual reference pages (manpages)While installing, configuring, or troubleshooting Ethernet, you may need to refer to any of thefollowing online manual reference pages (manpages) for useful HP-UX operating system or Ethernetcommands. To display a manpage, enter the following at the system prompt: man command name.For example, man arp.

• arp(1m): The arp command displays and modifies the Internet-to-station address mappingtables used by the Address Resolution Protocol.

• hosts(4): The hosts manpage describes the /etc/hosts database that contains a singleline entry for each host name entry and the corresponding IP address and aliases. This filecontains all addresses for local interfaces that ifconfig needs at boot time. This file canserve as a backup when the name server or Network Information Service is not working.

• ifconfig(1m): The ifconfig command assigns an address to a network interface andconfigures and displays network parameters.

• ioscan(1m): The ioscan command scans system hardware, usable I/O system devices, orkernel I/O system data structures as appropriate, and lists the results.

• netfmt(1m): The netfmt command formats common tracing and logging binary files.

• netstat(1): The netstat command provides network statistics and information about networkconnections.

58 Support and other resources

• nettl(1m): The nettl command logs network events and traces packets as they enter and exitthe Ethernet driver.

• nwmgr(1m): The nwmgr command reports the status of a card, and is also used for resettinga card (-r), configuring virtual LANs (VLANs), setting TCP segmentation offload (TSO) andother features, displaying information about cards that are successfully bound to the system,and verifying network connectivity through the data link layer (OSI Layer 2). The commandcan also be used to obtain 64-bit MIB statistics. Use the nwmgr command to configure andmanage the driver interface. Interfaces can also be configured using the web-basedmanagement tool HP-UX System Management Homepage (HP SMH).

• ping(1m): The ping command verifies network connectivity through the Network Layer (OSILayer 3) and reports the round-trip time of communications between the local and remotehosts.

• rad(1m): The rad command in HP-UX 11i performs OL* functions without any comprehensivechecks.

• route(1m): The route command adds and deletes entries to the network routing table.

• swinstall(1m): The swinstall command loads software filesets.

• netfmt(1m): The swverify command verifies the software installation.

• swlist(1m): The swlist command verifies the driver software installation.

• vlan(7): This manpage provides an overview of the VLAN technology.

5.3.3 Webpages with related informationInformation about most of the products discussed in this manual and free software can be obtainedfrom the following HP Software Depot webpage:https://h20392.www2.hp.com/portal/swdepot/displayProductsList.do?category=NSMFor more information about the HP-UX 11i operating system, including the latest update release,operating environments, layered products and solutions, technologies, and learning opportunities,see the HP-UX 11i website:http://www.hp.com/go/hpux

5.4 Typographic conventionsThis document uses the following typographical conventions:audit(5) An HP-UX manpage. In this example, audit is the name and 5 is the section in

the HP-UX Reference. On the Web and on the Instant Information CD, it maybe a hot link to the manpage itself. From the HP-UX command-line, you canenter man audit or man 5 audit to view the manpage. See man(1).

Book Title The title of a book. On the Web and on the Instant Information CD, it may bea hot link to the book itself.

KeyCap The name of a keyboard key. Note that Return and Enter both refer to the samekey.

Emphasis Text that is emphasized.Bold Text that is strongly emphasized, or defined use of an important word or phrase.term A term defined in the glossary. Click on the term to see the glossary definition.ComputerOut Text displayed by the computer.UserInput Commands and other text that you type.Command A command name or qualified command phrase.URL Web URL references, such as http://docs.hp.com.

5.4 Typographic conventions 59

Variable The name of a variable that you may replace in a command or function orinformation in a display that represents several possible values.

[ ] The contents are required in formats and command descriptions. If the contentsare a list separated by |, you must choose one of the items.

{ } The contents are optional in formats and command descriptions. If the contentsare a list separated by |, you may choose one of the items.

... The preceding element may be repeated an arbitrary number of times.| Separates items in a list of choices.

60 Support and other resources

6 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback(docsfeedback@hp.com). Include the document title and part number, version number, or the URLwhen submitting your feedback.

61

A Cabling requirementsThis appendix contains information about the cabling requirements for Ethernet cards.

A.1 ConnectorsThe connectors on HP’s Gigabit Ethernet and 10 Gigabit Ethernet cards adhere to appropriatestandards agreed upon by various standards bodies and are widely available. The 1000Base-SXport is compatible with the IEEE 802.3z standard and uses SC or LC connectors. The 1000Base-Tport is compatible with the IEEE 802.3ab standard and uses an RJ-45 connector.

A.2 CablingIncorrectly wired or installed cabling is the most common cause of communications problems forlocal area networks. HP recommends that you work with a qualified cable installer for assistancein your cabling requirements. Table B-1 summarizes the cabling requirements for the 1000Base-SXand 1000Base-T products.

Table 16 Cabling for 1000Base-SX and 1000Base-T

Operating DistanceModal BandwidthCable Description (850nm short-wavelaser)

2 to 500 meters (6.6 to 1640 ft)400 (MHz * km)50 micron multimode fiber (MMF) cable

2 to 550 meters (6.6 to 1804 ft)500 (MHz * km)

Up to 100 meters100 MHzCategory 5 or Category 5E unshieldedtwisted-pair (UTP)

A.2.1 Back-to-back connectionWhen running 1000Base-T back-to-back at either 10 or 100 Mbit/s, you must use a crossovercable configuration. At 1000 Mbit/s, you can use either a crossover or straight-through cable.

62 Cabling requirements

B Card statisticsThis appendix interprets the statistics displayed by the nwmgr command.

B.1 nwmgr displayThis page shows a sample of a nwmgr command display including all Extended MIB statistics. Thefollowing is an example of a nwmgr command that displays the Extended MIB statistics:nwmgr --stats extmib -c lanppa

The fields are defined in the following sections.*** lan0 Extended MIB statistics:Interface Name = lan0PPA Number = 0Description = lan0 HP PCI-X 1000Base-T Release B.11.31.01Interface Type = 1000Base-TMTU Size = 1500Speed = 100 MbpsStation Address = 0x0018FE28E4FDAdministration Status = UPOperation Status = UPLast Change = Sat Sep 29 10:30:56 2007Inbound Octets = 6481850892Inbound Unicast Packets = 507001Inbound Multicast Packets = 56384Inbound Broadcast Packets = 18603494Inbound Discards = 0Inbound Errors = 0Inbound Unknown Protocols = 2905838Outbound Octets = 45804959Outbound Unicast Packets = 493847Outbound Multicast Packets = 0Outbound Broadcast Packets = 9036Outbound Discards = 0Outbound Errors = 0Counter Discontinuity Time = Sat Sep 29 10:30:54 2007Physical Promiscuous Mode = FALSEPhysical Connector Present = TRUEInterface Alias = Link Up/Down Trap Enable = EnabledIndex = 1Alignment Errors = 0FCS Errors = 0Internal MAC Transmit Errors = 0Frame Too Long Errors = 0Internal MAC Receive Errors = 0Symbol Errors = 0Single Collision Frames = 0Multiple Collision Frames = 0SQE Test Errors = 0Deferred Transmissions = 0Late Collisions = 0Excessive Collisions = 0Carrier Sense Errors = 0Control Field Errors = 0Multicasts Accepted = 0Duplex Status = Full DuplexRate Control Ability = FALSERate Control Status = TRUECollision Count = 0Collision Frequency = 0

B.1 nwmgr display 63

*** lan0 subsystem-specific statistics:In Packet Error = 0Out Packet Error = 0Link Down Events = 0Loopback Packets = 0

NOTE: This example was the result of running the nwmgr command for a Gigabit Ethernet card.If the command is used on a Fast Ethernet card, the “PPA Number” entry in this listing would be“Network Management ID”. (If the command is used on a 10Gigabit ethernet, the “PPA Number”entry would be displayed as shown in this example.)

B.1.1 RFC 1213 MIB IIThe following list provides descriptions of the statistics fields in the nwmgr command display. Formore detailed information about the fields, see RFC 1213.Field DescriptionNetwork Management ID A unique ID assigned by the system for the network

management of each network interface.PPA Number A unique number assigned to each network interface.Description A textual string containing information about the interface.Type (value) The type of interface, distinguished according to the

physical/link protocols, immediately below the networklayer in the protocol stack.Gigabit Ethernet can have either an ethernet or IEEE 802.3value.10/100Base-TX can have either an ethernet-csmacd(6) oriso88023-csmacd(7) value.

MTU Size The size of the largest datagram which can be sent orreceived on the interface specified in octets. This value canbe 1500 or 9000.

Speed in bits per second The speed of the card — 1000 Mbit/s for 1000Base-SX.10, 100, or 1000 Mbit/s for 1000Base-T. 10 Mbit/s or100 Mbit/s for Fast Ethernet.

Station Address The interface address at the protocol layer immediatelybelow the network layer in the protocol stack. For interfacesthat do not have such an address, such as serial line, thisobject contains an octet string of zero length.

Administration Status (ifAdmin) Administration Status sets the status of the card. It may beset to one of these three values:

Table 17 Administration status (ifAdmin): Valid values

Allow card to pass packetsup(1)

card is inoperativedown(2)

card is in test modetesting(3)

NOTE: All drivers except gelan and btlan support theifAdmin parameter. However, with certain older versionsof HP-UX (prior to B.11.31.1109), the nwmgr commandmight not be able to modify the parameter unless the patchPHNE_41971 is installed. Either install the patch or updateyour HP-UX operating system.

64 Card statistics

Operation Status (ifOper) Operation Status reports the status of the card if ifAdminhas been set to up(1). If ifAdmin is set to down(2), thenifOper will also be down(2).

Table 18 Operation status (ifOper): Valid values

Ready to pass packetsup(1)

Not operative (card is down)down(2)

In test modetesting(3)

Last Change The value of SysUpTime at the time the interface entered itscurrent operational state. If the current state was enteredprior to the last reinitialization of the local networkmanagement subsystem, then this object contains a 0 value.

Inbound Octets The total number of octets received on the interface,including framing characters.

Inbound Unicast Packets The number of subnetwork-unicast packets delivered to ahigh-layer protocol.

Inbound Discards The number of inbound packets that were discarded eventhough no errors had been detected, preventing them frombeing delivered to a higher-layer protocol. One possiblereason for discarding such a packet could be out of receivebuffers.

Inbound Errors The number of inbound packets that contained errors,preventing them from being deliverable to a higher-layerprotocol.

Inbound Unknown Protocols The number of packets received through the interface thatwere discarded because of an unknown or unsupportedprotocol.

Outbound Octets The total number of octets transmitted out of the interface,including framing characters.

Outbound Unicast Packets The total number of packets that higher-level protocolsrequested be transmitted to a subnetwork-unicast address,including those that were discarded or not sent.

Outbound Discards The number of outbound packets that were discarded eventhough no errors had been detected to prevent them frombeing transmitted. One possible reason for discarding sucha packet could be out of transmit buffers.

Outbound Errors The number of outbound packets that could not betransmitted because of errors.

B.1.2 RFC 1284 Ethernet-like interface statisticsThe following list provides descriptions of the Ethernet-like statistics fields in the nwmgr(1m) commanddisplay:Field DescriptionIndex A value that uniquely identifies an interface to an 802.3

medium.Alignment Errors A count of frames received on a particular interface that are

not an integral number of octets in length and do not passthe FCS check.

FCS Errors A count of frames received on a particular interface that arean integral number of octets in length and do not pass theFCS check.

B.1 nwmgr display 65

Single Collision Frames A count of successfully transmitted frames on a particularinterface for which transmission is inhibited by exactly onecollision.

Multiple Collision Frames A count of successfully transmitted frames on a particularinterface for which transmission is inhibited by more thanone collision.

Deferred Transmissions A count of frames for which the first transmission attempt ona particular interface is delayed because the medium isbusy. The count represented by an instance of this objectdoes not include frames involved in collisions.

Late Collisions The number of times that a collision is detected on aparticular interface later than 512 bit-times into thetransmission of a packet.

Excessive Collisions A couple of frames for which transmission on a particularinterface fails due to excessive collisions or packets dropped.

Internal MAC Transmit Errors A count of frames for which transmission on a particularinterface fails due to an internal MAC sublayer transmiterror.

Carrier Sense Errors The number of times that the carrier sense condition waslost or never asserted when attempting to transmit a frameon a particular interface.

Frames Too Long A count of frames received on a particular interface thatexceed the maximum permitted frame size.

Internal MAC Receive Errors A count of frames for which reception on a particularinterface fails due to an internal MAC sublayer receive error.

B.2 Card statisticsThis section defines the card statistics that are output from the nwmgr command. The following isa sample card statistics output. An explanation of the statistics is in the following section.****** Driver Statistics ****** In Packet Error 0Out Packet Error 0Loopback packets 0Link down events 0

****** Host Command Statistics ******nicCmdsDelMCastAddr 0nicCmdsSetMACAddr 0nicCmdsSetMulticastMode 0micCmdsClearStats 0

****** NIC Events Statistics ******nicEventsFirmwareOperational 1nicEventsStatsUpdated 362765nicEventsLinkStateChanged 1nicEventsMCastListUpdated 1

****** Interface Statistics ******ifIndex 4ifType 6ifMtu 1514ifSpeed 1000000000ifAdminStatus 1ifOperStatus 1ifLastChange 12ifInDiscards 0ifInErrors 0ifInUnknownProtos 0

66 Card statistics

ifOutDiscards 0ifOutErrors 0ifOutQLen 0ifInOctets_low 26719576ifInOctets_high 0ifInUcastPkts_low 0ifInUcastPkts_high 0ifInMulticastPkts_low 0ifInMulticastPkts_high 0ifInBroadcastPkts_low 382146ifInBroadcastPkts_high 0ifOutOctets_low 0ifOutOctets_high 0ifOutUcastPkts_low 0ifOutUcastPkts_high 0ifOutMulticastPkts_low 0ifOutMulticastPkts_high 0ifOutBroadcastPkts_low 0ifOutBroadcastPkts_high 0

B.2.1 Explanation of card statisticsThe following list provides descriptions of the card statistics that are output from the nwmgrcommand:Field DescriptionDriver StatisticsIn Packet Error Number of inbound packets discarded because they were received

when the driver was not operational or the packet length was incorrect.Out Packet Error Number of outbound packets discarded because the driver was not

operational or the driver had insufficient resources (memory) to transmitthe packet.

Loopback packets Number of packets looped back to the upper layers by the driver.Link Down events Number of link down events, that is, cable disconnects processed by

the driver.Host Command StatisticsnicCmdsDelMCastAddr Number of times the driver has issued a command to the NIC

to delete a multicast MAC address.nicCmdsSetPromiscMode Number of times the NIC received a command to enable or

disable promiscuous mode.nicCmdsSetMACAddr Number of times the NIC received a command to set the current

MAC address.nicCmdsClearStats Number of times the NIC received a command to clear the card

statistics maintained by the card.NIC Events StatisticsnicEventsFirmwareOperational The number of events the driver has received from the NIC

indicating that the firmware on the NIC is in the operationalstate.

nicEventsStatsUpdated The number of times the NIC has updated the MIB interfacestatistics.

nicEventsLinkStateChanged The number of events the driver has processed indicatingthat the status of the link has changed.

nicEventsMCastListUpdated The number of times the NIC generated an event to reportthe addition or deletion of a multicast MAC address.

Interface StatisticsThese are the MIB statistics collected by the card as documented in RFC1066.

B.2 Card statistics 67

Glossary1000Base-SX A specific implementation of 1000 Mbit/s operating over two multimode fiber cables, as specified

in Standard IEEE 802.3z/D.50-1998.1000Base-T A specific implementation of 1000 Mbit/s operating over four-pair Cat-5 or Cat-5e UTP cables,

as specified in IEEE 802.3ab standards.2-tuple Defines a communicating local and remote Internet socket pair by the source and destination IP

addresses. For excample, TCP 2-tuple is used for TCP packet management and calculations; UDP2-tuple is used for UDP packet management and calculations.

4-tuple Defines a communicating local and remote Internet socket pair by the source and destination IPaddresses and port numbers. For example, TCP 4-tuple is used for TCP packet management andcalculations; UDP 4-tuple is used for UDP packet management and calculations.

802.1 IEEE 802.1 is a working group of the IEEE 802 project of the IEEE Standards Association. It isconcerned with 802 LAN/MAN architecture, internetworking among 802 LANs, MANs andother wide area networks, 802 Link Security, 802 overall network management, protocol layersabove the MAC and LLC layers.

802.1D 802.1D is the IEEE MAC Bridges standard that includes Bridging, Spanning Tree and others. Itis standardized by the IEEE 802.1 working group. It includes details specific to linking many ofthe other 802 projects including the widely deployed 802.3 (ethernet), 802.11 (Wi-Fi) and802.16 (WiMax) standards. VLANs (virtual LANs) are not part of 802.1D, but specified in802.1Q.

802.1p IEEE Standard supplement, now incorporated in IEEE 802.1D. Defines 8 priority levels for trafficclassification at the data link level and suggests how they might be used.

802.1Q IEEE Standard that specifies the architecture for VLAN tagging, association, and VLAN-capablebridges.

802.3 IEEE 802.3 is a working group and a collection of IEEE standards defining the physical mediaand the working characteristics of Ethernet. This is generally a local area network technologywith some wide area network applications. Physical connections are made between nodes andinfrastructure devices (hubs, switches, routers) by various types of copper or fiber cable. 802.3is a technology that supports the IEEE 802.1 network architecture.

802.3u-1995network

A 10- or 100- Mbit/s LAN, specified in the IEEE 802.3u-1995 Standard for LANs. It uses theCarrier Sense Multiple Access/Collision Detection (CSMA/CD) network access method to giveevery node equal access to the network.

Accelerated VirtualInput/Output(AVIO)

An I/O protocol that improves virtual I/O performance for network and storage devices usedwithin the Integrity VM (HPVM) environment. The protocol also enables support for a greaternumber of virtual I/O devices per guest.See also Direct Input Output (DIO).

adapter See card.alias Name of the interface that corresponds to a given Internet address on a system.autonegotiation A mechanism defined in IEEE 802.3u-1995 whereby devices sharing a link segment can exchange

data and automatically configure themselves to operate at the highest capability mode sharedbetween them. This is also used for link configuration per IEEE 802.3z and IEEE 802.3ab standardsof duplex and flow control configuration between two 1000Base-SX/T links.

card The adapter, most often in reference to the hardware or to a specific form factor (such as PCIemezzanine card). An I/O expansion card (also I/O adapter) is a printed circuit board that canbe inserted into an expansion slot of a computer motherboard or backplane to add networkfunctionality to a computer system through the expansion bus.

card instancenumber

A number that uniquely identifies a device within a class. A class of devices is a logical groupingof similar devices.

combination(combo) card

An Ethernet/Fibre Channel combo card is a PCIe device that can provide both Ethernet and FibreChannel connectivity, or a PCI-X device that provides both Ethernet and SCSI connectivity. Forexample, on some combo cards, HP-UX configures a card as four separate devices — a dual-portFC device and a dual-port Ethernet LAN device. The FC devices are connected to an FC fabric

68 Glossary

through two FC fiber connections on the card. The LAN devices are connected to an EthernetLAN through two NIC fiber connections on the card. The FC and LAN devices do not sharebandwidth on a common connection to the fabric or network.

ConvergedInfrastructure

HP Converged Infrastructure architecture, a set of associated services and partner offerings thatcreate a virtualized, on-demand data center. It integrates and virtualizes compute, storage,networking, and management resources based on several HP technologies, most notablyBladeSystem Matrix, FlexFabric, and Virtual Resource Pools.

converged networkadapter (CNA)

A computer I/O card that combines the functionality of a host bus adapter (HBA) with a networkinterface controller (NIC). In other words, it "converges" access to a storage area network anda local area network, respectively.

ConvergedNetworkIntegratedController (CNIC)

See Integrated FlexFabric adapter.

data link layer In the seven-layer OSI model of computer networking, the data link layer is layer 2. In TCP/IPreference model, it corresponds to, or is part of the link layer. The data link layer is the protocollayer that transfers data between adjacent network nodes in a wide area network or betweennodes on the same local area network segment. The data link layer provides the functional andprocedural means to transfer data between network entities and might provide the means todetect and possibly correct errors that may occur in the physical layer. Examples of data linkprotocols are Ethernet for local area networks (multi-node), the Point-to-Point Protocol (PPP), HDLCand ADCCP for point-to-point (dual-node) connections.The data link layer is concerned with local delivery of frames between devices on the same LAN.Data-link frames, as these protocol data units are called, do not cross the boundaries of a localnetwork. Inter-network routing and global addressing are higher layer functions, allowing data-linkprotocols to focus on local delivery, addressing, and media arbitration. In this way, the data linklayer is analogous to a neighborhood traffic cop; it endeavors to arbitrate between partiescontending for access to a medium.

destinationaddress

A field in the message packet format identifying the end nodes to which the packet is being sent.

DestinationPort-basedSteering (DPS)

A feature that allows packets to be steered to different queues based on the destination portnumber of the packet. This feature can improve performance with some workloads.

DHCP Dynamic Host Configuration Protocol. A network protocol that is used to configure network devicesso that they can communicate on an IP network.

Direct Input Output(DIO)

With HPVM, a networking feature that allows virtual machines to directly control I/O devices,minimizing device emulation overhead incurred with AVIO. Provides near-native I/O functionality,manageability, and performance with virtual machine workloads.

DLPI Data Link Provider Interface. An industry-standard definition for message communications toSTREAMS-based network interface drivers. HP-UX DLPI serves as a Layer 2 (Data Link Layer) ofan OSI architecture. DLPI serves as an interface between LAN device drivers and DLPI users. DLPIis intended for use by experienced network users. For more information, see the HP-UX dlpi(7)

DPS See Destination Port-based Steering (DPS).Ethernet A 10 Mbit/s LAN, developed by Digital Equipment Corporation, Intel and Xerox Corporation,

upon which the IEEE 802.3 network is based.Ethernet partners Two Ethernet devices that are connected by an Ethernet cable (CAT5 or Fiber). For example, two

Ethernet cards connected directly to each other by a cable, or an Ethernet card connected to anEthernet hub or switch.

Fast Ethernet A commonly used name applied to 100Base-T.Fibre Channel (FC) A network technology used for storage networking.Fibre Channel overEthernet (FCoE)

An encapsulation of Fibre Channel frames over Ethernet networks that is independent of theEthernet forwarding schemes and integrates with existing Fibre Channel networks and managementsoftware. Computers connect to FCoE through CNAs.

69

Flex-10 An HP Virtual Connect technology that lets you replace multiple lower-bandwidth physical NICports with a single Flex-10 port. Each 10GbE adapter port is divided into up to four individualFlexNICs with bandwidth allocation in 100Mb/s increments to the maximum 10Gb/s per adapterport. Flex-10 reduces management requirements, the number of NICs and interconnect modulesneeded, and power and operational costs.See also FlexFabric.

FlexFabric Part of the HP FlexNetwork architecture portfolio, FlexFabric is a highly-scalable data center fabricarchitecture of an HP Converged Infrastructure. HP FlexFabric creates a common, wired-once,virtual I/O network that consolidates Ethernet and storage networks onto a single fabric.Virtual Connect FlexFabric adapters broaden Flex-10 capabilities by providing a way to convergenetwork and storage protocols on a 10 Gb port. Virtual Connect FlexFabric modules and FlexFabricadapters can (1) converge Ethernet, Fibre Channel, or accelerated iSCSI traffic into a single 10Gb data stream, (2) partition a 10 Gb adapter port into four physical functions with adjustablebandwidth per physical function, and (3) preserve routing information for all data types.See also Flex-10.

FlexNIC Provided by HP Flex-10 and HP FlexFabric adapters, an abstraction of a portion of a VirtualConnect 10GbE connection that is presented to the operating system as a standard NIC with itsown driver instance. The 10GbE link is partitioned into several smaller bandwidth FlexNics. EachFlexNIC has a unique MAC address and supports key benefits of integrated switching, includingport aggregation, failover and VLAN tagging. Use of HP Flex-NICs with Virtual Connectinterconnect modules can reduce the required hardware by consolidating all the NIC connectionsonto two 10 Gb ports. It provides virtual machine applications a greater number of networkconnections per server without increasing network complexity or reducing server resources.See also FlexFabric.

full-duplex mode A mode of media utilization whereby data can flow in both directions simultaneously across themultiple wire pairs of a physical link. While full-duplex operation is not defined per se in the IEEE802.3u-1995 specification, the specification does define a mechanism for this mode to beautonegotiated between devices on each end of a link. Full-duplex mode is typically found onswitches.

function A PCIe function. Each function can be configured by HP-UX as a single device: an FCoE deviceor a LAN device. HP-UX can configure a dual-ported CNA with as many as 8 PCIe functions (upto four per port) in a Flex-10 environment. As many as two of these functions can be FCoE devices(one per port); the remainder are NIC or LAN devices (up to four per port).

Gbit/s Gigabits per second; also referred to as Gb/s.Gbyte/s Gigabytes per second; also referred to as GB/s.half-duplex mode The media utilization mode of IEEE 802.3u-1995 networks whereby data can flow in only one

direction at a time across the multiple wire pairs of a physical link.hardware path An identifier assigned by the system according to the physical location (slot) of the card in the

hardware backplane. On HP servers, the I/O subsystem identifies each La card by its hardwarepath.

host name Name of system on the network.hub A network interconnection device that allows multiple devices to share a single logical link segment.IEEE The Institute of Electrical and Electronics Engineers. A national association whose activities include

publishing standards applicable to various electronic technologies. The IEEE technical committeesare numbered and grouped by area.

IEEE 802.1 See 802.1.IEEE 802.1D See 802.1D.IEEE 802.1p See 802.1p.IEEE 802.1Q See 802.1Q.IEEE 802.3 See 802.3.IEEE 802.3u-1995network

See 802.3u-1995 network.

70 Glossary

IEEE 802.3u-1995network

The 802.3 committee that produced the standard for LAN networks.

IntegratedFlexFabric adapter

An I/O card built into the system board that supports both LAN and FCoE functionality on thesame ports. It supports LAN and FCoE or accelerated iSCSI connectivity concurrently withhigh-performance protocol offloads that optimize server efficiency and maximize servervirtualization ratios. Integrated FlexFabric adapters provide more functionality and intelligencethan do LOMs. The integrated FlexFabric adapter technology helps enable the HP ConvergedInfrastructure model and ubiquity of both 10GbE and network convergence. An IntegratedFlexFabric adapter. Also known as a Converged Network Controller (CNC), Converged NetworkIntegrated Controller (CNIC), or converged LOM.

Internet An internetwork, a global system of interconnected computer networks that use the standardInternet protocol suite to serve billions of users worldwide. A network of networks that consists ofmillions of private, public, academic, business, and government networks, of local to globalscope, that are linked by a broad array of electronic, wireless, and optical networkingtechnologies.

Internet address The network address of a computer node. This address identifies both which network the host ison and which host it is. For more information, see the HP-UX IP Address and Client ManagementAdministrator's Guide HP-UX 11i v2, HP-UX 11i v3 available at the following location (scrollthrough the User Guide section):www.hp.com/go/hpux-networking-docs-11iv3

interruptcoalescing

To avoid flooding the host system with too many interrupts, packets are collected and one singleinterrupt is generated for multiple packets instead of generating interrupts for every single packet.Adapters provide various degrees of control of interrupt coalescing behavior.

intranet A computer network that uses IP technology to share information, operating systems, or computingservices within an organization or corporation. Sometimes the term refers only to an organization’sinternal website, but may be a more extensive part of the organization’s information technologyinfrastructure and may consist of multiple LANs.

IP Internet Protocol. Data travels over an IP-based network in the form of packets.IP address See Internet address.iSCSI Internet SCSI. An IP-based storage networking standard for linking data storage facilities. Facilitates

data transfers over intranets and can manage storage over long distances. Can be used to transmitdata over LANs, WANs, or the Internet.See also SCSI.

Jumbo Frames Ethernet frames with more than 1500 bytes of payload or maximum transmission unit (MTU) size;generally, 9000 bytes. The size that optimizes bulk data transfers: larger amounts of data canbe sent with greater efficiency.

LAN See local area network (LAN).LAN onMotherboard(LOM)

A chip or chipset capable of network connections that has been embedded directly on themotherboard of a server. For example, server blades include LOMs that are dual-port 1 or 10Gigabit Ethernet interfaces.

LAN provider A software module that you can use to find and collect information about the Ethernet links on asystem. It is based on the CIM (Common Information Model) standard from the distributedmanagement task force (DMTF).

link level In the hierarchical structure of a primary or secondary station, the conceptual level of control ordata processing logic that controls the data link.

local area network(LAN)

A data communications system that allows a number of independent devices to communicatewith each other.

local network The network to which a node is directly attached.Major Number Unique value that identifies an individual hardware device.maximumtransmission unit(MTU)

Largest amount of data that can be transmitted through the interface. This value does not includethe LLC or MAC headers.

Mbit/s Megabits per second; also referred to as Mb/s.

71

Mbyte/s Megabytes per second; also referred to as MB/s.Media AccessControl (MAC)address

A unique identifier assigned to network interfaces for communications on the physical networksegment. MAC addresses are most often assigned by the manufacturer of a network interfacecard (NIC) and are stored in its hardware, the card's read-only memory, or some other firmwaremechanism. If assigned by the manufacturer, a MAC address usually encodes the manufacturer'sregistered identification number and may be referred to as the burned-in address. It may also beknown as an Ethernet hardware address (EHA), hardware address or physical address. A networknode may have multiple NICs and will then have one unique MAC address per NIC.

mezzanine card Also known as a daughterboard or daughtercard, plugs directly into the motherboard or anotherplug-in card to extend functionality. It usually fits on top of and parallel to the board or card itplugs into.See also , combination (combo) card, LAN on motherboard (LOM), standup card.

MIB Management information base. An SNMP data structure that specifies what data can be obtainedfrom or controlled in a device.

MTU See maximum transmission unit (MTU).network interface A communication path through which messages can be sent and received. A hardware network

interface has a hardware device associated with it, such as a LAN card. A software networkinterface does not include a hardware device, for example, the loopback interface. For every IPaddress instance, there must be one network interface configured.

network interfacecard (NIC)

A function or device that is configured as a network or LAN I/O device.

node Any point in a network where services are provided or communications channels areinterconnected. A node could be a workstation or a server processor.

Online Addition/Replacement and Deletion (OL*)The ability of a PCI-X I/O card to be added, replaced, or removed without the need to shut downor reboot the system.

packet A sequence of binary digits that is transmitted as a unit in a computer network. A packet usuallycontains control information plus data.

PCI-X Peripheral Component Interconnect-Extended or PCI-eXtended. An enhanced version of PCI bustechnology originally developed by IBM, HP and Compaq. PCI-X is a superset of PCI; PCI-X isbackward compatible with existing PCI cards. PCI-X cards can run in PCI slots though at theslower PCI speed. 64-bit PCI-X slots are longer than 32-bit PCI-X slots.

PCIe Peripheral Component Internet Express. An enhanced version of PCI bus technology that includesimprovements over PCI and PCI-X, including higher maximum bus throughput, lower I/O pincount and smaller physical footprint, better performance-scaling for bus devices, and more detailederror detection and reporting. May support hardware I/O virtualization.

physical point ofattachment (PPA)

A unique number assigned to each network interface.

PMTU Path MTUport The physical connection to the network. A NIC typically has two physical connections; this

configuration is often described as “dual-ported.”PPA See physical point of attachment (PPA).protocol A specification for coding messages exchanged between two communications processes.RJ-45 The name for the connector type used with UTP cabling.SCSI Small Computer System Interface. A set of standards for physically connecting and transferring

data between computers and peripheral devices such as printers, scanners, and disk drives. Anintelligent, peripheral, buffered, peer-to-peer interface that hides the complexity of the physicalformat. All devices can attach to the SCSI bus in a similar manner. The SCSI interface providesfaster data transmission rates than standard serial and parallel ports. In addition, many devicescan be attached to a single SCSI port, qualifying a SCSI as an I/O bus rather than merely aninterface.See also iSCSI.

72 Glossary

SNMP Simple Network Management Protocol. A widely used network monitoring and control protocol.It uses devices or software processes called SNMP agents to return information about networkdevices. The information is collected into a MIB (Management Information Base).

standup card A standup card plugs into a PCI slot (PCIe or PCI-X). It may be single-ported, dual-ported, orquad-ported, providing one, two, or four physical connections to the network.

subnet mask A 32-bit mask which, when AND'd with an Internet address, determines a subnetwork address.When the Internet address is AND'd with the subnet mask, the ones in the host portion of thesubnet mask will “overwrite” the corresponding bits of the host portion of the Internet address,resulting in the subnet address. For more information about subnet masks, see the HP-UX IP Addressand Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 available at thefollowing location (scroll through the User Guide section):www.hp.com/go/hpux-networking-docs-11iv3

subnetwork Small discrete physical networks connected by gateways that share the same network addressspace. For more information about subnetworks and subnet addressing, see the HP-UX IP Addressand Client Management Administrator's Guide HP-UX 11i v2, HP-UX 11i v3 available at thefollowing location (scroll through the User Guide section):www.hp.com/go/hpux-networking-docs-11iv3

switch A network interconnection device that allows multiple connected senders and receivers tocommunicate simultaneously in contrast to a hub (repeater) where only one device can send ata time. Some switches have fixed port speeds (10 or 100 Mbit/s) while others allow port speedsto be configured or autonegotiated.

TCP SegmentationOffload (TSO)

A mechanism by which the host stack offloads certain portions of outbound TCP packet processingto the network interface card (NIC) thereby reducing host CPU utilization.

topology The physical and logical geometry governing placement of nodes in a computer network. Also,the layout of the transmission medium for a network.

unshielded twistedpair (UTP)

A data cable type consisting of pairs of wires twisted together without an electrically shieldingjacket.

UTP See unshielded twisted pair (UTP).Virtual Connect HP Virtual Connect extends the benefits of virtualization beyond the server to the rest of the

infrastructure. Virtual Connect virtualizes server-to-network connections. It provisions LAN andSAN connectivity for BladeSystem server blades through administration of a Media Access Control(MAC) address and a World Wide Port Names (WWPN) address. This allows server administratorsto independently manage blade servers and their connectivity, maintaining high availabilityconnections and securely administering MAC addresses and WWPNs. With Virtual Connect, aserver profile holds the MAC addresses and WWPNs constant, so the server administrator caneasily apply the same networking profile to new hardware.See also Flex-10, FlexFabric.

Virtual LAN (VLAN) VLANs are a mechanism to determine which end stations should receive broadcast traffic, sinceit should not be sent arbitrarily to every connected user. Each packet transmitted by an end-stationis assigned to a VLAN. An end-station only receives all the multicast and broadcast traffic on theLANs to which it belongs, and an end-station receives unicast traffic addressed to it on the VLANto which it belongs.

World Wide PortNames (WWPN)address

A World Wide Name assigned to a port in a Fibre Channel fabric. Used on storage areanetworks, it performs a function equivalent to the MAC address in Ethernet protocol, as it issupposed to be a unique identifier in the network.

73

Index

Symbols10 Gigabit Ethernet

cards, 7drivers, 8, 13overview, 7

1000Base-SXcards, 7IEEE standards, 6

1000Base-SX Ethernet cardscabling requirements, 62

1000Base-Tcards, 6IEEE standards, 6

1000Base-T Ethernet cardscabling requirements, 62speed and duplexity settings, 25

4–tupledescribed, 10parameter, 36

AAccelerated Virtual Input/Output (AVIO)

described, 11driver support, 13

Address Resolution Protocol (ARP)function, 58testing, 43testing entries, 44

Administration Statusin nwmgr output, 64

Alignment Errors, 65APA see Auto Port Aggregation (APA)ARP see Address Resolution Protocol (ARP)Auto Port Aggregation (APA)

described, 11driver support, 13

Auto Port Aggregation (APA) failoverdescribed, 11driver support, 13

autonegotiationdisplaying and configuring, 25troubleshooting tips, 39

AVIO see Accelerated Virtual Input/Output (AVIO)

Bbridge/gateway loopback test, 48buffer

transmit size limit, 37buffers

maximum receive, 37maximum send, 37

Ccables, 62

testing, 39, 40

cardsdisplaying descriptions of, 16Extended MIB statistics, 63features supported, 13statistics displayed, 66supported features described, 9variety of, 8verifying installation, 16

Carrier Sense Errors, 66Checksum Offload (CKO)

described, 10displaying and configuring, 32driver support, 12multifragment, 12, 34

CKO see Checksum Offload (CKO)CNA see converged network adapter (CNA)coalescing see interrupt coalescingcombination (combo) card

described, 8configuration

cabling, 62verifying, 49

connectorsGigabit Ethernet, 62troubleshooting, 40

Converged Infrastructuredescribed, 9

converged network adapter (CNA)described, 9

CPU utilization and Gigabit Ethernet, 6crossover vs. straight-through cable configurations, 62

DDeferred Transmissions, 66destination MAC address

parameter, 37Destination Port-based Steering (DPS)

parameter, 37diagnostic flowcharts see troubleshootingdiagnostics threshold

parameter, 37DIO see direct I/O (DIO)direct I/O (DIO)

described, 11driver support, 13

DLKMdescribed, 11

documentationHP website, 59providing feedback on, 61

DPS see Destination Port-based Steering (DPS)drivers

10 Gigabit Ethernet, 8, 13card statistics, 67configuration files, 21

list of, 22

74 Index

determining latest version installed, 15Ethernet parameters

configuring, 21configuring overview, 21displaying, 21, 23unsupported (iether), 38utilities for configuring, 21

Fast Ethernet, 6, 8, 13features supported, 13Gigabit Ethernet, 7, 13installing and verifying, 15installing software, 15obtaining software, 15startup files

list of, 22startup scripts, 21supported features described, 9types of cards supported, 8verifying Ethernet LAN installation, 16

duplexitydisplaying and configuring, 25

Eerror messages

accessing, 54ping test, 46

Ethernet cardscabling requirements, 62Extended MIB statistics, 63statistics, 66

Ethernet LAN installationverifying, 16

Ethernet parameters see drivers, Ethernet parametersEthernet Station Address, 24Excessive Collisions, 66

FFast Ethernet

cards, 5drivers, 6, 8, 13overview, 5

FCoE see Fibre Channel over Ethernet (FCoE)FCS Errors, 65Fibre Channel over Ethernet (FCoE)

described, 9Flex-10

bandwidth allocation, 10described, 9driver support, 12functions

display of, 19FlexFabric

described, 9flow control

configuring, 29displaying and configuring, 27displaying current setting, 28driver support, 12parameters per driver, 27

flowcharts see troubleshootingFrames Too Long field, 66ftp session

transport-level testing, 47full-duplex mode

displaying and configuring, 25

Ggateway loopback test, 48Gigabit Ethernet

cards, 6drivers, 7, 13overview, 6

Gigabit Ethernet cardserror and logging messages, 54

Hhalf-duplex mode

displaying and configuring, 25hardware problems

troubleshooting, 39host command statistics, 67hosts

hosts command, 58network layers test, 44transport layers test, 47

HP Auto Port Aggregation (APA) see Auto PortAggregation (APA)

HP Converged Infrastructure see Converged InfrastructureHP Flex-10 see Flex-10HP FlexFabric see FlexFabricHP Serviceguard see ServiceguardHP-UX drivers see driversHP-UX Ethernet

manual reference pages, 58HP-UX LAN provider see LAN provider

IIEEE 802.1Q VLAN tagging and stripping

described, 10driver support, 12

ifconfig commandfunction, 58testing, 53

Inbound Discardsin nwmgr output, 65

Inbound Errorsin nwmgr output, 65

Inbound Octetsin nwmgr output, 65

Inbound Unicast Packetsin nwmgr output, 65

Inbound Unknown Protocolsin nwmgr output, 65

Index field, 65Interface

meaning in nwmgr output, 16interface statistics, 67Internal MAC Receive Errors, 66

75

Internal MAC Transmit Errors, 66interrupt coalescing

described, 11driver support, 13parameters, 36

interrupt migrationdescribed, 10driver support, 13

Interrupt Throttle Mode (ITR mode)parameter, 37

ioscan commanddisplaying card description, 16function, 58testing, 49

IP-level connectivityverifying, 18

IPv6described, 10driver support, 12

JJumbo Frames

configuration requirements, 30configuring, 31described, 10displaying and configuring, 29displaying current setting, 30driver support, 12Gigabit Ethernet features, 6testing, 54troubleshooting, 45, 46verifying change, 31

LLAN see Local Area Network (LAN)LAN on motherboard (LOM)

described, 8LAN provider

described, 11driver support, 13

lanscan commanddisplaying PPA number, 16

Last Changein nwmgr output, 65

Late Collisions, 66LEDs

testing, 39, 40link handling

described, 11driver support, 13

link speeddisplaying and configuring, 25

link-level connectivityverifying, 18

link-level test, 42Local Area Network (LAN)

interface status displays, 63logging, 54

syslog , 41

LOM see LAN on motherboard (LOM)loopback tests, 43, 48

MMAC address

description, 16destination, 37displaying, 16displaying and configuring, 24

manpages, 58maximum receive buffers

parameter, 37maximum send buffers

parameter, 37maximum transmission unit (MTU)

allowable sizes per driver, 30configuring, 31displaying and configuring, 29displaying current setting, 30Gigabit Ethernet, 6, 29Jumbo Frames testing, 54troubleshooting, 45verifying change, 31

mezzanine carddescribed, 8

MIB (SNMP) and driver statisticsdescribed, 12driver support, 13

MTU see maximum transmission unit (MTU)MTU Size

in nwmgr output, 64multi-function devices, 9multicast mode

described, 10driver support, 12

multifragment checksum offloadconfiguring, 34driver support, 12

Multiple Collision Frames, 66multiple queues

configuring, 32displaying and configuring, 31displaying current setting, 32

multiple receive queuesdescribed, 10driver support, 12

multiple transmit queuesdescribed, 10driver support, 12

Nncweb

configuring driver parameters, 21netfmt command, 51, 58netstat, 58nettl

tracing/logging driver support, 12, 13nettl log facility, 54

cable and LED tests, 41

76 Index

network, 6see also Local Area Network (LAN)troubleshooting, 43

network interface card (NIC), 67Network Management ID

in nwmgr output, 64network unreachable error

troubleshooting, 46NIC see network interface card (NIC)nwmgr command

configuring driver parameters, 21displaying driver parameters, 23displaying MAC address, 16Extended MIB card statistics, 63function, 59statistics displayed, 63, 66testing, 49, 51troubleshooting with, 42

OOLRAD see Online Addition, Replacement, and Deletion

(OL*)Online Addition, Replacement, and Deletion (OL*)

described, 11driver support, 13

online manual reference pages, 58Operation Status

in nwmgr output, 65Outbound Discards

in nwmgr output, 65Outbound Errors

in nwmgr output, 65Outbound Octets

in nwmgr output, 65Outbound Unicast Packets

in nwmgr output, 65

Ppacket size

parameter, 37pause frames, 27PCI Error handling

described, 11driver support, 13

PCI OLRADdescribed, 11driver support, 13

ping command, 59no response, 45, 46troubleshooting with, 43, 44

PPA numberdescribed, 18displaying, 16in nwmgr output, 64

promiscuous modedescribed, 10driver support, 12

Rrad command, 59receive buffers

parameter, 37receive flow control

configuring, 29displaying current setting, 29driver support, 12

receive queues, multiple see multiple receive queuesReceive Side Scaling (RSS)

described, 10driver support, 12

RFC 1213 MIB II nwmgr display, 64RFC 1284 Ethernet-like interface statistics, 65route command, 59route-to-host error

troubleshooting, 46RSS see Receive Side Scaling (RSS)

SServiceguard

described, 11driver support, 13

Single Collision Frames, 66SMH see System Management Homepage (SMH)speed

displaying and configuring, 25in nwmgr output, 64troubleshooting network problems, 45

standup carddescribed, 8

Station Addressin nwmgr output, 64

station addressparameter, 37

straight-through vs. crossover cable configurations, 62swinstall command, 59switch devices

troubleshooting connections, 42swlist command, 59swverify command, 59System Management Homepage (SMH)

configuring driver parameters, 21

TTCP 4–tuple

described, 10parameter, 36

TCP segment reassemblydescribed, 10displaying and configuring, 35driver support, 12setting values permanently, 36

TCP segmentation offload (TSO)changes to command output, 35configuring, 35described, 10displaying and configuring, 34displaying the current setting, 35

77

how it works, 34interaction with other software, 35

TCP/IP, 47technical support, 56telnet session

transport-level testing, 47transmit buffer size limit

parameter, 37transmit buffers

parameter, 37transmit flow control

configuring, 29displaying current setting, 29driver support, 12

transmit queues, multiple see multiple transmit queuestransport-level test, 47troubleshooting, 39

ARP test, 44basic steps, 39bridge/gateway loopback test, 48cable test, 39, 40communication between source and target host, 44configuration tests, 49customer support resources, 56examining syslog output, 41hardware problems, 39ifconfig test, 53ioscan and nwmgr tests, 49LED test, 40link-level test, 42netfmt and nwmgr tests, 51network-level tests, 43overview, 39ping test, 44summary of flowcharts and tests, 40switches, 42transport-level test, 47

TSO see TCP segmentation offload (TSO)Type (value) field

in nwmgr output, 64

UUDP 4–tuple

described, 10parameter, 36

unknown host errortroubleshooting, 46

VVirtual Connect

described, 9vPars

described, 11driver support, 13

Wwebsites

product manuals, 59

78 Index