HP Services Software Patches - vaxneta02_061

 
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.
 
*DECnet-VAX] VAXNETA02_061 VAX V6.1 Phase IV ECO Summary

Copyright (c) Digital Equipment Corporation 1995, 1996.  All rights reserved.

PRODUCT:     DECnet-VAX for OpenVMS VAX (Phase IV)

OP/SYS:      OpenVMS VAX Version 6.1

COMPONENTS:  NETACP.EXE
             NETDRIVER.EXE

SOURCE:      Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXNETA02_061
     ECO Kits Superseded by This ECO Kit:  VAXNETA01_061
     ECO Kit Approximate Size:  342 Blocks 
     Kit Applies To:  OpenVMS VAX V6.1
     System Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for NETACP and NETDRIVER on OpenVMS VAX V6.1. 
This kit addresses the following problems:

Problems Addressed in the VAXNETA02_061 Kit:

  o  The NETACP.EXE image for OpenVMS VAX V6.0 which was previously
     included in this ECO kit conflicted with a previously released
     Pathworks kit and could cause system crashes.  Support for
     OpenVMS VAX V6.0 has been removed from this ECO.


Problems Addressed in the VAXNETA01_061 Kit: 

  o  A Phase IV node running OpenVMS VAX V6.1 erroneously logs 4.20
     DECNET events after a synchronous line is down.  The following
     error message is output to the console:

          %%%%%%%%%%% OPCOM 28-JUN-1994 15:34:45.65 %%%%%%%%%%%  Message
          from  user  DECNET DECnet event 4.20, adjacency initialization
          failure

          Circuit  ISA-0,  Phase  IV  node  exists  in  the  absence  of
          bilingual router **

     Also, a Phase IV router running V6.1 has multiple adjacency up
     messages without any corresponding adjacency downs and cannot set
     host out.

  o  NETACP process hangs in (LEF) local event flag wait and any
     process that accesses a network channel after this occurs will
     become stuck in an RWAST mutex wait.  Other than network access,
     no other conditions are required to reproduce the problem.


INSTALLATION NOTES:

The system/cluster does not need to be rebooted after this kit is
installed.  However, the network will need to be shut down and
restarted on each node of the cluster in order for all kit changes to
take effect.  To shut down and start the network, execute the
following commands from the system manager account on each node of the
cluster:

     SHUTDOWN:

          Action                  Command

          Log into NCP            $ MC NCP
          Shut down network       NCP> SET EXECUTOR STATE OFF
          Exit NCP                NCP> EXIT

     STARTUP:

          Action                  Command

          Start network           $ @SYS$MANAGER:STARTNET.COM

Files on this server are as follows:

»vaxneta02_061.README
»vaxneta02_061.CHKSUM
»vaxneta02_061.CVRLET_TXT
»vaxneta02_061.a-dcx_vaxexe