A.1 Cluster Management Commands

To execute a cluster console command, enter cluster followed by the command. For example, if you want to display cluster statistics, enter cluster stats display at the terminal console. You can also enter cluster help at the console prompt to get information on the commands and their functions.

The functions of many of the commands can also be performed using iManager. See the other sections of this document for additional information.

Table A-1 lists the cluster-related terminal console commands and gives a brief description of each command.

Table A-1 Cluster Console Commands

Cluster Console Command

Description

 
ALERT {resource}{YES|NO}

The resource start, failover, or failback mode is set to manual and the resource is waiting to start on a node, or to fail over or fail back to another node.

Specify the resource name in the command and use the YES or NO switch to accept or reject an alert on a resource to control fail over, fail back, or manual start.

Example 

cluster alert res1 yes

CONVERT preview [resource]

CONVERT commit

Beginning in OES 2 SP3, you can use cluster preview without specifying a resource to preview all resources.

CONVERT preview

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 commit

DOWN

Removes all cluster nodes from the cluster. This command has the same effect as executing the CLUSTER LEAVE command on every server in the cluster.

Beginning in OES 2 SP3, you are prompted to confirm the cluster down.

 
EXEC "path_to_script"

Executes the specified script on all nodes in the cluster.

Example 

cluster exec "command"

INFO {All, Basic, Notification, Priority, Protocol, Summary}

Displays information on cluster configuration.

  • All displays a combination of Basic, Notification, Priority, and Protocol information.
  • Basic displays IP address, port, and cluster quorum settings.
  • Notification displays cluster email notification settings.
  • Priority displays the resource priority list.
  • Protocol displays the cluster protocol settings.
  • Summary displays the cluster protocol summary.

Example 

cluster info protocol

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.

 
LEAVE

Removes the node where the command is executed from the cluster. The node will not be visible to other servers in the cluster.

 
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).

Example 

cluster maintenance on

MIGRATE {resource} {node}

Migrates the specified resource from the node where it is currently running to the node that you specify in the command. The node that you specify must be running in the cluster and also be in the resource's Assigned Nodes list.

Example 

cluster migrate res1 node1

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

OFFLINE {resource}

Unloads the specified resource from the node where it is currently running.

Example 

cluster offline res1

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 Assigned Nodes list.

Example 

cluster online res1
cluster online res1 node1

POOLS

Lists the NSS pools on the shared disk system that are accessible by Novell Cluster Services.

 
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.

Example 

cluster rename POOL1_SERVER customized_name22

RESOURCES

Lists all resources that currently exist in the cluster. The resources do not need to be online or running.

 
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.

Beginning in OES 2 SP3, you are prompted to confirm the cluster restart.

Example 

cluster restart 60

SCAN FOR NEW DEVICES

IMPORTANT:This command is obsolete on Linux.

You can use the rescan-scsi-bus.sh script to scan for the new devices on Linux without rebooting. For information, see Scanning for New Devices without Rebooting in the SLES 10 SP4: Storage Administration Guide.

 
SET {Parameter} {Value}

Sets cluster parameters individually for the cluster. See Section 8.0, Configuring Cluster Policies and Priorities 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

STATS {Display, Clear}

The Display parameter reports the node number, node name, and heartbeat information to the console screen.

The Clear parameter resets the various stats counters. This command is useful for troubleshooting network problems related to the cluster heartbeat protocol.

Example 

cluster stats display

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.

 
VIEW

Displays the node name, cluster epoch number, master node name, and a list of nodes that are currently members of the cluster.