This section describes the object-oriented command set for Oracle Solaris Cluster. The object-oriented command set uses a common prefix cl and are located in /usr/cluster/bin.
Many commands in this command set have both a long form and a short form. For example, clresource and clrs are identical.
Each object-oriented command is designed to manage a single type of cluster object. The command name indicates the type of object that it manages. For example, the clresource command manages Oracle Solaris Cluster data service resources. Within a command, subcommands define operations that are allowed on the specific cluster object.
The general form of commands in the object-oriented command set is as follows:
command [subcommand] [option…] [operand …]
Options that you use with the object-oriented commands also have a long form and a short form. You specify the short form of an option with a single dash (-) followed by a single character. You specify the long form of an option with two dashes (--) followed by an option word. For example, –p is the short form of the property option. –-property is the long form.
Some options accept an option argument while others do not. If an option accepts an option argument, the option argument is required. The –? option requires no arguments. However, the –-property option requires an option argument that identifies the property being operated on.
You can group the short form of options without arguments behind a single dash (-). For example, –eM. You must separate groups of option-arguments following an option either by commas, or by a tab or a space character. When using a tab or space, surround the option-arguments with quotation marks (-o xxx,z,yy or -o “xxx z yy”).
To specify option arguments with long option names, use either the --input=configurationfile format or the --input configurationfile format.
All commands in this command set accept the –? or --help option. If you provide these options without a subcommand, summary help for the command is displayed. If you provide a subcommand, help for that subcommand only is displayed.
Certain commands work in conjunction with a configuration file. For information on the required format of this file, see the clconfiguration(7CL) man page.
Many subcommands in this command set accept + as an operand to indicate all applicable objects.
This section describes, in alphabetical order, the object-oriented commands that are available with the Oracle Solaris Cluster product.
Manage Oracle Solaris Cluster access policies for adding nodes
Authorize secure access by a specified machine during establishment of a new cluster node
Manage Oracle Solaris Cluster devices
Manage Oracle Solaris Cluster device groups
Manage the Oracle Solaris Cluster interconnect
Launch the centralized installer
Manage access to NAS devices for Oracle Solaris Cluster
Manage Oracle Solaris Cluster nodes
Manage Oracle Solaris Cluster private strings
Manage Oracle Solaris Cluster quorum
Manage Oracle Solaris Cluster resources for logical host names
Manage resources for Oracle Solaris Cluster data services
Manage resource groups for Oracle Solaris Cluster data services
Manage resource types for Oracle Solaris Cluster data services
Manage Oracle Solaris Cluster resources for shared addresses
Configure Oracle Solaris Cluster interactively
Administer Oracle Solaris Cluster SNMP hosts
Administer Oracle Solaris Cluster SNMP MIB
Administer Oracle Solaris Cluster SNMP users
Configure system resource monitoring
Manage the global configuration and the global status of Sun Cluster
Manage zone clusters for Oracle Solaris Cluster
As of the Oracle Solaris Cluster 4.4 release, the original command set, which used the sc prefix, is no longer available. The following list provides some common Oracle Solaris Cluster commands from the original command set and their current, object-oriented command set equivalents:
If an Oracle Solaris Cluster command is successful for all specified operands, the command returns zero (CL_NOERR). If an error occurs for an operand, the command processes the next operand in the operand list. The returned exit code always reflects the error that occurred first.
These exit codes are shared across this set of commands.
The command that you issued completed successfully.
Not enough swap space
A cluster node ran out of swap memory or ran out of other operating system resources.
You typed the command incorrectly, or the syntax of the cluster configuration information that you supplied with the –i option was incorrect.
Cluster is reconfiguring
The cluster is reconfiguring.
The object that you specified is inaccessible. You might need the root role or authorization to issue the command. See the rbac(7) man page for more information.
Object is in wrong state
You tried to modify a property, a resource group, or other object that you cannot modify at that particular time or at any time.
Resource method failed
A method of a resource failed. The method failed for one of the following reasons: (1)The validate method failed when you tried to create a resource or modify the properties of a resource. (2) A method other than validate failed when you tried to enable, disable, or delete a resource.
The property or value that you specified with the –p, –y, or –x option does not exist or is not allowed.
Internal error was encountered
An internal error indicates a software defect or other defect.
A physical input/output error has occurred.
No such object
The object that you specified cannot be found for one of the following reasons: (1) The object does not exist. (2) A directory in the path to the configuration file that you attempted to create with the –o option does not exist. (3)The configuration file that you attempted to access with the –i option contains errors.
Operation not allowed
You tried to perform an operation on an unsupported configuration, or you performed an unsupported operation.
You attempted to remove a cable from the last cluster interconnect path to an active cluster node. Or, you attempted to remove a node from a cluster configuration from which you have not removed references.
The device, device group, cluster interconnect component, node, cluster, resource, resource type, resource group, or private string that you specified already exists.
The type that you specified with the –t or –p option does not exist.
Node is in cluster mode
You attempted to perform an operation on a node that is booted in cluster mode. However, you can perform this operation only on a node that is booted in noncluster mode.
Node is not in cluster mode
You attempted to perform an operation on a node that is booted in noncluster mode. However, you can perform this operation only on a node that is booted in cluster mode.
See attributes(7) for descriptions of the following attributes: