5.2 Step 2: Set Up Galaxy Hardware
5.2.1 Installing the KFE72-DA Console Subsystem
Hardware
The KFE72-DA is the set of EISA-bus modules that estab-
lishes an additional console port. One KFE72-DA module set
is required per secondary partition.
The KFE72-DA contains three EISA modules that provide:
* Two COM ports
* A keyboard interface
* A mouse interface
* A small speaker
* An Ethernet port.
The COM-1 port is used for the console serial line. The
Ethernet port can be used as a network connection or it can
be terminated. The mouse and keyboard ports are not used.
The KFE72-DA must be plugged into the bottom three EISA
slots. For the AlphaServer 8400 this requires that you attach
a hose from your I/O port to a DWLPB PCI card cage. The
KFE72-DA module set must be installed in slots 0, 1, and 2 of
the card cage. The KFE72's SIO (a.k.a. Bridge) module en-
ables the EISA slots which are part of the combination PCI
/EISA backplane. The other two modules known as the "Data
Port Module" and "Beeper97" go in slots 1 and 2 respectively.
5.2.2 Using a Terminal Server
You may want to bring your console lines together using a
terminal server. For example, use a DECserver200 to allow
reverse-LAT access to each console over the network. While
this is not strictly required, it greatly simplifies OpenVMS
Galaxy configuration management. Refer to the appropriate
product documentation for details about configuring a LAT
Server or other terminal concentrator.
5.2.3 Recommendations for Configuring Console
Subsystems
Each additional console requires a separate KFE72-DA sub-
system installed in a separate DWLPB card cage with a hose
connecting it to a separate I/O module of type KFTIA or
KFTHA. If you are using a KFTIA, it must be in slot 8.
Additional KFTIA I/O modules must be in the next lower slot
or slots, with KFTHA I/O modules in the next lower slot or
slots after that.
You can use any combination of these two I/O modules as
long as you follow this slot assignment rule.
The AlphaServer 8400 supports a maximum of three I/O
modules. Attempting to configure more than three is unsup-
ported.
When configuring a console subsystem, the I/O hose con-
necting the I/O Processor and DWLPB card cage must be
plugged into the lowest hose port. Not just the lowest avail-
able hose port, but the absolute first hose port; the one closest
to the top of the module.
KFE72-DA modules must occupy slots 0, 1, and 2 of the
DWLPB card cage.
The console serial line is connected with an H8571-J con-
nector adapter that plugs into the right hand serial line port
when viewed from the rear of the machine. This is COM-1.
5.2.4 Installing EISA Devices
Plug-in EISA devices can only be configured in partition 0.
After installing EISA devices, the console will issue a mes-
sage requesting that you run the EISA Configuration Utility
(ECU).
Run the ECU as follows:
1. Shut down all OpenVMS Galaxy instances.
2. Be sure your floppy disk drive is properly connected to the
primary partitions hardware. Typically the drive can be
cabled into the Connector Module ("Beeper" part number
54-25133-01) in PCI slot 2.
3. Insert the diskette containing the ECU image.
4. Issue the following commands from the primary console:
P00>>> SET ARC_ENABLE ON
P00>>> INITIALIZE
P00>>> RUN ECU
5. Follow the procedures outlined by the ECU and exit when
done.
6. P00>>> boot
7. $ @SYS$SYSTEM:SHUTDOWN
8. P00>>> SET ARC_ENABLE OFF
9. P00>>> INITIALIZE
10. P00>>> GALAXY
11. Reboot the OpenVMS Galaxy
There are two versions of the ECU, one that runs on a
graphics terminal and another that runs on character cell
terminals. Both versions are on the diskette, and the console
determines which one to run. For OpenVMS Galaxy sys-
tems, the primary console will always be a serial device with
a character cell terminal.
If the ECU is not run, OpenVMS will display the following
message:
%SYSTEM-I-NOCONFIGDATA, IRQ Configuration data for EISA
slot xxx was not found, please run the ECU and reboot.
If you ignore this message, the system will boot, but the plug-
in EISA devices will be ignored.
Once you have configured and set up the OpenVMS Galaxy
hardware as described in in the previous sections, perform
the following steps to install and boot OpenVMS Galaxy
instances.