* * * READ ME * * *
              * * * Veritas Operations Manager 7.4.2 * * *
                         * * * Patch 200 * * *
                         Patch Date: 2020-10-22


This document provides the following information:

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


PATCH NAME
----------
Veritas Operations Manager 7.4.2 Patch 200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX
AIX 7.1
AIX 7.2
RHEL6 x86-64
RHEL7 x86-64
RHEL8 x86-64
SLES11 x86-64
SLES12 x86-64
SLES15 x86-64
Solaris 11 SPARC
Solaris 11 X86
Windows Server 2012 R2 X64
Windows 2016 X64
Windows 2019 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Operations Manager 7.4.2.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: vom-HF0742200
* 4017417 (4017414) Host family discovery fail due to json error in Task.pm
* 4017420 (4017419) VIOM Web Server does not start at the end of VIOM CMS patch upgrade.
* 4017423 (4017422) While adding VIOM Agent to VIOM CMS, getting error "Host is already part of the domain".
* 4017437 (4017435) Not able to generate email alert for VCS cluster down from Availability perspective.
* 4017442 (4017440) VIOM does report no valid SFHA license for version 5.1 on Windows servers.
* 4017453 (4017444) Tomcat upgrade to 9.0.37.0
* 4017461 (4017460) Product Enhancement - New reports for Veritas Volume Replicator.
* 4017472 (4017463) Product Enhancement: CLI to configure LDAP in VIOM.
Patch ID: vom-HF0742100
* 4009452 (4009454) Can not expand VVR volume on Windows InfoScale Node from VIOM GUI.
* 4009466 (4009463) MH patch install on Solaris 11 hosts does not unset the Veritas publisher.
* 4009469 (4009472) Some other fixes and security upgrades.
* 4009471 (4009470) VIOM patch shows Not installed though it is installed.
* 4009475 (4009474) Windows MH agent showing disconnected in VIOM even after refresh/reboot


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

Patch ID: vom-HF0742200

* 4017417 (Tracking ID: 4017414)

SYMPTOM:
json error in Task.pm is seen in log messages.

DESCRIPTION:
During Host family discovery on VIOM servers (CMS and Agents), you may see 'json error in Task.pm'.

RESOLUTION:
Fixed json error

* 4017420 (Tracking ID: 4017419)

SYMPTOM:
VIOM Web Server does not start at the end of VIOM CMS patch upgrade.

DESCRIPTION:
If customer's own certificate is being used for VIOM web server and the keystore password is different from the default 'changeit', then you may see that VIOM web server is not getting started at the end of VIOM patch upgrade.

RESOLUTION:
Taking backup of server.xml and restoring it after patch upgrade.

* 4017423 (Tracking ID: 4017422)

SYMPTOM:
You may see this issue on Linux Virtual Machines where VMs are cloned.

DESCRIPTION:
While adding VIOM Agent (Linux VM) to VIOM CMS, getting error "Host is already part of the domain".

RESOLUTION:
Created a unique ID for cloned Linux VMs based.

* 4017437 (Tracking ID: 4017435)

SYMPTOM:
You are not receiving email alert for VCS cluster down if rule is created under Availability perspective.

DESCRIPTION:
You are not receiving email alert for VCS cluster down if rule is created under Availability perspective.

RESOLUTION:
Added support for sending email alert from Availability perspective for VCS cluster down.

* 4017442 (Tracking ID: 4017440)

SYMPTOM:
VIOM GUI shows no valid license fault for SFHA 5.1

DESCRIPTION:
VIOM was not able to detect the SFHA 5.1 license key on Windows.

RESOLUTION:
Detected the license key,

* 4017453 (Tracking ID: 4017444)

SYMPTOM:
Tomcat vulnerabilities reported.

DESCRIPTION:
Tomcat upgrade to 9.0.37.0

RESOLUTION:
Upgraded tomcat version.

* 4017461 (Tracking ID: 4017460)

SYMPTOM:
N/A

DESCRIPTION:
VIOM does now have three new reports related to VVR in Server perspective.
- VVR replication data status
- Data Replication Status-Weekly
- Data Replication Status-Monthly

Details on new VVR reports are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.200

RESOLUTION:
N/A

* 4017472 (Tracking ID: 4017463)

SYMPTOM:
N/A

DESCRIPTION:
New CLI to allow VIOM user to -
- Configure LDAP
- Assign permissions
- Unconfigure LDAP
- Change bind user password for already configured LDAP. 
Details on how to use LDAP CLI are available in technote https://www.veritas.com/support/en_US/doc/viom_technote_7.4.2.200

RESOLUTION:
N/A

Patch ID: vom-HF0742100

* 4009452 (Tracking ID: 4009454)

SYMPTOM:
"Resize Volume" operation fails for VVR volume, for windows MH.

DESCRIPTION:
VIOM GUI operation "Resize Volume" fails on Windows InfoScale Node when try to resize VVR volume.

RESOLUTION:
Removed the decimal from VVR volume size and round off.

* 4009466 (Tracking ID: 4009463)

SYMPTOM:
After VIOM patch install on Solaris Agents, 'pkg publisher' command shows Veritas publisher.

DESCRIPTION:
After VIOM patch install on Solaris Agents, 'pkg publisher' command shows Veritas publisher. This publisher should be removed after patch install.

RESOLUTION:
Unsetting publisher once patch is installed.

* 4009469 (Tracking ID: 4009472)

SYMPTOM:
N/A

DESCRIPTION:
- Java upgrade - Upgrade JAVA version to 1.8.0.252.

- Tomcat upgrade - Upgrade apache tomcat to 9.0.35 as mitigation to CVE-2020-9484 vulnerability.

- SmartIO related fixes 
  1) Cache state update in GUI.
  2) Impact Analysis Chart fix.
  3) Can not create multiple cache on same disk

- VCS Service Group related fixes 
  1) Not able to create link for Service group dependency 
  2) GUI shows firedrill task in RUNNING.

- xprtld service getting timed out after reboot because of slow network service start.

- vomsc status/start/stop command throwing error message.

- Policy signature scan report is giving exception when signature is registered.

- Storage Migration Solution fixes
  1) Multiple volume migration tasks not able to schedule in single operations using migrate by host method.
  2) Not able to do Volume Migration using Migrate Volume by Host method

RESOLUTION:
Fixed above all mentioned issues.

* 4009471 (Tracking ID: 4009470)

SYMPTOM:
In Deployment, the patch shows as Not Installed though it is successfully installed.

DESCRIPTION:
Sometimes, you may see that VIOM patch installation is successful but when checking in Deployment, the patch shows as Not Installed and hence unable to apply the patch to other MH hosts.

RESOLUTION:
Handled the Json exception.

* 4009475 (Tracking ID: 4009474)

SYMPTOM:
Sometimes after Windows MH agent reboot, host can be seen in disconnected state in  Settings->Host.

DESCRIPTION:
You can see agent in disconnected state if host has Microsoft Failover Cluster Virtual Adapter.

RESOLUTION:
Skipping the Microsoft Failover Cluster Virtual Adapter from the host GUID.



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


1. Download the file vom-7.4.2.200.sfa
2. Launch a browser and login to the VIOM management server.
3. Navigate to Settings ->                         Deployment Icon.
4. Upload the Hotfix to the VIOM CMS using the Upload Solutions button.
   The Hotfix vom-7.4.2.200 should be visible in the Hot Fixes tree node.
5. Please install this Hotfix on CS using the following instructions:
    - Go to Settings ->                       Deployment ->                      Hot Fixes ->                        Veritas Infoscale Operations Manager Managed Host.
    - Click on Hot Fixes Tab. Click on Applicable Hosts Tab.
    - Right click on CS Name and click on Install.


REMOVING THE PATCH
------------------
Un-installation and rollback of this Hotfix is supported only on Solaris 11 and AIX platforms.


SPECIAL INSTRUCTIONS
--------------------
Known Incidents:
 
SDSCPE-39
xprtld process needs to start manually if we failover the "SFM_Services" group to passive node in VIOM CMS HA setup
SDSCPE-547
Disk will not remove from dg after performing volume migration from VIOM GUI.
SDSCPE-546
For storage provisioning, task is getting stuck in submitted state from VIOM GUI.
SDSCPE-536
Cannot perform VVR operation on secondary site, when disk group is created under CVM.


OTHERS
------
NONE