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
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.
AlphaServer 8400/GS140 Galaxy Configuration
AlphaServer 8400 systems can support two or three in-
stances of OpenVMS.
9 slots for:
I/O modules
Memory modules
Processor modules (2 CPUs per module)
Console line for each partition:
Standard UART for first partition
KFE72-DA for each additional partition
Example Configuration 1:
2 partitions, 8 CPUs, 12 GB memory
9 slots allocated as follows:
Two I/O modules
Four processor modules (2 CPUs each)
Three memory modules (4 GB each)
Example Configuration 2:
3 partitions, 8 CPUs, 8 GB memory
9 slots allocated as follows:
Three I/O modules
Four processor modules (2 CPUs each)
Two memory modules (4 GB each)
AlphaServer 8200/GS60/GS60E Galaxy Configura-
tion
AlphaServer 8200, GS60, and GS60E systems can sup-
port one possible OpenVMS Galaxy configuration (two
instances only).
5 slots for:
Two processor modules (two CPUs each)
Two I/O modules
One memory module
The AlphaServer GS140, GS60, GS60E, 8400, and
8200 systems provide a built-in UART for the first con-
sole line. Each additional console requires a module
set.
The only hardware required for Galaxy operation that is
not in the typical AlphaServer GS140, GS60, GS60E,
8400, and 8200 configuration is the KFE72-DA console
subsystem.
The KFE72-DA module set is the set of EISA bus mod-
ules that establish a console port.
XMI Bus Support
The XMI bus is supported only on the first instance (in-
stance 0) of a Galaxy configuration in an AlphaServer
8400 system.
AlphaServer 8400 systems can support only one
DWLM-AA XMI PIU subsystem cage for all XMI devices.
Note that the DWLM-AA takes up considerable space in
the system because an I/O bulkhead is required on the
back of the system to connect all XMI devices to the
system. This allows only two additional DWLPB PCI
PIUs in the system.
EISA Bus Support
The EISA bus is supported only on the first instance
(instance 0) of a Galaxy configuration. Due to the design
of all EISA options, they must always be on instance 0 of
the system. A KFE70 must be used in the first instance
for any EISA devices in the Galaxy system.
All EISA devices must be on instance 0. No EISA de-
vices are supported on any other instance in a Galaxy
system.
A KFE72-DA installed in other instances provides con-
sole connection only and cannot be used for other EISA
devices.
AlphaServer 4100 Configuration
To create an OpenVMS Galaxy on an AlphaServer 4100
system, you must observe the following configuration
and hardware requirements:
Two-Instance Maximum
You can run a maximum of two instances of OpenVMS
on an AlphaServer 4100.
Console Firmware
You must have AlphaServer 4100 console firmware,
which is located on the Alpha Systems Firmware Up-
date Version 5.4 CD–ROM that is included with the
OpenVMS Alpha Version 7.2–1 CD–ROM package.
AlphaServer 4100 Clock
5