Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_FIBRE_SCSI-V0300 Alpha V7.3 FibreChannel/SCSI ECO Summary
TITLE: OpenVMS VMS73_FIBRE_SCSI-V0300 Alpha V7.3 FibreChannel/SCSI ECO Summary

New Kit Date:       15-JUN-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT
 
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 2002.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  FibreChannel
            SCSI Drivers

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:   VMS73_FIBRE_SCSI-V0300
                     DEC-AXPVMS-VMS73_FIBRE_SCSI-V0300--4.PCSI
     ECO Kits Superseded by This ECO Kit: None
     ECO Kit Approximate Size:  2672 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3
     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), or later, must be installed BEFORE
       installation of this, or any required kit:

          VMS73_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.3.  This kit addresses the following problems:

PROBLEMS ADDRESSED IN VMS73_SCSI-V0300 KIT:

  o  In the event of an unrecoverable SCSI error occurring  on  the
     last block of a transfer, a system with SCSI Fast Path enabled
     (the default) may see one disk block of corruption.  The error
     will not appear in the error log, but the data will be bad.

          Images Affected:  [SYS$LDR]SYS$PKQDRIVER.EXE

  o  When booting, a shadowed system disk can hang the cluster.

          Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE


  o  The following recommended command line has been added to  Help
     for FC$CP:

         $  MCR SYS$ETC:FC$CP FGA 3 1 8  ! Or FGB, etc.


          Images Affected: [SYSHLP.UNSUPPORTED]FC$CP.EXE

  o  The help output for FC$CP.EXE shows a filename of FC$IC.  This
     should be FC$CP.

          Images Affected:  [SYSHLP.UNSUPPORTED]FC$CP.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:            0000B968


          Images Affected:  [SYS$LDR]SYS$FGEDRIVER.EXE


  o  heavy IO load may cause multiple port errors on GS80, GS160 or
     GS320  systems  with  a KZPEA controller.  Disk mount verifies
     may also occur as a result of IO's timing out  and  causing  a
     SCSI  bus  reset.   Excessive IO timeouts could result to data
     corruption.  The error log will show an Asynchronous Device=20
     Attention  from  the  KZPEA Adapter with a Type/Subtype string
     of=20 "0x0401".

          Images Affected: [SYS$LDR]SYS$PKADRIVER.EXE


  o  If a "BACKUP/MEDIA=COMPACTION" operation is in progress  on  a
     Fibre  Channel  tape  on one node, and another node enters the
     cluster,  that  booting  process  switches  the  BACKUP   into
     uncompressed mode.

     A related symptom does not require Fibre Channel or a cluster.
     If  a  compressed  BACKUP  is working and the tape experiences
     transient  power  failure,  the  drive  may  not   return   to
     compressed mode.

          Images Affected:  [SYS$LDR]SYS$MKDRIVER

  o  When backing up files to SCSI QIC tapes  (such  as  TZK11  and
     TZK10), the user may see the following error:

     SYSTEN-F-IVDENS, invalid density


          Images Affected:  [SYS$LDR]SYS$MKDRIVER.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:     
     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 may hang on boot.  When  this  problem  occurs  the
     user  loses complete control of the system.  A CRTL-P will not
     give the user the console prompt.  The only way to unhang  the
     system  is via a power cycle.  When the system hangs, the last
     console output will look something like this:

     FGB0-I-OP_FW, operational firmware revision: CS3.a81A4 n
     l%FGeB0-I-OP_SLI_1 _FW-, SLI-1 firmware revision:  C1D3.81A4
     %FGB0-I-iOP_SLI_2_FW, nSLI-2 firmware revision: C2D3.81A4


     This  output  looks  odd  because  it   contains   interleaved
     characters  from  another  driver.   This  happens because the
     Fibre Channel Driver  is  writing  to  the  console  from  the
     non-primary  CPU.   FGE Driver only writes this message to the
     console when bit 1 of USERD1 is set.  The user can avoid  this
     problem  with  the  old  driver by not setting this bit in the
     SYSGEN variable.

          Images Affected:  [SYS$LDR]SYS$FGEDRIVER.EXE


  o  An INIT command, when used on SCSI tapes, can take a 1/2  hour
     or  more  to  quit  if  no  tape is in the unit, or no tape is
     loading.

          Images Affected:  [SYS$LDR]SYS$MKDRIVER.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


  o  Attempting to mount a TLZ09 gives a DRVERR error.

          Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE


  o  A tape drive can log many errors between volume changes.

          Images Affected:  [SYS$LDR]SYS$PKADRIVER.EXE


  o  This change 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]SMI$OBJSHR.EXE
                            [SYSLIB]IOGEN$FIBRE_CONFIG.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 VMS73_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=V3.0

        -  De-assign the logicals assigned

     For  example,  a  sample   command   file   to   install   the
     VMS73_FIBRE_SCSI-V0300 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS73_FIBRE_SCSI/PROD=DEC/BASE=AXPVMS/VER=V3.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $!
          $ exit

All trademarks are the property of their respective owners.
Files on this server are as follows:
»dec-axpvms-vms73_fibre_scsi-v0300--4.README
»dec-axpvms-vms73_fibre_scsi-v0300--4.CHKSUM
»dec-axpvms-vms73_fibre_scsi-v0300--4.pcsi-dcx_axpexe
»vms73_fibre_scsi-v0300.CVRLET_TXT
privacy statement using this site means you accept its terms