OBSOLETE Patch-ID# 118985-06
Keywords: esm enterprise storage manager advanced applications
Synopsis: Obsoleted by: 118985-07 Sun StorEdge ESM 3.0.1 Advanced Applications Patch
Date: Jun/02/2005


Install Requirements: None                      
                      
Solaris Release: 8 9

SunOS Release: 5.8 5.9

Unbundled Product: StorEdge ESM Advanced Applications

Unbundled Release: 3.0.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.118985-06
SP_3_6_1_6.bin

Problem Description:

Issues corrected in this patch --
9890 - AppIQ Trap MIB and Trap Generation Code Fix
Problem: The software generates traps based on events from the Event Manager.  These traps are defined in a MIB file called AppIQ-Traps.MIB.  The traps that are generated cannot properly be decoded by some trap receivers because not all of the defined fields in the traps are being populated.
Symptom: Trap receivers do not show any of the trap details.
Solution:  The code was modified to populate all of the remaining field.
 
10008 - McDATA SWAPI Provider remote process dies
Problem: The McDATA SWAPI Provider starts up a remote process for each EFCM it needs to communicate with.  On a Solaris Server with dual NICs communicating to an EFCM on a Solaris server with dual NICs, the remote process dies during provisioning operations.
Symptom: Whenever a provisioning operation is attempted on McDATA switches, the operation fails and the user gets a dialog box that states that the Zone Service could not be found because the fabric is not valid.
Solution: The solution involves converting a SWAPIexception into a CIMException.  This conversion was not being done correctly, and the remote process could not handle the resulting exception and died.
As part of the fix for this problem, additional logging was put into the application to receive error messages from the remote process and log them in the cimom.log to more easily detect and fix any remote process errors in the future.
 
10389 - Report Cache Refresh Fails
Problem: Report Cache Refresh fails or takes long time.
Symptom: Report Cache Refresh will not complete successfully.The temp tablespace will grow very large and hit 32 GB OS file limit. The Report refresh will fail with an error 'unable to extend temp segement' or start seeing process out of memory error.
Solution: Tuned various views which were creating a problem due to sorting.  This controls the temp space growth by removing the sort and speed up the report refresh time. Modified the reinit.pl script to run this fix  during schema reinitialization.
 
 
Issues corrected in prior verions of patch --
9937 - Event flood during statistics collection
Problem:  Numerous similar events being generated due to errors while collecting statistical data from a device. This would clean up the event manager and facilitate troubleshooting.
Symptom: When a collector is running to collect statistical data, if a specific collection attempt fails, say due to an unreachable device, then a series of events show up in the event manager showing the same failure.
Solution: The solution to this issue was to trap any exception that was thrown during data collection and not create and send an event to the event service. Earlier we were creating a new event every time a data collection error/exception occurred.
 
6391 - McData zoning UI - differentiate between active and inactive zones
Problem: The zoning database for McDATA is kept on the EFCM server rather than on the individual switches.  When a zone set is activated in a McDATA fabric, the EFCM keeps a copy of the zone set, zones, and zone members in the inactive zone database.  This creates confusion in the UI since it is not easy to tell which zones are active and inactive and causes problems during provisioning.
Symptom: In the zone list for a McDATA switch, some zones will be listed twice.  One is the active zone and one is an inactive copy.  There is no way to tell which is which without clicking on each zone one at a time to look at the zone details page.  In addition, if the inactive zone is edited, the two zones can have different contents but still have the same name.
Solution: The Zones table in the Navigation and Provisioning will have an additional read only column that will show if a zone is active or not. The add/edit zones to a zone set wizard in provisioning was modified such that the names of the active zones are followed by the text (Active).  Note that active zones were already filtered IF there is an inactive zone with the same name.
 
9864 - McData SWAPI throttle
Problem: The McDATA SWAPI connection to the EFCM can send SWAPI requests faster than EFCM can handle them.  This can cause SWAPI errors, leading to repeated disconnect and reconnect events.  The result is incomplete or erroneous syncs and failed provisioning operations.
Sympton: The Event Manager will show multiple SWAPI disconnect and SWAPI reconnect events.  Provisioning operations will fail with error messages stating that the zone service on the fabric is invalid.
Solution: Introduce a throttle on the SWAPI traffic.  A new property in jboss.properties will be added, called cimom.mcData.swapiThrottle.  This property is the time in milliseconds that the application will delay between the completion of one SWAPI call and the start of the next SWAPI call.  Value range is 0-1000 milliseconds; default of 200.  The McDATA SWAPI provider will use this value to pause between each SWAPI call.  This pause will be independent for each EFCM connection.  The throttle will ensure that EFCM has time to process all SWAPI calls without getting overloaded.
 
9648 - Handle Clariion LUNs greater than 999
Problem: Clariion LUNs greater then 999 are missing after running Get All Element Details
Symptom: Navigation pages for Clariion storage systems do not show any LUNs greater then 999
Solution: Clariion LUN information is obtained by parsing NaviCLI output using regular expressions.  Before this fix, the regular expression for LUN number would accept only one-, two-, or three-digit numbers.  The regular expression was modified to accept any number of digits.
 
9255 - JVM upgrade
Problem: Several bugs are caused by having the 1.4.1 version of the Java virtual machine (JVM) installed with StorageAuthority.  These bugs are fixed in version 1.4.2_05 and later of the JVM.
Symptom: On Solaris the StorageAuthority server will restart during synchronization.  Memory leaks cause the JVM and therefore the StorageAuthority server to crash.  Other miscellaneous JVM bugs.
Solution: The solution is to upgrade to version 1.4.2 of the JVM on both Windows and Solaris.  We will be using 1.4.2_06 on Windows and 1.4.2_07 on Solaris.
 
9913 - CNT fabric ISL problem
Problem: When a CNT FC9000 switch is not the primary switch in a fabric, the SnmpSwitch provider reports an invalid FabricId (WWN) for this switch.  This isolates the switch into a separate fabric with an invalid fabric name.  ISL links to other switches are not displayed.
Symptom: FC9000 switch is listed in a separate fabric in System Explorer.  ISL links are missing.
Solution: Fix the SnmpSwitch provider to return the correct fabric id for FC9000 switches that are not the primary switch in the fabric.  The provider is retrieving the fabric id from an SNMP OID that the FC9000 switch does not populate.  The solution is to get the information from a different place in the MIB.
 
7741 - Truncated report names in enterprise reporting
Problem: Global reports site names are truncated after 6 characters.  
Symptom: While configuring the Global reports, we can provide site names with the maximum length of 32 characters. While showing the data in reports, the site names are truncated after 6 characters.
Solution: In the Global reports catalog file changed the site name precision to 256 characters.
 
9168 - Support for CNT UMD switch
Problem: Need to support CNT UltraNetR Multi-service Director (UMD) switches.
Symptom: Support for CNT switches is accomplished in HSSM through the SnmpSwitchProvider. The UMD switch supports multiple logical domains.  Because of this, the SNMP tables for the UMD are indexed differently than the SNMP table for all other CNT switches.  In addition, there is a CNT proprietary MIB that is not used by other CNT switches.  These things cause discovery to fail for UMD switches. 
Solution: Add additional code to the discovery portion of the SnmpSwitch provider to discover UMD switches.  Also, new code will be added to the provider to gather information from the SNMP tables of the UMD switch correctly.
 
9121 - McData Fabric ID reporting
Problem: McDATA switches discovered through EFCM using SNMP are sometimes showing the wrong FabricId.
Symptom: When the incorrect FabricId is reported for a switch, the System Explorer shows the switch in the wrong fabric.  This affects the topology view, path view, and reports.
Solution: The CLI will report the incorrect FabricId.  When getting SNMP information about a switch from EFCM, the FabricId of the switch is not reported directly.  The EFCM only tells whether the switch is the primary switch in the fabric or not.  If the switch is the primary switch, the FabricId is the WWN of the switch itself. If the switch is not the primary switch in the fabric, it is necessary to follow all ISL links from the switch to other switches in the fabric, and determine if any of them is the primary switch.  This process is followed until the primary switch is found.
 
9131 - Removing a LUN initiator
Problem: This fix is for Remove Initiator.  This command is found in the provisioning UI, luns tab, when a lun is deleted.  In the dialog that displays, removing a LUN Initiator (in a Host Group that has more than one initiator) removes all the initiators from the Host Group.
Symptom: If the user has more than one initiator for a host group, removing any one initiator will delete all of the initiator?s in the host group.  This is in addition to the one the user requested to be deleted.
Solution: Delete the host and host group, only if no other initiators are associated with them.  
1. delete host if there are no more host ports in that host.
2. delete the host group if there are no more hosts in that host group
 
9159 - Replication of Symmetrix RAID 5 volumes and pools
Problem: Symmetrix DMX systems with Enginuity 5670+ do not show RAID 5 pools and volumes. 
Symptom: The storage pool and storage volume navigation pages for Symmetrix DMX systems with Enginuity 5670+ do not show any pools or volumes that have RAID 5 raid level.
Solution: The problem occurred during the transition from EMC WideSky libraries version 5.1 to version 5.3.  RAID 5 is new in WideSky 5.3.  The code to support RAID 5 should have been added to Storage Authority during the transition, but this was never done.  This patch adds the necessary code to handle RAID 5.
 
9331 - Upgrading from SA 3.5 to ESM 3.0/3.0.1 does not run PopulateMappingData.sql
Problem: Seed data changed but was not included as part of the upgrade when it needed to be.  As a result, APPIQ_SnmpSwitchRemoteComputerSystem and APPIQ_SnmpSwitchRemotePort objects are replicated.
Symptom: Discover and sync QLogic and/or CNT switches.  RemoteConputerSystems will appear in the System Explorer.
Solution: Created a script which reruns the PopulateMappingData.sql file and create all the missing seed data. The script cleans up the database for any APPIQ_SnmpSwitchRemoteComputerSystem, APPIQ_SnmpSwitchRemotePort object replicated before running the patch.

Patch Installation Instructions:
----------------------------- 
1) Navigate to the directory where the Sun StorEdge Operations Manager is installed.
2) Set file permissions on install/setvars.sh to EXECUTE, and execute that script.
3) Execute /etc/init.d/appstormanager stop
4) Navigate to the directory where you unzipped this patch, and execute 118985-06/SP_3_6_1_6.bin
5) Follow the resulting on-screen patch installation instructions.
6) Execute /etc/init.d/appstormanager start
 
Special Installation Notes:
Either the "-i silent" or "-i console" switch may be used if needed.
 
Version Notes:
Navigate to the directory where the Sun StorEdge Operations Manager is installed.
The file Version.txt contains the version string for the product.
	Base version string: 3.6.1.42
	After patching: SP_3.6.1_n  (where "n" is the revision number of the patch)

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

None.

README -- Last modified date:  Friday, June 17, 2005

