**************************** ECO SUMMARY INFORMATION **************************** Release Date: 12-MAR-2007 **************************** ECO SUMMARY INFORMATION **************************** Release Date: 12-MAR-2007 Kit Name: DEC-AXPVMS-VMS83A_LAN-V0100--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 1884 blocks Installation Rating: INSTALL_2 Required Features: LAN Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS83A_UPDATE-V0100 or later Optional Kit Dependencies: None Checksums: VMS83A_LAN-V0100.ZIPEXE Checksum: 1561631814 DEC-AXPVMS-VMS83A_LAN-V0100--4.PCSI$COMPRESSED Checksum: 2518154398 VMS83A_LAN-V0100.ZIPEXE MD5 Checksum: 27ECF674552C866F7DAD63F5633D9227 DEC-AXPVMS-VMS83A_LAN-V0100--4.PCSI$COMPRESSED MD5 Checksum: 93305E6129799A92ABEAA59FED024964 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_LAN-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - LAN 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 V8.3 2.4 New functionality or new hardware support provided: Yes 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_LAN-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 Add Keywords to LAN$SDA 5.1.1.1 Functionality Description: Add keywords to LAN$SDA to represent specific bits to set or clear when changing tracing. Images Affected: - [SYSLIB]LAN$SDA.EXE 5.2 Problems addressed in this kit 5.2.1 VLAN Device Only Allows VLAN Traffic 5.2.1.1 Problem Description: When a VLAN device has been associated with a Broadcom LAN device, the LAN device includes a zero VLAN tag with non-VLAN users for packets transmitted by the device. This may be incompatible with some switches, although, at present, we are not aware of a switch where this presents a problem. Broadcom LAN devices include the DEGPA, DEGXA, A6825A, A6847A, A9782A, A9784A, AB465A, A6794A, and various embedded 5701 or 5703 LOM devices). If incompatible, only VLAN tagged traffic would be possible through the device and switch. For example, given a system with the LAN device EWA, if a VLAN device VLA is created using the EWA device, any packets sent by applications using the EWA device will include a zero VLAN tag. This change will ensure correct behavior so that only packets transmitted on VLAN devices (applications running on VL devices) will include a VLAN tag in the packet. And packets transmitted by applications running on the base LAN device (EWA in the example above) will not include a VLAN tag. Images Affected: Page 3 - [SYS$LDR]SYS$EW1000A.EXE - [SYS$LDR]SYS$EW5700.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: See problem description. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.1.5 Work-arounds: None. 5.2.2 NETDLLERR Bugcheck 5.2.2.1 Problem Description: The system can crash with a NETDLLERR bugcheck. Images Affected: - [SYS$LDR]SYS$EI1000.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. Page 4 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: When an Intel Gigabit device receives packets that are longer than 8192 bytes, the device writes the packet data into two consecutive receive ring entries. Under heavy load it is possible that the second ring entry has not been updated when the driver checks it, resulting in the system crash. This change corrects the problem and allows the oversize packets to be sent continuously to the device without resulting in a driver crash. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.2.5 Work-arounds: None. 5.2.3 Add DEB_HEX Value Type to LAN$SDA 5.2.3.1 Problem Description: Add the missing DEB_HEX deooding value type to LAN$SDA Images Affected: - [SYSLIB]LAN$SDA.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) None. Page 5 5.2.3.3 Problem Analysis: See problem description. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.3.5 Work-arounds: None. 5.2.4 Performance Degradation 5.2.4.1 Problem Description: Because of buffer allocation problems, the system may experience a performance degradation. Images Affected: - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$EW1000A.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: The LAN common receive routine is not keeping the correct count of allocated buffers for FAILOVER sets composed of VLAN and non-VLAN capable devices. Also, the DEGPA driver is wrongly bumping the allocated buffer count when buffer allocation fails. Page 6 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.4.5 Work-arounds: None. 5.2.5 Inaccurate Bytes Received Counter 5.2.5.1 Problem Description: The 'bytes received' counter should include all bytes of each packet including header bytes. The driver was inadvertently subtracting the header bytes, so the counters value was off by 18 bytes per packet. Images Affected: - [SYS$LDR]SYS$EW5700.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: See problem description. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.5.5 Work-arounds: None. Page 7 5.2.6 Bad VLAN/FAILSET Configuration May Crash a System 5.2.6.1 Problem Description: The system may crash if a physical LAN NIC is used to make a VLAN device, then the same physical device is used to to make a FAILOVER SET. Images Affected: - [SYS$LDR]SYS$LLDRIVER.EXE - [SYS$LDR]SYS$VLANDRIVER.EXE 4 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: See problem description 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.6.5 Work-arounds: None. 5.2.7 Inaccurate Bytes Received Counter 5.2.7.1 Problem Description: After upgrading to OpenVMS V8.3, MOPDLL settings in the LANCP permanent device database do not work. They are visible when doing a LANCP LIST command but fail to take effect during system startup. Doing a LANCP CONVERT DEVICE does not correct the problem. Images Affected: Page 8 - [SYSEXE]LANCP.EXE - [SYSEXE]LANACP.EXE 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) QXCM1000310355 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: When LANACP reads an older version of the LAN permanent device database (LAN$DEVICE_DATABASE.DAT), it automatically converts the data to the current version. However, the prior code depended on the record size of each new version to be larger than the previous versions. The device record size in V8.3 shrunk, causing a silent RMS RTB error. Also, the latest version contains a set of 'valid' bits that signify if a device parameter was valid in the record. The MOPDLL 'valid' bits were not being set for older database. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.7.5 Work-arounds: None. 5.2.8 SDA LAN HELP Command Terminates SDA 5.2.8.1 Problem Description: Entering a LAN HELP command in SDA can result in and error and termination of SDA. $ ANALYSE/SYS OpenVMS system analyzer SDA> LAN HELP %CLI-F-SYNTAX, error parsing 'ADDRESS' -CLI-E-ENTNF, specified entity not found in command tables Page 9 $ Images Affected: - [SYSLIB]LAN$SDA.EXE 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) QXCM1000371368 5.2.8.2.2 QAR(s) None. 5.2.8.3 Problem Analysis: See problem description. 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS after Alpha V8.3 5.2.8.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSLIB]LAN$SDA.EXE (new image) Image Identification Information image name: "LAN$SDA" image file identification: "X-44" image file build identification: "0080070007" link date/time: 15-NOV-2006 13:59:04.01 linker identification: "A13-03" Overall Image Checksum: 3321472708 o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-52" Page 10 image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:58.20 linker identification: "A13-03" Overall Image Checksum: 1661583049 o [SYSEXE]LANCP.EXE (new image) Image Identification Information image name: "LANCP" image file identification: "X-83A1" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:57.97 linker identification: "A13-03" Overall Image Checksum: 1150978786 o [SYS$LDR]SYS$EI1000.EXE (new image) Image Identification Information image name: "SYS$EI1000" image file identification: "X-24" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:01.15 linker identification: "A13-03" Overall Image Checksum: 3602879448 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-64" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:59.80 linker identification: "A13-03" Overall Image Checksum: 2290813298 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700" image file identification: "X-61" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:00.52 linker identification: "A13-03" Overall Image Checksum: 4248753802 o [SYS$LDR]SYS$EWXFRAME.EXE (new image) Image Identification Information image name: "SYS$EWXFRAME" image file identification: "X-18" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:02.17 Page 11 linker identification: "A13-03" Overall Image Checksum: 1533687700 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-9" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:38.75 linker identification: "A13-03" Overall Image Checksum: 575030692 o [SYS$LDR]SYS$LLDRIVER.EXE (new image) Image Identification Information image name: "SYS$LLDRIVER" image file identification: "X-23" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:02.69 linker identification: "A13-03" Overall Image Checksum: 842429645 o [SYS$LDR]SYS$VLANDRIVER.EXE (new image) Image Identification Information image name: "SYS$VLANDRIVER" image file identification: "X-14" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:55.82 linker identification: "A13-03" Overall Image Checksum: 64235250 o [SYS$LDR]XX$SDA.EXE (new image) Image Identification Information image name: "XX$SDA" image file identification: "X-3" image file build identification: "0080070007" link date/time: 15-NOV-2006 13:59:03.85 linker identification: "A13-03" Overall Image Checksum: 1752586015 7 INSTALLATION INSTRUCTIONS Page 12 7.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. 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS83A_LAN-V0100.ZIPEXE 7.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 VMS83A_LAN[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. 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. Page 13 Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.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=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_LAN-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_LAN/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 14 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 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.