sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
## Configuring the `cluster.conf` Configuration File The `cluster.conf` file requires the most information. The data in this file enables you to create the `machine.conf` and `network.conf` files. To configure the `cluster.conf` file, you must do the following: Define the cluster composition Define the cluster domain Define the node groups Define the services for node groups Define the number of disks for the master-eligible nodes and dataless nodes Define the boot policy for diskless nodes The following figure shows the components that are contained in the `cluster.conf` file: Figure 5-2 The `cluster.conf` Configuration File ### Defining the Cluster Composition The cluster composition section of the `cluster.conf` file contains the name and contents of the cluster. The hardware contents and domain name of the cluster are described by the `INVOLVE` keyword. The following program listing is a cluster composition section for a twelve node cluster spanned across two shelves:
    # Cluster composition
    #
    ELEMENT cluster 12N_cluster
            INVOLVE shelf shelf_1
                    shelf shelf_2
                    domain cluster_domain
                    nodeGroup master_el
                    nodeGroup dataless_N120
                    nodeGroup dataless_N200
All configuration elements of the cluster definition must be defined in the `cluster.conf` file, during stage 1. The exception is the `shelf` attributes that are defined in the `machine.conf` file. ### Defining the Cluster Domain The cluster domain definition section contains a logical definition of the cluster network parameters. In the cluster domain definition section: The name and ID of the cluster domain are described by the `ELEMENT` keyword The cluster network interfaces are described by the `INVOLVE` keyword The floating addresses are described by the `USE` keyword The following program listing is a cluster domain section for a twelve node cluster:
    # Cluster domain definition
    #
    # id -> CMM domainId
    # ip -> master master-nic0 master-nic1 floating addresses
    #
    ELEMENT domain cluster_domain id 100
            INVOLVE network phys-A
                    network phys-B
                    network cgtp
            USE ip master-cgtp
                ip master-nic0
                ip master-nic1
### Defining Nodes and Node Groups Every node in a cluster belongs to a node group. Node and node group attributes are defined in the `cluster.conf` file. Nodes belonging to a node group share the following properties: Type Operating system Architecture Class Foundation Services configuration Software Peripheral capabilities The following table lists the attributes that must be defined for each node group. Table 5-1 Mandatory Attributes for Each Node Group Definition
Keyword | Description
--- | ---
`node` | Name of the node to be included in the node group.
`service` | Foundation Services list
`type` | This can be master-eligible, diskless, or dataless.
`os` | Operating system.
`arch` | System architecture.
For information on the syntax to use for each of the keywords, see the `cluster.conf`(4) man page. For information on the concepts of node groups, see Planning Node Groups. The nodes that are included in a node group are described by the `INCLUDE` keyword. The `INCLUDE` keyword is also used to embed a diskless node group in a master-eligible node group. The services that are to be run with the node group are described by the `RUN` keyword. Each cluster must have at least one node group consisting of the two master-eligible nodes. The following program listing is an example node group and node definition for a master-eligible node group in a two-node cluster:
    # MEN group and related nodes definitions
    ELEMENT nodeGroup master_el type MASTER_ELIGIBLE os SOLARIS arch SPARC
            RUN service NHAS_MASTER_ELIGIBLE
    #
    # MEN definitions
    ELEMENT node peerNode1-2N
            USE board N120@peerNode1
                disk disk1@peerNode1
    #
    ELEMENT node peerNode2-2N
            USE board N120@peerNode2
                disk disk1@peerNode2
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems