* * * READ ME * * *
                  * * * Veritas I/O Fencing 7.3 * * *
                         * * * Patch 200 * * *
                         Patch Date: 2017-10-05


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 I/O Fencing 7.3 Patch 200


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxfen


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.3.0.200
* 3931023 (3864470) The I/O fencing configuration script exits after a limited number of retries.


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

Patch ID: 7.3.0.200

* 3931023 (Tracking ID: 3864470)

SYMPTOM:
When the I/O fencing startup script starts, it tries to configure fencing. The
startup script exits if it there is any error in configuring the VxFEN module.

DESCRIPTION:
Any errors while trying to configuring VxFEN causes I/O fencing startup script
to exit the retry operation after a specific number of tries. If the errors get
resolved after the startup script has exited, you need to manually start the I/O
fencing program.

RESOLUTION:
When the I/O fencing program starts the vxfen init script waits indefinitely for
vxfenconfig utility to configure VxFEN module.



INSTALLING THE PATCH
--------------------
Perform the following steps on each cluster node, one node at a time:
1. Stop VCS:
# /opt/VRTSvcs/bin/hastop -local -force
2. Stop vxfen:
# /etc/init.d/vxfen stop
3. Apply the patch:
# rpm -Uvh VRTSvxfen-7.3.0.200-RHEL6.x86_64.rpm
4. Start vxfen:
# /etc/init.d/vxfen start
5. Start VCS:
# /opt/VRTSvcs/bin/hastart


REMOVING THE PATCH
------------------
Perform the following steps on each cluster node, one node at a time:
1. Stop VCS:
# /opt/VRTSvcs/bin/hastop -local -force
2. Stop vxfen:
# /etc/init.d/vxfen stop
3. Uninstall VRTSvxfen package:
# rpm -ev VRTSvxfen
4. Install previous version of VRTSvxfen package.
5. Start vxfen:
# /etc/init.d/vxfen start
6. Start VCS:
# /opt/VRTSvcs/bin/hastart


SPECIAL INSTRUCTIONS
--------------------
To make sure all the file permission related changes are reflected in the patch, delete all the old VxFEN log files and directories before installing the new VxFEN patch.


OTHERS
------
NONE