Date: 2011-01-05
OS: Solaris Linux Windows HP-UX AIX
Etrack Incidents: 2185496

====================================================================================================================
VOM hot fix that prevents VOM central server from reporting the incorrect policy check for: Mirror across Enclosures.
====================================================================================================================

Name: HF030142900-02
Platforms: Solaris, Linux, Windows CMS and Solaris, HP-UX, AIX, Linux MHs.
VOM versions: 3.1, 3.1 RP1

DESCRIPTION:
------------
VOM has policy check which checks if the configuration under Storage Foundation is setup properly or not. Under these checks we have one specific check called "Mirror across Enclosures". The policy check validates if set of volumes have mirrors which are spread across different enclosures. Due to ill check in the VOM policy check, VOM was incorrectly reporting the violation for volumes. 
The hot fix addresses the issue.


INSTRUCTIONS
--------------

1. Download the file "HF030142900-02.sfa".
2. Launch a browser and login to the VOM management server.
3. Navigate to "Settings -> Deployment Management.
4. Upload the add-on to the VOM CMS using the "upload" button.
5. Follow the steps below to apply the hot fix:
    a) Once the add-on with the name HF030142900-02 is visible under the table, the user can choose (via option "Install") to deploy this on the hosts.
    b) Select the hosts where the hot fix needs to be deployed.

Note:
-------------
After the hot fix is applied on VOM central server 3.1 and managed hosts, if the managed hosts are upgraded from 3.1 to 3.1 RP1 following problems can be observed:-

1. After the central server upgrade the hot fix file (S2Legacy.pm.HF030142900-02) will be present in the location "/opt/VRTSsfmh/agentlet/VRTS/PC".
2. After the managed host upgrade the hot fix file (S2Legacy.pm.HF030142900-02) will be present in the location "/opt/VRTSsfmh/agentlet/VRTS/PC".
3. In central server deployment management page it will show that hot fix is not installed on either central server or managed host.
4. Now if you try to deploy the hot fix, it will show message "Hot fix is already installed on this system".
5. To avoid this issue there are 2 possible ways:-
      a> Uninstall the hot fix before central server and managed host upgrade.
      b> Remove the file (S2Legacy.pm.HF030142900-02) present in the location "/opt/VRTSsfmh/agentlet/VRTS/PC" and deploy the hot fix.