PRIMECLUSTER Global File Services Configuration and Administration Guide 4.6

12.6 How to start up CF by the GUI when a GFS Shared File System is used

This section describes how to start up CF by the GUI after stopping it on all the nodes where a GFS Shared File System is used.

The two start modes of the sfcfrmd daemon of the GFS Shared File System are wait (default) and wait_bg.

If wait is selected, starting the GFS Shared File System will fail because a quorum does not exist until CF is activated on all the nodes. If you need to start CF by the GUI when the CF is stopped on all the nodes, follow the steps below.

See

For information on how to start up CF, see "Starting CF" of "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

1. Select the "Cluster Admin" menu on the Web-Based Admin View operation menu. Select the node where CF will be started, and click <OK>.

   

2. Click <Load driver> then activate the CF driver.

   

3. The "Start CF" window will pop up. Click <OK> to start up CF.

   

4. Since CF is not activated on all the nodes, GFS startup fails then the "Error" window will pop up. Click <No> then cancel the GFS startup processing.

   

5. If the GFS startup is cancelled, the "Error" window will pop up again. Click <No> then cancel the script processing.

   

6. Check if all the services before GFS have been activated then click <OK>.

   

7. Repeat operations from step 1 to 6 on each cluster node then activate all the services before GFS.

   Note

   On the node where CF is activated lastly, GFS startup will succeed because CF has been activated on all the nodes.

8. On any node that cancelled the GFS startup processing, stop CF and restart up CF.

   See

   For information on how to stop CF, see "Stopping CF" of "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

9. Execute Step 8 then activate all the services after GFS on all the nodes where GFS startup is cancelled.