OS: Solaris Sparc
OS Version: 5.8, 5.9, 5.10
Fixes Applied for Products:
	VRTSvcs - Veritas Cluster Server by Symantec

Additional Instructions:
Please read the instructions below before installing the patch.

 PATCH VRTSvcs 4.1MP2 HF2 for Veritas Cluster Server 4.1MP2
===============================================================

 Patch Date:  07 October, 2009

This README provides information on:
 * BEFORE GETTING STARTED
 * CRC AND BYTE COUNT
 * FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH
 * PACKAGES AFFECTED BY THE PATCH
 * INSTALLING THE PATCH
 * UNINSTALLING THE PATCH


BEFORE GETTING STARTED:
----------------------
This patch only applies to:
	VRTSvcs running on Solaris Sparc 5.8, 5.9 or 5.10

Patch ID's for the appropriate SunOS Versions:
	For SunOS Sparc Release 5.8, 142604-02.
	For SunOS Sparc Release 5.9, 142605-02.
	For SunOS Sparc Release 5.10, 142606-02.

Ensure that you are running the supported configurations before
installing this patch.


FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: 
--------------------------------------------
Etrack Incidents: 1831777, 1829082, 1819540

SDR's of Fixed Symantec Incidents:
--------------------------------
Symantec Incident : 1831777
Symptom:
	The HASHADOW failed to re-start HAD and dumps core.

Defect Description:
	The core dump was seen, as a NULL pointer was de-referenced.

Resolution:
	The issue is now fixed.
-----------------------

Symantec Incident : 1829082
Symptom:
	HAD recived SIGSEV, while notifier message handler was trying 
	to log a send() failure.

Defect Description:
	An incorrect format specifier in logger function in notifier binary 
	triggered the SIGSEGV.

Resolution:
	The correct format specifier is now being used.
-----------------------

Symantec Incident : 1819540
Symptom:
	SMTP notification email should contain Entity name in subject line.
	This is an enhancement requested by a customer.

Defect Description:
	The email from notifier says the following in Subject 
	"Subject: VCS Warning, CPU Usage exceeded the threshold on the system".
	It doesn't contain the Entity name and Entity type in the notification. 

Resolution:
	The notification email has been modified to include 
	the Entity type and Entity name as per the customer request.
-----------------------

PACKAGES AFFECTED BY THE PATCH:
-------------------------------
This patch updates the following VCS package(s) 
	VRTSvcs from 4.1MP2 to 4.1MP2HF2


INSTALLING THE PATCH:
--------------------
The following steps should be run on the nodes in the VCS cluster,
where the patch is going to be installed:

Stopping VCS on the cluster node:
--------------------------------
To stop the cluster on all nodes follow the given steps:
1. Ensure that "/opt/VRTS/bin" directory is included in your PATH
   environment variable so you can execute all the VCS commands. Refer
   to "Veritas Cluster Server Installation Guide" for more information.

2. Verify that the version of VRTSvcs is 4.1MP2 or later for Solaris Sparc.

3. Freeze all the service groups persistently:
	# haconf -makerw
	# hagrp -freeze [group] -persistent
	# haconf -dump -makero

3. From any one node, execute the following command to stop the cluster:
	# hastop -all -force

4. Verify that the cluster is stopped on all nodes by running 
   the hasys command:
	# hasys -state

5. On all nodes, make sure that both had and hashadow processes 
   are stopped.

6. Stop the VCS CmdServer on all nodes:
	# CmdServer -stop


Installing the Patch:
--------------------
1. Un-compress the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VRTSvcs 4.1MP2HF2 patch using the following command:
	# patchadd [patch-id]
   Where [patch-id] is either of the following depending on 
   system configuration,
	For SunOS Release 5.8, [patch-id] is 142604-02.
	For SunOS Release 5.9, [patch-id] is 142605-02.
	For SunOS Release 5.10, [patch-id] is 142606-02.

2. Verify that the new patch has been installed:
	# showrev -p | grep [patch-id]
   You will find the following output on display with the patch 
   installed properly:
Patch: [patch-id] Obsoletes:  Requires: [4.1MP2 patch-id] Incompatibles:  
Packages: VRTSvcs


Re-starting VCS on the cluster node:
-----------------------------------
At this time, you can start cluster services on the cluster nodes.
1. On one node, please verify that VCS configuration is valid.
	# hacf -verify /etc/VRTSvcs/conf/config/

2. If the configuration is valid, start VCS:
	# hastart
   On all other nodes, start VCS by issuing hastart(1m) once the first node 
   goes to LOCAL_BUILD or RUNNING state.

3. Unfreeze all the groups:
	# haconf -makerw
	# hagrp -unfreeze [group] -persistent
	# haconf -dump -makero


UNINSTALLING THE PATCH:
-----------------------
Steps to remove the Patch from a cluster node:
---------------------------------------------
1. Follow the steps provided under "Stopping VCS on the cluster node" 
   section above, to stop VCS on the node & unload any drivers, as required.

2. Remove the patch by the following command:
	# patchrm [patch-id]
   Where [patch-id] is either of the following depending on system 
   configuration,
	For SunOS Release 5.8, [patch-id] is 142604-02.
	For SunOS Release 5.9, [patch-id] is 142605-02.
	For SunOS Release 5.10, [patch-id] is 142606-02.

3. Verify that the patch has been removed from the system:
	# showrev -p | grep [patch-id]
   There shall be no result on the output.

4. Restart the node following the steps under 
   "Re-starting VCS on the cluster node" section above.