* * * READ ME * * *
                       * * * InfoScale 8.0 * * *
                         * * * Patch 1400 * * *
                         Patch Date: 2022-04-13


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
   * KNOWN ISSUES


PATCH NAME
----------
InfoScale 8.0 Patch 1400


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 11 SPARC


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSamf
VRTSaslapm
VRTScps
VRTSllt
VRTSperl
VRTSvcs
VRTSvxfen
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 8.0
   * InfoScale Enterprise 8.0
   * InfoScale Foundation 8.0
   * InfoScale Storage 8.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: -8.0.0.1600
* 4057420 (4060462) Nidmap information is not cleared after a node leaves, resulting in add node failure subsequently.
* 4062799 (4064208) Node failed to join the existing cluster after bits are upgraded to a newer version.
* 4065841 (4065495) Add support for DELL EMC PowerStore.
* 4066221 (4056449) Vxconfigd fails to start on some nodes after a full upgrade with CVR/VVR on the primary site.
* 4066330 (4060176) Remove multiple VxVM(vxdmp/vxio/vxspec) modules support on Solaris 11.4
* 4068407 (4068404) ASL request for HPE 3PAR/Primera/Alletra 9000 ALUA support.
* 4069303 (4070613) On a Solaris system, if the SFCFS cluster is upgraded to InfoScale 8.0 by using the ABE method; the CVM protocol version does not increment automatically.
Patch ID: -5.34.0.1
* 4069608 (4069607) Security vulnerability detected on VRTSperl 5.34.0.0 released with Infoscale 8.0.
Patch ID: -8.0.0.1200
* 4066225 (4056666) The Error writing to database message may intermittently appear in syslogs on CP servers.
Patch ID: VRTSvxfen-8.0.0.1200
* 3951882 (4004248) vxfend generates core sometimes during vxfen race in CPS based fencing configuration
Patch ID: VRTSllt-8.0.0.1200
* 4066063 (4066062) Node panic is observed while using llt udp with multiport enabled.
* 4066667 (4040261) During LLT configuration, if set-verbose is set to 1 in /etc/llttab, an lltconfig core dump is observed.
* 4063186 (4066719) Remove multiple AMF module support on Solaris 11.4
* 4065820 (4065819) Protocol version upgrade failed.


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

Patch ID: -8.0.0.1600

* 4057420 (Tracking ID: 4060462)

SYMPTOM:
System is unresponsive while adding new nodes.

DESCRIPTION:
After a node is removed, and adding node with  different node name is attempted; system turns
unresponsive. When a node leaves a cluster, in-memory information related to the node is not cleared due to the race condition.

RESOLUTION:
Fixed race condition to clear in-memory information of the node that leaves the cluster.

* 4062799 (Tracking ID: 4064208)

SYMPTOM:
Node is unresponsive while it gets added to the cluster.

DESCRIPTION:
While a node joins the cluster, if bits on the node are upgraded; size
of the object is interpreted incorrectly. Issue is observed when number of objects is higher and on
InfoScale 7.3.1 and above.

RESOLUTION:
Correct sizes are calculated for the data received from the master node.

* 4065841 (Tracking ID: 4065495)

SYMPTOM:
This is new array and we need to add support for EMC PowerStore.

DESCRIPTION:
EMC PowerStore is new array and current ASL doesn't support it. So it will not be claimed with current ASL. This array support has been now added in the current ASL.

RESOLUTION:
Code changes to support EMC PowerStore have been done.

* 4066221 (Tracking ID: 4056449)

SYMPTOM:
vxdmp/vxio/vxspec driver fails to load as Add_drv cmd reports a busy error.  As a result, vxconfigd fails to start.

DESCRIPTION:
vxconfigd fails to start as indicated by the following logs

Starting vxdmp ......................................................................................................................... Done
    Starting vxio .......................................................................................................................... Done
    Starting vxspec ........................................................................................................................ Done
    Starting vxconfigd ................................................................................................................... Failed
    Starting vxloggerd ................................................................................................................... Failed
    Starting vxvollogd ..................................................................................................................... Done
    Starting vxesd ...................................................................................................................... Skipped
    Starting vxrelocd ................................................................................................................... Skipped
    Starting vxcached ................................................................................................................... Skipped
    Starting vxconfigbackupd ............................................................................................................ Skipped
    Starting vxattachd .................................................................................................................. Skipped
    Starting vvr ........................................................................................................................ Skipped

RESOLUTION:
Code changes introduced to handle add_drv cmd errors.

* 4066330 (Tracking ID: 4060176)

SYMPTOM:
InfoScale stack upgrade issues observed on Solaris 11.4

DESCRIPTION:
Multiple issues observed during upgrade of InfoScale stack. This is because of separate VxVM modules for 11.3 and 11.4 (and above).

RESOLUTION:
VxVM now provides single module for Solaris 11.4 (and above). Support for Solaris 11.3 is now removed.

* 4068407 (Tracking ID: 4068404)

SYMPTOM:
We need to add support to claim ALUA Disks on HPE 3PAR/Primera/Alletra 9000 arrays.

DESCRIPTION:
Current ASL doesn't support HPE 3PAR/Primera/Alletra 9000 ALUA array type. This ALUA array support has been now added in the current ASL.

RESOLUTION:
Code changes to support HPE 3PAR/Primera/Alletra 9000 ALUA array have been done.

* 4069303 (Tracking ID: 4070613)

SYMPTOM:
On a Solaris system, if the SFCFS cluster is upgraded to InfoScale 8.0 by using the ABE method; the CVM protocol version does not increment automatically.

DESCRIPTION:
On a Solaris system, if the SFCFS cluster is upgraded to InfoScale 8.0 by using the ABE method; the CVM protocol version does not increment automatically.

RESOLUTION:
1. Run the following command on the Solaris system after you upgrade to InfoScale 8.0 - vxdctl protocolversion
Review the CVM protocol version.

2. Run the following command to upgrade to the latest verison - vxdctl upgrade

Patch ID: -5.34.0.1

* 4069608 (Tracking ID: 4069607)

SYMPTOM:
Security vulnerability detected on VRTSperl 5.34.0.0 released with Infoscale 8.0.

DESCRIPTION:
Security vulnerability detected in the Net::Netmask module.

RESOLUTION:
Upgraded Net::Netmask module and re-created VRTSperl 5.34.0.1 version to fix the vulnerability .

Patch ID: -8.0.0.1200

* 4066225 (Tracking ID: 4056666)

SYMPTOM:
The Error writing to database message may appear in syslogs intermittently on InfoScale CP servers.

DESCRIPTION:
Typically, when a coordination point server (CP server) is shared among multiple InfoScale clusters, the following messages may intermittently appear in syslogs:
CPS CRITICAL V-97-1400-501 Error writing to database! :database is locked.
These messages appear in the context of the CP server protocol handshake between the clients and the server.

RESOLUTION:
The CP server is updated so that, in addition to its other database write operations, all the ones for the CP server protocol handshake action are also synchronized.

Patch ID: VRTSvxfen-8.0.0.1200

* 3951882 (Tracking ID: 4004248)

SYMPTOM:
vxfend process segfaults and coredumped

DESCRIPTION:
During fencing race, sometimes vxfend crashes and generates core dump

RESOLUTION:
Vxfend internally uses fork and exec to execute sub tasks. The new child process was using same file descriptors for logging purpose. This simultaneous read of same file using single file descriptor was resulting incorrect read and hence the process crash and coredump. This fix creates new file descriptor for child process to fix the crash

Patch ID: VRTSllt-8.0.0.1200

* 4066063 (Tracking ID: 4066062)

SYMPTOM:
Node panic

DESCRIPTION:
Node panic observed in llt udp multiport configuration with vx ioship stack.

RESOLUTION:
When llt receives an acknowledgement, it tries to free the packet and corresponding client frags blindly without checking the client status. If the client is unregistered, then the free functions of the frags will be invalid and hence should not be called.

* 4066667 (Tracking ID: 4040261)

SYMPTOM:
During LLT configuration, if set-verbose is set to 1 in /etc/llttab, an lltconfig core dump is observed.

DESCRIPTION:
Some log messages may have IDs like 00000. When such logs are encountered, it may lead to a core dump by the lltconfig process.

RESOLUTION:
VCS is updated to use appropriate message IDs for logs so that such issues do not occur.

* 4063186 (Tracking ID: 4066719)

SYMPTOM:
InfoScale stack upgrade issues observed on Solaris 11.4

DESCRIPTION:
InfoScale stack upgrade showed multiple issues due to separate AMF modules for 11.3, 11.4, and later versions.

RESOLUTION:
AMF now provides single module for Solaris 11.4 and later version. Support for Solaris 11.3 is now removed.

* 4065820 (Tracking ID: 4065819)

SYMPTOM:
Protocol version upgrade from Access Appliance 7.4.3.200 to 8.0 failed.

DESCRIPTION:
During rolling upgrade, IPM message 'MSG_CLUSTER_VERSION_UPDATE' is generated and as a part of it we do  some validations for bumping up protocol. If validation succeeds then a broadcast message to bump up the cluster protocol is sent and immediately we send success message to haclus. Thus, the success message is sent before processing the actual updating Protocol version broadcast message. This process occurs for very short period. Also, after successful processing of the broadcast message, the Protocol version is properly updated in config files as well as command shows correct value.

RESOLUTION:
Instead of immediately returning success message, haclus CLI waits till upgrade is implemented on broadcast channel and then success message is sent.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch infoscale-sol11_sparc-Patch-8.0.0.1400.tar.gz to /tmp
2. Untar infoscale-sol11_sparc-Patch-8.0.0.1400.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/infoscale-sol11_sparc-Patch-8.0.0.1400.tar.gz
    # tar xf /tmp/infoscale-sol11_sparc-Patch-8.0.0.1400.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSinfoscale800P1400 [<host1> <host2>...]

You can also install this patch together with 8.0 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 8.0 directory and invoke the installer script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installer -patch_path [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
Manual installation is not recommended.


REMOVING THE PATCH
------------------
Manual uninstallation is not recommended.


KNOWN ISSUES
------------
* Tracking ID: 4069684

SYMPTOM: If an Infoscale system has a private/local diskgroup which is not a part of any VCS service group;
VxIO and VXDMP driver might not stop during a full upgrade.

Performing InfoScale Enterprise prestop tasks
        Stopping vxspec ........................................................................................ Done
        Stopping vxio   ........................................................................................ Partially Done
        Stopping vxdmp  ........................................................................................ Partially Done
        Stopping CollectorService .............................................................................. Done
        Performing InfoScale Enterprise poststop tasks ......................................................... Done

Veritas InfoScale Enterprise Shutdown did not complete successfully

vxio failed to stop on orat8-2-01-ldom1
vxdmp failed to stop on orat8-2-01-ldom1

It is recommended to reboot the systems orat8-2-01-ldom1 to resolve the failures and then retry.
If the issues persist after reboot, contact our technical support or refer to installation guide for
further troubleshooting.
Do you want to continue? [y,n,q] (n)

WORKAROUND: Before a full upgrade, deport all diskgroups which are not under VCS control.



SPECIAL INSTRUCTIONS
--------------------
Veritas recommends using the latest CPI patch with -require option for any deployment-related operations.


OTHERS
------
NONE