Select the command set best used to verify proper failover function of a new ClusterXL
configuration.
A.
reboot
B.
cphaprob -d failDevice -s problem -t 0 register / cphaprob -d failDevice unregister
C.
clusterXL_admin down / clusterXL_admin up
D.
cpstop/cpstart
I think the answer should be B.
On older versions maybe, it doesn’t work on newer with ClusterXL.
Cluster XL Admin Guide R77, p.62
Recommended method:
– clusterXL_admin down
– clusterXL_admin up
And on the same page it is written that cphaprob commands should be different for a failover testing.
C indeed
C. clusterXL_admin down / clusterXL_admin up
B. for real
Checkpoint official course book:
the best practise method for initiating a failover administratively in a controlled manner (not failure testing) is to run the following command on an active cluster member:
cphaprob -d STOP -s problem -t 0 register
The command actually creates a problem notification entry with no refresh time in a problem state.
Running cphaprob list command will show that – it will show the entry names STOP , … etc …