|
|
 |
HP Services Software Patches - alpdriv21_062
|
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.
Copyright (c) Compaq Computer Corporation 1996, 1999. All rights reserved.
Modification Date: 23-JUN-99
Modification Type: Updated Kit: Supersedes ALPDRIV20_062
PRODUCT: OpenVMS Alpha
COMPONENTS: SYS$DUDRIVER.EXE
SYS$TUDRIVER.EXE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ALPDRIV21_062
ECO Kits Superseded by This ECO Kit: ALPDRIV20_062
ALPDRIV16_062
ALPDRIV15_062
ALPDRIV11_062
ALPDRIV08_062
ALPDRIV07_062
ALPDRIV04_070 (For V6.2* Only)
ALPDRIV03_070 (For V6.2* Only)
ALPDRIV02_070 (For V6.2* Only)
ALPDRIV01_070 (For V6.2* Only)
AXPDRIV01_062 (AXPDRIV)
ECO Kit Approximate Size: 612 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
ALPCLUSIO01_062
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for SYS$DUDRIVER.EXE and SYS$TUDRIVER.EXE on OpenVMS
Alpha V6.2 through V6.2-1H3. This kit addresses the following problems:
Problems Addressed in ALPDRIV21_062:
o When the ALPDRIV20_062 kit is installed, a regression
warning is issued and the SYS$DUDRIVER.EXE image is not
installed.
Image(s) Affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
Problems/Issues addressed in ALPDRIV20_062:
The two primary deliverables in this kit are:
1. A number of backported fixes from the V7.2 stream which keeps
V6.2 and V7.1 code consistent with the V7.2 release. This
proactively delivers fixes that were found during V7.2 regression
testing (some of these problems were also reported by customers).
2. The ability to mount and use Fibrechannel devices from V6.2 and
V7.1 systems.
Problems addressed in the ALPDRIV11_071 kit:
o When initializing a FIBRECHANNEL (DG) device from a client,
one of the two following errors is returned to the user (disk
only, not tape):
1. INIT-F_DIAGPACK, disk is a diagnostic pack; or
2. INIT-W-NOBADDATA, bad block data not found on volume
Note that an INIT of the same devices succeeds on the server.
Image(s) affected: [SYS$LDR]SYS$DUDRIVER.EXE
o The following describes conditions that may cause crashes:
1. During a virtual circuit failover event, DUDRIVER
attempts to use the CDT of another connection, for
example, the SCS$DIRECTORY, and this results in a
crash.
2. DUDRIVER will now detect that a CDRP has a zero
CDRP$L_UCB field, thereby preventing a system crash.
3. A failover when a device has two paths (one served
and one local) may result in a fatal MSCPCLASS bugcheck
error.
4. When an MSCP server loses connection to the local MSCP
device, a SHADDETINCON crash may ocur and the shadowset
member will be remvoed from the shadow set.
Image(s) affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o Potential performance problems may occur (high interrupt stack
time) on low end systems in large cluster configurations, when
drives go offline.
Image(s) affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o DUDRIVER/TUDRIVER device allocation class processing problems
can occur during failover and configuration.
1. Drives may be incorrectly configured multiple times as
separate devices with the same name on different paths.
2. Invalid data structures can be seen for DUDRIVER-based
devices with unusual (32-bit number) ALLOCLASSes, which
are not valid for any devices on the system.
3. Systems may crash upon receipt of "Duplicate Unit" MSCP
messages from a HSx controller. The foot print will be
an inconsistent I/O Database or ACCVIO.
Image(s) affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o The MOUNT and INIT commands can fail with an MEDOFL error.
Image(s) affected: [SYS$LDR]SYS$TUDRIVER.EXE
o Incorrect byte count in IRP/IOST may occur when a forced error
on a disk is encountered.
Image(s) affected: [SYS$LDR]SYS$DUDRIVER.EXE
o A DCL copy command to a tape drive connected to a HSD05/10
can cause a process hang. This problem will not happen with a
BACKUP command and will not happen on HSJ/HSC connected tape
drives.
Image(s) affected: [SYS$LDR]SYS$TUDRIVER.EXE
Problems Addressed in the ALPDRIV16_062 Kit:
o The ALPDRIV15_062 remedial kit required that the ALPCLUSIO01_062
kit be installed. If the user tried to install the ALPDRIV15_062
kit on a system that had both the ALPCLUSIO01_062 and OpenVMS
Alpha Y2K remedial kits installed, the ALPDRIV15_062 kit did not
recognize that the ALPCLUSIO01_062 kit had been installed. This
caused the ALPDRIV15_062 installation to fail.
There are no new ECO problem corrections in this kit. If you
have installed the ALPDRIV15_062 remedial kit, you do not need
to install the ALPDRIV16_062 remedial kit.
Problems Addressed in the ALPDRIV15_062 Kit:
o Attempting to perform a directory of a mounted tape causes the
process to hang and "INVALID COMMAND" MSCP END MSG* errorlog
entries to be generated.
o Unexpected end messages are logged on client nodes for GUS and
AVAILABLE commands.
o When SCSI disks connected to a HSxx controller are set
transportable, the system crashes with a DISKCLASS bugcheck.
o DUDRIVER does not FLUSH the pending queue of SHADOWING, HBR and
served IOs when connection failure routines are entered. This
causes a system/cluster hang.
o System crashes with a KERNEL STACK INVALID Bugcheck.
o A DCL copy command to a HSD05/10-based tape drive causes a
process hang.
o Starting with OpenVMS Alpha V7.1, the BACKUP and COPY utilities
will fail with "blank check" and "end of data" errors when
these utilities are used with certain newer tape drives (e.g.,
TLZ10) connected to HSJ or HSD controllers.
Problems Addressed in the ALPDRIV11_062 Kit:
o If a customer upgraded their system to V6.2 from V6.1, the
KITINSTAL.COM procedure in kits that require the ALPCLUSIO01
remedial kit to be installed first, did not properly verify
that the ALPCLUSIO01_062 remedial kit had been installed.
Problems Addressed in the ALPDRIV08_062 Kit:
o The ALPDRIV07_062 had incorrect build identifications within
the images which could have prevented the images from being
installed. This kit ALPDRIV08_062 fixes that problem.
Problems Addressed in the ALPDRIV07_062 Kit:
o The following problem was also addressed in the ALPDRIV04_070
kit, but was omitted from the SYS$DUDRIVER.EXE which was
shipped in the ALPCLUSIO01_062 kit. Customers must install
ALPCLUSIO01_062 on any Alpha V6.2 system before installing this
ALPDRIV07_062 kit.
A problem exists with HSJ/HSD30,40 and 50 controllers. After
some event that initiates Mount verification, a Pack-Ack will
fail to complete. The controller will report that it is
making progress on the command, but will never finish. This
causes all IO to the affected devices to be hung. The problem
has been seen mostly with the ONLINE component of a Pack-Ack.
One case of a NOP hanging has been seen. It is not known
whether other IOs including Data Transfer IOs may be involved.
o A 9TRK tape written with a density of 6250 is mounted on a TSZ07
tape drive. The mount completes successfully and this is followed
by a DCL directory command. When a Pack-Ack is issued for the tape
unit, the subsequent ONLINE command is issued using "stale" density
information. This ONLINE command is then rejected by the controller
with "INVALID COMMAND, INVALID FORMAT" errors and the process will
hang. The error count then continues to increment as the driver
keeps issuing the ONLINE command.
In the TUDRIVER routine, START_PACKACK, a GUS-ONLINE-GUS sequence
is issued to the tape unit. The initial GUS is skipped unless
the drive is a DLT type or if the UCB$V_TU_DENS_DETERMINED bit
is set in DEVSTS in the UCB. If a GUS is issued before the
ONLINE command, the density gets updated and the ONLINE succeeds.
o The operating system may crash with the following error:
"TMSCPSERV, Fatal error detected by TMSCP server"
This crash will only be seen if an MSCP-served tape device requires
mount verification.
The actual location of the crash is SCS$TAPE_MSCP_MV_C+00190.
Problems Addressed in the ALPDRIV04_070 Kit for OpenVMS Alpha V6.2*:
o A problem exists with HSJ/HSD 30, 40 and 50 controllers. After some
event that initiates Mount verification, a Pack-Ack will fail to
complete. The controller will report that it is making progress on
the command, but will never finish. This causes all IO to the
affected devices to be hung.
Problems Addressed in the ALPDRIV03_070 Kit for OpenVMS Alpha V6.2*:
o The system experiences repetitive Volume Processing Messages on Host
Based Volume Shadowing Disks. The CDDB$W_RSTRTCNT field of the
member devices will be incrementing as seen in the REINIT Count
field under SDA.
Problems Addressed in the ALPDRIV02_070 Kit for OpenVMS Alpha V6.2*:
o If the connection to the quorum disk is broken it can result in
quorum loss for the cluster. In this case, re-establishing the
connection to the quorum disk may not restore quorum for all nodes.
This could result in nodes being hung waiting for quorum.
Problems addressed in the ALPDRIV01_070 kit for OpenVMS Alpha V6.2*:
o The CDDB$W_LOAD_AVAIL field is loaded with an incorrect value which
prevents "static" load balancing working as implemented.
o System crash in DUDRIVER. Usually in FUNCTION_EXIT but it may occur
at other places.
o The errorlog does not contain any information on the actual command
that has timed out from a Get Command Status (GCS) command.
o Host Based Shadowset Virtual Units hang in Mount verification all IO
to the device is stalled.
Problems Addressed in the AXPDRIV01_062 Kit:
o For systems that are members of a VMScluster system, and that have a
KFESA/KFESB EISA DSSI controller, failover of I/O traffic using the
PEDRIVER (ETHERNET) to the PADRIVER (DSSI) - now works correctly.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted.
If you have other nodes in your VMS 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.
|
Files on this server are as follows:
|
»alpdriv21_062.README
»alpdriv21_062.CHKSUM
»alpdriv21_062.CVRLET_TXT
»alpdriv21_062.a-dcx_axpexe
»alpdriv21_062.CVRLET_TXT
|
