**************************** ECO SUMMARY INFORMATION **************************** Kit Name: DEC-AXPVMS-VMS732_LAN-V0400--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 6816 blocks Installation Rating: INSTALL_2 Required Features: LAN Reboot Required: Yes - rolling reboot Superseded Kits: VMS732_LAN-V0300 Mandatory Kit Dependencies: VMS732_UPDATE-V0400 VMS732_PCSI-V0100 Optional Kit Dependencies: None VMS732_LAN-V0400.PCSI-DCX_AXPEXE Checksum: 2328062482 DEC-AXPVMS-VMS732_LAN-V0400--4.PCSI Checksum: 2563771038 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_LAN-V0400 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - LAN This 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) 2.2 Reboot Requirement: Reboot Required. HP 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V7.3-2 2.4 New functionality or new hardware support provided: Yes 3 KITS SUPERSEDED BY THIS KIT: - VMS732_LAN-V0300 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0100 - VMS732_UPDATE-V0400 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_LAN-V0400 KIT 5.1 New functionality addressed in this kit None. 5.2 Problems addressed in this kit 5.2.1 Failset Formation Fails when members are unavailable 5.2.1.1 Problem Description: If any one member of a specified failset does not exist, formation of the failover set fails. Images Affected: - [SYS$LDR]SYS$LLDRIVER.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000222913 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: The original design caused the failover set creation to fail if any member was not available. With this change, if a LAN device is specified as a failset member and that device does not exist, formation of the failover set will proceed with the remaining members. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next OpenVMS Alpha release after V8.2 5.2.1.5 Work-arounds: None. 5.2.2 LANCP command SHOW DEV/COUNTERS output displayed incorrectly 5.2.2.1 Problem Description: The counters returned by LAN drivers include a few fields that the existing LANCP utility does not display correctly. This change adds support for a new counter type that allows output from the LANCP command SHOW DEV/COUNTERS to be displayed correctly. Images Affected: - [SYSEXE]LANCP.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: See problem description. Page 4 5.2.2.4 Release Version of OpenVMS that will contain this change: Next OpenVMS Alpha release after V8.2 5.2.2.5 Work-arounds: None. 5.2.3 Failover Set Is Not Enabled For Jumbo Frames 5.2.3.1 Problem Description: Even if a failover set is defined in LANCP with the /SIZE=JUMBO qualifier, the resulting failover set is not enabled for jumbo frames. Images Affected: - [SYSEXE]LANCP.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000238480 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: Because different NICs can have differing maximum jumbo frame sizes, whenever a LAN failover set is defined in LANCP using the /SIZE=JUMBO qualifier, the actual jumbo frame size needed to be set to 8192 for LLDRIVER to properly enable jumbo frames. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next OpenVMS Alpha release after V8.2 Page 5 5.2.3.5 Work-arounds: None. 5.2.4 I/Os to a DEGPA Hang 5.2.4.1 Problem Description: After boot, I/Os to a DEGPA hang, even though all other indications show that there is no problem. Momentarily disconnecting the NIC cable clears the condition. Images Affected: - [SYSEXE]SYS$EW1000A.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000241685,QXCM1000237296 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: There is a timing window during the driver initialization state. While in an event processing loop, if a "link-up" event occurred after a "firmware operational" event, the driver would be left in a "RUN-WAIT" state until another "link-up" or "link-down" event occurred (which could be a long time). 5.2.4.4 Release Version of OpenVMS that will contain this change: Next OpenVMS Alpha release after V8.2 5.2.4.5 Work-arounds: None. Page 6 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_LAN ECO kits can be found in the following files: o VMS732_LAN-V100 o VMS732_LAN-V200 o VMS732_LAN-V300 Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS732_LAN/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_LAN/VERSION = V4.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSLIB]LAN$SDA.EXE (new image) Image Identification Information image name: "LAN$SDA" image file identification: "X-14A4A6" image file build identification: "0060111012" link date/time: 3-AUG-2005 15:20:03.01 linker identification: "A11-50" Overall Image Checksum: 2906035723 o [SYSEXE]LANCP.EXE (new image) Image Identification Information image name: "LANCP" image file identification: "X-65A2" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:00.53 linker identification: "A11-50" Overall Image Checksum: 1367853502 o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information image name: "NET$CSMACD" Page 7 image file identification: "X-17" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:00.20 linker identification: "A11-50" Overall Image Checksum: 523885877 o [SYS$LDR]NET$FDDI.EXE (new image) Image Identification Information image name: "NET$FDDI" image file identification: "X-17" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:00.31 linker identification: "A11-50" Overall Image Checksum: 3032370308 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-42" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:02.50 linker identification: "A11-50" Overall Image Checksum: 2236558650 o [SYS$LDR]SYS$ERDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERDRIVER" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:54.89 linker identification: "A11-50" Overall Image Checksum: 2276940390 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-47A1" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:01.50 linker identification: "A11-50" Overall Image Checksum: 2940418166 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700" image file identification: "X-39" image file build identification: "XA99-0060111012" Page 8 link date/time: 3-AUG-2005 15:20:01.75 linker identification: "A11-50" Overall Image Checksum: 2972825702 o [SYS$LDR]SYS$EWDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:55.44 linker identification: "A11-50" Overall Image Checksum: 2560767735 o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER_DE500BA" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:55.71 linker identification: "A11-50" Overall Image Checksum: 75721884 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:51.95 linker identification: "A11-50" Overall Image Checksum: 1077119696 o [SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM" image file identification: "X-29" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:53.04 linker identification: "A11-50" Overall Image Checksum: 13266283 o [SYS$LDR]SYS$LAN_ATM4.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM4" image file identification: "X-5" image file build identification: "XA99-0060111012" link date/time: 25-MAR-2005 11:16:26.30 linker identification: "A11-50" Page 9 Overall Image Checksum: 2978058063 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:52.23 linker identification: "A11-50" Overall Image Checksum: 4023368001 o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) Image Identification Information image name: "SYS$LAN_FDDI" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:53.46 linker identification: "A11-50" Overall Image Checksum: 1245111133 o [SYS$LDR]SYS$LAN_TR.EXE (new image) Image Identification Information image name: "SYS$LAN_TR" image file identification: "X-4" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:19:53.70 linker identification: "A11-50" Overall Image Checksum: 1761214819 o [SYS$LDR]SYS$LLDRIVER.EXE (new image) Image Identification Information image name: "SYS$LLDRIVER" image file identification: "X-12" image file build identification: "XA99-0060111012" link date/time: 3-AUG-2005 15:20:01.98 linker identification: "A11-50" Overall Image Checksum: 2309497710 8 INSTALLATION INSTRUCTIONS Page 10 8.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable .PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_LAN-V0400.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification Page 11 8.3 Installation Command 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 VMS732_LAN/SAVE_RECOVERY_DATA [/SOURCE=location of Kit] The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.4 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 logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V4.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned Page 12 For example, a sample command file to install the VMS732_LAN-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_LAN/PRODUCER=DEC/BASE=AXPVMS- /VER=V4.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. 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 HP 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.