* * * READ ME * * *
             * * * Veritas Low Latency Transport 7.2 * * *
                         * * * Patch 400 * * *
                         Patch Date: 2017-10-06


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
----------
Veritas Low Latency Transport 7.2 Patch 400


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
SLES12 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSllt


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas InfoScale Storage 7.2
   * Veritas InfoScale Availability 7.2
   * Veritas InfoScale Enterprise 7.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.2.0.400
* 3923939 (3922320) Kernel panics in case of FSS with LLT over RDMA during heavy data transfer.


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

Patch ID: 7.2.0.400

* 3923939 (Tracking ID: 3922320)

SYMPTOM:
Kernel panics in case of FSS with LLT over RDMA during heavy data transfer.

DESCRIPTION:
In case of FSS using LLT over RDMA, sometimes kernel may panic because of an issue in the 
buffer advertisement logic of RDMA buffers. The case arises when the buffer advertisement for 
a particular RDMA buffer reaches the sender LLT node earlier than the hardware ACK comes to 
LLT.

RESOLUTION:
LLT module is modified to fix the panic by using a different temporary queue for such buffers.



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 llt-sles12_x86_64-Patch-7.2.0.400.tar.gz to /tmp
2. Untar llt-sles12_x86_64-Patch-7.2.0.400.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/llt-sles12_x86_64-Patch-7.2.0.400.tar.gz
    # tar xf /tmp/llt-sles12_x86_64-Patch-7.2.0.400.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSllt720P400 [<host1> <host2>...]

You can also install this patch together with 7.2 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 7.2 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:
--------------------------
-----------------------------------------------------------
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 VRTSllt-7.2.0.400-SLES12.x86_64.tar.gz to /tmp
2. Untar VRTSllt-7.2.0.400-SLES12.x86_64.tar.gz to /tmp/hf

    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/VRTSllt-7.2.0.400-SLES12.x86_64.tar.gz
    # tar xf /tmp/VRTSllt-7.2.0.400-SLES12.x86_64.tar
3. Install the patch(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd 
    /tmp/hf
    # ./installVRTSllt720P400 [<host1>    <host2>   ...]

You can also install this patch together with 7.2 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 7.2 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:
--------------------------
Perform the following steps on the node on which this patch is being applied:
1. Take backup of your configurations
2. Stop VCS
3. Install the patch
4. Restart VCS on the node

Stopping VCS on the cluster node:
--------------------------------

1. Ensure that the /opt/VRTSvcs/bin directory is included in your PATH
   environment variable so that you can execute all the VCS commands. Refer
   to Veritas Cluster Server Installation Guide for more information.

2. Freeze all the service groups persistently.
        # haconf -makerw
        # hagrp -freeze [group] -persistent

3. If the cluster is writable, you may close the configuration before stopping the cluster.
    Stop the cluster on this node:
        # haconf -dump -makero

   run the following command:
        # hastop -local -force

   Verify that the cluster is stopped by running the ha command:
    # hasys -state

   make sure that both had and hashadow processes are stopped. Also, stop the VCS CmdServer:
    # CmdServer -stop

4. Stop the cluster services in order:
    - For AMF:
    # systemctl stop amf
    - For VxFEN:
    # systemctl stop vxfen
    - For GAB:
    # systemctl stop gab
    - For LLT
    # systemctl stop llt

Note: Stop any other services depending on GAB


Installing the Patch
--------------------

1. Un-compress the downloaded patch and change the directory to the uncompressed patch location.
   Install the patch using the following command:

    # rpm -Uvh VRTSllt-7.2.0.400-SLES12.x86_64.rpm

2. Run the following command to verify if the new patch has been installed:

        # rpm -q VRTSllt

   If the proper patch is installed, the following output is displayed:

        VRTSllt-7.2.0.400-SLES12.x86_64


Re-starting the cluster services:
--------------------------------

1. To start the cluster services in order run the following command:
        - For LLT:
        # systemctl start llt
        - For GAB:
        # systemctl start gab
        - For VxFEN:
        # systemctl start vxfen
        - For AMF:
        # systemctl start amf
        - For VCS:
        # hastart
        # /opt/VRTSvcs/bin/CmdServer

2. Make VCS cluster writable:
        # haconf -makerw

3. Unfreeze all the groups:
        # hagrp -unfreeze [group] -persistent
        # haconf -dump -makero


REMOVING THE PATCH
------------------
Removal of the patch will result in removing the whole package from the system/node. To go back to a previous installed version of the package, you may need to re-install the package. Run the following steps on the node where the patch is being uninstalled:

To remove the patch from a cluster node:
---------------------------------------------
1. Freeze all the service groups persistently.
        # haconf -makerw
        # hagrp -freeze [group] -persistent

2. Stop VCS on the node by running the following command:
    - Follow the stop sequence as mentioned in the PATCH INSTALLATION section.

3. Remove the patch by using the following command:
    - For LLT:
        # rpm -e VRTSllt --nodeps

4. Verify that the patch has been removed from the system:
        - For LLT:
        # rpm -qa|grep VRTSllt

   Ensure that the package is not displayed. This confirms that the package is removed.

5. Install the relevant package from the VCS base media.
    Also refer to SORT for any applicable patches.

6. To start the cluster service, run the following command first on one node:
    - Follow the start sequence as mentioned in the PATCH INSTALLATION section.

7. Unfreeze all the groups.
        # hagrp -unfreeze [group] -persistent
        # haconf -dump -makero


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE