Fujitsu Siemens Computers SX series User Manual page 320

Performing DR
Further information on MSCF
As of Version 15.0 (component part of OSD/XC V2.0) HIPLEX MSCF automatically
supports Dynamic Reconfiguration. This excludes the possibility of inadvertent failure
detection (caused by the absence of the sign-of-life signals during DR). In terms of MSCF
DR runs as follows:
Start of Dynamic Reconfiguration
The system requests the "Cluster Recovery Lock" from MSCF (console message
MCS1048). When the lock is received the local system is placed in the RECOVERY-
START=*LOCKED status (console message MCS1002).
End of Dynamic Reconfiguration
The system releases the "Cluster Recovery Lock" (console message MCS1049).
When the lock is released the local system is returned to its original status (e.g.
RECOVERY-START=*AUTOMATIC) (console message MCS1002).
The following must be taken into consideration on partner systems in the MSCF
network:
–
–
Notes
While the "Cluster Recovery Lock" is retained on one or more systems in the MSCF
network, automatic failure handling is locked for these systems.
In special situation (e.g. during a CPU reconfiguration of reconfiguration of the global
storage) MSCF rejects the DR request with console message ETMDR04.
320
At the start of DR console message
for the system involved. This status is also displayed by the /SHOW-MSCF-
CONFIGURATION command with an "L" in the RECOVERY-START column.
At the end of Dynamic Reconfiguration console message MCS1040 reports the
original monitoring status for the system involved.
reports the monitoring status LOCKED
MCS1040
Dynamic Reconfiguration
U41272-J-Z385-3-76