**************************** ECO SUMMARY INFORMATION **************************** Kit Name: VMS722_LAN-V0500 DEC-AXPVMS-VMS722_LAN-V0500--4.PCSI Kit Applies To: OpenVMS ALPHA V7.2-2 Approximate Kit Size: 5232 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS722_LAN-V0400 Mandatory Kit Dependencies: VMS722_PCSI-V0100 VMS722_UPDATE-V0100 Optional Kit Dependencies: None ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS722_LAN-V0500 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 1 KIT NAME: VMS722_LAN-V0500 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. 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.2-2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS722_LAN-V0400 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS722_UPDATE-V0100 - VMS722_PCSI-V0100 Page 2 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: "X71Z-0050170002" link date/time: 30-JUL-2002 22:48:16.64 linker identification: "A11-39" o [SYSEXE]DEBUG_APB.EXE (new image) Image Identification Information image name: "DEBUG_APB" image file identification: "X-8" image file build identification: "X71Z-0050170002" link date/time: 30-JUL-2002 22:50:58.65 linker identification: "A11-39" o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information image name: "NET$CSMACD" image file identification: "X-17" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:40:13.80 linker identification: "A11-39" o [SYS$LDR]NET$FDDI.EXE (new image) Image Identification Information image name: "NET$FDDI" image file identification: "X-17" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:40:16.45 linker identification: "A11-39" o [SYS$LDR]SYS$EBDRIVER.EXE (new image) Image Identification Information image name: "SYS$EBDRIVER" Page 3 image file identification: "X-12" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:41:28.22 linker identification: "A11-39" o [SYS$LDR]SYS$EIBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIBTDRIVER" image file identification: "X-1" image file build identification: "X71Z-0050170002" link date/time: 28-JUN-2002 11:21:03.79 linker identification: "A11-39" o [SYS$LDR]SYS$EIDRIVER.EXE (new image) Image Identification Information image name: "SYS$EIDRIVER" image file identification: "X-25" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:41:35.20 linker identification: "A11-39" o [SYS$LDR]SYS$ERBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERBTDRIVER" image file identification: "X-4" image file build identification: "X71Z-0050170002" link date/time: 28-JUN-2002 11:21:34.99 linker identification: "A11-39" o [SYS$LDR]SYS$ERDRIVER.EXE (new image) Image Identification Information image name: "SYS$ERDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:37:59.22 linker identification: "A11-39" o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-31" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:41:20.75 linker identification: "A11-39" Page 4 o [SYS$LDR]SYS$EWBTDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWBTDRIVER" image file identification: "X-4" image file build identification: "X71Z-0050170002" link date/time: 28-JUN-2002 11:21:47.69 linker identification: "A11-39" o [SYS$LDR]SYS$EWDRIVER.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:38:16.91 linker identification: "A11-39" o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image) Image Identification Information image name: "SYS$EWDRIVER_DE500BA" image file identification: "X-3" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:38:25.11 linker identification: "A11-39" o [SYS$LDR]SYS$FWDRIVER.EXE (new image) Image Identification Information image name: "SYS$FWDRIVER" image file identification: "X-3" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:39:24.78 linker identification: "A11-39" o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information image name: "SYS$LAN" image file identification: "X-3" image file build identification: "X71Z-0050170006" link date/time: 11-JUL-2002 17:36:15.96 linker identification: "A11-39" o [SYS$LDR]SYS$LAN_ATM.EXE (new image) Image Identification Information image name: "SYS$LAN_ATM" image file identification: "X-27" image file build identification: "X71Z-0050170006" Page 5 link date/time: 11-JUL-2002 17:36:51.03 linker identification: "A11-39" 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: "X71Z-0050170006" link date/time: 11-JUL-2002 17:36:25.26 linker identification: "A11-39" 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: "X71Z-0050170006" link date/time: 11-JUL-2002 17:37:12.74 linker identification: "A11-39" 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: "X71Z-0050170006" link date/time: 11-JUL-2002 17:37:21.49 linker identification: "A11-39" 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS722_LAN-V0500 kit 6.1.1 Bootblock Corruption after installing VMS722_LAN-V0400 kit 6.1.1.1 Problem Description: If the VMS722_LAN-V0400 ECO kit is removed using PRODUCT UNDO PATCH, the boot block locaton is invalid after the UNDO completes. This may prevent a system from rebooting if the origial bootblock gets overwritten with other data. Images Affected: - [SYSUPD]POSTUNDO.COM Page 6 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.3 CLD(s) 70-3-7378 6.1.1.4 QAR(s) None. 6.1.1.5 Problem Analysis: The POSTUNDO.COM installation procedure performs a writeboot when a kit is un-installed using the PCSI UNDO PATCH feature. This procedure was being executed before all file processing had completed. 6.1.1.6 Work-arounds: If you have already installed the VMS722_LAN-V0400 ECO kit there is no need to install the VMS722_LAN-V0500 kit. To correct the boot problems on the boot disk, execute an MC WRITEBOOT command from a privileged account and answer the prompts as shown: $ MC WRITEBOOT Update VAX portion of boot block (default is Y) : N Update AXP portion of boot block (default is Y) : Y Enter AXP boot file :SYS$COMMON:[SYSEXE]APB.EXE $ 6.2 Problems addressed in VMS722_LAN-V0400 kit o The VMS722_LAN-V0300 kit is not compatible with the newly released PCSI UNDO functionality. This new PCSI functionality allows a user to uninstall a patch kit. If a user was to install the VMS722_LAN-V0300 patch kit using the new PCSI$SAVE_RECOVERY_DATA option and then attempted to uninstall the kit using the UNDO feature, the system could be left in an unbootable state. This new VMS722_LAN-V0400 kit re-issues the VMS722_LAN-V0300 kit with updated installation files that allow safe removal of the kit. Note that this is the only change in this new LAN patch kit. There are no new LAN changes in the VMS722_LAN-V0400 kit. If you have already installed the VMS722_LAN-V0300 patch kit, there is no need to install the VMS722_LAN-V0400 kit. Page 7 Images Affected: - POSTUNDO.COM 6.3 Problems addressed in VMS722_LAN-V0300 kit o The system can crash when another instance in the Galaxy shuts down and there is I/O outstanding to the EBA (Galaxy Shared Memory LAN) device. The driver fork routine now verifies that the other instance has not shut down before processing I/O on behalf of it. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o The receiving side of a transmit request to the EBA (Galaxy Shared Memory LAN) device may crash because the PFN count is incorrect. The transmit side now updates the PFN count before updating the pointers given to the other instance in the Galaxy (that is the target of the transmit request), eliminating a race condition in the driver. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o If the cluster code (PEDRIVER) is using the EBA (Galaxy Shared Memory LAN) device, it may choose another slower LAN device rather than the shared memory LAN device. This change sets the device line speed to 30000 so that PEDRIVER chooses this interconnect over other slower interconnects. Images Affected: - [SYS$LDR]SYS$EBDRIVER.EXE o Occasionally, a transmit request to the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device is not seen by the device. This causes the transmit to be delayed until the next transmit request is given to the device. Under heavy load conditions, this is not noticeable. Under light load, this is seen as a transmit that may take seconds to complete. Where the device is used as a cluster interconnect, the result is transmit retries and virtual circuit closures. Page 8 Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o With the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device, if the link partner redoes auto-negotiation (switch powered off, for example), the driver does not force a link transition when appropriate, resulting in the link partner selecting half-duplex mode when it should select full-duplex mode. Also, the requested settings are not advertised correctly resulting in difficulty auto-negotiating to the intended speed and duplex mode. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver is treating the console environment variable EIx0_MODE setting of "twisted-pair" as "Full-Duplex, Twisted-pair", so it should select half-duplex 10 mbit mode, but selects full-duplex instead. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device is not being set up correctly, generally resulting in a duplex mode mismatch problem, if the console environment variable, EIx0_MODE is set to FastFD. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device occasionally reads an invalid buffer descriptor from the receive ring. When this happens a machine check occurs with resulting system crash, often with an "invalid scatter-gather map" error. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Add support for the Intel 82559ER chip and the DE602-BB NIC. Page 9 Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Resolve a system crash with the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device driver and with IP traffic (generally involving a lot of telnet connections). When the number of segments comprising a transmit packet request exceeds 15, the driver copies the remaining segments into one additional segment. If this segment is not physically contiguous, therefore requiring two additional segments instead of one, the driver corrupts the stack and causes an INVEXCPTN system crash. The problem is that the check for maximum number of segments is off by one. Images Affected: - [SYS$LDR]SYS$EIDRIVER.EXE o Fix a few problems with auto-negotiation by DE500-BA PCI Ethernet devices to improve the ability of the driver to auto-negotiate to the correct setting. This includes adjusting the timing of various auto-negotiation events, and restarting auto-negotiation when appropriate. Images Affected: - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o On rare occasions, it is possible for the Tulip driver to reset the Tulip chip, but not wait long enough after reset before touching the device resulting in a machine check system crash. The solution is to increase the amount of time after a reset to guarantee that the device has sufficient time to reset itself after a reset. The Tulip driver includes support for the Tulip chip, DE425 EISA NIC, and the PCI Ethernet NICs DE434, DE435, DE500-XA, DE500-AA, DE500-BA, DE504-BA. Images Affected: - [SYS$LDR]SYS$ERDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER.EXE - [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE o The DEGPA firmware included in the device driver for the DEGPA PCI Gigabit Ethernet NIC cannot deal with a transmit buffer that is within 12 bytes of a 4 gigabyte boundary. This could lead to data corruption. This problem only affects the AlphaServer 4100, AlphaServer DS20, Page 10 AlphaServer ES40, AlphaServer GS80 and GS160, and system upgrades such as the DS25, ES45, and only those systems with at least 4 gigabytes of memory. The fix is to avoid the problem by copying the buffer to a special buffer that is not near such a boundary. The number of times the workaround is invoked is tallied in the internal driver counters (MC LANCP SHOW DEVICE/INTERNAL_COUNTERS) called "4GB workarounds", so you can see if the condition ever does occur. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o Increase the amount of time given for reset by the DEGPA PCI Gigabit Ethernet device driver of the Tigon II chip. The time is increased from 80 to 640 milliseconds. On some systems, insufficient reset time occasionally results in a machine check system crash when the driver touches the device after a reset. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o When user (protocol) is stopped, the user context is not reset correctly by the DEGPA PCI Gigabit Ethernet device driver. This results in the inability to restart the user without rebooting the system. For example, if DECnet is stopped and restarted it may fail to restart. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o The multicast addresses list is not given to the "DEGPA PCI Gigabit Ethernet device again after the driver resets the device to clear a transmit timeout condition. This can happen if the cable is unplugged with transmits outstanding to the device. The consequence is that multicast traffic stops for all users (protocols) until another user is started or an existing user is stopped and restarted. Images Affected: - [SYS$LDR]SYS$EW1000A.EXE o On DEC 7000 systems with the DEFPA PCI FDDI device, which use mailbox hardware to read and write registers, the error bits (which the driver should clear) are not being cleared properly. This may result in a machine check system crash because of stale error bits. Page 11 Images Affected: - [SYS$LDR]SYS$FWDRIVER.EXE o For all LAN devices, modify the VCI transmit path (used by PEDRIVER, DECnet-Plus, TCP/IP, LAST, LAT and others) to verify the transmit request is not too long, incrementing the "Transmit too long" error counter and returning error status to the offending application. This improves the ability to diagnose application problems by identifying the failure to transmit in the device counters and making it more visible. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o For all LAN devices, modify the VCI interface to allow a VCI user to enable promiscuous mode. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o For all LAN devices, Remove the limitation of 255 multicast addresses enabled for a device. This may improve efficiency somewhat by decreasing the multicast filtering work done by the LAN driver. Only the Gigabit Ethernet devices take advantage of this capability. Images Affected: - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.EXE Page 12 - [SYS$LDR]SYS$LAN_FDDI.EXE - [SYS$LDR]SYS$LAN_TR.EXE - [SYS$LDR]SYS$LAN_ATM.EXE o When a DECnet-Plus NCL command, "SHOW FDDI STATION * ALL" request is processed by the LAN driver network management code, if the requested device returns counters data asynchronously, it is possible that R3 is destroyed during the LAN driver processing. This results in an INVEXCPTN crash in NCL.EXE. The problem is that R3 is not preserved cross the call to obtain counters, when it should be. This affects any DECnet-Plus network managed device that returns counters data asynchronously to a counters request, which is all XMI and all FDDI adapters. Images Affected: - [SYS$LDR]NET$CSMACD.EXE - [SYS$LDR]NET$FDDI.EXE o Improve the boot messages for the EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet), ERA (Tulip, DE422 EISA, DE425 EISA, DE205 ISA Ethernet), and EWA (PCI Tulip, DE434, DE435, DE500-XA, DE500-AA, DE500-BA PCI Ethernet) LAN devices, so that more details are available to diagnose boot failures. Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$ERBTDRIVER.EXE - [SYS$LDR]SYS$EIBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE o Add support for booting the Alpha Personal Workstation, XP-1000, over the embedded 21143 chip. Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYS$LDR]SYS$ERBTDRIVER.EXE - [SYSEXE]APB.EXE Page 13 - [SYSEXE]DEBUG_APB.EXE o The boot driver for the DE500 PCI Ethernet device is not restarting auto-negotiation after resetting the device, which results in the link partner (generally an auto-negotiating 10/100 switch) selecting half-duplex mode and the boot driver selecting full-duplex mode. The duplex mode mismatch slows satellite booting considerably. Images Affected: - [SYS$LDR]SYS$EWBTDRIVER.EXE - [SYSEXE]APB.EXE - [SYSEXE]DEBUG_APB.EXE 7 INSTALLATION INSTRUCTIONS: 7.1 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 VMS722_LAN /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt 7.2 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V5.0 Page 14 - De-assign the logicals assigned For example, a sample command file to install the VMS722_LAN-V0500 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS722_LAN/PROD=DEC/BASE=AXPVMS/VER=V5.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 7.3 Special Installation Instructions: If you have already installed the VMS722_LAN-V0400 ECO kit there is no need to install the VMS722_LAN-V0500 kit. To correct the boot problems on the boot disk, execute an MC WRITEBOOT command from a privileged account and answer the prompts as shown: $ MC WRITEBOOT Update VAX portion of boot block (default is Y) : N Update AXP portion of boot block (default is Y) : Y Enter AXP boot file :SYS$COMMON:[SYSEXE]APB.EXE $ 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2003 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 Page 15 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.