skip book previous and next navigation links
go up to top of book: HP OpenVMS Alpha Partitioning and Galaxy Guide HP OpenVMS Alpha Partitioning and Galaxy Guide
go to beginning of chapter: OpenVMS Galaxy Concepts OpenVMS Galaxy Concepts
go to previous page: CD Drive Recommendation CD Drive Recommendation
go to next page: Security Considerations in an OpenVMS Galaxy Computing EnvironmentSecurity Considerations in an OpenVMS Galaxy Computing Environment
end of book navigation links

Clustering with Galaxy  



This section contains information on clustering instances with other instances in an OpenVMS Galaxy computing environment or with non-Galaxy OpenVMS clusters.

For information about OpenVMS Galaxy licensing requirements that apply to clustering instances, see the OpenVMS License Management Utility Manual.

Becoming an OpenVMS Galaxy Instance  

When you are installing OpenVMS Alpha Version 7.3, the OpenVMS installation dialog asks questions about OpenVMS Cluster and OpenVMS Galaxy instances.

If you answered "Yes" to the question

Will this system be a member of an OpenVMS cluster? (Yes/No)
and you answered "Yes" to the question
Will this system be an instance in an OpenVMS Galaxy? (Yes/No)
the following information is displayed:
For compatibility with an OpenVMS Galaxy, any systems in the OpenVMS
cluster which are running versions of OpenVMS prior to V7.1-2 must 
have a remedial kit installed. The appropriate kit from the following
list must be installed on all system disks used by these systems.
(Later versions of these remedial kits may be used if available.)
 
        Alpha V7.1 and V7.1-1xx         ALPSYSB02_071
        Alpha V6.2 and V6.2-1xx         ALPSYSB02_062
 
        VAX V7.1                        VAXSYSB01_071
        VAX V6.2                        VAXSYSB01_062
For more information, see the HP OpenVMS Alpha Version 7.3-2 Upgrade and Installation Manual.

SCSI Cluster Considerations  

This section summarizes information about SCSI device naming for OpenVMS Galaxy computing environments. For more complete information about OpenVMS Cluster device naming, see the OpenVMS Cluster Systems manual.

If you are creating an OpenVMS Galaxy with shared SCSI buses, you must note the following:

For OpenVMS to give the SCSI devices the same name on each instance correctly, you need to use the device-naming feature of OpenVMS.

For example, assume that you have the following adapters on your system when you enter the SHOW CONFIG command:

PKA0 (embedded SCSI for CDROM)
PKB0 (UltraSCSI controller KZPxxx)
PKC0 (UltraSCSI controller)
When you make this system a two-instance Galaxy, your hardware looks like the following:
Instance 0
PKA0  (UltraSCSI controller)
 
Instance 1
PKA0  (embedded SCSI for CDROM)
PKB0  (UltraSCSI controller)
Your shared SCSI is connected from PKA0 on instance 0 to PKB0 on instance 1.

If you initialize the system with the LP_COUNT environment variable set to 0, you will not be able to boot OpenVMS on the system unless the SYSGEN parameter STARTUP_P1 is set to MINIMUM.

This is because, with the LP_COUNT variable set to 0, you now have PKB connected to PKC, and the SCSI device-naming that was set up for initializing with multiple partitions is not correct for initializing with the LP_COUNT variable set to 0.

During the device configuration that occurs during boot, OpenVMS notices that PKA0 and PKB0 are connected together. OpenVMS expects that each device has the same allocation class and names, but in this case, they do not.

The device naming that was set up for the two-instance Galaxy does not function correctly because the console naming of the controllers has changed.


go to previous page: CD Drive Recommendation CD Drive Recommendation
go to next page: Security Considerations in an OpenVMS Galaxy Computing EnvironmentSecurity Considerations in an OpenVMS Galaxy Computing Environment