Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS721_FIBRE_SCSI-V0600 Alpha V7.2-1 FibreChannel/SCSI ECO Summary
Copyright (c) Compaq Computer Corporation 2000, 2001, 2002. All rights reserved.
New Kit Date: 06-JUN-2002
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS721_FIBRE_SCSI-V0500
OP/SYS: OpenVMS Alpha
COMPONENT: FibreChannel
SCSI Drivers
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_FIBRE_SCSI-V0600
DEC-AXPVMS-VMS721_FIBRE_SCSI-V0600--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS721_FIBRE_SCSI-V0500
ECO Kit Approximate Size: 4720 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
To be installed by all customers.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this, or any required kit:
VMS721_PCSI-V0100
VMS721_UPDATE-V0300
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be installed:
VMS721_SYS-V1200
ECO KIT SUMMARY:
An ECO kit exists for FibreChannel and SCSI Drivers on OpenVMS Alpha
V7.2-1. This kit addresses the following problems:
NEW FUNCTIONALITY INTRODUCED IN VMS721FIBRE_SCSI-V0600 KIT:
o Interrupt and Response Coalescing is a functional option
implemented in KGPSA firmware which allows LP8000 and LP9002
adapters to reduce the number of interrupts seen by a host.
Given a response count and a delay time (in ms), the adapter
can defer interrupting the host until that number of responses
is available or until that amount of time has passed,
whichever occurs first. This also makes each interrupt seen
by the host more cost-effective because it will generally
process more responses per interrupt than without Interrupt
Coalescing.
Images Affected: [SYSHLP.UNSUPPORTED]FC$CP.EXE
[SYS$LDR]SYS$FGEDRIVER.EXE
[SYS$LDR]SYS$PGADRIVER.EXE
o Enabling Interrupt and Response Coalescing
You can turn on Interrupt and Response Coalescing with the
following command:
$ MCR SYS$ETC:FC$CP FGx <enables> [<delay ms>] -
$_ [<response count>]
- FGx : the type of FG device (FGA, FGB etc.). To
determine which FG devices are present, refer to the
section titled "Determining FGx Devices"
- <enables> : Enables bit 1 = Response Coalescing and bit 0
= Interrupt Coalescing.
- <delay ms> : Delay is in milliseconds and can range from
0 to 255 decimal.
- Response count can range from 0 to 63 decimal.
- Any negative value leaves a parameter unchanged.
- Values returned are those which are current after any
changes.
The recommended command is:
MCR SYS$ETC:FC$CP FGA 3 1 8
You should substitute FGA with whatever FG device you wish to
configure. The command must be run once per boot for every
Emulex FibreChannel adapter on which Interrupt Coalescing is
to be enabled. Once enabled it will persist across adapter
initializations, path switches, CPU affinity changes, etc., in
other words, until the next boot. Interrupt Coalescing can be
turned off by passing an "enables" value of 0.
o Determining FGx Devices
In order to tell which FGx device(s) you have on your system,
execute the following commands:
$ ANALYZE/SYSTEM
SDA>CLUE CONFIG/A
Following is an excerpt of an example of the output of the
above commands. Note that all fields are not included, only
those needed to determine adapter type.
Adapter Configuration:
----------------------
Port BusArrayEntry Device Name / HW-Id
---- ---------------- --------------------
FGA: FFFFFFFF.810FBC40 KGPSA-CA (Emulex LP8000)
FGB: FFFFFFFF.810FBC78 KGPSA-** (Emulex LP9000)
Interrupt and Response Coalesing will only operate on LP8000
and LP9002 adapters. If the device name is not listed you
will you will need to EXAMINE the BusArrayEntry entry to tell
whether the Adapter is an LP8000, LP9002 or an earlier type of
adapter. Following is an example of the EXAMINE command:
SDA> EXAMINE FFFFFFFF.810FBC40
FFFFFFFF.810FBC40: F80010DF.F80010DF "ß..øß..ø"
SDA> EXAMINE FFFFFFFF.810FBC78
FFFFFFFF.810FBC78: F90010DF.F90010DF "ß..ùß..ù"
The field F80010DF.F80010DF shows that the adapter is an
LP8000 adapter.
The field F90010DF.F90010DF shows that the adapter is an
LP9002 adapter.
PROBLEMS ADDRESSED IN VMS721_FIBRE_SCSI-V0600 KIT:
o When booting, a shadowed system disk can hang the cluster.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o If the system experiences bus starvation because of heavy IO
activity, there is a possibility that some IO will timeout and
reset the SCSI bus. This could result in Disk Mount Verifies.
Also, data corruption might occur during heavy IO Timeouts.
The IO Timeouts could be detected by looking for Error Type 4,
Subtype 1 in the Error Log,
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o When a Fibre Channel disk is being brought back online after a
controller failover, the user may see a variety of problems
ranging from process hangs and system hangs, to system crashes
with a variety of bugchecks. All systems using disks served
from the affected HSG controllers will be affected.
The nature of this problem is twofold:
o It completely shuts down the HSG controller. Anything
accessing that HSG will hang until their I/O times out.
This will cause any number of failures from all the disks
becoming unavailable.
o It consumes a number of resources on the systems. A crash
will result from what ever critical resource runs out
first.
If the wrong equilibrium is reached, the systems can appear to
hang indefinitely. It is possible, but not likely, that they
will recover with no intervention.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o If a non-clustered OpenVMS system, prior to V7.3, attempts to
mount a fibre channel disk with a persistent reservation on
it, the system will bugcheck with an "INVEXCEPTN, Exception
while above ASTDEL".
Persistent reservations can be on a disk from the SWCC program
or when the disk was mounted by a V7.3 OpenVMS release or
later. They can also be present from having the disk used by
a non-OpenVMS operating system that uses persistent
reservations.
Crashdump Summary
-----------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.802929C8 SYS$DKDRIVER+109C8
Failing PS: 38000000.00000804
Module: SYS$DKDRIVER
(Link Date/Time: 9-FEB-2001 08:51:21.81)
Offset: 000109C8
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o When a TLZ10 tape with an incorrect label is installed on a
789X SCSI adapter (KZPEA 7899 card or built-in 7895 card in a
DS20E), the user should receive a MEDOFL (Medium offline)
error. Instead, the user receives an incorrect DRVERR (Drive
Error) error.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o An INIT command, when used on SCSI tapes, can take 1/2 hour or
more to quit if no tape is in the unit. With this change, the
INIT command fails immediately when there is no media in the
drive.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o The system can crash with an "INCONSTATE, Inconsistent I/O
data base" bugcheck at SYS$FGEDRIVER+8C3C.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INCONSTATE,
Inconsistent I/O data base
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.802DAC3C SYS$FGEDRIVER+08C3C
Failing PS: 18000000.00000804
Module: SYS$FGEDRIVER
(Link Date/Time: 5-DEC-2001 14:41:56.69)
Offset: 00008C3C
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
[SYSLIB]FC$SDA.EXE
o The system can crash with a SSRVEXCEPT, Unexpected system
service exception" bugcheck.
Crashdump Summary Information:
------------------------------
Bugcheck Type: SSRVEXCEPT, Unexpected system service
exception
CPU Type: AlphaServer 2100 4/233
Failing PC: FFFFFFFF.801CB968
NSA$REFERENCE_RIGHTS_CHAIN_C+00008
Failing PS: 10000000.00000201
Module: SECURITY
(Link Date/Time: 5-AUG-2001 01:12:10.86)
Offset: 0000B96
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o Attempting to mount a TLZ09 gives a DRVERR error.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o After executing a HSV110 controller restart, the system loses
connection to the disks on the HSV110.
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
PROBLEMS ADDRESSED IN VMS721_FIBRE_SCSI-V0500 KIT:
o If an MCR SYMAN IO AUTO command is issued to hot add/ swap
SCSI targets, there is a possibility that a system can
experience a hang.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o A system can experience excessive SCSI bus resets due to
un-synchronized access to device registers.
Images Affected: [SYS$LDR]SYS$PKWDRIVER.EXE
o Tape Density values are not stored correctly. This causes
third party tape applications, such as Oracle's RMU backup
utility, to fail when performing multi-volume tape backup and
other operations which require the tape density to be stored
correctly.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o The system can hang due to IO's Timing Out, and the driver not
re-trying the IO command. The IO timeout can be detected
through the error log.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
o On OpenVMS Alpha clusters sharing a SCSI bus and attached to
the bus with KZPBA SCSI controllers, disks may not come out of
Mount Verify.
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o When performing multi-volume Backup (and various other Backup
operations involving label processing) with generic SCSI
tapes, compaction status gets turned off.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o Odd byte records read from tape to a memory buffer larger than
the tape record results in one extra byte of data.
Images Affected: [SYS$LDR]SYS$PKWDRIVER.EXE
o When an HSZ/HSG device reports mirror copy status events, the
ERRCNT of the device is incremented. This gives the false
impression that there is a problem with the device(s).
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o In a multiprocessor environment, exception conditions (such as
AUTOGEN, disk errors, power glitches, etc.) cause the
PKWDRIVER, the hardware interface, and the script code to
become un-synchronized relative to each other. This lack of
synchronization can cause excessive bus resets, mount verify
timeouts, command timeouts, I/O system hangs, system crashes
and/or file corruption. The most obvious problem is the
occurrence of SCSI bus resets. These can be seen with a "SHOW
ERROR" command and will be in the error log.
Images Affected: [SYS$LDR]SYS$PKWDRIVER.EXE
o Tape drive performance degrades significantly after a tape
error.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o If a disk is mounted software write protected, when the disk
enters and completes mount verification, the disk is software
write enabled.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o A system can crash with an INVEXCEPTN, Exception while above
ASTDEL bugcheck.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.802FB820 SCS$POLL_MODE_C+00460
Failing PS: 1C000000.00000804
Module: SYS$SCS (Link Date/Time:
9-DEC-2000 00:44:16.18)
Offset: 00005820
Images Affected: [SYS$LDR]SYS$PGADRIVER.EXE
o A system can experience CPUSPINWAIT Crashes. See Crash dump
summary below.
Crashdump Summary Information:
------------------------------
Bugcheck Type: CPUSPINWAIT, CPU spinwait timer
expired
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.80088384
SMP$TIMEOUT_C+00064
Failing PS: 18000000.00000804
Module: SYSTEM_SYNCHRONIZATION_MIN
(Link Date/Time: 26-MAY-2001 22:21:11.81)
Offset: 00000384
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o For 8MM tapes (for example Exabyte, TZK15), a COPY command to
a freshly initialized tape results in a fatal drive error
whenever the COPY command is issued on a TMSCP client node.
The error log will show that an Illegal Request has been sent
to the drive.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o Mounting CDs in the Yamaha CD-Writer CRW8424S results in a
'%MOUNT-F-FORMAT, invalid media format' error message.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o When booting, a shadowed system disk can hang the cluster.
Images Affected: [SYS$LDR]SYS$DKDRIVER.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: 'VMS721_FIBRE_SCSI-V0600' or 'VMS721_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. Compaq 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 VMS721_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 INSTALLATIONS 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=V6.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS721_FIBRE_SCSI-V0600 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS721_FIBRE_SCSI/PROD=DEC/BASE=AXPVMS/VER=V6.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 | 90C34674 | X-2 | 11-APR-2002 |
| | | 10:35:50.62 |
+----------------------------+----------+-----------------+--------------+
| FC$SDA.EXE | 6A6BB50C | X-6A3A1B1 | 11-APR-2002 |
| | | 10:35:48.48 |
+----------------------------+----------+-----------------+--------------+
| SMI$OBJSHR.EXE | 6542EB20 | X40-A8 | 15-AUG-2001 |
| | | 23:21:22.12 |
+----------------------------+----------+-----------------+--------------+
| SYS$DKDRIVER.EXE | E78624A2 | X-12 | 11-APR-2002 |
| | | 10:33:56.93 |
+----------------------------+----------+-----------------+--------------+
| SYS$FGEDRIVER.EXE | D84CE519 | X-26A22B2 | 11-APR-2002 |
| | | 10:35:36.71 |
+----------------------------+----------+-----------------+--------------+
| SYS$GKDRIVER.EXE | 0454FD19 | X-38B1 | 11-APR-2002 |
| | | 10:34:26.02 |
+----------------------------+----------+-----------------+--------------+
| SYS$MKDRIVER.EXE | C52203BD | X-12 | 11-APR-2002 |
| | | 10:34:17.24 |
+----------------------------+----------+-----------------+--------------+
| SYS$PGADRIVER.EXE | 780E0535 | X-35A5A1A3 | 11-APR-2002 |
| | | 10:35:31.00 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKADRIVER.EXE | D2E58FB3 | X-12A2 | 11-APR-2002 |
| | | 10:35:23.61 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKCDRIVER.EXE | E35B65B6 | X-3 | 11-APR-2002 |
| | | 10:34:34.64 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKEDRIVER.EXE | 1877BD95 | X-3 | 11-APR-2002 |
| | | 10:34:46.48 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKJDRIVER.EXE | 0AA25880 | X-3 | 11-APR-2002 |
| | | 10:34:52.22 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKQDRIVER.EXE | B82E7B34 | X-10A1 | 11-APR-2002 |
| | | 10:35:12.30 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKSDRIVER.EXE | BABEF440 | X-3 | 11-APR-2002 |
| | | 10:34:56.94 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKTDRIVER.EXE | FF390596 | X-3 | 11-APR-2002 |
| | | 10:35:02.21 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKWDRIVER.EXE | B5571F92 | X-27 | 11-APR-2002 |
| | | 10:35:17.72 |
+----------------------------+----------+-----------------+--------------+
| SYS$PKZDRIVER.EXE | A66BCECE | X-3 | 11-APR-2002 |
| | | 10:35:07.22 |
+----------------------------+----------+-----------------+--------------+
| SYSMSG.EXE | 156417F1 | X-3 | 22-OCT-2001 |
| | | 04:38:20.40 |
+----------------------------+----------+-----------------+--------------+
|
