Debug Size:

5 - Starting RSF-1 Services

If services are set to stopped and manual on the cluster nodes, they can be started by simply putting the service into Automatic mode on each node.
NOTE - It is advisable to put the primary node mode to Automatic before doing this on the other node, so for example, put POOLA service in Automatic mode on romulus, and POOLB service in Automatic mode on remus
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto POOLA
remus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto POOLB
rsfcli can again be used to verify the services are now running:
romulus# /opt/HAC/RSF-1/bin/rsfcli -v list
romulus:
POOLA running auto unblocked sales_staff-public bge0 20 8
POOLB stopped manual unblocked support_staff-public bge0 20 8
remus:
POOLA stopped manual unblocked sales_staff-public bge0 20 8
POOLB running auto unblocked support_staff-public bge0 20 8
romulus#
It is now safe to put all services in automatic mode across the cluster:
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto POOLB
remus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto staff_staff
romulus# /opt/HAC/RSF-1/bin/rsfcli -v list
romulus:
POOLA running auto unblocked sales_staff-public bge0 20 8
POOLB stopped auto unblocked support_staff-public bge0 20 8
remus:
POOLA stopped auto unblocked sales_staff-public bge0 20 8
POOLB running auto unblocked support_staff-public bge0 20 8
romulus#
If either of the services are not shown as running, view the RSF-1 log files to look for reasons. If a service is shown as broken_safe, it can be repaired and reset to automatic as follows:
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 repair POOLA
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto POOLA
If however a service is showing as broken_unsafe, further investigation is required before a retry should be attempted. Please refer to the RSF-1 Administrator's Guide for further information and detail.

If the services are successfully running, we are now ready to run some failure and failover tests.
Prev Page
Next Page