![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
A triple dollar sign system prompt ($$$) indicates that you are in this restricted DCL environment, as shown in the following example:
$$$ SHOW DEVICE
To exit from the DCL environment and return to the menu, enter the
LOGOUT command.
1.3.6 How the Shutdown Option Works
When you choose the shutdown option (5) from the menu, your system shuts down and you are returned to the console prompt (>>>). The system displays a message similar to the following:
Shutting down the system
SYSTEM SHUTDOWN COMPLETE
Now that you have reviewed key terms, examined hardware and software requirements, and learned how to use the menu system included on the OpenVMS Alpha operating system CD--ROM, you can do the following:
| IF ... | THEN ... |
|---|---|
| you want to install the operating system in an OpenVMS Cluster environment, | go to Chapter 2. |
| you want to install the operating system in a nonclustered environment, | go to Chapter 3. |
| you want to upgrade the operating system in a standalone, Volume Shadowing, or OpenVMS Cluster environment, | go to Chapter 5. |
| you want only to back up or restore your system disk, | go to Appendix B. |
This chapter contains information that you should review before
performing an installation in an OpenVMS Cluster environment.
2.1 For More Information
Before installing the operating system in an OpenVMS Cluster environment, be sure you review any relevant OpenVMS Cluster information, contained in the following documents:
Be sure the following sources of information are available as well:
OpenVMS Alpha Version 7.1 and OpenVMS VAX Version 7.1 provide two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems. These two support types are warranted and migration.
Warranted support means that Digital has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations.
Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Digital has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX or to OpenVMS Alpha. Problem reports submitted against these configurations will be answered by Digital. However, in exceptional cases Digital may request that you move to a warranted configuration as part of answering the problem.
Migration support will help you move to warranted OpenVMS Cluster version mixes with minimal impact on your cluster environment. Table 2-1 shows the level of support provided for all possible version pairings.
| Alpha V6.2--xxx | Alpha V7.0 | Alpha V7.1 | |
|---|---|---|---|
| VAX V6.2-- xxx | WARRANTED | Migration | Migration |
| VAX V7.0 | Migration | WARRANTED | Migration |
| VAX V7.1 | Migration | Migration | WARRANTED |
Note
Digital does not support the use of Version 7.1 with Version 6.1 (or earlier versions) in an OpenVMS Cluster environment. In many cases, mixing Version 7.1 with versions prior to Version 6.2 will successfully operate, but Digital cannot commit to resolving problems experienced with such configurations.
If during the installation you answer YES to the system prompt asking whether your system will be a member of an OpenVMS Cluster, you will need to provide the following information after you boot the system disk:
| Required Information | Explanation |
|---|---|
| Type of configuration | Configuration types (CI, DSSI, SCSI, local area, or mixed-interconnect) are distinguished by the interconnect device that the VAX and Alpha computers in the OpenVMS Cluster use to communicate with one another. |
| DECnet node name and node address | See the network or system manager to obtain the DECnet node name and node address for the computer on which you are installing the OpenVMS Alpha operating system. If you install DECnet-Plus (Phase V) software and do not plan to use DECnet for OpenVMS (Phase IV) addresses, then you do not need to provide this information. |
| Allocation class value |
During the installation procedure, you will be asked for the allocation
class value (ALLOCLASS) of the Alpha computer on which you are
installing the OpenVMS Alpha operating system. For example:
Enter a value for Alpha143 ALLOCLASS parameter:
Refer to OpenVMS Cluster Systems for the rules on specifying allocation class values. Note that in a mixed-interconnect OpenVMS Cluster environment, the allocation class value cannot be zero if the nodes serve DSSI or CI disks. It must be a value from 1 to 255. This is also true for any Alpha computer that is connected to a dual-pathed disk. After you enter the allocation class value, the installation procedure uses it to automatically set the value of the ALLOCLASS system parameter. |
| Whether you want a quorum disk | Refer to OpenVMS Cluster Systems to help you determine whether you want a quorum disk in the cluster. |
| Location of the page and swap files | On a nonclustered system, the page and swap files are on one or more local disks but on a clustered system, the files are on one or more local or clustered disks. See OpenVMS Cluster Systems to help you determine where the page and swap files will be located for the system on which you are installing the OpenVMS Alpha operating system software. |
| Systems that will be MOP¹ servers, disk servers, and tape servers | If you are going to set up either a local area or a mixed-interconnect cluster, you will need to make these determinations. |
| Cluster group number and cluster password |
If you are going to set up a local area cluster or a mixed-interconnect
cluster that is LAN-based, use the following rules to determine the
cluster group number and password:
|
After you have completed all the tasks in this chapter, go to Chapter 3 to begin the installation.
This chapter describes the following tasks:
Note
Before you install the operating system, be sure your computer is running the correct version of PALcode, as described in Section 1.2.4.
At different points during the installation, you must respond to prompts asking you to supply specific information. This manual and the Help text available during the installation procedure tell you how to obtain most of this information and how to make decisions when responding to specific prompts.
However, Digital recommends that you review the following summary
before you begin the installation so that you have an understanding
beforehand of the types of information you will need to provide.
3.1.1 Summary of Prompts
During the installation, the system will prompt you for the following information:
The OpenVMS Alpha Version 7.1 operating system includes procedures that allow you to easily install the operating system using the POLYCENTER Software Installation utility. In console mode, you can boot the operating system CD--ROM to begin the installation procedure. On a system that is already running the OpenVMS Alpha operating system, you can invoke the installation procedure by entering a command at the DCL level.
Depending on whether you are installing the OpenVMS Alpha operating system from the operating system CD--ROM or from a running OpenVMS Alpha system, begin the procedure as follows:
| If installing from ... | Then ... |
|---|---|
| the operating system CD--ROM, | go to Section 3.3 |
| a running OpenVMS Alpha system, | go to Section 3.4 |
3.3 Booting the Operating System CD--ROM
To get started, boot the OpenVMS Alpha operating system CD--ROM either
from your local CD--ROM drive or from a CD--ROM drive connected to the
InfoServer, as described in the following sections.
3.3.1 Booting from the Local Drive
To boot the operating system CD--ROM from the local CD--ROM drive, follow these steps:
BOOT -flags 0,0 source-drive
>>> BOOT -flags 0,0 DKA400
To boot the operating system CD--ROM using the InfoServer, follow these steps:
>>> BOOT -FL 0,0 -FI APB_071 lan-device-name
| Alpha Computer | Ethernet Device |
FDDI Device |
|---|---|---|
| ALPHAbook 1 | EOA0 | -- |
| AlphaServer 400 series | EWA0 | FWA0 |
| AlphaServer 1000 series | ERA0, EWA0 | FRA0 |
| AlphaServer 1000A series | EWA0 | FWA0 |
| AlphaServer 2000 series | ERA0, EWA0 | FRA0 |
| AlphaServer 2100, 2100A series | ERA0, EWA0 | FRA0 |
| AlphaServer 4100 series | EWA0 | FWA0 |
| AlphaServer 8200 series | EXA0, EWA0 | FXA0 |
| AlphaServer 8400 series | EXA0, EWA0 | FXA0 |
| 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 |
>>> BOOT -FL 0,0 -start 0 -FI APB_071 EZA0
Network Initial System Load Function
Version 1.1
FUNCTION FUNCTION
ID
1 - Display Menu
2 - Help
3 - Choose Service
4 - Select Options
5 - Stop
Enter a function ID value:
Enter a function ID value: 3[Return] OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2[Return] Enter a Known Service Name: ALPHA071[Return]
Note: If you boot the OpenVMS Alpha operating system CD--ROM 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 INITIALIZE option, |
do the following:
|
| you previously chose the PRESERVE option, |
do the following:
|
The following sections describe how to create the system disk from the
operating system CD--ROM and from a running system.
3.4.1 Installing from the CD--ROM
After you boot the operating system CD--ROM, choose the install option (1) from the menu displayed on the screen. For example:
OpenVMS Alpha (TM) Operating System, Version V7.1
Copyright (c) 1996 Digital Equipment Corporation. All rights reserved.
Installing required known files...
Configuring devices...
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system
or you can install or upgrade layered products that are included
on the OpenVMS Alpha operating system CD-ROM.
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) Install or upgrade OpenVMS Alpha Version V7.1
2) Display products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Execute DCL commands and procedures
8) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1
After you choose the install option, go to Section 3.4.3 to continue the
procedure.
3.4.2 Installing from a Running System
If you are installing the operating system from an Alpha system that is already running the OpenVMS Alpha operating system, enter the following command from the SYSTEM account and then press the Return key:
$ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL
After you enter the command, go to Section 3.4.3 to continue the
procedure.
3.4.3 Choosing INITIALIZE or PRESERVE
After you choose the install option (if you are installing from the operating system CD--ROM) or start the AXPVMS$PCSI_INSTALL command procedure (if you are installing from a running OpenVMS Alpha system), the system displays the following information and prompts:
***********************************************************
The installation procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
There are two choices for Installation/Upgrade:
INITIALIZE - removes all software and data files that were
previously on the target disk and installs OpenVMS Alpha.
PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk
and retains all other contents of the target disk.
* NOTE: You cannot install OpenVMS Alpha on an existing disk on
which OpenVMS VAX or any other operating system is installed.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE])
Respond to the INITIALIZE or PRESERVE prompt as follows:
| IF ... | THEN ... |
|---|---|
| your system disk is new, |
do the following:
|
| you want to remove all files from an existing system disk, |
do the following:
|
| you want to retain certain files on an existing disk, | press the Return key to accept the default (PRESERVE). |
The procedure next asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example:
You must enter the device name for the target disk on which
OpenVMS Alpha will be installed.
Enter device name for target disk: (? for choices) ?
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DKA100: Online 0
DKA200: Online 0
DKA400: Online wrtlck 0
Enter device name for target disk: (? for choices) DKA200
The system then prompts you for the volume label and asks if the information is correct. You can keep the label already assigned to the disk, accept the default label assigned by the system (ALPHASYS), or specify a different volume label (with a limit of 12 characters that can be letters A--Z, numbers 0--9, dollar signs ($), hyphens (-), or underscores (_)). After you select the volume label and choose to continue by answering Yes to the next prompt, the target disk is initialized and mounted, and page and swap files are created. For example:
DKA200: is now labeled SYSDISK
Do you want to keep this label? (Yes/No) [Yes] NO
Enter volume label for target system disk: [ALPHASYS]
You have chosen to install OpenVMS Alpha on a new disk.
The target system disk, DKA200:, will be initialized.
It will be labeled ALPHASYS.
Any data currently on the target system disk will be lost.
Is this OK? (yes/No) YES
Initializing and mounting target ...
Before you respond to the system prompt asking you to enter a password for the SYSTEM account, note the following:
The following is a sample display:
You must enter a password for the SYSTEM account.
The password must be a minimum of 8 characters in length
and may not exceed 31 characters.
It will be checked and verified.
The system will not accept passwords that can be guessed easily.
Password for SYSTEM account:
Re-enter SYSTEM password for verification:
If you enter the password incorrectly or if the system determines that
the password is too easy for another user to guess, the system displays
an error message and gives you the opportunity to specify a valid
password.
3.4.7 Becoming a Cluster Member
The procedure now asks if your system will be part of a cluster. The display is similar to the following:
Will this system be a member of an OpenVMS Cluster? (Yes/No) [No]
If you answer Yes, you will be asked a series of questions about the
cluster after you boot the new system disk.
3.4.8 Installing Windowing and Network Products
The procedure next allows you to install the DECwindows Motif for OpenVMS Alpha, DECnet-Plus (Phase V), and Digital TCP/IP Services for OpenVMS software that is included with the OpenVMS Alpha operating system.
Note that you can change the default values for these products later in the installation procedure. However, if you want to install DECnet for OpenVMS (Phase IV) software, you must do so separately as a layered product.
The display is similar to the following:
If you want windowing and/or networking you can install any or all
of the following products along with the OpenVMS operating system:
o DECwindows Motif for OpenVMS Alpha
o DECnet-Plus (Phase V)
o Digital 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 all of the default values for this product?"
Do you want to install DECwindows Motif for OpenVMS Alpha V1.2-4?
(Yes/No) [YES]
Beginning with OpenVMS V7.1 DECnet-Plus (Phase V) is provided with the OpenVMS
operating system. Digital strongly recommends that DECnet users
install DECnet-Plus (Phase V). DECnet Phase IV applications are supported
by DECnet-Plus (Phase V).
DECnet Phase IV is available for separate installation. Please see
the "OpenVMS V7.1 Release Notes" for important information
regarding DECnet Phase IV support.
Do you want to install DECnet-Plus (Phase V) V7.1?
(Yes/No) [YES]
Do you want to install Digital TCP/IP Services for OpenVMS V4.0-A?
(Yes/No) [YES] no
If you install the DECnet-Plus for OpenVMS (Phase V) Alpha software but want to use addresses compatible with DECnet for OpenVMS (Phase IV) software, you need to set two parameters, SCSNODE and SCSSYSTEMID, so that your system is identified by name and number in a DECnet or cluster environment. You must specify a DECnet address (which the system uses to calculate the SCSSYSTEMID value). The following is an example of the system display and valid responses:
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.
If you have multiple OpenVMS systems, the SCSNODE on each system
must be unique.
Enter SCSNODE: mynode
If you plan to use DECnet, SCSSYSTEMID must be set based on the
DECnet address.
DECnet Phase IV addresses are in the format
DECnet_area_number.DECnet_node_number
DECnet_area_number is a number between 1 and 63.
DECnet_node_number is a number 1 and 1023.
If you plan to use DECnet WITHOUT Phase IV compatible addresses,
enter 0.0.
Enter DECnet (Phase IV) Address [1.1]: 63.180
SCSSYSTEMID will be set to 64692, calculated as follows:
(DECnet_area_number * 1024) + DECnet_node_number)
At this point in the installation, the procedure asks you for information that is used for providing local time zone support. 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 considered as your default time zone. Usually, this is the time zone in which your system is running. In addition, your system must be correctly configured to use a valid OpenVMS time differential factor (TDF).
6486P001.HTM OSSG Documentation 6-DEC-1996 10:35:08.28
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.