- Daemon Monitor
A service that monitors the Foundation Services daemons, many Solaris
operating system daemons, and some companion products daemons.
- dataless node
A peer node that boots from its local disk. A dataless node
runs customer applications locally, but accesses the Foundation Services through the
cluster network. Data generated on dataless nodes is sent to the master node.
A dataless node cannot be the master node or the vice-master node.
See also diskless node.
- data partition
A disk partition that contains data. A data partition is mirrored
from the master node to the vice-master node. For a data partition on a physical
disk to be mirrored, it must have an associated bitmap partition.
See also bitmap partition.
- deployment
The installation and deployment of the Foundation Services.
Deployment is used as a generic term for installation and deployment. There
is no difference between the methods of installation and deployment, except
that deployment also includes the redeployment and reconfiguration of flash
archives.
- development host
A system used to develop an application.
- DHCP
(Dynamic Host Configuration Protocol)
A TCP/IP
protocol that enables machines to obtain IP addresses statically or dynamically
from centrally administered servers.
- DHCP client ID
A boot policy that associates a CLIENT_ID
string with a diskless node.
See also DHCP dynamic and DHCP static.
- DHCP dynamic
A boot policy that creates a dynamic map between the Ethernet
address of a diskless node and an IP address taken from a pool of available
addresses.
See also DHCP client ID and DHCP static.
- DHCP static
A boot policy that maps the Ethernet address of a diskless
node to a fixed IP address.
See also DHCP client ID and DHCP dynamic.
- direct link
A link between the serial ports on the master-eligible nodes.
The direct link prevents the occurrence of split brain when the network between
the master node and vice-master node fails.
- diskfull node
A peer node that contains at least one disk on which applications
can run and information can be permanently stored. Master-eligible nodes are
diskfull nodes. Dataless nodes are not considered to be diskfull nodes.
See also diskless node and dataless node.
- diskless node
A peer node that does not have a local disk or is not configured
to use its local disk. Diskless nodes boot through the network, using the
master node as a boot server. Diskless nodes run customer applications locally,
but access the Foundation Services through the cluster network. Data generated on diskless
nodes is sent to the master node. A diskless node cannot be the master node
or the vice-master node.
See also diskfull node
and dataless node.
- disqualified
A master-eligible node that cannot participate in an election
for the master role or vice master role. Disqualified is a state used by the
Cluster Membership Manager.
- distributed services
Services that run on all peer nodes. The distributed services
include the Cluster Membership Manager, the Node State Manager, the Node Management
Agent, the Daemon Monitor, and the Watchdog Timer.
See also highly available services.
- domainid
(domain identification number)
The number that
identifies a cluster. The domainid is the same
for each peer node in a cluster.
See also nodeid.
- double fault
The simultaneous failure of both master-eligible nodes, or
the simultaneous failure of both redundant networks.
- downtime
The percentage of time that a system is unavailable, including
attributable, scheduled, unscheduled, total, and partial system outages. Downtime
also includes outages caused by operational error.
See also availability and outage.