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

| Previous Contents Index Next
### Specifying the Version of the Operating System to be Installed on the Cluster Some hardware types require specific or modified versions of the Solaris operating system that `nhinstall` is unable to detect automatically. In these cases, you must explicitly force `nhinstall` to recognize the version of the operating system you want to install on the cluster. To determine if your cluster hardware requires such action, see the README files in the Foundation Services patches you are installing on the cluster. ### Selecting the Solaris Package Set to be Installed To install a Solaris package set on cluster nodes other than the default package set, specify the Solaris package set to be installed. For a list of the contents of the default package set, see the `/opt/SUNWcgha/config.standard/nodeprof.conf.template` file. For information about installing a Solaris package set on cluster nodes, see the `nodeprof.conf`(4) man page. For information about installing a different Solaris package set on the diskless nodes to that installed on the master-eligible nodes, see the `diskless_nodeprof.conf`(4) man page. ### Installing a Different Version of the Operating System on Diskless Nodes To install a different version of the Solaris operating system on diskless nodes to that which you are installing on master-eligible nodes, specify the location of the two Solaris distributions in the `env_installation.conf` file. For example:
    SOLARIS_DIR=/export/su28u7fcs
    DISKLESS_SOLARIS_DIR=/export/su29HW8a
By default, the value provided to the DISKLESS_SOLARIS_DIR parameter is set to be the same as that provided to the SOLARIS_DIR parameter. For more information, see the `env_installation.conf`(4) man page. ### Configuring Reduced Duration of Disk Synchronization By default `nhinstall` enables this feature which reduces the time taken for full synchronization between the master and the vice-master disks by synchronizing only the blocks that contain replicated data. Note - Only use this feature with UFS file systems. To disable this feature and have all blocks replicated, add the following line to the `cluster definition.conf` file:
    SLICE_SYNC_TYPE=RAW
For more information, see the `cluster_definition.conf`(4) man page and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring a Data Management Policy There are three data management policies available with the current patch level of the Foundation Services. By default, the `nhinstall` tool sets the data management policy to be `Integrity`. To choose another policy, change the value of the following variable in the `cluster_definition.conf` file.
    DATA_MGT_POLICY=INTEGRITY | AVAILABILITY | ADAPTABILITY
For more information, see the `cluster_definition.conf`(4) man page and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring Masterless Cluster By default, diskless nodes reboot if there is no master in the cluster. If you do not want the diskless nodes to reboot in this situation, add the following line to the `cluster_definition.conf` file:
    MASTER_LOSS_DETECTION=YES
For more information, see the `cluster_definition.conf`(4) man page and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring Sanity Check of Replicated Slices To activate the sanity check of replicated slices, add the following line to the `cluster_definition.conf` file:
    CHECK_REPLICATED_SLICES=YES
By default, the `nhinstall` tool does not activate this feature. For more information, see the `cluster_definition.conf`(4) man page and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring Delayed Synchronization By default, with an `nhinstall` installation, disk synchronization starts automatically when the cluster software is installed. If you want to delay the start of disk synchronization, add the following line to the `cluster_definition.conf` file:
    SYNC_FLAG=NO
You can trigger disk synchronization at a time of your choice using the `nhenablesync` tool. For more information, see the `cluster_definition.conf`(4) and `nhenablesync`(1M) man pages and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring Serialized Slice Synchronization By default, `nhinstall` configures the cluster so that slices are synchronized in parallel. Synchronizing slices one slice at a time reduces the network and disk overhead but increases the time it takes for the vice-master to synchronize with the master. During this time, the vice-master is not eligible to take on the role of master. To enable serialized slice synchronization, add the following line to the `cluster_definition.conf` file:
    SERIALIZE_SYNC=YES
For more information, see the `cluster_definition.conf`(4) man page and What's New in Netra High Availability Suite Foundation Services 2.1 6/03. ### Configuring the Default Router to the Public Network By default, `nhinstall` configures the installation server to be the default router to the public network. To choose another machine as the router to the public network specify the IP address of the default router of your choice in the `cluster_definition.conf` file as follows:
    DEFAULT_ROUTER_IP=IP address
For more information, see the `cluster_definition.conf`(4) man page.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems