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 configur-
  ing 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 in-
  form 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 de-
  vices.  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 de-
  fined 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>>>  GALAXY

  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
  Galaxy  Configuration  Tree  =  12c000
  starting  cpu  1  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  2  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  3  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  4  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  5  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  6  in  Galaxy  instance  1  at  address  01000c001
  starting  cpu  7  in  Galaxy  instance  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.

  5.7.1  Console Hints

  Because the AlphaServer 8400 was built prior to the Galaxy
  Software Architecture, OpenVMS Galaxy console firmware
  and system operations must deal with a few restrictions.

  The following list briefly describes some things you should be
  aware of and some things you should avoid doing:

  *   Do not set the BOOT_RESET        environment variable to   1.
      This causes each secondary console to reset the bus be-
      fore booting, thus resetting all previously booted partitions.
      Remember that OpenVMS Galaxy partitions share the
      hardware.

  *   Be patient.  Console initialization, and system rebooting
      can take several minutes.

  *   Do not attempt to abort a firmware update pro-

      cess!

      This can leave your system seriously hung.

  *   When updating console firmware, update      ALL CPUs     at
      the same time.

      You cannot run two different types of CPUs or two dif-
      ferent firmware revisions.  If you fail to provide consistent
      firmware revisions, the system will hang on power-up.

  *   Never issue the  GALAXY     command from a secondary
      console.  This will re-initialize the system, and you will
      need to start over from the primary console.