HP Galaxy Software Architecture on OpenVMS Alpha, Version 1.1 (12790)
HP Galaxy Software Architecture on OpenVMS Alpha, Version 1.1 SPD 70.44.09
SUPPORTED HARDWARE
AlphaServer ES47, ES80, and GS1280 Galaxy Con-
figuration
OpenVMS Alpha Version 7.3–1 or higher supports the
following maximum configurations on these AlphaServer
systems:
• AlphaServer ES47 M4 (2 instances)
• AlphaServer ES80 M8 (4 instances)
• AlphaServer GS1280 M8 (2 instances)
• AlphaServer GS1280 M16 (4 instances)
• AlphaServer GS1280 M8 (4 instances)
• AlphaServer GS1280 M16 (8 instances)
• AlphaServer GS1280 M32 (8 instances)
• AlphaServer GS1280 M64 (16 instances*)
*Note: M64 requires at least 2 hard partitions with a
maximum of 8 instances each.
Configuration Rules
Note: The AlphaServer ES80 and GS1280 systems can
be configured with one or more hard partitions. Open-
VMS Galaxy can be installed on each hard partition to
configure one or more soft partitions.
Each soft partition must have at least:
• 1 Console interface per CPU
• Each CPU can be a primary (only 1 primary per 2P
duo)
• 1 I/O port (IO7)
• Minimum required memory per CPU
AlphaServer GS80/160/320 Galaxy Configuration
OpenVMS Alpha Version 7.2–1H1 or higher supports
the following maximum configurations on these Al-
phaServer systems:
• AlphaServer GS80 (2 instances)
• AlphaServer GS160 (4 instances)
• AlphaServer GS320 (8 instances)
Configuration Rules
Note: The AlphaServer GS160, and GS320 systems
can be configured with one or more hard partitions.
OpenVMS Galaxy can be installed on each hard par-
tition to configure one or more soft partitions.
Each soft partition must have at least:
• A standard COM1 UART console line
• A master PCI drawer
• An I/O module
• One CPU module
• One memory module
AlphaServer ES40 Galaxy Configuration
AlphaServer ES40 systems can support a maximum of
two instances of OpenVMS.
AlphaServer ES40 Clock
An AlphaServer ES40 has one clock. For an OpenVMS
Galaxy, this means that you cannot run the two in-
stances at different times. Also, the SET TIME com-
mand affects both instances. Note that 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 system, 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.
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.
Storage Controllers
You will need one storage controller (such as a KZPSA)
per instance. For each instance, this can go to a sepa-
rate StorageWorks box or to the same box for running
as a SCSI cluster.
4