Professional Documents
Culture Documents
1303
Ethernet Driver Release Notes (Edition 2
update)
HP-UX 11i v3
Abstract
This document contains specific information that is intended for users of this HP product.
Document
Edition number
manufacturing part
number
5900-2658
Edition 2
March 2013
5900-2500
Edition 1
March 2013
1 10GigEthr-02 overview
The 10GigEthr-02 bundle contains the PCIe 10 Gigabit Ethernet iexgbe driver. This driver supports
the following 10 Gigabit Ethernet products and LOMs:
PCIe 10 Gigabit Standup Ethernet
adapters
BL860c i2
BL870c i2
BL890c i2
Integrity Superdome 2
NOTE: The HP-UX ioscan utility shows AM225A, AM232A and AM233A adapters all as
AM225A. This is because the only difference between the adapters is the type of SFP module
that is used. Since the adapters are functionally equivalent at the operating system level, ioscan
does not distinguish between them.
For more information about installing the supported PCIe 10 Gigabit Ethernet and mezzanine
adapters, see the following documents:
HP-UX and Windows OS Installation Guide for HP NC532m Dual Port Flex-10 10Gb Ethernet
Multifunction BL-c Adapter
1.1 Terminology
The following terms are used in this document:
Adapter
The whole card.
AVIO
Card
Device
DIO
Flex-10
1 10GigEthr-02 overview
Function
LOM
mezzanine adapter
NIC
PCIe
Port
The physical connection to the network. The NIC typically has two
physical connections; this configuration is often described as
dual-ported.
1.2 Features
The iexgbe driver is a PCIe 10 Gigabit Ethernet driver that can support the standup, mezzanine,
and LAN on motherboard (LOM) technologies for a variety of platforms. It supports the HP Virtual
Connect Flex-10 interface on server blade platforms. Before HP Virtual Connect was introduced,
only two interconnect choices were available for connecting server blades to a network
passthrough devices and switches. Passthrough devices are simple but require too many cumbersome
cables and create complexity. Blade switches reduce the number of cables but add more
management responsibilities for LAN and SAN administrators. In both cases, multiple people are
needed to perform very simple server tasks. Only HP offers the third choice HP Virtual Connect
which reduces cables without adding switches to manage and provides many other advantages.
For more information about HP Virtual Connect, see the following website:
http://h18004.www1.hp.com/products/blades/virtualconnect/index.html
Other notable features provided by the iexgbe driver include:
Transmit Checksum Offload (CKO) and TCP Segmentation Offload (TSO) for IPv4
Jumbo Frames
IPv6
Interrupt migration
Interrupt coalescing
Link handling
DLKM
HP Serviceguard
PCI OLRAD
vPars V6
nettl tracing/logging
HP Smart Update Manager (HP SUM) support for online updating of I/O adapter firmware
HP SUM is the SPP deployment tool. It can be used to perform online updates of the I/O
adapter firmware on Integrity server systems running HP-UX. The 10GigEthr-02 driver is now
compatible with HP SUM, allowing online update of the firmware on supported I/O adapters.
The nwmgr firmware update command displays appropriate advisory messages describing
the online update. For example:
$ nwmgr -s --hp -A fw_dwnld=firmware_file.frm -c lan12
Firmware file: firmware_file.frm
Firmware file loaded and validated successfully
Proceed with update (Y if so)? Y
Please do not interrupt until complete (approximately 2-3 minutes)
Downloading firmware image to flash ...
1. Only LACP mode is supported with APA aggregation with 10GbE links. APA aggregate mode is not supported with
server blades over Virtual Connect interconnects. Virtual Connect does not support aggregates (trunks), LACP, or
otherwise on the downlinks side.
Boot time reduced significantly for configurations requiring that multiple parameters be set
(QXCR1001149267)
The boot time configuration delay when multiple parameters are being set is now reduced
significantly. Prior to this release, system boot time could be impacted significantly by the
number of parameters being set in the configuration file, especially in system configurations
supporting a large number of iexgbe LAN devices. Each configuration parameter was set
using independent calls to the driver. Additional delays would result if driver resets were
required for the settings to take effect. With this release of the driver, a single call is used to
set multiple parameters, reducing the delay caused by multiple resets.
A new command line option has been added to the lanadmin command to provide this
enhancement:
lanadmin -X boot_parameter [{drv_pr_on | drv_pr_off}] [mtu=size] [{recv_cko_on | recv_cko_off}] [{send_cko_on
| send_cko_off}] [drv_mq=queue-number] [vmtu={0 | 32160}] ppa
For example:
/usr/sbin/lanadmin -X boot_param send_cko_on drv_mq=4 vmtu=32160
recv_cko_on drv_pr_off mtu=1500 9
Rx flow control
Tx flow control
ON/OFF
ON/OFF
OFF only.
ON/OFF
Default setting during driver
NOTE:
initialization before startup
1. If previous value is ON, setting
configuration parameters are applied
MTU to 9000 automatically sets Rx will be: ON
flow control to OFF.
2. If the MTU value is changed back
to 1500, the original Rx flow
control setting (rx_fctrl) prior
to changing to 9000 MTU is
restored.
Only OFF
Only ON
Only OFF
Only ON
For non-Flex-10 interfaces, Tx and Rx flow control will be enabled by default. Setting Jumbo Frames
MTU disables Rx flow control; Rx flow control cannot be enabled if the interface has a Jumbo
Frames MTU.
For Flex-10 interfaces, Tx flow control is always enabled and Rx flow control is always disabled.
Table 2 (page 7) lists new configuration file parameters for non-Flex-10 interfaces. These
parameters are added to the configuration file /etc/rc.config.d/hpiexgbeconf at installation
if the file has not been previously modified by the customer. If the file has been previously modified,
the configuration file is not automatically modified with the new parameters, and the configuration
file must be updated manually. The new version will be available in file
usr/newconfig/etc/rc.config.d/hpiexgbeconf.
Table 2 Configuration file parameters for non-Flex-10 interfaces1
Command
Function
Valid values
Default
HP_IEXGBE_TX_FLOW_CONTROL
ON/OFF
ON
ON/OFF
ON
For Flex-10 interfaces, the configuration parameters described in this table will fail if changed from the default settings
listed in column 4. The defaults are permanent settings.
The following warning messages have been added to the nwmgr command:
Setting MTU size greater than 1500 (enabling Jumbo Frames) for a non-Flex-10 interface
brings up the warning message shown in the following example:
server2#nwmgr -s -A mtu=9000 -c lan3
WARNING: For non-flex10 interface, setting Jumbo MTU will automatically turn OFF Rx flowcontrol
lan3 current values:
New MTU = 9000
Attempting to turn off Tx flow control for a Flex-10 interface brings up the warning message
shown in the following example:
server2#nwmgr -s -A tx_fctrl=off -c lan3
WARNING: For flex10 interface, the Tx flow control will be always on and the Rx flow control will be always
off
lan3 current values:
New Transmit Flow Control = Off
NOTE: The warning message incorrectly displays the Tx flow control state as Off when it
should be On. This is a known issue (see Known problems and limitations (page 10)).
Attempting to turn on Rx flow control for a Flex-10 interface on which the MTU size is greater
than 1500 (enabling Jumbo Frames) brings up the warning message shown in the following
example. The Rx flow control cannot be turned on in this instance, so the specified value (on)
is invalid; Rx flow control remains turned off.
server2#nwmgr -s -A rx_fctrl=on -c lan3
WARNING: For flex10 interface, the Rx flow control is always on
For non-flex10 interface, if Jumbo MTU is set, the rx flow control cannot be turned on
lan3 current values:
New Receive Flow Control = ERROR: Invalid value
Description
Link status is incorrectly reported for LAN ports connected to a switch or pass-through
When LAN ports are connected to a switch or pass-through, the iexgbe driver might fail to
detect a cable connect or disconnect. As a result, the LAN interface link status on the system
side is incorrectly displayed by nwmgr and lanadmin. For example, after a cable disconnect,
the status is incorrectly reported as UP instead of DOWN.
QXCR1001222146
Description
The host encountered a rare hang situation as the intctl command gets stuck within the
kernel after repeated interrupt migrations are run on the host backing interface. The cause is
the driver failing to perform an appropriate handshake with the kernel module responsible
for completing the interrupt migration event under certain rare circumstances.
Description
QXCR1001209171
AVIO: High outbound discards on HPVM guest with iexgbe interface. TCP connections (such
as rlogin and telnet) from a remote system to the guest do not work and the guest hangs
intermittently.
QXCR1001182096
When packets with an invalid LLC, IP or TCP header length are sent through the HPVM guest
igssn interface, the iexgbe driver will drop such packets. But the guest is not aware of
such drops and it continues to expect send completion for those packets. This situation results
in a gradual reduction of the number of usable descriptors for igssn, which causes
performance to degrade and, eventually, the igssn interface to hang.
QXCR1001192266
For non-Flex-10 (non-VC) interfaces, when using customized iexgbe configuration file settings
that enable Jumbo Frames (MTU size greater than 1500), problems occur at startup. This
problem surfaced after Tx and Rx flow control support was introduced to the iexgbe driver
(QXCR1001093086). The workaround in the preceding release was to disable flow control
by default. The B.11.31.1205 release sets Tx and Rx flow control to ON by default. Any
request to turn on Jumbo Frames will override the Rx flow control settings and automatically
set Rx flow control to OFF.
Description
Disables flow control by default. This removes the possibility of bringing up issues introduced
with the B.11.31.1201 release (QXCR1001093086). For more information about the issues,
see Section 4 (page 10).
QXCR1001270195 iexgbe 1303 versions introduced issues due to missing firmware lock
The following symptoms might be seen because of this defect:
iexgbe driver continuously sends UP/DOWN notification events to the WBEM provider.
(QXCR1001268673) The WBEM events seen by the user are of these types:
DL_HP_EXT_LINK_DOWN_IND and DL_HP_EXT_LINK_UP_IND.
(QXCR1001267062) The nettl log becomes filled with link EPHY8073 link up
notification messages.
The following is an example of the messages seen:
<4006> 10GBase-SR in path 0/0/0/3/0/0/5
Link Event.
EPHY8073 link up or
<4006> 10GBase-SR in path 0/0/0/3/0/0/5
Link Event.
EPHY8726 link up
(QXCR1001268375) Ports for which the adapter reports the incorrect speed might
occasionally cause APA formation to fail during startup.
10
Incorrect warning message after attempt to turn off Tx flow control for a Flex-10 interface
When an attempt is made to turn off Tx flow control for a Flex-10 interface, a warning message
indicates correctly that Tx flow control always stays on for Flex-10 interfaces; however, the
warning message displays the current value of Tx flow control as Off instead of On.
Severity: Minor
Workaround: Disregard the displayed state of Tx flow control.
#echo "$boot_cmdstr"
echo "${HPLANADMIN} -X boot_param $boot_cmdstr $PPA"
emsg=`${HPLANADMIN} -X boot_param $boot_cmdstr $PPA 2>&1`
if [[ $? -ne 0 ]]; then
errmsg; rval=${ERROR}
fi
waitfor $(driverState)
# SAM script would have attempted a MTU change earlier; this is 2nd try
#configure_mtu
#if (( $mturet != 0 )); then
#
errmsg # emsg was set by configure_mtu
#
rval=$ERROR
#
fi
For the non-Flex-10 interface, you can change the flow control and MTU size as needed.
However, when Jumbo Frames are enabled, if Rx flow control is already set to ON, the driver
automatically resets RX flow control to OFF. Rx flow control and Jumbo Frames cannot both
be in operation at the same time.
Severity: Medium
Workaround: If you want Rx flow control, disable Jumbo Frames.
11
When you use the ncweb or SMH interface to change the number of receive queues, an error
message appears.
Workaround: Use nwmgr instead of ncweb to change number of the queues. The command
syntax is:
nwmgr -s -A drv_mq=<new#> -c lan<instance>
where
<new#>
<instance>
For specific installation instructions, see the installation procedure or overview document for
your adapter.
For detailed information on supported server platforms, operating systems, and firmware level
requirements, see the Ethernet Support Matrix.
12
Enter your product name (for example, NC532m or, for LOMs, a server name such as
Superdome 2) or enter the product number and click Search.
Click the Cross operating system (BIOS, Firmware, Diagnostics, etc.) link.
Click EFI and FWs for use on Integrity under the Description heading for the EFI download.
To review firmware versions and release notes, click the Readme tab. To download the
firmware, click the Download button.
Download the firmware.
9.
To install the firmware update, follow the procedure supplied with the downloaded update
package.
6 Related information
The latest documentation for Ethernet adapters is available in English at:
http://www.hp.com/go/10-gigabit-ethernet-docs
Installation guides are listed alphabetically in the Setup and install general section.
Support Matrix documents are listed alphabetically in the General reference section.
8 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.
6 Related information
13