Updated: 11 December 1998 |
OpenVMS Alpha Galaxy Guide
Previous | Contents |
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.
This chapter describes the requirements and procedures for creating an
OpenVMS Galaxy computing environment on an AlphaServer 4100.
7.1 Before You Start
Be sure to read the Release Notes chapter in this guide.
To create an OpenVMS Galaxy on an AlphaServer 4100, you must also be familiar with the following configuration and hardware requirements:
You can run a maximum of two instances of OpenVMS on an AlphaServer 4100.
You must have AlphaServer 4100 console firmware Version AS4_G53_75 (Available on the OpenVMS Alpha Version V7.2 kit).
In addition to the console hints in Chapter 5, you should be aware of the following:
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.
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. COM-2 is used for this purpose.
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.
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.
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.
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.
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 following steps:
P00>>>show config |
Console G53_75 OpenVMS PALcode V1.19-16, Digital UNIX PALcode V1.21-24 Module Type Rev Name System Motherboard 0 0000 mthrbrd0 Memory 512 MB EDO 0 0000 mem0 Memory 256 MB EDO 0 0000 mem1 CPU (Uncached) 0 0000 cpu0 CPU (Uncached) 0 0000 cpu1 Bridge (IOD0/IOD1) 600 0021 iod0/iod1 PCI Motherboard 8 0000 saddle0 CPU (Uncached) 0 0000 cpu2 CPU (Uncached) 0 0001 cpu3 Bus 0 iod0 (PCI0) Slot Option Name Type Rev Name 1 PCEB 4828086 0005 pceb0 4 DEC KZPSA 81011 0000 pks1 5 DECchip 21040-AA 21011 0023 tulip1 Bus 1 pceb0 (EISA Bridge connected to iod0, slot 1) Slot Option Name Type Rev Name Bus 0 iod1 (PCI1) Slot Option Name Type Rev Name 1 NCR 53C810 11000 0002 ncr0 2 DECchip 21040-AA 21011 0024 tulip0 3 DEC KZPSA 81011 0000 pks0 |
P00>>> boot -fl 0,0 ewa0 -fi as4_g53_75 UPD> update srm* <power-cycle system> |
P00>>> BOOT -FLAGS 0,80 cd_device_name . . . Bootfile: [GALAXY_FIRM_072.KIT]AS4_G53_75.EXE . . . |
P00>>> create -nv lp_cpu_mask0 1 P00>>> create -nv lp_cpu_mask1 6 P00>>> create -nv lp_io_mask0 10 P00>>> create -nv lp_io_mask1 20 P00>>> create -nv lp_mem_size0 10000000 P00>>> create -nv lp_mem_size1 c000000 P00>>> create -nv lp_count 2 P00>>> create -nv lp_shared_mem_size 4000000 P00>>> set auto_action halt |
P00>>> init P00>>> galaxy |
CPU0 would not join |
IOD0 and IOD1 did not pass the power-up self-test |
P01>>> create -nv lp_cpu_mask0 1 P01>>> create -nv lp_cpu_mask1 6 P01>>> create -nv lp_io_mask0 10 P01>>> create -nv lp_io_mask1 20 P01>>> create -nv lp_mem_size0 10000000 P01>>> create -nv lp_mem_size1 c000000 P01>>> create -nv lp_count 2 P01>>> create -nv lp_shared_mem_size 4000000 P01>>> set auto_action halt |
P00>>> init |
Do you REALLY want to reset the Galaxy (Y/N) |
P00>>> set boot_osflags 12,0 P00>>> set bootdef_dev dka0 P00>>> set boot_reset off !!! must be OFF !!! P00>>> set ewa0_mode twisted P01>>> set boot_osflags 11,0 P01>>> set bootdef_dev dkb200 P01>>> set boot_reset off !!! must be OFF !!! P01>>> set ewa0_mode twisted |
P01>>> boot |
GALAXY=1 |
$ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL |
P00>>> boot |
Add the line GALAXY=1 |
$ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL |
P00>>> set auto_action restart P01>>> set auto_action restart |
P00>>> init |
Do you REALLY want to reset the Galaxy (Y/N) |
Congratulations! You have created an OpenVMS Galaxy.
With OpenVMS Alpha Version 7.2, you can run a single-instance Galaxy on any Alpha platform. This capability allows early adopters to evaluate OpenVMS Galaxy features and, most important, to develop and test Galaxy-aware applications without incurring the expense of setting up a full-scale Galaxy computing environment on a system capable of running multiple instances of OpenVMS (for example, an AlphaServer 8400).
A single-instance Galaxy running on any Alpha system is not an emulator. It is OpenVMS Galaxy code with Galaxy interfaces and underlying operating system functions. All Galaxy APIs are present in a single-instance Galaxy (for example, resource management, shared memory access, event notification, locking for synchronization, and shared memory for global sections).
Any application that is run on a single-instance Galaxy will exercise the identical operating system code on a multiple-instance Galaxy system. This is accomplished by creating the configuration file SYS$SYSTEM:GLX$GCT.BIN, which OpenVMS reads into memory. On a Galaxy platform (for example, an AlphaServer 8400), the console places configuration data in memory for OpenVMS to use. Once the configuration data is in memory, regardless of its origin, OpenVMS boots as a Galaxy instance.
To use the Galaxy Configuration Utility (GCU) to create a single-instance Galaxy on any Alpha System, use the following procedure:
Run the GCU on the OpenVMS Alpha system on which you want to use the single-instance Galaxy.
If the GCU is run on a non-Galaxy system, it will prompt as to whether you want to create a single-instance Galaxy. Click on OK.
The GCU next prompts for the amount of memory to designate as shared memory. Enter any value that is a multiple of 8 MB. Note that you must specify at least 8 MB of shared memory if you want to boot as a Galaxy instance.
When the GCU has displayed the configuration, it will already have written the file GLX$GCT.BIN to the current directory. You can exit the GCU at this point. If you made a mistake or want to alter the configuration, you can close the current model and repeat the process.
To reboot the system as a Galaxy instance:
This chapter contains information that OpenVMS Engineering has found
useful in creating and running OpenVMS Galaxy environments.
9.1 System Auto-Action
Upon system power-up, if the AUTO_ACTION console environment variable is set to BOOT or RESTART for instance 0, then the GALAXY command will automatically be issued and instance 0 will attempt to boot.
The setting of AUTO_ACTION in the console environment variables for the other instances will dictate their behavior upon the issuing of the GALAXY comamnd (whether it is issued automatically or by the user from the console).
To setup your system for this feature, you must set the console
environment variable "AUTO_ACTION" to "RESTART" or "BOOT" on each
instance, and be sure to specify appropriate values for the
BOOT_OSFLAGS and BOOTDEF_DEV environment variables for each instance.
9.2 Changing Console Environment variables
Once you have established the initial set of LP_* environment variables for OpenVMS Galaxy operation and booted your system, changing environment variable values requires that you first re-initialize the system, change the values, and re-initialize again. Wrapping the changes between INITs is required to properly propagate the new values to all partitions.
For AlphaServer 4100 systems no INIT command is needed to start, but you must change these variables on both instances. |
Because AlphaServer 8400 and 8200 systems were designed prior to the Galaxy Software Architecture, OpenVMS Galaxy console firmware and system operations must handle a few restrictions.
The following list briefly describes some things you should be aware of and some things you should avoid doing:
The GLX_INST_TMO SYSGEN parameter:
Each SHARING member ticks a heartbeat cell in shared memory which the other instances watch. If an instance's heartbeat stops ticking for GLX_INST_TMO milliseconds, that instance will be assumed to be dead and removed as a sharing member.
If for example, you CTRL-P a sharing member for longer that GLX_INST_TMO milliseconds, upon issuing a Continue command from the console, the instance will immediately bugcheck with a GLXEXIT bugcheck. This is very similar to the behavior of an OpenVMScluster that would result in a CLUEXIT bugcheck if a cluster member was in a CTRL-P state for longer than RECNXINTERVAL seconds.
The sharing members all use the same value of GLX_INST_TMO. The value
used is the smallest value of any node that has EVER booted into the
Galaxy.
9.5 Turning Galaxy Mode Off
If you want to turn off OpenVMS Galaxy software, change the lp_count environment variable as follows and enter the following commands:
>>> SET LP_COUNT 0 ! Return to monolithic SMP config >>> INIT ! Return to single SMP console >>> B -fl 0,1 device ! Stop at SYSBOOT SYSBOOT> SET GALAXY 0 SYSBOOT> CONTINUE |
Previous | Next | Contents |
Copyright © Compaq Computer Corporation 1998. All rights reserved. Legal |
6512PRO_004.HTML
|