A.1 Using Console Commands

Table A-1 lists the server console commands for managing a business continuity cluster and gives a brief description of each command.

To execute a cluster console command, enter cluster followed by the command. For example, if this cluster belongs to a business continuity cluster, and you want to see this cluster’s peer clusters, enter cluster view at the server console. You can also enter cluster help at the console prompt to get information on the commands and their functions.

IMPORTANT:You must be logged in as the root user, or any other user in admin or ncsgroup.

Some commands prompt the user for input. When using the command in a script, the prompt is not needed. You can use the --noprompt option for the command to bypass the prompted interaction.

For example, the cluster migrate command prompts the user to specify whether to continue migration if the cluster is experiencing connection issues. When you use the cluster migrate command in a script, add the --noprompt option to the command line to skip the prompt:

        cluster migrate --noprompt [source/resource] [destination/nodename]

Table A-1 Console Commands for Business Continuity Clustering

Console Command	Description
cluster connections [-a]	Displays the connection status of the cluster. Specifying -a attempts to show the connection status of all clusters in the business continuity cluster.
cluster credentials [peer_cluster]	Lets you change the administrator user name and password that this cluster uses to connect to the specified peer cluster. The cluster you specify must belong to a cluster that has already been enabled for BCC.
cluster disable [resource]	Disables BCC for the specified cluster resource. The resource you specify must belong to a cluster that has already been enabled for BCC. If no resource is specified, the entire cluster is disabled for BCC. IMPORTANT:Before you disable BCC for a given peer cluster, you must first disable BCC for each of the cluster resources running on that cluster. Before you disable BCC for a given cluster resource, remove the secondary peer clusters from its Assigned list. For information, see Section 8.7, Disabling BCC for a Cluster Resource. After you have disabled BCC for all resources running on the cluster, remove the secondary peer clusters from the Assigned list of preferred nodes, then disable BCC for the cluster. If you disable BCC for a cluster by using the cluster disable console command, BCC is automatically disabled for those cluster resources that have been enabled for BCC. If you re-enable BCC for the cluster, you must re-enable BCC for each individual cluster resource that you want to be enabled for business continuity. This can be a time-consuming process if you have many cluster resources that are enabled for business continuity. For this reason, you should use caution when disabling BCC for an entire cluster.
cluster enable [resource]	Enables BCC for the specified resource. The resource you specify must belong to a cluster that has already been enabled for BCC. If no resource is specified, the entire cluster is enabled for BCC. When enabling a resource for business continuity, previous versions of the CLI would not set the peer clusters where the resource was assigned to run. The only way to set peer clusters for a resource was through iManager. The new version of the cluster CLI automatically sets all the clusters in the business continuity cluster on a resource. Assigning a resource to specific clusters still must be done through iManager.
cluster migrate [source/resource] [destination/nodename]	Migrates the specified resource from the specified source cluster to the specified target (destination) cluster. Specifying * for the resource name migrates all BCC-enabled resources. Specifying * for the node name brings the resource online at the most preferred node.
cluster nsmi	Execute a test run of an NSMI script for a single business continuity resource load or unload script. This command is to be used only for testing Business Continuity Clustering scripts. IMPORTANT:Ensure that the appropriate resource is offline in all peer clusters in the BCC before executing this command. The command prompts you for the resource name (such as pool6_server) and the type of BCC script (load or unload). The available scripts are listed, and you are prompted to enter the ID next to the script you want to use. Output is sent to the system log.
cluster refresh	This command should not be used except under the direction of OpenText Support.
cluster resetresources	Changes the state of all resources on this cluster to offline and secondary. This is a recovery procedure that should be run while only one node is up in the peer cluster that is brought back in service. For more information refer to section Section 9.2, Bringing a Downed Cluster Back in Service. After a failure, bring up one node in the cluster. All other nodes should remain powered off. Run the cluster resetresources command. Bring up the remaining nodes in the cluster.
cluster resources [resource]	Lets you view the state and location of cluster resources and whether resources are primary or secondary. You can optionally specify a specific resource name.
cluster status	Lets you view the state and location of cluster resources and whether resources are primary or secondary. If the resource state is primary, the node where the resource is running is displayed. If the resource state is secondary, the cluster where the resource is located is displayed.
cluster view	Displays the node name, cluster epoch number, master node name, a list of nodes that are currently members of the cluster, and peer clusters if this cluster belongs to a business continuity cluster.