SUN CLuster probe value

Question

Hi,
I've a little question about probe value when creating a probe script.
Exit code 100 (automatic failover) means that the probe is not valid and it should restart during the rety-count in the retry_interval,
Exit code 0 means that everything is OK
What about the other values? (1,2,......99). Is there other values ??
Thanks.

Answer 1

Pat,
For GDS there is also exit 201, which will perform an immediate failover.
Your exit 100 ---> to immediate failover is not completely true. An exit 100 from the probe will inform GDS that the application has failed and requires immediate attention. That attention is determined by other resource properties, i.e. Retry_count and retry_interval. So, assuming Retry_count=2, then GDS will attempt a resource restart and only consider a failover to another node once Retry_count is exceeded within Retry_interval.
The SUNW.gds man page provides further information, i.e.
The exit status of the probe command is used to deter-
mine the severity of the failure of the application.
This exit status, called probe status, is an integer
between 0 (for success) and 100 (for complete failure).
The probe status can also be 201, which causes the
application to fail over unless Failover_enabled is set
to False.
One point to also consider is that Sun Cluster also sums the failure history, so 100 indicates a complete failure. This implies that your probe could exit 50 and if the next time the probe runs it also exit's 50, you'll have a failure history sum of 100 which would trigger a reaction for a complete failure, e.g.
25 + 25 + 25 +25 = 100 would trigger a complete failure
50 + 50 = 100 would trigger a complete failure
Please note that if you consider exit values such as 25 or 50, then the failure history must be summed within the moving Retry_interval window. So if Retry_interval was set to 300 then you have a 5 minute moving window in which to sum 100 in order to get GDS to react to a complete failure. This implies that if your probe exits 50 and then 301 seconds later exits 50 again GDS won't react unless your probe exists sum 100 with Retry_interval.
Hope this makes sense.
Regards
Neil