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

| Previous Contents Index Next
The services are assigned in the `cluster.conf` file. For information on how to configure the services, see Choosing Services for Each Node Group. #### Carrier Grade Transport Protocol One of the Foundation Services that SMCT automatically installs and configures on your cluster is the CGTP. The CGTP enables a redundant network for your cluster. If you do not require a redundant network for your cluster and you do not want to install andconfigure the CGTP, you must install manually or by using the `nhinstall` tool. In this case, if the single network link fails, there is no back up network and you might lose information. For a complete description of the CGTP, see "Carrier Grade Transport Protocol" in the Netra High Availability Suite Foundation Services 2.1 6/03 Overview. For information about installing manually or by using the `nhinstall` tool, see the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. #### Watchdog Timer Service Install and configure the Watchdog Timer provided with the Foundation Services only if you are using Netra servers that have hardware watchdogs at the Lights-Off Management (LOM) level. If you are using Netra servers with hardware watchdogs at the OpenBoot™ PROM (OBP) level, do not install the Watchdog Timer provided with the Foundation Services. These hardware watchdogs are monitored by the server's software. For a list of the types of watchdogs of different Netra servers, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide ### Specifying a Diskless Node Boot Policy During the configuration process, you are asked to specify a boot policy for each diskless node group. The following table summarizes the boot policies supported by the SMCT. Table 4-3 Boot Policies for a Diskless Node Group
Boot Policy | Description
--- | ---
DHCP static boot policy | Based on the Ethernet address of the diskless nodes. Use the `MAC_ADDR_POLICY` parameter in the `cluster.conf` file.
DHCP client ID boot policy | Based on the client ID of a slot in a CompactPCI server. Use the `STATIC_CLIENT_ID_POLICY` parameter in the `cluster.conf` file.
DHCP dynamic boot policy | Not supported by the SMCT.
The SMCT does not support dynamic address assignment. To assign dynamic addresses to diskless nodes, you can either install manually or use the `nhinstall` tool. These installation methods are described in the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. ## Planning Disk Layout and File Systems This section describes the disk layout and file system configuration options for master-eligible nodes and dataless nodes. This section provides information about the disk space that you may require and the various configurations that are available. Disk layout and the configuration of file systems is defined during configuration stage 1, and is described in Defining the Disk Layout. The way you partition your disk depends on whether the disk is part of a master-eligible node or a dataless node. If your cluster is to contain diskless nodes, the disk partitions of the master-eligible nodes are different. Another condition to consider is volume managment software, which, if used, affects the way a disk is partitioned. If you plan to logically partition and mirror disks, you require one of the following volume management software: Solstice DiskSuite™ 4.2.1 for Solaris 8 2/02 Solaris Volume Manager for Solaris 9 The following table summarizes the possible disk layout configurations: Table 4-4 Disk Layout Options for the Foundation Services
Disk Type | Diskless Node Configuration | Volume Management Software Configuration | Two Disk Support
--- | --- | --- | ---
Master-eligible | Optional | Optional | Optional
Dataless | No | No | Optional
The SMCT does not support virtual disk partitioning. To use virtual disk partitioning, you must install the Solaris operating system and manually set up the virtual partitioning before following the manual installation procedure. For more information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Custom Installation Guide. For examples of disk layout and file system definition sections of the `machine.conf` file, see Appendix B, Configuration File Examples for the `machine.conf` File. ### Planning Disk Layout and File Systems for Master-Eligible Nodes The master-eligible nodes in your cluster must have identical disk partitions. The disk partitions of the master-eligible node depend on the requirements of your cluster, and whether your cluster contains diskless or dataless nodes. #### Disk Layout and File Systems for a Cluster With Diskless Nodes The following table provides the minimum space requirements for an example disk partition of master-eligible nodes in a cluster with diskless nodes: Table 4-5 Example Disk Layout and File Systems for a Cluster With Diskless Nodes
Disk Partition | Contents | Description | Minimum Size
--- | --- | --- | ---
0 | `/` | The root file system, boot partition, and volume management software. This partition must be mounted with the `logging` option. | 2 Gbytes minimum
1 | `swap` | Minimum size when physical memory is less than 1 Gbyte. | 1 Gbyte
2 | `overlap` | Entire disk. | Size of the entire disk
3 | `/export` | Exported file system reserved for diskless nodes. This partition must be mounted with the `logging` option. This slice is partitioned further if diskless nodes are added to the cluster. | 1 Gbyte + 100 Mbytes per diskless node
4 | `/SUNWcgha/local` | This slice is reserved for NFS status files, services, and configuration files. This partition must be mounted with the `logging` option. | 2 Gbytes
5 | Reserved for Reliable NFS internal use | Bitmap partition reserved for `nhcrfsd`. This partition is associated with the `/export` partition. | See Table 4-6
6 | Reserved for Reliable NFS internal use | Bitmap partition reserved for `nhcrfsd`. This partition is associated with the `/SUNWcgha/local` partition. | See Table 4-6
7 | `/mypartition` | For additional applications. | The remaining space
For replication, create bitmap partitions for each partition containing an exported replicated file system on the master-eligible nodes. The size of the bitmap partition must be equal to 512 bytes + 1 bit per 32 Kbytes of the data device size. In this example, the bitmap partitions are created on partitions 5 and 6. The following table gives example bitmap partitions. Table 4-6 Example Bitmap Partitions
File System Name |  | Bitmap File | File System (Mbytes) | Bitmap Partition (Kbytes) | Bitmap size (block)
--- | --- | --- | --- | --- | ---
`/export` |  | `/dev/rdsk/c0t0d0s5` | 2000 | 8512 | 18
`/SUNWcgha/local` |  | `/dev/rdsk/c0t0d0s6` | 1512 | 6512 | 14
For information on creating bitmap partitions, see the Sun StorEdge Availability Suite 3.1 Remote Mirror Software Installation Guide. #### Disk Layout and File Systems for a Cluster Without Diskless Nodes For a cluster without diskless nodes, the following partitions are not required: The `/export` partition One partition reserved for Reliable NFS internal use These partitions correspond to partitions 3 and 5 in Table 4-5. ### Planning the Disk Layout and File Systems for Master-Eligible Nodes by Using Volume Management Software This section describes the disk layout of the master-eligible nodes when using volume management software. You must use volume management software if you are using a Netra-20 as a master-eligible node. #### Disk Layout and File Systems for a Cluster With Diskless Nodes The following table provides the minimum space requirements for example disk partitions for a master-eligible node using volume management software, in a cluster with diskless nodes: Table 4-7 Example Disk Layout and File Systems for a Cluster With Diskless Nodes
Disk Partition | Contents | Description | Minimum Size
--- | --- | --- | ---
0 | `/` | The root file system, boot partition, and volume management software. This partition must be mounted with the `logging` option. | 2 Gbytes minimum
1 | `swap` | Minimum size when physical memory is less than 1 Gbyte. | 1 Gbyte
2 | `overlap` | Entire disk. | Size of the entire disk
3 | `/SUNWcgha/local` | This slice is reserved for NFS status files, services, and configuration files. This partition must be mounted with the `logging` option. For a cluster without diskless nodes, this partition is free. This partition can also be mirrored. | 2 Gbytes
4 | `/export` | Exported file system reserved for diskless nodes. This partition must be mounted with the `logging` option. This slice is partitioned further if diskless nodes are added to the cluster. | 1 Gbyte + 100 Mbytes per diskless node
5 | `/mypartition` | Free for user. This partition can be mirrored. | The size of slice 5 (user-defined).
6 | `/mypartition` | Free for user. This partition can be mirrored. | The size of slice 6 (user-defined).
7 | Reserved | Reserved for SNDR bitmaps and volume management software meta database. | The sum of SNDR bitmaps + volume management software meta database files
#### Disk Layout and File Systems for a Cluster Without Diskless Nodes For a cluster without diskless nodes, the following partition is not required: The `/export` partition
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems