* * * READ ME * * *
                  * * * InfoScale Enterprise 7.4 * * *
                           * * * Patch * * *
                         Patch Date: 2018-07-23


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
----------
InfoScale Enterprise 7.4 Patch


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows 2012 X64
Windows Server 2012 R2 X64
Windows 2016 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.4
   * InfoScale Enterprise 7.4


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: Patch_7_4_00001_3953402
* 3953402 (3953405) The VMwareDisks agent now supports IPv6 configuration.


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

Patch ID: Patch_7_4_00001_3953402

* 3953402 (Tracking ID: 3953405)

SYMPTOM:
The VMwareDisks agent fails to bring the configured VMware disk online when an IPv6 address is mentioned in its configuration.

DESCRIPTION:
If the IPv6 address of an ESXi or a vCenter server is mentioned in the resource configuration of a VMware disk, the corresponding VMwareDisks resource goes into the UNKNOWN state. This issue occurs because the VMwareDisks agent fails to parse the IPv6 address format.

RESOLUTION:
This hotfix updates the VMwareDisks agent to also support IPv6 addresses in its resource configuration. The existing support for IPv4 addresses and host names continues as is. Note that the IPv6 addresses must be specified in square brackets []; for example:
VMwareDisks vmdk_res (
   ESXDetails = { "[2620:128:f0a2:900d::150]" = "root=GMIsMUlSKsNSlSLuJUo" }
   HAInfoDetails =  { "[2001::15]" = "Administrator@IAG=JPLvPXoVNvQVo" }
   DiskPaths = {"6000C295-b352-d76e-c590-f696c58bd277:[datastore1] New Virtual Machine/New Virtual Machine_3.vmdk" = "0:1" }
)

FILE / VERSION:
VMwarelib.dll / 7.4.00001.290
VMwareDisks.dll / 7.4.00001.290



INSTALLING THE PATCH
--------------------
This package contains self-extracting files that are specific to the processor architecture and operating system version.
Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or the CLI. Instructions for both these options are provided below.


To install the hotfix on server systems using the GUI
-------------------------------------------------------------------------
1. Double-click the hotfix executable file to extract its contents to a default location on the cluster node.
By default, the files are extracted to:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates"

The Hotfix Installer Wizard is automatically launched after the files are extracted.

2. Click "Next" on the Welcome screen. 
The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to begin the hotfix installation. 
The status of each installation task is updated as it completes.

4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.

5. If this is a clustered configuration (VCS or MSCS), perform steps 1-4 on all the other nodes in the cluster.


To install the hotfix on server systems using the CLI
------------------------------------------------------------------------
1. Navigate to the following location at the command prompt:
"C:\temp"

2. Run one of the following commands to extract the hotfix files to the default location:
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /x
or
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /extract

3. Navigate to the default location where the hotfix files are extracted.
By default, the files are extracted to:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

4. Run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber>  /silent
Here, <Hotfix_BuildVersion_IncidentNumber> is the name of the hotfix file excluding the OS, platform, and .exe extension.

5. To complete the hotfix installation, follow the instructions that are displayed at the command prompt.

6. If this is a clustered configuration (VCS or MSCS), perform steps 1-5 on all the other nodes in the cluster.


REMOVING THE PATCH
------------------
Additional Notes
------------------------
- To confirm the installation of a hotfix, run the following command:
vxhf.exe /list

On server systems, vxhf.exe is located at:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

The output of this command lists the hotfixes installed on a system.

- The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF"

- For general information about the hotfix installer (vxhf.exe), refer to the following technote:
https://www.veritas.com/support/en_US/article.TECH73446

- To view a list of hotfixes already installed on a system, refer to the steps mentioned in the following technote: 
https://www.veritas.com/support/en_US/article.TECH73438

- For information on uninstalling a hotfix, refer to the steps mentioned in the following technote: 
https://www.veritas.com/support/en_US/article.TECH73443


SPECIAL INSTRUCTIONS
--------------------
DISCLAIMER: This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Veritas disclaims all liability relating to or arising out of this fix. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into an InfoScale for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Veritas Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available if you sign up for notifications from the Veritas support site http://www.veritas.com/support and/or from Services Operations Readiness Tools (SORT) http://sort.veritas.com.


OTHERS
------
NONE