Setting up iSNS Server HA Using Sun Cluster 3.2 =============================================== The overall tasks are - Install Sun Cluster 3.2. For information about Sun Cluster see http://docs.sun.com/app/docs/doc/819-2969(Sun Cluster Concepts Guide for Solaris OS). - Encapsulate iSNS SMF service into Failover Proxy Resource. - Specify iSNS data store location in a Cluster File System. - Online the associated cluster resource group. Sun Cluster SMF proxy resource type SUNW.Proxy_SMF_failover can be used to encapsulate iSNS SMF service into a Failover Proxy Resource Configuration. For information on how you can encapsulate SMF services with Sun Cluster 3.2, see http://docs.sun.com/app/docs/doc/819-2974/6n57pdk2b?a=view(Enabling Solaris SMF Services to Run With Sun Cluster) For information about failover configuration, see http://docs.sun.com/app/docs/doc/819-2974/6n57pdjtp?a=view(Creating a Resource Group) It is assumed that Sun Cluster 3.2 is successfully installed prior to executing the following steps. Execute the following steps on a cluster member. 1) Become superuser or assume a role that provides Solaris.cluster.modify RBAC authorization. 2) Register the proxy SMF failover resource type. # clresourcetype register SUNW.Proxy_SMF_failover 3) Verify that the proxy resource type has been registered. An example output: # clresourcetype list SUNW.LogicalHostname:2 SUNW.SharedAddress:2 SUNW.Proxy_SMF_failover 4) Create the SMF failover resource group for iSNS service. For example: # clresourcegroup create isns_rg 5) Verify that the SMF resource group has been created. An example output: # clresourcegroup status isns_rg === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ isns_rg pstar4 No Unmanaged pstar3 No Unmanaged pstar2 No Unmanaged pstar1 No Unmanaged 6) Add an iSNS SMF failover application resource to the resource group. When you create an iSNS resource of SMF proxy resource type, you need to specify the extension property "Proxied_service_instances". The extension property's value is the path to a file that contains proxied SMF service along with path of the corresponding service FMRI manifest file. An example property file "isns_svc.txt" below shows the service name and the path to the manifest file for the iSNS server. You may create a local file on all nodes of the cluster or place the file in a cluster file system to let each node share the same defintion. In the example below, the isns_fs file system is assumed to be created and mounted. For creating a Cluster File system, refer to http://docs.sun.com/app/docs/doc/819-2970/6n57ljhns?a=view # cat /global/isns_fs/isns_svc.txt , # clresource create -g isns_rg -t SUNW.Proxy_SMF_failover -x \ Proxied_service_instances=/global/isns_fs/isns_svc.txt isns_resource Note that isns_resouce above is an example resource name. 7) Verify that the SMF failover application resource has been added and validated. # clresource show isns_resource === Resources === Resource: isns_resource Type: SUNW.Proxy_SMF_failover Type_version: 2.0 Group: isns_rg R_description: Resource_project_name: default Enabled{pstar4}: True Enabled{pstar3}: True Enabled{pstar2}: True Enabled{pstar1}: True Monitored{pstar4}: True Monitored{pstar3}: True Monitored{pstar2}: True Monitored{pstar1}: True 8) Let the Cluster manage the resource group #clresourcegroup manage isns_rg #clresourcegroup status isns_rgsource === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ isns_rg pstar4 No Offline pstar3 No Offline pstar2 No Offline pstar1 No Offline 9) Now specify a data store file in a Cluster File System through svccfg(1M). #svccfg -s isns_server setprop config/data_store_location="/global/isns_fs/isnsdata.xml" where /global/isns_fs is a mount point for a cluster file system among cluster nodes as described step 6. The server will create the file if it doesn't exist at the start time. You should specify the same data store file property on all nodes in order to have all nodes to share the data store. 10) Enable the resource for the iSNS server online. #clresource enable isns_resource 11) Run the iSNS server by bringing the resource group online. # clresourcegroup online isns_rg With the steps above the iSNS server will be running in another node when cluster failover occurrs. Note that if the resource group is unmanged for whatever reason you need to repeat step 8-11. ------------------------------------------------------------------------------- Changing iSNS service properties after encapsulating with Failover SMF Proxy Resource ------------------------------------------------------------------------------- You should not use SMF svcadm for disabling, enabling or refreshing SMF services that are encapsulated in a proxy resource. In order to change properties of the SMF services (in the SMF repository) that are encapsulated in a proxy resource, you should follow the following steps. Example steps to follow for changing a property of the service. 1) On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization. 2) Bring the iSNS reourcegroup offline # clresourcegroup offline isns_rg 3) Disable iSNS resource # clresource disable isns_resource 4) Change the required properties using Solaris SMF service commands You need to change these properties on all nodes of the cluster node list. For example, # svccfg -s isns_server setprop config/ESI_retry_threshold_count=4 You should change the property on all nodes. Otherwise, during a fail over situation, you will not have expected service properties in place. Note that if you unmanage the resource group(isns_rg from the example above) or delete the resource group(isns_resouce from the example above) any changed properties will be overwrritten by defalut values. 5) Enable iSNS resources # clresource enable isns_resource 6) Bring the iSNS resourcegroup online from one node # clresourcegroup online isns_rg