Server Configuration and Server State Attributes

Oracle Clusterware assigns each server a set of attributes as soon as you add a server to a cluster. Some of these attributes describe the physical characteristics of the server, while others describe the state conditions of the server. Also, there are other server attributes which you can modify that help further categorize servers. If you remove the server from the cluster, then Oracle Clusterware deletes the server object.

You use server configuration attributes to categorize servers, as part of a server categorization management policy.

Table 3-4 lists and describes server configuration attributes.

Table 3-4 Server Configuration Attributes

Attribute	Description
ACTIVE_CSS_ROLE	Role being performed by the server. A server can have one of the following roles: `hub`: Designated role for a server in an Oracle Flex Cluster or the designated role for any node in an Oracle Clusterware standard Cluster. `leaf`: The server is a Leaf Node in an Oracle Flex Cluster. Note: You cannot configure this attribute.
CONFIGURED_CSS_ROLE	Configured role for the server. A server can be either of the following: `hub`: Designated role for a server in an Oracle Flex Cluster or the designated role for any node in an Oracle Clusterware standard Cluster. `leaf`: The server is a Leaf Node in an Oracle Flex Cluster. Note: You cannot configure this attribute.
CPU_CLOCK_RATE	CPU clock rate in megahertz (MHz)
CPU_COUNT	Number of processors
CPU_EQUIVALENCY	The relative value (expressed as a positive integer greater than or equal to 1) that Oracle Clusterware uses to describe that the CPU power provided by a server may deviate (positively or negatively) from its physical representation using a baseline of 1000, for example. A value lower than 1000 describes that, despite a certain value for the `CPU_COUNT` and `CPU_CLOCK_RATE` parameters, the equivalent power provided by this server is respectively lower. Use the following commands to view or modify, respectively, this attribute on the local server: crsctl get cpu equivalency crsctl set cpu equivalency
CPU_HYPERTHREADING	Status of hyperthreading for the CPU. A value of `0` signifies that hyperthreading is not in use. A value of `1` signifies that hyperthreading is in use.
MEMORY_SIZE	Memory size in megabytes (MB)
NAME	The name of the server.
RESOURCE_USE_ENABLED	A server pool resource management parameter. If the value for this attribute is 1, which is the default, then the server can be used for resource placement. If the value is 0, then Oracle Clusterware disallows starting server pool resources on the server. The server remains in the Free pool. You can review the setting and control this attribute for each cluster member node by using the `crsctl get resource use` and `crsctl set resource use` commands.
SERVER_LABEL	An arbitrary value that you can use to label the server. You can use this attribute when setting up server categories. For example, you can specify a ___location (such as building_A or building_B), which makes it possible to put servers into pools where ___location is a requirement, by creating an appropriate server category and using it for the server pool. Use the following commands to view or modify, respectively, this attribute on the local server: crsctl get server label crsctl set server label

Table 3-5 lists and describes read-only server state and configuration attributes:

Table 3-5 Server State Attributes

Attribute Description

Attribute	Description
ACTIVE_POOLS	A space-delimited list of the names of the server pools to which a server belongs. Oracle Clusterware manages this list automatically.
STATE	A server can be in one of the following states: `ONLINE`: The server is a member of the cluster and is available for resource placement. `OFFLINE`: The server is not currently a member of the cluster. Subsequently, it is not available for resource placement. `JOINING`: When a server joins a cluster, Oracle Clusterware processes the server to ensure that it is valid for resource placement. Oracle Clusterware also checks the state of resources configured to run on the server. Once the validity of the server and the state of the resources are determined, the server transitions out of this state. `LEAVING`: When a planned shutdown for a server begins, the state of the server transitions to `LEAVING`, making it unavailable for resource placement. `VISIBLE`: Servers that have Oracle Clusterware running, but not the Cluster Ready Services daemon (CRSD), are put into the `VISIBLE` state. This usually indicates an intermittent issue or failure and Oracle Clusterware trying to recover (restart) the daemon. Oracle Clusterware cannot manage resources on servers while the servers are in this state. `RECONFIGURING`: When servers move between server pools due to server pool reconfiguration, a server is placed into this state if resources that ran on it in the current server pool must be stopped and relocated. This happens because resources running on the server may not be configured to run in the server pool to which the server is moving. As soon as the resources are successfully relocated, the server is put back into the `ONLINE` state. Use the `crsctl status server` command to obtain server information.
STATE_DETAILS	This is a read-only attribute that Oracle Clusterware manages. The attribute provides additional details about the state of a server. Possible additional details about a server state are: Server state: `ONLINE`: `AUTOSTARTING RESOURCES` Indicates that the resource autostart procedure (performed when a server reboots or the Oracle Clusterware stack is restarted) is in progress for the server. `AUTOSTART QUEUED` The server is waiting for the resource autostart to commence. Once that happens, the attribute value changes to `AUTOSTARTING RESOURCES`. Server state: `RECONFIGURING`: `STOPPING RESOURCES` Resources that are restricted from running in a new server pool are stopping. `STARTING RESOURCES` Resources that can run in a new server pool are starting. `RECONFIG FAILED` One or more resources did not stop and thus the server cannot transition into the `ONLINE` state. At this point, manual intervention is required. You must stop or unregister resources that did not stop. After that, the server automatically transitions into the `ONLINE` state. Server state: `JOINING`: `CHECKING RESOURCES` Whenever a server reboots, the Oracle Clusterware stack restarts, or CRSD on a server restarts, the policy engine must determine the current state of the resources on the server. While that procedure is in progress, this value is returned.

ACTIVE_POOLS

A space-delimited list of the names of the server pools to which a server belongs. Oracle Clusterware manages this list automatically.

STATE

A server can be in one of the following states:

ONLINE: The server is a member of the cluster and is available for resource placement.
OFFLINE: The server is not currently a member of the cluster. Subsequently, it is not available for resource placement.
JOINING: When a server joins a cluster, Oracle Clusterware processes the server to ensure that it is valid for resource placement. Oracle Clusterware also checks the state of resources configured to run on the server. Once the validity of the server and the state of the resources are determined, the server transitions out of this state.
LEAVING: When a planned shutdown for a server begins, the state of the server transitions to LEAVING, making it unavailable for resource placement.
VISIBLE: Servers that have Oracle Clusterware running, but not the Cluster Ready Services daemon (CRSD), are put into the VISIBLE state. This usually indicates an intermittent issue or failure and Oracle Clusterware trying to recover (restart) the daemon. Oracle Clusterware cannot manage resources on servers while the servers are in this state.
RECONFIGURING: When servers move between server pools due to server pool reconfiguration, a server is placed into this state if resources that ran on it in the current server pool must be stopped and relocated. This happens because resources running on the server may not be configured to run in the server pool to which the server is moving. As soon as the resources are successfully relocated, the server is put back into the ONLINE state.

Use the crsctl status server command to obtain server information.

STATE_DETAILS

This is a read-only attribute that Oracle Clusterware manages. The attribute provides additional details about the state of a server. Possible additional details about a server state are:

Server state: ONLINE:

AUTOSTARTING RESOURCES

Indicates that the resource autostart procedure (performed when a server reboots or the Oracle Clusterware stack is restarted) is in progress for the server.
AUTOSTART QUEUED

The server is waiting for the resource autostart to commence. Once that happens, the attribute value changes to AUTOSTARTING RESOURCES.

Server state: RECONFIGURING:

STOPPING RESOURCES

Resources that are restricted from running in a new server pool are stopping.
STARTING RESOURCES

Resources that can run in a new server pool are starting.
RECONFIG FAILED

One or more resources did not stop and thus the server cannot transition into the ONLINE state. At this point, manual intervention is required. You must stop or unregister resources that did not stop. After that, the server automatically transitions into the ONLINE state.

Server state: JOINING:

CHECKING RESOURCES

Whenever a server reboots, the Oracle Clusterware stack restarts, or CRSD on a server restarts, the policy engine must determine the current state of the resources on the server. While that procedure is in progress, this value is returned.