Etrack Incidents: 3544014, 3547070, 3554888, 3558091, 3560778, 3562000, 3563162, 3564824, 3568891, 3575234, 3575748, 3585568, 3585625, 3590152, 3592242, 3592293, 3593646, 3593686, 3607102, 3613957, 3615771, 3629749, 3633211, 3636992, 3645575, 3646306, 3647882, 3658763, 3662841, 3685523, 3685545, 3686082, 3688167, 3693971, 3695787, 3698407, 3700127, 3701225, 3703516, 3703624, 3708334, 3717037, 3727593, 3732924, 3733986, 3733990, 3734134, 3736469, 3737673, 3738427, 3740142, 3741197, 3753106, 3753563, 3757978, 3760914, 3761954, 3764538, 3764885, 3776019, 3778452, 3780579
                          * * * README * * *
               * * * Veritas Operations Manager 6.1 * * *
                        * * * Hot Fix 600 * * *
                         Patch Date: 2015-06-12


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 600


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-HF0610600
* 3780579 (3766961) VOM does not discovery Volume Manager objects on UNIX and Linux
* 3760914 (3760913) "ERROR: integer out of range" flush in dbsync.log
* 3764885 (3764880) DBSync log file has entry of "Failed to open file /var/opt/VRTSsfmh/etc/sfm_sys.conf"
* 3778452 (3763940) Unable to upgrade VRTSsfmh to 6.1 from Veritas Operations Manager Web GUI
* 3776019 (3776022) VOM is reporting that "critical updates are missing" when it is shown that the 
specified patch is actually installed.
* 3740142 (3668419) The vxdclid daemon may core dump while querying for VxVM volume set tags.
* 3736469 (3753105) CPU cores counting includes CPU threads(or logical)
* 3732924 (3700501) Windows Server 2003 is incorrectly shown as an applicable host for deployment as a
VOM managed host.

PATCH ID:vom-HF0610500
3662841 (3663615)  HF install is failing using vomadm command for Solaris 11 MH. 
3734134 (3734126)  Service Group status is not updated for faulted host in the Availability Perspective 
3753106 (3753105)  CPU cores counting includes CPU threads(or logical) 
3753563 (3753565)  All the associated volumes to an RVG not visible in Volumes tab of RVG 
3757978 (3763970)  VOM on Windows is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 
3761954 (3761953)  VOM rule execution isn't working properly if rule is scoped on Organizations in Server perspective. 

PATCH ID:vom-HF0610400
3685523 (3705009)  Disk group failed alerts are not seen in VOM. 
3701225 (3709304)  VOM is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 
3708334 (3708193)  VOM displays incorrect patch information 
3727593 (3737995)  Deployment Policies can not have Risk Threshold > 10000 
3733986 (3694801)  Not able to set privilege control software & location using .csv file while doing agentless hosts configuration. 
3733990 (3729074)  Agentless host discovery using sudo goes in Failed State if discovery command like powermt etc not found on Host. 
3737673 (3737670)  Can not configure IBM SVC Enclosure using private certificate. 
3738427 (3738428)  VOM rule execution isn't working properly if rule is scoped on organizations in Server perspective. 
3741197 (3741193)  LDR tier mapping stored proc taking ~16 hours for execution on Qualcomm setup and further blocking all the LDR family discovery (dbsync) processes. 

PATCH ID:  vom-HF0610300
3613957 (3613956)  Unable to add a host to VOM after upgrade to VOM 6.1. 
3636992 (3636983)  VOM 6.1 shows MH status as "Not Installed" .
3658763 (3658760)  Failed to remove MHs from VOM GUI and vomadm cli with --force. 
3685545 (3685137)  DB updates/inserts are very slow and discovery requests from management hosts(MH) are rejected. 
3686082 (3691731)  Provide SFMdb3.dblog rotation for better logging and debugging. 
3688167 (3688166)  Adding host fails in VOM 6.1. 
3695787 (3671234)  HBA vendor name discovery corrupts the SF family sfm.dump and this results in filling up DB logs with error messages. 
3698407 (3698406)  Failure to add host using gendeploy. 
3700127 (3718074)  Customer needs REST API for licenses > Deployment details view and deployment by SPVU report. 
3703624 (3703625)  Tune postgres configuration settings as per machine configuration (physical memory). 
3717037 (3548269)  Info messages are being logged as error messages in log file. 
3693971 (3693967)  On Windows host with disk attached greater than 2TB, sfhbaapp.exe was crashing. 
3703516 (3660809)  The portlets in deployment overview tab takes too much time to show data.

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. 
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-HF0610600

* 3732924 (Tracking ID: 3700501)

SYMPTOM:
Windows Server 2003 is incorrectly shown as an applicable host for VOM managed
host install.
This can lead to an unsupported install of Windows Server 2003.

DESCRIPTION:
Windows Server 2003 is incorrectly shown as an applicable host for deployment as a
VOM managed host.
VOM no longer supports Windows Server 2003.

RESOLUTION:
Fail the install of the VOM managed host for Windows Server 2003.

* 3736469 (Tracking ID: 3753105)

SYMPTOM:
Ncore to license shown were more than actual physical cores on hyperthreading 
enabled hosts on Linux.

DESCRIPTION:
CPUINFO which used to calculate number of cores does not gives information if a 
core is physical core of virtual.

RESOLUTION:
Made changes to check if hyperthreading enabled then count threads per core and 
use that value to count actual Ncore to license.

* 3740142 (Tracking ID: 3668419)

SYMPTOM:
The vxdclid daemon is not running and therefore the vxlist command will not give
output.

DESCRIPTION:
The vxdclid daemon may core dump whey querying for VxVM volume set tags.
This must not be done when no volume set tags are present.

RESOLUTION:
Skip checking for volume set tags when no such tags are present.

* 3776019 (Tracking ID: 3776022)

SYMPTOM:
When VxFS patches are installed on the host, VOM UI still shows that critical 
updates are missing even though they are installed.

DESCRIPTION:
VOM discovery was not correctly discovering the patches installed. Hence it was 
still reporting as critical updates are missing from the host.

RESOLUTION:
The sfha_version.pl script which discovers the SFHA patches installed was fixed 
to discover the FS patches. Now VOM does not report critical updates are missing 
if the patches are installed.

* 3764885 (Tracking ID: 3764880)

SYMPTOM:
When any Managed Host reports data to Management Server, DBSync log file on Management Server, has entry of failed to open sfm_sys.conf file.

DESCRIPTION:
This message is logged by INI parser module, as it doesn't find file sfm_sys.conf, it is asked to parse.

RESOLUTION:
Checked existence of file sfm_sys.conf, before asking INI parser module to parse it.

* 3760914 (Tracking ID: 3760913)

SYMPTOM:
dbsync.log file logged with 22003 error messages "ERROR: integer out of 
range" for P_AUDIT_LOG table.

DESCRIPTION:
Issue is with primary key ID which is with SERIAL data type having 
range from 1 to 2147483647 and because of UPSERTRULE the id columns generated 
values are going out of SERIAL range.

RESOLUTION:
Modified the primary key data type to BIGSERIAL.

* 3776019 (Tracking ID: 3776022)

SYMPTOM:
When VxFS patches are installed on the host, VOM UI still shows that critical 
updates are missing even though they are installed.

DESCRIPTION:
VOM discovery was not correctly discovering the patches installed. Hence it was 
still reporting as critical updates are missing from the host.

RESOLUTION:
The sfha_version.pl script which discovers the SFHA patches installed was fixed 
to discover the FS patches. Now VOM does not report critical updates are missing 
if the patches are installed.

* 3778452 (Tracking ID: 3763940)

SYMPTOM:
Unable to upgrade VRTSsfmh to 6.1 from Veritas Operations Manager Web GUI with error in setup.pl.

DESCRIPTION:
Unable to upgrade VRTSsfmh to 6.1 from Veritas Operations Manager Web GUI with error in setup.pl because of missing variable.

RESOLUTION:
Added missing variable in setup.pl while generating it.

* 3780579 (Tracking ID: 3766961)

SYMPTOM:
The vxlist command times out and therefore VOM does not discovery Volume Manager
objects on UNIX and Linux

DESCRIPTION:
vxlist times out because vxdclid is not responding.  vxdclid is hanging on queries
to disks in a Volume Manager error state

RESOLUTION:
Skip Volume Manager disk queries for disks in error state

PATCH ID:vom-HF0610500

 * INCIDENT NO:3662841	 TRACKING ID:3663615

SYMPTOM: Installation of Hotfix fails on solaris 11 Managed Host while installing through
vomadm. 

DESCRIPTION: While trying to install Hotfix on a Sol 11 box using vomadm, we were mistakenly
picking up the tar.gz from  incorrect directory 

RESOLUTION: Modified the code to take cpu type also in consideration while fetching tar.gz 
from the store. 

 * INCIDENT NO:3734134	 TRACKING ID:3734126

SYMPTOM: In the "Availability" perspective when a cluster is selected in the left
pane and "Service Group Status" on the upper pane the status of a host is not
updated when a host is hard powered off. 

DESCRIPTION: In the "Availability" perspective when a cluster is selected in the
left pane and "Service Group Status" on the upper pane the status of a host is not
updated when a host is hard powered off. The fault is detected in other views, but
not in this one. On a hard power off the last status is preserved and the service
groups are marked online both on the powered off host where it was last online and
the new host where it was migrated to due to the fault. 

RESOLUTION: Changed the sql query to display a stale when node is down. 

 * INCIDENT NO:3753106	 TRACKING ID:3753105

SYMPTOM: Ncore to license shown were more than actual physical cores on hyper-threading 
enabled hosts on Linux. 

DESCRIPTION: CPUINFO which used to calculate number of cores does not gives information if a 
core is physical core or virtual. 

RESOLUTION: Made changes to check if hyper-threading enabled then count threads per core and 
use that value to count actual Ncore to license. 

 * INCIDENT NO:3753563	 TRACKING ID:3753565

SYMPTOM: vxprint -Vl does not show more than 255 characters hence not all the
associated volumes are not available. 

DESCRIPTION: If the length of the volume names in data vols key in vxprint -Vl goes more than
55 characters, then vxprint -Vl skips displaying the later volumes. Since, the
complete volume list is unavailable some volumes are not displayed. 

RESOLUTION: Modified the discovery to get the list of volumes from a different command. 

 * INCIDENT NO:3757978	 TRACKING ID:3763970

SYMPTOM: VOM is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 

DESCRIPTION: The man-in-the-middle POODLE attack takes advantage of the protocol version
negotiation feature built into SSL/TLS to force the use of SSL 3.0 and then
leverage this new vulnerability to decrypt select content within the SSL session. 

RESOLUTION: Update the OpenSSL to version 0.9.8zc which has the fix for this vulnerability. 

 * INCIDENT NO:3761954	 TRACKING ID:3761953

SYMPTOM: If different rules are created on different organizations in Server perspective, 
notification of fault/risk may be received by recipient of different rule too. 

DESCRIPTION: If different rules are created on different organizations in Server perspective, 
SNMP/SMTP notification for fault/risk which MS raises on behalf of MH(e.g. xprtld not 
running on MH, MH reinstalled) goes to Rule subscriber of organizations to which MS 
belongs instead of Rule subscriber of organizations to which faulted MH belongs. 

RESOLUTION: If rule is scoped on Organizations in Server perspective, and faults which are raised 
by MS on behalf of MH, decision of applicable rule for a fault/risk will be taken 
considering faulted host. 


PATCH ID:vom-HF0610400

 * INCIDENT NO:3685523	 TRACKING ID:3705009

SYMPTOM: Alerts related to disk groups are seen in VEA but not reported to VOM. 

DESCRIPTION: Due to corruption of alerts.cache file disk group alerts are not  seen in VOM
after Hf5 is installed. 

RESOLUTION: Added the handling of alerts.cache file's parsing. 

 * INCIDENT NO:3701225	 TRACKING ID:3709304

SYMPTOM: VOM is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 

DESCRIPTION: The man-in-the-middle POODLE attack takes advantage of the protocol version
negotiation feature built into SSL/TLS to force the use of SSL 3.0 and then leverages this
new vulnerability to decrypt select content within the SSL session. 

RESOLUTION: Update the OpenSSL to version 0.9.8zc which has the fix for this vulnerability. 

 * INCIDENT NO:3708334	 TRACKING ID:3708193

SYMPTOM: VOM does not recognize SFHA versions of 6.1.1.x and incorrectly gives a warning
that the host missing critical patches. 

DESCRIPTION: VOM does not recognize SFHA versions of 6.1.1.x and incorrectly gives a warning
that the host missing critical patches. 

RESOLUTION: Update the patch discovery module to recognize version 6.1.1.x. 

 * INCIDENT NO:3727593	 TRACKING ID:3737995

SYMPTOM: Risk and threshold value cannot be set more than 10, 000

DESCRIPTION: When attempting to create the tier policy based on SPVU if the threshold is set more than 10000 a pop-up is 
displayed with error "Risk and fault thresholds must be less than 10000".

RESOLUTION: Removed the constraint for maximum value of 10000 from fault and risk
threshold 

 * INCIDENT NO:3733986	 TRACKING ID:3694801

SYMPTOM: While doing Agentless hosts configuration using 'csv' file, you can not set
privilege control software & its location. 

DESCRIPTION: While doing Agentless hosts configuration using 'csv' file, you can not set
privilege control software like 'sudo' & its location (e.g. /usr/sbin). 

RESOLUTION: Added support to add privilege control software name and its location using .csv file. 

 * INCIDENT NO:3733990	 TRACKING ID:3729074

SYMPTOM: If you are discovering agentless Linux host using non root user then discovery may
go in failed state. 

DESCRIPTION: Agentless discovery of Linux Host may go in failed state using non root user. This
is due to non existence of powermt etc commands on host. 

RESOLUTION: Handled the discovery if some of the discovery commands like powermt not found on
hosts. 

 * INCIDENT NO:3737673	 TRACKING ID:3737670

SYMPTOM: Failed to configure IBM SVC Enclosure using private certificate, this asks for
password as well. 

DESCRIPTION: While configuring IBM SVC enclosure using private certificate, VOM says that
password field is mandatory. 

RESOLUTION: Made password field in IBM SVC Configuration page 'not mandatory'. 

 * INCIDENT NO:3738427	 TRACKING ID:3738428

SYMPTOM: If different rules are created on different organizations in Server perspective, 
notification of fault/risk may be received by recipient of different rule too. 

DESCRIPTION: If different rules are created on different organizations in Server perspective, 
SNMP/SMTP notification of fault/risk on shared object between hosts across 
different organizations may be received by recipient of different rule too. 

RESOLUTION: If rule is scoped on organizations in Server perspective, decision of applicable 
rule for a fault/risk will be taken considering host which is raising it and not 
the actual object on which the fault/risk is raised. 

 * INCIDENT NO:3741197	 TRACKING ID:3741193

SYMPTOM: Blocked LDR family discovery (dbsync) processes observed and 
SP_LDR_TIER_MAPPING stored proc in progress since ~8 hours. 

DESCRIPTION: Issue is with the business logic in SP_LDR_TIER_MAPPING stored 
proc which gets executed from within SP_update_ldr_info() proc. In tier 
mapping proc, for a host if there is no exact match found in PRICE TIER then 
there exists loop which iterates over this table to find best match for host's 
LDR info and it was observed that this loop was being performed for all the 
hosts irrespective of referring into look up table's similar entries. This is 
contributing to very poor performance and on in-house DB it took ~16 hours for 
this procedure to complete. 

RESOLUTION: Modified the business logic in SP_LDR_TIER_MAPPING to improve 
execution performance. In addition to performance, also corrected THREADS_PER_CORE
calculation in tier mapping. This value was found incorrect for the all the hosts 
which fall in best match category. 


 PATCH ID:vom-HF0610300
 
 * 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:3636992	 TRACKING ID:3636983

SYMPTOM: After upgrading MH, VOM shows the MH status as "Not Installed" 

DESCRIPTION: After the MH upgrade to 6.1, VOM shows the MH as not installed 
when it should be showing it as installed. 

RESOLUTION: The issue was due to the change in naming convention of SORT for 
VOM packages from vom-6.1.0.0-cms to vom-6.1.0.0_cms (hyphen replaced by 
underscore). This caused the VOM store discovery to not report and show the status as not 
installed. The Store discovery was fixed to accommodate the changed convention. 

 * INCIDENT NO:3658763	 TRACKING ID:3658760

SYMPTOM: Integer out of range exceptions during remove MH operation. 

DESCRIPTION: Delete host operation inserts log data into P_SF_OBJ_MOD_LOG. 
However database log table P_SF_OBJ_MOD_LOG is bloated and integer out of 
range exceptions are reported for additional data inserts. This is because 
of the primary key which is of SERIAL type and UPSERT RULE combination which 
results in bloat of primary key column values thereby rejecting any further 
data inserts. Also one of the stored procedure which gets called during 
deleting host had issues and was forcing the rollback of entire delete host 
operation. 

RESOLUTION: Empty P_SF_OBJ_MOD_LOG table, reset table's primary key sequence 
and drop the UPSERT RULE of table. Additionally fixed get_sfm_rpt_host_id() 
stored procedure. 

 * INCIDENT NO:3685545	 TRACKING ID:3685137

SYMPTOM: Database insert slowness, blocking queries and MH discovery request 
rejections. 

DESCRIPTION: The update/insert SQL queries on the CMS are running very slow 
and resulting into other discovery requests SQL queries waiting state for very 
long periods of time. This causes the waiting discovery triggered connection 
requests to be rejected and hence the updated data is not reflected in the CMS 
database.
The xdbadm cli binary which is used to send update queries into the database 
results into blocking queries and acquired locks for the entire execution 
session. Issue is because xdbadm is running entire SQL in one big transaction 
and hence is not releasing DB table locks thereby blocking other requests and 
hence overall slow activity because other parallel requests are waiting to 
acquire locks to perform their activity. 

RESOLUTION: In xdbadm cli binary the ODBC setting auto-commit was made off in 
Sybase but with PostgreSQLs default auto-commit behavior this ODBC setting is 
not required. Hence optimized xdbadm binary to not have auto-commit setting 
and the overall queries now run faster. 

 * INCIDENT NO:3686082	 TRACKING ID:3691731

SYMPTOM: Log file size of 34 GB with /var at 98% full 

DESCRIPTION: At present in 6.1 GA there is no log rotation set for database 
log file SFMdb3.dblog file and as a result size of the database log 
SFMdb3.dblog was observed in GBs (34 GB) for customer scenario. Due to this 
it becomes challenging for the field and support engineers to gather log for 
evidences. Also further for engineering its difficult to mine data from such 
a huge log file. 

RESOLUTION: Tuned database log SFMdb3.dblog rotation settings for better 
optimization and troubleshooting of database log file. 

 * INCIDENT NO:3688167	 TRACKING ID:3688166

SYMPTOM: Add host fails intermittently and there are CGI connection rejection 
errors on the MH. 

DESCRIPTION: The DB update calls are getting rejected, even though there are no 
currently running dbsync.pl process. This happens because the connection queue 
gets full and the connections were not getting de-queued on expiry. Restart of 
xprtld service allowed the add host to proceed. 

RESOLUTION: The connection handling in xprtld daemon has been fixed to also de-
queue the connections on expiry preventing the rejection of incoming 
connections. 

 * INCIDENT NO:3695787	 TRACKING ID:3671234

SYMPTOM: HBAs, other than Emulex and QLogic may cause the issue. 

DESCRIPTION: If there are HBAs other than QLogic & Emulex then HBA vendor name
discovery corrupts the SF family sfm.dump and this results in filling up DB logs
with error messages. 

RESOLUTION: Put a check to identify non Emulex and QLogic HBAs. Others HBAs
Vendor's name will be discovered as Unknown. 

 * INCIDENT NO:3698407	 TRACKING ID:3698406

SYMPTOM: Database insert slowness, long running dbsync processes and hence 
gendeploy rejections. 

DESCRIPTION: The environment has VCS cluster nodes configured and single VCS 
MH discovery triggered dbsync activity is taking more than expected time to 
complete. Since dbsync process execution is slow this results into xprtlc 
timeout of gendeploy request and finally failure to add host via gendeploy.
The VCS MH dbsync processes are slow because all the VCS tables have a trigger 
which performs inserts on this HIST table and further the UPSERT RULE on HIST 
table adds the overhead of validating INSERT/UPDATE while doing search on this 
table which results into expensive query plan. The rule on VCS HIST is not 
required since it overall adds the overhead to VCS tables inserts wherein 
every insert SQL is taking almost 1 sec to complete which ideally should be 
~0.2 sec. 

RESOLUTION: Removed UPSERT RULE on VCS history table - p_vcs_hist. 

 * INCIDENT NO:3700127	 TRACKING ID:3718074

SYMPTOM: No REST API support was available for Licenses. 

DESCRIPTION: Customer needs REST API for licenses > Deployment details view and 
Deployment by SPVU report. No REST API support was available for licenses.

RESOLUTION: Added 2 REST APIS 

 * INCIDENT NO:3703624	 TRACKING ID:3703625

SYMPTOM: Slow read performance of database. 

DESCRIPTION: At present in 6.1 GA product ships with default postgres configuration 
settings. Many of these settings if tuned provides better read and write database
performance. 

RESOLUTION: A perl script modify_pg_conf.pl which modifies DB parameters for better performance based
on total physical memory of the system is now shipped and executed at install time. 

 * INCIDENT NO:3717037	 TRACKING ID:3548269

SYMPTOM: Constant increase in size of log file. 

DESCRIPTION: Success messages, info messages as well as some queries were 
getting logged in the log file. Due to this log was unnecessarily filled up 
and size was increasing. 

RESOLUTION: Removed most of the inessential messages, rest redirected to 
internal logs. 

 * INCIDENT NO:3693971	 TRACKING ID:3693967

SYMPTOM: sfhbaapp.exe crashes. 

DESCRIPTION: On Windows host with storage attached greater than 2 TB, the sfhbaapp.exe crashes. Reason behind crash is 
DeviceIOControl call with command READ_CAPACITY_16 fails. Due to this the capacity value remain uninitialized and at later 
point in time when it was accessed it gives access violation error and creates dump. 

RESOLUTION: Initialized the capacity value to zero. If DeviceIOControl fails, will get the capacity using DiskGeometry. 

 * INCIDENT NO:3703516	 TRACKING ID:3660809

SYMPTOM: The portlets in deployment overview tab keeps showing data loading message. It takes too much time to show data. 

DESCRIPTION: If management server is managing more than 1000 hosts on which Storage Foundation or Storage Foundation HA products are installed,
the database queries take time to retrieve data from the database. 

RESOLUTION: The optimized database queries have been provided. 


  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: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: SFHA 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.600.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.600 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.600 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 3 GB of disk space to upload vom-6.1.0.600.sfa. Please ensure that Management Server has at least 3 GB of free disk space where CMS is installed.

2. This HF resolves DB performance issues. If the CMS is already experiencing DB performance issues the upload of Hotfix can fail through GUI. In such a case please install hotfix through vomadm using the commands given below on the CMS.     
   On Linux     : /opt/VRTSsfmh/bin/vomadm  hotfix --install <hf>
   On Windows   : 1. cd C:\Program Files\Veritas\VRTSsfmh\bin 
                  2. perl.exe vomadm hotfix --install <hf>

3. 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
				  
4. 3662841 - For installing HF5 on Solaris 11 MH through vomadm, HF4 needs to be installed first through GUI.

5. 3753106 - Fix for this issue is applicable for Linux only.

6. 3778452 - After installing 6.1.0.600, the MH package of 6.1 needs to be uploaded to resolve the issue.

SUMMARY OF KNOWN ISSUES
-----------------------
NONE

DETAILS OF KNOWN ISSUES
-----------------------
NONE

OTHERS
------
NONE