Patch Date:  February, 2010

OS: Linux
OS Version: RHEL50 (x86_64/i686)
Fixes Applied for Products:
  VRTSvcsag - Veritas Cluster Server (VCS) Bundled Agents by Symantec

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

 PATCH VRTSvcsag 5.0MP3RP2HF7 for VCS Bundled Agent 5.0MP3RP2
===============================================================

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


GETTING STARTED
---------------
This patch applies only to:
  VRTSvcsag 5.0MP3RP2 running on RHEL50 for x86_64/i686

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


CRC AND BYTE COUNT
------------------
Ensure that the patch file that you have downloaded matches the following checksum and byte count, depending on the OS version you are using.

Use the following command to find the checksum and byte count.
For RHEL50 (i686/x86_64):
# cksum VRTSvcsag-5.0.30.27-MP3RP2HF7_RHEL5.i686.rpm
395031907       497553  VRTSvcsag-5.0.30.27-MP3RP2HF7_RHEL5.i686.rpm


PACKAGES AFFECTED BY THIS PATCH
-------------------------------
This patch updates the following VCS package: 
  VRTSvcsag from 5.0MP3RP2 to 5.0MP3RP2HF7


FIXES AND ENHANCEMENTS INCLUDED IN THIS PATCH 
---------------------------------------------
Etrack Incident: 1943070
Case ID: 320-236-317

SDR's of Fixed Symantec Incidents
---------------------------------
Symantec Incident: 1943070

Symptoms:
* When a Samba server is configured with the non-default path of 
  the smb.conf file, the agent cannot monitor the resource.
* Also the VCS SambaServer agent does not monitor multiple Samba 
  instances.

Defect Description:
* The SambaServer agent only supports the default smb.conf configuration file path. This is because for the default smb.conf file path the PID file named smbd.pid is located in the <SambaLockDir> directory, and the SambaServer agent looks for the smbd process ID only in this smbd.pid file.  If the smb.conf file is located in the non-default location or its name is different than "smb.conf", the pid file generated is named as smbd-<smb.conf.filename>.pid.
The existing SambaServer agent did not read the smbd process ID from such non-default smbd PID file name.

* The VCS SambaServer agent supported only single instance of smbd on the given cluster node. Although this is not a defect but a feature
request, the patch covers support for this request.
Resolution:
* Now the SambaServer agent derives the Samba PID file path using the configured smb.conf file path. This way it correctly reads the smbd process ID and monitors the same.
* Also the SambaServer agent now supports multiple Samba instances. Now, the agent monitors each instance on its specified interfaces and ports.


INSTALLING THE PATCH
--------------------
Run the following steps on all nodes in the VCS cluster:
1. Stop VCS on a node.
2. Install the patch.
3. Restart VCS on the node.

Stopping VCS on a node
----------------------
To stop VCS on a node:

1. Ensure that the "/opt/VRTS/bin" directory is included in your PATH
   environment variable so that you can execute all the VCS commands.     
   For more information, refer to the Veritas Cluster Server 
   Installation Guide.

2. Verify that the version of VRTSvcs is 5.0 MP3 RP2 for Linux.

3. Freeze all the service groups persistently.
    # haconf -makerw
    # hagrp -freeze <group> -persistent
    # haconf -dump -makero

4. Run the following commands to update SambaShare agent's type 
   definition to work with the patched agent.
    # haconf -makerw
    # hatype -modify SambaShare ArgList -add SambaServerRes
    # haconf -dump -makero

5. Stop the cluster on all nodes. If the cluster is writable, you may
   close the configuration before stopping the cluster.
    # haconf -dump -makero

   From any node, execute the following command.
    # hastop -all
    or
    # hastop -all -force

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

   On all nodes, make sure that both had and hashadow processes are
   stopped. Also, stop the VCS CmdServer on all nodes.
    # CmdServer -stop


Installing the patch
--------------------
Repeat the following steps on all the nodes.
1. Gunzip and untar the downloaded patch. 

2. Change directory to the unzipped patch location. 

3. Install the VRTSvcsag patch using the following command:
	# rpm -Uvh VRTSvcsag-5.0.30.27-MP3RP2HF7_<DIST>.<ARCH>.rpm
   where, DIST is RHEL50 and ARCH is i586/i686.

4. Verify that the new patch has been installed:
	# rpm -q VRTSvcsag
   The following information is displayed after successful patch 
   installation:
	   VRTSvcsag-5.0.30.27-MP3RP2HF7_<DIST>
   where, DIST is RHEL50 .


Re-starting VCS on a node
-------------------------
1. At this time, you can start the cluster services on all cluster 
   nodes. First start VCS on one node:
    # hastart

   On all the other nodes, start VCS by issuing the hastart command 
   after the first node goes to LOCAL_BUILD or RUNNING state.

2. Unfreeze all the groups:
     # haconf -makerw
     # hagrp -unfreeze <group> -persistent
     # haconf -dump -makero


UNINSTALLING THE PATCH
----------------------
Removal of the patch will result in removing the whole package 
from the system or node. To go back to a previous installed version 
of the package, you may need to re-install the package again.

To uninstall the patch:

1. To stop VCS on the node, follow the steps given in the section "Stopping VCS on a node" above.

2. Uninstall the patch by using the following command:
	# rpm -e VRTSvcsag

3. Verify that the package has been removed:
	# rpm -qa | grep VRTSvcsag 
   The package VRTSvcsag should not be displayed, which confirms 
   that the package is removed.

4. Restart VCS on the node following the steps given in the section   "Re-Starting VCS on a node" above.

5. Run the preceding steps on all nodes in the VCS cluster.