* * * READ ME * * *
                * * * Symantec Dynamic Multi-pathing for ESX 6.1 * * *
                        * * * Hot Fix 100 * * *
                         Patch Date: 2014-11-25


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
----------
Symantec Dynamic Multi-pathing for ESX 6.1 Hot Fix 100


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
ESX 5.0
ESX 5.1
ESX 5.5


PACKAGES AFFECTED BY THE PATCH
------------------------------
vxdmpmpp.vib


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Dynamic Multi-pathing for ESX 6.1



SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.1.0.100
* 3596401 (3581025) vDMP with VMware ESX5.0U1 and VMs (Microsoft Clustering) crashed while doing controller failover.
* 3596402 (3617423) [VDMP] ESX panic while running add/remove devices with no license installed on server.
* 3596400 (3509592) panic while freeing memory in dmp_group_stats() while browsing storage view and getting the statistics of selected the storage array


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

Patch ID: 6.1.0.100

* 3596401 (Tracking ID: 3581025)

SYMPTOM:
When the user installed VxDMP on a ESXi host and without adding a valid license key, added new storage array to the running system, the host encountered a PSOD.

DESCRIPTION:
When VxDMP detects a new storage array on a live system, it performs a license validation check. This check was making a reference to an uninitialized memory.

RESOLUTION:
The fix was to avoid the reference to the memory when the license validation check is done while addition of a new storage array.

* 3596402 (Tracking ID: 3617423) 
SYMPTOM:
When the customer was executing Cluster Validation test for Vmware, the server used to crash. When they execute the same test on a server without VDMP installed, the tests were succeeding.

DESCRIPTION:
In some cases, when DMP receives the SCSI command (PGR_OUT command ) in PSA context, DMP waits for it in the same context. This was causing system panic.
RESOLUTION:
Since DMP was waiting in PSA context, solution was to handoff the command to a separate thread and complete the execution as part of the same. 

* 3596400 (Tracking ID: 3509592)
SYMPTOM: Customer reported ESXi panics whenever they try to drill down on the I/O statistics in the DMP console.
DESCRIPTION: 
When the number of virtual machines on a path is more than the number of paths filtered for I/O statistics, the size of memory allocated is incorrect.

RESOLUTION:
DMP code checks for the specific condition and uses the max of the two values (number of virtual machine and number of paths) for allocating and freeing memory


INSTALLING THE PATCH
--------------------

1. Put the ESXi host into maintenance mode.

2. Login to the ESXi host, and remove the current VxDMP packages

	a. Symantec VxDMP CIM provider, VxDMP Array Support and VxDMP Plug-in

	   # esxcli software vib remove -n vxdmpprov -n vxaslapm -n vxdmpmpp

3. Install the new ESXi offline bundle using the --no-sig-check option.

# esxcli software vib install --depot=[Datastore]/VxDMP-6.1.000.001_ESXi_offline-bundle.zip --no-sig-check

4. Reboot the ESXI host, then verify that the VxDMP VIBs are installed.



REMOVING THE PATCH
------------------

1. Put the ESXi host into maintenance mode.

2. Login to the ESXi host, and remove the current VxDMP packages

	a. Symantec VxDMP CIM provider, VxDMP Array Support and VxDMP Plug-in

	   # esxcli software vib remove -n vxdmpprov -n vxaslapm -n vxdmpmpp


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


OTHERS
------
NONE