ECO NUMBER: ALPBOOT12_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPBOOT12_062 2 KITS SUPERSEDED BY THIS KIT: ALPBOOT11_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this kit: ALPCLUSIO01_062 3.2 In order to receive the 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 Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYS$LDR]EXCEPTION.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYS$LDR]SYS$FABTDRIVER.EXE (new image) o [SYS$LDR]SYSLDR_DYN.EXE (new image) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYS$LDR]SYSTEM_DEBUG.DSF (new file) -- COVER LETTER -- Page 2 13 April 1998 5 PROBLEMS ADDRESSED IN ALPBOOT12_062 KIT o The formatting of the section titled "Support the use of the " dump_dev " environmental variable." was incorrect, which made the section unreadable. This formatting has been fixed. Hence, this kit has no new problem corrections. If you have installed the ALPBOOT10_062 or ALPBOOT11_062 remedial kits, you do not need to install this kit. 6 PROBLEMS ADDRESSED IN ALPBOOT11_062 KIT o The ALPBOOT10_062 remedial kit required that the ALPCLUSIO01_062 kit be installed. If the user tried to install the ALPBOOT10_062 kit on a system that had both the ALPCLUSIO01_062 and OpenVMS Alpha Y2K remedial kits installed, the ALPBOOT10_062 kit did not recognize that the ALPCLUSIO01_062 kit had been installed. This caused the ALPBOOT10_062 installation to fail. There are no new ECO problem corrections in this kit. If you have installed the ALPBOOT10_062 remedial kit, you do not need to install the ALPBOOT11_062 remedial kit. 7 PROBLEMS ADDRESSED IN ALPBOOT10_062 KIT o Some images in the the ALPBOOT09_062 kit had an installation conflict with the ALPCLUSIO01_062 remedial kit. This kit resolves that conflict. Since the ALPCLUSIO01_062 kit contained newer images, the images in question have been removed from the ALPBOOT10_062 kit. 8 PROBLEMS ADDRESSED IN ALPBOOT09_062 KIT o If a customer upgraded their system to V6.2 from V6.1, the KITINSTAL.COM procedure in kits that require the ALPCLUSIO01 remedial kit to be installed first, did not properly verify that the ALPCLUSIO01_062 remedial kit had been installed. o While booting, the system crashes during driver loading. This is caused by a corrupt driver prologue table for a previously loaded driver. -- COVER LETTER -- Page 3 13 April 1998 9 PROBLEMS ADDRESSED IN ALPBOOT08_062 KIT o The ALPBOOT07_062 kit contained some incorrect build identifications within the images which could have prevented the images from being installed. This kit ALPBOOT08_062 contains the correct build identifications and fixes that problem. 10 PROBLEMS ADDRESSED IN ALPBOOT07_062 KIT o Kitinstal does not check for ALPCLUSIO01_062 kit to be installed on the system. 11 PROBLEMS ADDRESSED IN ALPBOOT06_062 KIT o This kit provides the necessary files to support the DE500-AA Fast EtherWORKS PCI 10/100 adapter under the OpenVMS Alpha V6.2 Operating System and the associated V6.2 hardware releases. These hardware releases include OpenVMS Alpha V6.2-1H1, V6.2-1H2, and V6.2-1H3. This allows OpenVMS Alpha V6.2* users to take advantage of the newest generation Fast Ethernet adapter from Digital Equipment Corporation without requiring a total operating system upgrade. The DE500-AA supersedes the DE500-XA which is currently supported by OpenVMS Alpha V6.2. Note: OpenVMS Alpha V7.1 also includes support for the DE500-AA. The DE500 -XA will be retired by the end of March, 1997. (Please refer to the ALPHA qualified options list to confirm support for your particular CPU.) The combination of this TIMA kit and the DE500-AA provides a form, fit, and functionally equivalent PCI to Fast Ethernet adapter to the DE500-XA on OpenVMS Alpha V6.2 host CPUs. In addition, the DE500-AA adapter implements industry standard auto-negotiation for 10 or 100 Mbps and for half or full duplex, and includes a socket for optional ROM support. Both the DE500-XA and the DE500-AA utilize a single RJ45 connector for connection to either a 10 or 100 Mbps Ethernet network. These adapters support full duplex Ethernet communication when connected to a co-operating full duplex-compatible device. You must ensure that the connected device supports full duplex mode before forcing this feature, or serious network problems can result. If auto-negotiate mode is used, this is not a concern, as the hardware will determine the duplex capability of the connected device. -- COVER LETTER -- Page 4 13 April 1998 DE500-AA Boot Device Driver (SYS$EWBTDRIVER.EXE) This driver adds support for the DE500-AA and continues to support the PCI Ethernet adapters that were previously supported by OpenVMS Alpha V6.2. This includes the DE500-XA, DE450, and the DE435. All these devices show up under the Operating System as EWx0, where x is the controller letter (e.g. A, B, C). This new driver supports DE500-AA booting over twisted pair media at speeds of 10 and 100 mbits/sec, full or half duplex, and with auto negotiation. The DE500-XA supports booting over twisted pair media at speeds of 10 and 100 mbits/sec half duplex. For each EW device recognized by the console there is a console environment variable called EWx0_MODE that must be correctly set to select the appropriate operating mode. The environment variable is set with the console command: >>> SET EWx0_MODE media_selection Where x is the controller letter (e.g. A, B, C) and media_selection is one of the following: Twisted-Pair Full Duplex, Twisted-Pair AUI BNC Fast FastFD (Full Duplex) Auto-Negotiate Note: An Alpha system console may assign a controller letter to an adapter differently from OpenVMS. It is recommended that the user issue a SHOW CONFIGURATION command at the console to determine the correct letter designation for each adapter. Restrictions ------------ 1. The ALPBOOT06_062 kit CANNOT be installed if the ALPCLUSIO01_062 Cluster Compatibility Kit for mixed V6.2 and V7.1 systems was previously installed. 2. If the ALPBOOT06_062 kit is installed the ALPLAN04_062 kit must also be installed. 3. The system firmware must be at a revision level that supports the DE500-AA for boot support. The Alpha Firmware CD V3.8 or later has the required support for each applicable system type. -- COVER LETTER -- Page 5 13 April 1998 o The ALPBOOT05_062 kit had an error in the .VUI file that installed the EXEC_INIT.EXE image. This error did not affect installation of this image but could have had an impact as future kits were released. 12 PROBLEMS ADDRESSED IN ALPBOOT05_062 KIT o The ALPBOOT04_062 kit experienced errors during the installation process that caused some images to not be moved to their final directory locations. 13 PROBLEMS ADDRESSED IN ALPBOOT04_062 KIT o Alpha 8200/8400 systems are not generating crash dumps to FDDI served system disks. This problem is corrected in OpenVMS Alpha V7.0. 14 PROBLEMS ADDRESSED IN ALPBOOT03_062 KIT o $UNWIND sometimes unwinds to the last program counter. This problem will be seen by customers who use ACMSxp on OpenVMS ALPHA V6.2. This problem is corrected in OpenVMS Alpha V7.0 o The "dump_dev" environmental variable will be used to locate the system disk when the crash dump file must be written. If this variable is not populated or if it does not exist, the "booted_dev" environmental variable is currently used as the device to access the sysdump.dmp file. If the device cannot be found, then NO dump will be written. For those systems that boot using CI devices and that can be found on more than one controller, ensure that the "dump_dev" environmental variable is populated. Having the "dump_dev" variable populated will guarantee that the BUGCHECK code checks both controllers when trying to find the device. For example, if a disk is located on a dual redundant pair of HSJ controllers, then the "dump_dev" environmental variable MUST contain both controllers that can access that boot device. The "bootdef_dev" variable will list both paths to the system boot device. Therefore, if the boot device should move between controllers, the console will be able to locate it and then boot the system. -- COVER LETTER -- Page 6 13 April 1998 The "dump_dev" variable should always be a copy of the "bootdef_dev" environmental variable. Consequently, it will list both paths to the system boot device and will enable the bug check code to locate the dump device on either controller. If the system disk is a two-member shadow set, then BOTH paths to BOTH devices should be stored in "bootdef_dev" and in "dump_dev". For example, the results of executing show device and show * are displayed below. Note, that this system is using a two-member system disk shadow set: >>> show dev polling for units on cixcd0, slot 2, xmi0... Resetting IO subsystem... · · · dua206.4.0.2.3 $4$DUA206 (RED70A) RA72 dua229.4.0.2.3 $4$DUA229 (RED70A) RA72 . . . polling for units on cixcd1, slot 4, xmi0... dub206.7.0.4.3 $4$DUA206 (GRN70A) RA72 . . . polling for units on cixcd1, slot 4, xmi0... dub229.4.0.4.3 $4$DUA229 (GRN70B) RA72 >>> >>> show * auto_action HALT . . . bootdef_dev dub206.7.0.4.3,dua206.4.0.2.3,dua229.4.0.2.3, dub229.4.0.4.3 . . . dump_dev dub206.7.0.4.3,dua206.4.0.2.3,dua229.4.0.2.3, dub229.4.0.4.3 . . . >>> -- COVER LETTER -- Page 7 13 April 1998 15 PROBLEMS ADDRESSED IN ALPBOOT02_062 KIT o The DE205 boot driver is deficient in that the performance is less than admirable. It actually works but periodically requires a timeout and reset of the bootdriver thus extending boot times considerably (by a factor of 20). o Shutting down or forcing a crash on a satellite that is booted from a shadowed system disk produces the following error message but no dump file: **** Cannot use unit 0, not the master member of the system disk shadow set o Dumps can't be taken if DUMP_DEV was specified but SYSINIT has not yet filled in the system disk data. o When a system disk fails over to an alternate path (HSC) crashdumps aren't written but the system reboots successfully. 16 PROBLEMS ADDRESSED IN ALPBOOT01_062 KIT o The selection of 10 and 100 megabits/second and full-duplex operation using LANCP does not work. Normally, the device driver autoselects the speed, first attempting 100 and then switching to 10 megabit operation on failure. If no cable is connected, 10 megabit operation is selected and a LANCP SET SPEED command is necessary to force 100 megabit operation. The device driver does not implement the SET SPEED command correctly. In addition, it does not implement the SET DEVICE/FULL_DUPLEX command correctly, thus does not allow the selection of full-duplex operation. These problems are corrected for the DE500 driver, to allow speed and full-duplex settings to be modified via LANCP commands. This problem is fixed in OpenVMS Alpha V7.0 o The media autoselection for the DE450, between twisted pair (10baseT), thinwire (10base2), and thickwire (10base5), does not work for any selection other than twisted pair. Note that the device driver the DE450 driver does autoselection of the media connection, selecting twisted pair, then thickwire, then thinwire, switching on failure. If no cable is connected, the driver selects thinwire. To change the cable selection, refer to the LANCP documentation for the SET DEVICE/MEDIA command. This problem is fixed in OpenVMS Alpha V7.0 o Add DE450 and DE500 boot support. Note that the DE450 does not use a jumper to switch between 10base2 (thinwire) and 10base5 (thickwire). To select thinwire at the console prompt for boot -- COVER LETTER -- Page 8 13 April 1998 purposes, set the EWA0_MODE console environment variable to BNC. To select thickwire, set the variable to AUI. This problem is fixed in OpenVMS Alpha V7.0 o Add DE203, DE204, DE205 boot support for the AlphaStation 200 and 400 systems. Booting is supported only for a module set to the default parameters, I/O port address of 300 (hex) and memory base address of D0000 (hex). This problem is fixed in OpenVMS Alpha V7.0 17 PROBLEMS ADDRESSED IN ALPAPB01_062 KIT o The primitive file system used during booting of OpenVMS Alpha cannot locate files whose file number is greater than 65536. Depending on the phase of the boot, this can result in an access violation or a message such as: %SYSINIT-F-LOADERR,error loading RMS.EXE status=00000044 This problem is corrected in OpenVMS Alpha V7.0 18 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 19 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 ALPBOOT12_062 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. -- COVER LETTER -- Page 9 13 April 1998 If you have other nodes in your VMS 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. Copyright (c) Digital Equipment Corporation, 1998 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 Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment 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 DIGITAL 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.