Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS722_FIBRE_SCSI-V0400 Alpha V7.2-2 FibreChannel/SCSI ECO Summary
*OpenVMS] VMS722_FIBRE_SCSI-V0400 Alpha V7.2-2 FibreChannel/SCSI ECO Summary
New Kit Date: 09-MAY-2003
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Hewlett Packard Company 2001, 2002,2003. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: FibreChannel
SCSI Drivers
SOURCE: Hewlett Packard Company
ECO INFORMATION:
ECO Kit Name: VMS722_FIBRE_SCSI-V0400
DEC-AXPVMS-VMS722_FIBRE_SCSI-V0400--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS722_FIBRE_SCSI-V0300
ECO Kit Approximate Size: 16800 Blocks
Kit Applies To: OpenVMS Alpha V7.2-2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_2
2- To be installed by all customers using the following
feature(s):
Fibre Channel or SCSI Devices.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS722_UPDATE-V0100
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 FibreChannel and SCSI Drivers on OpenVMS Alpha
V7.2-2. This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS722_FIBRE_SCSI-V0400
o A BACKUP command from a client system to a TMSCP served
SCSI tape may complete with success, but the resulting
saveset cannot be read by BACKUP. For example:
$ INIT $7$MKC0: TEST0
$ MOUNT/FOREIGN $7$MKC0:
%MOUNT-I-MOUNTED, TEST0 mounted on _$7$MKC0: (UTRA41)
$ BACK/LOG TEST.TXT TP:TEST0/SAV
%BACKUP-S-COPIED, copied USER1:[USER]TEST.TXT;1
$ DISMOUNT/NOUNLOAD TP
$ MOUNT/FOREIGN TP
%MOUNT-I-MOUNTED, TEST0 mounted on _$7$MKC0: (UTRA41)
$BACK/LIST TP:
Listing of save set(s)
%BACKUP-F-LABELERR, error in tape label processing on
$7$MKC0:[000000].; -SYSTEM-W-ENDOFFILE, end of file
Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE
o This kit provides a utility that will allow customers to
update the firmware in an MSA1000 series Fibre SCSI raid
controller. The utility can also do some diagnostics.
Images Affected:[SYSHLP.UNSUPPORTED]MSA_UTIL.EXE
o FibreChannel storage (DG) disks fail over to the MSCP
path due to the local direct paths becoming permanently
inaccessible.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o A system with an LP89802 can crash with the following
error.
Crashdump Summary Information:
------------------------------
Bugcheck Type: MACHINECHK, Machine check while
in kernel mode
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.80011690
EXE$SYSTEM_CORRECTED_ERROR_C+00510
Failing PS: 20000000.00001F04
Module: SYS$CPU_ROUTINES_270F
(Link Date/Time: 20-NOV-2002 15:11:40.36)
Offset: 00003690
Failing Instruction:
EXE$SYSTEM_CORRECTED_ERROR_C+00510: BUGCHK
Stack Pointers:
KSP = FFFFFFFF.F0819C60 ESP = FFFFFFFF.F081B000
SSP = FFFFFFFF.F0805000 USP = FFFFFFFF.F0805000
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o FibreChannel storage fails to configure on boot.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o DIR-E-TAPEPOSLOST errors when can occur when a DIRECTORY
command is used on skip-filemark-capable tape drives.
Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE
o A system can hang when backing up files to and SDLT with
V35 or V46 firmware.
Crashdump Summary:
------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.80047904
EXE_STD$QUEUE_FORK_C+00084
Failing PS: 20000000.00001504
Module: SYSTEM_PRIMITIVES_MIN
Offset: 0001B904
Images Affected:[SYS$LDR]SYS$PKWDRIVER.EXE
o When restoring a multivolume saveset created with a
command similar to the following BACKUP command:
$ MOUNT/FOREIGN ALPHA3$MKD0:
$ BACKUP/IMAGE SY2:ALPHA3$MKD0:SY2_IMG/save_set/EXACT_ORDER
The restore operation fails because BACKUP is requesting
and waiting for the wrong tape to be loaded.
Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE
o SYS$PKSDRIVER.EXE has the ability to re-initialize the
KZPSA adapter when the the adapter indicates (via an
ADAPTER MISCELLANEOUS interrupt) that its firmware has
crashed. Under certain circumstances, this
re-initialization can fail and result in a system crash.
This is usually caused by a bad KZPSA module or other
hardware.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.803D51FC SYS$PKSDRIVER+031FC
Failing PS: 28000000.00000804
Module: SYS$PKSDRIVER (Link Date/Time:
17-MAR-2001 03:31:19.38)
Offset: 000031FC
Stack Pointers:
KSP = FFFFFFFF.B0881A28 ESP = FFFFFFFF.B06E7000
SSP = FFFFFFFF.B06D5000 USP = FFFFFFFF.B06D5000
Failing Instruction:
SYS$PKSDRIVER+031FC: LDQ R22,#X0010(R7)
Images Affected:[SYS$LDR]SYS$PKSDRIVER.EXE
o If a fibre channel device is power cycled or disconnected
from the fabric, OpenVMS may permanently lose access to
the device.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
PROBLEMS ADDRESSED IN VMS722_FIBRE_SCSI-V0300 KIT
o If a device is write protected after mount, then, a write
operation is attempted, then the device is un-write
protected, the device remains unwritable until it is
dismounted and remounted.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o If an IO operation failed setup_cmd due to a lack of
pool, a system could crash due to an ACCVIO in
SYSTEM_PRIMITIVES.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o After incurring a SCSI error, mount verification may not
start on the device when it should.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o A system LOW on pool may experience a crash due to an
ACCVIO bugcheck in SYSTEM_PRIMITIVES.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o An MSCP served IO can be sent to the target after
cancellation. This could cause corruption on devices
that are reachable via other nodes. The user would see
stale buffer corruption on MSCP-served disks when
experiencing network disruptions.
Images Affected:[SYS$LDR]SYS$PKADRIVER.EXE
[SYS$LDR]SYS$PKCDRIVER.EXE
[SYS$LDR]SYS$PKEDRIVER.EXE
[SYS$LDR]SYS$PKJDRIVER.EXE
[SYS$LDR]SYS$PKQDRIVER.EXE
[SYS$LDR]SYS$PKSDRIVER.EXE
[SYS$LDR]SYS$PKTDRIVER.EXE
[SYS$LDR]SYS$PKWDRIVER.EXE
[SYS$LDR]SYS$PKZDRIVER.EXE
o The user could see numerous "MEDIUM IS OFF LINE" errors
every time a Fibre Channel tape is initialized or used.
Images Affected:[SYS$LDR]SYS$PGADRIVER.EXE
o On write operations, RZ1EF-CB disk firmware reports an
incorrect transferred byte count. This results in
undetected disk corruption.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o A system can crash with a INVEXCEPTN, Exception while
above ASTDEL bugcheck
Crash Dump Summary
------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Image: $1$DGA510:[PRG]LPARTREQ.EXE;6
Failing PC: FFFFFFFF.80405E60
SYS$PGADRIVER+0BE60
Failing PS: 38000000.00000804
Module: SYS$PGADRIVER (Link Date/Time:
24-AUG-2001 00:12:20.64)
Offset: 0000BE60
Images Affected:[SYS$LDR]SYS$PGADRIVER.EXE
o When booting from a Fibre Channel disk, the system may
experience a boot hang
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o The user will see unnecessary console messages from
FGEDRIVER.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o Skip-by-filemark tape operations sometimes take
unacceptable amounts of time for skip counts of 1 or 2.
Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE
o This kit generally enhances the handling of Fibre Channel
tape bridges and in particular allows SCSI tapes to be
configured behind a Network Storage Router.
Images Affected:[SYSLIB]IOGEN$FIBRE_CONFIG.EXE
[SYSLIB]SMI$OBJSHR.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
o A system can crash with an INVEXCEPTN bugcheck
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above
ASTDEL
Current Process: STACONFIG
Current Image: STACONFIG.EXE
Failing PC: FFFFFFFF.80029F14
IOC$DEALLOC_CNT_RES_NOSYNC_C+00154
Failing PS: 20000000.00000B04
Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time:
28-MAR-2002 14:22:47.68)
Offset: 00001F14
Images Affected:[SYS$LDR]SYS$PKQDRIVER.EXE
o Disk drives that support the SCSI-3 SPC3 standard cannot
be mounted. When an attempt is made to mount such drives
the error log records "invalid inquiry" messages.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o During a hard reset the system can experience 64-byte LAL
corruption or an ACCVIO system crash.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o A boot/configuration hang can occur if an FGx device does
not come online.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o Storage is not detected when connected to a McData
switch.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
o The system can crash with a LOCKMGRERR, Error detected by
Lock Manager bugcheck:
Crashdump Summary Information (reformatted for space considerations):
------------------------------
Bugcheck Type: LOCKMGRERR, Error detected by Lock Manager
Current Image:
Failing PC: FFFFFFFF.80325F68 SYS$CLUSTER+1BF68
Failing PS: 38000000.00000804
Module: SYS$CLUSTER (Link Date/Time: 21-MAR-2001
16:53:58.69)
Offset: 0001BF68
General Registers:
R0 = 00000000.00002044
^^^^^^^^ %SYSTEM-F-INSFSPTS, insufficient
SPTEs available
R1 = 00000000.00000000
R2 = 00000000.00000000
S0/S1 Space Free PTEs
---------------------
MAPPED ADDRESS PTE ADDRESS
...
FFFFFFFF.816FC000 FFFFFEFD.FFE05BF0
PTE COUNT
0001FFE0.5C380000 00000003 <<<
MAPPED ADDRESS PTE ADDRESS
FFFFFFFF.8170E000 FFFFFEFD.FFE05C38
PTE COUNT
0001FFE0.5C980000 00000003 <<<
MAPPED ADDRESS PTE ADDRESS
FFFFFFFF.81726000 FFFFFEFD.FFE05C98
PTE COUNT
0001FFE0.5CC80000 00000003 <<<
MAPPED ADDRESS PTE ADDRESS
FFFFFFFF.81732000 FFFFFEFD.FFE05CC8
PTE COUNT
0001FFE0.5D280000 00000003 <<<
...
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o The user may see frequent mount verifications. These can
have several causes:
- Frequent quorum disk mount verification can occur
when the quorum disk has a relatively heavy I/O load
applied to it. This is not a problem when the quorum
disk is used as recommended,meaning with no
significant I/O load. However, in some customer
clusters this recommendation is ignored.
- Frequent TX/RX DMA failures can occur which result in
mount verifications.
Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
o During system boot, fibre channel storage devices may not
be configured.
Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database(s). To view these articles, open the appropriate
product database and perform a query using either of the following search
strings: 'VMS722_FIBRE_SCSI-V0400' or 'VMS722_FIBRE_SCSI'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
This kit requires a system reboot. 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.
INSTALLATION INSTRUCTIONS:
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 VMS722_FIBRE_SCSI /SOURCE=[location of Kit]
The kit location may be a tape drive, CD, or a disk directory that
contains the kit.
Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
Special Installation Instructions:
o 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 definitions
and commands:
- $ DEFINE/SYS NO_ASK$BACKUP TRUE
- $ DEFINE/SYS NO_ASK$REBOOT TRUE
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V4.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS722_FIBRE_SCSI-V0400 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS722_FIBRE_SCSI/PROD=DEC/BASE=AXPVMS/VER=V4.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| FC$CP.EXE | 90C367D4 | X-2 | 27-MAR-2003 |
| | | 00:55:49.92 |
+----------------------------+----------+-----------------+--------------+
| FC$SDA.EXE | 5C1890C5 | X-6A3A1B2 | 27-MAR-2003 |
| | | 00:55:47.76 |
+----------------------------+----------+-----------------+--------------+
| IOGEN$FIBRE_CONFIG.EXE | 87134628 | X-10A2A1 | 21-AUG-2002 |
| | | 14:04:09.02 |
+----------------------------+----------+-----------------+--------------+
| MSA_UTIL.EXE | EAE30DEE | X-1 | 27-MAR-2003 |
| | | 00:55:52.91 |
+----------------------------+----------+-----------------+--------------+
| SMI$OBJSHR.EXE | 0BF17CF2 | X40-A8 | 19-FEB-2003 |
| | | 10:20:57.46 |
+----------------------------+----------+-----------------+--------------+
| SYS$DKDRIVER.EXE | C7DA9F96 | X-12 | 27-MAR-2003 |
| | | 00:45:26.17 |
+----------------------------+----------+-----------------+--------------+
| SYS$FGEDRIVER.EXE | 02A7D74D | X-26A22A1A3A9 | 27-MAR-2003 |
| | | 00:55:16.85 |
+----------------------------+----------+-----------------+--------------+
| SYS$GKDRIVER.EXE | ACCB22C6 | X-40A1 | 27-MAR-2003 |
| | | 00:49:34.12 |
+----------------------------+----------+-----------------+--------------+
| SYS$MKDRIVER.EXE | 3DE02BF0 | X-12 | 27-MAR-2003 |
| | | 00:48:23.51 |
+----------------------------+----------+-----------------+--------------+
| SYS$PGADRIVER.EXE | 597E2238 | X-35A5A1A6 | 27-MAR-2003 |
| | | 00:54:55.47 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKADRIVER.EXE | C4D7877D | X-12A2 | 27-MAR-2003 |
| | | 00:54:31.32 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKCDRIVER.EXE | 02F46776 | X-3 | 27-MAR-2003 |
| | | 00:50:20.22 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKEDRIVER.EXE | 7CA77F35 | X-3 | 27-MAR-2003 |
| | | 00:51:12.90 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKJDRIVER.EXE | F92FBCAF | X-3 | 27-MAR-2003 |
| | | 00:51:45.46 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKQDRIVER.EXE | 27D8C587 | X-10A3 | 27-MAR-2003 |
| | | 00:53:53.10 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKSDRIVER.EXE | 07FF682F | X-3 | 27-MAR-2003 |
| | | 00:52:19.19 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKTDRIVER.EXE | B30A8000 | X-3 | 27-MAR-2003 |
| | | 00:52:59.76 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKWDRIVER.EXE | 02A8F2C6 | X-28 | 27-MAR-2003 |
| | | 00:54:06.55 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKZDRIVER.EXE | E9E2DA1A | X-3 | 27-MAR-2003 |
| | | 00:53:26.92 |
+----------------------------+----------+-----------------+--------------+
|
