vrp-centos69_x86_64-Patch-3.3.2.2

 Basic information
Release type: Patch
Release date: 2019-06-07
OS update support: None
Technote: None
Documentation: None
Popularity: 190 viewed    downloaded
Download size: 31.48 MB
Checksum: 1974807897

 Applies to one or more of the following products:
Resiliency Platform 3.3.2 On CentOS 6.9 x86-64

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

 Fixes the following incidents:
3979293

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
                 * * * Veritas Resiliency Platform Hot Fix 2 (3.3.2.2) * * *                         
                         Hotfix Date: 2019-06-3


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

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.2:
* STESC-2532 (VRP-23481) - vxtap IO hang when doing memory performance testing on CentOS 7.4
* VRP-23460 - IOTAP Package Installation failed if boot and root on seprate partition on SLES platform

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

* STESC-2532 (Fix Tracking ID - VRP-23481)

SYMPTOM: vxtap IO hang when doing memory performance testing on CentOS 7.4. The same behavior is observed on other versions of RedHat and SUSE as well.

DESCRIPTION: CentOS VM hangs when stress testing is performed on the VM. The VM works fine with same stress testing without the vxtap driver.

RESOLUTION: When stress testing is performed the memory consumption of the OS increases to such high level that vxtap does not get enough needed memory and used to go into sleep while trying to replicate the IO being processed.
Fix involves temporarily pausing the replication when vxtap detects that the available memory is beyond a threshold value. When enough memory is available replication processing resumes.

* VRP-23460

SYMPTOM: Installation of IOTAP addon fails on SLES platform

DESCRIPTION: IOTAP Package Installation failed if boot and root on seprate partition on SLES platform.

RESOLUTION: Handled the configuration of separate boot and root partition as part of installation.

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.2
  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. 
  10. Login to RM and go to Settings -> Updates -> Managed Hosts and launch Upgrade Hosts for all the affected Hosts
    
    

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.