HP OpenVMS Alpha Partitioning and Galaxy Guide |
Creating an OpenVMS Galaxy on an AlphaServer 4100... |
|
|
|
| |
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 that is available on the OpenVMS Version 7.3 CD-ROM.
Console commands
In addition to the console hints in Creating an OpenVMS Galaxy on an AlphaServer 8400 System, note the following:
AlphaServer 4100 clock
An AlphaServer 4100 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. 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 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
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 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 following must be true:
To create an OpenVMS Galaxy on an AlphaServer 4100 system, perform the steps in the following sections.
|
|
|