Table 8-1 shows the detailed information for each step in the pre-migration stage. Table 8-1 Description of the pre-migration operation flow Step Description 1 Check whether HyperSwap is used. If Yes, go to 2; otherwise, go to 1.1. 1.1 Check whether  LPM_POLICY=unmanage  is set. If Yes, go to 2; otherwise, go to 4 by running the  following command: clodmget -n -f lpm_policy HACMPcluster 2 Change the node to  unmanage resource group  status by running the following command: clmgr stop node <node_name> WHEN=now MANAGE=unmanage 3 Add an entry to the  /etc/inittab  file, which is useful in a node crash before restoring the  managed state, by running the following command: mkitab hacmp_lpm:2:once:/usr/es/sbin/cluster/utilities/cl_dr undopremigrate >  /dev/null 2>&1 4 Check whether RSCT DMS critical resource monitoring is enabled by running the following  command: /usr/sbin/rsct/bin/dms/listdms -s cthags | grep -qw Enabled 5 Disable RSCT DMS critical resource monitoring by running the following commands: /usr/sbin/rsct/bin/hags_disable_client_kill -s cthags /usr/sbin/rsct/bin/dms/stopdms -s cthags 6 Check whether the current  node_timeout  value is equal to the value that you set by running  the following commands: clodmget -n -f lpm_node_timeout HACMPcluster clctrl -tune -x node_timeout 7 Change the CAA  node_timeout  value by running the following command: clmgr -f modify cluster HEARTBEAT_FREQUENCY="600" 8 If storage area network (SAN)-based heartbeating is enabled, then disable this function by  running the following commands: echo 'sfwcom' >> /etc/cluster/ifrestrict clusterconf 296  IBM PowerHA SystemMirror V7.2.3 for IBM AIX and V7.2.2 for Linux