Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 16
Update of File System policies Access, Locking and Folder Rename, while the NAS Server
View all Dell PowerStore 5200T manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 16 highlights
Issue ID MDT-348290 MDT-342144 MDT-324043 MDT-321516 MDT-314145 MDT-294859 MDT-216469 MDT-214910 MDT-201466 MDT-358444 MDT-339330 MDT-145911 MDT-101588 MDT-400497 MDT-372280 MDT-213516 Functional Area Description PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore Manager (GUI) PowerStore REST API PowerStore REST API PowerStore REST API PowerStore REST API Security Security Security File system policies modification by PowerStore Manager are not being updated An inaccessible SMTP server could cause PowerStore Manager to fail to load. Hardware events on single appliance in dual appliance cluster could result in appliance in service mode, this will result in failure to reach quorum and GUI inaccessible. Update of File System policies (Access, Locking and Folder Rename), while the NAS Server is configured with only NFS protocol, are not updated appropriately although it shows success in PowerStore Manager. Jobs with null start times may appear in the PowerStore Manager 24-hour Jobs page more than 24 hours after the job has completed. In PowerStore Manager, the Express Service Code field is sometimes missing from the Hardware > Appliances page. Internal standby database went down but internal database replication didn't pause or disable causing management commits to be blocked making PowerStore Manager unavailable. Some resource types are not labeled properly, and related jobs are declared incorrectly in PowerStore Manager. Incorrect SNMP or SMTP configuration could affect work for another internal processes. PowerStore behavior is different if LUN is specified manually and auto-generated. If it is auto-generated we check the LUN is not exceeded 254 (for Windows). And it is not checked if is it set manually. Under certain high latency workloads, performance metrics REST queries time out. In such cases, the errors "Request timed out" and "Error retrieving data" are displayed by PowerStore Manager when attempting to display capacity and performance. Restarting the ControlPath (CP) restored metrics calls using REST, but the above errors are still seen from PowerStore Manager. Unable to change the NetBIOS name while creating or editing a NAS server with AD Joined SMB server in PowerStore Manager. REST GET requests for nested parameters fail and return a 400 HTTP response code. Ports used for internal communication will only be exposed internally within the PowerStore appliance to eliminate the security concern. Improved password complexity hints, password requirements and error handling messages when password entered doesn't meet these requirements. DNS is not supported for LDAP. MDT-396137 Serviceability PowerStore MIB does not include Timestamp in imports list MDT-331288 Serviceability MDT-413999 Storage - Block Request to include active alerts in the "svc_health_check" service script and to provide more details in the case of a failing or warned check. A rare timing issue can lead to a kernel process being delayed, resulting in a node reboot MDT-389953 Storage - Block If inter-node communication is lost while both nodes are committing updates to the same metadata, and power to both nodes is lost, the array could see metadata inconsistencies. 16 Resolved Issues