IEther-00 (iether) B.11.31.1307 Ethernet Driver Release Notes (1st Edition) HP-UX 11i v3

Table 3 HP-UX 11i v3 December 2012 fixes IEther-00 B.11.31.1212
DescriptionSR number
On multiple-CPU systems and a high-transmit load, the iether driver might cause intermittent
system hangs or high CPU utilization.
QXCR1001247694
In addition, under these circumstances, systems with MC/Serviceguard might exhibit a
cluster-reformation or system Transfer Of Control (TOC).
Potentially poor network performance might be observed when operating the LAN adapter
at 10Mb or 100Mb half-duplex. The following adapters could be impacted: AD221A,
AD222A, AD393A, and rx2800 LAN on Motherboard (LOM) adapters.
QXCR1001200917
Table 4 HP-UX 11i v3 October 2012 fixes IEther-00 B.11.31.1210
DescriptionSR number
After a LAN adapter port is reset, the statistics reported might reveal a large number of
Inbound Discards. Activity on the receive side might appear to be hung. The following LAN
adapter products could be impacted: AD221A, AD222A, AD393A, and rx2800 core
LAN-on-Motherboard (LOMs).
1
QXCR1001220405
1
The rx2800 LAN interface is on the system motherboard. This LAN adapter appears in ioscan output as AH395-60001”.
Table 5 HP-UX 11i v3 September 2012 fixes IEther-00 B.11.31.1209.01
DescriptionSR number
False link status reported when NC360m or NC364m autonegotiation is OFF (Intel
82571mezzanine adapters only). When autonegotiation is OFF for the NC360m or NC364m
QXCR1001202598
adapter, and the corresponding switch port is disabled, the LAN interface link status on the
system side is displayed by nwmgr and lanadmin as UP. It should be displayed as DOWN.
Link status detection delay with NC360m and NC364m PCIe Ethernet mezzanine server blade
adapter (Intel 82571mezzanine adapters only). When a link is down, there is a significant
QXCR1001216397
delay before the iether driver detects this and logs a nettl error. Reported delays range
from 2 to 36 seconds.
Table 6 HP-UX 11i v3 September 2012 fixes IEther-00 B.11.31.1209
DescriptionSR number
System fails to produce a crash dump after a soft reset (TOC). This results because the iether
driver crashes when initializing at the same time that the system is performing the TOC (transfer
of control).
QXCR1001194114
4 Problems fixed in this or earlier versions 5