Changing the partition setup may affect console environment
variable values; check to ensure they are correct. To ensure that
AUTOGEN reboots correctly when it needs to reboot the system after
an initial installation and after a system failure or operator-requested
reboot, set the BOOTDEF_DEV and BOOT_OSFLAGS variables on each of
your Galaxy consoles before booting.
When the OpenVMS system is booted with Galaxy enabled, each
soft partition can run a separate instance of the operating system
as a Galaxy member.
At a point in the boot process, the instance will attempt
to join the Galaxy configuration. If no Galaxy exists, the attempt
triggers the creation of a Galaxy, generating a new Galaxy ID and
initializing the structures in shared memory that all members in
the resulting Galaxy will use. If a Galaxy does exist, the instance
joins, connecting to the shared memory constructs and, through them,
to the other member instances.
For a Galaxy instance on the ES47/ES80/GS1280:
There can be only one primary
CPU in any 2P building block.
Either CPU of a 2P building
block can be a primary in a Galaxy instance.
Each Galaxy requires an IO
port.
Up to 8 Galaxy partitions
are supported per hard partition.
When you have correctly installed the Galaxy firmware and
configured the consoles, you can boot the initial Galaxy environment
as follows:
For each Galaxy instance:
P00>>> B -FL 0,1 DKA100 // or whatever your boot device is.
SYSBOOT> SET GALAXY 1
SYSBOOT> CONTINUE
Congratulations! You have created an OpenVMS Galaxy.