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 ES40... Creating an OpenVMS Galaxy on an AlphaServer ES40...
go to previous page: Step 4: Set the Environment Variables Step 4: Set the Environment Variables
go to next page: Creating an OpenVMS Galaxy on AlphaServer GS80/160/320 SystemsCreating an OpenVMS Galaxy on AlphaServer GS80/160/320 Systems
end of book navigation links

Step 5: Initialize the System and Start the Console Devices  



  1. Initialize the system and start the Galaxy firmware by entering the following commands:
    P00>>> init      ! initialize the system
    P00>>> lpinit    ! start firmware
    After the self-test completes, the Galaxy command starts the console on instance 1.

    Note that when the I/O bus is divided between the two Galaxy partitions, the port letter of a device might change. For example, a disk designated as DKC300 when the AlphaServer ES40 is a single system could become DKA300 when it is configured as partition 0 of the OpenVMS Galaxy.
  2. Configure the console for instance 1.
  3. Configure the system root, boot device, and other related variables.

    The following example settings are from an OpenVMS Engineering system. Change these variables to meet the needs of your own environment.
          Instance 0
    P00>>> set boot_osflags	12,0
    P00>>> set bootdef_dev	dka0
    P00>>> set boot_reset	off             !!! must be OFF !!!
    P00>>> set ewa0_mode	twisted
     
     
          Instance 1
    P01>>> set boot_osflags	11,0
    P01>>> set bootdef_dev	dkb200
    P01>>> set boot_reset	off             !!! must be OFF !!!
    P01>>> set ewa0_mode	twisted
  4. Boot instance 1 as follows:
    P01>>> boot
    Once instance 1 is booted, log in to the system account and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the following line:
    GALAXY=1
    Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters are correct. Run AUTOGEN as follows to configure instance 1 as a Galaxy member, and leave the system halted:
    $ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL
  5. Boot instance 0 as follows:
    P00>>> boot
    Once instance 0 is booted, log in to the system account and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the following line:
    GALAXY=1
    Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters are correct. Run AUTOGEN as follows to configure instance 0 as a Galaxy member, and leave the system halted:
    $ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL
  6. Prepare the Galaxy to come up automatically upon initialization or power cycle of the system. Set the AUTO_ACTION environment variable on both instances to RESTART:
    P00>>> set auto_action restart
     
    P01>>> set auto_action restart
  7. Initialize the Galaxy again by entering the following command at the primary console:
    P00>>> init
    When the console displays the following confirmation prompt, type Y:
    Do you REALLY want to reset all partitions? (Y/N)
    Alternatively, you could power-cycle your system, and the Galaxy with both instances should bootstrap automatically.

Congratulations! You have created an OpenVMS Galaxy on an AlphaServer ES40 system.


go to previous page: Step 4: Set the Environment Variables Step 4: Set the Environment Variables
go to next page: Creating an OpenVMS Galaxy on AlphaServer GS80/160/320 SystemsCreating an OpenVMS Galaxy on AlphaServer GS80/160/320 Systems