Patch-ID# 122122-01

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 storagetek operations manager
Synopsis: Sun StorageTek Operations Manager 4.1 Manager Patch
Date: May/04/2006


Install Requirements: None                      
                      
Solaris Release: 9 10

SunOS Release: 5.9 5.10

Unbundled Product: Sun StorageTek Operations Manager

Unbundled Release: 4.1

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.

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: 

README.122122-01
SP_4_2_0_1A.bin

Problem Description:

Issues corrected in this patch --
 
420001	Inability to delete 3.x storage system
Problem: After upgrading pre-4.0 databases storage element delete will result in error.
Symptom: After upgrading pre 4.0 databases storage element delete will yield java.sql.SQLException: ORA-02292: integrity constraint (APPIQ_SYSTEM.CARD_CONTAINER_ID_FK) violated - child record found.
Solution: Created sql script SP1DBChanges.sql to clean up the orphan records and fix the card containership. This script is run during installation of this service pack, and during upgrade to future releases.
 
 
420002	Inability to view configuration/reports after deleting user who scheduled report
Problem: Deleting a user breaks Configuration | Reports . The underlying problem is that when a user is deleted, schedules that were created by the user are not updated to reflect the deletion.
Symptom: 1. Create a user and log in as that user 2. Schedule a report for delivery 3. Log in as admin, and delete the user created in step 1 4. Try to go to Configuration | Reports. You will see an error like: " Cannot find data model with id:com.appiq.toolkit.security.impl.UserImpl:1001" 
Solution: There are 2 parts to the solution: 1. A script is run as part of installation of this service pack and upgrade to delete any scheduled tasks owned by deleted users.  2. All user deletion is now trapped and their scheduled tasks are now deleted.
 
 
420003	Inability to restore position of unmanaged elements with WWN of all digits
Problem: For unmanaged elements, System Explorer saves their positions by using their WWN.  When retrieving information from the database, System Explorer mistakely treats the WWN of all digits as an element ID.  This causes the position of corresponding elements to not be restored.
Symptom:  Users can not restore the positions for the unmanaged elements that have the WWN of all digits
Solution:  When System Explorer gets a saved WWN of all digits, first search all managed elements to see if there is a match.  If no matching element exists, the WWN will be used to retrive the unmanaged elements.
Note that WWNs contain 16 characters, which effectively makes these values impossible to be considered element IDs. Element IDs are numbers that increment by 1.
 
 
 
420004	Failure in chargeback of currency validation for some currencies
Problem: User input validation fails for Asian currency symbols.
Symptom: When Asian currency symbols such as the Yen symbol are entered in Chargeback, a JavaScript error message appears informing the user that the currency symbol is invalid.
Solution: There are 2 different Unicode representations/code points for most Asian currencies. For example, there is both a full-width Yen sign and half-width Yen sign. Java always returns full-width Yen; however, the previous validation was done against the half-width Yen sign, thus it failed.
The fix introduced in the code covers validation for both code points. We now validate against a list containing full-width currency symbols obtained from Java and the half-width symbols we had previously supported. 
 
 
420005	Inability to display element topology if there are unmounted paths
Problem: Element Topology only displays mounted external (form mount point to storage system) paths. Unmounted external paths are not displayed.
Symptom: User can not see external, unmounted paths in Element Topology.
Solution: Display the external paths for an unfiltered and unmounted path.
 
 
420006	Inability to discover NetBackup on Linux
Problem: NetBackup discovery on Linux fails
Symptom: Backup details could not be collected for Linux Hosts.
Solution: The solution is to remove DOS end-of-line characters from the scripts. This change is made in cimiq.xml after copying the files to the agent directory under cimiq_dist. A special ant tag removes all the EOL characters from all the files in the directory. 
 
 
420007	Support for Brocade 48000 and 200E
Problem: Brocade 48000 switches did not accurately report the number of ports.
Symptom: There were errors in the sync process and the topology was not be correct for models: 48000 4100 200E 2000 3016 4012 3014 4020 7420.
Solution: Brocade 48000 is now added to the list of supported director switches to get the port information correctly.  Director switches calculate ports differently than other Brocade switches because director switches have multiple port modules. Support has also been added for displaying the model property for Brocade switches listed above.
 
 
420008	Support for multiple Sun 35xx arrays on a single DotHill provider
Problem: Fixing replication of multiple Sun 3510 arrays that are managed by single Dot Hill SMI-S provider. Also, handling the port deviceId field, which the SMI-S provider was supplying in an unexpected format.
Symptom: There were replication errors when multiple arrays were managed by the same provider / server. 
There were also array configurations that could cause the SMI-S provider to supply deviceId in unexpected format.  This resulted in missing ports and host security group information on the navigation page and incorrect topology. 
Solution: Usage of port property DeviceID is totally removed. 
The multiple array errors were happening because of incorrect caching. Caching has been fixed to resolve this error.
 
 
420009  Host data not collected by SIM (HP SIM integrated only)
Problem: With the integration of the HP-SIM and the HP-SE products, the initial discovery of a Host device that can be monitored by both HP-SIM and HP-SE (the CIM Extensions are present) can result in a condition whereby the HP-SIM fails to successfully collect data from that host.  This fix will allow the users to successfully gather host data from either HP-SIM or HP-Se
Symptom: When a host has been discovered that can be managed by both HP-SIM and HP-SE, the scheduled data collections to that host performed by HP-SIM will fail.  The user will receive a notification that the data collection event was aborted for a general reason.  The users will not see the expected host data within the HP-SIM reporting structure.
Solution: The code was changed such that when HP-SE is populating host information back into HP-SIM it correctly provides all expected data.  HP-SIM is expecting a piece of string data that HP-SE was supplying as a null value.  By providing a non-null value to HP-SIM along with the host data, HP-SIM is able to correctly process the device and the ability for HP-SIM to collect data from that host is not affected.
 
420010  HP-SIM does not know when SE discovery is complete (HP SIM integrated only)
Problem:  With the integration of the HP-SIM and the HP-SE products, there is a case where devices discovered within HP-SIM may not successfully be added to a discovery task within HP-SE.  When HP-SIM is able to successfully identify a device, or at least able to ping a device, the device IP address information and credential information to the HP-SE product for it to perform a Step 1 discovery step.  Prior to sending this information to HP-SE, the HP-SIM product via the connector, checks to ensure that HP-SE is not currently running a discovery operation.  If a discovery operation is occurring, the HP-SIM product will hold onto the newly discovered device information until such time as it determines HP-SE has completed its discovery steps.
When HP-SIM checks to see if HP-SE is doing a discovery operation, it is only looking to see if the Step 1 (Discovery Setup) discovery is running.  If a new device or set of devices is discovered within HP-SIM when HP-SE is in some other discovery set, such as Step 2 Topology or Step 3 Details, HP-SIM will incorrectly determine that HP-SE is not doing a discovery operation, and will hand over the information for the devices that HP-SIM just discovered.  HP-SE will accept the information from HP-SIM, but it will not run a Step 1 Discovery Setup step against the devices.
Symptom: The users will see devices that have been discovered within the HP-SIM product, but have not been also discovered by HP-SE.  There is no visual feedback to indicate that something has not worked correctly.  The users must re-identify the devices in HP-SIM when HP-SE is not in a discovery step 
Solution: The code was changed such that the call made by HP-SIM to find out if HP-SE is currently in a running a discovery task will now check for all possible HP-SE discovery states.  HP-SIM will hold off on sending new discovery information if HP-SIM detects that HP-SE is in either a Step 1 Discovery Setup, Step 2 Topology or Step 3 Details discovery operation.  Once HP-SIM is able to adequately determine that HP-SE is not performing any discovery operations, HP-SIM will hand over the new discovery information, and instigate a Step 1 Discovery Setup discovery step in HP-SE.
 
 
420011	System Explorer slow to open in large NAS configurations
Problem: In a system with many NetApp shares, starting System Explorer can take an extremely long time.
Symptom: In a system with many NetApp shares, starting System Explorer can take hours. 
Solution: The calculation of host dependencies on NetApp servers has been optimized. It had been extremely inefficient.
 
 
420012	Volume creation on CV/EVA 5.0 fails
Problem: Attempts to create a Storage Volume on an EVA system managed by CommandView 5.0 will fail.
Symptom: Storage Volume creation would fail.
Solution: We now properly escape the CIM object path for the configuration service as per RFC 2396. We had been using java.net.URLEncoder.encode, which escapes spaces as plus signs rather than ?%20? as per the RFC. (Cf http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4616184)
 
 
420013	Create Host Security Group can fail on CV/EVA 5.0 if the proxy provider had 	previously managed a second storage array
Problem: If you attempt to create or edit a Host Security Group on an EVA system managed by CommandView 5.0, you may get errors if the CommandView host also managed other EVA systems.
Symptom: Host Security Group creation or modification would fail. Error code 4 (generic failure) would be returned by the EVA provider.
Solution: Until now, we were checking to see if a given WWN was known to a provider by making an EnumerateInstances call and checking the WWN against the StorageID property of CIM_StorageHardwareID.  This works in the case of embedded providers, but it breaks down in the case of a proxy provider managing multiple arrays because a given initiator WWN will have separate instances for each of the arrays it is known by.  Instead of the EnumerateInstances call, we are now making an AssociatorNames call from the StorageSystem to the StorageHardwareIDManagementService and then an Associators call to the StorageHardwareIDs.
 
 
420014	We do not get Windows serial numbers
Problem: The product does not show Serial Numbers for windows hosts. This is important for asset tracking.
Symptom: UI and reports (host properties and chargeback) do not show the serial number for windows hosts.
Solution: An association associating physical package with computer system was missing. Added the association class and provider for windows hosts.
 
 
420015	Storage systems discovered with generic SMI-S have replication errors forCIM_ProtocolControllerForPort
Problem: Storage systems that are discovered with the generic SMI-S infrastructure do not show the mapping to front end ports for HSGs.
Symptom: Replication errors for class CIM_ProtocolControllerForPort occur during a GAED.
Solution: Because the CIM_ProtocolControllerForPort association requires a ClassMap to help the mapper connect the front end ports to the protocol controller instances, we use a replication bean to set the ClassMap appropriately depending on whether the FC Port instance is a front-end or back-end port..
 
 
420016	Error discovering SQL Server after installing Windows security pack
Problem: SQL Server database applications can not be discovered from Windows management servers that have certain Microsoft security patches installed.
Symptom: Discovering SQL Server application gives "ORA-12154: TNS:could not resolve service name".
Solution: Forced ODBC connections to use TCP/IP instead of named pipes by modifying the registry key for ODBC connection Network Library.  The default transport was changed by Microsoft in several of their security patches.
 
 
420017	File SRM fails with very long directory names
Problem: If a very long directory path is scanned on a Windows File Server, the scan process will terminate silently
Symptom: Scanning network drives from a Windows File Server that has paths > 260 characters will terminate the scan. Storage Essentials will not receive the scan results, and will display an asterisk next to the network drive.
Solution: We expanded the directory buffer used to 1024 characters to create a UNC path. Note that Windows MAX_PATH value is only 260 characters. However, some network drives, such as those mounted on NetApp servers, can support longer paths.  We also changed the code that gets the Windows SID (Security ID) to handle the long paths as well. 
 
 
420018	Tru64 CIM Extensions crash if no HBA API Library
Problem: The Tru64 CIM Extensions that shipped with R4.2 do not work with the HBA API Library that currently ships with Tru64.
Symptom: On startup of the Tru64 CIM Extension, the following error will appear: java.lang.UnsatisfiedLinkError: dlopen: Cannot map library libhbaapi.so.  After that, the CIM Extension will stop running.
Solution: We rebuilt the CIM Extension to work with the latest HBA API library. 
The CIM Extensions now require either the V5.1B-2 or V5.1B-3 Tru64 patches.
 
 
420020  CV/EVA 5.0: Removing a Volume From HSGs
Problem: On an EVA accessed through CommandView 5.0, if you remove a volume from one Host Security Group, it will display in the UI as if it is not in any Host Security Groups.
Symptom: When you use CommandView 5.0 to manage an EVA and remove a storage volume from a Host Security Group, all other Host Security Groups will report that the volume is not a member as well.
Neither CommandView nor the EVA are adversely affected. StorageEssentials just reports incorrect information. The next Get All Elements Details request will correct the problem.
Solution:  The replication code was replicating the wrong CIM class. It was replicating CIM_PROTOCOLCONTROLLERFORUNIT, but should have replicated HPEVA_ProtocolControllerForVolume. This is now fixed.
 
 
Issues correct in previous versions of this patch --

Patch Installation Instructions:
-----------------------------
1) Execute /etc/init.d/appstormanager stop
2) Navigate to the directory where you unzipped this patch, and execute 122122-01/SP_4_2_0_1A.bin
3) Follow the resulting on-screen patch installation instructions.
4) Execute /etc/init.d/appstormanager start
 
Special Installation Notes:
 
************************************************************
NOTE: Installing this Patch will overwrite the jboss.properties.
If you have modified jboss.properties, you must first make a copy 
of the old one, and then restore it after this Patch installation.
************************************************************ 
 
Either the "-i silent" or "-i console" switch may be used if needed.
 
Version Notes:
Navigate to the directory where the Sun StorageTek Operations Manager is installed.
The file Version.txt contains the version string for the product.
        Base version string: 4.2.0.0
        After patching: 4.2.0.n  (where "n" is the revision number of the patch)

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

None.

README -- Last modified date:  Thursday, May 4, 2006

