HP OpenVMS Alpha Partitioning and Galaxy Guide |
Creating an OpenVMS Galaxy on an AlphaServer 8400... |
|
|
| |
Overview of KFE72-DA Console Subsystem Hardware ![]()
The
AlphaServer 8400 provides a standard built-in UART, which is used
as the console line for the primary Galaxy instance. The console
for each additional instance requires a KFE72-DA console subsystem,
which is the set of EISA-bus modules that establishes an additional
console port.
Note that the AlphaServer 8400 supports a maximum of three I/O modules. Attempting to configure more than three is unsupported.
Each separate KFE72-DA subsystem must be installed in a separate DWLPB card cage with a hose connecting it to a separate I/O module of type KFTIA or KFTHA.
All KFTIA I/O modules must be installed first, starting at slot 8. Any KFTHA I/O modules must follow the KFTIA modules, using the consecutively lower-numbered slots.
You can use any combination of these two I/O modules as long as you follow this slot assignment rule.
When configuring a console subsystem, the I/O hose connecting the I/O module and DWLPB card cage must be plugged into the lowest hose port. Not just the lowest available hose port, but the absolute first hose port; the one closest to the top of the module.
The KFE72-DA contains three EISA modules that provide:
Installing the KFE72-DA
Modules ![]()
For
each instance of the OpenVMS operating system after instance zero,
you must install the following three modules in the PCI card cage:
To install these modules, follow the procedures in Slide the PCI Card Cage Out to Attaching the Connectors, which supplement the installation procedures for KFE72-DA modules in Chapter 5 of the KFE72 Installation Guide.
Slide the PCI Card Cage Out ![]()
Follow the procedures in Section 5.2.1 of the KFE72
Installation Guide.
Insert Modules and Connect Ribbon Cables ![]()
| When installing PCI modules, be sure the option bulkheads mate with the EMI gasket on the PCI card cage. |
To insert the modules in the PCI card cages and connect the appropriate ribbon cables, see Attaching Ribbon Cables and perform the following steps:
|
Figure 1 Attaching Ribbon Cables |
![]() |
Attaching the Connectors ![]()
To connect the console terminal and additional devices, see
Connectors and connect the console serial
line (H8571-J connector) to COM1.
Note that the pair of arrows between the numbers 1 and 2 on the serial port module is an industry standard symbol for a serial port and does not indicate port numbers.
|
Figure 2 Connectors |
![]() |
Slide Shelf Back Into System ![]()
To return the card cage, follow steps 2 through 9 in the procedure
in Section 5.2.3 of the KFE72 Installation Guide.
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.
See the appropriate product documentation for details about configuring
a LAT Server or other terminal concentrator.
Installing EISA Devices ![]()
Plug-in
EISA devices can only be configured in partition 0. After installing
EISA devices, the console issues a message requesting that you run
the EISA Configuration Utility (ECU).
Run the ECU as follows:
P00>>> SET ARC_ENABLE ON P00>>> INITIALIZE P00>>> RUN ECU
P00>>> boot
$ @SYS$SYSTEM:SHUTDOWN
P00>>> SET ARC_ENABLE OFF
P00>>> INITIALIZE
P00>>> LPINITThere 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 systems, the primary console is always a serial device with a character-cell terminal.
If the ECU is not run, OpenVMS displays 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 boots, but the plug-in EISA devices are ignored.
Once you have configured and set up the OpenVMS Galaxy hardware as described in the previous sections, perform the following steps to install and boot OpenVMS Galaxy instances.
|
|