The scstat utility displays the current state of Sun Cluster and its components. Only one instance of the scstat utility needs to run on any machine in the Sun Cluster configuration.
When run without any options, scstat displays the status for all components of the cluster. This display includes the following information:
A list of cluster members
The status of each cluster member
The status of resource groups and resources
The status of every path on the cluster interconnect
The status of every disk device group
The status of every quorum device
The status of every Internet Protocol Network Multipathing group and public network adapter
You need solaris.cluster.device.read, solaris.cluster.transport.read, solaris.cluster.resource.read, solaris.cluster.node.read, solaris.cluster.quorum.read, and solaris.cluster.system.read RBAC authorization to use this command without options. See rbac(5).
The resource state, resource group state, and resource status are all maintained on a per-node basis. For example, a given resource has a distinct state on each cluster node and a distinct status on each cluster node.
The resource state is set by the Resource Group Manager on each node, based only on which methods have been invoked on the resource. For example, after the Stop method has run successfully on a resource on a given node, the resource's state will be Offline on that node. If the Stop method exits nonzero or times out, then the state of the resource is Stop_failed.
Possible resource states are: Online, Offline, Start_failed, Stop_failed, Monitor_failed, or Online_not_monitored.
Possible resource group states are: Unmanaged, Online, Offline, pending_online, pending_offline, or Error_stop_failed.
In addition to resource state, the RGM also maintains a resource status that can be set by the resource itself by using the API. The field Status Message actually consists of two components: status keyword and status message. Status message is optionally set by the resource and is an arbitrary text string that is printed after the status keyword.
Descriptions of possible values for a resource's status are as follows:
The resource is online and providing service.
The resource is online, but its performance or availability might be compromised in some way.
The resource has encountered an error that prevents it from functioning.
The current status is unknown or is in transition.
The resource is offline.
Device group status reflects the availability of the devices in that group.
The following are possible values for device group status and their descriptions:
The device group is online. There is a primary node, and devices within the group are ready for I/O.
The device group is online, but not all of its potential primaries (secondaries) are up. For two-node connectivity, this status basically indicates that a stand-by primary does not exist, which means a failure of the primary node will result in a loss of access to the devices in the group.
The device group is between one status and another. This status might occur, for example, when a device group is going from offline to online.
The device group is offline. There is no primary node. The device group must be brought online before any of its devices can be used.
You can specify command options to request the status for specific components.
If more than one option is specified, the scstat utility prints out the status in the order specified.
The following options are supported:
Shows status for all disk device groups.
You need solaris.cluster.device.read RBAC authorization to use this command option. See rbac(5).
Shows status for all resource groups.
You need solaris.cluster.resource.read RBAC authorization to use this command option. See rbac(5).
Shows status for the specified node (node) and status of the disk device groups of which this node is the primary node. Also shows the status of the quorum devices to which this node holds reservations of the resource groups to which the node is a potential master, and holds reservations of the transport paths to which the node is attached.
You need solaris.cluster.device.read, solaris.cluster.transport.read, solaris.cluster.resource.read, solaris.cluster.node.read, solaris.cluster.quorum.read, and solaris.cluster.system.read RBAC authorization to use this command option. See rbac(5).
Shows status for all IP Network Multipathing groups and public network adapters.
Shows status for all nodes.
You need solaris.cluster.node.read RBAC authorization to use this command option. See rbac(5).
Shows status for all components in the cluster. Use with -v[v] to display more verbose output.
You need solaris.cluster.device.read, solaris.cluster.transport.read, solaris.cluster.resource.read, solaris.cluster.node.read, solaris.cluster.quorum.read, and solaris.cluster.system.read RBAC authorization to use -p with -v[v]. See rbac(5).
Shows status for all device quorums and node quorums.
You need solaris.cluster.quorum.read RBAC authorization to use this command option. See rbac(5).
Shows verbose output.
Shows status for cluster transport path.
You need solaris.cluster.transport.read RBAC authorization to use this command option. See rbac(5).
The following command displays the status of all resource groups followed by the status of all components related to the specified host:
% scstat -g -h host
The output that is displayed appears in the order in which the options are specified.
These results are the same results you would see by typing the two commands:
% scstat -g
% scstat -h host
The following exit values are returned:
The command completed successfully.
An error has occurred.
See attributes(5) for descriptions of the following attributes:
An online quorum device means that the device was available for contributing to the formation of quorum when quorum was last established. From the context of the quorum algorithm, the device is online because it actively contributed to the formation of quorum. However, an online quorum device might not necessarily continue to be in a healthy enough state to contribute to the formation of quorum when quorum is re-established. The current version of Sun Cluster does not include a disk monitoring facility or regular probes to the quorum devices.