I have a problem about cross-architecture satellite booting.

I have a problem about cross-architecture satellite booting.

Post by fairfi.. » Tue, 25 Feb 1997 04:00:00





Quote:> We want to make a cluster by following configuration.
> This cluster have one alpha 8400 server, 40 AXP satellites,
> 30 VAX satellites and dual HSJ40 disk controllers.
> AXP, VAX system disk is located on the CI for assess by
> bootserver.
[...]
> I know how to install Alpha OpenVMS. but I don't know how to
> install VAX OpenVMS. Because VAX server don't exist in this
> cluster.

        You MUST have at least ONE VAX  that has LOCAL ACCESS to the VAX
    system disk, or to a disk which can be made a copy of the VAX system
    disk.   There  is NO way to install or upgrade OpenVMS/VAX  from  an
    OpenVMS/Alpha system.  Period.

        You have essentially two choices.  (1) Get an inexpensive(?) VAX
    that can be attached to the  CI  and  directly access the VAX system
    disk hosted by the HSJ's.  Or (2) add a local disk to one of the VAX
    satellites.   Make  sure that disk is large enough to take an  image
    backup of the HSJ-hosted VAX system disk (that is, it ought to be at
    least as big).

        If you're going the local-disk-on-a-satellite way, you'd find it
    easiest if that satellite VAX also had a local CDrom drive, although
    "there are ways" to do an  install,  the first time, without a CDrom
    or  tape  drive (don't ask, but I _have_ done it :-).   Once  you've
    gotten to the point of having a VAX system disk  somewhere,  you  do
    upgrades by taking a disk-to-disk image backup of the HSJ VAX system
    to  the  satellite's  disk,  do the upgrade on the satellite's disk,
    then disk-to-disk image backup of  the  satellite's  disk to the HSJ
    disk.

        With a VAX on the CI,  you  just install and upgrade directly to
    the HSJ disk.

        -Ken
--

 SLAC, P.O.Box 4349, MS 46  |  DECnet:   45537::FAIRFIELD (45537=SLACVX)
 Stanford, CA   94309       |  Voice:    415-926-2924    FAX: 415-926-3515
 -------------------------------------------------------------------------
 These opinions are mine, not SLAC's, Stanford's, nor the DOE's...

 
 
 

I have a problem about cross-architecture satellite booting.

Post by Hyun Suk Jun » Wed, 26 Feb 1997 04:00:00


Hi, All.

We want to make a cluster by following configuration.
This cluster have one alpha 8400 server, 40 AXP satellites,
30 VAX satellites and dual HSJ40 disk controllers.
AXP, VAX system disk is located on the CI for assess by
bootserver.

--- Configuration ----

                   +- VAX system disk -+
           +-------|                   |-------+
           |       +- AXP system disk -+       |  
         HSJ40                               HSJ40
           |                                   |
           +---------------+  +----------------+
                           |  |
                       star coupler  
                             |         CI interconected.
                        Alpha 8400    -------------------
                             |
                       GIGA  SWITCH
                            | |        FDDI interconnected.
                          NIS600      ---------------------
                             |         ETHERNET
=----+--------------------+-----------------+----------=
        |                                      |
   VAX satellites                       Alpha satellites

I know how to install Alpha OpenVMS. but I don't know how to
install VAX OpenVMS. Because VAX server don't exist in this
cluster.

I read a book for VMScluster systems for OpenVMS.  I found about
cross-architecture satellite booting. In this book, I can't find
how to install VAX OpenVMS and register VAX satellites in
VMS cluster.

How can I install VAX OpenVMS system disk?
Or is there a better way?
I hope how to register VAX satellites in VMS cluster.

Thanks,
Hyun-Suk, Jung.

+-----------------------------------------------------+
+                                                     +
+          Hyun Suk Jung / Design Engineer            +
+                                                     +
+       Intergrated CAD/CAM Development Team,         +
+       Engineering & Technology Division,            +
+       DAEWOO HEAVY IND. Ltd.                        +
+                                                     +

+     Phone   : +82 558 680 4129                      +
+     FAX     : +82 558 680 2142,2143                 +
+     Address : 1, Ajoo-dong, Koje-shi,               +
+               Kyongsangnam-do, KOREA 656-714        +
+                                                     +
+-----------------------------------------------------+

 
 
 

I have a problem about cross-architecture satellite booting.

Post by Tim Shop » Wed, 26 Feb 1997 04:00:00




>        If you're going the local-disk-on-a-satellite way, you'd find it
>    easiest if that satellite VAX also had a local CDrom drive, although
>    "there are ways" to do an  install,  the first time, without a CDrom
>    or  tape  drive (don't ask, but I _have_ done it :-).

That got me thinking... I suppose you could taking an Alpha running VMS
and do a "BACKUP/RESTORE" of the first (and maybe
some subsequent) saveset(s) of the VAX/VMS distribution
onto a disk, and then boot the VAX system from that disk.  Once
you're up and in the cluster (or even just running DECNET) you could
proceed to do the rest of the installation.  Or is there something
much more fiendishly clever? :-)  


 
 
 

I have a problem about cross-architecture satellite booting.

Post by John Macalliste » Wed, 26 Feb 1997 04:00:00


If the standard installation procedures don't allow for installing
 VAX/VMS on an AlphaVMS system, you could simply attach a disk,
 temporarily, to one of the VAX satellites and install/upgrade
 VMS on that (perhaps in stand-alone mode) and then copy the VMS
 files on to the main server disk.
If the temporary disk is actually a straight copy of the real
 server disk the installation should not be difficult.
John
                                                    +-------------------+
                                                    |   ( )       ( )   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Name: John B. Macallister            |     Postal address : Nuclear Physics Laboratory, Keble Road, Oxford OX1 3RH, UK.         |
| Telephone: +44-1865-273388 (direct) +44-1865-273333 (tel reception)  |   Fax:  +44-1865-273418    |    Telex: 83295 NUCLOX G    |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

 
 
 

I have a problem about cross-architecture satellite booting.

Post by pre » Thu, 27 Feb 1997 04:00:00



> Hi, All.

> We want to make a cluster by following configuration.
> This cluster have one alpha 8400 server, 40 AXP satellites,
> 30 VAX satellites and dual HSJ40 disk controllers.
> AXP, VAX system disk is located on the CI for assess by
> bootserver.

> --- Configuration ----

>                    +- VAX system disk -+
>            +-------|                   |-------+
>            |       +- AXP system disk -+       |  
>          HSJ40                               HSJ40
>            |                                   |
>            +---------------+  +----------------+
>                            |  |
>                        star coupler  
>                              |         CI interconected.
>                         Alpha 8400    -------------------
>                              |
>                        GIGA  SWITCH
>                             | |        FDDI interconnected.
>                           NIS600      ---------------------
>                              |         ETHERNET
> =----+--------------------+-----------------+----------=
>         |                                      |
>    VAX satellites                       Alpha satellites

Two ways. The easy one is to pull a drive from the HSJ, plus it
into a VAX satellite and install VMS onto it. when it is all up,
run cluster_config and boot in another VAX. Oh, make sure you
have all of sysuaf, and the net work files on a common disk for
the cluster to use. See the manual for that.

You now have 1 machine that can local boot, and a vax satellite.

Plug the disk back onto the HSJ, change the disk parameter in
NCP/LANCP and boot the satellite... then add the other systems.

The other way is to drop the... B savest onto the disk, set up
the mop boot stuff for a vax, then boot it via ethernet. Two
traps. The vax system disk must NOT be mounted on the 8400!
So you need the boot files for the vax on the alphas disks.

The first method is much less pain. And, I would add that
KEEPING a vax with a local disk ( or a couple in fact ) is
a wise move. It will make fife MUCH easier in the future.

~Paul

 
 
 

I have a problem about cross-architecture satellite booting.

Post by fairfi.. » Mon, 03 Mar 1997 04:00:00




[...]

Quote:> That got me thinking... I suppose you could taking an Alpha running VMS
> and do a "BACKUP/RESTORE" of the first (and maybe
> some subsequent) saveset(s) of the VAX/VMS distribution
> onto a disk, and then boot the VAX system from that disk.  Once
> you're up and in the cluster (or even just running DECNET) you could
> proceed to do the rest of the installation.  Or is there something
> much more fiendishly clever? :-)  

        Nope, I'm hardly clever, let alone _fiendishly_ clever! :-)

        You've got the basic idea, but modify it slightly: Restore the B
    saveset to the target to-be-VAX system disk.  If I recall (it's been
    a little while), this is a  image backup which establishes the basic
    file  structure and creates a VAX-bootable disk.  Next, simply  copy
    all the other savesets (C --> F, or whatever)  to  the  MFD  of  the
    target  disk.   It's  also  convenient  to  copy any _other_ product
    installation  savesets,  DECwindows,  Multinet,  whatever,  to  that
    directory  as  well, assuming you've enough space.  Finally,  remove
    the disk from the system on which you prepared it and install it  in
    the  satellite  (or  whatever  VAX).   Now  boot  that disk: the VMS
    installation procedure will  take  off  automatically  and you're on
    your way!  :-)

        -Ken
--

 SLAC, P.O.Box 4349, MS 46  |  DECnet:   45537::FAIRFIELD (45537=SLACVX)
 Stanford, CA   94309       |  Voice:    415-926-2924    FAX: 415-926-3515
 -------------------------------------------------------------------------
 These opinions are mine, not SLAC's, Stanford's, nor the DOE's...

 
 
 

1. Cross Architecture Boot with Cluster_Config ?

Configuring and running a VMScluster is not new technology.
Mixed Architecture Cluster is also also not really new.

But Cross Architecture Boot (booting VAX from Alpha or Alpha from VAX)
was unsupported since day one (for VAX satellites you needed a VAX
bootserver and for Alpha satellites you needed an Alpha Bootserver -
eg. an OpenVMS upgrade still needs directly attached disks and
CLUSTER_CONFIG.COM can only manipulate the current system disk) and
only did work if you do all modifications the CLUSTER_CONFIG.COM does
by hand. Eg. the directory structure and especially the MOP database...

eg. a VAX client looks like:
    Tertiary Loader { SYS$SYSTEM:TERTIARY_VMB.EXE }

while an Alpha client looks like

Are there any plans for supporting Cross-Archtitecture (fully with Cross
Configuration) VMSclusters ? Or does it already work and I only missed
it because the last time I used the CLUSTER_CONFIG.COM directly was the
time when the Alpha got introduced in the early 90. ?

If not, won't OpenVMS IPF require to change/support this ?

TIA

--
Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651
Network and OpenVMS system manager  Fax.    +43 1 81111-888

A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"

2. Rotation in spherical images.

3. Satellite switching boot nodes in multiple boot node LAVC

4. Splitting up an image in a table.

5. decnet problem with satellite boot

6. A2000 RGB port.

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

8. SerialOp -> BlockDriver utility...

9. Problem with satellite boot

10. problem with satellite boot

11. Cross Architecture ?

12. Q: Cross Architecture ?

13. Bugcheck booting satellite after upgrade to 7.1-2