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: Creating an OpenVMS Galaxy on an AlphaServer 8200... Creating an OpenVMS Galaxy on an AlphaServer 8200...
go to previous page: Step 6: Set the Environment Variables Step 6: Set the Environment Variables
go to next page: Step 8: Boot the OpenVMS GalaxyStep 8: Boot the OpenVMS Galaxy
end of book navigation links

Step 7: Start the Secondary Console Device  



If the KFE72-DA was configured for Windows NT, it expects to find the video board and hangs if one is not present. This is a common occurrence when configuring an OpenVMS Galaxy. Use this console command to set the mode of operation as follows:
P08>>> SET CONSOLE SERIAL
When you enter this command to the primary console before initializing the secondary console, the setting is 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 determines which to use, but you can assign a specific media type by entering the following commands:

P08>>> SHOW NETWORK
 
P08>>> 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 before initializing the secondary console.

Once you have set your console mode and network media types (if used), reinitialize 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, defer initialization until later.

If you are ready to initialize the system, enter:

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

To verify that partitioning has occurred, enter:

P08>>> SHOW DEVICE
or
P08>>> SHOW NETWORK
To initialize the secondary console, enter:
P08>>> 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
 
P08>>>
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 the secondary partition. The secondary console should initialize within 2 minutes.

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

For more information about OpenVMS console restrictions and hints, see OpenVMS Galaxy Tips and Techniques.


go to previous page: Step 6: Set the Environment Variables Step 6: Set the Environment Variables
go to next page: Step 8: Boot the OpenVMS GalaxyStep 8: Boot the OpenVMS Galaxy