user manual

ManualsBrandsHP (Hewlett-Packard) ManualsServerBA322 90087

HP OpenVMS Version 8.4 Upgrade and

Installation Manual

HP Part Number: BA322-90087

Published: June 2010

Summary of content (346 pages)

PAGE 1
HP OpenVMS Version 8.
PAGE 2
© Copyright 2010 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.
PAGE 3
Table of Contents Preface..............................................................................................................................15 About this document............................................................................................................................15 Intended Audience................................................................................................................................15 When to Use This Manual.........................................
PAGE 4
2.4 Required OpenVMS Cluster Information.......................................................................................43 2.5 Dismounting the Target System Disk Elsewhere in the Cluster.....................................................43 2.6 Beginning the Installation...............................................................................................................44 3 Installing the OpenVMS Operating System..............................................................45 3.
PAGE 5
4.7.1 Checking the Directory Structure and Preserving Your Security Protections........................87 4.7.2 Checking the SYSCOMMON Directories................................................................................87 4.7.3 Purging Duplicate Files from the System Disk.......................................................................88 4.7.4 Examining the System Disk....................................................................................................88 4.7.
PAGE 6
.3.10 Setting OpenVMS Cluster Membership Information..........................................................114 6.3.11 Setting OpenVMS Galaxy Information (Alpha Only).........................................................115 6.3.12 Updating Time Zone Information.......................................................................................115 6.3.13 Upgrading Windowing, Networking, and Related Products.............................................115 6.4 Completing the Upgrade...................
PAGE 7
.13 Expanding the System Libraries (Optional; OpenVMS Alpha Only) Compressing the System Libraries (Optional, OpenVMS Integrity servers: Not Recommended).............................................153 7.14 Installing Patches (Optional but Recommended)........................................................................157 7.15 Installing and Configuring Layered Products (New Installations, Some Upgrades).................159 7.15.1 Alternative Procedure...................................................
PAGE 8
B Configuring OpenVMS Integrity servers Hardware Operation and Boot Operations, and Booting and Shutting Down Your System......................................187 B.1 Configuration and Management Utilities for HP Integrity servers .............................................187 B.1.1 Overview of Utilities and Console Options..........................................................................188 B.1.2 Configuration and Management Utilities on Cell-Based Servers.........................................
PAGE 9
C Setting Up and Performing Network Booting.........................................................227 C.1 About the OpenVMS InfoServer Utility.......................................................................................227 C.2 Setting Up Your System as an InfoServer Client..........................................................................229 C.2.1 Determining the Local Network I/O Card to Be Used ........................................................229 C.2.
PAGE 10
F.4.4 Changing the Disk Volume Cluster Size...............................................................................303 F.4.5 Logging Out, Shutting Down, and Rebooting......................................................................303 F.5 Restoring the System Disk.............................................................................................................303 F.5.1 Getting Started......................................................................................................
PAGE 11
Glossary.........................................................................................................................325 Index...............................................................................................................................
PAGE 12
List of Figures E-1 12 Fibre Channel Host and SAN Storage Controller Configuration...............................................
PAGE 13
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 7-2 A-1 A-2 A-3 B-1 B-2 B-3 C-1 C-2 Definitions of Terms......................................................................................................................21 Getting OpenVMS Started on Integrity servers............................................................................24 Preinstallation Checklist................................................................................................................
PAGE 14
List of Examples 3-1 C-1 C-2 C-3 C-4 E-1 E-2 E-3 E-4 14 Component Options and Suboptions............................................................................................71 Setting Up the Boot Server and Client (for Version 8.3-1H1 and Lower)...................................238 Setting Up the Boot Server and Client (for Version 8.4)..............................................................238 DHCP Message......................................................................................
PAGE 15
Preface About this document This document explains how to install, or upgrade to, Version 8.4 of the HP OpenVMS Alpha or OpenVMS for Integrity servers 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.
PAGE 16
Server Blade products). HP iLO management processors make it simpler, faster and less costly to manage your Integrity servers remotely. The iLO Advanced KVM Card on the Integrity servers combines a physical graphics/USB card with additional logic to permit the Lights Out Advanced features of Virtual Media and Integrated Remote Console. Licenses to use iLO/vKVM are provided with the Server Blade products. For other server products, licenses might have to be purchased separately.
PAGE 17
Typographical Conventions The following conventions are used in this manual: Convention Meaning Ctrl/X A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. PF1X A sequence such as PF1X indicates that you must first press and release the key labeled PF1 and then press and release another key (x) or a pointing device button. Enter In examples, a key name in bold indicates that you press that key.
PAGE 18
an earlier OpenVMS version documentation set. They have not been revised, they remain valid for OpenVMS Version 8.4. • • • • • • • • • • Cover Letter for HP OpenVMS Version 8.4 and any other cover letters included with your kit. HP OpenVMS Version 8.4 New Features and Documentation Overview, which describes enhancements and new features included in this release of the OpenVMS Integrity servers operating system and provides an overview of the documentation that supports OpenVMS.
PAGE 19
http://h71000.www7.hp.com/openvms/integrity/integrity_gwm.html • The hardware manuals that are supplied with your Alpha or Integrity servers computer. These manuals provide detailed information about your system hardware, including the operation of the system unit, the drives, and the monitor.
PAGE 20
HP Encourages Your Comments HP welcomes your comments on this manual. Please send comments to the following email address: openvmsdoc@hp.com How to Order Additional Documentation For more information about how to order additional documentation, see the OpenVMS documentation website: http://www.hp.
PAGE 21
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 Integrity servers' 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.
PAGE 22
Table 1-1 Definitions of Terms (continued) Term Definition Virtual KVM (vKVM) Virtual keyboard, video, and mouse feature included with Integrated Lights Out (iLO) 2 Management Processor (MP) on Integrity servers (rx2660, rx3600, and rx6600 Integrity servers and the BL860c and BL870c Server Blade products). The feature allows you to connect a virtual serial line from your PC to Integrity servers, enabling your PC, keyboard, and mouse to function as if directly connected to the server.
PAGE 23
user interface and the functionality provided by vKVM and vMedia. MP and Integrity iLO provide a service interface that allows access to all hardware and, in a complex, all nPartitions. The MP is always available, even when the main power source is turned off (MP can operate on standby power). On cell-based servers (such as rx7620, rx8620, and Superdome), MP is available whether or not nPartitions are configured or booted in the server complex.
PAGE 24
All processors (cores) and memory are contained in cells, each of which can be assigned for exclusive use by an nPartition. An nPartition defines a subset of the server hardware resources that is used as an independent system environment. An nPartition has its own EFI system boot interface and each nPartition boots and reboots independently.
PAGE 25
1.3 Examining Hardware and Software Components Before you begin an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections. 1.3.1 Hardware Components For hardware components, verify the following:: • Be sure the hardware is installed and verified for proper operation. For detailed information, see the hardware manuals you received with your computer.
PAGE 26
The DVD label is the printed label on the OE DVD. The volume label is the machine-readable name that the OpenVMS Integrity servers operating system uses to access and identify the DVD. 1.3.5 Firmware on Alpha Systems OpenVMS Alpha performs a firmware check each time the system is booted. When you boot the OpenVMS Alpha operating system CD, the system automatically checks the version of console firmware that is running on your computer. The system also provides information about how to update the firmware.
PAGE 27
1.3.6.1 Checking Firmware Version To determine the firmware version in place on your Integrity servers, you can use the Extensible Firmware Interface (EFI) info fw command at the EFI Shell prompt, as in the following example. (For cell-based servers, check the firmware at the nPartition console.) Shell> info fw You can also use the EFI Boot Manager to obtain firmware information. With MP, you can use the MP sysrev command.
PAGE 28
3. (zip-compressed) file to your system. (To access the release notes, see step 5 in the preceding section.) Unzip the firmware file into the corresponding .ISO file. The .ISO file is a block copy of the firmware disk for the Integrity servers system. On OpenVMS systems, you can obtain the INFO-ZIP utility from an OpenVMS Freeware CD and use the UnZip utility provided with INFO-ZIP.
PAGE 29
• When the source drive is a virtual DVD drive served by the InfoServer, the device name is typically the following: DAD1: • On OpenVMS systems configured in certain OpenVMS Cluster or HSx environments, the device naming convention is similar to the following: DUA20.14.0.2.0 The values you specify identify components such as the boot device, controller, unit number of the boot device, HSx controller node number, and channel numbers.
PAGE 30
8) Execute DCL commands and procedures 9) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) Review the following sections to understand how the menu works. Then you can choose appropriate menu options when you are asked to do so before, during, and after an installation or upgrade. 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.
PAGE 31
which any other operating system is installed. This includes implementations of OpenVMS for other architectures. Do you want to INITIALIZE or to PRESERVE? [PRESERVE] 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.
PAGE 32
NOTE: You cannot install OpenVMS on a disk where another operating system is installed. For example, you cannot take a UNIX disk, select the PRESERVE option, and then install OpenVMS on the disk. The UNIX disk is not structured in the format that OpenVMS requires. If you intend to choose the PRESERVE option (because there are certain files on the disk that you want to retain), HP recommends that you first make a backup copy of your system disk.
PAGE 33
HP HP HP HP HP HP HP I64VMS I64VMS I64VMS I64VMS I64VMS I64VMS I64VMS HPBINARYCHECKER version V1.0 WBEMCIM version V2.91-A070728 WBEMPROVIDERS version V2.0-31 DWMOTIF version V1.7 DECNET_PLUS version V8.4 DECNET_PHASE_IV version V8.4 TCPIP version V5.7 The following Layered Product kits are available on the OpenVMS Distribution media (CD/DVD). They can be installed by selecting option 3. If they are already installed, they can be reconfigured by selecting option 5, or removed by selecting option 6.
PAGE 34
8.3 or later, signed kits that you install subsequently are validated, including any signed kits included on the distribution media.) The DCL command PRODUCT SHOW HISTORY displays the validation status of these kits as unsigned rather than as a validated kit. As shown in the following example, you are also prompted for a target disk and asked whether you want brief or detailed descriptions. The procedure presents a list of products and allows you to select any or all of these products.
PAGE 35
The install 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 14 ? E - HP I64VMS AVAIL_MAN_BASE V8.4 HP I64VMS CDSA V2.3-306 HP I64VMS DECNET_PHASE_IV V8.4 HP I64VMS DECNET_PLUS V8.4 HP I64VMS DWMOTIF V1.7 HP I64VMS DWMOTIF_SUPPORT V8.4 HP I64VMS HPBINARYCHECKER V1.0 HP I64VMS KERBEROS V3.1-152 HP I64VMS SSL V1.4-284 HP I64VMS TCPIP V5.
PAGE 36
------------------------------------HP I64VMS AVAIL_MAN_BASE V8.4 HP I64VMS CDSA V2.3-306 HP I64VMS DECNET_PLUS V8.4 HP I64VMS DWMOTIF V1.7 HP I64VMS DWMOTIF_SUPPORT V8.4 HP I64VMS HPBINARYCHECKER V1.0 HP I64VMS KERBEROS V3.1-152 HP I64VMS OPENVMS V8.4 HP I64VMS TCPIP V5.7 HP I64VMS VMS V8.4 HP I64VMS SSL V1.4-284 HP I64VMS TDC_RT V2.3-1 HP I64VMS WBEMCIM V2.91-A070728 HP I64VMS WBEMPROVIDERS V2.
PAGE 37
• • • The product is available for installation while your system is booted from the operating system media. For information about displaying products that are available for installation, see Section 1.4.2 (page 32) (option 2 on the main menu). The product is installed. For information about displaying installed products, see Section 1.4.4 (page 35) (option 4 on the main menu). The version of the product that is available for installation is the same as the version of the product that is installed.
PAGE 38
1.4.6 Using the Remove Installed Products Option (6) Option 6 allows you to remove products that were installed or registered with the PCSI utility. (This option removes complete products. To remove patches, use option 7, as described in Section 1.4.7 (page 39).) IMPORTANT: Do not remove the following system-integrated products (SIPs): Availability Manager, CDSA, HPBinarychecker, Kerberos, SSL, TDC_RT, WBEM Services for OpenVMS (WBEMCIM), and WBEM Providers for OpenVMS.
PAGE 39
Choose one or more items from the menu separated by commas: 1.4.7 Using the Patches and Recovery Data Option (7) Select option 7 to install or undo patches and to perform related operations.
PAGE 40
Enter additional location, D, or just press Return: After you provide the necessary information, a PCSI /PRODUCT command automatically performs the operation you requested. If you chose options 1, 2, or 4 from the submenu, the PCSI utility prompts you for additional input and displays additional information. 1.4.
PAGE 41
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 45) for information about installing your system. 2.1 Preinstallation Tasks Use the checklist in Table 2-1 to ensure that you perform all necessary tasks prior to installing your system in an OpenVMS Cluster environment.
PAGE 42
Warranted support combinations with OpenVMS Integrity servers Version 8.4 and OpenVMS Alpha Version 8.4 are shown in Table 2-2. Table 2-2 Warranted Cluster Support with OpenVMS Version 8.4 Operating system Warranted in combination with OpenVMS Alpha Version 8.4 OpenVMS Integrity servers Version 8.4 OpenVMS Integrity servers Version 8.4 OpenVMS Integrity servers Version 8.4 OpenVMS Alpha Version 8.4 Additional warranted combinations are included in the following list.
PAGE 43
2.
PAGE 44
remain so during the installation. For instructions on dismounting cluster disks, see Section 5.5.2.3 (page 99). 2.6 Beginning the Installation After you have completed all the tasks in this chapter, go to Chapter 3 (page 45) to begin the installation.
PAGE 45
3 Installing the OpenVMS Operating System This chapter explains how to install the OpenVMS Alpha and Integrity servers operating systems. 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.
PAGE 46
3.2.1 Booting the OpenVMS Alpha CD This section explains how to boot the OpenVMS Alpha operating system CD, either from your local CD drive, as described in Section 3.2.1.2 (page 46), or from a CD drive served by the InfoServer, as described in Section 3.2.1.3 (page 46). First, you need to identify the name of the CD drive, as explained in Section 3.2.1.1 (page 46). For more information about booting operations, see Section A.1 (page 167). 3.2.1.
PAGE 47
NOTE: If you are using a DEC 3000 or 4000 series system, note the following: • On DEC 3000 series systems, you can boot through the InfoServer using an alternate TURBOchannel device, such as a PMAD (Ethernet) or DEFTA (FDDI), by specifying the device name as “n/ESA0”. The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8 (page 175).
PAGE 48
NOTE: If you boot the OpenVMS Alpha operating system CD from an InfoServer but lose your connection during the installation procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following: IF ... THEN ... You previously chose the 1. Boot the OpenVMS Alpha operating system CD again from the network. INITIALIZE option 2. Choose the install option (1) on the menu and perform the installation again, as described in this chapter. You previously chose the 1.
PAGE 49
For information about other required and optional tasks to be performed before or after booting the system, see Appendix B (page 187). CAUTION: To boot your OpenVMS Integrity servers operating system on a cell-based server (Superdome servers, or midrange servers such as rx8620 and rx7620), note that the ACPI configuration must be set correctly. For more information, see Section B.5.1 (page 204). 3.2.2.
PAGE 50
NOTE: When booting OpenVMS from the installation DVD for the first time on any OpenVMS Integrity servers 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. 3.2.2.
PAGE 51
1. 2. Obtain installation materials and necessary site-specific information Guest operating system's networking information, such as: • Host name for each guest • IP Address for each guest (if fixed) • Subnet Mask • IP address of one or more DNS servers and the gateway machine • DECnet address for each guest 3. 4. 5.
PAGE 52
• • • • • 2 CPUs 2 GB memory AVIO LAN virtual switch with the name myswitch AVIO disk with backing store as /fdev/frackA/disk1 AVIO DVD with backing store as /dev/rdisk/disk7 (for DVD) or AVIO disk with backing store as /fev/frackA/OpenVMS.iso (for ISO file) NOTE: Specify the operating system type as OpenVMS. If a physical disk is used as a backing store, the disk can be defined to assume disk4 as the path to the physical disk.
PAGE 53
Loading.: EFI Shell [Built-in] EFI Shell version 1.10 [14.
PAGE 54
• Output from the installation procedure is nearly identical for both Alpha and Integrity servers except, of course, the operating system names as well as names of products included with the installation.
PAGE 55
During the installation, the procedure prompts you for the following information: • • • • • • The name of the target drive, and the 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 30)). A volume label for the target disk (if you choose not to use the default volume label). A password for the SYSTEM account.
PAGE 56
. . **************************************************************** You can install or upgrade the OpenVMS I64 operating system or you can install or upgrade layered products that are included 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.
PAGE 57
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. PRESERVE -- Installs or upgrades OpenVMS I64 on the target disk and retains all other contents of the target disk.
PAGE 58
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.
PAGE 59
if you do not need the new features of ODS-5 disks, including the support of applications ported from other operating systems (such as UNIX, Linux, and MS Windows). • ODS-5 — ODS-5 supports file names that are longer, have a wider range of legal characters, and allow for mixed-case file names. This feature permits use of file names similar to those in a Microsoft Windows or UNIX environment. — ODS-5 supports hard links to files, access dates, and files whose names differ only by case.
PAGE 60
Is this OK? (Yes/No) YES Initializing and mounting target.... %EFI-I-VOLINIT, FAT volume DIAGNOSTICS has been initialized Creating page and swap files.... 8. Configure and Validate Boot Options (Integrity servers only): On OpenVMS Integrity servers installations, the procedure next asks whether you want to create or validate boot options. Boot options in the EFI Boot Manager boot option menu can provide a convenient way to boot your system.
PAGE 61
• • • Z). The system converts all characters to uppercase, so the case of characters you enter does not matter. Press Enter after you enter the password. (The password does not display as you type it.) After you enter the password, the procedure checks to make sure it meets the requirements for a valid password. Reenter the password for verification. The following is a sample display: You must enter a password for the SYSTEM account.
PAGE 62
DECnet Phase IV for OpenVMS or DECnet-Plus for OpenVMS with DECnet Phase IV addresses, then SCSNODE must be the same as your DECnet node name. The following is an example of the display and a valid response: For your system to operate properly, you must set two parameters: SCSNODE and SCSSYSTEMID. SCSNODE can be from 1 to 6 letters or numbers. It must contain at least one letter. If you plan to use DECnet, SCSNODE must be the DECnet Phase IV node name, or the DECnet-Plus (Phase V) node synonym.
PAGE 63
OpenVMS systems, the SCSSYSTEMID on each system must be unique. Enter SCSYSTEMID [65535]: 12345 3.
PAGE 64
14. 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.
PAGE 65
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.
PAGE 66
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.
PAGE 67
The OpenVMS Alpha operating system uses one or more of several types of licenses, as described in the HP OpenVMS Version 8.4 for Alpha and Integrity Servers Software Product Description (SPD 82.35.xx) . For more information about licensing terms and policies, contact your local HP sales office, or see the HP software licensing information at the following location: http://h18000.www1.hp.com/products/software/info/terms/swl_sld.
PAGE 68
o HP TCP/IP Services for OpenVMS If you want to change your selections, you can do so later in the installation by answering "NO" to the following question: "Do you want the defaults for all options?" Do you want to install DECwindows Motif for OpenVMS I64 V1.7? (Yes/No) [Yes] Y If you want to install the OpenVMS graphical user interface and you have the hardware that supports it and the license to use it, answer YES; otherwise, answer NO.
PAGE 69
NOTE: For support of Instant Capacity (iCAP) (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 Integrity servers, TCP/IP Services for OpenVMS is installed automatically. 18. Choose Descriptive Help Text (Optional): After you respond to the prompt for TCP/IP Services for OpenVMS, the final stages of the installation proceed.
PAGE 70
COPYRIGHT ... Hewlett-Packard Development Company, L.P. Do you want the defaults for all options? [YES] When selecting options, note the following: • If you want all the default values, press Enter. If you want to select options individually, answer NO. The procedure then prompts you for each option and suboption shown in Example 3-1 (page 71). • • • • • • Review the list of options and compare them with the requirements for your system.
PAGE 71
....There are post-installation tasks you must complete. WBEM Providers for OpenVMS (WBEMPROVIDERS) HP I64VMS DWMOTIF V1.7: DECwindows Motif If a Language Variant is installed, refer to the Installation Guide. 20. Finish Installation onto System Disk – Review and Confirm Options: When you have answered all the prompts and selected the options you want installed, the procedure displays information about the products you have selected.
PAGE 72
Are you satisfied with these options? [YES] If you answer NO to this question, you are allowed to selectively configure options and suboptions, even if you did not do so previously. When you finish, you are asked again whether you are satisfied with the options you selected. When you answer YES to indicate you are satisfied with the selections, the installation begins installing OpenVMS onto the target disk.
PAGE 73
to be performed. The version numbers in this example do not necessarily reflect the version numbers of the products actually shipped with OpenVMS Version 8.4. The following HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS HP I64VMS products have been installed: AVAIL_MAN_BASE V8.4 Layered Product CDSA V2.3-306 Layered Product DECNET_PLUS V8.4 Layered Product DWMOTIF V1.7 Layered Product DWMOTIF_SUPPORT V8.
PAGE 74
22. Installation Creates and Validates Boot Options (Integrity servers only): At this point in an OpenVMS Integrity servers installation, the procedure creates and validates boot options if you chose to have the procedure do so (see step 8). • If you answered NO in step 8, the following message is displayed: If there is an existing boot option that was used to boot this system disk, you may be able to use it.
PAGE 75
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.
PAGE 76
24. 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.15 (page 159).
PAGE 77
When the system starts booting, the initial informational messages displayed are similar to the following: OpenVMS (TM) Alpha Operating System, Version 8.4 Installing required known files... Configuring devices... (c) Copyright 1976-2006 Hewlett-Packard Development Company, L.P. 3.5.2 Booting the OpenVMS Integrity servers System Disk The following steps explain how to boot your new OpenVMS Integrity servers system disk. For more information about this and special booting operations, see Section B.
PAGE 78
corresponding EFI device depends on what partitions are configured on the target disk. blk 3. The blk devices are block devices. Multiple blk devices exist for each volume that has a bootable partition or diagnostic partition. These devices may include the DVD device as well as the diagnostic partitions on OpenVMS system disks. Diagnostic partitions are intended and reserved for use by HP Services. (For more information about this partition, see Appendix J (page 323).
PAGE 79
For more information about cluster configuration, see the HP OpenVMS Cluster Systems manual or the Guidelines for OpenVMS Cluster Configurations manual. If you answered YES to the question about joining an OpenVMS Cluster, the system now prompts you for information about your configuration. Table 3-2 lists the OpenVMS Cluster prompts and suggested responses. These prompts appear if you answered YES to the question about joining an OpenVMS Cluster or if you manually run SYS$MANAGER:CLUSTER_CONFIG.
PAGE 80
1 2 The Ethernet might not be required for communication within a local area OpenVMS Cluster system configured with FDDI devices. Within certain Digital Storage Systems Interconnect (DSSI) or computer interconnect (CI) mixed-interconnect configurations, neither the Ethernet nor FDDI are required for communication. If your configuration fits either scenario, you can answer NO (N) to this question. Cluster group number and password are required by any cluster nodes that use the local area network.
PAGE 81
SHUTDOWN -- Perform an Orderly System Shutdown on node I64CSI %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... %SHUTDOWN-I-CHECKOK, basic reboot consistency check completed . . . After installation, the OpenVMS Alpha system is automatically restarted. If the Alpha system does not reboot automatically, you must manually do so.
PAGE 82
3. At this point, you can create a DECterm session or initiate other management functions. For information about creating a DECterm session, see the DECwindows Motif for OpenVMS Applications Guide. 3.10 Postinstallation Tasks After you have successfully installed the OpenVMS operating system and logged in to the SYSTEM account, you must perform certain postinstallation tasks before you can use the system. For complete information, see Chapter 7 (page 125).
PAGE 83
4 Before Upgrading the OpenVMS Operating System This chapter describes which tasks you should perform prior to beginning an upgrade. Section 4.1 (page 83) 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.
PAGE 84
• • HP OpenVMS System Management Utilities Reference Manual, for information about using system management utilities such as SYSMAN and ANALYZE/DISK_STRUCTURE HP OpenVMS Guide to System Security, for information about reestablishing your security environment after the upgrade 4.3 Notes, Cautions, and Restrictions This section provides important information that can affect the success of your upgrade. Review the cautions, restrictions, and notes carefully before you begin the upgrade. 4.3.
PAGE 85
NOTE: When you initially purchase the OpenVMS software and license, HP provides a Product Authorization Key (PAK) that is required to enable the License Management Facility (LMF) to register the license and to validate and authorize subsequent use of the product. A PAK does not provide license or new version rights. For more information about licensing and the License Management Facility, see the HP OpenVMS License Management Utility Manual.
PAGE 86
Before you shut down the operating system that you plan to upgrade, follow these steps to remove DECram for OpenVMS (if you have already shut down your operating system, you must reboot before continuing). IMPORTANT: 1. Perform these steps only on versions of OpenVMS Alpha prior to 8.2.
PAGE 87
1. Check for a POLYCENTER software installation (PCSI) utility TDC V2.0 installation by logging on to a privileged account and entering the following command: $ PRODUCT SHOW PRODUCT TDC If the resulting display shows that TDC is not found on the system, no action is required; if TDC is found, proceed to step 2. 2. If the SHOW PRODUCT display shows that TDC V2.0 is installed, enter the following command to remove the product: $ PRODUCT REMOVE TDC 4.
PAGE 88
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.DIR $ DIRECTORY/FILE_ID/NOHEADING/NOTRAILING DKA100:[SYS*]SYSCOMMON.DIR Output from the first command should list a single file.
PAGE 89
to alert you and allows you to terminate the upgrade so you can create more disk space and try the upgrade again. NOTE: If the files on your system disk are badly fragmented, you might not be able to complete an upgrade, even when the amount of disk space appears to be sufficient. HP recommends that you back up and restore the system disk prior to upgrading. Restoring the system disk from an image backup defragments the disk.
PAGE 90
Table 4-2 Logical Names for Relocated Authorization Files (continued) Logical Name Location and File Name NETOBJECT SYS$SYSTEM:NETOBJECT.DAT NETPROXY SYS$SYSTEM:NETPROXY.DAT NET$PROXY SYS$SYSTEM:NET$PROXY.DAT RIGHTSLIST SYS$SYSTEM:RIGHTSLIST.DAT SYSUAF SYS$SYSTEM:SYSUAF.DAT SYSUAFALT SYS$SYSTEM:SYSUAFALT.DAT SYSALF SYS$SYSTEM:SYSALF.DAT VMSMAIL_PROFILE SYS$SYSTEM:VMSMAIL_PROFILE.DATA VMS$AUDIT_SERVER SYS$MANAGER:VMS$AUDIT_SERVER.DAT VMS$OBJECTS SYS$SYSTEM:VMS$OBJECTS.
PAGE 91
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.
PAGE 92
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.
PAGE 93
4.9.1 Setting the Boot Device Be sure your system is set to boot by default from the disk you intend to upgrade. For OpenVMS Alpha systems, use the SHOW BOOTDEF_DEV and SET BOOTDEF_DEV console commands to accomplish this task. (For more information, see Appendix A (page 167).) For OpenVMS Integrity server systems, HP recommends using the OpenVMS Integrity servers Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.
PAGE 94
2. 3. 4. Boot the operating system media, following the instructions for OpenVMS Integrity servers in Section B.6 (page 211), and for OpenVMS Alpha in Section A.1 (page 167). Use the menu system to enter the DCL environment (option 8). Mount the system device and the target device on which you will make the backup copy. (If you are backing up to tape, skip to the next step.) For example, if your system disk is on DKA0: and the target device is on DKA100:, you might use the following commands.
PAGE 95
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 103). 5.1 Preupgrade Tasks for OpenVMS Cluster Environments NOTE: Be sure you have performed the preupgrade tasks described in Chapter 4 (page 83) before you upgrade your OpenVMS Cluster system.
PAGE 96
request that you move to a warranted configuration as part of the solution. Migration support helps customers move to warranted OpenVMS Cluster pairs. Warranted support combinations with OpenVMS Integrity servers Version 8.4 and OpenVMS Alpha Version 8.4 are shown in Table 5-2. Table 5-2 Warranted Cluster Support with OpenVMS Version 8.4 Operating system Warranted in combination with OpenVMS Alpha Version 8.4 OpenVMS Integrity servers Version 8.4 OpenVMS Integrity servers Version 8.
PAGE 97
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.4 Release Notes. For information about supporting the Performance Data Collector base software (TDC_RT) in OpenVMS Clusters, see Section 7.9.9.5 (page 149). 5.4 Adding a New System to an OpenVMS Cluster To add a new OpenVMS Version 8.
PAGE 98
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 99).
PAGE 99
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 99).) NOTE: Any attempt to access the target system disk from the remaining OpenVMS Cluster members will corrupt the target disk. Even if the target system disk is mounted only by a remaining cluster member and no file access is performed, the target disk will probably be corrupted.
PAGE 100
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). After all satellite nodes have shut down, select the REMOVE_NODE option. If a proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure hangs the cluster.
PAGE 101
After the shutdown procedure is finished on all nodes, go to Chapter 6 (page 103) 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.
PAGE 102
PAGE 103
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 103) includes a checklist that you can use to make sure you perform all the upgrade tasks described in this chapter. 6.
PAGE 104
2. Enter the SHOW DEVICE command at the console prompt (>>>) and look for the correct drive listed in the output (for example, DKA400). If you are booting from the InfoServer, look for a device listed with its hardware address, as in the last line of the following example (EWA0): >>> SHOW DEVICE dva0.0.0.1000.0 dka200.2.0.5.0 dka300.3.0.5.0 dka400.4.0.5.0 ewa0.0.0.3.
PAGE 105
FUNCTION ID 1 2 3 4 5 - FUNCTION Display Menu Help Choose Service Select Options Stop Enter a function ID value: 3. Respond to the prompts as follows, pressing Enter after each entry: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name (ALPHA084 is the default service name for the InfoServer hardware; for the InfoServer utility, ask your system or network manager for the service name).
PAGE 106
6.2.2.1 Booting from the Local Drive To boot a local OpenVMS Integrity servers 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 servers 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.
PAGE 107
NOTE: When booting OpenVMS from the installation DVD for the first time on any OpenVMS Integrity servers 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.2.
PAGE 108
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1 6.3.2 Selecting 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.
PAGE 109
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.
PAGE 110
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.
PAGE 111
* * * * * If you continue, recovery data for the patches listed above will be deleted. The deletion of recovery data does not affect the installation status of patches applied to products that are not participating in this operation. However, continuing with this operation prevents you from uninstalling these patches at a future time by use of the PRODUCT UNDO PATCH command.
PAGE 112
NOTE: If your disk is initialized with ODS-5 with hard links not enabled. You can enable them after the upgrade by executing the following commands: $ SET VOLUME/VOLUME_CHARACTERISTICS=HARDLINKS SYS$SYSDEVICE $ ANALYZE DISK_STRUCTURE/REPAIR SYS$SYSDEVICE The target system disk is currently at On-Disk Structure Level 2 (ODS-2). It can be converted to On-Disk Structure Level 5 (ODS-5). OpenVMS I64 systems include WBEM Services for OpenVMS; the WBEM data repository requires an ODS-5 disk.
PAGE 113
If you choose to change to ODS-5, you are given the option to enable hard links. (For more information about hard links, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.) The upgrade then continues. Do you want to convert the target system disk to ODS-5? (Yes/No/?) YES DKB400: has been converted to ODS-5. You can use the BACKUP/CONVERT command to convert ODS-5 disks back to ODS-2 format. For more information, refer to the OpenVMS System Management Utilities Reference Manual.
PAGE 114
after the upgrade completes (for information about changing boot flags, see Section B.5.2 (page 205)). You can set VMS_FLAGS or accept the default, 0,0. Enter the value for VMS_FLAGS: (n,n) [0,0] If you do not want the procedure to assist you in setting up or validating boot options on the EFI console, answer NO. HP recommends that you allow the procedure to assist you in setting up and validating boot options.
PAGE 115
by the upgrade procedure. Note that you can run this procedure manually to configure or reconfigure your system as a member of an OpenVMS Cluster. For more information about configuring a member of an OpenVMS Cluster, see the Guidelines for OpenVMS Cluster Configurations manual. 6.3.11 Setting OpenVMS Galaxy Information (Alpha Only) The procedure next asks whether your system is an instance in an OpenVMS Galaxy.
PAGE 116
is installed on your system. It will be upgraded. KERBEROS for OpenVMS I64... is installed on your system. It will be upgraded. SSL for OpenVMS I64... is installed on your system. An upgrade is not required. Performance Data Collector (base) for OpenVMS I64... is installed on your system. It will be upgraded. HP Binary Checker for OpenVMS I64 DECwindows Motif for OpenVMS I64 V1.7 is installed on your system. An upgrade is not required. Beginning with OpenVMS V7.
PAGE 117
6.4.1 Selecting Descriptive Help Text The procedure next prompts you as follows: The installation 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] If you answer YES, the procedure displays additional explanatory text with each prompt. 6.4.2 Removing Older Versions of ENCRYPT Beginning with OpenVMS Version 8.3, Encryption for OpenVMS is included with the operating system.
PAGE 118
6.4.4 Saving Archived Files By default, the OpenVMS upgrade deletes files that were archived as filename.type_OLD by OpenVMS remedial kits. If you do not want to delete these files, you can save them by performing one of the following actions: • • When the script asks whether you want the defaults for all options, answer NO. (This script is shown in the example in Section 6.4.5 (page 118).) Step through the options and answer NO to the option for deleting files archived by remedial kits.
PAGE 119
• • plus any new components that were not in the previous version of the OpenVMS operating system. If you want to include or exclude any components differently than you did in the last installation or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing. If you want to review the current defaults first, answer NO. Then answer YES when the procedure asks whether you want to view the values.
PAGE 120
For a list of component options included with the OpenVMS Version 8.4 operating system, see Example 3-1 (page 71). 6.4.6 Component and Product Installation Confirmation Messages When you have answered all the prompts and selected the components you want installed, the procedure allows you to review your selections and make changes, and then displays information about the various components and products that were installed, as shown in the following sample display in which the review is not chosen.
PAGE 121
HP I64VMS OPENVMS V8.3 HP I64VMS VMS V8.3 Platform (product suite) Operating System HP I64VMS OPENVMS V8.4: OPENVMS and related products Platform HP I64VMS KERBEROS V3.1-152 Configure and set up Kerberos If Kerberos will be run on this system, but has not been used previously, you need to perform the following steps. o Run the Kerberos configuration procedure: @SYS$STARTUP:KRB$CONFIGURE.COM o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.
PAGE 122
The EFI Boot Manager menu includes multiple Boot Options for $1$DGA1200: Boot Options cannot be created or validated automatically. Please use the OpenVMS I64 Boot Manager to ensure that you have a valid boot option for the system you have just installed.
PAGE 123
1) 2) 3) 4) 5) 6) 7) 8) 9) Upgrade, install or reconfigure OpenVMS I64 Version 8.4 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/?) 6.4.
PAGE 124
PAGE 125
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 125) includes a checklist that you can use to make sure you perform all the postinstallation or postupgrade tasks necessary for your system. 7.
PAGE 126
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 127) 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.
PAGE 127
Table 7-1 Postinstallation and Postupgrade Checklist (continued) Task Section □ Initialize and run the Performance Data Collector base software (TDC_RT). Section 7.9.9 (page 147) □ Prepare your OpenVMS system and your PC to run OpenVMS Management Station, and follow procedures in Appendix H (page 311). Section 7.9.10 (page 150) □ Install OpenVMS Debugger clients on a PC. Section 7.9.11 (page 150) □ Create or edit a system-specific or clusterwide login welcome message Section 7.
PAGE 128
If your system disk will be part of a multiple-member shadow set, then a backup is not necessary. Either form or re-form the shadow set, as described in Section 7.7 (page 131); this creates a backup copy of the newly installed or upgraded system disk through the shadow copy operation. Remember to dismount any added shadow set members after the shadow copy has completed, complete any steps described in this chapter that you need to perform and, when you are finished, re-form the shadow set.
PAGE 129
If you have upgraded your operating system, register any new OpenVMS or layered product licenses. Note that licensing schemes differ between OpenVMS Alpha and Integrity server systems. For OpenVMS Integrity server systems, a single OE license grants the right to use all the components bundled in the purchased OE. Each OE is offered with Per Core Licenses (PCLs). For information about registering licenses, see the following documents: • • • HP OpenVMS License Management Utility Manual HP OpenVMS Version 8.
PAGE 130
shadowing, see the HP Volume Shadowing for OpenVMS manual. For more information about setting ALLOCLASS for clusters, see the HP OpenVMS Cluster Systems manual. 7.5 Tuning BAP System Parameters (Alpha Upgrade Only) OpenVMS Alpha Version 7.1 and later contains system parameters that control the operation of bus-addressable pool (BAP). The CIPCA, CIXCD, KFMSB, and Qlogic ISP 1020 (KZPSM-AA) adapters are some of the adapters that use bus-addressable pool to improve performance.
PAGE 131
IMPORTANT: If any BAP parameters are defined in MODPARAMS.DAT, HP strongly recommends removing them. Their presence in MODPARAMS.DAT could be the source of the current boot problem or might be a source of one in the future if a change is made to the adapter card configuration in the system. If you make changes to adapters in the future and the system boots successfully, immediately run AUTOGEN, by entering the following command: $ @SYS$UPDATE:AUTOGEN GETDATA SETPARAMS NOFEEDBACK 7.
PAGE 132
1. Enter the SHOW DEVICE D command to display a list of disks available on your system. For example: $ SHOW DEVICE D Device Name $11$DKB100: (NODE1) $11$DKB200: (NODE1) 2.
PAGE 133
4. 5. 6. 7. Configure DECnet if it was installed or added during an upgrade (Section 7.8.4 (page 135)). Configure TCP/IP Services for OpenVMS if it was installed or added during an upgrade (Section 7.8.5 (page 135)). If neither DECnet nor TCP/IP Services for OpenVMS is being used, install and configure third-party networking software, if necessary (Section 7.8.6 (page 136)). Update SYSTARTUP_VMS.
PAGE 134
NOTE: Normally, you create a queue manager only once. The system stores the START QUEUE command in the queue database to enable the queue manager to start automatically whenever the system reboots. If the queue manager has been started before on your system, do not specify this START QUEUE command again; the /NEW_VERSION qualifier causes your system to overwrite your current queue database files. To configure shared files on multiple system disks or off the system disk, edit the SYS$MANAGER:SYLOGICALS.
PAGE 135
the DECwindows Motif for OpenVMS Installation Guide and Managing DECwindows Motif for OpenVMS Systems. 7.8.4 Configuring DECnet If you installed DECnet, or if you added DECnet during an upgrade, you must now configure DECnet. Follow the instructions provided for the version of DECnet you installed.
PAGE 136
Section 7.18 (page 161)) so that the TCP/IP Services software starts automatically when your system is rebooted. IMPORTANT: manager. Do not configure TCP/IP Services for OpenVMS without first starting the queue 7.8.6 Installing and Configuring Third-Party Networking Software You need networking software to download patches and as a requirement for certain layered products. If you are using neither DECnet nor TCP/IP Services for OpenVMS, you should install and configure third-party networking software now.
PAGE 137
Module installed successfully. CDSA-I-Init, Secure Delivery Initialization complete 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.
PAGE 138
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.
PAGE 139
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.
PAGE 140
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.4 is referenced by HP I64VMS OPENVMS V8.
PAGE 141
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.
PAGE 142
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.
PAGE 143
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 Integrity servers Version 8.
PAGE 144
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 and gWLM.
PAGE 145
2. Ensure that the CIM Server is running and verify the list of providers installed by entering the following command: $ CIMPROVIDER -L -S This displays output similar to the following: MODULE OperatingSystemModule ComputerSystemModule ProcessModule IPProviderModule 3. STATUS OK OK OK OK To configure the WBEM Providers for OpenVMS software, enter the following command: $ @SYS$COMMON:[WBEMPROVIDERS]WBEMPROVIDERS$CONFIGURE.COM You are prompted to enter the primary owner name and contact information.
PAGE 146
4.
PAGE 147
If you choose to use Instant Capacity, Temporary Instant Capacity, or Global Instant Capacity, configure the software by entering the following command: $ @SYS$MANAGER:ICAP$CONFIG.COM For more information about configuring and using Instant Capacity, see the HP Instant Capacity User’s Guide on the following website: http://docs.hp.com/en/netsys.html#Utility%20Pricing%20Solutions 7.9.
PAGE 148
NOTE: Do not attempt to explicitly remove TDC_RT from your system. The PRODUCT REMOVE command is not supported for TDC_RT although there appears to be an option to remove it. TDC_RT is installed with the operating system and is tightly bound with it. HP or third-party applications might require TDC_RT. 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 TDC_RT V2.
PAGE 149
When TDC_RT Version 2.1 or any newer version of TDC is installed, files associated with TDC Version 1.n are not removed. In any case, TDC_RT Version 2.1 (or later) and TDC Version 1.n can safely coexist on a system. You can remove the older TDC files by uninstalling TDC (use the DCL command PRODUCT REMOVE). • TDC Version 2.2 on an earlier version of OpenVMS If you upgrade to OpenVMS Version 8.4 from an earlier version of OpenVMS on which TDC Version 2.2 was installed, files shared by TDC_RT Version 2.
PAGE 150
member, then all cluster members in a single-version, single-architecture OpenVMS Cluster should be able to run the software. For mixed-version and mixed-architecture clusters, you should obtain and install a complete Performance Data Collector kit (TDC Version 2.2) from the following website: http://www.hp.com/products/openvms/tdc The complete kit provides an SDK and run-time environments for all supported OpenVMS configurations.
PAGE 151
If you do not want to use a node-specific welcome file, you can optionally define the logical in SYS$MANAGER:SYSTARTUP_VMS.COM to display a message, such as in the following example: $ DEFINE SYS$WELCOME “Welcome to node HOMER” For more information about creating login welcome messages, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials. 7.
PAGE 152
2. 3. 4. 5. Choose option 1 on the menu. Choose the PRESERVE option. Enter the name of the device that contains the system disk and answer the questions. After you answer the question “Do you want detailed descriptions?,” information regarding reconfiguring or reinstalling is displayed. Read the instructions, then choose the desired entry on the menu of options.
PAGE 153
1) 2) 3) 4) Reconfigure the OpenVMS platform. Reconfigure the OpenVMS operating system. Reinstall the OpenVMS operating system. Return to the Main Menu (abort the upgrade/installation). Enter choice or ? for help: (1/2/3/4/?) 2 The following product has been selected: HP I64VMS VMS V8.4 Operating System 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.
PAGE 154
$ @SYS$UPDATE:LIBDECOMP For more information about the utility, you can request help by entering the following command: $ @SYS$UPDATE:LIBDECOMP HELP You can list the sizes and format (reduced or expanded) of the libraries by using the following command: $ @SYS$UPDATE:LIBDECOMP LIST For complete information about expanding and reducing system library files and using LIBDECOMP.COM, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.
PAGE 155
Table 7-2 Reduced and Expanded Sizes of Libraries (continued) Library Name/Description HELPLIB.HLB1 DCL help OpenVMS Alpha OpenVMS Integrity servers Reduced Size (as shipped) Reduced Size Expanded Size Expanded Size (as shipped) 10055 18701 10830 21426 LANCP$HELP.HLB LAN Control Program help 116 169 113 163 LATCP$HELP.HLB LAT Control Program help 157 243 157 243 MAILHELP.HLB Mail Utility help 211 316 211 316 NCPHELP.HLB Network Control Program help 262 412 262 412 SDA.
PAGE 156
Table 7-2 Reduced and Expanded Sizes of Libraries (continued) Library Name/Description OpenVMS Alpha OpenVMS Integrity servers Reduced Size (as shipped) Reduced Size Expanded Size Expanded Size (as shipped) VAXCRTLDX.OLB VAX D_floating support; support for /L_DOUBLE_SIZE=128 compiler qualifier 1663 2648 Not included VAXCRTLT.OLB IEEE T_floating double-precision, floating-point entry points 1578 2491 Not included VAXCRTLTX.
PAGE 157
7.14 Installing Patches (Optional but Recommended) HP recommends installing any relevant OpenVMS and networking patches that are available. Most patches are optional, but some layered products might require one or more patches on the system before their software is installed. For more information about patches that might be required on your system, see the HP OpenVMS Version 8.4 Release Notes, and the documentation provided for the relevant layered products. As of Version 8.
PAGE 158
On OpenVMS Integrity server systems, to access the directory containing the V8.4 operating system patches, enter the following command, using the exact case indicated for each letter: FTP> cd openvms_patches/i64/V8.4 250 CWD command successful. To access the directory containing patches for layered products such as TCP/IP Services or DECnet, enter the following command (for Alpha systems, specify alpha in place of Integrity servers):: FTP> cd openvms_patches/layered_products/i64 250 CWD command successful.
PAGE 159
7.15 Installing and Configuring Layered Products (New Installations, Some Upgrades) The OpenVMS operating system kit includes several layered products.
PAGE 160
4. 5. To install layered products, choose option 3 on the menu. For more instructions, see Section 1.4.3 (page 33). After the installation completes, shut down the system by selecting option 9 on the menu. When you boot the target system, the layered products you installed will be present. For additional information about installing layered products, see the HP OpenVMS System Manager's Manual. 7.15.
PAGE 161
4. To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the device name and directory at the prompt. For example: $ @SYS$UPDATE:VMSINSTAL * Where will the distribution volumes be mounted: DKA400:[DIAA032.KIT] To install layered products that require the PCSI utility (indicated in the directories by file names with file types of .PCSI or .
PAGE 162
recommends that you run UETP after an installation or if new hardware was added as part of an upgrade. Before using UETP, you must create a SYSTEST (standalone system) or SYSTEST_CLIG (OpenVMS Cluster system) account. You should also create an account for HP service representatives to use. You can use the CREATE_SPECIAL_ACCOUNTS.COM file to create these accounts, as explained in HP OpenVMS System Manager's Manual, Volume 1: Essentials.
PAGE 163
1. Run AUTOGEN in feedback mode, examine AGEN$PARAMS.REPORT, and reboot the system. To run AUTOGEN in feedback mode, use the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK To view AGEN$PARAMS.REPORT on your screen, enter the following command: $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT You can print this file or examine it using the EDIT/READ_ONLY command.
PAGE 164
7.25 Modifying System Parameters Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. Read the notes in Section 7.25.1 (page 164). These notes apply to modifications being made after a new installation and after an upgrade. If you are modifying system parameters after an upgrade, also see Section 7.25.2 (page 164). 7.25.
PAGE 165
7.25.2.1 System File Sizes AUTOGEN sets the following files at sizes appropriate for your system: • • • [SYSEXE]SYSDUMP.DMP [SYSEXE]PAGEFILE.SYS [SYSEXE]SWAPFILE.SYS If you have special workloads or configurations, you can specify different sizes for these files by performing the following steps: 1. 2. Log in to the SYSTEM account. Enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES 3. 4. If the file sizes displayed need to be adjusted, add symbols to the MODPARAMS.
PAGE 166
PAGE 167
A Booting and Shutting Down Your OpenVMS Alpha System This appendix applies to Alpha systems only and explains how to halt, boot, and shut down the operating system. It also includes related information, such as setting the system for automatic booting and using the Writeboot utility. This appendix also includes brief troubleshooting procedures.
PAGE 168
After you boot, the system displays a menu from which you can choose options to perform the following tasks: • Install or upgrade the operating system using the PCSI utility. • Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk. • Shut down the system. A.1.1.
PAGE 169
Table A-1 Supported LAN Devices (continued) Alpha Computer Ethernet Device FDDI Device AlphaStation 200 series EWA0 FWA0 AlphaStation 400 series EWA0 FWA0 AlphaStation 500 series EWA0 FWA0 AlphaStation 600 series ERA0, EWA0 FWA0 DEC 2000 series ERA0 — DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 — DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 DIGITAL Personal Workstation (DPWS) series EWA0 FWA0 AlphaServer DS15 EWA0, EIA0, EGA0 FWA0 AlphaServer DS20 EWA0, EI
PAGE 170
Network Initial System Load Function Version 1.2 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 as follows, and press Enter after each entry: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name (ALPHA084 is the default service name for the InfoServer hardware; for the InfoServer utility, ask your system or network manager for the service name).
PAGE 171
NOTE: If you boot the OpenVMS Alpha operating system CD from an InfoServer but lose your connection during the installation or upgrade procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following: IF ... THEN ... You previously chose the 1. Reboot the OpenVMS Alpha operating system CD. INITIALIZE option 2. Choose the install/upgrade option (1) on the menu and perform the installation or upgrade procedure again. You previously chose the 1.
PAGE 172
• y is either A or B, depending on the SCSI port of the PMAZB or PMAZC adapter that contains the boot device. • zzz is the SCSI unit number of the boot device. The OpenVMS Alpha operating system does not distinguish between the PMAZB or PMAZC adapter and the integrated SCSI adapter. The operating system views them as identical adapters.
PAGE 173
• • Specify another system startup command procedure Select the default system parameter file (ALPHAVMSSYS.PAR) if you modified system parameters to values that render the system unbootable • Specify a minimum startup There are several ways to perform a conversational boot. The following procedure is the most direct: IF ... THEN GO TO... The OpenVMS Alpha operating system is running Step 1 The OpenVMS Alpha operating system is not running Step 4 1. 2. Log in to the SYSTEM account.
PAGE 174
For examples of using conversational booting, see Section A.1.5 (page 174) and Section A.1.9 (page 175). A.1.5 Booting with Minimum Startup In certain cases, you might want to boot your system without performing the full sequence of startup events. For example, if a startup event prevents you from logging in, you might want to boot the system without executing the startup so that you can log in and fix the problem. You can use the conversational boot to specify a minimum startup.
PAGE 175
SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of the operating system to a different root directory. (See the HP OpenVMS System Manager's Manual for more information about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.) To boot from a different directory (for example, [SYS3]), enter the BOOT command as follows: >>> BOOT -FLAGS 3,0 DKA200 A.1.
PAGE 176
can reset the active values for all system parameters to the default value. (In most cases, HP recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.
PAGE 177
A.1.9.2 Booting Without Startup and Login Procedures If the system does not complete the startup procedures or does not allow you to log in, you might need to bypass the startup and login procedures. The startup and login procedures provided by HP should always work. However, if you introduce an error when modifying the startup or login procedure, it is possible to accidentally lock yourself out of the system. How to Perform This Task 1.
PAGE 178
How to Perform This Task 1. 2. Halt the system by pressing Ctrl/P or whatever method is used for your computer. (See Section A.3 (page 182) for more information about how to halt Alpha computer systems.) Begin the conversational boot by entering the BOOT command in the following format: BOOT -FLAGS 0,1 [device-name] For device-name, substitute the device name of the drive from which you want to boot.
PAGE 179
A.2 Configuring Boot Behavior for Alpha Systems The following sections describe how to set up automatic booting, set and show the default boot device, modify boot parameters, and create a bootable OpenVMS Alpha system disk using the Writeboot utility. A.2.1 Setting the System for Automatic Booting Alpha computers can boot automatically from a designated boot device. When you installed the OpenVMS Alpha operating system, you designated the system disk as the default boot device. Section A.2.
PAGE 180
8. After you set this variable, HP recommends that you set the boot device and operating system flags as well, using the SET BOOTDEF_DEV and SET BOOT_OSFLAGS commands described in the following sections. A.2.2 Setting and Showing Boot Devices Use the SET BOOTDEF_DEV command to tell the system which drive you want to boot from (that drive becomes the default boot device). Use the SHOW BOOTDEF_DEV command to display the current default boot device.
PAGE 181
Hexadecimal Value System Response 80 Prompts for the name of the secondary bootstrap file. 100 Halts the system before the secondary bootstrap. 2000 Marks corrected read data error pages as bad. 10000 Displays extensive, detailed debug messages during the boot process. 20000 Displays selected user-oriented messages during the boot process.
PAGE 182
NOTE: The file must be contiguous and movefile operations on the file must be disabled. If the file is not contiguous, use the DCL command COPY/CONTIGUOUS (or similar) to re-create a contiguous version of the file. To disable movefile operations, use the DCL command SET FILE/NOMOVE. This prevents bootstrap failures that could result from the normal and expected operations of disk defragmentation tools.
PAGE 183
A.3.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. You can perform the following three types of shutdown operations: • An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM (see Section A.3.2.1 (page 183) ) • An emergency shutdown with OPCCRASH.EXE (see Section A.3.2.2 (page 183) ) • An emergency shutdown with crash commands (see Section A.3.2.
PAGE 184
This causes the system to perform a bugcheck. 5. 6. After the system reboots, log in to the SYSTEM account. To examine the dump file, enter the following commands and press Enter after each one: $ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP SDA> SHOW CRASH For more information about the System Dump Analyzer (SDA) utility, see the HP OpenVMS System Analysis Tools Manual. A.4 Troubleshooting Procedures The following sections describe procedures that you can follow if you encounter problems with your system. A.4.
PAGE 185
appear, the program you are executing might be stalled or “hanging.” (If you have disabled Ctrl/T by entering the command SET NOCONTROL=T or have set the terminal to NOBROADCAST mode by entering the command SET TERMINAL/NOBROADCAST, this procedure does not work.) • Make sure the cable connecting the terminal or monitor to the system is secure. If you determine that you have a system problem: 1. Force an exit from a stalled or hanging program by pressing Ctrl/Y.
PAGE 186
PAGE 187
B Configuring OpenVMS Integrity servers 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 Integrity servers operating system, and shut down the operating system. The appendix also includes brief troubleshooting procedures.
PAGE 188
B.1.1 Overview of Utilities and Console Options The main interfaces that are typically available for configuring and managing your HP Integrity servers 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.
PAGE 189
NOTE: In some HP documents, you might see the acronym POSSE used in place of or in combination with EFI. EFI is an Intel specification of an interface between firmware and the operating system. POSSE (Pre-OS System Environment) is the HP implementation of EFI that extends the EFI Shell and EFI Boot Manager to include additional features for managing hardware and system boot options.
PAGE 190
NOTE: MP provides much more functionality than BMC and might be more appropriate for your needs. On some systems, MP is an optional component and on others it is built into the system. • Baseboard Management Controller (BMC) BMC is more limited in functionality than MP. BMC enables you to control some management features built into the system board, such as diagnostics, configuration, and hardware management. BMC provides a console connection on some systems.
PAGE 191
• Terminal attribute is set to PASSALL • Terminal attribute is set to PASTHRU • IO$_READALL • IO$_READPBLK • Ctrl/V is entered, which tells the driver to pass the next character and skip the remap check. Alternatively, you can set up your terminal emulator so that the Backspace key deletes the last character typed. However, for the key to work properly on OpenVMS, you must still enter the SET TERMINAL command described earlier. B.
PAGE 192
Your first step is to decide what console to use. Depending on your hardware/firmware configuration, OpenVMS can use one of the following types of consoles: • System serial port • MP (or iLO MP) serial port The MP interface is not visible to OpenVMS unless the MP serial port is selected as the Primary console. • Graphics (VGA) device Graphics console support allows you to use a monitor and a USB keyboard and mouse connected directly to the Integrity server ports available for such purposes.
PAGE 193
on the speed of the LAN, and in general is only recommended for doing occasional system management functions that do not require performance sensitive graphics. NOTE: Make sure your Integrity servers has the latest firmware updates installed. B.2.
PAGE 194
2. From the Boot Configuration menu, select the Console Configuration menu and press Enter: 3. If the Console Configuration menu shows that your preferred device is already configured as the Primary console, you need not continue; otherwise, select the device that you want as the OpenVMS Primary console.
PAGE 195
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: B.2.1.2 Using the EFI Shell to Select the OpenVMS Console To select the device for your OpenVMS console using the EFI shell, follow these steps: B.
PAGE 196
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.
PAGE 197
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.
PAGE 198
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.
PAGE 199
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.
PAGE 200
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 Integrity servers DVD to install the operating system onto a system disk. Follow the instructions in Chapter 3 (page 45) (specifics for booting are provided in this appendix).
PAGE 201
shadow set to the boot list and dump device list. (Be sure to add all members to both lists.) For instructions on how to use the utility, see Section B.5 (page 203). For more information about configuring Fibre Channel devices with this utility, see Appendix E (page 289). For information about using the OpenVMS Integrity servers Boot Manager utility to display boot options, see Section B.5.2.2 (page 208). For information about setting the pause length, see Section B.5.2.3 (page 208).
PAGE 202
devices while the operating system is running, use the OpenVMS Integrity servers Boot Manager utility (SYS$MANAGER:BOOT_OPTIONS.COM), as described in Section B.5 (page 203). 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 . . .
PAGE 203
To move from the EFI to MP, press Ctrl/B (this assumes MP is present and configured). For more information about using EFI, see the documentation provided for your Integrity servers. B.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.
PAGE 204
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 B.6 (page 211). HP recommends that you load and use the most current system firmware.
PAGE 205
NOTE: The acpiconfig command does not necessarily report the setting that was used on the current nPartition boot stage. It reports only the current setting, which is used for the next boot of the nPartition. B.5.
PAGE 206
OpenVMS I64 Boot Manager Boot Options List Management Utility (1) (2) (3) (4) (5) (6) ADD an entry to the Boot Options list DISPLAY the Boot Options list REMOVE an entry from the Boot Options list MOVE the position of an entry in the Boot Options list VALIDATE boot options and fix them as necessary Modify Boot Options TIMEOUT setting (B) Set to operate on the Boot Device Options list (D) Set to operate on the Dump Device Options list (G) Set to operate on the Debug Device Options list (E) EXIT from the Bo
PAGE 207
7. Flags Description 0,20000 Print debug messages on boot. 0,30000 Print more debug messages on boot. 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 as in the following example. This example shows a sample confirmation message (for devices with multiple paths, such as Fibre Channel devices, a separate confirmation message is displayed for each path).
PAGE 208
Shell> \efi\vms\vms_bcfg boot add 1 dka0: -fl 0,2 "HP OpenVMS I64" For more information about EFI utilities for OpenVMS, see the HP OpenVMS System Management Utilities Reference Manual. B.5.2.2 Displaying EFI Boot Entries and Mapped OpenVMS Devices The Integrity servers EFI Boot Manager shows the various paths to the boot device. You can use the OpenVMS Integrity servers Boot Manager utility to display the OpenVMS boot device options known to EFI.
PAGE 209
info cpu command or the EFI cpuconfig command to display current settings, such as the setting of the Hyper-Threading feature. You might need to restore boot options, such as if they get lost during a firmware upgrade. You can save and restore your EFI boot path settings on Integrity servers by using the OpenVMS Integrity servers Boot Manager (SYS$MANAGER:BOOT_OPTIONS.COM) utility. You can also use the EFI variable -s command to save boot option variables and the variable -r command to restore them.
PAGE 210
NOTE: If the target OpenVMS Integrity servers system disk has an incorrectly-placed [000000]GPT.SYS file, the disk cannot be used reliably as an OpenVMS Integrity servers 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).
PAGE 211
B.5.4 Alpha and Equivalent Integrity servers 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. Some of the commands listed might not be available on certain hardware systems.
PAGE 212
NOTE: To boot your OpenVMS Integrity servers operating system, you can use a VGA graphics device (except on rx2600 Integrity servers 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 servers, see Section B.2 (page 191).
PAGE 213
B.6.1.2 Booting OpenVMS Integrity servers on an nPartition CAUTION: To prevent loss of data when booting your OpenVMS Integrity servers operating system, note the following: • You must first ensure that the nPartition has its ACPI configuration set to the default (see Section B.5.1 (page 204)). NOTE: OpenVMS Version 8.4 introduces support for cell local memory (CLM) on Integrity cell-based servers. Prior OpenVMS versions had a restriction — they used only interleaved memory (ILM).
PAGE 214
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. 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.
PAGE 215
1. To ensure that EFI can access the DVD, enter the following commands at the EFI Shell prompt of entry-class or single-cell Integrity servers. 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:>.
PAGE 216
2. To boot the DVD, enter the following command at the EFI Shell prompt, where fsn: is the Integrity servers 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.
PAGE 217
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 B.6.3 Booting the OpenVMS Integrity servers OE DVD from the InfoServer To boot from a virtual DVD drive on the LAN using OpenVMS Integrity servers InfoServer software, you must initially perform certain configuration steps (one time only).
PAGE 218
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 B.3.1 (page 201). B.6.
PAGE 219
Table B-2 SYSGEN Commands Used in the SYSBOOT Procedure (continued) Command Description ENABLE CHECKS Permits checking of parameter values specified with the SET command. 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.
PAGE 220
Value System Response 3 Displays the SYSBOOT prompt and includes XDELTA but does not take the initial breakpoint. 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. B.6.
PAGE 221
SYSBOOT> USE DEFAULT The USE DEFAULT command specifies that default values should be used for all parameters. 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.
PAGE 222
SYSBOOT> CONTINUE 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.
PAGE 223
The last command causes the booting to continue. 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.
PAGE 224
crash and to bring you eventually to EFI. If you enter any other character, the system returns back to the IPC facility. B.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 B.5.2 (page 205).
PAGE 225
B.7.2.2 Emergency Shutdown with OPCCRASH.EXE If you cannot perform an orderly shutdown with the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency shutdown program. To run the OPCCRASH.EXE program, log in to the SYSTEM account and enter the following command: $ RUN SYS$SYSTEM:OPCCRASH For more information about the OPCCRASH program, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.
PAGE 226
dangerous. If the system does not reboot automatically, reboot the system manually as described in Section B.6.7 (page 217). • If the system stops responding to your commands (that is, if the system hangs), there is a possible failure in a system software or hardware component or a possible power failure. • If the system exhibits erratic behavior (it does not respond according to specifications), it indicates a possible failure in a system software or hardware component.
PAGE 227
C 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 Integrity servers (Version 8.2-1 or later) systems. It also describes how to boot the virtual DVD/CD drive from the network. C.
PAGE 228
Table C-1 InfoServer Booting: Differences Between Alpha and Integrity server Systems (continued) Component Alpha Integrity servers Boot server Any MOP-enabled system with the specified file Only those BOOTP servers having the network device MAC address defined in the BOOTP database LAN server InfoServer hardware, or InfoServer utility InfoServer application running on OpenVMS running on OpenVMS Alpha Version 8.3 or Alpha Version 8.
PAGE 229
Table C-2 Procedure for Enabling InfoServer Network Booting (continued) Alpha only Enable MOP on the boot server and then copy APB_084.SYS from See the LANCP chapter the OpenVMS Version 8.4 distribution media to the MOP download in HP OpenVMS System database (LAN$DLL, which defaults to MOM$SYSTEM). Management Utilities Reference Manual: A-L. Integrity servers only Set up the TCP/IP Services for OpenVMS BOOTP server and TFTP Section C.4 (page 235). server.
PAGE 230
3. Start the LANCP utility and enter the LANCP command SHOW CONFIGURATION at the LANCP prompt, as in the following example. The resulting display lists four LAN devices, two of which are available (connected), as indicated by the Link column (Up means the device is available; Down means it is not). You can use a device that is in use by other protocols. Decide which available devices you want to use for network booting and record the device’s name, MAC address, and IP address.
PAGE 231
4. The utility prompts you for the position you want your entry to take in the EFI boot option list. Enter any position number other than 1. (The number 1 position sets the device for automatic rebooting, which is not desirable for upgrades.) Enter the desired position number (1,2,3,,,) of the entry. To display the Boot Options list, enter "?" and press Return. Position [1]: 4 5. The utility prompts you for OpenVMS boot flags. By default, no flags are set.
PAGE 232
NOTE: The Boot Configuration Menu provided by EFI or the EFI tool VMS_BCFG are other alternatives for adding a boot entry. For more information on EFI tools, see the System Management Utilities Reference Manual. C.2.3 Verifying the Network I/O Device Is Bootable by EFI Finally, verify that the LAN device you selected for your system’s InfoServer client is bootable by EFI. Verification is recommended if the selected device is not one of the core I/O LAN devices installed on your Integrity servers.
PAGE 233
! ! Note: ! The LAD disk block cache is structured as a number of fixed-size ! buckets. You must specify both the bucket size and the number of ! buckets for the cache. ! ! The LAD cache is allocated from non-paged pool and is in no way ! associated with the XFC cache. The total LAD cache size in bytes ! may be determined by the formula: ! ! cache-bytes = bucket-size-in-blocks * number-of-buckets * 512 ! ! Be sure the SYSGEN parameters NPAGDYN/NPAGEVIR are sized appropriately.
PAGE 234
NOTE: As indicated in the file comments, the LAD cache comes out of nonpaged pool. If you increase the cache significantly, you might need to increase the nonpaged pool SYSGEN parameters (NPAGEDYN and NPAGEVIR). 3. Determine which network device will be used for InfoServer LAD operations. You can use any network device that is visible to OpenVMS. Typically, any network device that works with DECnet or TCP/IP Services for OpenVMS should work.
PAGE 235
7. Now that you have set up and enabled the InfoServer server, you must use the InfoServer control program to create a service for the DVD drive. Follow these steps: a. Mount the OpenVMS distribution media systemwide. In the following example, DQA0 is the DVD drive name (typically, DQA0 or DNA0 is the drive name) and I64084 is the volume label (for OpenVMS Integrity servers): $ MOUNT/SYSTEM DQA0 I64084 b.
PAGE 236
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. IMPORTANT: You do not have to perform steps 2 and 3 when booting an OpenVMS Integrity servers Version 8.4 or later if boot flags are set to 0,200400. 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.
PAGE 237
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:”, if steps 2 and 3 were performed and VMS_LOADER.EFI and IPB.EXE are copied to the newly created directory.
PAGE 238
5 6 7 Adds host MOZART as a client entry in the BOOTP database, where the MAC address of the client’s LAN device is 00-13-21-5B-85-E4 (as was determined in the example for the client in Section C.2.1 (page 229)) and the boot file for the client is [V831H1]VMS_LOADER.EFI. Displays information about the boot client MOZART as stored in the local host database (use this command to verify that the client has been configured appropriately).
PAGE 239
NOTE: You can copy the DVD to an LD device and boot from the LD device. This process is faster than using a DVD. 1. Make sure the CD or DVD is mounted systemwide on the OpenVMS system serving as the InfoServer, and make sure an InfoServer service for the DVD drive is available on the network and accessible from your client system (the system to be booted from the InfoServer). The service should point to the server DVD drive on which the OpenVMS CD or DVD is mounted.
PAGE 240
to the appropriate network and are bootable using the InfoServer, in which case it does not matter which one you select. Note also that once you have OpenVMS running, you can display the devices and their corresponding MAC addresses by using the LANCP command SHOW CONFIG at the DCL prompt. The command lists the OpenVMS device names along with the MAC address and other characteristics.
PAGE 241
Example C-3 DHCP Message Loading.: Network Boot, 10/100 Running LoadFile() CLIENT MAC ADDR: 00 13 21 5H 85 E4 DHCP./ CLIENT IP: 1.1.24.219 MASK: 255.0.0.0 Running LoadFile() DHCP IP: 0.240.0.0 Starting: I64 Upgrade VIA NET %EIA-I-BOOTDRIVER, Starting auto-negotiation %EIA-I-BOOTDRIVER, Auto-negotiation selected 100BaseTX FDX Network Initial System Load Function Version 1.2 FUNCTION ID 1 2 3 4 5 FUNCTION - Display Menu Help Choose Service Select Options Stop Enter a function ID value: 4.
PAGE 242
Example C-4 Loading of Memory Disk Message Loading.: Network Boot Mac(00-15-60-04-f4-1e) Client MAC Address: 00 15 60 04 F4 1E .- Client IP Address: 1.1.238.63 Subnet Mask: 255.255.240.0 BOOTP Server IP Address: 1.1.238.239 DHCP Server IP Address: 0.240.0.0 Boot file name: LDA3:[VMS$COMMON.SYSEXE]VMS_LOADER.EFI Retrieving File Size.| Retrieving File (TFTP).Loading memory disk from IP 1.1.238.239 ................................................................................ Loading file: LDA3:[VMS$COMMON.
PAGE 243
NOTE: If you boot the OpenVMS Alpha operating system CD or OpenVMS Integrity servers OE DVD from an InfoServer but lose your connection during the installation or upgrade procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following: IF ... THEN ... You previously chose the 1. Reboot the OpenVMS CD DVD. INITIALIZE option 2. Choose the install/upgrade option (1) on the menu and perform the installation or upgrade procedure again. You previously chose the 1.
PAGE 244
PAGE 245
D Using HP SIM and vMedia for Provisioning OpenVMS HP Systems Insight Manager (HP SIM) allows you to provision OpenVMS to one or more Integrity servers in the network. This means that, from a single location in the network (a Microsoft Windows ProLiant server designated as the management workstation), you can use HP SIM to install, upgrade or configure OpenVMS on several servers simultaneously.
PAGE 246
Ignite-UX server for provisioning HP-UX on Integrity servers. Using HP SIM with InfoServer, you can provision up to eight servers simultaneously. To use vMedia, which is provided with Integrity servers that include iLO 2 MP, you must create an ISO image of the OpenVMS OE DVD, store the image on an accessible PC or Windows server in the network, and use HP SIM to connect your Integrity servers vMedia to that image. Using vMedia, you can provision one server at a time.
PAGE 247
On the Integrity server: — vMedia licensing through the Advanced Server Management option (iLO 2 Advanced Pack) and the user virtual media access right. vMedia is part of the iLO Advanced Pack feature set. This license is provided and pre-enabled on the Integrity BL860c and BL870c Server Blade products. On the management workstation (or a Windows-based PC/server on the same LAN as the Integrity server): — — — Microsoft Internet Explorer Version 6 or later. Java Plug-in 1.5.0_08 or later.
PAGE 248
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. To deploy OpenVMS Version 8.4, the InfoServer server must be running OpenVMS Integrity Version 8.4 or later. Perform these basic steps to set up InfoServer: a. Copy the SYS$STARTUP:ESS$LAD_STARTUP.TEMPLATE file to the SYS$STARTUP:ESS$LAD_STARTUP.DAT file.
PAGE 249
IMPORTANT: For each subsequent upgrade of OpenVMS, you must create a separate directory for the boot files specific to the OpenVMS version and, where appropriate, modify the path specified for each client’s boot files. To make subsequent upgrades easier, you can use systemwide or clusterwide logical names. c. d. e. f. Copy the following two files from the DVD to the TCPIP$TFTP_ROOT:[V831H1] directory: • [SYS0.SYSCOMMON.SYSEXE]VMS_LOADER.EFI • [SYS0.SYSCOMMON.SYSEXE]IPB.
PAGE 250
$ $ $ $ MOUNT/OVERRIDE=IDENTIFICATION DNA0: BACKUP/IMAGE/VERIFY DNA0: LDA1: DISMOUNT DNA0: DISMOUNT LDA1: For more information about InfoServer commands, including how to work with LD devices, see the InfoServer help (at the InfoServer prompt, type HELP) or the HP OpenVMS System Management Utilities Reference Manual. 4.
PAGE 251
D.
PAGE 252
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.
PAGE 253
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.
PAGE 254
8. 254 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.
PAGE 255
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 servers over a high-speed network link. 9. This brings up the Virtual CD/DVD-ROM dialog box, as in the following example.
PAGE 256
You can now provision OpenVMS through HP SIM (see Section D.1.6.2 (page 268)) or use vMedia independently of HP SIM (see Section D.2 (page 279). D.1.5 Setting Up HP SIM and the Windows Server to Provision OpenVMS Install and configure HP SIM on a Microsoft Windows ProLiant server in the LAN according to the instructions in the HP SIM Windows Installation and Configuration Guide and the HP SIM Release Notes available in the Information Library on the following website: http://www.hp.
PAGE 257
If your system is listed with the proper port IP address and identification, you are ready to provision. (HP SIM identifies such properties as the type of system, which in this case is MP, the operating system and version, and the product name.) If your MP is not listed, perform a manual discovery as described in the subsequent sections. NOTE: If your iLO 2 MP is connected properly and turned on, HP SIM must discover it.
PAGE 258
2. Click New. Under the resulting New Discovery heading, select Discover a single system. Enter the name of the discovery task in the Name: text box. Under Schedule, clear the Automatically execute discovery every check box. Enter the IP address of the Integrity servers iLO 2 MP port to be discovered, and click Save. 3. After the discovery task is saved, select the newly created discovery task on the Discovery page and click Run Now.
PAGE 259
4. Click View Task Results to view the progress of the discovery. D.1.6 Provisioning OpenVMS Once the iLO 2 MP of your Integrity servers (and any other servers you want to provision) has been discovered and identified, you can provision OpenVMS (deploy or configure the operating system on the target Integrity servers). To provision OpenVMS using the InfoServer, see ““Provisioning OpenVMS Through the InfoServer” (page 261).” D.
PAGE 260
To provision OpenVMS using the vMedia device, see “Provisioning OpenVMS Through vMedia” (page 268). To apply OpenVMS licenses on your Integrity servers running OpenVMS, see “Installing Licenses on OpenVMS Servers Through Provisioning” (page 272). To configure OpenVMS TCP/IP on your Integrity servers through Provisioning, see “Configuring OpenVMS TCP/IP Through Provisioning” (page 275).
PAGE 261
D.1.6.1 Provisioning OpenVMS Through the InfoServer To provision OpenVMS using HP SIM with the InfoServer, follow these steps. 1. Complete the procedure described in “Setting Up InfoServer Support” (page 247) to setup InfoServer for use with Provisioning. 2. Ensure that each server to be provisioned is not booted into an operating system. The servers can be in a powered-OFF state, in a halted state, or booted into the EFI shell.
PAGE 262
7. 262 Provide the following information for each Integrity server being provisioned: • MP Login Credentials: This information is used to login to the MP console of the target server to provision OpenVMS. The default for the user name and password is Admin. • Timeout (in minutes): This value determines the maximum duration of inactivity allowed on the system console during OpenVMS installation or upgrade, after which HP SIM provisioning reports that the system is not responding.
PAGE 263
— Installation of optional products: You can choose to install the following optional products with the OpenVMS installation: ◦ DECwindows Motif for OpenVMS ◦ HP TCP/IP Services for OpenVMS ◦ DECnet Phase IV or DECnet-Plus for OpenVMS If you select DECnet Phase IV or DECnet-Plus for installation, you must specify the DECnet address to be used. Enter the DECnet address as 0.0 if you plan to use DECnet without Phase IV compatible addresses.
PAGE 264
8. 264 In Step 5, HP SIM LAN-boots the target servers, and uses InfoServer to provision the selected version of OpenVMS on each target server. The installation progress is indicated for each target server, as shown in the example.
PAGE 265
This image illustrates the progress of provisioning OpenVMS from InfoServer. 9. To view what is going on in the background for an Integrity server that is being provisioned, access the server iLO 2 MP website address from any browser, as shown in the image below. Click Launch to access the server serial console. IMPORTANT: • Do not interrupt the installation process. • Do not allow Write access to the server console while the installation or upgrade process is in progress.
PAGE 266
The provisioning install script runs in the background and provides responses to install OpenVMS on the target servers. The following example shows some of the automatic responses from the install script.
PAGE 267
IMPORTANT: Do not interrupt the process. Do not allow Write access to your server console while the installation or upgrade process is in progress. After approximately 60 minutes, depending on the network bandwidth and configuration, the installation completes. If the procedure does not complete successfully, provisioning terminates. The reason for failure is displayed in the progress column and on the console screen, as well as in the log file
PAGE 268
Installation Directory>\logs\OPENVMS\_.log on the ProLiant server that is running HP SIM. NOTE: After completing the installation, you must register all licenses for use of the operating system and any installed layered products. For information about registering licenses, see “Registering Your Licenses” (page 128). For information on using HP SIM provisioning to register your licenses, see “Installing Licenses on OpenVMS Servers Through Provisioning” (page 272). D.1.6.
PAGE 269
7. Provide the following information for the Integrity server being provisioned: • MP Login Credentials: This information is used to login to the MP console of the target server to provision OpenVMS. The default for the user name and password is Admin. • Timeout (in minutes): This value determines the maximum duration of inactivity allowed on the system console during OpenVMS installation or upgrade, after which HP SIM provisioning reports that the system is not responding.
PAGE 270
NOTE: If this option is enabled, and no boot option exists for the selected system disk, Provisioning sets the VMS boot flags for the new boot option as 0,0. 8. 270 Verify that the information for the target server is accurate, and click Next. HP-SIM boots OpenVMS from vMedia and provisions OpenVMS on the selected target server.
PAGE 271
This image illustrates the progress of provisioning OpenVMS from vMedia. 9. Meanwhile, to view what is going on in the background on the Integrity server that is being provisioned, access the server iLO 2 MP website address from any browser. Click Launch to access the server serial console. D.
PAGE 272
IMPORTANT: Do not interrupt the provisioning process. Do not allow Write access to your server console while the installation or upgrade process is in progress. 10. After approximately 90 minutes, depending on the network bandwidth and configuration, the upgrade procedures is completed. If the procedure does not complete successfully, provisioning terminates.
PAGE 273
You can install licenses on up to eight Integrity servers at a time. NOTE: To install the license, ensure that OpenVMS is up and running. Before proceeding, verify that the correct installation of OpenVMS is running on all the selected servers. HP SIM displays the Integrity servers to be provisioned. 3. Verify the target servers that you have selected, and click Run Now. 4.
PAGE 274
5. 274 HP-SIM logs in to the MP console and OpenVMS on each target server, and installs the provided licenses in the background. The license installation progress is indicated, as shown in the example.
PAGE 275
IMPORTANT: Do not interrupt the license installation process. Do not allow Write access to your server console while the license installation is in progress. The license installation process completes within a few minutes. If the procedure does not complete successfully, provisioning terminates. The reason for failure is displayed in the progress column and on the console screen, as well as in the log file, \logs\OPENVMS\ __License.
PAGE 276
HP SIM displays the Integrity servers to be provisioned. You can configure TCP/IP on up to eight Integrity servers at a time. 276 3. Verify the target servers that you have selected, and click Run Now. 4. On the subsequent page, provide the following information for each Integrity server being provisioned: • MP Login Credentials: This information is used to login to the MP console of the target server to configure TCP/IP. The default values for the user name and password is Admin.
PAGE 277
IMPORTANT: Do not interrupt the provisioning process. Do not allow Write access to your server console while this procedure is in progress. You can continue to fill out rest of the details for OpenVMS TCP/IP Configuration and TCP/IP Services while provisioning fetches the network interfaces in the background. After completion, provisioning populates the TCP/IP Interfaces field in the GUI with the interfaces found in the link-up state. You can select the TCP/IP interface later, if required.
PAGE 278
◦ ◦ ◦ ◦ • Gateway IP address Domain suffix for the connection Broadcast address: This address is automatically computed from the interface IP address. At least one and up to four name server IP addresses. TCP/IP Services: Select the client and server components to be enabled on the target server. You must select at least one TCP/IP service for each target server.
PAGE 279
IMPORTANT: Do not interrupt the configuration process. Do not allow Write access to your server console while the TCP/IP configuration is in progress. After configuring TCP/IP, provisioning starts the TCP/IP services on each target server. The TCP/IP configuration provisioning completes within a few minutes. If the procedure does not complete successfully, provisioning terminates.
PAGE 280
vMedia also allows the installation of layered products, either remotely or on systems without a built-in DVD drive. The connected virtual device is not limited 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.
PAGE 281
NOTE: When using vMedia to install or upgrade OpenVMS, HP recommends using an image of the OpenVMS Integrity servers 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.
PAGE 282
3. From a browser on a Windows-based PC or server in the same network as your Integrity servers, 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.
PAGE 283
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 D.1.4 (page 250). 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.) D.
PAGE 284
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.
PAGE 285
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.
PAGE 286
SMCLP: CL: SL: HE: X: 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.
PAGE 287
13. Now you can boot the OpenVMS Integrity servers 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 servers. NOTE: The %SYSTEM-I-MOUNTVER messages and the Universal Serial Bus Configuration Manager message are new to OpenVMS Version 8.
PAGE 288
PAGE 289
E 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 on OpenVMS Alpha and Integrity server systems. 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 Version 8.
PAGE 290
Example E-1 Using wwidmgr -show wwid P00>>> set mode diag Console is in diagnostic mode P00>>> wwidmgr -show wwid polling kgpsa0 (KGPSA-B) slot 2, bus 0 PCI, hose 1 kgpsaa0.0.0.2.1 PGA0 WWN 1000-0000-c920-a7db polling kgpsa1 (KGPSA-B) slot 3, bus 0 PCI, hose 1 kgpsab0.0.0.3.
PAGE 291
Example E-2 Using wwidmgr -show wwid -full P00>>> wwidmgr -show wwid -full kgpsaa0.0.0.2.1 - Port: 1000-0000-c920-a7db kgpsaa0.0.0.2.1 - Port: 2007-0060-6900-075b kgpsaa0.0.0.2.1 - Port: 20fc-0060-6900-075b kgpsaa0.0.0.2.1 - Port: 5000-1fe1-0000-0d14 - dga12274.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0016 - dga15346.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0026 - dga31539.13.0.2.1 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 - dga31155.13.0.2.
PAGE 292
- via adapter kgpsaa0.0.0.2.1 kgpsaa0.0.0.2.1 kgpsab0.0.0.3.1 kgpsab0.0.0.3.1 via fc_nport 5000-1fe1-0000-0d14 5000-1fe1-0000-0d11 5000-1fe1-0000-0d13 5000-1fe1-0000-0d12 Con Yes No Yes No DID 210013 210213 210013 210213 Lun 50 50 50 50 [2] UDID:51 WWID:01000010:6000-1fe1-0000-0d10-0009-8090-0677-0027 (ev:none) - current_unit:31539 current_col: 0 default_unit:31539 via adapter via fc_nport Con DID Lun kgpsaa0.0.0.2.1 5000-1fe1-0000-0d14 Yes 210013 51 kgpsaa0.0.0.2.
PAGE 293
• • The changes made by the wwidmgr command do not take effect until after the next system initialization, so the next step is to use the initialize command. After initialization, the console show device command displays each FC adapter, followed by the paths through that adapter to each of the defined FC disks. The path-independent OpenVMS device name for each FC disk is displayed in the second column. E.
PAGE 294
Example E-3 Using widmgr -quickset P00>>> wwidmgr -quickset -udid 10 Disk assignment and reachability after next initialization: 6000-1fe1-0000-0d10-0009-8090-0677-0016 via adapter: dga10.1001.0.2.1 kgpsaa0.0.0.2.1 dga10.1002.0.2.1 kgpsaa0.0.0.2.1 dgb10.1003.0.3.1 kgpsab0.0.0.3.1 dgb10.1004.0.3.1 kgpsab0.0.0.3.
PAGE 295
command, not only the two FC disks that were set up using the console wwidmgr -quickset command. The OpenVMS SHOW DEV/MULTIPATH command confirms that OpenVMS has configured all four paths to each disk. Example E-4 Boot Sequence from an FC System Disk P00>>> set bootdef_dev dga50.1002.0.2.1,dga50.1001.0.2.1,dgb50.1003.0.3.1,dgb50.1004.0.3.1 P00>>> b (boot dga50.1002.0.2.1 -flags 0,0) dga50.1002.0.2.1 is not connected dga50.1002.0.2.1 is not connected dga50.1002.0.2.1 is not connected dga50.1002.0.2.
PAGE 296
IMPORTANT: If you have an entry-class Integrity servers, you can update the firmware yourself. If you have a cell-based Integrity servers, you must contact HP Customer Support to update the firmware for you. To flash the memory of the FC HBA on an entry-class server, update the EFI driver and RISC firmware to the latest versions available. In addition, to enable the HBA factory default settings, update the NVRAM resident in the FLASH ROM on the HBA, if necessary.
PAGE 297
3. 4. 5. From the “Download drivers and software page”, select “Cross operating system (BIOS, Firmware, Diagnostics, etc)”. Download the Offline Diagnostics and Utilities software. Previous versions of the software might be listed along with the current (latest) version. Be sure to select the latest version. Alternatively, you can select the appropriate Offline Diagnostics and Utilities link under the Description heading on this web page.
PAGE 298
(4) MOVE the position of an entry in the Boot Options list (5) VALIDATE boot options and fix them as necessary (6) Modify Boot Options TIMEOUT setting (B) Set to operate on the Boot Device Options list (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 b
PAGE 299
10. When you next see the boot option list displayed at your console by EFI, it should look similar to the following (assuming you took the default in step 7). In this example, the device is $1$DGA1 for two dual-ported EVA5000 storage arrays (the four separate boot paths are identified in the display). Figure E-1 (page 299) illustrates the host FC ports (FGA0 and FGB0) on the Integrity servers and the corresponding FC SAN/EVA5000 storage controller configuration. Please select a boot option $1$dga1 FGA0.
PAGE 300
Boot the FC system disk by selecting the appropriate boot option from the EFI Boot Manager menu and pressing Enter. If your FC boot path is the first option in the menu, it might boot automatically after the countdown timer expires. E.2.
PAGE 301
F 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 Alpha CD or the OpenVMS Integrity servers OE DVD, or through an alternative method that does not require the CD or DVD.
PAGE 302
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. F.4 Backing Up the System Disk The following sections describe how to back up the system disk. F.4.1 Getting Started Before you back up the system disk, do the following: 1.
PAGE 303
$$$ 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.
PAGE 304
1) 2) 3) 4) 5) 6) 7) 8) 9) Upgrade, install or reconfigure OpenVMS I64 Version 8.4 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. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command.
PAGE 305
F.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).
PAGE 306
5. As the procedure completes the installation, the display is similar to the following: HP I64VMS OPENVMS V8.4: OpenVMS and related products platform COPYRIGHT (c) ... Hewlett-Packard Development Company, L.P. Execution phase starting ... The following product will be installed: HP I64VMS VMS V8.4 Portion Done: 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100% The following product has been installed: HP I64VMS VMS V8.4 . . . The installation of minimum OpenVMS I64 is now complete.
PAGE 307
NOTE: During the boot and login operations on this minimum version of the operating system, you can ignore license messages that are similar to the following: %LICENSE-I-NOLICENSE, no license is active for this software product 3. If your system disk is shadowed, install and load a Volume Shadowing for OpenVMS license on this data disk. Then you can back up the shadowed system disk from this data disk without disabling the shadow set.
PAGE 308
PAGE 309
G 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.
PAGE 310
PAGE 311
H 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.
PAGE 312
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.
PAGE 313
H.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.
PAGE 314
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.
PAGE 315
H.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.
PAGE 316
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. H.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.
PAGE 317
H.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.
PAGE 318
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. H.2.6 Installation Directory The installation procedure allows you to select the installation directory and suggests \Program Files\OpenVMS Mgmt Station\ as the default. H.2.7 Installation Procedure Run the TNT032-D.EXE file from a temporary directory.
PAGE 319
• 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. The OpenVMS Management Station Uninstall program does not remove the MMC support files. H.
PAGE 320
PAGE 321
I 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.
PAGE 322
6. Because the PRODUCT REMOVE command does not delete certain files, review the target disk to determine whether you want to delete, move, or archive the operating system files that still remain on the disk. Following are lists of the files that the PRODUCT REMOVE command does not delete: • In target-disk:[SYS*.SYSEXE], where * is the hexadecimal number of any additional OpenVMS Cluster root on the target disk: — IA64VMSSYS.PAR (OpenVMS Integrity server systems) — ALPHAVMSSYS.
PAGE 323
J 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 Integrity server 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.
PAGE 324
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. J.2 Removing the Diagnostic Partition File (Integrity servers only) To remove the diagnostic partition on an OpenVMS Integrity servers system disk and to recover the disk space occupied, delete the file SYS$MAINTENANCE:SYS$DIAGNOSTICS.
PAGE 325
Glossary This glossary defines key terms in the context of an OpenVMS computing environment. Advanced Server for OpenVMS Supported on OpenVMS Alpha systems only, an OpenVMS-based network operating system compatible with Microsoft networking technology. Allows OpenVMS systems to be file and print servers for Windows desktop users. These users can use Microsoft products and utilities such as Windows Explorer to access file and print resources.
PAGE 326
and satellite booting. For satellite booting, the boot server is part of an OpenVMS Cluster; it includes either a MOP server (for OpenVMS Alpha systems) or a BOOTP/TFTP server (for OpenVMS Integrity server systems), and a disk server for the satellite system disk. See also InfoServer, satellite node. bootstrap See boot. CDSA Common Data Security Architecture. A multiplatform, Open Source security infrastructure.
PAGE 327
See also DECnet-Plus, TCP/IP Services for OpenVMS. DECnet-Plus Formerly known as DECnet/OSI, DECnet-Plus is the networking software that offers the capabilities defined in the DIGITAL Network Architecture (DNA) Phase V protocols. DECnet-Plus provides the newest DECnet features such as extended addressing and downline-load performance enhancements. DECnet-Plus integrates DECnet and OSI protocols and provides a linkage to TCP/IP.
PAGE 328
FOE Foundation Operating Environment. Discontinued operating environment for OpenVMS for Integrity servers available prior to OpenVMS Version 8.4 and since replaced by the Base Operating Environment (BOE). See also BOE, DCOE. Foundation Operating Environment See FOE. Global Workload Manager See gWLM. gWLM HP Integrity Essentials Global Workload Manager. The VSE Management Software application that provides centralized, intelligent, policy-based resource management across multiple HP servers.
PAGE 329
iLO See MP. InfoServer A general-purpose disk storage server (virtual device server). It can make devices available to client systems on the LAN. Client systems can connect to the virtual devices and use them as though they are locally attached devices. OpenVMS systems connected to the same LAN can boot from a virtual drive available from the InfoServer instead of from a local CD or DVD. Insight Power Manager See IPM. instance See OpenVMS instance. Instant Capacity See iCAP.
PAGE 330
See also MOP server. MOP server A computer system using either the LAN Auxiliary Control Process (LANACP) or DECnet software to downline-load systems using the Maintenance Operations Protocol (MOP). Systems loaded include OpenVMS systems, print servers, and LAT servers. See also MOP. MP Management Processor. A utility on HP Integrity servers that provides both local and remote access for controlling the system console, reset/power management, and transfer of control (TOC) capabilities.
PAGE 331
partition A subset of the server hardware that includes processor, memory, and I/O resources on which an operating system can run. This type of partitioning allows a single server to run an operating system independently in each partition with isolation from other partitions. See also cell, nPartition, server complex, virtual partition.
PAGE 332
SIP System Integrated Product. A product provided by HP that can be installed or upgraded as part of the OpenVMS installation or upgrade. SIPs include required products, such as CDSA, Kerberos, and the base kit for Availability Manager, and on OpenVMS Integrity server systems only, WBEM Services for OpenVMS and WBEM Providers for OpenVMS, and optional products such as DECwindows Motif, DECnet-Plus, DECnet Phase IV, TCP/IP Services for OpenVMS. See also layered products.
PAGE 333
server interconnect choices come with compromises such as too many cables or too much to manage, VC reduces the number of network cables and simplifies management while adding the unique ability to wire everything once, then add, replace or recover servers in minutes instead of hours or days. HP Virtual Connect includes the HP 1/10Gb Virtual Connect Ethernet Module and HP 4 Gb Virtual Connect Fibre Channel Module for c-Class BladeSystem, and the HP Virtual Connect Manager. Virtual Connect See VC.
PAGE 334
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. WBEM Providers for OpenVMS Available on OpenVMS Integrity server systems, a product that enables (along with WBEM Services for OpenVMS) HP Systems Insight Manager (HP SIM) management of the operating system.
PAGE 335
Index A Accounts creating after installation or upgrade, 161 ACPI configuration, 204 Advanced Encryption Standard (AES), 327 Advanced Server for OpenVMS defined, 325 AGEN$INCLUDE files returning to system disk, 90 AGEN$PARAMS.
PAGE 336
Boot device paths configuring on FC, 297 Boot flags, 180, 205 Boot options boot devices, 180, 205 changing EFI boot timeout, 208 displaying, 179, 208 during upgrade, 121 setting, 179–182, 205 setting during installation, 60, 74 setting during upgrade, 113 Boot server configuration for InfoServer, 235 defined, 325 Booting automatic, 179, 205, 207 canceling boot device, 180 cell-based servers, 212 conversational, 172, 218 emergency, 175, 220 with default system parameters, 175, 220 without startup and login p
PAGE 337
over the network, 175 with alternate TURBOchannel adapter, 175 with PMAZB TURBOchannel adapter, 171 with PMAZC TURBOchannel adapter, 171 DECamds check for valid versions for system upgrade, 85 DECevent reinstall after upgrade, 161 Decipher, 327 DECnet declaring during installation, 62 installing or upgrading, 30 node address, 43 providing during installation, 79 node name, 43 possible values, 79 providing during installation, 79 DECnet Phase IV configuring, 135 defined, 326 ignoring during startup, 135 inst
PAGE 338
Fibre Channel configuring and booting, 289–300 configuring for booting, 200, 205, 292, 297 in cluster, 300 configuring for dumping, 292, 297 displaying device information, 289, 294, 296 firmware, 289, 295, 296 newly installed disk, 60 newly upgraded system disk, 114 SAN storage array graphic, 299 system disk booting, 292, 300 system disk identification, 57 FIELD account creating after installation or upgrade, 161 Files restoring on the system disk, 29 Firmware revision checking, 26, 27 updating, 26 FOE defi
PAGE 339
help text, 69 HP SIM provisioning, 259 information needed for OpenVMS Cluster, 41–44 Integrity VM guest operating system, 52 layered products, 67, 71 after installation or upgrade, 159 license registration, 66 on target disk, 72 OpenVMS Debugger clients, 150 PCSI, 30 procedure, 55–76 prompts, 54 rebooting system, 81 recording, 25 selecting component options, 69 setting passwords, 60 specifying OpenVMS Cluster configuration, 78 stages of, 45 system information, providing, 60 third-party networking software,
PAGE 340
problems due to login procedure, 177, 221 problems due to startup procedure, 177, 221 Logical CPU defined, 329 Logical names UAFALTERNATE, 178, 223 Login command procedures booting without, 177, 221 errors preventing login, 177, 221 Login welcome message defining, 150 M Magnetic media defined, 21 Maintenance Operations Protocol (MOP) defined, 329 Management Processor (see MP (Management Processor)) MCOE defined, 329 Media defined, 329 Migration support, 41, 95 defined, 329 Minimum startup, 174, 219 Mission
PAGE 341
EXPECTED_VOTES parameter, 165 group number rules for creating, 43 information required for OpenVMS installation, 41–44 installation prompts, 78, 79 supplying ALLOCLASS parameter, 79 installing, 78 installing TDC_RT, 149 label for system disk, 301 local area, 329 migration support, 41, 95 defined, 329 mixed-version support, 95 parameters after upgrade, 165 password rules for creating, 43 quorum adjusting using Availability Manager or DECamds, 100 adjusting using IPC, 100 maintaining during rolling upgrades,
PAGE 342
forgotten, 81, 177, 222 minimum length, 60 setting during installation, 60 Patches finding, installing, removing using distribution media menu option, 39 installing from download, 157 required for existing OpenVMS Cluster members, 42, 97 Secure Delivery, 157 PATHWORKS for OpenVMS (Advanced Server) defined, 331 PCSI and recovery data, 110 installing layered products independently, 161 installing patches using FTP, 157 installing the operating system, 30 upgrading the operating system, 30 Performance Data Col
PAGE 343
swap file size, 163 SYSTARTUP_VMS.
PAGE 344
Secure Delivery and distribution kits, 33, 54, 69, 117, 159 and installing patches, 157 defined, 331 Selecting active console devices, 199 Server complex defined, 331 SET AUTO_ACTION command, 179 SET BOOT command, 209 SET BOOT_OSFLAGS command, 180 SET BOOTDEF_DEV command, 180 SETBOOTBLOCK command, 209 Shadow sets, 92 (see also Volume shadowing) adding to boot and dump device lists, 60, 114 backing up system disk, 305 forming, 131 license required, 128 system parameters, 129 reforming, 162 system disk upgrad
PAGE 345
boot options, 205 booting, 76, 172, 217 after installation, 81 after transferring required save set, 76 checking amount of free space on, 153 creating, 57 defined, 21, 332 initializing, 57, 108 alternative methods, 31, 323 preparing an alternate for backup, 305 preparing for upgrade, 87 preserving, 31, 57, 108 removing system files, 151 restoring, 303 restoring files on, 29 space needed for upgrade, 89 to decompress libraries, 153 specifying during installation, 57 during upgrade, 108 unique volume label re
PAGE 346
User authorization file (see UAF) User Environment Test Package (see UETP) V VC, 23 VGA graphics as console device, 191, 199 Virtual Connect (see VC) virtual console defined, 333 virtual device defined, 333 virtual machine defined, 333 Virtual media (see vMedia (Virtual Media)) Virtual partition defined, 333 vKVM defined, 333 vMedia (Virtual Media), 246 defined, 333 for provisioning setting up, 250 using independently of HP SIM, 279 vms_bcfg command, 207, 208 vms_show command, 208 VMSI18N, 309 VMSINSTAL ut