* * * READ ME * * *
                 * * * Veritas Resiliency Platform Hot Fix 5 (3.3.2.5) * * *                         
                         Hotfix Date: 2019-05-21


This document provides the following information:

   * HOTFIX NAME
   * APPLIANCES SUPPORTED BY THE HOTFIX
   * BASE PRODUCT VERSION FOR THE HOTFIX
   * SUMMARY OF ISSUES FIXED BY THE HOTFIX
   * DETAILS OF ISSUES FIXED BY THE HOTFIX
   * INSTALLING THE HOTFIX
   * KNOWN ISSUES
   * NOTE


HOTFIX NAME
----------
Veritas Resiliency Platform Hotfix 3.3.2.5

APPLIANCES SUPPORTED BY THE HOTFIX
----------------------------------------
Infrastructure Management Server

BASE PRODUCT VERSION FOR THE HOTFIX
-----------------------------------
Veritas Resiliency Platform 3.3.2


SUMMARY OF ISSUES FIXED BY THE HOTFIX
---------------------------------------
Hotfix 3.3.2.5:
* STESC-2592 (VRP-23764) - Create port fails in rehearsal as VMWare IP is not discoverd
* STESC-2561 (VRP-23747) - Discovery of datastore cluster within folder
* STESC-2991 (VRP-23768) - IMS cannot connect to NBU master
* STESC-2871 (VRP-23986) - IP customization failes with error message: "IP customization failed for [1 - 0] macs." 
* STESC-2697 (VRP-24079) - Cluster are not getting discover in RM after upgrade.	

DETAILS OF ISSUES FIXED BY THE HOTFIX
--------------------------------------------
This hotfix fixes the following JIRA issues:

* STESC-2592 (Fix Tracking ID - VRP-23764)

SYMPTOM: Create port fails in rehearsal as VMWare IP is not discoverd

DESCRIPTION: The link between the nic and ip is missing as nic is not getting discovered. 
This is because the macAddress of the VM is in upper case. 

RESOLUTION: Changed the case of mac address to uppercase. 
This ensures that all checks for NIC & MAC happens at same case which resolves the issue.

* STESC-2561 (Fix Tracking ID - VRP-23747)

SYMPTOM: Discovery of datastore cluster within folder

DESCRIPTION: RG creation fails if the data store cluster is under a folder. 
We are expecting datastore cluster under the datacenter and operation will fail in case there is a folder between both.

RESOLUTION: Code changes have been done to discover datastore clusters within folder.
While getting given named datastore cluster reference, traverse all the folders inside datastorefolder underneath DC.

* STESC-2991 (Fix Tracking ID - VRP-23768)

SYMPTOM: IMS cannot connect to NBU master

DESCRIPTION: NBU license shipped with VRP was expired in March 2019.
Without valid license VRP was unable to communicate with NBU as the connection request was rejected.

RESOLUTION: Updated the license which is used by VRP to communicate with NBU master.

* STESC-2871 (Fix Tracking ID - VRP-23986)

SYMPTOM: IP customization failes with error message: "IP customization failed for [1 - 0] macs." 

DESCRIPTION: IP customization does not work without UAC being disabled. Push of IP customization agent fails without UAC being disabled.
Even when the IP customization is installed manually, IP customization task fails of rehearal/ migrate workflow fails as VRP tries to do forceful install again.

RESOLUTION: Skip the IP customization agent installation if the agent is already installed on the VM.

* STESC-2697 (Fix Tracking ID - VRP-24079)

SYMPTOM: Cluster are not getting discover in RM after upgrade.

DESCRIPTION: Policy discovery is done for VMWare Cluster version later than 6.0U2 (Build number 3620759). The latest patch on top of 6.0 have build number 8 digit long instead of 7 digit long.
The build number was getting checked as string instead of number.

RESOLUTION: Fixed the logic to check the build version as a number instead of string value.

INSTALLING THE HOTFIX
--------------------
  1. Contact Veritas Technical Support for this hotfix and check if the hotfix is relevant to issue seen in your environment.
  2. Download the hotfix and copy it to any server having access to VRP appliances.
  3. Extract the downloaded tar ball. Hotfix files for all applicable components will be extracted into the patches directory.
  4. Make sure there is no operation in progress while the hotfix is being applied.
  5. Perform the following steps to upload the hotfix on each of the applicable components.
    a) Open the SFTP session from clish
	   utilities> sftp-session start put hotfix
	b) Provide the password for this temporary SFTP session
	c) Open SFTP session using the above created user information and upload the corresponding hotfix file for this component.
  6. Perform the following steps to install the hotfix
    a) Verify that the hotfix is uploaded from clish
	   hotfix> list-available-hotfixes
	b) Apply the hotfix from clish
	   hotfix> apply-hotfix 3.3.2.5
  7. Verify hotfix is applied successfully from clish
     hotfix> list-applied-hotfixes
  8. Close the SFTP session opened earlier
     utilities> sftp-session stop
  9. Repeat the steps 5 to 8 on all applicable components. The hotfix functionality can fail if even one component is skipped. 
    
    

KNOWN ISSUES
-----------
None

NOTE
----
 a)Make sure that hotfix 3.3.2.1 is installed before installing this hotfix. 
 b)Rollback of hotfix is not supported.