Fixed compatibility issue when installing Foglight for Storage Management 4.3.0 on Windows® 10.
Fixed issue where the unit of Available Capacity was not displayed correctly in reports.
Fixed issue where NetApp Cluster - Ports - Topology Tab - Port Dependencies was not displaying the SVM and LIF columns.
Fixed issue where the VMAX IDs were not in the expected format.
Updated the Foglight for Storage Management Installation Guide with the correct requirements for VMAX arrays.
Improved the message description for errors triggered during the validation/collection, when not collecting from Enterprise Manager.
The following is a list of issues resolved in hotfixes issued for the previous release. These issues are also fixed in this release.
Issues also resolved in the 220.127.116.11 hotfix
NetApp Cluster - LUNs are not connected in the SAN topology view unless a NAS/NFS share is also present to the same ESX/Hyper-V host.
NetApp Cluster Mode sometimes fails to report the volume state. The agent does not issue a NullPointerException in this case.
NetApp Cluster - Identical portset and initiator group names (igroups) between Storage Virtual Machines (SVMs) may collide.
Issues also resolved in the 4.3.1 hotfix
Enhanced support for Hitachi Tuning Manager custom path installations
Note: Deactivate and activate the Storage Collector Agent that has Tuning Manager enabled to collect performance data once the agent is created.
The following is a list of issues known to exist at the time of this release.
Issue with Isilon pool query command.
Isilon OneFS 8.0: Unable to create Isilon Agent due to not being able to authenticate target.
After upgrading to FSM 4.3 from 4.0, external FglAMs may not appear in the list of agent managers on the Agent Managers dashboard. If this occurs, restart the external FglAMs.
Installation failed when install Foglight/FVE/FSM with embedded DB to Windows %PROGRAMFILES% dir.
FSM 4.2 to FSM 4.3 upgrade may fail as a result of the Storage database not shutting down completely during the upgrade.
Workaround: If this occurs, proceed with the following steps to correct the issue:
If both valid and invalid credentials are provided for the system to be monitored, it is possible for the valid credential to not be found or used. The invalid credential should be manually deleted in this case.
Capacity trending and time-to-full predictions are not available for storage elements that are not being actively monitored by an agent.
NetApp System-api-list calls made to determine what other API calls are available may trigger log messages on the NetApp system regarding access permission on the NetApp console. Foglight for Storage Management does not call these other API methods.
In some system configurations, the topology links between storage items and hypervisor systems may not be created or displayed properly under San Data Paths tab. A specific cause has not yet been identified.
ASP settings of Storage Agent Collect is getting corrupted after upgrading to FSM 4.2.x.
Unable to create Storage Support Bundle after upgrading to 4.2.
Repeatedly deploying the same Python Agent cartridge to a FglAM agent manager can consume more than the required amount of memory. Restarting the agent manager will correct this until the next redeployment.
NetApp - Used in Monitored Environment value under Summary is incorrect for NASVolumes.
The upgrade of agents to version 4.2 can take longer than usual to complete. The upgrade is expected to eventually complete without error however.
NFS mounts differentiated by StorageVirtualMachine are not "attached" to Virtual Machines.
Compellent arrays: Incorrect error message shown for bad credentials.
Daylight Saving Time (DST) change causes Compellent agent to request data for an incorrect time range. Stopping and starting the agent corrects this.
In certain configurations VM images on CIFS volumes mounted from NetApp shares may not display in the SAN topology graph.
VM to LUN mapping calculations can fail.
SAN topology mapping is inconsistent.
NullPointerException when submitting Equallogic LUN status.
Storage Management Roles: Cannot create Storage reports.
After upgrade to FglAM running as root, new Postgres versions will refuse to start.
Workaround: FglAM and FMS server must not be run as root.
Links between VMware® and Storage disappear during CDT replay.
Values for the protection level obtained from Clariion arrays may be different if collected using the command line from those collected using an SMIS connection.
Some NetApp filter instances will display no information for IP and FC ports.
NetApp filer volume available capacity values are different for overcommitted volumes.