Booting OpenVMS Alpha as a satellite

Booting OpenVMS Alpha as a satellite

Post by John Nunnall » Sun, 07 Apr 1996 04:00:00



We have an ethernet-based mixed-architecture VMScluster.  We have a
separate system disk for our VAX and Alpha systems.  We're trying to boot
an AlphaServer 1000 4/266 as a satellite into our cluster.  The boot
server is an AlphaServer 1000 4/200 running VMS 6.1-1H2.

I was told by two DEC sources that the 266 would run VMS 6.1-1H2.  We get
the following error when debugging is 'turned on' and I boot the 266 as a
satellite from the 200.  Pardon the long included text, but it appears to
be relevant:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Quote:>>>b -flag 0,10000

(boot ewa0.0.0.11.0 -flags 0,10000)

Trying MOP boot.
.............

Network load complete.
Host name: JOSIE
Host address: aa-00-04-00-03-01

bootstrap code read in
base = 152000, image_start = 0, image_bytes = 7de78
initializing HWRPB at 2000
initializing page table at 144000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%APB-I-APBVER, Alpha Primary Bootstrap, Version X5SC
Initializing XDELTA...
Initial breakpoint not taken...
Checking PALcode revisions...
Creating APBs memory pool...
Initializing TIMEDWAIT constants...
%APB-I-BOOTDEV, Determining boot device type
Initializing the system root specification...
%APB-I-BOOTDRIV, Selecting boot driver
%VMScluster-I-MOPSERVER, MOP server for downline was node JOSIE
%APB-I-BOOTFILE, Selecting boot file
%APB-I-BOOTVOL, Mounting boot volume
%VMScluster-I-INIT, Initializing the NISCA_BTDRIVER
%VMScluster-I-SYSDISK, Satellite system disk is _JOSIE$DKA0:
%VMScluster-I-SYSROOT, Satellite system root is <SYS50.>

%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
.
.
. The last two lines continue in a loop until I halt the computer.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Note that it actually talks out the Ethernet and gets a load file.

So far, DEC thinks it has something to do with the DE450 and DE500
ethernet cards not working with VMS 6.1 on the AlphaServer 1000 platform.
But I was also told by someone else at DEC that the DE500 _would_ work.

JOSIE does appear to be set up properly as a Boot Server and a Disk Server.

Does anybody have any insight?

Thanks in advance for any help.

  Adrian Knight           |       Network Manager

  900 E. Center, Box 2264 |    Phone: (501) 279-4440
  Searcy, AR  72149-0001  |      FAX: (501) 279-4600

 
 
 

Booting OpenVMS Alpha as a satellite

Post by George Corneli » Mon, 08 Apr 1996 05:00:00



Quote:

> We have an ethernet-based mixed-architecture VMScluster.  We have a
> separate system disk for our VAX and Alpha systems.  We're trying to boot
> an AlphaServer 1000 4/266 as a satellite into our cluster.  The boot
> server is an AlphaServer 1000 4/200 running VMS 6.1-1H2.

> I was told by two DEC sources that the 266 would run VMS 6.1-1H2.  We get
> the following error when debugging is 'turned on' and I boot the 266 as a
> satellite from the 200.  Pardon the long included text, but it appears to
> be relevant:

> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>b -flag 0,10000
> (boot ewa0.0.0.11.0 -flags 0,10000)

> Trying MOP boot.
> .............

> Network load complete.

[...]

Quote:> %VMScluster-I-INIT, Initializing the NISCA_BTDRIVER
> %VMScluster-I-SYSDISK, Satellite system disk is _JOSIE$DKA0:
> %VMScluster-I-SYSROOT, Satellite system root is <SYS50.>

> %VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
> %VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
> %VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
> %VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server

I just had something similar happen when I tried to boot a VAXstation
that had previously been in someone else's cluster and it was trying
to join his cluster instead of mine.  Turns out his cluster kept winning
the race for the MOP download, but since the LAVC protocol was not
bridged from his Ethernet to mine, disk serving would not work.

So the problem was that one protocol was getting through and not
the other.  There's a possibility that something like that is your
problem, assuming there is a bridge or switch between the two nodes.
The fix, of course, is to enable the bridging of LAVC packets.

--

- Show quoted text -

>   Adrian Knight           |       Network Manager

>   900 E. Center, Box 2264 |    Phone: (501) 279-4440
>   Searcy, AR  72149-0001  |      FAX: (501) 279-4600


 
 
 

Booting OpenVMS Alpha as a satellite

Post by Carl J Lydi » Mon, 08 Apr 1996 05:00:00



=%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
=%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
=%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
=%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
=..
=..
=.. The last two lines continue in a loop until I halt the computer.
=
=+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
=
=Note that it actually talks out the Ethernet and gets a load file.
=
=So far, DEC thinks it has something to do with the DE450 and DE500
=ethernet cards not working with VMS 6.1 on the AlphaServer 1000 platform.
=But I was also told by someone else at DEC that the DE500 _would_ work.

This is just a guess, but those error messages sound as if they're telling you
that the boot node isn't MSCP serving the system disk:

$ HELP/MESSAGE REINIT_WAIT

 REINIT_WAIT,  Waiting for access to the system disk server

  Facility:     VAXCLUSTER, VAXcluster and VMScluster Facilities

  Explanation:  A satellite is attempting to access a device served to it and
                cannot access it at this time. The satellite will retry for a
                period of time, waiting for the disk server to recover and for
                the device to come on line.

  User Action:  Attempt to connect to the MSCP server for this device. If
                there is a serious problem, abort now. Otherwise, continue
                retrying over a period of time, while allowing the disk server
                some time to recover or reboot.

=JOSIE does appear to be set up properly as a Boot Server and a Disk Server.

Check again just to make sure.  In particular, you'll want to make sure that
MSCP_LOAD is set to 1, and that MSCP_SERVE_ALL is set to either 1 or 2 (you
probably want it set to 1).  Also, look closely at the console messages you get
when you boot the boot node, checking for reports of problems with the MSCP
server.
--------------------------------------------------------------------------------

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.

 
 
 

1. Satellite boot problems OpenVMS AlphA V7.1/DECNET IV

Hi,

After upgrading to 7.1 Ive tried to add a new satellite. The
boot procedure won't finish properly and I have no idea where
to look at.

Here's logfile:

======================================================================

(boot ewa0.0.0.8.0 -flags 0,10000)

Trying MOP boot.
.........

Network load complete.
Host name: DG10
Host address: aa-00-04-00-46-bc

bootstrap code read in
base = 166000, image_start = 0, image_bytes = 71077
initializing HWRPB at 2000
initializing page table at 158000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%APB-I-APBVER, Alpha Primary Bootstrap, Version X6C7
Initializing XDELTA...
Initial breakpoint not taken...
Checking PALcode revisions...
APB-W-PALREV, PALcode revision 5.48 is below supported minimum of 5.56
              PLEASE UPDATE YOUR PALcode
Creating APBs memory pool...
Initializing TIMEDWAIT constants...
%APB-I-BOOTDEV, Determining boot device type
Initializing the system root specification...
%APB-I-BOOTDRIV, Selecting boot driver
%VMScluster-I-MOPSERVER, MOP server for downline was node DG10
%APB-I-BOOTFILE, Selecting boot file
%APB-I-BOOTVOL, Mounting boot volume
%VMScluster-I-INIT, Initializing the NISCA_BTDRIVER
%VMScluster-I-SYSDISK, Satellite system disk is _$70$DKA0:      
%VMScluster-I-SYSROOT, Satellite system root is <SYS10.>                                
%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-E-BOOTINIT, PEM$BOOT_INIT initialization failure

===========================================================================

These lines been produced until I'll switch off the machine.

Thanks for any advice
Eberhard

===============================================================================

Dr. Eberhard Heuser-Hofmann
Univ. Konstanz
Fakultaet fuer Chemie
Universitaets-Strasse 10
D-78464 Konstanz
Germany
Phone: +49-7531-88-2026, FAX: +49-7531-88-3139

===============================================================================

2. Printing large Publisher 98 document on Epson Stylus Color 1520 is truncated

3. Satellite switching boot nodes in multiple boot node LAVC

4. Error 2013 during query

5. decnet problem with satellite boot

6. Sugestions for PLD

7. Bugcheck booting satellite after upgrade to 7.1-2

8. I have a problem about cross-architecture satellite booting.

9. Changing boot disk on satellite member

10. Slooooow satellite boot

11. Satellite not booting

12. Bugcheck booting satellite after upgrade to 7.1-2