Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 15

Issue ID MDT-355259 MDT-353892 MDT-349885 MDT-346706 MDT-338550 MDT-334129 MDT-261240 MDT-258656 MDT-143340 MDT-364566 MDT-308912 MDT-413595 MDT-403276 MDT-395179 MDT-393775 MDT-365546 MDT-359217 MDT-357698 Functional Area Description Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts Notifications and Alerts PowerStore CLI PowerStore CLI PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) When SSD drive is marked as failed in management due to previous errors, but is reported healthy due to self healing attempts, an eject/reinsert loop may be triggered resulting in repeating removing/reinserting alerts Frequent DB vacuuming caused by event processing running in a tight loop due to duplicated events. Switching to ESX maintenance mode while Disable Support Notifications is already enabled will shorten the remaining period of the maintenance window to one hour. On systems with many SSDs or initiators: upon starting the system (after a planned or unplanned system stop), the system may issue too many events in a short period of time, causing some alerts to not be cleared as they should. Enabling RSC (Remote Secure Credentials) after it failed might succeed but will not clear the previous failure alerts (alert Event Code 0x00400703). Event processing exceptions causing database fragmentation was leading to frequent database space alerts. Unclear alert "Error disconnecting initiator group from storage" while trying to delete a host from a host group while the host is still bound to Virtual Volumes. When adding an appliance to the cluster, or creating a new cluster, the validation job may show as failed. The following alert that is raised on a NAS server might not be cleared even after system comes out of an Out of Space (OOS) state for NAS: "Failed to set NAS Server back to Read/Write mode & Failed to set NAS Server back to Read/Write mode" If the system is back from the OOS state and the NAS Server is fully functional, either ignore the alert or manually acknowledge and clear the alert. The "svc_ntp_ctl" service script may show an old NTP server that was added earlier when running v1.x and not the new NTP added after the upgrade to v2.x. The ID of remote syslog server is not displayed in the PowerStore CLI command "remote_syslog_server show" The remote syslog feature may inflate the management database by sending the same logs again and again which may cause the automatic database cleanup to fail. Eventually, if alerts about the database space usage are not handled by support, the lack of space on the management database can cause management commands (PowerStore Manager, CLI, or REST API)) to be "not available" until manually cleaned. Login to PowerStore Manager may failed with timeout due to performance or capacity metrics rollup failure. Management functions may be limited because of some internal commands not acknowledged and left in the internal management database. A false positive alert, "Metadata Validation Error (DATA_PATH_SCHEDULE_NAMESPACE_RECOVERY_LATER)", may be raised due to a rare condition in the data path. Some internal commands were not cleared following a successful execution and left in the management database. In the PowerStore T Initial Configuration Wizard (ICW), on the vCenter Information (Optional) screen, the hover text for the Your vCenter Information info icon should read: vCenter account information with administrate role and privileges recommended." as it is recommended, not required. Management database may become almost full if identical system events are submitted. Resolved Issues 15