$ @CLUSTER_CONFIG.COM
Cluster/IPCI Configuration Procedure
CLUSTER_CONFIG_LAN Version V2.84
Executing on an Alpha System
DECnet-Plus is installed on this node.
Alpha satellites will use LANCP, not DECnet, for MOP downline loading.
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".
BISMIL is an Alpha system and currently a member of a cluster
so the following functions can be performed:
MAIN Menu
1. ADD an Alpha 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 BISMIL.
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 [7]: 1
This ADD function will add a new Alpha 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.
If this cluster will run IPCI, then TCP/IP installed on the system
should be version 5.7 and above or else IPCI configuration will be
aborted.
Do you want to continue [Y]? [Return]
Is the node to be a clustered node with a shared SCSI/FIBRE-CHANNEL bus (Y/N)? Y
Will the node be a satellite [Y]? N
What is the node's SCS node name? MOON
DECnet is running on this node. Even though you are configuring a LAN-
based cluster, the DECnet database will provide some information and
may be updated.
What is the node's DECnet fullname? local:.MOON
Do you want to define a DECnet synonym [Y]? N
What is the MOP service client name for this node [MOON]? VENUS
What is the node's SCSSYSTEMID number? 24.123
NOTE: 24.123 equates to an SCSSYSTEMID of 24699
Will MOON run DECnet [Y]? [Return]
Note:
This procedure will not update any network databases
with information about MOON. You must do that
yourself.
Will MOON be a boot server [Y]? [Return]
This procedure will now ask you for the device name of MOON's system root.
The default device name (DISK$ALPHA732:) is the logical volume name of
SYS$SYSDEVICE:.
What is the device name for MOON's system root [default DISK$ALPHA732:]?
What is the name of MOON's system root [SYS1]? [Return]
Creating directory tree SYS1 ...
System root SYS1 created
ENABLE IP for cluster communications (Y/N)? N
CAUTION: If you do not define port allocation classes later in this
procedure for shared SCSI buses, all nodes sharing a SCSI bus
must have the same non-zero ALLOCLASS value. If multiple
nodes connect to a shared SCSI bus without the same allocation
class for the bus, system booting will halt due to the error or
IO AUTOCONFIGURE after boot will keep the bus offline.
WARNING: If BISMIL is sharing the same SCSI bus with MOON, then BISMIL's
ALLOCLASS parameter or port allocation class for the shared bus
must be changed from 0 to the same non-zero value that will be
entered for MOON. Use the CHANGE option of
CLUSTER_CONFIG_LAN.COM to change BISMIL's ALLOCLASS
parameter before MOON is booted.
Enter a value for MOON's ALLOCLASS parameter [1]: [Return]
Does this cluster contain a quorum disk [N]? [Return]
Size of pagefile for MOON [RETURN for AUTOGEN sizing]? [Return]
A temporary pagefile will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.
Size of temporary pagefile [10000]? [Return]
Size of swap file for MOON [RETURN for AUTOGEN sizing]? [Return]
A temporary swap file will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.
Size of temporary swap file [8000]? [Return]
Each shared SCSI bus must have a positive allocation class value. A shared
bus uses a PK adapter. A private bus may use: PK, DR, DV, DQ.
When adding a node with SCSI-based cluster communications, the shared
SCSI port allocation classes may be established in SYS$DEVICES.DAT.
Otherwise, the system's disk allocation class will apply.
A private SCSI bus need not have an entry in SYS$DEVICES.DAT. If it has an
entry, its entry may assign any legitimate port allocation class value:
n where n = a positive integer, 1 to 32767 inclusive
0 no port allocation class and disk allocation class does not apply
-1 system's disk allocation class applies (system parameter ALLOCLASS)
When modifying port allocation classes, SYS$DEVICES.DAT must be updated
for all affected nodes, and then all affected nodes must be rebooted.
The following dialog will update SYS$DEVICES.DAT on MOON.
Enter [RETURN] to continue: [Return]
There are currently no entries in SYS$DEVICES.DAT for MOON.
After the next boot, any SCSI controller on MOON will use
MOON's disk allocation class.
Assign port allocation class to which adapter [RETURN for none]:
Will a local (non-HSx) disk on MOON and not on a hierarchical storage
controller be used for paging and swapping (Y/N)? N
If you specify a device other than DISK$ALPHA732: for MOON's
page and swap files, this procedure will create PAGEFILE_MOON.SYS
and SWAPFILE_MOON.SYS in the <SYSEXE> directory on the device you
specify.
What is the device name for the page and swap files [DISK$ALPHA732:]?
%SYSGEN-I-CREATED, BISMIL$DKB100:<SYS1.SYSEXE>PAGEFILE.SYS;1 created
%SYSGEN-I-CREATED, BISMIL$DKB100:<SYS1.SYSEXE>SWAPFILE.SYS;1 created
The configuration procedure has completed successfully.
MOON has been configured to join the cluster.
Before booting MOON, you must create a new default
bootstrap command procedure for MOON. For instructions,
see your processor-specific installation and operations guide.
The first time MOON boots, NET$CONFIGURE.COM and
AUTOGEN.COM will run automatically.
The following parameters have been set for MOON:
VOTES = 1
QDSKVOTES = 1
After MOON has booted into the cluster, you must increment
the value for EXPECTED_VOTES in every cluster member's
MODPARAMS.DAT. You must then reconfigure the cluster, using the
procedure described in the "OpenVMS Cluster Systems" manual.
|
