OpenVMS Alpha Galaxy Guide

Updated: 11 December 1998

OpenVMS Alpha Galaxy Guide

Contents

5.7 Step 7: Start the Secondary Console Devices

If the KFE72-DA was ever configured for Windows-NT, it probably expects to find the video board and will hang if one is not present. This is a common occurrence when configuring an OpenVMS Galaxy. A console command can be used to set the mode of operation as follows:

P00>>> SET CONSOLE SERIAL

When you issue this command to the primary console prior to initializing the secondary consoles, the setting will be propagated to the secondary console hardware.

If you decide to use the Ethernet port, you may need to inform the console of which media type and connection you intend to use: AUI, UDP, or Twisted-Pair. The console and operating system will determine which to use, but you can assign a specific media type using the following commands:

P00>>> SHOW NETWORK P00>>> SET EWA0_MODE TWISTED

The first command displays a list of available network devices. The second command establishes the default media type for the specified device (EWA0 in this example). This should be done for all Ethernet devices prior to initializing the secondary consoles.

Once you have set your console mode and network media types (if used) you should re-initialize the system to ensure that the current settings are saved. If you have already defined your Galaxy partitions, you can initialize now. If you have not defined your Galaxy partitions, you should defer initialization until later.

If you are ready to initialize the system, enter:

P00>>> INIT

You should see the primary console respond with its usual power-up-self-test (POST) report. This could take up to two minutes. If you have properly defined the Galaxy partitions, only the I/O devices associated with the primary partition will be visible.

To verify that partitioning has occurred, enter:

P00>>> SHOW DEVICE or P00>>> SHOW NETWORK

To initialize the secondary console, enter:

P00>>> LPINIT

The console displays the following:

Partition 0: Primary CPU = 0 Partition 1: Primary CPU = 2 Partition 0: Memory Base = 000000000 Size = 010000000 Partition 1: Memory Base = 010000000 Size = 010000000 Shared Memory Base = 020000000 Size = 010000000 LP Configuration Tree = 12c000 starting cpu 1 in Partition 1 at address 01000c001 starting cpu 2 in Partition 1 at address 01000c001 starting cpu 3 in Partition 1 at address 01000c001 starting cpu 4 in Partition 1 at address 01000c001 starting cpu 5 in Partition 1 at address 01000c001 starting cpu 6 in Partition 1 at address 01000c001 starting cpu 7 in Partition 1 at address 01000c001 P00>>>

This command must be entered from the primary Galaxy console. If the Galaxy partitions have been properly defined, and hardware resources have been properly configured, you should see the primary console start the processors assigned to each secondary partition. Each of the secondary consoles should initialize within about two minutes.

If one or more consoles fails to initialize, you should double-check your hardware installation, Galaxy partition definitions, and hardware assignments.

For more information about OpenVMS console restrictions and hints, see Chapter 9.

5.8 Step 8: Boot the OpenVMS Galaxy

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.

Chapter 6
Creating an OpenVMS Galaxy on an AlphaServer 8200

This chapter describes how to create an OpenVMS Galaxy computing environment on an AlphaServer 8200.

6.1 Step 1: Choose a Configuration and Determine Hardware Requirements

Quick Summary of an AlphaServer 8200 Galaxy Configuration

Only one possible configuration.

Two instances only
5 slots for:
- Two processor modules (two CPUs each)
- Two I/O modules
- One memory module

6.2 Step 2: Set Up Galaxy Hardware

When you have acquired the hardware required for your configuration, follow the procedures in this section to assemble it.

6.2.1 Installing the KFE72-DA Console Subsystem Hardware

The KFE72-DA is the set of EISA-bus modules that establishes an additional console port. One KFE72-DA module set is required per secondary partition.

The KFE72-DA contains three EISA modules that provide:

Two COM ports
A keyboard interface
A mouse interface
A small speaker
An Ethernet port.

The COM-1 port is used for the console serial line. The Ethernet port can be used as a network connection or it can be terminated. The mouse and keyboard ports are not used.

The KFE72-DA must be plugged into the bottom three EISA slots. For the AlphaServer 8200 this requires that you attach a Hose from your I/O module to a DWLPB PCI card cage. The KFE72-DA module set must be installed in slots 0, 1, and 2 of the card cage. The KFE72's SIO (a.k.a. Bridge) module enables the EISA slots which are part of the combination PCI/EISA backplane. The other two modules known as the "Data Port Module" and "Beeper97" go in slots 1 and 2 respectively.

6.2.2 Using a Terminal Server

You may want to bring your console lines together using a terminal server. For example, use a DECserver200 to allow reverse-LAT access to each console over the network. While this is not strictly required, it greatly simplifies OpenVMS Galaxy configuration management. Refer to the appropriate product documentation for details about configuring a LAT Server or other terminal concentrator.

6.2.3 Recommendations for Configuring Console Subsystems

Each additional console requires a separate KFE72-DA subsystem installed in a separate DWLPB card cage with a hose connecting it to a separate I/O module of type KFTIA or KFTHA. If you are using a KFTIA, it must be in slot 8.

Additional KFTIA I/O module must be in the next lower slot or slots, with KFTHA I/O module in the next lower slot or slots after that.

You can use any combination of these two I/O modules as long as you follow this slot assignment rule.

The AlphaServer 8200 supports a maximum of three I/O modules. Attempting to configure more than three is unsupported.

When configuring a console subsystem, the IO hose connecting the IO Processor and DWLPB card cage must be plugged into the lowest hose port. Not just the lowest available hose port, but the absolute first hose port; the one closest to the top of the module.

KFE72-DA modules must occupy slots 0, 1, and 2 of the DWLPB card cage.

The console serial line is connected with an H8571-J connector adapter that plugs into the right hand serial line port when viewed from the rear of the machine. This is COM-1.

6.2.4 Installing EISA Devices

Plug-in EISA devices can only be configured in partition 0. After installing EISA devices, the console will issue a message requesting that you run the EISA Configuration Utility (ECU).

Run the ECU as follows:

Shut down all OpenVMS Galaxy instances.
Be sure your floppy disk drive is properly connected to the primary partitions hardware. Typically the drive can be cabled into the Connector Module ("Beeper" part number 54-25133-01) in PCI slot 2.
Insert the diskette containing the ECU image.

Issue the following commands from the primary console:

P00>>> SET ARC_ENABLE ON P00>>> INITIALIZE P00>>> RUNECU

Follow the procedures outlined by the ECU and exit when done.
P00>>> boot
$ @SYS$SYSTEM:SHUTDOWN
P00>>> SET ARC_ENABLE OFF
P00>>> INITIALIZE
P00>>> LPINIT
Reboot the OpenVMS Galaxy

There are two versions of the ECU, one that runs on a graphics terminal and another that runs on character cell terminals. Both versions are on the diskette, and the console determines which one to run. For OpenVMS Galaxy systems, the primary console will always be a serial device with a character cell terminal.

If the ECU is not run, OpenVMS will display the following message:

%SYSTEM-I-NOCONFIGDATA, IRQ Configuration data for EISA slot xxx was not found, please run the ECU and reboot.

If you ignore this message, the system will boot, but the plug-in EISA devices will be ignored.

Once you have configured and set up the OpenVMS Galaxy hardware as described in in the previous sections, perform the following steps to install and boot OpenVMS Galaxy instances.

6.3 Step 3: Create A System Disk

Decide whether to use a system disk per instance or to use a cluster common disk

A new SECURITY.EXE is required for all cluster members running a version prior to OpenVMS Version 7.1-2 that share the same VMS$OBJECTS.DAT with Galaxy instances. (For more information, see Section 1.4.)

6.4 Step 4: Install OpenVMS Alpha Version 7.2

No special installation procedures are required to run OpenVMS Galaxy software. Galaxy functionality is included in the base operating system and can be enabled or disabled using the console command and system parameter values described later in this chapter.

For more information about installing the OpenVMS Alpha operating system, see the OpenVMS Alpha Version 7.2 Upgrade and Installation Manual.

6.4.1 OpenVMS Galaxy Licensing Information

See Chapter 4.

6.5 Step 5: Upgrade the Firmware

Creating an OpenVMS Galaxy environment on an AlphaServer 8200 requires a firmware upgrade to each processor module. If you use these modules again in a non-Galaxy configuration, you will need to reinstall the previous firmware. It is a good practice to have a current firmware CD on hand.

It saves some time if you install ALL processor modules you intend to use and update them at the same time. The AlphaServer 8200 requires that you use the same firmware on all processor boards. If you need to upgrade a board at a later time, you must:

Remove all boards that are not at the same firmware revision level
Update the older boards
Reinstall the remaining boards

To upgrade your firmware, the system must be powered on, running the standard console (that is, the lp_count environment variable---if you have established one---must be set to zero).

Note that the OpenVMS Galaxy firmware (GALAXY_FIRM_072.KIT) is located on the Alpha CD1 for OpenVMS Version 7.2.

Use the following commands:

P00>>> BOOT -FLAGS 0,80 cd_device_name . . . Bootfile: [GALAXY_FIRM_072.KIT]AS8_G53_27.EXE . . .

When the firmware update has completed, you must rebuild the EEPROM format on each even-numbered processor module as follows:

P00>>> SET CPU 0 P00>>> BUILD -E P00>>> SET CPU 2 P00>>> BUILD -E . . . P00>>>INIT

Note that a MOP bootable version of the firmware update,
[GALAXY_FIRM_072.KIT]AS8_G53_27.SYS, is also on the CD.

6.6 Step 6: Set Environment Variables

When you have upgraded the firmware on all of your processor modules, you can create the Galaxy-specific environment variables as shown in the following example. This example assumes you are configuring a 2 instance, 8 CPU, 1 Gigabyte OpenVMS Galaxy computing environment.

P00>>> create -nv lp_count 2 P00>>> create -nv lp_cpu_mask0 1 P00>>> create -nv lp_cpu_mask1 fe P00>>> create -nv lp_io_mask0 100 P00>>> create -nv lp_io_mask1 80 P00>>> create -nv lp_mem_size0 10000000 P00>>> create -nv lp_mem_size1 10000000 P00>>> create -nv lp_shared_mem_size 20000000 P00>>> init

Once these variables have been created, you can use console SET commands to manipulate them. These variables need only be created on processor 0 as shown.

The following descriptions give detailed information about each environment variable.

LP_COUNT

If set to zero, the system will boot a traditional SMP configuration only. Galaxy console mode is OFF.

If set to a non-zero value, the Galaxy features will be used, and the Galaxy variables will be interpreted. The exact value of lp_count represents the number of Galaxy partitions the console should expect. Currently, this number must be 0 or 2.

Note that if you assign resources for three partitions and set this variable to two, the remaining resources will be left unassigned. You may also create the variables for the maximum number of partitions ahead of time and simply not assign resources to them (set them to non-zero values) until needed.

LP_CPU_MASK partition number

This bit-mask determines which CPUs are to be initially assigned to the specified Galaxy partition number. The AlphaServer 8200 console chooses the first even-numbered CPU as its primary. Keep this in mind when assigning the resources (in other words, do not assign only an odd-numbered CPU to a partition).

LP_IO_MASK partition number

These variables assign IO processors by slot number to each instance.

100 represents the I/O module in slot 8
80 represents the I/O module in slot 7

These are the only valid assignments for the AlphaServer 8200.

You can assign more than one I/O module to an instance using these masks, but each Galaxy instance requires at least one I/O module.

LP_MEM_SIZE partition number

These variables allocate a specific amount of private memory for the specified instance. It is imperative that you create these variables using proper values for the amount of memory in your system and the desired assignments for each instance. Refer to Table 6-1 for common values.

See also the shared memory variable on the following line.

LP_SHARED_MEM_SIZE

This variable allocates memory for use as shared memory. Refer to Table 6-1 for common values.

Tips

Shared memory must be assigned in multiples of 8 megabytes and all values are expressed in hexadecimal bytes.

You can define only the amount of shared memory to use, and leave the other lp_mem_size variables undefined. This will cause the console to allocate the shared memory from the high address space, and split the remaining memory equally among the number of partitions specified by the lp_count variable. If you also explicitly assign memory to a specific partition using a lp_mem_size variable, but leave other partition memory assignments undefined, the console will again assign the memory fragments for shared memory and any partitions with explicit assignments, then split and assign the remaining memory to any remaining partitions not having explicit memory assignments.

BOOTDEF_DEV and BOOT_OSFLAGS variables

You should set these variables on each of your Galaxy consoles prior to booting to ensure that AUTOGEN reboots correctly when it needs to reboot the system after an initial installation and after a system crash or operator requested reboot.

6.6.1 Galaxy Environment Variables Example

P00>>> SHOW LP* lp_count 2 lp_shared_mem_size 20000000 (512 MB) lp_mem_size0 10000000 (256 MB) lp_mem_size1 10000000 (256 MB) lp_cpu_mask0 1 (CPU 0) lp_cpu_mask1 fe (CPUs 1-7) lp_io_mask0 100 (I/O module in slot 8) lp_io_mask1 80 (I/O module in slot 7) P00>>

6.6.2 Useful Integers

Table 6-1 lists common values for Galaxy environment variables. All values are expressed in hexadecimal bytes.

Table 6-1 Table of Useful Integers
1 Megabytes 0x 10 0000

2 Megabytes 0x 20 0000

4 Megabytes 0x 40 0000

8 Megabytes 0x 80 0000

16 Megabytes 0x 100 0000

32 Megabytes 0x 200 0000

64 Megabytes 0x 400 0000

128 Megabytes 0x 800 0000

256 Megabytes 0x 1000 0000

448 Megabytes 0x1C00 0000

512 Megabytes 0x 2000 0000

1 Gigabyte 0x 4000 0000

2 Gigabytes 0x 8000 0000

4 Gigabytes 0x 1 0000 0000

8 Gigabytes 0x 2 0000 0000

16 Gigabytes 0x 4 0000 0000

32 Gigabytes 0x 8 0000 0000

64 Gigabytes 0x 10 0000 0000

128 Gigabytes 0x 20 0000 0000

256 Gigabytes 0x 40 0000 0000

512 Gigabytes 0x 80 0000 0000

1 Terabyte 0x 100 0000 0000

**Table 6-1 Table of Useful Integers**
1 Megabytes	0x 10 0000
2 Megabytes	0x 20 0000
4 Megabytes	0x 40 0000
8 Megabytes	0x 80 0000
16 Megabytes	0x 100 0000
32 Megabytes	0x 200 0000
64 Megabytes	0x 400 0000
128 Megabytes	0x 800 0000
256 Megabytes	0x 1000 0000
448 Megabytes	0x1C00 0000
512 Megabytes	0x 2000 0000
1 Gigabyte	0x 4000 0000
2 Gigabytes	0x 8000 0000
4 Gigabytes	0x 1 0000 0000
8 Gigabytes	0x 2 0000 0000
16 Gigabytes	0x 4 0000 0000
32 Gigabytes	0x 8 0000 0000
64 Gigabytes	0x 10 0000 0000
128 Gigabytes	0x 20 0000 0000
256 Gigabytes	0x 40 0000 0000
512 Gigabytes	0x 80 0000 0000
1 Terabyte	0x 100 0000 0000

6.7 Step 7: Start the Secondary Console Devices

P00>>> SET CONSOLE SERIAL

When you issue this command to the primary console prior to initializing the secondary consoles, the setting will be propagated to the secondary console hardware.

P00>>> SHOW NETWORK P00>>> SET EWA0_MODE TWISTED

If you are ready to initialize the system, enter:

P00>>> INIT

To verify that partitioning has occurred, enter:

P00>>> SHOW DEVICE or P00>>> SHOW NETWORK

To initialize the secondary console, enter:

P00>>> LPINIT

The console displays the following:

If one or more consoles fails to initialize, you should double-check your hardware installation, Galaxy partition definitions, and hardware assignments.

For more information about OpenVMS console restrictions and hints, see Chapter 9.

Contents

Legal

 
6512PRO_003.HTML

OpenVMS Alpha Galaxy Guide

5.7 Step 7: Start the Secondary Console Devices

Chapter 6Creating an OpenVMS Galaxy on an AlphaServer 8200

6.2 Step 2: Set Up Galaxy Hardware

Chapter 6
Creating an OpenVMS Galaxy on an AlphaServer 8200