**************************** ECO SUMMARY INFORMATION **************************** Release Date: 31-MAY-2005 Kit Name: DEC-AXPVMS-VMS731_LAN-V1300--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 8048 blocks Installation Rating: INSTALL_2 Required Features: LAN Reboot Required: Yes - rolling reboot Superseded Kits: VMS731_LAN-V1200 Mandatory Kit Dependencies: VMS731_UPDATE-V0500 VMS731_PCSI-V0200 Optional Kit Dependencies: None VMS731_LAN-V1300.PCSI-DCX_AXPEXE Checksum: 478131349 DEC-AXPVMS-VMS731_LAN-V1300--4.PCSI Checksum: 3904134112 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS731_LAN-V1300 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-1 2.4 New functionality or new hardware support provided: {Functionality yes or no} 3 KITS SUPERSEDED BY THIS KIT: - VMS731_LAN-V1200 Page 2 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0500 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 FILES PATCHED OR REPLACED: o [SYSEXE]APB.EXE (new image) Image Identification Information image name: "APB" image file identification: "X-8" image file build identification: "XA2Q-0060030005" link date/time: 23-JUN-2004 13:12:22.83 linker identification: "A11-50" Overall Image Checksum: 1829181365 o [SYSEXE]DEBUG_APB.EXE (new image) Image Identification Information image name: "DEBUG_APB" image file identification: "X-8" image file build identification: "XA2Q-0060030005" link date/time: 23-JUN-2004 13:12:23.35 linker identification: "A11-50" Overall Image Checksum: 889014035 o [SYSLIB]LAN$SDA.EXE (new image) Image Identification Information image name: "LAN$SDA" image file identification: "X-12A3" image file build identification: "0060030020" link date/time: 1-FEB-2005 10:39:10.88 linker identification: "A11-50" Overall Image Checksum: 2693343462 Page 3 o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-32" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:38:53.01 linker identification: "A11-50" Overall Image Checksum: 3813221373 o [SYS$LDR]SYS$EBDRIVER.EXE (new image) Image Identification Information image name: "SYS$EBDRIVER" image file identification: "X-12A1" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:39:07.58 linker identification: "A11-50" Overall Image Checksum: 1108074182 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-42" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:39:08.97 linker identification: "A11-50" Overall Image Checksum: 2449764093 o [SYS$LDR]SYS$ERDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:37:59.04 linker identification: "A11-50" Overall Image Checksum: 1517346378 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-44" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:39:04.64 linker identification: "A11-50" Overall Image Checksum: 2248686628 Page 4 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700" image file identification: "X-39" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:39:05.86 linker identification: "A11-50" Overall Image Checksum: 1938545399 o [SYS$LDR]SYS$EWDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:38:10.15 linker identification: "A11-50" Overall Image Checksum: 1945350300 o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$DE500BADRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:38:14.94 linker identification: "A11-50" Overall Image Checksum: 1815760982 o [SYS$LDR]SYS$FCDRIVER.EXE (new image) Image Identification Information image name: "SYS$FCDRIVER" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:38:32.96 linker identification: "A11-50" Overall Image Checksum: 2735160699 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:35:39.60 linker identification: "A11-50" Overall Image Checksum: 2154861839 Page 5 o [SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM" image file identification: "X-28" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:36:54.97 linker identification: "A11-50" Overall Image Checksum: 1747581343 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:35:53.62 linker identification: "A11-50" Overall Image Checksum: 3598944825 o [SYS$LDR]SYS$LAN_FDDI.EXE (new image) Image Identification Information image name: "SYS$LAN_FDDI" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:37:23.62 linker identification: "A11-50" Overall Image Checksum: 1985998924 o [SYS$LDR]SYS$LAN_TR.EXE (new image) Image Identification Information image name: "SYS$LAN_TR" image file identification: "X-3" image file build identification: "XA9J-0060030020" link date/time: 1-FEB-2005 10:37:33.15 linker identification: "A11-50" Overall Image Checksum: 1891420134 o [SYS$LDR]APB_BOOTP.EXE (new image) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_LAN-V1300 KIT Page 6 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 INVEXCEPTN Bugcheck At SYS$EBDRIVER+00D28 6.2.1.1 Problem Description: After installing the VMS731_LAN-V1200 ECO kit on a Galaxy configuration, the system can crash with an INVEXCEPTN bugcheck at SYS$EBDRIVER+00D28. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: STACONFIG Current Image: STACONFIG.EXE Failing PC: FFFFFFFF.804FCD28 SYS$EBDRIVER+00D28 Failing PS: 20000000.00000804 Module: SYS$EBDRIVER (Link Date/Time: 18-JUL-2002 20:10:08.84) Offset: 00000D28 Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) QXCM1000210368 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: LAN event tracing starts during driver initialization. This results in a crash in EBDRIVER during unit initialization. Page 7 6.2.1.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.1.5 Work-arounds: None. 6.2.2 DECnet-Plus And Host Based Routing Not Working 6.2.2.1 Problem Description: When using the Broadcom 5703 with DECnet-Plus and Host Based Routing support, when one node sends packets to another node with a DEGXA the receiving node does not see the packets. This prevents DECnet-Plus Host Base Routing (HBR) from working. Images Affected: - [SYS$LDR]SYS$EW5700.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: The Broadcom 5703 offers perfect filtering of multicast addresses for up to 12 addresses. Beyond 12, there is a 256 bit hash filter that limits the amount of unwanted multicast traffic that has to be discarded by the driver. There is a problem that affects particular multicast addresses. The solution is to disable perfect filtering and rely on the 256 bit hash filter for multicast filtering. Page 8 6.2.2.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.2.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problem addressed in previous V7.3-1 LAN patch kits can be found in the following files: o [SYSHLP]VMS731_LAN-V1200.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V1100.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V1000.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0900.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0800.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0700.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0600.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0500.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0400.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0300.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0200.RELEASE_NOTES o [SYSHLP]VMS731_LAN-V0100.RELEASE_NOTES 8 INSTALLATION INSTRUCTIONS 8.1 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 VMS731_LAN-V1300.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] Page 9 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 8.2 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 VMS731_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.3 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 Page 10 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=V13.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_LAN-V1300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_LAN/PRODUCER=DEC/BASE=AXPVMS- /VER=V13.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2005 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. Page 11 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.