Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added some pagebreaks / PDF export

...

To get more detailed information, boot OpenVMS and issue a "show dev device /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.

$

...

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

ComponentValue
System Type

AlphaServer ES40 6/667

Serial Number

SN01234567

Number of CPUs4
System memory512 Mb
Div
classpagebreak

 

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 a "show config" command 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 collects the following information of placement of peripheral devices on PCI bus:

  • Bus number
  • Slot number
  • Function number

...

Back to Table of Contents

Div
classpagebreak

 

Creation of CHARON-AXP configuration file

...

#
# 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 the xtem from which CHARON-AXP kit)runs
#

load virtualoperator_serial_line OPA0 port=10003 application="putty -load OPA0"console OPA0

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

set ide container="\\.\CdRom0/dev/cdrom"

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

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

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

set PKA container[600] = "C:\My tapes\/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\/my_disks/RZ24.vdisk"

...

Back to Table of Contents

...

Create special directories for storing disk and tape images, as needed. Created directories are referenced in the sample configuration file above.

...> cd C:\
C:\> mkdir "My disks"

C:\> mkdir "My tapes" 

This operation can also be done using Windows Explorer.

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

Image Removed

The main dialog of the utility will appear:

Image Removed

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. Press then the "Create Disk Image" button:

Image Removed

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 Removed

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

Image Removed

...

$ mkdir /my_disks
$ mkdir /my_tapes 

Next, create disk images using the "mkdskcmdutility:

$ mkdskcmd -d rz24 -o /my_disks/rz24.vdisk
Please wait...
100% done
Success.
$ mkdskcmd -d rz23 -o /my_disks/rz23.vdisk
Please wait...
100% done
Success.
$ mkdskcmd -d rz22 -o /my_disks/rz22.vdisk
Please wait...
100% done
Success.
$ mkdskcmd -d rz28 -o /my_disks/bootable.vdisk
Please wait...100% done
Success.

Back to Table of Contents

...

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

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

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

set ide container="\\.\CdRom0/dev/cdrom"

(warning) 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

...

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

...

.cfg" is the configuration file we use in this example):

$ es40.exe migration.cfg

initializing ...

polling for units on kzpba0, slot 2, bus 0, hose 1 ...
pka0.0.0.2.1 PKA0 Q-Logic/ISP PCI SCSI HBA

... enter console

CHARON-AXP/ES40 for Windows x64 Linux (AlphaServer ES40 6/667), Version 4.6.1660316803
(C) 2009-2014 2015 STROMASYS SA.
All rights reserved.

P00>>>boot dqa0

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

...

Login to the source HP Alpha system. Stop all the batch queues, kick off the users, stop all application applications and close databases if any. The commands listed in SYS$MANAGER:SYSHUTDWN.COM may be helpful.  The goal is to close as many files as possible. The system disk will have several files opened (pagefile, swapfile, etc.), but this is normal.

...

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 DKA0:
newvms$  BACKUP BACKUP/IMAGE DKA300:[000000]DKA0.BCK/SAVE DKA0:
newvms$  DISMOUNT DISMOUNT DKA0:
newvms$ MOUNT/FOREIGN FOREIGN DKA100:
newvms$ BACKUP/IMAGE DKA300:[000000]DKA100.BCK/SAVE DKA100:
newvms$ DISMOUNT DKA100:
newvms$ MOUNT/FOREIGN FOREIGN DKA200:
newvms$ BACKUP/IMAGE DKA300:[000000]DKA200.BCK/SAVE DKA200:
newvms$ DISMOUNT DKA200:

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.

(info) The NIC can be disabled with a "connection:disabled" statement in the CHARON configuration file.

...

  • Connect a SCSI tape drive to CHARON-AXP host via a PCI card 
    • Map the tape drive in the CHARON-AXP configuration file

           a. Restore source HP Alpha system backups from tape to disk images via OpenVMS running on CHARON-AXP.
           b. Boot from standalone backups and restore its content to CHARON-AXP virtual disks

    • Dump source HP Alpha system backups to tape images with "mtd" utility and:
           a. Boot from freshly installed OpenVMS system and restore the tape images to CHARON-AXP virtual disks
           b. Boot from standalone backups and restore its content to CHARON-AXP virtual disks
  • Create a network cluster between the source HP Alpha system and CHARON-AXP (it is possible to use the source system as boot server); then simple backup from one disk to another:

    $ BACKUP/IMAGE/IGNORE=INTERLOCK REAL$DKA0: DKA0:

...