Partitioning for the AlphaServer GS80/160/320

If both a Table of Contents and Search form are not displayed in separate frames along with this one, you may wish to redisplay this book in a frameset, beginning with the first page.

HP OpenVMS Alpha Partitioning and Galaxy Guide

Managing Workloads With Partitions

Partitioning for the AlphaServer ES47/ES80/GS1280

OpenVMS Galaxy Support

Partitioning forthe AlphaServer GS80/160/320

Each hard partition requires the following:

A standard COM1 UART console linefor each partition.

A PCI drawer for each partition.

An I/O module per partition.

At least one CPU module per partition.

At least one memory module per partition.

Memory options should be selected in the context of an application'ssensitivity to memory bandwidth and memory capacity, and the numberof hardware partitions. This determines the number of memory base modulesand upgrades needed. The total capacity required determines thesize of the arrays to be chosen.

Memory modules should be configured in powers of 2: That is,0, 1, 2, or 4 base modules in a QBB. Upgrades should also be installedin powers of 2: 0, 1, 2, or 4 base modules in a QBB.

The following sections describe three hard partition configurationexamples:

Example configuration 1 has four QBBsand four hard partitions. Each hard partition contains one QBB.

Example configuration 2 has four QBBs and two hardpartitions. Each hard partition contains two QBBs.

Example configuration 3 has four QBBs and two hardpartitions. One partition contains one QBB, and the other containsthree QBBs.

For more information about the partitioning procedures describedin this section, see the AlphaServer GS80/160/320 FirmwareReference Manual.

Hard Partition ConfigurationExample 1

The example configuration in Configuration Example 1 uses four QBBs to configure four hard partitions.Each hard partition contains one QBB.

Figure 5 Configuration Example 1
tbs

To configure an AlphaServer GS160 system with four hard partitions,enter the following sequence of SCM commands.

From the SCM console, enter the following settings for the hp NVRAMvariables. Note that the values are bit masks.

SCM_E0> power off -all SCM_E0> set hp_count 4SCM_E0> set hp_qbb_mask0 1SCM_E0> set hp_qbb_mask1 2SCM_E0> set hp_qbb_mask2 4SCM_E0> set hp_qbb_mask3 8SCM_E0> set hp_qbb_mask4 0SCM_E0> set hp_qbb_mask5 0SCM_E0> set hp_qbb_mask6 0SCM_E0> set hp_qbb_mask7 0 SCM_E0> power on -all

You can also power on or off individual hard partitions. Forexample, using this configuration, enter:

SCM_E0> power off -allSCM_E0> set hp_count 4SCM_E0> set hp_qbb_mask0 1SCM_E0> set hp_qbb_mask1 2SCM_E0> set hp_qbb_mask2 4SCM_E0> set hp_qbb_mask3 8SCM_E0> set hp_qbb_mask4 0SCM_E0> set hp_qbb_mask5 0SCM_E0> set hp_qbb_mask6 0SCM_E0> set hp_qbb_mask7 0SCM_E0> power on -partition 0SCM_E0> power on -partition 1SCM_E0> power on -partition 2SCM_E0> power on -partition 3

During the powering up phases of each hard partition, statusinformation is displayed showing how the partitions are coming online. Pay close attention to this information and confirm that thereare no failures during this process.

As each hard partition comes on line, you can start workingwith that hard partition's console device. Also note, that dependingon the setting of the NVRAM variable AUTO_QUIT_SCM, each hard partition'sconsole comes on line in either the SCM or SRM console mode.

From each hard partition's console, enter into the SRM consoleand configure any console variables specific to that hard partition.After that, boot OpenVMS in each hard partition according to standardOpenVMS procedures. For example:

The typical hard partition 0 SRM console settings for OpenVMSare:

P00>>>show bootdef_devbootdef_dev             dkb0.0.0.3.0P00>>>show boot_osflagsboot_osflags            0,0P00>>>show os_typeos_type                 OpenVMS

The typical hard partition 1 SRM console settings for OpenVMSare:

P00>>>show bootdef_devbootdef_dev             dkb0.0.0.3.0P00>>>show boot_osflagsboot_osflags            1,0P00>>>show os_typeos_type                 OpenVMS

The typical hard partition 2 SRM console settings for OpenVMSare:

P00>>>show bootdef_devbootdef_dev             dkb0.0.0.3.0P00>>>show boot_osflagsboot_osflags            2,1P00>>>show os_typeos_type                 OpenVMS

The typical hard partition 3 SRM console settings for Tru64UNIX are:

P00>>>show bootdef_devbootdef_dev             dka0.0.0.1.16P00>>>show boot_osflagsboot_osflags            AP00>>>show os_typeos_type                 UNIX

Hard Partition ConfigurationExample 2

The example configuration in Configuration Example 2 uses four QBBs to configure two hard partitions.Each hard partition contains two QBBs.

Figure 6 Configuration Example 2
tbs

To configure an AlphaServer GS160 with two hard partitions,perform the following sequence of SCM commands.

From the SCM console, enter the following settings for the hp NVRAMvariables:

SCM_E0> power off -all SCM_E0> set hp_count 2SCM_E0> set hp_qbb_mask0 3SCM_E0> set hp_qbb_mask1 cSCM_E0> set hp_qbb_mask2 0SCM_E0> set hp_qbb_mask3 0SCM_E0> set hp_qbb_mask4 0SCM_E0> set hp_qbb_mask5 0SCM_E0> set hp_qbb_mask6 0SCM_E0> set hp_qbb_mask7 0 SCM_E0> power on -all

As each hard partition comes on line, you can start workingwith that hard partition's console device.

From each hard partition's console, you enter, as in configurationexample 1, into the SRM console, and configure any console variablesspecific to that hard partition, and then boot OpenVMS in each hard partition.

Hard Partition ConfigurationExample 3

As in configuration example 2, the configuration in Configuration Example 3 uses four QBBs to configuretwo hard partitions; the only difference is the changing of thenumber of QBBs per hard partition.

Figure 7 Configuration Example 3
tbs

To configure an AlphaServer GS160 system, perform the followingsequence of SCM commands.

From the SCM console, enter the following settings for the hp NVRAMvariables:

SCM_E0> power off -all SCM_E0> set hp_count 2SCM_E0> set hp_qbb_mask0 7SCM_E0> set hp_qbb_mask1 8SCM_E0> set hp_qbb_mask2 0SCM_E0> set hp_qbb_mask3 0SCM_E0> set hp_qbb_mask4 0SCM_E0> set hp_qbb_mask5 0SCM_E0> set hp_qbb_mask6 0SCM_E0> set hp_qbb_mask7 0 SCM_E0> power on -all

As in the other examples, as each hard partition comes online, you can start working with that hard partition's console device.

Updating ConsoleFirmware on AlphaServer GS80/160/320 Systems

To update the SRM console firmware on a system that is hardpartitioned, you must do so separately for each hard partition.There is no way to update all of the firmware on each partitionat one time.

Partitioning for the AlphaServer ES47/ES80/GS1280

OpenVMS Galaxy Support