<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">Patch-ID# 105008-03
Keywords: solstice ha high availability HA 1.3 SUNWhagen patch
Synopsis: Solstice HA 1.3: SUNWhagen Patch
Date: Dec/04/97

Solaris Release: 2.5.1

SunOS Release: 5.5.1

Unbundled Product: Solstice High Availability

Unbundled Release: 1.3

Relevant Architectures: sparc

BugId's fixed with this patch: 4080543 4058087 4061900

Changes incorporated in this version: 4080543

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

	/etc/opt/SUNWhadf/hadf/hafmconfig
	/opt/SUNWhadf/clust_progs/callmethod
	/opt/SUNWhadf/fault_progs/ha_dbms_call
	/opt/SUNWhadf/fault_progs/ha_dbms_serv

Problem Description: 

4080543: Fault monitors for database services are being launched before
         the start_net method for those monitored services even got
         started, this causes undesirable restart/takeover conditions.


(From rev 02)
4058087: CMM calls processor_bind() only on 'sun4d' arch, subsequently
     all its childs inherit the same cpu affinity, this behavior negatively
     impacts any program started from cluster transition.

(From rev 01)
4061900: HA 1.3 does not  fail over when public network is pulled.
     During a public net failure, a race condition between the faultd 
     abort thread and the cmm abort transition thread exist when the cluster 
     is running yp, this results in a race by both threads to grab the diskset
     and the following failure results:
    
       "ERROR: tkown_disks: metaset -s &lt;lhost&gt; -f -t failed: metaset: 
          &lt;phost&gt;: /etc/opt/SUNWmd/lock.1: Resource temporarily unavailable."

     By setting the faultd abort timeout longer than clustd, we are favoring
     clustd, ensuring it wins the race.

Patch Installation Instructions: 
-------------------------------- 
Refer to the Install.info file for instructions on using the
generic 'installpatch' and 'backoutpatch' scripts provided with
each patch.  Any other special or non-generic installation
instructions should be described below as special instructions.

Special Install Instructions: 
----------------------------- 

After installing patch on both nodes of the cluster, force a cluster 
reconfiguration to pick up the new value:

	# haswitch -r





There are no known problems with *initial* installation of this patch.
However, if you install this patch using installpatch, then remove it
using backoutpatch, and then install it once again using installpatch,
you may see error messages like the following from installpatch:

   ...
   Generating list of files to be patched...
   ./installpatch[77]: syntax error at line 6 : `'' unmatched
   mv: cannot access /tmp/resolvedfiles.5285
   Verifying sufficient filesystem capacity (exhaustive method)...
   ...

It appears that the patch still installs correctly after these error
messages are output.  For current status on this problem, reference
Sun bugid 4022870.
</pre></body></html>