================================================================ HP OpenVMS Update Kit for Integrity Servers VMS84I_UPDATE-V0700 Release Notes ================================================================ 1 KIT NAME: VMS84I_UPDATE-V0700 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). _______________________ Caution _______________________ Do not remove the kit if the controllers are configured in HBA mode. If the kit is removed, the 1 system becomes unbootable. ______________________________________________________ 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. Refer to section 11.5 "Special Installation Instructions" for any such requirements BEFORE attempting to install the VMS84I_UPDATE-V0700 patch kit. 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: This update kit supports the following: o Solid State Drive (SSD) support with rx2800 i2 servers and BL8x0c i2 server blades o Host Bus Adapters (HBA) mode on HP Smart Array P410i and P411 controllers o SCSI support on rx2800 i2 servers with HP Integrity PCI Express (PCIe) Ultra320 SCSI adapter o HP Smart Array P711m controller and HP 6 Gb/s SAS BL Switch o HP P2000 G3 SAS array o HP D2200sb Storage Blade o HP Virtual Connect FlexFabric 10 Gb/24-port module For more information, see Section 5. 2 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_UPDATE-V0600 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 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_UPDATE-V0700 KIT 5.1 New functionality addressed in this kit 5.1.1 New hardware support in this kit o Support for SSD on rx2800 i2 servers and BL8x0c i2 server blades SSDs are supported in this update kit. HP Smart Array P410i, P411, P711m, and P812 controllers with firmware revision 5.16b0 and later support SSDs. The following Single Level Cell (SLC) SSDs are supported: o HP 200GB SAS 2.5in SSD SLC - 632492-B21 o HP 400GB SAS 2.5in SSD SLC - 632494-B21 SSD gas gauge support: SSDs are NAND flash devices which use semiconductor technology that can perform a finite number of PROGRAM/ERASE cycles to read and write to the device, before they wear out. For those devices the SSD gas gauge provides information about "Life Remaining" of the SSD drive. SSD gas gauge data reports the following: 3 - Power-on hours: Reports the number of hours the SSD is powered ON. This value increases every hour the SSD is powered ON. - SSD usage remaining: Reports in percentage the remaining life of SSD available for use. Note: 100% means a new drive and 0% means no usage left. - Estimated life remaining based on workload to date: MSA$UTIL estimates the remaining life, in days, of the SSD drive based on its power-on hours and percent usage remaining. As the 'write' workloads on the SSD drive increases, the percentage of usage remaining decreases and the life remaining, in days, decreases proportionately. - Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) error due to usage reported: Reports whether S.M.A.R.T. error is triggered by controller firmware when drive wears out of complete usage. MSA$UTIL is enhanced to support and report SSD specific information. It provides the detailed gas gauge information and consolidate SSD group details. Images Affected: - [SYSEXE]MSA$UTIL.EXE o SCSI support on rx2800 i2 servers with HP Integrity PCIe Ultra320 SCSI adapter The HP Integrity PCIe Ultra320 SCSI adapter is a standup parallel SCSI controller supported on rx2800 i2 servers. This HBA is ideal for attaching Ultra320 tape backup devices on servers using the PCIe interface. ________________________ Note ________________________ The VMS84I_UPDATE-V0600 kit and later supports HP Integrity PCIe Ultra320 SCSI adapter only with tapes. The tape libraries such as MSL 8096, MSL 4048, and MSL 2024 are supported. ______________________________________________________ 4 o HP Smart Array P711m Controller and HP 6 Gb/s SAS BL Switch The HP Smart Array P711m controller is a PCIe mezzanine card supporting shared and direct attached SAS storage. It is one of the highest performing controllers in the HP 6 Gb/s SAS portfolio, and provides new levels of reliability, connectivity, and storage performance for HP Blade Servers through its support of the latest SCSI technology and advanced RAID capabilities. The HP 6 Gb/s SAS BL Switch for HP BladeSystem c-Class enclosures is an integral part of HP direct connect SAS storage, enabling the connectivity between HP Smart Array P711m controller in each server and the supported HP SAS storage systems. Utilities such as MSA$UTIL and SDA are enhanced to support HP Smart Array P711m controller. Images Affected: - [SYSEXE]MSA$UTIL.EXE - [SYSLIB]PKR$SDA.EXE o HP P2000 G3 SAS array The P2000 G3 SAS is the follow-on product to the MSA2000sa G2, adding the latest 6 Gb/s SAS technology to the four host ports per controller. The P2000 G3 SAS array is designed for directly attaching up to four dual-path or eight single path rack servers. SAS array support for BladeSystems utilizes the HP 6 Gb/s SAS BL Switch. Following are the enhancements: o Support for adding boot from P2000 G3 storage array. o Support for 255 SAS external storage Logical Unit Numbers (LUNs). Images Affected: - [SYS$LDR]SYS$DKBTDRIVER.EXE - [SYSLIB]IOGEN$CISS_CONFIG.EXE - [SYS$LDR]SYS$PKRDRIVER.EXE 5 - [SYS$LDR]SYS$PKRDRIVER.STB o HP D2200sb Storage Blade The D2200sb Storage Blade delivers direct attached storage for c-Class servers, with support for up to twelve hot plug small form factor (SFF) SAS hard disk drives, SAS SSDs, or SATA midline hard disk drives. The enclosure backplane provides a PCIe connection to the adjacent c-Class server blade and enables high performance storage access without any additional cables. The D2200sb Storage Blade features an onboard HP Smart Array P410i controller with 1 GB flash- backed write cache, for increased performance and data protection. o HP Virtual Connect FlexFabric 10 Gb/24-port module HP Virtual Connect FlexFabric 10Gb/24-port modules are the simplest, most flexible way to connect server blades to data or storage networks. A FlexFabric adapter provides standard NIC functions, Flex10 NIC device capabilities, and Fiber Channel or iSCSI Flex HBA capability. Each FlexFabric adapter contains two 10 Gb Ethernet ports. Each 10 Gb Ethernet port has four Flex10 physical functions - either FlexNICs or Flex HBAs. Storage traffic can be assigned as a FlexHBA only to the second physical function of each FlexFabric adapter port. If the block storage access is not required, you can disable the FlexFabric adapter storage function and configure the second physical function as another Flex NIC function. The FlexFabric technology includes Flex10 capable NIC cards and Flex10 VC modules. ________________________ Note ________________________ In this update kit, only LAN functionalities are supported on FlexFabric and is equivalent to Flex10. ______________________________________________________ This update kit supports the following: o VC FlexFabric modules: - HP VC FlexFabric Ethernet Module - 571956-B21 FW: 3.51 6 o Servers that support FlexFabric: - BL8x0c i2 server blades o Flex10 capable NICs - LAN On Motherboard (LOMs) ports of BL8x0c i2 server blades - Mezzanine cards - HP NC532m 10GbE 2 port NIC card - 467799-B21 o Non-Flex10 mezzanine cards - HP NC360m 2 port NIC card - 445978-B21 - HP NC364m 4 port NIC card - 447883-B21 The FlexFabric feature supports the following device control channel (DCC) protocol events: o Dynamic bandwidth changes reported by the FlexFabric VC module. o Link state changes reported by the FlexFabric VC module. For more information on the FlexFabric benefits and functionality, see the following website: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf 5.1.2 New features supported in this kit o Support for Host Bus Adapters (HBA) mode on HP Smart Array P410i and P411 controllers These controllers can work in either RAID or HBA mode. In this release, the support is extended for HBA mode, which enables the devices connected to these controllers be configured as raw physical devices. The device naming convention of the disks that are connected to HP Smart Array P410i and P411 controllers in HBA mode are as follows: - Internal disk devices that are connected internally within the server through HP Smart Array P410i controller are named as 'DKAxxx', where 'xxx' is the bay number in which disk is placed multiplied by 100. 7 - External disk devices that are connected externally to the server through HP Smart Array P411 controller are named as '$3$DGAxxx', where 'xxx' is the unique device identifier (UDID) assigned to the disk. This update kit supports the following storage enclosures connected to HP Smart Array P411 controller in HBA mode: D2600, D2700, MSA60, MSA70, and MDS600. Images Affected: - [SYS$LDR]SYS$DKBTDRIVER.EXE - [SYS$LDR]SYS$PKRBTDRIVER.EXE - [SYSEXE]IPB.EXE - EFI\VMS\IPB.EXE - [SYSLIB]IOGEN$CISS_CONFIG.EXE - [SYS$LDR]EXEC_INIT.EXE - [SYSLIB]LIB.MLB - [SYSLIB]SYS$LIB_C.TLB - [SYSEXE]VMS_LOADER.EFI - EFI\VMS\VMS_LOADER.EFI - [SYS$LDR]SYS$PKRDRIVER.EXE - [SYS$LDR]SYS$PKRDRIVER.STB o MSA$UTIL is enhanced to SET/DISPLAY UDID for external disks attached to HP Smart Array P411 controller in HBA mode. o MSA$UTIL is enhanced to display whether the controller is in RAID or in HBA mode. o The VMS_BCFG.EFI utility is modified to provide support for setting UDID. UDID field must be set for devices connected to HP Smart Array P411 controller in HBA mode, for OpenVMS to configure the device. 8 The setting of UDID using VMS_BCFG.EFI utility can only be done for system disks that are externally connected to an HP Smart Array P411 controller in HBA mode. To set the UDID: VMS_BCFG.EFI UDID where, device-name - System disk connected to an HP Smart Array P411 controller in HBA mode. The format must be 'fsx:', where 'fsx:' is the device associated with the OpenVMS Integrity severs system disk. udid-number - Specifies the UDID which is used as the unit number in the device name for an external disk. For example, The device name is in the form '$3$dgaxyz', where 'xyz' is the UDID for external disks. Images Affected: - [SYSEXE]VMS_BCFG.EFI - [SYSEXE]VMS_SHOW.EFI - [SYSEXE]VMS_SET.EFI ________________________ Note ________________________ MSA$UTIL is the preferred utility to set the UDIDs for disks. If an internal system disk is moved to an external enclosure, MSA$UTIL might not be available to set the UDID for the boot disk. In such scenario, you can use the VMS_BCFG.EFI utility to set the UDID only for the system or boot disk. ______________________________________________________ o The VMS_SHOW.EFI utility is modified to display the device name with the unit number for all the devices connected through HP Smart Array P410i controller in HBA mode. 9 ________________________ Note ________________________ The device naming is correct for all the internal SAS disk drives connected to the HP Smart Array P410i controller with factory default connections. VMS_ SHOW.EFI might display incorrect device names if the factory default connections of the disks to the controller are disturbed. ______________________________________________________ Images Affected: - [SYSEXE]VMS_BCFG.EFI - [SYSEXE]VMS_SHOW.EFI - [SYSEXE]VMS_SET.EFI o New $GETDVI system service item codes The $GETDVI system service provides the following item codes that return the SSD wear out gas gauge data, and returns "-1" for other disks except SSD that are connected in HBA mode: o DVI$_SSD_USAGE_REMAINING - Reports in percentage the remaining life of SSD available for use. o DVI$_SSD_LIFE_REMAINING - Estimates the remaining life, in days, of the SSD drive based on its percent usage remaining. ________________________ Note ________________________ DVI$_SSD_USAGE_REMAINING and DVI$_SSD_LIFE_REMAINING new item codes are available for SYS$GETDVI system service, LIB$GETDVI library routine, and F$GETDVI lexical function. It works only on the node to which SSD disks are directly connected. ______________________________________________________ Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE 10 - [SYS$LDR]IO_ROUTINES_MON.STB - [SYSEXE]DCL.EXE - [SYSLIB]STARLET.REQ - [SYSLIB]STARLET.R64 - [SYSLIB]STARLET.MLB - [SYSLIB]BASIC$STARLET.TLB - [SYSLIB]STARLETPAS.TLB - [SYSLIB]STARLETSD.TLB - [SYSLIB]SYS$STARLET_C.TLB o The BOOT_OPTIONS.COM utility is enabled to support devices connected to HP Smart Array P410i and P411 controllers in HBA mode. Images Affected: - [SYSEXE]EFI$BCFG.EXE - [SYSEXE]ERRFMT.EXE o SDA CLUE extension can be used to check whether HBA mode is enabled for HP Smart Array P410i and P411 controllers. To check whether HBA mode is enabled for controllers, run the following command: SDA> CLUE SCSI/PORT The following example shows the 'hba_mode' in the "Port Flags" field: SCSI Port Descriptor (SPDT): ---------------------------- PKB0: Driver SYS$PKRDRIVER SPDT Address 8A958C00 Port Type Ramanujan CISS Controller ADP Address 8A0D3CC0 Adapter PCIE UCB Address 8A9586C0 Device 00000000.00000000 () Busarray Address 8A0D4080 Port Host SCSI Id 0 Port Flags synch,asynch,mapping_reg,dir_dma,luns,cmdq,port_autosense,smart_port,64bit_luns,hba_mode Port Device Status online 11 Images Affected: - [SYSLIB]CLUE$SDA.EXE 5.2 Problems addressed in this kit 5.2.1 Problems with MSA$UTIL LUN expansion and migration 5.2.1.1 Problem Description: The following problems are observed in the MSA$UTIL: - MSA$UTIL fails to expand or extend a LUN to a size greater than 1 TB. - LUN migration from RAID 50 or RAID 60 to other raid levels fails in MSA$UTIL. These problems have been fixed. Images Affected: - [SYSEXE]MSA$UTIL.EXE QuIX case(s) reporting this problem: None. 5.2.1.2 Workaround: None. 5.2.2 Speed toggle on switch port from 1 Gigabit to 10 Gigabit brings down the 10 Gigabit Broadcom ports 5.2.2.1 Problem Description: Speed toggle on switch port from 1 Gigabit to 10 Gigabit brings down the 10 Gigabit Broadcom ports. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$ER57711.EXE 12 - [SYS$LDR]SYS$ER57711_MON.EXE QuIX case(s) reporting this problem: QXCR1001151296 5.2.2.2 Workaround: None. 5.2.3 LOM ports hang after 30 minutes of bidirectional traffic with RESET 5.2.3.1 Problem Description: Resetting a LOM port during high traffic can result in a hang and the port state being changed to DOWN. This behavior has been observed when there is continuous high traffic for more than 30 minutes before being reset. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$EW57711.EXE - [SYS$LDR]SYS$EW57711_MON.EXE - [SYS$LDR]SYS$ER57711.EXE - [SYS$LDR]SYS$ER57711_MON.EXE QuIX case(s) reporting this problem: None. 5.2.3.2 Workaround: None. 5.2.4 VMS_SHOW displays the UDID as zero for all Fibre channel disks connected through QMH2562 HBA 13 5.2.4.1 Problem Description: When VMS_SHOW DEVICE command is run from the EFI shell, all the Fibre channel devices connected through QMH2562 HBA are displayed as DGA0. This problem has been fixed. Images Affected: - [SYSEXE]VMS_SHOW.EFI - [SYSEXE]VMS_BCFG.EFI - [SYSEXE]VMS_SET.EFI QuIX case(s) reporting this problem: QXCM1001116407, QXCM1001166316 5.2.4.2 Workaround: None. 5.2.5 On rx2620, MCA occurs when shutdown is issued from an V8.4 installation DVD 5.2.5.1 Problem Description: On rx2620, when shutdown is issued from an V8.4 installation DVD using the reboot option, an Machine Check Abort (MCA) occurs. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE [SYS$LDR]SYS$DQDRIVER.STB QuIX case(s) reporting this problem: QXCM1001164264, QXCM1001149674 14 5.2.5.2 Workaround: None. 5.2.6 System crash occurs due to inaccessible DMA registers 5.2.6.1 Problem Description: A system crash with MACHINECHK bugcheck in SYS$PLATFORM_ SUPPORT+0001A662, can occur when using CDDVD utility to write to an IDE DVD drive connected by the CMD649 controller. The device interrupt times out as the DMA registers on the CMD649 controller are inaccessible. This problem has been fixed. Images Affected: - [SYS$LDR]SYS$DQDRIVER.EXE QuIX case(s) reporting this problem: QXCM1001171288 5.2.6.2 Workaround: None. 6 TIMA KITS INCLUDED IN THIS KIT The following TIMA kits are included in this kit: o VMS84I_MSCP-V0100 o VMS84I_FORRTL-V0100 o VMS84I_SHADOWING-V0100 o VMS84I_SYS-V0200 o VMS84I_ACRTL-V0100 o VMS84I_MUP-V0300 o VMS84I_LOGINPLUS-V0200 15 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_UPDATE patch kits can be found in the following files: o VMS84I_UPDATE-V0100.RELEASE_NOTES o VMS84I_UPDATE-V0200.RELEASE_NOTES o VMS84I_UPDATE-V0300.RELEASE_NOTES o VMS84I_UPDATE-V0400.RELEASE_NOTES o VMS84I_UPDATE-V0500.RELEASE_NOTES o VMS84I_UPDATE-V0600.RELEASE_NOTES o VMS84I_UPDATE-V0200_COVER.TXT o VMS84I_UPDATE-V0500_COVER.TXT o VMS84I_SHADOWING-V0100.RELEASE_NOTES o VMS84I_FORRTL-V0100.RELEASE_NOTES o VMS84I_MSCP-V0100.RELEASE_NOTES o VMS84I_SYS-V0100.RELEASE_NOTES o VMS84I_SYS-V0200.RELEASE_NOTES o VMS84I_DEBUG-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0100.RELEASE_NOTES o VMS84I_FIBRE_SCSI-V0200.RELEASE_NOTES o VMS84I_IPC-V0100.RELEASE_NOTES o VMS84I_LAN-V0100.RELEASE_NOTES o VMS84I_RMS-V0100.RELEASE_NOTES o VMS84I_RMS-V0200.RELEASE_NOTES o VMS84I_DRIVER-V0100.RELEASE_NOTES o VMS84I_SYSLOA-V0100.RELEASE_NOTES o VMS84I_LOGINPLUS-V0100.RELEASE_NOTES o VMS84I_ACRTL-V0100.RELEASE_NOTES o VMS84I_MUP-V0100.RELEASE_NOTES o VMS84I_MUP-V0200.RELEASE_NOTES 16 o VMS84I_MUP-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_UPDATE /VERSION=V7.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_UPDATE /VERSION=V7.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_UPDATE /VERSION=V7.0 /SELECT = *.RELEASE_NOTES 8 KNOWN PROBLEMS AND LIMITATIONS This section describes the known problems and limitations in this patch kit. o On HP Smart Array P411, P711m, and P812 controllers, when SAS cable is unplugged or plugged in to a running system, path failover or device discovery does not happen. The Smart Array controller hangs and a system reboot is required to bring the controller online. This issue will be addressed in a future release of Smart Array firmware. o On a few Integrity servers, boot options added for DVD using the BOOT_OPTIONS.COM utility might fail to boot from the DVD, which results in an error message. An alternate method is to add boot option for DVD using 'bcfg' utility or manually boot the DVD: 1. From the EFI Shell> prompt, run the "map -r" command. This command lists the 'fs' partition corresponding to the DVD, which can be identified by looking for the keyword CDROM. 17 For example, fs0 :CDRom - Alias cd64a0a0 blk0 PcieRoot(0x30304352)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/CDROM(0x0) Shell>fs0:\EFI\BOOT\BOOTIA64.EFI will boot the DVD o After identifying the 'fs' partition corresponding to the DVD, you can use the 'bcfg' utility to add the boot option for DVD. For example, Shell>bcfg boot add 2 fs0:\EFI\BOOt\BOOTIA64.EFI "OpenVMS ISO DVD" o The volumes that are configured from HP P2000 G3 SAS array with LUN number only up to 99 are used as BOOT or DUMP devices. This issue will be addressed in a future release. o Online addition of volumes from the HP P2000 G3 SAS array might show fewer paths than the actual mapped paths in the host. The workaround for this problem is to switch the controller ownership of VDISK created on HP P2000 G3 SAS array or reboot the host. When all the volume paths are visible, VDISK can be assigned to the default owner. o VMS_SHOW.EFI utility displays DK device names instead of DG names to external LUNs connected through HP P2000 G3 SAS array. For example, VMS: DKB17 SAS Drive EFI: Acpi(PNP0A08,30304352,0A03)/Pci(7|0)/Pci(0|0)/Scsi(Pun4,LunD) An alternative method for identifying the external system disk: The 'Vol fsx' command executed at shell provides the volume label (HP recommends that you provide meaningful names to boot disks, for easy identification during the EFI boot process) of the corresponding LUN. 18 For example, Shell> vol fs2 Volume V8_4 (rw) 130,797,568 bytes total disk space 103,579,648 bytes available on disk 2,048 bytes in each allocation unit where, 'V8_4' is the volume label of the LUN that corresponds to fs2. On OpenVMS, run the SHOW DEVICE command to get the volume label of the LUNs. o For HP P2000 G3 SAS array LUNs, the SHOW DEVICE /FULL command displays port associated World Wide Identifier (WWID) in place of LUN associated WWID in the "WWID" field. A similar behavior occurs while using the $GETDVI system service or F$GETDVI lexical function using WWID item code. o Multi-initiator configuration is not supported with HP Smart Array P411 controller. o Using SORT32 utility on huge files displays an error and warning messages When performing SORT operation on huge files (that is, greater than 10 GB), the SORT operation might terminate due to the following error message: %SORT-F-SYSERROR, system service error -LIB-F-INSVIRMEM, insufficient virtual memory Increasing the WSEXTENT and PGFLQUOTA values might allow the SORT operation to complete successfully, but displays the following warning message: %SORT-W-SYSERROR, system service error -LIB-F-INSVIRMEM, insufficient virtual memory Note: You can ignore the warning message, if the SORT operation is successful. 19 Even with the increased WSEXTENT and PGFLQUOTA values, the SORT operation might fail, due to the inherent limitation of the SORT utility in not utilizing P2 space. o RMS SYS$OPEN system service fails with an "-RMS-E-FNF, file not found" error message when opening a symbolic link pointing to a non-directory file with ".DIR" or ".dir" extension. This behavior is also seen with utilities such as TYPE command, which internally uses RMS SYS$OPEN system service. For example, $ SHOW DEF SYS$SYSDEVICE:[TEST] $ $ CREATE TEMP.DIR ! Non-directory file with ".DIR" extension This is not a directory. Exit $ $ CREATE/SYM="/SYS$SYSDEVICE/TEST/TEMP.DIR" SYM.LNK ! Create symbolic link pointing to the file $ $ DIR/LINK Directory SYS$SYSDEVICE:[TEST] SYM.LNK;1 -> /SYS$SYSDEVICE/TEST/TEMP.DIR 1 $ TYPE SYM.LNK %TYPE-W-OPENIN, error opening SYS$SYSDEVICE:[TEST]SYM.LNK;1 as input -RMS-E-FNF, file not found $ o Installing images using symbolic link is not supported. For example, $ CREATE SYMLINK.EXE /SYMLINK="TARGET_DIRECTORY/IMAGE.EXE" $ INSTAL CREATE SYMLINK.EXE o Binding more than 26 disks into a volume set using the MOUNT/BIND command fails with an error message. While mounting disks sequentially into a volume set using the MOUNT/BIND command, every disk number equal to (16 x Y) + 27, where, Y ranges from 0 to 14, fails with "MOUNT-F-SETLIMIT" error message. This failure is due to a design restriction within the MOUNT utility. 20 Workaround: When binding disks into a volume set, if a "MOUNT-F- SETLIMIT" error message is displayed, dismount the first member of the volume set and attempt the MOUNT/BIND operation again. For example, To bind 50 disks into a volume set: 1. Create the volume set of 50 disks: $ MOUNT/BIND=TEST Disk1:, Disk2:, ., Disk50: Label1, Label2, ., Label50 %MOUNT-I-MOUNTED, Disk1 mounted on Label1: (node) %MOUNT-I-MOUNTED, Disk2 mounted on Label2: (node) %MOUNT-F-SETLIMIT, too many volumes in volume set Now, disks 1 to 26 are mounted into the volume set, while the disks from 27 to 50 fail with "MOUNT-F- SETLIMIT" error message. 2. Dismount the first member of the volume set: $ DISMOUNT Disk1 $ MOUNT/BIND=TEST Disk1:, Disk2:, ., Disk50: Label1, Label2, ., Label50 %MOUNT-I-MOUNTED, Disk1 mounted on Label1: (node) %MOUNT-I-MOUNTED, Disk42 mounted on Label42: (node) %MOUNT-F-SETLIMIT, too many volumes in volume set Now, disks 1 to 42 are mounted into the volume set, while the disks from 43 to 50 fail with "MOUNT-F- SETLIMIT" error message. 3. Repeat step 2 to dismount the first member of the volume set. $ DISMOUNT Disk1 $ MOUNT/BIND=TEST Disk1:, Disk2:, ., Disk50: Label1, Label2, ., Label50 %MOUNT-I-MOUNTED, Disk1 mounted on Label1: (node) %MOUNT-I-MOUNTED, Disk50 mounted on Label50: (node) Now, disks 1 to 50 are successfully mounted as a single volume set. o Class scheduling limitation 21 The DCL commands associated with class scheduling such as SHOW SYS/SCHED, SHOW PROCESS/SCHED, and SET PROCESS/SCHED fails in the following scenarios: a. Moving class scheduler database from one system to another To activate the classes on the new node: $ MC SYSMAN SYSMAN> SET ENVIRONMENT /CLUSTER //if class is configured for all cluster members SYSMAN> CLASS MODIFY %SMI-I-CLUWIDE, scheduling class is now valid cluster-wide b. An OpenVMS guest instance having a class scheduler database is rebooted After reboot, the class scheduler is in un- initialized state thereby causing the DCL commands to fail. This is because Guest instance is booted via the memory disk (that is, VMS boot flags set to 0, 200000) and since the class scheduler database file is not loaded onto memory disk during booting, system fails to recognize the existence of a class scheduler database causing it to be un-initialized. The previous problem exists for any system booted via memory disk booting, that is, with VMS boot flags set to (0,200000). To prevent this problem add the database file to SYS$COMMON:[SYS$LDR]SYS$USER_MEMORYDISK.DAT as follows: ! Add files after this line. SYS$SYSTEM:VMS$CLASS_SCHEDULE.DATA, optional c. The class scheduler database file is present only in the path pointed to by VMS$CLASS_SCHEDULE logical and is deleted from the default [SYSEXE] directory. VMS$CLASS_SCHEDULE logical can be used to point to the class scheduler database file. SYSMAN by default creates the class scheduler database file in [SYSEXE] directory. If you have defined VMS$CLASS_SCHEDULE logical and the file is moved out of [SYSEXE] directory to the new path pointed by the logical, the DCL commands might fail after the system is rebooted. 22 The workaround for this issue is to retain a copy of the initial database file in the [SYSEXE] directory. 9 DOCUMENTATION ERRATA This section describes correction(s) to the various manuals in the OpenVMS documentation set. o In VMS84I_UPDATE-V0500 release notes, section 8 must be read as: RAD_SUPPORT enables RAD-aware code to be executed on systems that support Resource Affinity Domains (RADs); for example, AlphaServer GS160 systems and Integrity cell-based servers, BL8x0c i2 server blades, or rx2800 i2 servers. An RAD is a set of hardware components (CPUs, memory, and I/O) with common access characteristics. Bits are defined in the RAD_SUPPORT parameter as follows: RAD_SUPPORT (default is 207 for Alpha and 10944667 for Integrity servers) 10 FILES PATCHED OR REPLACED: o [SYSEXE]DCL.EXE (new image) Image Identification Information Image name: "DCL" Image file identification: "X-54" Image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 5-APR-2012 14:08:01.23 Overall Image Checksum: E1B408A1 o [SYSEXE]MSA$UTIL.EXE (new image) Image Identification Information 23 Image name: "MSA$UTIL" Image file identification: "X-33" Image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 14:02:00.32 Overall Image Checksum: 8031D7E3 o [SYS$LDR]SYS$ER57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 3-FEB-2012 17:04:03.74 Overall Image Checksum: EDB5D977 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: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 3-FEB-2012 17:04:07.28 Overall Image Checksum: 98D22752 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information Image name SYS$EW5700DRIVER" Image file identification: "X-5" Image build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 14:00:26.00 Overall Image Checksum: 2FFEF0CD o [SYS$LDR]SYS$EW5700_MON.EXE (new image) Image Identification Information 24 Image name: "SYS$EW5700DRIVER_MON" Image file identification: "X-5" Image build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 14:00:32.15 Overall Image Checksum: F2ED86B2 o [SYS$LDR]SYS$EW57711.EXE (new image) Image Identification Information Image name: "SYS$EW57711DRIVER" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 3-FEB-2012 17:04:03.74 Overall Image Checksum: EDB5D977 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: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 3-FEB-2012 17:04:07.28 Overall Image Checksum: 98D22752 o [SYSEXE]IPB.EXE (new image) Image Identification Information Image name: "IPB" image file identification: "X-4" image file build identification: "0100000073" linker identification: "Linker I02-37" Link Date/Time: 17-APR-2012 20:44:42.63 Overall Image Checksum: 138D1C8 o [SYS$LDR]EXEC_INIT.EXE (new image) Image Identification Information 25 Image name: "EXEC_INIT" image file identification: "X-217" image file build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 3-FEB-2012 17:02:59.42 Overall Image Checksum: B78E5364 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKRDRIVER" image file identification: "X-5" image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 14:00:12.13 Overall Image Checksum: 5E9012D8 o [SYS$LDR]SYS$DKBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$DKBTDRIVER" image file identification: "X-5" image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 13:59:41.29 Overall Image Checksum: 7344110D o [SYS$LDR]SYS$PKRBTDRIVER.EXE (new image) Image Identification Information Image name: "SYS$PKRBTDRIVER" image file identification: "X-5" image file build identification: "0100000073" linker identification: "Linker I02-37" Link Date/Time: 17-APR-2012 20:44:43.99 Overall Image Checksum: B05474E1 o [SYSLIB]IOGEN$CISS_CONFIG.EXE (new image) Image Identification Information 26 Image name: "IOGEN$CISS_CONFIG" image file identification: "X-10" image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 13:56:32.36 Overall Image Checksum: 1A93E0A7 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information Image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "0100000073" linker identification: "Linker I02-37" Link Date/Time: 17-APR-2012 20:36:01.20 Overall Image Checksum: 44669112 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information Image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "0100000073" linker identification: "Linker I02-37" Link Date/Time: 17-APR-2012 20:36:03.46 Overall Image Checksum: AABECD3A o [SYSLIB]PKR$SDA.EXE (new image) Image Identification Information Image name: "PKR$SDA" image file identification: "X-13" image file build identification: "0100000069" linker identification: "Linker I02-37" Link Date/Time: 7-MAR-2012 18:20:35.10 Overall Image Checksum: 459E9F1D o [SYS$LDR]SYS$DQDRIVER.EXE (new image) Image Identification Information 27 Image name: "SYS$DQDRIVER" image file identification: "X-5" image file build identification: "0100000069" linker identification: "Linker I02-37" Link Date/Time: 7-MAR-2012 18:18:57.12 Overall Image Checksum: F8BE3F77 o [SYSLIB]CLUE$SDA.EXE (new image) Image Identification Information Image name: "CLUE$SDA" image file identification: "X-69" image file build identification: "0100000069" linker identification: "Linker I02-37" Link Date/Time: 7-MAR-2012 18:18:46.91 Overall Image Checksum: 81DF87CB o [SYSEXE]EFI$BCFG.EXE (new image) Image Identification Information Image name: "EFI$BCFG" image file identification: "X-43" image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 13:59:54.84 Overall Image Checksum: 6F7BEF2A o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information Image name: "ERRFMT" image file identification: "X-22" image file build identification: "0100000072" linker identification: "Linker I02-37" Link Date/Time: 3-APR-2012 13:59:37.32 Overall Image Checksum: 670DAF21 o [SYSLIB]BASIC$STARLET.TLB (new file) o [SYSLIB]STARLET.MLB (new file) o [SYSLIB]STARLET.R64 (new file) o [SYSLIB]STARLET.REQ (new file) 28 o [SYS$LDR]SYS$DQDRIVER.STB (new file) o [SYSLIB]STARLETPAS.TLB (new file) o [SYSLIB]STARLETSD.TLB (new file) o [SYSLIB]SYS$STARLET_C.TLB (new file) o [SYSHLP]SYSGEN.HLB (new file) o [SYSUPD]SYS_PARAMETERS.HLP (new file) o [SYSHLP]SYSMANHELP.HLB (new file) o [SYSEXE]VMS_BCFG.EFI (new file) o [SYSEXE]VMS_SET.EFI (new file) o [SYSEXE]VMS_SHOW.EFI (new file) o [SYS$LDR]SYS$EW5700.STB (new file) o [SYS$LDR]SYS$EW5700_MON.STB (new file) o [SYSLIB]SYS$LIB_C.TLB (new file) o [SYSLIB]LIB.MLB (new file) o [SYS$LDR]EXEC_INIT.STB (new file) o [SYSEXE]VMS_LOADER.EFI (new file) o [SYS$LDR]SYS$PKRDRIVER.STB (new file) o [SYSHLP]MSA_UTIL_HELP.HLB (new file) o [SYSUPD]DCLDICT.HLP (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) 11 INSTALLATION INSTRUCTIONS 11.1 Test/Debug Image Loss In the course of debugging problems reported to HP 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 29 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. 11.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_UPDATE-V0700.ZIPEXE 11.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_UPDATE[/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. 30 11.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=V7.0 [/SOURCE=location of Kit] o De-assign the logical names assigned Example: A sample command file to install the VMS84I_UPDATE-V0700 kit: 31 $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_UPDATE/PRODUCER=HP/BASE=I64VMS/VER=V7.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 11.5 Special Installation Instructions In order to Install or perform any PRODUCT commands on the VMS84I_UPDATE-V0700 patch kit, you must have the VMS84I_ PCSI-V0400 or later kit installed on your system. If you attempt to install from another OpenVMS system disk by using /REMOTE qualifier, you must have the latest PCSI kit installed on the source system disk. 11.5.1 How to create DVD with ISO file To create DVD with ISO file on Windows 7 Enterprise (Service Pack 1): 1. Download the ISO file. To download the file, contact HP support representative. 2. Copy the ISO file on to the system in a folder. 3. Double-click the ISO file. The dialog box appears. 4. Click the "Burn Disc" button to start the ISO file burn. The DVD process takes approximately 20 to 25 minutes and might vary depending on the system configuration. 5. When the burning is complete, the disc is ejected and is ready for use. 32 11.5.2 Setting controller to HBA mode To set the HP Smart Array P411 controller mode to HBA mode: 1. Download the 'saupdate', which is an EFI utility from the HP Technical Support Centre: http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp?lang=en&cc=us 2. Copy the utility to the USB drive. 3. Connect the USB drive to rx2800 i2 server: Shell> map -r Device mapping table ... fs7 :Removable BlockDevice - Alias f55b1 blk7 PcieRoot(0x30304352)/Pci(0x1D,0x7)/USB(0x1,0x1) ... Shell> Shell>fs7: fs7:\efi\>saupdate set_mode all hba WARNING:Changing controller mode could result in DATA LOSS!!! Key in 'YES' to continue or 'NO' to quit:yes Changing mode of the controller at 0:2:0:0 to HBA Resetting and reinitializing controller,it may take several minutes Controller mode change successful fs7:\efi\>reset ________________________ Note ________________________ The above command sets the mode to HBA for all controllers. If you want to set the mode for a specific controller, provide the controller details accordingly. ______________________________________________________ 33 11.5.3 Setting UDID for devices To set the UDID: $ MCR MSA$UTIL MSA> SHOW CONTROLLER !This command shows the controller name MSA> SET CONTROLLER CONTROLLER_NAME MSA> SET DISK 205 /IDENTIFIER=1234 MSA> EXIT $ $ MCR SYSMAN IO AUTO /LOG ... %IOGEN-I-CONFIGURED, configured device DGA1234 The SET DISK /IDENTIFIER command can also be run at $$$ using "Option 8" to configure disks during Operating System installation. For information about setting UDID for devices, see Section 5.1.2. 12 COPYRIGHT AND DISCLAIMER: © 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. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY 34 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.