vom-Patch-6.0.0.0700

 Basic information
Release type: Patch
Release date: 2015-04-28
OS update support: None
Technote: None
Documentation: None
Popularity: 1301 viewed    downloaded
Download size: 237.66 MB
Checksum: 1332064567

 Applies to one or more of the following products:
Operations Manager 6.0.0.0 On AIX
Operations Manager 6.0.0.0 On HP-UX 11i v1 (11.11)
Operations Manager 6.0.0.0 On HP-UX 11i v2 (11.23)
Operations Manager 6.0.0.0 On HP-UX 11i v3 (11.31)
Operations Manager 6.0.0.0 On Linux
Operations Manager 6.0.0.0 On Solaris 10 SPARC
Operations Manager 6.0.0.0 On Solaris 10 X64
Operations Manager 6.0.0.0 On Solaris 11 SPARC
Operations Manager 6.0.0.0 On Solaris 11 X64
Operations Manager 6.0.0.0 On Solaris 8 SPARC
Operations Manager 6.0.0.0 On Solaris 9 SPARC
Operations Manager 6.0.0.0 On Windows 32-bit
Operations Manager 6.0.0.0 On Windows x64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
vom-6.0.0.0600 (obsolete) 2014-10-01

 Fixes the following incidents:
3345216, 3348061, 3362605, 3364450, 3368041, 3370322, 3373459, 3382649, 3385186, 3385525, 3393443, 3393519, 3393528, 3393825, 3396404, 3397462, 3403690, 3404524, 3404595, 3405184, 3409720, 3424122, 3429719, 3430962, 3436971, 3437599, 3441412, 3441540, 3443344, 3448587, 3450605, 3450788, 3450789, 3452646, 3452900, 3458341, 3461060, 3461444, 3462759, 3463744, 3465454, 3465831, 3468815, 3469021, 3484855, 3485022, 3497347, 3503269, 3504553, 3509361, 3513011, 3514649, 3516011, 3518586, 3540945, 3544018, 3549683, 3552213, 3554556, 3563168, 3575747, 3585567, 3587445, 3590153, 3592294, 3593645, 3593688, 3599090, 3599874, 3615772, 3630108, 3656633, 3685524, 3693972, 3709310, 3738097, 3757978

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
               * * * Veritas Operations Manager 6.0 * * *
                        * * * Hot Fix 0700 * * *
                         Patch Date: 2015-04-27


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.0 Hot Fix 0700


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 2012 X64
Windows Server 2003 R2 X64
Windows 2003 X64
Windows 2003 32-bit
Windows Server 2008 R2 X64
Windows 2008 X64
Windows 2008 32-bit


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
PATCH ID:vom-HF06000700
3503269 (3503268)  Direct download of Add-On failed. 
3656633 (3651166)  VOM console sees Solaris 11 SFHA 6.1.1 as 6.1 
3685524 (3705009)  Disk group failed alerts are not seen in VOM. 
3693972 (3693967)  On Windows host with disk attached greater than 2TB, sfhbaapp.exe was crashing. 
3709310 (3709304)  VOM is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 
3738097 (3737670)  Can not configure IBM SVC Enclosure using private certificate. 
3757978 (3763970)  VOM on Windows is vulnerable to the SSLv3 POODLE(CVE-2014-3566) attack. 

PATCH ID:vom-HF06000600
3575747 (3575745)  VOM 6.0 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. 
3585567 (3585566)  Keyless License not detected. 
3587445 (3577772)  Layout is not displayed for volumes created by LVM. 
3590153 (3590151)  Policy Scan for Disk connectivity does not give enough detail "LUN ID". 
3592294 (3576824)  vxdclid is opening too many file descriptors. 
3593645 (3593642)  HF install will fail if there is insufficient space in /tmp. 
3593688 (3593632)  Base Release displays incorrect for SFHA-RHEL6_x86_64-6.2 
3599090 (3558088)  Switch configuration fails if password has single quotes ('). 
3599874 (3599864)  Brocade Switch Zone information not being displayed for Brocade Switch. 
3615772 (3615769)  Add host failing with MH having English-UK locale.
3630108 (3592242)  Set credential operation for secure databases fails. 

PATCH ID:vom-HF06000500
3452900 (3560777)  Issues with disk discovery when LUNZ devices are present. 
3504553 (3520178)  VOM 5.0 hbaapp rewinds tape drives, causing a potential risk of overwriting previously backed up data. 
3513011 (3526792)  VOM does not properly show RVG and host relationships for VVR in clustered environments. 
3514649 (3517052)  Mismatch between VOM and Sort for SPVU calculation 
3516011 (3563150)  Clustered VVR RVGs displayed on the wrong host in MS Console with host aliasing. 
3540945 (3576296)  Data Availability card is blank after deploying HF. 
3544018 (3544024)  veaintf doesn't spawn msfocreg.exe. 
3549683 (3564823)  Unable to delete Availability perspective Organization object 
3554556 (3554764)  VCS resources displayed twice in VOM UI 
3563168 (3571489)  Top Hosts for Thin Reclamation Report is not showing vmax hosts 
3552213 (3552205)  SF6.1 hotfixes are not visible through VOM GUI.

PATCH ID: vom-HF06000400
3436971 (3509323)  Cannot start Veritas Storage Foundation Messaging Service (XPRTLD) 
3468815 (3505492)  Since 6.0 upgrade VOM showing wrong-- RVG status faulted 
3484855 (3486881)  [VMWare NRT] NRT discovery is not happening on the Linux upgraded setup 
3497347 (3505550)  Handle killing of java.exe for Windows in 6.0 MAINT 
3509361 (3509367)  Backslash missing from DOMAIN\User in Edit Config 
3514649 (3517052)  [VOM][06470529] mismatch between VOM and Sort for SPVU calculation 
3518586 (3526358)  VOM6.0 Statistics 'Live' option shows incorrect 'free memory'. 

Patch ID: vom-HF06000300
3497347	(3468475)  Cannot connect to web console after installing Hotfix 6.0.0.0200a.

Patch ID: vom-HF06000200
3348061 (3346812)  Script needed for duplicate VM ID check. 
3405184 (3405182)  Veritas Operations Manager (VOM) 6.0 Agentless discovery for Linux Host with device-mapper cannot correlate physical disks with LVM volume-groups and volumes. 
3424122 (3329566)  get_vitals returns the incorrect OSRELEASE("UNKNOWN-Server 4.0"), on windows 2012 and 2012R2 
3429719 (3429720)  Unable to add 2nd host due to same OS_UUID with infiniband mac 
3430962 (3430937)  When adding Windows MH trying to use gendeploy : ERROR":"Version mismatch for this utility. The import file is newer...". 
3437599 (3334167)  SSL certificate location showing blank in VOM even if LDAP configured with SSL certificate 
3441412 (3468964)  Installation of VOM HF was failing. 
3441540 (3441541)  VOM needs VRTSsfm.mib 
3443344 (3442750)  Attempting to sort on Qtrees page breaks loading Qtree pages for other filers 
3448587 (3448574)  VVR Bandwidth add-on is unable to find vxprint.exe in windows 
3450605 (3450601)  Hotfixes are not shown after upgrade to VRTSsfmh6 
3450788 (3402529)  Listing of DB files for the database is not available in API 
3450789 (3439388)  VOM 6.0: Customer is noting extra/extraneous multiple scrollbars in CSS overlaying some of the screen area. 
3452646 (3452644)  Unable to edit overridden attribute at resource level e.g. RestartLimit 
3458341 (3458350)  UI needs to unset filter flag for applicable hosts to sfa install. 
3461060 (3461058)  Unable to online disks from VOM UI on Windows hosts 
3461444 (3461447)  Can't test SORT connectivity from Management Server UI if proxy server is not specified. 
3462759 (3468903)  After removing add-ons from VOM UI it removes it from repository, but the entries are still remains in GUI 
3463744 (3463741)  [VOM 6.0] - VOM 6.0 does not detect errors on managed hosts 
3465454 (3465452)  SFM_Services_SECD starts outside of VCS after reboot of cluster node. 
3465831 (3461184)  [VCSFO_REPORT_ALERT]Average fail over duration Reports Data is cleared after some time 
3469021 (3469018)  Unable to configure LDAP/AD the last screen of configuration wizard is blank. 
3485022 (3486327)  Vulnerability port 5634 on HP-UX managed hosts 

Patch ID: vom-HF06000100
3345216 (3345210) New vdid needed for STK array on Solaris
3362605 (3424556) statlog data files are too big
3364450 (3363058) Scheduled firedrill does not offline after completing.
3368041 (3364402) Request unsuccessful error while saving licenses deployment details grouped by Host.
3370322 (3370321) Local filesystem shows multiple servers.
3373459 (3373460) Linux localhost PAM authentication fails
3382649 (3382647) Settings - management server page not loading
3385186 (3385183) Disk group Search needs hostname column and operations authority
3385525 (3323302) Validate User Group does not work if Active Directory allow Anonymous bind and DS ACL are used
3393443 (3396287) Unable to make event alert rule for removed path
3393519 (3388217) Showing 'Total' instead of 'Raw' size in overview page waterfall chart for thin pool/CPG.
3393528 (3388202) Showing label 'Thin Virtual Disk/Volume Count' instead of 'Virtual Disk Count'
3393825 (3393824) VOM report violation for layered volume and does not report violation for subvolume
3396404 (3411771) VOM 6.0 shows a file system faulted for all systems in VMWare environment though it is full only on one system.
3397462 (3397461) sfmh-discovery.pl should start hareg with all the options on solaris 9 if SUNWpool or SUNWpoolr are missing as they do not exists on Solaris 9
3403690 (3403696) [Infra]Blank page is displays for Suppress/Restore faults in Infra perspective.
3404524 (3404496) [VOM][05644566]License Life cycle report is showing BIRT exception
3404595 (3404695) [INFRA] SFHA download settings are not saved on a upgraded CS.
3409720 (3420991) Blank page when opening settings - sort - SFHA download settings.


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

 PATCH ID:vom-HF06000700

 * INCIDENT NO:3503269	 TRACKING ID:3503268

SYMPTOM: Direct download of Add-On failed. 

DESCRIPTION: Encryption and Decryption code was incorrect while storing and 
retrieving proxy password 

RESOLUTION: The password was not getting decrypted.Made corresponding changes in
Add-on/HF installation wizards.Added required jar file in the class-path. 

 * INCIDENT NO:3656633	 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. 

 * INCIDENT NO:3685524	 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:3693972	 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:3709310	 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:3738097	 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: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
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. 


 PATCH ID:vom-HF06000600

 * INCIDENT NO:3575747	 TRACKING ID:3575745

SYMPTOM: For policy check called IP resource check, resource ID is shown in violation
details instead of resource name. Therefore, 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:3585567	 TRACKING ID:3585566

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

DESCRIPTION: Initially VCS installed check was not done and alert was raised for any 
Campuscluster 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:3587445	 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:3590153	 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:3592294	 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:3593645	 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:3593688	 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:3599090	 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:3599874	 TRACKING ID:3599864

SYMPTOM: Brocade Switch Zone information not being displayed for Brocade Switch. 

DESCRIPTION: Query used to display Zone information (initiators, targets) was not 
returning results for discovered zone members - (switch domain , port index) 

RESOLUTION: Corrected the query to display data in GUI, if switch zone members that 
are like (switch domain, port index) are discovered from backend. 

 * INCIDENT NO:3615772	 TRACKING ID:3615769

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

DESCRIPTION: This is platform specific issue, it is observed on Windows 2008 SP2 MH 
having English-UK locale. 
For Linux CMS 6.0, MH get added special characters. For Linux CMS 6.1, add host fails 
with error. It happens because systeminfo command return OS version with special characters. 

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

 * INCIDENT NO:3630108	 TRACKING ID:3592242

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

 PATCH ID:vom-HF06000500

 * INCIDENT NO:3452900	 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:3504553	 TRACKING ID:3520178

SYMPTOM: VOM 5.0 hbaapp rewinds tape drives, causing a potential risk of overwriting
previously backed up data. 

DESCRIPTION: On VOM 5.0 Linux Agent with tape Drives attached, VOM hbaapp tries to perform SCSI
inquiry on Tape Drives and it may cause tapes to rewind.
Though, we use '-P' flag to skip tape drives discovery in VOM hbaapp but due to
bug in the code, hbaapp was not skipping SCSI inquiry on tape drives. 

RESOLUTION: Added code to skip SCSI inquiry on Tape Drives when hbaapp is running with '-P'
flag. 

 * INCIDENT NO:3513011	 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:3514649	 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 pop-up.

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. Pop-up 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:3516011	 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. 
This issue is applicable for Windows platform only.

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

 * INCIDENT NO:3540945	 TRACKING ID:3576296

SYMPTOM: Data Availability card is blank after deploying HF. 

DESCRIPTION: Regression due to HF. View used for showing data availability card 
was invalid when HF is installed on CMS. 

RESOLUTION: Added a call to stored procedure which compiles all views and stored 
procedures after HF is applied which updated all views. 

 * INCIDENT NO:3544018	 TRACKING ID:3544024

SYMPTOM: veaintf doesn't spawn msfocreg.exe. 

DESCRIPTION: This is regression, was introduced in VOM 6.0 HF4. It happens because
veaintf checks existence of msfocreg.exe in invalid location, 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:3549683	 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 not 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 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:3554556	 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:3563168	 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:3552213	 TRACKING ID:3552205

SYMPTOM: SF6.1 hotfixes are not visible through VOM GUI.

DESCRIPTION: Installed SF 6.1 hotfixes are not visible, it happens because changed version 
naming convention. 

RESOLUTION: Done changes to parse newly introduced version naming convention.
 
PATCH ID:vom-HF06000400

 * INCIDENT NO:3436971	 TRACKING ID:3509323

SYMPTOM: xprtld on windows managed host is not starting up 

DESCRIPTION: xprtld on windows mh was does not start if the port 5634 is already 
in listening state. This happened due to orphaned child process still running. 

RESOLUTION: The child process were of veaintf.exe that crashed making them 
orphaned. veaintf crash has been fixed which resolved the issue. 

 * INCIDENT NO:3468815	 TRACKING ID:3505492

SYMPTOM: VOM showing wrong RVG status faulted since 6.0 upgrade. 

DESCRIPTION: VOM was showing incorrect 'replication stopped' faults. 

RESOLUTION: The status which we were querying was not correct because of which we were raising 
wrong faults. Modified the code to query correct status. 

 * INCIDENT NO:3484855	 TRACKING ID:3486881

SYMPTOM: VMware Near Real Time discovery is not happening on the upgraded MS 6.0. 

DESCRIPTION: VMware Near Real Time discovery is not happening on the upgraded MS 
6.0 from previous version. This happened due to missing subscription entry for 
VMware event listener. 

RESOLUTION: Added subscription entry for VMware event listener as part of upgrade 
MS. 

 * INCIDENT NO:3497347	 TRACKING ID:3505550

SYMPTOM: Need to kill java.exe for Windows in 6.0_maint 

DESCRIPTION: In case of Windows server, when web server is stopped/restarted, 
need to kill running java.exe process during shutdown of web server. 

RESOLUTION: In case of Windows server, stamp process ID for java.exe in a file at 
server startup, which then will be used while shutdown of process to ensure 
java.exe is killed when web server is stopped 

 * INCIDENT NO:3509361	 TRACKING ID:3509367

SYMPTOM: In Edit vCenter Configuration wizard, backslash in domain\user is 
missing 

DESCRIPTION: If vCenter is configured with username with its domain, in Edit 
Configuration wizard, for username field, backslash is missing. 

RESOLUTION: For the user name field, escaped special characters for their special 
meanings so that now user name shows domain\username if configured so. 

 * INCIDENT NO:3514649	 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 pop-up.

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. Pop-up 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:3518586	 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. 

 PATCH ID:vom-HF06000300

  * INCIDENT NO:3497347	 TRACKING ID:3468475

SYMPTOM: Cannot connect to web console after installing Hotfix 6.0.0.0200a.

DESCRIPTION: After installing Hotfix 6.0.0.0200a, web server was not coming up as there were failures in updating jre files during Hotfix-2 installation. 

RESOLUTION: The issue has been fixed by killing any stale running java processes after
WEBGUI stop.
 
 
 PATCH ID:vom-HF06000200

 * INCIDENT NO:3348061	 TRACKING ID:3346812

SYMPTOM: Managed hosts with duplicate Virtual machine identifiers (VMIDs) are purged. 

DESCRIPTION: Managed hosts with duplicate Virtual machine identifiers are purged without a
warning. 

RESOLUTION: Provide a script named check_duplicate_vmid.pl that can be run to report possible
duplicate VMIDs in VOM 5.0/5.0.1 before upgrading to VOM 6.0. 

 * INCIDENT NO:3405184	 TRACKING ID:3405182

SYMPTOM: Veritas Operations Manager (VOM) 6.0 Agentless discovery for Linux Host with 
device-mapper cannot correlate physical disks with LVM volume-groups and 
volumes. 

DESCRIPTION: Agentless discovery of Linux host having DM (device-mapper) is unable to 
correlate the physical disk when the LVM commands, vgdisplay and lvdisplay, show the 
output with disk in mpath/mapper format 

RESOLUTION: Agentless discovery code has been changed to handle the PV name as listed in the 
above output to correlate with /dev/dm-# correctly. 

 * INCIDENT NO:3424122	 TRACKING ID:3329566

SYMPTOM: getvitals returns "OSRELEASE" : "UNKNOWN-Server 4.0" for windows 2012 
and windows 2012R2 

DESCRIPTION: Incorrect OSRELEASE returned Windows 2012 and Windows 2012R2 

RESOLUTION: Modify xprtld to check for windows 2012 and 2012R2 versions 

 * INCIDENT NO:3429719	 TRACKING ID:3429720

SYMPTOM: Unable to add Linux managed host to VOM CMS. 

DESCRIPTION: On Linux managed host with infiniband mac addresses, add host 
operation fails for 2nd host if one host is already added. This is because mac 
address are duplicate for infiniband adapters. 

RESOLUTION: VOM add host now skips infiniband addresses and uses ethernet 
addresses which are unique to construct hostguid on Linux. 

 * INCIDENT NO:3430962	 TRACKING ID:3430937

SYMPTOM: On MH, the gendeploy script fails when attempting to connect to CMS 

DESCRIPTION: Generated gendeploy script fails with error : ERROR":"Version 
mismatch for this utility. The import file is newer.." 

RESOLUTION: On CMS, Fixed gendeploy.pl script, which is used to create the 
gendeploy script used to manually add MH's. Added missing file close() statement. 

 * INCIDENT NO:3437599	 TRACKING ID:3334167

SYMPTOM: SSL certificate location showing blank in VOM even if LDAP configured 
with a SSL certificate. 

DESCRIPTION: The LDAP configuration Properties panel does not show the SSL
certificate location even though it was provided during configuration. 

RESOLUTION: Fetch the certificate details from VOM DB while showing the
Properties panel. 

 * INCIDENT NO:3441412	 TRACKING ID:3468964

SYMPTOM: When install operation is performed by selecting HF an error message is 
displayed as "Solution not available in store". 

DESCRIPTION: The required information was missing when install operation was 
performed by selecting HF. 

RESOLUTION: The issue has been fixed so that installation succeeds that is 
performed by selecting HF. 

 * INCIDENT NO:3441540	 TRACKING ID:3441541

SYMPTOM: SNMP faults are not being alerted 

DESCRIPTION: SNMP faults are not being alerted after configuring SNMP rules 

RESOLUTION: Include file /opt/VRTSsfmcs/config/snmp/VRTSsfm.mib 

 * INCIDENT NO:3443344	 TRACKING ID:3442750

SYMPTOM: Attempting to sort on Qtrees page breaks loading Qtree pages for
other filers. 

DESCRIPTION: When one tries to sort the Qtrees grid, nothing happens. And
after that if one navigates to another Qtree, once can see a blank page. 

RESOLUTION: The Qtree grid store was not being initialized afresh for new
instance of grid. Also the columns were not mapped for sorting. Initialize the
grid store for new instances of grid. Also map all the UI columns to DB columns
for sorting to happen properly. 

 * INCIDENT NO:3448587	 TRACKING ID:3448574

SYMPTOM: VVR Bandwidth report was not generated on Windows platform. 

DESCRIPTION: VVR Bandwidth report was not generated because populated rvg-id is 
invalid on Windows. Apart from that, environment variable vmpath was not getting 
populated in VOM discovery environment. 

RESOLUTION: Change done in rvg co-relation to populate correct rvg-id. Now populating vmpath 
from registry rather than environment variable. 

 * INCIDENT NO:3450605	 TRACKING ID:3450601

SYMPTOM: Hotfixes are not shown after upgrade to VRTSsfmh 6.0. 

DESCRIPTION: In VOM6.0 list of hotfixes is not visible inside 'Settings -->
Deployment --> Repository --> Hotfixes' page. This problem is because of Java
Warning message in json file. It was causing json to upload in DB. 

RESOLUTION: Fix is to redirect error messages in err files so that json files do not have 
any error messages. 

 * INCIDENT NO:3450788	 TRACKING ID:3402529

SYMPTOM: Unable to list DB files from API. 

DESCRIPTION: Listing of DB files for the database is not available using API. 

RESOLUTION: We have added the listing of DB files through API. 

 * INCIDENT NO:3450789	 TRACKING ID:3439388

SYMPTOM: Extra scroll bars appears on screen. 

DESCRIPTION: Extra/extraneous multiple scroll bars are visible in some of the 
panels for some browsers. 

RESOLUTION: Removed the extra scroll bars for Host overview panel as well as Disk 
list panel. 

 * INCIDENT NO:3452646	 TRACKING ID:3452644

SYMPTOM: Editable attributes like RestartLimit at resource level are non-editable from VOM
6.0 console. 

DESCRIPTION: Overridden attributes from Type level to Resource level are treated as non
editable in VOM 6.0 . 

RESOLUTION: Fixed the source code to treat overridden attributes as editable by default. 

 * INCIDENT NO:3458341	 TRACKING ID:3458350

SYMPTOM: When an add-on or VOM HF is uploaded in VOM an error message is displayed 
as "Applicable hosts are not present in domain. Hence removed.". 

DESCRIPTION: This message appears when there are no applicable hosts present in VOM 
domain for add-on/HF being uploaded. The message was appearing for some add-ons/HFs 
even if applicable hosts were present in VOM. This was happening with add-ons/HFs 
that were removed earlier in the past from VOM and same were uploaded later. 

RESOLUTION: A fix has been made to allow successful upload of add-on/HF when there 
are applicable hosts present in VOM even if it had been removed in the past. 

 * INCIDENT NO:3461060	 TRACKING ID:3461058

SYMPTOM: Unable to online disks from VOM UI on Windows hosts. 

DESCRIPTION: For raw disks, as disk name is appended with "(NO SIGNATURE)", we were 
not able to online/offline disks. 

RESOLUTION: Modified the command template to pass disk name in quotes. 

 * INCIDENT NO:3461444	 TRACKING ID:3461447

SYMPTOM: SORT connectivity cannot be tested from UI unless a proxy server is specified. 

DESCRIPTION: SORT connectivity cannot be tested in Management server setting unless you 
specify a proxy server. Due this, you can't test SORT connectivity from MS even if it 
may have direct access to SORT. 

RESOLUTION: Enabled the test connectivity option even if you don't enter a proxy server.
If proxy server and port are empty then MS will try direct connection to SORT 
and will display the result. 

 * INCIDENT NO:3462759	 TRACKING ID:3468903

SYMPTOM: After removing add-on from VOM it gets removed from repository, but it 
still keeps appearing VOM. 

DESCRIPTION: Since add-on keeps appearing in VOM even after removal, user will 
experience failures if any operation is performed on such add-on. 

RESOLUTION: The issue has been fixed so that add-on will not keep appearing in 
the VOM after performing successful remove operation. 

 * INCIDENT NO:3463744	 TRACKING ID:3463741

SYMPTOM: VOM 6.0 does not show any notifications for error on Windows Managed 
Host. 

DESCRIPTION: VOM 6.0 does not raise any alert notification like VEA when the 
Disk Group has all the disks in failed state on Windows. 

RESOLUTION: VOM 6.0 now listens to VEA alerts for Windows and shows then in VOM 
alerts and rules page. 

 * INCIDENT NO:3465454	 TRACKING ID:3465452

SYMPTOM: On Linux, SFM security daemon may not start/stop correctly 

DESCRIPTION: sfmsecdctrl command fails to start or stop the SFM security daemon 

RESOLUTION: Modified the command, sfmsecdctrl, to accommodate user tty settings 
for COLUMN size, when it is set to small for long output of the ps cli command. 

 * INCIDENT NO:3465831	 TRACKING ID:3461184

SYMPTOM: Failover History data gets deleted when HAD goes down on cluster node. 

DESCRIPTION: Whenever HAD goes down on a cluster node, all the Fail over History 
Data earlier reported for the cluster gets deleted. Once HAD starts again, the 
Fail over History Report will not show any fail over data prior to HAD start and 
only new fail over data will be shown. 

RESOLUTION: A fix has been made so as not to delete the historical data of 
Fail over History Report. Now we do not report any deletes for this data after 
HAD goes down. 
If data has already been deleted, it cannot be recovered with this fix. 

 * INCIDENT NO:3469021	 TRACKING ID:3469018

SYMPTOM: Unable to configure an ldap domain in VOM 

DESCRIPTION: While configuring an ldap domain in VOM, the ldap UI wizard does 
not complete and the last page is blank 

RESOLUTION: The issue was due to the base domain name entry not handling space in the 
name on windows. The entry is now enclosed in quotes and the wizard now completes 
successfully. 

 * INCIDENT NO:3485022	 TRACKING ID:3486327

SYMPTOM: An unknown user may access a VOM managed host on HP-UX using port 5634. 

DESCRIPTION: Entering an unknown user and no password into the password prompt dialog 
    using URL https://MH_NAME:5634 allows access. 

RESOLUTION: Properly check return arguments when querying for user names.


PATCH ID: vom-HF06000100

 * INCIDENT NO:3345216   TRACKING ID:3345210

SYMPTOM: vxlist runs slow and takes a long time to complete

DESCRIPTION: vxlist cli after sometime, does not return the o/p quickly if the managed host has 
luns from STK 6580 arrays assigned to it.

RESOLUTION: The vdid support for STK 6580 array was not present causing the dcli make vdid 
calls every time stat collection was run. 
This caused thread build up in the dclid process causing vxlist request to be 
serviced late. The support is added and now the issue is resolved.

 * INCIDENT NO:3362605   TRACKING ID:3424556

SYMPTOM: Statlog data files are too big.

DESCRIPTION: Space used by files in /var/opt/VRTSsfmh/stats is allocated too 
generously.  While these files are sparse, they are mapped into several 
processes and the extra size can put pressure on virtual memory.  Only 
large system configurations are indicated.

RESOLUTION: The issue is fixed by correcting the calculation for file size limits.

 * INCIDENT NO:3364450   TRACKING ID:3363058

SYMPTOM: After completion of scheduled firedrill, the firedrill service groups do not go 
offline even after offline flag is selected.

DESCRIPTION: In schedule firedrill wizard even after selection of offline firedrill group 
checkbox, the service group stay online.

RESOLUTION: The parsing logic was incorrect to check the value of the offline flag. Even 
after checking the offline checkbox, the value was treated as false instead of 
true.
Corrected the parsing logic to store the correct value of checkbox flag.

 * INCIDENT NO:3368041   TRACKING ID:3364402

SYMPTOM: Error while exporting data

DESCRIPTION: Navigate to Deployment details view under licenses perspective. 
View is grouped on "product" name by default. Change grouping to "Host" and try 
to export the data. It throws exception before applying this fix

RESOLUTION: Error was due to the incorrect ORDER BY clause in the SQL query. 
After changing the grouping, sort order was not formed correctly. Fixed the 
issue by setting sort order as ASC if nothing else is specified.

 * INCIDENT NO:3370322   TRACKING ID:3370321

SYMPTOM: Local file system shows multiple servers.

DESCRIPTION: For cloned Linux VMs, as the LV UUIDs were same for multiple VMs, we do see that 
the volumes tab as well as the file systems tab shows multiple hosts on VOM.

RESOLUTION: Issue is fixed by appending hostguid to LV UUID and VG UUID. This would eventually result into unique LV UUIDS for all the hosts.

 * INCIDENT NO:3373459   TRACKING ID:3373460

SYMPTOM: User cannot login to a Linux VOM central server

DESCRIPTION: Linux localhost PAM authentication fails

RESOLUTION: Add missing file /opt/VRTSsfmcs/sec/lib/libauthpamc_t.so

 * INCIDENT NO:3382649   TRACKING ID:3382647

SYMPTOM: VOM 6.0 Settings->Management Server page is not loading.

DESCRIPTION: Special characters in any of the fields in the settings page are causing the page not to load.

RESOLUTION: JSON object in the settings page was constructed without proper encoding.

 * INCIDENT NO:3385186   TRACKING ID:3385183

SYMPTOM: Disk group needs hostname column and operations authority.

DESCRIPTION: 1) When did search on a dg, there is no hostname column. This needs to be added.
2) When found a disk group, double click gave no authorization error.

RESOLUTION: Added hostname column to dg search. Also fixed authorization error, double click 
now takes the user to the dg details page.

 * INCIDENT NO:3385525   TRACKING ID:3323302

SYMPTOM: Validate User Group does not work if Active Directory allow Anonymous 
bind and DS ACL are used

DESCRIPTION: VxAT when validating a group, attempts anonymous bind even when 
Directory manager credentials are supplied, this may result in no group found as 
anonymous bind might only be able to query certain part of the directory or 
cannot query at all , this will not result in Error but returned value will be 
zero.

RESOLUTION: Changed AT to bind with credentials if Directory Manager Credentials 
are supplied rather than issuing anonymous bind. If no credentials are supplied 
then attempt to bind using anonymous bind.

 * INCIDENT NO:3393443   TRACKING ID:3396287

SYMPTOM: In VOM 6.0, when a path is lost for a disk on Windows, there is no alert 
notification in the VOM CMS.

DESCRIPTION: When a path is lost on Windows, VOM MH does not raise any alert for 
it, hence a user cannot create any rules on the alert.

RESOLUTION: VOM MH has been enhanced to raise alerts when a disk loses path on 
Windows. A user can now create rule on the same.

 * INCIDENT NO:3393519   TRACKING ID:3388217

SYMPTOM: Showing 'Total' instead of 'Raw' size in overview page waterfall chart for thin
pools.

DESCRIPTION: The label in the Thin pool storage summary chart shows Raw whereas the value is
actually Total. This applicable for thin pools across all array vendors. The
problem is observed in Enclosure and ThinPool overview.

RESOLUTION: Show label 'Total' instead of 'Raw' in Thin Pool Storage summary at Enclosure and
ThinPool overview.

 * INCIDENT NO:3393528   TRACKING ID:3388202

SYMPTOM: Showing label 'Thin Virtual Disk/Volume Count' instead of 'Virtual Disk Count'

DESCRIPTION: 'Thin' was being appended to the beginning of the label without checking the 
show_tp_tldev capability

RESOLUTION: - Check show_tp_tldev capability before deciding to append 'Thin' to Virtual
Volume Count.
- Applies to the thin pool grid and properties pop-up.

 * INCIDENT NO:3393825   TRACKING ID:3393824

SYMPTOM: VOM report violation for layered volume and does not report violation for subvolume.

DESCRIPTION: VOM Cross Enclosure Mirroring policy check was showing incorrect violations for 
layered volumes.

RESOLUTION: Modified the code to exclude layered volumes from Cross Enclosure Mirroring 
Policy check.

 * INCIDENT NO:3396404   TRACKING ID:3411771

SYMPTOM: VOM 6.0 shows a file system faulted for all systems in VMWare environment though 
it is full only on one system.

DESCRIPTION: Local OS file systems on local LVM shows multiple hosts on the VOM. Here for 
cloned Linux VMs, we do see that LV UUIDs are same for multiple VMs. Because of 
this VOM 6.0 shows file system as faulted for all hosts having same LV_UUID.

RESOLUTION: We rely on LV UUIDs to do the co-relation between LVM volumes and file systems. 
So as the LV UUIDs are same on multiple cloned Linux systems, the issue is fixed by 
adding hostguid to the LV UUIDs which would eventually result into unique LV 
UUIDS for all the hosts.

 * INCIDENT NO:3397462   TRACKING ID:3397461

SYMPTOM: Real time discovery was not getting triggered for remote group notifications.

DESCRIPTION: Real time notifications are fetched using hareg binary. hareg binary packaged 
with SFMH package has dependency on SUNWpool package for Solaris. SUNWpoolr 
package was missing so MH was listening to only group notification which 
resulted in delayed discovery.

RESOLUTION: The dependency of hareg binary is only on SUNWpool and not SUNWpoolr. Removed 
the check for SUNWpoolr package which is not present on Solaris 9.
We will now correctly listen to all notifications even if SUNWpoolr package is 
missing.

 * INCIDENT NO:3403690   TRACKING ID:3403696

SYMPTOM: The Suppress and Restore Fault pop-up is blank

DESCRIPTION: In the Settings view, when the user tries to run the Suppress/Restore Fault
operation from the Faults listing view, the pop-up that is launched is empty.

RESOLUTION: The security access check was incorrect, due to which a Null Pointer Exception was
being thrown on the server. Due to this the pop-up window was blank.
The security access check has been fixed now for both the Suppress and Restore
faults operations. This has resolved the issue.

 * INCIDENT NO:3404524   TRACKING ID:3404496

SYMPTOM: License lifecycle report and Demo License reports present in License perspective
show below exception when run.

DESCRIPTION: This issue occurs when user's browser locale is set to any language other than 
'English' or 'English - US'.  i.e if language is set to 'English - India'  or  
'English - Ireland' or other variants of English this issue may occur.

RESOLUTION: Fixed the code to work regardless of browser locale.

 * INCIDENT NO:3404595   TRACKING ID:3404695

SYMPTOM: Enabling SFHA download settings (under Settings -> SORT -> SFHA download settings) does not work.

DESCRIPTION: Enabling SFHA download settings does not work when Management Server has been is upgraded from version 5.0 to 6.0.

RESOLUTION: Added fix to save this setting when user enables these settings.

 * INCIDENT NO:3409720   TRACKING ID:3420991

SYMPTOM: On a Management Server with non English system locale,
Page at Settings -> SORT -> SFHA download settings is blank.

DESCRIPTION: On a Management Server with non English system locale,
When you open Settings -> SORT -> SFHA download settings in GUI the tab is blank.

RESOLUTION: Added fix to correctly parse the SFHA download schedule regardless of system
locale.


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.0 Managed Hosts as well as VOM 6.0 Management Server.

1. Download the file vom-6.0.0.0700.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.0.0.0700 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.0.0.0700 and select Install.
	- Select the 6.0 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 not supported.


SPECIAL INSTRUCTIONS
--------------------
 1. It requires approximately around 1 GB of disk space to upload vom-6.0.0.0700.sfa. Please ensure that Management Server has at least 1 GB of free disk space where CMS is installed.
 2. In the hf.log file, you would see a warning "Failed to update C:\Program Files\Veritas\VRTSsfmh\\bin\perl.exe: No such file or directory". Please ignore this warning. This would not have any functional impact.
 3. For raising SNMP traps first we have to configure SMTP mail server. Without configuring SMTP, SNMP traps will not be generated.
 4. Installation of this Hotfix using vomadm CLI on Windows is not supported.
 5. Please follow the below steps to install this Hotfix using vomadm on Unix setups:
	- Rename vom-6.0.0.0700.sfa to VRTSsfmh-6.0.0.0700.sfa
	- Provide the full path of the VRTSsfmh-6.0.0.0700.sfa in vomadm: 	/opt/VRTSsfmh/bin/vomadm hotfix --install <hf>
 6. This step is required only if InfiniBand is in the user's environment and unable to add host due to duplicate MAC address. 
    For Incident 3429719, after installing this Hotfix on Linux using vomadm as mentioned in Point 5, please follow the below instructions:
	- Remove .hostguid file located under /var/opt/VRTSsfmh.
	- Restart xprtld.
 7. This step is applicable for Windows 2008 SP2 MH, having locale as English-UK. Please refer ET# 3615772 for more details.
        - Rename vom-6.0.0.0700.sfa to vom-6.0.0.0700.tar.gz.
	- Extract tarball vom-6.0.0.0700.tar.gz.
	- Go to VRTSsfmh-6.0.0.0700\Windows\x64.
	- Extract tarball VRTSsfmh-6.0.0.0700.tar.gz.
	- Extract tarbal mh_diff.tar.gz.
	- Go to mh\lib\modules\VRTS.
	- copy OS.pm to C:\Program Files\Veritas\VRTSsfmh\lib\modules\VRTS\
 8. This step is required only for ET# 3599090. For Brocade switch configuration, if password contains single quotes ('),
    then Fabric addon(6.0.0.0300) is required.  

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


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

OTHERS
------
NONE