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.

...

$ 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

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:

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

Bus 00 Slot 03: DECchip 21142 Network 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

...

Back to Table of Contents

Div

class	pagebreak

Making disk images

In our example, possible mappings of 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 the "MkDisk" utility.

Start the "MkDisk" utility from the "Start" menu to create disk images:

The main dialog of

Div

class	pagebreak

The main dialog of the utility will appear:

Select "Alpha AXP" in the "Select System" drop-down menu, "SCSI" 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:

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:

...

Repeat this sequence for the disks "RZ28.vdisk", "RZ22.vdisk" and "RZ23.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

...

# # 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\bootable.vdisk"
set PKA container[100] = "C:\My disks\RZ22.vdisk"
set PKA container[200] = "C:\My disks\RZ23.vdisk" set PKA container[300] = "C:\My disks\migration.diskvdisk" set PKA container[400] = "C:\My disks\fresh_openvms.vdisk"

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

set ide container="\\.\CdRom0"

...

Create an empty disk image for installation of HP 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 "dqa0" ("migration.cfg" is the configuration file we use in this example):

...

.

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 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 6

New Version Current

Key

Creation of CHARON-AXP configuration file

Making disk images

Installation of HP Alpha operating system