This paragraph provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for N1 Service Provisioning System only.
For restrictions that apply to all data services, see the Sun Cluster Release Notes.
Your data service configuration might not be supported if you do not adhere to these restrictions.
Sun Cluster HA for N1 Service Provisioning System can only be configured as a failover data service. Each component of N1 Grid Service Provisioning System can operate as a failover data service only. Therefore, all the components of the Sun Cluster HA for N1 Service Provisioning System can only be configured to run as failover data services.
Install the N1 Grid Service Provisioning System components on shared storage. The Master Server and the Local Distributor have to be installed on the shared storage. The remote agents which are configured to bind on the logical host have to be installed on the shared storage as well.
This restriction is automatically adhered in failover zone configurations.
Configure a Sun Cluster resource for the N1 Grid Service Provisioning System Remote Agent for raw and ssl communication only. The Master Server will start and stop the Remote Agent on every connection, as long as the Remote agent is configured for ssh communication. In this case, there is no Sun Cluster resource needed. In the ssh scenario, you have to install the N1 Grid Service Provisioning System Remote Agent on the shared storage and copy the ssh keys from one node to the remaining nodes of the cluster. This assures that all the cluster nodes have the same ssh personality.
There is no need to copy ssh keys in failover zone configurations.
The N1 Grid Service Provisioning System configuration in a failover zone uses the smf component of Sun Cluster HA for Solaris Containers. The registration of the N1 Grid Service Provisioning System data service in a failover zone defines an smf service to control the N1 Grid Service Provisioning System database. The name of this smf service is generated in this naming scheme: svc:/application/sczone-agents:resource-name. No other smf service with exactly this name can exist.
The associated smf manifest is automatically created during the registration process in this location and naming scheme: /var/svc/manifest/application/sczone-agents/resource-name.xml. No other manifest can coexist with this name.