Known Oracle FS System and Pillar Axiom Issues

The following issues are associated with the listed versions of the Oracle FS System and Pillar Axiom systems.

Table 1 Known Oracle FS System and Pillar Axiom issues
Fixed in release	Issue	Workaround or planned fix
5.0	[13759030] If an iSCSI initiator is connected to a port on a Controller (Slammer), and that Controller (Slammer) is powered off, the GUI displays the LUN and Host connection status for the iSCSI initiator as `Connected`.	This issue is fixed in release 5.0 of the Pillar Axiom software.
5.0	[13759805] If more than 256 SAN LUNs are configured on an Pillar Axiom, the GUI can send invalid messages to the FSPM daemon running on SAN host systems. The control path connection between FSPM and the Pillar Axiom continually moves between `Communicating` and `Not Communicating` states. This prevents features that depend on the FSPM control path (such as setting the load balancing algorithm) from working properly. The data path, which manages LUN access from the host, is not affected.	This issue is fixed in release 5.0 of the Pillar Axiom software.
5.2.1 (and 4.5.1)	[13764609, 13762326] While the system is recovering from temporary use of non-optimized paths to the alternate Controller (Slammer), there can be a decrease in I/O performance between a LUN and a Controller (Slammer).	This issue is fixed in release 4.5.1 or higher and 5.2.1 or higher of the Pillar Axiom software. If the Pillar Axiom is running a release earlier than 4.5.1 or 5.2.1, you can perform the following actions: Re-home the LUN to the alternate CU on the Controller (Slammer) by following the instructions in the Oracle Flash Storage System Administrator’s Guide to re-home the LUN. Re-home the LUN again to the Controller (Slammer).
5.4	[13764561] The GUI sometimes continues to display host paths that are no longer valid after FSPM stops. FSPM no longer communicates path information to the GUI and the GUI continues to display the host paths as if FSPM was still running.	This issue is fixed in release 5.4 of the Pillar Axiom software.
5.4	[14581579] A defect in the Pillar Axiom software prevents proper creation of an FSPM host entry in the management server when there are more than 1024 LUN mappings to the initiators associated with the host, and the mappings differ between the initiators. You can recognize this defect in the GUI when the following symptoms occur together: The FSPM host is not communicating. The system displays the following `TaskFailed` system alert: UNSATISFIED_REQUEST_PMI_COMMUNICATION_ERROR	This issue was fixed in release 5.4 of the Pillar Axiom software. For Pillar Axiom software version 5.3 or earlier, take the following actions: Stop the FSPM service on the host. Manually update the mappings on all of the host initiators so that all initiators see the exact same set of LUNs with the same LUN number. To enable the host to configure itself, restart the FSPM service.
5.4	[14747038] The Pillar Axiom software is sometimes unable to configure the load balancing setting for LUNs on FSPM hosts. Attempts to change the load balancing setting through the GUI or CLI fail with the following error: Unsatisfied request due to internal error	This issue was fixed in the release 5.4 Pillar Axiom software.
6.1	[17478592] When HP-UX mode is selected for a host, the Pillar Axiom System enables configurations to be created which are not compatible with HP-UX mode. HP-UX mode is not actually enabled in these cases even though the configuration says that HP-UX mode is enabled.	Workaround: before enabling HP-UX mode for a host entry, make sure no unmapped (globally visible) LUN is assigned LUN number 0. Also make sure no LUN is mapped to the host entry with LUN number 0. After HP-UX mode has been enabled for a host entry, ensure that no unmapped (globally visible) LUN is subsequently given LUN number 0, and that no LUN is subsequently mapped to the host entry with LUN number 0.