OpenVMS VMS721_DS20E_ES40 Alpha V7.2-1 DS20E/ES40 ECO Summary
TITLE: OpenVMS VMS721_DS20E_ES40 Alpha V7.2-1 DS20E/ES40 ECO Summary
Modification Date: 29-SEP-1999
Modification Type: Corrected URL for firmware site.
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
Copyright (c) Compaq Computer Corporation 1999. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: LAN
DECW$SERVER_DDX_GZ
EXEC_INIT
GCU
SYS$CPU_ROUTINES_2208
DRIVERS
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_DS20E_ES40
DEC-AXPVMS-VMS721_DS20E_ES40-V0100--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 3088 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: NO - All cluster nodes must be
rebooted at the same time.
Installation Rating: INSTALL_2
2 - To be installed on all systems running
the listed version(s) of OpenVMS and
using the following feature(s):
DS20E or creating an OpenVMS Galaxy
on an AlphaServer ES40 System
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS721_LAN-V0100
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for LAN support on OpenVMS Alpha V7.2-1. This kit
addresses the following problems:
New Functionality Addressed in VMS721_DS20E_ES40-V0100:
o This kit provides OpenVMS Version 7.2-1 support for the Compaq
AlphaServer DS20E. The DS20E is a follow-on to the Compaq
AlphaServer DS20. This kit includes the following OpenVMS
support on the DS20E:
+ Server management
+ 3X-DEPVD-AA PCI adapter
+ IDE CD-ROM and boot and runtime
Image(s) Affected:
- [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
- [SYS$LDR]SYS$IIDRIVER.EXE
- [SYSEXE]SYS$SMHANDLER.EXE
o On Compaq AlphaServer DS20E systems, the following system routines
cannot be used to perform I/O tribyte reads and writes:
+ IOC$READ_PCI_CONFIG
+ IOC$WRITE_PCI_CONFIG
+ IOC$READ_IO
+ IOC$WRITE_IO
If a device driver calls any of these system routines with a
length of three, you must use one of the following methods
instead-depending on your I/O cards characteristics:
For IOC$READ_IO and IOC$READ_PCI_CONFIG:
+ Use a longword read, and mask out the byte.
+ Do a combination of word and byte reads, and
append the Data.
For IOC$WRITE_IO and IOC$WRITE_PCI_CONFIG:
+ Read a longword, modify the tribyte, and rewrite the
longword.
Note that AlphaServer 8200/8400 and GS60/140 systems with
Alpha 21264 CPUs support tribyte reads and writes.
o TCP/IP for OpenVMS Version 4.2 does not support the new
3X-DEPVD-AA PCI adapter on the AlphaServer DS20E. Prior
to running UCX$CONFIG procedures, use the following command
to manually configure TCP/IP with the new ethernet adapter:
_$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) -
_$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) -
_$ /DESCRIPTION=INTEL_ETHERNET
Check with your Compaq support representative if you have
further questions on TCP/IP and the 3X-DEPVD-AA PCI adapter.
o This change adds P2V chip support to the P2A code used on ELSA.
This functionality is only used if you are using a P2V graphics
adaptor
Image(s) Affected:
- [SYS$LDR]SYS$GZVDRIVER.EXE
- [SYSEXE]SYS$CONFIG.DAT
o This Section describes the requirements and procedures for
creating an OpenVMS Galaxy computing environment on an
AlphaServer ES40.
For complete information about the Galaxy Software Architecture
on OpenVMS Alpha, refer to the OpenVMS Alpha Galaxy Guide (Order
number: AA-REZQB-TE). The most recent version is always available
at
http://www.openvms.digital.com:8000/
For complete information about AlphaServer ES40 systems, see the
AlphaServer ES40 Owners Guide (Order number: EK-ES240-UG.A01).
Image(s) Affected:
- [SYSEXE]GCU.EXE
- [SYSMGR]GALAXY.GCR
- [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE
- [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE
- [SYSEXE]SYS$SMHANDLER.EXE
To create an OpenMVS Galaxy on an AlphaServer ES40 system:
1. Read the release notes chapter in the OpenVMS Alpha
Galaxy Guide.
2. Read the configuration and hardware requirements.
3. Perform the steps described below.
Before you start:
In addition to the information in the Release Notes chapter
in the OpenVMS Galaxy Guide, you must also be familiar with
the following configuration and hardware requirements:
+ Two-instance maximum
You can run a maximum of two instances of OpenVMS on an
AlphaServer ES40.
+ Console firmware
To create an OpenVMS Galaxy environment on AlphaServer
ES40 systems, you must download the latest version of the
V5.5-xx console firmware from the following location:
http://ftp.digital.com/pub/Digital/Alpha/firmware/interim/es40/
+ AlphaServer ES40 clock
An AlphaServer ES40 has one clock. For an OpenVMS Galaxy,
this means that you cannot run the two instances at
different times. Also, the SET TIME command affects both
instances. Note that this may not become evident until a
number of hours have passed.
+ Console ports
COM1 (lower) is the console port for instance 0.
COM2 (upper) is the console port for instance 1.
Unlike creating an OpenVMS Galaxy on an AlphaServer 8400,
you do not need additional hardware for the second
console. COM-2 is used for this purpose.
+ CPUs
CPU0 must be the primary for instance 0.
CPU1 must be the primary for instance 1.
CPUs 2 and 3 are optional secondary CPUs that can be
migrated.
+ I/O adapters
PCI Hose 0 (PCI0) belongs to instance 0 (upper 4 PCI slots)
PCI Hose 1 (PCI1) belongs to instance 1 (lower 6 PCI slots)
Note that PCI0 contains an embedded ISA controller.
+ Storage controllers
You will need one storage controller (such as a KZPSA) per
instance. For each instance, this can go to a separate
Storagework box or to the same box for running as a SCSI
cluster.
+ Network cards
If each instance needs network access, a network card
(such as a DE500) is required for each instance.
One card each goes in PCI0 and PCI1.
+ Physical memory
Private memory must start on a 64 MB boundary.
Shared memory must begin on an 8 MB boundary.
All instances except the last must have a multiple of
64 MB.
Step 1. Confirm the AlphaServer ES40 Configuration
Use the SHOW CONFIG command to make sure that the AlphaServer
ES40 you are using to create an OpenVMS Galaxy environment
meets the requirements described.
At the console prompt, enter the following command:
P00>>>show config
The console displays information similar to the following
example:
Firmware
ARC Console: v5.70
PALcode: OpenVMS PALcode V1.61-2
Tru64 UNIX PALcode V1.54-2
Serial Rom: V2.2-F
RMC Rom: V1.0
RMC Flash Rom: T2.0
Processors
CPU 0 Alpha 21264-4 500 MHz 4MB Bcache
CPU 1 Alpha 21264-4 500 MHz 4MB Bcache
CPU 2 Alpha 21264-4 500 MHz 4MB Bcache
CPU 3 Alpha 21264-4 500 MHz 4MB Bcache
Core Logic
Cchip DECchip 21272-CA Rev 9(C4)
Dchip DECchip 21272-DA Rev 2
Pchip 0 DECchip 21272-EA Rev 2
Pchip 1 DECchip 21272-EA Rev 2
TIG Rev 10
Memory
Array Size Base Address Intlv Mode
--------- ---------- ---------------- ----------
0 4096Mb 0000000000000000 2-Way
1 4096Mb 0000000100000000 2-Way
2 1024Mb 0000000200000000 2-Way
3 1024Mb 0000000240000000 2-Way
10240 MB of System Memory
Slot Option Hose 0, Bus 0, PCI
1 DAPCA-FA ATM622 MMF
2 DECchip 21152-AA Bridge to Bus 2, PCI
3 DEC PCI FDDI fwb0.0.0.3.0 00-00-F8-BD-C6-5C
4 DEC PowerStorm
7 Acer Labs M1543C Bridge to Bus 1, ISA
15 Acer Labs M1543C IDE dqa.0.0.15.0
dqb.0.1.15.0
dqa0.0.0.15.0 TOSHIBA CD-ROM XM-6302B
19 Acer Labs M1543C USB
Option Hose 0, Bus 1, ISA
Floppy dva0.0.0.1000.0
Slot Option Hose 0, Bus 2, PCI
0 NCR 53C875 pkd0.7.0.2000.0 SCSI Bus ID 7
1 NCR 53C875 pke0.7.0.2001.0 SCSI Bus ID 7
dke100.1.0.2001.0 RZ1BB-CS
dke200.2.0.2001.0 RZ1BB-CS
dke300.3.0.2001.0 RZ1CB-CS
dke400.4.0.2001.0 RZ1CB-CS
2 DE500-AA Network Con ewa0.0.0.2002.0 00-06-2B-00-0A-58
Slot Option Hose 1, Bus 0, PCI
1 NCR 53C895 pka0.7.0.1.1 SCSI Bus ID 7
dka100.1.0.1.1 RZ2CA-LA
dka300.3.0.1.1 RZ2CA-LA
2 Fore ATM 155/622 Ada
3 DEC PCI FDDI fwa0.0.0.3.1 00-00-F8-45-B2-CE
4 QLogic ISP10x0 pkb0.7.0.4.1 SCSI Bus ID 7
dkb100.1.0.4.1 HSZ50-AX
dkb101.1.0.4.1 HSZ50-AX
dkb200.2.0.4.1 HSZ50-AX
dkb201.2.0.4.1 HSZ50-AX
dkb202.2.0.4.1 HSZ50-AX
5 QLogic ISP10x0 pkc0.7.0.5.1 SCSI Bus ID 7
dkc100.1.0.5.1 RZ1CB-CS
dkc200.2.0.5.1 RZ1CB-CS
dkc300.3.0.5.1 RZ1CB-CS
dkc400.4.0.5.1 RZ1CB-CS
6 DECchip 21154-AA Bridge to Bus 2, PCI
Slot Option Hose 1, Bus 2, PCI
4 DE602-AA eia0.0.0.2004.1 00-08-C7-91-0A-AA
5 DE602-AA eib0.0.0.2005.1 00-08-C7-91-0A-AB
6 DE602-TA eic0.0.0.2006.1 00-08-C7-66-80-9E
7 DE602-TA eid0.0.0.2007.1 00-08-C7-66-80-5E
Step 2: Install OpenVMS Alpha Version 7.2-1
No special installation procedures are required to run OpenVMS
Galaxy software. Galaxy functionality is included in the base
operating system and can be enabled or disabled using the
console command and system parameter values described later in
this chapter.
If your AlphaServer ES40 is not part of a SCSI cluster, you
must install OpenVMS Version 7.2-1 on two system disks-one
disk for each instance.
If your AlphaServer ES40 is part of a SCSI cluster with a
cluster-common system disk, install OpenVMS Version 7.2-1 on
one system disk.
For more information about installing the OpenVMS Alpha
operating system, see the OpenVMS Alpha Version 7.2 Upgrade
and Installation Guide.
Step 3: Upgrade the Firmware
To upgrade the firmware, use one of the following procedures:
Copy the firmware file to MOM$SYSTEM on a MOP-enabled server
that is accessible to the AlphaServer ES40. Enter the
following commands on the console:
P00>>> boot -fl 0,0 ewa0 -fi {firmware filename}
UPD> update srm*
Or, use the following commands:
P00>>> BOOT -FLAGS 0,A0 cd_device_name
.
.
.
Bootfile: {firmware filename}
.
.
.
Set Environment Variables
Configure the primary console for instance 0.
CPU0 is the primary for instance 0.
CPU1 is the primary for instance 1.
For descriptions of the Galaxy environment variables and
common values for them, refer to Chapter 6 in the OpenVMS
Alpha Galaxy Guide.
The following example is for an AlphaServer ES40 with three
CPUs and 512MB of memory divided into 256MB + 192MB + 64MB.
P00>>> set lp_count 2
P00>>> set lp_cpu_mask0 1
P00>>> set lp_cpu_mask1 6
P00>>> set lp_io_mask0 10
P00>>> set lp_io_mask1 20
P00>>> set lp_mem_size0 10000000
P00>>> set lp_mem_size1 c000000
P00>>> set lp_shared_mem_size 4000000
P00>>> set auto_action halt
If you have four CPUs and you want to assign all secondary
CPUs to instance 1, the lp_cpu_mask1 variable will be E. If
you split the CPUs between both instances, CPU 0 must be the
primary for instance 0, and CPU 1 must be the primary CPU for
instance 1.
The following example shows LP_CPU_MASK values for secondary
CPU assignments with primary CPUs.
Assign secondary CPU 2 with primary CPU 0 and secondary CPU 3
with primary CPU 1.
>>>set lp_cpu_mask0 5
>>>set lp_cpu_mask1 A
CPU Selection LP_CPU_MASK
0(primary partition 0) 2^0 = 1
1(primary partition 1) 2^1 = 2
2(secondary) 2^2 = 4
3(secondary) 2^3 = 8
The mem_size variables depend on your configuration and how
you want to split it up.
lp_io_mask0 must be set to 1
lp_io_mask1 must be set to 2
You must set the console environment variable AUTO_ACTION to
HALT. This will ensure that the system does not boot and that
you will be able to enter the Galaxy command.
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
P00>>> lpinit ! same as galaxy command
After the self-test completes, the Galaxy command will
start 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
commands 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.
Problems Addressed in VMS721_DS20E_ES40:
o The EXTENDED_ID flag in the SYS$CONFIG.DAT file is used to
allow full 64-bit ID checking on PCI devices. This will be
used for LAN and ATM devices to ensure that the device is a
qualified device.
A problem in the LOOKUP_ID code causes the ID mask to be
extended to 64-bits the first time the flag is seen, and
it is never reduced back to 32-bits for non-extended IDs.
This causes a failure to find some disk devices at boot, and
prevents booting.
The user sees an error that a device on the boot command line
could not be found, and the system halts.
Image(s) Affected: [SYS$LDR]EXEC_INIT.EXE
o When the 680 handler issued the code 22Bh to SYS$SMHANDLER it
did not display a message.
Image(s) Affected: [SYSEXE]SYS$SMHANDLER.EXE
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system
must be rebooted. If the system is a member of a VMScluster, the
entire cluster should be rebooted simultaneously.
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
European Site
Files on this server are as follows:
dec-axpvms-vms721_ds20e_es40-v0100--4.README
dec-axpvms-vms721_ds20e_es40-v0100--4.CHKSUM
dec-axpvms-vms721_ds20e_es40-v0100--4.pcsi-dcx_axpexe
vms721_ds20e_es40-v0100.CVRLET_TXT
