Professional Documents
Culture Documents
GOAL
The Generic Data Service (GDS) is a mechanism for making simple applications highly
available or scalable by plugging them into the Solaris Cluster Resource Group
Management framework. Prior to Solaris Cluster 3.1 update 3 (9/04), the GDS model
assumed that all applications would be network aware. This document shows how to
register GDS for non-network aware applications pre Solaris Cluster 3.1 update 3 and
also covers a new property available since this release.
FIX
1. Introduction
There are two required properties for GDS resource type at resource creation:
Start_command
Port_list
However non-network-aware application does not have a listening port, which means
no port can be filled in for the "Port_list" property.
For Solaris Cluster version prior to 3.1u3 workaround is to leverage some well-known
ports of solaris, such as 7/tcp, 23/tcp. Use of Port 7/tcp is highly recommended, as port
7/tcp has been tested.
If security reason require to harden systems and close some well-known ports such as
7/tcp, 23/tcp, another choice is to disable port monitoring by using an alternate probe
script.
Starting Cluster 3.1 update 3, there is a new property available for SUNW.gds resource
type:
Network_aware=<boolean>
Setting this property equal to 'false' (default is 'true') means Port_List property does not
have to be set.
Below example will shows both Solaris Cluster pre 3.2 (sc* command) and post 3.2 (cl*
command) command.
Register the resource type SUNW.gds:
# scrgadm -a -t SUNW.gds
or
# clrt register SUNW.gds
Product
Sun Cluster 3.1
Sun Cluster 3.0
Sun Cluster 3.0 7/01
Sun Cluster 3.0 5/02
Sun Cluster 3.0 12/01
Solaris Cluster 3.2