======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_FIBRE_SCSI-V0400 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - MDS600 Storage Enclosure Diagnostics support with OpenVMS. - HP LTO-5SB3000c Tape Blades support with OpenVMS. - VMS84I_UPDATE-V0700 kit installed on Rx2800 i2 servers and BL8x0 i2 server blades. - VLS tape devices attached through Emulex FC HBA placed on any supported integrity servers running OpenVMS. - MSA$UTIL Fixes. 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: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_FIBRE_SCSI-V0300 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: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0700 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_FIBRE_SCSI-V0400 KIT 5.1 New functionality addressed in this kit 5.1.1 HP LTO-5 SB3000c Tape Blades. 5.1.1.1 Problem Description: Problem Description: The HP LTO-5 SB3000c Tape Blade delivers direct attached storage for c-Class servers. The enclosure backplane provides a PCIe connection to the adjacent c-Class server blade and enables high performance storage access without any additional cables. SB3000c Tape Blade deliver versatile, integrated tape backup solutions that are ideal for a data protection solution integrated into the blade enclosure. This FIBRE_SCSI kit supports SB3000c Tape Blades. Images Affected: - [SYSEXE]MSA$UTIL.EXE 5.1.1.2 Quix and PTR cases reporting this problem: Page 3 5.1.1.2.1 Quix Cases None. 5.1.1.2.2 PTR(s) 75-126-262 5.1.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.1.1.4 Work-arounds: None. 5.1.2 MDS600 Storage Enclosure Diagnostics support. 5.1.2.1 Problem Description: o MDS600 Storage Enclosure Diagnostics support Smart array controller driver (SYS$PKRDRIVER) is enabled to collect Serial Output Buffer (SOB) data from controller. This will help in collection of diagnostics information from a MDS600 storage enclosure. o Supported Configuration and Firmware Revisions Server Blade : HP BL8x0 i2 blades P700m Smart Array Controller : 7.22 3Gb SAS Switch Firmware : 2.2.15.0 MDS600 Firmware : 2.66 ________________________ Note ________________________ MDS600 diagnostic information can be collected only from firmware serial log of P700m smart array controller placed in bay 1 server blade of c7000 enclosure. ______________________________________________________ o To Enable SOB Set the 'FIBRE_SCSI_RSV1' sysgen parameter value to 268435456 (decimal). FIBRE_SCSI_RSV1 is a DYNAMIC parameter. FIBRE_SCSI_RSV1 is a 32-bit mask, with the following bit(s) defined. Each bit can be set independently. The value of the system parameter is the sum of the values of the bits that have been set. Remaining or undefined values are reserved for HP use only. Page 4 Bit Mask Description 29 268435456 0 = Disable SOB collection. (decimal) 1 = Enable SOB collection. ____________________________ Note _____________________________ If 'FIBRE_SCSI_RSV1' sysgen parameter is cleared then all the previous SOB data collected in ring buffer will be flushed. _______________________________________________________________ $ MCR SYSGEN SYSGEN> SHOW FIBRE Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- FIBRE_SCSI_RSV1 0 0 0 -1 D SYSGEN> SYSGEN> SET FIBRE 268435456 SYSGEN> WRITE CURRENT SYSGEN> WRITE ACTIVE SYSGEN> EXIT $ $ MCR SYSGEN SYSGEN> SHOW FIBRE Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- FIBRE_SCSI_RSV1 268435456 0 0 -1 D SYSGEN> EXIT o Getting SOB Data SOB data can be collected through PKR SDA extension. $ analyze/system OpenVMS system analyzer SDA> pkr show devices !This command shows the controller name PKR Devices ----------- SPDT Port Model ID Default ---------------------------------------- 88DB40C0 PKB0 SA-P700 323D * 88277BC0 PKA0 SA-P410i 3245 SDA> SDA> pkr set dev PKB0 !This command sets the default controller. SDA> SDA> PKR GET SOB_RING Page 5 Displays the firmware serial log which contains diagnostic information of storage enclosures. ____________________________ Note ______________________ SOB_RING is a circular buffer and the entries will wrap around once the buffer is full. ________________________________________________________ Images Affected: - [SYS$LDR]SYS$PKRDRIVER.EXE - [SYS$LDR]SYS$PKRDRIVER.STB - [SYSLIB]PKR$SDA.EXE 5.1.2.2 Quix and PTR cases reporting this problem: 5.1.2.2.1 Quix Cases None. 5.1.2.2.2 PTR(s) 75-131-10 5.1.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.1.2.4 Work-arounds: None. 5.2 Problems addressed in this kit 5.2.1 1.Adding a check for the maximum size of the LUN that can be created while combining unequal sizeddisks with the specified raid level. 2.Adding a check for size of new disks while expanding LUNS 3.In msa$util the show controller/full displayed question mark. Page 6 5.2.1.1 Problem Description: 1.Msa$util has been modified to check the maximum size of the LUN that can be created while using unequal sized disks with a specified raid level. 2.Raid expansion failed when expanding a LUN with a new disk which had a smaller capacity as compared to those combined initially resulting in the creation of a hole. A check has been added to compare the sizes of the disks specified originally to create the raid unit and the disks that were used to expand. 3.The show controller/full command returned question marks for physical connectors as the physical connectors could not be identified correctly .It has been modified to display the external connectors. Images Affected: - [SYS$EXE]MSA$UTIL.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases None 5.2.1.2.2 PTR(s) 75-120-160 75-129-3 75-128-54 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 Attempting to mount VLS devices connected through Emulex FC HBA causes hang Page 7 5.2.2.1 Problem Description: The wrongly calculated FCP response size caused the read requests from mount command to fail which in turn sends command in a loop causing hang. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$PGADRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001206204 5.2.2.2.2 PTR(s) 75-126-241 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: None. 5.2.3 System crash with INCONSTATE bugcheck at SYS$PKRDRIVER+43650. 5.2.3.1 Problem Description: Rx2800 i2 servers and BL8x0 i2 server blades with VMS84I_UPDATE-V0700 installed may experience an INCONSTATE bugcheck at SYS$PKRDRIVER+43650 (PKR$MAP_BUFFER_MW_C+0240). This can occur if there is insufficient contiguous nonpaged memory pool in the system (and can also occur if the NPAGEDYN and NPAGEVIR SYSGEN parameters are undersized). Images Affected: - [SYS$LDR]SYS$PKRDRIVER.EXE Page 8 - [SYS$LDR]SYS$PKRDRIVER.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001235197 QXCM1001238476 QXCM1001246441 QXCM1001246643 QXCM1001250095 QXCM1001250152 5.2.3.2.2 PTR(s) 75-126-303 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.3.4 Work-arounds: If customer is not using any devices claimed by SYS$PKRDRIVER, the auto-configuration of devices in this driver can be disabled to avoid the crash. $MCR SYSMAN SYSMAN>IO SET EXCLUDE=PK* SYSMAN> IO SHOW EXCLUDE ***Disabling ports this way requires a reboot*** 5.2.4 MSA$UTIL-Display of external connectors in Show controller/bus command . 5.2.4.1 Problem Description: MSA$UTIL failed to display the external connectors in case of external controllers(p411,p812). Images Affected: - [SYSEXE]MSA$UTIL.EXE Page 9 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases None. 5.2.4.2.2 PTR(s) 75-13-2124 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 System crash with INCONSTATE bugcheck at SYS$PGADRIVER + 15B80. 5.2.5.1 Problem Description: A system crash with Access violation is seen on systems while processing I/Os due to a bad Emulex Fibre Channel HBA. This occurs due to an invalid command length reported by the FC HBA. While trying to process this corrupt command the driver BUGCHECKs due to access violation. Images Affected: - [SYS$LDR]SYS$PGADRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001113140 5.2.5.2.2 PTR(s) None. Page 10 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: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_FIBRE_SCSI patch kits can be found in the following files: o VMS84I_FIBRE_SCSI-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0200.RELEASE_NOTES o VMS84I_FIBRE_SCSI-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_FIBRE_SCSI /VERSION=V4.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_FIBRE_SCSI /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_FIBRE_SCSI /VERSION=V4.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]MSA$UTIL.EXE (new image) Image Identification Information Image name: "MSA$UTIL" Image file identification: "X-34" Image build identification: "0100000090" linker identification: "Linker I02-37" Link Date/Time: 12-NOV-2012 18:02:54.39 Overall Image Checksum: 520CDF5 Page 11 o [SYSLIB]PKR$SDA.EXE (new image) Image Identification Information Image name: "PKR$SDA" Image file identification: "X-14" Image build identification: "0100000090" linker identification: "Linker I02-37" Link Date/Time: 12-NOV-2012 18:02:56.14 Overall Image Checksum: E945AF58 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information Image name: "SYS$PGADRIVER" Image file identification: "X-5" Image build identification: "0100000090" linker identification: "Linker I02-37" Link Date/Time: 12-NOV-2012 18:02:43.37 Overall Image Checksum: A7BF9A35 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKRDRIVER" Image file identification: "X-5" Image build identification: "0100000090" linker identification: "Linker I02-37" Link Date/Time: 12-NOV-2012 18:02:38.48 Overall Image Checksum: E322DA7 8 INSTALLATION INSTRUCTIONS 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. Page 12 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_FIBRE_SCSI-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_FIBRE_SCSI[/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. 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 Page 13 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_FIBRE_SCSI-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_FIBRE_SCSI/PRODUCER=HP/BASE=I64VMS/VER=V4.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2012 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 14 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.