|
|
HP Services Software Patches - vaxdriv05_061
|
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
*OpenVMS] VAXDRIV05_061 VAX V6.1 PADRIVER/PEDRIVER ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: PADRIVER.EXE
PEDRIVER.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXDRIV05_061
ECO Kits Superseded by This ECO Kit: VAXLAVC01_061 for OpenVMS
VAX V6.1 *ONLY*
ECO Kit Approximate Size: 252 Blocks
Kit Applies To: OpenVMS VAX V6.1
System/Cluster Reboot Necessary: Yes
Installation Rating: 3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for PADRIVER and PEDRIVER on OpenVMS VAX V6.1.
This kit addresses the following problems:
Problems Addressed in the VAXDRIV05_061 Kit:
o Adapters such as the KFESA restart and log "Invalid Buffer
Name" errors. INVALID BUFFER NAME errors are a known issue
that occur as a result of an incompatibility (or "race
condition" as mentioned in the original case text) in certain
hardware where there is a different perception of when a DSSI
packet has been "received" as good. If a reset occurs during
this time (before BUS FREE), the initiator will resend the
packet to the target that has already accepted the packet as
"good". If the resent packet is the last in a buffered data
transfer, the re-transmit attempt may not occur until after the
target has invalidated its buffer descriptor resulting in the
error.
This appears to happen in systems at times of heavy I/O
activity.
o Any message which is received with an SCS$W_STATUS field of 0
will cause OpenVMS to crash. This situation will not occur
very often. It is basically caused by non-compliance to SCS
specifications or by errors in firmware.
Problems Addressed in the VAXLAVC01_061 ECO Kit for OpenVMS VAX V6.1:
o Nodes in an LAVC (Local Area VAX Cluster) may CLUEXIT bugcheck
in mixed ENET/FDDI environments where duplicate hello messages are
being produced (i.e., out-of-rev bridge firmware).
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system must
be rebooted. If the system is a member of a VMScluster, the entire
cluster should be rebooted.
Files on this server are as follows:
|
»vaxdriv05_061.README
»vaxdriv05_061.CHKSUM
»vaxdriv05_061.CVRLET_TXT
»vaxdriv05_061.a-dcx_vaxexe
|