A.0 Console Commands for Novell Cluster Services

Novell® Cluster Services™ provides several server console commands to help you perform certain cluster-related tasks. Table A-1 lists the cluster-related server console commands and gives a brief description of each command.

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 server console. You can also enter help cluster 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 Cluster Console Commands

Cluster Console Command


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 fail over or fail back to another node. Specify the resource name in the command and use the YES or NO switch to specify whether you want the resource to fail over, fail back, or start.


Equivalent of running scan all, scan for new devices, and scan for new partitions on 0xffff on every node in the cluster. Running this command will cause the cluster to discover new LUNs, devices, and partitions on shared media.


Causes Cluster Services to disregard the current Cluster Volume Broker (CVB) database. Rebuilds the CVB database to allow the use of duplicate pool names.

CVSBIND {ADD, DEL}{resource}{IP address}

Enables applications that rely on the bindery or bindery emulation to access a virtual server on the cluster. Specify the virtual server name for the cluster resource and the IP address for the virtual server. Use the ADD or DEL switch to enable or disable bindery access to the virtual server.

DHCP {context}

Specifies the eDirectory context where DHCP configuration information is stored. This command is useful if you have problems getting DHCP to function properly on a cluster.


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


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


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


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.

MIGRATE {resource}{node name}

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

OFFLINE {resource}

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

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.


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


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

RESTART {seconds}

Restarts Cluster Services software on all servers in the cluster.

STATS {Display, Clear}

Reports the node number, node name, and heartbeat information. You must switch to the log console screen to see cluster statistics.

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.


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