10GigEthr-02 (iexgbe) B.11.31.1303 Ethernet Driver Release Notes (Edition 2)
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
3 Problems fixed in this release
The following defects were fixed in this release:
Table 3 HP-UX 11i v3 January/March 2013 fixes — 10GigEthr-02 B.11.31.1301 and B.11.31.1303
DescriptionSR number
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
QXCR1001233679
side is incorrectly displayed by nwmgr and lanadmin. For example, after a cable disconnect,
the status is incorrectly reported as UP instead of DOWN.
Port unavailable, queues fail to initialize on Superdome
While doing stress testing with heavy traffic along with periodic port resets, olrad, and
ifconfig plumb/unplumb, the port might be unable to initialize the maximum number of
QXCR1001222146
queues supported. In such cases for drivers with versions AR1209 and earlier, the port
transitions to the DEAD state. To make the port usable, a system reboot is required. The issue
is rarely reproducible; reproducing the issue requires the above-mentioned stress testing
sustained over a long duration.
Problems fixed in recent versions
Table 4 HP-UX 11i v3 September 2012 fixes — 10GigEthr-02 B.11.31.1209
DescriptionSR number
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
QXCR1001202586
the driver failing to perform an appropriate handshake with the kernel module responsible
for completing the interrupt migration event under certain rare circumstances.
8










