PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System)

5.1.2.2 Using the Shutdown Configuration Wizard

The configuration procedure for the shutdown facility varies depending on the machine type. Check the hardware machine type and configure an appropriate shutdown agent.

• For a PRIMEPOWER 250, or 450:
  • RCI (Panic, Reset) and XSCF (Panic, Reset, Console Break)
    Or
    RCI (Panic, Reset) and RCCU
• For a PRIMEPOWER 200, 400, 600, 650, or 850:
  • RCI (Panic, Reset) and RCCU
• For a PRIMEPOWER 800, 900, 1000, 1500, 2000, or 2500:
  • RCI (Panic, Reset)

For details on the configuration procedure of the shutdown facility and asynchronous monitoring facility, and details on the facilities, see the following manuals:

• "3.3.1.8 PRIMECLUSTER SF" in the "PRIMECLUSTER Concept Guide."
• "8. Shutdown Facility" in "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

WaitForPROM function is not currently supported and its setup is not necessary in normal operation.

Starting up the shutdown configuration wizard

From the CF main window of the Cluster Admin screen, select the Tool menu and then Shutdown Facility -> Configuration Wizard. The shutdown configuration wizard will start.

You can also configure the shutdown facility immediately after you complete the CF configuration with the CF wizard.

The following confirmation popup will appear. Click Yes to start the shutdown configuration wizard.

Selecting a configuration mode

You can select either of the following two modes to configure the shutdown facility:

• Easy configuration (recommended)
• Detailed configuration

This section explains how to configure the shutdown facility using Easy configuration (Recommended). With this mode, you can configure the PRIMECLUSTER shutdown facility according to the procedure.

[Selecting the SF configuration mode]

Select Easy configuration (recommended) and then click <Next>.

Selecting a shutdown agent

After you confirm the hardware machine type, select an appropriate shutdown agent.

[Selecting a shutdown agent]

Select No SCON Configuration.

Then, select all the shutdown agents to be used.

• For a PRIMEPOWER 250 or 450: (Select all of the following.)
  • RCI Panic
  • XSCF Panic
  • Console Break
  • RCI Reset
  • XSCF Reset

  * If you select Console Break, you can select RCCU or XSCF as the Console Break agent. To choose RCCU, you have to configure the RCCU unit in advance.

• For a PRIMEPOWER 200, 400, 600, 650, or 850:
  • RCI Panic
  • Console Break
  • RCI Reset
• For a PRIMEPOWER 800, 900, 1000, 1500, 2000, or 2500:
  • RCI Panic
  • RCI Reset

Upon the completion of configuration, click Next.

Configuring XSCF

If you select XSCF Panic or XSCF Reset for the shutdown agent, the screen for configuring the XSCF will appear.

Enter the settings for XSCF that you recorded in "Check console configuration."

[Configuring XSCF]

XSCF-name

Enter the IP address of XSCF or the host name of XSCF that is registered in the /etc/inet/hosts file.

User-Name

Enter a user name to log in to the control port.

Password

Enter a password to log in to the control port.

Once you have made all the necessary settings, click Next.

Configuring a Console Break agent

If you select Console Break as the shutdown agent, the screen used for selecting a Console Break agent will appear.

[Selecting a Console Break agent]

The selection to be made for the Console Break agent varies depending on the machine type to be set up. Confirm the hardware machine type and then set up an appropriate Console Break agent.

• For a PRIMEPOWER 250 or 450:
  RCCU or XSCF
• For a PRIMEPOWER 200, 400, 600, 650, or 850:
  RCCU

Upon the completion of configuration, click Next.

Configuring RCCU

If you select RCCU as the Console Break agent, you must configure RCCU.

Enter the settings for RCCU that you recorded in "Check console configuration."

If you wish to use RCCU with its factory settings, select Use Defaults.

Otherwise, uncheck Use Defaults, and then enter the user name, password, and superuser password.

[Configuring RCCU (Use Defaults)]

RCCU name

Enter the IP address of RCCU or the host name of RCCU that is described in the /etc/inet/hosts file.

After you have completed this configuration, click Next.

[Configuring RCCU (Does not use default)]

RCCU name

Enter the IP address of RCCU or the host name of RCCU that is described in the /etc/inet/hosts file.

User-Name

Enter a user name to log in to the control port of RCCU.

Password 1

Enter a password to log in to the control port of RCCU.

Confirm

Enter the password that has been set for Password 1 for confirmation.

Password 2 (admin)

Enter a password to log in to the control port of RCCU with superuser access privileges.

Confirm

Enter the password that has been set for Password 2 (Admin) for confirmation.

Once you have completed this configuration, click Next.

Configuring Wait for PROM

Wait for PROM is currently not supported, and normally does not need to be configured.

Uncheck the check box if checked, and then click the [Next] button.

[Configure Wait for PROM]

Entering node weights and administrative IP addresses

Enter the weights of the nodes and the IP addresses for the administrative LAN.

[Entering node weights and administrative IP addresses]

Weight

Enter the weight of the node that constitutes the cluster. Weight is used to identify the survival priority of the node group that constitutes the cluster. Possible values for each node range from 1 to 300.
For details on survival priority and weight, refer to the explanations below.

Admin IP

Enter an IP address directly or click the tab to select the host name that is assigned to the administrative IP address.

Once you have completed this configuration, click Next.

Survival priority

Even if a cluster partition occurs due to a failure in the cluster interconnect, all the nodes will still be able to access the user resources. For details on the cluster partition, see "2.2.2.1 Protecting data integrity" in the "PRIMECLUSTER Concept Guide."
To guarantee the consistency of the data constituting user resources, you have to determine the node groups to survive and those that are to be forcibly stopped.
The weight assigned to each node group is referred to as a "Survival priority" under PRIMECLUSTER.
The greater the weight of the node, the higher the survival priority. Conversely, the less the weight of the node, the lower the survival priority. If multiple node groups have the same survival priority, the node group that includes a node with the name that is first in alphabetical order will survive.

Survival priority can be found in the following calculation:

Survival priority = SF node weight + ShutdownPriority of userApplication

SF node weight (Weight):

Weight of node. Default value = 1. Set this value while configuring the shutdown facility.

userApplication ShutdownPriority:

Set this attribute when userApplication is created. For details on how to change the settings, see "Changing the Operation Attributes of a Cluster Application."

For details on the ShutdownPriority attribute of userApplication, see "Attributes."

Survival scenarios

The typical scenarios that are implemented are shown below:

[Largest node group survival]

• Set the weight of all nodes to 1 (default).
• Set the attribute of ShutdownPriority of all user applications to 0 (default).

[Specific node survival]

• Set the "weight" of the node to survive to a value more than double the total weight of the other nodes.
• Set the ShutdownPriority attribute of all user applications to 0 (default).

In the following example, node1 is to survive:

[Specific application survival]

• Set the "weight" of all nodes to 1 (default).
• Set the ShutdownPriority attribute of the user application whose operation is to continue to a value more than double the total of the ShutdownPriority attributes of the other user applications and the weights of all nodes.

In the following example, the node for which app1 is operating is to survive:

Saving the configuration

Confirm and then save the configuration. In the left-hand panel of the window, those nodes that constitute the cluster are displayed, as are the shutdown agents that are configured for each node.

[Saving the configuration]

Click Next. A popup screen will appear for confirmation. Select Yes to save the setting.

Displaying the configuration of the shutdown facility

If you save the setting, a screen displaying the configuration of the shutdown facility will appear. On this screen, you can confirm the configuration of the shutdown facility on each node by selecting each node in turn.

You can also view the configuration of the shutdown facility by selecting Shutdown Facility -> Show Status from the Tool menu.

[Show Status]

Shut State

"Unknown" is shown during normal system operation. If an error occurs and the shutdown facility stops the relevant node successfully, "Unknown" will change to "KillWorked."

Test State

Indicates the state in which the path to shut down the node is tested when a node error occurs. If the test of the path has not been completed, "Unknown" will be displayed. If the configured shutdown agent operates normally, "Unknown" will be changed to "TestWorked."

Init State

Indicates the state in which the shutdown agent is initialized.

To exit the configuration wizard, click Finish. Click Yes in the confirmation popup that appears.

Confirm that the shutdown facility is operating normally.

If "InitFailed" is displayed in the Initial state even when the configuration of the shutdown facility has been completed or if "Unknown" is displayed in the Test state or "TestFailed" is highlighted in red, the agent or hardware configuration may contain an error. Check the /var/adm/messages file and the console for an error message. Then, apply appropriate countermeasures as instructed the message that is output.

For details on how to respond to the error messages that may be output, see the following manual.

"12.12 Monitoring Agent messages" in the "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."