Etrack Incidents: 3544014, 3554888, 3558091, 3560778, 3562000, 3563162, 3564824, 3568891, 3575234, 3575748, 3585568, 3585625, 3590152, 3592242, 3592293, 3593646, 3593686, 3613957, 3615771, 3629749, 3633211, 3646306, 3547070, 3607102, 3645575, 3647882
                          * * * README * * *
               * * * Veritas Operations Manager 6.1 * * *
                        * * * Hot Fix 200 * * *
                         Patch Date: 2014-11-11


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLING THE PATCH
   * REMOVING THE PATCH
   * SPECIAL INSTRUCTIONS
   * SUMMARY OF KNOWN ISSUES
   * DETAILS OF KNOWN ISSUES
   * OTHERS

PATCH NAME
----------
Veritas Operations Manager 6.1 Hot Fix 200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX 6.1 ppc
AIX 7.1 ppc
HP-UX 11i v2 (11.23)
HP-UX 11i v3 (11.31)
RHEL5 i686
RHEL5 x86-64
RHEL6 x86-64
SLES10 i586
SLES10 x86-64
SLES11 x86-64
Solaris 10 SPARC
Solaris 10 X86
Solaris 11 SPARC
Solaris 11 X86
Solaris 9 SPARC
Windows Server 2008 R2 X64
Windows 2008 X64
Windows 2008 32-bit
Windows 2012 X64
Windows 2012 R2 X64


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
Veritas Operations Manager 6.1.0.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
PATCH ID:vom-HF0610200

3544014 (3544024)  veaintf doesn't spawn msfocreg.exe. 
3554888 (3554764)  Disk type resources from CVM were being shown twice in VOM availability perspective. 
3558091 (3558088)  Switch configuration fails if password has single quotes ('). 
3560778 (3560777)  Issues with disk discovery when LUNZ devices are present. 
3562000 (3517052)  Mismatch between VOM and Sort for SPVU calculation.
3563162 (3563150)  VVR RVGs displayed on the wrong host in CMS Console with host aliasing. 
3564824 (3564823)  Unable to delete Availability perspective Organization object. 
3568891 (3526792)  VOM doesn't display RVG and host relationships properly in CVR environment. 
3575234 (3577772)  Layout is not displayed for volumes created by LVM. 
3575748 (3575745)  Policy Check for IP Resource is adding a three digit number in front of
                   the IP resource name, this is causing an invalid violation to be reported. 
3585568 (3585566)  Keyless License not detected. 
3585625 (3573940)  User is unable to select FSS option while Creating DG from Cluster in SFRAC env due to Cluster type RAC 
3590152 (3590151)  Policy Scan for Disk Connectivity does not give enough detail 'LUN ID'. 
3592242 (3642699)  Set credential operation for secure databases fails. 
3592293 (3576824)  vxdclid is opening too many file descriptors. 
3593646 (3593642)  HF install will fail if there is insufficient space. 
3593686 (3593632)  Base Release displays Incorrect for SFHA-RHEL6_x86_64-6.2. 
3613957 (3613956)  Unable to add a host to VOM after upgrade to VOM 6.1. 
3615771 (3615769)  Add host failing with MH having english-UK locale. 
3629749 (3629745)  VxFS file system report usage is not getting updated, reports are incorrect. 
3633211 (3571489)  Top Hosts for Thin Reclamation Report is not showing hosts, which has Thin Reclaimable luns from VMAX array. 
3646306 (3653045)  Fail to remove a managed host from VOM. 
3547070 (3526358)  VOM 6.0 statistics 'Live' option shows incorrect 'free memory'. 
3607102 (3607101)  VOM API Certificate validation period is too short. 
3645575 (3663528)  xprtld daemon cannot be started after install on RHEL 7. 
3647882 (3651166)  VOM console sees Solaris 11 SFHA 6.1.1 as 6.1 


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

 PATCH ID:vom-HF0610200

 * INCIDENT NO:3544014	 TRACKING ID:3544024

SYMPTOM: veaintf doesn't spawn msfocreg.exe. 

DESCRIPTION: It happens because veaintf checks existence of msfocreg.exe in invalid location and exit with an 
error that file doesn't exist. Therefore veaintf doesn't spawn msfocreg. 

RESOLUTION: Changes done to check file existence in valid location. 

 * INCIDENT NO:3554888	 TRACKING ID:3554764

SYMPTOM: Disk type resources from CVM were being shown twice in VOM availability
perspective. 

DESCRIPTION: If disk type resources are configured in CVM, and if such a
resource is part of a parallel service group, and if the disk type attribute is
set differently for that resource on each member host, then its entry was
displayed twice in tree view, even if it was a single resource. 

RESOLUTION: Made changes to database view that shows resources in tree view in availability
perspective to get rid of unnecessary storage related joins. 

 * INCIDENT NO:3558091	 TRACKING ID:3558088

SYMPTOM: Switch configuration fails if password has single quotes (') 

DESCRIPTION: While configuring switch, if switch password contains single quotes, UI fails
while saving this configuration due to single quote (') in password. 

RESOLUTION: Allow single quote (') in password as backend discovery is supported but to
handle this character, escape single quote character (') from password before
saving it. 

 * INCIDENT NO:3560778	 TRACKING ID:3560777

SYMPTOM: Issues with disk discovery when LUNZ devices are present. 

DESCRIPTION: VOM was incorrectly showing the LUNZ devices as Disks. 

RESOLUTION: Modified the code to exclude the LUNZ devices from Disk as well as Devicepath 
tables. This fix is applicable only for SFW hosts. 

 * INCIDENT NO:3562000	 TRACKING ID:3517052

SYMPTOM: mismatch between VOM and Sort for SPVU calculation. 

DESCRIPTION: Customer has global zones which are in cluster.  SPVU shown in the 
view does not match with the SPVU popup.

All global zones in the cluster have same model, cores and processors except for 
one. Hence the SPVU-per-core value for that zone is different.

Stored procedure considered cores from all global zones including the one for 
which spvu-per-core was different. Popup did not consider this zone. Hence the 
values did not match. 

RESOLUTION: Made change such that one distinct cluster node will have its own 
SPVU 
calculation. So, even if make/cores/processors are different for zones in 
cluster, SPVU will be calculated accordingly.

Ensured that SPVU True-up report should sum-up SPVUs from all these zones and 
show Total SPVU for the product correctly. 

 * INCIDENT NO:3563162	 TRACKING ID:3563150

SYMPTOM: VVR RVGs displayed on the wrong host in CMS Console with host aliasing. 

DESCRIPTION: If VVR is configured with host alias, then host reports incorrect
RVGs. It happens because host-id was getting reported for remote RVG as well. 

RESOLUTION: Changes done to report host-id only for local RVG, not for
remote RVG. 

 * INCIDENT NO:3564824	 TRACKING ID:3564823

SYMPTOM: Unable to delete Availability perspective Organization object. 

DESCRIPTION: When an OE has some child elements associated and they later are 
removed, OE can't be deleted immediately with the error saying OE has
associated child objects. This is due to views related to Cluster do not get
cleaned up and stale entry under OE is not deleted resulting in error. 

RESOLUTION: Added clean-up logic for stale VCS related and static_view objects in
the OE during the post host deletion time. 

 * INCIDENT NO:3568891	 TRACKING ID:3526792

SYMPTOM: VOM doesn't display RVG and host relationships properly in CVR environment. 

DESCRIPTION: Host and RVG relationship flip-flops among the hosts in cluster. This
happens because all hosts in cluster reports same RVG in their SF discovery cycle. 

RESOLUTION: For shared RVG, every host in cluster will report on behalf
of LogOwner's host-id. It will avoid flip-flop issue and all shared RVG will be
displayed under LogOwner only. 

 * INCIDENT NO:3575234	 TRACKING ID:3577772

SYMPTOM: Layout is not displayed for LVM volumes if VOM HF1 or subsequent HFs are 
installed. 

DESCRIPTION: Layout is not displayed for LVM volumes if HF1 is installed. This 
happened because while fixing one issue, key in hash was not updated. 

RESOLUTION: Fixed key population in hash that maintains mapping of LVM volume to 
layout. 

 * INCIDENT NO:3575748	 TRACKING ID:3575745

SYMPTOM: For policy check called IP resource check, resource ID is shown in violation
details instead of resource name. And, the policy check does not work for a
global cluster/host in global cluster. 

DESCRIPTION: Violation details view shows resource ID instead of resource name.
Policy check does not work for a global cluster/host in global cluster. 

RESOLUTION: Changes have been made in violation details view to show resource ID.
Specific command is fired in case of global cluster/host in global cluster to
make the policy check run successfully on it. 

 * INCIDENT NO:3585568	 TRACKING ID:3585566

SYMPTOM: False alert for VCS license not present is raised in case SF campus cluster DR is
configured. 

DESCRIPTION: Initially VCS installed check was not done and alert was raised for any 
campus cluster configured and VCS licenses not present. 
Causing DR license missing message even in case SF DR is configured. 

RESOLUTION: Made changes to check if DR is configured, raise alert if and only if VCS is 
configured. Alert won't be raised in case VCS is installed but not configured. 

 * INCIDENT NO:3585625	 TRACKING ID:3573940

SYMPTOM: In VOM, user not able to select FSS option while Creating DG from Cluster
in SFRAC env due to Cluster type RAC 

DESCRIPTION: Check for Cluster type is present which checks if cluster is of type
CVM or CVS so option is disabled for cluster type 'RAC' 

RESOLUTION: Check for cluster sub type removed. FSS DG creation will be allowed
for all hosts with FSS flag on. 

 * INCIDENT NO:3590152	 TRACKING ID:3590151

SYMPTOM: Even if disks from a VCS diskgroup type resource are connected to all clustered
nodes, they are reported as disconnected when Disk connectivity policy check is
run on host/Organization entity. 

DESCRIPTION: The disk connectivity policy check reports incorrect violations, and also does
not show LUN ID in violation details. 

RESOLUTION: Correction has been made in disk connectivity policy check, and LUN ID are shown
in violation details. 

 * INCIDENT NO:3592242	 TRACKING ID:3642699

SYMPTOM: Set credential operation for secure databases fails. 

DESCRIPTION: Set credential operation for secure databases fails with error 
"Failed to apply the credentials for database instance sybaseha: Probe to the
Database failed. Either Password is incorrect or Database is down". 

RESOLUTION: Password decryption issue resolved in VOM utility 'secwrapper'. 

 * INCIDENT NO:3592293	 TRACKING ID:3576824

SYMPTOM: The vxdclid daemon open too many file descriptors without closing. 

DESCRIPTION: Each vxlist request requires a new thread.
Opened file descriptors are not closed on thread creation failure. 

RESOLUTION: Check for thread creation failure and close opened file descriptors. 

 * INCIDENT NO:3593646	 TRACKING ID:3593642

SYMPTOM: HF install will fail if there is insufficient space in /tmp. 

DESCRIPTION: HF Deploy uses /tmp directory to extract tarball, if /tmp doesn't have
sufficient space then HF install will fail. 

RESOLUTION: Extracting tar into appdir to avoid it. 

 * INCIDENT NO:3593686	 TRACKING ID:3593632

SYMPTOM: Base Release displays incorrect information for SFHA-RHEL6_x86_64-6.2. 

DESCRIPTION: SFHA-RHEL6_x86_64-6.2 is visible in Infra->Deployment->HotFix->Name panel and
marked as GA. This SF version is not yet released, just archived in SORT "in
development" mode only. 

RESOLUTION: If the enable-sort-test file is present in CMS, only then report "in
development" product's information. 
 
 * INCIDENT NO:3613957	 TRACKING ID:3613956

SYMPTOM: Unable to add a host to VOM after upgrade to VOM 6.1 

DESCRIPTION: A Java exception occurs because of a database integer overflow
which results in an incorrect record value. 

RESOLUTION: Modify the database stored procedure function to properly insert
serial id linearly. 

 * INCIDENT NO:3615771	 TRACKING ID:3615769

SYMPTOM: Add host failing with MH having English-UK locale. 

DESCRIPTION: This is platform specific issue, issue is observed on Windows 2008 SP2. Add host
failing with MH having English-UK locale, it happens because systeminfo command
return OS version with special characters. 

RESOLUTION: Now executing systeminfo command in en-US locale to avoid special characters. 

 * INCIDENT NO:3629749	 TRACKING ID:3629745

SYMPTOM: VxFS file system report usage is not getting updated, reports are
incorrect. 

DESCRIPTION: For the report 'VxFs File Systems with Highest % of Used Capacity'
file systems with higher usage were not listed in reports. File systems of lower
usage are listed instead. 

RESOLUTION: Query used to list the file systems was showing reports in ascending
order, changed it to descending. 

 * INCIDENT NO:3633211	 TRACKING ID:3571489

SYMPTOM: Top Hosts for Thin Reclamation Report is not showing hosts which has
Thin Reclaimable luns from VMAX array. 

DESCRIPTION: Top Hosts for Thin Reclamation report under Server Perspective does
not show hosts and thin reclaimable vxfs file systems if they are using storage
from Symmetrix VMAX arrays.
The reason behind this issue is that vxdisk -o thin, fssize list does not
provide PHYS_ALLOC(mb) value for Thin Reclaimable luns which is from EMC
Symmetrix VMAX array. 

RESOLUTION: After applying this fix on VOM CMS, you should configure and
discover EMC Symmetrix VMAX arrays in VOM CMS using Storage Insight add-on.
As per technote TECH153261, Consumed Capacity Of Symmetrix Disk discovered via
SI-Addon is being considered as value of PHYS_ALLOC(mb). 

 * INCIDENT NO:3646306	 TRACKING ID:3653045

SYMPTOM: Fail to remove a managed host from VOM 

DESCRIPTION: An exception occurs when calling a stored procedure function for
fault tables. 

RESOLUTION: Modify the return of the stored procedure to proper table type. 

 * INCIDENT NO:3547070	 TRACKING ID:3526358

SYMPTOM: Live statistics for memory usage on Solaris mh shows incorrect free 
memory.

DESCRIPTION: When a user views the live stats option for memory utilization, the 
free memory displayed does not agree with the data reported by vmstat command 

RESOLUTION: VOM stats gathering was incorrectly collecting free memory from 
vmstat command. This is fixed by providing the correct arguments to vmstat while 
executing it. 

* INCIDENT NO:3607102	 TRACKING ID:3607101

SYMPTOM: Generated API certificate is no longer valid after 9 hrs. 

DESCRIPTION: The certificate generated for API login is valid only for 9 hrs. Once
that timeframe is crossed, a new certificate needs to be generated. This is an
overhead for certain customers. 

RESOLUTION: Added a new option 'nocertcheck' for API login which skips the
certificate validity check. However the permissions of the user logging in will
still be taken care of and the information will be shown accordingly.

Sample invocation:
/opt/VRTSsfmh/bin/xprtlc -l https://localhost:14161/vom/api/login -f
certfile=@/tmp/cert.txt -d nocertcheck=1 

* INCIDENT NO:3645575	 TRACKING ID:3663528

SYMPTOM: xprtld daemon cannot be started after install on RHEL 7. 

DESCRIPTION: xprtld daemon cannot be started after install on RHEL 7, as it fails 
to load the AT libraries. 

RESOLUTION: The AT library name was corrupted during copy hence the library 
failed to load causing xprtld to exit. This has been fixed and xprtld now starts 
up.

* INCIDENT NO:3647882	 TRACKING ID:3651166

SYMPTOM: VOM console sees Solaris 11 SFHA 6.1.1 as 6.1 

DESCRIPTION: SHHA 6.1.1 was installed on MH but CMS was displaying SF version as 6.1. 

RESOLUTION: There was some issue in sfha_version.pl for installed product sfcfsha.


INSTALLING THE PATCH
--------------------
IMPORTANT NOTE : Please take a backup of the database using the instructions given in the Admin guide before installing this Hotfix.

This Hotfix is applicable for VOM 6.1 Managed Hosts as well as VOM 6.1 Management Server.

1. Download the file vom-6.1.0.200.sfa
2. Launch a browser and login to the VOM management server.
3. Navigate to Settings ->   Deployment Icon.
4. Upload the Hotfix to the VOM CMS using the "Upload Solutions" button.
   The HF vom-6.1.0.200 should be visible in the Hot fixes tree node.
5. Please install this Hotfix on CS first using the following instructions:
	- Go to Settings ->  Deployment ->  Hot fixes ->  Veritas Operations Manager.
	- Click on Hot fixes Tab. Click on Applicable Hosts Tab.
	- Right click on CS Name and click on Install.
6. For installing this Hotfix on Managed Hosts, please follow the below instructions:
	- Go to Settings ->  Deployment ->  Hot fixes ->  Veritas Operations Manager.
	- Click on Hot fixes Tab and then right click on the HF vom-6.1.0.200 and select Install.
	- Select the 6.1 hosts on which you want to apply the HF and click on the Finish button.


REMOVING THE PATCH
------------------
Un-installation and rollback of this Hotfix is supported only on Solaris 9, Solaris 10, HP-UX and AIX.


SPECIAL INSTRUCTIONS
--------------------
1. It requires approximately around 2 GB of disk space to upload vom-6.1.0.200.sfa. Please ensure that Management Server has at least 2 GB of free disk space where CMS is installed.

2. For issue # 3564824, stale OE gets deleted after midnight. For immediate removal, following command can be used:-
   On Linux     : /opt/VRTSsfmcs/config/adm/db_cron_ctrl.pl --oper_type execute --task_name DB_PURGE_STALE_ENTRIES
   On Windows   : 1. cd C:\Program Files\Veritas\VRTSsfmh\bin 
                  2. perl.exe "C:\Program Files\Veritas\VRTSsfmcs\config\adm\db_cron_ctrl.pl" --oper_type execute --task_name DB_PURGE_STALE_ENTRIES

SUMMARY OF KNOWN ISSUES
-----------------------
3662841 (3663615)  HF install is failing using vomadm command for Solaris 11 MH

DETAILS OF KNOWN ISSUES
-----------------------
3662841 HF installation is working fine through deployment management on Solaris 11 MH, but fails with vomadm command. 

OTHERS
------
NONE