Note
The SHOW CLUSTER command continues to show the name of the ISE
replaced. This does not harm the system. After the next reboot, the
replacement ISE name appears.
Note also that the following message is displayed if another node is
already assigned the same SYSTEMID and NODENAME:
%PWA0-REMOTE SYSTEM CONFLICTS WITH KNOWN SYSTEM
In this case, shut down the new node and issue a unique SYSTEMID and
NODENAME for the new node.
6.6.4 Installing an ISE in a Running System
When you install a new ISE in a system that is running, perform the following
steps to initialize the new ISE parameters:
1.
Disable the MSCP server as described in Table 6–5.
Table 6–5 Disabling the MSCP
Disks
Action
RF-series
Press and hold the SU switch/button
SF 72 or SF73
Set the MSCP enable switch
SF35
Press the MSCP/Fault switch (LED is green when enabled)
2.
Set the ISE power switch to on (1). Wait for the drive to start spinning (and
on RF-series disks, the interlock solenoid to lock.
3.
If you have an RF-series disk, release the server setup switch. If you have an
SF disk, continue with Step 4.
4.
Refer to Table 6–3 and Section 6.6.1, and select values for the following
parameters:
•
ALLCLASS
•
FORCENAM
•
FORCEUNI
•
NODENAME
•
UNITNUM
5.
Determine whether the VMS DUP class driver is loaded by entering the
following DCL command:
$ SHOW DEVICE FYA0
Return
If the driver is not loaded, load it by entering the following:
$ MCR SYSGEN
Return
SYSGEN> CONNECT FY0/NOADAPTER
Return
SYSGEN> EXIT
Return
6.
Enter SET HOST/DUP to establish a DUP connection with the ISE as follows:
$
SET HOST/DUP/SERVER=MSCP$DUP/TASK=PARAMS
nodename
Managing Integrated Storage Elements 6–11
