Satellite boot Alpha V6.2-1H3 from Alpha 7.2-1

[Adrian O]

Trying to satellite boot an alpha 6.2-1H3 (fully patched Alphaserver 4100) with system disk served from an Alphaserver 800 5/500 running V7.2-1 which has both fibre channel and locally attached disks.

If we satellite boot V7.2-1 on the 4100 everything works as expected.

When we try to boot V6.2-1H3, we get the following console output:

bootstrap code read in
FRU table creation disabled
base = 200000, image_start = 0, image_bytes = 7d878
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

%VMScluster-I-MOPSERVER, MOP server for downline was node DEV004
%VMScluster-I-SYSDISK, Satellite system disk is _$255$DKA100:
%VMScluster-I-SYSROOT, Satellite system root is
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
...
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
...
Repeat until ^P

Anyone any ideas as to where/what to look at?

Regards,

Adrian.

[Jon Pinkley]

Is $255$DKA100: MSCP served by DEV004? Is DEV004 the Alphaserver 800 5/500 running 7.2-1?

Jon

[Jon Pinkley]

Are you attempting to satellite boot V6.2-1H3 from a V6.2-1 system or the 7.2-1 system. I have never attempted satellite booting from anything but a common system disk, and multiple VMS versions off a single system disk isn't supported.

More details about the configurations would help diagnosis.

Jon

[Adrian O]

dev003 has no locally attached storage and is trying to be booted as a satellite from dev004.

dev004, the alpha 800, is serving all disks (MSCP_SERVE_ALL=1 and MSCP_LOAD=1).

$255$dka100 is mounted /cluster and (should be) served to the 4100 (dev003) from dev004.

dev004 is running 7.2-1 from its dedicated system disk.

$255$dka100 is a dedicated V6.2-1H3 system disk.

The 2 servers are connected via ethernet crossover cable, and the satellite booting works fine
when both nodes are booting 7.2-1.

Only seeing the problems when trying to boot 6.2-1H3 on dev003.

[Wim Van den Wyngaert]

Did you verify the mc lancp node or ncl mop client config ? Post it ?

Wim

[Wim Van den Wyngaert]

In a mixed-version OpenVMS Cluster system, serving "all available disks" is restricted to its pre-Version 7.2 meaning, that is, serving locally attached disks and disks connected to HSx and DSSI controllers whose node allocation class matches that of the system's node allocation class. To serve "all available disks" in a mixed-version cluster, you must specify the value 9.


Try 9 ?

Wim

[Adrian O]

The MOP load seems to work ok:

LANCP> show node dev003

Node Listing, volatile database:
DEV003 (08-00-2B-C5-C2-23):
MOP DLL: Load file: APB.EXE
Load root: $255$DKA100:
Last file: $255$DKA100:[SYSCOMMON.SYSEXE]APB.EXE
Boot type: Alpha satellite
33 loads requested, 6 volunteered
6 succeeded, 0 failed
Last request was for a system image, in MOP V4 format
Last load initiated 23-JUL-2008 11:06:58 on EWA0 for 00:00:05.26
3224595 bytes, 25143 packets, 0 transmit failures

Totals:
Requests received 33
Requests volunteered 6
Successful loads 6
Failed loads 0
Packets sent 12558
Packets received 12585
Bytes sent 3160548
Bytes received 64047
Last load DEV003 at 23-JUL-2008 11:06:58.59

Rgds

Adrian.

[Adrian O]

Wim,

Tried MSCP_SERVE_ALL=9 yesterday.
Set it to 1 this morning.

Same difference.

Trying with 9 again now...

Rgds,

Adrian

[Wim Van den Wyngaert]

The param is not dynamic. You need to reboot the disk server.

Wim

[Adrian O]

Changed MSCP_SERV_ALL to 9.
Removed quroum disk!
Autogenned, rebooted.

No change.