* * * READ ME * * *
                    * * * InfoScale U1_IE_7.4 * * *
                           * * * Patch * * *
                         Patch Date: 2023-05-08


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 U1_IE_7.4 Patch


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



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: U1_IE_7.4.1_1
* 3972341 (3972339) Need HA support for Alibaba Cloud IP and disk resources.
* 3977628 (4054733) The active node encounters a system crash with BugCheck 0x1E during a failover operation in a Microsoft failover cluster configuration.
* 3982225 (3981992) A potentially critical security vulnerability in VCS needs to be addressed.
* 3985560 (3985568) An AWS IP resource fails to come online when overlay IP is configured.
* 3992122 (3994609) Addition of Nutanix vdid library.
* 3996182 (3995685) Discrepancy in engine log messages of PR and DR site in GCO configuration.
* 3998131 (3969673) VVR replication fails to start and instead gets stuck in the Activating state in a NAT environment.
* 4006640 (4008147) IBM DB2 support on Windows
* 4009238 (4026952) On Infoscale 7.4.1 hosts attached to Hitachi G1500 storage, formatting a large volume caused a severe issue on the arrays.
* 4011864 (4011862) An import operation fails in a VMNSDg configuration because the operating system may fail to detect some of the disks being imported and therefore consider them as missing.
* 4014557 (4014554) Several "NoSlot" memory errors appear in the vxrlink extended output and VVR throughput decreases dramatically.
* 4016723 (4016720) If virtual server names are used for local or remote rlinks in a 3-way or a 4-way GCO configuration, the RVGPrimary resource fails when processing the additional secondaries.
* 4017145 (4017762) In case of a three-way or a four-way GCO configuration with Volume Replicator, during GCO switch or failover, the DiffSync operation fails on the secondary replication volume.
* 4017262 (4017261) After an RVGPrimary resource is switched in a GCO configuration, either the synchronization with the additional secondaries fails to start automatically or only a full synchronization takes place.
* 4028990 (4028986) Security vulnerabilities exist in some InfoScale binaries.
* 4028992 (4028986) Security vulnerabilities exist in some InfoScale binaries.
* 4063339 (4051631) Data corruption occurs in case of snapback operations that involve thin reclaimable disks.


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

Patch ID: U1_IE_7.4.1_1

* 3972341 (Tracking ID: 3972339)

SYMPTOM:
Need HA support for Alibaba Cloud IP and disk resources.

DESCRIPTION:
The InfoScale Availability and InfoScale Enterprise products should be able to support HA configurations for the IP and the disk resources in Alibaba Cloud.

RESOLUTION:
This patch provides two new agents, AlibabaIP and AlibabaDisk, to support HA conifgurations for the IP and Disk resources in Alibaba cloud.

FILE / VERSION:
Patch_7_4_10001_3972341.msp / -

* 3977628 (Tracking ID: 4054733)

SYMPTOM:
The active node encounters a system crash with BugCheck 0x1E during a failover operation in a Microsoft failover cluster configuration.

DESCRIPTION:
BugCheck 0x1E points to a division by zero error in one of the libraries.

RESOLUTION:
Fixed the issue in the library related to the EMC disks in which the error was encountered.

FILE / VERSION:
ddlprov.dll / 7.3.07010.0

* 3982225 (Tracking ID: 3981992)

SYMPTOM:
A potentially critical security vulnerability in VCS needs to be addressed.

DESCRIPTION:
A potentially critical security vulnerability in VCS needs to be addressed.

RESOLUTION:
This hotfix addresses the security vulnerability. For details, refer to the security advisory at: https://www.veritas.com/content/support/en_US/security/VTS19-003.html

* 3985560 (Tracking ID: 3985568)

SYMPTOM:
An AWS IP resource fails to come online when overlay IP is configured.

DESCRIPTION:
This issue occurs due to the use of a deprecated function an error in the command that is used to retrieve the status of the overlay IP during the monitor cycle.

RESOLUTION:
This hotfix addresses the issue by using the appropriate function and by fixing the error in the command that is used to retrieve the status of the overlay IP.

FILE / VERSION:
aws_functions.pl / 7.4.10003.0

* 3992122 (Tracking ID: 3994609)

SYMPTOM:
Addition of Nutanix vdid library.

DESCRIPTION:
Addition of Nutanix vdid library.

RESOLUTION:
Addition of Nutanix library.

FILE / VERSION:
ddlprov.dll / 7.4.10001.0
vdid_shr.dll / 7.4.10001.0
nutanix.dll / 7.4.10001.0

* 3996182 (Tracking ID: 3995685)

SYMPTOM:
A discrepancy was observed between the VCS engine log messages at the primary site and those at the DR site in a GCO configuration.

DESCRIPTION:
If a resource that was online at the primary site is taken offline outside VCS control, the VCS engine logs the messages related to the unexpected change in the state of the resource[, successful clean Entry Point execution and so on]. The messages clearly indicate that the resource is faulted. However, the VCS engine does not log any debugging error messages regarding the fault on the primary site, but instead logs them at the DR site. Consequently, there is a discrepancy in the engine log messages at the primary site and those at the DR site.

RESOLUTION:
The VCS engine module is updated to log the appropriate debugging error messages at the primary site when a resource goes into the Faulted state.

FILE / VERSION:
had.exe / 7.4.10004.0
hacf.exe / 7.4.10004.0
haconf.exe  / 7.4.10004.0

* 3998131 (Tracking ID: 3969673)

SYMPTOM:
VVR replication fails to start and instead gets stuck in the Activating state in a NAT environment.

DESCRIPTION:
In NAT mode, VVR uses the IP from which it receives heartbeats (usually the NAT routers) for heartbeating instead of the actual IPs on the rlink. A bug in code caused VVR to use the source port as the destination port, instead of the configured port (usually 4145) that it is supposed to use.

RESOLUTION:
This hotfix updates VVR so that it uses the correct configured port as the destination port.

FILE / VERSION:
vxio.sys / 7.3.07007.27

* 4006640 (Tracking ID: 4008147)

SYMPTOM:
InfoScale does not support HA configurations for IBM DB2 instances on Windows.

DESCRIPTION:
InfoScale does not support HA configurations for IBM DB2 instances on Windows.

RESOLUTION:
InfoScale products now support HA configurations for IBM DB2 instances on Windows.

NOTE: For details, refer to the technote at: https://www.veritas.com/support/en_US/doc/142076261-142117181-1-1.

FILE / VERSION:
DB2.dll / 7.4.10005
VxDB2Util.exe / 7.4.10005
DB2.xml

* 4009238 (Tracking ID: 4026952)

SYMPTOM:
On Infoscale 7.4.1 hosts attached to Hitachi G1500 storage, formatting a large volume caused a severe issue on the arrays.

DESCRIPTION:
During a format operation on a large volume attached to Infoscale 7.4.1 systems, the corresponding Hitachi G1500 array controllers become unresponsive. This issue occurs because VxIO sends several UNMAP/WRITE-SAME requests that are 1.3 GB in size, which the target storage fails to handle.

RESOLUTION:
This hotfix addresses the issue that occurs due to large-sized UNMAP commands issued by the VxIO module.

* 4011864 (Tracking ID: 4011862)

SYMPTOM:
An import operation fails in a VMNSDg configuration because the operating system may fail to detect some of the disks being imported and therefore consider them as missing.

DESCRIPTION:
During an import operation in a VMNSDg configuration, the operating system may sometimes fail to detect all the disks in the disk group. In such a scenario, the undetected disks or volumes are marked as missing or RAW, and the import operation fails.

RESOLUTION:
This hotfix provides the new DgImportWaitTimeOut attribute to address this issue. The default value of DgImportWaitTimeOut is 60 seconds. Before initiating the disk group import, the VMNSDg agent checks whether any disks are missing. If none of the disks are missing, it immediately proceeds with the import. If any disks are missing, it waits for 1 second and performs the check again. The agent repeats this process until all the disks in the group are available, or for the duration specified by DgImportWaitTimeOut, and then initiates the import.

FILE / VERSION:
VMNSDG.dll / 7.4.10006

* 4014557 (Tracking ID: 4014554)

SYMPTOM:
Several "NoSlot" memory errors appear in the vxrlink extended output and VVR throughput decreases dramatically.

DESCRIPTION:
When a replicated volume serves large workloads, several "No Slot" memory errors may appear in the VVR replication volume statistics. Eventually, VVR throughput decreases dramatically, indicating a need for additional memory slots to properly serve the workloads.

RESOLUTION:
This hotfix addresses the issue by allowing a larger number of memory slots to be configured on the secondary system so that large workloads can be properly served.

FILE / VERSION:
DriverCopy.bat / -
vvrcli_msgs.dll / 7.4.10006.0
vxio.sys / 7.4.10006.0
vxtune.exe / 7.4.10006.0

* 4016723 (Tracking ID: 4016720)

SYMPTOM:
If virtual server names are used for local or remote rlinks in a 3-way or a 4-way GCO configuration, the RVGPrimary resource fails when processing the additional secondaries. The following error is logged:
2020/08/26 14:36:31 VCS ERROR V-16-20027-25 (PRA03SMD) RVGPrimary:RVG_capvol5:diff_sync:Attaching secondary CAP_SAV_CAPVOL5.adam.adroot.edf.fr {163.81.173.69} failed with error code 2304 and message Error V-107-58644-1184: Invalid syntax

DESCRIPTION:
This issues occurs because the DiffSync.pl script cannot process the local_host and the remote_host values in the required format to execute vxrclient command.

RESOLUTION:
This patch updates the relevant Perl scripts to parse the local_host and the  remote_host values correctly while working with rlinks in a 3-way or a 4-way GCO configuration.

FILE / VERSION:
DiffSync.pl /-
Online.pl /-

* 4017145 (Tracking ID: 4017762)

SYMPTOM:
In case of a three-way or a four-way GCO configuration with Volume Replicator, during GCO switch or failover, the DiffSync operation fails on the secondary replication volume.

DESCRIPTION:
As a part of a three-way or a four-way way GCO configuration, during GCO switch or failover, the DiffSync operation gets triggered on the secondary replication volume. To enable DiffSync, the target volume needs to be online. The DiffSync operation fails because all the secondary replication volumes are offline by default.

RESOLUTION:
This hotfix resolves the issue by performing the online and the offline operations on the secondary replication volumes during the DiffSync operation.

FILE / VERSION:
vxrsync_msgs.dll / 7.4.10007
vxrserver / 7.4.10007

* 4017262 (Tracking ID: 4017261)

SYMPTOM:
After an RVGPrimary resource is switched in a GCO configuration, either the synchronization with the additional secondaries fails to start automatically or only a full synchronization takes place.

DESCRIPTION:
This issue occurs either because the diff_sync.pl script fails to work as expected, or because the module skips the difference-based synchronization of additional secondaries in favor of a full synchronization.

RESOLUTION:
This hotfix resolves the issue with the Perl script. Additionally, it provides a new attribute for the RVGPrimary agent, which lets you specify the type of synchronization to be done when the RVGPrimary agents comes online.

FILE / VERSION:
DiffSync.pl /-
Online.pl /-

* 4028990 (Tracking ID: 4028986)

SYMPTOM:
Security vulnerabilities exist in some InfoScale binaries.

DESCRIPTION:
Some security vulnerabilities are identified in some of the InfoScale binaries.

RESOLUTION:
This patch updates the vulnerable InfoScale binaries to improve security. For details about the vulnerability, refer to the following article: https://www.veritas.com/content/support/en_US/security/VTS20-014

* 4028992 (Tracking ID: 4028986)

SYMPTOM:
Security vulnerabilities exist in some InfoScale binaries.

DESCRIPTION:
Some security vulnerabilities are identified in some of the InfoScale binaries.

RESOLUTION:
This patch updates the vulnerable InfoScale binaries to improve security. For details about the vulnerability, refer to the following article: https://www.veritas.com/content/support/en_US/security/VTS20-014

* 4063339 (Tracking ID: 4051631)

SYMPTOM:
Data corruption occurs in case of snapback operations that involve thin reclaimable disks.

DESCRIPTION:
When the data integrity is checked after the snapback operation, the snapshot data does not match the data on the original volume. This issue occurs if the data on the original volume is edited or deleted after performing the snapback operation.

RESOLUTION:
The vxio module is updated to handle such a scenario so that the data corruption issue no longer occurs during a snapback operation.

FILE / VERSION:
vxio.sys / ="7.4.10011"



INSTALLING THE PATCH
--------------------
Download the executable file of this update to a temporary location on your system.


Each update includes the individual patches or hotfixes that contain enhancements and fixes related to reported issues.
See the "FIXED_INCIDENTS" section for details.


Before you begin
----------------
[1] Ensure that the logged-on user has privileges to install the update on all the systems.

[2] One or more patches or hotfixes that are included in this update may require a reboot. Before proceeding with the installation, ensure that the system can be rebooted.

[3] Veritas recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this update.

[4] Close the Windows Event Viewer before proceeding with the installation.


To install the update in the silent mode
----------------------------------------
[1] Double-click the update executable file to start its installation.

The installer performs the following tasks:
    - Extracts all the individual patch or hotfix executable files to the following location: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<PatchOrHotfixName>   "
    - Runs the preinstallation tasks
    - Installs all the patches or hotfixes sequentially
    - Runs the postinstallation tasks
The installation progress status is displayed in the command window.

[2] After all the patches of hotfixes are installed, the installer may prompt you to restart the system.
Type Y to restart the system immediately, or type N to restart the system later.

Note: The installer prompts for a system restart only if patches or hotfixes that require a reboot are included in the update and are installed. You must restart the system for such changes to take effect.


To install the update using the command line
--------------------------------------------
Use the VxHFBatchInstaller.exe utility to install the update from the command line.
The usage of this utility is as follows:
vxhfbatchinstaller.exe /Patch:<UpdateName>    [/PreInstallScript:<PreInstallScript.pl>   ] [/silent [/suppress]]
    - Replace <UpdateName>    is the executable file name without the platform, architecture, and .exe extension. For example, if the executable name is U1_IE_741_1_x64.exe, specify it as U1_IE_741_1.
    - PreInstallScript.pl is the Perl script that includes the preinstallation steps. These steps forcefully kill the required services and processes in case a graceful stop request does not succeed. Veritas recommends that you use this option and script only in case the installer fails repeatedly while performing the preinstallation tasks.
    - /silent indicates that the installation is run in a non-verbose mode; the installer does not prompt for any inputs during the installation.
    - /suppress indicates that the system is automatically restarted, if required, after the installation is complete.

Perform the following steps:

[1] From the command prompt, navigate to the directory where the executable file is located, and then run the file to extract the contents to a default location on the system.
The installer displays a list of patches or hotfixes that are included in the update. On 64-bit systems, those executable files are extracted to: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<UpdateName>   "

[2] In the same command window, run the following command to begin the installation in the silent mode:
vxhfbatchinstaller.exe /Patch:<UpdateName>    /silent
For example, to install an InfoScale 7.4.1 update on Windows Server 2019, the command is:
vxhfbatchinstaller.exe /Patch:U1_IE_741_1 /silent

The installer performs the following tasks:
    - Extracts all the individual hotfix executable files to the following location: "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName>   "
    - Runs the preinstall tasks
    - Installs all the hotfixes sequentially
    - Runs the postinstallation tasks
    - Displays the installation progress status in the command window

[3] After all the patches or hotfixes are installed, the installer prompts for a system restart only if some of them require a reboot. You must restart the system for such changes to take effect.
Note:If you specified the /suppress option in the previous step earlier, the installer automatically restarts the system. For example: vxhfbatchinstaller.exe /Patch:U1_IE_741_1 /silent /supress


REMOVING THE PATCH
------------------
For information on uninstalling a patch or hotfix, refer to the technote at: http://www.veritas.com/docs/000039693.


SPECIAL INSTRUCTIONS
--------------------
[+] To confirm the list of patches or hotfixes installed on a system, run the following command from the directory where the update files are extracted:
vxhfbatchinstaller.exe /list
This command displays a list of the patches and hotfixes that are installed as part of a update. It also displays the patches or hotfixes that are included in the update but are not installed on the system.

[+] To confirm the installation of the update, take one of the following actions:
    - Run the vxhf.exe /list command. This command lists the patches or hotfixes that are installed on the system.
    - In the Programs and Features window, click "View installed updates" to view the list of patches or hotfixes that are installed on the system.

[+] To confirm that the latest update is installed on a system, run the following command from the directory where the update files are extracted:
vxhfbatchinstaller.exe /patchlevel
This command displays the latest update that is installed, the status of the installation, and a list of all patches or hotfixes that are a part of the update but are not installed on the system.

[+] The update installer (vxhfbatchinstaller.exe) creates and stores logging information in the "%allusersprofile%\Veritas\VxHF\VxHFBatchInstaller.txt" file.

[+] The patch or hotfix installer (vxhf.exe) creates and stores logging information in the "%allusersprofile%\Veritas\VxHF\VxHF.txt" file.

[+] For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.veritas.com/docs/000039694

[+] To view a list of patches or hotfixes that are already installed on a system, refer to the technote at: http://www.veritas.com/docs/000039691.

[+] For information on uninstalling a patch or hotfix, refer to the technote at: http://www.veritas.com/docs/000039693.

[+] For general information about the update installer (VxHFBatchInstaller.exe), refer to the technote at: http://www.veritas.com/docs/000023795.


OTHERS
------
NONE