* * * READ ME * * *
                * * * Software Support Tools 6.0.1 * * *
                      * * * Patch 6.0.1.100 * * *
                         Patch Date: 2015-01-09


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
----------
Software Support Tools 6.0.1 Patch 6.0.1.100


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSspt


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec VirtualStore 6.0.1
   * Veritas Cluster Server 6.0.1
   * Veritas Dynamic Multi-Pathing 6.0.1
   * Veritas Storage Foundation 6.0.1
   * Veritas Storage Foundation Cluster File System HA 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation for Sybase ASE CE 6.0.1
   * Veritas Storage Foundation HA 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 151223-01
* 3009445 (3631185) On VRTSspt 6.0.5, the VRTSexplorer fails in Solaris 10 for SPARC platform 
after
applying the patch 119783-25.


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

Patch ID: 151223-01

* 3009445 (Tracking ID: 3631185)

SYMPTOM:
On Veritas Support Package (VRTSspt) 6.0.5, 
  After applying the patch 119783-25, Data Collector in VRTSspt is not able 
to
collect logs in Solaris 10 for SPARC.

DESCRIPTION:
There are two root causes for this problem:
The first one is the successful exit code of nslookup can be 0 or other
numbers, for example, 1,  but before adding the patch, it is always 0. Data
Collector only handles the exit code with 0.
The second one is the IPv4 address of remote Solaris host is not got first
before pinging it.

RESOLUTION:
For the first issue, the code is modified by handling more exit codes.
  For the second issue, the code is modified by obtaining a host's IPv4 
address
first before using it.



INSTALLING THE PATCH
--------------------
patchadd 151223-01


REMOVING THE PATCH
------------------
patchrm 151223-01


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


OTHERS
------
NONE