HP OpenVMS Version 8.3-1H1 for Integrity Servers Upgrade and Installation Manual HP Part Number: BA322-90077 Published: October 2007 Edition: 1.
© Copyright 2007 Hewlett-Packard Development Company, L.P Legal Notice Confidential computer software. Valid license from HP 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. The information contained herein is subject to change without notice.
Table of Contents Preface..............................................................................................................................17 About this document............................................................................................................................17 Intended Audience................................................................................................................................17 When to Use This Manual.........................................
2.6 Beginning the Installation...............................................................................................................48 3 Installing the OpenVMS Operating System..............................................................49 3.1 Installation Tasks.............................................................................................................................49 3.2 Booting the OpenVMS Operating System Media.................................................................
.3 Mixed-Version Support in an OpenVMS Cluster Environment.....................................................88 5.4 Adding a New System to an OpenVMS Cluster.............................................................................89 5.5 Types of Upgrades...........................................................................................................................89 5.5.1 Concurrent Upgrade.....................................................................................................
7.7.2 Setting Up the Queue Manager and Default Queues ...........................................................120 7.7.3 Configuring a Multihead System (Optional)........................................................................121 7.7.4 Configuring DECnet .............................................................................................................121 7.7.5 Configuring HP TCP/IP Services for OpenVMS...................................................................122 7.7.
A.2.1.1 Using the EFI Boot Manager to Select the OpenVMS Console....................................155 A.2.1.2 Using the EFI Shell to Select the OpenVMS Console...................................................156 A.2.2 Selecting Your OpenVMS Console on rx2600 Integrity Servers...........................................157 A.3 Overview of Using EFI.................................................................................................................161 A.3.1 General Notes About Using EFI........
B.5 Booting OpenVMS I64 from the InfoServer..................................................................................199 B.6 Troubleshooting InfoServer Boot Problems..................................................................................201 C Using HP SIM and vMedia to Install and Upgrade OpenVMS...........................203 C.1 HP SIM Provisioning of OpenVMS..............................................................................................203 C.1.
G.1.3 Error Log Information..........................................................................................................259 G.1.4 Updating the Printer and Storage Database.........................................................................259 G.1.5 Editing the System Files.......................................................................................................259 G.1.6 Controlling the Printer and Storage Environment.............................................................
List of Figures D-1 Fibre Channel Host and SAN Storage Controller Configuration...............................................
List of Tables 1-1 1-2 2-1 2-2 2-3 3-1 3-2 4-1 4-2 5-1 5-2 5-3 6-1 7-1 A-1 A-2 A-3 B-1 B-2 Definitions of Terms......................................................................................................................25 Getting OpenVMS Started on Integrity Servers............................................................................28 Preinstallation Checklist................................................................................................................
List of Examples 3-1 B-1 Component Options and Suboptions............................................................................................68 Setting Up the Boot Server and Client.........................................................................................
Preface About this document This document explains how to install, or upgrade to, Version 8.3-1H1 of the OpenVMS for Integrity servers (OpenVMS I64) operating system. Also included are the prerequisites for installing and upgrading your software and the required and optional tasks you can perform after you complete the software installation or upgrade.
provisioning. Such support facilitates installing or upgrading OpenVMS on Integrity servers that do not include a CD/DVD drive. Provisioning is supported with HP SIM Version 5.1 or later. You use HP SIM to initiate the provisioning, after which the installation or upgrade process occurs automatically in the background.
• Support for a VGA console and USB keyboard as console devices for booting With VGA support, you can now connect a monitor, keyboard, and mouse directly to connectors provided for that purpose on your Integrity server panel. You no longer need to use a serial console, including PC/terminal emulator or character-cell terminal as a console. On systems that do not include an embedded graphics device, you might be able to select a graphics option card in a PCI slot to be the graphics console.
• • • • • Appendix F (page 255) discusses the OpenVMS internationalization data kit (VMSI18N) and how to install it. Appendix G (page 257) explains how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. Appendix H (page 267) explains how to remove the OpenVMS operating system from your disk.
Convention Meaning – A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes—binary, octal, or hexadecimal—are explicitly indicated. Related Information Before installing, upgrading, or using the OpenVMS operating system on your computer, be sure you have access to the following documents.
• For documentation related to Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), and Pay per use (PPU), see the HP Instant Capacity User’s Guide and HP Pay per use User’s Guide on the following website: http://docs.hp.com/en/hplex.html#Utility%20Pricing • HP SIM documentation is available in the Information Library on the following website: http://www.hp.
http://www.docs.hp.com. Manufacturing Part Number Supported Operating Systems Supported Versions Edition Number Publication Date BA322–90077 OpenVMS I64 Version 8.3-1H1 1.0 October, 2007 HP Encourages Your Comments HP welcomes your comments on this manual. Please send comments to either of the following addresses: Internet: openvmsdoc@hp.
1 Getting Started This chapter defines key terms and describes preliminary procedures you must perform before installing or upgrading your OpenVMS system. NOTE: Throughout this book, examples are taken from OpenVMS I64 installations or upgrades except where stated otherwise. OpenVMS DCL commands are in uppercase, while HP Integrity servers console commands are in lowercase. 1.1 Key Terms Table 1-1 lists a few key terms you need to know before you install or upgrade the system.
1.
You can move from the EFI interface to MP and back again. Similarly, you can move from MP to the operating system and back. 1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures HP Virtual Connect (VC) is a set of interconnect modules and embedded software available for HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server connections.
server model and version, always refer to the hardware documentation provided for your Integrity server. Table 1-2 Getting OpenVMS Started on Integrity Servers Step Action Documentation 1 Connect your console cable to the serial port; if MP is present on Section A.2 (page 152) your server, connect to the MP serial port. 2 Optionally, configure MP to accept connections over TCP/IP Services for OpenVMS.
1.3.2 Software Components For software components, verify the following: • • Be sure you have all the items listed on the bill of materials contained in the distribution kit. If your distribution kit is incomplete, notify HP Customer Support and request priority shipment of any missing items. Before installing the OpenVMS operating system software, review all cover letters and release notes. 1.3.
NOTE: The info fw command at the EFI> Shell prompt cannot be used while OpenVMS is running. You can use the MP interface to check firmware on your system while OpenVMS is running. NOTE: EFI Shell commands are not case sensitive. However, in this manual, EFI and other Integrity server interface commands are displayed in lowercase to help distinguish them from OpenVMS DCL commands. For more information about the latest firmware for your Integrity server, check the HP OpenVMS Version 8.
The following example shows the command for unzipping an .ISO image of the latest firmware for an rx2600 system (the file name changes with each update of the firmware available on the website): $ UNZIP PF_CPEAKSYS0nnn.ZIP Archive: SYS$SYSROOT:[SYSMGR]PF_CPEAKSYS0nnn.ZIP inflating: PF_CPEAKSYS0nnn.ISO 4. Record the data on the CD, specifying the .ISO file as the source for the CD.
1.4 Using the Operating System Menu The following sections describe how to use the operating system menu to install, upgrade, and modify your system disk, and perform other related tasks. The OpenVMS operating system main menu displays automatically when you boot the OpenVMS operating system from the operating system media (for instructions on how to boot from the operating system media, see Section 3.2 (page 49)).
1.4.1 Using the Install, Upgrade, or Reconfigure OpenVMS Option (1) Select option 1 on the operating system main menu to install, upgrade, or reconfigure your OpenVMS software. Selecting option 1 implements a PCSI utility concept called a platform.
1.4.1.1 INITIALIZE Option When you specify the INITIALIZE option, the following operations take place: • • All software and data files that already exist on the target disk are removed. The software can only be recovered from a backup of the disk, so make sure that you either have a backup or will not need the data again. The operating system is installed.
1.4.2 Using the Display Layered Products Option (2) Use option 2 to display layered products that can be installed. NOTE: Although option 2 displays any patch kits available from the OpenVMS distribution media, HP recommends using option 7 to display patch kits; option 7 enables you to specify locations to search in addition to the standard location.
HP I64VMS DWMOTIF_SUPPORT V8.3-1H1 Full LP HP I64VMS KERBEROS V3.1-152 Full LP HP I64VMS SSL V1.3-284 Full LP HP I64VMS TCPIP V5.6 Full LP HP I64VMS TDC_RT V2.3-1 Full LP HP I64VMS WBEMCIM V2.61-A070728 Full LP HP I64VMS WBEMPROVIDERS V1.5-31 Full LP ----------------------------------- ----------- Compressed Compressed Compressed Compressed Compressed Compressed Compressed ---------- 12 items found Press Return to continue... 1.4.
The procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the key.
NOTE: When you boot the OpenVMS operating system media and select the option to install layered products, the installation procedure for the selected layered product(s) does not run the Installation Verification Procedure (IVP) for layered products. Because the operating system is booted from the media and the layered products are installed on a different device (the target drive), the IVPs cannot execute correctly.
HP I64VMS TCPIP V5.6 HP I64VMS VMS V8.3-1H1 HP I64VMS SSL V1.3-284 HP I64VMS WBEMCIM V2.61-A070728 HP I64VMS WBEMPROVIDERS V1.5-31 HP I64VMS TDC_RT V2.3-1 HP I64VMS AVAIL_MAN_BASE V8.3 HP I64VMS CDSA V2.2 HP I64VMS DECNET_PHASE_IV V8.3 HP I64VMS DWMOTIF V1.6 HP I64VMS OPENVMS V8.3 HP I64VMS VMS V8.3 HP I64VMS KERBEROS V3 HP I64VMS KERBEROS V3 HP I64VMS CDSA V2.1 HP I64VMS DECNET_PHASE_IV V8.2 HP I64VMS DWMOTIF V1.5 HP I64VMS OPENVMS V8.3 HP I64VMS TCPIP V5.4-18 HP I64VMS VMS V8.
You must enter the device name for the target disk on which the layered product(s) reconfiguration will be performed. Enter device name for target disk: [DKB300] (? for choices) DKB300 DKB300: is labeled V82SYS. The reconfigure operation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing "?". Do you always want detailed descriptions? (Yes/No) [No] NO 1 2 3 4 5 6 7 8 9 10 11 12 13 ? E - HP I64VMS AVAIL_MAN_BASE V8.3-1H1 HP I64VMS CDSA V2.
You must enter the device name for the target disk on which the layered product(s) removal will be performed. Enter device name for target disk: [DKB300:] (? for choices) DKB300 DKB300: is labeled V82SYS. The remove operation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing "?". Do you always want detailed descriptions? (Yes/No) [No] NO 1 2 3 4 5 6 7 8 9 10 11 12 13 ? E - HP I64VMS AVAIL_MAN_BASE V8.3 HP I64VMS CDSA V2.
Enter device name for target disk: (? for choices) [DKB300] • When you choose submenu option 1, you are prompted to choose detailed or brief descriptions, as follows: The patch operation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing ?. Do you always want detailed descriptions? (Yes/No) [No] • For each of the submenu options (1 through 5), you are prompted for the patch kit source. You can specify alternate locations.
**** Hit any key to cold reboot P00>>> **** 1.5 Making the Install/Upgrade/Backup Selection Now that you have reviewed key terms, examined hardware and software requirements, and learned how to use the menu system included on the OpenVMS operating system media, you can do the following: IF ... THEN GO TO... You want to install the operating system in an OpenVMS Cluster environment Chapter 2 (page 45), and then Chapter 3 (page 49). Perform postinstallation tasks described in Chapter 7 (page 113).
2 Preparing to Install in an OpenVMS Cluster Environment This chapter contains information to review and steps to perform before installing OpenVMS in an OpenVMS Cluster environment. If you are not installing your operating system in an OpenVMS Cluster environment, go to Chapter 3 (page 49) for information about installing your system. 2.
Warranted support means that HP has fully qualified the two specified versions coexisting in an OpenVMS Cluster and will address all problems identified by customers using this configuration. Migration support means that HP has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX, OpenVMS Alpha, or OpenVMS I64. Problem reports submitted against these configurations will be answered by HP.
OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS Version 8.3 Release Notes. For information about supporting the TDC_RT software in OpenVMS Clusters, see Section 7.8.10.5 (page 135). 2.
2.5 Dismounting the Target System Disk Elsewhere in the Cluster Before installing OpenVMS on a target drive in an OpenVMS Cluster, make sure the target system disk is not mounted elsewhere in the cluster. The target system disk must be dismounted clusterwide (except on the system from which the installation is being performed) and must remain so during the installation. For instructions on dismounting cluster disks, see Section 5.5.2.3 (page 91). 2.
3 Installing the OpenVMS Operating System This chapter explains how to install the OpenVMS I64 Version 8.3-1H1 operating system. It includes sample output similar to what you might see during an installation and explains how to respond to the prompts. If you purchased a system with the operating system preinstalled, then most of the information in this chapter does not apply.
3.2.1 Booting the OpenVMS I64 OE DVD You can boot the OpenVMS I64 OE DVD in any of the following ways. This section gives detailed instructions on booting from the local DVD drive. Detailed instructions on the other methods are available in the appendixes, as noted in the corresponding sections to follow. • • • • From your local DVD drive (Section 3.2.1.1 (page 50)) From a virtual DVD drive served over the network by the InfoServer utility (Section 3.2.1.
4. From the main EFI boot menu (for cell-based servers, this must be the EFI boot menu for the nPartition on which OpenVMS is to be booted), select the appropriate item from the boot options list. Note that the EFI boot menu is timed; press any key to stop the countdown timer. For some systems, the boot option to select is the Internal Bootable DVD option. If that option is not listed in your EFI boot menu, move to the Boot From a File menu and select the Removable Media Boot option, if present.
3.2.1.4 Booting Using vMedia To use vMedia to boot an image of the OpenVMS OE DVD, certain configuration steps are required initially (one time only); see Section C.1.4 (page 207). For instructions on booting with vMedia, see Section C.2 (page 232). 3.3 Installing the OpenVMS Operating System onto a System Disk After booting the operating system media, you can create an operating system disk by using option 1 of the menu provided by the operating system media.
During the installation, the procedure prompts you for the following information: • • • • • • The names of the source drive, target drive, and LAN device (if booting is served by an InfoServer). Whether you want to select the INITIALIZE or PRESERVE option (as described in Section 1.4.1 (page 33)). A volume label for the target disk (if you choose not to use the default volume label). A password for the SYSTEM account.
1. Select Option 1 on the Menu: When you boot the OpenVMS operating system CD or DVD (as instructed in Section 3.2 (page 49)), the initial HP copyright message and other messages are displayed, followed by the operating system main menu that is shown in the following example. Choose option 1 to install the operating system, as shown. Note that after the initial copyright message, a few minutes might pass before the OpenVMS operating system menu appears. . . Installing required known files...
? - to repeat an explanation ^ - to change prior input (not always possible) Ctrl/Y - to exit the installation procedure 2. Create the System Disk: The procedure allows you to begin creating the system disk. First it displays the following information, followed by the prompt asking whether you want to initialize or preserve the disk: There are two choices for Installation/Upgrade: INITIALIZE - Removes all software and data files that were previously on the target disk and installs OpenVMS I64.
4. Specify the Volume Label: If you select a device that can be used, the procedure then informs you of the volume label currently assigned to this device and asks whether you want to keep that label. If you choose not to keep that label, you are prompted for a new label, as shown in the following example. The OpenVMS operating system uses the volume label to identify and reference the disk. Make sure the label you use is unique; problems occur if the same label is used by different disk volumes.
— — ODS-5 volumes cannot be mounted on any version of OpenVMS prior to Version 7.2. Systems running OpenVMS VAX Version 7.2 and higher can mount ODS-5 volumes, but cannot create or access files having extended names. (Lowercase file names are seen in uppercase on OpenVMS VAX systems.) Select ODS-2 or ODS-5 by entering 2 or 5 at the prompt. 6. Enable Hard Links (ODS-5 Only): If you selected ODS-5, the procedure asks whether you want to enable hard links (if you selected ODS-2, skip to the next step).
Boot options in the EFI Boot Manager boot option menu can provide a convenient way to boot your system. The installation procedure can automatically create a new boot option (if none exists) or validate existing boot options.
The password must be a minimum of 8 characters in length, and may not exceed 31 characters. It will be checked and verified. The system will not accept passwords that can be guessed easily. The password will not be displayed as you enter it.
parameter is based on the DECnet Phase IV address. SCSSYSTEMID must also be unique within an OpenVMS Cluster. If you plan to use DECnet, SCSSYSTEMID must be set based on the DECnet Phase IV address. Do you plan to use DECnet (Yes/No) [YES]: YES If you answer YES, the information about the DECnet Phase IV addresses is displayed along with a prompt for a DECnet Phase IV address.
13. Set Local Time Zone: Now the procedure asks you to configure the local time zone. For local time zone support to work correctly, the installation procedure must set the time zone that accurately describes the location you want to be your default time zone. Usually, this is the time zone in which your system is running. In addition, the procedure asks you to set the OpenVMS time differential factor (TDF). The procedure displays the main time zone menu.
words immediately after the equals string, or you can enter the equals sign alone, in which case the procedure prompts you for the words or partial words of the time zone you want to select. After you enter that information, the procedure displays all matching time zones, and you can then select the appropriate one.
procedure: Configuring the Time Differential Factor (TDF) Default Time Differential Factor for standard time is -5:00. Default Time Differential Factor for daylight saving time is -4:00. The Time Differential Factor (TDF) is the difference between your system time and Coordinated Universal Time (UTC). UTC is similar in most respects to Greenwich Mean Time (GMT). The TDF is expressed as hours and minutes, and should be entered in the hh:mm format. TDFs for the Americas will be negative (-3:00, -4:00, etc.
http://h18000.www1.hp.com/products/software/info/terms/swl_sld.html When you answer YES to the prompt to register your licenses now, the installation procedure launches the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following options menu: VMS License Management Utility Options: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12.
You may install any of the optional software products separately after the OpenVMS installation completes. NOTE: Beginning with OpenVMS Version 8.3, DECwindows client files are made available through the DWMOTIF_SUPPORT kit. (Prior to Version 8.3, the client files were included directly with the OpenVMS operating system kit.) The OpenVMS installation procedure installs this kit automatically. The DWMOTIF_SUPPORT kit name is listed during the installation.
NOTE: For support of Instant Capacity (iCAP) and Pay per use (PPU) functionality (supported on cell-based Integrity servers), and for support of such products as gWLM and HP SIM, you must install TCP/IP Services for OpenVMS. When you use HP SIM to provision OpenVMS on an Integrity server, TCP/IP Services for OpenVMS is installed automatically. 17. Choose Descriptive Help Text (Optional): After you respond to the prompt for TCP/IP Services for OpenVMS, the final stages of the installation proceed.
• • • • • • Review the list of options and compare them with the requirements for your system. If you are selecting components individually, be sure that you include all components necessary to support the needs of your users. Note also that certain components depend on the installation of other components. If you are not sure whether you want certain options, request help by entering a question mark (?) at the prompt for that option.
selections and make changes if necessary, then installs the product, provides informational messages, and returns you to the original menu. First, you are asked whether you want to review the options: Do you want to review the options? [NO] If you answer YES, the procedure displays all the selected options and suboptions, similar to Example 3-1. If you answer NO, the installation continues as described with the sample script (beginning with "Execution phase starting ...") that follows.
HP HP HP HP HP HP HP I64VMS I64VMS I64VMS I64VMS I64VMS I64VMS I64VMS OPENVMS V8.3-1H1 SSL V1.3-284 TCPIP V5.6 TDC_RT V2.3-1 VMS V8.3-1H1 WBEMCIM V2.61-A070728 WBEMPROVIDERS V1.5-31 DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] DISK$I64SYS:[VMS$COMMON.] Portion done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90% %PCSI-I-PRCOUTPUT, output from subprocess follows ...
Refer to SYS$HELP:SSL013.RELEASE_NOTES for more information. HP I64VMS TDC_RT V2.3-1: The Performance Data Collector (base) for OpenVMS Users of this product require the following privileges: (CMKRNL,LOG_IO,WORLD,PHY_IO,SYSPRV,SYSLCK) Users of this product require the following process resource limits: WSQUO minimum 7000 A read-me file is available in SYS$COMMON:[TDC]TDC_README.TXT Release notes are available in SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT HP I64VMS TCPIP V5.6 : HP TCP/IP Services for OpenVMS.
Validate EFI Boot Options list: Timeout = 0 secs. ------------------------------------------------------------------1 OpenVMS on DKB400: PKA0.1 DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) efi$bcfg: Option Failed. Fixing Boot Entry automatically. efi$bcfg: Entry 1 Boot0001 removed. efi$bcfg: DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) (Boot0001) Option successfully added ----------------------------------------------------------------------1 entries validated.
23. Shut Down the System: Unless you want to perform other operations prior to booting the new system disk, choose the shutdown option (9) on the OpenVMS main menu to shut down the operating system, as shown in the following example. If you want to install layered products that have not been installed yet, HP recommends doing so during the postinstallation phase, as described in Section 7.14 (page 141).
Loading.: EFI Shell [Built-in] EFI Shell version 1.10 [14.61] Device mapping table fs0 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig8FCF6F11-... fs fs1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part4,Sig8FCF6F10-...) blk0 : Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,Master) blk1 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0) blk2 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part1,Sig8FCF6F11-...) b lk blk3 : Acpi(HWP0002,100)/Pci(1|0)/Scsi(Pun0,Lun0)/HD(Part2,Sig8FCF6F10-...
now, as explained in Section A.5 (page 164). Appendix A (page 149) includes additional information regarding setting up and booting HP Integrity servers. 3.5 Joining an OpenVMS Cluster If you answered YES to the question about joining an OpenVMS Cluster, the system now asks a series of questions about your configuration (such as CI, DSSI, SCSI, local area, or mixed interconnect). If you answered NO to this question, the system immediately runs AUTOGEN, as described in Section 3.6 (page 75).
3.6 Running AUTOGEN At this point, the system automatically runs AUTOGEN to evaluate your hardware configuration and estimate typical workloads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and your system reboots, the installation procedure is complete. The installation procedure displays messages similar to the following: AUTOGEN will now be run to compute the new system parameters.
. . After shutdown of an OpenVMS I64 system, it reboots automatically only if you have set the system disk boot option accordingly; otherwise, you must boot the system manually, as described in Section 3.4.1 (page 72). When the system reboots, it displays informational messages and accounting information indicating that your OpenVMS operating system has finished booting and is now ready for use.
4 Before Upgrading the OpenVMS Operating System This chapter describes which tasks you should perform prior to beginning an upgrade. Section 4.1 (page 77) includes a checklist that you can use to make sure you perform all the tasks described in this chapter. 4.1 Preupgrade Tasks Use the checklist in Table 4-1 to ensure that you perform all necessary tasks prior to upgrading your system. Table 4-1 Preupgrade Checklist Task Section □ Review relevant documentation. Section 4.
Earlier OpenVMS Version Documents Information in the following documents remains valid except where superseded by the OpenVMS documents listed previously. • • • • • HP OpenVMS Cluster Systems Guidelines for OpenVMS Cluster Configurations HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems (specifically, the chapter entitled “Managing System Parameters”), for information about using AUTOGEN, modifying the system parameters file (MODPARAMS.
NOTE: Unless you have specific reasons to do otherwise, HP recommends that you accept the defaults and install all OpenVMS options. OpenVMS and layered products have various dependencies on many of these options. Even if you think you do not need certain options, some OpenVMS or layered product operations might not work correctly if other OpenVMS options are not installed. Note also that, for OpenVMS I64 installations, the availability of certain options depends on the OE you have purchased.
$ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[000000]VMS$COMMON.DIR $ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING SYS$SYSDEVICE:[SYS*]SYSCOMMON.DIR If you did not boot from the system disk that you are upgrading, mount the disk to be upgraded and specify the actual device name in the command. For example, if the system disk to be upgraded is mounted on DKA100, you would use commands similar to the following: $ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[000000]VMS$COMMON.
4.5.5 Returning Authorization and AGEN$INCLUDE Files to the System Disk If you place authorization and AGEN$INCLUDE files on disks other than the system disk, the upgrade procedure will not find these files. This is because the other disks are not mounted during the upgrade. In addition, the logical names you set up to point to these files are not defined during the upgrade. The following sections explain how to make these files available to the upgrade procedure. 4.5.5.
Table 4-2 Logical Names for Relocated Authorization Files (continued) Logical Name Location and File Name VMS$OBJECTS SYS$SYSTEM:VMS$OBJECTS.DAT VMS$PASSWORD_DICTIONARY SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA VMS$PASSWORD_HISTORY SYS$SYSTEM:VMS$PASSWORD_HISTORY.DATA VMS$PASSWORD_POLICY SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE 4.5.5.2 AGEN$INCLUDE Files If you use the AGEN$INCLUDE feature in SYS$SYSTEM:MODPARAMS.
IMPORTANT: Any system parameters that you modified and did not enter in the SYS$SYSTEM:MODPARAMS.DAT file are lost during the upgrade. To retain these parameters, enter their names and the values that you have in use for them in SYS$SYSTEM:MODPARAMS.DAT. When AUTOGEN runs after the upgrade, it uses the values in SYS$SYSTEM:MODPARAMS.DAT. For example, if the current value of GBLPAGES is 30000, and you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.
SYS$SPECIFIC directory. When the system (or each system in a cluster) is rebooted after the upgrade, AUTOGEN runs. If a recent AGEN$FEEDBACK.DAT file is available, it is used. The data in this file helps AUTOGEN set system parameters for your specific applications and workload. NOTE: If you do not have a current AGEN$FEEDBACK.DAT file, AUTOGEN might calculate system parameters that do not reflect your system's requirements.
4.7.1 Setting the Boot Device Be sure your system is set to boot by default from the disk you intend to upgrade. For OpenVMS I64 systems, HP recommends using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) to add shadowed system disks in a multiple-member shadow set to the EFI boot device list and dump device list. Be sure to add all members to both lists. For more information about setting boot options and using this utility, see Section A.5.2 (page 165). 4.7.
entering its volume label. The /FOREIGN qualifier is required for the target disk when you use the BACKUP /IMAGE command. $$$ MOUNT /OVERRIDE=IDENTIFICATION DKA0: $$$ MOUNT /FOREIGN DKA100: 5. To back up the system disk to a magnetic tape, enter the following commands, where MTA0: is the magnetic tape drive and label is the volume label. Note that the BACKUP command automatically mounts the tape and begins the backup to it.
5 Preparing to Upgrade in an OpenVMS Cluster Environment This chapter describes how to prepare to upgrade in an OpenVMS Cluster environment. If you are not upgrading in an OpenVMS Cluster environment, go to Chapter 6 (page 95). 5.1 Preupgrade Tasks for OpenVMS Cluster Environments NOTE: Be sure you have performed the preupgrade tasks described in Chapter 4 (page 77) before you upgrade your OpenVMS Cluster system.
5.3 Mixed-Version Support in an OpenVMS Cluster Environment HP provides two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems: warranted support and migration support. Warranted support means that HP has fully qualified two specified versions coexisting in an OpenVMS Cluster and will address all problems identified by customers using these configurations.
Before introducing an OpenVMS Version 8.3-1H1 system into an existing OpenVMS Cluster, you might need to install certain patch kits (also known as remedial kits) on cluster members running earlier versions of OpenVMS. In a mixed-architecture cluster, you need to install an LMF patch on any OpenVMS Version 7.3-2 Alpha members. For a complete list of required patch kits, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS Version 8.3 Release Notes.
1. Log in locally to the SYSTEM account. If you have more than one system disk, make sure that you have performed the preupgrade tasks on each system disk that you are upgrading. Make sure the target system disk is not mounted on any other node in the cluster and remains dismounted during the upgrade. It should be mounted only on the system that is performing the upgrade. (For information about dismounting disks, see Section 5.5.2.3 (page 91).
the remaining OpenVMS Cluster members. Make sure the target system disk is not mounted on any other node in the cluster and remains dismounted during the upgrade. It should be mounted only on the system that is performing the upgrade. (For information about dismounting disks, see Section 5.5.2.3 (page 91).) NOTE: Any attempt to access the target system disk from the remaining OpenVMS Cluster members will corrupt the target disk.
6. Use the following command to shut down any nodes that boot from the system disk you are upgrading (shut down satellite nodes first): $ @SYS$SYSTEM:SHUTDOWN a. b. When the procedure asks whether an automatic system reboot should be performed, enter N (NO). Choose the REMOVE_NODE option. If a proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure hangs the cluster.
After the shutdown procedure is finished on all nodes, go to Chapter 6 (page 95) to begin the upgrade procedure. CAUTION: During the upgrade it is very important that the system disk being upgraded is accessed only by the node on which the upgrade is being performed. If the disk can be accessed from other nodes in the cluster, for example, through an HSC or HSJ device, you must ensure that this does not happen.
6 Upgrading the OpenVMS Operating System This chapter explains how to upgrade the OpenVMS operating system from a local CD or DVD drive and includes information about reinstalling or reconfiguring your system. This chapter is organized into sections that describe the major tasks for upgrading OpenVMS, in the order in which these tasks must be performed. Section 6.1 (page 95) includes a checklist that you can use to make sure you perform all the upgrade tasks described in this chapter. 6.
6.2.1.1 Booting from the Local Drive To boot a local OpenVMS I64 OE DVD, follow these steps. To boot the DVD on a cell-based server, a DVD device must be accessible by the nPartition that OpenVMS is being installed on. 1. 2. 3. 4. Make sure your Integrity server is powered on. If your system has an attached external device, make sure it is turned on and operational. Insert the DVD into the drive you want to use. Cycle power.
NOTE: When booting OpenVMS from the installation DVD for the first time on any OpenVMS I64 system with a SAN storage device, you might experience a delay in EFI initialization because the entire SAN is scanned. Depending on the size of the SAN, this delay might range from several seconds to several minutes. 6.2.1.
6.3.2 Choosing INITIALIZE or PRESERVE The procedure displays the following information and prompts: *********************************************************** This procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the key.
MKA500 is not a disk device CAUTION: If the selected target disk includes .EXE or .COM files installed by a previous upgrade or installation in one or more system-specific root directories in SYS$COMMON, the upgrade procedure tells you that when you boot from a root that contains any of these files, they are used instead of the files provided by the newer version of OpenVMS. This can make the upgraded system unbootable or cause errors after booting.
appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall or upgrade any of the products you installed along with the OpenVMS operating system installation, choose "Install or upgrade layered products" (option 3) from the main menu.
* these patches at a future time by use of the PRODUCT UNDO PATCH command. Do you want to continue? [YES] If you answer YES (the default), the recovery data sets are deleted and the OpenVMS upgrade continues. Deleting RECOVERY DATA SET 001 ... If you answer NO, the recovery data sets are not deleted and the OpenVMS upgrade aborts. Do you want to continue? [YES] NO %PCSIUI-I-USERABORT, operation terminated by user request You chose to retain recovery data on the target system disk.
OpenVMS I64 systems include WBEM Services for OpenVMS; the WBEM data repository requires an ODS-5 disk. If you choose to convert the target system disk to ODS-5, the repository can be on the system disk; otherwise you will need to provide an additional ODS-5 disk. (? for more information.) Do you want to convert the target system disk to ODS-5? (Yes/No/?) If you answer YES, the disk will be converted to ODS-5.
Hard links can be enabled on ODS-5 disks. WBEM Services for OpenVMS does not require hard links. (? for more information) (***Enabling hard links can take from 5-10 minutes to an hour or more.***) Do you want to enable hard links? (Yes/No/?) YES If you choose to enable hard links, the procedure automatically executes an ANALYZE/DISK_STRUCTURE/REPAIR operation to correctly set the reference (link) counts.
NOTE: If your newly upgraded system disk is a Fibre Channel device, HP recommends that you add it as a boot option in the EFI boot menu. If you do not allow the upgrade procedure to add the device to the boot menu, you can add it by using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM) after the upgrade completes. (To add Fibre Channel devices to the EFI boot menu, you must use this utility instead of EFI.
For more information about TDF and local time zone support, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. 6.3.12 Upgrading Windowing, Networking, and Related Products The procedure now presents information about the optional DECwindows GUI (DECwindows Motif for OpenVMS) and networking (DECnet and TCP/IP) products that will be upgraded along with the OpenVMS operating system.
NOTE: Beginning with OpenVMS Version 8.3, DECwindows client files are made available through the DWMOTIF_SUPPORT kit. (Prior to Version 8.3, the client files were included directly with the OpenVMS operating system kit.) The OpenVMS installation procedure installs this kit automatically. The DWMOTIF_SUPPORT kit name is listed during the installation. Required versions of some of the windowing and networking products might already be installed on the system.
6.4.3 Secure Delivery Validation As of Version 8.3, most PCSI kits included on the OpenVMS distribution media are signed using Secure Delivery. Each target file includes an associated digital signature file (also referred to as a manifest) that is used for Secure Delivery validation. This validation involves authenticating the originator (HP, in this case) and verifying the contents of the target file.
Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform COPYRIGHT 1976, 30-Aug-2007 Hewlett-Packard Development Company, L.P.
NOTE: Unless you have specific reasons to do otherwise, HP recommends that you accept the defaults and install all OpenVMS options. OpenVMS and layered products have various dependencies on many of these options. Even if you think you do not need certain options, some OpenVMS or layered product operations might not work correctly if other OpenVMS options are not installed.
HP I64VMS VMS V8.3-1H1 Operating System HP I64VMS WBEMCIM V2.61-A070728........Layered Product HP I64VMS WBEMPROVIDERS V1.5-31........Layered Product The following HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS products have been removed: CDSA V2.2 DECNET_PLUS V8.2 KERBEROS V3.0 OPENVMS V8.3 VMS V8.3 Layered Product Layered Product Layered Product Platform (product suite) Operating System HP I64VMS OPENVMS V8.3-1H1: OPENVMS and related products Platform HP I64VMS KERBEROS V3.
1 DKB400 PCI(0|20|1|0) Scsi(Pun1,Lun0) "OpenVMS on DKB400: PKA0.1" ---------------------------------------------------------------------1 entries found. In this example, one boot option is found. If multiple entries are found and if they are all SCSI devices, the procedure displays the following message and then notifies you that the upgrade is complete: The EFI Boot Manager menu includes multiple Boot Options for $1$DGA1200: Boot Options cannot be created or validated automatically.
on the OpenVMS I64 distribution media (CD/DVD). You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) 2) 3) 4) 5) 6) 7) 8) 9) Upgrade, install or reconfigure OpenVMS I64 Version 8.
7 After Installing or Upgrading the OpenVMS Operating System After you have installed or upgraded the OpenVMS operating system, you must perform several important tasks to prepare the system for operation. Section 7.1 (page 113) includes a checklist that you can use to make sure you perform all the postinstallation or postupgrade tasks necessary for your system. 7.
Table 7-1 Postinstallation and Postupgrade Checklist □ Task Section For a newly installed system disk, you can back up the disk. (At this point, you could reinstall OpenVMS onto the disk instead.) Section 7.2 (page 115) For a newly upgraded system disk, if it is not going to be a shadow set member, back up the system disk as a safeguard before proceeding with the next steps. If your newly upgraded system disk is going to be a shadow set member, you can re-form it in a later step.
Table 7-1 Postinstallation and Postupgrade Checklist (continued) Task Section □ On Integrity servers that use HP SIM services, configure HP SIM. Section 7.8.9 (page 132) □ Initialize and run the Performance Data Collector base software (TDC_RT). Section 7.8.10 (page 133) □ Prepare your OpenVMS system and your PC to run OpenVMS Management Station, and follow procedures in Appendix G (page 257). Section 7.8.11 (page 135) □ Install OpenVMS Debugger clients on a PC. Section 7.8.
complete any steps described in this chapter that you need to perform and, when you are finished, re-form the shadow set. If your newly installed or upgraded system disk will not be in a shadow set, back up the system disk by performing the following steps. (For a newly installed system disk, it might be just as easy to reinstall the operating system.) 1. 2. 3. 4. Shut down the system (as described in Section A.7.2 (page 185)). Boot the operating system media, as described in Section 3.2 (page 49).
For information about registering licenses, see the following documents: • • • HP OpenVMS License Management Utility Manual HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes and the HP OpenVMS Version 8.3 Release Notes HP Operating Environments for OpenVMS for Integrity Servers Software Product Description (SPD 82.34.xx). To register licenses, use the OpenVMS License utility as follows: 1.
7.5 Running AUTOGEN to Set System Parameter Changes If you modified MODPARAMS.DAT to enable or modify shadowing parameters (see Section 7.4 (page 117)), then run AUTOGEN and reboot the system by performing the following steps. This makes the changes take effect. 1. Run AUTOGEN by entering the following command: $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES NOFEEDBACK 2. 3. 4. After AUTOGEN completes, display or print the SYS$SYSTEM:AGEN$PARAMS.REPORT file and review it.
2. Enter a command in the following format: MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label where: • • • • DSAn: is the virtual unit name of the shadow set, where n is a unique number from 0 to 999. upgraded-disk: is the name of the shadowed system disk on which you just upgraded or installed OpenVMS. new-member: is the name of the disk you want to add as a member of the shadow set.
For instructions on customizing the system, review the following documentation: • • The release notes, for notes and restrictions that might be relevant to your customization plans The HP OpenVMS System Manager's Manual, for instructions on customizing and using your system Note that other customization tasks are described later in this chapter. 7.7.
your system to overwrite queue database files on a system where the queue manager has been started previously. $ START QUEUE /MANAGER /NEW_VERSION $ INITIALIZE /QUEUE /START /BATCH SYS$BATCH As noted, the queue manager starts automatically the next time you boot your OpenVMS system. To have the SYS$BATCH queue start automatically, edit the line in the SYS$STARTUP:SYSTARTUP_VMS.COM file that starts the SYS$BATCH queue by removing the exclamation mark (!) and, if present, the extra dollar sign ($).
If you installed DECnet Phase IV, see the DECnet for OpenVMS Guide to Networking manual for information about configuring this software using the NETCONFIG command procedure. Once you have configured DECnet Phase IV, edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM so that the software starts when the system reboots. (This step is not required if you are running DECnet Phase V.
• • • • • • • WBEM Services for OpenVMS (Section 7.8.5 (page 127)) WBEM Providers for OpenVMS (Section 7.8.6 (page 131)) Instant Capacity (iCAP) software (Section 7.8.7 (page 132)) Pay per use (PPU) software (Section 7.8.8 (page 132)) HP SIM software (Section 7.8.9 (page 132)) Performance Data Collector base software, TDC_RT (Section 7.8.10 (page 133)) OpenVMS Management Station (Section 7.8.11 (page 135)) 7.8.
NOTE: Do not attempt to explicitly remove CDSA from your system. The PRODUCT REMOVE command is not supported for CDSA although there appears to be an option to remove CDSA. CDSA is installed with the operating system and is tightly bound with it. Attempts to remove it might not work as expected and can create undesirable side effects. An attempt to remove it results in a message similar to the following: %PCSI-E-HRDREF, product HP I64VMS CDSA V2.3 is referenced by HP I64VMS OPENVMS V8.
NOTE: Do not attempt to explicitly remove the Availability Manager from your system. The PRODUCT REMOVE command is not supported for Availability Manager although there appears to be an option to remove Availability Manager. The Availability Manager base software is installed with the operating system and is tightly bound with it. Attempts to remove it might not work as expected and can create undesirable side effects.
NOTE: Do not attempt to explicitly remove Kerberos from your system. The PRODUCT REMOVE command is not supported for Kerberos although there appears to be an option to remove Kerberos. Kerberos is installed with the operating system and is tightly bound with it. Attempts to remove it might not work as expected and can create undesirable side effects. An attempt to remove it results in a message similar to the following: %PCSI-E-HRDREF, product HP I64VMS Kerberos V3.1 is referenced by HP I64VMS OPENVMS V8.
NOTE: Do not attempt to explicitly remove SSL from your system. The PRODUCT REMOVE command is not supported for SSL although there appears to be an option to remove SSL. SSL is installed with the operating system and is tightly bound with it. Attempts to remove it might not work as expected and can create undesirable side effects. An attempt to remove it results in a message similar to the following: %PCSI-E-HRDREF, product HP I64VMS SSL V1.3 is referenced by HP I64VMS OPENVMS V8.
NOTE: HP recommends that you do not remove the WBEM Services for OpenVMS product even if you do not have a need for it. If you attempt to use the PRODUCT REMOVE command to remove this product, you might see a message similar to the following. This message is automatically displayed for any product that is required with OpenVMS. The consequences of removing WBEM Services for OpenVMS might not be as severe as implied by the message unless other software is using the product on your server.
Do you want to continue (Yes/No) [YES]?: %WBEMCONFIG-I-CREREPBEGIN, Create Repository Begins... %WBEMCONFIG-I-CREREPCOMPLETE, Create Repository Complete. This utility creates: SYS$STARTUP:WBEM_Services$Startup.com which should be added to SYS$STARTUP:SYSTARTUP_VMS.COM. This utility creates: SYS$STARTUP:WBEM_Services$Shutdown.com which should be added to SYS$STARTUP:SYSHUTDWN.COM. This utility creates: SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.
1. Enter the following command $ RUN SYS$SYSROOT:[WBEM_SERVICES]WBEM_SERVICES$CONFIG This command starts the utility that configures and initializes the environment for WBEM Services for OpenVMS. If the WBEM Services for OpenVMS product (Version 2.0) available with OpenVMS I64 Version 8.3 is already configured on your system, the following error message and the recommended remedial actions appear: %WBEMCONFIG-E-SYSCOMMONLOGICAL, WBEM_VAR can no longer be defined to point to a location in SYS$COMMON.
This utility creates: SYS$STARTUP:WBEM_Services$Shutdown.com which should be added to SYS$STARTUP:SYSHUTDWN.COM. This utility creates: SYS$SYSROOT:[wbem_services]WBEM_Services$Define_Commands.com which users who use this product can add to their login.com. 4. The utility now asks you whether to start the CIMServer: Do you want to start the CIMServer now (Y/N) {Y}?: CIMServer must be running so that your system can use such applications as Instant Capacity, Pay per use, and gWLM.
NOTE: HP recommends that you do not remove the WBEM Providers for OpenVMS product even if you do not have a need for it. If you attempt to use the PRODUCT REMOVE command to remove this product, you might see a message similar to the following.
7.8.10 Initializing and Running the Performance Data Collector Base Software (Optional) The Performance Data Collector for HP OpenVMS (TDC) collects and manages configuration and performance data for analysis by other applications. TDC_RT Version 2.2 is a run-time only (base) variant of the TDC software that is installed automatically with the OpenVMS operating system for use on specific operating system platforms. Use of the TDC_RT software is not required.
7.8.10.3 Compatibility with Prior Releases Note the following about prior releases of TDC software. • TDC Version 1.n For users of some third-party system-management applications, TDC Version 1.n was distributed by web download. Applications developed using TDC Version 1.n will not work with TDC Version 2.2 software until they are rebuilt using the TDC Version 2.2 Software Developer’s Kit (SDK). You can obtain this SDK kit from the following website: http://www.hp.
For more information about running the application, see the file SYS$COMMON:[TDC]TDC_README.TXT. Release notes are located in the file SYS$COMMON:[TDC]TDC_RELEASE_NOTES.TXT. See both of these files before running the collector application. 7.8.10.5 Installation in OpenVMS Clusters TDC_RT is installed in SYS$COMMON:[TDC] by default. Included are only those files required to run the data collector with the particular operating system version it was distributed with.
system problems, and so forth. A template file is provided by the operating system. To create your own SYS$WELCOME file, do the following: 1. Copy the template file using the following command: $ COPY SYS$MANAGER:WELCOME.TXT SYS$SPECIFIC:[SYSMGR]WELCOME.TXT For a clusterwide welcome message, you can copy the file to SYS$COMMON:[SYSMGR]. 2. 3. Replace the text in SYS$SPECIFIC:[SYSMGR]WELCOME.TXT with text specific to your system. Edit SYS$MANAGER:SYSTARTUP_VMS.
NOTE: You can obtain information about individual system files by entering the HELP SYSTEM_FILES command at the dollar sign prompt ($). IMPORTANT: Unless you have a specific need to exclude operating system files from your system disk, HP strongly recommends that you accept the defaults and install all files that are part of OpenVMS. In general, limited disk space is not a good reason to exclude files; problems encountered when needed files are missing can cost much more than the cost of a larger disk.
Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products" from the main menu. If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu.
them can hinder system performance. You can use the command procedure SYS$UPDATE:LIBDECOMP.COM to decompress, compress, or list the sizes of the system libraries.
FTP> passive on Passive is on. 6. To access the directory containing the V8.3-1H1 operating system patches, enter the following command, using the exact case indicated for each letter: FTP> cd openvms_patches/i64/V8.3-1H1 250 CWD command successful. To access the directory containing patches for layered products such as TCP/IP Services or DECnet, enter the following command : FTP> cd openvms_patches/layered_products/i64 250 CWD command successful. 7.
7.14 Installing and Configuring Layered Products (New Installations, Some Upgrades) The OpenVMS operating system kit includes several layered products.
For additional information about installing layered products, see the HP OpenVMS System Manager's Manual. 7.14.1 Alternative Procedure Use this alternative procedure to install the following products: • Layered products on a target system that has a different operating system version than that of the operating system media (CD/DVD) • Layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .
7.15 Creating Print Queues (New Installations, Some Upgrades) If you have a large number of print queues to add and you need to get the system in use quickly, you can set up one print queue per area or work group and then add the other print queues later, after the user accounts are added (Section 7.17 (page 143)). For more information about adding print queues, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. 7.16 Updating SYSTARTUP_VMS.
7.20 Reforming the Shadow Set as Final Postupgrade Backup If your system disk participates in a volume shadowing environment, re-form the shadow set again to generate another shadow copy onto the other disks in the set. To do so, follow the instructions in Section 7.6 (page 118). 7.
3. HP recommends that you run AUTOGEN from the SAVPARAMS phase through the TESTFILES phase weekly thereafter until the system stabilizes (that is, until AUTOGEN finds nothing that needs to be adjusted). Make sure you run AUTOGEN when your system is running under a typical workload. Examine AGEN$PARAMS.REPORT to determine the need for additional changes.
• • Enter numeric values as integers without commas (for example, 10000). Enter alphabetic characters in lower or uppercase. HP recommends that you include comments in the MODPARAMS.DAT file indicating who changed the value, when it was done, and why it was done. An exclamation point (!) serves as a comment starter and can appear anywhere on a line. The following example illustrates the modifications recommended in the preceding bulleted items: ! the following changes made by K.
• The upgrade procedure creates a new MODPARAMS.DAT for each system root on your system disk. Normally, there is one root for each computer that boots from the system disk. You must review and adjust each of these MODPARAMS.DAT files individually. The MODPARAMS.DAT file for the system on which you are running is located in the SYS$SYSROOT:[SYSEXE]MODPARAMS.DAT file. The MODPARAMS.DAT files for other roots on the same system disk can be found in SYS$SYSDEVICE:[SYSx.SYSEXE]MODPARAMS.
A Configuring OpenVMS I64 Hardware Operation and Boot Operations, and Booting and Shutting Down Your System This appendix briefly describes the configuration and management tools that might be available on HP Integrity servers, and explains how to set up the system console, configure boot options, boot the OpenVMS I64 operating system, and shut down the operating system. The appendix also includes brief troubleshooting procedures.
A.1.1 Overview of Utilities and Console Options The main interfaces that are typically available for configuring and managing your HP Integrity server environment are the Extensible Firmware Interface (EFI) and the Management Processor (MP). On entry-class Integrity servers, MP has been replaced by the Integrated Lights Out (iLO) Management Processor, which includes all the functionality of MP plus additional features. On some models, the Baseboard Management Control (BMC) utility is provided.
the nPartition is in an active state but has not booted an operating system; each nPartition has its own EFI interface. Using MP, you can select the partition for which you want EFI access. You can access all hardware and nPartitions in the complex. The following is a brief summary of MP’s main features: — Console connectivity As a console interface, MP enables you to interact with EFI and to power the server on or off; ultimately, it can function as the OPA0: terminal port on OpenVMS.
A.1.2 Configuration and Management Utilities on Cell-Based Servers For the more complex environments provided by cell-based Integrity servers, a wider variety of tools is provided. Systems with multiple nPartitions provide a separate EFI interface for each nPartition. MP provides access to, and allows management across, the complex and each nPartition EFI interface.
provides serial access as well as networked access to the firmware console. If using the serial port, use a VT100–capable terminal or emulator device. On Integrity servers that do not have an MP port, the console serial port (generally on the back of the server) is enabled. With the exception of some older Integrity server models, such as the HP Integrity rx2600 server, the current firmware available for Integrity servers provides a text menu-based interface by default.
enabling multihead DECwindows graphics operation, the VGA console defaults to screen 0. If no VGA device is configured as a console, DECwindows selects a default screen based on the Integrity server model and device bus ordering. For details about enabling multihead DECwindows graphics operation, see Section 7.7.3 (page 121). Note the following restrictions: — OpenVMS supports up to four add-on graphics devices plus any built-in graphics, depending on the Integrity server and available slots.
A.2.1.1 Using the EFI Boot Manager to Select the OpenVMS Console To select the device for your OpenVMS console using the EFI Boot Manager, follow these steps. Depending on the firmware version and configuration, menu selections displayed on your screen might differ from those seen in the examples . Note that with this EFI firmware, you no longer have to select a console input device, console output device, and console error device.
4. Enter P to configure the selected device as the Primary console. You then see the selected device as the Primary console: 5. Press the Esc key to return to the previous menu. When prompted whether to save changes to NVRAM, enter Y: 6. When prompted whether to reset the system, enter Y to make the changes take effect: A.2.1.
1. At the EFI Shell prompt, enter the conconfig command to view the index number for the available console devices, as in the following example (the column titled “Primary” displays how the device is configured (P for Primary, S for Secondary, NC for Not Configured): Shell>conconfig CONSOLE CONFIGURATION Index Primary Type ----- ------- ----1 P Serial 2 S Serial 3 S VGA 2.
NOTE: To see the MP login user name and password prompts, you might need to press Enter one or more times on your console keyboard. If this does not work, try pressing Ctrl/B. If you see only the MP password prompt, press Enter to get to the MP login prompt. If the login prompt still fails to appear, the system might be powered off. (When you powered on the system, you might have pressed the power button twice, which turns it on and then off.
NOTE: The appearance of EFI Boot Manager screens and menus differs from version to version of the firmware. Boot Menu EFI Shell [Built-in] Internal Bootable DVD --------------------Boot Configuration System Configuration Security Configuration From the EFI boot menu, select the Boot Configuration option (or, in some versions of EFI, the Boot Option Maintenance Menu). To move to an option, use the up or down arrow key.
NOTE: With OpenVMS systems, the input, output, and error console all must point to the same serial-line console device. New systems might be shipped with multiple devices selected for each of the console types, so make sure only one device is selected for each. If you see an error message that mentions multiple device-path instances for the console input or output device, perform the following steps to select a single console only.
5. Perform a cold reset if required. Your system might require a cold reset. Newer versions of EFI do not require a cold reset. For more information, see your hardware documentation. At this point, you can boot the OpenVMS I64 DVD to install the operating system onto a system disk. Follow the instructions in Chapter 3 (page 49) (specifics for booting are provided in this appendix).
instructions on how to use the utility, see Section A.5 (page 164). For more information about configuring Fibre Channel devices with this utility, see Appendix D (page 241). For information about using the OpenVMS I64 Boot Manager utility to display boot options, see Section A.5.2.2 (page 168). For information about setting the pause length, see Section A.5.2.3 (page 169).
(SYS$MANAGER:BOOT_OPTIONS.COM), as described in Section A.5 (page 164). The EFI Utilities for OpenVMS are described in the HP OpenVMS System Management Utilities Reference Manual. Example 1 — From Top Level fs0:\> \efi\vms\vms_show device . . . fs0:\> \efi\vms\vms_set dump_dev dga3730 Example 2 — First Moving to \efi\vms fs0:\> cd \efi\vms fs0:\efi\vms> vms_show device . . .
For more information about using EFI, see the documentation provided for your Integrity server. Extensive information can also be found online at: http://developer.intel.com/technology/efi/help/efidocs.htm A.4 Enabling or Disabling Hyper-Threading on Dual-Core Processors Systems that have Intel Itanium® Dual-Core processors can support Hyper-Threading. Hyper-Threading provides the ability for processors to create an additional logical CPU that might allow additional efficiencies of processing.
1. Power up your server system, as explained in the hardware documentation for your server. If you use the power button on the front panel, press it only once. NOTE: If you see a warning that the BMC system event log (SEL) is full, you can safely continue by following the prompts; OpenVMS processes the contents of the SEL. If you want to clear the SEL manually, see the instructions in the first note of Section A.6 (page 172). HP recommends that you load and use the most current system firmware.
• During installation or upgrade, allowing the OpenVMS I64 installation/upgrade procedure to automatically establish an EFI boot option for your system disk • Using the OpenVMS I64 Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.
(D) Set to operate on the Dump Device Options list (G) Set to operate on the Debug Device Options list (E) EXIT from the Boot Manager utility You can also enter Ctrl-Y at any time to abort this utility Enter your choice: 1 NOTE: While using this utility, you can change a response made to an earlier prompt by entering the caret (^) character as many times as needed. To end and return to the DCL prompt, press Ctrl/Y. 3. The utility prompts you for the device name.
Enter a short description (do not include quotation marks). Description ["DKA0"]: DKA0: OpenVMS V8.3-1H1 for PLMs System efi$bcfg: DKA0: (BOOT003) Option successfully added 8. When you have successfully added your boot option, exit the utility by entering E at the prompt: Enter your choice: E $ A.5.2.1.1 Using EFI to Set Automatic Booting of Your System Disk HP recommends allowing the OpenVMS installation or upgrade procedure to set your system disk to boot automatically.
To display all entries in the Boot Options list, press Return. To display specific entries, enter the entry number or device name. (Enter "?" for a list of devices): DQA0 EFI Boot Options list: Timeout = 20 secs. ---------------------------------------------------------------------------04. DQA0 PCI(0|0|2|0) ATA(Primary,Master) "DVD-ROM " ---------------------------------------------------------------------------1 entries found.
A.5.3 Writing a New Boot Block The boot block structures on the system disk contain the size and location of the boot partition and other details relevant to the bootstrap of OpenVMS I64. The size and location of the boot partition stored within the boot block structures must be maintained and must reference the current location of the OpenVMS file SYS$EFI.SYS.
NOTE: If the target OpenVMS I64 system disk has an incorrectly-placed [000000]GPT.SYS file, the disk cannot be used reliably as an OpenVMS I64 system disk. Typically, the file gets incorrectly placed due to the use of an older version of BACKUP/IMAGE, a file-based BACKUP disk restoration, or an errant disk defragmentation tool (the file is set with /NOMOVE to disable move operations; defragmentation tools that do not honor this setting will corrupt the file). A correctly-located GPT.
A.5.4 Alpha and Equivalent Integrity Server System Boot Commands The Extensible Firmware Interface (EFI) on Integrity servers performs most of the same functions that the SRM console does on Alpha processors. If you are familiar with the Alpha tool, use the following table to find EFI commands equivalent to the Alpha commands you commonly use on Alpha systems. Note that some of the commands listed might not be available on certain hardware systems.
NOTE: To boot your OpenVMS I64 operating system, you can use a VGA graphics device (except on an rx2600 Integrity server or other servers that lack the firmware capabilities), a serial device, or a network interface for the console. For information about setting up the console on your Integrity server, see Section A.2 (page 152).
A.6.1.2 Booting OpenVMS I64 on an nPartition CAUTION: To prevent loss of data when booting your OpenVMS I64 operating system, note the following: • You must first ensure that the nPartition has its ACPI configuration set to the default (see Section A.5.1 (page 165)). • OpenVMS I64 does not support using cell local memory (CLM). The nPartition on which OpenVMS I64 is booted must have all memory configured as interleaved memory (memory that can be mapped across more than one cell).
4. From the main EFI boot menu (for cell-based servers, this must be the EFI boot menu for the nPartition on which OpenVMS is to be booted), select the appropriate item from the boot options list. Note that the EFI boot menu is timed; press any key to stop the countdown timer. For some systems, the boot option to select is the Internal Bootable DVD option. If that option is not listed in your EFI boot menu, move to the Boot From a File menu and select the Removable Media Boot option, if present.
1. To ensure that EFI can access the DVD, enter the following commands at the EFI Shell prompt of a entry-class or single-cell Integrity server. Enter the commands in the order shown. (The EFI Shell prompt may not necessarily be Shell> as in this example; it could be a prompt that reflects the current file system, such as fs0:>.
2. To boot the DVD, enter the following command at the EFI Shell prompt, where fsn: is the Integrity server DVD drive (such as fs0:). Shell> fsn:\efi\boot\bootia64.efi If this command does not work, or if you have doubts about which device maps to the DVD drive, you can use the EFI Boot Manager menu system to boot the OE DVD, as described in the following steps: a. From the main EFI boot menu, select the Boot Configuration option (or in some versions of EFI, the Boot Option Maintenance Menu). b.
EFI Boot Maintenance Manager ver n.nn[nn.nn] Select file or change to new directory: n/nn/nn 06:21a
n/nn/nn 06:21a . . . n/nn/nn 06:21a . . . 2,048 . 2,048 .. 334,848 BOOTIA64.EFI Exit A.6.3 Booting the OpenVMS I64 OE DVD from the InfoServer To boot from a virtual DVD drive on the LAN using OpenVMS I64 InfoServer software, you must initially perform certain configuration steps (one time only).2. Boot the system disk manually by entering the following command at the EFI Shell prompt, where fsn: (such as fs1:) is the device associated with the system disk: Shell> fsn:\efi\vms\vms_loader.efi You must either specify the full path (as shown in this example) or start the system loader from the \efi\vms directory. For more information, see Section A.3.1 (page 162). A.6.
Table A-2 SYSGEN Commands Used in the SYSBOOT Procedure (continued) Command Description HELP Displays a summary of the SYSBOOT commands on the terminal screen. SET parameter-name Establishes the value of a system parameter. SET/STARTUP Sets the name of the system startup command procedure. SHOW [parameter] Displays active, current, default, maximum, and minimum values for specific parameters. (Use qualifiers to display characteristics of parameters grouped by categories.
Value System Response 6 Includes XDELTA and takes the initial breakpoint. 7 Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system initialization. The following is an example of booting with XDELTA from fs1: at the EFI> prompt: EFI> fs1:\efi\vms\vms_loader.efi -flags 0,7 For more information about using XDELTA, see the HP OpenVMS Delta/XDelta Debugger Manual. A.6.
3. To avoid starting all layered products on a system that is not tuned for them, possibly causing the system to hang, set the STARTUP_P1 system parameter as follows: SYSBOOT> SET STARTUP_P1 "MIN" 4. Enter the following command to ensure that the operating system does not record for subsequent system reboots the STARTUP_P1 parameter change you made in step 3: SYSBOOT> SET WRITESYSPARAMS 0 5. Enter the following command to continue booting: SYSBOOT> CONTINUE 6. 7.
5. 6. When the system is booted, the operator console displays the DCL command prompt ($). You are now logged in. Enter the following two DCL commands: $ SPAWN $ SET NOON The SPAWN command enables you to stay connected to the console, and the second command instructs the operating system to ignore any errors that might occur. If you do not enter these commands and you invoke an error, the system logs you out. Without the SPAWN command, you are logged out when the startup procedure completes in step 8. 7.
4. At the DCL prompt, the system now accepts startup commands directly from the console. Enter the following two commands. These commands allow a normal system startup while you are left logged in on the console. Without the SPAWN command, you are logged out when the startup completes. $ SPAWN $ @SYS$SYSTEM:STARTUP 5. Once you log out of this session, the system completes the startup and can be used normally. Optionally, you can choose to reboot the system.
A.7.2 Shutting Down the System Before you shut down the operating system, decide if you want it to reboot automatically or if you want to enter console-mode commands after the shutdown completes. If you want the system to reboot automatically after the shutdown, first set up automatic booting, as described in Section A.5.2 (page 165). You can perform the following two types of shutdown operations, as discussed in the indicated sections: • An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM (see Section A.7.2.
For more information about the OPCCRASH program, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. On cell-based Integrity servers, entering the OpenVMS RUN SYS$SYSTEM:OPCCRASH command results in the system dumping memory and then halting at the P00>>> prompt. To reset the nPartition following OPCRASH, access the nPartition console and press any key to reboot. Using the MP tc command to reset an nPartition results in the system dumping memory and then automatically resetting the nPartition.
To determine whether the failure is a system problem: • Be sure that you did not press F1 (Hold Screen). The Hold Screen light turns on when you press either F1 or Ctrl/S. • Press Ctrl/T to check the status of your process. A status line should appear indicating the name of the program that is executing and other information. If the status line does not appear, the program you are executing might be stalled or hanging.
B Setting Up and Performing Network Booting This appendix explains the steps required to enable your system to boot over the LAN using the OpenVMS InfoServer utility, a software application available on OpenVMS Alpha (Version 8.3 or later) and OpenVMS I64 (Version 8.2-1 or later) systems. It also describes how to boot the virtual DVD/CD drive from the network. B.
Because of these differences, any procedures used for Alpha systems to set up booting from the InfoServer hardware are not valid for setting up booting from the OpenVMS InfoServer utility. In addition, actions for setting up booting from the OpenVMS I64 InfoServer utility differ from those required for setting up booting from an OpenVMS Alpha InfoServer utility.
NOTE: The discussion of InfoServer booting in this manual pertains to environments where the boot clients and servers are located in the same LAN. For more complex circumstances, consult HP Customer Support. B.2 Setting Up Your System as an InfoServer Client To set up your local OpenVMS I64 system as an InfoServer client for network booting, you must perform the following steps. Detailed instructions are provided in the subsections that follow.
B.2.2 Adding the Network Boot Option to the EFI Boot Manager To add the LAN device (virtual DVD drive) as a network boot option, use the OpenVMS I64 Boot Manager utility, as follows: 1. At the DCL prompt, enter the following command to start the OpenVMS I64 Boot Manager utility: $ @SYS$MANAGER:BOOT_OPTIONS 2. The OpenVMS I64 Boot Manager Boot Options main menu is displayed.
the device name and MAC address (without dashes) are included anyway in the boot entry line. Enter a short description (do not include quotation marks). Description ["EIA0"]: I64 UPGRADE VIA NET efi$bcfg: eia0 (Boot0002) Option successfully added Using the utility to display the devices at this point (selecting 2 on the main menu), you see your device listed, as in the following example: Enter your choice: 2 To display all entries in the Boot Options list, press Return.
The following steps are necessary to set up the InfoServer software on the designated system: 1. Copy SYS$STARTUP:ESS$LAD_STARTUP.TEMPLATE to ESS$LAD_STARTUP.DAT (save the ESS$LAD_STARTUP.TEMPLATE file as a backup). 2. Edit SYS$STARTUP:ESS$LAD_STARTUP.DAT to modify parameters as needed. This file configures InfoServer parameters affecting the OpenVMS LASTport/Disk™ (LAD) server, which allows access to the DVD drive.
Parameter Description 6 64 blocks 7 128 blocks 8 256 blocks CACHE_BUCKETS Determines the number of buckets in the cache. The default is 512. Numbers larger than 16384 might adversely affect performance. To reach a desirable cache size, consider increasing the BUFFER_SIZE parameter. MAXIMUM_SERVICES Sets the maximum number of services that can be defined at one time for the server. The value of this parameter must be a power of 2.
you can skip the reboot and execute the SYS$STARTUP:ESS$LAD_STARTUP.COM file manually. After you complete these steps, the InfoServer server software is running and available to serve boot requests. Note that the network devices are LAD0 (the LAD Server Virtual Device) and LAST0 (the LAST Transport Layer Virtual Device). 6. The InfoServer server can run on the same system as the InfoServer client. You might want to start the InfoServer client on this system, allowing the system to mount InfoServer devices.
NOTE: All instructions and examples assume the use of TCP/IP Services for OpenVMS. Other IP products might work but have not been tested and are not supported at this time. 1. Make sure TCP/IP Services for OpenVMS is installed and that: • At least one IP interface is defined. • The BOOTP server and TFTP server are configured and started. • Optionally, make sure TELNET and FTP are configured and started. To display IP interface information, use the TCPIP SHOW INTERFACE command.
6. For each boot client, add an entry in the BOOTP database to associate the MAC address of the client’s LAN device with the boot file to be loaded from the boot server, as in the following example. In this example, hostname is the host name of the boot client, and MACaddress is the client’s MAC address in the format xx-xx-xx-xx-xx; the boot file specification need not include “TCPIP$TFTP_ROOT:”. $ TCPIP SET BOOTP hostname /HARDWARE=ADDRESS=MACaddress_$ /FILE=[V831H1]VMS_LOADER.
Displays information about the boot client MOZART as stored in the BOOTP database (use this command to verify that the client has been configured appropriately). After you complete these steps, in addition to the required steps in the preceding sections, you can boot a client over the network using the InfoServer application. Instructions on performing the InfoServer boot are in Section B.5 (page 199). A troubleshooting section is included in Section B.6 (page 201). 7 B.
Booting with the EFI Boot Manager a. b. c. From the EFI Boot Manager screen, select the Boot Configuration option (or in some versions of EFI, the Boot Option Maintenance Menu). From the EFI Boot Configuration menu, select the Boot From a File option. The Boot From a File menu lists the bootable devices (in EFI terminology, load files), including their MAC addresses. The composition of the list depends on how your Integrity server is set up.
FUNCTION ID 1 2 3 4 5 FUNCTION - Display Menu Help Choose Service Select Options Stop Enter a function ID value: 4. Respond to the prompts by pressing Enter after each entry; use the default service name indicated or one suggested by the system manager: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name ( I640831H1 is the default service name for the OpenVMS I64 OE DVD; check with your system or network manager for the service name to specify).
1. When you attempt to boot over the network, check your console display for the following: • The IP address of the boot server that sends your EFI console the OpenVMS I64 loader file (VMS_LOADER.EFI). If this IP address is not as expected, your client host might be in the database of the wrong boot server. Enter your client host IP address in the database of the correct boot server (see step 5 of Section B.4 (page 196)), and remove your client from the database of any other boot servers.
C Using HP SIM and vMedia to Install and Upgrade OpenVMS HP Systems Insight Manager (HP SIM) allows you to provision OpenVMS to one or more servers in the network. This means that, from a single location in the network (a Windows-based PC or server designated serving as the management workstation), you can use HP SIM to install or upgrade OpenVMS on several servers simultaneously.
SIM to install or upgrade a server over the network. For more information about vMedia, see Section C.2 (page 232). NOTE: DVDs are accessible by vMedia as read-only. C.1.2 Prerequisites for HP SIM Provisioning Support of HP SIM provisioning requires the following: • HP SIM Version 5.1 or later, running on a Microsoft Windows ProLiant server. The ProLiant server must be on the same LAN as any Integrity servers that you plan to provision.
NOTE: When using vMedia to install or upgrade OpenVMS, HP recommends that you use an image of the OpenVMS I64 OE DVD located on your Windows-based PC or server. This has two advantages: — If the DVD is defective or corrupted, when you attempt to create an image of it, the imaging software will fail, thereby indicating the DVD's condition. — Installing or upgrading OpenVMS from the image file is much faster than installing from a DVD.
1. At least one system in the LAN must be designated as the InfoServer server. This is the system that hosts the DVD drive from which network booting is performed. It must be running OpenVMS Alpha Version 8.3 or later, or OpenVMS I64 Version 8.2–1 or later. Perform these basic steps to set up the InfoServer server: a. Copy the SYS$STARTUP:ESS$LAD_STARTUP.TEMPLATE file to the SYS$STARTUP:ESS$LAD_STARTUP.DAT file.
hostname is the host name of the provisioning/boot client and ipaddress is its IP address: $ TCPIP SET HOST hostname/ADDRESS=ipaddress f. For each provisioning/boot client, you might need to add an entry in the BOOTP database to specify a gateway and network mask.
2. Make sure your Integrity server iLO 2 MP and vMedia are set up as documented in your Integrity server hardware documentation (for example, see the HP Integrity iLO 2 MP Operations Guide). Enable the right to use the vMedia applet. Make sure your Integrity server is powered on. Once you connect to your server's iLO 2 MP and log in, you can check the status and power on your Integrity server from your browser.
4. Select the Virtual Devices tab and then select Virtual Media from the list on the left. If your Integrity server is not a cell-based system, skip to the next step. If your server is a cell-based system, you must select the partition before launching the vMedia application, as in the following example: 5. Click Launch in the upper right corner of the Virtual Media screen, as shown in the following example: C.
6. You might see the following warning or similar warnings or informational messages regarding security. In the security warning shown here, you can check the box to always trust content, and then click Yes. (To avoid certification warnings, install valid certificates for the iLO 2 MP. For more information, see the HP Integrity iLO 2 MP Operations Guide. In addition, see the online help provided by your browser.) A screen similar to the following might appear next.
7. From the Virtual CD/DVD-ROM dialog box that appears next, make sure the Local Media Drive option is selected, and then click Create Disk Image, as in the following example: 8. The Create Disk Image dialog box appears, as in the following example. Specify a path or file name for the image to be created, and then click Create. C.
NOTE: As noted previously, HP recommends that you do not install or upgrade directly from a DVD (on your local Windows-based management workstation) with vMedia. Creating a disk image on the local drive (or a network drive) will make the installation or upgrade much faster. This assumes the local or network drive is accessible to your Integrity server over a high-speed network link.
9. This brings up the Virtual CD/DVD-ROM dialog box, as in the following example. Select the Local Image File option, browse for the created ISO image file that you want vMedia to access, and then click Connect. The screen should then indicate the image is connected to vMedia, as in the following example. Now the targeted Integrity server is ready to be booted using the ISO image file. C.
You can now provision OpenVMS through HP SIM (see Section C.1.6.2 (page 226)) or use vMedia independently of HP SIM (see Section C.2 (page 232). C.1.
1. First, to determine whether your system's iLO 2 MP has been discovered, access the HP SIM home page and select System and Event Collections→All Management Processors in the lefthand panel. The following is an example of an HP SIM All Management Processors listing. If your system is listed with the proper port IP address and identification, you are ready to provision.
2.
3. Under the System Information heading, enter the IP address of the system running the InfoServer, then click Add System: C.1.6 Provisioning OpenVMS Once the iLO 2 MP of your Integrity server (and any other servers you want to provision) has been discovered and identified, you can provision OpenVMS (deploy the operating system on the target Integrity servers). To provision OpenVMS using the InfoServer, see “Section C.1.6.1.” To provision OpenVMS using the vMedia device, see Section C.1.6.2 (page 226).
C.1.6.1 Provisioning OpenVMS Through the InfoServer To provision OpenVMS using HP SIM with the InfoServer, follow these steps: 1. From the HP SIM home page, select System and Event Collections→All Management Processors. 2. Select Deploy→OpenVMS, and then select one of the following options from the OpenVMS menu: 1. Install OpenVMS from InfoServer... 2. Install OpenVMS from vMedia... 3. Upgrade OpenVMS from InfoServer... 4. Upgrade OpenVMS from vMedia...
3. In the Step 1: Verify Target Systems screen, HP SIM displays any discovered and identified Integrity servers that run the OpenVMS operating system and verifies whether they are supported for provisioning. In the following example, two servers are found and verified. Click Run Now. OpenVMS can be provisioned on up to eight servers at once. C.
4. 220 In the Step 2 screen of the upgrade, enter the MP access information (the default for the user name and password is Admin) for your Integrity servers, as well as the InfoServer/BOOTP information, as in the following example. The timeout value is the inactivity duration as observed from the provisioned server during an installation or upgrade. You can increase the default value; HP does not recommend decreasing the value. The default for InfoServer provisioning is five minutes.
5. In the Step 3 screen of the upgrade, HP SIM uses the InfoServer to access disks on the systems that are available to be upgraded, as shown in the following example. This takes a few minutes. Progress is indicated in the Upgrade Disk field. C.
6. Meanwhile, to see what is going on in the background for an Integrity server that is being provisioned, access the server's iLO 2 MP website address from any browser, as in the following example. Click Launch to access the server's serial console. The following console screen example shows the procedure providing the InfoServer information and retrieving the system loader file VMS_LOADER.EFI.
IMPORTANT: Do not interrupt the process! Do not allow write access to your server's console while the installation or upgrade is in progress. C.
7. When finished, the names of the disks to be upgraded are displayed, as in the following example. Click Next. 8. This begins the upgrade.
9. The upgrade script is now running in the background on the console screen. The following example shows several of the automatic responses to the upgrade script. IMPORTANT: Do not interrupt the process! Do not allow write access to your server's console while the installation or upgrade is in progress. C.
10. After approximately 60 minutes (depending on the network and configuration), the upgrade completes, as indicated in the following example: If the procedure does not complete successfully, the provisioning terminates. The reason for failure is displayed in the Progress column as well as on the console screen and in the log file HPSIM\logs\OPENVMS\ipaddress-date.log on the ProLiant server that is running HP SIM.
IMPORTANT: For upgrades, your OpenVMS boot flags must be set to (0,0). IMPORTANT: Do not interrupt the installation or upgrade process at your server's console. Do not allow write access to your server's console while the installation or upgrade is in progress. C.
3. 228 In the Step 1: Verify Target Systems screen, HP SIM displays discovered and identified Integrity servers that run the OpenVMS operating system and verifies whether they are supported for provisioning. In the following example, one server is found and verified. Click Run Now. With use of vMedia, OpenVMS can be provisioned on one server at a time.
4. In the Step 2 provisioning screen, enter the MP access information (the default for the user name and password is Admin) for your Integrity server, as in the following example. The timeout value is the inactivity duration as observed from the provisioned server during an installation or upgrade. You can increase the default value; HP does not recommend decreasing the value. The default for vMedia provisioning is ten minutes. An asterisk (*) next to a field title indicates that a value is required.
5. In the Step 3 provisioning screen, enter the SCS node name and select from the Installation Disk list the disk on which you want to install OpenVMS, as shown in the following example. CAUTION: Make sure you select the correct disk. HP SIM provisioning automatically initializes the disk for an installation.
6. At this point, the boot process begins from vMedia. The installation is now in progress, as indicated in the following screen: C.
7. After about 90 minutes, the installation should complete, as indicated in the following screen: If the procedure does not complete successfully, the provisioning terminates. The reason for failure is displayed in the Progress column as well as on the console screen and in the log file HPSIM\logs\OPENVMS\ipaddress-date.log on the ProLiant server running HP SIM. NOTE: After an installation finishes, you must register all licenses for use of the operating system and any installed layered products.
to installation or upgrade purposes. You can access the virtual device while OpenVMS is running. For example, you can use vMedia to install and enable layered products. NOTE: DVDs are accessible by vMedia as read only. The vMedia device is the first in a series of virtual-disk capabilities included in the current generation of MP hardware.
NOTE: When using vMedia to install or upgrade OpenVMS, HP recommends using an image of the OpenVMS I64 OE DVD located on your Windows-based PC or server. This has two advantages: • If the DVD is defective or corrupted, the imaging software will fail when you attempt to create an image of it, thereby indicating the DVD's condition. • Installing or upgrading OpenVMS from the image file is much faster than installing from a DVD.
3. From a browser on a Windows-based PC or server in the same network as your Integrity server, access your Integrity server's iLO 2 MP by specifying the DNS name or IP address. Then log in as shown in the following example: 4. Select the Virtual Devices tab, then select Virtual Media from the list on the left. If your Integrity server is not a cell-based system, skip to the next step. If your server is a cell-based system, select the partition before launching the vMedia application, as shown: C.
5. Now launch the vMedia application by clicking Launch, as shown in the following example: 6. At this point, you might see popup security warnings, such as the one shown in Section C.1.4 (page 207). In this case, you can check the box to always trust content, and then click Yes. (To avoid certification warnings, install valid certificates for the iLO 2 MP hardware. For more information, see the HP Integrity iLO 2 MP Operations Guide. In addition, see the online help provided by your browser.
7. From the Virtual CD/DVD-ROM dialog box shown in the following example, make sure the Local Media Drive option is selected, and then click Create Disk Image: 8. The Create Disk Image dialog box appears, as in the following example. Specify a path or file name for the image to be created, and then click Create. NOTE: As noted previously, HP recommends that you do not install or upgrade directly from a DVD (on your local Windows-based management workstation) with vMedia.
9. The Virtual CD/DVD-ROM dialog box appears, as in the following example. Select the Local Image File option, and then browse for the created ISO image file that you want vMedia to access. Then click Connect. The following screen indicates that the image is connected to vMedia. Now the targeted Integrity server is ready to be booted using the ISO image file.
10. At this point, access the Integrity server's console from a browser or terminal emulator, log in to the MP, and enter the co command at the MP main menu: MP MAIN MENU: CO: VFP: CM: SMCLP: CL: SL: HE: X: Console Virtual Front Panel Command Menu Server Management Command Line Protocol Console Log Show Event Logs Main Help Menu Exit Connection [usb2mp] MP> co 11. At the EFI Shell prompt, enter the reconnect -r command to make sure all devices are discovered: Shell> reconnect -r 12.
13. Now you can boot the OpenVMS I64 image, either using the EFI boot menu or the following command at the EFI Shell prompt: Shell> fs0:\efi\boot\bootia64.efi As shown in the following example, the OpenVMS displays several messages followed by the operating system menu. You can now begin the installation or upgrade of OpenVMS on the Integrity server. NOTE: The %SYSTEM-I-MOUNTVER messages and the Universal Serial Bus Configuration Manager message are new to OpenVMS Version 8.
D Setting Up and Booting Fibre Channel Storage Devices This appendix describes how to set up and boot from a Fibre Channel (FC) Storage Area Network (SAN) storage device. You may prefer booting from an FC storage device because of its speed and because it can serve as a common cluster system disk in a SAN. FC storage is supported on all storage arrays that are supported on OpenVMS systems. For a list of supported devices, see the HP OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.
fs0:\efi\hp\tools\io_cards\fc2\efiutil> Fibre Channel Card Efi Utility n.nn info (11/1/2004) 2 Fibre Channel Adapters found: Adapter Path A0 Acpi(000222F0,200)/Pci(1|0) A1 Acpi(000222F0,200)/Pci(1|1) WWN Driver (Firmware) 50060B00001CF2DC n.nn (n.nn.nnn) 50060B00001CF2DE n.nn (n.nn.nnn) D.1.
NOTE: On certain entry-level servers, if no FC boot device is listed in the EFI boot menu, you might experience a delay in EFI initialization because the entire SAN is scanned. Depending on the size of the SAN, this delay might range from several seconds to several minutes. Cell-based systems (such as rx7620, rx8620, and the Superdome) are not affected by this delay.
7. The utility prompts you for a description to include with your boot option entry. By default, the device name is used as the description. You can enter more descriptive information. In the following example, the default is taken: Enter a short description (do not include quotation marks).
Figure D-1 Fibre Channel Host and SAN Storage Controller Configuration Integrity Server running OpenVMS FGA0 FGB0 FC SAN FC SAN 5000-1FE1-0011-B158 5000-1FE1-0011-B159 5000-1FE1-0011-B15C 5000-1FE1-0011-B15D EVA5000 Storage Controller System Disk For more information about this utility, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. Boot the FC system disk by selecting the appropriate boot option from the EFI Boot Manager menu and pressing Enter.
NOTE: The OpenVMS I64 Boot Manager utility requires the shared FC disk be mounted. If the shared FC disk is not mounted clusterwide, the utility tries to mount the disk with a /NOWRITE option. If the shared FC disk is already mounted clusterwide, user intervention is required. $$$ @SYS$MANAGER:BOOT_OPTIONS 5. 6. 246 Use the utility to add a new entry for the shared cluster system disk. Follow the instructions provided in Section D.1.3 (page 242). Boot the new system into the cluster.
E Backing Up and Restoring the System Disk This appendix describes how to perform backup and restore operations on the system disk. You perform these tasks by entering commands from a specialized backup environment. You access this environment through the menu that is displayed when you boot the OpenVMS I64 OE DVD, or through an alternative method that does not require theDVD. This specialized backup environment is required because it allows you to create an exact copy of the system disk.
on a disk. Therefore, to avoid jeopardizing the integrity of your data in any way, HP recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. E.4 Backing Up the System Disk The following sections describe how to back up the system disk. E.4.1 Getting Started Before you back up the system disk, do the following: 1.
$$$ BACKUP/IMAGE/VERIFY source-drive: target-drive: Example 1 In this example, the system disk and a target disk are mounted so the BACKUP command can create a backup disk. (You can use a backup disk as a system disk.) $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200 $$$ MOUNT/FOREIGN DKA300 $$$ BACKUP/IMAGE/VERIFY DKA200: DKA300: Example 2 In this example, the system disk and a target tape device are mounted so the BACKUP command can create a backup tape.
1) 2) 3) 4) 5) 6) 7) 8) 9) Upgrade, install or reconfigure OpenVMS I64 Version 8.3-1H1 Display layered products that this procedure can install Install or upgrade layered products Show installed products Reconfigure installed products Remove installed products Find, Install, or Undo patches; Show or Delete recovery data Execute DCL commands and procedures Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 8 4. 5.
E.6 Alternative Backup and Restore Procedure (Minimum OpenVMS Environment) This section describes an alternative method of performing backup and restore operations. This method is similar to creating a Standalone Backup directory on a disk, as supported by OpenVMS VAX systems and certain earlier versions of OpenVMS Alpha (using SYS$UPDATE.STABACKIT.COM).
5. As the procedure completes the installation, the display is similar to the following: HP I64VMS OPENVMS V8.3-1H1: OpenVMS and related products platform COPYRIGHT (c) 30-Aug-2007 Hewlett-Packard Development Company, L.P. Execution phase starting ... The following product will be installed: HP I64VMS VMS V8.3-1H1 Portion Done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100% The following product has been installed: HP I64VMS VMS V8.3-1H1 . . . The installation of minimum OpenVMS I64 is now complete.
NOTE: HP recommends that you do not install any other licenses, including OpenVMS licenses, on this alternate system. You can use the system only from the console. 4. 5. 6. 7. Mount the system disk and any output devices you plan to use during the backup or restore operations. See Section E.5.2 (page 250) for more information. Perform the necessary backup or restore operations by entering the appropriate BACKUP commands. For examples of using the BACKUP command to back up the system disk, see Section E.4.
F Installing the OpenVMS Internationalization Data Kit The OpenVMS internationalization data kit (VMSI18N kit) provides locale data and iconv code converters for international software, utilities, and HP C international run-time routines. The HP C RTL provides capabilities to allow application developers to create international software. The HP C RTL obtains information about a language and a culture by reading this information from locale files. This kit contains all of the supported locale files.
$ 256 Installing the OpenVMS Internationalization Data Kit
G Preparing to Use OpenVMS Management Station This appendix explains how to prepare your OpenVMS system to run the OpenVMS Management Station server software and how to prepare your PC to run the OpenVMS Management Station client software. This appendix also includes other related information. OpenVMS Management Station is a powerful Microsoft Windows based management tool for system managers and others who perform management tasks on OpenVMS systems.
In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required. However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common system disk, you must coordinate the files on those disks.
G.1.2 Starting the Server on Other Nodes If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without rebooting, you need to start the software on those nodes. Use SYSMAN to start the server as follows: $ @SYS$STARTUP:TNT$STARTUP.COM Or you can log in to each node that shares the SYS$COMMON: directory and enter the following command: $ @SYS$STARTUP:TNT$STARTUP.
Command Parameter 1 Parameter 2 Description @TNT$STARTUP BOOT ALL Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station. @TNT$STARTUP BOOT PRINTERS Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station.
G.1.7.1 When Is the Database Updated? The database is updated: • As part of the OpenVMS Management Station installation. • When you specifically start TNT$UTILITY.COM. • At periodic intervals as a server background thread. Two logical names control how often this server thread runs: Logical Name Description TNT$PRINTER_RECON_INTERVAL How often the thread should run, in minutes, from when the server was last started on this node.
node from the database. That is, in the absence of a valid connection to that OpenVMS node, the information in the database is assumed to be correct. G.1.8 Keeping Your Storage Environment Up to Date The TNT$UTILITY.COM utility accepts parameters (UPDATE STORAGE) to update the storage database. However, the storage database is updated dynamically every time you use the OpenVMS Management Station client to perform a storage management operation. Therefore, you do not need to run TNT$UTILITY.
G.1.12 Determining and Reporting Problems If you encounter a problem while using OpenVMS Management Station, please report it to HP. Depending on the nature of the problem and the type of support contract you have, you can take one of the following actions: • If your software contract or warranty agreement entitles you to telephone support, call HP. • If the problem is related to OpenVMS Management Station documentation, use the Internet address listed in the preface of this manual to send us your comments.
Copy the client file to a temporary directory on the PC using either of the following procedures: • Create a file share to the OpenVMS system and copy the file. • Use FTP on the PC to copy the file from the OpenVMS system. G.2.6 Installation Directory The installation procedure allows you to select the installation directory and suggests \Program Files\OpenVMS Mgmt Station\ as the default. G.2.7 Installation Procedure Run the TNT032-D.EXE file from a temporary directory.
• VMSPRINT.FTS • VMSPRINT.GID • VMSSCOPE.FTS • VMSSCOPE.GID • VMSSTORE.FTS • VMSSTORE.GID • VMSACNT.FTS • VMSACNT.GID The OpenVMS Management Station Uninstall program does not delete these files. To complete the removal: 1. Delete these files. 2. Delete the OpenVMS Management Station directory. Note that the OpenVMS Management Station Uninstall program does not remove the MMC support files. G.
H Removing the OpenVMS Operating System This appendix explains how to remove the OpenVMS operating system from your disk. You can remove the OpenVMS operating system from your disk in the following ways: • If the disk contains a small number of user files, copy those user files elsewhere and then reinitialize the disk. • If the disk contains many user files, use the PRODUCT REMOVE command to remove an obsolete or extra copy of the OpenVMS operating system without removing any of the user files.
• — PAGEFILE.SYS — SWAPFILE.SYS In target-disk:[VMS$COMMON.SYSEXE]: — LMF$LICENSE.LDB — PCSI$FILE_SYSTEM.PCSI$DATABASE — PCSI$PROCESSOR.PCSI$DATABASE — PCSI$ROOT.PCSI$DATABASE — RIGHTSLIST.DAT — SYSUAF.DAT As you examine the preceding lists of files, you might want to archive, rather than delete, the following files: • IA64VMSSYS.PAR (OpenVMS I64 systems) • MODPARAMS.DAT • LMF$LICENSE.LDB • RIGHTSLIST.DAT • SYSUAF.
I Alternative Ways to Initialize the System Disk The usual way to create a new OpenVMS system disk is to install OpenVMS with the INITIALIZE option. When you do this, the installation process responds as follows: • On OpenVMS I64 systems only, a diagnostic partition is created. The diagnostic partition is visible only from the console; it corresponds to the contents of SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS on the system disk.
3. 4. 5. Exit DCL (log off), and then select option 1 (“Upgrade, install or reconfigure OpenVMS”) on the main menu. When you are asked whether to initialize or preserve the target disk, choose PRESERVE (the default). Continue with the installation. I.2 Removing the Diagnostic Partition File To remove the diagnostic partition on an OpenVMS I64 system disk and to recover the disk space occupied, delete the file SYS$MAINTENANCE:SYS$DIAGNOSTICS.SYS and then reset the boot block.
Glossary This glossary defines key terms in the context of an OpenVMS computing environment. Availability Manager A system management tool that enables the system manager to monitor one or more OpenVMS nodes on an extended LAN from an OpenVMS, Windows 2000, or Windows XP system. Availability Manager helps system managers and analysts target a specific node for analysis. The tool collects system and process data from multiple nodes simultaneously; it analyzes the data and displays the output.
CI Computer interconnect. A type of I/O subsystem. It links computers to each other and to HSx devices (for example, an HSJ or HSG). See also CI-only cluster, DSSI. CI-only cluster A computer system consisting of several computers attached to a computer interconnect (CI) through which it communicates with other computers in the cluster. These computers share a single file system. CI provides redundant paths. See also computer interconnect (CI), DSSI-only cluster.
DSSI-only cluster A computer system consisting of several computers attached to a Digital Storage System Interconnect (DSSI) through which it communicates with other computers in the cluster. These computers share a single file system. See also DSSI, CI-only cluster. EFI Extensible Firmware Interface. The interface between HP Integrity server operating system and system firmware enabling you to perform such tasks as configuring the firmware and controlling the booting environment.
HSx drive Any disk or tape drive connected to an HSx device (for example, an HSJ or HSG). A system disk on an HSx drive can be shared by several computers in an OpenVMS Cluster environment. Human Recognition Service Standard See HRS. Hyper-Threading Supported on systems that have dual-core processors, this feature provides the ability for processors to create a second virtual core that allows additional efficiencies of processing.
migration support In OpenVMS Clusters, migration support means that HP has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX, OpenVMS Alpha, or OpenVMS I64. Problem reports submitted against these configurations are answered by HP. However, in exceptional cases HP might request moving to a warranted configuration as part of the solution. Migration support helps customers move to warranted OpenVMS Cluster pairs.
Operating Environment See OE. Operating Environment DVD See OE DVD. operating system CD The CD containing the OpenVMS Alpha operating system and the installation and other procedures. See also operating system media, Operating Environment DVD. operating system media The operating system CD or the OE DVD included with your OpenVMS distribution kit. See also operating system CD, OE DVD.
Secure Sockets Layer See SSL. server blades Thin, modular, self-contained computer servers containing one or more microprocessors and memory. Server blades are designed for high density and eliminate the need for many components such as power cords and network cables that are present in traditional rack-mount systems. HP server blades support technologies such as hot-plug hard-drives, multiple I/O cards, multi-function network interconnects and Integrated Lights Out.
TiCAP Temporary Instant Capacity. Supported on cell-based Integrity servers, an HP product option included with Instant Capacity (iCAP) that enables you to purchase prepaid processor activation rights for a specified (temporary) period of time. Temporary capacity is available in licenses of 30 core-days (or 720 core-hours), which can be spread across all Instant Capacity cores as required. The minimum activation time for any core is 30 minutes. TiCAP was formerly referred to as TiCOD. See also iCAP, PPU.
WBEM Web-Based Enterprise Management. A collection of management and Internet standard technologies that aid and unify management of large-scale distributed computing environments. WBEM provides the ability for the industry to deliver a well-integrated set of standard-based management tools, facilitating the exchange of data across otherwise disparate technologies and platforms. See also WBEM Providers for OpenVMS, WBEM Services for OpenVMS.
Index A Accounts creating after installation or upgrade, 143 ACPI configuration, 165 Advanced Encryption Standard (AES), 273 AGEN$INCLUDE files returning to system disk, 82 AGEN$PARAMS.
C CDSA defined, 271 initializing, 123 installing, 64 installing or upgrading, 33 upgrading, 105 Cell defined, 271 Cell boot phase, 173 Cell-based servers, 152 (see also nPartition) booting, 173 defined, 271 EFI, 162 terminology, 27 utilities, 152 Checklist installation, 49 postinstallation and postupgrade, 113 preinstallation for OpenVMS Cluster, 45 preupgrade, 77 preupgrade for OpenVMS Cluster, 87 upgrade, 95 CI-only OpenVMS Cluster defined, 272 Cluster (see OpenVMS Cluster) Cluster size (disk volume), 249
E EFI (Extensible Firmware Interface), 26 adding boot options, 165 boot path settings storing and restoring, 169 changing boot option timeout, 169 defined, 273 description, 149 displaying boot options, 168, 169 on nPartition, 162 using, 161–164 EFI Boot Manager, 150 (see also OpenVMS I64 Boot Manager (BOOT_OPTIONS.
saving or restoring state of, 169 I iCAP (Instant Capacity) and removal of the operating system from system disk, 267 and system disk initialization, 34 configuring, 132 defined, 274 requirements, 33, 66, 106 iLO (Integrated Lights Out), 26, 149 InfoServer booting, 199 client configuration, 191 defined, 25, 274 for provisioning setting up, 205 LAN devices supported, 191 losing connection, 201 software application boot server configuration, 196 booting OpenVMS, 199 configuration, 189–202 server configuratio
L LAN devices InfoServer support, 191 Layered products defined, 274 installing after OpenVMS installation or upgrade, 141 alternative procedure, 142 during OpenVMS installation, 64, 67 during OpenVMS upgrade, 112 installing or upgrading independently of system, 36, 141 reconfiguring, 39 registering, 36 Secure Delivery, 36, 52, 66, 107, 141 system upgrade effect on, 79 LIBDECOMP.
DVD defined, 275 for OpenVMS defined, 275 licensing, 64 options, 67, 79 On-Disk Structure Level specifying, 56 OPCCRASH.
shutting down the system, 42 upgrading OpenVMS, 33–34, 97–112 using, 32–43 Output saving from installation, 28 P Page file checking size, 146 modifying size, 144 PAK (Product Authorization Key) registering after an installation or upgrade, 116 registering during installation, 63 Partition defined, 276 Partition Manager, 27, 152 Password forgotten, 76, 183 minimum length, 58 setting during installation, 58 Patches finding, installing, removing using distribution media menu option, 41 installing from downloa
page file size, 144 patches, 139 PPU configuration, 132 print queues, 143 queue manager and default queues, 120 shadow sets license required, 116 shadow sets reformation, 144 shadow sets, forming, 118 SSL configuration, 126 swap file size, 144 SYSTARTUP_VMS.
S SAN disk, 245 SAN storage device delay in EFI initialization, 51, 96, 175, 243 graphic, 245 Satellite booting, 192 Satellite node defined, 276 Save sets transferring to system disk, 55 Scratch disk defined, 276 SCSSYSTEMID system parameter specifying, 59 Secure Delivery and distribution kits, 36, 52, 66, 107, 141 and installing patches, 139 defined, 276 Selecting active console devices, 160 Server complex defined, 277 SET BOOT command, 170 SETBOOTBLOCK command, 170 Shadow sets, 84 (see also Volume shadowi
adding system files, 136 analyzing and repairing, 80 backing up, 247–253 after an installation, 143 after installation or upgrade, 115 alternate disk for, 251 before an upgrade, 85 from OpenVMS main menu, 32 boot options, 165 booting, 72, 178 after installation, 76 checking amount of free space on, 138 creating, 55 defined, 25, 277 initializing, 55, 98 alternative methods, 34, 269 preparing an alternate for backup, 251 preparing for upgrade, 79 preserving, 34, 55, 98 removing system files, 136 restoring, 24
User Environment Test Package (see UETP) upgrading, 105 V VC, 27 VGA graphics as console device, 153, 160 Virtual Connect (see VC) Virtual media (see vMedia (Virtual Media)) Virtual partition defined, 278 vMedia (Virtual Media), 203 defined, 278 for provisioning setting up, 207 using independently of HP SIM, 232 vms_bcfg command, 168, 169 vms_show command, 169 VMSI18N, 255 VMSINSTAL utility, 141 installing layered products independently, 142 Volume label OpenVMS I64 OE DVD, 29 requirement for OpenVMS Clus
