| From: "OpenVMS.org Lists" <ovms-lists@openvms.org> | | Subject: VMS83I_LAN-V0800, ECO Kit Release | | Date: Thu, 14 Feb 2008 16:27:44 -0500 | | To: <alerts@openvms.org> |
|
 |
|
DATE: 14-FEB-2008 14:17:30.87
TO: Customer Interest List
SUBJECT: Released Kit: VMS83I_LAN-V0800
The VMS83I_LAN-V0800 kit has been released. This kit should be
available on the following patch download site within 24
hours of receiving this announcement.
http://www.itrc.hp.com/service/patch/mainPage.do
ftp://ftp.itrc.hp.com/
Kit files are:
VMS83I_LAN-V0800.ZIPEXE
VMS83I_LAN-V0800.TXT
Following are the release notes for this kit.
****************************
ECO SUMMARY INFORMATION
****************************
Release Date: 14-FEB-2008
Kit Name: HP-I64VMS-VMS83I_LAN-V0800--4.PCSI$COMPRESSED
Kit Applies To: OpenVMS for Integrity Servers V8.3
Approximate Kit Size: 12621 blocks
Installation Rating: INSTALL_2
Required Features: LAN
Reboot Required: Yes
Special Install Instructions: No
Superseded Kits: VMS83I_LAN-V0700
Mandatory Kit Dependencies: VMS83I_UPDATE-V0500 or later
Optional Kit Dependencies: None
Checksums:
VMS83I_LAN-V0800.ZIPEXE Checksum: 1990705125
HP-I64VMS-VMS83I_LAN-V0800--4.PCSI$COMPRESSED Checksum: 799949204
VMS83I_LAN-V0800.ZIPEXE MD5 Checksum:
DB0BA0AC52BC029EC2C89C4EA6ECE9A7
HP-I64VMS-VMS83I_LAN-V0800--4.PCSI$COMPRESSED MD5 Checksum:
AD044430AF87F007494598A1E979900C
=======================================================================
Hewlett-Packard OpenVMS ECO Cover Letter
=======================================================================
1 KIT NAME:
VMS83I_LAN-V0800
2 KIT DESCRIPTION:
2.1 Installation Rating:
INSTALL_2 : To be installed by all customers using the
following feature(s):
- LAN
2.2 Reboot Requirement:
Reboot Required.
HP strongly recommends that a reboot is performed immediately after
kit installation to avoid system instability. If you have other
nodes in your OpenVMS cluster, they must also be rebooted in order
to make use of the new image(s). If it is not possible or
convenient to reboot the entire cluster at this time, a rolling
re-boot may be performed.
2.3 Version(s) of OpenVMS to which this kit may be applied:
OpenVMS for Integrity Servers V8.3
2.4 New functionality or new hardware support provided:
Yes
3 KITS SUPERSEDED BY THIS KIT:
- VMS83I_LAN-V0700
4 KIT DEPENDENCIES:
4.1 The following remedial kit(s), or later, must be installed
BEFORE installation of this, or any required kit:
- VMS83I_UPDATE-V0500
Page 2
4.2 In order to receive all the corrections listed in this kit,
the following remedial kits, or later, should also be
installed:
- None
5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83I_LAN-V0800
KIT
5.1 New functionality addressed in this kit
5.1.1 Clear and Restore Counters Support, LANCP Utility
5.1.1.1 Functionality Description:
For LANCP, there are two new qualifiers, /CLEAR and
/RESTORE, which are used with the LANCP commands SHOW
DEVICE/COUNTERS and SHOW DEVICE/INTERNAL_COUNTERS, to
allow counters to be cleared and restored. Only LANCP
counter displays are affected. The counters maintained
by the drivers remain unchanged. This functionality is
included in LANCP and LANACP. The drivers affected
include support to indicate which counter fields are
clearable and to convert many counter fields from 32 bits
to 64 bits to avoid problems when a counter has exceeded
32 bits.
The commands:
MC LANCP SHOW DEVICE/COUNTERS/CLEAR
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS/CLEAR
clear the counters after the commands execute, so that
the subsequent commands:
MC LANCP SHOW DEVICE/COUNTERS
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS
show the incremental values since the counters were
cleared. To restore the counters to the original values,
use the commands:
MC LANCP SHOW DEVICE/COUNTERS/RESTORE
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS/RESTORE
A side effect of this new functionality is that the size
of the mailboxes used for communication between LANCP and
LANACP has increased to accommodate cleared counters
information. Users may have to increase the BYTLM quota
value for the user account used to issue the LANCP
counters commands. If BYTLM is insufficient, a warning
message will accompany the command output, to indicate
the need to increase it.
Page 3
Images Affected:
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
5.1.2 SHOW DEVICE/INTERNAL_COUNTERS Command Improvement,
LANCP Utility
5.1.2.1 Functionality Description:
For LANCP, the SHOW DEVICE/INTERNAL_COUNTERS command
displays many counters, status and informational fields
maintained by the LAN driver. Typically, the command
does not display zero counters, unless you specify the
/ZERO qualifier. Some of the fields added to the
internal counters, by other changes in this patch kit,
include text and packet data fields which would have been
displayed if blank or zero. This LANCP change treats
blank text data and zero packet data strings as zero
data. These fields will not be displayed unless they are
non-blank or non-zero or if you specify the /ZERO
qualifier.
Images Affected:
- [SYSEXE]LANCP.EXE
Page 4
5.1.3 Ability to Collect Additional Information on Receive
CRC Errors, LAN Drivers
5.1.3.1 Functionality Description:
Most LAN devices do not deliver bad receive packets to
the LAN driver. Some of the the LAN drivers included in
this kit have been modified to include a device-specific
function to enable this functionality, to enhance the
diagnosis of network problems by allowing capture of the
packet header of bad packets.
Once enabled, you can display the packet header and time
of the last error using the LANCP command:
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS/DEBUG
In addition, you can trace the errors with LAN driver
tracing by using the LANCP commands:
MC LANCP SET DEVICE/TRACE
MC LANCP SHOW DEVICE/TRACE
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYSEXE]LANCP.EXE
5.1.4 MOP CONNECT Command Enhancement, LANCP Utility
5.1.4.1 Functionality Description:
The LANCP MOP CONNECT command is used to connect to a
remote console, for example,to connect to a DECserver.
This enhancement makes connections more robust by
increasing the retry count and timeout values for the
connection code within LANCP.
Images Affected:
- [SYSEXE]LANCP.EXE
Page 5
5.1.5 SHOW Command Enhancement, LANCP Utility
5.1.5.1 Functionality Description:
The output from LANCP SHOW commands has been modified to
show consistent header output across the various SHOW
commands. The header now includes the time and node
name.
Images Affected:
- [SYSEXE]LANCP.EXE
5.1.6 Additional Debug and Monitoring Support, LAN Drivers
5.1.6.1 Functionality Description:
Added support for additional debug and monitoring
functionality, via _MON versions of drivers. If the _MON
version of the driver is copied to the non _MON version,
or if the system is booted with system parameter
SYSTEM_CHECK set to 1, the debug and monitoring
functionality will be available.
The monitoring functionality collects network utilization
data. Tools to collect and analyze this data will be
provided in the future.
Images Affected:
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.7 LAN_FLAGS System Parameter Validation, LAN Drivers
5.1.7.1 Functionality Description:
Since a possible system manager error is to enter a
system parameter in decimal instead of hex or vice versa,
the LAN drivers now validate the contents of the
LAN_FLAGS system parameter. If the setting is simply
non-standard, the driver displays a warning message but
accepts the setting. If the setting is non-standard and
could adversely affect the operation of the driver, the
driver displays a message and ignores the setting. In
both cases, an error log entry is made with the hex value
Page 6
0xDAFF, indicating the LAN_FLAGS setting is non-standard,
i.e., DAFFy.
Images Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.8 Device Internal Counters and Histogram Data, LAN
Drivers and LANCP Utility
5.1.8.1 Functionality Description:
The driver internal counters already include transmit
time and fork time histograms measuring the time from
issuance of a transmit request to completion of the
transmit request, and the time from scheduling a fork
process to the time the fork process actually runs. This
data gives an idea of how heavily loaded the system is,
particularly with respect to fast path CPU assignment
among devices.
An additional histogram has been included to measure the
amount of time that an application takes to process a
received packet before returning control back to the LAN
driver. This is useful for diagnostic purposes.
In some drivers, the /DEBUG qualifier was needed to
display this data. Now, the /DEBUG qualifier is not
needed to display this histogram data. Note that the
/ZERO qualifier is needed to see all counter fields
including zero counters.
The LANCP command to display the internal counters data
is:
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS
Page 7
Images Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.9 Blade Virtual Connect MAC Address Support, NC360M and
NC364M Mezzanine NICs
5.1.9.1 Functionality Description:
This driver update adds support for the ability to set
the MAC address of the Blade Mezzanine NIC cards, NC360M
and NC364M, using the Virtual Connect features in the On
Board Administrator (OA).
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.1.10 Dual and Quad Port Gigabit Ethernet Blade, NC360M and
NC364M Mezzanine NICs
5.1.10.1 Functionality Description:
This driver update adds support for the Dual and Quad
Port Gigabit Ethernet Blade Mezzanine NICs, NC360M,
NC364M.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
Page 8
- [SYS$LDR]SYS$EI1000_MON.EXE
5.1.11 Quad Port Gigabit Ethernet Support, Intel PCI-X,
PCI-Express NICs
5.1.11.1 Functionality Description:
This driver update adds support for the Intel Gigabit
Ethernet NICs:
- AD193A, single-port, UTP, PCI-X (includes single-port
4G QLogic FibreChannel)
- AD194A, dual-port, UTP, PCI-X (includes dual-port 4G
QLogic FibreChannel)
- AD331A, single-port, UTP, PCI-X
- AD332A, single-port, MMF, PCI-X
- AD337A, dual-port, UTP, PCI-Express
- AD338A, dual-port, MMF, PCI-Express
- AD339A, quad-port, UTP, PCI-Express
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIGBTDRIVER.EXE
- [SYSEXE]SYS$CONFIG.DAT
5.1.12 LAN Driver Enhancements, Intel Gigabit Devices
5.1.12.1 Functionality Description:
The following changes have been made to the Intel Gigabit
driver to add support for new devices and to add new
features.
- Enhanced device self test by adding diagnostic code
to do a CRC validation of the first 50k packets
received. If the driver detects a failure, it makes
an error log entry, displays a failure message, and
marks the device offline and unusable.
Page 9
- Added support for loopback mode, which is used by
UETP and by diagnostic programs.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.1.13 Dual Port Gigabit Ethernet Support, Broadcom Gigabit
BCM5704 Blade LOM
5.1.13.1 Functionality Description:
This driver update adds support for the Dual Port Gigabit
Ethernet Blade LOM device, Broadcom BCM5704 chip.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.1.14 Gigabit Ethernet Support, AD385A NIC
5.1.14.1 Functionality Description:
This driver update adds support for the 10 Gigabit
Ethernet PCI-X 266 mhz device, AD385A.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.15 LAN Failover Driver Enhancements
5.1.15.1 Functionality Description:
In order to improve the diagnostic capabilities of the
LAN Failover driver, the internal counters have been
modified to include the failover transition time.
When a LAN device transitions from "link up" to "link
down", the LAN failover driver transitions to a standby
device, if one is available. The amount of time needed
to perform this transition from the time the link state
change is noticed is very fast, usually a few
milliseconds at most.
Page 10
However, the actual transition time is somewhat more,
because it takes some time for the driver to recognize
that the link has gone down, and then it takes some time
for the switch to recognize that receive traffic
originally intended for one port is now to go to a
different port. Switch configuration parameters affect
this time significantly.
The true time it takes to failover from one device to
another is measured from the last packet received on the
original active device to the first unicast packet
received on the new active device. This time is recorded
in the LLDRIVER internal counters which can be displayed
by the LANCP command SHOW DEVICE/INTERNAL_COUNTERS LL.
Note that if there is only occasional receive traffic,
the transition time cannot be determined accurately. So,
a user could see a very long transition time, just
because, in the absence of receive traffic, the driver
really can not tell when the failover actually completes.
The failover time is most accurate when there is a
continuous stream of transmit and receive traffic which
has been interrupted by the failover operation and
continues after the transition to the standby device.
The failover time in this case is a better approximation
of the actual time taken to do a transition, subject to
any considerations of the application used to generate
the continuous stream of traffic. Note that the last
packet received may be unicast or multicast. But the
first packet received on the new device is unicast to
include the time taken for the switch to begin forwarding
unicast traffic.
Images Affected:
- [SYS$LDR]SYS$LLDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
Page 11
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.1.16 GETDVI Device Status Enhancement, LAN Drivers
5.1.16.1 Functionality Description:
In order to enable enhancements to the system service
GETDVI, the LAN drivers have been modified to maintain
status for jumbo frames and auto-negotiation in a common
area that the system service can access.
This allows use of the DCL lexical function F$GETDVI to
display this status. And it enables the DCL SHOW
DEVICE/FULL command display of this status as well.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$LAN.EXE
- [SYS$LDR]SYS$LAN_CSMACD.EXE
- [SYS$LDR]SYS$LAN_FDDI.EXE
- [SYSLIB]LAN$SDA.EXE
- [SY$LIB]SDA$SHARE.EXE
5.2 Problems addressed in this kit
Page 12
5.2.1 Error Log Entry after Device Configured, LAN Drivers
5.2.1.1 Problem Description:
The LAN drivers make an error log entry on every link
transition to "link up" and "link down", and the error
count on the device is incremented. There is one case
that can be confusing - when a device is first
configured, the link state transitions from "unknown" to
"link up". There was a link transition but no error.
The drivers have been modified to avoid making an error
log entry in this case. Until the device has gone to the
"link up" state, and then transitioned to "link down", no
error log entry will be made.
This means that on a system that has just been booted, a
DCL SHOW ERROR command will not show any errors charged
to the LAN devices. Until a cable has been connected to
a device and the link state transitions to "link up" for
the first time, no errors will be recorded for the
device. There are some exceptions, i.e., if the device
is run in loopback mode a "link up" state is entered
despite the lack of a valid cable connection. In this
case, if there is a hardware error, the driver may log an
error against the device. Also, if the LAN_FLAGS are
questionable, the driver may log an error against the
device.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
Page 13
5.2.1.2 Quix and PTR cases reporting this problem:
5.2.1.2.1 Quix Cases
None.
5.2.1.2.2 PTR(s)
None.
5.2.1.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity servers V8.3-1H1
5.2.1.4 Work-arounds:
None.
5.2.2 Problem Setting Preferred CPU for Logical LAN and VLAN
Devices
5.2.2.1 Problem Description:
HP TCP/IP, using an LL or VL (LAN Failover or VLAN)
device, may run on the primary CPU because it thinks the
LAN device does not support fastpath.
When a VCI application (DECnet-Plus, TCP/IP, PEDRIVER,
LAT, LAST, et al) is started, the application is given
the address of the preferred CPU database. This allows
the application to determine which CPU the LAN device has
been affinitized to. For LAN Failover and VLAN devices
(LL and VL devices), the LAN drivers do not supply this
data correctly, so VCI applications may not be aware that
the LAN driver for a particular device is running on a
particular CPU.
The change in this LAN kit corrects this initialization
defect, allowing VCI applications to rely on the
preferred CPU database field.
Images Affected:
- [SYS$LDR]SYS$LAN.EXE
Page 14
5.2.2.2 Quix and PTR cases reporting this problem:
5.2.2.2.1 Quix Cases
QXCM1000404029
5.2.2.2.2 PTR(s)
None.
5.2.2.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.2.4 Work-arounds:
Set the preferred CPU of the Logical LAN or VLAN device
explicitly, then start the application on the device.
5.2.3 Duplicate Link Up Message, DE500 Devices
5.2.3.1 Problem Description:
When auto-negotiation is in progress, the "link up"
message was displayed on the console once at the start of
auto-negotiation and again when auto-negotiation
finished. This has been corrected, so only a single
"link up" message is displayed on the console when the
link transitions to link up and auto-negotiation is
enabled.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.3.2 Quix and PTR cases reporting this problem:
5.2.3.2.1 Quix Cases
None.
5.2.3.2.2 PTR(s)
None.
Page 15
5.2.3.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.3.4 Work-arounds:
None.
5.2.4 Incorrect Error Log Entry, DE500 Devices
5.2.4.1 Problem Description:
The error log entry for "link down" events included the
hex type field of 0xCA which is used to indicate "link
up" or "Connection Available". The hex type field has
been changed to 0xCD indicating "link down" or
"Connection Down".
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.4.2 Quix and PTR cases reporting this problem:
5.2.4.2.1 Quix Cases
None.
5.2.4.2.2 PTR(s)
None.
5.2.4.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.4.4 Work-arounds:
None.
5.2.5 Transmit Error Status and Cluster Instability, DE500
Devices
Page 16
5.2.5.1 Problem Description:
When the DE500 is disconnected from the network, transmit
requests return error status as expected, but the DE500
LAN driver incorrectly hands the transmit requests to the
DE500. This extends the amount of time the LAN driver
owns the transmit request before returning it with error
status.
For most applications, this is of no consequence.
However, for the cluster applications, NISCS and
PEDRIVER, this may cause connectivity problems when
multiple LAN interfaces are in use and one of them is the
device that is disconnected from the network.
Connectivity problems would be visible as PEDRIVER error
messages and bad performance, potentially leading to a
CLUEXIT.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.5.2 Quix and PTR cases reporting this problem:
5.2.5.2.1 Quix Cases
None.
5.2.5.2.2 PTR(s)
None.
5.2.5.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.5.4 Work-arounds:
None.
5.2.6 Full-Duplex State Not Reported Correctly, DE600 Devices
Page 17
5.2.6.1 Problem Description:
When the device was set to "full-duplex enabled" and
"auto-negotiation is disabled", the LAN driver for the
Intel 10/100 device did not set the device characteristic
"full duplex operational" correctly. It would then
appear that the device was in half-duplex mode, when it
actually was in full-duplex mode as requested.
This problem occurred when the console environment
variable, EIx0_MODE, was set to "Full Duplex, Twisted
Pair" or "FastFD", when LANCP commands were issued after
boot to set the device to half-duplex or full-duplex
mode.
This display problem affected the LANCP command SHOW
DEVICE/CHARACTERISTICS, any programs that did a QIO
SENSEMODE to look at the device settings, and also the
SDA command SHOW LAN.
Images Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
5.2.6.2 Quix and PTR cases reporting this problem:
5.2.6.2.1 Quix Cases
None.
5.2.6.2.2 PTR(s)
None.
5.2.6.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.6.4 Work-arounds:
None.
Page 18
5.2.7 Performance Degradation, DEGPA Device
5.2.7.1 Problem Description:
If memory is severely exhausted on a system, the DEGPA
driver miscounts the number of buffers allocated. When
this happens, the driver aggravates the memory exhaustion
problem by attempting to allocate even more buffers.
This causes a performance degradation on the system
beyond the degradation that would be obvious when the
system is severely low on memory.
Images Affected:
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
5.2.7.2 Quix and PTR cases reporting this problem:
5.2.7.2.1 Quix Cases
None.
5.2.7.2.2 PTR(s)
None.
5.2.7.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.7.4 Work-arounds:
None.
5.2.8 Recursive Bugcheck During Device Configuration, Intel
and Broadcom Gigabit Devices
5.2.8.1 Problem Description:
The driver may crash if a system crash occurs before the
device has been fully configured. This would result in a
recursive bugcheck if the system crashes (for some other
reason) during booting. This doesn't affect the system,
since the system was crashing anyway, but complicates the
analysis of the crash because of the second bugcheck.
Page 19
This can occur in the few milliseconds from the time the
driver has been loaded to the time the driver has been
initialized.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.8.2 Quix and PTR cases reporting this problem:
5.2.8.2.1 Quix Cases
None.
5.2.8.2.2 PTR(s)
None.
5.2.8.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.8.4 Work-arounds:
None.
5.2.9 Mishandling Oversize Receive Packet, Intel Gigabit
Devices
5.2.9.1 Problem Description:
If an oversized packet was received when the device owned
exactly 1 receive buffer, the driver would incorrectly
process the next receive entry before the packet has been
completely received, possibly leading to a system crash.
Note that this problem is listed incorrectly as a denial
of service vulnerability at,
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5242, with
the idea being that an attacker could intentionally send
oversize packets to a system and therefore induce a
crash. In fact, it is virtually impossible to induce a
crash because of this problem.
Page 20
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.2.9.2 Quix and PTR cases reporting this problem:
5.2.9.2.1 Quix Cases
None.
5.2.9.2.2 PTR(s)
None.
5.2.9.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.9.4 Work-arounds:
None.
5.2.10 Transmit Hang Problem, Intel Gigabit Devices
5.2.10.1 Problem Description:
For some variants of the Intel chip used in LAN devices
supported by this driver, a problem exists that can
result in a transmit hang with jumbo packets. This
problem is detected by the standard LAN driver transmit
timeout mechanism which detects the hang condition after
3 seconds and resets and reinitializes the device. The
hang has been seen under heavy load conditions perhaps
once a day. It is visible as an error charged to the
device each time the device is reset and forces
applications to retry a transmit request. The driver has
been modified to avoid the condition leading to the hang
by adjusting the length of the first transmit segment
given to the device for a transmit request.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
Page 21
5.2.10.2 Quix and PTR cases reporting this problem:
5.2.10.2.1 Quix Cases
None.
5.2.10.2.2 PTR(s)
None.
5.2.10.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.10.4 Work-arounds:
None.
5.2.11 Broadcast Address Not Enabled Problem, Broadcom
Gigabit Devices
5.2.11.1 Problem Description:
If promiscuous mode is enabled on the device, the
broadcast address is not enabled correctly. This problem
has been fixed. Note that only a privileged user can
enable promiscuous mode on a device.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.11.2 Quix and PTR cases reporting this problem:
5.2.11.2.1 Quix Cases
None.
5.2.11.2.2 PTR(s)
None.
Page 22
5.2.11.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.11.4 Work-arounds:
None.
5.2.12 Receive Bytes Counter Incorrect, Intel and Broadcom
Gigabit Devices
5.2.12.1 Problem Description:
The "bytes received" and "multicast bytes received"
counters maintained by the driver did not include the 14
bytes of header and 4 bytes of CRC on each packet
received. This has been corrected.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.12.2 Quix and PTR cases reporting this problem:
5.2.12.2.1 Quix Cases
None.
5.2.12.2.2 PTR(s)
None.
5.2.12.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
Page 23
5.2.12.4 Work-arounds:
None.
5.2.13 Media Type Not Correct on Blade System, Broadcom
Gigabit LOM
5.2.13.1 Problem Description:
The media type for the BCM5704 LOM on Blade systems was
reported as "single-mode fiber" instead of "multi-fiber"
fiber. This error occurred with the following commands:
MC LANCP SHOW CONFIGURATION
MC LANCP SHOW DEVICE/CHARACTERISTICS
SDA> SHOW LAN
Driver operation was not affected by this problem.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.13.2 Quix and PTR cases reporting this problem:
5.2.13.2.1 Quix Cases
None.
5.2.13.2.2 PTR(s)
None.
5.2.13.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
5.2.13.4 Work-arounds:
None.
Page 24
5.2.14 Device Speed Not Reported Correctly, Broadcom Gigabit
Devices
5.2.14.1 Problem Description:
If a LANCP> SET DEVICE /SPEED command is used to change
the speed of the device but the speed does not actually
change (for example, because auto-negotiation prevented
the speed change from taking effect), the driver does not
detect that the speed change did not take place. A
LANCP> SHOW DEVICE/CHARACTERISTICS command will
erroneously report the device speed as the requested
speed rather than the actual, unchanged speed.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.14.2 Quix and PTR cases reporting this problem:
5.2.14.2.1 Quix Cases
None.
5.2.14.2.2 PTR(s)
None.
5.2.14.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
5.2.14.4 Work-arounds:
None.
5.2.15 Loopback Mode Not Disabled Correctly, Broadcom Fiber
Gigabit Devices
Page 25
5.2.15.1 Problem Description:
Loopback mode cannot be disabled once enabled on a fiber
Broadcom Gigabit device, unless a device reset is done.
The affected devices are the DEGXA-SA, DEGXA-SB,
DEGX2-SA, Blade BCM5704 LOM, and the A9782A combo card.
Loopback mode is typically enabled by diagnostic
programs, and can be enabled only on a device that is not
in use by another application.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.15.2 Quix and PTR cases reporting this problem:
5.2.15.2.1 Quix Cases
None.
5.2.15.2.2 PTR(s)
None.
5.2.15.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
5.2.15.4 Work-arounds:
After running the diagnostic program, do a device reset
using the LANCP command:
MC LANCP UPDATE DEVICE/RESET devname
5.2.16 Transmit Ring Inconsistency NETDLLERR Bugcheck Crash,
Broadcom Gigabit Devices
Page 26
5.2.16.1 Problem Description:
On rare occasions, the driver detects a transmit ring
inconsistency with the DEGXA and crashes the system with
a NETDLLERR bugcheck. Also, on rare occasions, the
device does not correctly update the receive return ring.
The driver detects this inconsistency when completing the
next receive packet and crashes the system with a
NETDLLERR bugcheck.
Both of these inconsistencies have been corrected. The
driver now detects these conditions and does a simple
reset of the DEGXA and restarts the users rather crashing
the system. Any instances of these inconsistencies can
be observed in the driver internal counters visible by
the LANCP command:
MC LANCP SHOW DEVICE/INTERNAL_COUNTERS
The new counters fields are:
- Transmit ring inconsistencies - number of occurrences
- Last transmit inconsistency - time of the last
occurrence
- Recieve entry mismatches (resulting in reset) -
number of occurrences
These driver detected errors are transparent to
applications, but may result in a few lost packets,
during the few milliseconds that it takes to reset the
DEGXA. The frequency of the error is expected to be
extremely rare, perhaps once a year on an occasional
system.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.2.16.2 Quix and PTR cases reporting this problem:
5.2.16.2.1 Quix Cases
QXCM1000757284
Page 27
5.2.16.2.2 PTR(s)
None.
5.2.16.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
5.2.16.4 Work-arounds:
None.
5.2.17 Transmit Timeout Problem, 10 Gigabit AB287A NIC
5.2.17.1 Problem Description:
If the last 10 gigabit transaction was a transmit request
and there was no additional activity, transmit or
receive, for an extended period of time, the driver could
signal a transmit timeout and reset the NIC. While this
is recoverable by applications, it can adversely affect
the performance of the device.
In addition, when the reset was done, the contents of the
driver internal counters were not reset correctly,
resulting in incorrect counters values displayed by the
LANCP SHOW DEVICE/INTERNAL_COUNTERS command.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.17.2 Quix and PTR cases reporting this problem:
5.2.17.2.1 Quix Cases
None.
5.2.17.2.2 PTR(s)
None.
Page 28
5.2.17.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.17.4 Work-arounds:
None.
5.2.18 Logical LAN Device Status, LAN Failover Device
5.2.18.1 Problem Description:
The LAN Failover device (LL) is associated with an
underlying physical LAN device, which maintains device
status including the settings for auto-negotiation,
full-duplex operational, and link state. The LAN
failover driver uses the settings in the underlying
physical device but did not mirror these settings in the
LAN failover device correctly. If a user looked at this
status in SDA using a SHOW LAN command, or at the DCL
prompt using a SHOW DEVICE/FULL LL command, or looked at
the status using the F$GETDVI syntax, for example,
F$GETDVI("LLA0","LAN_LINK_UP"), they would not see the
correct status.
The LAN failover driver has been modified to mirror these
settings in the LAN failover device, so that the correct
status is displayed.
Images Affected:
- [SYS$LDR]SYS$LLDRIVER.EXE
5.2.18.2 Quix and PTR cases reporting this problem:
5.2.18.2.1 Quix Cases
QXCM1000752692
5.2.18.2.2 PTR(s)
None.
5.2.18.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
Page 29
5.2.18.4 Work-arounds:
None.
5.2.19 Logical LAN Prohibition Against VLAN Devices, LAN
Failover Device
5.2.19.1 Problem Description:
VLANs may be created on Logical LAN devices. Logical LAN
Failsets may not include VLAN devices. The LAN Failover
driver did not enforce this prohibition, which could
result in creation of a Logical LAN device using VLAN
devices which do not function properly as VLAN devices.
The LAN Failover driver now enforces this prohibition and
error status will be returned on an attempt to create
such a set using LANCP.
Images Affected:
- [SYS$LDR]SYS$LLDRIVER.EXE
5.2.19.2 Quix and PTR cases reporting this problem:
5.2.19.2.1 Quix Cases
None.
5.2.19.2.2 PTR(s)
None.
5.2.19.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.19.4 Work-arounds:
None.
5.2.20 Problem Starting Applications, VLAN Device
Page 30
5.2.20.1 Problem Description:
If an application is started on a VLAN device, without
first starting an application on the associated LAN
device, the application will fail to start. Typically,
this only happens on standalone systems, since a system
in a cluster normally starts PEDRIVER on all devices
which avoids this condition when applications such as
TCP/IP and DECnet are subsequently started. This has
been corrected.
Images Affected:
- [SYS$LDR]SYS$VLANDRIVER.EXE
5.2.20.2 CLDs, and QARs reporting this problem:
5.2.20.2.1 CLD(s)
None
5.2.20.2.2 QAR(s)
None.
5.2.20.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.20.4 Work-arounds:
None.
5.2.21 Problem Setting MAC Address, VLAN Device
5.2.21.1 Problem Description:
An application may be started on a VLAN device and have
requested that the MAC address cannot be changed after
being started. This request may be ignored if an
application is subsequently started on the associated LAN
device and that application changes the MAC address of
the LAN device. The result is that the MAC address of
the VLAN device may change when it should not, which may
cause the application to fail.
This has been corrected.
Page 31
Images Affected:
- [SYS$LDR]SYS$LAN_CSMACD.EXE
5.2.21.2 CLDs, and QARs reporting this problem:
5.2.21.2.1 CLD(s)
None
5.2.21.2.2 QAR(s)
None.
5.2.21.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.21.4 Work-arounds:
None.
5.2.22 VLAN Device Only Allows VLAN Traffic, Broadcom Gigabit
Devices
5.2.22.1 Problem Description:
When a VLAN device has been associated with a Broadcom
LAN device, the LAN device includes a zero VLAN tag with
non-VLAN users for packets transmitted by the device.
This may be incompatible with some switches, although, at
present, we are not aware of a switch where this presents
a problem. Broadcom LAN devices include the DEGPA,
DEGXA, A6825A, A6847A, A9782A, A9784A, AB465A, A6794A,
and various embedded 5701 or 5703 LOM devices).
If incompatible, only VLAN tagged traffic would be
possible through the device and switch. For example,
given a system with the LAN device EWA, if a VLAN device
VLA is created using the EWA device, any packets sent by
applications using the EWA device will include a zero
VLAN tag.
This change will ensure correct behavior so that only
packets transmitted on VLAN devices (applications running
on VL devices) will include a VLAN tag in the packet.
And packets transmitted by applications running on the
base LAN device (EWA in the example above) will not
include a VLAN tag.
Page 32
Images Affected:
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW5700.EXE
5.2.22.2 CLDs, and QARs reporting this problem:
5.2.22.2.1 CLD(s)
None.
5.2.22.2.2 QAR(s)
None.
5.2.22.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.22.4 Work-arounds:
None.
5.2.23 Conservation of Blank Lines, LANCP Utility
5.2.23.1 Problem Description:
When LANCP is used to extract counters and other
information, without keyboard input, LANCP may print an
extra blank line. The blank line is present because of a
call to SMG$CREATE_KEYBOARD which establishes a recall
buffer.
LANCP has been modified to avoid the call to
SMG$CREATE_KEYBOARD until keyboard input is actually
needed, thus preventing the display of the extraneous
blank line.
Images Affected:
- [SYSEXE]LANCP.EXE
Page 33
5.2.23.2 CLDs, and QARs reporting this problem:
5.2.23.2.1 CLD(s)
QXCM1000742251
5.2.23.2.2 QAR(s)
None.
5.2.23.3 Release Version of OpenVMS that will contain
this change:
Post V8.3-1H1
5.2.23.4 Work-arounds:
None.
5.2.24 MOP Downline Load Settings Lost After Upgrade, LANCP
Utility
5.2.24.1 Problem Description:
After upgrading to OpenVMS V8.3, MOP Downline Load
settings in the LANCP permanent device database do not
work. They can be seen by a LANCP LIST DEVICE/MOP
command but fail to take effect during system startup.
Doing a LANCP CONVERT DEVICE does not correct the
problem.
When LANACP reads an older version of the LAN permanent
device database (LAN$DEVICE_DATABASE.DAT), it
automatically converts the data to the current version.
However, the prior code depended on the record size of
each new version to be larger than the previous versions.
The device record size in V8.3 shrank, causing a silent
RMS RTB error. Also, the latest version contains a set
of "valid" bits that signify if a device parameter was
valid in the record. The MOPDLL "valid" bits were not
being set for older database.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
Page 34
5.2.24.2 CLDs, and QARs reporting this problem:
5.2.24.2.1 CLD(s)
QXCM1000310355
5.2.24.2.2 QAR(s)
None.
5.2.24.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.24.4 Work-arounds:
None.
5.2.25 LAN Failover Set Definition Lost After Upgrade, LANCP
Utility
5.2.25.1 Problem Description:
LAN Failover sets that are defined in the LAN Permanent
Device Database in prior versions of OpenVMS are not
properly read and configured in OpenVMS Version 8.3.
Moreover, executing a LANCP CONVERT DEVICE command does
not correct the problem.
As the LANCP device database has evolved, it has become
necessary for LANCP and LANACP to identify the version of
the database it is reading in order to properly interpret
it. Record size has been used to identify the version,
and the code has assumed that the record size will always
increase in size with each new version. In OpenVMS
Version 8.3, the record size shrank, causing the
information at the end of previous version records to be
lost because the input buffer is too small.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
Page 35
5.2.25.2 CLDs, and QARs reporting this problem:
5.2.25.2.1 CLD(s)
QXCM1000385682
5.2.25.2.2 QAR(s)
None.
5.2.25.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.25.4 Work-arounds:
None.
5.2.26 System Crash When No LAN Devices Configured, LANACP
Utility
5.2.26.1 Problem Description:
When a system is booted without DECnet-Plus installed and
with no LAN devices configured (system parameter NOAUTO
is 1 and SYSMAN has not been used to configure any
devices), the system may crash if the system manager
attempts to start the LANACP process using the usual
command procedure SYS$STARTUP:LAN$STARTUP.COM.
Images Affected:
- [SYSEXE]LANACP.EXE
5.2.26.2 CLDs, and QARs reporting this problem:
5.2.26.2.1 CLD(s)
QXCM1000402325
5.2.26.2.2 QAR(s)
None.
Page 36
5.2.26.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.26.4 Work-arounds:
None.
5.2.27 Problem Purging Devices, LANCP Utility
5.2.27.1 Problem Description:
Under some conditions, purging all devices from the LAN
Permanent Device Database may cause the LANCP image to
hang, requiring a Control-C, or Control-Y to terminate
LANCP. Once terminated, LANCP can be rerun to purge
devices individually until all have been purged.
The LANCP command is:
MC LANCP PURGE DEVICE/ALL
Images Affected:
- [SYSEXE]LANCP.EXE
5.2.27.2 CLDs, and QARs reporting this problem:
5.2.27.2.1 CLD(s)
None.
5.2.27.2.2 QAR(s)
None.
5.2.27.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.27.4 Work-arounds:
Control-Y.
Page 37
5.2.28 Problem Configuring Virtual Devices, LANACP Utility
5.2.28.1 Problem Description:
Only the last Logical LAN (LL) or VLAN (VL) device
present in the LAN permanent device database is
configured when LANACP is started. For example, if LLA,
LLB, VLA, VLB were defined in the LAN permanent device
database, only VLB would be configured on LANACP startup.
This has been correct so all devices are configured.
Images Affected:
- [SYSEXE]LANACP.EXE
5.2.28.2 CLDs, and QARs reporting this problem:
5.2.28.2.1 CLD(s)
None.
5.2.28.2.2 QAR(s)
None.
5.2.28.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.28.4 Work-arounds:
Any missing virtual devices may be configured one at a
time after the system has been booted and LANACP has
configured the remaining devices.
5.2.29 LAN SDA Extension
5.2.29.1 Problem Description:
The LAN SDA extension, LAN$SDA, displays additional LAN
related data and is normally included in LAN kits because
any change the the LAN drivers may need an update to the
SDA extension.
In addition to this need to include LAN$SDA in this kit,
some changes to the Intel 82558/82559 driver,
SYS$EIDRIVER, have not been reflected in the SDA
extension properly. This has been corrected, so LAN SDA
commands that select the DE600 and other Intel
82558/82559 devices are displayed correctly.
Page 38
Images Affected:
- [SYSLIB]LAN$SDA.EXE
5.2.29.2 CLDs, and QARs reporting this problem:
5.2.29.2.1 CLD(s)
None.
5.2.29.2.2 QAR(s)
None.
5.2.29.3 Release Version of OpenVMS that will contain
this change:
Next release of OpenVMS for Integrity Servers after
V8.3-1H1
5.2.29.4 Work-arounds:
None.
5.2.30 MCR NCL SHOW CSMA-CD Port * All Induced System Crash
5.2.30.1 Problem Description:
Issuing the following NCL command may cause a system
crash. This can only be done by a privileged user on a
system where a large number of multicast addresses has
been enabled.
MCR NCL SHOW CSMA-CD PORT * ALL
Note that this problem is listed incorrectly as a denial
of service vulnerability at
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-5241, with
the idea that someone could intentionally issue this
command remotely or without privileges. In fact, the
command can only be done by a privileged user on the
system. Without access to the system and without
privileges, it is impossible to crash the system with
this command.
Images Affected:
- [SYS$LDR]NET$CSMACD.EXE
Page 39
5.2.30.2 CLDs, and QARs reporting this problem:
5.2.30.2.1 CLD(s)
QXCM1000435837
5.2.30.2.2 QAR(s)
None.
5.2.30.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.30.4 Work-arounds:
None.
5.2.31 User Application Does Not Receive Packets, QIO
5.2.31.1 Problem Description:
A user channel appears have started up correctly but will
not receive any packets.
When a user program starts a channel to a LAN device, the
P2 buffer specified in the SETMODE startup request
contains a 2-byte protocol type in a 4-byte parameter
value field. If the user program supplies a value,
sign-extended from 2 to 4 bytes, and if that protocol
type value has the high bit set, the resulting 4 byte
parameter value contains ones in the high order 2 bytes
of the 4 byte field. The LAN driver then extracts the
entire 4 bytes to use for the protocol type when it
should only extract 2 bytes.
The 2 byte protocol type in receive packets, will not
match the 4 byte protocol value recorded by the LAN
driver on behalf of the channel, preventing the channel
from receiving packets.
Images Affected:
- [SYS$LDR]SYS$LAN_CSMACD.EXE
- [SYS$LDR]SYS$LAN_FDDI.EXE
Page 40
5.2.31.2 CLDs, and QARs reporting this problem:
5.2.31.2.1 CLD(s)
None.
5.2.31.2.2 QAR(s)
None.
5.2.31.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.31.4 Work-arounds:
None.
5.2.32 SDA LAN HELP Command Terminates SDA, SDA Utility
5.2.32.1 Problem Description:
Entering a LAN HELP command in SDA can result in an error
and termination of SDA.
$ ANALYZE/SYSTEM
OpenVMS system analyzer
SDA> LAN HELP
%CLI-F-SYNTAX, error parsing 'ADDRESS'
-CLI-E-ENTNF, specified entity not found in command tables
$
Images Affected:
- [SYSLIB]LAN$SDA.EXE
5.2.32.2 CLDs, and QARs reporting this problem:
Page 41
5.2.32.2.1 CLD(s)
QXCM1000377158
5.2.32.2.2 QAR(s)
None.
5.2.32.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.32.4 Work-arounds:
None.
5.2.33 SHOW DEVICE DSA Command ACCVIO, SDA Utility
5.2.33.1 Problem Description:
After installation of the VMS83I_LAN-V0300 patch kit, a
SHOW DEVICE DSA command within SDA will result in an
ACCVIO of SDA. The SDA image is exited and the user is
returned to DCL.
Images Affected:
- [SYSLIB]SDA$SHARE.EXE
5.2.33.2 CLDs, and QARs reporting this problem:
5.2.33.2.1 CLD(s)
QXCM1000371368
5.2.33.2.2 QAR(s)
75-109-1287
5.2.33.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
Page 42
5.2.33.4 Work-arounds:
None.
5.2.34 Bad VLAN/Logical LAN Configuration May Crash a System,
VLAN and Logical LAN Drivers
5.2.34.1 Problem Description:
The system may crash if a VLAN device is created on a LAN
device which is not a Logical LAN device, and then the
same LAN device is entered into a LAN Failover set for
use as a LAN Failover device.
Images Affected:
- [SYS$LDR]SYS$LLDRIVER.EXE
- [SYS$LDR]SYS$VLANDRIVER.EXE
5.2.34.2 CLDs, and QARs reporting this problem:
5.2.34.2.1 CLD(s)
None.
5.2.34.2.2 QAR(s)
None.
5.2.34.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.34.4 Work-arounds:
None.
5.2.35 System Hang On Boot, VLAN and Logical LAN Drivers
5.2.35.1 Problem Description:
When starting DECnet Phase IV and TCP/IP on a VLAN device
defined using a LAN Failover device, the system may hang
at this point in the system startup procedure, especially
if the DECnet startup procedure STARTNET.COM is executed
in SYSTARTUP_VMS.COM instead of through a batch queue.
Page 43
When DECnet Phase IV starts and attempts to change the
MAC address to the DECnet address, the duplicate address
test done to validate the prospective address hangs.
Since the duplicate address test never completes, DECnet
never starts up and the DECnet startup procedure does not
complete.
This failure only occurs when the LAN failover device
does not contain any active devices, i.e., the LAN
failover set includes only LAN devices that were not
connected to the network. In this case, it is not
possible to do a duplicate address test because there is
no underlying LAN device.
Images Affected:
- [SYS$LDR]SYS$VLANDRIVER.EXE
5.2.35.2 CLDs, and QARs reporting this problem:
5.2.35.2.1 CLD(s)
QXCM1000384770
5.2.35.2.2 QAR(s)
None.
5.2.35.3 Release Version of OpenVMS that will contain
this change:
V8.3-1H1
5.2.35.4 Work-arounds:
None.
6 PROBLEMS ADDRESSED IN PREVIOUS KITS
Problems addressed by previously released VMS83I_LAN patch kits can
be found in the following files:
o VMS83I_LAN-V100.RELEASE_NOTES
o VMS83I_LAN-V200.RELEASE_NOTES
o VMS83I_LAN-V300.RELEASE_NOTES
o VMS83I_LAN-V400.RELEASE_NOTES
Page 44
o VMS83I_LAN-V500.RELEASE_NOTES
o VMS83I_LAN-V600.RELEASE_NOTES
o VMS83I_LAN-V700.RELEASE_NOTES
Before kit installation, these files can be extracted from the kit
via the following commands:
o To extract all release notes files at once use:
PRODUCT EXTRACT RELEASE_NOTES VMS83I_LAN /VERSION=V8.0 -
[/file=destination_directory]
o To extract a single release notes file use:
PRODUCT EXTRACT FILE VMS83I_LAN /VERSION=V8.0 -
/SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory]
The names of individual RELEASE_NOTES files in the kit can be
found with:
PRODUCT LIST VMS83I_LAN /VERSION=V8.0 /SELECT = *.RELEASE_NOTES
7 FILES PATCHED OR REPLACED:
o [SYSLIB]LAN$SDA.EXE (new image)
Image Identification Information
Image name: "LAN$SDA"
image file identification: "X-52"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:35.74
Overall Image Checksum: 3626078080
o [SYSEXE]LANACP.EXE (new image)
Image Identification Information
Image name: "LANACP"
image file identification: "X-25"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:29.0
Overall Image Checksum: 3514197045
o [SYSEXE]LANCP.EXE (new image)
Image Identification Information
Image name: "LANCP"
Page 45
image file identification: "X-87"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:28.73
Overall Image Checksum: 1751752700
o [SYS$LDR]NET$CSMACD.EXE (new image)
Image Identification Information
Image name: "NET$CSMACD"
image file identification: "X-17"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:28.06
Overall Image Checksum: 1317373172
o [SYSLIB]SDA$SHARE.EXE (new image)
Image Identification Information
Image name: SDA$SHARE"
image file identification: "X-1"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:20.30
Overall Image Checksum: 2515997348
o [SYS$LDR]SYS$EI1000.EXE (new image)
Image Identification Information
Image name: "SYS$EI1000"
image file identification: "X-37"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:31.95
Overall Image Checksum: 3341943414
o [SYS$LDR]SYS$EI1000_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EI1000_MON"
image file identification: "X-35"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:32.54
Overall Image Checksum: 3654504532
o [SYS$LDR]SYS$EIDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$EIDRIVER"
image file identification: "X-54"
image file build identification: "XBCA-00800700051"
Page 46
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:38.62
Overall Image Checksum: 3207276152
o [SYS$LDR]SYS$EIDRIVER_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EIDRIVER_MON"
image file identification: "X-54"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:38.91
Overall Image Checksum: 2737869428
o [SYS$LDR]SYS$EIGBTDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$EIGBTDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-00800700020"
linker identification: "Linker T02-28"
Link Date/Time: 15-OCT-2007 12:02:02.86
Overall Image Checksum: 1732294569
o [SYS$LDR]SYS$EW1000A.EXE (new image)
Image Identification Information
Image name: "SYS$EW1000A"
image file identification: "X-69"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:33.66
Overall Image Checksum: 1405754571
o [SYS$LDR]SYS$EW1000A_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EW1000A_MON"
image file identification: "X-69"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:34.09
Overall Image Checksum: 652592
o [SYS$LDR]SYS$EW5700.EXE (new image)
Image Identification Information
Image name: "SYS$EW5700"
image file identification: "X-79"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:30.99
Page 47
Overall Image Checksum: 1466487008
o [SYS$LDR]SYS$EW5700_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EW5700_MON"
image file identification: "X-79"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:31.30
Overall Image Checksum: 3139692267
o [SYS$LDR]SYS$EWDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$EWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:21.99
Overall Image Checksum: 3795547794
o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image)
Image Identification Information
Image name: "SYS$EWDRIVER_DE500BA"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:24.49
Overall Image Checksum: 2424862029
o [SYS$LDR]SYS$EWXFRAME.EXE (new image)
Image Identification Information
Image name: "SYS$EWXFRAME"
image file identification: "X-28"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:33.19
Overall Image Checksum: 1230099641
o [SYS$LDR]SYS$EWXFRAME_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EWXFRAME_MON"
image file identification: "X-28"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:33.94
Overall Image Checksum: 3596239942
Page 48
o [SYS$LDR]SYS$FWDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$FWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:23.93
Overall Image Checksum: 1924690643
o [SYS$LDR]SYS$LAN.EXE (new image)
Image Identification Information
Image name: "SYS$LAN"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:15.08
Overall Image Checksum: 2973092216
o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image)
Image Identification Information
Image name: "SYS$LAN_CSMACD"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:17.85
Overall Image Checksum: 3816417884
o [SYS$LDR]SYS$LAN_FDDI.EXE (new image)
Image Identification Information
Image name: "SYS$LAN_FDDI"
image file identification: "X-5"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:20.02
Overall Image Checksum: 2354498779
o [SYS$LDR]SYS$LLDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$LLDRIVER"
image file identification: "X-28"
image file build identification: "XBCA-0080070051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:34.40
Overall Image Checksum: 3853831084
Page 49
o [SYS$LDR]SYS$VLANDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$VLANDRIVER"
image file identification: "X-16"
image file build identification: "XBCA-00800700051"
linker identification: "Linker T02-28"
Link Date/Time: 11-JAN-2008 11:16:25.54
Overall Image Checksum: 645750774
o [SYSHLP]LANCP$HELP.HLB (new file)
o [SYSEXE]SYS$CONFIG.DAT (new file)
8 INSTALLATION INSTRUCTIONS
8.1 Test/Debug Image Loss
In the course of debugging problems reported to OpenVMS
Engineering, customers may be given debug or point-fix images to
install. Typically, these images do not have the same image
generation flags contained in images released via the OpenVMS
remedial patch process. Because of this, any debug or point-fix
image that is in the SYS$COMMON area, will be replaced by any image
of the same name installed by this kit. If this occurs, you will
lose any functionality that is provided by the replaced image. If
you wish to retain these debug or point-fix images, you can take
the following steps:
o Prior to installing this kit, move the test/debug image(s) to
be saved to the SYS$SPECIFIC area.
o During kit installation, you will be asked if you wish to
delete the image(s) in SYS$SPECIFIC. You should answer NO for
each image that you want to keep.
o After installation completes, but before rebooting the system
(if required), move the image(s) from SYS$SPECIFIC back to
SYS$COMMON.
8.2 Compressed File
This kit is provided as a Self Extracting ZIPEXE kit. To expand
this file to the installable .PCSI file, run the file with the
following command:
$ RUN VMS83I_LAN-V0800.ZIPEXE
Page 50
8.3 Installation Command
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:
PRODUCT INSTALL VMS83I_LAN[/SOURCE=location of Kit]
Note that this kit will install with the /SAVE_RECOVERY_DATA option
turned on. Using this qualifier will allow easy removal of the kit
from the system in the event of problems. If you wish to disable
this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the
PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is
optional but highly recommended. Using this qualifier will allow
easy removal of the kit from the system in the event of problems.
The kit location may be a tape drive, CD, or a disk directory that
contains the kit. The /SOURCE qualifier is not needed if the
PRODUCT INSTALL command is executed from the same directory as the
kit location.
Additional help on installing PCSI kits can be found by typing HELP
PRODUCT INSTALL at the system prompt.
8.4 Scripting of Answers to Installation Questions
During installation, this kit will ask and require user response to
several questions. If you wish to automate the installation of
this kit and avoid having to provide responses to these questions,
you must create a DCL command procedure that includes the following
logical name definitions and commands:
o To avoid the BACKUP question, define the following:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
o To avoid the REBOOT question, define the following:
$ DEFINE/SYS NO_ASK$REBOOT TRUE
o To save replaced files as *.*_OLD define the following logical
name as YES. If you do not wish to save replaced files, define
the logical name as NO. Note that if you use the
/SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT
INSTALL command all replaced files will be saved as part of
that operation. There is no need to also save files as
*.*_OLD:
$ DEFINE/JOB ARCHIVE_OLD NO
o Add the following qualifiers to the PRODUCT INSTALL command and
add that command to the DCL procedure.
/PROD=HP/BASE=I64VMS/VER=V8.0 [/SOURCE=location of Kit]
Page 51
o De-assign the logical names assigned
For example, a sample command file to install the VMS83I_LAN-V0800
kit would be:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ DEFINE/JOB ARCHIVE_OLD NO
$!
$ PROD INSTALL VMS83I_LAN/PRODUCER=HP/BASE=I64VMS/VER=V8.0"
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
$!
9 COPYRIGHT AND DISCLAIMER:
(C) Copyright 2008 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or its
subsidiaries 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.
Neither HP nor any of its subsidiaries shall be liable for
technical or editorial errors or omissions contained herein. The
information in this document is provided "as is" without warranty
of any kind and is subject to change without notice. The
warranties for HP products are set forth in the express limited
warranty statements accompanying such products. Nothing herein
should be construed as constituting an additional warranty.
DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY
THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL
EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR
PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE
FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH
MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.
-= END =-
|
|