* * * READ ME * * *
             * * * Veritas Operations Manager  4.0 * * *
             * * * Hot Fix 040010970-07 * * *
                   Patch Date: 2011.07.20



This document provides the following information:

   * PATCH NAME
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Operations Manager Hot Fix 040010970-07


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSsfmh
VRTSsfmcs

BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------

   * Veritas Operations Manager 4.0


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX, Linux, Windows, Solaris and HP


INCIDENTS FIXED BY THE PATCH
----------------------------
This patch fixes the following Symantec incidents:

* 2430339
* 2437732
* 2437604 


SYMPTOM:
1. Large number of mh_driver processes seen on Managed hosts in case host is configured to multiple VOM Central Servers.
2. /etc/default/sfm_resolv.conf file gets deleted on Linux VMWare Managed hosts
3. Large number of mh_driver processes seen for VCS family on AIX managed hosts which have VCS 4.x installed.



DESCRIPTION:
HotFix HF040010970-07 is applicable for 4.0 Managed hosts and 4.0 Central Server

It addresses the following issues:-

1. Large number of mh_driver processes seen on Managed hosts
This is seen for certain cases when the managed host is configured to multiple VOM Servers.
if a CLI called by the mh_driver discovery process hangs and then the host is configured to multiple VOM servers then subsequent
scheduled mh_driver processes take a blocking lock on a file that is already locked by the hung mh_driver process.
This causes many mh_driver processes to get built up and not terminate.

2. /etc/default/sfm_resolv.conf file gets deleted on Linux VMWare Managed hosts
The VOM logic for creation of a hostguid for VMWare hosts is based on MAC addresses. Under certain scenarios VMWare could change
the MAC address of the guest. This causes the VOM hostguid to change and it deletes the sfm_resolv.conf file(incorrectly assuming the host is cloned.)

3. Large number of mh_driver processes seen for VCS family on AIX managed hosts which have VCS 4.x installed.
sfmh-discovery.pl processes uses /opt/VRTSsfmh/bin/hareg to monitor VCS related events. on AIX with VCS 4.x installed 
/opt/VRTSsfmh/bin/hareg does not find all its required libraries. This causes sfmh-discovery.pl to assume the error message from this CLI to be a VCS
operation change and it fires VCS discovery. This happens in a loop causing VCS discovery to spin.


RESOLUTION:
For issue 1) fix made to mh_driver to not take a blocking lock if it finds a previous discovery rescan is already in progress
For issue 2) fix made to not update the hostguid if the bios uuid has not changed for a Linux VMWare host.
For issue 3) fix made to sfmh-discovery.pl to use /opt/VRTSvcs/bin/hareg instead of /opt/VRTSsfmh/bin/hareg on AIX if VCS version installed is 4.x


INSTALLING THE PATCH
--------------------
This hotfix is applicable for VOM Central Server and VOM Managed hosts. 
It has to be first installed on the VOM CMS. Once successfully installed on the
CMS installation should be initiated for VOM Managed Hosts. 


1. Download the file "HF040010970-07.sfa".
2. Launch a browser and login to the VOM management server.
3. Navigate to Settings -> Deployment Management tab.
4. Upload the add-on to the VOM CMS using the "upload" button.
   The HF HF040010970-07 should be  visible in the table below.
5. Select the VOM CS host and install the HF on it first before installing it on any Managed hosts
During HF installation on the VOM CS the UI will be shutdown. 
Start the UI using the command "/opt/VRTSsfmcs/cweb/sfmw start" if the VOM CS is Solaris/Linux. 
On a windows VOM CS start the VOM UI using "sc start sfmgui"
6. Once the HF installation is complete on the VOM CS then install it on the Managed hosts


REMOVING THE PATCH
------------------
1. Launch a browser and login to the VOM management server.
2. Navigate to Settings -> Deployment Management tab.
3. Select the add-on. This will take you to the page which shows the status of the HF on all hosts.
Uninstall it first from the VOM CS host. Once the HF is uninstalled successfully from the VOM CS then uninstall it from
remaining managed hosts


SPECIAL INSTRUCTIONS
--------------------
NONE