OpenVMS VAXPHV01_071 VAX V7.1 FDDI Drivers ECO Summary

TITLE: OpenVMS VAXPHV01_071 VAX V7.1 FDDI Drivers ECO Summary
 
Modification Date:  22-FEB-99
Modification Type:  New Kit

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 1999.  All rights reserved.

OP/SYS:     DIGITAL OpenVMS VAX 

COMPONENT:  FDDI Drivers 
              ECDRIVER
              EFDRIVER
              EPDRIVER
              ESDRIVER
              ETDRIVER
              EXDRIVER
              EZDRIVER
              FCDRIVER
              FQDRIVER
              FXDRIVER
              NET$CSMACD
              NET$FDDI
              XEDRIVER
              XQDRIVER

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXPHV01_071 
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  1098 Blocks
     Kit Applies To:  OpenVMS VAX V7.1
     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:

         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 FDDI Drivers on OpenVMS VAX V7.1.  This kit 
addresses the following problems: 

  o  For the command:

     NCL> SHOW FDDI STATION FDDI-0 * ALL

     the SMTstationID field was displayed as '0000000000000000'H,
     but should have been '080008002B209E45'H.

  o  A crash occurred in module FX$SCHED_CMDUNS_FORK while doing a
     DEVICELOCK.

       The crash occurred under the following conditions:

         1.  FDDI (DEMFA)

         2.  MOPRC (60-02)

         3.  crash address FXDRIVER+022E4

         4.  current process was running TSM$MAIN

  o  During testing of failover to a second FDDI controller, after
     an FDDI cable was removed, a SET HOST command hung for one
     minute, resulting in a bugcheck at TIMER.BUG.  Note that the
     problem did not cause a fatal error and allowed the FDDI ring
     to resynchronize.

  o  DECnet hung for 1 minute when the FDDI cable was removed from
     the bulkhead.

  o  Attempting to start the MOPRC protocol on a DEMFA returned an
     SS$_DEVREQERR error status.

  o  If a DEMFA FDDI controller fails, then transmit requests can
     possibly fail to complete within a timeout period.

     The failure that a user sees is that the FDDI path fails and
     then the cluster software does not switch to another path,
     usually resulting in a CLUEXIT error.

  o  When the cable is disconnected from the DEMFA FDDI controller,
     timing problems can occur in the driver, which could result in
     a crash after an extended period of cable disconnections
     (typically weeks).

  o  The LAN Driver received a loopback packet with a broadcast
     destination address, which was an invalid use of the loopback
     protocol (90-00) format.  However, the packet was not regarded
     as invalid, resulting in a crash at EZDRIVER+072E3.

  o  Transmit timeouts errors must be set as fatal.

     A problem with failover occurred on the DEMFA on a VAX system.
     Although a transmit timeout had occurred, the transmit completed 
     with an error status and continued.  Since the failure happened 
     in such a way that the link did not go down and come back up, a 
     failover never happened.

  o  A crash occurred during timeout processing and it can happen
     on a VAX 4000-90, VAX 4000-300, etc., that also has an SGEC
     Ethernet adapter.


INSTALLATION NOTES:

The images in this kit will not take effect until the system is
rebooted.  If there are other nodes in the VMScluster, 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.


All trademarks are the property of their respective owners.

Colorado Site
Georgia Site

vaxphv01_071.README
vaxphv01_071.CHKSUM
vaxphv01_071.CVRLET_TXT
vaxphv01_071.a-dcx_vaxexe