ECO NUMBER: VAXPHV01_071 ----------- PRODUCT: OpenVMS VAX Operating System -------- UPDATED PRODUCT: OpenVMS VAX Operating System 7.1 ---------------- APPRX BLCK SIZE: 1098 ---------------- COVER LETTER 1 KIT NAME: VAXPHV01_071 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.1 4.2 Files patched or replaced: o [SYS$LDR]ECDRIVER.EXE (new image) o [SYS$LDR]EFDRIVER.EXE (new image) o [SYS$LDR]EPDRIVER.EXE (new image) o [SYS$LDR]ESDRIVER.EXE (new image) o [SYS$LDR]ETDRIVER.EXE (new image) o [SYS$LDR]EXDRIVER.EXE (new image) o [SYS$LDR]EZDRIVER.EXE (new image) o [SYS$LDR]FCDRIVER.EXE (new image) o [SYS$LDR]FQDRIVER.EXE (new image) -- COVER LETTER -- Page 2 4 February 1999 o [SYS$LDR]FXDRIVER.EXE (new image) o [SYS$LDR]NET$CSMACD.EXE (new image) o [SYS$LDR]NET$FDDI.EXE (new image) o [SYS$LDR]XEDRIVER.EXE (new image) o [SYS$LDR]XQDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXPHV01_071 KIT 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. -- COVER LETTER -- Page 3 4 February 1999 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. 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXPHV01_071 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. 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. -- COVER LETTER -- Page 4 4 February 1999 Copyright (c) Compaq Computer Corporation, 1999 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.