The issues listed in the following table have been resolved.
| Issues |
|---|
| [13745415] Communication with the Pilot not established after a SAN connection: If a SAN connection to an Oracle FS System was established after the FSPM daemon had started on the host, FSPM might not discover that system and establish a management connection to its Pilot in a timely manner. |
| [16803514] Dynamically added HBA ports not automatically detected: FSPM did not necessarily notice when Fibre Channel (FC) HBAs were added dynamically to a host at runtime, and so often did not automatically add the FC HBAs to the host definition in the Oracle FS System. |
| [19693021] FSPM periodically not communicating with the Pilot: When many changes were detected at the host in quick succession, FSPM could lose communication with the Pilots for a while, and then reconnect. |
| [20105124] Limit of 2048 LUNs in communication with the Pilot: FSPM and the Oracle FS System Pilot were only able to exchange information about 2048 LUNs, instead of the 4096, which were supported. Information would only be displayed correctly in the user interfaces for 2048 LUNs on each host. |
| [22952241] Errors at the host cause inappropriate load balancing settings: The load balancing settings for LUNs could get set to unexpected values when certain transient errors happened on the host. |
| [23499175] FSPM daemon boot disruption: In unusual conditions during host boot, the starting of the FSPM daemon could be disrupted. |
| [23733362] FSPM daemon shutdown timeout: Some error conditions could cause an FSPM daemon shutdown to take longer than expected, causing the Service Management Facility to time it out. |