Patch-ID# 121070-02

NOTE:
***********************************************************************
READ THE TERMS OF THE AGREEMENT ("AGREEMENT") IN THE LEGAL_LICENSE.TXT
FILE CAREFULLY BEFORE USING THIS SOFTWARE. BY USING THE SOFTWARE, YOU
AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE
TERMS, PROMPTLY DESTROY THE UNUSED SOFTWARE.
***********************************************************************

Keywords: esm enterprise storage manager advanced applications
Synopsis: Sun StorEdge ESM 4.0 Advanced Applications Patch (Extension)
Date: Feb/07/2006


Install Requirements: None                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: StorEdge ESM Advanced Applications

Unbundled Release: 4.0

Xref: 

Topic: 

Relevant Architectures: sparc
NOTE:
This patch does not address or correct issues pertaining to a 
standard SVR4 package.  Therefore:
  1)  This patch is NOT installed via /usr/sbin/patchadd nor 
      removed via /usr/sbin/patchrm.
  2)  This patch will NOT be reflected in the Solaris patch 
      database or in /var/sadm/patch.
  3)  This patch will NOT be searchable or traceable via 
      /usr/bin/showrev.
Complete installation instructions are found below.


NOTE:
**
** this patch is meant for the extension hosts only.  not for the manager.
**

BugId's fixed with this patch: 

Changes incorporated in this version: 

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch: 

APPQcime.ZIP
README.121070-02

Problem Description:

Issues corrected in this patch --
 
400021 Network mounted file scans will no longer fail on Windows hosts
Problem: File SRM scans on Windows network drives fail. Because of this, network drives were hidden from the scan configuration dialog.
Symptom: Firstly, network drives are not visible in the scan scheduler UI.
Secondly, even if they are enabled in UI and selected for scan, the scan would fail. The returned Berkeley database would be empty and no scan data would be available for that drive.
Solution: The solution provided is to make connections to the UNC path of the network drive rather than the drive letter. This grants us access to the top-leve
directory for the drive. However, accessing subdirectories would still fail with access denied errors.
 
400022 Solaris Agent will no longer halt if some password encryption techniques
are used
Problem: Our CIM Extension on Solaris 9 hosts with MD5 password encryption will crash when contacted by the management server during discovery
Symptom: Solaris hosts with MD5 password encryption cannot be discovered or managed.
Solution: The Solaris authentication code was fix so it can handle non-default encryption algorithms
 
400024 Eliminate rare/random Solaris CIM Extension halt condition
Problem: The Solaris CIM Extension can stop running.  This occurred once at the co-location site and was probably due to configuration changes that were being made while the agent was running.
Symptom: The Solaris CIM Extension stops running.
Solution: The fix is to test all return codes from these operations before continuing.
 
400025 VCS volumes will now show if there are CIFS or Sharity mount points
Problem: When CIFS or Sharity devices are on the host, VxFS devices are not reported
Symptom: No VxFS devices are reported.
Solution: The fix is simply to continue if the parse for NFS mounts fails, since CIFS is unrelated to NFS.
 
400026 Added detail to File scan log messages
Problem: File SRM scans can report errors such as 'No Such File or Directory' or 'Protection Error' in its logs. However, the logs do not specify the file or directory that is reporting the error.
Symptom: Scan failure messages in the Scan Status UI page and XGather.log on the agent showing no additional information except the error that actually occurred in such cases.
Solution: When an error occurs during a scan, the log message will now include the full path of the directory or file we are attempting to scan.
 
400027 File scans will no longer abort after the first error
Problem: When an error such as 'File or Directory does not exist' or 'Protection error' is detected, file scans abort. This makes scanning network shares especially problematic.
Symptom: File scans fail, and scan failure messages appear in the Scan Status UI page and XGather.log on the file server.
Solution: In the event of such error conditions we skip the scan of that particular file or directory , log the error message and to continue scan from the next file or directory.
 
400029 NFS mount point with DNS name will no longer fail VxVM volume discovery
Problem: If a UNIX host has an NFS mount point, whose share name specified as 'fully_qualified_domain_name:/mountpoint', the CIM Extension will skip all the Veritas volumes.
Symptom: In these cases volume capacity is shown as zero even after data collection completes.
Solution: When a logical volume has a name containing a fully-qualified domain name, ProviderUtils.isIPAddress was  expecting a number. An exception would be thrown This was not handled properly. This required changes to the isIPAddress() method of  'ProviderUtils.java' class.
 
400036 VxVM parsing should now work on non-English locales
Problem: VxVM parsing does not work on Unix hosts running in non-English locales.
Symptom: External disks can show up as local.
Solution: We now explicitly set the locale to POSIX before starting up the CIM Extensions. This causes the VxVM commands that are used to return English output, which can be successfully parsed.
 
400037 Agents in Zulu time should no longer cause NullPointerException
Problem: Our CxWS date-time routine throws a NullPointerException when called in Zulu time (GMT without Daylight Savings).
Symptom: File SRM collections and test collections fail.
Solution: The fix is to detect this case and return the correct DateFormat object instead of a null.
 
Issues correct in previous versions of this patch --

Patch Installation Instructions:
----------------------------- 
1) Execute /etc/init.d/appqcime stop
2) Unzip the file APPQcime.ZIP in a tmp directory.
3) Copy the contents of the reloc/APPQcime directory over to the existing APPQcime directory, located in /opt/APPQcime
4) Execute /etc/init.d/appqcime start

Special Install Instructions:
--------------
None

README -- Last modified date:  Tuesday, February 7, 2006

