Ethernet Support Guide HP-UX 11i v3 Abstract This document contains specific information that is intended for users of HP products.
© 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, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Contents 1 Overview..................................................................................................5 1.1 Fast Ethernet and cards........................................................................................................5 1.2 Gigabit Ethernet and cards ..................................................................................................6 1.3 10 Gigabit Ethernet and cards..............................................................................................
.3.8.1 Flowchart 7 procedures......................................................................................48 4.3.9 Flowchart 8: Configuration tests..................................................................................49 4.3.9.1 Flowchart 8 procedure........................................................................................49 4.3.10 Flowchart 9: ioscan and nwmgr tests..........................................................................49 4.3.10.
1 Overview This 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 troubleshoot them. 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 networking and has a knowledge of HP-UX operating system concepts, commands, and configuration.
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. For example, the btlan driver manages both 100Base-T and 100Base-FX interfaces. For more information about this driver and managing it, see the nwmgr_btlan(1m) manpage and “Setting and displaying driver Ethernet parameters” (page 21).
1000Base-SX cards support full-duplex point-to-point or back-to-back operations only (using switch-to-card or card-to-card connections). The cards do not support half-duplex and do not speed negotiate (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 mezzanine cards provide two or more Gigabit Ethernet ports on a single card.
HP-UX provides several drivers that manage 10 Gigabit Ethernet cards and interfaces. The drivers are shipped with software bundles. Each driver may support several cards. Table 2 (page 8) lists the HP-UX 10 Gigabit drivers, their associated bundle names, and the manpage where you can obtain more information. Some information about managing drivers is also included in “Setting and displaying driver Ethernet parameters” (page 21).
The network device may be a converged network adapter (CNA), also called a converged network interface controller (C-NIC). This is a computer input/output device that combines the functionality of 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 be configured by HP-UX as a number of LAN devices, depending on the system configuration.
Table 3 Description of features Feature Description Receive and transmit flow control Allows use of flow control negotiation and the sending and receiving of pause frames. For information about configuring flow control, see Section 3.6 (page 27). Transmit and receive Checksum Offload (CKO) The CKO option enables the network adapter to compute the TCP checksum on transmit and receive, saving the host from having to compute the checksum. This feature reduces CPU overhead.
Table 3 Description of features (continued) Feature Description Interrupt coalescing To avoid flooding the host system with too many interrupts, packets are collected so one single interrupt is generated for multiple packets. Some driver interfaces have attributes that allow you to configure the minimum time between interrupts. For 10Gigabit Ethernet drivers, see the nwmgr_driver(1m) manpage, where driver is the name of the driver.
Table 3 Description of features (continued) Feature Description MIB (SNMP) and driver Directs the data link service (DLS) provider to return 64-bit statistics. statistics nettl tracing/ logging 1 A tool for capturing network events or packets. Logging captures network activities such as state changes, errors, and connection establishment. Tracing captures, or takes a snapshot of, inbound and outbound packets going through the network, as well as loopback or header information.
Table 4 Feature support per driver (continued) Fast Ethernet Gigabit Ethernet 10 Gigabit Ethernet Feature btlan iether IEther-00 gelan igelan GigEther-00 GigEther-01 ixgbe icxgbe iexgbe iocxgbe 10GigEthr-00 10GigEthr-01 10GigEthr-02 10GigEthr-03 Interrupt migration Yes Yes Yes Yes Yes Yes Yes Yes Interrupt coalescing No Yes10 Yes Yes Yes Yes Yes Yes Link handling No Yes No Yes No No Yes Yes DLKM Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
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.
2 Installing HP-UX driver software and verifying connectivity This chapter describes how to obtain and install the latest software for an Ethernet card and how to verify connectivity. 2.1 Determining whether the latest version of the LAN driver is installed To determine whether you have the latest version of the LAN card driver on your server, follow these steps: 1.
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).
SRVR06 /> nwmgr Name/ Interface ClassInstance State ============== ========= lan2 UP lan4 DOWN lan5 DOWN lan0 UP lan1 UP lan6 UP lan7 UP lan3 UP lan900 DOWN lan901 DOWN lan902 DOWN lan903 DOWN lan904 DOWN lan8 UP lan9 UP lan10 UP lan11 UP lan12 UP lan13 UP lan14 UP lan15 UP Station Address ============== 0x001F29F2908C 0x00215AB004BC 0x00215AB004BE 0x001F29F29092 0x001F29F29093 0x001B78290818 0x001B78290819 0x001F29F2908D 0x000000000000 0x000000000000 0x000000000000 0x000000000000 0x000000000000 0x984BE12F
0/4/0/0/0/3 0/4/0/0/0/4 0/4/0/0/0/5 0/4/0/0/0/6 0/4/0/0/0/7 0x984BE12F359D 0x984BE12F359A 0x984BE12F359E 0x984BE12F359B 0x984BE12F359F 11 12 13 14 15 UP UP UP UP UP lan11 lan12 lan13 lan14 lan15 snap11 snap12 snap13 snap14 snap15 151 152 153 154 155 ETHER ETHER ETHER ETHER ETHER Yes Yes Yes Yes Yes 119 119 119 119 119 The PPA number is the unique number assigned to each physical device.
ioscan —fknC lan The following is an example of ioscan output for each port of an AT111A CNA card: ioscan -kfnC lan Class 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) Adapter lan 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 slo
If this is reported, HP-UX detected the adapter but the driver is not recognized. • 20 If the correct driver is installed and the adapter is not listed in the ioscan output, contact HP for assistance.
3 Setting and displaying driver Ethernet parameters This chapter explains how to set Ethernet parameter values for drivers and how to display the current values. 3.1 Tools for configuring Ethernet parameters On 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.
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 persist across reboots unless the --sa option is specified with the command.
3.3 Displaying Ethernet parameters You can use the nwmgr command to display Ethernet parameter settings. By default, the information is displayed in human-readable form. You can also display the information in script-friendly parsable form by specifying the - -sc or - -script option. Output examples in this document show the 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.
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 port or function, where ppa is the port or function number.
Example 3 Displaying a device's MAC address To display the MAC address setting, enter the following command, where ppa is the PPA number of 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.
Table 8 1000Base-T parameters and valid values Driver Configuration file parameter nwmgr parameter Valid values Default gelan HP_GELAN_SPEED speed 10hd 10fd 100hd 100fd auto_on auto_on igelan HP_IGELAN_SPEED speed 10hd 10fd 100hd 100fd 1000fd auto_on auto_on iether HP_IETHER_SPEED speed 10hd 10fd 100hd 100fd 1000fd auto_on auto_on NOTE: Speeds below 1000 Mbit/s are allowed only if the MTU size is 1500 bytes or less (Jumbo Frames disabled, as described in Section 3.7 (page 29)).
Example 5 Displaying current speed and duplex setting To display the current speed and duplex setting, use the following nwmgr command, where ppa identifies 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 across reboots; where possible, enable autonegotiation.
Table 10 Configuration file and nwmgr flow control parameters Receive flow control parameter Transmit flow control parameter Configuration file nwmgr Default Configuration file nwmgr Default iether HP_IETHER_FLOW_CONTROL rx_fctl ON Not supported gelan HP_GELAN_FLOW_CONTROL rx_fctl ON Not supported igelan HP_IGELAN_FLOW_CONTROL rx_fctl ON Not supported ixgbe HP_IXGBE_RX_FLOW_CONTROL rx_fctl ON HP_IXGBE_TX_FLOW_CONTROL tx_fctl ON Driver 1 icxgbe HP_ICXGBE_RX_FLOW_CONTROL rx_fctl ON HP_ICXG
Example 7 Displaying current receive flow control settings To display the current receive flow control setting, use the following command, where ppa identifies the device by its PPA number. Sample output is shown. nwmg -g -A rx_fctrl -c lanppa lan0 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 identifies the device by its PPA number. Sample output is shown.
Table 11 Allowable MTU sizes for each HP-UX 11i v3 driver Driver/bundle name Allowable MTU Sizes btlan (included with HP-UX installations) 257 through 1500 iether /IEther-00 257 through 1500, and 9000 gelan /GigEther-00 1024 through 1500, and 9000 igelan /GigEther-01 257 through 1500, and 9000 ixgbe /10GigEthr-00 257 through 1500, and 9000 icxgbe/10Gigethr-01 257 through 1500, and 9000 iexgbe /10GigEthr-02 257 through 1500, and 9000 iocxgbe /10GigEthr-03 257 through 1500, and 9000 3.7.
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 the driver's configuration file to set the HP_driver_MTU parameter, where driver is the name of the driver.
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 queues to be used by the driver.
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 driver to driver. Table 12 (page 33) lists the configuration file CKO parameter name for each driver that supports the feature.
Example 17 Setting UDP multifragment CKO for ixgbe drivers The ixgbe driver supports UDP IPv4 multifragment checksum offload. The configuration parameter for setting multifragment checksum offload is HP_IXGBE_UDP_MF_CHECKSUM_OFFLOAD. The nwmgr parameter is udpmf_cko. To enable or disable the feature, set the parameter to ON or OFF. The receive and transmit CKO parameters must both be enabled.
Example 19 Displaying the current TSO setting Use the nwmgr command in the following format to display the TSO capability of the link. An output example follows. # nwmgr -g -A vmtu -c lanppa Driver/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 configuration file or by using the nwmgr command to modify the VMTU parameter.
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 the driver's configuration file to set the appropriate parameter value to ON or OFF.
Table 14 Some other parameters that might be settable and are device-specific (continued) Parameter Description Supporting drivers Coalescing range limit Link-utilization range limit for interrupt ixgbe, icxgbe coalescing. 1 Coalescing interrupt timer Time interval between interrupts; the ixgbe, icxgbe, iexgbe, iocxgbe, maximum time for the NIC to coalesce iether3,gelan, igelan4 before it raises an interrupt.
1 2 3 4 The ixgbe and iocxgbe set the parameter individually for transmit and receive; the icxgbe sets a parameter that applies to both. The iether, gelan, igelan, iexgbe, and iocxgbe drivers set interrupt timers individually for transmit and receive. Restrictions and recommendations concerning modification of this parameter exist for cards using the iether driver; see Section 3.13 (page 38). The igelan driver only supports a timer for receive. 3.
4 Troubleshooting This chapter provides flowcharts that will help diagnose Ethernet hardware and software problems. 4.1 Troubleshooting overview As with any troubleshooting process, a systematic approach is helpful. The following table and subsequent 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.
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 flowcharts Table 15 summarizes the types of network tests recommended in the diagnostic flowcharts. Table 15 Diagnostic flowcharts Chart Type of test Purpose 1 Cable and LED test Checks that hardware, cables, and connectors between your system and card are operational.
Figure 1 Flowchart 1: Cable and LED test Cable and LED test Does dmesg/syslog show error message? YES Check card installation, reset and/or reseat card. NO Link LED = OFF or All speed LEDs = ON? YES NO All speed LEDs = OFF or Link LED = Flashing? NO Link-level test YES Check for incorrect/faulty network cable or connector. Ensure that settings for switch and card are the same. Configuration tests 4.3.1.
configuration tests (“Flowchart 8: Configuration tests” (page 49)). Otherwise, if the Link LED is 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.
4.3.2.1 Flowchart 2 procedures • Enter nwmgr --diag -A dest=destination_MAC-c lanppa using the remote host’s MAC 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.
4.3.4 Flowchart 4: ARP test Use the process in this flowchart to validate arp entries and remote host availability. Figure 4 Flowchart 4: ARP test ARP test Enter ping remote-host 2000 -n 1 command. Is remote host entry in ARP cache? NO Remote host up? YES NO YES Bring up remote host. Is the ARP entry correct and complete? NO Use ARP to correct and complete the entry. YES Repeat ping test 4.3.4.1 Flowchart 4 procedures • Enter ping to the remote host’s IP address so that an ARP entry is added.
Figure 5 Flowchart 5: ping test ping test Enter ping remote-host 2000 command. YES Successful? NO Transportlevel test NO Enter netstat -in. Are MTUs same on local and remote hosts? Repeat ping test YES Is speed appropriate? Set desired speed on local and remote hosts by entering nwmgr -s -A speed=value -c lanppa command. Repeat ping test NO Set MTUs the same on local and remote hosts by entering nwmgr -s -A mtu=size -c lanppa.
4.3.6 Flowchart 5 ping test (continued) Figure 6 Flowchart 5: ping test (continued) ping not successful Network unreachable error? YES Configuration tests NO YES No response from ping? Using Jumbo Frames? YES Do switches in the path support Jumbo Frames? YES NO Reconfigure network. Repeat ping test NO NO Cable and LED test Unknown host error? YES Correct BIND, YP, or/etc/hosts configuration. NO No route-to-host error? Repeat ping test YES Add route table entry. NO Call HP 4.3.6.
4.3.7 Flowchart 6: Transport-level test Use the process in this flowchart to check communications between transport layers on the source and target host. Figure 7 Flowchart 6: Transport-level test Transportlevel test Enter telnet to remote host. telnet succesful? YES Stop NO Enter ftp to remote host. ftp successful? YES Call HP NO Is TCP configured on local and remote hosts? NO Configure TCP. Repeat transport-level test YES Network congested? NO Call HP YES Call HP 4.3.7.
4.3.8 Flowchart 7: Bridge/gateway loopback test Use the process in this flowchart to check the general network connections through a gateway . Figure 8 Flowchart 7: Bridge/gateway loopback test Bridge/ gateway test Enter ping from a known good host through a gateway to another known good host. Succesful? YES Check route table on problem host and all hosts in path and correct if necessary. NO Networklevel tests Examine gateway. See non-HP documentation or if HP, enter ifconfig on gateway.
or host (for more details on ifconfig, see configuration tests, “Flowchart 8: Configuration tests” (page 49)). • If ifconfig does not show the UP parameter as output for the gateway, enter netstat -i to 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/gateway test.
Figure 10 Flowchart 9: ioscan and nwmgr tests ioscan and nwmgr test Is the card claimed by the system, as shown by entering ioscan? Does nwmgr show hardware UP for your interface? YES NO IInstall driver using swinstall and use kernel configuration commands as needed.
• If the driver is displayed, check whether the dmesg/syslog output shows error messages pertaining 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 or reseat the card, and repeat this test. Otherwise, call your HP representative for assistance. Note that NetTL creates the following log files: • ◦ nettl.LOG000 ◦ nettl.
Figure 11 Flowchart 10: netfmt and nwmgr -r -c lanppa tests netfmt (logging) and nwmgr -r test Enter netfmt. Check causes and actions in log output. Problem solved? YES ifconfig test NO Reset card. NO Reset successful? YES Link-level test NO Reset card once more; if still not successful, call HP. 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.
4.3.12 Flowchart 11: ifconfig test Use the process in this flowchart to verify configuration of the network interface on a host. Figure 12 Flowchart 11: ifconfig test ifconfig Test Enter ifconfig interface IP address netmask netmask up command. Enter ifconfig interface command. ifconfig successful ? NO NO Add network config for card to /etc/rc.config.d/netconf. NO Correct ifconfig flag settings. YES YES ifconfig entry in /etc/rc.config.
/etc/rc.config.d/netconf file and reboot. If the flags are incorrect, correct them with ifconfig and repeat this test. Otherwise, if ifconfig is not successful and error messages 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 Frames Jumbo Frames only apply to Gigabit or 10 Gigabit Ethernet. If you are using Fast Ethernet cards, you may ignore this section. 4.3.13.
For information on using the GUI version, see the nettladm(1m) manpage . For information on using 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 log message.
5 Support and other resources This chapter explains how to contact HP to obtain support or provide feedback, and lists a variety of resources. In addition, it provides a table describing conventions used in this document. To contact HP to provide documentation feedback, see Chapter 6 (page 61). 5.1 Contacting HP This section describes how to contact HP for product support. 5.1.
• 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 are collected.
5.
• nettl(1m): The nettl command logs network events and traces packets as they enter and exit the Ethernet driver. • nwmgr(1m): The nwmgr command reports the status of a card, and is also used for resetting a card (-r), configuring virtual LANs (VLANs), setting TCP segmentation offload (TSO) and other features, displaying information about cards that are successfully bound to the system, and verifying network connectivity through the data link layer (OSI Layer 2).
Variable The name of a variable that you may replace in a command or function or information in a display that represents several possible values. [ ] The contents are required in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items. { } The contents are optional in formats and command descriptions. If the contents are a list separated by |, you may choose one of the items. ...
6 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Cabling requirements This appendix contains information about the cabling requirements for Ethernet cards. A.1 Connectors The connectors on HP’s Gigabit Ethernet and 10 Gigabit Ethernet cards adhere to appropriate standards agreed upon by various standards bodies and are widely available. The 1000Base-SX port is compatible with the IEEE 802.3z standard and uses SC or LC connectors. The 1000Base-T port is compatible with the IEEE 802.3ab standard and uses an RJ-45 connector. A.
B Card statistics This appendix interprets the statistics displayed by the nwmgr command. B.1 nwmgr display This page shows a sample of a nwmgr command display including all Extended MIB statistics. The following 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 Interface Name = PPA Number = Description = B.11.31.
*** lan0 subsystem-specific statistics: In Packet Error = 0 Out Packet Error = 0 Link Down Events = 0 Loopback 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.
Operation Status (ifOper) Operation Status reports the status of the card if ifAdmin has been set to up(1). If ifAdmin is set to down(2), then ifOper will also be down(2).
Single Collision Frames Multiple Collision Frames Deferred Transmissions Late Collisions Excessive Collisions Internal MAC Transmit Errors Carrier Sense Errors Frames Too Long Internal MAC Receive Errors A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision.
ifOutDiscards ifOutErrors ifOutQLen ifInOctets_low ifInOctets_high ifInUcastPkts_low ifInUcastPkts_high ifInMulticastPkts_low ifInMulticastPkts_high ifInBroadcastPkts_low ifInBroadcastPkts_high ifOutOctets_low ifOutOctets_high ifOutUcastPkts_low ifOutUcastPkts_high ifOutMulticastPkts_low ifOutMulticastPkts_high ifOutBroadcastPkts_low ifOutBroadcastPkts_high 0 0 0 26719576 0 0 0 0 0 382146 0 0 0 0 0 0 0 0 0 B.2.
Glossary 1000Base-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.
through two FC fiber connections on the card. The LAN devices are connected to an Ethernet LAN through two NIC fiber connections on the card. The FC and LAN devices do not share bandwidth on a common connection to the fabric or network. Converged Infrastructure HP Converged Infrastructure architecture, a set of associated services and partner offerings that create a virtualized, on-demand data center.
Flex-10 An HP Virtual Connect technology that lets you replace multiple lower-bandwidth physical NIC ports with a single Flex-10 port. Each 10GbE adapter port is divided into up to four individual FlexNICs with bandwidth allocation in 100Mb/s increments to the maximum 10Gb/s per adapter port. Flex-10 reduces management requirements, the number of NICs and interconnect modules needed, and power and operational costs. See also FlexFabric.
IEEE 802.3u-1995 network The 802.3 committee that produced the standard for LAN networks. Integrated FlexFabric adapter An I/O card built into the system board that supports both LAN and FCoE functionality on the same ports. It supports LAN and FCoE or accelerated iSCSI connectivity concurrently with high-performance protocol offloads that optimize server efficiency and maximize server virtualization ratios. Integrated FlexFabric adapters provide more functionality and intelligence than do LOMs.
Mbyte/s Megabytes per second; also referred to as MB/s. Media Access Control (MAC) address A unique identifier assigned to network interfaces for communications on the physical network segment. MAC addresses are most often assigned by the manufacturer of a network interface card (NIC) and are stored in its hardware, the card's read-only memory, or some other firmware mechanism.
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 network devices. 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, or quad-ported, providing one, two, or four physical connections to the network.
Index Symbols 10 Gigabit Ethernet cards, 7 drivers, 8, 13 overview, 7 1000Base-SX cards, 7 IEEE standards, 6 1000Base-SX Ethernet cards cabling requirements, 62 1000Base-T cards, 6 IEEE standards, 6 1000Base-T Ethernet cards cabling requirements, 62 speed and duplexity settings, 25 4–tuple described, 10 parameter, 36 A Accelerated Virtual Input/Output (AVIO) described, 11 driver support, 13 Address Resolution Protocol (ARP) function, 58 testing, 43 testing entries, 44 Administration Status in nwmgr output,
determining latest version installed, 15 Ethernet parameters configuring, 21 configuring overview, 21 displaying, 21, 23 unsupported (iether), 38 utilities for configuring, 21 Fast Ethernet, 6, 8, 13 features supported, 13 Gigabit Ethernet, 7, 13 installing and verifying, 15 installing software, 15 obtaining software, 15 startup files list of, 22 startup scripts, 21 supported features described, 9 types of cards supported, 8 verifying Ethernet LAN installation, 16 duplexity displaying and configuring, 25 E
Internal MAC Transmit Errors, 66 interrupt coalescing described, 11 driver support, 13 parameters, 36 interrupt migration described, 10 driver support, 13 Interrupt Throttle Mode (ITR mode) parameter, 37 ioscan command displaying card description, 16 function, 58 testing, 49 IP-level connectivity verifying, 18 IPv6 described, 10 driver support, 12 J Jumbo Frames configuration requirements, 30 configuring, 31 described, 10 displaying and configuring, 29 displaying current setting, 30 driver support, 12 Giga
network, 6 see also Local Area Network (LAN) troubleshooting, 43 network interface card (NIC), 67 Network Management ID in nwmgr output, 64 network unreachable error troubleshooting, 46 NIC see network interface card (NIC) nwmgr command configuring driver parameters, 21 displaying driver parameters, 23 displaying MAC address, 16 Extended MIB card statistics, 63 function, 59 statistics displayed, 63, 66 testing, 49, 51 troubleshooting with, 42 R O S OLRAD see Online Addition, Replacement, and Deletion (O
how it works, 34 interaction with other software, 35 TCP/IP, 47 technical support, 56 telnet session transport-level testing, 47 transmit buffer size limit parameter, 37 transmit buffers parameter, 37 transmit flow control configuring, 29 displaying current setting, 29 driver support, 12 transmit queues, multiple see multiple transmit queues transport-level test, 47 troubleshooting, 39 ARP test, 44 basic steps, 39 bridge/gateway loopback test, 48 cable test, 39, 40 communication between source and target ho
