======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_LAN-V0400 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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_LAN-V0300 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0900 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 VMS84I_LAN-V0400 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Incorrect user buffer was reflected when Jumbo frame is enabled on the Logical LAN device. 5.2.1.1 Problem Description: When Jumbo frame is enabled for the Logical LAN device which includes EW57711 10G as a failover device, incorrect buffer size is reflected for the LAN user. The buffer size reflected is 1.5KB instead of 7.5KB. As a result LAN application was not able to use Jumbo size buffer. Please refer the following customer advisory on the jumbo frame size restriction for EW57711 device. http://h41302.www4.hp.com/km/saw/view.do?docId=emr_na-c03499018 Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$ER57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$ER57711_MON.EXE - [SYS$LDR]SYS$EW57711DRIVER.STB - [SYS$LDR]SYS$EW57711DRIVER_MON.STB 5.2.1.2 Quix and PTR cases reporting this problem: Page 3 5.2.1.2.1 Quix Cases QXCM1001225887 QXCM1001240914 5.2.1.2.2 PTR(S) 75-126-270 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.1.4 Work-arounds: - None 5.2.2 OpenVMS 8.4 LAT Control Program Hang. 5.2.2.1 Problem Description: Creation of LAT link on a physical port whose link status is DOWN will hangs forever during boot waiting on LATCP commands. This issue has been fixed. Images Affected: - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]SYS$LAN_CSMACD.STB - [SYS$LDR]SYS$LAN.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001227049 Page 4 5.2.2.2.2 PTR(S) None 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.2.4 Work-arounds: Use LAN_FLAGS bit 14 Ex: SYSGEN >SET LAN_FLAGS 16384 SYSGEN> W C SYSGEN > W A Note: With this patch, it is no longer necessary to workaround this issue. 5.2.3 Link flaps are occurring on NC364 module in the absence of inter-connecting module. 5.2.3.1 Problem Description: Link flaps occur on a random port on the NC364 quad port module, when only one port has physical connectivity and remaining ports do not. Images Affected: - [SYS$LDR]SYS$EI1000.EXE - [SYS$LDR]SYS$EI1000_MON.EXE - [SYS$LDR]SYS$EI1000.STB - [SYS$LDR]SYS$EI1000_MON.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001272578 QXCM1001265662 5.2.3.2.2 PTR(S) 75-126-359 Page 5 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity fter V8.4 5.2.3.4 Work-arounds: None 5.2.4 "INVEXCEPTN, Exception while above ASTDEL" - system crashed while processing UCB list. 5.2.4.1 Problem Description: UCB list gets corrupted while mapping an incoming 802.2 packet to a corresponding UCB. The problem occurs due to a syncronization issue. This issue is fixed. Images Affected: - [SYS$LDR]SYS$LAN_CSMACD.EXE - [SYS$LDR]SYS$LAN.EXE - [SYS$LDR]NET$CSMACD.EXE - [SYS$LDR]SYS$LAN_CSMACD.STB - [SYS$LDR]SYS$LAN.STB - [SYS$LDR]NET$CSMACD.STB 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001289986 QXCM1001268175 5.2.4.2.2 PTR(S) 75-126-307 Page 6 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.4.4 Work-arounds: - None 5.2.5 Stand-by device in Logical LAN Failoverset receives broadcast packets. 5.2.5.1 Problem Description: When a physical device switches from primary to stand-by mode in a Logical LAN failover set, it continues to receive broadcast messages, i.e. messages sent to MAC address FF-FF-FF-FF-FF-FF. A device makes this switch either due to a network issue which causes to the link to go down or when the user forces the switch using the MC LANCP device reset command. In both these cases we observe that an initialization routine erroneously sets the receive mode of the device to normal, thereby enabling it to continue receiving the broadcast packets. Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$EW57711DRIVER.STB - [SYS$LDR]SYS$EW57711DRIVER_MON.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001351981 5.2.5.2.2 PTR(S) 75-126-405 Page 7 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.5.4 Work-arounds: System reboot. 5.2.6 Certain logical LAN devices do not get created after the system boots. 5.2.6.1 Problem Description: The LAN primitive database used during the system boot is assumed to be present in the boot disk's SYSEXE path. The access to the primitive database while updating it depends on the SYS$SYSROOT logical. Thus in environments where SYS$SYSROOT logical is defined to point to multiple devices with first entry in the search path pointing to a device other than the currently booted device, the newly created logical LAN devices might not appear after the system boots. This issue is fixed. Images Affected: - [SYSEXE]LANCP.EXE 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001326476 5.2.6.2.2 PTR(S) 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.6.4 Work-arounds: Copying the LAN$DEVICE_DATABASE.SEQ file from the SYS$SYSTEM directory on a running system to SYS$SPECIFIC:[SYSEXE] (correct boot device ) will ensure that the primitive database file refered during the boot has the right contents. Page 8 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_LAN patch kits can be found in the following files: o VMS84I_LAN-V0100.RELEASE_NOTES o VMS84I_LAN-V0200.RELEASE_NOTES o VMS84I_LAN-V0300.RELEASE_NOTES 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 VMS84I_LAN /VERSION=V4.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_LAN /VERSION=V4.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_LAN /VERSION=V4.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]LANCP.EXE (new image) Image Identification Information Image name: "LANCP" Image file identification: "X-93" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:18:09.27 Overall Image Checksum: 28194A1 o [SYS$LDR]NET$CSMACD.EXE (new image) Image Identification Information Image name: "CSMACD - NETWORK MANAGEMENT" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:18:03.33 Overall Image Checksum: CC2C9EF8 Page 9 o [SYS$LDR]SYS$EI1000.EXE (new image) Image Identification Information Image name: "SYS$EI1000DRIVER" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:18:42.51 Overall Image Checksum: E689AD91 o [SYS$LDR]SYS$EI1000_MON.EXE (new image) Image Identification Information Image name: "SYS$EI1000DRIVER_MON" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:18:46.87 Overall Image Checksum: 5C9EA2CB o [SYS$LDR]SYS$ER57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:12.99 Overall Image Checksum: 7C4D33EC o [SYS$LDR]SYS$ER57711_MON.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:19.34 Overall Image Checksum: 7F83B8E3 o [SYS$LDR]SYS$EW57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:12.99 Overall Image Checksum: 7C4D33EC Page 10 o [SYS$LDR]SYS$EW57711_MON.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:19.34 Overall Image Checksum: 7F83B8E3 o [SYS$LDR]SYS$LAN.EXE (new image) Image Identification Information Image name: "SYS$LAN" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:37.45 Overall Image Checksum: 5D4C63C6 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information Image name: "SYS$LAN_CSMACD" Image file identification: "X-5" Image build identification: "0100000136" linker identification: "Linker I02-37" Link Date/Time: 10-JUL-2014 17:19:39.89 Overall Image Checksum: 19C23370 o [SYS$LDR]NET$CSMACD.STB (new file) o [SYS$LDR]SYS$EI1000.STB (new file) o [SYS$LDR]SYS$EI1000_MON.STB (new file) o [SYS$LDR]SYS$EW57711DRIVER.STB (new file) o [SYS$LDR]SYS$EW57711DRIVER_MON.STB (new file) o [SYS$LDR]SYS$LAN.STB (new file) o [SYS$LDR]SYS$LAN_CSMACD.STB (new file) 8 INSTALLATION INSTRUCTIONS Page 11 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 Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_LAN-V0400.ZIPEXE 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 VMS84I_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 12 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=HP/BASE=I64VMS/VER=V4.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_LAN-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_LAN/PRODUCER=HP/BASE=I64VMS/VER=V4.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! Page 13 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2014 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.