IEther-00 (iether) B.11.31.1210 Ethernet Driver Release Notes, Edition 2 (November 2012)

• PCI OLRAD

• PCI Error handling and recovery

• vPars V6

• HP Integrity Virtual Machines (HPVM)

• HPVM AVIO

• HP-UX LAN provider

• MIB and driver statistics

• Configurable using SMH or nwmgr

• nettl tracing/logging

3 New and changed features in this release

3.1 New features

There are no new features included in IEther-00 at the time of this publication.

3.2 Changed features

There are no changed features included in IEther-00 at the time of this publication.

4 Problems fixed in this or earlier versions

4.1 Problems fixed in this version

Table 1 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).

QXCR1001220405

The rx2800 LAN interface is on the system motherboard. This LAN adapter appears in ioscan displays as AH395-60001.

4.2 Problems fixed in previous releases

Table 2 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 cards only). When autonegotiation is OFF for the NC360m or NC364m

QXCR1001202598

card, 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

card (Intel 82571mezzanine cards only). When a link is down, there is a significant delay

QXCR1001216397

before the iether driver detects this and logs a nettl error. Reported delays range from

2 to 36 seconds.

Table 3 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