test

Sun HPC ClusterTools 3.0 Administrator's Guide: With CRE

mpadmin Objects and Attributes

From the perspective of mpadmin, a Sun HPC cluster consists of a system of objects, which include

Each type of object has a set of attributes whose values can be operated on via mpadmin commands. These attributes control various aspects of their respective objects, such as: whether a node is enabled or disabled (that is, whether it can be used or not), the names of partitions, and which nodes a partition contains.

Note -

The CRE sets most cluster object attributes to default values each time it boots up. With few exceptions, do not change these system-defined values.

mpadmin Contexts

mpadmin commands are organized into four contexts, which correspond to the four types of mpadmin objects. These contexts are illustrated in Figure 6-1 and summarized below.

Figure 6-1 The mpadmin Contexts

Graphic

Except for Cluster, each context is nested in a higher context: Node within Cluster, Partition within Cluster, and Network within Node.

The mpadmin prompt uses one or more fields to indicate the current context. Table 6-2 shows the prompt format for each of the possible mpadmin contexts.

Table 6-2 mpadmin Prompt Formats

Prompt Formats 

Context 

[cluster-name]::

Current context = Cluster. 

[cluster-name]Node::

Current context = Node, but not a specific node. 

[cluster-name]N(node-name)::

Current context = a specific node. 

[cluster-name]Partition::

Current context = Partition, but not a specific partition. 

[cluster-name]P(partition-name)::

Current context = a specific partition. 

[cluster-name]N(node-name) Network::

Current context = Network Interface, but not a specific network interface. 

[cluster-name]N(node-name) I(net-if-name)::

Current context = a specific network interface. 

Note -

When the prompt indicates a specific network interface, it uses I as the abbreviation for Network Interface to avoid being confused with the Node abbreviation N.