Page Comparison

...

This section describes how to migrate your HP Alpha system to CHARON-AXP. We will use a sample HP AlphaServer ES40 system running OpenVMS to demonstrate the migration procedure. The process is similar for all CHARON-AXP models.

...

Turn on your source HP Alpha system. At the ">>>" prompt, issue "show device" command:

>>>show device

sys0.0.0.0.0

SYS0

System

ROOT

Device
ewa0.0.0.1.1

EWA0

F8-D1-11-00-67-E6
pka0.0.0.2.1

PKA0

Q-Logic/ISP

PCI

SCSI

HBA
pga0.0.0.3.1

PGA0 WWN 1000

PGA0 WWN 1000-0000-0248-C550
pqa0.0.0.15.0

PQA0

ALi

1553C

Integrated

IDE

Controller
pqb0.0.1.15.0

PQB0

ALi

1553C

Integrated

IDE

Controller
dqa0.0.0.15.0

DQA0

TSSTcorpCDDVDW

SH-222BB
dka0.0.0.2.1

DKA0

DEC

RZ28

(C)DEC
dka100.1.0.2.1

DKA100

DEC

RZ22

(C)DEC
dka200.2.0.2.1

DKA200

DEC

RZ23

(C)DEC
mka600.6.0.2.1

MKA600

Virtual

SCSI

Tape

>>>

To get more detailed information boot OpenVMS and issue "show dev /full" command:

$ show device /full

Disk PFCAXP$DKA0:, device type RZ28, is online, mounted, file-oriented device,
 shareable, available to cluster, error logging is enabled.
...

Disk PFCAXP$DKA100:, device type RZ22, is online, file-oriented device,
 shareable, available to cluster, error logging is enabled.
...

Disk PFCAXP$DKA200:, device type RZ23, is online, file-oriented device,
 shareable, available to cluster, error logging is enabled.
...

Disk PFCAXP$DQA0:, device type TSSTcorpCDDVDW SH-222BB, is online, file-oriented
 device, shareable, available to cluster, error logging is enabled.
...

Disk $1$DGA0: (PFCAXP), device type RZ24, is online, file-oriented device,
 shareable, available to cluster, error logging is enabled.
...

Magtape PFCAXP$MKA600:, device type Virtual SCSI Tape, is online, file-oriented
 device, available to cluster, error logging is enabled, device supports
 fastskip (per_io).
...

Terminal OPA0:, device type VT102, is online, record-oriented device, carriage
 control.
...

Device EWA0:, device type DE500, is online, network device, device is a template
 only.
...

Device FGA0:, device type KGPSA Fibre Channel, is online, shareable, error
 logging is enabled.
...

Device PGA0:, device type SCSI FCP, is online, error logging is enabled.

...

Device PKA0:, device type Qlogic ISP1020 SCSI port, is online, error logging is
 enabled.
...

Device $1$GGA32767:, device type Generic SCSI device, is online, shareable.

$

The source HP Alpha peripheral configuration in this example is:

Controller	Devices on controller	Description
KZPBA	-DKA0 (RZ28) -DKA100 (RZ22) -DKA200 (RZ23) -MKA600 (tape)	SCSI disk/tape controller
KGPSA	-DGA0 (RZ24)	FC disk controller
OPA0		System console
TSSTcorpCDDVDW SH-222BB	-DQA0	IDE CD-ROM controller
EWA0		Network interface, MAC address: "F8-D1-11-00-67-E6"

Now collect some general information about the HP AlphaServer ES40 system:

>>>show cpu /full

System: PFCAXP, AlphaServer ES40 6/667

SMP execlet = 3 : Enabled : Streamlined.
 Config tree = None
 Primary CPU = 0
 HWRPB CPUs = 4
 Page Size = 8192
 Revision Code =
 Serial Number = SN01234567
 Default CPU Capabilities:
 System: QUORUM RUN
 Default Process Capabilities:
 System: QUORUM RUN

....

>>>

>>>show mem

...

Info

In case of Tru64 UNIX V5 running on the host system it is recommended to use the following commands to get information on the host configuration:

Command	Description
`#/sbin/hwmgr view devices`	Get detailed information about the host hardware configuration
`#/sbin/hwmgr show scsi`	Get specific information about the host SCSI controllers and attached disks
`#/sbin/hwmgr view hierarchy`	Get information about the host controllers

Please reference to the Tru64 UNIX User's Guide for more details.

Div

class	pagebreak

The source HP Alpha peripheral configuration in this example is:

Controller	Devices on controller	Description
KZPBA	-DKA0 (RZ28) -DKA100 (RZ22) -DKA200 (RZ23) -MKA600 (tape)	SCSI disk/tape controller
KGPSA-CA	-DGA0 (RZ24)	FC disk controller
OPA0		System console
TSSTcorpCDDVDW SH-222BB	-DQA0	IDE CD-ROM controller
EWA0		Network interface, MAC address: "F8-D1-11-00-67-E6"

Now collect some general information about the HP AlphaServer ES40 system:

>>>show cpu /full

System: PFCAXP, AlphaServer ES40 6/667

SMP execlet = 3 : Enabled : Streamlined.
Config tree = None
Primary CPU = 0
HWRPB CPUs = 4
Page Size = 8192
Revision Code =
Serial Number = SN01234567
Default CPU Capabilities:
System: QUORUM RUN
Default Process Capabilities:
System: QUORUM RUN

....

>>>

>>>show mem

System Memory Resources on 5-FEB-2015 09:29:16.42

Physical

Memory

Usage

(pages):

Total

Free

In

Use

Modified

Main

Memory

(512.00MB)

65536

56496

8610

430

...

>>>

So the collected information about the HP AlphaServer ES40 system is:

Component	Value
System Type	AlphaServer ES40 6/667
Serial Number	SN01234567
Number of CPUs	4
System memory	512 Mb

Div

class	pagebreak

Info

In some particular situations it is also important to know the exact placement of all the peripheral devices on HP Alpha PCI bus. To get that information issue "show config" command in at ">>>" prompt of HP Alpha console, for example:

>>>show config

...

PCI

Bus

00

Slot

03:

DECchip

21142

Network

Controller
ewa0.0.0.3.0 00-00-F8-03-

Controller
ewa0.0.0.3.0 00-00-F8-03-9A-6D

Bus

00

Slot

07:

Cypress

PCI

Peripheral

Controller

Bus

00

Slot

07:

Function

1:

PCI

IDE

Bus

00

Slot

07:

Function

2:

PCI

IDE

Bus

00

Slot

07:

PCI

USB

Bus

00

Slot

08:

DECchip

21052

PCI

to

PCI

Bridge

Bus

01

Slot

08:

ISP1040

Scsi

Controller

pka0.7.0.1008.0

SCSI

Bus

ID

7

dka0.0.0.1008.0

RZ2DD-KS

dka400.4.0.1008.0

RRD45

>>>

The "show config" command allows to collect collects the following information of placement of peripheral devices on PCI bus:

Bus number
Slot number
Function number

...

Back to Table of Contents

Div

class	pagebreak

Creation of CHARON-AXP configuration file

Using the above info, the following configuration can be created:

...

#
# First RQDX3 controller on address 772150
#
load RQDX3/RQDX3 DUA address=017772150
set DUA container[0]="C:\My disks\rz23.vdisk"
set DUA container[1]="C:\My disks\rz24.vdisk"

#
# Second RQDX3 controller on address 760334
#
load RQDX3/RQDX3 DUB address=017760334
set DUB container[2]="C:\My disks\rz25.vdisk"
set DUB container[3]="C:\My disks\rz26.vdisk"

#
# First TQK50 controller on address 774500
#
load TQK50/TQK50 MUA address=017774500
set MUA container[0]="C:\My tapes\tape1.vtape"

#
# Second TQK50 controller on address 760444
#
load TQK50/TQK50 MUB address=017760444
set MUB container[3]="C:\My tapes\tape2.vtape"

#
# First DHQ11 controller on address 760500
#
load DHQ11/DHV11 TXA address=017760500
load virtual_serial_line/chserial TXA0 port=10010
set TXA line[0]=TXA0

#
# Second DHQ11 controller on address 760520
#
load DHQ11/DHV11 TXB address=017760520
load virtual_serial_line/chserial TXB0 port=10011
set TXB line[0]=TXB0

#
# DESQA controller on address 774440
#
load DESQA/DEQNA XQA address=017774440 interface=XQA0 load packet_port/chnetwrk XQA0 interface="connection:Charon"

...

Note the Qbus addresses specification: The number is prefixed with "0", meaning it is an octal value. The number of digits reflects the 22 bit Qbus architecture.

Additional DHQ11 serial lines can be mapped later. For now, only 2 lines are configured. They are mapped to IP ports 10010 and 10011.

DESQA is mapped to a network interface having the name "Charon". This interface will be used for CHARON-AXP (see the Installation section for more details) on this particular host.

...

#
# HP AlphaServer model: AlphaServer ES40 6/667
#

set session hw_model = AlphaServer_ES40
set ace cpu_architecture = EV67
set rom dsrdb[0] = 1820 system_name = "AlphaServer ES40 6/667"

...

#
# Override default System Serial Number, set it to "SN01234567"
#

set rom system_serial_number = SN01234567

#
# Specify RAM size: 512 Mb
#

set ram size=512

#
# Map OPA0 console to "Putty" terminal emulator (included in CHARON-AXP kit)
#

load virtual_serial_line OPA0 port=10003 application="putty -load OPA0"

#
# Сonnect the emulator's DQA0 to the host's ATAPI CD/DVD-ROM drive.
#

set ide container="\\.\CdRom0"

#
# Load optional DE500BA PCI Ethernet Adapter (EWA0) and map it to the "Charon" host network interface
#

load DE500BA/dec21x4x EWA interface=EWA0
load packet_port/chnetwrk EWA0 interface="connection:Charon"

#
# Load DEC-KZPBA SCSI controller and map it to 3 disk containers and 1 tape container
#

load KZPBA PKA scsi_id = 7

set PKA container[0] = "C:\My disks\bootable.vdisk"
set PKA container[100] = "C:\My disks\RZ22.vdisk"
set PKA container[200] = "C:\My disks\RZ23.vdisk"

set PKA container[600] = "C:\My tapes\my_tape.vtape"

#
# Load DEC-KGPSA-CA PCI FC adapter and map it to a disk container
#

load KGPSA FGA

set FGA container[0] = "C:\My disks\RZ24.vdisk"

...

Back to Table of Contents

Div

class	pagebreak

Making disk images

In our example, possible mappings of RQDX3 and TQK50 tapes include physical devices and KZPBA SCSI controller include disk and tape images. Tape images should have not to be manually created , whereas you have to provision disk images, as described below.

...

...> cd C:

\
C:\> mkdir "My disks"

C:\> mkdir "My tapes"

This operation can also be done using Windows Explorer.

Next, create disk images using Start the "MkDisk" utility.Start the "MkDisk" utility from utility from the "Start" menu to create disk images:Image Removed

Image Added

Div

class	pagebreak

The main dialog of the utility will appear:

Image RemovedImage Added

Select "HP Alpha AXP" in the "Select System" drop-down menu, "MSCPSCSI" in the "All Controllers" drop-down menu and "RZ24" (for example) in the "Select Disk Type" drop-down menu, then press .

Div

class	pagebreak

Press then the "Create Disk Image" button:Image Removed

Image Added

Div

class	pagebreak

The utility will ask you to specify the output file name. Select the "C:\My disks" directory created just before (or create it directly in the dialog) and press "Save" button:

Image RemovedImage Added

The "MkDisk" utility will create the requested disk image:

Image RemovedImage Added

Repeat this sequence for the disks "RZ23RZ28.vdisk", "RZ25RZ22.vdisk" and "RZ26RZ23.vdisk". Put Place them in the same "C:\My disks" folder.

Back to Table of Contents

Div

class	pagebreak

Installation of HP Alpha operating system

...

The example configures the CHARON-AXP MicroHP Alpha 3600 AlphaServer ES40 system for installation of HP Alpha/VMS OpenVMS from a distribution CD-ROM (usually it is "\\.\CdRom0" if the host has only one CD-ROM drive):

# # First RQDX3 controller on address 772150 with addition of 3 units: a disk for HP Alpha/VMS, storage disk and CD-ROM drive
#
load RQDX3/RQDX3 DUA address=017772150
set DUA DEC-KZPBA SCSI controller is mapped to 5 disk containers; one of them (DKA300) - for migration purposes; # another one (DKA400) - for installation of fresh HP OpenVMS system from distributive
#

load KZPBA PKA scsi_id = 7

set PKA container[0] = "C:\My disks\rz23bootable.vdisk"
set DUA PKA container[1100] = "C:\My disks\rz24RZ22.vdisk"
set DUA PKA container[2200] = "C:\My disks\new_vms_systemRZ23.vdisk" set DUA PKA container[3300] = "C:\My disks\backup_storagemigration.vdisk" set DUA PKA container[4400] = "C:\My disks\fresh_openvms.vdisk"

#
# CD-ROM for HP OpenVMS installation (DQA0)
#

set ide container="\\.\CdRom0"

DUA3 DKA300 will be the disk where all the source disks will be copied, so its size needs to be big enough to store all the disk backup images

Create an empty disk image for installation of HP Alpha/VMS OpenVMS and another one for storing backups from the source HP Alpha system as it is shown in the section above.

Run CHARON-AXP and boot from "dua4" ("migration.cfg" is the configuration file we use in this example):

...

section above.

Run CHARON-AXP and boot from the CDROM named "dqa0" ("migration.cfg" is the configuration file we use in this example):

...>es40.exe migration.cfg

P00>>>boot dqa0

Install HP Alpha/VMS including DECnet on "dua2dka400". DECnet address must belong to the same area as the source HP Alpha system.

Login to the newly installed VMS OpenVMS system and initialize the disk intended for backups storage. Let's assume it's prompt is "newvms$ "

newvms$ INIT DUA3DKA300: SCRATCH
newvms$ MOUNT/SYSTEM/NOASSIST DUA3DKA300: SCRATCH

Back to Table of Contents

...

The use of the "SHOW DEVICE /FILES" command would be of help to know files opened on a disk

Issue (letLet's assume that the CHARON-AXP system is node 1.400 in this example). Issue then the following commands from the source HP Alpha. Let's assume it's login is Alpha whose prompt is set to "source$ "

source$ BACKUP/IMAGE/IGNORE=INTERLOCK DUA0DKA0: 1.400::DKA300:[000000]DKA0.BCK/SAVE
source$BACKUP/IMAGE/IGNORE=INTERLOCK DKA100: 1.400::DUA3DKA300:[000000]DUA0DKA100.BCK/SAVEsource$ BACKUP/IMAGE/IGNORE=INTERLOCK DUA1 DKA200: 1.400::DUA3DKA300:[000000]DUA1DKA200.BCK/SAVE SAVE

Once the backup procedure completes, the disk "DUA3DKA300" of CHARON-AXP will contain 2 savesets: "DUA03 savesets: "DKA0.BCK", "DKA100.BCK" and and "DUA1DKA200.BCK"

Back to Table of Contents

...

Next, restore the new savesets to their corresponding virtual disks. Login to CHARON-AXP and issue this sequence of commands to restore all the savesets created on the previous step:

newvms$ MOUNT/FOREIGN DUA0DKA0:
newvms$ BACKUP/IMAGE DUA3DKA300:[000000]DUA0DKA0.BCK/SAVE DUA0DKA0:
newvms$ DISMOUNT DUA0DKA0:

newvms$ MOUNT/FOREIGN DKA100:
newvms$ BACKUP/IMAGE DKA300:[000000]DKA100.BCK/SAVE DKA100:
newvms$ DISMOUNT DKA100:

newvms$ MOUNT/FOREIGN DUA1 DKA200:
newvms$ BACKUP/IMAGE DUA3DKA300:[000000]DUA1DKA200.BCK/SAVE DUA1DKA200:
newvms$ DISMOUNT DUA1DKA200:

If you are going to have CHARON-AXP and the original physical HP Alpha on the network at the same time, you must change the network identity of one (usually the CHARON-AXP).

The easiest way is to boot the CHARON-AXP virtualized system on the restored system disk with the network Disabled and configure new addresses, as needed. The NIC can be disabled with a "connection:disabled" statement in the CHARON cfg configuration file.

Then Enable the network and reboot.

Back to Table of Contents

...

Connect a SCSI tape drive to CHARON-AXP / CHARON-PDP host via a PCI card
- Map the tape drive in the CHARON-AXP / CHARON-PDP configuration file
  a. Restore source HP Alpha system backups from tape to disk images via VMS/RSX11/RT11 OpenVMS running on CHARON-AXP / CHARON-PDP.
  b. Boot from standalone backups and restore its content to CHARON-AXP / CHARON-PDP virtual disks
- Dump source HP Alpha /PDP11 system backups to tape images with "mtd" utility and:
  a. Boot from freshly installed VMS/RSX11/RT11 OpenVMS system and restore the tape images to CHARON-AXP / CHARON-PDP virtual disks
  b. Boot from standalone backups and restore its content to CHARON-AXP / CHARON-PDP virtual disks
Create a network cluster between the source HP Alpha /PDP11 system and CHARON-AXP / CHARON-PDP (it is possible to use the source system as boot server); then simple backup from one disk to another:
$ BACKUP/IMAGE/IGNORE=INTERLOCK REAL$DUA0REAL$DKA0: DUA0DKA0:

Back to Table of Contents

Versions Compared

Old Version 3

New Version Current

Key

Creation of CHARON-AXP configuration file

Making disk images

Installation of HP Alpha operating system