Table of Contents
Advertisement
3.7.3 Cluster Enabling NSS Pools and Volumes
If you have a shared disk system that is part of your cluster and you want the pools and volumes on
the shared disk system to be highly available to NCP clients, you will need to cluster enable those
pools and volumes. Cluster enabling a pool or volume allows it to be moved or mounted on different
servers in the cluster in a manner that supports transparent client reconnect.
Cluster-enabled volumes do not appear as cluster resources. NSS pools are resources, and load and
unload scripts apply to pools and are automatically generated for them. Each cluster-enabled NSS
pool requires its own IP address. This means that each cluster-enabled volume does not have an
associated load and unload script or an assigned IP address.
NSS pools can be cluster enabled at the same time they are created. If you did not cluster enable a
pool at creation time, the first volume you cluster enable in the pool automatically cluster enables
the pool where the volume resides. After a pool has been cluster enabled, you need to cluster enable
the other volumes in the pool if you want them to be mounted on another server during a failover.
When a server fails, any cluster-enabled pools being accessed by that server will fail over to other
servers in the cluster. Because the cluster-enabled pool fails over, all volumes in the pool will also
fail over, but only the volumes that have been cluster enabled will be mounted. Any volumes in the
pool that have not been cluster enabled will have to be mounted manually. For this reason, volumes
that aren't cluster enabled should be in separate pools that are not cluster enabled.
If you want each cluster-enabled volume to be its own cluster resource, each volume must have its
own pool.
Some server applications don't require NCP client access to NSS volumes, so cluster enabling pools
and volumes might not be necessary. Pools should be deactivated and volumes should be
dismounted before being cluster enabled.
1 Start your Internet browser and enter the URL for iManager.
The URL is http://server_ip_address/nps/imanager.html. Replace server_ip_address with the
IP address or DNS name of a Linux server in the cluster that has iManager installed or with the
IP address for Apache-based services.
2 Enter your username and password.
3 In the left column, locate Clusters, then click the Cluster Options link.
iManager displays four links under Clusters that you can use to configure and manage your
cluster.
4 Enter the cluster name or browse and select it, then click the New link.
5 Specify Pool as the resource type you want to create by clicking the Pool radio button, then
click Next.
6 Enter the name of the pool you want to cluster-enable, or browse and select one.
7 (Optional) Change the default name of the virtual Server object.
When you cluster enable a pool, a Virtual Server object is automatically created and given the
name of the Cluster object plus the cluster-enabled pool. For example, if the cluster name is
cluster1 and the cluster-enabled pool name is pool1, then the default virtual server name will be
cluster1_pool1_server.
If you are cluster-enabling a volume in a pool that has already been cluster-enabled, the virtual
Server object has already been created, and you can't change the virtual Server object name.
Installation and Setup
31
Advertisement
Table of Contents
