VAX Cluster Setup
This section illustrates the setup of the VAX cluster software on the SIMH instance running on the PowerMac G5 (TINY).
Cluster ConfigurationThe first step is to establish TINY as a boot node so that the other physical VAX systems can boot from TINY. This will setup up a network based LAVC; Local Area VAX Cluster. The pre-requisites are that a VAX cluster license was installed and there are operating system licenses with sufficient units to accommodate the stellite nodes. In the LAVC environments, all licenses and operating system images are kept on the cluster boot node (TINY).
| Part 1: Boot Node Setup |
|---|
Manuels-PowerBook-G4-15:~ manuel$ telnet 192.168.0.251
Trying 192.168.0.251...
Connected to 192.168.0.251.
Escape character is '^]'.
Welcome to OpenVMS (TM) VAX Operating System, Version V7.1
Username: system
Password:
Welcome to OpenVMS VAX V7.1
****************** Notice *************
UCX TCP/IP installed
Decnet Phase IV installed
Fortran and C compilers are installed
***************************************
Last interactive login on Sunday, 7-APR-2019 07:49
Last non-interactive login on Sunday, 31-MAR-2019 16:40
Yes Master?
Yes Master?
Yes Master?
Yes Master? set def sys$manager
Yes Master? @cluster_config
Cluster Configuration Procedure
Executing on a VAX System
This system is running DECnet Phase IV.
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 BRIEF".
This VAX node is not currently a cluster member.
MAIN MENU
1. ADD TINY to existing cluster, or form a new cluster.
2. MAKE a directory structure for a new root on a system disk.
3. DELETE a root from a system disk.
4. EXIT from this procedure.
Enter choice [1]:
Will the LAN be used for cluster communications (Y/N)? y
Enter this cluster's group number: 1
Enter this cluster's password:
Re-enter this cluster's password for verification:
Will TINY be a boot server [Y]?
Verifying circuits in network database...
Note:
This procedure will establish circuit QNA-0 for providing boot service.
Updating permanent network database...
Enter a value for TINY's ALLOCLASS parameter [0]:
Does this cluster contain a quorum disk [N]?
WARNING: TINY will be a voting cluster member. EXPECTED_VOTES for
this and every other cluster member should be adjusted at
a convenient time before a reboot. For complete instructions,
check the section on configuring a cluster in the "OpenVMS
Cluster Systems" manual.
Execute AUTOGEN to compute the SYSGEN parameters for your configuration
and reboot TINY with the new parameters. This is necessary before
TINY can become a cluster member.
Do you want to run AUTOGEN now [Y]?
Running AUTOGEN -- Please wait.
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 extended
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
upgrade will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
on node TINY
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:09.75 %%%%%%%%%%%
Operator _TINY$TNA3: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:09.75 %%%%%%%%%%%
Operator status for operator _TINY$TNA3:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE,
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,
OPER12
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 2
%SHUTDOWN-I-SHUTNET, the DECnet network will now be shut down
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:10.61 %%%%%%%%%%%
Message from user DECNET on TINY
DECnet shutting down
SHUTDOWN message on TINY from user SYSTEM at _TINY$TNA3: 10:17:10
TINY will shut down in 0 minutes; back up SOON. Please log off node TINY.
Reboot system with AUTOGENerated parameters
2 terminals have been notified on TINY.
%SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:14.22 %%%%%%%%%%%
Message from user SYSTEM on TINY
_TINY$TNA3:, TINY shutdown was requested by the operator.
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:14.26 %%%%%%%%%%%
Logfile was closed by operator _TINY$TNA3:
Logfile was TINY::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;51
%%%%%%%%%%% OPCOM 7-APR-2019 10:17:14.30 %%%%%%%%%%%
Operator _TINY$TNA3: has been disabled, username SYSTEM
Connection closed by foreign host.
|
Boot Node Configuration
The next task is to setup TINY as a boot node to it can serve VMS to its satellites systems.
| Part 2: Configuring the boot node |
|---|
Yes Master? @sys$manager:cluster_config
Cluster Configuration Procedure
Executing on a VAX System
This system is running DECnet Phase IV.
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 BRIEF".
TINY 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 TINY.
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]: 3
CHANGE Menu
1. Enable TINY as a disk server.
2. Disable TINY as a disk server.
3. Enable TINY as a boot server.
4. Disable TINY as a boot server.
5. Enable the LAN for cluster communications on TINY.
6. Disable the LAN for cluster communications on TINY.
7. Enable a quorum disk for TINY.
8. Disable a quorum disk for TINY.
9. Change TINY's satellite's Ethernet or FDDI hardware address.
10. Enable TINY as a tape server.
11. Disable TINY as a tape server.
12. Change TINY's ALLOCLASS value.
13. Change TINY's TAPE_ALLOCLASS value.
14. Return to MAIN menu.
Enter choice [14]: 3
Verifying circuits in network database...
A boot server must have a circuit enabled for providing
downline load service to satellites.
Note:
TINY has 1 Ethernet datalink(s) in the ON state
that can be used to provide boot service to satellites.
This procedure will establish Ethernet circuit QNA-0 for boot serving.
Updating permanent network database...
In order to enable or disable DECnet MOP service in the volatile
network database, DECnet traffic must be interrupted temporarily.
Do you want to update the volatile database now [Y]?
Enter a value for TINY's ALLOCLASS parameter [0]:
The configuration procedure has completed successfully.
TINY has been enabled as a boot server. Disk serving and
LAN capabilities are enabled automatically. If TINY was
not previously set up as a disk server, please run AUTOGEN
to reboot TINY:
$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT
Yes Master? @sys$update autogen getdata feedback reboot
%DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSUPD].COM; as input
-RMS-E-FNF, file not found
Yes Master? @sys$update:autogen getdata reboot feedback
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;2 created
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;2 created
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
upgrade will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
on node TINY
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:41.58 %%%%%%%%%%%
Operator _TINY$TNA1: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:41.58 %%%%%%%%%%%
Operator status for operator _TINY$TNA1:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, LICENSE,
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,
OPER12
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1
%SHUTDOWN-I-SHUTNET, the DECnet network will now be shut down
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
SHUTDOWN message on TINY from user SYSTEM at _TINY$TNA1: 20:52:42
TINY will shut down in 0 minutes; back up SOON. Please log off node TINY.
Reboot system with AUTOGENerated parameters
2 terminals have been notified on TINY.
%SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:42.94 %%%%%%%%%%%
Message from user DECNET on TINY
DECnet shutting down
%SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:51.51 %%%%%%%%%%%
Message from user SYSTEM on TINY
_TINY$TNA1:, TINY shutdown was requested by the operator.
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:51.57 %%%%%%%%%%%
Logfile was closed by operator _TINY$TNA1:
Logfile was TINY::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;56
%%%%%%%%%%% OPCOM 7-APR-2019 20:52:51.60 %%%%%%%%%%%
Operator _TINY$TNA1: has been disabled, username SYSTEM
|
Boot Node as a Disk Server
The boot node must be configured to serve disks over DECNET so that disks can be shared amongst cluster nodes.
| Part 3: Configuring the boot node to serve disks |
|---|
Yes Master? @sys$manager:cluster_config
Cluster Configuration Procedure
Executing on a VAX System
This system is running DECnet Phase IV.
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 BRIEF".
TINY 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 TINY.
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]: 3
CHANGE Menu
1. Enable TINY as a disk server.
2. Disable TINY as a disk server.
3. Enable TINY as a boot server.
4. Disable TINY as a boot server.
5. Enable the LAN for cluster communications on TINY.
6. Disable the LAN for cluster communications on TINY.
7. Enable a quorum disk for TINY.
8. Disable a quorum disk for TINY.
9. Change TINY's satellite's Ethernet or FDDI hardware address.
10. Enable TINY as a tape server.
11. Disable TINY as a tape server.
12. Change TINY's ALLOCLASS value.
13. Change TINY's TAPE_ALLOCLASS value.
14. Return to MAIN menu.
Enter choice [14]: 1
Will TINY serve RFxx disks [N]?
Enter a value for TINY's ALLOCLASS parameter [0]:
The configuration procedure has completed successfully.
TINY has been enabled as a disk server. In MODPARAMS.DAT:
MSCP_LOAD has been set to 1
MSCP_SERVE_ALL has been set to 2
Please run AUTOGEN to reboot TINY:
$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT
Yes Master? @sys$update:autogen getdata reboot feedback
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;3 created
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;3 created
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
upgrade will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
on node TINY
|
This section shows how a satellite node was configured as a VAX cluster member that boots its VMS operating system image from TINY over the network using the MOP protocol over DECNET. To configure a satellite node you need to know the MAC address of the satellite VAX which is displayed at system boot time. Additionally you need to determine the proposed DECNET node number and name for the satellite. This section only shows the partial satellite configuration, not a complete log file was obtained.
| Part 4: Adding a satellite VAX node |
|---|
Yes Master? @sys$manager:cluster_config
Cluster Configuration Procedure
Executing on a VAX System
This system is running DECnet Phase IV.
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 BRIEF".
TINY 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 TINY.
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
What is the node's DECnet node name? hawk
What is the node's DECnet node address? 1.32
Will HAWK be a satellite [Y]? y
WARNING: When the new node is a satellite, the network databases on
TINY are updated by this procedure. You must see to it that
the network databases on all other cluster members are updated.
For help, refer to the "OpenVMS Cluster Systems" manual.
|
Once satellites nodes are added to the boot node, an AUTOGEN should be run to update the MODPARAMS file with any recommended changes. In the example below, the swap and page files were adjusted by the autogen process.
| Optional: Run AUTOGEN on the boot node |
|---|
Yes Master? @sys$update:autogen getdata setparams
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
******************
%AUTOGEN-E-PHASE, Errors were detected with the FEEDBACK data.
The ending phase is being changed to "TESTFILES" so that no
modifications will take place without you first being able to
review the results of feedback as reported in
SYS$SYSTEM:AGEN$PARAMS.REPORT. If the results are OK, re-invoke
AUTOGEN as follows:
@SYS$UPDATE:AUTOGEN GENPARAMS SETPARAMS FEEDBACK
If the results are NOT OK, you may wish to invoke AUTOGEN
without using the feedback mechanism as follows:
@SYS$UPDATE:AUTOGEN GETDATA SETPARAMS NOFEEDBACK
******************
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, TESTFILES phase is beginning.
AUTOGEN calculations for page, swap, and dump files.
Page and Swap file calculations.
PAGEFILE1_SIZE information (for SYS$SYSTEM:PAGEFILE.SYS):
Feedback information.
Old value was 122000, New value is 61000
Maximum observed usage: 0
SYS$SYSTEM:PAGEFILE.SYS would have been created with 61000 blocks.
SWAPFILE1_SIZE information (for SYS$SYSTEM:SWAPFILE.SYS):
Feedback information.
Old value was 45000, New value is 22500
Maximum observed usage: 0
SYS$SYSTEM:SWAPFILE.SYS would have been created with 22500 blocks.
Dumpfile calculations:
Current dump file is SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP
Current dump file size is currently 262173.
Please leave in place the 2049 block file called
TINY$DUA0:[SYS0.SYSEXE]ERRORLOG.DMP;, as required
to accomodate error log buffers.
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
|