Besides the basic states listed above, RMS may report additional state details in the following locations:
In the Cluster Admin GUI, the properties view of an object includes the State Details item at the top of the list. Unlike most other attributes, which are determined at configuration time by the Wizard Tools, this information-only field is dynamically set by RMS at runtime.
In the output of the hvdisp utility, the StateDetails column appears at the end of each line.
In most cases, the StateDetails field is empty. RMS typically provides this extra information when an application is in maintenance mode, or when an object is in a transitional, inconsistent, or standby state. The following table lists all possible StateDetails values for RMS objects.
Value | Description |
|---|---|
Failed Over | Failed Over Offline processing successful and failover initiated |
Faulted | Received Faulted report |
Fault Occurred | The resource error has occurred in the past. |
Inconsistent on remote | userApplication is Online on multiple hosts, but is not Online on the local host |
Initial Fault | userApplication already faulted when RMS started |
Joined | SysNode is in Offline state because it has joined the cluster |
Killed | SysNode is in Faulted state because of a successful kill |
Not Joined | SysNode is in Offline state because it has not yet joined the cluster |
Offline | Received Offline report |
Offline Failed | Offline processing failed |
Offline Success | Offline processing successful |
Offline intended | Intended state is Offline |
Online | Received Online report |
Online !! | Intended state is Online, but some resources under userApplication are not Online |
Online intended | Intended state is Online |
Partial | Resources under the userApplication are partially started |
PreCheckScriptFailed | PreCheckScript failed |
Preserved | PreserveState set, no Offline processing initiated |
Shutdown | SysNode is in Faulted state because it has been shutdown |
Standby | Received Standby report |
Standby !! | Intended state is Standby, but some resources under userApplication are not Standby |
Standby intended | Intended state is Standby |
Remote Faulted | Control application is Faulted in at least one node. |
Remote Offline | Control application is not Standby in any node. |
For example, if an application was online on a particular node before it was put into maintenance mode, it will generally return to the online state on the same node when it leaves maintenance mode. RMS indicates this by reporting Online intended in the state details field on that node. On other nodes where the application was previously offline, RMS will report Offline intended in the state details field.
