skip book previous and next navigation links
go up to top of book: HP OpenVMS Alpha Partitioning and Galaxy Guide HP OpenVMS Alpha Partitioning and Galaxy Guide
go to beginning of chapter: Creating an OpenVMS Galaxy on an AlphaServer ES40... Creating an OpenVMS Galaxy on an AlphaServer ES40...
 
go to next page: Step 1: Confirm the AlphaServer ES40 ConfigurationStep 1: Confirm the AlphaServer ES40 Configuration
end of book navigation links

Before You Start  



You must be familiar with the following AlphaServer ES40 configuration and hardware requirements:

Two-instance maximum

You can run a maximum of two instances of OpenVMS on an AlphaServer ES40.

Console firmware

To create an OpenVMS Galaxy environment on AlphaServer ES40 systems, you must download the latest version of the V6.2 console firmware from the following location:

http://ftp.digital.com/pub/DEC/Alpha/firmware/
AlphaServer ES40 clock

An AlphaServer ES40 has one clock. For an OpenVMS Galaxy, this means that you cannot run the two instances at different times. Also, the SET TIME command affects both instances. This may not become evident until a number of hours have passed.

Console ports

On a rack-mounted system: COM1 (lower) is the console port for instance 0. COM2 (upper) is the console port for instance 1.

On a pedestal system: COM1 (left) is the console port for instance 0. COM2 (right) is the console port for instance 1.

Unlike creating an OpenVMS Galaxy on an AlphaServer 8400, you do not need additional hardware for the second console. COM2 is used for this purpose.

CPUs

CPU0 must be the primary for instance 0. CPU1 must be the primary for instance 1. CPUs 2 and 3 are optional secondary CPUs that can be migrated.

For an example of the CPU environment variable settings on an AlphaServer ES40, see Step 4: Set the Environment Variables.

I/O adapters

On a rack-mounted system: PCI hose 0 (PCI0) belongs to instance 0 (upper 4 PCI slots) PCI hose 1 (PCI1) belongs to instance 1 (lower 6 PCI slots)

On a pedestal system: PCI hose 0 (PCI0) belongs to instance 0 (right-hand slots) PCI hose 1 (PCI1) belongs to instance 1 (left-hand slots)

Note that PCI0 contains an embedded ISA controller.

To see an I/O adapter configuration example, see Step 1: Confirm the AlphaServer ES40 Configuration.

Storage controllers

You need one storage controller (such as a KZPSA) per instance. For each instance, this can go to a separate StorageWorks box or to the same box for running as a SCSI cluster.

Network cards

If each instance needs network access, a network card (such as a DE600) is required for each instance.

One card each goes in PCI0 and PCI1.

Memory Granularity Restrictions

Private memory must start on a 64-MB boundary.

Shared memory must start on an 8-MB boundary.

Instance 0 must have a multiple of 64 MB.


 
go to next page: Step 1: Confirm the AlphaServer ES40 ConfigurationStep 1: Confirm the AlphaServer ES40 Configuration