======================================================================= VMS Software, Inc. OpenVMS ECO Kit Release Notes ======================================================================= 1 KIT NAME: VMS842L3I_LAN-V0800 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1: To be installed by all customers. This installation rating serves as a guide to which customers should apply this remedial kit. Reference the attached Disclaimer of Warranty and Limitation of Liability Statement. 2.2 Reboot Requirement: A reboot is required after installing this kit. VMS Software, Inc. strongly recommends that a reboot be performed immediately after kit installation to avoid system instability. If you are installing this kit in a VMScluster, any systems that share the same system disk with the installing system must also be rebooted in order to make use of the new images. 2.3 Version(s) of VSI OpenVMS to which this kit may be applied: VSI OpenVMS for Integrity Servers V8.4-2L3 3 KITS SUPERSEDED BY THIS KIT: None Note: There are no previous LAN patch kits for VSI OpenVMS for Integrity Servers V8.4-2L3. All previously released LAN patches for all prior VSI OpenVMS versions were directly included in V8.4-2L3. This patch kit is numbered as V8.0 to keep in synch with patch kit content for other VSI OpenVMS versions. 4 KIT DEPENDENCIES: None 5 PROBLEMS ADDRESSED IN THIS KIT 5.1 Disallow incorrectly configured multi-function mode in AM225A card 5.1.1 Problem Description An AM225A card may be incorrectly configured as multi-function mode rather than single function mode. Multi-function mode is not supported by VSI OpenVMS. When set to multi-function mode, eight ER devices are configured with six of them marked offline. This may adversely affect operation of the other two devices. In single function mode, only the two supported devices are configured. The previous version of the relevant drivers did not issue any warning messages if the card was in multi-function mode, and incorrectly allowed use of the two devices which happened to initialize as online and available. The version of the drivers supplied in this patch kit will issue the following messages on the console terminal should the card be in multi-function mode at boot: %ERA0, Multi-function mode enabled, only single function mode is allowed %ERA0, Reboot and select in device configuration menu %ERA0, Failed during ew$init %ERB0, Multi-function mode enabled, only single function mode is allowed %ERB0, Reboot and select in device configuration menu %ERB0, Failed during ew$init %ERC0, Failed during ew$init %ERD0, Failed during ew$init %ERE0, Failed during ew$init %ERF0, Failed during ew$init %ERG0, Failed during ew$init %ERH0, Failed during ew$init Note that all the devices are marked unusable with the drivers supplied in this patch kit. If your system includes an AM225A card and you have been using it while incorrectly configured as a multi-function device, those devices will no longer work with this patch kit applied until the card is correctly configured in single function mode. To determine if you have an incorrectly configured card, use the command: $ SHOW DEVICE ER If you see eight devices ERA0 thru ERH0 with the last six offline, your AM225A card must be reconfigured to single function mode. Resetting the device must be done while the machine is halted. Reset the system and select the Device Manager, then select the Device Configuration Menu for each port. For "Force SF Mode", select "" then "S" to save for all the ports. Please contact VSI Support if you are unfamiliar with changing the device configuration in the console subsystem for Integrity Servers. 5.1.2 Images and/or Files Affected: [SYS$LDR]SYS$EW57711.EXE [SYS$LDR]SYS$EW57711_MON.EXE [SYS$LDR]SYS$ER57711.EXE [SYS$LDR]SYS$ER57711_MON.EXE 5.1.3 VSI case identifier Netsuite NS1876 5.1.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.2 Lowercase commands entered in LANCP may fail 5.2.1 Problem Description If a process with PARSE_STYLE set to EXTENDED mode enters commands in LANCP using lower case, some fields which should be forced to upper case are left in lower case. This causes incorrect behavior for selecting or comparing device or node names for various commands. LANCP has been modified to uppercase input where appropriate. 5.2.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE 5.2.3 VSI case identifier Netsuite NS2022 5.2.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.2.5 Workaround A simple workaround is to enter only uppercase commands, device names, and node names in LANCP operations. 5.3 BE3 device may fail to initialize due to BMBX timeout 5.3.1 Problem Description An Emulex BE3 device (NC553i LOM and others) may encounter a timeout during initialization. A message displayed on the console terminal indicates: Timeout waiting for BMBX ready, 0x where is some hexadecimal value. The device is left offline and unusable until the next boot. The BE3 is a dual ported device. Firmware activity on one port can block activity on the other port. This occurs during device initialization. On some systems, the timeout period was too short to allow correct initialization. The timeout value has been raised to accommodate delayed processing during initialization. 5.3.2 Images and/or Files Affected: [SYS$LDR]SYS$EWBE3.EXE [SYS$LDR]SYS$EWBE3_MON.EXE 5.3.3 VSI case identifier Netsuite NS2302 Jira ND-174 5.3.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.4 Changing the size of a LAN Failover device may leave size unchanged 5.4.1 Problem Description The size of a LAN Failover device may be specified as STANDARD or JUMBO. If the size is changed from LANCP but no other changes are also requested, the request is ignored and the size is left unchanged until the next reboot or restart of LANACP. The LAN Failover handling has been modified to always convey any size change regardless of other device information on a command. 5.4.2 Images and/or Files Affected: [SYSEXE]LANCP.EXE [SYSEXE]LANACP.EXE 5.4.3 VSI case identifier None 5.4.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 5.4.5 Workaround Disable the LAN Failover set then re-enable it, or reboot the system. 5.5 Newer firmware in embedded BE3 LAN device may fail to initialize 5.5.1 Problem Description An Emulex BE3 device (NC553i LOM and others) may encounter a timeout during initialization, leaving the device offline and unusable. A message displayed on the console terminal indicates: Timeout waiting for BMBX ready, 0x where is some hexadecimal value. This is the same symptom as described above in section 5.3, but the cause is different. Newer BE3 firmware fails to correctly perform a "VLAN config" function. By experimentation, VSI has determined that BE3 firmware version 4.9.416.12 succeeds but version 4.9.416.17 fails. VSI has no way to influence the firmware development, and hardware support is uncertain. By reverting to previous commands which performed the same configuration handling without a "VLAN config" command, the newer firmware initializes correctly. To avoid other potential issues with the later firmware, newer optional functionality has been removed from the normal driver image, SYS$EWBE3.EXE. The additional functionality includes additional data in various internal counters as displayed via the LANCP command SHOW DEVICE/INTERNAL/DEBUG. The fields include PHY and transceiver information and BE3 chip temperature. Flow control settings are also queried every two hours. The newer optional functionality has been retained in the _MON version of the driver. This is the driver which is loaded when the SYSTEM_CHECK system parameter is set to 1. Should you require the added new functionality, you may force this driver to load without setting SYSTEM_CHECK (which has drastic performance implications in other parts of the system). Use the command: $ COPY SYS$COMMON:[SYS$LDR]SYS$EWBE3_MON.EXE - SYS$COMMON:[SYS$LDR]SYS$EWBE3.EXE to enable the optional functionality. VSI recommends that only very experienced network individuals should ever use these advanced options. 5.5.2 Images and/or Files Affected: [SYS$LDR]SYS$EWBE3.EXE [SYS$LDR]SYS$EWBE3_MON.EXE 5.5.3 VSI case identifier Netsuite NS2822 5.5.4 Release Version of VSI OpenVMS that will contain this change: Next VSI OpenVMS for Integrity Servers release after V8.4-2L3 6 PROBLEMS ADDRESSED FROM PREVIOUS KITS None 7 IMAGES OR FILES REPLACED: [SYS$LDR]SYS$ER57711.EXE Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:06.51 Image Checksum (MD5): 0DF746608C764EEB2F5465E40E1E8B4E [SYS$LDR]SYS$ER57711_MON.EXE Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:07.21 Image Checksum (MD5): CA2682D25A8757D72211D173EC1DA0D6 [SYS$LDR]SYS$EW57711.EXE Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:06.51 Image Checksum (MD5): 0DF746608C764EEB2F5465E40E1E8B4E [SYS$LDR]SYS$EW57711_MON.EXE Image name: "SYS$EW57711DRIVER_MON" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:07.21 Image Checksum (MD5): CA2682D25A8757D72211D173EC1DA0D6 [SYS$LDR]SYS$EWBE3.EXE Image name: "SYS$EWBE3DRIVER" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:07.82 Image Checksum (MD5): 59C27D0E67F256A750C23100D6752A66 [SYS$LDR]SYS$EWBE3_MON.EXE Image name: "SYS$EWBE3DRIVER_MON" Image file identification: "X-5" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:07.98 Image Checksum (MD5): 0252D9A5041992D8842D8DD6CC4A7AF9 [SYSEXE]LANACP.EXE Image name: "LANACP" Image file identification: "X-29" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:03.61 Image Checksum (MD5): 7837BA5D3BE0EA95FF7033E03C6446ED [SYSEXE]LANCP.EXE Image name: "LANCP" Image file identification: "X-93A3" Image build identification: "XFWL-C6E-000017" Link identification: "Linker I02-37" Link Date/Time: 28-AUG-2021 15:56:03.20 Image Checksum (MD5): 926F2A09BE6437FE2FB959C2AA8BE300 Note: VMS Software, Inc. will only distribute kits in signed form. There is no need for most customers to compare file checksums for security or kit integrity reasons. However, some sites may require such checking even when using signed kits. The image or file checksums are supplied (in MD5 format) to provide comparisons to the extracted final kit files. To find a file checksum, use: $ CHECKSUM/ALGORITHM=MD5 filename $ SHOW SYMBOL CHECKSUM$CHECKSUM Note: Because a file or image may be replaced by multiple patch kits over time, a PCSI generation number is used to ensure that the latest version of the file or image is preserved on your system during PRODUCT INSTALL of a patch kit. Should a particular kit installation discover a newer version of a file or image in place on the system disk, the following message will be displayed: %PCSI-I-RETAIN, file will not be replaced because file from kit has lower generation number This is a normal occurrence depending on the order of kit installation. The correct version of the file or image will remain on the system after the current kit installation. The %PCSI-I-RETAIN message is informational only and does not indicate a problem. 8 INSTALLATION INSTRUCTIONS 8.1 Compressed File This kit is provided as a self-extracting ZIPEXE file. To expand this file to the installable PCSI kit, execute the file image with the following command: $ RUN VMS842L3I_LAN-V0800.ZIPEXE 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 VMS842L3I_LAN [/SOURCE=location of kit] The kit location may be a tape drive, CD/DVD, 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. This kit requires the use of /RECOVERY_MODE and /SAVE_RECOVERY_DATA and will automatically set them; they do not need to be present on the command line. The release notes for any kit may be extracted prior to kit installation using the PRODUCT EXTRACT RELEASE_NOTES command. User-selectable options for installation behavior and scripting are available in this kit, refer to Appendix A for further details. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 9 COPYRIGHT ******************************************************************** * * * VMS SOFTWARE, INC. CONFIDENTIAL. This software is confidential * * proprietary software licensed by VMS Software, Inc., and is not * * authorized to be used, duplicated or disclosed to anyone without * * the prior written permission of VMS Software, Inc. * * Copyright 2021 VMS Software, Inc. * * * ******************************************************************** 10 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 VMS SOFTWARE, INC. 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. 11 PATCH ID I64VMS-VMS842L3I_LAN-V0800--4 APPENDIX A - User-selectable control options and scripting considerations Controlling kit behavior for introductory questions --------------------------------------------------- This kit provides user-selectable control options for kit dialogue interaction and automated scripting capability as described here in this appendix. The general form of a VSI ECO patch kit, when using PRODUCT INSTALL, consists of three initial questions regarding these topics: 1. System disk backup: A reminder that VSI recommends backing up the system disk before installing patches, followed by a "Do you want to continue?" yes/no question, default = YES. 2. Reboot requirement: A summary of whether the kit being installed requires a system reboot, followed by a "Do you want to continue?" yes/no question, default = YES. 3. Archival of updated files: A description of saving an "_OLD" copy of each image or file updated by the kit, followed by a "Do you want to save "_OLD" copies of replaced files?" yes/no question, default = NO. Other questions may be asked later, depending on the target disk or system environment or other kit-specific requirements. Note: An initial "Do you want to continue?" question may be asked directly by the PCSI utility during any PRODUCT command -- this has nothing to do with the kit being used. To avoid that question, you must supply sufficient detail to uniquely identify the product you wish to use and specify /OPTIONS=NOCONFIRM on the PRODUCT command. Control options are available to customize the dialogue for the initial three kit questions. The controls are logical names, which may be defined in the process logical name table with a value of YES or NO. To modify the behavior of the VSI ECO patch kit regarding the initial questions, define one or more of the following logical names before issuing the PRODUCT INSTALL command. o To skip one or more of the questions, define the corresponding logical name shown here to YES: SKIP$BACKUP - Skip system backup awareness question. SKIP$REBOOT - Skip system reboot awareness question. SKIP$ARCHIVE_OLD - Skip question about saving "_OLD" files. This will take the default, which is NO. SKIP$INTRO - Skip all three of the above questions. o To specifically override the default for saving "_OLD" files, define this logical name to YES or NO: VSIKIT$ARCHIVE_OLD - Sets an answer for saving "_OLD" files behavior. This will skip the archive "_OLD" files question regardless of the above SKIP$* logical names. o Two additional logical names may be defined as YES to modify the amount of explanatory text displayed for each question: VSIKIT$VERBOSE - Shows all explanatory text for questions. VSIKIT$BRIEF - Skips some general details in the explanations. The default if neither name is defined is VERBOSE. If both names are defined to YES, VERBOSE overrides BRIEF. The BRIEF form is displayed for any questions that are skipped. For example, to skip all three questions but save an archive "_OLD" copy of each replaced file: $ DEFINE VSIKIT$ARCHIVE_OLD YES $ DEFINE SKIP$INTRO YES $ PRODUCT INSTALL Standard behavior for YES/NO questions asked during kit installation -------------------------------------------------------------------- Any YES/NO questions asked during kit installation now follow these rules: 1. Ctrl-Y issued while a question is being asked will force the current PRODUCT operation to terminate. This is completely safe to do while the initial three questions are being asked during PRODUCT INSTALL as no changes have yet been made to the target disk. 2. Some questions may ignore Ctrl-Y and ask for a specific answer, if aborting the current operation may have side effects. PCSI may trap Ctrl-Y directly for some PRODUCT operations. Ctrl-Y may be disabled during some sensitive kit processing. 3. The default YES/NO answer is automatically chosen if a kit is installed from a batch job, unless explicitly overridden by a logical name which provides the particular value, such as VSIKIT$ARCHIVE_OLD. Installing a kit from a batch job --------------------------------- To install a kit from a batch job you will need to fully qualify the kit name so PCSI will have enough information to select the kit without asking for confirmation. For example, to install this kit: $ PRODUCT INSTALL VMS842L3I_LAN/VERSION=V8.0/OPTIONS=NOCONFIRM If the kit is located in a directory other than the current default directory, you will also need to add the qualifier: /SOURCE= For a batch job, any YES/NO question will automatically select the default answer. Use the control logical names explained above to modify the behavior if necessary. For the system disk backup and reboot questions, the batch behavior is identical to the default. For the save "_OLD" files question, define the VSIKIT$ARCHIVE_OLD logical name to YES if you want to save copies of the files, since the batch default is NO. Deprecated logical names from HPE patch kits -------------------------------------------- The three names listed below were used by older VSI OpenVMS patch kits for compatibility with HPE patch kit behavior. These old names continue to function, but VSI encourages you to modify any scripts you may have to use the new names shown instead: Old name New name --------------- -------------------- NO_ASK$BACKUP SKIP$BACKUP NO_ASK$REBOOT SKIP$REBOOT ARCHIVE_OLD VSIKIT$ARCHIVE_OLD