|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: system PRIVILEGED account (root
stage1.cxo.cpqcorp.net)Date: Thu May 09 2002 - 02:30:04 CDT
*******************************************************************************
* *
* This is an update to an existing patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.2-2/dec-axpvms-vms722_fibre_scsi-v0200--4.README
*******************************************************************************
TITLE: OpenVMS VMS722_FIBRE_SCSI-V0200 Alpha V7.2-2 FibreChannel/SCSI ECO Summary
New Kit Date: 09-MAY-2002
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS722_FIBRE_SCSI-V0100
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname.pcsi-dcx_axpexe or
kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe. The
resultant file will be the PCSI installation file which can be
used to install the ECO.
Copyright (c) Compaq Computer Corporation 2001, 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: FibreChannel
SCSI Drivers
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS722_FIBRE_SCSI-V0200
DEC-AXPVMS-VMS722_FIBRE_SCSI-V0200--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS722_FIBRE_SCSI-V0100
ECO Kit Approximate Size: 1984 Blocks
Kit Applies To: OpenVMS Alpha V7.2-2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 : To be installed by all customers.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
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-V0200 KIT:
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: 0000B968
Images Affected: [SYS$LDR]SYS$FGEDRIVER.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, system hangs, and 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 two fold.
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 forever. It is possible, but not likely, that they will
also recover with no intervention.
Images Affected: [SYS$LDR]SYS$DKDRIVER.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 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 The system can crash with a INVEXCP bugcheck.
Crashdump Summary Information
-----------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
Failing PC: FFFFFFFF.80363B80 SYS$PKADRIVER+0BB80
Failing PS: 00000000.00001504
Offset: 0000BB80
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 with no media in the drive.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
NEW FUNCTIONALITY INTRODUCED IN VMS722_FIBRE_SCSI-V0100 KIT:
o The Compaq KZPEA-DB SCSI Storage Adapter is a high-performance
dual channel Ultra 160 SCSI adapter that connects external or
internal SCSI storage devices to a PCI-based host Alpha
system. The module provides multimode SCSI support for both
Single-Ended (SE) and Low Voltage Differential (LVD)SCSI
peripherals in a 33/66 MHz PCI slot.
The KZPEA adapter has the following features:
1. Provides full-featured dual-channel Ultra 160 SCSI host
adapter with a 66/33 MHz 64-bit PCI interface.
2. Supports Ultra160 data transfer rates up to 160 MB/sec on
the 16-bit SCSI bus using LVD SCSI peripherals.
3. Supports mixed SCSI-2, Ultra2, and Ultra160 SCSI
peripherals on Compaq Storageworks enclosures.
4. Supports hot-swapping/hot-adding of SCSI peripherals.
Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE
Restrictions and Workarounds:
The KZPEA-DB Ultra 160 SCSI Storage Adapter currently supports
only split bus racks, not single bus Starbrite storage racks.
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 VMS722_FIBRE_SCSI-V0100 KIT:
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 unsynchronized relative to each other. This
un-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 A system can crash with an INVEXCEPTN
SYS$K_VERSION_01+00D20
error.
Crashdump Summary Information:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above
ASTDEL
Current Process: O-2-BAD
Current Image: $1$DGA1000:[SYS3.SYSCOMMON.]
[SYSEXE]OPCCRASH.EXE;4
Failing PC: 00000000.00030D20
SYS$K_VERSION_01+00D20
Failing PS: 10000000.00000803
Module: OPCCRASH
Offset: 00030D20
Images Affected: [SYS$LDR]SYS$FGEDRIVER.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 If a disk is mounted software write protected, when the disk
enters and completes mount verification, the disk is changed
to software write enabled.
Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE
o I/O to or from a Qlogic bus can hang when the bus is heavily
loaded and undergoing stress, such as in a cluster transition.
Images Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o For 8MM tapes only (eg. 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 shows that an Illegal Request has been sent to
the drive.
Images Affected: [SYS$LDR]SYS$MKDRIVER.EXE
o FGEDRIVER can experience the following problems:
o INVEXCEPTN, Exception while above ASTDEL
o INCONSTATE, Inconsistent I/O data base
Images Affected: [SYS$LDR]SYS$FGEDRIVER.EXE
o A system can crash during system startup if a SCSI Exabyte
tape drive is present on a parallel SCSI bus.
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
o The system can crash with a SHADDETINCON bugchek in
SYS$SHDRIVER.
Crashdump Summary Information:
------------------------------
Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent
state
Current Process: NULL
Current Image: <not available>
Failing PC: FFFFFFFF.A9C2EB98
SYS$SHDRIVER+82B98
Failing PS: 34000000.00000804
Module: SYS$SHDRIVER (Link Date/Time:
5-AUG-2001 01:03:45.34)
Offset: 00082B98
Images Affected: le;[SYS$LDR]SYS$FGEDRIVER.EXE
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 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=V2.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS722_FIBRE_SCSI-V0200 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=V2.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
---
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]