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
An AlphaServer 4100 has one clock. For an Open-
VMS Galaxy, this means that you cannot run the two
instances 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
COM1 (upper) is the console port for instance 0.
COM2 (lower) is the console port for instance 1.
Unlike creating an OpenVMS Galaxy on an AlphaServer
8400, you do not need additional hardware for the sec-
ond 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
The four lower PCI slots belong to IOD0, which is the
I/O adapter for instance 0.
The four upper PCI slots belong to IOD1, which is the
I/O adapter for instance 1.
Storage Controllers
You will need two storage controllers (such as KZPSAs).
These can go to separate StorageWorks boxes or to the
same box for running as a SCSI cluster. One controller
each goes in IOD0 and IOD1.
Network Cards
If each instance needs network access, a network card
(such as a DE500) is required for each instance.
One card each goes in IOD0 and IOD1.
Physical Memory
Because OpenVMS Galaxy on an AlphaServer 4100
does not support memory holes, physical memory for
an OpenVMS Galaxy environment must be contiguous.
To achieve this on an AlphaServer 4100, one of the fol-
lowing must be true:
• All memory modules must be the same size (for ex-
ample, 1 GB).
• If two sizes are present, only one module can be a
smaller size. You must put the larger modules into
the lower-numbered slots.
Note: OpenVMS Alpha Version 7.3–2 is the last version
to support OpenVMS Galaxy on the AlphaServer 4100
and ES40.
LICENSING REQUIREMENTS
The Galaxy Software Architecture on OpenVMS (Open-
VMS Galaxy) is a System Integrated Product (SIP): the
OpenVMS Galaxy code is integrated and delivered with
the OpenVMS operating system.
The License Management Facility (LMF) Product Au-
thorization Keys (PAKs) representing OpenVMS Galaxy
licenses allow you to access and use OpenVMS Galaxy
software. For more information about the location of the
PAKs available with OpenVMS Alpha Version 7.3–1 or
higher, see the corresponding Guide to OpenVMS CD-
ROMs.
The following list summarizes OpenVMS Galaxy licens-
ing requirements:
• One OpenVMS Operating System License for a
Galaxy system
• One SMP Extension License for each CPU after the
first CPU
• One OpenVMS Galaxy License for each CPU in a
Galaxy system
• No changes to how HP layered products are li-
censed:
One capacity license per system
One user license per use
The following sections describe these requirements in
more detail.
OpenVMS Operating System License
When an AlphaServer system is configured as an
OpenVMS Galaxy system, there are no changes in how
a system is licensed for the OpenVMS operating sys-
tem.
One OpenVMS Base License is required for the Galaxy
system, plus one SMP Extension License for each CPU
after the first CPU.
OpenVMS Galaxy License
In order to create and run multiple instances, one
OpenVMS Galaxy License is required for each CPU in
a Galaxy system.
License rights for running a single-instance Galaxy on
any Alpha system are provided by the OpenVMS Base
License.
6