Cluster Takeover And Failback - Oracle ZFS Storage Appliance Administration Manual

assignments in turn form the binding of network addresses to storage resources that clients
expect to see. Regardless of which appliance controls the collection of resources, clients are
able to access the storage they require at the network locations they expect.
Related Topics
"Shutting Down a Clustered Configuration (CLI)" on page 199
■

Cluster Takeover and Failback

Clustered controller nodes are in one of a small set of states at any given time:
Cluster States
TABLE 44
State
UNCONFIGURED
OWNER
STRIPPED
Icon CLI/BUI Expression
Clustering is not
configured
Active (takeover
completed)
Ready (waiting for
failback)
Shutting Down a Clustered Configuration (CLI)
Description
A system that has no
clustering at all is in this
state. The system is either
being set up or the cluster
setup task has never been
completed.
Clustering is configured,
and this node has taken
control of all shared
resources in the cluster.
A system enters this state
immediately after cluster
setup is completed from its
user interface, and when
it detects that its peer has
failed (i.e. after a take-
over). It remains in this
state until an administrator
manually executes a fail-
back operation.
Clustering is configured,
and this node does
not control any shared
resources. A system is
STRIPPED immediately
after cluster setup is
completed from the user
interface of the other node,
or following a reboot,
power disconnect, or
other failure. A node
remains in this state until
an administrator manually
Configuring the Appliance 209