Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > it.comp.retrocomputing > #51283
| From | Powell <demasir@postacalda.com> |
|---|---|
| Newsgroups | it.comp.retrocomputing |
| Subject | Re: VAX 4000-200 e cluster Digital |
| Date | 2019-06-21 17:47 +0200 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qeiu6a$1rem$1@gioia.aioe.org> (permalink) |
| References | <qe2chb$ol2$1@gioia.aioe.org> <d8rcge1j6ir4448e38bua2ld9ra75h314o@4ax.com> |
Il 16/06/2019 18.49, G. ha scritto:
> esempio, a suo tempo, ero riuscito con l'emulatore Simh e con vmware
>> a creare due macchine in cluster: il VAX 4000-200 senza dischi al boot
>> vede solo il device ethernet (EZA0).
>> Mi chiedo: sarebbe possibile farla funzionare come satellite, quindi
>> fare il boot dal primo VAX?
> Certo che sì :)
>
> Occorre un cluster a cui aggiungere un satellite, dopodiché si fa il boot
> via rete del VAX e quello viene caricato dal cluster e gli si associa.
>
> Lo puoi fare anche con l'altro VAX che hai recuperato, ma ti consiglio di
> fare prima qualche esperimento con una macchina emulata
Ho fatto ripartire le macchine emulate e ho collegato il VAX 4000-200 senza dischi sullo stello switch di rete:
OpenVMS (TM) VAX Version V7.3
%SYSINIT, waiting to form or join a VMScluster system
%VAXcluster-I-LOADSECDB, loading the cluster security database
%MSCPLOAD-I-LOADMSCP, loading the MSCP disk server
...
Username: system
Password:
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
Last interactive login on Sunday, 1-JUL-2012 18:08
$
$ sh net
Product: DECNET Node: PSWVAX Address(es): 1.1
Product: TCP/IP Node: vax.homeip.net Address(es): 192.168.1.111
$
$ sh cluster
View of Cluster from system ID 1025 node: PSWVAX 1-JUL-2012 19:
+-----------------------------+
¦ SYSTEMS ¦ MEMBERS ¦
+-------------------+---------¦
¦ NODE ¦ SOFTWARE ¦ STATUS ¦
+--------+----------+---------¦
¦ PSWVAX ¦ VMS V7.3 ¦ MEMBER ¦
+--------+----------+---------¦
¦ MCRVAX ¦ VMS V7.3 ¦ MEMBER ¦
+-----------------------------+
$
$ @cluster_config
Cluster Configuration Procedure
Executing on a VAX System
DECnet Phase IV is installed on this node.
DECnet is not running on this node.
LANACP LAN server process is running.
LANACP will be used for all satellite boot serving.
Cluster Configuration Procedure
Executing on a VAX System
DECnet Phase IV is installed on this node.
The LAN, not DECnet, will be used for MOP downline loading.
To ensure that this procedure is executing with the required
privileges, invoke it from the system manager's account.
Enter a "?" for help at any prompt. If you are familiar with
the execution of this procedure, you may want to mute extra notes
and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF".
PSWVAX is a VAX system and currently a member of a cluster
so the following functions can be performed:
MAIN MENU
1. ADD a VAX node to the cluster.
2. REMOVE a node from the cluster.
3. CHANGE a cluster member's characteristics.
4. CREATE a duplicate system disk for PSWVAX.
5. MAKE a directory structure for a new root on a system disk.
6. DELETE a root from a system disk.
7. EXIT from this procedure.
Enter choice [1]: 1
This ADD function will add a new VAX node to the cluster.
WARNING: If the node being added is a voting member, EXPECTED_VOTES for
every cluster member must be adjusted. For complete instructions
check the section on configuring a cluster in the "OpenVMS Cluster
Systems" manual.
CAUTION: If this cluster is running with multiple system disks and
common system files will be used, please, do not proceed
unless appropriate logical names are defined for cluster
common files in SYLOGICALS.COM. For instructions, refer to
the "OpenVMS Cluster Systems" manual.
Do you want to continue [N]? Y
Will the node be a satellite [Y]?
Verifying LAN adapters in LANACP database...
What is the node's SCS node name?
Adesso come si va avanti? Dove prendo SCS node name?
Grazie
Back to it.comp.retrocomputing | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-15 11:07 +0200
Re: VAX 4000-200 e cluster Digital G. <gerry77@no.spam.mail.com> - 2019-06-16 18:49 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-17 09:52 +0200
Re: VAX 4000-200 e cluster Digital G. <gerry77@no.spam.mail.com> - 2019-06-18 06:14 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-19 10:33 +0200
Re: VAX 4000-200 e cluster Digital G. <gerry77@no.spam.mail.com> - 2019-06-20 04:32 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-21 17:47 +0200
Re: VAX 4000-200 e cluster Digital G. <gerry77@no.spam.mail.com> - 2019-06-22 06:02 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-22 14:58 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-22 15:09 +0200
Re: VAX 4000-200 e cluster Digital G. <gerry77@no.spam.mail.com> - 2019-06-23 00:20 +0200
Re: VAX 4000-200 e cluster Digital Lead_Oxide <lead@tin.it.invalid> - 2019-06-24 12:39 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-24 14:53 +0200
Re: VAX 4000-200 e cluster Digital Powell <demasir@postacalda.com> - 2019-06-25 12:28 +0200
csiph-web