A.1 Cluster Management Commands

CONVERT preview [resource]

CONVERT preview

CONVERT commit

Finalizes the cluster conversion from NetWare to Linux after all nodes in a mixed cluster have been converted to Linux. The CLUSTER CONVERT command can be executed only on Linux cluster nodes.

Specify a resource name with the Preview option to view the resource load and unload script changes prior to finalizing the conversion. If you do not provide a resource name, it displays the information for all resources.

Use the Commit switch without specifying a resource to finalize the conversion for all cluster resources.

Examples

cluster convert preview res1
cluster convert preview
cluster convert commit

EXEC "path_to_script"

Executes the specified script on all nodes in the cluster.

Example

cluster exec "command"

JOIN

Adds the node where the command is executed to the cluster and makes the node visible to other servers in the cluster. Novell Cluster Services software must already be installed and running on a node for it to join the cluster.

Example

cluster join

MAINTENANCE {ON|OFF}

Turning this switch on lets you temporarily suspend the cluster heartbeat while hardware maintenance is being performed. This is useful if you want to reset or power down the LAN switch without bringing the cluster servers down.

Turning this switch on from one cluster server puts the entire cluster in maintenance mode.

Running the command without the {ON|OFF} parameter reports the maintenance status of the cluster (that is, whether maintenance mode is on or off).

Examples

cluster maintenance on
cluster maintenance

MONITOR {resource} <start | stop | status>

Manually starts, stops, or checks the status of resource monitoring. The resource must be running on the node where you issue the command. Resource monitoring must be enabled for the resource in order to use this command.

Example

cluster monitor sh_pool_res_01 status

ONLINE {resource}{node name}

Starts the specified resource on the most preferred node that is currently active. You can start the resource on a different node by specifying that node in the command. The node that you specify must be running in the cluster and also be in the resource’s Preferred Nodes list.

Example

cluster online res1
cluster online res1 node1

RENAME <old_resource_name> <new_resource_name>

Renames a pool cluster resource. This command must be issued from the master node. The resource must be in offline state to be renamed. The new name must not exist prior to the renaming.

Renaming the resource does not modify the resource’s virtual server name (NCS:NCP Server object). You can delete and re-create the NCS:NCS Server object with a new name by using iManager.

Example

cluster rename POOL1_SERVER custom_name22

RESTART [seconds]

Restarts Novell Cluster Services software on all servers in the cluster. The cluster leave process begins immediately. Specify a value of 60 or more seconds as the time to wait before the cluster join begins.

The default setting is 60 seconds. The default setting is used if a value is not provided, if the value provided is smaller than 60 seconds, or if the input is invalid.

You are prompted to confirm the cluster restart.

Example

cluster restart 60

SET {Parameter} {Value}

Sets cluster parameters individually for the cluster. See Section 9.0, Configuring Cluster Policies, Protocols, and Properties for more information on cluster parameters.

Specify one of the following parameters and a value for that parameter:

• IPADDRESS sets the cluster master IP address to the specified value. If you change the cluster IP address, you must restart cluster software on all cluster nodes.
• PORT sets, or lets you change, the IP port number of the cluster master.
• QUORUMWAIT sets the amount of time in seconds that the cluster waits before resources start to load.
• QUORUM sets the number of nodes that must be running in the cluster before resources will start to load.
• HEARTBEAT sets the amount of time in seconds between transmits for all nodes in the cluster except the master.
• TOLERANCE sets the amount of time in seconds that the master node gives all other nodes in the cluster to signal that they are alive.
• MASTERWATCHDOG sets the amount of time in seconds between transmits for the master node in the cluster.
• SLAVEWATCHDOG sets the amount of time in seconds that the slave nodes give the master node in the cluster to signal that it is alive.
• MAXRETRANSMITS sets the maximum number of times transmits will be attempted between the master node and slave nodes.
• ENABLEEMAIL enables and disables email notification. You can set the value to OFF to disable email notification, or either CRITICAL or VERBOSE to enable email notification.
• EMAILADDRESSES lets you specify the email addresses used for email notification. The addresses should be separated by spaces. Using this parameter without specifying any addresses clears existing addresses that have been set previously.
• EMAILOPTIONS sets the email notification options. Specify XML as the value to receive email notification in XML format. Not specifying any value with this parameter turns notification in XML format off.
• RESOURCEPRIORITY sets the resource priority for the cluster.

Example

cluster set ipaddress 10.1.1.1

STATUS {resource}

Reports the status of the specified resource. This includes the number of times the resource has been migrated or failed over to another server, the resource state, and the node where the resource is currently running.

Example

cluster status res1