PRIMECLUSTER Installation and Administration Guide 4.2 (Linux for Itanium)

5.1.2.3.1 Setting up the MMB Shutdown Facility

Registering MMB information

Carry out the MMB information registration described here after "Setting Up CF and CIP" and before "Setting Up the Shutdown Daemon," which is described later.

1. Execute the "clmmbsetup -a" command on all nodes, and register the MMB information.

   For instructions on using the "clmmbsetup" command, see the "clmmbsetup" manual page.

   # /etc/opt/FJSVcluster/bin/clmmbsetup -a mmb-user

   Enter User's Password:
   Re-enter User's Password:
   #

   For mmb-user and User's Password, enter the following values that were checked in "Checking the Shutdown Agent Information."

   mmb-user

   User's name for controlling the MMB with RMCP

    

   User's Password

   User's password for controlling the MMB with RMCP.

    

2. Execute the "clmmbsetup -l" command on all nodes, and check the registered MMB information.

   If the registered MMB information was not output on all nodes in Step 1, start over from Step 1.

   # /etc/opt/FJSVcluster/bin/clmmbsetup -l

   cluster-host-name user-name
   -----------------------------------
   node1 mmb-user
   node2 mmb-user
   #

Setting up the shutdown daemon

On all nodes, create /etc/opt/SMAW/SMAWsf/rcsd.cfg with the following information:

CFNameX,weight=weight,admIP=myadmIP: agent=SA_xxx,timeout=20
CFNameX,weight=weight,admIP=myadmIP: agent=SA_xxx,timeout=20

  CFNameX:Specify the CF node name of the cluster host.

  weight:Specify the weight of the SF node.

  myadmIP:Specify the IP address of the administration LAN for the local node.

  agent=SA_xxx:Specify the name of the shutdown agent.

To set the node to panic status through the MMB

Specify "SA_mmbp".

To reset the node through the MMB

Specify "SA_mmbr".

Example) Shown below is a setup example for a 2-node configuration.

# cat /etc/opt/SMAW/SMAWsf/rcsd.cfg

node1,weight=2,admIP=fuji2:agent=SA_mmbp,timeout=20:agent=SA_mmbr,timeout=20
node2,weight=2,admIP=fuji3:agent=SA_mmbp,timeout=20:agent=SA_mmbr,timeout=20

• For the shutdown agents to be specified in the rcsd.cfg file, set both the SA_mmbp and SA_mmbr shutdown agents in that order.

• Set the same contents in the rcsd.cfg file on all nodes. Otherwise, a malfunction may occur.

When creating the /etc/opt/SMAW/SMAWsf/rcsd.cfg file, you can use the /etc/opt/SMAW/SMAWsf/rcsd.cfg.mmb.template file as a template.

Starting the MMB asynchronous monitoring daemon

1. Starting the MMB asynchronous monitoring daemon

   Check that the MMB asynchronous monitoring daemon has been started on all nodes.

   # /etc/opt/FJSVcluster/bin/clmmbmonctl

   If "The devmmbd daemon exists." is displayed, the MMB asynchronous monitoring daemon has been started.

   If "The devmmbd daemon does not exist." is displayed, the MMB asynchronous monitoring daemon has not been started. Execute the following command to start the MMB asynchronous monitoring daemon.

   # /etc/opt/FJSVcluster/bin/clmmbmonctl start

2. Starting the shutdown facility.

   Check that the shutdown facility has been started on all nodes.

   # /usr/bin/sdtool -s

   If the shutdown facility has already been started, execute the following command to restart the shutdown facility on all nodes.

   # /usr/bin/sdtool -r

   If the shutdown facility has not been started, execute the following command to start the shutdown facility on all nodes.

   # /usr/bin/sdtool -b

3. Checking the status of the shutdown facility

   Check the status of the shutdown facility on all nodes.

   # /usr/bin/sdtool -s

Display results of the sdtool -s command

• If "InitFailed" is displayed as the initial status, it means that a problem occurred during initialization of that shutdown agent.

• If "TestFailed" is displayed as the test status, it means that a problem occurred while the agent was testing whether or not the node displayed in the cluster host field could be stopped. Some sort of problem probably occurred in the software, hardware, or network resources being used by that agent.

• If "Unknown" is displayed as the stop or initial status, it means that the SF has still not executed node stop, path testing, or SA initialization. "Unknown" is displayed temporarily until the actual status can be confirmed.

• If TestFailed or InitFailed is displayed, check the SA log file or /var/log/messages. The log file records the reason why SA testing or initialization failed. After the failure-causing problem is resolved and SF is restarted, the status display changes to InitWorked or TestWorked.

If "sdtool -s" is executed immediately after the OS is started, "TestFailed" may be displayed as the test status in the local node. However, this status is displayed because the snmptrapd daemon is still being activated and does not indicate a malfunction. If "sdtool -s" is executed 10 minutes after the shutdown facility is started, TestWorked is displayed as the test status.

In the following example, TestFailed is displayed test status for the local node (node1).

# sdtool -s

Cluster Host Agent SA State Shut State Test State Init State
------------ ----- -------- ---------- ---------- ----------
node1 SA_mmbp.so Idle Unknown TestFailed InitWorked
node1 SA_mmbr.so Idle Unknown TestFailed InitWorked
node2 SA_mmbp.so Idle Unknown TestWorked InitWorked
node2 SA_mmbr.so Idle Unknown TestWorked InitWorked